DEV Community

Mythex
Mythex

Posted on Fully Autonomous

Can ChatGPT or Claude build a mobile app end to end? The six steps between the chat and the App Store

Ask ChatGPT or Claude for "an iPhone app for my dog-walking business: clients book walks, walkers see their day, I see payments" and you'll get something within a minute. Usually it's one of two things: a web page you can click around in (Claude's artifact panel, ChatGPT's canvas), or a pile of React Native or Swift files with instructions that start with "First, install Xcode".

Neither is an app on your phone. Neither is in the App Store.

So, can they build a mobile app end to end? Short answer: the chat can write almost all of the code. It can't do the steps that need a Mac, a signing certificate, a developer account and a store review. Their coding agents (Claude Code and Codex) can do more of it, if you already have those things set up. This article walks through the six steps between "the chat wrote code" and "it's on my customers' phones", so you know which ones the AI does and which ones land on you.

The six steps from prompt to phone

Every mobile app, AI-written or not, goes through the same pipeline:

  1. Code for the screens and logic.
  2. A backend: a database, sign-in, and an API the app talks to.
  3. A native project: the Xcode project for iOS and the Gradle project for Android that wraps your code.
  4. A build: compiling that project into an .ipa (iPhone) or .aab/.apk (Android).
  5. Signing: proving to Apple and Google that the build came from you.
  6. Distribution: TestFlight and Google Play testing, then review, then the public stores.

Here's where ChatGPT and Claude fit on each.

Step 1: Code. The chat is genuinely good here

Both models write solid React Native, Flutter, Swift and Kotlin. For a booking app like the dog-walking example, a prompt like this gets you a reasonable first pass:

Write a React Native (Expo) app with three tabs: Book a walk (pick dog, date, time slot), My bookings, and Profile. Use TypeScript. Keep data in a single API module so I can swap in a real backend later.

The catch is that you can't run it inside the chat. Claude's artifacts and ChatGPT's canvas preview web code (HTML and React), not native mobile code. What you see in the side panel is a web mock-up of your app, not the app.

Step 2: The backend. Nobody does this for you in a chat

The preview stores bookings in memory, so your walker never sees the booking your client just made. A real app needs a shared database, sign-in for clients and walkers, and rules about who can see what (a walker sees their walks, not everyone's payment details).

The chat will happily write the schema and API code. Someone still has to create the database, host the API, keep secrets out of the app bundle and pay for it every month.

Step 3: The native project. Agents can do it, chats can't

To get onto a phone, your code needs a native shell. With Expo or Capacitor that's a few commands; with Swift it's an Xcode project. This is where the coding agents come in. Claude Code and Codex can run commands, create the project, install packages and fix errors as they go. A chat window can only tell you what to type.

Step 4: The build. iPhone builds need macOS

Android builds run on any machine. iPhone builds need Xcode, and Xcode only runs on macOS. That matters for AI agents:

  • Claude Code runs where you run it. On a Mac with Xcode installed, it can run xcodebuild and read the errors. On Windows or Linux, it can't build for iPhone.
  • Codex in the cloud works in Linux containers, so it can write the iOS code but can't compile it there. Run the Codex CLI on your own Mac and you're back to the Claude Code situation.
  • Cloud build services (Expo's EAS Build, Codemagic, Bitrise and others) give you Mac build machines without owning a Mac. The AI can write their config file; you create and connect the account.

Step 5: Signing. This one is yours

Apple and Google only accept builds signed with your keys:

  • Apple: the Apple Developer Program costs $99 a year. You need certificates and provisioning profiles, or an App Store Connect API key that lets a build service handle them.
  • Google: a Google Play developer account is a one-time $25. Builds are signed with your upload key, and Play App Signing manages the final key.

No AI can sign up for these for you. Both need your identity, and Apple's needs a payment and, for companies, a D-U-N-S number.

Step 6: Distribution. Testing first, then review

  • iPhone: upload to App Store Connect, invite testers in TestFlight, then submit for App Review. Expect a rejection or two the first time, often for missing privacy details, login problems the reviewer hits, or an app that "looks like a website".
  • Android: upload to an internal testing track first. New personal Google Play accounts must also run a closed test with at least 12 testers for 14 days before they can publish to production. Organisation accounts skip that rule.

So what can each one do, honestly?

Step ChatGPT / Claude (chat) Claude Code / Codex (agent) You
1. Code Yes Yes Review it
2. Backend Writes the code Writes and can deploy, if you give it accounts Choose hosting, pay for it
3. Native project Instructions only Yes Install tooling
4. Build No Yes, on a Mac (iPhone) or any machine (Android) Provide the Mac or a build service
5. Signing No Can use keys you created Developer accounts, keys
6. Distribution Writes store text Can upload with an API key Testers, review, release

If you're a developer, a coding agent plus a Mac plus your developer accounts gets you surprisingly close to end to end. If you run a business and don't want a terminal, the chat alone gets you to step 1 and a pile of instructions.

For a wider side-by-side of what each assistant's plans include (previews, coding agents, prices), we keep a comparison here: ChatGPT vs Claude vs Gemini for building apps.

The other route: an app builder that runs the pipeline

The middle steps (backend, native project, build machines, uploads) are where most non-developers stop. AI app builders take those over. I work at Mythex, one of them, so here's how it works there, and weigh it accordingly.

You describe the app in a chat, the same way you'd prompt ChatGPT:

A booking app for a dog-walking business in Austin. Clients book a walk (dog, date, time slot) and see their bookings. Walkers sign in and see today's walks with addresses. I see all bookings and mark them paid.

Mythex builds it as a web app with a Postgres database and hosts it at a URL, so steps 1 and 2 happen together, and you can try it in a browser straight away. Then, on the Pro plan, you open Publish → Android or iPhone, or just say "build the Android app and send it to Google Play":

Publish → Android in Mythex: the latest build, the Google Play account, and Build new version

The agent wraps the web app with Capacitor, builds it on Mythex's build machines (no Xcode or Android Studio on your side) and either gives you an Android file to download or sends it to your Google Play internal testing track. iPhone builds go to your TestFlight.

A Mythex Android build card: In internal testing, with a link to the Play Console

Steps 5 and 6 still need you. You connect your own Google Play service account key and App Store Connect API key, because the apps are published under your developer accounts, not ours. Creating the app listing the first time, Google's Data safety form and Apple's App Privacy section stay on the stores' own websites. Anything that can't be taken back, like releasing to production or submitting for review, the agent asks you about first. The mobile docs walk through each store: docs.mythex.ai/mobile/overview.

Honest limits

  • Wrapped web screens, not fully native UI. Capacitor apps run your web app inside a native shell. For booking, ordering, portals and internal tools that's usually fine. For a graphics-heavy game or something that leans on advanced native APIs, write native code.
  • Store review still applies. Apple rejects apps that feel like a thin website. Give the app something that belongs on a phone: sign-in, push notifications, offline-friendly screens, a clear purpose.
  • Developer accounts cost money whichever route you take: $99/year for Apple, $25 once for Google.
  • Mobile builds need Pro on Mythex. The Free plan builds and publishes the web version only.

For teams

If the app is for your staff rather than the public (a field-service checklist, an inspection form, a sales tracker), you may not need the public stores at all. TestFlight and Google Play internal testing are built for exactly this: up to 100 internal testers on each, no public listing. A web app added to the home screen is often enough too.

On Mythex's Business plan, a team shares one workspace with roles (Admin, Editor, Viewer), can make an app members-only so only signed-in colleagues open it, and can require Google Workspace sign-in for the company domain. Plans and prices are on the pricing page.

The takeaway

ChatGPT and Claude can write a mobile app. On their own, they can't ship one. The code is the easy part now. What stops people is the backend, the build machine, the signing keys and the store rules. Pick your route by who will handle those four things: you with a coding agent and a Mac, a build service you configure, or a builder that runs the pipeline and leaves you only the accounts and the review.

Top comments (0)