How often can an iOS app ask for a review?

The system review prompt (SKStoreReviewController / requestReview) shows at most three times per user per 365 days, and iOS decides whether a given request displays at all — users who disabled prompts never see one. You can't detect whether the prompt appeared or what the user tapped, so spend your three requests on moments of genuinely delivered value.

When is the best moment to ask for an app review?

Right after the app delivered the thing the user came for — the completed workout, the exported file, the found insight — and never during onboarding, after a crash, or on a timer. The user's emotional state at prompt time is what you're sampling; ask at the win and you sample satisfied users.

Do ratings affect App Store ranking and downloads?

Both. The star average displays in search results, so it directly moves tap-through — 4.8 next to a competitor's 4.1 wins taps before anyone reads a word. Rating quality and volume also feed search ranking as relevance signals. A slipping average is one of the quietest ways a funnel degrades with no metadata change at all.

FunnelHound / Guides / Getting more reviews

How to get more App Store reviews (without begging)

By Emin — indie iOS developer building FunnelHound · Published 15 Sep 2026

One rule does most of the work: ask at the win. The system prompt fires at most three times per user per year and iOS decides if it shows at all — so the only variable you control is the user's mood at ask time. Prompt after delivered value, never on a timer, and the stars take care of themselves.

How the prompt machinery actually works

requestReview is a request, not a command: iOS caps it at three displays per user per 365 days, suppresses it for users who turned prompts off, and tells you nothing about whether it appeared or what happened. Two consequences. First, your three shots are precious — a prompt burned on app-launch #2 is a shot not fired at the moment the user loved you. Second, since you can't measure the prompt directly, judge it by the outcome: rating velocity in App Store Connect after you moved the ask. There's also the write-review deep link (your App Store URL with ?action=write-review) for a "Leave a review" button in settings — always allowed, uncapped, and the right home for the ask outside the system prompt.

Timing: sample the happy moments

After the win: the exported report, the finished streak, the found leak. The app just proved itself; the ask is a natural "glad it helped".
Never during onboarding — the user hasn't received anything yet; you're asking a stranger to vouch for you.
Never after friction: a crash, a failed sync, a paywall dismissal. You'd be running an exit poll at the complaints desk.
Not every win either. Second or third win beats first — habit says more than novelty, and you stay under the cap for months.

Reply to reviews — it's marketing in public

Review replies (free, in App Store Connect) are read by far more people than the one reviewer: every prospect scrolling your reviews sees whether the developer shows up. A fixed bug plus a public "fixed in 2.1, thank you" turns a 2-star complaint into social proof of maintenance — and reviewers regularly revise ratings after a real fix. Prioritize replies to recent, visible, fixable complaints; skip debates. This is conversion work as much as support — the same page that shows your screenshots shows your replies.

Why the stars are a funnel input, not a vanity number

The rating average renders in search results, so it moves tap-through before your product page ever loads; rating volume and quality feed ranking itself. That makes a slipping average one of the sneakiest funnel leaks: downloads sag, metadata unchanged, and the cause is sitting in a column nobody watches. Watch rating trend next to TTR — when they dip together, you've found your diagnosis. And the unbeatable review strategy remains embarrassingly boring: fix crashes, ship the thing users asked for, then ask at the win.

Catch the funnel dip before the stars drag it down

FunnelHound shows tap-through and installs from App Store Connect — so a ratings problem surfaces as the leak it really is.

Get FunnelHound

Share this on X

Data notes: prompt limits and behavior per Apple's StoreKit documentation as of 2026. Incentivized reviews and review gating ("only happy users get the prompt" flows that filter before asking) violate App Store guidelines — the timing advice here shapes when you ask, not who gets to answer.