Why the React Native bet is being unwound
Shopify went all-in on React Native in 2020 and the bet paid off: features were built once, developers without a mobile background could contribute, and the company stopped chasing feature parity. Three goals drove that decision — avoid building the same feature twice, let developers work across the stack, and spend less time on parity and more on shipping. React Native delivered all three. The team did sink significant time and resources into performance work, foundational improvements to the framework, and keeping up with updates and external dependencies, but those were acceptable tradeoffs.
The January 2025 assessment that React Native's future was bright was accurate for its time, and the framework remains excellent. What shifted is the cost side of the equation: coding models improved dramatically, and for Shopify's apps and team, writing the same feature in Swift and Kotlin no longer carries its old price.
Shopify has been using LLMs to build software since 2021, starting with feature implementation, bug investigation and fixes, and code review. As models improved, so did the complexity of work entrusted to them. By late 2025 they were raising a question the 2020 decision never had to answer: does building software twice still mean doing twice the work?
The company re-evaluated its mobile stack from first principles and prototyped. Rebuilding several core parts of its biggest apps in Swift and Kotlin with LLMs produced better results than expected. Agents implemented a feature on Android using the iOS version as reference and vice versa, helped developers contribute effectively outside their primary stack, and sharply cut the cost of maintaining parity through shared specifications, tests, and review checkpoints.
The two-platform cost has not vanished. What changed is that agents now handle enough of the implementation, translation, testing, and review work that this cost is no longer the deciding factor it was in 2020. Sharing implementation has lost relative advantage while the benefits of per-platform builds remain — closer access to platform capabilities and first-party tooling, with fewer framework and dependency layers between code and platform.
What happens to the open-source libraries
Shopify's published React Native libraries became the top choice in their categories, and the company says it wants a clean transition with no surprises.
- React Native Skia — Shopify continues sponsoring it through the end of 2026, and William Candillon continues work beyond that. He will fork the repo in the coming months and publish under a new name; the original repo will be archived when the transition completes. Updates will be posted along the way, and apps depending on the library are encouraged to sponsor it.
- FlashList — at roughly 2M downloads/week, it is the default way to render high-performance lists in React Native. Shopify will keep fixing critical compatibility issues while in discussions with several companies about long-term stewardship; interested parties can reach out to Mustafa Ali.
- Restyle — with a smaller user base, the repo is being archived. It will keep working through the end of 2026, after which maintenance stops. Forks are welcome, and Shopify will help with a handover if a team picks it up.
Greenfield over brownfield
Shopify's largest apps — Shopify, Shop, Point of Sale, Inbox — are used daily by millions of merchants and buyers. The team weighed gradual brownfield migration against rebuilding from scratch, the approach it had rejected when moving the other direction, since rewriting would take years and freeze feature work.
This time greenfield won clearly: LLMs are good at building Swift and Kotlin features with the React Native version as reference; a clean slate removes prior constraints; and prototypes showed substantially faster rebuilds than were possible before coding agents.
Shop was migrated first. With AI assistance, the team went from proof of concept to a fully rebuilt native app published in the app stores in 12 weeks. The Shopify app — 300+ screens, home and lockscreen widgets, an Apple Watch app, complications, Siri Shortcuts — is underway and ships later this year, with the remaining apps to follow.
Helix: structure against slop
Pointing an LLM at the React Native codebase and one-shotting native features does not work, even with upfront research frozen into specs and task files — the output is a mass of unmaintainable code that cannot ship. Shopify's answer is Helix, a system built around the assumption that the first output will be wrong.
A developer points Helix at a screen. It reads the React Native code and proposes ordered checkpoints — small slices reviewable in minutes. Each checkpoint must prove behavior with tests, match the running app in a visual review, survive two adversarial code reviewers, and get human approval before it is committed and the next begins. Feedback from every review is retained, so the loop grows more autonomous as migration proceeds.
Helix rebuilding a screen in the Shopify mobile app using Swift and Kotlin
Making agents fast on mobile
Simulator control has been the bottleneck for agentic work on mobile. Agents that could not reliably build, test, and iterate needed constant babysitting; custom tooling to reproduce, fix, and verify bugs autonomously was slow and brittle. React Native's hot module reload helps but does not solve the problem, because simulator control relies largely on the accessibility tree or screenshots to read state, act, and verify. Code changes take seconds while testing output takes minutes — and model quality is irrelevant if the work cannot be tested quickly.
Shopify is addressing this architecturally: business logic must be fully decoupled from UI and run headlessly on desktop, exposed to agents through a CLI. That lets them iterate in milliseconds rather than minutes without touching a simulator, inspecting app state, navigating sections, and performing actions. Agents can then work autonomously for hours.
Where simulator interaction is required, the CLI connects in a remote mode and drives the UI via commands without inspecting layout or the accessibility tree, enabling very fast operation and E2E tests.
Success criteria
Every app moves to Swift and Kotlin with AI throughout, but not by lowering the bar: each rebuild must meet or exceed current performance, stability, accessibility, and product quality. These are not the same apps translated into different languages — they are being rebuilt so humans and agents can understand, test, and change them quickly.
Migration is not the finish line. Success means teams deliver better experiences for merchants and buyers faster, measured by product velocity, app quality, and how much work agents complete autonomously. Shopify says it will publish deeper dives into Helix and the agent-addressable architecture, and it is hiring mobile engineers, infrastructure engineers, and developers working where AI and software engineering meet.
Crediting the ecosystem that made the React Native years work
Shopify frames its move as a matter of timing rather than a verdict on the framework: native is the right choice for Shopify now, while React Native was the right choice for Shopify in 2020. That earlier bet only paid off because of the people behind it, and the company closes by naming them.
Framework stewards and graphics tooling
The React Native team at Meta is thanked for stewardship of the framework, for listening to Shopify's feedback, and for collaborating closely over the years. Shopify credits its investments in architecture, performance, tooling, and community with making React Native substantially better today than it was.
William Candillon is credited with creating React Native Skia and pushing it well beyond what the team had imagined, redefining what graphics and animation in React Native could do.
Software Mansion is recognized for its work on Reanimated, for responding to feedback, and for helping solve some of the hardest animation and performance problems in Shopify's apps.
The internal effort
Hundreds of Shopify engineers took part in the transition — adopting React Native, migrating apps, building shared foundations, improving performance, maintaining integrations, and contributing back to the ecosystem.
Many of you became beginners again, challenged long-held assumptions, and made the transition successful while continuing to ship for merchants and buyers.
The wider community
The React Native community earns thanks for using Shopify's open-source libraries, contributing code, filing issues, questioning the company's decisions, and sharing what they learned — feedback that included, in Shopify's words, the spicy kind. It all made the work better, the company says.
The tools, lessons, and relationships built over the past six years will keep shaping how Shopify builds mobile apps. As for what comes next on the native side, the company says it is just getting started.



