Rating prompt (SKStoreReviewController)

• You can prompt for ratings up to three times in a 365-day period.
• Ask when users are most likely to feel satisfaction, such as after completing an action, level or task.
• Do not interrupt their activity.
• Make your support contact easy to find in the app and on the product page, so unhappy users can reach you instead of leaving a poor review.

The summary rating appears on the product page and in search results, and Apple states that ratings and reviews can influence ranking. A steady flow of ratings keeps the average current. Because the prompt is limited to three per year, each use counts.

For a hypothetical habit tracker, good moments are the seventh consecutive day of a streak, or the first time a user completes all habits in a day. Poor moments are app launch, a crash recovery or the middle of data entry.

Pick one or two placements, based on the points where users succeed, and keep them. Changing them often makes it hard to see what works.

• Asking on first launch, before the user has seen any value.
• Burning all three prompts in the first month.
• Using the prompt right after an error.
• Expecting a prompt to reset a bad average. If the average is hurt by an old problem, read ratings reset first.

Respond to the feedback that arrives with a developer response and read reviews for how written feedback is shown.