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. Two of them, react-native-skia and flash-list, are being handed off to new maintainers. The third, restyle, will be archived at the end of 2026 because it has a smaller user base than the other two.

Why it matters

For six years, the standard advice for most teams building a mobile app was to pick one codebase over two unless you had a specific reason not to. Shopify’s post is a real-world example of a large engineering org saying that advice no longer automatically holds, because AI coding agents can now absorb the duplicate implementation, translation, and testing work that used to make two codebases expensive.

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, flash-list, or restyle should also note the transition, since restyle’s archival at the end of 2026 means it won’t receive further updates from Shopify.

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