2
5 Comments

Show IH: I built a personal finance app and now I need 12 beta testers to get past Google Play's gate

I've been building Money Me -- a personal finance app for tracking spending, income, budgets, and savings goals. No bank syncing, no data harvesting. You enter what you want to track, nothing more.

The web app is live at money-me.com and works well. I wrapped it as a TWA (Trusted Web Activity) for Android -- same app, native wrapper.

Here's the problem: Google Play requires 12 testers opted into your closed beta for 14 consecutive days before they'll let you publish to production. Makes sense as a policy, but as a solo dev with no existing audience, it's a real bottleneck.

If you've got an Android phone and wouldn't mind keeping the app installed for a couple of weeks, I'd really appreciate the help:

https://play.google.com/apps/testing/com.moneyme.twa

You can also try the web version first at https://money-me.com -- it's the exact same app.

Every tester gets 6 months of Premium free once we hit production.

Happy to swap beta tests if you're building something too -- drop your link and I'll return the favour.

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

    The TWA approach is smart — avoids rebuilding the whole thing natively while still getting Play Store distribution. Writing up the technical story separately was a good call too, that kind of transparency builds trust with early adopters.

    The 12-tester requirement is one of Google's more frustrating policies for solo devs launching without an existing audience. Have you tried reaching out directly to people in personal finance communities who might be interested in a privacy-focused budgeting tool? That angle tends to resonate with people who are already skeptical of apps that harvest their data.

    Putting "no bank syncing, no data harvesting" front and center in your Play Store listing copy rather than burying it in the description could make a real difference for conversion.

  2. 1

    For the 12-tester gate, the highest-signal testers are the ones who run a scripted real flow, not just install. With Kinetic Override I’d ask Android testers to grant the permission, record one tap/swipe loop, replay it twice, then tell me where trust or timing broke. That kind of checklist makes beta feedback much less vague.

  3. 1

    Congrats on launching Money Me! Your focus on privacy and manual entry really addresses a big concern in personal finance apps today. Naming and branding are indeed critical for user trust, so testing different options with your target audience sounds smart. I'd love to hear how you’re handling user feedback during beta testing and if you’ve considered AI-assisted categorization to ease manual input without compromising privacy. At Centscribe, we also emphasize practical money routines and manual transaction review, so I’m curious if you’ve explored similar features. Would you be open to sharing what’s working well or any challenges you’re facing? It’d be great to exchange insights on building user trust and engagement in this space.

  4. 1

    Quick update: I wrote up the full technical story on dev.to for anyone curious about the TWA approach and what actually broke along the way: https://dev.to/markusbnet/how-i-shipped-my-pwa-to-google-play-as-a-twa-and-what-actually-went-wrong-392j

    Also wrote the backstory on why I built yet another budgeting app: https://dev.to/markusbnet/why-i-built-my-own-budgeting-app-and-yes-i-know-there-are-hundreds-already-3a41

  5. 1

    The product direction is clear, but the naming is the part I would seriously pressure-test before the Play Store launch.

    Personal finance apps are trust products. People decide very quickly whether something feels safe enough to track income, spending, budgets, and savings. “Money Me” explains the category, but it also sounds very generic and lightweight for something handling private financial habits. The hyphenated domain adds a little more friction too, especially if you want users to remember it, recommend it, or trust it from search/app store results.

    The strongest angle here is not “another budget tracker.” It is private, manual-control personal finance without bank syncing or data harvesting. That deserves a name that feels more premium and trustworthy from the first impression.

    Beryxa.com would fit that direction better if you want the app to feel more like a serious private finance product instead of another lightweight budget tracker. Since you are still before Android production release, this is exactly the point where the name is easiest to fix.

Trending on Indie Hackers
The hardest part isn't building anymore User Avatar 110 comments The feature you're most sure about is the one you should question first User Avatar 67 comments I sold $6,773 in 2 weeks, with almost no existing community. User Avatar 63 comments I let 3 LLMs argue on the famous AI "Car wash: Walk or Drive" problem to prove a point. User Avatar 47 comments Before you build another feature, use this workflow User Avatar 45 comments I spent months chasing clients who already had a webmaster. So I built something that only finds the ones who don't. User Avatar 34 comments