Reviews & Ratings
Use Private Test Feedback to Improve Your Public Release
Understand the difference between useful product feedback and public store ratings.
On this page · 4 sections
At a glance
In plain English
- Ask for observations before opinions
- Keep public reviews independent
- Respond through product changes
Ask for observations before opinions
During a private test, ask what happened in a specific journey and what the participant expected. Those details help improve the product. A positive score without context does not tell you why a flow succeeded or where another user might struggle.
Keep public reviews independent
Do not make favourable ratings a condition of participation or compensation. Keep paid testing tasks separate from public-review requests. Consult Google's ratings policy before designing any campaign, and avoid presenting purchased praise as independent customer experience.
Respond through product changes
Group recurring concerns by user journey and prioritise reproducible failures. After release, use genuine customer feedback to refine your backlog. Explain fixes clearly in support replies without asking users to change a rating as the price of receiving help.
Sources
Official references used
- App testing requirements for new personal developer accounts (Google Play Console Help)
- Set up an open, closed, or internal test (Google Play Console Help)
- View and analyze your app's ratings and reviews (Google Play Console Help)
Continue
Choose the next step
Related
Next pages to read
Apply the guide to your closed-testing run.
Use the free tools to check your setup, or review managed tester support when recruitment and coordination are the blocker.