Correction, October 13, 2026: Shopify was discussing future FlashList stewardship, rather than announcing a completed handoff. React Native Skia has a separate fork plan, and Restyle maintenance ends after 2026.
What happened
Shopify is rebuilding its mobile apps as separate native Swift (iOS) and Kotlin (Android) codebases instead of one shared React Native codebase, the company said on its engineering blog. React Native is a framework that lets developers write one set of code that runs on both iPhones and Android phones, rather than writing and maintaining two separate versions.
Shopify adopted React Native in 2020 for three reasons: to stop building the same features twice, to let developers work across iOS and Android without specializing, and to spend less time chasing feature parity between platforms. The company credits React Native as a strong platform for the six years it used it.
The reason for the reversal isn’t that React Native failed. It’s that the cost it was solving no longer requires the tradeoff. As Shopify puts it: “Native still means building and maintaining software on two platforms, that cost has not disappeared. What changed is that agents can now do enough of the implementation, translation, testing, and review work that it’s no longer the deciding factor it was in 2020.”
Shopify maintains three widely used React Native libraries. React Native Skia’s maintainer plans a fork under a new name, with Shopify sponsorship through 2026. Shopify is discussing long-term FlashList stewardship with other companies and will continue fixing critical compatibility issues. Restyle will be kept working through 2026, then Shopify will stop maintaining it.
Why it matters
A shared codebase reduces duplicate platform work. Shopify’s account shows how agents changed that calculation for a large engineering organization, through implementation, translation and testing. Its approach still includes shared specifications, review checkpoints and human approval.
That’s a narrower claim than “AI makes cross-platform frameworks obsolete.” Shopify isn’t saying React Native is worse software. It’s saying the specific cost that justified choosing it, in this case duplicate engineering effort, has shrunk enough that a large team with real resources can afford native again.
Who should care
Teams currently choosing between a shared codebase (React Native, Flutter) and separate native apps should treat this as a data point, not a verdict. Shopify has engineering resources most teams don’t. If your team is small, the duplicate-platform cost that cross-platform frameworks solve hasn’t disappeared just because agents exist.
Anyone maintaining or depending on React Native Skia, FlashList, or Restyle should also note the transition, since Restyle will no longer receive Shopify maintenance after 2026.
What builders should do next
Before deciding to split a shared codebase into native ones, estimate how much of the duplicate implementation and testing work an AI coding agent can actually absorb for your specific app, not in general. Shopify’s post describes implementation, translation, testing, and review work moving to agents. Confirm your own team actually gets similar help on those same tasks before assuming the tradeoff shifted for you too.
If you maintain a cross-platform library that Shopify sponsors, check whether it’s one of the three affected and plan your own maintenance path independent of Shopify’s continued involvement.
End of article