How we read App Store reviews without losing our minds
App Store reviews are a strange medium. People write them when they’re frustrated, occasionally when they’re delighted, almost never when things are working. Reading them raw, in chronological order, is a fast way to feel both worthless and validated within ten minutes.
And we don’t have only one store. Our apps live on the App Store, Google Play, the Microsoft Store, the Chrome Web Store and Edge Add-ons, each with its own review format, its own tone and its own way of replying. Without a routine, reviews would either take over the week or get ignored entirely. Neither is acceptable.
What we do instead
Once a week — never daily — one engineer pulls all new reviews across every app into a single document, grouped by app, then by signal: bug, feature request, support question, kind word, noise. Bugs go straight into our tracker. Feature requests get a tally. Support questions get replied to in-store. Kind words get screenshotted and pinned in the team chat (this matters more than it sounds).
The job rotates, so no one person carries the emotional weight of every review for long, and everyone on the team stays close to what people are actually saying. Whoever does it that week also writes a short summary at the top of the document: what’s new, what’s repeating, anything that looks urgent.
The weekly rhythm has one exception. If anyone spots something serious between passes — data loss, a crash on launch, a feature broken for everyone — it goes straight to whoever owns that app. Everything else can wait a few days without harm.
How we reply
We answer support questions in plain language, without templates where we can avoid them. When a review reports a bug we’ve fixed, we say which update fixed it. When someone asks for a feature we’re not going to build, we say so politely rather than promising to “pass it on to the team.” A clear no is more respectful than a vague maybe.
We don’t argue with reviews, even unfair ones. Occasionally a review is simply wrong about what the app does. The reply corrects the facts once, briefly, for the benefit of the next person reading — and then we leave it.
What we ignore
Star ratings in isolation. The score is a lagging indicator of work we did months ago, drifting in response to invisible changes in the user base. We watch the slope, not the number.
We also set aside reviews that are really about something else: a store’s billing, a phone’s storage, a different app with a similar icon. They get a short helpful reply when we can offer one, and no further thought.
What we got wrong
For a while we read reviews whenever a notification came in. It felt responsive. In practice it meant a single angry sentence could derail an afternoon, and we reacted to individual voices instead of patterns. Batching them weekly made us calmer and, oddly, better at spotting real problems — a bug mentioned by several different people in one week stands out in a way it never did when we read them one at a time.
The trick is reading reviews on our schedule, not on Apple’s.