Claude Code and Expo: Building and Shipping React Native Apps
Short answer: Expo is one of the most productive targets for Claude Code because one TypeScript codebase produces iOS and Android apps and EAS handles builds and store uploads. Pin the Expo SDK version in CLAUDE.md, install packages with npx expo install, test in development builds rather than Expo Go, and treat over-the-air updates with release discipline.
On this page
Why Claude Code works well with Expo
Expo reduces a mobile app to mostly TypeScript and configuration, which is the terrain where coding agents are strongest. Claude Code can read the whole project, run the dev server, execute tests and type checks, and iterate on screens quickly. File-based routing with Expo Router makes the structure predictable, so the agent rarely gets lost in navigation code.
The second advantage is the build pipeline. EAS Build compiles iOS and Android binaries in the cloud, so a Mac is not strictly required for every step, and EAS Submit uploads to App Store Connect and Play Console. That shortens the distance between a working feature and a tester's phone.
Setting up the project so the agent stays on track
Most problems with Claude Code in Expo projects come from version drift. Training data contains many Expo SDK versions and older React Native patterns, so the agent may suggest APIs that were renamed or removed. Give it explicit context in CLAUDE.md.
- The exact Expo SDK version and whether the project uses Expo Router.
- A rule to add native packages only with npx expo install, which picks compatible versions.
- Preferred libraries for state, forms, storage and networking, so the agent does not introduce alternatives.
- Commands for type checking, linting and tests that must pass before a task is considered done.
- A note that native folders are generated by prebuild and should not be edited by hand, if you use continuous native generation.
Common mistakes coding agents make in Expo apps
Knowing the typical failure modes saves hours of debugging. The first is installing a library that requires custom native code and then testing in Expo Go, where it cannot run. Use a development build as soon as the app needs any native module beyond the Expo Go set.
The second is editing ios or android folders directly in a project that regenerates them with prebuild. Changes disappear on the next build. Native configuration belongs in app.json, app.config.ts or a config plugin, and Claude Code can write config plugins well when asked explicitly.
The third is permissions and usage strings. An agent may add camera or location access in code without the matching configuration in app.json, which leads to crashes on iOS and rejections in review. Make permission configuration part of every feature task.
Need a hand? apprat.io helps with exactly this. Book a call for free and get a clear plan in 15 to 30 minutes.
Building and submitting with EAS
Once the app works in a development build, set up release profiles and let EAS handle the heavy lifting.
- Define development, preview and production profiles in eas.json, each with its own environment variables.
- Configure bundle identifier and Android package name in the app config; they cannot change after publishing.
- Let EAS manage credentials or upload your own, and store them outside the repository.
- Run a production build for both platforms and install it through TestFlight and the Play internal testing track.
- Use EAS Submit to upload builds to App Store Connect and Play Console.
- Complete store metadata, privacy declarations and review notes before submitting for review.
Over-the-air updates: powerful, but needs rules
EAS Update can push JavaScript and asset changes to installed apps without a new store review. That is valuable for urgent fixes, and risky if used carelessly. An update that changes the native layer needs a new binary; an update pushed to the wrong runtime version can break apps in the field.
Apple's guidelines allow interpreted code updates as long as they do not change the app's primary purpose or bypass review for new features. A practical rule: OTA for bug fixes and copy changes, store releases for new features. Keep a staging channel, test every update there first and have a rollback ready.
From working build to maintained product
Claude Code and Expo get you to a store-ready app quickly. Keeping it healthy means upgrading the Expo SDK regularly, reviewing agent changes, testing on real devices and running releases on schedule. Skipping SDK upgrades for a year usually turns into a painful multi-version jump.
apprat.io provides that ongoing ownership: coding agents implement features, and named senior AI Code Engineers review every change, test on real iOS and Android devices and handle releases. The Claude Code-to-App module picks up existing Expo projects as they are, including SDK upgrades and native module issues. For the store side, appsubmitter.io can run submissions and rejection handling in your own accounts.
With apprat.io plans starting at 129 EUR per month including human AI Code Engineer hours and a 30-day free trial, it is easy to test whether the setup fits your Expo project. A free call helps scope the first steps.
Frequently asked questions
Should I use Expo or bare React Native with Claude Code?
For most new apps, Expo is the better choice because it reduces native configuration, offers cloud builds and keeps the agent working mainly in TypeScript. Bare React Native makes sense when you depend on unusual native SDKs or existing native code, though config plugins now cover many of those cases within Expo.
Can Claude Code run and test my Expo app?
Claude Code can start the dev server, run type checks, unit tests and linting, and read error output. It cannot tap through the app on a physical phone by itself, so manual testing or automated end-to-end tests on simulators and devices remain necessary before release.
Do I still need a Mac for iOS builds with Expo?
Not necessarily. EAS Build compiles iOS apps on cloud macOS machines, and EAS Submit uploads them. A Mac remains useful for running the iOS simulator and debugging native issues, but it is no longer strictly required for building and submitting.
Are over-the-air updates allowed by Apple and Google?
Both stores permit updating JavaScript and assets under conditions. Apple requires that updates do not change the primary purpose of the app or add features that bypass review. Use OTA updates for fixes and small adjustments, and ship new features through regular store releases.
