Who has to do this
The rule is for personal developer accounts created after November 13, 2023. If your Google Play account is one of them, your app cannot go straight to production. Google first wants proof that real people tested it.
The rule in one sentence
You run a closed test with at least 12 testers who stay opted in for at least 14 days in a row, and at least 12 testers must still be opted in on the day you apply for production.
Step by step
- Create the closed test. In Play Console, open Test and release › Testing › Closed testing and create a track. Add your testers as an email list or a Google Group.
- Upload your app. Add an app bundle to the closed track and send the release for review.
- Invite the testers. Share the opt-in link. Each tester opens it with the same Google account you added, accepts, and installs the app from Google Play.
- Keep them in for 14 days. Tell every tester to stay opted in for at least 14 days. Testers who leave before that do not count.
- Collect feedback. A group chat for your testers makes this easy, and Google suggests one too. Write down what they found and what you fixed.
- Apply for production. After 14 days, open the Dashboard in Play Console and click Apply for production. Google asks questions in three parts: about your closed test, about your app, and about your production readiness.
- Wait for the review. Google says it usually takes seven days or less, but it can take longer. When it is approved, you can publish to production.
Common mistakes
- Using internal testing. Internal testing is a different track. The rule asks for a closed test.
- A different Google account. A tester who opts in with another account than the one on your list does not count.
- Exactly 12 testers. If one leaves, you drop below 12. Invite a few more.
- Testers who leave on day 10. The 14 days must be continuous. Explain this before they join.
- Thin answers. In the production application, describe the real feedback, how you collected it, and what you changed. One-line answers make a weak application.
Our own apps went through it
Our game Dot Rivals went through this exact process: a closed test, the production application, and then its launch. It is live on Google Play today. Our dua app, DuaSpot, is in its closed test right now.
Need help publishing?
We set up the store listing, the closed test and the production application, and we stay with you through the review. If your app was built by someone else, we can publish it too, from your own developer account.
Is your app ready for Google Play’s new rules?
Send us your app’s Google Play link. We look at it and tell you, free, what Google’s new rules mean for your next update: target API 36, 16 KB page support, and the 12-tester test for new accounts.
Need more than a check? Tell us about your app and we reply within 24 hours.
Questions
Does internal testing count?
No. The rule asks for a closed test. Internal testing is a separate track and does not count toward the 12 testers.
Can my friends and family be the testers?
Yes. Any people with a Google account can be testers, as long as they opt in and stay opted in for at least 14 days in a row.
What if a tester leaves early?
Testers who opt in, test for fewer than 14 days and then opt out do not count. Add a few more testers than 12, so one person leaving does not reset your plan.
How long does the production review take?
Google says the review usually takes seven days or less, but it can sometimes take longer.
One email a week for app owners
Our newest guide and one practical tip from our work. No spam, and you can unsubscribe with one click.
We send a confirmation email first. Privacy