Where to find 12 testers for Google Play

What a tester actually has to do

Google does not count email addresses: it counts people who joined your track and stayed on it. You need 12 opted in continuously for 14 days before you can apply for production access — it was 20 testers until June 2025, the threshold is 12 now.

To count, a person has to:

• have a Google account, the one they actually use on the Play Store on their phone;
• open your opt-in link and agree to join the track;
• install the app from the Play Store, on that phone;
• keep it installed for fourteen days;
• and open it now and then, otherwise you finish the fourteen days with nothing to fix.

The rule itself, and what sends the count back to zero, is in the closed-testing guide.

Five places to look

• The people around you: family, friends, former colleagues. They are not the most objective, but they are the only ones who will still answer you on day 9.
• Your local community: developer groups, your school, your coworking space. Twelve people in the same room beat a hundred addresses in a spreadsheet.
• Your current customers and users: if they are waiting for your update, they have a reason to keep the app installed to the end.
• Developer exchange groups: they work as long as you hold up your end, which means actually testing other people’s apps for fourteen days.
• A pool of registered testers, such as ekko’s: people who signed up to test, filtered by platform, device, city and language.

What fails

• Buying installs. It is against Play Store policy, and bought accounts disappear after a few days: you are back on day 1, having paid for it.
• “I test yours if you test mine” with no follow-up. Everybody installs on day one, everybody uninstalls on day 3, and nobody says so.
• A list of addresses that are not the phones’ Google accounts. Someone whose phone is signed in to another address will never see your app.
• Recruiting exactly twelve people. One drop-out is enough to fall back under the threshold, and the days already spent are not kept.

Keeping them for fourteen days

• Say it up front: two weeks, the app stays installed, and it takes five minutes a week.
• Give one short, concrete instruction: what to try, in what order, and what you want to know.
• Remind them on day 3 and day 7. That is where people drop off, not on day 13.
• Say thank you, and say what you fixed thanks to them. Someone who sees their feedback handled stays to the end.

What ekko changes

ekko gives you the pool: you describe your app, the platform and the devices you want, and registered testers join your campaign. The SDK in your app follows the first time each tester opens your app, then every session after that, and reminds anyone who has not opened it in seven days, on its own.

Meanwhile, every “it doesn’t work” arrives complete: the annotated screen capture, the console, the network requests and the device. Read the seven mistakes that restart your 14 days too, then open a campaign: the first one is free.

ekko cannot see the Play Console: it counts what it sees from your app. Google counts from the Play Console: check your track’s dashboard before requesting production access.

Questions and answers