Flutter & Mobile Engineering

Google Play's 12-Tester Rule: Plan Your Android Launch

By Muhammad Bilal Shakoor, Co-founder · Published · Last updated

Google Play requires personal developer accounts created after 13 November 2023 to run a closed test with at least 12 testers, opted in continuously for 14 days, before they can apply for production access. Google says the review usually takes seven days or less. For a founder that is about three weeks of calendar time once the app is testable, so start the closed test as early as the app is stable enough for real users, and recruit testers before you need them.

What is Google Play's closed-testing rule?

Google's Play Console Help page says personal developer accounts created after 13 November 2023 must run a closed test for their app with a minimum of 12 testers. The testers must have been opted in for the preceding 14 days. Until that is met, Production and Pre-registration stay disabled for the app.

Two details catch first-time publishers. A tester who opts in and leaves before 14 days is not counted. A tester who leaves and comes back counts only if the 14 days are consecutive. Plan for more than 12 sign-ups, because the count that matters is the one still opted in on the day you apply.

The rule, from Google's help page

  • 12

    testers at minimum in a closed test

  • 14

    days they must stay opted in, continuously

  • 7

    days a production-access review usually takes, at most

Does the rule apply to your account?

Google's page names personal accounts created after 13 November 2023. It does not list organization accounts or say they are exempt, so do not assume either way. Open the Dashboard in your Play Console: it shows whether the requirement applies to your app.

The account type matters before you start. Google's developer-details page says the account type is read-only and reflects the choice made at sign-up. Google's sign-up page lists a one-time US$25 registration fee and says you may be asked for a government ID and a card in your legal name. Organization accounts add organization details, which Google's page says come from your payments profile and include a D-U-N-S number. Google says applying for a D-U-N-S number through Dun & Bradstreet is free. Choose the type that matches who legally owns the app, not the one that looks like a shortcut.

How much time does it add to your launch?

The arithmetic is simple. The 14-day window is the floor. Add Google's usual review time of seven days or less and the best case is 14 + 7 = 21 days, about three weeks, from the day your twelfth tester opts in. Google says the review can occasionally take longer, and it may ask you to keep testing if you have fewer than 12 opted-in testers or they were not engaged enough. Every restart adds another window.

Google's testing-tracks page adds that first-time publication can take several hours before open and closed test links become available. Do not leave closed-test setup to the last afternoon.

Path to production for a new personal account

  1. 1

    Finish app setup in Play Console

    Closed testing needs only a completed app setup.

  2. 2

    Start the closed test and share the opt-in link

  3. 3

    12 testers stay opted in for 14 days

  4. 4

    Apply for production from the Dashboard

    A three-part form.

  5. 5

    Google reviews the application

    Usually seven days or less; can take longer.

What counts as a closed test, and what does not?

Internal testing is the right place for your own team and early QA. Google's testing-tracks page says closed testing is for wider, targeted groups, and open testing only becomes available once production access is granted. Testers cannot post public reviews and their feedback does not affect your public rating.

Internal and closed testing, per Google

Internal testing

  • Up to 100 testers, listed by email address.
  • Builds reach testers within minutes.
  • Can start before app setup is finished.
  • Does not count toward the 12-tester requirement.

Closed testing

  • Email lists or Google Groups.
  • Not searchable on Google Play: you share the opt-in link.
  • Testers need a Google Account and must opt in themselves.
  • This is the track the requirement is about.

What does Google ask when you apply?

That form is why recruiting twelve silent accounts is a poor plan. Google asks how engaged the testers were and what you changed because of their feedback. Real testers, such as customers, staff and friendly users with different phones, also find the crashes and missing screens Google tells you to fix before review. If your app needs a sign-in, Google asks for working login credentials.

The application form has three parts

  • About your closed test

    How easy testers were to recruit, how engaged they were, a summary of feedback and how you collected it.

  • About your app

    Target audience, value proposition and estimated first-year installs.

  • About production readiness

    Changes you made after testing and how you judged the app ready.

How should a founder plan around it?

  • Decide the account type first, and who owns it, before anyone pays the fee. It cannot be changed in settings afterwards.
  • Open the Dashboard early and read what it says applies to your app.
  • Recruit testers while the app is still being built. Aim for comfortably more than 12 so dropouts do not reset the window.
  • Start the closed test with a stable build, not a demo that crashes on the second screen.
  • Keep a simple feedback log: who tested, what they reported, what you changed. You need it for the form.
  • Put 14 days plus review time on the launch calendar for Android, and let iOS go out first if the dates collide.
  • Do not buy a testing service on the strength of a blog post. Google's page does not mention any, and its form asks about real engagement.

Some older guides quote a different tester count and some describe extra engagement checks. Only the wording on Google's own page is authoritative, and it can change, so re-read it the week you plan to start.

What is the next step?

Work back from the date you want the app live on Android. Subtract the review week and the 14-day test, and that is the date the closed test must start. If that date is already behind you, the honest options are to move the launch or to launch on iOS first. Apple's checks are a separate list, covered in our App Store checklist.

Read: App Store review checklist for founders

Mobile app development services

Sources

Related guides

Talk to an engineer about your project

Start with a free project call. We learn what you are building and recommend the right next step, with no pitch.

Book a call