expo-web-to-native

Topics in the source

• Web to Native
• Principles
• Run it as a loop (recommended)
• The migration
• 1. Assess → write the worklist
• 2. Scaffold the shell
• 3. Shell it in DOM components — the day-one milestone
• 4. Strangle screens to native — by value

A web React app does not convert to native — there is no transpiler. It migrates, screen by screen, the way a strangler fig grows around a tree and slowly replaces it: stand up a native shell, run the whole web UI inside it on day one, then strangle each screen into native in priority order. This skill is the spine that orders the work; each step hands off to an existing Expo skill rather than re-explaining it. It operationalizes Expo's From Web to Native with React — read that for the why. Migrate, don't rewrite. Never big-bang it; every step keeps the app shippable. Ship on day one. The web UI runs in a DOM-component shell (step 3) before anything is nativized — that's the milestone; everything after is polish. Strangle by value. Nativize the hot screens; leave the rest in the webview. Each DOM screen carries a 2 MB web runtime — reason enough not to ship everything as DOM. Nativize means redesign, not reskin. A strangled screen should look like Apple/Google shipped it, not the web page reskinned. Reach for @expo/ui first - it renders real SwiftUI/Compose, so it feels exactly like the OS; styled RN primitives are the fallback for custom layouts only. Plus platform navigation (exp

This is an excerpt. Refer to the complete source and its current requirements.