Choose how the app is built
There are three common routes. Each is a framework, a set of ready-made building blocks for apps.
| Route | Language | Good to know |
|---|---|---|
| React Native with Expo | JavaScript or TypeScript | One codebase for iPhone and Android; Expo adds tools that make starting and testing simpler |
| Flutter | Dart | One codebase for iPhone and Android, from Google, with its own interface toolkit |
| Swift with SwiftUI | Swift | Apple's own language and toolkit; iPhone only, with the closest access to Apple features |
If you know web development, or want Android too, Expo is a gentle start. If you want an app that feels fully at home on Apple devices and need its newest features, choose Swift. AI models write all three well, because all three are widely used and documented.
What the AI does well
- Creating the project and its folder structure.
- Building screens, navigation, forms and lists from a description or a screenshot.
- Connecting to a server, saving data on the device and handling sign-in.
- Explaining and fixing build errors when you paste the full message.
- Writing tests, store descriptions and the privacy text.
It is weaker at things it cannot see or touch: how a gesture feels in the hand, how the app behaves on a slow connection, and settings that live in Apple's websites and not in your code.
What still needs a Mac, Xcode and an Apple account
Xcode is Apple's free development tool. It builds the app, runs the iPhone Simulator and signs the app, and it only runs on macOS. A native Swift app needs it from the first day. Flutter and React Native projects also need it to build the iPhone version on your own machine.
There are cloud build services that build an iPhone app without a Mac of your own. Expo offers one. Check their current documentation for what they cover.
To publish on the App Store you need membership of the Apple Developer Program, which is paid. Apple's site has the current terms. Signing, which proves the app comes from you, is managed through that account. Every app and update goes through Apple's review before it appears in the store.
Testing on a device
The Simulator is a pretend iPhone on your Mac. It is quick and good for layout. It cannot fully stand in for a real phone: the camera, notifications, sensors and real performance need a device.
With Expo, the Expo Go app can open your project on your own phone during development. With Xcode, you connect a phone and run the app on it. To share a test version with other people, Apple provides TestFlight. Test on a real device before you submit.
A sensible step-by-step
- 1. Write a one-page brief. What the app does, the three or four main screens, what data it stores.
- 2. Pick the framework and install its tools, plus Xcode.
- 3. Ask the AI to create the project and get an empty app running in the Simulator before adding anything.
- 4. Build one screen at a time. Run the app after each one.
- 5. Add data and sign-in once the screens work with sample data.
- 6. Test on a real iPhone. Fix what the Simulator hid.
- 7. Prepare the store listing: icon, screenshots, description, privacy details.
- 8. Send a test build to a few people, then submit for review.
Save a checkpoint after every working step. The habits in what is vibe coding apply fully here. If you also want Android, read how to build an Android app with AI.
Doing this in VibeCode.surf
VibeCode.surf is a general desktop AI code editor, in beta. It has no iOS simulator of its own and no App Store publishing. What it does is run the coding side: agents write Swift, Dart or TypeScript, keep a plan and project notes, and run the command-line tools you have installed, such as Expo, Flutter or Xcode commands, after you approve each command. You start long-running things like a development server yourself in the built-in terminal, and a Fix with agent button sends a terminal error to the active agent. The Simulator still opens from Xcode as usual.
If your framework can also run the app as a web page on localhost, the preview has a phone-size frame and agents can check layouts at phone size in their browser. That is a layout check, not a replacement for the Simulator or a device. The app builder guide has more. There is no debugger with breakpoints and no language-server autocomplete yet, so keep Xcode open for those. macOS is the tested platform, which suits iPhone work. You can install it with one command.