expo-web-to-native

There is no transpiler — you migrate incrementally with Expo. Scaffold an Expo Router shell mirroring your routes, wrap every screen as a DOM component so the app runs on day one, then redesign screens natively in priority order using @expo/ui and Expo Router.

Use Expo DOM components ('use dom') to run existing web UI inside native routes as a temporary shell. For permanent screens, port idioms using the false-friends mapping: div becomes View, onClick becomes onPress, localStorage becomes expo-sqlite, and relative fetches need absolute URLs.

For physical goods and services, use @stripe/stripe-react-native with PaymentSheet. For digital goods or subscriptions, Apple and Google require in-app purchases via RevenueCat — shipping Stripe.js for digital goods gets the app rejected, so decide this at assessment time.

Expo Router is file-based like the Next.js App Router, and route trees map almost 1:1 — [id]/page.tsx becomes [id].tsx. Differences: useLocalSearchParams replaces useSearchParams, router.replace replaces redirect(), and layout routes must be native, never DOM components.

A green expo export only proves the screen bundles, not that it renders. Verify by running both apps: capture the web original with agent-browser and the native screen with argent or simctl, then compare content and behavior for the same route.

If you have no existing web repo and are building native fresh, skip the migration steps entirely — just use expo-router and the false-friends idiom map. Also keep presentational low-value screens in the DOM webview rather than nativizing everything, since each DOM screen carries a ~2 MB web runtime.