When to Ask for App Store Reviews: Mid-Onboarding, Right After the First Win (the 4.9-Star Timing)

The short answer: ask inside onboarding, seconds after the first win

When to ask for app store reviews has one answer that repeats across the tasu library: mid-onboarding, immediately after the user completes something small and feels good about it, before the paywall and before any friction. Don't wait for the user to earn the right through days of usage. A prompt placed on a felt emotion captures gratitude. A prompt placed a week later captures a considered product judgment, made after the user has seen a price.

The moment you're looking for is a completed micro-experience: a first to-do ticked off, a first guided session finished, a personalized result appearing on screen. Not a questionnaire. Not a loading bar with nothing behind it. The user has to have felt the product do something.

The apps holding 4.9 stars all ask at the same moment

Catzy asks right after the user's first 60-second to-do list completes, mascot still animating. The cat celebrated, the user did something small, the prompt lands on that. Catzy holds 4.9 stars across thousands of reviews at $35K MRR and 100K+ downloads.

Prayer Lock asks immediately after the user's first guided prayer, which completes inside the app in under 60 seconds. It holds 4.9 stars from 6.7K reviews at $21K MRR in 6 months, built by a solo founder. Liftoff puts the ask on its plan-building loading screen with the star rating displayed at the same time, at 4.7 stars and $500K per month on iOS. Oniri asks right after its personalized projection graph, which its teardown describes as the highest positive emotional state in the flow, before any friction.

Yazio is the one that names the strategy out loud. It asks mid-onboarding, before the paywall and before any friction, at 700K monthly installs. Its teardown calls that screen the highest-leverage move in the entire flow, and an ASO strategy rather than just a UX choice. George Lamb shipped the same mid-onboarding rating screen as part of Wrestle AI's build, which did $160K in 6 months with zero code.

Why the rating is an acquisition asset, not a vanity metric

Most of the people you ask will never pay you. They can still leave a review. Mau Baron, who built Prayer Lock to $25K per month solo, puts the rationale plainly: show the review modal right after the user completes your core feature, when they're at their most excited, because it's the most important thing you can do for your ASO and social proof. That review compounds over time and brings more organic downloads for free.

So the review prompt is the one screen in onboarding that monetizes your non-payers. At scale the rating average stops being a number in App Store Connect and starts being the thing that decides whether a search result becomes a tap. It's the same logic behind putting the ask right after the aha moment: the user's willingness to vouch for you peaks exactly once, and it peaks early.

The failure mode: ask before any product experience, harvest one-star reviews

Bend is the cautionary case, and it's a big app: 15M+ users, 100K monthly downloads, $1.1M monthly revenue. Its App Store review ask fires after a forced 22-screen questionnaire, before the paywall, and before the user has done a single stretch. The user is being asked to evaluate something they haven't experienced.

The emotion at that moment isn't gratitude. It's "I just want to see if this works." A documented user review captures it exactly: the app asks you to rate it "with no idea if the app is any good," because a forced questionnaire and a rate-the-app popup were the only things it let the user experience. Those reviews are written in frustration, they're one star, and they stay permanently visible to every organic searcher.

The fix is a pure position change. Move the ask to after the first real success moment. Don't rewrite the prompt, don't add a pre-prompt asking "are you enjoying the app?", just move it behind one completed thing. Worth being honest about the evidence weight here: Bend still holds 4.7 stars, so this isn't a controlled experiment, and nobody has published a clean A/B on ask placement. What the library shows is a consistent pattern, with the two highest-rated flows (Catzy and Prayer Lock, both 4.9) asking after a completed micro-experience.

Each trigger is scarce, so spend it only on a success moment

Both app stores cap how often you can trigger the native review dialog per user per year. That makes every trigger a limited resource, which changes the calculus. You don't get to sprinkle the prompt around and see what sticks.

The rule from Max, who runs a portfolio of about 40 apps at $36K per month, is the success-only rule: fire it after a win, never after an error, a paywall bounce, or any other friction point. It's an assertion rather than a dataset, but the logic is hard to argue with. A trigger spent on a moment of frustration doesn't just fail to earn a review. It buys you a bad one, or a dismissal that burns the trigger for the year.

The zero-cost second placement: rating and share at the top of settings

Feynman AI leads its settings page with "Rate us 5 stars" and "Share Feynman AI" at the top, reaching the self-selected users who bother to open settings. It's second-best to a peak-emotion ask, and Feynman AI only has it because its onboarding is a single account-creation screen with no success moment to attach a prompt to. But it costs nothing to add and it catches the engaged tail.

The absent case is what quantifies the stakes. Pillo has no review surface and no share prompt anywhere, on an app whose 570K downloads are driven mostly by organic discovery through strong ratings (4.76 across 17K reviews). Its teardown calls that a growth flywheel running at half speed. The rating is already doing the acquisition work. Nothing in the product asks for more of it.

How to place your review ask

• Find the first moment in your flow where the user completes something and feels it: a first entry logged, a first session finished, a personalized result revealed. That's your slot
• Put the native prompt there, inside onboarding, before the paywall. Catzy fires it seconds after a 60-second to-do list completes and holds 4.9 stars
• If your onboarding has no success moment yet, build one before you build the ask. A questionnaire is not a win, which is the whole Bend lesson
• Never fire it after an error, a paywall dismissal, or a failed action. Each trigger is capped per user per year, so a wasted one is gone
• Add "Rate us" and "Share" to the top of your settings page as well. Zero cost, catches the self-selected engaged users, and it's the only surface Pillo is missing at 570K downloads
• Check the ask sits inside the coverage checklist for the rest of the flow (see the six jobs of onboarding), so the review screen isn't crowding the permission ask or the paywall
• If your AI coding agent is building the flow, the tasu MCP is the conversion-expertise layer it calls while it builds, so it gets the sourced placement instead of a guess