Rating Prompts in Onboarding: Why App Review Rejects Them
An app that asks for a star rating before the user has done anything meaningful is now a review risk. Apple has begun rejecting apps that place a rating prompt inside onboarding, citing App Review Guideline 5.6.3 on manipulation of the App Store customer experience. The fix is not to hide the prompt better. It is to move the ask to a moment the user has actually earned.
What changed and why it matters
The guideline itself is not new. What changed is how Apple applies it. Prompting for a review early in onboarding used to be a common growth tactic, and some apps collected large numbers of five-star ratings before users had used the product in any meaningful way. Apple now treats that pattern as manipulation under Guideline 5.6.3, which prohibits manipulating elements of the App Store customer experience such as charts, search, reviews, or referrals.
The practical consequence: new versions of an app that still prompt during onboarding can be rejected during review. It is not clear whether Apple will also audit apps already live in the App Store. There is a second, quieter risk. Apple may already have been discounting ratings submitted shortly after install by comparing install time with rating time, which would erase any App Store optimization benefit the prompt was meant to create.
Treat the two risks separately. A rejection is a submission-level policy outcome. Rating filtering is a data-quality outcome. You can avoid the first by removing the prompt, and still lose the second if your replacement trigger fires before the user has a real opinion.
Where the prompt should live instead
Remove every rating and review request from the onboarding flow. Then decide what counts as a meaningful moment in your product. Apple's Human Interface Guidelines describe the right target as natural and happy moments: after a user completes something, achieves something, or has a genuine reason to form an opinion.
That definition is easy to state and hard to instrument. A first launch is not a meaningful moment. Neither is finishing onboarding without using the core feature. The useful question is: what event in your app would make a user able to say something specific about the experience?
A practical trigger checklist:
- The user has completed the core action at least once, not merely opened the app.
- The completion produced a visible result the user can judge, such as a saved item, a finished session, or a resolved task.
- The moment is positive or neutral, not immediately after an error, paywall, or permission denial.
- The prompt is not shown during onboarding, account creation, or the first session.
- The trigger is tracked as an event so you can review when prompts actually appear.
A worked example using the source's own idea: suppose your app helps users complete a short daily task. Opening the app is not a trigger. Completing the task and seeing the result is. If you log that completion event, you can hold the rating request until the event fires, rather than tying it to a screen in the onboarding sequence. The same engagement-tracking approach is described for building a happiness engine that prompts when a positive rating is most likely. The source notes that the same guide applies to Google Play, although Google was not yet limiting this pattern at the time of writing.
Bottom line
Stop asking for reviews during onboarding. Apple can reject your app for it, and the ratings may not have counted anyway. Replace the onboarding prompt with an engagement-based trigger that fires after the user has done something worth reviewing. Track the engagement event, keep the prompt out of the first-run flow, and review the trigger against the checklist above before your next submission.
Frequently asked questions
Is Guideline 5.6.3 new?
No. The guideline is not new. What changed is that Apple has started applying it to rating prompts placed inside onboarding, which it had not previously done in this way.
Will Apple remove apps that are already live?
It is not clear whether Apple will review apps already in the App Store for this pattern. Apps that still prompt during onboarding can be rejected when a new version is submitted.
Does this apply to Google Play?
The engagement-based approach also applies to Google Play. At the time of writing, Google was not yet limiting rating prompts in the same way.
What is a happiness engine?
It is a system that tracks user engagement and triggers a review request when the user is most likely to have a positive experience to report. The goal is to ask after a meaningful, positive moment rather than at a fixed point in onboarding.