Shopify Moves Off React Native, Backs Native Development as AI Coding Shifts the Calculus

Shopify has decided to abandon React Native and return to native iOS and Android development, a striking reversal of its 2020 commitment to the cross-platform framework. The shift reflects a reassessment by the company's mobile leadership, who now believe that the engineering case for maintaining separate native codebases has grown stronger than the case for using a shared abstraction layer—a conclusion driven largely by the rapid maturation of AI-assisted coding.

Why the Change#

Two specific forces prompted Shopify's reconsideration. The first was the looming need for a substantial overhaul: adopting React Native's New Architecture would have forced the team to rework native integrations, rendering logic, and the boundaries between shared and platform-specific code. Rather than pour resources into that refactor, leadership decided to explore whether a greenfield rewrite in native code might be more strategic.

The second factor was the leap forward in AI coding models. A single engineer validated the idea with a proof-of-concept in one week. Six engineers then rebuilt Shopify's flagship Shop app entirely—from empty canvas to production—in just 12 weeks. The team used Apple's SwiftUI and Google's Jetpack Compose, modern declarative frameworks that share enough conceptual symmetry to help AI agents work across both platforms while adhering to native design idioms.

Performance and Stability Gains#

The native rewrite delivered measurable improvements:

• Startup speed dropped 23% on iOS and 50% on Android
• Session stability jumped from 99.5% to 99.95%—a tenfold reduction in crashes
• Build times improved 75% on Android
• Android's native scrolling sustained 120 FPS without heavy manual tuning

An Important Caveat#

Shopify's framing invites scrutiny. The performance comparisons are measured against the old React Native architecture, not the newer one. Some developers have questioned whether upgrading to React Native's latest version might have delivered similar gains without the cost of a full rewrite.

One other real tradeoff emerged in community debate: over-the-air updates become far harder with native code. Every release must pass app store review, slowing release cycles—a friction point less familiar to teams steeped in web development culture, where rapid iteration is the norm. Native teams, by contrast, tend to invest more heavily in testing and validation precisely because rollbacks are expensive.