Shopify Moves From React Native Back to Swift and Kotlin

Shopify is reversing a major mobile-development decision it made in 2020: the company is moving its mobile apps from React Native back to native Swift and Kotlin development. The change comes after Shopify found that coding agents can now handle enough implementation, translation, testing, and review work to reduce the main cost of maintaining separate iOS and Android codebases. Its Shop app has already gone through the migration, moving from proof of concept to published native apps in 12 weeks.

Why Shopify changed its mobile strategy

React Native made sense for Shopify when the company adopted it because one shared codebase reduced duplicated work between iOS and Android. Developers could build a feature once, share much of the implementation, and spend less time keeping the two platforms aligned. Shopify says that approach worked well and helped developers without deep mobile experience contribute to its applications. The assumption that has changed is the cost of writing the same feature twice: coding agents can now translate an existing implementation into platform-specific code much faster than traditional development allowed.

The Shop app provided Shopify's first real test

Shopify did not begin by rewriting its entire mobile portfolio. The team first spent a week using coding agents to migrate as much of the existing Shop application as possible into a native iOS implementation built with SwiftUI, Apple's declarative user-interface framework. The result was not production-ready, but it demonstrated that screens, interactions, and application flows could be recreated from the existing React Native implementation. That proof of concept gave Shopify enough confidence to commit to the full migration.

Six engineers built the native foundations

For the full migration, a core group of six engineers established the native foundations and rebuilt the main user journeys, with feature teams joining later to validate functionality and edge cases. The objective was not simply to reproduce the visible screens. Shopify also had to preserve sign-in sessions, push notifications, analytics events, recommendations data, and other behavior that existing users and backend systems depended on. The team also used the migration to remove some screens and simplify parts of the application. That makes the project closer to a controlled application rewrite than a straightforward conversion between programming frameworks.

Shopify reports faster startup and smaller Android builds

Shopify compared the native Shop app with its React Native predecessor across startup time, stability, application size, build time, and rendering performance. On iOS, Shopify measured a cold-start time of 2,466 milliseconds for the native version versus 3,200 milliseconds for React Native, a reported 23% reduction. On Android, the native version measured 2,233 milliseconds versus 4,433 milliseconds, a reported 50% reduction. These are Shopify's own measurements from its migration, so they should be treated as application-specific results rather than proof that native applications are always faster.

The Android package became 109 MB smaller

The most striking size difference appeared on Android. Shopify reports that its native Android release build was 184 MB compared with 293 MB for the React Native version, a reduction of 109 MB or 37.2%. The iOS difference was much smaller in the other direction: 68 MB for native compared with 67 MB for React Native. This matters because application size affects download time, storage requirements, and the amount of software users must install before they can use an app, but the result should not be generalized to every React Native project because dependencies and application architecture vary considerably.

Native development also improved Shopify's build workflow

Shopify reports that Android release build time fell by approximately 75% after the migration, while iOS release builds took about the same amount of time. Faster builds can have an effect beyond developer convenience because shorter build-test cycles allow engineers and coding agents to validate changes more frequently. Shopify also reports that the native Android application reached 120 frames per second while scrolling and navigating on a Pixel device with relatively little optimization. That result is an observation from the Shop app rather than a general benchmark between native Android and React Native.

AI did not remove the need for experienced developers

The migration provides an important qualification to the idea that coding agents can simply replace conventional mobile development. Shopify found that generated code could satisfy feature requirements while still creating duplication, architectural drift, or performance problems. Engineers therefore combined agents with repository guidance, linting, automated tests, static analysis, performance checks, and code review. Platform expertise remained necessary for architectural decisions and for reviewing the SwiftUI and Jetpack Compose implementations, where Jetpack Compose is Google's declarative toolkit for Android user interfaces.

Shopify built tools specifically for agent-assisted migration

The company also changed its development process around the migration rather than simply giving an AI assistant access to the repository. Shopify created a reusable workflow around its Pi coding agent, using specialized agents to inspect the React Native source, document behavior, prepare platform-specific plans, implement features, and review parity between versions. It also built Tardis, an internal debugging tool that gives agents structured access to application events, logs, state, and commands. The team could capture screenshots and event data at defined checkpoints and compare the native and React Native applications while accounting for values such as timestamps that naturally change between runs.

The move does not mean React Native has become obsolete

Shopify's decision is significant, but it is not evidence that React Native has stopped being useful. The company itself says React Native remains an excellent framework and credits it with delivering substantial benefits since 2020. The more interesting change is economic: if coding agents can substantially reduce the cost of implementing the same feature separately on two platforms, the main reason for sharing one implementation becomes weaker. For smaller teams, applications with limited native requirements, or products where development simplicity matters more than platform-specific optimization, React Native can still be a rational choice.

Shopify's larger mobile portfolio is now following the same path

The Shop app is only the first migration Shopify has publicly described. The company says its larger Shopify app, which contains more than 300 screens along with widgets, an Apple Watch application, complications, and Siri Shortcuts, is also being migrated and is expected to ship later in 2026. Shopify plans to maintain feature parity between iOS and Android even though the implementations will now be separate. That is the real programming lesson from the decision: AI has not eliminated the cost of native development, but it may have changed which architecture makes sense when implementation, testing, and translation can increasingly be delegated to software agents.