Getting 12 testers through 14 days is the part everyone talks about. After that, Play Console hands you a form, and the form is where a lot of apps get turned back.
I run TestFi, a small testing marketplace, and developers forward us their refusal emails. The reason is almost never that they had too few testers. It's that Google didn't see enough engagement, or didn't see the developer do anything with what testers said. Both get judged from what you write in this form.
Google doesn't publish the form, and the wording shifts a little between accounts. This is how it reads in Play Console in 2026. There are three sections.
About your closed test
1. How did you recruit users for your closed test? For example, did you ask friends and family, or use a paid testing provider?
Tell the truth, including if you paid a testing service. Paid testers aren't against the rules. Fake accounts, emulators and one person running five accounts are. A vague answer reads worse than an honest one.
Weak: "Friends and online communities."
Better: "16 testers through [service], a paid testing provider, plus 3 colleagues. Everyone installed from the opt-in link on their own Android phone."
2. How easy was it to recruit testers for your app?
Multiple choice. Pick what happened. Nobody gets refused for saying it was hard.
3. Describe the engagement you received from testers.
This is the one the refusals point at. Numbers beat adjectives: how many testers stayed the full 14 days, how often they came back, what they actually did in the app. If you asked for check-ins, say how many came back.
Weak: "Testers were very engaged and used the app every day."
Better (the app here is made up, use your own numbers): "14 of 16 testers stayed opted in for all 14 days. 13 sent a written check-in on day 7 and 12 on day 14. Most used the habit list and reminders. 5 tried CSV export, which is how we found the export crash."
4. Provide a summary of the feedback that you received from testers. Include how you collected the feedback.
Two answers in one. How: a form, check-in questions, an email thread, a feedback button in the app. What: group it into themes and count them. "Six testers said onboarding asked for too much before showing anything" is a summary. "Testers liked the app" isn't.
About your app
5. Who is the intended audience for your app?
One or two specific sentences. "Students revising for exams who want five-minute daily reviews" beats "everyone who wants to learn".
6. Describe how your app provides value to the users.
What someone can do with it that they couldn't before, in plain words. Not a feature list.
7. How many installs do you expect in your first year?
Multiple choice. Be realistic. A small number is not a red flag.
Your production readiness
8. What changes did you make based on your closed test?
The other refusal reason I see a lot: testers said things and nothing changed. List the updates you shipped during or after the test, each one tied to something a tester said, with version numbers.
Weak: "We fixed some bugs and improved the UI."
Better: "1.0.3 fixed the CSV export crash two testers reported. 1.0.4 cut onboarding from five screens to two after six testers called it too long."
9. How did you decide that your app is ready for production?
Your evidence. What testers found and you fixed, what's still open and why it can wait, testers getting through the main flow on the last build.
Collect the material during the 14 days, not after
Nearly every weak answer I've read has the same cause: the developer opened the form on day 15 with nothing written down.
- Give testers a small task every few days, so they have something specific to report.
- Ask for a written check-in on day 7 and day 14 at least, and keep them.
- Ship one update during the test that answers something a tester said.
- Write down version numbers and dates as you go.
Already refused? You can run another closed test and apply again. Do those four things the second time and write the answers from what you collected.
Disclosure: I'm the founder of TestFi. Our closed test is $39.99 for 16 testers, or $49.99 for 20. Every tester writes check-in notes on day 7 and day 14, and the campaign dashboard drafts answers to this form from those notes, leaving brackets for the parts only you know, like what you changed. Details at testfi.app/google-play-12-testers. The advice above works however you find your testers.
If your refusal email says something I didn't cover, paste the reason in the comments and I'll tell you what I'd write.
Top comments (0)