A one-star review notification lands and the instinct is either to fire back defensively or to ignore it and hope it sinks. Both reactions cost you more than the review itself, because your reply isn’t just for that one user — it’s a public, permanent post that every future visitor to your app’s listing will read before they decide whether to download.
Table of Contents
This guide walks through a simple framework for writing a reply that actually helps, plus the specific rules Apple and Google enforce on App Store Connect and Google Play Console — character limits, editing, and notifications — so you don’t find out the hard way that your reply got cut off or never reached the reviewer.
Quick Answer
Reply promptly, address the specific problem the reviewer mentioned (not a generic apology), take responsibility without being defensive, and give a concrete next step — a fix that’s already shipped, a workaround, or an invitation to email support with more detail. Keep it short: Google Play caps replies at 350 characters, and even on the App Store, where there’s no official cap, brevity reads better than a corporate script.
A 5-Step Framework for the Reply Itself
Read it twice before responding. A one-star review written in frustration is rarely about your product being worthless — it’s usually one specific bug, a confusing screen, or a bad support experience. Reacting within minutes, while you’re still annoyed, is how replies turn defensive.
Name the actual issue. ‘Sorry you had a bad experience’ could be copy-pasted onto any review. ‘Sorry the export button crashed the app on your device’ shows you actually read it — and shows everyone else reading the thread that you pay attention.
Apologize for the experience, not necessarily the facts. You can acknowledge frustration without conceding a factual point you know is wrong (e.g., a review blaming your app for a known OS-level bug). State what’s true, briefly, and move on.
Give a concrete next step. ‘Fixed in version 4.2, out now’ or ‘Please email support@yourapp.com with your order number and we’ll sort it same day’ does more work than any amount of apologizing. If it’s already fixed, say so — that’s often what turns a rating around.
Stop there. Don’t argue, don’t over-explain, and per Google’s own guidance, don’t explicitly ask the reviewer to raise their rating — focus the reply on solving their problem, not on the star count.
The Platform Rules You Need to Know
On Google Play Console, developer replies are capped at 350 characters of plain text (HTML tags get stripped and don’t count toward the limit), so write tight. The user gets a push and email notification the first time you reply to a given review — replying again to the same thread doesn’t re-notify them, so make the first reply count. Google’s own guidance is explicit that 1- and 2-star reviews deserve a hand-written reply rather than a canned template.
On the App Store, accounts with the Account Holder, Admin, or Customer Support role in App Store Connect can respond to reviews. Apple doesn’t publish an exact character limit, but replies can run considerably longer than Google Play’s 350-character cap. The reviewer is notified when you first respond, and you can go back and edit your response at any time — only the latest version is shown publicly, with a notation marking it as edited. Per Apple’s own guidance, if you make several edits to a response in a short window (say, fixing a typo or tightening the wording), that counts as a single notification to the reviewer rather than a fresh one for every edit — so don’t be afraid to clean up a reply shortly after posting it.
If a review is abusive, spam, or violates the store’s terms, don’t reply to it at all — use Apple’s ‘Report a Concern’ option or Google Play’s reporting flow instead. Reporting doesn’t notify the reviewer, whereas replying does.
Tips and Common Mistakes
Don’t copy-paste the same reply across multiple one-star reviews — it’s easy for readers to spot a template, and it undercuts the sincerity of the apology.
Don’t argue in public. Even if the reviewer is factually wrong, a back-and-forth in a public reply thread makes your app look worse to everyone browsing, not just the reviewer.
Don’t let ‘we’re looking into it’ be the last word. When the fix ships, go back and reply again (or edit your existing reply) referencing the update — this is exactly the kind of follow-through both Apple and Google’s guidance points toward.
Don’t skip one-star reviews because ‘that user is already gone.’ The reply is really aimed at the hundreds of undecided people who read reviews before installing — a calm, specific response to criticism often reassures them more than a wall of five-star reviews does.
Explore more: More app development guides.
Responding to one-star app reviews FAQs
Can I edit an App Store or Google Play review response after posting it?
Yes on both. In App Store Connect you can edit your response at any time and only the latest version displays publicly (marked as edited) — Apple’s guidance says making several edits in a short window still counts as one notification to the reviewer, not one per edit. Google Play Console also lets you revise your reply.
Is there a character limit for review replies?
Google Play limits developer replies to 350 characters of plain text. Apple hasn’t published an official limit for App Store replies, but in practice you have noticeably more room than on Google Play — that doesn’t mean you should use it all.
Will replying to a one-star review get the user to change their rating?
There’s no guarantee, but both platforms notify the reviewer when you first respond, which gives them a chance to reconsider if their issue gets resolved. Focus the reply on actually solving their problem rather than asking for a higher rating — Google explicitly discourages the latter.
Build It With GTStudios
Need help with your website, app, or small-business tech? GTStudios builds web, apps, and software for small businesses. See how GTStudios can help.
Photo by Rahul Chakraborty on Unsplash.