In this guide
A review request asks for a public verdict. A feedback request asks for information. They sound close but lead to different results, and the second one is easier to answer honestly.
The difference
- Feedback is private, specific and meant for you: "The export button did nothing."
- A review is public, short and meant for other visitors: "Doesn't work. 1 star."
Someone who hits a bug will often write a review in anger if the only door open is the store. Give them a private door first.
Why feedback first
- You hear about problems before they become stars.
- You get detail a star never carries.
- Your request stays neutral: you ask what happened, not for a score.
Keep it honest
Do not use the feedback step as a filter that sends only happy users to the store and hides the rest. Apple's guidelines (section 3) list "filtered" feedback next to paid, incentivized and fake feedback as attempts to manipulate reviews, and Google's policy says to "Prompt users to leave a rating in a clear, non-deceptive way." Neither page names this flow explicitly, so check the current Apple and Google guidance first (see request a rating safely). A rating prompt should never come with a reward.
Wording examples
Example, neutral feedback ask:
"How is it going? Tell us what worked and what didn't. It takes a minute and only we read it."
Example, after a clear success:
"Glad that worked. Want to tell us what we could improve?"
Avoid: "Love the app? Give us 5 stars!" and anything that promises something in return.
Where to put it
Offer a feedback link in settings and after key moments. Do not interrupt first-run or a task in progress. Details in asking for in-app feedback without nagging and when to ask.
What to do with the answers
Tag them and look for repeats: review tagging sheet.
AppReviewX is built on this idea: private, structured feedback, one feedback written for one credit. Start free.
Related: hub, tagging sheet, request a rating safely.