How to publish your Cursor app to Google Play (2026 guide)

So you used Cursor to build your first app. It works on your phone, it looks great, and you're ready to share it with the world. But then you hit the wall — how do you actually get it on Google Play?

Publishing an app isn't hard, but there are about 40 things you need to get right. Missing even one can get your app rejected. This guide walks you through every step.

What you need before you start

Before we dive in, here's what you'll need:

  • A Google Play Developer account — costs $25 one-time. Sign up at play.google.com/console. Usually approved within hours.
  • Your app on GitHub — if your code isn't on GitHub yet, you'll need to push it there.

That's it. You don't need a Mac, and you don't need Android Studio or any other developer tools.

Step 1: Check if your app is ready

Google Play has specific requirements — app icons, a privacy policy, proper configuration, and more. Most apps built with AI tools are missing several of these.

The fastest way to find out what's missing: use a free scanner like Shippabel's app checker. Paste your GitHub link and get a report in 30 seconds.

Common issues found in Cursor-built apps:

  • Missing app icon (Google Play needs a 512×512 PNG icon)
  • No privacy policy (required for every app on Google Play)
  • Default package name (needs to be unique, like com.yourname.yourapp)
  • No splash/loading screen
  • Hardcoded API keys in the code

Step 2: Fix the issues

Most issues are simple configuration changes. Here's what you need:

  • App name — max 30 characters, this is what shows under your icon
  • Package name — a unique ID like com.yourname.yourapp
  • Version code & version name — start with version code 1 and version name 1.0
  • App icon — a 512×512 PNG file
  • Splash screen — the loading screen people see when opening your app

Tools like Shippabel can auto-fix most of these with one click — they commit the changes directly to your GitHub repo.

Step 3: Write your store listing

Your store listing is what convinces people to download your app. On Google Play you need:

  • App name (30 chars max)
  • Short description (80 chars max)
  • Full description — up to 4000 characters
  • Screenshots — at least 2, framed in device mockups
  • Privacy policy — a hosted web page explaining data collection

Writing all this from scratch takes hours. AI tools can generate it in seconds — Shippabel uses Claude AI to write 3 variants of your store listing that you can pick from.

Step 4: Create screenshots

Google Play requires screenshots showing what your app looks like. The rules are simple:

  • At least 2 phone screenshots (up to 8)
  • Each side between 320px and 3840px
  • 16:9 or 9:16 aspect ratio

The trick: take raw screenshots on your phone, then frame them in device mockups with captions. This looks much more professional than raw screenshots.

Step 5: Build and submit

You can't submit the development version of your app — you need a production build. For Google Play, that's a signed Android App Bundle (AAB).

You don't need Android Studio or a computer to build it. Shippabel builds your app in the cloud and produces the signed AAB that Google Play needs.

After building, the AAB is uploaded to your app in Google Play Console. Then you wait for review — Google usually reviews new apps in a few hours to a few days.

The easy way

If all of this sounds like a lot, it is. That's exactly why tools like Shippabel exist — they handle every step automatically. Scan, fix, write your store page, create screenshots, build, and submit. From "it works on my phone" to "it's on Google Play."

Check your app for free →