On September 10, 2026, Shopify published “Native is now the future of mobile at Shopify” and the Hacker News thread passed 1,200 points in a day. Shopify was the company that went all-in on React Native in 2020, built FlashList and React Native Skia, and wrote in January 2025 that the framework’s future was bright. So the question arrived in my inbox a dozen times that week: is React Native dead in 2026? We have shipped React Native apps and an SDK through every architecture change since 2019, and I think the honest answer has three parts. The framework is healthier than it has ever been technically. The reason one very large company left is real and worth understanding. And neither of those facts is the one that should decide your next project.
What Shopify actually said
Read the post itself, not the summaries. Mustafa Ali is careful: React Native “remains an excellent framework”, their apps are fast, and the 2020 bet “has been extremely successful”. The move back to Swift and Kotlin rests on one changed assumption. In 2020 the cost of building every feature twice was the deciding factor. By late 2025 Shopify’s coding agents could implement a feature on Android using the iOS version as a reference, keep parity through shared specifications and tests, and let developers work outside their primary stack. Once that cost fell, the advantages of native (closer to platform capabilities, fewer framework layers) won their internal comparison. That is a statement about a company with hundreds of mobile engineers, two mature native codebases they had never fully retired, and a serious agent infrastructure. It is not a benchmark of React Native. Shopify also committed to transitioning its open-source libraries cleanly, which is why React Native Skia moved to the unscoped react-native-skia package under William Candillon in October and shipped 3.0 there.
The same month, Nolan Lawson published a benchmark of how well agents build in different frameworks and made the point that most “better for agents” claims come with no evidence. Shopify’s post at least describes its experiment. Most of the “React Native is dead” takes that followed it did not.
The numbers in November 2026
I pulled these on November 1, 2026. Treat npm download counts as a trend, not a census; CI inflates every package.
| Signal | October 2025 | October 2026 |
|---|---|---|
react-native npm downloads, month |
18.2 million | 55.3 million |
expo npm downloads, month |
9.1 million | 42.1 million |
| Latest stable React Native | 0.82 | 0.88.1 (October 27, 2026) |
| Latest Expo SDK | 54 | 58 (October 15, 2026) |
Those two download lines tripled and quadrupled in twelve months. Whatever share of that is bots, the share did not change between the two Octobers. The framework released 0.86, 0.87 and 0.88 in 2026 with no user-facing breaking changes in any of them, and 0.88 shipped the SceneDelegate work that keeps apps launching on iOS 27 and Xcode 27, a platform requirement a dying project would have missed. Our upgrade guide walks the 0.87 to 0.88 diff; it is five files.
Governance: React Native is no longer a Meta project
In February 2026 the React Foundation launched under the Linux Foundation, and React, React Native and JSX are now owned by the foundation rather than Meta. The eight platinum founding members are Amazon, Callstack, Expo, Huawei, Meta, Microsoft, Software Mansion and Vercel. The repository already moved: releases are published at github.com/react/react-native. For the “what if Meta loses interest” question that has hung over React Native since 2015, this is the answer. Three of the eight founders (Callstack, Expo, Software Mansion) build their businesses on React Native specifically, and Microsoft ships Office, Teams features and Xbox surfaces on it. The framework’s future is no longer one company’s quarterly priority.
Where the ecosystem is strong
Judge a framework by what shipped in a random week. In the last week of October 2026: React Native 0.88.1 moved SwiftPM build settings out of project.pbxproj; Expo pushed a coordinated SDK 58 patch set and two EAS CLI majors with terminal trace viewing; React Native ExecuTorch 0.11 put llama.cpp-style sampling, 16k-context LLMs and depth estimation on device; React Native Paper opened its 6.0 alpha; Unistyles, Skia, react-native-screens, VisionCamera and Sentry all released. Nitro Modules made native modules cheap to write, the New Architecture is the only architecture since 0.82, and Expo’s EAS Observe now records native crashes with no setup. None of this is maintenance mode. The parts of React Native I fought in 2019 (bridge serialization, the upgrade grind, the third-party module lottery) are mostly gone.
We can say this from our own apps. We maintain the Ethora chat SDK for React Native and the app that ships on it, and the 0.86, 0.87 and 0.88 upgrades each took under an hour. The 2021 upgrades took days. That is the same framework measured by the same team, and it moved in one direction.
Where it is weak
Be honest about the other column. Hiring is harder than it was: the r/reactnative Layoffs and hiring thread from late October is full of experienced developers between roles, and some companies read the Shopify post as permission to stop opening React Native positions. Fragmentation persists at the edges: the right UI kit, the right styling engine (NativeWind 4 or the 5 release candidate, Unistyles, Tamagui) and the right navigation stack still require a decision a Flutter team does not make. Startup time and memory on low-end Android still trail a well-built Kotlin app, and anything that touches the newest OS surface (widgets, Live Activities, hinge-aware layouts) arrives weeks after the platform does. Agents do narrow the “build once” advantage, exactly as Shopify says. If your team is large enough to run two native codebases and your agent tooling is mature, the calculation changes. For most teams it does not.
The comparison people are really asking about
The “dead” question usually hides a choice between three options, and we have written each one up at length: Flutter vs React Native for the cross-platform rival (Flutter’s GitHub repository has over 180,000 stars; the two frameworks are at parity on most axes and differ on language and ecosystem), React Native vs Swift for the Shopify path, and React vs React Native for web teams wondering whether their skills carry over. The short version in late 2026: pick native when you have two platform teams already and the app’s value is in platform-specific capability; pick Flutter when your team prefers Dart and a single rendering engine; pick React Native when you have React developers, want to share code with a web product, or expect to ship a lot of UI quickly with Expo.
So is React Native dead in 2026?
No. A framework with 55 million monthly downloads, a neutral foundation with eight corporate members, three breaking-change-free releases in a year, and an on-device AI stack maturing inside it is not dead. What ended in 2026 is the period when React Native was the default answer for every mobile team regardless of size. Shopify showed that at the very top end, with agents doing the duplicate work, native can win again. Nolan Lawson showed that most of us have no data on which stack agents handle best. The rest of us should do what Shopify did, which is measure our own costs, rather than copy their conclusion.
FAQ
Is React Native still supported in 2026?
Yes. React Native 0.88.1 was released on October 27, 2026 under the React Foundation, with Meta, Microsoft, Amazon, Expo, Callstack, Software Mansion, Vercel and Huawei as founding members. Expo SDK 58 shipped in October 2026.
Why did Shopify leave React Native?
Shopify’s September 2026 post says coding agents reduced the cost of building each feature twice in Swift and Kotlin, so the main advantage of sharing an implementation shrank while native’s advantages remained. It explicitly calls React Native an excellent framework and its React Native apps fast.
Is Flutter or React Native better in 2026?
They are close. Flutter has a single rendering engine and Dart; React Native has JavaScript, React skills, web code sharing and Expo’s tooling. Team background usually decides it. See our detailed comparison.
Should I learn React Native in 2026?
If you know React, yes: the skills transfer directly, Expo makes the first app a day’s work, and the job market, while tighter than 2022, is far larger than any other cross-platform option.
Does Meta still use React Native?
Yes, Meta remains a founding member of the React Foundation and a core contributor, and React Native is used across its apps. Ownership of the project moved to the foundation in February 2026.