Why did Google Play ask me for 12 testers before I could publish my app?

I finished my first Android app, uploaded it to Play Console, and instead of a publish button I got a screen I hadn't expected. Before going to production I had to run a closed test: at least 12 testers, for 14 uninterrupted days.

To be honest, the questions in my head that night were different ones. Would the app actually install? Would it open? Would the first screen throw an error? That's what I was thinking about while uploading; recruiting testers never crossed my mind.

What the requirement is

Google introduced a rule for personal developer accounts created after November 13, 2023: before an app can go to production, it has to be tested in the closed testing track with at least 12 testers for 14 consecutive days. When the period ends, you apply for production access in the Console and Google reviews the application. What matters is not the age of your Google account but the date you registered as a developer on Play Console.

The Console shows it as a checklist: the first two items took two days, the third one is tied to the calendar.

Where what I read differed from what I lived

I had read what people wrote about this online, and honestly, the process matched the descriptions fairly closely. The difference wasn't in the information; it was in the feeling. No article tells you how tight the window is for you specifically. In my case there was a warning that the account would be closed for inactivity, and the schedule was already tight. Instead of waiting for the 14-day clock to start, I had to start collecting testers the same day.

The first build also failed. The app installed on the phone but closed before the first screen was drawn. The cause wasn't Play; it was my own build configuration. A build that ran fine in the emulator couldn't find some environment variables when built in the cloud. The second upload fixed it. I mention this for one reason: if your first upload doesn't work, don't panic; the problem is most likely not on Google's side.

How I found 12 people

I asked colleagues at work and relatives in the family group chat. Twelve people were in within about two days, faster than I expected. I told everyone the same thing: you'll tap a link and install the app, it stays on your phone for two weeks without being uninstalled, and you don't have to use it.

Whether I can ask the same people again for the next app, I'm not sure. Asking for a favor once is easy; repeating it for every app starts to wear people out.

What this does to an independent developer

Google's reasoning is understandable. The help page frames the requirement around testing the app with real users and collecting feedback before launch. My reading is that it aims less at punishing developers and more at setting a testing threshold for what enters the store: an app that has run on real devices for 14 days is a better starting point than one that has never been tested at all.

But the cost isn't evenly distributed. For someone with 12 Android users around them who can be asked for two weeks, this is a two-day task. For someone without that circle, trying to build something alone, it's a barrier that requires paying for testers. I think there should be some relief here, say a smaller tester count, or a testing pool provided by Google itself. Not everyone has 12 people to call.

Where I am now

The closed test started today; this is day one. The app is ParetoRidge, it's on 12 phones, and the clock is running. In 14 days I'll apply for production and wait, curiously, for what Google says. I'll write the result here.