A ratings strategy that holds up
How to earn better app ratings without breaking store rules: when to ask, how system prompt limits work on both stores, why gating and incentives fail, and how to fix root causes and handle review bombing.

On this page
A ratings strategy that holds up asks the right users at the right moment through the official system prompts, never gates or rewards ratings, and fixes the problems that low ratings point to. That combination tends to lift both your average and your rating velocity, which helps conversion and keeps you clear of the policy trouble that shortcuts invite. This guide covers the prompts, the timing, the rules and the monitoring.
Key takeaways
- Your rating shows next to your app in search and on the product page, so it shapes conversion before anyone reads a review.
- Use only the system prompts, StoreKit on iOS and the In-App Review API on Android, and accept that the system decides when they appear.
- Ask right after a success moment, never during a task, after an error or at a paywall.
- Never gate ratings by asking only happy users, and never reward ratings. Both break store rules.
- Read low ratings as a bug tracker, and track rating velocity as well as the average.
Why ratings matter
The ratings and reviews glossary entry explains how each store collects and displays them. Here is why they deserve a strategy.
Conversion. The star rating and rating count appear in search results and at the top of the product page. A low average is visible before your screenshots get a chance to make the case, and it can undo good creative work. Track it alongside your conversion rate.
Search and visibility. Both stores treat quality as a signal, although neither publishes how much ratings weigh in search. Google Play also says it may reduce the visibility of apps whose user-perceived crash or ANR rates exceed its Android vitals thresholds, and the same technical problems tend to show up in one-star reviews.
Featuring. Editorial teams on both stores look for high-quality apps. A weak rating will not help your case for a feature, and a feature brings a wave of new users who will rate you too.
How the system prompts work
App Store
On iOS you request a rating through StoreKit, and the system decides whether to show the prompt. As of November 2026 it appears at most 3 times per user in 365 days, people can turn rating requests off in their settings, and the request has no effect in apps distributed through TestFlight. Apple's guidelines require this API for review requests and do not allow custom review prompts. You never learn whether someone rated, so design the flow to work either way. For people who want to rate on their own initiative, you can also link to your App Store review page from a settings or about screen.
Google Play
On Android you use the In-App Review API. Google applies a time-bound quota per user and does not publish the exact number, which can change. The API does not tell your app whether the review card was shown or whether the user left a review, and Google advises against triggering it from a button, because a user who has hit the quota would tap and see nothing.
| App Store | Google Play | |
|---|---|---|
| Tool | StoreKit review request | In-App Review API |
| Frequency limit | Up to 3 prompts per user in 365 days | Time-bound quota, exact number not published |
| Who decides if it shows | The system | The system |
| Tells you if the user rated | No | No |
Because both systems ration prompts, every request should go to the moment when an honest positive rating is most likely. The in-app rating prompt glossary entry summarizes the mechanics.
Ask after a success moment
A success moment is the point where the user has just gotten what they came for. Good candidates:
- A workout logged, a lesson finished or a level completed.
- A file exported, a booking confirmed or a delivery received.
- A third active day in a week, which shows the app has become a habit.
Poor moments are the ones where the user is busy, frustrated or deciding whether to pay: onboarding, checkout, the paywall, a loading screen, or anything right after an error or crash.
A hypothetical rule set for a recipe app might look like this. Request a rating when someone saves their third recipe, only after they have opened the app on at least three separate days, never in a session that included an error, and no more than once a quarter from your side, whatever the system quota allows. Rules like these keep you well inside the limits and aim each request at a satisfied user.
Never gate or incentivize
Gating means asking "Do you enjoy the app?" first and sending only the yes answers to the rating prompt, while routing the no answers to a feedback form. Google's In-App Review guidelines say not to ask users opinion questions before or while showing the review card, and Apple requires its own API for rating requests. Gating also distorts your rating as a signal, so you lose the early warning that honest ratings give you.
Incentives are clearer still. Both stores prohibit offering rewards for ratings or reviews, whether coins, unlocks, discounts or entries into a draw, and they can remove the affected ratings or take action against the app.
What you can do is give every user an easy, always-available way to send feedback, in settings or help, that is not placed as a fork in front of the rating prompt. Unhappy users get heard, and your rating stays honest.
Resetting the App Store summary rating
When you release a new version, App Store Connect lets you reset your summary rating. Written reviews stay visible, but the star average starts over and only appears again once enough new ratings arrive. That gap can cost conversion, so use a reset rarely, and only when a version genuinely fixes the cause of most low ratings, such as a crash on a common device.
Google Play has no reset. It weights recent ratings more heavily, so improvements show up over time, and it shows ratings per country and device. A bad release on one device type can drag down the rating that people on that device see, even when your overall average looks fine.
Fix the root causes
Low ratings are the cheapest bug reports you will ever get. Turn them into a routine:
- Tag reviews by topic, such as crashes, login, performance, pricing, ads and missing features.
- Count tags by app version and country each week.
- Match spikes to releases, and send the top issue to the team that owns it.
- When a fix ships, reply to the reviewers who raised it, since people can update their review after you reply. The guide to replying to app reviews and the developer response entry cover tone and timing.
Monitor rating velocity
The lifetime average moves slowly, while recent ratings tell you what is happening now. Watch four numbers:
- New ratings per day.
- The average of new ratings over the last 7 and 30 days, next to the lifetime average.
- The share of one and two star ratings among new ratings.
- New ratings per 1,000 downloads, against your own history.
Here is a hypothetical example. Your app usually gets about 40 new ratings a day with a 30-day average of 4.5. Version 5.2 ships, and three days later you see 70 ratings a day with the 30-day average falling to 4.1. More ratings with lower scores usually means a new problem, not a change in prompting. Pause the rollout if you used a phased release or a staged rollout, read the new one-star reviews first, and fix before you prompt again.
Handling review bombing
Review bombing is a sudden wave of negative ratings driven by something outside the app experience, such as a news story, a policy decision or a coordinated campaign. Handle it in order:
- Confirm it. Look for a spike in one-star ratings with similar wording, unrelated to app behavior, starting at the same time.
- Reply calmly and once. Write one factual reply for the topic and use it consistently. Do not argue review by review.
- Report what breaks the rules. Both stores have policies against fake and off-topic reviews, and both give developers a way to report individual reviews.
- Do not answer with prompts or incentives. Prompting every user to outvote the wave burns your quota and can look like manipulation.
Be honest about the cause. If the wave follows a real change users dislike, such as a price rise or a removed feature, it is feedback, and the fix is product work.
How AppMetis helps
The reviews inbox in Analytics & ASO brings reviews from both stores into one place, with filters by rating, country, language and replied status, reply templates, topic tags and alerts for one and two star reviews, so a spike shows up the day it starts. Ratings, reviews and downloads sit in the same workspace, which makes the root cause routine above faster. For the market view, Market Intelligence keeps reviews for about 1.7M Android and 168K iOS apps, so you can find a competitor in app search and see how its users react to its releases.
Next steps
- Map two or three success moments in your app and move the rating request there.
- Remove any gate, reward or custom prompt from your rating flow.
- Set alerts for spikes in one and two star reviews.
- Run a monthly root cause review from tagged reviews, and reply when fixes ship.
