React Native or Flutter? A Project-by-Project Decision Guide
Both frameworks are used in production; the right question is not "which is better" but "which one for this project". Current versions, the architectural difference, OTA updates with Expo, and a decision table.
There is no overall winner; the project decides. If your team knows JavaScript/React, web and mobile come from the same team, or you want to ship small fixes without waiting for store review, choose React Native + Expo. If you need pixel-identical, custom-drawn UI on every platform or one codebase for mobile, desktop and embedded, Flutter leads.
We build mobile apps with React Native and Expo. This article says plainly why, and when we would recommend Flutter instead. For how we work: React Native app development.
Current versions
| Fact | React Native | Flutter |
|---|---|---|
| Built by | Meta (since 2015) | Supported by Google, maintained with the community |
| Language | TypeScript (default for new projects) or JavaScript | Dart |
| Latest stable | 0.87 | 3.47 |
| UI | The platform's own native UI components | Its own rendering engine (Impeller) |
| Targets | iOS, Android; separate initiatives for Windows, macOS and web | Mobile, web, desktop, embedded |
Versions checked on the official sites on October 6, 2026. On the Expo side, the latest stable release is SDK 57 (React Native 0.86), with SDK 58 in beta.
How they differ
React Native: React components render to the platform's native UI, so your app uses the same native APIs as other apps. Since 0.76, the New Architecture is enabled by default in every project. It removes the asynchronous bridge between JavaScript and native code and replaces it with JSI (JavaScript Interface).
The React Native team recommends starting new apps with a framework such as Expo. Expo brings cloud builds (EAS Build), store submission (EAS Submit) and over-the-air updates (EAS Update) together.
Flutter: draws every screen with its own engine. Since 3.27, Impeller is the default renderer on iOS and on Android API 29+, and the only one on iOS. The UI is drawn the same everywhere, following your design rather than platform components. The language is Dart, a real learning cost for a JavaScript team.
Updates without store review (OTA)
Expo's EAS Update ships the non-native parts of an app (JavaScript, styling, images) without going through store review. Users get the update the next time they open the app.
The limits: changes to native code or native dependencies, permissions, or the Expo SDK version need a new build. Updates still have to follow App Store and Google Play guidelines.
When React Native leads
- The team already knows JavaScript, TypeScript or React.
- A website or web admin panel comes from the same team; React knowledge and some code can be shared.
- Shipping small fixes without waiting for store review matters (EAS Update).
- You want each platform to use its own native UI components.
When Flutter leads
- The brand UI must look identical, custom-drawn, on both platforms.
- Animation-heavy interfaces that need custom drawing.
- The same codebase should target desktop or embedded devices as well as mobile.
- The team knows Dart, or has time to learn it.
Performance
Both make performance claims, but neither official site gives a neutral "this one is faster" benchmark. For screens that update constantly (live charts, animated maps), build a small prototype of your own scenario and measure it.
In e-commerce, booking and productivity apps, slowness usually comes from architecture rather than the framework: needless re-renders, large lists and network calls.
Integrations: check the SDK first
Whether a payment, e-invoicing or banking provider offers an official package for React Native or Flutter varies by provider. Before choosing a framework, check what the services you depend on officially support. Without an official package, the integration has to be written as a native module, which adds time.
Other options
| Option | What is shared | When |
|---|---|---|
| Native (Swift + Kotlin) | Nothing; each platform is separate | Heavy 3D, advanced AR, low-level hardware access |
| Kotlin Multiplatform | Business logic, data models, networking; UI optional (Compose Multiplatform) | Kotlin teams that want to keep native UI and share logic |
| Capacitor | A web app written in JavaScript, HTML and CSS | A web team bringing an existing app to the stores |
Decision table
| Your situation | Pick | Why |
|---|---|---|
| The team knows JavaScript/React | React Native | Same language and React model |
| Web and mobile come from one team | React Native | React knowledge and some code are shared |
| Small fixes must ship without store review | React Native + Expo | EAS Update delivers non-native changes directly |
| The UI must be drawn identically everywhere | Flutter | Its own engine (Impeller) draws every screen |
| Mobile + desktop + embedded from one codebase | Flutter | All are official targets |
| A local payment or e-invoicing SDK is critical | Check the SDK first | The platform with an official package wins |
| Native UI is a must, logic should be shared | Kotlin Multiplatform | Shares code without replacing native UI |
| Your tech lead has a clear preference | Let it weigh in | Teams carry less risk with tools they know |
Common misconceptions
- "The bridge makes React Native slow." The New Architecture, default since 0.76, removed the asynchronous bridge.
- "Flutter will be abandoned." Flutter is supported and used by Google; the latest stable release is 3.47.
- "One codebase means half the cost." Most design, business logic and testing happens once, but store processes, platform-specific behaviour and device testing still happen for each platform.
- "OTA means I never need the stores." No: native changes need a new build, and updates must follow store guidelines.
The right question is not "which is better" but which tool lets this team ship this product on this schedule with the least risk.
Frequently asked questions
Is React Native or Flutter faster to build with? The one your team already knows. React Native for a JavaScript/React team, Flutter for a Dart team.
Do I have to use Expo? No, but the React Native team recommends a framework like Expo for new apps.
What if Flutter is the better fit for my project? For most business apps we find React Native + Expo the right call; if Flutter or native fits your project better, we say so at the quote stage.