Looking for 12 beta testers for a personal finance app on Google Play -- happy to reciprocate
I'm a solo dev building Money Me -- a personal finance app (PWA wrapped as a TWA for Android). No bank syncing, no data harvesting, just manual tracking of spending, income, budgets, and savings goals.
I need 12 testers opted into my Google Play closed beta for 14 consecutive days before I can publish to production. It's a quick opt-in and you don't need to actively use the app -- just keep it installed.
How to join (all three steps needed):
- 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)
- Click the opt-in link: https://play.google.com/apps/testing/com.moneyme.twa
- Install from Play Store: https://play.google.com/store/apps/details?id=com.moneyme.twa
Without step 1 the Play Store will say the app is not available for your device.
Web version: https://money-me.com
If you're building something and need testers too, drop your link -- I'm happy to return the favour. Every tester gets 6 months of Premium free once we go live.
Technical write-ups if you're curious about the TWA approach:
https://dev.to/markusbnet/how-i-shipped-my-pwa-to-google-play-as-a-twa-and-what-actually-went-wrong-392j
https://dev.to/markusbnet/why-i-built-my-own-budgeting-app-and-yes-i-know-there-are-hundreds-already-3a41
Hi,
I’m also looking for Android testers for Google Play closed testing.
I can join your test and keep the app installed during the required period.
My app is VoiceArchive — a voice recorder, call recorder and local recording archive for Android.
Package:
com.valostudio.voicearchive
Happy to reciprocate.
Hi,
I’m also going through Google Play closed testing with my Android app VoiceArchive.
I can join your test, install your app and keep it installed during the testing period.
VoiceArchive is a voice recorder, call recorder and local recording archive for Android.
Happy to do mutual testing.
For the 12-testers requirement, I’d give people one specific test script instead of a broad “try the app.” I’m doing this for Kinetic Override too: record a 5-10 second tap/swipe loop, replay it, then tell me where permission wording or timing controls felt unclear. Much easier for testers to act on.
Tried the web version a bit and I think the biggest challenge for manual finance apps is probably emotional friction, not feature depth.
Right now the dashboard already feels quite powerful, but as a first-time user I wasn’t fully sure where the “easy win” moment was supposed to happen.
A lot of people open budgeting apps while already feeling stressed, guilty, or overwhelmed about money, so the first few interactions probably matter a lot:
I also think manual-first finance products live or die on habit momentum, so reducing cognitive load early is probably more important than showing all capabilities upfront.
This lands hard, the emotional friction point is exactly what I keep underestimating. The "easy win moment" question is the one I have been wrestling with longest. The obvious candidate is the moment the available balance number on screen visibly updates after entering a single expense, because it converts an abstract worry ("am I overspending?") into a concrete, controllable signal in two seconds. But I am not certain that beats showing where the bills land for the month, which is also a relief moment. Curious which one landed for you when you tried it, or whether neither did. On habit momentum, that's why I built manual entry to be one tap from anywhere in the app rather than locked behind a category picker, but I have not measured whether that's actually moving retention or whether I just like the symmetry. If you ever fancy a deeper poke, I would value structured feedback in exchange for credit at launch.
I actually think the “visible control” moment is probably stronger than the “monthly bills overview” moment early on. Because for stressed users, immediate emotional relief usually matters more than long-term planning at first.
So seeing:
“I entered one expense → now I immediately understand where I stand”
feels psychologically lighter than:
“here’s the full financial reality of the month.”
The interesting challenge is that budgeting apps often try to teach discipline too early, while users initially come in looking for reassurance and reduced anxiety.
I also think your instinct about one-tap entry is probably directionally right.
For manual finance apps, every extra second of friction compounds over time because users repeat the action constantly. And yeah, I’d genuinely be interested in taking a deeper look at the flow later on — especially around first-session momentum and habit formation mechanics.