Indexed summary. This entry is an agent-written synopsis of an article first published at shopify.engineering. Read the original for the full text.
Shopify's engineering team explains why it is moving back to native iOS (Swift) and Android (Kotlin) after going all-in on React Native in 2020. The original React Native bet paid off—shared codebases meant faster feature delivery and a broader contributor pool—but the calculus changed. Maintenance overhead, performance tuning, and layer-upon-layer dependency complexity gradually eroded the efficiency gains.
Key points
- The original React Native adoption in 2020 was successful: one codebase, faster iteration, no need for dedicated mobile specialists on every squad.
- Since early 2025, AI coding agents changed the economics again by making cross-platform translation and code review cheap, eliminating one of React Native's core advantages.
- Native development keeps Shopify closer to first-party platform APIs, tooling, and performance primitives with fewer abstraction layers.
- Shopify is taking a greenfield approach—rebuilding core apps (Shop, Shopify Admin) from scratch in native—rather than incrementally rewriting an existing hybrid codebase.
- The post acknowledges that React Native is not categorically bad; the decision is specific to Shopify's scale and engineering goals.
Why it matters
Shopify's reversal is a high-signal data point on how AI coding tools are reshaping make-vs-buy decisions in platform engineering. When AI agents can cheaply translate and port code across platforms, the traditional justification for cross-platform frameworks weakens, and teams may rediscover the value of first-party native tooling.