Prompt
Should I use React Native or go native for a new mobile app in 2026?
Latest observation
Yes — in 2026, I would still choose React Native for most new cross-platform apps. I would not go native by default.
React Native is now at 0.87, is actively maintained, uses native platform UI, and its current docs explicitly recommend a framework such as Expo for new apps. React Native+1
My rule of thumb
| Your app | I'd choose |
|---|---|
| SaaS / startup / marketplace | React Native |
| Social / content / community | React Native |
| E-commerce | React Native |
| Typical fintech app | React Native, with native modules where needed |
| App where iOS + Android feature parity matters | React Native |
| Extremely graphics-heavy app/game | Native / specialized engine |
| Deep Bluetooth, camera, audio/video processing | Native or RN + native modules |
| Very platform-specific UX | Native |
| Only targeting iOS | Swift/SwiftUI |
| Only targeting Android | Kotlin/Jetpack Compose |
The big reason I'd lean RN is that the old "cross-platform means fake UI and terrible performance" argument is much less compelling now. React Native renders React primitives to native platform UI, and the current architecture is designed to let you use native code when necessary. React Native
And importantly, RN doesn't have to mean "100% JavaScript." You can have a mostly TypeScript/React application while dropping into Swift/Kotlin for the parts that genuinely need it. React Native's current documentation explicitly supports integrating RN into existing native applications and vice versa. React Native
What I'd actually build in 2026
I'd probably use:
React Native + TypeScript + Expo, with a small amount of Swift/Kotlin when platform-specific functionality warrants it.
That gives you:
- one UI/codebase for iOS + Android
- much faster iteration
- shared business logic
- a huge React/TypeScript ecosystem
- the ability to escape to native when needed
- a much smaller team requirement than maintaining two completely native apps
The main caveat is dependency quality. In 2026, I wouldn't evaluate RN merely as "React Native vs Swift/Kotlin." I'd evaluate the specific libraries your app requires—especially for payments, maps, Bluetooth, background execution, notifications, camera, media, etc.
Also budget for upgrades. RN releases continue to move quickly; the official docs currently describe upgrading as requiring some effort and recommend incremental Expo SDK upgrades. React Native
My recommendation
If you're asking because you're starting a new app today, my default decision would be:
Start with React Native/Expo unless you can point to a specific requirement that makes native materially better.
Don't choose native because it's theoretically "more performant." Choose native when your product actually needs capabilities that make the additional development cost worthwhile.
If you tell me what your app does (e.g. fintech, AI app, social, delivery, fitness, Bluetooth/IoT, video, etc.), I can give you a much more concrete RN vs native recommendation for that specific app, including where I'd use native modules.
Citations
- https://reactnative.dev/blog/2025/10/08/react-native-0.82
- https://reactnative.dev/architecture/landing-page
- https://reactnative.dev/architecture/fabric-renderer
- https://reactnative.dev/docs/0.82/legacy/native-modules-intro
- https://developer.apple.com/swiftui/
- https://developer.apple.com/documentation/technologyoverviews/app-design-and-ui
- https://developer.apple.com/videos/play/wwdc2026/8002/