Get More App Store Reviews Without Pressuring Users

ملخص

Pixel shares a practical guide to earning more app reviews by asking after success moments and using Apple’s and Google’s system review prompts. It explains platform limits, why developers should offer unhappy users a clear support channel, and why incentives or asking whether users like the app can backfire.

DEV Community

How to get more App Store reviews without asking unhappy users

This guide was originally published on the Hailbell blog. Short answer: Ask right after a success moment: the user finished something, hit a milestone, or, best of all, you just solved their problem in support. Use the system prompt (requestReview on iOS, the In-App Review API on Android), because Apple allows no custom review prompts and both platforms limit how often theirs appears. Give unhappy users an easy way to reach you instead, such as a support chat or a visible contact link, so a complaint reaches you before it becomes a one-star review. Don't ask "Do you like the app?" first, and never offer anything for a review. Most apps have very few reviews. This month, a developer who runs a directory of indie iOS apps counted 757 apps updated in the last 90 days; 562 had under 5 US ratings (r/iosdev). Their question is the one this page answers: what got you your first ratings? Hailbell is our product, built by an indie app developer who uses it in his own apps; one section near the end says where it helps. Everything before that needs no tools. What Apple and Google allow Checked November 9, 2026, on developer.apple.com (Review Guidelines last updated October 16, 2026), developer.android.com and Google Play's policy center. Apple Use the system API to ask for a review: guideline 5.6.1 says Apple will "disallow custom review prompts". For someone who hasn't rated your app on that device, the prompt shows at most three times in 365 days. The system decides whether it appears, you can't change its look or text, and people can turn it off entirely. SKStoreReviewController is deprecated since iOS 18; use AppStore.requestReview(in:) or SwiftUI's requestReview environment action. Google The In-App Review API shows a card over your app. Google doesn't publish the quota and says it can change without notice; calling it more than once in a short period (for example, under a month) might show nothing. You can't restyle the card or cover it. Both Paid, incentivized or fake reviews are banned. Apple's guidelines also name "filtered" feedback as manipulation, and Google says not to ask any question before the card. Breaking these can get the app removed. 1. Give unhappy users a way to reach you first This keeps your average up. Someone whose purchase didn't unlock will write a review if that's the only place to complain. Apple says this on its own ratings page: make your support contact easy to find in the app and on your product page, so you can fix bad experiences "that may otherwise lead to poor reviews". That means a "Contact support" row in Settings, a help link on error screens and in restore purchases, and a support URL on your listing that a person answers. This is for everyone, not a filter. Happy and unhappy users see the same support link and the same review prompt. You're just giving everyone a quicker way to get help than a one-star review. 2. Pick the moments to ask Apple's guidance is to ask "when users are most likely to feel satisfaction with your app, such as when they've completed an action, level, or task", and not on first launch, during onboarding or in the middle of a task. Google says to wait until someone has used the app enough to give useful feedback. Good moments look like this: A recipe app: after someone marks their third recipe as cooked, back on the recipe list. A budgeting app: after the user closes out their first full month and sees the summary. A language app: after a 7-day streak, on the lesson-complete screen. A photo editor: after a successful export, once the share sheet is dismissed. Any app with support: right after you fixed someone's problem and they said thanks. More on this in step 5. Bad moments: after a crash or error, after someone closed your paywall without buying, mid-typing, or on launch. Apple's sample code also waits until the task is done several times, asks once per app version at most, and pauses a few seconds on the done screen. 3. Call the system prompt at those moments On i...
Get More App Store Reviews Without Pressuring Users
Powered by Readybot.io

الأحدث من Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …

Why a Java HPA Got Stuck at 20 Kubernetes Pods

Pixel shares how a Spring Boot pricing service autoscaled to 20 Kubernetes pods and stayed there because the JVM retained committed heap memory after traffic …