On iOS, use Apple's system review request API at carefully chosen moments, let the system decide whether to show it, avoid triggering it from buttons or repeatedly, and never gate it by sentiment. Add a separate link to the App Store review page for users who choose to review.
Use the system API correctly
Apple provides an API to request a review, and the system limits how often the prompt appears. Calling it does not guarantee display. Follow Apple's current guidance in documentation.
Avoid calling it in response to a user tapping a rate button; use a separate link for that.
Choose thresholds
Require some usage before asking, such as multiple sessions or completed tasks, and require a recent success event. Avoid asking new users before they have seen value.
Track the last prompt date to avoid asking too often, even though the system limits it.
Handle versions and ratings reset choices
When you ship a major fix, you may choose whether to reset the summary rating for the version, which hides prior ratings for that version. Consider the trade-offs and keep honest.
Prompt more after fixes users asked for, when sentiment improves.
Test and monitor
Test the prompt behavior in debug and TestFlight, knowing that behavior differs. Monitor prompt-to-review rates and the effect on ratings after releases.
Respond to reviews that arise.
Common mistakes with iOS rating prompt
Calling the review API from a Rate us button is the typical implementation error, because the system may show nothing. Another mistake is asking too often or too early. Treating the API as a guarantee leads to wrong assumptions.
Teams also overlook that ratings reset decisions are tied to version releases.
IOS rating prompt: a worked example
A note app uses the system prompt after a user saves their tenth note, and adds a separate Rate on the App Store link in settings that opens the review page directly.
It tracks prompt-to-review rates and reviews recent ratings per version.
How to do it, step by step
- Call the system API at the right momentRequest a review after a success event.
- Do not tie it to a buttonUse a direct review link for the manual option.
- Set usage thresholdsRequire several sessions.
- Test in TestFlightKnow that behavior differs from production.
- MonitorTrack prompt-to-review rates and ratings.
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.
A Rate us button calls the review API
The button opens the App Store review page directly
Why it works: The API may show nothing.
Ask every launch
Ask after meaningful success, once the system allows it
Why it works: Over-asking annoys users.
None
A Rate on the App Store link in Settings
Why it works: It gives willing users a route.
Action plan
- Use the system review request
- Use a separate link for manual rating
- Set usage thresholds
- Trigger after success events
- Track last prompt date
- Monitor effect on ratings
Metrics to monitor
- Prompt-to-review rate
- Average rating
- Rating volume per version
- Review reply rate
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 calling the API always show the prompt?
No. The system decides, and frequency is limited.
Can I put the prompt behind a button?
Use a direct link to the review page for button-driven reviews.
Can I filter by sentiment?
No; sentiment gating of public prompts is not allowed.
Keep reading
More in Ratings and Reviews
Browse all 13 Ratings and Reviews guides
