Apps above 4.5 stars receive three times more installs than equivalent apps with lower ratings. Yet most indie developers handle ratings reactively: waiting for angry users to rate them while satisfied users never think to. Here is how to build a proactive rating strategy that works within Apple's guidelines.
Why ratings matter more than most ASO factors
Ratings affect App Store rankings in two ways. Directly: Apple's algorithm treats high ratings as a quality signal and uses them as a ranking input. Indirectly: ratings are visible in search results before a user even taps your listing. An app showing 4.8 stars gets clicked more, converts more, and therefore ranks higher: because conversion rate is itself a ranking signal.
The compounding effect is significant. More positive ratings → higher rating score → higher conversion rate → more installs → more installs provide more data for Apple to rank your app → higher rankings → more organic impressions. Breaking into this positive cycle is one of the highest-leverage things an indie developer can do in the first 90 days after launch.
The challenge: users do not leave ratings spontaneously unless they are upset. Satisfied users feel no urgency to open a review dialog. You have to ask: but how and when you ask determines whether you get a 5-star rating or a 1-star complaint.
The moment-of-success principle
The single most important rule in rating strategy: ask at the moment the user has just experienced value. Not on first launch. Not after a frustrating action. Not on a random timer. At the exact moment when the user has accomplished something meaningful with your app.
- Habit tracker: ask after a 7-day streak, not on app open.
- Fitness app: ask after a completed workout summary, not after a failed set.
- Language learning app: ask after passing a quiz or reaching a level milestone, not after a mistake.
- Finance app: ask after a successful import or savings goal, not after a failed bank connection.
- Reading app: ask after completing a reading plan day or devotional, not on first open.
The principle scales to any app. Find the moment where the user has just received value: the completed task, the goal hit, the problem solved. That is when they are most willing to give you 5 stars.
SKStoreReviewRequestAPI: use only this
Apple provides SKStoreReviewRequestAPI (or requestReview() in SwiftUI) to trigger the native App Store rating dialog. This is the only review request mechanism you should use.
The native dialog has three properties that custom prompts cannot match:
- Trust: Users recognize the official Apple dialog. Custom prompts look like dark patterns: "Rate our app!" screens that try to intercept unhappy users before they reach the App Store.
- Compliance: Apple's guidelines prohibit custom rating prompts that route users to the App Store only if they select a positive rating. Custom funnels that ask "are you happy?" and only show the App Store link on "yes" are a violation and can get your app rejected or removed.
- Conversion: The native dialog converts better because users trust it. A trusted dialog on a well-timed request gets 5-star responses. A custom dialog on a random timer gets dismissals and complaint reviews.
Implementation is one line in Swift:
// SwiftUI
import StoreKit
@Environment(\.requestReview) var requestReview
// Call at moment of success:
requestReview()Apple limits the dialog to appearing a maximum of 3 times per 365 days per user, regardless of how many times you call the API. This is a feature, not a limitation: it prevents over-prompting automatically.
Responding to negative reviews the right way
Users who receive a genuine, helpful response to a negative review frequently update their rating. This is one of the most actionable and underused rating improvement tactics available. A 2-star review with a thoughtful developer response that resolves the issue often becomes a 4-star review within a week.
What a good response looks like
"Hi [name], I'm sorry the import process failed. I've just pushed version 1.4 with a fix for the issue you described. Could you update and let me know if it is working? If not, email me and I will resolve it directly."
That response acknowledges the specific problem, explains what changed, gives a path forward, and sounds like a real person.
What a bad response looks like
"Thank you for your feedback. We are always working to improve. Please contact support for assistance."
That response reads like a template, moves the burden back to the user, and gives no sign that the developer understood the issue.
The rating reset option
App Store Connect allows you to reset your ratings on a new version update. This is useful when you have a bad historical rating baseline that does not reflect the current quality of your app: for example, if you shipped a major v2.0 that fixed the core issues causing 1-star and 2-star reviews.
Go to App Store Connect → Your App → App Store → App Store Version → Ratings Reset. This resets your displayed rating to "No ratings yet" for the new version. All previous reviews still exist but the aggregate star count restarts.
When to use it: Your current rating is below 3.5 stars. You have genuinely fixed the issues causing negative reviews. You have a plan to generate positive ratings quickly in the new version window (because "No ratings yet" also converts worse than 4.5 stars).
When not to use it: If you have a 4.2+ star rating with a significant volume of reviews: the history is an asset. Only reset if you are genuinely starting fresh from a bad baseline.