1. What the rule is. Google Play requires developers whose personal developer account was created after November 13, 2023 to run a closed test before their app can be distributed on Google Play. The authoritative page is "App testing requirements for new personal developer accounts" (https://support.google.com/googleplay/android-developer/answer/14151465): "Google Play requires personal developer accounts created after November 13, 2023, to test their apps before those apps are eligible for distribution on Google Play." Until the requirement is met, Play Console keeps Production (Test and release > Production) and Pre-registration (Test and release > Testing > Pre-registration) disabled for the app.
2. The exact numeric bar. At the moment you apply for production access, at least 12 testers must be opted in to the closed test, and those testers must have been opted in continuously for at least the preceding 14 days. Quote from the doc: "At least 12 testers must be opted in to your closed test when you apply for production access, and they must have been opted in continuously for the preceding 14 days." History matters here: when the policy launched in November 2023 the threshold was 20 testers; Google lowered the minimum to 12 in 2025. A lot of older blogs and forum answers still say 20 - treat 12 as the current number and design with a buffer on top of it.
3. What "continuous" means. The 14 days must be unbroken for each tester. From the FAQ: "Testers who opt in, test for fewer than 14 days, and then opt out do not count toward the requirement. If a tester opts out and opts back in later, the 14 days must be consecutive to count toward the minimum requirement of 12 continuous opted-in testers." Each tester carries their own clock: a replacement who joins after someone else leaves starts at zero and does not inherit the departed tester's elapsed time. Because exactly 12 is fragile, keep a few extra testers so a single opt-out does not drop you below the line at the moment you apply.
4. Who is exempt. The requirement is tied to the account type, not the app: it applies to personal accounts created after November 13, 2023. Organization (company) accounts are not subject to this closed-testing gate - but they must still clear account verification (and, for individuals, the identity/phone and address checks) before they can publish. If you have a choice of account type at registration, understand that choosing "personal" opts you into this rule; converting an account type later is not a supported self-service flow.
5. The testing tracks and how they gate each other. Internal testing: no requirement, distributes builds to a small trusted group within seconds of being added - optional but a useful first step. Closed testing: this is the track the policy is about; it must be completed before production access, and you must have completed your app setup to open it. Open testing: only becomes available after you already have production access, so it cannot be used to satisfy the requirement. Production: disabled until the closed-test criteria are met and your application is approved. In short, the only path through the gate is a closed test that meets the 12-testers/14-days bar.
6. How to actually run the closed test. Finish app setup, then create a closed testing track in Play Console (Test and release > Testing > Closed testing) and add testers - by email list or by linking a Google Group, or via a Google Groups email address. Share the opt-in (join) URL with them; a name added to a list does nothing until the person actually accepts and opts in. Keep shipping updated builds through the test so testers exercise fixed code, give testers clear instructions on what to test and how to report bugs, and open a feedback channel (email, a forum, or a messaging group). Testers can also send private feedback from the store listing. Review their feedback in Play Console on the Testing feedback page (Monitor and improve > Ratings and reviews > Testing feedback) and keep a written record - you will have to summarise it when you apply.
7. Applying for production access. When the criteria are met, open the Dashboard in Play Console and click "Apply for production". The form has three sections. (a) "About your closed test": how easy it was to recruit testers; whether testers used all available app features; whether tester usage matched expected production behaviour (and any differences you observed); a summary of the feedback and how you collected it. (b) "About your app/game": your target audience, your value proposition (how the app benefits users, or what makes the game unique), and your estimated first-year install range - this section is not shown publicly and does not affect visibility. (c) "About your production readiness": what you changed based on the closed test, and how you decided the app is ready to ship. Note the doc's warning: if you Discard or leave the page without clicking Next/Apply, your answers are not saved. Click "Apply" to submit.
8. Review and what can send you back. After you submit, Google reviews the application and emails the account owner; review usually takes seven days or less but can occasionally take longer. Google may require you to keep running the test - the stated reasons are having fewer than 12 opted-in testers or insufficient tester engagement during the testing period. If you get bounced, do not re-apply blindly: keep the test running, raise real engagement, and only re-apply once the numbers are safely above the line.
9. Compliance gates that are checked at the same time. The doc stresses that it is your responsibility to be fully compliant with all Google Play Developer Content Policies *before* applying, and that review is not a troubleshooting step - submitting a non-compliant app expecting reviewers to find problems leads to rejection, delays and longer appeals. It names four areas to double-check: app content and features (content, features and monetization models comply with policy), app targeting and content rating (the target age group and store listing settings match the actual audience and content), functional reliability (stable app, no crashes, broken functionality or missing screens), and test credentials (if the app needs sign-in, provide valid working login credentials so reviewers can test it). Run a pre-launch report (Release > Pre-launch report) to surface crashes, warnings and performance issues before you apply.
10. Practical checklist before you click Apply. (1) Confirm your account type and creation date - if it is a personal account created after 2023-11-13 the gate applies to you. (2) Have well over 12 testers opted in (a buffer of 3-5) and verify in Play Console that they all show as opted in and have been so for 14+ unbroken days on the day you apply. (3) Ship several build updates during the test and act on feedback so you have real changes to describe. (4) Keep written notes of the feedback and your responses; you will summarise them. (5) Make sure the store listing, content rating, data safety form and target audience are accurate and the app has working review credentials. (6) Fix crashes and dead screens shown by the pre-launch report. (7) Only then open the Dashboard and apply, and expect a reply within about a week. If you are on a personal account and want to avoid this gate entirely, the structural answer is an organization account - but that carries its own verification (D-U-N-S/legal-entity checks) and is not a way to skip identity verification.