You’ve probably spent the last five years defending your mobile tech stack. Maybe you fought in the trenches of React Native, arguing that write-once-run-anywhere was the only sane economic choice. You were right. But yesterday’s smartest decision is today’s legacy code.
Shopify just announced they are abandoning React Native and going back to native iOS and Android. The internet’s immediate reaction was a collective, smug validation: “I told you native was better.”
But that’s not the real story. The real story is much more unsettling.
Shopify didn’t reverse course because React Native failed. They reversed course because AI just changed the math.
Back in 2020, cross-platform made perfect economic sense. You could write one codebase, deploy it everywhere, and save a fortune on developer salaries. It was a brilliant, rational decision. But in 2024, Large Language Models (LLMs) can write, refactor, and translate native code at a fraction of the cost.
Consistency is the enemy of rationality. A decision can be 100% right when you make it, and 100% right to abandon five years later.
The dirty secret of React Native was that you always ended up dropping into native code to do anything interesting or optimized anyway. You were paying a complexity tax for an abstraction layer. The only reason the industry tolerated it was the economic moat of cross-platform efficiency.
AI just blew up that moat.
AI didn’t just change how we write code; it changed the fundamental economics of what we choose to build with.
If you are still clinging to React Native or Flutter today, you are defending an assumption that AI has already dismantled. You are paying an abstraction tax for a discount that no longer exists. Native development is cheaper now because AI is doing the heavy lifting, eliminating the need for a bridge between your JavaScript and the native UI.
This triggers both validation and deep unease. We feel validated because native was always technically superior. But we feel unease because if Shopify—a company that literally wrote the book on scaling React Native—can walk away from a massive stack overnight, what else is on the chopping block?
The wheel of fashion turns once more in tech, but this time it isn’t driven by developer preference. It’s driven by a first-principles reevaluation of what code costs. The tradeoff between cross-platform efficiency and native quality has shifted dramatically.
Anyone choosing a mobile stack today needs to update their framework. Yesterday’s “right answer” is today’s liability. The question isn’t whether your current stack still works. The question is whether the economic reason you chose it still exists.
FAQ
Q: Isn't this just Shopify's internal politics, not an industry trend?
A: No. Shopify's engineering team explicitly cited LLMs changing the core assumptions of their 2020 decision. When a massive e-commerce platform rewrites its app from scratch, it's not politics; it's a calculated economic shift.
Q: Should I immediately stop using React Native or Flutter?
A: If your team is highly specialized in it, no. But if you're starting a new project, you need to factor in AI-assisted native development. The cost savings of cross-platform are shrinking by the day.
Q: Won't AI just make React Native better too?
A: Yes, but AI improves native code more because native code has better training data and no abstraction layer overhead. AI closes the gap from the bottom up, making the cross-platform abstraction layer redundant.