You are not unusual. Most solo developers do not know 12 people with Android phones, and the ones who do usually find that half of them are on iPhone.
This is the real blocker in Google’s testing requirement. Not the 14 days, not the paperwork. Twelve human beings who will install your app and keep opening it for a fortnight.
There are three honest ways across, and one category of shortcut that will cost you your account.
Why does Google assume I have 12 friends?
Because its own guidance does. Google suggests recruiting testers from your friends, family, colleagues or classmates, and from communities where your users are likely to be [1].
That advice works if you already have an audience or a team. It does not work if you built something alone at night and have never shipped before, which describes most people hitting this requirement for the first time.
Worth saying plainly: the requirement is not a judgement on your app. It applies to every new personal developer account regardless of quality, and it exists because Google is filtering an enormous volume of low-effort submissions. In 2025 it blocked over 1.75 million policy-violating apps and banned more than 80,000 developer accounts [2]. You are being asked to prove your app is real. That is all.
Route 1: developer communities
Free, and the slowest of the three.
Places people genuinely find testers: r/AndroidClosedTesting and similar subreddits, Discord servers for indie developers, the Google Play Developer Community, itch.io devlogs, and local developer meetups.
What it actually feels like: you post asking for testers, a handful of people respond, some install and vanish. Developers commonly report needing several rounds of this, and it is normal to burn a week before the 14 days even start.
Make it work harder:
- Post what your app does, not just that you need testers. People install things that sound interesting.
- Offer to test theirs in return, explicitly, in the first message.
- Ask for 16 people, not 12, because a third will go quiet.
- Send the opt-in link and the account rule in the same message, or half of them will never complete opt-in.
Route 2: a reciprocal pack
Free, and it costs you time rather than money.
The idea is straightforward: a group of developers all test each other’s apps for the same period. Everyone in the group needs production access for their own app, so unlike a one-off swap the incentive lasts the whole run rather than ending the moment both sides have installed.
Our free Testers Community app works this way. You join a Pack of 16 developers who test each other’s apps for 16 days, opening every app daily and leaving real feedback. Members who stop testing are replaced, so the group does not quietly decay.
The honest cost: you are testing fifteen other apps every day while yours is being tested. If your evenings are already the only time you have to build, this is a real trade.
Route 3: a testing service
Paid, and the fastest.
You submit your app, verified testers are assigned to it, and they run the full period. No recruiting, no chasing, no wondering whether someone opted in.
Ours starts at ₹999 for 15 testers across the full 14 days, with testers assigned within 6 hours and anyone who goes inactive replaced. There is more detail at the end of this post.
The honest cost: it is money, and it is money spent before you know whether the app will earn anything. That is a genuine decision, not an obvious one.
Which route should I pick?
| If this is you | Route |
|---|---|
| Plenty of time, no budget, first app | Communities or a pack |
| You will publish several apps | Build a reusable list through communities |
| A deadline, a launch date, or a client | A service |
| Already rejected once and starting again | A service, because a second failure costs weeks |
| You enjoy testing other people’s apps | A pack |
What about just making 12 accounts myself?
Do not. This is the shortcut everyone thinks of and it is the one that ends accounts.
- Fake Google accounts. Creating accounts to test your own app is exactly the pattern Google’s enforcement systems look for, and it puts your developer account at risk.
- Emulators. They do not produce the engagement signals a real device does, and a test made entirely of them looks artificial.
- Buying installs. Purchased engagement is detectable and against policy.
- Your own second phone. One extra device is not going to bridge a gap of twelve.
Google banned more than 80,000 developer accounts in 2025 [2]. Losing a $25 account is annoying. Losing the app you spent six months building is not.
How do I actually ask people?
If you are going the free route, the ask matters more than the list. What works:
- Lead with the app. One sentence on what it does and who it is for.
- Be specific about the commitment. “Install it and open it a few times a week for two weeks” is honest and gets fewer flakes than “just install this”.
- Send the opt-in link plus the account rule in the same message. They must be signed into the exact Google account you added.
- Follow up on day 3 and day 8. Not to nag, but because people forget, and a reminder is usually enough.
- Say thank you properly. Credit them in the app, give them the paid version, or test their app back.
Frequently asked questions
Can my iPhone-owning friends help?
No. Testers need an Android device and a Google account, because they install through the Play Store.
Do the 12 testers have to be people I know?
No. Google places no requirement on who they are, only that they genuinely use the app. Strangers from a community count exactly the same as friends.
Can one person use two accounts to count twice?
No, and attempting it is the kind of pattern that gets accounts banned.
How long does the free route usually take?
Plan for a week of recruiting before your 14 days start, and expect to lose a few people along the way. Developers frequently report needing more than one attempt.
Is it worth paying when I have not launched yet?
It depends entirely on whether your time or your money is scarcer. If you have already been rejected once, the calculation usually changes, because another failed cycle costs weeks.
Can I mix routes?
Yes, and many people do. Recruit whoever you can from communities, then top up. Nothing stops you combining sources.
If you would rather not do the recruiting
Option 1: have the testers assigned to you
- Starter, ₹999 gives you 15 verified Android testers for the full 14 days.
- Pro, ₹1,699 gives you 25 testers, plus a detailed ASO report and priority support.
- Testers assigned within 6 hours, so your 14 days start today rather than after a week of asking.
- They stay active for the full period.
- Anyone who goes inactive is replaced.
- A feedback report at the end, plus pre-filled answers for the 10 production access questions.
- 100% production access or your money back.
More than 10,000 apps have reached production this way. Submit your app to start.
Option 2: join a free Pack of 16
If time is the thing you have more of, the Testers Community app pairs you into a pack of 16 developers testing each other’s apps for 16 days, with inactive members replaced.
Either way, read the full requirements before you begin, and our guide to inviting testers properly so nobody falls at the opt-in step.
