Nativestarter
Guides

What Shopify's move to native actually did

Deciding, 6 min read

Most coverage of Shopify's announcement stopped at the headline. The two engineering posts behind it are more useful than the headline, because they describe a method. Here is what it did, and what does and does not transfer to a smaller team.

The facts, from Shopify

On 10 September 2026 Shopify said it is moving its mobile apps (Shopify, Shop, Point of Sale and Inbox) from React Native to Swift and Kotlin. Its reason: “LLMs changed one of the core assumptions behind our 2020 decision”.

The Shop app went first. Shopify says it went “from a proof of concept to a fully rebuilt native app published in the app stores in just 12 weeks”. The Shopify app itself will ship later this year.

The method: checkpoints, not a conversion

The part worth copying is the workflow. Shopify describes the work as small, ordered slices, and each slice has to pass gates before the next one begins.

The gates Shopify describes: tests, visual review against the running app, two adversarial code reviewers, and human approval. The running React Native app is the reference, so the specification is the behaviour users already have.

The feedback loop

Gates only work if they are cheap enough to run on every slice. That means business logic that runs without a simulator, and a scripted way to drive the running app to a known state.

This is the part smaller teams most often skip. Without a fast feedback loop, the gates become the bottleneck and people start skipping them.

What transfers to your team

The checkpoint discipline transfers completely. It costs nothing but patience and it is the difference between a migration and a pile of generated code.

Parity checking against the running app transfers, and it matters more for a small team, because you have fewer people to notice drift by eye.

Adversarial review transfers. A second agent with a brief to disagree is cheap, and a human approving after it is still essential.

What does not

Shopify is a large company that can build its own internal tooling. A five-person team with no one who wants to own Kotlin is in a different position, and the right move for them may be to stay on React Native and add native code where it counts.

Shopify's experience is also specific to its own apps. Your numbers will depend on how old your React Native setup is, what your app does, and how much of it is really platform code already.

Sources

Shopify has no connection to Nativestarter.

Run the migration with your own agent

The Migration Pack gives your coding agent the skills, reviewers and scripts to move a React Native app to native one checkpoint at a time.