Shopify ditches React Native for native apps again — and blames AI for the U-turn
The e-commerce giant says coding agents have made building twice in Swift and Kotlin cheaper than maintaining one shared codebase, but the claim is doing a lot of heavy lifting.
Shopify is tearing up its mobile playbook for the second time in six years. Having switched to React Native in 2020 to avoid building every feature twice, the company now says it is heading back to writing native apps in Swift for iOS and Kotlin for Android. The stated reason isn’t that React Native failed — Shopify is explicit that the framework “worked well” and remains “an excellent framework”. The reason, apparently, is that AI coding agents have got good enough to make writing (and maintaining) two separate native codebases cheaper than propping up one shared one.
What Shopify is actually claiming
The company’s engineering team says the 2020 decision rested on three benefits: not building the same feature twice, letting backend-leaning developers dabble in mobile, and cutting down time lost to feature parity issues between platforms. All three held up, according to Shopify. What changed, it says, is the cost side of the equation — as of a January 2025 update the plan was still to keep investing in React Native, but by September 2026 the calculus had reportedly flipped because large language models had “dramatically” improved at writing native code.
That’s a striking claim, but it’s worth being clear about what’s confirmed and what isn’t. Shopify’s post confirms the switch is happening and gives the headline justification. What it doesn’t lay out in detail — at least not in the material published so far — is hard data: no benchmark showing coding-agent-assisted Swift/Kotlin development actually costs less than shared React Native work, no timeline for the migration, and no breakdown of how many of Shopify’s apps or how many of its reported 3,000-odd engineers this touches.
Why the sceptics on Hacker News aren’t convinced
The discussion thread racked up hundreds of comments, and a fair chunk of the scepticism isn’t about AI at all — it’s about Shopify’s engineering organisation itself. Commenters pointed out that Shopify reportedly employs around 3,000 engineers, compared with roughly 60 who built the first version of Chrome or the 150 credited on GTA 5 (including GTA Online). Others pushed back, noting that comparing a single app’s launch team to an entire company’s headcount, spread across web, backend, infrastructure and more, isn’t a fair fight. The broader point stands, though: a company known for a famously large and, to some critics, unwieldy engineering function reversing a major architectural bet is as much a story about internal management as it is about AI capability.
So who does this actually affect
Nobody using Shopify’s storefront or merchant apps is going to notice anything from this decision directly — a well-executed native rewrite should, if anything, be invisible to shoppers and sellers. This is squarely an internal engineering and hiring story: it affects Shopify’s mobile developers, who will presumably need deeper native platform skills again, and it’s a data point for other companies weighing up React Native, Flutter or native development, especially those leaning on AI coding tools to lower the cost of maintaining multiple codebases.
The takeaway
Shopify has made a real, checkable decision to move back to native mobile development, but the justification — that AI coding agents have quietly rewritten the economics of cross-platform development — is currently an assertion from the company itself, not an independently verified fact. Worth watching for how the migration actually plays out, and whether other engineering teams follow suit for the same stated reason, rather than taking Shopify’s framing as proof that AI has already solved mobile development’s oldest trade-off.