What Feedback Should You Report in Google Play's Production Access Form?
The production questionnaire asks what feedback your testing produced — and "it went well" isn't an answer that holds up. Here's what feedback Google actually finds convincing, and what to do if your testers genuinely didn't hit any problems.
What useful feedback actually looks like
- Bug reports with device, OS version, and reproduction steps.
- Usability friction — where a tester got confused or stuck in a flow.
- Feature gaps a tester specifically pointed out.
- A specific tester quote or a recurring theme across multiple testers, not a paraphrase of "it was good."
What to do with feedback once you have it
Document what changed as a result. "A tester reported X, we fixed it in build Y" is exactly the kind of specific, verifiable story that answers the questionnaire's feedback question well.
What if your testers found nothing?
It's tempting to write generic praise instead. Don't invent bugs that didn't happen — but do look harder. Onboarding friction, unclear copy, and small UI details are still real feedback. Google's questions are about whether testing reflected genuine use, not about whether bugs were found.
How a structured QA report helps
A written report that documents each finding by severity, device, and tester gives you exactly the specific material the questionnaire rewards. Our Complete package includes a QA feedback report built from the actual 14-day test, so you're never stuck writing a vague answer.
Skip the hassle — we'll handle your closed test.
12 real Android testers, 14 days of daily engagement, and a first-try approval guarantee. Start today — no card required.
Start your closed test →Frequently asked questions
- Do I need to report bugs to get approved?
- Not specifically bugs — but you do need something specific. Usability notes, small UX issues, or a documented "no significant issues found" with details of what was actually checked are all valid.
- Can I use email or WhatsApp screenshots as feedback evidence?
- Yes. How feedback was collected matters less than being able to describe it specifically and honestly in your questionnaire answer.
- What if feedback was informal — does it still count?
- Yes. Informal feedback is still real feedback as long as you can describe it concretely — what was found, by whom, and what you did about it.
- Should every tester submit separate feedback?
- It's not a published requirement, but feedback from multiple testers gives you more specific, credible material to draw on when answering the questionnaire.
- Is 'no issues found' an acceptable answer?
- It can be, if you back it up with specifics about what was tested and how — flows checked, devices used. A bare "no issues" with no detail is the weak version of this answer.
Official sources
Keep reading