Check what changed in the product

A complete redesign or a repaired reliability problem may make historical scores less representative. Document the relevant fixes, affected users and retesting results. A new version number alone does not show that the underlying complaints are gone. Review support and crash evidence as well as beta opinions, especially when the release changes payment access, storage or sign-in.

Consider the cost of a small sample

A reset removes accumulated ratings from the summary calculation for the new baseline, leaving fewer signals for prospective users. Apple recommends using the feature sparingly. Estimate how long it may take to receive independent new ratings from real usage without assuming every install produces one. Do not combine the reset with a paid-review campaign to manufacture an immediate replacement sample.

Prepare support for the remaining written history

Older written reviews remain visible, so clear replies and release notes still matter. Explain verified improvements rather than saying criticism has been wiped away. Keep before-and-after records of the decision and monitor the new version separately. A reset is irreversible in its effect on the historical summary baseline; consult the current console instructions before making the production change.

USE THIS IN YOUR NEXT ROUND

Working example

Decision example: a notes app fixes an identified sync-loss bug and retests affected accounts on several devices. The owner weighs keeping the substantial historical rating count against resetting the summary for the repaired version. Record the reasoning and support plan. This article does not recommend a reset solely because the average is below a desired marketing threshold.

Your next steps

  • Document fixes and the evidence that they work.
  • Check the current console behavior before acting.
  • Plan for a smaller new rating sample.
  • Keep replies to historical written reviews accurate.

Official sources

Sources checked October 2, 2026. Review the current provider documentation before acting on requirements.

Turn the next test into something useful.

Publish a focused brief on RateMyApp. Credits fund approved private reports; public store reviews are voluntary and unrewarded.

List your app for feedback