Personal Google Play developer accounts created after November 13, 2023 must run a closed test with at least 12 testers who stay opted in for at least 14 continuous days before they can apply for production access. Google lowered the count from 20 to 12 in late 2024. Organization accounts are exempt. After the test, you answer questions about how you tested, what feedback you received, and why the app is ready.
Who the requirement applies to and why
The requirement applies to personal developer accounts created after November 13, 2023. Google introduced it to raise app quality and reduce low-effort or malicious apps from new accounts. Organization accounts, which go through business verification, do not have to meet it, which is one reason companies should register as organizations from the start.
The rule is not just a hurdle; it is a forcing function for real testing. Apps that skip meaningful pre-launch testing often launch with crashes, confusing onboarding, and early one-star reviews that are hard to recover from. Used well, the 14 days give you feedback and stability data before your listing goes public.
How the 12 testers and 14 days are counted
Testers join a closed testing track through an email list or a Google Group and opt in through the testing link, then install the app from Google Play. You need at least 12 testers opted in, and they need to remain opted in for at least 14 continuous days. Play Console shows your progress on the dashboard.
If testers opt out and your count drops below 12, progress can be affected, so recruit more than the minimum. Aim for 20 or more committed testers to absorb drop-off. Testers need a Google account and an Android device that can install your app.
Recruit testers who give real feedback
The best testers resemble your target users: people on your waitlist, members of communities related to your app, early customers of a web product, or beta groups for your niche. Explain what you need, such as using the app a few times a week and reporting problems, and make feedback easy with a short form or in-app link.
Be cautious with tester-exchange schemes and paid services that supply anonymous testers who install and never open the app. Google asks how you recruited testers and what you learned, and an app with no engagement during testing gives you nothing to say. Real users also become your first reviewers after launch, which supports improving app ratings ethically.
Answer the production access questions well
After the test, you apply for production access from the Play Console dashboard. Google asks about the closed test, including how easy it was to recruit testers and how engaged they were, about the app's intended audience and value, and about production readiness, including what you changed based on feedback.
Answer specifically. Describe how many testers used key features, the main issues reported, and the fixes you shipped. Vague or copied answers can lead to rejection and another round of testing. Keep a simple log during the 14 days so you can answer accurately rather than from memory.
Use the 14 days for ASO groundwork
The testing window is the perfect time to prepare the public listing. Draft the title, short description, and full description from Google Play keyword research, and test captions with testers to learn which words they use for the app's main benefit. Collect their exact phrases for screenshot captions.
You can also set up pre-registration for games and apps that qualify, build your launch checklist, and prepare screenshots at the right Google Play sizes. By the time production access arrives, the listing is ready rather than rushed.
Common mistakes that restart the clock
Inviting exactly 12 people is the classic error: one or two opt out, the count drops, and the developer loses days. Another is sharing the wrong link, such as the internal testing link, or adding testers to a list that is not attached to the closed track. Check the track, the list, and the opt-in link before announcing the test.
Developers also rush the production application with one-line answers or ship a build during the test that breaks core features. Keep the app stable, log what testers do, and document every fix with a version number. If an application is rejected, read the reason carefully, address it directly, and run a better-organized test rather than repeating the same one.
A worked example: from first upload to production
A solo developer builds a plant-care reminder app on a personal account. On day one, they create a closed testing track, invite 25 people from a gardening forum and their newsletter, and share a feedback form. By day three, 21 testers have opted in. Feedback shows that the photo-identification feature is slow on older phones.
The developer ships two updates during the test, improving image processing and simplifying onboarding. On day 15, they apply for production access, citing tester counts, the performance fix, and the onboarding change. Access is granted, and the developer launches with a staged rollout and a listing built from tester vocabulary. The full process mirrors our guide to publishing on Google Play.
How to do it, step by step
- Confirm whether your account is affectedCheck your account type and creation date. Organization accounts and personal accounts created before November 13, 2023 are not subject to the rule.
- Create a closed testing trackUpload an App Bundle to closed testing and add testers by email list or Google Group.
- Recruit 20 or more real testersInvite people who match your audience so you stay above 12 even if some opt out.
- Run 14 days of structured testingAsk testers to use specific features, collect feedback through a form, and ship fixes during the window.
- Apply for production with specificsAnswer Google's questions with tester counts, issues found, and changes made, then launch with a staged rollout.
Before and after examples
Illustrative examples written for a generic app in this category, not client results. Swap in your own product, audience, and data.
Please install my app to help me get 12 testers.
We are testing a plant-care reminder app for two weeks. Use it three times a week and tell us what is confusing. Testers get early access to premium features.
Why it works: A clear, motivating ask attracts testers who engage, which strengthens your production application.
Testing went well.
23 testers used reminders an average of nine times. Main issue: slow photo identification on older devices, fixed in version 1.0.3. Onboarding reduced from five screens to three.
Why it works: Specific evidence shows Google the test was real and the app improved.
Invite exactly 12 testers.
Invite 25, expecting some to drop off, and monitor opt-ins daily.
Why it works: Falling below 12 can affect progress toward the 14 days.
Action plan
- Register companies as organization accounts
- Recruit at least 20 testers who match the audience
- Give testers specific tasks and a feedback form
- Ship fixes during the 14-day window
- Log metrics and changes for the application
- Prepare the public listing while you wait
Metrics to monitor
- Opted-in tester count by day
- Active testers using key features
- Feedback items and fixes shipped
- Crash-free users during testing
- Time from first upload to production access
Record the baseline, release date, audience, markets, and external changes before interpreting movement. Rankings and conversion are useful signals, but a decision is stronger when activation, retention, and business value confirm that the page attracted the right users.
Frequently asked questions
How many testers do I need for Google Play?
At least 12 testers opted in to a closed test for 14 continuous days, if you have a personal account created after November 13, 2023.
Does the closed testing requirement apply to organization accounts?
No. Organization accounts are exempt, although they still need to complete business verification.
What happens if a tester opts out during the 14 days?
Your count can drop below 12, which may affect progress. Recruiting more than the minimum protects you against drop-off.
Can I use paid tester services?
It is risky. Google asks how you recruited testers and how engaged they were, and testers who never use the app give you nothing useful to report.
Keep reading
More in Platform Guides
Browse all 9 Platform Guides guides
Work with ASOWin
Primary sources
Platform capabilities and limits can change. Verify current requirements in these official resources:
