How to Answer a 1-Star App Review Without Making It Worse

To respond to a 1-star app review, do three things in order: name the exact problem in the reviewer's own words, own the fix with a date or a real next step, and offer exactly one thing for them to do next. Skip the defense. That's the whole move. The rest of this page is the scripts, the edge cases, and the evidence for why it works.

A one-star review feels like an attack, so the instinct is to explain yourself. Resist it. The reviewer isn't asking for a defense. They're asking to be heard and then given a reason to come back. The stakes are higher than the one review, too: your public replies are read by every prospect who scrolls the reviews before they tap install. You're never writing to one angry person. You're writing to the next thousand who are deciding whether you're the kind of team that shows up when something breaks.

Yes, and the numbers are unusually clear for something this cheap to do. At Google I/O 2019, Google reported that developers who respond to reviews see an average rating bump of +0.7 stars. A peer-reviewed study of over 4.5 million reviews (Hassan et al.) found users were roughly six times more likely to raise their rating after a developer replied: 4.4% did versus 0.7% who changed with no reply. And McIlroy et al. (IEEE, 2017) found that when a rating did change after a response, 38.7% of those changes were increases.

None of those numbers are magic. They're the aggregate of thousands of individual replies that did the three things above, plus the ones that didn't and moved nothing. A reply is a lever; whether it lifts depends entirely on how you write it. If you want the full breakdown of the mechanism, we go deep in does replying to app reviews raise your rating. Here, we're going to write the replies.

Open by restating the specific thing that went wrong. "Sorry the app logged you out after the update" tells the reviewer you actually read what they wrote. Generic openings do the opposite. "Thanks for your feedback!" reads as a form letter, and a form letter to someone who's furious is its own small insult.

Naming the problem also does quiet work on the next reader. When a prospect sees a developer accurately describe a bug and then say it's fixed, the review stops being a warning and becomes proof of a responsive team. You've turned a liability into a testimonial without spinning anything.

Notice what that reply doesn't do. It doesn't argue. It doesn't say "we couldn't reproduce this." It doesn't bury the fix under three paragraphs of process. It names the bug, gives a version number, holds one door open, and gets out. Under 350 characters, which matters because Google Play enforces a hard 350-character reply limit. You don't get to ramble even if you want to.

Money reviews are the ones that read angriest, because the stakes feel concrete to the reviewer in a way a UI gripe doesn't. The trap is getting defensive about a charge you believe is correct. The move is to acknowledge the frustration as real, then route them to the one place a refund can actually happen, which for both stores is the store, not you.

Be honest about that boundary. You can't refund an App Store or Play purchase directly, and pretending you can just delays their resolution. Point them at the right door and offer to help from your side.

Some one-stars are about a device that ran out of storage, a carrier outage, a feature the app never claimed to have, or a competitor's product entirely. Your job is still not to argue. It's to gently correct the record for the next reader while staying warmly on the reviewer's side, because the audience for this reply is everyone who reads it later and needs to know the complaint doesn't apply to them.

There's a real craft to these, and it's easy to sound smug. We wrote a whole field guide on it: app reviews that aren't your fault. The short version is validate the frustration, correct the fact in one clean sentence, then offer help anyway.

That one's in Spanish on purpose. A large share of the world's app reviews aren't in English, and a reviewer who writes in their own language and gets a reply in yours feels handled, not heard. Answering in the reviewer's language is one of the highest-leverage things you can do, and it's the single most tedious to do by hand. If most of your negative reviews come from abroad, replying in any language is worth its own read.

After you've named the problem, state what you're doing and when. If a fix is shipping, say the week. If it isn't, say what you're investigating. Vague sincerity beats fake precision, but real precision beats both. Then close with a single action: an email to support, a beta invite, an extended trial. One door, held open.

The reason it's one door and not three is that a wall of options reads as a dodge. "You can email us, or tweet us, or check our help center, or..." tells the reviewer you'd rather they went away. One clear next step tells them you expect to actually resolve this.

Here's the part most teams skip. When you ship the fix a reviewer flagged, you've earned the right to go back and tell them, and, carefully, to ask if they'd take another look. This is the only time asking for a rating change isn't tacky, because you're not begging; you're closing a loop the reviewer opened.

Timing and tone are everything. Wait until the fix is genuinely live. Reference their specific complaint so they know it's not a mass mailing. Make the ask soft and optional, and give them the update whether or not they re-rate. The point is that you fixed it; the re-rating is a bonus you don't require.

That reviewer might bump you to four stars. They might not. But the update itself is now public, and every future reader sees a team that came back and closed the loop. That's the compounding return on replies — and it only works if you can actually track which reviews you promised what, then circle back when the build ships. Doing that across a few hundred reviews a month by memory is where good intentions quietly die.

The three-move formula is easy to write once. It's hard to write two hundred times a month, in six languages, within the day, while also shipping the app. And speed matters: since Google's 2019 shift to a recency-weighted average, a fresh low-star review you convert quickly moves your visible rating more than an old one ever could. How fast you reply is a lever you control, and a reply that lands next week lands on a rating that's already settled.

This is the gap Reply Argus is built for. It watches your App Store and Google Play reviews in one inbox, drafts a reply to each in the three-move shape — grounded in your past approved replies and your own knowledge base so it never invents a fix you didn't ship, and writes it in the reviewer's own language. You approve, edit, or set opt-in rules to auto-publish the safe ones. When you fix a bug, the reviews that flagged it are clustered together, so circling back to ask for a revisit is one pass, not an archaeology dig.

Pick your worst one-star from this week and rewrite it in the three moves: name it, own the fix, one next step. It'll take five minutes and it'll teach you the shape better than any template. When five minutes times two hundred reviews stops being a thing you have time for, start free with Reply Argus — no card, and it drafts your first reply in minutes, in the reviewer's language, for you to approve.