Shopify Just Left React Native. Here's Why That Doesn't Mean You Should.
Shopify is moving from React Native back to native Swift and Kotlin after 5 years. Here's why that's a Shopify-scale decision, not a verdict on the framework.
On September 10, 2026, Shopify announced that native is now the future of mobile at Shopify. After years of being one of React Native’s loudest public champions, Shopify is moving its mobile apps back to native Swift and Kotlin.
That is real news. It deserves more than a shrug.
In 2020, Shopify published React Native is the Future of Mobile at Shopify and went all-in on the framework across its mobile work, including the Shop app. For a lot of developers, “Shopify React Native” became one of the strongest examples you could point to when defending React Native at serious scale.
So yes, this is a notable reversal. But if your search history now includes “is React Native dying 2026”, slow down. Shopify’s decision is important. It is not a universal verdict.
What Shopify Actually Said
The key detail is that Shopify did not describe React Native as a technical failure.
Shopify’s post says the original reasons for adopting React Native were practical: build features once, let more developers contribute across the stack, and avoid constantly chasing feature parity between iOS and Android. According to Shopify, React Native delivered those benefits. Their apps were fast. Their apps were stable. The tradeoff made sense for years.
What changed was the cost model.
Shopify says AI coding agents have made native development cheaper for their specific organization. Maintaining Swift and Kotlin codebases still means maintaining two codebases, but agents can now help with implementation, translation, tests, reviews, and parity work. That lowers the cost of duplicate native work enough that Shopify is willing to take the native path again.
The Shop app is the headline example. In a separate migration writeup, Shopify says the team moved from proof of concept to fully rebuilt native apps, published in the app stores, in 12 weeks with AI-assisted development.
That is impressive. It is also very Shopify-shaped.
This Is A Shopify-Scale Calculation
Shopify is not a two-person startup trying to get an MVP into the App Store before funding runs out. It is not a small agency deciding whether one JavaScript-heavy team can maintain both platforms. It is not a solo developer coming from React who wants the lowest-friction path into mobile.
Shopify has large mobile apps, mature engineering systems, native specialists, internal tooling, strong review culture, and enough organizational muscle to build custom agent workflows around its own codebase. It can afford to ask, “What if we rebuild this entire app natively?” and then actually staff the answer.
Most teams cannot copy that context.
For many companies, the original React Native argument still holds: one product team, one shared feature implementation, one React and TypeScript mental model, and targeted native code only where the app needs it. That is not a toy advantage. It can decide whether a team ships in three months or spends six months trying to keep two apps in sync.
That is why one company’s reversal should make you think, not panic.
React Native Did Not Freeze In Time
Another mistake is treating this like Shopify left the same React Native that existed in 2020 or even 2023.
React Native has changed a lot. The New Architecture brings Fabric, JSI, and TurboModules into the center of the framework. The official React Native docs describe the New Architecture as work designed to unlock higher-quality experiences, faster JavaScript/native interfacing, synchronous layout improvements, and better support for modern React features. Ecosystem work around Nitro Modules is also pushing native module development toward faster, more type-safe JSI-based bindings.
None of this means React Native is magic. You can still build a slow React Native app. You can still ship dependency mess, weird navigation, poor startup time, and native-module pain. But the framework is not standing still while native platforms evolve.
Meta also continues to invest in React Native. The official React Native showcase still highlights React Native across Meta products and major apps, including Microsoft apps like Teams. Discord has been working through React Native’s New Architecture at real production scale. Coinbase has publicly written about its React Native mobile work. Bluesky’s public app repository describes its Web, iOS, and Android app as a React Native application.
And beyond those, production React Native usage is still associated with companies such as Bloomberg, Tesla, Walmart, and Pinterest. As of September 13, 2026, there is no comparable public announcement from Discord, Coinbase, Microsoft Teams, Bloomberg, Tesla, Walmart, Pinterest, or Bluesky saying they are abandoning React Native.
That matters because ecosystems are not judged by one logo leaving. They are judged by the shape of ongoing investment, migration paths, tooling, community pressure, and whether real teams can still ship real products.
The Career Question Is Different
If you are learning mobile development from a React or JavaScript background, Shopify’s decision should not scare you away from React Native.
React Native is still the lowest-friction path from React into mobile. You bring over components, state thinking, TypeScript, hooks, data-fetching patterns, testing habits, package management, and a lot of frontend intuition. You still need to learn mobile fundamentals: app lifecycle, permissions, push notifications, navigation stacks, accessibility, deep links, store releases, performance, and when to drop into native code.
But you are not starting from zero.
That transferable-skill advantage does not disappear because Shopify has enough scale and AI tooling to justify a different tradeoff. A developer with React skills can still become productive in React Native faster than they can become equally productive in both SwiftUI and Jetpack Compose.
Learning native is valuable. I am not arguing against Swift or Kotlin. In fact, the best React Native developers eventually learn enough native development to debug the platform boundary with confidence. But that is different from saying every React developer should abandon React Native and learn two native stacks before building anything.
AI Cuts Both Ways
The most interesting part of Shopify’s announcement is the AI argument. Shopify is saying coding agents changed the economics of native development. That is believable.
But “AI favors native” is too simple.
AI also makes React Native development faster. It can generate boilerplate, scaffold screens, write TypeScript types, build form states, create tests, explain native module errors, compare iOS and Android behavior, help bridge native APIs, and debug upgrade issues. For a React Native team, AI can reduce the cost of the exact work that often made mobile development feel slow.
The difference is where the leverage lands.
At Shopify’s scale, AI may reduce the pain of maintaining two native codebases enough that native wins. At a smaller company’s scale, AI may make one React Native team even more productive because the team can move faster without splitting product work across two platform teams.
Same tool. Different math.
This is why the right question is not “Did AI make native better than React Native?” The better question is, “For our team, our app, and our constraints, where does AI reduce the most expensive work?”
So Should You Leave React Native?
Only if your own evidence says so.
If your app is extremely platform-integration-heavy, depends on deep OS features, needs specialized background behavior, has intense performance requirements, or already has strong Swift and Kotlin teams, native may be the better long-term choice.
If your app is mostly product UI, shared business logic, forms, feeds, messaging, dashboards, ecommerce flows, content, payments, maps, media, or API-driven workflows, React Native can still be a very practical decision.
The practical takeaway is boring, which is usually where good engineering lives: measure your own situation.
Look at your team size. Look at your timeline. Look at your existing skill base. Look at how much code truly needs to be platform-specific. Look at your app’s performance profile on real devices. Look at your dependency risk. Look at the cost of keeping iOS and Android at feature parity. Then decide.
Shopify leaving React Native is a serious signal that AI is changing mobile engineering economics. It is not proof that React Native is dying in 2026.
Do not let one company’s headline choose your stack for you.