1
4 Comments

Show IH: Money Me - personal finance app, looking for Android beta testers

Hi all, solo dev here. I built a personal finance app called Money Me and I'm at the closed testing stage on Google Play, so I need a small group of Android testers willing to keep it installed for a couple of weeks.

The idea: a personal finance app that doesn't connect to your bank. You enter your expenses, income, savings goals and bank balances yourself, and it shows you what you've actually got left over each month. The whole point is privacy, none of your data leaves your account.

I also built an MCP for it, so you can connect it to Claude or another AI assistant and ask questions like "what did I spend on food last month" or "can I afford this".

Site: https://money-me.com

If you've got an Android phone and fancy helping me get over the line, here is the join flow (all three steps needed):

  1. Join the Money Me Beta Testers Google Group: https://groups.google.com/g/money-me-beta-testers (free, anyone can join, dedicated to this app)
  2. Click the opt-in link: https://play.google.com/apps/testing/com.moneyme.twa
  3. Install Money Me from Play Store: https://play.google.com/store/apps/details?id=com.moneyme.twa (search "Money Me" if the link does not open the listing)

Without step 1 the Play Store will say the app is not available for your device. Drop a comment when you have installed and I'll happily install yours if you are at the same stage.

Any feedback on the app or the MCP angle especially appreciated.

posted to Icon for group Show IH
Show IH
on May 6, 2026
  1. 1

    The “no bank connection” angle is a good trust hook. For permission-sensitive Android apps I’d put the safety constraint directly in the first tester script: what data stays local, what permission is needed, and what success looks like in the first minute. I’m using the same pattern for Kinetic Override because macro/automation apps need trust before features.

  2. 1

    For the Google Play closed-test stage, I’d separate “people who will stay opted in” from “people who can break the first-run flow”. With Kinetic Override, I care most about testers who can notice permission wording, local-data trust, and the first useful macro loop on a real Android device.

  3. 1

    Important update on how to join the test, the opt-in link alone is not enough. You also need to be a member of the Money Me Beta Testers Google Group. The flow is:

    1. Join the Money Me Beta Testers Google Group: https://groups.google.com/g/money-me-beta-testers (free, anyone can join, 20,000+ devs already there)
    2. Click the opt-in link: https://play.google.com/apps/testing/com.moneyme.twa
    3. Install Money Me from Play Store (search "Money Me" or open https://play.google.com/store/apps/details?id=com.moneyme.twa)

    Without step 1 the Play Store will show the app as not available for your device. Cheers.

  4. 1

    Bump. Still chasing the last few testers to clear the 12/14 gate. Useful lessons I've picked up during the closed-testing wait: (1) actually test Stripe checkout inside the TWA on a real device, the redirect handling is finicky; (2) your icon will scale weirdly on at least one Pixel; (3) the data safety declaration takes longer than the rebuild. If you're on Android and have 30 seconds, opt-in's still live above. Happy to mutual-swap if you're at the same stage.

Trending on Indie Hackers
I Was Picking the Wrong SaaS Tools for Two Years. Here's the Mistake I Finally Figured Out. User Avatar 120 comments Drop your landing page URL. I'll use Ferguson to tell you why visitors might be leaving User Avatar 102 comments I'm launching on Product Hunt tomorrow... so I audited their homepage first! User Avatar 24 comments Why Remote Teams Stop Talking (And Don't Even Notice It) User Avatar 24 comments I sold $6,773 in 2 weeks, with almost no existing community. User Avatar 21 comments Built a local-first Amazon profit-by-SKU + QuickBooks/Xero journal tool. Looking for founding users. User Avatar 20 comments