Improving an app's reputation starts with the experience causing the reviews. Connect feedback to versions, devices and reproducible problems, then fix the product and communicate accurately. A rating campaign cannot substitute for resolving crashes, confusing charges or a broken core task.
01
Turn reviews into a diagnostic backlog
Group feedback by app version, operating system, language and issue where the information is available. Distinguish usability problems, defects, billing questions and policy concerns. For a hypothetical booking app, failed confirmations may be a reproducible bug while unclear cancellation terms need better product communication. Check support records and technical evidence without exposing individual account data in the public review thread.
02
Ship improvements and explain their scope
Prioritize fixes by user impact and risk, then test the affected workflow. Use release notes to describe what changed accurately. Apple recommends informing relevant reviewers when an update addresses their issue; Google Play provides tools to analyze ratings and reviews. Keep support contact details accessible and direct billing or store-specific problems to the appropriate route rather than pretending the developer controls every transaction.
- Record the issue, affected version, reproduction evidence and product owner.
- Update privacy and permission explanations when behavior or data use changes.
- Reply respectfully with a concrete next step and no personal information.
03
Evaluate recovery over successive releases
Review recurrence, stability and support outcomes alongside ratings. A new version does not automatically erase written feedback. Apple states that resetting a summary rating does not reset written reviews, so treat such options carefully and avoid presenting them as complaint removal. Invite authentic feedback through permitted mechanisms without rewards for favorable ratings, and use remaining criticism to identify work that is still unfinished.
Frequently asked questions
Should we answer old reviews after a fix?
A relevant, concise update can help when the issue has actually been addressed. State the version or change accurately and avoid claiming every user's problem is resolved.
Can developers remove any unfavorable store review?
No. Use reporting for genuine violations under the store's rules. Valid negative feedback belongs in product improvement and support work, not an automatic deletion campaign.
Continue with your next step
Related guides on this topic
Sources and policies
Check the current policy before submitting a request.
You do not have to figure out the next step alone.
Share the URLs and explain your concern. We will review the context and explain which options are worth assessing.
Request a confidential reviewOr call (307) 429-2531Educational information, not legal advice. Outcomes depend on the facts and decisions made by third parties.