If you opened a personal developer account on Google Play after November 13, 2023, you cannot publish an app straight to production. These accounts must first run a closed test with at least 12 testers who stay opted in for 14 consecutive days, and then apply for production access. Until that happens, the Production and Pre-registration features in Play Console stay disabled.
Who the rule covers
The requirement applies to personal developer accounts created after November 13, 2023. Apps from these accounts are not eligible for distribution on Google Play until they have been tested. The date the account was created decides whether the rule applies.
Meeting the testing threshold does not unlock production by itself. You still have to submit an application, and Google has to approve it. Together the test and the application are the route to production for these accounts.
The three testing tracks
Play Console has three testing tracks, and each one becomes available at a different point. Only the closed track counts toward production access, so it helps to know which is which before you start.
| Track | When it becomes available | Role in the requirement |
|---|---|---|
| Internal testing | No requirements | Optional |
| Closed testing | After completing app setup | Where the 12-tester, 14-day test runs |
| Open testing | After gaining production access | Not available until the application is approved |
Internal testing is optional and has no requirements of its own. Open testing cannot replace the closed test, because it only opens once production access has been granted. The closed test is the one that counts.
How the 12 testers and 14 days are counted
The closed test needs a minimum of 12 testers who have been opted in continuously for at least 14 days before you apply. The word "continuously" is where many plans go wrong. The rule handles two common situations as follows:
- A tester who opts in, tests for fewer than 14 days and then opts out does not count toward the requirement.
- A tester who opts out and later opts back in must still reach 14 consecutive days.
A tester who drops out partway through does not keep the days already logged. The safest approach is to keep every tester enrolled without a break for the full period. Check the count of opted-in testers before you apply rather than assuming everyone stayed.
Forum claims that differ from the rule
Developer forums carry versions of the requirement that do not match the rule set out above. One forum post stated the requirement was 20 testers for 14 days, with the countdown starting on the day the 20th user installs the app. That figure is higher than the 12-tester minimum, and it measures the 14 days from an install date rather than from continuous opt-in.
Another forum poster claimed that each tester email must be on a unique device for an app to get production approval. The requirements described in this article say nothing about devices. Treat both forum claims with caution and plan around the 12-tester, 14-day rule.
Applying for production access
Once the closed test meets the threshold, click Apply for production on the Dashboard. The form that follows has three parts:
- About the closed test
- About the app or game
- About production readiness
The application asks you to summarise the feedback testers gave you. It also asks how engaged testers were, including whether they used all of the app's features. You then describe the changes you made and explain how you decided the app was ready.
These questions make the closed test more than a headcount. Twelve testers who opened the app once give you little to report. Testers who used the app and sent feedback give you material for every part of the form.
Before you submit
Make sure the app complies with policy before you apply. If the app requires authentication, provide valid login credentials in Play Console. Both steps belong on a checklist you complete before clicking Apply for production.
Review and what happens next
Google reviews production access applications, usually in seven days or less, though occasionally longer. The account owner is notified of the result by email.
Approval is not guaranteed. Google may require you to keep running the closed test if fewer than 12 testers are opted in or if tester engagement is insufficient. In that case the test continues, and you will need to apply again.
When the application is approved, the Production page and Open testing become available in Play Console. At that point the account can move from closed testing to a public release.
What it adds up to
For personal accounts created after November 13, 2023, the path to production runs through a closed test of at least 12 testers over 14 unbroken days. After that comes a three-part application and a review that usually takes up to a week. Allow for the test period, the review and a possible extension when you plan a launch date.
Keep testers enrolled without interruption and collect their feedback as the test runs. Check policy compliance and login details before you apply. Give less weight to forum figures that differ from the rule, such as 20 testers or one device per tester, than to the requirement itself.