How to Write a Useful App Review Reply in 350 Characters

Google Play gives you exactly 350 characters for a developer reply, and it's a hard cap. Paste in more and the response won't post. To fit a genuinely useful answer inside it, drop the greeting and the gratitude paragraph, lead with the actual fix or answer in the first sentence, and close with one clear next step. That's the whole method. A tight reply that solves the problem beats a warm one that runs out of room before it says anything.

The instinct most teams fight is padding. "Hi there, thank you so much for taking the time to leave your feedback…" — that opener alone can burn 120 of your 350 characters before you've touched the complaint. Below is how to spend the budget well: what counts toward the limit, the three-part shape that always fits, and before/after examples so you can see the cuts. (Apple, worth noting up front, publishes no official limit — more on that near the end.)

Everything visible counts: letters, numbers, punctuation, and spaces. A space between two words is one of your 350, so line breaks and the double-space after a period add up faster than people expect. There's no separate word limit — it's a raw character count, and the Play Console editor stops accepting input the moment you hit the ceiling.

Two things eat more budget than they look like they should. Emoji frequently count as two characters rather than one, so a couple of decorative emoji can quietly cost four to six. And a pasted URL is expensive — a long support link can swallow 40 or 50 characters on its own. If you need to point someone somewhere, a short branded link costs far fewer characters than a full support URL.

Almost every good reply under 350 characters follows the same three beats. One short line of acknowledgement so the reviewer feels heard. The fix or answer — the reason they're reading. And a single next step that moves them forward. No sign-off, no second ask, no restating the problem back to them. Each beat earns its characters or it gets cut.

Here's a real-shaped example. The bloated version below runs to 389 characters, over the cap, so Google Play would reject it outright. Notice how little of it addresses the actual crash:

"Hi there! Thank you so much for taking the time to leave us a review and for being a valued member of our community. We are truly sorry to hear that you experienced a crash, and we completely understand how frustrating that must be. Your feedback is incredibly important to us and we are always working hard to improve. Please rest assured that our team is looking into this. Thanks again!"

Four sentences, zero information. The reviewer still doesn't know if it's fixed, what to do, or whether they'll ever hear back. Now the same situation, rebuilt to the three-beat shape and landing at 217 characters, well under the limit with room to spare:

That reply is shorter, warmer, and actually solves the problem — cutting the filler left room for the version number and the next step. This isn't only an aesthetic preference. When researchers ranked what makes a developer response likely to change a user's rating, the strongest predictor wasn't politeness or reply speed. It was the length ratio between the review and the response (Srisopha et al., EASE 2021). A reply proportional to the review that engages the specific complaint moves ratings more than a long, generic one. The 350-character cap nudges you toward exactly that.

And the payoff for replying at all is well documented: when Google introduced recency-weighted ratings at I/O 2019, it reported that responding to reviews correlates with an average lift of 0.7 stars. A tight, specific answer to a one-star complaint is also quiet reassurance for the next hundred people reading it before they decide to install. If you want the fuller case, we walk through it in [does replying to app reviews raise your rating](/blog/does-replying-to-app-reviews-raise-your-rating).

When a draft runs long, trim in this order, top to bottom: the top items are almost always pure padding, the bottom ones are load-bearing and should survive.

The cap doesn't change when the review is in Spanish, German, or Japanese: it's still 350 characters, and character-based scripts like Japanese count each character toward the limit the same way. The good news is that the three-beat shape translates cleanly. Here's the crash reply rebuilt in Spanish, 241 characters, still under the cap and keeping all three beats intact:

Replying in the language the reviewer wrote in matters more than most teams assume — a user is likelier to update their rating when the answer meets them in their own language than when it's a translated-looking English wall. We cover doing that across a whole inbox in [reply to app reviews in any language](/blog/reply-to-app-reviews-in-any-language), and the store-by-store differences (including this exact character-limit gap) in [App Store vs Google Play review replies](/blog/app-store-vs-google-play-review-replies).

So a useful reply in 350 characters isn't a compromise — the constraint is doing you a favor, forcing out the filler and leaving the fix. Acknowledge in a clause, answer concretely, point to one next step, and almost everything fits with room to spare. The harder part is doing that for every review across both stores, in every language, without the queue lapsing during a busy week. That's the part worth handing off. [Start free with ReplyArgus](/signup), no card needed, and Argus drafts your first reply in minutes — in the reviewer's own language and already sized for Google Play's 350-character cap.