Ratings vs Reviews: They're Not the Same Signal (and Why It Matters)

A rating is a silent star tap: someone picks one to five stars and leaves, no words. A review is that same tap *plus* written text. On both the App Store and Google Play they push your average score identically. A bare one-star tap hurts your number exactly as much as a one-star with a furious paragraph attached. But everything else diverges. You can only reply to the written ones. Only the written ones carry keywords that other shoppers read before they install. And on both stores, the silent taps quietly outnumber the essays by a wide margin.

That distinction sounds pedantic until it changes how you spend your time. Treat every star that moves your average as something you can answer, and you'll go hunting for a reply button that isn't there for most of your ratings. Here's where the two signals split, how each feeds your average and your ranking, and what you can actually do about each.

A rating is the minimum a user can leave: they tap a star count and submit. No text field, nothing to moderate, done in a second. A review is a superset: the same star selection *with* a written body, and usually a title on the App Store. So every review is also a rating; not every rating is a review.

This is why the two counts on your dashboard never match. Both stores show a total *ratings* count (every star tap, silent or not) and a smaller pile of written *reviews* underneath it. Most people who rate never type a word; a tap, and they're gone. That gap is the whole story: the thing that moves your average most (raw ratings volume) and the thing you can actually engage with (written reviews) are not the same population, and one is far larger than the other.

For the star average itself: no. A one-star is a one-star whether it arrived naked or with a thousand-word rant. The store doesn't weight a written review's stars more heavily than a silent tap's; the math treats them as equal votes. So if you're only worried about the number under your app icon, ratings and reviews are interchangeable inputs.

Where they *do* diverge is recency and volume. Because silent ratings are so much easier to leave, they dominate the flow, and both stores reward fresh flow. Google Play switched to a recency-weighted average at Google I/O 2019 (your newest ratings count for more than old ones), so a burst of recent star taps moves a Play number faster than an equal count from three years ago. Apple runs a cumulative lifetime average with an optional per-version reset. If you want the full mechanics of each formula, we broke them down in [how your app's star rating is actually calculated](/blog/how-is-your-app-star-rating-calculated). The takeaway here: ratings and reviews feed the *same* average by the *same* rule, but ratings feed it in far greater volume.

This is the split that catches teams off guard. A developer response has to attach to something and address something, and a silent star tap gives you neither: no text to answer, no title, often no way to even tell what went wrong. On the App Store, a rating without a review isn't a reviewable entry in App Store Connect at all; there's no thread to open. You respond to *reviews*, and a review by definition has words.

So the reply lever, the one that genuinely moves ratings upward, only works on the written slice of your feedback. And it's a lever with real evidence behind it. A study of over four 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. Google reported at I/O 2019 that responding developers see an average lift of about 0.7 stars. Every one of those effects requires a written review to reply to; the silent one-star taps are invisible to the whole mechanism.

The two stores handle that written-review reply flow a little differently (character limits, notifications, edit rules), which we compared side by side in [App Store vs Google Play review replies](/blog/app-store-vs-google-play-review-replies).

That reply only exists because the reviewer wrote something. Now picture the same unhappy user leaving a silent two-star tap instead: identical damage to your average, zero surface to reach them. Same signal to the algorithm, completely different options for you. The full case for the reply lever is in [does replying to app reviews raise your rating](/blog/does-replying-to-app-reviews-raise-your-rating).

Your star rating is a confirmed ranking factor on both stores: Apple's guidance lists ratings among search inputs, and Google Play's docs name ratings, review quantity, and review quality outright. That part is fed by *all* your ratings, silent taps included, and neither store publishes the weight. We laid out what's confirmed versus inferred in [how reviews affect App Store and Play ranking](/blog/how-reviews-affect-app-store-ranking).

Written reviews add one thing silent ratings can't: words. Prospective users read them while scrolling your listing, and a wall of specific, recent, well-answered reviews is social proof a bare star count never provides. Google also names *review quality* as a ranking input, and the keywords inside reviews are a plausible (if unquantified) relevance signal. So a rating moves the number; a review moves the number *and* the narrative.

The plan follows straight from the split. You can't chase silent ratings individually, so the game there is volume and freshness: prompt for ratings at genuine moments of delight and keep [review velocity](/blog/review-velocity) up so recent positive taps land where both stores reward them. For the written reviews you *can* touch, the goal is to answer every reviewable one fast, before the user has moved on and while your fix is still front of mind.

That second job is where it gets relentless by hand. Written reviews arrive across two stores, in every language your users speak, at all hours, and each store has its own reply limit: Google Play caps responses at a hard 350 characters, while Apple publishes no official limit (community testing suggests a few thousand characters). This is exactly the gap [ReplyArgus](/features) closes. It watches your App Store and Google Play reviews in one inbox, surfaces the ones you can actually reply to, and drafts a grounded response for each, in the reviewer's own language and already sized to each store's limit, so you approve in a click or opt into rule-based auto-publish for the clean cases.

So they're two signals wearing the same star icon. A rating is a vote: it moves your average and then it's gone. A review is a vote plus a conversation, the same effect on the number but with words you can answer and a real chance to turn a low score into a higher one. Chase volume on the silent taps, and pour your attention into the reviews you can actually reply to. [Start free with ReplyArgus](/signup), no card, and Argus drafts your first reply in minutes, in the reviewer's own language and already sized for each store, so no written review goes unanswered while the ratings quietly stack up.