iOS SDK
iOS review prompt for SKStoreReviewController and requestReview
PromptSurge for iOS is a Swift package that shows a short, branded pre-prompt and then calls StoreKit's own review request when the user confirms. Two calls in your code; the copy, theme, header image and languages come from the server.
Free plan · iOS 14+ · Swift Package Manager
1 · Your pre-prompt
A quick favor
We worked hard on offline sync. A short review helps other people discover the app.
2 · The native rating sheet
App Store or Google Play
Apple's or Google's own sheet, shown unchanged
What the iOS SDK does for you
StoreKit's own review sheet
On confirm the SDK asks StoreKit for its review sheet with your window scene: current SDK versions call AppStore.requestReview(in:) on iOS 16 and later and SKStoreReviewController.requestReview(in:) before that. iOS decides whether the sheet appears, up to three times a year per device; the SDK never draws stars or collects a rating itself.
UIKit and SwiftUI
Pass any presenting view controller; from SwiftUI, hand it your root view controller. The dialog is a programmatic UIKit card that respects the safe area and scrolls long copy.
Every eligibility check built in
Opt-out, a 90-day cooldown per device, the 10% control group, the 50-device warm-up and your plan's monthly cap are checked before anything appears. When the pre-prompt is held back for the warm-up, the control group or a spent cap, the native request still fires, so the moment is not lost.
No ATT prompt, privacy manifest included
The only identifier is a salted SHA-256 hash of identifierForVendor and your bundle ID; there is no IDFA and no App Tracking Transparency prompt. PrivacyInfo.xcprivacy ships in the package, and the README gives you the App Privacy answers.
Shown without waiting
Call prefetch() at launch and the copy is cached on the device, so requestReview(in:) can show the dialog without a network round-trip.
The integration
Add the package in Xcode (File > Add Package Dependencies, then paste the URL below and pick the PromptSurge product). Initialize once, then call requestReview(in:) at your moment. The full steps, including Package.swift, are in the docs.
Package URL
https://github.com/PromptSurge-SDK/sdk-iosApp entry (SwiftUI)
import SwiftUI
import PromptSurge
@main
struct YourApp: App {
init() {
PromptSurge.initialize(apiKey: "ps_live_your_key_here")
PromptSurge.prefetch() // warms the cache in the background
}
var body: some Scene {
WindowGroup { ContentView() }
}
}At your moment (UIKit)
import PromptSurge
class CheckoutViewController: UIViewController {
private func onPurchaseSuccess() {
PromptSurge.requestReview(in: self)
}
}While integrating, PromptSurge.setLogLevel(.info) prints one line per decision, including the warm-up that keeps a new app on the native sheet for its first 50 devices.
What your user sees, in three steps
Same users, same moment. The difference is that they are asked first, in words about your app.
Trip saved
Available offline
requestReview()
Step 1
Your code picks the moment
Call requestReview() right after something went well, such as a saved trip or a finished level.
A quick favor
We put a lot of work into offline maps. A short review helps other travelers find this app.
Not nowSureStep 2
The pre-prompt asks in your words
A short message that names what your app does. Not now closes it and nothing else happens.
Rate this app
Tap a star to rate
A review that names the feature
Offline maps saved my trip. Works without a signal.
Step 3
The store's own rating sheet
A yes opens the store's sheet, unchanged. The message they just read gives them something specific to write about.
What it is built for
More reviews from the same users
People are asked at a moment you chose, with a reason to answer.
More written reviews
A message about a feature invites words, not only stars.
Your keywords in their words
Reviews that name what your app does tell the next visitor who it is for.
A signal the stores read
Apple and Google both say ratings and reviews play a part in how apps rank in search.
Your dashboard shows what changed for your app: written reviews per day, stars and keyword mentions, before the pre-prompt and with it.
Sources: Apple: App Store search · Google Play: app discovery and ranking
How it works
Add the SDK
Install the iOS, Android or Unity package and call initialize() once at launch. Then call requestReview() at a moment you choose, such as a finished level, a saved project or a completed order.
Make the pre-prompt yours
In the dashboard, write the title, message and two button labels, or let the built-in AI draft them from your own reviews. Pick a theme, add a header image on Startup and above, and accept: the copy is translated into 10 languages and reaches devices without an app update.
Compare against the control group
10% of devices never see the pre-prompt and get the native sheet directly at the same moments. The dashboard puts both groups side by side and records your store rating and rating count every day.
Measured against a control group, not assumed
Every app gets a control group. 10% of devices are assigned to it for their lifetime and never see the pre-prompt: when they reach the moment you chose, the native sheet fires directly, as it would without PromptSurge. A new app also starts with a warm-up of 50 devices on the native sheet alone, so a baseline exists before the first pre-prompt is shown.
The dashboard compares the two groups over every device that reached your review moment: how many saw the pre-prompt, how many tapped through, how many native sheets were requested. It holds back a verdict until each side has at least 50 devices.
One honest limit: Apple and Google never tell an app whether a user rated or what they wrote. So next to the funnel, PromptSurge records your store rating and rating count once a day and shows the change. It is a store total, not credited to any single prompt, and the dashboard says so.
10% control group
Assigned per device, for life. The native sheet fires directly at the same moments.
50-device warm-up
A new app starts on the native sheet alone, so the baseline comes first.
Daily store snapshot
Your average rating and rating count from each store, once a day, for apps with a store link.
Frequently asked questions
Which iOS versions are supported?
iOS 14 and later, built with Xcode 14 or later, installed with Swift Package Manager.
Is a pre-prompt allowed under App Store guideline 5.6.1?
Guideline 5.6.1 says to use Apple's API to ask for reviews and that Apple will disallow custom review prompts. PromptSurge never collects a rating itself: the stars and the review text always happen in Apple's own sheet, requested through StoreKit. The dialog before it is a short request that never asks how the user feels. Apple's StoreKit documentation also says not to call requestReview in response to a button tap, because the system may not show the sheet; with a pre-prompt, the user's tap on confirm is what requests it. In current SDK versions PromptSurge stops showing its pre-prompt on a device once it has requested Apple's sheet there three times in 365 days, Apple's own limit, so a yes is less likely to be met by nothing. How Apple reviews a particular app is Apple's decision, so keep any copy you write yourself a plain statement and consider describing the pre-prompt in your notes for App Review; the dashboard warns you when copy asks a question.
What the stores say, and a note for App Review →Will the native sheet always appear after a confirm?
No, iOS decides. StoreKit shows the request at most three times in 365 days per device, and to someone who has already rated only for a new version after a year. In current SDK versions the pre-prompt is no longer shown on a device once the SDK has requested the sheet there three times in 365 days. Neither the SDK nor any other code can see whether it appeared or whether the user rated.
Why does nothing appear on my test device?
Almost always the warm-up: a new app stays on the native sheet alone until 50 distinct devices have reached the review moment. Switch the warm-up off for the app in the dashboard while you test, and turn on setLogLevel(.info) to see each decision.
What do I declare in App Privacy?
Identifiers > Device ID and Usage Data > Product Interaction, both for analytics, not linked to identity and not used for tracking, in addition to whatever the rest of your app collects. The README has the table.
Related
Start free
The Indie plan is free forever: one app, 500 pre-prompt impressions a month, no credit card. Custom header images start with Startup at €39 per app per month. Prices in EUR, VAT included.
Two calls in your iOS app, the rest in the dashboard
Free plan, no credit card. Create an app, copy its API key and ship.
Create your free account →Already have an account? Log in