Apple lets developers choose, when releasing a version, whether to reset the summary rating so it reflects only the new version. This can help after a major fix but removes accumulated social proof, so use it deliberately and only when the new version genuinely changes quality.
How the option works
When submitting a new version, developers can choose to reset the summary rating. The prior ratings remain associated with older versions but are not shown in the summary. Check current Apple documentation for details.
The choice is tied to a version release.
When it can make sense
If a major bug or redesign caused low ratings and the new version fixes the main issues, a reset may let the summary reflect improved quality. The product should be clearly better.
Avoid using it to hide persistent problems.
Risks and trade-offs
A reset can leave you with few ratings, which may reduce trust and conversion until new ratings accumulate. Prepare compliant prompts to gather ratings after success moments.
Consider that ratings volume influences credibility.
Plan and monitor
Before resetting, forecast how quickly you can collect new ratings and what conversion might do in the meantime. Monitor after release and be ready to respond to reviews.
Document the decision and results.
Common mistakes with iOS ratings reset
Resetting to escape a rating that reflects ongoing problems is the main mistake, since new reviews will reflect the same issues. Another is resetting without a plan to gather new ratings quickly. Ignoring conversion effects of a low rating count is a third.
Not documenting the decision leaves the team confused later.
IOS ratings reset: a worked example
After a redesign that caused bugs, an app fixes the main issues in a major release. The team estimates how many ratings it can collect in a month with compliant prompts and decides to reset.
It monitors conversion and reviews closely and replies to new feedback.
How to do it, step by step
- Confirm the fix is realMake sure the new version resolves the main causes.
- Estimate rebuilding timeForecast how many ratings you can collect in a month.
- Prepare compliant promptsSet triggers after success events.
- Monitor conversionWatch conversion after the reset.
- DocumentRecord the decision and results.
Before and after examples
Illustrative examples written for a generic app in this category, not client results. Swap in your own product, audience, and data.
Reset to hide old reviews
Reset after fixing the bugs that drove low ratings
Why it works: The product must be clearly better.
Hope for ratings
Prompt after the third completed task
Why it works: A plan rebuilds volume.
Never revisit
Check conversion weekly for the first month
Why it works: A low rating count can hurt trust.
Action plan
- Confirm the new version fixes the core issues
- Estimate time to rebuild rating volume
- Prepare compliant rating prompts
- Monitor conversion after reset
- Respond to new reviews
- Document the decision
Metrics to monitor
- Summary rating after reset
- Rating volume over time
- Conversion before and after
- Review sentiment
Record the baseline, release date, audience, markets, and external changes before interpreting movement. Rankings and conversion are useful signals, but a decision is stronger when activation, retention, and business value confirm that the page attracted the right users.
Frequently asked questions
Does a reset delete reviews?
Previous reviews remain tied to earlier versions, but the summary resets.
Is it always a good idea after a fix?
No; losing volume can hurt trust.
Can I reset any time?
It is tied to submitting a new version.
Keep reading
More in Ratings and Reviews
Browse all 13 Ratings and Reviews guides
