WhollySoftware
Back to blogDesign

Designing Feedback and Rating Prompts That Get Honest Responses

Wholly Software TeamMarch 4, 20266 min read
Designing Feedback and Rating Prompts That Get Honest Responses

A client's mobile app was asking users to rate the app on the App Store immediately after they opened it for the first time, which is a moment with zero basis for judgment and predictably produced a flood of mediocre, uninformative ratings. We moved the prompt to trigger after a genuine success moment instead — completing a specific task the app is built around — and average ratings improved, not because the product changed, but because we were finally asking at a moment that reflected actual value delivered.

We also stopped combining sentiment capture and public rating into a single step. The revised flow asks a private, low-stakes question first ('How's it going so far?' with a simple positive/negative choice), and only routes genuinely positive responses toward the public App Store prompt, while negative responses go to a private feedback form instead of a public one-star review. This is a common and effective pattern, but implementing it required real care to avoid selectively suppressing negative feedback from reaching the team — we routed it to a support inbox, not into a void.

Open-text feedback fields performed far worse than we expected unless we gave people a starting structure. A blank 'tell us what you think' box mostly collected either nothing or vague single-word answers. Replacing it with 2-3 short, specific prompts ('What were you trying to do?' 'What got in the way?') produced meaningfully longer and more usable responses, because most users don't naturally know what a product team wants to hear without some framing.

We designed rating and feedback requests to be easy to dismiss without penalty, since forcing an interaction — a modal that can't be closed without answering — reliably produces resentful, low-quality responses just to make the prompt go away. A visible, low-friction dismiss option, paired with a reasonable cooldown before asking again, produced a smaller but noticeably more honest and useful set of responses across the client projects where we've measured it.

FeedbackUX ResearchMobile Design
Designing Feedback and Rating Prompts That Get Honest Responses — Wholly Software