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, ready-to-adapt templates for the most common complaint types, and 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 (a review blaming your app for a known OS-level bug, for example). 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.
Example Replies You Can Adapt
A bug that’s already fixed: ‘Hi [name], you’re right that the export button was crashing on some Android 14 devices — that’s fixed in version 4.3, which is live now. Update and it should work; if it doesn’t, email support@yourapp.com and we’ll dig in.’ Naming the exact bug and version number is what separates this from a template.
A missing feature or design complaint: ‘Thanks for the honest feedback — dark mode isn’t in the app yet, but it’s on our roadmap based on requests like this one. In the meantime, lowering your device brightness in low-light use helps a bit. Appreciate you flagging it.’ This doesn’t pretend the gap doesn’t exist, which reads as more credible than a deflection.
A pricing or subscription complaint: ‘I hear you on the price — we priced the annual plan to work out cheaper per month than the monthly option if that helps. If you were charged after canceling, email support@yourapp.com with your receipt and we’ll sort it directly.’ Billing disputes belong in a private channel, not a public back-and-forth, so the reply should route there fast.
A review that’s a misunderstanding or user error: ‘Sorry for the confusion — the sync happens automatically every time you open the app, so there’s no manual button to press. If it’s still not syncing on your end, email us and we’ll take a look at your account.’ State the correct behavior plainly, once, without sounding like you’re correcting the reviewer’s intelligence.
An abusive, spam, or policy-violating review: don’t reply at all. Use Apple’s ‘Report a Concern’ option in App Store Connect or Google Play’s reporting flow instead — reporting doesn’t notify the reviewer, whereas replying does, and a public reply to an abusive review just gives it more visibility.
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 edit or delete your response at any time — you don’t even need to be the person who originally wrote it. Only the latest version is shown publicly, with a notation marking it as edited.
App Store Connect also lets you turn on email alerts for when a customer edits a review you’ve already replied to, so you’re not relying on manually re-checking old threads to catch an updated rating.
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 offer refunds, discount codes, or account-specific fixes in the public reply. Route anything involving personal or billing details to email or in-app support, and keep the public-facing reply generic enough to post without exposing the reviewer’s account info.
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.
Photos
Frequently Asked Questions
Can I edit an App Store or Google Play review response after posting it?
Yes on both. In App Store Connect you can edit or delete your response at any time, and only the latest version displays publicly, marked as edited — you don’t even need to be the original author to edit it. Google Play Console also lets you revise your reply at any time; the updated text simply replaces the old one.
Is there a character limit for review replies?
Google Play Console enforces a hard 350-character limit on developer replies, with HTML tags stripped and excluded from the count. Apple doesn’t publish an exact cap for App Store Connect replies, but shorter is still better — reviewers and future readers skim, they don’t read corporate statements.
Will replying to a one-star review get the user to change their rating?
It can, but it’s not guaranteed and you shouldn’t explicitly ask for it. A specific, helpful reply — especially one pointing to a fix that’s already shipped — is what sometimes prompts reviewers to go back and raise their rating on their own. Google’s guidance specifically advises against asking directly.
Should I reply to or just report an abusive or clearly fake review?
Report it instead of replying. Both Apple’s ‘Report a Concern’ flow in App Store Connect and Google Play’s review-reporting option exist precisely for spam, abuse, and policy-violating reviews, and reporting doesn’t notify the reviewer the way a reply does.
Who is allowed to reply to reviews on each platform?
On App Store Connect, only accounts with the Account Holder, Admin, or Customer Support role can post or edit review responses. Google Play Console reply permissions are controlled through the account’s user-management settings, so check that a team member has the right access level before assuming they can respond.
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.
Want dev news in your inbox? Subscribe to the free newsletter.