Why Is My App's Rating Different in Other Countries?

Your app's rating is different in other countries because there is no single global rating — both the App Store and Google Play show each user a *localized* average built from the reviews of people in their own market. Open your app in the US storefront and you might see 4.6; open the exact same build in Germany or Brazil and it can read 4.1 or 3.8. Same app, different number, because a shopper in Munich is shown what Munich users think, not a worldwide blend.

This surprises developers who watch one average in their dashboard and assume that's what every user sees. It isn't. A rough regional launch, a payment bug that only fires on a local carrier, a translation nobody proofread — any of these can drag the rating in that one market well below your global figure, and the users you're trying to win there see the low one. Below: how each store localizes the number, why one bad market pulls down only its own rating, and why replying *per market, in the reviewer's language* is the lever that fixes it.

Both stores compute a rating for the audience actually looking at the listing. Apple has always done this by storefront — each country's App Store has its own pool of ratings and reviews. Google Play used to show one worldwide number, then changed course: since November 2021 it shows users a rating specific to their country or region, and since early 2022 it further narrows it by device type (phone, tablet, foldable, Chromebook, Wear OS, Auto). So on Play the number is filtered twice: where you are, and what you're holding.

That means the "my rating dropped but only in France" mystery isn't a glitch — it's the design. The store shows local users a local number, so a problem in one market doesn't tank your rating everywhere else, but it does show up sharply in that market's own number while your other storefronts stay clean. If you've only ever watched the blended average, you've been reading a number no individual user is shown.

The App Store is a collection of country storefronts, and your app has a separate rating and review set in each one. A five-star run in Japan does nothing for the number a shopper sees in Mexico; the Mexican storefront shows Mexican ratings. This is why an app can sit at 4.7 in its home market and 3.9 in a country where it launched late, shipped an unlocalized build, or hit a region-specific bug.

Apple's rating is a cumulative lifetime average per storefront, with no public recency weighting, so a bad early stretch in one country lingers there longer than it would on Play. We put both stores' rating math side by side in [how your app's star rating is actually calculated](/blog/how-is-your-app-star-rating-calculated) — the per-storefront structure is why your territories drift apart.

Google's own reasoning when it rolled this out names your exact problem. Per the Android Developers Blog announcement: a bug that only hit one country used to drag an app's rating down *everywhere*, and a great tablet experience got buried under a flood of phone ratings. Country- and device-specific ratings were the fix. Now a Japanese user sees ratings from Japanese users, a tablet user sees ratings from tablet users, and a localized failure stays contained to the market it happened in.

Play's rating is also recency-weighted (since Google I/O 2019), so unlike Apple, each market's number self-heals as fresh local reviews arrive, so a rough stretch in one country doesn't linger the way it can on iOS. If you manage both stores, the practical differences are laid out in [App Store vs Google Play review replies](/blog/app-store-vs-google-play-review-replies).

Because each storefront pools only its own reviews, a market with a concentrated problem takes a concentrated hit. If checkout fails for one country's payment method, every affected user there rates one or two stars into that storefront's pool alone — your global blend barely twitches, but the local number craters, and that's what prospective installers in that country see. Localization works the same way: ship an English-only interface into a Spanish- or Japanese-speaking market and the reviews complaining about it stack up in that market's storefront, suppressing installs in a self-reinforcing loop. The number isn't lying; it's telling you exactly where your product or localization is failing, market by market. The fix has to be market-specific too, which is where replies come in.

Replying makes the reviewer meaningfully more likely to revise their rating upward, and on a per-market rating, every converted rating lands exactly where it helps. A study of 4.5 million reviews by Hassan et al. found users were roughly six times more likely to raise their rating after a developer replied (4.4% versus 0.7% with no reply). McIlroy et al. (IEEE, 2017) found that when a rating changed after a response, 38.7% of those changes were increases, and Google's I/O 2019 guidance cited an average lift of +0.7 stars. On a localized rating, those upward revisions accrue to the exact storefront you're trying to lift.

The catch is language. A reply in English to a reviewer who wrote in German or Portuguese reads as a form letter and rarely earns the re-rate, and it's the German storefront's number you needed to move. Neither store auto-translates your reply for you (we cover what the store does and doesn't translate in [does the App Store translate reviews](/blog/does-the-app-store-translate-reviews)), so [answering in each reviewer's own language](/blog/reply-to-app-reviews-in-any-language) is on you. Google Play caps the reply at a hard 350 characters; Apple publishes no official limit (community testing suggests a few thousand characters), so keep it tight either way. Here's a two-star in a German storefront, answered in German so it actually converts:

That reply names the local bug and the version that fixes it, in the language the reviewer used, and it lands in the German storefront's pool — precisely the number dragging installs in Germany. One review is easy. Every reviewable review, fast, across a dozen storefronts and as many languages during a release week, is where teams fall behind. That's the gap [ReplyArgus](/features) closes: it watches your App Store and Google Play reviews across every market in one inbox, drafts a grounded on-brand reply for each in the reviewer's own language (100+ supported, both directions), sized to each store's limit, and lets you approve in a click or opt into rule-based auto-publish for clean cases.

Before you can fix a market, you have to see it. Both consoles break the number down by territory — most developers just never filter it.

There's no one rating to fix — there's a US number, a German number, a Brazilian number, and on Play a phone and a tablet number under each. Once you read the per-market numbers your users actually see instead of the blended average, the low ones tell you exactly where your product, your localization, or your last release let people down. The repair is local too: answer the reviews dragging each storefront, in that market's language. [Start free with ReplyArgus](/signup), no card, and Argus drafts your first reply in minutes — so no market's number stays broken while you're staring at the global one.