What Google actually requires

This is Google’s rule as we read it on its help page, “Test your app with at least 12 testers before applying for production”. Google has changed the number before (it was 20), so confirm each figure on that page.

The requirement

• Who: personal developer accounts created after 13 November 2023. Google describes the rule for personal accounts; check the page for how your account type is treated.
• How many: a closed test with at least 12 testers.
• How long: the testers must be opted in continuously for at least 14 days.
• Then: you apply for production access in Play Console.

What “continuously” means in practice

Google counts opted-in testers. A tester who opts out and later opts in again starts their 14 days over. If you drop below 12 opted-in testers during the test, the clock is at risk. That is why a margin matters, and why the guide on dropouts exists.

What Google asks when you apply

The production-access application has three parts, which we paraphrase:

1. About your closed test. How easy it was to recruit testers, how engaged they were (did they use all the features, did it match expected production use) and a summary of the feedback you received and how you collected it.
2. About your app. Your target audience, what value it offers and an estimated install range for the first year.
3. About production readiness. What you changed because of the test and how you decided it was ready.

Google says it usually reviews applications within about seven days, and it can take longer. See how to answer these questions.

What the rule does not say

• It does not say how to find testers or where they must come from.
• It does not promise approval after 14 days. Google reviews the application, including your answers.
• Nothing here is a statement about Google’s other policies, including those on fake engagement or incentivised installs. Read Google Play’s current developer policies for that.

If the page above now says something different, trust the page, not this guide.