Short answer: yes. VibeKit can build a native iPhone app and take it to the App Store from your phone, with no Mac and no Xcode: its agent writes the app, VibeKit builds, signs and uploads it to your TestFlight, and you send it to Apple's review in App Store Connect. You need a paid Apple Developer Program membership and a free Expo account, and Apple reviews every app before it goes live.
We build VibeKit, one of the options below. Native iPhone apps and App Store shipping have been on for every VibeKit account since September 28, 2026; this is the concrete walkthrough. For the broader questions, see building an iPhone app without a Mac and whether AI can build a native iPhone app.
What do you need, and what does it cost?
As of November 2026:
- Apple Developer Program: 99 USD a year, paid by you to Apple (prices vary by region). It has to be your own account: an individual's legal name is listed as the seller on the App Store, and you must pay with your own card.
- An Expo account: free. Expo's Free plan includes 15 iOS builds a month in a low-priority queue, and the limits reset monthly. Expo's Starter plan is $19 a month if you need more.
- VibeKit: any plan, Free included. There is no charge per build or submission. But free apps sleep after 60 idle minutes, and a free account gets 12 awake hours per UTC day, shared across its apps. An App Store app gets its data from its VibeKit backend, so the first open after a sleep waits while it wakes, and once the day's awake hours are used it stays asleep until midnight UTC. Once real people install it, get an always-on app: Starter is $9.99 a month on the web and includes one. AI usage comes from credits, or from your own Anthropic or OpenAI key at no markup.
So the floor is $99 a year to Apple. Everything else can stay at $0.
Step by step: from idea to the App Store on your iPhone
Every VibeKit step below works in the VibeKit iPhone app, or on the web at app.vibekit.bot.
1. Build it as an iPhone app. Create a new app, pick Mobile app, then iPhone app, and describe it. The agent writes a native Expo (React Native) app, and you open it on your phone in the free Expo Go app while you build. Each change you ask for publishes on its own right after the reply. Already have a VibeKit web app? Ask its agent to make it a native iPhone app: it converts in place, keeping the same address, data and accounts, and Previous versions can undo it.
2. Join the Apple Developer Program. In select regions you can enroll in the Apple Developer app on your iPhone, verifying your identity with a photo of your ID; elsewhere, enroll on Apple's website. Enrolling as a company also needs a D-U-N-S Number; individuals do not.
3. Connect your Apple account. In VibeKit's iPhone app, go to Profile > Developer > Your Apple and Expo accounts (older app versions: Settings > App Store; on the web, the App Store card in Settings). You need an App Store Connect API key:
- The first time, the Account Holder requests API access in App Store Connect under Users and Access > Integrations. Apple approves these requests case by case.
- Then generate a Team key with the Admin role and download its .p8 file to Files. Apple lets you download it only once.
- Enter the Key ID, the Issuer ID and your Team ID (the screen links to your Apple membership details), choose the .p8 from Files, and tap Connect Apple. VibeKit checks the key with Apple before saving it, encrypted.
4. Connect your Expo account. Make a free account at expo.dev, create a token under Access tokens, paste it, and tap Connect Expo. Expo notes that anyone with the token can act on your behalf; you can revoke it on expo.dev any time.
5. Ask your app's agent. Copy the message the screen shows, "Put this in the App Store", and send it in your app's chat. The agent registers your app's bundle ID (like com.yourname.yourapp) on your Apple team and walks you through the rest. It also prepares its part: a real 1024-pixel icon, a privacy page, and a demo account for Apple's reviewer if the app has sign-in.
6. Create the app in App Store Connect. This is Apple's step, and only you can do it: Apps > + > New App, platform iOS, a name, a language, the bundle ID the agent registered, and a SKU. VibeKit then finds the record by its bundle ID.
7. Build to TestFlight. Tell the agent to build it, or tap Build under step 5 of the accounts screen. VibeKit creates the signing certificate through Apple's API with your key, the build runs in your Expo account, and VibeKit uploads it to App Store Connect and adds you as a TestFlight tester. When the status says it is in TestFlight, install it from the TestFlight app. A TestFlight build stays testable for up to 90 days.
8. Fill in the listing and tap Submit for Review. In App Store Connect, add the description, screenshots and privacy details, choose the build, then Add for Review and Submit for Review. The agent can draft the text. VibeKit never presses this button: Apple's guideline 4.2.6 says app generation services "should not submit apps on behalf of their clients", so the submission is yours, under your account.
How long does it take?
| Step | Who | Time |
|---|---|---|
| Apple enrollment | You, then Apple | No fixed time stated for individuals. Companies wait up to 5 business days for a D-U-N-S Number, then up to 2 more |
| API access | Apple | Approved case by case, no time stated |
| Expo account and token | You | A few minutes |
| Build, sign, upload, process | VibeKit, Expo, Apple | VibeKit estimates 10 to 20 minutes, longer when Expo's free queue is busy |
| App Review | Apple | At least 50% in under 24 hours, 90% in under 48 |
In our own first test, on September 27, 2026, the build went from the request to TestFlight in 9 minutes. The waits that matter are Apple's: enrollment and review.
Does any step need a computer?
No step needs a Mac or Xcode. The VibeKit steps are built for the phone, including picking the .p8 from Files. The Apple steps (the API key, New App, the listing) are on the App Store Connect website, because Apple's App Store Connect iPhone app covers sales, reviews and replying to App Review, not creating keys or apps. Open the website in Safari on your iPhone; if a page is fiddly on a small screen, any computer's browser does the same job.
What if Apple rejects it?
App Store Connect shows which guideline your app missed, and you can reply to App Review there. Paste Apple's message into your app's chat, let the agent fix it, ask for a new build, and resubmit. Three guidelines to read before submitting: an app should be more than "a repackaged website" (4.2), an app with a login needs demo account details and its backend switched on (2.1), and every app needs a privacy policy link (5.1.1).
What happens after it is live?
Changes you make in chat reach Expo Go and the web version right away. The App Store copy changes only when you ship a new build and Apple reviews it, so each update repeats steps 7 and 8. The installed app gets its data and accounts from its VibeKit address, so keep the app on VibeKit: deleting it there would break every installed copy.
This is VibeKit's newest path, so expect rougher edges than on web apps.
What about Android and Google Play?
VibeKit has no Google Play path today. On Android, the same app opens in Expo Go, and its web version installs from Chrome with its own icon.
Other ways to do it
Replit turns a description into a native iOS app with its Agent, previews it through Expo, and walks you through App Store submission with your own Apple Developer account; its page says that to build a native app you "open Replit on the web". Rork is built for native apps: new projects are native iPhone apps in Swift or native Android apps in Kotlin (it no longer starts new Expo projects; older ones keep working), and it publishes to the App Store and Google Play from the same Publish menu. Native iPhone apps in SwiftUI are included in its Pro plan at $20 a month; Max, from $200 a month, adds iPad, Apple Watch, Vision Pro and widgets. If you need Google Play, or want your app written in Swift, Rork is the one; VibeKit has no Google Play path. For the wider picture, see how to build an app from your phone and our guide to the four approaches.
Start your first native app
Start in VibeKit, or open the iOS app. Create a new app, pick Mobile app, then iPhone app, and try:
Build an iPhone app for my morning routine: a checklist of five habits I can tick off each day, a streak counter for each habit, and a history screen for the last 14 days. Save everything to my account so it is still there when I reopen the app.
Open it in Expo Go, tick two habits, then close the app completely and reopen it: if both are still ticked, it works. When you are happy with it, send the agent "Put this in the App Store" and follow the steps above.