PromptSurge

Android SDK

Android in-app review with Google Play's In-App Review API

PromptSurge for Android is a Kotlin library that shows a short, branded pre-prompt and then launches Google Play's In-App Review flow when the user confirms. Two calls in your code; the copy, theme, header image and languages come from the server.

Free plan · minSdk 24 · JitPack

1 · Your pre-prompt

Your header image

A quick favor

We worked hard on offline sync. A short review helps other people discover the app.

Not nowLeave a review

2 · The native rating sheet

App Store or Google Play

Apple's or Google's own sheet, shown unchanged

Not now closes the dialog and shows nothing else.

What the Android SDK does for you

Play's own review card

On confirm the SDK runs ReviewManager's requestReviewFlow() and launchReviewFlow(). The card is Google's, shown as it is; the pre-prompt has already closed, and Play's own quota decides whether the card appears.

Fits any app theme

The dialog is Material 3. On a Material theme it inherits your look; on AppCompat, platform or custom game themes it falls back to its own bundled theme instead of crashing. Dashboard colours are applied on top.

Safe in production apps

minSdk 24, no runtime permissions, nothing added to your manifest, R8 rules shipped in the AAR. requestReview() does nothing if the activity is finishing, its state is already saved or the dialog is already up.

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 first. When the pre-prompt is held back for the warm-up, the control group or a spent cap, Play's review flow still launches, so the moment is not lost.

Data Safety answers included

The only identifier is SHA-256 of ANDROID_ID plus your package name, never the raw ID, and no advertising ID is used. The README lists exactly what to declare in the Play Data Safety form.

The integration

Add JitPack and one Gradle dependency (coordinates and the current version are in the docs), initialize in your Application, then call requestReview() at your moment.

Application.onCreate()

import com.promptsurge.sdk.PromptSurge

class MyApp : Application() {
    override fun onCreate() {
        super.onCreate()
        PromptSurge.initialize(this, "ps_live_your_key_here")
    }
}

At your moment

// In an Activity (AppCompatActivity works)
PromptSurge.requestReview(this)

// Or from a Fragment
PromptSurge.requestReview(requireActivity())

While integrating, PromptSurge.setLogLevel(PromptSurge.LogLevel.INFO) prints one line per decision. Play's card is quota-limited and often shows nothing on a debug build, so an invisible card there is normal.

View integration docs →

On the phone

What your user sees, in three steps

Same users, same moment. The difference is that they are asked first, in words about your app.

  1. 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.

  2. A quick favor

    We put a lot of work into offline maps. A short review helps other travelers find this app.

    Not nowSure

    Step 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.

  3. 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

  1. More reviews from the same users

    People are asked at a moment you chose, with a reason to answer.

  2. More written reviews

    A message about a feature invites words, not only stars.

  3. Your keywords in their words

    Reviews that name what your app does tell the next visitor who it is for.

  4. 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

  1. 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.

  2. 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.

  3. 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 Android versions are supported?

minSdk 24 (Android 7.0) and later, Kotlin 1.9 or later, distributed through JitPack. The dialog needs androidx.fragment, which appcompat already brings in.

How does the pre-prompt relate to Google Play's in-app review guidelines?

Google asks apps to show its review card unchanged, with nothing on top of it, and not to ask the user any questions before or while presenting it, naming opinion questions ('Do you like the app?') and predictive ones ('Would you rate this app 5 stars?'). PromptSurge never alters or overlays Play's card, its dialog has closed before the card opens, and its default and generated copy are statements that ask for a review, never a question. Google's guide also says apps should not offer a call-to-action button that triggers the review flow, because its quota may keep the card from appearing; a pre-prompt's confirm button is such a button, so weigh that guidance for your app. In current SDK versions PromptSurge skips its pre-prompt on a device within 30 days of its last request for Play's card, which lowers that risk but cannot remove it, because Google does not publish its quota. If you write your own copy, keep the title a statement like the example on this page; the dashboard warns you about any question.

What the stores say, and a note for App Review →

Does Not now use up Play's quota?

No. Not now launches no review flow at all. Only a confirm, or the native-only paths for the warm-up, the control group and a spent plan cap, call the In-App Review API.

Why does nothing appear on my test device?

Usually the warm-up: a new app stays on Play's card alone until 50 distinct devices have reached the review moment. Switch it off for the app in the dashboard while you test. Play's own card is also quota-limited and often stays hidden on debug builds.

What do I declare in Data Safety?

Device or other IDs, and App activity > App interactions: collected, not shared, for analytics, not linked to the user, in addition to whatever the rest of your app collects. The README explains each answer.

Two calls in your Android 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