Google Play's 12-tester rule: how to get production access

Personal developer accounts created after November 13, 2023. Google's help article on the requirement is written for personal accounts; if you publish as an organization, go by what your own Play Console asks for. Apps on older accounts are not affected.

• It has to be a closed test. Internal testing is a different track and does not count.
• At least 12 testers opted in to that closed test.
• Each opted in continuously for at least 14 days. A tester who opts out before 14 days does not count, and one who opts out and back in needs 14 consecutive days again.

1. Create the app in the Play Console and fill in the basics of the store listing.
2. Build a signed .aab; Corenna's Android build produces one. Google requires a brand-new app's first release to be created by hand, so upload this one to a closed testing track in the Play Console yourself.
3. Add testers as an email list or a Google Group, then share the opt-in link. Each tester opens it with the Google account on their phone, accepts, and installs the app from the Play Store.
4. Keep at least 12 opted in for 14 days in a row. Invite a few more than 12, so one person dropping out does not take you below the line.
5. Ship updates during the test. With Google Play connected in Corenna, each update goes straight to the closed track with release notes, and the build number goes up by itself.
6. When you qualify, open the Play Console Dashboard and choose Apply for production.

The application has three parts:

• Your closed test: how easy testers were to recruit, how they engaged (did they use all the features, the way real users would?), and a summary of their feedback.
• Your app: who it is for, what it offers them, and how many installs you expect in the first year.
• Production readiness: what you changed because of the test, and how you decided the app was ready.

Google says review usually takes seven days or less. It can ask for more testing if fewer than 12 testers are opted in or engagement was too thin, so testers who actually use the app, and updates that respond to them, are what get you through.

Friends and family with Android phones, your waitlist, a community you are part of, or other developers going through the same rule. Because Google asks how testers engaged, a list of people who install the app and never open it is a weak basis for an application.

Production releases work like the test: build a new .aab and send it to the production track, or to internal or closed testing first. Every update must use the same signing key and a higher version code, which Corenna handles; see shipping an update to a live app.