How I cleared Google Play's 12 testers / 14 days requirement

The first time I opened Play Console with a finished app, I thought the hard part was over. The code worked, the screenshots were done, the store listing was written. Then I hit the closed testing requirement, and "publish" turned into a two-week project of its own.

I've now been through it twice. My first two apps, Jaap108: Mala Counter - Mantra and PanchVeda (Panchang, Kundli & Matchmaking), both cleared the 14-day closed test and are live in production on Google Play. This post is what I learned along the way, and why I ended up building a small tool to make it less painful for the next person.

The rule, in plain terms

If you have a personal Google Play developer account created after 13 November 2023, you can't apply for production access straight away. First you have to run a closed test with at least 12 testers who stay opted in continuously for 14 days.

A few details that tripped me up:

• It used to be 20 testers. Google lowered it to 12 in December 2024, so a lot of older guides and Reddit threads still say 20.
• "Continuously" matters. If testers opt out partway, the clock doesn't care that you once had 12. You need 12 opted in across the whole 14 days.
• Organization accounts aren't covered by this rule. It's aimed at personal accounts.
• After the 14 days you still have to apply for production access and answer questions about your testing. Meeting the numbers doesn't mean automatic approval.

For the full, up-to-date breakdown, I keep a guide here: Google Play 12 testers / 14 days explained.

Why it's harder than it sounds

Twelve people sounds easy until you try to find them.

Friends and family mostly don't have Android, or don't want to install a random APK-looking thing. The ones who do often install it once and forget. Some uninstall it to free up space a week later, which can break your streak.

Joining is fiddly. Testers need to be added to your list (or a Google Group), open the opt-in link, accept, then install from the Play Store. Every step loses someone. Explaining "no, click the other link" over WhatsApp gets old fast.

Two weeks is a long time to keep people engaged. Google also wants to see that testers actually used the app, not just that they were on a list. So you need people who'll open it more than once.

The paid shortcuts felt wrong to me. There are services that sell you a batch of testers. I didn't want to pay strangers to tap through my app, and I wasn't sure how that would look when I applied for production and had to describe my testing.

What actually worked

Nothing clever. Mostly persistence and a bit of structure. This is roughly the playbook that got Jaap108 and PanchVeda through.

1. I used a Google Group for the tester list. Instead of adding emails one by one, I added a Google Group as the tester list. Anyone who joined the group got access. It made onboarding a single link and removed a lot of back-and-forth.
2. I wrote a 3-step "how to join" message. Join the group, open the opt-in link, install from Play. Screenshots for each. I sent the same message every time instead of improvising.
3. I recruited a few more than 12. A buffer covers the people who drop off. Being exactly at 12 means one uninstall resets your nerves, if not your clock.
4. I asked other Android devs. This was the turning point. Other indie devs understood the problem immediately, because they had the same one. They installed properly, stayed opted in, and actually opened the app. In return, I tested theirs.
5. I kept a simple log. Who joined, when, whether they were still opted in. When I applied for production access, I could describe what testing happened and what I changed because of it.

That fourth point is the one I want to dwell on. Devs testing each other's apps is fair. Nobody's paying anybody. Everyone's in the same queue, everyone needs 12 people, and everyone can be one of someone else's 12.

So I built LaunchReady

The swap worked, but organising it by hand was messy: spreadsheets, DMs, chasing people who forgot. So I built LaunchReady (listed on Google Play as 12 Testers: Closed Test Buddy).

The idea is simple: it's a tester swap. You list your closed test, you test other developers' apps, and they test yours. No buying testers, no anonymous click farms. Just Android devs helping each other get through the same gate.

A few honest notes, because I'd want to know these as a user:

• The app contains ads. There's a Pro upgrade that removes them. That's how I'm trying to keep it running.
• Play Store reviews are never rewarded. LaunchReady doesn't trade reviews or ratings, and you shouldn't ask testers for them. Swapping testing is one thing. Swapping reviews breaks Google's policies and isn't something I want any part of.
• It can't guarantee production approval. Nothing can. Google decides that. What a swap can do is help you get real testers who stay opted in and actually use your app, which is the part you control.

If you're stuck at the start of your 14 days, the guide I linked above covers the rule in more detail, including the Google Group setup and what to expect when you apply for production: launchready.hummout.com/google-play-12-testers-14-days.

If you're about to start your closed test

My short list, whether or not you use my app:

• Recruit 15 or so, not 12.
• Use a Google Group so joining is one link.
• Send one clear, screenshot-backed join message.
• Ask testers to keep the app installed for the full two weeks and open it a few times.
• Actually fix things testers report, and note what you changed. You'll want that when you apply.
• Look for other devs in the same position. Testing each other's apps is the most reliable way I found.

The requirement is annoying, but it's survivable. And if you're in the middle of it right now: good luck, and feel free to say hi in the comments. Happy to test your app too.