The Growth Hack That Now Gets Apps Rejected: Onboarding Rate Prompts and Guideline 5.6.3

The Old Playbook

For a long time the logic was simple: show the Rate/Review prompt as high in the funnel as possible, before users hit bugs, paywalls, confusing flows, or any moment where the product stops matching their expectations. Catch them while the experience is still clean, and the rating tends to come back higher.

It worked because the math usually worked out. Some users got annoyed and left a one-star rating, but the common belief was that if they deleted the app shortly after, Apple would in some cases drop that rating from the public average. Meanwhile a steady stream of quick five-star ratings pulled the score up. Given how widely this pattern spread across mobile apps, the economics clearly held up for a lot of products — even when part of the audience disliked the experience.

The uncomfortable part is that the metric could improve while the actual experience got worse for some users.

What Changed

After the recent App Store Review Guidelines updates, more teams are reporting rejections for exactly this setup. Apple is treating some onboarding Rate/Review prompts as rating manipulation under Guideline 5.6.3, Discovery Fraud, which prohibits manipulating any element of the App Store customer experience — reviews included.

A move that used to look like a quick growth hack is becoming a real risk to review outcomes, release velocity, and reputation. And when a rejection lands on a routine update, it doesn't only cost you the rating tactic. It can hold up an unrelated release while you sort the flag out.

Where the Ask Actually Belongs

The natural place to ask for a rating sits deeper in the product, at a moment when the user has a reason to feel positive. A few signals worth building around:

• The user has completed a key flow and seen a real result.
• They've come back across several sessions.
• They've hit a milestone or a clear win inside the product.
• They've just had a support issue resolved well.
• They've taken an action that usually correlates with satisfaction — sharing, upgrading, or inviting someone.

Ask at the moment a user has clearly gotten enough value to want to rate you, and that's the rating that sticks — and the one Apple won't flag.

Testing This Without Shipping a New Build

Most teams already agree that timing matters. The harder problem is finding the right moment for your specific product, segment by segment, without burning a release cycle on every guess.

This is one of the use cases Amply is built for: testing triggers, segments, and placements for Rate/Review prompts remotely, without shipping a new app version. You can move the prompt to a post-value moment, target it to the segments most likely to leave a positive rating, and keep adjusting as you learn — all without waiting on review for each iteration.

The Takeaway

The onboarding rate prompt isn't dead — it's just in the wrong place. The same tactic that used to inflate a score is now the one Apple reads as manipulation, and the cost of getting it wrong has shifted from a few annoyed users to a blocked release.

If you're rethinking where your rating prompt fires, that's exactly the kind of decision Amply is designed to help you test and tune — move it to the moment a user has already gotten value, and let the higher, more durable ratings follow.