PromptSurge

Set up PromptSurge with an AI assistant

You sign up and copy one key. Claude, ChatGPT, Gemini or Grok does the code. This page has the prompt to paste and the guide your assistant reads.

You do

  • Create the account and the app
  • Copy the API key
  • Pick the message in the console
  • Approve where the review request goes

Your assistant does

  • Adds the SDK to the project
  • Initializes it at app start
  • Finds a good moment and adds the one call
  • Tells you which log lines prove it works
1

Your part: about five minutes

  1. Create a free account. No credit card.
  2. Press Create app, paste your App Store or Google Play link if the app is live, and copy the API key. It starts with ps_live_ and is shown once.
  3. Open Pre-prompt in the app’s menu, pick a message for your app category and press Go live. It ships in ten languages.

An assistant cannot do these for you: the account is yours, and the key is shown only to the person who creates the app.

2

Hand it over: paste this prompt

Replace the platform in the first line, paste it into your assistant, and give it the key when it asks.

Integrate the PromptSurge SDK into this <Android, iOS or Unity> project.

1. Read https://promptsurge.me/llms-full.txt first and follow it exactly. If you cannot open web pages, tell me and I will paste the file.
2. Install the SDK version that file names. Do not guess a newer one.
3. Initialize it once at app start with my API key. I will give you the key; keep it out of source control the way this project already handles secrets.
4. Find ONE place where the user has just finished something successfully (a completed level, a saved document, a finished workout) and call requestReview there. Show me the candidates you found and why you picked that one before you change the code.
5. Do not call it at app launch, do not put it behind a "Rate us" button, and do not add any dialog of your own before it. PromptSurge shows its own message, and the cooldowns are built in.
6. Turn the SDK log level to info for debug builds only, build the project, and tell me exactly which log lines I should see when I reach that moment on a device.
7. Tell me what I still have to do myself in the PromptSurge console.

The guide the prompt points to is one plain text file: promptsurge.me/llms-full.txt. If your assistant cannot open web pages, open that file yourself, copy all of it, and paste it into the chat after the prompt.

3

With your assistant

Claude

Working in your project: Claude Code works inside your project folder. Open a terminal there, start it, and paste the prompt.

In a chat window: In the Claude app, paste the prompt and attach the file that starts your app. It answers with the changes to make.

ChatGPT

Working in your project: If you use Codex or another mode that can work in your repository, paste the prompt there.

In a chat window: In a normal chat, paste the prompt. If it cannot open the link, paste the text of the guide file after it.

Gemini

Working in your project: Gemini in Android Studio and the Gemini command line tool can read your project. Paste the prompt there.

In a chat window: In the Gemini app, paste the prompt. If it cannot open the link, paste the text of the guide file after it.

Grok

Working in your project: If your setup lets Grok work on your code, paste the prompt there.

In a chat window: In a chat, paste the prompt, then the text of the guide file, then the file that starts your app.

Whichever you use, the prompt makes it show you the moment it picked before it changes anything. Say yes only if that moment is right after the user finished something that went well.

4

Check the result

  • The project builds, and the assistant named the log lines to look for.
  • Run the app on a device and reach the moment. In the console, Events shows an initialize event within a minute or two.
  • Seeing no PromptSurge dialog on your test device is normal at first. The first 50 devices of an app go straight to the store’s rating sheet, which builds the baseline your dashboard compares against.
  • Before you submit the app, add the note for App Review from the docs.
5

Things to ask your assistant later

Look through this project and list three other moments where a user has just finished something successfully. For each one, say how often a typical user reaches it in their first week. Do not change any code.
Here are 50 of my app store reviews. List the five features people praise most, each as one or two words I can use as a keyword. Leave out anything negative.

The first helps you move the review request to a moment more people reach; your console’s App insights page shows how many do. The second gives you keywords for Keywords in the console, which the AI-written messages then name.

Messages, languages and the look are set by you in the console. There is no interface for an assistant to change them, so nothing your users see changes without your click.

Prefer to do it by hand: the integration docs have the same steps.