All posts
Guide · 3 Oct 2026 · 9 min read

How your Google Play rating is calculated (and how to raise it)

Google Play weights recent ratings more heavily than old ones, so a bad release can sink your stars fast and a good one can lift them. How the rating works, what research says about replying to reviews, and a recovery plan.

AASODrift team · Indie Android developers

Key takeaways

  • Since 2019 Google Play has shown a rating that gives more weight to recent ratings, not a simple lifetime average.
  • That cuts both ways: a buggy release can pull your stars down quickly, and fixing it can bring them back within weeks.
  • In a study of 4.5 million Google Play reviews, researchers found that replying to a review often had a positive effect on the user’s rating.
  • Use the In-App Review API at a natural high point, never behind a “Rate us” button, and never ask “Do you like the app?” first.

Your star rating sits right next to your app name in Google Play search results. It’s one of the few things a searcher sees before deciding whether to tap your listing, so it affects how many people install from every keyword you rank for.

Recent ratings count more

In 2019 Google changed how Play calculates the rating it shows. Instead of a lifetime average, the rating is recalculated to give more weight to your most recent ratings. Google’s stated reason was that developers wanted “a rating that reflects a more current version of your app, not what it was years ago”.

2019
Google Play switches to a recency-weighted rating
4.5M
reviews studied by Hassan et al. (2018)
126,686
developer responses in that study
2,328
top free apps analysed

What this means in practice:

  • A release with a crash or a confusing change can pull your rating down within days, because the angry ratings are recent.
  • Years of good ratings don’t protect you as much as they used to.
  • Fixing the problem and asking happy users to rate you can recover your rating far faster than under a lifetime average.

Does replying to reviews help?

There is good evidence that it does. Hassan, Tantithamthavorn, Bezemer and Hassan studied 4.5 million reviews and 126,686 developer responses across 2,328 top free Google Play apps. They found that responding to a review often has a positive effect on the rating that user gives the app. They also found the most common reasons developers reply are to thank users and to ask for more detail about a reported problem.

A reply works best when it is specific and shows something will happen:

Example · Replying to a 1-star crash report
Before

“Sorry for the inconvenience. Please contact support.”

After

“Thanks for flagging this, and sorry. We found a crash on Android 14 when opening the timer from a notification. Version 3.4.1 fixes it and is rolling out now. If it still happens after updating, reply here and we’ll look again.”

Why it works: Names the problem, confirms it is fixed, gives a version number and invites the user back. That is the reply that gets a rating updated.

Ask the right users at the right moment

Google’s In-App Review API lets people rate you without leaving your app. Google’s own guidance is clear about how to use it:

  • Trigger it after someone has used your app enough to give useful feedback, for example after finishing a workout, a level or their first budget.
  • Don’t ask any questions before or while showing it, including “Do you like the app?” or “Would you rate us 5 stars?”.
  • Don’t put it behind a button. Google enforces a quota on how often the dialog can appear, so a “Rate us” button may do nothing and feel broken.
  • Don’t prompt excessively.

A 30-day rating recovery plan

  1. Week 1: read your last 100 reviews. Group the complaints. Usually one or two problems cause most of the 1-star ratings.
  2. Week 1: check Android vitals for crash and ANR spikes around your latest release.
  3. Week 2: ship the fix. Mention it in your release notes in plain words.
  4. Week 2: reply to every recent negative review about that problem, telling people the fix is live.
  5. Weeks 2–4: add or move your In-App Review prompt to a moment of success, for all users.
  6. Week 4: compare your rating and your keyword rankings to where they were before the bad release.
Let AI read your reviews
ASODrift groups your latest reviews into themes, highlights the problems costing you stars and drafts replies you can edit and post.
See review insights
+Is the Google Play rating an average of all ratings?

No. Since 2019 Google Play shows a rating that gives more weight to recent ratings.

+Can I delete bad reviews on Google Play?

No. You can reply, and you can report reviews that break Google’s review policies, but you can’t remove genuine reviews.

+Can users change their rating after I reply?

Yes. Users can edit their rating at any time, and research on Google Play found that replies often lead to a better rating from that user.

+How often can I show the in-app review prompt?

Google enforces a quota and doesn’t guarantee the dialog will appear each time you call it. Trigger it at natural moments rather than from a button.

Sources

  1. Search Engine Land: New app rating formula headed to Google Play (2019)
  2. Hassan et al., “Studying the dialogue between users and developers of free apps in the Google Play Store”, Empirical Software Engineering (2018)
  3. Android Developers: Google Play In-App Review API

Specifications and figures are as published by Google and the listed sources at the time of writing; check Play Console for the latest.

Know where you rank. Every morning.

One app, five keywords, daily checks. Free, no card.

Start tracking
Free for 1 app · 5 keywords
No card needed
Start free