Why Recent Reviews Weigh More: Freshness in the Store Algorithms

Recent reviews weigh more because Google Play's displayed rating has been *recency-weighted* since Google I/O 2019 — your newest ratings count for more than the ones you earned years ago. The practical consequence catches a lot of teams off guard: a fresh review you rescue from two stars to four moves the visible number more than an old rating ever could, because the algorithm is literally biased toward what people feel about your app *right now*. That's the whole reason speed matters when you reply.

This isn't a growth-hack theory. It's a documented change to how the Play Store computes the number under your app icon, and it reshapes which reviews are worth your attention first. Below: why Google made freshness a weight, how much a recent review actually pulls, and the one move that turns the mechanic into rating points: converting a recent complaint before the reviewer moves on.

Until August 2019, Google Play used a lifetime cumulative average — every rating an app had ever received counted equally. A five-star from launch day pulled exactly as hard as one from last week, which meant a rough start could shackle an app to a low number for years even after the team fixed everything. At Google I/O 2019, Google announced the fix: the rating shown on the Play Store now gives more weight to your most recent ratings, and that recalculated number rolled out that summer.

The logic is user-facing, not developer-facing. Google wants the star rating to tell a prospective installer whether the app is good *today*, not whether it was good in 2021. An app that shipped buggy, got hammered with one-stars, then genuinely turned things around should see its rating climb as newer, happier ratings accumulate and the old ones fade in influence. The reverse is equally true: coast on an old reputation while quality slips, and recent one-stars drag the number down faster than the cumulative model ever allowed. Google later layered personalization on top too, tailoring the average by country and device form factor, but every version of the calculation shares that same bias toward recent, relevant ratings.

Here's the honest limit: Google has never published the exact decay curve — no half-life, no coefficient, no table of how a rating's weight tapers as it ages. Anyone quoting you a precise multiplier is guessing. What Google confirmed is the *direction*: newer ratings count for more, older ones for less, on a continuous slide rather than a hard cutoff.

You don't need the exact formula to act on it. Picture your rating as a rolling average that keeps its eye on the last several weeks: a wave of new five-stars this month outweighs the same count from three years ago, and a cluster of recent one-stars stings more than an equal cluster buried in your history. So the reviews with the most unrealized pull are the recent ones: the ratings from this week and last are what the algorithm is actively weighting, and therefore what you can still move. An angry review from eighteen months ago is nearly frozen influence; an angry review from Tuesday is a live lever.

Apple is the counterexample that proves the point. Its App Store summary rating is a cumulative average with no publicly documented recency weighting, which is why a rough iOS launch haunts an app far longer than an Android one. Even there, freshness still works three ways — new ratings add volume, they sit at the *top* of your listing where prospects read before installing, and they're the raw material for a per-version rating reset. We break down both formulas side by side in [how your app's star rating is actually calculated](/blog/how-is-your-app-star-rating-calculated).

Put the two facts together and a priority order falls out. Fresh reviews weigh more, and a reply makes an unhappy user meaningfully more likely to revise upward — 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), and McIlroy et al. (IEEE, 2017) found that when a rating changed after a response, 38.7% of those changes were increases. So the single best-paying action you have is to catch a *recent* complaint and give the reviewer a real reason to re-rate.

A two-star you convert to four this week isn't just a deleted complaint — it's a fresh high rating minted into the exact slot the algorithm weights most, while the same fix a year late would arrive as a low-weight rating on a formula that's already stopped caring. That delta is the entire point of recency weighting, and it's why the reviews at the top of your queue are worth more than the backlog.

That reply runs 270 characters (comfortably under Google Play's hard 350-character cap), names the exact bug and the exact fix, and hands the reviewer a concrete reason to come back and bump the rating. On Play that fresh rating counts extra; on Apple it nudges the cumulative average up and pushes the angry review off the top of your listing. The mechanics of why this works, and how often, are laid out in [does replying to app reviews raise your rating](/blog/does-replying-to-app-reviews-raise-your-rating).

Recency weighting rewards fresh ratings, but a reviewer only mints one if your reply reaches them while they still care. That window is short. A reviewer is most likely to update their rating while the problem, and your fix, are still front of mind; a reply that lands a week after they've moved on rarely gets read, let alone acted on. Srisopha et al. (EASE 2021), studying what makes a developer response actually succeed, ranked timeliness among the top predictors of a review-response working, ahead of politeness. Fast isn't a nicety here; it's mechanically load-bearing.

So the operational target is unglamorous: answer every reviewable review, in the reviewer's own language, fast, across both stores — and prioritize the freshest ones, because those are the ratings the algorithm is still weighting. Keeping that pace is where teams fall behind, especially across several apps and a busy release week. It's the gap [ReplyArgus](/features) is built to close: it watches your App Store and Google Play reviews in one inbox, drafts an on-brand reply for each (grounded in your past approved replies and an auto-ingested knowledge base from your store listing, sized to each store's limits), and lets you approve in a click or opt into rule-based auto-publish for the clean cases. The freshest complaint gets a grounded answer in minutes instead of sitting untouched while its weight is still high. The broader case for staying fast is in [why review velocity matters](/blog/review-velocity).

The number under your app icon isn't a fixed grade — on Google Play it's a rolling read weighted toward the newest voices, and on Apple it's a cumulative average where fresh reviews still sit up top where prospects read. Either way the movable points live in the same place: the recent reviews you can still reach. Catch the freshest complaint, answer it fast and grounded, and you mint a high rating exactly where the algorithm rewards it. [Start free with ReplyArgus](/signup), no card, and Argus drafts your first reply in minutes, in the reviewer's own language and sized for each store, so the reviews that move your rating never sit long enough to go stale.