Google Play closed testing: 12 testers for 14 days, explained

The short answer

If your Google Play developer account is a personal account created after November 2023, Google will not let you publish to production straight away. You first run a closed test with at least 12 testers who stay opted in for at least 14 days in a row, then apply for production access from Play Console. Organisation accounts do not have this requirement.

• Who it applies to: new personal developer accounts, not organisation accounts.
• What you need: a closed testing track with 12 or more testers opted in for the last 14 consecutive days.
• What comes next: you apply for production access and answer questions about your test; Google reviews the answers before you can publish.

Why Google asks for it

The rule exists to stop untested and throwaway apps reaching the store. Google wants evidence that real people installed your app, used it and that you acted on their feedback. Treat it as a real beta, not a box to tick: the production-access form asks how you recruited testers, what feedback they gave and what you changed.

How to pass it the first time

• Recruit more than 12 testers (15 to 20) so a few dropping out does not reset your count.
• Use people who will actually open the app: customers, staff, friends who match your audience. Share the opt-in link and check each one has joined.
• Keep every tester opted in for the full 14 days; the clock counts consecutive days.
• Ship at least one update during the test that fixes something testers reported, and keep notes of the feedback.
• Before applying, make sure the store listing, privacy policy, data safety form and content rating are complete and match the app.

Why production access gets refused

• Too few testers were opted in for the whole 14 days.
• Testers joined but barely used the app, so there is no sign of real testing.
• Vague answers on the form: no clear audience, no feedback, no changes made.
• Paid 'tester' services with accounts that never really use the app. Google can see engagement, and it is not worth risking your developer account.

If you are refused, Google lets you keep testing and apply again. Fix the engagement first, run the test properly for another 14 days, then reapply with specific answers.

Where Wraplet helps

We plan the closed test into the release schedule from day one: the testing track, a tester plan, a feedback log and the update you ship mid-test, then the production-access answers. Two of our own apps, Pip Talk and ODDCITY, are going through this closed-testing stage on Google Play right now, so the steps above are the ones we follow ourselves.