How to get 12 Google Play testers for free
Updated
Finding twelve people is not the hard part. Keeping twelve people opted in for fourteen continuous days is. If one drops out on day nine and you are at eleven, you are not meeting the requirement until you are back at twelve.
So this list ranks the free methods by how well each one holds testers, not just how many it finds. Most developers end up combining two or three.
Before you ask anyone
Get these ready first, so every person you ask can join in under two minutes:
- A closed testing track with a published release. The opt-in link only works once the release is live. Setting that up is covered here.
- The opt-in link, not your Play Store link. Testers must open the opt-in link and accept, or they do not count.
- A way to add them. A Google Group lets people add themselves; an email list means you add each address by hand.
- A target of fifteen, not twelve. The extra three are your margin.
1. Your own test-for-test exchange partners
Holds testers: well, because both sides need the same thing.
In an exchange, another developer tests your app and you test theirs, both for the full fourteen days. It works because nobody is doing you a favour: if they leave your test, you can leave theirs. That shared stake is what keeps people opted in on day nine, when goodwill has run out.
The catch is the obligation. You are promising fourteen days of someone else's test, and your reputation depends on keeping it.
TestersWiz is a free exchange built around this. Each tester's opt-in is checked against the developer's own Play Console before they count, both sides are held to the full window, and there is no cap on how many testers you take. There is nothing to buy for testing.
2. People you already know
Holds testers: well for a few people, badly at twelve.
Friends, family and colleagues are the best testers you will ever have, but few people have twelve with Android phones who will keep an unfinished app for two weeks. Ask individually, not in a group chat. A personal message gets answered; a broadcast gets a thumbs-up and no opt-in.
A message that works:
Hi [name], I'm launching my first Android app and Google needs 12 people
to test it for 2 weeks before I can publish it. Could you help?
1. Open this link on your Android phone: [opt-in link]
2. Tap "Become a tester", then install the app from the Play Store page
3. Keep it installed for 2 weeks. Opening it now and then helps a lot
Any feedback, even "this screen confused me", is really useful. Thank you!
Then check your Play Console count rather than trusting "done!" replies. Here is how to verify each one.
3. Your own audience
Holds testers: very well, because they want the app.
If you have a waitlist, a newsletter, a social following or users of an earlier project, these are the people Google's help page has in mind when it suggests reaching "communities where potential users exist". They are real users, their feedback is useful, and they have a reason to stay.
Most first-time developers do not have this yet, which is why it is third.
4. Developer communities
Holds testers: unpredictably.
App-testing subreddits, Discord servers and developer forums have people who will help, and plenty of developers asking for exactly the same thing. Many communities limit these posts because of the volume, so read each one's rules before posting.
What works: offer to test in return, give the link and the three steps above, and follow up. What does not: a bare link and "need testers pls".
Testers from communities are strangers with no stake in your test, which is why this method drops people most often. Recruit more than you need.
What not to do
- Your own spare accounts or emulators. They do not make your testing real, and production review looks at whether it was. Why own accounts are a risk.
- Counting invitations. Invited is not opted in. Only opted-in testers count.
- Stopping at twelve. One uninstall and you are below the line.
- Removing testers after fourteen days. Keep everyone until Google grants production access; the review comes after the test.
Keeping them for fourteen days
- Check the count every two or three days, not only at the end. Play Console shows the current number, not a history.
- Replace drop-outs immediately. Every day you spend below twelve costs you, so add a replacement the same day. What to do when someone opts out.
- Ship an update in the middle. It gives testers something to look at, and a new build does not reset the clock.
- Ask for feedback once, specifically. "What confused you on the first screen?" gets answers. "Any feedback?" does not. You will need that feedback for the production access form.
If free methods are too slow for your deadline, paying for testers is a reasonable choice too. The trade-offs are in free vs paid app testers.