Is a tester exchange allowed by Google Play?
Updated
Short answer: Google's published requirements do not restrict how you find testers. What Google does care about is whether the testing was real: real people, using their own accounts, actually trying the app. A tester exchange can meet that standard or fail it, depending on how it is run and how you take part.
We run a test-for-test exchange, so weigh what follows with that in mind. We have tried to be precise about what Google says and does not say.
What Google says
Google's help page on the testing requirement tells new developers to find testers by reaching out to "friends, family, colleagues, or classmates", connecting "with communities where potential users exist", and using social media to invite followers. It does not list approved or forbidden recruitment methods. (Those routes, and how well each keeps testers for fourteen days, are compared in how to get 12 Google Play testers for free.)
It does say two things that matter more than where testers come from:
- Give testers clear instructions on how to test and report bugs.
- Keep a record of feedback, because you must summarise your testing feedback when applying for production access.
So the question is not "is an exchange allowed" but "will an exchange give me real testing I can describe honestly". That depends on the exchange.
What makes an exchange legitimate
- Real people with their own accounts. Each tester is a person using their own Google account on their own phone. Not spare accounts, not emulators, not one person with twelve logins. Why own accounts are a risk.
- Verified opt-ins. Someone saying "I joined" is not proof. The developer should check each tester against their own Play Console.
- Actual use. Testers install the app, open it on different days and try what it does. An exchange where everyone opts in and never opens anything produces a test with nothing to report.
- Feedback. Testers say what confused them and what broke. That is what the production access form asks you to summarise.
Where exchanges go wrong
- Opt in and forget. It meets the count and fails the purpose. You reach the application with no engagement to describe.
- Fake or farmed accounts. Some groups and services fill seats with accounts that exist only for that. It is the one thing that turns a legitimate method into a risky one.
- Copy-paste feedback. "Great app, no issues" from twelve people tells a reviewer nothing, and suggests nobody looked.
- Promises of approval. Nobody but Google can promise production access.
How TestersWiz handles it
On TestersWiz, other developers test your app while you test theirs. Every tester is a member with their own account; the developer checks each tester's Google address against their own Play Console before they count; and testers check in with evidence during the fourteen days. None of that guarantees production access, which only Google decides, but it is designed to produce the kind of testing you can describe truthfully.
What to write in your application
Say how you recruited testers, plainly. For example: "Some testers were friends and colleagues, and the rest were Android developers from a test-for-test exchange, where I tested their apps in return." Then describe what testers found and what you changed. The production access questions guide goes through every question.
Other options
An exchange is one of four common routes, alongside people you know, your own audience and paid services. Each has a different cost in time, obligation or money. Free vs paid app testers compares them honestly.