Google Play asks developers with newer personal accounts to prove their app works before it reaches the public. If you are launching your store's app from a personal Play Console account, this rule decides your launch date, so it is worth planning for on day one.
What the rule says
Personal developer accounts created after 13 November 2023 must run a closed test before they can apply for production access. Google's requirement:
- at least 12 testers opted in to the closed test
- opted in continuously for 14 days or more
- testers who leave before 14 days don't count
When you meet it, you apply for production access from the Play Console dashboard. Organisation accounts are not covered by this rule.
How to plan your launch around it
- Start the closed test early. Upload your first build to a closed testing track as soon as the app works, even before the design is final.
- Recruit more than 12 testers. Aim for 15 to 20 so a few drop-outs don't reset you. Friends, family and staff all count.
- Make sure each tester opts in. Sharing the link isn't enough: every tester must open the opt-in link with their Google account and install the app from Play.
- Use the 14 days well. Ask testers to actually shop in the app and send feedback. The feedback helps you fix problems before your public launch.
Tip: with AppFromShop, design changes reach installed test apps instantly, so you can keep improving the app during the 14 days without uploading new builds.
Personal or organisation account?
| Personal | Organisation | |
|---|---|---|
| Closed test before production | Required (12 testers, 14 days) | Not required by this rule |
| What you need | Your own identity | A registered business and a D-U-N-S number |
| Name on the store | Yours | Your company's |
If you already run a registered business, an organisation account avoids the closed-test wait, but getting a D-U-N-S number can itself take weeks.
Next steps
Read our guide to publishing to Google Play, or start a free trial and have your app on your own phone today.
