Choosing a Service
Real testers vs install farms
Search for closed testing help and you'll find offers from about $30 alongside offers at several hundred. They are not the same product, and the difference is not service quality — it's whether the thing being sold is compatible with staying on Google Play. Here is how to tell them apart before you hand over an opt-in link.
What is and isn't in bounds
| In bounds | Out of bounds |
|---|---|
| Recruiting real people to opt in and test | Bots, emulator farms, automated installs |
| Paying a provider to organise and manage testers | Buying install counts to move rankings |
| Giving testers tasks and collecting private feedback | Paying for public ratings or reviews |
| Replacing a tester who drops out with another real person | Fake or recycled Google accounts |
| Documenting findings in a QA report | Scripted sessions faking engagement |
The right-hand column isn't a grey area. Manipulating installs, ratings and reviews is addressed directly in Google Play policy, and enforcement lands on the developer account — your account, not the provider's. That asymmetry is the whole risk: the seller keeps the money either way.
Six questions that separate the two
1. "What exactly am I buying — testers, or installs?"
A straight answer names people and a process. A vague one names a number.
2. "What do the testers actually do?"
If nobody can describe the tasks, nobody is doing tasks. That also means you'll have nothing to write in the feedback section of the questionnaire.
3. "What do I get at the end?"
Ask to see a real deliverable before paying. A device coverage table and reproducible findings is a report; "completed" is a message.
4. "What happens if a tester drops out on day 3?"
The honest answer involves replacing them early, because Google counts the 14 days per tester and a replacement needs their own consecutive run. Anyone claiming a dropout is never a problem hasn't run a cycle.
5. "Will you ask testers to leave ratings or reviews?"
The correct answer is no. If it's yes, walk away — that's the part that puts your account at risk.
6. "Can you guarantee production approval?"
Nobody can. Google decides, and its documentation says you may be asked to keep testing if the app isn't ready. A provider promising approval is either misinformed or telling you what you want to hear.
Do the arithmetic on a $5 gig
Marketplace listings for "12 testers, 14 days" start around $5 and commonly sit under $50. Work out what that buys. Twelve people, keeping an app installed and opening it across fourteen days, then writing feedback. At $5 that is roughly forty cents per tester for two weeks of intermittent attention. At $50 it is about four dollars each.
No real person does that. The economics only close if the "testers" are recycled accounts, an emulator pool, or a swap ring where the same dozen people rotate through hundreds of apps without ever opening them. That is not a cheaper version of the same service — it is a different product, and it is the product whose enforcement risk sits on your developer account.
Why the cheap option often costs more
A $30 cycle that produces no usable feedback still leaves you facing the same questionnaire with nothing to write in it. If that application comes back asking for more testing, you have spent the money and the fourteen days and you are back where you started — except a month later. The expensive part of this process was never the fee; it was the calendar.
Related: the questionnaire questions and how to answer them, what a real report contains, and what to do after a refusal.
Want the version that holds up?
Real people, real tasks, and a report with their names off it.
Human testers enrolled for the full 14 days, daily enrollment checks, private feedback, and a QA report you can answer Google's questionnaire from. Plans from $180, worldwide.
Start your testing cycle