Flutter or React Native — which to pick for your first app

People usually argue about Flutter and React Native as if it were about languages: Dart versus JavaScript. That's not the real difference. The real one is what draws the button on screen.
React Native asks the system to show a real system button. Flutter paints its own, pixel by pixel, with its own engine. Everything else follows from that single decision: how it looks, what happens after an iOS update, and why one app weighs more than the other.
The fundamental difference
Flutter is written in Dart and carries its own graphics engine. Its official FAQ says so directly: Flutter doesn't rely on web browser technology nor on the set of widgets that ship with each device — it uses its own high-performance rendering engine. It also explains why: so the quality and flexibility of your app aren't limited by the built-in widgets. Flutter is "architected to drive pixels" instead of using them. Its component set is doubled — Material style and Cupertino, i.e. iOS style.
React Native is React for phones: the same JavaScript or TypeScript and the component logic you know from the web. But its View and Text unfold into real system views on the platform. Since version 0.76 the New Architecture is on by default: the old asynchronous bridge between JavaScript and native has been replaced with a direct interface where JavaScript holds a reference to a C++ object and vice versa.
An easy way to remember it: Flutter brings its own canvas, React Native works on someone else's.
The criteria that actually matter
No table here — just the honest axes where the decision really changes.
- Language and what you already know. React Native: JavaScript or TypeScript, React, npm — if you've touched the web, half your knowledge moves over. Flutter: Dart, a good language, but new to almost everyone, and you'll learn it from scratch.
- Look and feel. Flutter gives you an identical screen on both platforms — a plus for brand-led design, a minus when you want the app to feel native. React Native uses system components, so details like list behaviour or system text selection come free.
- OS updates. A new iOS ships with a refreshed control style, and a React Native app picks it up, because the controls are the system's. Flutter draws exactly what it drew before: visual updates arrive with Flutter versions.
- Libraries and native capabilities. Both ecosystems are mature. React Native has more ready-made wrappers from the JavaScript world; Flutter has more uniform package quality. Either way you'll eventually peek into native code: the SDKs for payments, maps and analytics live there.
- App size. Flutter carries its rendering engine, so an empty app is bigger. React Native starts leaner but puts on weight quickly with libraries. The gap is obvious on your first "Hello world" and nearly invisible on a real product.
- Where you can grow. Flutter officially targets iOS, Android, web and desktop from one codebase. React Native is most confident on phones — and your web app is probably going to be React anyway.
- How well AI writes this code. A quiet but real edge for React Native: JavaScript and React are the largest slice of what models were trained on. AI helps confidently with Dart and Flutter too, but guesses current package versions less often.
Who should pick what — bluntly
- You've touched the web (React, JS, TypeScript) — take React Native. Not because it's better, but because you won't be learning a mobile platform and a new language at once. One new hard thing at a time.
- You care about one branded design and lots of animation — take Flutter. Your own canvas means full control of every pixel on both platforms.
- You're starting from absolute zero with no web background — take Flutter. The on-ramp is friendlier: one language, one way to do most things, great docs, and fewer forks in the road like "which navigation library is correct this year."
- You need one platform and maximum performance — take neither. Swift or Kotlin will be simpler than cross-platform plus native patches.
And an honest caveat: the tool almost never decides the fate of a first app. Projects fail not because of Dart or JavaScript, but because nobody wanted the idea. Before arguing, it's worth re-reading the app versus website comparison — maybe what you need is a website.
Is Kotlin Multiplatform a third option?
A different kind. There you share the logic and write native UI per platform. Less savings on UI, but the UI is always the system's. A good choice when you already have a native app and want to stop duplicating business rules.
Can I mix in native code?
You can and you should — both technologies were built for it. Flutter and React Native both let you call platform-native code when no package exists. Treat it not as an emergency exit but as ordinary work: any framework covers the typical case, not every case.
Which is faster for a weekend prototype?
Whichever gets your screen onto a phone sooner. Both have hot reload and can run on a device without a full rebuild. If the difference isn't obvious, flip a coin and spend the half-day you saved on the idea itself.
The AI Architect 2027 course: step by step from computer basics to your own app and first customers. 543 short lessons on your phone.





