For App Builders · Guide

Google Play's 12 Testers for 14 Days Rule, Explained

By Will McCullough, DigiRune Studios ·

The short answer: If your Google Play developer account is a personal account created after November 13, 2023, you cannot publish to production until you run a closed test with at least 12 testers who have stayed opted in for 14 days in a row. Then you apply for production access in Play Console and answer a short set of questions about your test. Google usually reviews the application in seven days or less.

Who has to follow the rule?

Google's testing requirement covers personal developer accounts created after November 13, 2023. Until those accounts meet it, the Production and Pre-registration features in Play Console stay switched off. Google's page names only personal accounts, so organization accounts are not covered by this requirement.

Not sure which you have? Open Play Console. In our experience, if the Production section is locked and the dashboard asks you to run a closed test, the rule applies to you.

What counts as 12 testers for 14 days?

Google asks for at least 12 testers who have stayed opted in continuously for 14 days or more when you apply. Three details trip people up:

  • The days must be consecutive. A tester who opts in, tests for a week and opts out does not count. If they opt out and back in later, their 14 days start again.
  • You need 12 on the day you apply. If a few people drop out and you fall below 12, you are not ready yet. Recruit a few extra from the start.
  • Testers must join your closed test track. They opt in through your test link and install from Google Play.

How do I set up the closed test?

  1. Finish your app setup in Play Console. A closed track needs it complete.
  2. Optional first step: use the internal testing track on your own phone. It has no requirements and catches obvious problems.
  3. Create a closed testing release, add your testers' Google accounts, and roll it out.
  4. Share the opt-in link with clear instructions: install, use the app for real, send feedback, and stay opted in for at least 14 days.
  5. Keep notes as feedback arrives. You will need them for the application.

Where do I find 12 testers?

Google suggests your personal and professional networks, communities and social media, aiming for people who match your real audience. In practice, friends and family who own Android phones are the easiest start. A small group chat for testers keeps them engaged and gives you one place to collect feedback.

Paid tester services exist. If you use one, remember that Google also asks whether testers used your features and how they behaved, so testers who install and never open the app will not help you answer honestly.

What does Google ask in the production access application?

When the 14 days are up, choose Apply for production on the Play Console dashboard. The form has three parts:

  • About your closed test: how easy recruiting was, whether testers used all your features and whether their use matched what you expect in production, and a summary of the feedback and how you collected it.
  • About your app or game: your target audience, what makes the app worth installing, and an estimated first-year install range. Google says these answers are not shown publicly and do not affect your app's visibility.
  • About your production readiness: what you changed because of the test, and how you decided the app was ready.

Save each section as you go. Leaving the page without saving loses your answers.

What happens after I apply?

Google says review usually takes seven days or less, and occasionally longer. If you had fewer than 12 opted-in testers, or Google judges the testing too light, you may be asked to keep testing. Before you apply, check the basics yourself: content rating, target audience, the app works reliably, and any login has working test credentials. Google is clear that its review is not a troubleshooting step.

How do I give myself the best chance?

  • Ship at least one update during the test that fixes something testers reported. It gives you a real answer for the readiness section.
  • Run Play Console's pre-launch report to catch crashes before testers do.
  • Judge the whole experience, not just crashes: confusing screens and slow starts cost ratings later.
  • Remind testers around day 7 and day 12 to stay opted in.

Taking your app to the stores?

The DigiRune Studios Store Launch Kit is a step-by-step guide and checklist for getting through Apple App Store and Google Play review, built from the process we use for our own apps. Apple and Google make every approval decision; the kit helps you submit ready.

See the Store Launch Kit

Sources

Store rules change. Check the official pages on the day you submit. Checked November 19, 2026.