If you opened a personal Google Play developer account after 13 November 2023, you can't go straight to production. You have to run a closed test with at least 12 people for 14 days in a row, then ask Google for production access. Until then, the Production page in Play Console stays disabled.
Who it applies to
Google's requirement is written for personal accounts created after that date. Older personal accounts aren't covered by it.
Organization accounts are a different route: you need a D-U-N-S number to register, which is free from Dun & Bradstreet. Financial, health, VPN and government apps have to use one anyway.
What the rule asks for
- At least 12 testers opted in to your closed test when you apply
- Each of them opted in for the 14 days before you apply, without a break
- A tester who leaves early doesn't count, and someone who leaves and rejoins has to make it 14 days in a row
Production access isn't automatic
When the 14 days are up, you apply from the Play Console dashboard. Google asks about three things:
- Your test: how easy testers were to recruit, how engaged they were, and what feedback you got
- Your app: who it's for, why they'd want it, and how many installs you expect in the first year
- Your readiness: what you changed because of the test, and how you decided it was ready
Google says review usually takes seven days or less. If it thinks testers weren't engaged enough, it can ask you to keep testing.
How not to lose two weeks
- Recruit more than 12. We'd aim for 20, because one person dropping out at the wrong moment can cost you the window.
- Check the opted-in count in Play Console. Agreeing to help isn't the same as accepting the invite.
- Ask testers to really use it. Google asks about engagement, so a dozen people who installed it once is a weak answer.
- Keep notes on feedback as it comes in. You'll need them for the application.
- Ship at least one update based on that feedback. Then you have a true answer when Google asks what changed.
Do the paperwork first. Closed tracks need a Data safety form and a privacy policy; only apps on internal testing are exempt.
How long to plan for
Fourteen days of testing, up to a week or so for the application, then the production review itself. From your first upload, a month is a safe plan.
If you're launching on both stores, start the closed test early and let it run alongside your iOS submission. Otherwise your iPhone version can be live weeks before Android. If that iPhone version is a wrapped web app, read guideline 4.2 first.
Sources
We check these before publishing. If something here has gone stale, tell us.
