Guide
How to respond to negative app reviews
A negative review is read by far more people than the one who wrote it. The reply is not damage control — it is the only part of the exchange you control, and it is permanent.
Last updated
Answer the specific ones first
A one-star review that names a crash, a charge, or lost data is worth answering properly. A one-star review that says “rubbish” is not — there is nothing to respond to, and a reader can see that too. Sorting by rating and working down is the obvious approach and the wrong one; sort by whether there is a fact in the review.
When you cannot fix it yet
The temptation is to say nothing until there is good news. That leaves the review standing unanswered, which reads as nobody being home. Say what you know: that you have reproduced it, what causes it, and that you will update the reply when it ships. Then actually do that — both stores notify the reviewer when a reply changes.
Weak
Sorry for the trouble! Please reach out to support@example.com and we'll take a look.
Better
Reproduced — it affects accounts created before March when syncing over cellular. Not fixed yet; we'll update this reply when it ships. Your data is intact on our side in the meantime.
The second answers the question every reader has — is this me, and is it over — without pretending to a fix that does not exist. It also gives you a reason to come back and edit it.
Do not argue
Some reviews are unfair, some are about a feature working as designed, and a few are simply wrong. Correcting the record factually is fine. Litigating it is not: the exchange is permanent, public, and read by people forming a first impression of how you treat customers. You are not trying to win with the reviewer. You are trying to be legible to everyone after them.
Common questions
Should you reply to every negative review?
Reply to every one that names something specific — a crash, a charge, missing data. A review that only says "bad" gives a reader nothing to evaluate and gives you nothing to answer. Time spent on vague one-stars is better spent on the specific ones, which are the ones prospective users actually read.
How quickly should you respond?
Within a day or two for anything after a release. Negative reviews cluster in the days following an update, and a cluster answered quickly reads as a team paying attention. The same cluster answered three weeks later reads as damage control.
Can a reply change someone’s rating?
Yes, and it is one of the few things that reliably does. Both stores notify the reviewer when you respond, and both let you edit the reply later — so answering once while a bug is open and again when it ships a fix gives the reviewer a concrete reason to revisit their rating.
What should you do about unfair or abusive reviews?
Both stores have a reporting path for reviews that break their policies, and it is worth using for genuine abuse or spam. For a review that is merely harsh, reply factually and move on. Arguing in public is read by everyone who comes after, and the argument is the thing they remember.
Doing this by hand does not scale
BeenuLabs reads every App Store and Google Play review as it arrives, works out what it means, and drafts a reply in your brand voice and the reviewer's own language. You approve it — or set a star threshold above which it publishes itself.
Start freeFree forever on one app. No card required.