Flutter draws every pixel of your app itself. That one design decision explains how Flutter works under the hood, why a Flutter app looks the same on every device, and where it differs from React Native, which drives the platform’s own UI components instead. Almost everything that matters for the choice follows from it: which language your team writes, how the app looks and which developers you need.
This article explains how Flutter works under the hood, what changed in React Native with the New Architecture and how to choose between the two. The technical details were checked against the official documentation and release notes on November 11, 2026. ElevateX doesn’t build apps; it places IT freelancers who work with your team. That’s why you’ll also find below how to vet developers for both frameworks and what they cost.
How Flutter works under the hood (as of November 2026)
Flutter is an open-source UI framework from Google. The current stable version is Flutter 3.47, released on August 12, 2026. It ships with Dart 3.13 (Flutter release notes, Dart changelog, as of November 11, 2026).
Three layers: framework, engine, embedder
A Flutter app consists of three layers (Flutter architectural overview):
- Framework (Dart): This is where you write your app. You compose the UI from widgets, from a button to the layout. The Material and Cupertino libraries provide widgets in the style of Android and iOS.
- Engine (mostly C++): It renders the UI, lays out text and contains the runtime for the Dart code.
- Embedder: One layer per platform that anchors the app in the operating system and takes care of windows, input and the event loop. For Android it is written in Java and C++, for iOS and macOS in Swift and Objective-C, for Windows and Linux in C++.
The layers of Flutter, based on Flutter’s architectural overview, as of November 2026.
Rendering: Impeller has replaced Skia
The most important difference from React Native: Flutter doesn’t use the operating system’s UI components. It bypasses their libraries and draws every widget itself. That’s why a Flutter app looks the same on every device. And that’s why Flutter has to rebuild every system element that is supposed to feel native.
In the past, the graphics library Skia did the drawing. Today it is Impeller, a rendering engine built for Flutter (Flutter documentation on Impeller, as of November 11, 2026):
| Platform | Renderer |
|---|---|
| iOS | Impeller is the only supported renderer; switching to Skia is not possible |
| Android | Impeller is the default from API level 29. Older devices and devices without Vulkan fall back to the legacy OpenGL renderer |
| macOS, Windows, Linux | Impeller has been the default since Flutter 3.47. The option to turn it off is to be removed in a future release |
| Web | Still renders with Skia |
Impeller compiles its shaders when the engine is built, not while the app is running. According to the documentation, the goal is predictable performance.
Dart: one language, two compilers
You write Flutter apps in Dart. The language is type safe and has null safety: a value can only be null if you explicitly allow it (Dart overview). Two compilers matter for Flutter:
- During development, the code runs in the Dart VM with a just-in-time compiler. It recompiles changes incrementally and enables hot reload: the changed code lands in the running app and the state is preserved. Flutter cites reload times of under a second (Flutter FAQ).
- For release, an ahead-of-time compiler turns the code into machine code for ARM or x64. On the web, it becomes JavaScript or WebAssembly.
Dart handles concurrency with isolates. These are independent workers that don’t share memory and communicate only through messages.
Access to platform features
Flutter reaches the camera, sensors or a payment provider’s SDK in two ways: through platform channels, which pass messages between Dart and the platform-specific code, and through dart:ffi, which binds C-based APIs directly. Many features are available as ready-made packages on pub.dev. If the app needs a real native component, such as a map or a web view, Flutter embeds it in the widget tree as a platform view. For features that sit very close to the device, such as Bluetooth, additional native code may be needed, in Flutter and in React Native alike.
Platforms and existing apps
Flutter supports six targets: Android, iOS, web, Windows, macOS and Linux (supported platforms). You don’t have to rewrite an existing app to use it. With add-to-app, Flutter can be integrated into an existing app as a module, so that only parts of the app run on Flutter.
Advantages and disadvantages of Flutter
Advantages
- Consistent UI: Because Flutter does its own drawing, the app looks the same on every device. Custom designs and animations don’t depend on the platform’s UI components.
- One codebase for six platforms: Android, iOS, web, Windows, macOS and Linux.
- Short development loop: Hot reload shows changes in the running app without losing state.
- Compiled code: The released app runs as machine code, and Impeller compiles its shaders in advance.
- Testing built in: Flutter comes with unit, widget and integration tests (Flutter documentation on testing).
Disadvantages
- Native UI components are rebuilt: The Material and Cupertino widgets are replicas. New system designs therefore don’t arrive in the app by themselves. You’ll find a current example further down.
- The engine travels with the app: Every app contains the engine. Flutter puts this baseline at a few megabytes compressed (Flutter FAQ).
- Dart is less widespread: In the Stack Overflow Developer Survey 2025, 5.9 percent of respondents work with Dart and 66 percent with JavaScript. With Flutter, your team usually maintains an additional language.
- On the web, for applications only: Flutter recommends its web target for app-like experiences. According to the documentation, it is currently not suitable for static, text-rich pages, partly because the output doesn’t match what search engines need for indexing (Flutter web FAQ).
How React Native works (as of November 2026)
React Native comes from Meta. Meta released it in 2015 and has maintained it ever since (reactnative.dev). You write the app in JavaScript or TypeScript with React. Unlike Flutter, React Native doesn’t do its own drawing: the React components become native UI components of the platform. A text field is a real iOS or Android text field. So the app looks like the platform it runs on, and it can differ between iOS and Android.
The JavaScript code is executed by the Hermes engine. Hermes compiles JavaScript to bytecode at build time, which speeds up app startup (React Native documentation on Hermes). For new apps, React Native itself recommends using a framework such as Expo (getting started with React Native).
The New Architecture has been mandatory since 2025
React Native has replaced its foundations over the past two years. If you know the framework from earlier days, you know the bridge: an asynchronous channel through which JavaScript and native code exchanged messages. The New Architecture replaces the bridge with the JavaScript Interface (JSI), which lets both sides talk to each other directly and synchronously. It also brings a rewritten renderer and a new native module system (announcement of the New Architecture).
| Version | Released | What changed |
|---|---|---|
| 0.76 | October 2024 | The New Architecture is the default |
| 0.82 | October 2025 | First version that runs on the New Architecture only. The legacy architecture can no longer be enabled |
| 0.84 | February 2026 | Hermes V1 is the default engine. Legacy architecture code is no longer included in iOS builds |
| 0.88 | October 2026 | Current version; according to the release post, no breaking changes for app code |
Table as of November 11, 2026, based on the release posts on the React Native blog.
This matters when you look for developers: someone who last worked with React Native before 2025 may only know the legacy architecture, which current versions no longer support.
Platforms and existing apps
The core of React Native targets Android and iOS. Windows, macOS and the web are covered by separate projects such as React Native Windows, React Native macOS and React Native Web. Like Flutter, React Native can be added to an existing native app, for individual views or flows (integration with existing apps).
Flutter vs React Native compared
| Flutter | React Native | |
|---|---|---|
| Maintainer | Meta | |
| Language | Dart | JavaScript or TypeScript with React |
| UI | Its own widgets, drawn by the engine | The platform’s native UI components |
| Execution | Machine code compiled ahead of time | JavaScript in the Hermes engine, compiled to bytecode at build time |
| Look | The same on all platforms unless you build it differently | Follows each platform |
| Target platforms | Android, iOS, web, Windows, macOS, Linux | Android and iOS in core; Windows, macOS and web through separate projects |
| Current version (as of November 11, 2026) | 3.47 with Dart 3.13 | 0.88 |
| Adding to an existing app | Add-to-app | Integration with existing native apps |
| Apps listed in the showcase | Google Pay, NotebookLM, BMW, Toyota (Flutter showcase) | Facebook, Instagram, Microsoft Outlook, Shopify (React Native showcase) |
The table deliberately contains no performance figure. Performance depends on the app, the device and the version, and both frameworks have only just renewed their foundations: Flutter with Impeller, React Native with the New Architecture and Hermes V1. Older benchmarks therefore often describe a state that no longer exists.
What the usage figures say
How widely the two frameworks are used is harder to prove than many comparisons suggest. The Stack Overflow Developer Survey 2025 no longer lists Flutter and React Native separately. Earlier editions had a section of their own for them. What the survey does show is how many respondents did extensive development work with the underlying languages and technologies over the past year:
| Language or technology | Share of respondents in 2025 | Basis for |
|---|---|---|
| JavaScript | 66.0% | React Native |
| TypeScript | 43.6% | React Native |
| React (on the web) | 44.7% | React Native, same programming model |
| Dart | 5.9% | Flutter |
Source: Stack Overflow Developer Survey 2025. 31,771 people answered the question on languages, 23,678 the one on web technologies.
So for React Native you’ll find considerably more developers who already know the language and the programming model. That doesn’t mean they can build mobile apps: app stores, device diversity and native modules are a craft of their own. Conversely, Dart’s small share says nothing about the quality of Flutter developers.
Decision table: what fits your team?
| Your situation | Tendency | Why |
|---|---|---|
| Your team builds the web frontend with React and TypeScript | React Native | Same language, same tools, same way of thinking |
| The app has its own design and should look identical on iOS and Android | Flutter | Flutter does its own drawing, so the result doesn’t depend on the platform’s UI components |
| The app should feel like a native app on each platform | React Native | It uses the native UI components |
| Web and desktop should come from the same codebase as iOS and Android | Flutter | Six supported target platforms |
| An existing native app is to be extended step by step | Both work | Add-to-app with Flutter, integration with existing apps with React Native |
| The team has no experience with either Dart or React | Open | Then it comes down to which developers you can get and who maintains the app afterwards |
| Lots of device-level features such as Bluetooth, sensors or special SDKs | Open | Native code may be needed in both frameworks. Check beforehand which packages exist |
A current example: the new iOS 26 design
Apple’s “Liquid Glass” design in iOS 26 shows how far the technical approach reaches. Flutter draws its iOS widgets itself, so someone has to rebuild the new design. In June 2025, the Flutter team stated that it was not developing the iOS 26 design features in the Cupertino library for the time being. Since July 2025, the plan has been for that work to happen in packages split out of the framework. The corresponding issue in the Flutter repository is still open as of November 11, 2026.
In React Native, you can use the system’s own elements. For the glass effect, for example, there is Expo’s GlassView, which uses the native iOS element from iOS 26 onward.
If your app should follow Apple’s new system designs quickly, that speaks for React Native. If it has its own design anyway, it hardly matters.
What clients are currently asking ElevateX for
At ElevateX, Flutter and React Native are both currently rarely requested specifically. Sören Elser, founder and managing director of ElevateX, describes what clients look for instead: “The focus is currently far less on specific frameworks or a specific tech stack, and much more often on AI engineering, agentic engineering.” What he means is whether developers can build with AI support and have already done so in projects. “That pushes the tech stack and the frameworks people work with pretty far into the background.”
This is an observation from the requests ElevateX receives, not a finding about the market as a whole. Our reading for your decision: the framework is less often the bottleneck than the question of whether someone has already solved your app’s problem and how they work. The article What is Agentic Engineering? explains what AI-assisted development involves.
How to vet Flutter and React Native developers
How do you tell whether someone has real production experience? For Sören, one of the most useful questions is this: first describe your own project briefly and name the one or two main problems you’re currently struggling with. Then ask the developer “in which projects they have actually solved this issue before”, and have them “really explain hands-on how they solved the problem”.
You can follow up with questions based on the current state of the frameworks. These follow-ups don’t come from Sören; they follow from the sections above.
Flutter
- Which Flutter version did the last production project run on, and what changed with the move to Impeller?
- Which platform features did the person integrate themselves, through platform channels or
dart:ffi? Where was a ready-made package not enough? - How were the tests set up: unit, widget and integration tests?
React Native
- Has the person migrated an app to the New Architecture or started a project on it directly? What broke during the migration?
- With Expo or without a framework, and why?
- Which native modules did they write or adapt themselves?
If your team is mainly looking for someone who develops with AI assistance, you’ll find questions for that in the interview guide for agentic engineering.
What does a Flutter or React Native developer cost?
At ElevateX, the all-in hourly rate for the client for app and mobile freelancers is usually between €105 and €118 per hour. The range covers app and mobile roles as a whole; it is not broken down by framework. Billing is by the hour, with no minimum term and no minimum volume. Costs start on the first working day.
How long an app takes and how large the team needs to be can’t be answered in general terms. The article App Development Costs shows how to calculate the cost of your own project from roles, weeks and hourly rate.
The most common mistake when looking for app developers
Asked about the most common mistake companies make when looking for app developers, Sören says it is committing to a contract model, saying from the outset “I’m only looking for freelancers, or I’m only looking for permanent staff”, “before it’s even clear what kind of person I actually need for the task, and for how long”.
So clarify the task first, then the framework and the contract type. A permanent team and freelancers aren’t mutually exclusive here: Sören sees freelancers as “much more of a strategic tool” and says “it’s not an either-or”. In his view, a freelancer is the right choice where a result is needed at short notice, meaning someone would have to be working on the task within two to four weeks.
Requesting app developers for Flutter or React Native
ElevateX places freelancers only and doesn’t build apps itself. Once it’s clear which task needs doing, you get the first matching profiles through ElevateX, up to three, within 48 hours after your request has been finalized. Sören personally talks to every freelancer whose profile a client receives. Almost all freelancers placed by ElevateX speak German, around 90 percent by Sören’s estimate.
Conclusion
Flutter does its own drawing and in return delivers a consistent look on six platforms. React Native uses the platform’s UI components and suits teams that work with React and TypeScript. Decide based on the skills in your team, how demanding the UI is and which platforms you target. And vet developers on your concrete problem rather than on their list of frameworks.




![The Best Free Project Management Software [2024]](/_astro/free-project-management-software-featured-en.Cab8uzoy_HzD0Y.webp)
