You can get the testers Google Play requires for free, and the number is now twelve, not twenty. The three reliable free methods are your own personal network, where friends, family, and colleagues all count as long as they use real Google accounts and engage, reciprocal tester-exchange communities where developers test each other's apps, and a Google Group to manage opt-ins. Whatever the source, testers must opt in for fourteen continuous days and genuinely use the app. Avoid paid or fake testers, which risk your account.
Short answer
It is twelve testers now, and you can find them for free. Google's testing requirement for new personal accounts is at least twelve testers, opted in for fourteen continuous days, before you can apply for production; it was twenty until December 2024. Free sources are your personal network (family and friends count, with real Google accounts), reciprocal tester-exchange communities on Reddit, Discord, and dedicated groups, and a Google Group to send opt-ins. Testers must actually use the app across the fourteen days. Do not buy or fake testers, which is fake engagement that violates Google's policies and risks termination.
First, it is 12 testers now, not 20
Before you start recruiting, know the real number: Google reduced the requirement from twenty testers to at least twelve in December 2024, after individual developers found twenty too hard to reach. The fourteen-day continuous window stayed the same. So if a guide or search still says twenty, it is out of date, and you need fewer people than you feared.
This matters for your plan, because twelve is a genuinely reachable number through free channels. Twelve real people, opted in and engaged for two weeks, is achievable from your own network plus a reciprocal community, without paying anyone. Start from the current number so you do not over-recruit or panic.
What each tester needs to do
A tester is a real person with a Google account who opts in to your closed test and uses the app. Specifically, they need to join through your opt-in link or a Google Group, stay opted in for the full fourteen continuous days, and actually open and use the app during that window, because Google checks for genuine engagement, not just installs. If testers drift away or never open the app, you may fall short even with twelve names.
This definition is what makes free recruiting work and fake recruiting fail. Any real person you know or meet can be a valid tester, which is why your network and reciprocal groups are enough. What does not work is fake or bot accounts, because they cannot provide the genuine engagement the requirement is checking for.
Free method 1: your personal network (yes, family counts)
Your own network is the first and easiest source, and yes, family counts. Friends, family members, and colleagues are all valid testers as long as each uses their own real Google account, opts in, and engages with the app. There is nothing wrong with asking the people you know; the requirement is about real testing, not strangers specifically.
Be practical about it. Send each person the opt-in link, explain they need to install the app and open it a few times over two weeks, and confirm they actually joined, since an opt-in that never happens does not count. A dozen people from your combined personal and work circles is often enough on its own, before you even reach outside groups.
Free method 2: reciprocal tester-exchange groups
When your own network is not enough, reciprocal communities fill the gap, and they are free because they run on mutual help. These are groups of developers in the same situation who test each other's apps: you join others' closed tests, and they join yours. Because everyone needs the same thing, participation is high and it costs nothing but your time testing back.
The table below lists common places to find them.
| Source | What it is | Notes |
|---|---|---|
| Friends and family | People you know with Google accounts | Real accounts, and they must engage |
| r/androiddev and similar | Android developer subreddits | Often reciprocal |
| Discord and Telegram groups | Developer and testing communities | Test others' apps in return |
| Tester-exchange communities | Groups built around the 12-tester rule | Genuine, reciprocal testing |
| Indie and maker communities | Indie Hackers, forums, your following | Ask your existing audience |
When you use these groups, be a good participant: genuinely test the apps you sign up for, not just your own, because the communities work on reciprocity and reward people who contribute. Treating it as a real exchange gets you engaged testers rather than a list of names that will not last fourteen days.
Free method 3: set up a Google Group
A Google Group makes managing testers easier and is itself free. In Play Console, you can add testers by a Google Group email address instead of listing individual emails, so anyone who joins the group is automatically a tester. This is handy when you are recruiting from a community, because people can join the group themselves.
It also simplifies the opt-in. You share one link, testers join the group, and they receive the opt-in for your closed test. For a reciprocal community especially, a Google Group turns recruiting into a single shareable link rather than collecting addresses one by one, which lowers the effort for both you and your testers.
A recruiting checklist
Putting it together, the process is short if you do it in order. The checklist below covers it from setup to applying for production.
| Step | Action | Why |
|---|---|---|
| 1 | Create a closed testing track | It is where the test runs |
| 2 | Add testers by email or a Google Group | Sends them the opt-in |
| 3 | Share the opt-in link and ask them to join | Starts the 14-day clock |
| 4 | Confirm 12 or more opted in early | The window is continuous |
| 5 | Ask testers to open the app during the 14 days | Engagement is required |
| 6 | Apply for production after the window | The goal of the test |
The one thing that trips people up is timing: because the fourteen days are continuous and counted from when testers are opted in, get your twelve in early rather than adding them one at a time, which keeps pushing back the date you can apply.
Keeping testers engaged for 14 days
Recruiting is only half the job; the testers have to stay engaged. Google can require more testing if engagement is low, so a dozen people who install and vanish may not satisfy the requirement. Ask your testers to open the app and try its main features a few times across the two weeks, and give them a reason to, such as genuinely wanting their feedback.
A little communication keeps them in. A short message at the start explaining what you need, and a reminder partway through, goes a long way, especially with reciprocal testers who are juggling several apps. Treating testers as real testers, and using what they report, is both what the requirement wants and what makes your first release better.
What not to do
Skip the shortcuts that look free but cost you the account. Buying testers, using bots or fake accounts, or paying for installs is fake engagement, which Google's policies prohibit and its enforcement can act on by terminating accounts. It also tends not to work, because fake testers do not provide the sustained engagement Google checks for.
The honest path is genuinely cheaper. Real testers from your network and reciprocal groups cost only time, while a faked test risks the developer account you are trying to launch on. When a method promises to meet the requirement instantly with accounts you do not know, treat that as the warning sign it is.
Test for real: also scan your build
The requirement exists to get real testing before launch, and your testers will surface crashes and confusing flows, but they will not see the security problems underneath: an embedded API key, cleartext traffic, or a debuggable build. Clearing the tester gate does not mean the app is safe to ship.
A scanner like PTKD.com analyzes your .apk and returns findings ordered by severity and mapped to OWASP MASVS, so the testing period is also when you catch security issues before real users are exposed. To be clear about the boundary: PTKD does not provide testers or affect the requirement, and it cannot shorten the fourteen days. It covers the part of readiness that a tester count never measures.
What to take away
- The requirement is twelve testers now, not twenty, and you can get them for free.
- Your personal network counts, including family, as long as each uses a real Google account and engages.
- Reciprocal tester-exchange groups on Reddit, Discord, and dedicated communities fill any gap, for the cost of testing back.
- A Google Group turns recruiting into a single shareable opt-in link.
- Keep testers engaged for the full fourteen days, avoid fake testers, and scan your build with PTKD.com before launch.
