If you've published an Android app after November 2023, you've hit the wall: Google requires a closed test with 12 testers, active for 14 continuous days, before your app can go to production. Sounds simple until you actually try it.
Here's what nobody tells you upfront, and what I learned the hard way:
The part that actually breaks people
It's not finding 12 people. It's keeping 12 people overlapping in the same 14-day window. If tester #7 installs on day 3 and uninstalls on day 9, they don't count toward your 14 days anymore — and if that drops you below 12 active testers on any given day, Google resets your progress. You start the clock over.
Google is also watching for real engagement, not just installed-app pings. If you ship v1.0 on day 1 and touch nothing until day 14, that reads as "no real testing happened" and you can still get rejected even after technically hitting the numbers.
So the real requirement is: 12 people, genuinely using your app, continuously overlapping, for two full weeks, while you're visibly iterating. That's a much harder bar than "find 12 friends."
What doesn't work (or doesn't scale)
Asking friends/family — works once. You won't have 12 friends willing to do this for every app, every time you need to re-run a track.
Buying testers on Fiverr — there's a whole gig economy around this now, which tells you two things: the pain is real, and a lot of those testers are not actually using your app, which is exactly the kind of signal Google is trying to filter out.
Posting once and hoping — a single Reddit post gets you a burst of installs on day 1 and nobody left by day 8. You need people who stick around for the full window.
What actually works
Find people who need the same thing you do. The fastest way to get a tester who won't drop off is to find another developer who also needs 12 testers for their own app right now. If you test their app for 14 days, it's very much in their interest to test yours back for the same 14 days — your incentives are perfectly aligned, which is exactly what keeps people from quitting on day 6.
Look in the right places. Developers stuck on this exact requirement post about it constantly in:
Google's own Play Console Help community
r/androiddev and r/AndroidClosedTesting (check each subreddit's self-promo rules first — some only allow it in weekly threads)
Dev-focused Discord/Telegram groups for Flutter and native Android
Track completion, not just installs. Whatever system you use — spreadsheet, group chat, or an app — you want visibility into who's actually opening your app on which days, so you can spot a drop-off before it costs you the whole 14-day window and re-approach that tester before they vanish.
Consider a reciprocal testing community instead of building your own list from scratch. This is basically what I ended up doing after burning through my personal network twice. Instead of manually chasing 12 people per app, you join a pool of other developers in the same situation — you test a few of their apps, they test yours back, and because everyone's actively working toward their own 14-day count, the drop-off problem mostly disappears (nobody wants to be the one who breaks someone else's streak, since they need the same favor back). I've been building PeerPlay for exactly this — it's free for the reciprocal track, still early, but it's solving my own problem first.
The checklist
Confirm your Google Group / tester list is correctly linked in Play Console before you start the clock
Recruit more than 12 — assume some drop-off, aim for 14-15 committed testers
Ship at least one visible update/response during the 14 days (don't go silent)
Check daily that you still have 12+ overlapping active testers, not just 12+ total installs
Have a backup tester or two on standby in case someone drops
Hope this saves someone the two failed attempts it took me to figure this out. Happy to answer questions in the comments if you're stuck on a specific part of the process.
Top comments (0)