Short answer
Cursor is an AI code editor, so a Cursor-built app is whatever stack you chose: usually a web app, sometimes React Native or Swift. Web apps reach the App Store fastest in a native shell such as WebViewGold with added native features; native projects are edited in Cursor but built, signed and archived with Xcode. A two-week plan covers hardening, the iOS build, TestFlight and review.
On this page
What "a Cursor app" means for iOS
Cursor is an editor built on the VS Code foundation with strong AI features: agent mode, multi-file edits, project rules. It does not host apps or generate a platform-specific format. So the question is not "how do I export from Cursor" but "what did we build in Cursor, and how does that stack get onto an iPhone?"
Three typical answers:
- A web app (React, Next.js, Vue, Laravel, Rails). Most Cursor projects fall here.
- A cross-platform mobile app (React Native with Expo, Flutter, Capacitor).
- A native Swift app, written in Cursor alongside Xcode.
Cursor is excellent for the code. Xcode remains mandatory for the iOS build: signing, archiving, asset catalogs, capabilities and simulator debugging all live there. Teams that work well treat Cursor and Xcode as two windows on the same repository, not as competitors.
Cursor and Xcode side by side
A setup that works for Swift and for native parts of cross-platform apps:
- Open the repository root in Cursor for writing code, refactoring and tests.
- Keep the
.xcodeprojor.xcworkspaceopen in Xcode for building, running on the simulator and managing signing. - Let Cursor's agent run
xcodebuildfrom the integrated terminal so it can read compile errors directly. - Never let the agent edit the project file's signing section; change signing only in Xcode.
Add a project rule (Cursor supports rule files in the repository) that captures your iOS conventions: minimum iOS version, the architecture pattern you use, how networking is structured, which files are off limits. Rules cut down the number of times the agent invents a new pattern for every screen.
The two-week plan for a Cursor-built web app
Most teams reading this have a web app. Here is a realistic plan to get it into the App Store.
| Days | Focus | Output |
|---|---|---|
| 1 to 2 | Mobile hardening in Cursor | Every screen usable at phone width, touch targets of at least 44 pt, no hover-only actions |
| 3 | Production deployment | Stable custom domain, monitoring, error page for outages |
| 4 to 5 | iOS shell | WebViewGold project configured and building |
| 6 to 7 | Native features | Push notifications, Sign in with Apple or email login, camera if relevant |
| 8 | Account and privacy | In-app account deletion, privacy policy, data inventory |
| 9 to 10 | TestFlight | Internal and external testers, bug fixes |
| 11 to 12 | Store listing | Screenshots, description, keywords, review notes, demo account |
| 13 to 14 | Submission and buffer | Submit, respond to questions, fix if rejected |
Developer account setup is not in the plan; if your company does not have one yet, start that first, because the D-U-N-S verification can take days. See developer accounts for companies.
Days 4 and 5: the shell
WebViewGold delivers an Xcode template where you insert your URL, set the bundle ID, icon and launch screen, and toggle native features such as push notifications, offline handling and native sharing. It is a one-time purchase. Open the project in Xcode, build it, and you have an iOS app loading your Cursor-built web app.
You can also open the WebViewGold project in Cursor and ask the agent to explain or adjust parts of it, but make changes deliberately: it is native code with its own lifecycle, and a small edit in the wrong place can break push registration or file uploads.
If Days 4 to 7 sound like the wrong use of your team's time, WeSetupYourWebViewApp sets up the WebViewGold app for you and hands over full source code in about 72 hours.
Days 6 and 7: native features that matter to reviewers
Pick features your users will actually notice, because Apple's Guideline 4.2 rejects apps that offer nothing beyond the website:
- Push notifications for events in your product, with a backend endpoint you build in Cursor that stores tokens and sends messages.
- Native share sheet for exporting reports, links or files.
- Biometric unlock for apps holding personal or business data.
- Camera and document capture feeding into existing upload flows.
Guideline 4.2 for web-based apps explains in detail what tends to pass.
If you built React Native or Flutter in Cursor
Skip the shell. Your work is the release pipeline: production configuration, app icons and splash assets, permission strings, release builds and signing in Xcode or a cloud build service, then TestFlight. The most common failure is a release build that crashes while the debug build ran fine, usually because of a missing environment variable or a native dependency not linked. Test release builds on a real device early.
Quality checks before you submit
Cursor speeds up writing code; it does not check whether the result feels right on an iPhone. Before submission:
- Walk through every flow on a small iPhone with large text enabled.
- Check that keyboards do not cover input fields.
- Verify that links to external sites open in an in-app browser and users can return.
- Remove debug pages, test routes and placeholder text.
A short audit from UXreviewer.io finds friction that the team no longer sees after weeks of building. For thoughts on review discipline for agent-written code in general, see Cursor workshop for developer teams.
Submission
Create the app in App Store Connect, upload the archive from Xcode, attach it to a version, complete privacy labels and age rating, and submit with clear review notes. appsubmitter.io does submissions, listings and rejection handling for you, in your own developer account, and can set up CI/CD so later releases do not depend on one person's Mac.
FAQ
Can Cursor build and sign an iOS app?
Cursor edits code and can run terminal commands such as xcodebuild, but signing, capabilities and archiving rely on Xcode and your Apple developer account on macOS. Use Cursor for code and Xcode for the build.
Do I need to learn Swift to publish a Cursor web app on iOS?
No. With a native shell such as WebViewGold, configuration happens in a prepared Xcode project. Basic Xcode familiarity helps; deeper Swift knowledge is only needed for custom native features.
How long does App Review take for a first app?
Often a day or two, sometimes longer, and rejections add rounds. Plan a buffer of several days before any announced launch date.
Can Cursor's agent fix App Review rejections?
It can help implement fixes, such as adding account deletion or changing permission texts. Interpreting the rejection and replying to Apple is still a human task.