How to Collect Useful Feedback During Closed Testing

The Questionnaire Hurdle

Many developers perfectly execute the 14-day closed test, maintain a 12-tester streak, and still get rejected. Why? Because they fail the final step: The Production Access Questionnaire.

Google asks you to detail exactly what feedback you received from your testers. If you answer "The app was perfect," you will be rejected. You must provide actionable, realistic feedback.

Where Should Feedback Be Collected?

Google Play offers a built-in feedback mechanism for closed tracks. Testers can leave private reviews directly on the Play Store listing that only you can see.

However, you should not rely solely on this. We recommend setting up secondary channels:

• A Google Form: Create a short survey asking testers to rate the onboarding flow, the UI clarity, and report any bugs.
• A Dedicated Email: Instruct testers to email screenshots of weird layouts or crashes.
• A Discord/Slack Channel: For real-time chat and immediate bug reporting.

What Kind of Feedback is Useful?

You need feedback that proves your testers actually used the app deeply. Categorize the feedback you collect into three buckets:

1. Usability / UX

Examples: "The text on the settings page is too small to read on my Pixel 6." or "The 'Next' button blends into the background."

2. Bugs & Glitches

Examples: "The app crashed when I tried to upload a profile photo larger than 5MB."

3. Feature Requests

Examples: "It would be great if the app supported a dark mode toggle."

Using the Feedback

When you apply for production, summarize this collected data clearly. Explain exactly which of these issues you fixed during the 14-day window (e.g., "We increased the font size in release V1.0.2") and which feature requests you have added to your future roadmap. This level of detail guarantees approval.