Docs · Help
Using FirstPass
Everything you need, in plain words. A check takes about ten minutes, needs no sign-up, and nothing is uploaded.
Start here
Google Play tells you about problems one at a time, with days of waiting between each rejection. FirstPass shows you all the likely ones at once, so you can fix them together and send your app for review one time.
- Open Check my app and answer a few plain questions about your app.
- Optionally, let the AI tool that built your app read the project and report back (the build check).
- See every issue, sorted by how serious it is, each with a prompt you can paste into your AI tool.
- Fix them, press Send for review in Google Play Console, and leave the app alone while it is reviewed.
The five steps
Each step is a short page. If you don’t know an answer, pick “I’m not sure”, or skip the optional ones. Your answers are saved as you go, and you can go back at any time.
| Step | What it asks | Why Google cares |
|---|---|---|
| 1. Your app | Name, what it does, how it was built, the kind of app, your developer account type, and whether it is already live. | Some kinds of app (money, health, VPN, government, children) have extra rules, and new personal accounts must run a test first. |
| 2. People and accounts | Whether people sign in, a login for Google's reviewers, deleting an account, children, posts other people see, AI-written content. | Reviewers must be able to get into your app, and accounts need a way to be deleted. |
| 3. Money | What people can pay for, how they pay, subscriptions, and ads. | What you sell decides which payment system Google allows. |
| 4. Privacy | What the app uses on the phone, which tools are built in, and your privacy policy link. | Google compares what the app touches with what you tell it. Mismatches are a common reason for rejection. |
| 5. Your store page | Your name and descriptions, the pictures you have, and which App content forms you filled in. | Store pages have length limits, banned wording and picture sizes. |
The build check
Some rules are about the code, and the packages inside your app often add permissions or collect data without telling you. Google holds you responsible for all of it. Instead of asking you to upload anything, FirstPass hands you one prompt for the AI tool that wrote your app.
- On the last step, press Copy the build check prompt.
- Paste it into the AI tool that built your app (Claude, Cursor, or any other) with your project open. It reads the project and changes nothing.
- It replies with a block of text that starts with
{. Paste the whole reply into the box on the page. FirstPass confirms what it found, for example “7 permissions and 5 packages found, targeting Android API 34”.
I need a factual report about this mobile app project so I can check it against Google Play's rules. Do not change any files.
Look through the project (for Flutter: pubspec.yaml, android/app/build.gradle or build.gradle.kts, android/app/src/main/AndroidManifest.xml; for Expo / React Native: app.json or app.config.*, package.json, android/ if it exists, and any config plugins). Include permissions that packages add by themselves, not only the ones written in my own manifest.
Reply with ONLY this JSON, filled in. Use null when you cannot tell.
{
"framework": "flutter | expo | react-native | native | other",
"frameworkVersion": "",
"expoSdk": null,
"packageName": "",
"targetSdk": null,
"minSdk": null,
"versionCode": null,
"permissions": ["android.permission.EXAMPLE"],
"sdks": ["every third-party package that talks to a server, e.g. firebase_analytics"],
"paymentSdks": ["stripe, paypal, razorpay, in_app_purchase, react-native-iap, revenuecat ..."],
"adSdks": ["google_mobile_ads ..."],
"billingLibraryVersion": null,
"hasNativeLibraries": null,
"supports16KbPageSize": null,
"debuggable": null,
"usesCleartextTraffic": null,
"isMostlyWebView": null,
"hasAccountDeletion": null,
"hasPrivacyPolicyLink": null,
"notes": "anything else Google Play review might care about, in one or two sentences"
}What the report contains
- The framework and its version, and the app’s package name.
- The target and minimum Android API level, and the version code.
- Every permission, including the ones added by packages.
- Third-party packages that talk to a server, and which of them handle payments or ads.
- The Play Billing library version, native libraries and whether they support 16 KB memory pages.
- Whether it is a debug build, allows unencrypted connections, or is mostly a website in a frame.
- Whether the app has account deletion and a privacy policy link.
You can skip the build check and add it later. The checks that read the code, such as the target API level and the payment library version, only run when you paste the report.
Reading your results
The headline says how many things would get your app rejected, or that it is ready to send for review. Below it, every finding sits in one of three groups:
| Group | What it means |
|---|---|
| Will get you rejected | Fix these before you submit. Google would stop the review on any one of them. |
| Likely to be flagged | Worth fixing now. They often cause a rejection, or a note from the reviewer. |
| Worth doing | Good practice, or a rule that is coming soon. |
Open any finding to see:
- what the problem is, in plain words;
- What to do, step by step, either in Play Console or in your code;
- a prompt to copy into your AI coding tool, written so it does the work and explains it simply;
- the name Google uses for the rule in its emails, with a link to Google’s own page;
- an I’ve fixed this box, so you can keep track.
Copy one prompt that fixes all the code issues joins the code fixes into a single prompt. A tag such as “From 1 February 2027” means the rule is announced but not enforced yet.
Link checks
If you give a privacy policy or account deletion link, FirstPass opens it the way a reviewer would. It reports links that are not https, are PDFs, look like an editable shared document, don’t load, or show almost no text without scripts.
Stripe or Google Play?
This is the rule that surprises people most, and it depends on what you sell, not on how your app is built.
| You sell | Examples | How to take payment |
|---|---|---|
| Things used inside the app | Premium features, subscriptions, coins or credits, removing ads, online courses | Google Play Billing. Putting a card form such as Stripe here gets an app rejected. |
| Real-world things | Products shipped to people, food, rides, bookings, repairs, bills | Not Google Play Billing. Stripe and similar services are fine, and Google's billing isn't allowed for these. |
- An app can have both. Use Google Play for the in-app items and keep Stripe for the physical goods and services.
- A button or link that sends people to your website to pay for something used in the app is also against the rule.
- Subscriptions must show the price, how often it charges, and that it renews until cancelled, on the subscribe screen, without tapping anything.
- A few regions have programmes that allow other payment options for digital goods. They need enrolment and don’t apply everywhere, so check Google’s Payments policy before relying on one.
Before you submit
- Upload the fixed build to every track you have used, not only production. Old test versions can block a new one.
- Fixes are not sent by themselves. Open Publishing overview in Play Console and press Send for review.
- Then leave the app alone. A new change while it is in review can restart the wait, which is usually 3 to 7 days.
- Play Console runs its own quick checks about 15 minutes after you save. Read them before sending.
- If Google still rejects it, fix and resubmit. You get one appeal per rejection, so keep it for when Google is clearly wrong.
New personal developer accounts (opened after November 2023) also need 12 testers for 14 days in a closed test before the app can go public. FirstPass flags this when it applies to you.
Store page studio
The studio makes everything your Google Play page shows, at the sizes and lengths Google accepts. What you write there is saved in this browser and used by the check.
| Tool | What it does | Limits it enforces |
|---|---|---|
| Words | Drafts the app name, short description and full description from your own words, then checks them. | 30, 80 and 4,000 characters. Flags promotional words, emoji, ALL CAPS, repeated punctuation, other brands and keyword stuffing. |
| Feature graphic | The banner at the top of your page. Pick colours, add your icon, upload a picture or make a free AI one. | Exactly 1024 × 500, no transparency. Free AI pictures carry a small mark in one corner. |
| Screenshots | Refits your real phone screenshots to 1080 × 1920, with an optional caption of up to 60 characters. | Up to 8. Each side 320 to 3,840 pixels, and the long side no more than twice the short side. |
| Icon | Turns your picture into the icon Google wants and shows how Google Play will round it. | 512 × 512 PNG under 1,024 KB. Upload a full square with no rounded corners or shadow. |
Drafting the words with AI uses Google’s Gemini free tier. Read the draft through and keep only claims that are true of your app today.
Your data
Your answers and build report stay in your browser, saved on your own device. There is no account, and your answers are never stored on a FirstPass server. The only thing kept on the server is the optional beta tester sign-up. Start over on the results page clears them.
These are the only times something leaves your browser, and only what the feature needs:
| When | What is sent | To whom |
|---|---|---|
| The link check runs | The privacy policy or deletion link you typed, and your app name. | FirstPass, which then opens the link. |
| You press Draft my store page | App name, your one-sentence description, features and kind of app. | FirstPass, which asks Google's Gemini for a draft. |
| You press Make picture | The few words you typed to describe the background. | FirstPass, which asks the Pollinations image service. |
| You join the beta testers | Anonymous: a one-way code for your device, and the time. With your name: also the name you typed, which may be shown on the front page. No IP address is kept. | FirstPass, in a private store. You can remove yourself afterwards with the Remove me button. |
| You send feedback | Your message, optional rating and email, the page you were on, plus your IP address, device and browser. | The FirstPass team, by email. |
Free-tier AI services may use what they receive to improve their products, so don’t put anything confidential in those boxes.
Questions and answers
Does FirstPass guarantee my app will be approved?
No. It catches the common problems before Google does, and tells you why each one matters. Google’s reviewers decide, and Google’s rules change.
Is it free?
Yes, it is free while it is in beta.
Does it work for iPhone apps?
Not yet. It checks Android apps for Google Play. Some early testers have asked for iOS, so if you would use it, tell us.
I picked “I’m not sure” and got a long list. Is that normal?
Yes. When FirstPass can’t tell, it shows the check so you can confirm. Run the build check to answer many of the technical ones for you.
I disagree with a finding.
Open it and use Google’s own page, linked in the finding, to confirm the rule. Policies change, so if FirstPass is out of date, tell us which one.
Do I need to run the build check?
It is optional, but it finds things the questions can’t: packages that quietly add permissions, an old target API level, an unsupported payment library, or a debug build.
My results disappeared.
Answers live in this browser. A different browser, a private window, or cleared site data starts fresh. Use the same browser to carry on.
How do I reach a person?
Use the feedback form, or write to support@nxcsol.com.
Something missing or wrong?
These docs follow the app as it works today. If a step doesn’t match what you see, tell us.
Send feedback