Quick answer
If you have a personal Google Play developer account created after 13 November 2023, you must run a closed test with at least 12 testers who have stayed opted in continuously for at least the last 14 days. Only then can you apply for production access and publish to everyone. Google decides whether to grant access.
The rule in one paragraph
Google introduced testing requirements for new personal developer accounts in November 2023 to improve app quality on Google Play. According to Google's Play Console Help page on app testing requirements, developers with personal accounts created after 13 November 2023 must run a closed test with a minimum of 12 testers who have been opted in continuously for at least 14 days. Until then, the Production and Pre-registration tracks stay locked in Play Console. When you meet the criteria, you apply for production access from the Dashboard and answer questions about your app and your testing.
Google has changed the details before — the number of testers was originally higher — so always check your own Play Console before you plan dates.
Who it applies to
| Account | Does the rule apply? |
|---|---|
| Personal account created after 13 November 2023 | Yes |
| Personal account created before that date | Generally no — check Play Console |
| Organization account | The requirement is aimed at personal accounts; organization accounts have their own verification steps |
If you are unsure which account type to choose, read personal vs organization developer account.
What the words actually mean
- Closed test — a private release track. Only testers you invite, by email list or Google Group, can join. See closed vs open vs internal testing.
- 12 testers — at least 12 people opted in. Aim for more than 12 so one person leaving doesn't drop you below the line.
- Opted in — the tester has accepted your test through the opt-in link using their Google account.
- Continuously for 14 days — the count must stay at 12 or more for the whole 14-day window, not just on the last day. See why the clock can reset.
Why testers need to actually use the app
The numbers get you to the point where you can apply. After that, Google reviews your application, including questions about how you tested, what feedback you received and what you changed. Developers commonly report rejections when testers opted in but barely used the app.
Plan short daily tasks so testers use different features across the 14 days, and keep a record of the feedback and the fixes you made. It gives you real answers for the application and a better app on launch day.
A simple 14-day plan
- Before day 1: upload a stable build, set up the closed track, write the opt-in instructions, recruit 15–20 testers.
- Days 1–3: install, onboarding, core feature. Collect first-impression feedback.
- Days 4–10: one feature or scenario per day; fix critical bugs and push updates.
- Days 11–14: regression check, final feedback round, write down what you changed.
- After day 14: apply for production access with specific, honest answers.
Our closed testing tracker shows your day count and earliest application date, and how to prepare for a Google Play closed test covers setup in more detail.
Frequently asked questions
Can I use my friends as the 12 testers?
Yes, anyone with a Google account can be a closed tester if they opt in. The hard part is keeping 12 or more people opted in and genuinely using the app for 14 days, which is why many developers use a structured testing service.
Do testers have to keep the app installed?
Google's stated requirement is about testers being opted in. In practice, genuine use across the period gives you useful feedback and better answers for your production access application.
Does passing the test guarantee approval?
No. Meeting the criteria lets you apply. Google reviews the application and decides.
Does the rule apply to updates?
The requirement is about getting production access for a new personal account. Once you have production access, check Play Console for how it applies to further apps on that account.