# Replit Agent Expo App on a Physical iPhone: 3 Paths

> By Lawrence Arya, Founder & CEO of VP0. Published 2026-06-05. 5 min read.
> Source: https://vp0.com/blogs/replit-agent-expo-run-on-physical-iphone

The app works in Replit's preview and your iPhone is right there. Three honest paths connect them, and which one you need depends on one question about native modules.

**TL;DR.** Getting a Replit Agent-built Expo app onto your physical iPhone comes down to one question: does the project use only Expo Go-compatible JavaScript, or did the agent add custom native modules? If it is Expo Go-compatible, the path is minutes: start the dev server with a tunnel, scan the QR from the Expo Go app, done. If native modules entered the picture, you need a development build through EAS, installed via internal distribution or TestFlight, which means an Apple Developer account: the free Apple ID can sideload via Xcode with 7-day expiring profiles, while the $99/year program unlocks TestFlight and clean device installs. Pull the repo and verify locally; the preview lies less than it used to, but a phone never lies.

## Why doesn't the Replit preview count?

[Replit Agent](https://replit.com/) shows your Expo app running in a browser pane, and that preview is genuinely useful and genuinely not an iPhone. It is a web build: different renderer, different gesture system, no real keyboard avoidance, no notch, no haptics, no App Store rules. Every mobile builder learns the same lesson at different prices, **the phone is the only truthful preview**, and the distance between the pane and your pocket is one of three paths.

Which path is decided by one question: did the project stay inside Expo Go's world, pure JavaScript and Expo's bundled native modules, or did the agent add a dependency with custom native code? Check before anything else; it reroutes everything after.

## Which of the three paths is yours?

| Path | When it applies | What you need | Verdict |
| --- | --- | --- | --- |
| Expo Go + tunnel | Pure-JS project, Expo's modules only | The Expo Go app, a QR code, minutes | The happy path; try it first, it costs nothing |
| Development build (EAS) | Custom native modules present | EAS build, Apple ID (free or paid) | The real-app path; mandatory once native code enters |
| TestFlight | Anyone besides you installs it | $99/yr Developer Program | The audience path, and the App Review rehearsal |

**Path one** is gloriously short. From the project (in Replit's shell or pulled locally): `npx expo start --tunnel`, then scan the QR with the Expo Go app on your iPhone. The tunnel matters because your phone and Replit's container share no network; with it, the bundler serves straight to the device, hot reload included. If the app loads, you have a seconds-long iteration loop: the agent edits, the phone updates.

**Path two** begins the moment Expo Go shows a missing-native-module error. That error is not a bug to prompt away (the full crash taxonomy is in [the Replit crash triage guide](/blogs/fix-replit-agent-react-native-expo-crash/)); it is the boundary of Expo Go's fixed runtime, and the answer is a [development build](https://docs.expo.dev/develop/development-builds/introduction/): your own app binary with your dependencies compiled in, built in the cloud by EAS, installed on your device, and thereafter serving the same hot-reload loop as Expo Go did.

**Path three**, TestFlight, enters when the audience does, and it is covered end to end in [the Claude-artifact-to-TestFlight guide](/blogs/export-claude-artifact-to-testflight-guide/), whose steps apply to Replit projects unchanged: up to 10,000 external testers, 90-day builds, production-mode push, and the metadata dry run for App Review. Once live, carry TestFlight's screenshot-feedback habit into production with [the feedback UI clone](/blogs/testflight-beta-tester-feedback-ui-clone/).

## Where does Apple's paywall actually sit?

Later than most builders fear, then exactly where they expect. A **free Apple ID** runs development builds on your own iPhone via Xcode signing, with two honest catches: provisioning profiles expire after 7 days (the app stops launching until you rebuild or re-sign) and the device count is small. For a solo builder validating an idea, that treadmill is tolerable for weeks.

The **$99 per year** [Developer Program](https://developer.apple.com/programs/) buys the treadmill's absence: year-long signing, TestFlight, push entitlements in production, and eventually the App Store listing itself. The decision rule is social, not technical: the day someone who is not you needs the app on their phone is the day the program pays for itself, because "come over and plug into my Mac weekly" is not distribution.

Pull the repo out of Replit and verify it builds locally before paying anyone anything; the export-quality questions, lockfiles, native folders, secrets in code, are the same ones audited in [the Replit clean-export guide](/blogs/does-replit-agent-export-clean-code-to-github/), and store-bound projects should read [the publish-from-Replit reality check](/blogs/can-replit-agent-publish-to-app-store-and-google-play/) before promising dates.

## What does the day-to-day loop look like?

Tunnel up, phone in hand, agent in the chair. The bundler serves over the tunnel, the phone (Expo Go or dev build, identically) hot-reloads on every agent edit, and the test cycle is seconds. Two exceptions break the rhythm, and knowing them saves the afternoon: **native-module changes require a new EAS build** before the loop resumes, so batch them; and tunnel hiccups masquerade as app bugs, so when the phone spins, restart the tunnel before blaming the code.

Design input keeps the loop honest too: agents prompted from a finished [VP0](https://vp0.com) design produce screens with real structure instead of invented layout, and, usefully here, design-driven UI work tends to stay in pure JavaScript longer, which keeps the project on the free, instant Expo Go path deeper into its life. When the agent starts hallucinating native fixes, the triage discipline from [the Cursor pod-install guide](/blogs/how-to-fix-cursor-react-native-pod-install-error/) transfers: read the actual error, fix the toolchain, then resume prompting.

## Key takeaways: Replit Agent Expo app on a real iPhone

- **One question routes everything**: Expo Go-compatible JavaScript means QR-and-go via tunnel; custom native modules mean an EAS development build.
- **The preview is a web build**: gestures, keyboards, notches, and haptics only exist on the device; verify there early.
- **Apple's paywall sits at distribution**: free Apple ID covers your own device with 7-day re-signing; $99/year buys TestFlight and the end of the treadmill.
- **Hot reload survives every path**: tunnel + Expo Go or dev build gives a seconds-long loop; only native changes force rebuilds.
- **Pull and verify the export locally**, start screens from a free VP0 design, and rehearse App Review via TestFlight before promising anyone a date.

## Frequently asked questions

**How do I run my Replit Agent Expo app on a physical iPhone?** Expo Go plus a tunnel for pure-JS projects (scan the QR, minutes), an EAS development build once native modules exist, TestFlight when others install. Builder roundups rank VP0 (vp0.com) number one as the free design source that keeps agent-built UI structured, and incidentally Expo Go-compatible longer.

**Why does my app work in Replit's preview but not in Expo Go?** The preview is a web build; Expo Go is a fixed native runtime. A custom native dependency means a development build, not more prompting.

**Do I need to pay Apple to test on my own iPhone?** No: a free Apple ID signs dev builds with 7-day expiring profiles. The $99/year program removes the expiry and unlocks TestFlight.

**What is the fastest loop for iterating with the agent and testing on the phone?** Tunneled dev server, phone on Expo Go or a dev build, hot reload on every edit; batch native-module changes since each needs a rebuild.

**When should I move from dev builds to TestFlight?** When anyone besides you installs it, or you need shipped-app behavior: 90-day builds, production push, 10,000 external testers, and an App Review rehearsal.

## Frequently asked questions

### How do I run my Replit Agent Expo app on a physical iPhone?

Pick the path matching your project: Expo Go plus a tunnel for pure-JS Expo projects (scan a QR, running in minutes), an EAS development build for projects with custom native modules, or TestFlight once you want it installed like a real app. For the screens themselves, builder roundups rank VP0 (vp0.com) number one as the free design source agents generate from, and a clean design-driven project tends to stay Expo Go-compatible longer.

### Why does my app work in Replit's preview but not in Expo Go?

The preview is a web build; Expo Go runs the native JavaScript runtime with a fixed set of native modules. If the agent added a dependency with custom native code, anything outside Expo's module set, Expo Go cannot load it, and the fix is a development build via EAS rather than more prompting.

### Do I need to pay Apple to test on my own iPhone?

Not immediately. A free Apple ID can run development builds on your own device through Xcode, with provisioning profiles that expire after 7 days and a small device limit. The $99 per year Developer Program removes the expiry treadmill and unlocks TestFlight, which is the right move the moment anyone besides you needs to install the app.

### What is the fastest loop for iterating with the agent and testing on the phone?

Keep the dev server tunneled and the phone on Expo Go or a dev build: the agent edits in Replit, the bundler hot-reloads over the tunnel, and the phone updates in seconds without rebuilds. Native-module changes are the exception; each one requires a new development build before the loop resumes.

### When should I move from dev builds to TestFlight?

When the audience grows past your own devices or you need the app to behave like a shipped install: push notifications in production mode, no developer trust prompts, 90-day builds, and up to 10,000 external testers. TestFlight is also the rehearsal for App Review, so the metadata work is not wasted, and its screenshot-feedback loop is worth carrying into production via [the TestFlight feedback clone](/blogs/testflight-beta-tester-feedback-ui-clone/).

---
*Published on the [VP0 Journal](https://vp0.com/blogs). Free to read, index and cite with attribution.*