What Google actually asks for
Before an app can go live on Google Play, Google wants to see it exercised by real people on real devices. For apps using the closed testing track, that means a minimum of 12 testers opted in for 14 continuous days before you can request production access.
This isn’t a suggestion — it’s a hard gate. The Play Console will literally refuse your production-access request until the requirement is met.
Why 12 testers and 14 days?
Google’s logic is straightforward: a handful of reviewers on one device tells you nothing. Twelve testers spread across different Android versions, screen sizes and carriers surfaces the bugs that break a real launch.
The 14-day window matters too. It catches the issues that only show up after a week of regular use — battery drain, memory leaks, notification fatigue.
Common first-time mistakes
- Inviting fewer than 12 people to avoid “wasting” invites
- Testers who never accept the invite or never install the app
- Counting testers who opt out halfway through the 14 days
- Submitting for production access before the timer completes
How to get it right
Invite more than 12 — a buffer of 15–20 means one dropout won’t reset your streak. Make sure every tester actually installs the app and stays opted in for the full window. Track it daily, not on day 13.
If you don’t have that many trusted testers, that’s exactly what a closed testing service is for.