Can Cursor Publish to the App Store and Google Play?
Cursor is an editor, not a publisher. It writes a real app you own, then you submit it like any developer.
TL;DR
No, Cursor does not publish to the App Store or Google Play; it is a local code editor, not a hosted platform with a publish button. It writes a real app you own, then you submit it yourself, usually with Expo EAS for React Native or Xcode for native iOS, plus the Play Console for Android. You need an Apple Developer account ($99/yr) and a Google Play account ($25). Start screens from a free VP0 design to build faster.
No, Cursor does not publish your app to the Apple App Store or Google Play, because Cursor is a code editor, not a hosted build-and-publish platform. There is no publish button. What Cursor does is write a real app on your machine, and you submit it yourself the way any developer would. That is not a downside so much as a different model, and once you know the path it is straightforward. Here is how publishing actually works from a Cursor project.
Cursor writes the app; you ship it
Cursor edits code locally, so the app lives in your repo and you own it, the point in can Cursor build a full React Native app from scratch. But it does not host or submit anything, unlike a cloud builder. So the question is not whether Cursor can publish, it cannot, but what the publishing pipeline looks like for the code it produces. That depends on whether you built a React Native app or a native iOS app.
The React Native path: Expo EAS
If Cursor built a React Native and Expo app, the cleanest route to both stores is Expo’s submit service, known as EAS. It builds the native binaries in the cloud and submits them to App Store Connect and the Google Play Console, so you do not need a Mac for the iOS build. You run a couple of commands from your project, and EAS handles the heavy lifting. This is the same pipeline a hand-coded Expo app uses.
The native iOS path: Xcode
If Cursor wrote native Swift, you submit through Xcode and App Store Connect on a Mac, the standard Apple flow, and a guided version is in the Cursor to TestFlight tutorial. For Android native, you build an AAB and upload it to the Play Console. Either way, Cursor got you the code; the submission tools are Apple’s and Google’s.
What you need
| Item | Detail |
|---|---|
| Apple Developer account | $99/year, for the App Store |
| Google Play account | $25 one-time, for Google Play |
| Build tool | Expo EAS (React Native) or Xcode (native) |
| Cursor | Free Hobby or $20/mo Pro, to write the app |
| Store assets | Icon, screenshots, description |
The accounts are the same ones any app needs, listed at the Apple Developer Program and the Google Play Console. Cursor’s cost is just the editor.
Cursor vs a hosted builder for publishing
The tradeoff is control versus convenience. A hosted tool like Replit hands you a URL but not a native store app, the situation in can Replit Agent publish to the App Store and Google Play. Cursor gives you a real, owned codebase and the standard, fully native publishing path, which is more steps but no lock-in, the principle in AI app builder no vendor lock-in. If you want the most control over a genuinely native app, Cursor plus EAS or Xcode is the route.
Build faster so you reach publishing sooner
The slow part before publishing is building the screens, and Cursor is fastest when it has a target. Open a finished screen on VP0, the free AI-readable iOS and React Native design library, and have Cursor implement that exact layout, ideally with a rules file like best .cursorrules file for pure Swift mobile. One precise build beats several rewrites, so you reach the submission step sooner and with model usage to spare.
Key takeaways
- Cursor does not publish to the stores; it is an editor, so you submit the app yourself.
- For React Native, submit through Expo EAS, which builds and submits without a Mac.
- For native iOS, submit through Xcode and App Store Connect; for Android, upload an AAB to the Play Console.
- You need an Apple Developer account ($99/yr) and a Google Play account ($25), plus your build tool.
- Build screens from a free VP0 design so you reach the publishing step faster.
Compare: see can Cursor build a full React Native app from scratch and Cursor to TestFlight tutorial.
Frequently asked questions
Can Cursor publish to the App Store and Google Play?
No, not directly. Cursor is a local code editor with no publish button; it writes a real app you own, and you submit it yourself. For a React Native app, use Expo EAS to build and submit to both stores. For native iOS, use Xcode and App Store Connect, and for Android upload an AAB to the Play Console. You need the developer accounts either way.
How do I publish an app I built in Cursor?
It depends on what you built. For React Native and Expo, run Expo EAS to build the binaries in the cloud and submit to App Store Connect and the Google Play Console, no Mac required. For native Swift, submit through Xcode on a Mac. Cursor produced the code; these are the standard build and submit tools you use on top.
Do I need a Mac to publish a Cursor app?
Not necessarily. If you built a React Native app, Expo EAS builds the iOS binary in the cloud, so you can submit without a Mac. If you wrote native Swift, you need a Mac with Xcode for the iOS submission. Android does not require a Mac in either case; you upload an AAB to the Google Play Console.
How much does it cost to publish a Cursor app?
The developer accounts cost $99 a year for Apple and a one-time $25 for Google Play. Cursor itself is free on the Hobby plan or $20 a month for Pro, and Expo EAS has its own free tier and paid plans for builds. So the baseline to list an app is the two store accounts plus whatever build tier you need.
Is Cursor or a hosted builder better for publishing?
A hosted builder is easier for a web app but often does not produce a native store binary. Cursor gives you a real, owned codebase and the standard fully native publishing path through EAS or Xcode, which is more steps but no lock-in. If you want maximum control over a genuinely native app, Cursor plus EAS or Xcode is the stronger route.
Questions from the VP0 Vibe Coding community
Can Cursor publish to the App Store and Google Play?
No, not directly. Cursor is a local code editor with no publish button; it writes a real app you own, and you submit it yourself. For a React Native app, use Expo EAS to build and submit to both stores. For native iOS, use Xcode and App Store Connect, and for Android upload an AAB to the Play Console. You need the developer accounts either way.
How do I publish an app I built in Cursor?
It depends on what you built. For React Native and Expo, run Expo EAS to build the binaries in the cloud and submit to App Store Connect and the Google Play Console, no Mac required. For native Swift, submit through Xcode on a Mac. Cursor produced the code; these are the standard build and submit tools you use on top.
Do I need a Mac to publish a Cursor app?
Not necessarily. If you built a React Native app, Expo EAS builds the iOS binary in the cloud, so you can submit without a Mac. If you wrote native Swift, you need a Mac with Xcode for the iOS submission. Android does not require a Mac in either case; you upload an AAB to the Google Play Console.
How much does it cost to publish a Cursor app?
The developer accounts cost $99 a year for Apple and a one-time $25 for Google Play. Cursor itself is free on the Hobby plan or $20 a month for Pro, and Expo EAS has its own free tier and paid plans for builds. So the baseline to list an app is the two store accounts plus whatever build tier you need.
Is Cursor or a hosted builder better for publishing?
A hosted builder is easier for a web app but often does not produce a native store binary. Cursor gives you a real, owned codebase and the standard fully native publishing path through EAS or Xcode, which is more steps but no lock-in. If you want maximum control over a genuinely native app, Cursor plus EAS or Xcode is the stronger route.
Part of the AI App Builders: Pricing, Code Ownership & Shipping hub. Browse all VP0 topics →
Keep reading
Can Rork Publish to the App Store and Google Play?
Yes. Rork publishes real native apps to both stores, automating builds and submission through Expo's EAS. Here is how it works and the free fallback if it fails.
Can Draftbit Publish to the App Store and Google Play?
Yes. Draftbit publishes real native React Native apps to both stores, either managed for you or self-published on Pro. Here is how it works and what you need.
Can FlutterFlow Publish to the App Store and Google Play?
Yes. FlutterFlow's one-click deploy publishes a real native app to both stores, no Xcode or terminal needed. Here are the steps and the first-release Android gotcha.
Can Thunkable Publish to the App Store and Google Play?
Yes. Thunkable publishes native apps directly to both stores from the platform, on a paid plan. The catch: no code export, so you are locked in.
Can Replit Agent Publish to the App Store or Google Play?
Not directly. Replit Agent builds and hosts web apps, not native app-store binaries. Here is what it does publish, and three real paths to get to the stores.
Can Lovable Publish to the App Store and Google Play?
Not directly. Lovable builds web apps, so reaching the stores means exporting the code and wrapping it with Capacitor. Here is the real path and its limits.