Shopify announced on its engineering blog on September 10 that it is moving its mobile apps from React Native back to Swift and Kotlin, because coding agents changed the core assumption behind the 2020 decision.
Key facts
- When: Migration has started; no completion date announced
- Who it affects: React Native developers directly. For merchants it's indirect — the Shopify admin app's release cadence and feel will shift
- What to do: Nothing on the merchant side. Teams using FlashList, Skia or Restyle should read the open-source handover plans
What happened
Shopify went all-in on React Native in 2020 for three reasons: stop building the same feature twice, let developers work across the stack, and spend less time chasing feature parity. The author wrote in January 2025 that React Native's future was bright, and says that was true given what they knew then. What changed is model capability. Shopify has used LLMs to build software since 2021, and by late 2025 the models had them questioning whether building twice still meant twice the work. The team prototyped by rebuilding several core parts of its biggest apps in Swift and Kotlin with LLMs, and found agents could implement an Android feature using the iOS version as reference and vice versa, help developers contribute outside their primary stack, and cut the cost of maintaining parity through shared specifications, tests and review checkpoints. The post is explicit that native still means maintaining two platforms and that cost hasn't disappeared — React Native apps can be fast, and theirs are. What changed is that the advantage of sharing an implementation shrank while the advantages of building per platform remain. On open source: Shopify sponsors React Native Skia through the end of 2026, its maintainer will fork and republish under a new name in the coming months and the original repo will be archived; FlashList, at roughly 2M downloads a week, will keep getting critical compatibility fixes while Shopify discusses long-term stewardship with several companies; Restyle is being archived.

What it means for independent store owners
There's no operational action here, but it's the most instructive business judgement about AI adoption published this year, because of its shape: a company publicly reversing a successful technical decision — not because the old approach got worse, but because the assumption underneath it changed. That reasoning transfers directly. Plenty of trade-offs in the DTC playbook exist purely because labour was expensive: one language version only, one set of creative assets, no detail pages for slow-moving categories, no support scripts in secondary languages. Those were the correct answers under a given cost structure. The cost structure moved, so the answers might have to. Note carefully what Shopify actually wrote: the cost did not disappear, two platforms still need maintaining. This is not "AI made duplicate work free," it's "duplicate work dropped from being the deciding factor to being an acceptable line item." Translated to your store: a second language version still needs proofreading and still generates support tickets. Only the generation step stopped being the bottleneck. One concrete watch item for Shopify merchants — release cadence and stability of the admin app may wobble during migration, so if you run daily operations from your phone, keep an eye on the release notes.