How to Pass Closed Testing on Google Play

I'm building a pet project — a time tracking app called Timetracker. I built the web version a while ago, and now it was finally time for the Android app. I put it together fairly quickly using a hybrid approach with Capacitor. Built it, tested it, and decided to upload it to Google Play Console to make it publicly available. Turns out, under the new rules (new since the last time I tried to publish anything there), you can't just publish an app. You need to pass closed testing first.

What Google Requires

Google Play introduced these rules for personal developer accounts to reduce the number of junk apps in the store. The gist: before you can apply for production access, you need to run a closed test — at least 12 testers must install your app and stay in the testing program for 14 consecutive days. It used to be 20, but they lowered it to 12 at the end of 2024.

Key details:

• Testers must use real Android devices — emulators don't count
• This only applies to personal accounts (organization accounts skip this requirement)
• If testers drop out and you fall below 12, the 14-day clock may reset
• After testing, the review officially takes up to 7 days, but in practice it's 1–2 days

Where to Find 12 People

This is where it gets interesting. 12 people doesn't sound like much. But in practice, finding even that many turned out to be surprisingly difficult.

First, I asked friends and family. Messaged those I could, explained the situation: "Just install the app and don't delete it for two weeks, nothing else needed." I got 5 volunteers. Five is good, but I needed at least 12.

You could search for testers on forums, topic-specific chats, Reddit. But that's slow, unreliable, and people often forget to install or delete the app after a couple of days.

Testers Community

After some searching, I found Testers Community. It's a platform that helps developers meet Google Play's closed testing requirements. There are two options:

Paid (€14 per app): you get 25 testers, they start installing within 6 hours, and there's a guarantee — if Google rejects your app, you get a refund. Plus some kind of UX report.

Free: through the Testers Community mobile app. It works on a mutual help basis — first you test other people's apps, then you can add your own. You need to earn 60 credits, which means testing 3 other apps.

I went with the free option. Signed up, downloaded the app, tested three other apps (just installed them and poked around a bit). After that, I could add my own.

The Result

People started installing my app pretty quickly. In less than 24 hours, I had enough testers — even more than 12.

I watched the stats: none of the people who installed via Testers Community ever launched the app again. Some uninstalled it after a day or two. But it didn't matter — Google Play only cares about participation in the testing program, not active usage. The tester count still held.

After that, I just had to wait two weeks. Once the 14 days were up, the option to apply for production access appeared in Google Play Console. I applied — and got approved.

Summary

If you're an indie developer who needs to pass Google Play's closed testing — here's what I recommend:

1. Ask friends and family — however many you can get
2. Fill the rest through Testers Community (free)
3. Wait 14 days
4. Apply for production access

The whole process took me about three weeks from uploading the first build to the app appearing on Google Play. Two of those weeks were just waiting. Testers Community saved me a ton of time searching for testers — highly recommend it.