"Not in My Language. One Star." — Handling Language-Complaint Reviews

You can't add Turkish, or Thai, or Brazilian Portuguese to your app by tomorrow. So when a review lands that says "not in my language, one star," the reflex is to shrug and scroll past it. Don't. This is the single most reversible negative review you get, and the move is almost backwards from what you'd expect: reply in the reviewer's own language, name the gap honestly, and put the language on your roadmap without inventing a ship date. A review written out of feeling excluded turns into public proof that you actually listen.

Here's why a language complaint deserves a different playbook than a normal one-star, the exact reply that softens it, and how to run this across locales you don't even read yourself.

A crash report is a fact: the camera broke, fix it. A language complaint is closer to an accusation. The reviewer isn't telling you something is broken — they're telling you the app wasn't built with them in mind. That lands as personal, and it reads as personal to everyone in their locale who scrolls the reviews next.

That's the part developers underrate. One "solo en inglés, no sirve" near the top of your Spanish-locale reviews is a signal to a whole market that this app isn't for them, and they self-select out before they ever install. Fresh reviews also carry more weight than old ones in both stores' rating math, so a recent language ding punches above a two-year-old complaint. We get into why in [recent reviews weigh more](/blog/recent-reviews-weigh-more).

But that same emotional core is why it's so recoverable. What the reviewer wants most in that moment isn't the feature shipped by Friday — it's to be understood. You can give them that instantly, before a single line of localization gets written, by answering in the language they wrote in.

The complaint underneath every language review is "you didn't consider me." Reply in English and you quietly confirm it. Reply in their language, matching the exact one they wrote in, and you contradict it in the most direct way there is — no feature required, no roadmap promise made. You've shown the consideration they said was missing.

Here's what that looks like in practice. A one-star, Spanish, angry that the app is English-only:

Notice what that reply does and doesn't do. It agrees with the reviewer instead of getting defensive. It admits the app is English-only today. It puts Spanish on the roadmap but refuses to name a date it can't keep. And every word of it is in Spanish — the whole point. Responding at all already tends to help: Google shared at I/O 2019 that developers who respond to reviews see about a +0.7 star bump on average, and Hassan et al.'s study of 4.5 million reviews found a reviewer who gets a reply is roughly six times more likely to raise their rating than one who's ignored. A reply in their own language is the version of that with the friction taken out.

The instinct to soften an angry reviewer is the right one; the trick is doing it without over-promising. We break the full angry-review move down in [how to respond to negative app reviews](/blog/how-to-respond-to-negative-app-reviews); the language case is that same discipline pointed at a fixable-but-not-today problem.

The structure is the same every time. Only the language changes.

This is where honesty pays compound interest. There are three real situations, and each has a truthful reply:

Tagging every one of these isn't tidiness — it's product intelligence. Ten scattered "add German" reviews across six months feel like noise; the same ten clustered together are a ranked feature request with a market attached. That's what ReplyArgus does automatically: reviews roll up into a PM roadmap board (exportable to Jira, Notion, or Google Sheets), so rising language demand surfaces as a theme instead of hiding one review at a time.

Replying in Spanish is easy if you speak Spanish. The wall is the other twenty locales: the reviews in languages you can't read, can't verify a translation for, and can't confidently reply in. Hand-translating each one is slow, and slow is fatal here, because a language reviewer who's already feeling ignored is the last person who'll wait a week for an answer.

This is the exact seam ReplyArgus is built into. It watches your App Store and Google Play reviews in one inbox, detects each review's language, and drafts the reply in that same language across 100+ languages, both directions, grounded in your past approved replies and an auto-ingested knowledge base of your store listing, so the draft answers from what your app actually is, not a generic template. You approve it in a click, or set a rule to auto-publish the safe ones. The full mechanics live in [replying to app reviews in any language](/blog/reply-to-app-reviews-in-any-language), and the whole workflow is on the [features page](/features).

Here's the same playbook running in a language most solo teams can't answer in unaided. A Japanese two-star, softened without a word of English:

Does any of this move the number? Responding well correlates with rating recovery more than most single things you can do to a review. We lay out the evidence, and its limits, in [does replying to app reviews raise your rating](/blog/does-replying-to-app-reviews-raise-your-rating). A language reply is that effect at its strongest: you're solving the reviewer's real grievance, feeling unseen, on the spot.