Who it applies to
The rule covers personal developer accounts created after 13 November 2023. Until it's met, Production and Pre-registration stay disabled for your app, and open testing isn't available either.
What you have to do
Start a closed test
Upload a signed release to a closed test in the Play Console.
Get at least 12 testers opted in
Share the opt-in link with people who'd really use your app.
Keep them opted in for 14 days in a row
Collect their feedback and fix what they find.
Apply for production access
Answer Google's questions from the Play Console.
Wait for the review
Google says it usually takes seven days or less, and can occasionally take longer.
How the 14 days are counted
- The 14 days must be in a row.
- A tester who opts out before 14 days doesn't count.
- A tester who opts out and comes back starts again from zero.
- What matters is the day you apply: at least 12 testers must have been opted in for 14 days or more at that point.
Recruit more than 12. With exactly 12, one departure on day 10 puts you back under the limit.
What the form asks
- Your closed test: how easily you recruited testers, how they used the app, whether they tried every feature, what feedback you received and how you collected it.
- Your app: the target audience, the value it offers and how many installs you expect in the first year. Google doesn't show these answers publicly.
- Your readiness: what you changed after testing, and how you decided the app was ready.
Why an app stays in testing
- Fewer than 12 testers were opted in.
- Testers didn't use the app enough during the test.
- The app doesn't comply with Google Play policies.
- The app crashes, or has broken features or missing screens.
- The app needs a login and you gave no valid test credentials.
Finding your testers
Start with people who already care: your website's users, your mailing list, your customers, your colleagues. Google asks how they engaged with the app, so 12 names who never open it won't help you.
Running the test with a SaasToStore app
- A paid Android build gives you a signed
.aab: that's the file to upload to your closed test. The free test build is an APK for your own phone. - Your next builds use the same signing key, so testers receive your updates.
- A fix on your website reaches testers right away, with no new build. See what needs a new build.
Sources
Read on 1 November 2026: Google Play, app testing requirements for new personal developer accounts.