How to Vibe Code an iPhone App With Claude Code (2026)
A step-by-step 2026 guide to building an iPhone app with Claude Code: installing it, choosing between a Superapp project on Mac, a native Xcode project and an Expo project, writing CLAUDE.md, prompting, testing on your iPhone and publishing to the App Store.
Published · Last updated
Superapp, Xcode and Expo are the three ways to vibe code an iPhone app with Claude Code in 2026, and the right one depends on whether you have a Mac, whether you want native Swift and who you want doing the App Store work. This guide walks through all three, with the exact install commands, a CLAUDE.md you can copy, the prompts that work, what each route costs and how each one gets your app onto the App Store.
How to Vibe Code an iPhone App With Claude Code: The Short Answer
Superapp's Mac version is the fastest way to a published native app with Claude Code: Superapp generates the app as a native Swift and Xcode project in a normal folder on your Mac, you open that folder in Claude Code for detailed changes, and Superapp prepares and submits the App Store build. If you are a developer, the classic route is a native Xcode project, using Claude inside Xcode or Claude Code in the terminal, then archiving and uploading from Xcode yourself. If you do not have a Mac, use Expo: Claude Code writes a React Native app, you test it on your iPhone with Expo Go, and Expo's EAS service builds and submits it in the cloud. All three need a paid Claude plan, from $20 a month, and Apple's 99 USD a year Developer Program.
Quick answer: How do I build an iPhone app with Claude Code? Install Claude Code (included in paid Claude plans, from $20 a month), then pick a route. With Superapp for Mac, open the Superapp project folder in Claude Code; on Mac, "a Superapp project is a normal local folder containing a native Swift and Xcode project," and Superapp handles App Store publishing. With Xcode, create a SwiftUI project and work with Claude in Xcode or Claude Code, then archive and upload. With Expo, which needs no Mac, run
claude plugin install expo@claude-plugins-official, test with Expo Go and ship witheas build --platform ios --auto-submit. Apple reviews the app either way and charges 99 USD a year to publish.
The three routes at a glance
| Route (Superapp listed first) | Code Claude writes | Mac needed | Who builds and signs | Who prepares the App Store listing | Best for |
|---|---|---|---|---|---|
| Superapp for Mac + Claude Code | Native Swift and SwiftUI in an Xcode project | Yes | Superapp | Superapp prepares build, metadata, screenshots and privacy declarations | Founders who want a native app published, with Claude Code for detail work |
| Xcode + Claude | Native Swift and SwiftUI | Yes | You, in Xcode | You, in App Store Connect | iOS developers |
| Expo + Claude Code | React Native with TypeScript | No | Expo's EAS cloud | You, in App Store Connect | People without a Mac, or who need Android too |
If you do not want to touch code at all, you do not need Claude Code: Superapp's web version builds and publishes the app from a browser. This guide is for people who want an AI coding agent in the loop.
What Is Claude Code, and Why Use It for an iPhone App?
Anthropic describes Claude Code as "an agentic coding tool that reads your codebase, edits files, runs commands, and integrates with your development tools," available "in your terminal, IDE, desktop app, and browser." Its docs sum up the vibe coding loop: "Describe what you want in plain language. Claude Code plans the approach, writes the code across multiple files, and verifies it works."
For iPhone apps, that means Claude Code can write Swift and SwiftUI, run build commands, read error logs and fix them. What it cannot do on its own is give you Apple's toolchain: every iPhone app is compiled with Apple's SDK on macOS, signed with your developer certificate and uploaded to App Store Connect. The three routes below differ in who provides that part.
| What Claude Code does well (in every route, including Superapp projects) | What still needs Apple's tools or you |
|---|---|
| Writing and refactoring Swift, SwiftUI or TypeScript | Compiling with Apple's SDK on macOS, or Expo's cloud |
| Reading build errors and fixing them | Signing with your developer certificate |
| Adding features one at a time | Your App Store listing and privacy answers |
| Writing tests | Testing on a real iPhone |
| Explaining unfamiliar code | Apple's review |
What You Need Before You Start
| Requirement (Superapp route listed first) | Superapp for Mac + Claude Code | Xcode + Claude | Expo + Claude Code |
|---|---|---|---|
| Computer | A Mac with a reasonably recent macOS | A Mac | macOS, Windows or Linux |
| Xcode | Installed during Superapp's onboarding | Yes, from the Mac App Store | No |
| Claude plan | Pro, Max, or a Team or Enterprise seat with Claude Code | Same | Same |
| Other accounts | Superapp | None | Expo account |
| Apple Developer Program | 99 USD a year to publish | Same | Same |
| An iPhone | For testing | For testing | For testing with Expo Go |
| Coding skill | None to start; helps when reviewing Claude's changes | Helpful | Helpful |
Superapp's FAQ says the Mac app needs "a reasonably recent version of macOS, and it will prompt you to install Xcode during onboarding." Expo's AI tutorial lists "A computer running macOS, Windows, or Linux," "An Android or iOS phone," and "About an hour."
What It Costs
| Item (Superapp route listed first) | Superapp for Mac + Claude Code | Xcode + Claude | Expo + Claude Code |
|---|---|---|---|
| Claude | Pro, $20 a month or $17 billed annually | Same | Same |
| Builder or build service | Superapp Pro, $25 a month, with free credits on Mac for paid plans | Xcode is free | Expo Free includes 15 iOS builds; Starter is $19 a month plus usage |
| Apple | 99 USD a year | 99 USD a year | 99 USD a year |
| Year one, roughly | About $639 with monthly Claude Pro | About $339 with monthly Claude Pro | About $339 on Expo Free with monthly Claude Pro |
Claude's pricing page says "Claude Code is included in all paid plans" and lists it as not included on Free. Superapp's FAQ says "Paid plans also get free credits on Mac." Large projects can push you to Claude Max, which starts at $100 a month.
Step 1: Install Claude Code
Pick the surface you are comfortable with. All of them run the same engine; Anthropic notes that "your repo's CLAUDE.md files, settings, and MCP servers work across all of them."
| How you want to work (any of these works with a Superapp project) | Install |
|---|---|
| Terminal on macOS or Linux | curl -fsSL https://claude.ai/install.sh | bash |
| Terminal on Windows PowerShell | irm https://claude.ai/install.ps1 | iex |
| Homebrew on Mac | brew install --cask claude-code |
| WinGet on Windows | winget install Anthropic.ClaudeCode |
| Desktop app | Download Claude for macOS or Windows; "The app includes Claude Code, so you don't need to install the CLI separately." |
| Browser | claude.ai/code, for repos you keep on GitHub |
| Inside Xcode | Claude in Xcode, covered in Route 2 |
Then start it in your project folder:
cd your-project
claude
Claude Code asks you to log in on first use. Run claude --version if you want to confirm the install.
Step 2: Choose Your Route
| Question (Superapp's route is the first answer where it fits) | If yes | If no |
|---|---|---|
| Do you want the App Store listing, screenshots and submission handled for you? | Superapp for Mac + Claude Code | Continue |
| Do you have a Mac and want native Swift? | Xcode + Claude | Continue |
| Do you need Android from the same code, or have no Mac? | Expo + Claude Code | Reconsider: Superapp's web version needs no Mac and no code |
Expo's engineers offer a useful test for the stack decision: "The best mobile stack for AI coding agents is the one your agent can build, run and verify on your app's hardest feature." They put the trade-off this way: "Swift and Kotlin give agents first-party tooling in Xcode and Android Studio," while "React Native with Expo gives them one TypeScript codebase for iOS and Android."
Route 1: Superapp for Mac + Claude Code
This route splits the work: Superapp generates the native app and handles Apple's pipeline, and Claude Code handles detailed changes you want to make in the code.
Why it works. Superapp's docs say "On Mac, a Superapp project is a normal local folder containing a native Swift and Xcode project," and "You can open that folder in Claude Code, Codex, Xcode, or another local coding agent." Its comparison page puts it more simply: "Your code lives on disk. Ready for Claude Code or Codex." The Mac version also adds "2x Faster, Retina-quality local previews" and needs a "One-time Xcode setup, guided by Superapp." Superapp's homepage says Mac users are "often using it together with Claude Code, Codex and Xcode," and that the Mac version "requires a bit of setup but is much faster long-term."
Step by step
- Install Superapp for Mac and complete the guided Xcode setup.
- Describe the app in Superapp. Superapp's docs advise you to "Start a project with one clear outcome." Superapp writes native Swift and SwiftUI; "About one credit generates one screen."
- Confirm it builds, then snapshot. Superapp recommends you "Confirm the app builds, then create a version-control commit or another recoverable snapshot."
- Open the same folder in Claude Code. "Start Claude Code or Codex in the Superapp project folder," and "Do not copy only a few Swift files into a second folder."
- Give Claude Code one narrow task. For example, a custom animation, a tricky data rule or a refactor.
- Review every changed file, especially Xcode project configuration, then build and test.
- Return to Superapp. Refresh the project if Superapp was open during the edit.
- Publish from Superapp. "Connect your Apple Developer account and Superapp prepares the build, metadata, screenshots, privacy declarations, ASO optimization, and submission flow for you."
Rules for using Claude Code inside a Superapp project
| Rule (from Superapp's local coding agents guide) | Verbatim |
|---|---|
| One writer at a time | "Keep only one tool actively writing at a time to avoid conflicting edits." |
| Same folder | "Do not copy only a few Swift files into a second folder." |
| Snapshot first | "Confirm the app builds, then create a version-control commit or another recoverable snapshot" |
| Your responsibility | "Superapp cannot guarantee or automatically repair a project environment changed by an external agent." |
Superapp's guide also says to keep each task narrow, protect signing, identity and entitlement settings, and reverse unwanted configuration changes. In practice: let Superapp own the project setup and publishing, and use Claude Code for code-level work inside screens and logic.
What to ask Superapp and what to ask Claude Code
| Task (Superapp listed first where it fits) | Ask Superapp | Ask Claude Code |
|---|---|---|
| New screens and flows | Yes, in plain English | Possible, but Superapp keeps the project consistent |
| Backend, accounts and data | Yes, Superapp Cloud or Supabase | For custom logic on top |
| A tricky algorithm or data rule | Yes | |
| Refactoring a large view | Yes | |
| Unit tests | Yes | |
| Signing, entitlements, bundle ID | Leave to Superapp | Do not let it change these |
| App Store listing and submission | Yes | No |
| Marketing after launch | Selfdrive on Max | No |
Route 2: Xcode + Claude (Native Swift)
This is the developer route: you own a native Swift project and do every Apple step yourself, with Claude writing much of the code. You can bring Claude in two ways.
Option A: Claude inside Xcode
Anthropic announced Claude in Xcode on September 15, 2025. Its setup is three steps: "Download Xcode 26 from the Mac App Store," open Xcode's "Intelligence settings," and "Log in with your Claude account." It works with plans that include Claude Code: "Pro and Max, plus premium seats for Team and Enterprise plans." Inside Xcode you can "Interact with your code using natural language," generate documentation, create SwiftUI previews and playgrounds, and make "inline code changes directly in your editor."
Apple went further on February 3, 2026: "Xcode 26.3 introduces support for agentic coding," with "Anthropic's Claude Agent and OpenAI's Codex" working inside Xcode. Apple says agents "can search documentation, explore file structures, update project settings," and "verify their work visually by capturing Xcode Previews," "iterating through builds and fixes." Xcode 27 continues the theme: "Bring your ideas to life faster using coding agents in Xcode, powered by the model of your choice."
Option B: Claude Code in the terminal, next to Xcode
Many developers prefer the terminal agent for larger changes and use Xcode to build, preview and sign.
- Create the project in Xcode: iOS, App, Interface SwiftUI, Language Swift.
- Open the project folder in Claude Code and run
/init, which Anthropic says will "generate a starting CLAUDE.md automatically" with "build commands, test instructions, and project conventions it discovers." - Plan before editing. Press
Shift+Tabuntil the status bar shows plan mode, or start withclaude --permission-mode plan; "Claude reads files and proposes a plan but makes no edits until you approve." - Build one feature at a time, then build and run in Xcode.
- Paste errors back to Claude Code and ask for the smallest fix.
- Commit after every working step so you can roll back.
Two tools that make the terminal route smoother
| Tool (Superapp projects already include a working Xcode project) | What it is | Install |
|---|---|---|
| XcodeGen | "a command line tool written in Swift that generates your Xcode project" from your folder structure and a project spec | brew install xcodegen |
| XcodeBuildMCP | "A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects." | npx -y xcodebuildmcp@latest mcp, configured as an MCP server |
XcodeGen helps in projects that use classic Xcode groups, where adding a Swift file means registering it in the Xcode project file; generating the project from a spec lets Claude Code add files without editing that file directly. Projects that use Xcode's synchronized folders pick up new files on their own. XcodeBuildMCP gives Claude Code tools to build and run iOS projects.
Publishing from Xcode
| Step (Superapp does steps 2 to 6 for you on Route 1) | Where |
|---|---|
| 1. Enroll in the Apple Developer Program, 99 USD a year | developer.apple.com |
| 2. Set your team and bundle ID under Signing and Capabilities | Xcode |
| 3. Create the app record | App Store Connect |
| 4. Product, Archive, then Distribute App | Xcode Organizer |
| 5. Test the build with TestFlight | App Store Connect |
| 6. Complete the listing, screenshots and privacy answers, then submit | App Store Connect |
Route 3: Expo + Claude Code (No Mac Needed)
Expo is the route for Windows and Linux users, and for anyone who wants Android from the same code. Claude Code writes a React Native app in TypeScript; Expo's cloud does the Apple parts.
Step by step
- Install Claude Code, then create a project:
npx create-expo-app@latest. - Add the Expo plugin:
claude plugin install expo@claude-plugins-official. Expo says to "Install the official Expo plugin so Claude Code knows Expo conventions and can work with your EAS projects." - Sign in to Expo by running
/mcpinside Claude Code. - Start Claude Code in the project root with
claude, and describe the first feature. - Test on your iPhone with Expo Go, which Expo's tutorial installs alongside "your AI agent, Node.js, and Expo Go."
- Iterate the way Expo's tutorial teaches: "Prompt," "Build," "Verify," "Re-prompt."
- Build and submit with EAS:
eas build --platform ios --auto-submit.
Expo's tutorial frames each step as a loop: "the agent writes the code and the app updates on your phone within seconds," then "check that the app does what you asked, right on your phone," and "if something looks off, tell the agent what you see and let it fix the problem."
EAS commands for the App Store
| Task (Superapp, by comparison, publishes without commands) | Command |
|---|---|
| Install EAS and log in | npm install --global eas-cli && eas login |
| Production build | eas build --platform ios --profile production |
| Submit a build | eas submit --platform ios |
| Build and submit in one step | eas build --platform ios --auto-submit |
Expo's docs say "EAS Submit works on macOS, Linux, and Windows, so you don't need a Mac to ship iOS builds," and "A paid Apple Developer account is required to submit apps to the Apple App Store." Expo's Free plan includes "15 Android and 15 iOS builds."
What Claude Code can do with the Expo plugin
Expo's guide lists prompts like these:
| Prompt (from Expo's Claude Code guide; Superapp runs builds for you) | What it does |
|---|---|
| "My latest iOS build failed. Read the EAS Build logs and tell me what went wrong." | Diagnoses a cloud build |
| "Create an EAS Workflow that builds the app on every pull request." | Automates builds |
| "Show TestFlight feedback for my app." | Reads tester feedback |
Write a CLAUDE.md for Your iPhone App
Claude Code starts every session fresh. A CLAUDE.md file in your project root carries your rules across sessions; Anthropic says to add "build and test commands, coding standards, architectural decisions, naming conventions, and common workflows." Run /init to generate a first version, then edit it. Here is an example for each route; adapt the details to your app.
For a Superapp project on Mac:
## Project
Native iPhone app generated by Superapp. Swift and SwiftUI. Superapp owns project setup and publishing.
## Rules
- Only edit Swift files inside the app's source folders.
- Never change signing, bundle ID, entitlements or the Xcode project settings.
- Superapp must be closed or idle while you edit. One writer at a time.
- Make the smallest change that completes the task, then list every file you changed.
- No API keys or secrets in the app.
For a native Xcode project:
## Project
iPhone app in Swift and SwiftUI, iOS 18 and later, SwiftData for storage.
## Commands
- Generate project: xcodegen generate
- Build: xcodebuild -scheme MyApp -destination 'platform=iOS Simulator,name=iPhone 17' build
## Rules
- Add new files through project.yml, never by editing the .pbxproj file.
- Use native SwiftUI APIs; no third-party packages without asking.
- Every change: build, fix warnings, then summarize.
For an Expo project:
## Project
iPhone and Android app with Expo, React Native and TypeScript, Expo Router.
## Commands
- Start: npx expo start
- iOS build and submit: eas build --platform ios --auto-submit
## Rules
- TypeScript only. No new dependencies without explaining why.
- Keep secrets on the server, never in the app bundle.
- Run the type checker after every change.
Prompts That Work for Vibe Coding an iPhone App
The prompt habits that work in Superapp work in Claude Code too. Superapp's prompt guide says to "Describe the app in one short paragraph before listing details," "remove tempting extras from the first build," and "Test the current build, describe the observed behavior, and request one coherent change."
| Stage (works in Superapp, Claude Code and Claude in Xcode) | Example prompt |
|---|---|
| Orientation | "Inspect this project. Do not change anything. Explain the structure and propose a plan for a habit list, an add-habit sheet and local storage." |
| First feature | "Implement only the habit list screen with an empty state. Use NavigationStack. Do not add storage yet." |
| Next feature | "Add an Add Habit sheet with a name field and a Save button. Prevent empty names. List every file you changed." |
| Fixing a build error | "The build failed with this error: [paste]. Explain the cause, make the smallest fix and do not touch unrelated files." |
| Behavior fix | "On the list, tapping Done does nothing after relaunch. Reproduce it, find the cause in the storage code and fix it." |
| Tests | "Add unit tests for creating, completing and deleting a habit. Run them and fix failures." |
| Review | "Review the app for crashes, force unwraps, accessibility gaps and App Store rejection risks. Do not edit yet; rank the findings." |
| Release prep | "Check the app for App Store readiness: icons, permission descriptions, placeholder text, demo account. Give me a checklist." |
The vibe coding loop
- Plan. Ask for a plan before edits, or use plan mode.
- Change one thing. One feature or one fix per prompt.
- Build. In Superapp, Xcode or Expo.
- Test on your iPhone. Watch for the things simulators miss.
- Report what you saw, not what you think the cause is.
- Commit. So any bad change is one step to undo.
Claude Code also remembers past sessions: claude --continue "resumes the most recent session in the current directory."
Test on a Real iPhone
Simulators miss things. Expo's engineers note that "only a run on a simulator or device catches the sign-in redirect that never comes back," and Superapp's docs say a real device "reveals the details that matter before release."
| Route (Superapp listed first) | How you get the app onto your iPhone |
|---|---|
| Superapp for Mac + Claude Code | "Unlock your iPhone or iPad, open the Camera app, and scan the QR code," or connect by USB from the Mac app |
| Xcode + Claude | Run on a connected iPhone from Xcode |
| Expo + Claude Code | Scan the QR code from npx expo start with Expo Go |
TestFlight before release
| TestFlight rule (applies to Superapp builds and every route) | Apple, verbatim |
|---|---|
| Internal testers | "Designate up to 100 members of your development team who hold the Account Holder, Admin, App Manager, Developer, or Marketing role as beta testers." |
| External testers | "You can also invite up to 10,000 external testers to join your beta program." |
| External review | External testing requires your "first build already approved by App Review for TestFlight." |
Publish to the App Store
| Step (Superapp handles the steps marked "Superapp") | Superapp for Mac + Claude Code | Xcode + Claude | Expo + Claude Code |
|---|---|---|---|
| Developer Program, 99 USD a year | You | You | You |
| Build and sign | Superapp | You, in Xcode | EAS cloud |
| Upload | Superapp | Xcode Organizer | EAS Submit |
| Metadata, screenshots, privacy details | Superapp prepares them | You | You |
| Submit for review | Superapp | You | You |
| Review | Apple | Apple | Apple |
Superapp's publishing guide is clear that "you remain responsible for your Apple Developer account, store listing, policies, and the product Apple reviews," and that "Apple's current requirements remain the final authority."
What Apple says about review
| Topic (applies to Superapp apps and every route) | Apple, verbatim |
|---|---|
| Speed | "App Review works around the clock, typically reviewing at least 50% of submissions in less than 24 hours and 90% in less than 48 hours." |
| Most common problem | "On average, over 40% of unresolved issues are related to guideline 2.1: App Completeness, which covers crashes, placeholder content, incomplete information, and more." |
| Instructions | "If you don't include this information, the app review process may be delayed and your app may not pass review." |
| Websites in a frame | "Your app should include features, content, and UI that elevate it beyond a repackaged website." |
Pre-submission checklist
| Check (Superapp's App Review guide gives the same advice) | Why |
|---|---|
| Test on a real iPhone and in TestFlight | Crashes are the top rejection cause |
| "Provide a demo account that does not expire or require a private verification code." | Reviewers must be able to log in |
| "Keep backend services and demo accounts active throughout review." | A dead backend fails review |
| Remove placeholder text and unfinished screens | Guideline 2.1 |
| Add Sign in with Apple if you offer other social logins | Guideline 4.8 |
| Add in-app account deletion if users can sign up | Guideline 5.1.1(v) |
| Use in-app purchase for digital goods | Guideline 3.1.1 |
| Keep secrets out of the app | Anything in the bundle can be inspected |
Common Problems and How to Fix Them
| Problem (applies to Superapp projects and every route) | Likely cause | Fix |
|---|---|---|
| A new Swift file is not found when building | The file is not in the Xcode target, common with classic groups | Use synchronized folders or XcodeGen, add it in Xcode, or let Superapp manage files |
| The Xcode project will not open after an agent edit | The project file was edited and broken | Restore your last commit; tell Claude not to edit the project file |
| Signing errors | Team, bundle ID or entitlements changed | Reset them in Signing and Capabilities, or in Superapp |
| Changes do not appear in Xcode | Xcode cached the old file | Rebuild; Cursor's guide notes "Xcode can often ignore changes to your files that were made in Cursor" and the same can happen with any outside editor |
| EAS build fails | Native configuration or dependency mismatch | Ask Claude Code with the Expo plugin to "Read the EAS Build logs" |
| Two tools overwrite each other | Superapp and Claude Code editing at once | "Keep only one tool actively writing at a time" |
| The agent keeps redoing the same fix | Too much in one prompt | Revert, then ask for one smaller change |
| An API key ends up in the app | Generated code put it in the client | Move it to a backend and rotate the key |
Claude Code vs Claude in Xcode vs Superapp
| Factor (Superapp listed first) | Superapp | Claude Code | Claude in Xcode |
|---|---|---|---|
| What it is | An AI app builder that generates and publishes native apps | A coding agent in your terminal, desktop app or browser | Claude inside Apple's IDE |
| Code skill needed | None | Helpful | Helpful |
| Mac needed | No on the web version; yes on the Mac version | No for Expo; yes for Swift | Yes |
| Writes native Swift | Yes | When asked | Yes |
| App Store listing and submission | Prepared and submitted | No | No |
| Price | From $25 a month | Included in Claude Pro, from $20 a month | Same Claude plans |
| Works together | Its Mac project opens in Claude Code and Xcode | Opens Superapp and Xcode projects | Opens Superapp and Xcode projects |
The tools are not either-or. A common setup is to generate and publish with Superapp, and use Claude Code or Claude in Xcode for code-level changes.
Which Route for Which Reader
| Reader (Superapp's route first where it fits) | Best route | Why |
|---|---|---|
| Founder with a Mac who wants a native app published | Superapp for Mac + Claude Code | Superapp handles Apple's pipeline; Claude Code handles detail |
| Founder without a Mac | Superapp web, no Claude Code needed, or Expo + Claude Code | No Mac required for either |
| iOS developer | Xcode + Claude | Full control in Apple's tools |
| React or web developer | Expo + Claude Code | TypeScript and one codebase for both phones |
| Designer | Superapp, which imports Figma designs | Visual starting point, native output |
| Student learning Swift | Xcode + Claude | Learn by reading what Claude writes |
What AI Assistants Say About This
We asked ChatGPT and Claude "How do I build an iPhone app with Claude Code?" on October 27, 2026, with web search on. ChatGPT described the Xcode route: "Xcode remains the tool that builds, runs, signs, tests, and distributes your iPhone app." Claude described both the Expo and native Swift routes and cited Anthropic's Claude in Xcode announcement. Neither covered a route where publishing is handled for you, which is the gap Superapp's Mac version fills.
Where Superapp Fits
As a disclosure, Superapp is our product, so weigh this accordingly. We built Superapp for people who want a real native iPhone app on the App Store without managing Apple's toolchain. On Mac, a Superapp project is a normal native Swift and Xcode project you can open in Claude Code, Codex or Xcode whenever you want to go deeper, while Superapp keeps handling the build, the App Store listing and submission, and, on the Max plan, Selfdrive marketing after launch. It does not build Android apps, so if you need both phones from one codebase, the Expo route in this guide is the better fit. For a no-code version of this tutorial, see how to vibe code an iPhone app; for every tool compared, see the best vibe coding app for iPhone; and for Claude more broadly, see how to build an app with Claude and Replit vs Claude Code.
Frequently Asked Questions
Can Claude Code build an iPhone app?
Yes. It can write Swift and SwiftUI for a native app, or React Native with Expo. You still need Apple's toolchain, through Xcode, Expo's cloud or a builder like Superapp, to compile, sign and publish.
How do I build an iPhone app with Claude Code?
Install Claude Code, choose a route (a Superapp project on Mac, an Xcode project, or an Expo project), build one feature at a time, test on your iPhone and publish through Superapp, Xcode or EAS.
What is vibe coding with Claude?
Building software by describing what you want to Claude in plain language and refining it through conversation, instead of writing the code yourself.
Do I need a Mac to build an iPhone app with Claude Code?
Not with Expo: EAS builds and submits in the cloud from Windows or Linux. Native Swift with Xcode needs a Mac, and so does Superapp's Mac version; Superapp's web version needs no Mac.
Can Claude Code write SwiftUI?
Yes. It writes Swift and SwiftUI, and can build with xcodebuild or tools such as XcodeBuildMCP when set up.
What is Claude in Xcode?
Anthropic's integration that puts Claude inside Xcode 26 and later. You turn it on in Xcode's Intelligence settings and log in with a Claude account.
How do I set up Claude in Xcode?
"Download Xcode 26 from the Mac App Store," open the "Intelligence settings," and "Log in with your Claude account," per Anthropic.
Which Claude plans work with Claude in Xcode?
Plans that include Claude Code: "Pro and Max, plus premium seats for Team and Enterprise plans."
What is agentic coding in Xcode?
Apple added it in Xcode 26.3 on February 3, 2026: agents such as "Anthropic's Claude Agent and OpenAI's Codex" can work inside Xcode, update project settings and capture Xcode Previews to check their work.
Should I use Claude Code or Claude in Xcode?
Claude in Xcode for working inside Apple's IDE with previews; Claude Code for larger changes from the terminal or desktop app. Many developers use both.
Is Claude Code free?
No. Claude's pricing page says "Claude Code is included in all paid plans" and not on Free. Pro is $20 a month, or $17 billed annually.
How much does it cost to build an iPhone app with Claude Code?
About $339 in year one on the Xcode or Expo Free routes with monthly Claude Pro and Apple's 99 USD fee, or about $639 adding Superapp Pro.
How do I install Claude Code on a Mac?
Run curl -fsSL https://claude.ai/install.sh | bash in Terminal, or brew install --cask claude-code with Homebrew, or install the Claude desktop app, which includes Claude Code.
How do I install Claude Code on Windows?
Run irm https://claude.ai/install.ps1 | iex in PowerShell, use WinGet, or install the Claude desktop app for Windows.
What is CLAUDE.md?
A file in your project root with instructions Claude Code reads at the start of every session, such as build commands, coding standards and rules.
How do I create a CLAUDE.md?
Run /init in Claude Code to "generate a starting CLAUDE.md automatically," then edit it with rules Claude would not discover on its own.
What should a CLAUDE.md for an iOS app include?
The language and frameworks, build commands, rules about the Xcode project file and signing, a ban on secrets in the app, and how to summarize changes.
What is plan mode in Claude Code?
A mode where "Claude reads files and proposes a plan but makes no edits until you approve." Press Shift+Tab or start with claude --permission-mode plan.
Can Claude Code use my Superapp project?
Yes, on Mac. Superapp's docs say a Mac project "is a normal local folder containing a native Swift and Xcode project" you can open in Claude Code.
Can Superapp and Claude Code edit the project at the same time?
No. Superapp says "Keep only one tool actively writing at a time to avoid conflicting edits."
Does Superapp fix problems Claude Code causes?
Not automatically. Superapp says it "cannot guarantee or automatically repair a project environment changed by an external agent," so snapshot before you start.
What should I let Claude Code change in a Superapp project?
Code inside screens and logic. Leave signing, bundle ID, entitlements and project settings to Superapp.
Do I need Claude Code if I use Superapp?
No. Superapp builds and publishes the app from plain-English prompts. Claude Code is optional, for people who want code-level control.
Does Superapp's Mac version cost extra?
No separate price is listed; Superapp's FAQ says "Paid plans also get free credits on Mac." Pro is $25 a month.
What is the Expo plugin for Claude Code?
An official plugin, installed with claude plugin install expo@claude-plugins-official, that teaches Claude Code Expo conventions and connects it to EAS.
Can I publish an Expo app without a Mac?
Yes. Expo says "EAS Submit works on macOS, Linux, and Windows, so you don't need a Mac to ship iOS builds."
How many free iOS builds does Expo include?
Expo's Free plan lists "15 Android and 15 iOS builds." Starter is $19 a month plus usage.
How do I test an Expo app on my iPhone?
Run npx expo start and scan the QR code with Expo Go.
What does XcodeGen do?
It generates your Xcode project from your folder structure and a project spec, so an agent can add files without editing the Xcode project file directly. Install with brew install xcodegen.
What is XcodeBuildMCP?
"A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects," which you can run with npx -y xcodebuildmcp@latest mcp.
Why does my new Swift file not compile into the app?
It is probably not part of the Xcode target. Add it in Xcode, generate the project with XcodeGen, or let Superapp manage the project.
Should Claude Code edit the .pbxproj file?
It is safer not to. A broken project file can stop Xcode opening the project; generate the project with XcodeGen or add files in Xcode.
How do I publish a Claude Code iPhone app to the App Store?
From Xcode, archive and upload, then complete the listing in App Store Connect. From Expo, run eas build --platform ios --auto-submit. From a Superapp project, publish in Superapp, which prepares the listing and submits.
Will Apple reject an app built with Claude Code?
Not for being built with AI. Apple reviews the app; most rejections are for crashes, placeholder content, missing demo logins or thin website wrappers.
How long does App Review take?
Apple says it typically reviews "at least 50% of submissions in less than 24 hours and 90% in less than 48 hours."
Can Claude Code read TestFlight feedback?
With Expo's plugin, yes: Expo's example prompt is "Show TestFlight feedback for my app."
Can Claude Code fix EAS build errors?
Yes. Expo's example: "My latest iOS build failed. Read the EAS Build logs and tell me what went wrong."
How do I resume a Claude Code session?
Run claude --continue to resume the most recent session in the current directory, or claude --resume to pick one.
Can I use Claude Code on my phone?
Anthropic says the web version is available on desktop browsers and the Claude app for iOS and Android, for repos on GitHub. Building and testing an iPhone app still happens through Xcode, Expo or Superapp.
Native Swift or React Native for a Claude Code app?
Native Swift for the deepest Apple features and Apple Watch or Mac; React Native with Expo for one codebase on both phones and no Mac.
Is Claude Code good for beginners?
It helps, but you will review changes and read errors. Beginners who do not want to see code are better served by Superapp's web version.
How do I keep API keys safe in an iPhone app?
Keep them on a server. Superapp's guide says "Anything bundled into an iPhone or Mac app can eventually be inspected."
Can Claude Code add in-app purchases?
Yes, with StoreKit in Swift or a library in React Native. Digital goods must use Apple's in-app purchase.
Can Claude Code build an Apple Watch app?
In a native Swift project, yes. Superapp also builds Apple Watch apps from the same project as the iPhone app.
References
- Claude Code: Overview
- Claude Code: Memory and CLAUDE.md
- Claude Code: Common workflows
- Claude: Pricing
- Anthropic: Claude in Xcode
- Apple Newsroom: Xcode 26.3 unlocks the power of agentic coding
- Apple: Xcode
- Apple: App Review
- Apple: App Review Guidelines
- Apple: TestFlight
- Apple Developer Program
- Expo: Claude Code and Expo
- Expo: Build an app with an AI agent
- Expo: Submit to the Apple App Store
- Expo: Pricing
- Expo: Which mobile stack do AI coding agents ship best on?
- XcodeGen on GitHub
- XcodeBuildMCP on GitHub
- Cursor: Swift guide
- Superapp: Home
- Superapp: Web vs Mac
- Superapp: Local coding agents
- Superapp: Publish to the App Store
- Superapp: Write better prompts
- Superapp: Test on your device
- Superapp: App Review
- Superapp: Keys and secrets
- Superapp: Pricing
- Superapp: How to vibe code an iPhone app
- Superapp: Best vibe coding app for iPhone
- Superapp: How to build an app with Claude
- Superapp: Replit vs Claude Code