If your personal developer account was created after November 13, 2023, Google Play will not let your app go to production until it has passed a closed test with at least 12 testers opted in for 14 days in a row. The rule is free to meet in theory: nothing stops you from recruiting twelve volunteers yourself. In practice, free testers are paid for with your time, your favors and your patience.
This guide covers every free way to get 12 testers, the real cost of each, and the habits that keep a free group above 12 for two full weeks. If you are not yet sure what the rule requires, start with the 12 testers, 14 days requirement explained.
What a free tester has to do for you
Whoever your testers are, the requirement asks the same of each of them. Make sure people know this before they agree, because a tester who drops out on day 9 is worse than no tester at all:
- Use an Android phone whose Play Store is signed in with the Google account you add to your tester list.
- Open your opt-in link, accept the invitation and install the app from Google Play.
- Stay opted in for 14 days without leaving the program or deleting that Google account.
- Open the app regularly and ideally send a line or two of feedback. Google asks about engagement when you apply for production access.
That is a small ask for one day and a big ask for fourteen. The routes below differ mainly in how likely people are to keep their promise.
Route 1: People you already know
Friends, family, classmates and colleagues are the most reliable free testers because they want you to succeed. Their weak spots are practical: many own iPhones, some will be confused by the opt-in step, and most will forget about an app they do not need after a few days.
- Count Android users first. If you know fewer than 15 people with Android phones, you will need a second route anyway.
- Ask in person or by direct message, not in a group chat where everyone assumes someone else will do it.
- Send exact instructions. Our ready-made instructions for testers can be copied into a message as they are.
- Give them something to try. Two or three specific tasks produce better feedback than 'have a look'.
Route 2: Your own audience and early users
If you already have followers, a mailing list, a website with visitors or users of an earlier app, invite them into the closed test as an early-access beta. These are the testers Google most wants to see: people who chose your app because they are interested in what it does.
Use a Google Group as your tester list so anyone can join without you editing the list in Play Console, and put the group link and the opt-in link on one simple page. Be clear that it is an early version, that it is Android only, and that staying in for two weeks helps you launch.
Route 3: Tester exchanges and developer communities
Because every new personal account hits the same rule, developers have built a whole culture of test-for-test swaps: subreddits, Discord and Telegram groups, forum threads and dedicated exchange apps. You join other people's closed tests, they join yours.
This is the route most solo developers try first, and its cost is mostly hidden:
| What it costs you | Typical reality |
|---|---|
| Testing in return | You usually join as many tests as the number of testers you want, often 15 to 20 apps |
| Daily effort | Opening each of those apps regularly for 14 days, plus your own app's work |
| Device storage | Fifteen or more extra apps installed on your phone for two weeks |
| Drop-outs | People uninstall once their own test passes, sometimes before yours does |
| Feedback quality | Often generic, because everyone is testing many apps at once |
Exchanges work best when you treat them as a contract. Join tests from people who have just started, so your two weeks overlap. Keep a spreadsheet of who joined your test and whose tests you joined, and follow up politely with anyone whose opt-in you cannot see. Never rely on an exchange for exactly 12 testers.
The real cost of free testers
Add it up honestly before you commit. Recruiting and reminding testers, plus testing other developers' apps in an exchange, can easily take half an hour to an hour a day for two weeks or more. If the count drops below 12 near the end, the continuous period breaks and you may need another 14 days. A failed production access application can add another round on top.
How to keep free testers opted in for 14 days
Most free tests fail in the second week, not the first. These habits keep the count above 12:
- Recruit at least 15 to 20 people. The buffer absorbs the ones who drift away.
- Confirm every opt-in. Check the tester count in Play Console after the first two days and ask anyone missing whether they used the right Google account.
- Send short reminders on about day 3, day 7 and day 11, with one new thing to try each time.
- Ship an update during the test. A new version gives testers a reason to open the app again and shows Google you acted on feedback.
- Thank people publicly when the test ends, so they say yes next time.
If the count drops or never seems to reach 12 even though people say they joined, work through why Play Console is not counting your testers before the clock suffers. And follow a day-by-day plan for the 14-day closed test so the production access application is ready when the two weeks end.
When paying for testers makes more sense
If you weigh the hours above against a one-time fee, a testing service is often cheaper. Before choosing one, read our checklist for buying 12 testers, because the quality of these services varies a lot.
TesterBie is one such service for 12 testers for Google Play. Real Android phones in a device lab, each with its own Google account, join your closed test through our Google Group, install your app from Google Play and use it every day for 14 days, with spare phones on standby so the count stays above 12. You follow everything on a dashboard and get bug reports with screenshots by email. Plans are 13 testers for $14.99, 15 testers for $19.99 or 20 testers for $29.99 per app, paid once. Compare plans if your time is worth more than the swap.
Frequently asked questions
Can I really get 12 testers for free?
Yes. Friends and family with Android phones, your own audience and tester exchange communities can all provide testers at no cost. The cost is time: recruiting, reminding and, in exchanges, testing other developers' apps for two weeks.
Do tester exchange apps and groups break Google's rules?
Google does not publish rules on where testers come from. What matters is that testers really opt in, install and use the app, and that you describe your test truthfully when you apply for production access.
How many free testers should I recruit?
Recruit at least 15, and closer to 20 if most of them come from an exchange. Free testers drop out more often, and falling below 12 breaks the continuous 14-day period.
Can I use my own other Google accounts as testers?
Opting in with several accounts you control fills the counter but produces no real engagement or feedback, which is what Google reviews when you apply. It is a weak basis for a production access application.