Google Play requires 12 testers opted in for 14 consecutive days before you can go to production. Sounds simple, but finding those first 12 committed testers is a real challenge.
I'm building Money Me, a personal finance app. The web app is live at money-me.com and now I'm trying to get the Android version through Google's closed testing gate.
What I've tried so far:
What's worked for you when finding early testers or first users? Any channels I'm missing?
If you want to help (Android + 30 seconds):
6 months Premium free for testers. Happy to test your app in return too.
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 Android closed testing I’d make the ask much more task-based than “please test my app.” With Kinetic Override, the useful feedback would be: install, grant the permission, record one short tap/swipe loop, replay it twice, then tell me where the trust/performance wording felt unclear. You may get better testers if each person has one concrete 3-minute scenario instead of a broad beta request.
For the Play closed-test gate, I’d make the tester ask very scenario-specific instead of “please install.” I’m doing this with Kinetic Override too: give people 2-3 tiny Android tasks that map to the real use case, then ask where trust or permissions felt confusing. That feedback is much more actionable than raw installs.
For the 12-tester gate, I’d make the ask extremely concrete: one install is not enough; ask each tester to run the same first-use checklist and report the first hesitation. For Kinetic Override, that means permission screen → record one tap/swipe macro → replay twice → note where timing or trust breaks.
The 12/14-day Android tester gate is brutal because installs alone do not prove much. For Kinetic Override I would rather find exact-fit testers who can run one real macro flow: permission screen, record taps/swipes, replay timing, then tell me where trust or timing breaks.