Most developer responses to App Store reviews fall into one of three categories. Robotic: "Thank you for your feedback! We are always working to improve." Defensive: "Actually, if you read the FAQ..." Or the most common: absolute silence.
None of these help. Not with the reviewer, and not with the thousands of potential users reading your responses before deciding whether to download.
I've written hundreds of review responses across three apps. Here are 15 templates that actually work — organized by the five types of negative reviews I see most often, plus templates for positive reviews. Copy them, tweak them, make them yours.
The golden rule before we start
Every template here follows the same structure: acknowledge the specific issue, explain what you're doing about it, give them a way to reach you directly. That's it. Three sentences is all you need.
Never use the same template twice for reviews visible on the same page. Potential users can see multiple responses — if they're identical, you look like a bot.
Bug and crash reports (3 templates)
These are the easiest to respond to because the action is clear: fix the bug.
Template 1 — Known bug, fix incoming:
"Sorry about the crash on [specific scenario]. We've identified the issue and a fix is going out in [version/timeframe]. If you'd like to help us test the fix early, email us at [support email] — we'd really appreciate it."
Template 2 — Can't reproduce yet:
"That's frustrating — sorry you hit this. We haven't been able to reproduce the crash on our end yet. Could you email [support email] with your device model and iOS version? That would help us track this down much faster."
Template 3 — Bug fixed in latest version:
"Good news — we fixed this in version [X.X]. If you update to the latest version, you should be all set. Let us know at [support email] if it's still happening after the update."
Pricing and value complaints (3 templates)
Price complaints are rarely about the number. They're about perceived value — a pattern I noticed across thousands of reviews. The user hit a paywall before understanding what your app does.
Template 4 — "Too expensive":
"Totally understand — price matters, especially for indie apps. The free plan covers [key free features]. If you decide to try the paid tier, it includes [2-3 key paid features] for [price]. But either way, we appreciate you giving it a shot."
Template 5 — "Used to be free, now it's not":
"Fair point. We added the paid tier to fund [specific improvement — e.g., faster sync, new features, server costs]. The core features are still free. If the paid features aren't worth it for your use case, the free plan should still work well for you."
Template 6 — "Not worth the subscription":
"Sorry it didn't meet your expectations. We'd love to know which features fell short — if you email us at [support email], we'll take a serious look. We also offer a [refund/cancellation] if you're within [timeframe]."
UX confusion (2 templates)
When someone says "I don't understand how to use this," the problem isn't them. It's your app.
Template 7 — "Can't figure out how to do X":
"That's on us — [feature] should be easier to find. Here's a quick path: [1-2 step directions]. We're reworking this in the next update to make it more intuitive. Thanks for pointing it out."
Template 8 — "Too complicated":
"Appreciate the honest feedback. We're simplifying the [specific area] in our next update. In the meantime, if you email [support email], I can walk you through the setup — it takes about 2 minutes once you know where things are."
Feature requests (2 templates)
Feature requests disguised as complaints are a gift — they tell you exactly what to build next.
Template 9 — Requested feature is on your roadmap:
"Great news — [feature] is on our roadmap for [quarter/timeframe]. You're not the first person to ask, which tells us we're prioritizing the right things. Stay tuned."
Template 10 — Requested feature isn't planned:
"Interesting idea — we hadn't considered [feature] but it makes sense for your use case. I've added it to our feedback tracker. If enough people ask, it'll move up the priority list. Thanks for the suggestion."
"It used to be better" regression reviews (2 templates)
These come in waves after updates. Handle them with humility.
Template 11 — UI change backlash:
"We hear you — the [specific change] has been polarizing. The goal was [explain reasoning — e.g., better performance, cleaner navigation]. We're listening to the feedback and considering adjustments. Your input matters here."
Template 12 — Feature removed or changed:
"Sorry about the disruption. We [changed/removed] [feature] because [honest reason]. We know it's frustrating when something you relied on changes. Email us at [support email] — we want to make sure you have a workaround."
Positive reviews worth responding to (2 templates)
Don't ignore your fans. A response to a positive review turns a happy user into an advocate.
Template 13 — Detailed positive review:
"This made our day — seriously. Glad [specific thing they mentioned] is working well for you. If you ever have ideas for how we can make it even better, we're all ears at [support email]."
Template 14 — Short positive review ("Great app!"):
"Thanks! If there's anything specific you'd love to see added, let us know. We read every piece of feedback."
The nuclear option: the angry one-liner (1 template)
"Worst app ever." "Garbage." "Delete this."
These reviews have zero detail, maximum emotion. You can't fix what they won't describe. But you can still respond.
Template 15 — The rage review:
"Sorry you had a bad experience. We'd like to make it right — if you can share what went wrong at [support email], we'll dig into it personally."
Short, professional, door left open. That's all you can do. And every potential user reading it will see that you tried.
How to use these without sounding fake
Three rules. First, customize every response. Change 2-3 words minimum. Reference something specific from their review. "Sorry about the crash on launch" is better than "Sorry about the issue." Second, respond within 24 hours. Speed signals that someone is home. Third, never argue. Even when they're wrong. The response is for the audience, not the reviewer.
If you're responding to reviews via the App Store Connect API, you can template these into your workflow and personalize on send. That's what we do with AppTriage — pull the review in, draft from a template, customize, send.
Get all 15 templates (and more) in our copy-paste response templates library. Or skip the copy-pasting entirely — reply to reviews directly from your AppTriage inbox with one-click templates. Try free.