A step-by-step look at the closed test that new personal developer accounts must run before publishing an app.
When you upload your first app with a personal developer account, the “Publish to production” button is locked. Google Play asks personal accounts created after 13 November 2023 to run a closed test before making an app public. Organisation (company) accounts are exempt.
Falla AI is at exactly this stage right now. Here is the process as I experience it with my own apps.
What exactly is required?
- The app must be live on a closed testing track.
- At least 12 testers must have joined the test.
- Those testers must have stayed in the test continuously for the last 14 days.
Once that’s met, a production access application opens on the Play Console home page. When it is approved, you can publish the app publicly.
The rules change from time to time. When the requirement first appeared the number was 20; it later dropped to 12. Check the current wording in Play Console before you start.
1. Set up the closed testing track
In Play Console, create a track under Test and release → Closed testing and upload your first build. There are two ways to add testers:
- Email list: you enter each tester’s Google account address one by one.
- Google Group: you create a group and add its address. Anyone who wants to join simply becomes a member, so you never have to update the list by hand. I find this more practical.
When the build passes review, Play gives you an opt-in link.
2. Get the testers actually into the test
This is where most people get stuck. Adding people to the list is not enough; every tester has to:
- Open the opt-in link and tap “Become a tester”,
- Install the app from Google Play.
Sending an APK file doesn’t count. You can track how many people have joined on the closed testing page in Play Console.
3. Secure your 14 days
Because the requirement is “continuously for the last 14 days”, if someone leaves the test and the number drops below 12, the time you’ve waited can be wasted. So:
- Start with 15-20 people, not 12.
- Ask testers clearly not to uninstall the app for 14 days.
- Friends and family help, but try to find a few people who will really use your app. Their feedback is what will actually help you in the application.
4. Don’t waste the test period
The application form asks: how you found your testers, what feedback you received, what you changed based on it, and how you know the app is ready for production. So during the 14 days:
- Write down the feedback you receive.
- Publish at least one or two updates and note what you fixed.
- Keep an eye on crashes in Play Console’s Android vitals screen.
5. Apply for production access
When the 14 days are up, the application section on the home page opens. Answer the questions briefly but concretely: a sentence like “Testers reported a bug on the sign-in screen, which I fixed in version 1.0.3” is far more convincing than “the test went fine”.
Reviewing the application usually takes a few days. If it’s rejected, read the reason, extend the test a little and apply again.
In short
The closed testing requirement looks like an obstacle at first, but it’s a good chance to try your app with real users. Start early, keep the tester count generous and use those two weeks to genuinely improve the app.
If you need help getting your app onto Google Play, get in touch.