Skip to content
Tech AI Wire

Shopify drops React Native for Swift and Kotlin

Shopify is rebuilding its apps in Swift and Kotlin 6 years after going all-in on React Native. Coding agents did enough of the porting to change the math.

By Tech AI Wire Team

3 min read

XLinkedIn
A Shopify Point of Sale card terminal standing on a plain gray studio backdrop.

By the numbers

to rebuild the Shop app, with 6 engineers
12 weeks
smaller Android app, a 37% cut
-109 MB
fewer crashes, per Shopify
10x
Shop app cold startup time
Android, React Native
4433ms
Android, native
2233ms
iOS, React Native
3200ms
iOS, native
2466ms

Shopify is rebuilding every mobile app it ships in Swift and Kotlin, six years after declaring React Native its future. The company's announcement on September 10, 2026 gives one reason above the others: "LLMs changed one of the core assumptions behind our 2020 decision."

That assumption was the cost of building the same feature twice. React Native existed at Shopify to avoid it. Coding agents now absorb enough of that duplicate work that the tradeoff flipped.

What changed in the arithmetic

Shopify adopted React Native in 2020 for three stated reasons: stop building the same features twice, let developers work across the stack, and spend less time chasing feature parity. It worked. InfoQ reports the apps reached load times under 500 milliseconds and crash-free sessions above 99.9%.

The company doubled down as recently as January 2025, reaffirming React Native after a five-year migration. Then, per its own account, late 2025 model improvements were large enough to reopen the question.

InfoQ reports that Head of Mobile Mustafa Ali reassessed the commitment and concluded the benefit-to-cost ratio of two native codebases now beat an abstraction layer. Shopify is blunt that the cost did not vanish: agents now do "enough of the implementation, translation, testing, and review work" that it stopped being decisive.

A second push came from the framework itself. Both InfoQ and Shopify note a React Native New Architecture refactor was coming, which would have meant extensive rework of native modules and rendering anyway.

The numbers from the rebuild

One engineer proved the approach in a week. Six engineers then rebuilt the Shop app, 300 or more screens plus widgets, an Apple Watch app and Siri Shortcuts, and shipped it in 12 weeks.

MeasureReact NativeNative
Android cold start4,433 ms2,233 ms
iOS cold start3,200 ms2,466 ms
Session stability99.5%+99.95%+
Android app size293 MB184 MB
iOS app size67 MB68 MB

Android gained the most: startup roughly halved, the download shrank by 109 MB, release builds got 75% faster, and feed scrolling hit 120 frames per second. Crashes fell about tenfold. iOS improved less, and the iOS app got 1 MB bigger.

The tooling they had to build first

The part worth copying is not the decision but the scaffolding. Shopify's migration writeup describes building a coding-agent extension called Pi, with separate subagents for reviewing the source app, documenting its behavior, planning the platform work, implementing features and reviewing parity.

They also built a debugging tool called Tardis that gives an agent structured access to a running app's events, logs and state. That is what let agents check their own work. They compared screenshots and event windows between the two apps at checkpoints, allowing for normal runtime variation.

One rule held the project together. Shopify's stated principle was that "Android and iOS must be at feature parity at all times." And the ordinary controls stayed: linting, tests, static analysis, performance checks and human code review.

What this means for developers

Read the losses before the wins. Moving to native cost Shopify over-the-air updates, because native releases go through app store review. If your release strategy depends on shipping a fix in an hour, that is the line item this decision spends.

The transferable lesson is in the tooling, not the framework. Agents did useful work here because Shopify gave them a way to observe a running app and compare behavior automatically. InfoQ reports the advice that follows. Isolate platform and UI code from stable business logic, so a model can test outcomes on a desktop rather than in a simulator. That pattern is the same one behind Bun's AI-driven Rust rewrite, where verifiable checkpoints mattered more than raw model quality.

Resist reading this as a verdict on React Native. Shopify says plainly that "native is the right choice for Shopify now, but React Native was the right choice for Shopify in 2020". InfoQ reports its advice to other teams: think native and React Native rather than picking a side. A company with 300-screen apps, six engineers to spare and a custom agent harness is not the median team.

If you depend on Shopify's open-source React Native work, check its status. Skia and FlashList have found new maintainers, and Restyle is being archived by the end of 2026.

Sources

  1. Native is now the future of mobile at Shopify - Shopify Engineering
  2. Migrating Shop app from React Native to native - Shopify Engineering
  3. Shopify Drops React Native for Swift and Kotlin as AI Changes Cross-Platform Development Tradeoffs - InfoQ

Related articles

The daily brief

Three to five stories a day, and what each one means for the people who build software. Free, no spam.