Short answer
A Cursor-built app reaches Google Play either as a web app in a native wrapper such as WebViewGold or as a native or cross-platform Android project. Cursor handles the code, Android Studio and Gradle handle builds. The parts teams most often get wrong are permanent identities (package name, keys, fingerprints), testing on realistic devices and the store listing itself.
On this page
Cursor writes the code, Gradle builds the app
Cursor is an AI code editor, not an app platform. A "Cursor app" is whatever you built: most often a web application, sometimes a React Native, Flutter or Kotlin project. For Google Play the end product is always the same: a signed Android App Bundle uploaded to the Play Console.
A workable split for Android:
- Cursor for writing and refactoring code, generating tests and running Gradle tasks in the terminal.
- Android Studio for the emulator, layout inspector, profiler, logcat and managing SDK versions.
Kotlin and Gradle files edit fine in Cursor, but Android Studio's tooling for inspecting a running app is hard to replace. Use both on the same repository and add a project rule in Cursor that lists your Android conventions, build commands and files the agent must not touch.
If your Cursor project is a web app, the Android project is a wrapper. WebViewGold gives you an Android Studio template: set your URL, package name, icon, splash and native features (push notifications, offline handling, file downloads, native share), build and sign. One-time payment, and the source stays yours. WeSetupYourWebViewApp sets it up for you in about 72 hours with full source code if you would rather not.
Identities you set once and live with
Some decisions on Android are effectively permanent. Get them right before the first upload.
Package name. The applicationId identifies your app on Google Play forever. Use a reverse domain you own, such as com.example.inspections. Changing it later means publishing a new app and losing installs and reviews.
Upload key and keystore. You sign bundles with an upload key. Store the keystore file and passwords in a password manager or secrets vault with at least two people able to access them. Never commit them to the repository, and never paste them into an AI chat.
Play App Signing. Enrol when you create the app. Google then holds the app signing key, and a lost upload key can be reset through support instead of ending your app.
Certificate fingerprints. Services that verify your app (Google sign-in, Firebase, Maps, Digital Asset Links for App Links or Trusted Web Activities) need the SHA fingerprint of the key that signs the installed app. For Play-distributed builds that is the Play App Signing key, shown in the Play Console, not your local debug key. Mismatched fingerprints are behind many "works in debug, fails from Play" bugs.
Version codes. Each upload needs a higher versionCode. Automate it in your build so nobody guesses.
Testing on the devices your users actually own
Developers test on one good phone. Android users run thousands of device models. A practical minimum matrix:
| Device class | Why it matters | What to look for |
|---|---|---|
| Older mid-range phone, several Android versions back | Slower CPU, older WebView or system behaviour | Load time, scroll smoothness, crashes |
| Current mid-range phone | Your typical user | Overall feel, keyboard behaviour |
| Small screen or large font setting | Accessibility and layout limits | Cut-off text, overlapping buttons |
| Tablet or foldable | Play shows your app on these too | Stretched layouts, orientation changes |
| Gesture navigation and three-button navigation | Both are common | Back behaviour on every screen |
Combine your own devices with the Play Console's pre-launch report, which runs the app on a set of test devices and reports crashes and accessibility issues.
Web app specifics inside the wrapper
If Cursor built your product as a web app, a few checks are specific to Android WebViews:
- Back navigation must step through your app's history and close only from the start screen.
- File inputs must open the file chooser and camera; test uploading a photo taken in the moment.
- Downloads must save or open the file, not show a blank page.
- Google sign-in must run outside the embedded web view, because Google blocks OAuth there; open it in a Custom Tab and return via a deep link.
- Offline state should be a designed screen, not the default error page.
A maintained wrapper such as WebViewGold handles file choosers, downloads and offline screens for you; your job is to confirm they work with your app's flows.
Our guide to converting a web app into iOS and Android apps explains the broader options if you are still deciding.
The store listing is part of the product
Cursor cannot write your store presence for you in a way that converts, but it can help draft. What you need:
- App name and short description that state the job the app does.
- Full description written for people, not keyword stuffing.
- A high-resolution icon and a feature graphic in Google's required dimensions.
- Phone screenshots showing real screens with real-looking data, plus tablet screenshots if you support tablets.
- Privacy policy URL, Data safety answers and content rating.
- Account deletion link if users can create accounts.
Read App Store Optimization for AI-built apps for listing tactics that apply to Google Play too. Before you finalise screenshots, an independent audit by UXreviewer.io often surfaces small UX issues that are easy to fix and visible in every screenshot.
Policies that catch Cursor-built apps
- Minimum functionality. A pure website copy is weak; add push, offline handling, file features or other native value.
- Testing requirement. New personal accounts need a closed test with at least 12 testers for 14 continuous days before production. Organization accounts are exempt.
- Target API level. Google raises it yearly; plan updates.
- Permissions. Remove anything the agent added that you do not use.
- Payments. Digital goods consumed in the app generally use Google Play Billing.
For an overview of frequent issues, see Google Play rejection reasons for converted web apps.
Submit and iterate
Upload to internal testing, fix what you find, move to closed testing, then roll out to production in stages. appsubmitter.io handles listings, submission, CI/CD and rejection responses in your own Play Console if you want the store side off your plate.
FAQ
Can I build an Android app entirely in Cursor?
You can write all the code in Cursor and run Gradle builds from its terminal. Android Studio remains useful for emulators, profiling and debugging, so most teams use both.
What happens if I lose my Android signing key?
With Play App Signing, you lose only the upload key, which Google can reset after verification. Without it, you may be unable to update the app. Enrol from the start.
Why does Google sign-in fail only in the Play version of my app?
Usually because the registered SHA fingerprint is from your debug or upload key, while Play-installed builds are signed with the Play App Signing key. Register that fingerprint too.
Do I need tablet screenshots?
Only if you want the listing to look complete on tablets, which is where Google shows your app as well. Make sure the layout works there first.