The Rule
Newly created personal developer accounts must first run a closed test before they can apply for production access. As of the latest rule I know of, that means at least 12 testers opted in and a test that runs for 14 days continuously. Organisation accounts follow a different path. The idea is to keep low-quality and abandoned apps out of production, and that is a fair goal.
Why It Bites Indies
- You need people: a solo developer has to find a dozen real people with Android phones who will opt in and stay in.
- You lose two weeks: the clock is fixed, so a launch plan has a built-in delay before the first public user.
- It rewards having a network: developers with a community clear it easily; a developer with no audience yet has a chicken-and-egg problem.
How To Handle It Well
Treat the closed test as a real beta rather than a hoop. Ask friends, colleagues and early users who would honestly use the app, give them a way to send feedback, and fix what they report. Real testers find real bugs, and you will go into production with a build that has been used by people who are not you. I have published several apps to Google Play, including AI Exodus and SUTOK (see the SUTOK page), and the habit that pays off most is the one that sounds boring: keep a web version live so there is always a working product, whatever the store timeline does.
Compare it with the alternative in my App Store opinion piece: a gate you can pass by being organised is easier to live with than a judgement you cannot appeal. Planning a first release? Ask me for a launch checklist.