Shopify Is Going Native Again: What AI Agents Changed in the Native vs React Native Decision

The assumption behind a decade of decisions

In 2020, Shopify announced that React Native was the future of mobile at the company. The reasoning was economic. Teams shared 95% or more of their code between iOS and Android, and one team reported feeling twice as productive (Shopify, 2020). Building the same feature twice, in two languages, with two sets of specialists, was the cost everyone wanted to avoid.

That cost shaped an industry. Many companies chose a shared codebase because it was affordable, even when it did not produce the best app.

What Shopify changed, and why

On September 10, Shopify published a post titled "Native is now the future of mobile at Shopify." The central sentence is direct: LLMs changed one of the core assumptions behind the 2020 decision. In Shopify's words, agents have reduced the advantages of sharing implementation, while the advantages of building for each platform remain.

The company is clear that React Native was the right choice in 2020. What changed is the price of the alternative.

The first result is the Shop app. According to Shopify's engineering team:

• one engineer built a proof of concept in a week,
• a core team of six, later joined by feature teams, rebuilt the app and shipped it to the stores in 12 weeks,
• startup time fell by 23% on iOS and 50% on Android,
• crash-free sessions improved from 99.5% to 99.95%,
• the Android binary shrank by 37%.

The main Shopify app, with more than 300 screens, is in migration now.

What made it work

The engineering write-ups give a more detailed picture than the headline "agents rewrote the app."

Shopify rebuilt the app from scratch, using the existing React Native version as the reference. The team notes that agents were particularly effective when they had an existing implementation to work from.

Specialized agents handled source review, planning, implementation and parity checks, and a debugging tool captured screenshots and event streams from both versions of the app so they could be compared. For the main Shopify app, work is split into checkpoints, and each one requires tests, a visual match, adversarial code review and human approval.

The agents wrote the code, and the process made it trustworthy. A team without a working app to compare against, or without the discipline to verify each step, should not expect the same result.

Shopify is not alone

Coinbase moved its app to React Native in 2021 and described the transition as a success. A recent job posting now describes a team executing a greenfield rewrite of the retail mobile app from React Native to native Swift and Kotlin, using AI-assisted code generation and agentic translation. Coinbase has not announced it officially, but the description is specific.

Two large companies are too few to call this a trend. Still, they show that the question is open again in places where it was considered settled.

The other side of the argument

Agents make everything cheaper, including cross-platform work.

In October, Callstack, a React Native consultancy, released Apex, a coding model specialized in React Native and priced well below frontier models, after a private beta that started in May. Its makers say models for native iOS and Android are next. If specialized models reduce the cost of React Native work as well, the gap that Shopify describes narrows from both directions.

There are other reasons for caution:

• Google's Android Bench 2.0 found that the best available model passed roughly 28% of long-horizon Android tasks. Models handle well-defined transformations far better than open-ended refactoring.
• Kotlin Multiplatform and Compose Multiplatform are moving the other way, with production use in large apps (JetBrains).
• In the 2025 Stack Overflow survey, 43.6% of respondents used TypeScript, 10.8% Kotlin and 5.4% Swift (Stack Overflow). There are far fewer native specialists to hire.

Shopify has a large mobile team and internal tooling built for this migration. Its math is not automatically yours.

When the math favors native

The decision is still a trade-off, but the weights have changed. Native is more attractive than it was two years ago when:

• the app depends on hardware: Bluetooth, camera, sensors, background processing,
• it must work offline and recover reliably,
• startup time and stability are part of the product,
• the app will live for many years, and platform changes need to be adopted quickly,
• a working app already exists and can serve as the reference for a rebuild.

A shared codebase remains reasonable when the team is small, the app is mostly forms and content, and time to first release matters more than the last 20% of performance.

Questions before you decide

1. What share of our mobile effort goes into working around the framework rather than building features?
2. Which features depend on platform capabilities we reach through a bridge or a plugin?
3. Do we have tests and a running app that an agent-assisted rebuild could be verified against?
4. Who on the team can review Swift and Kotlin code with confidence?
5. What would we measure to know the migration was worth it?

Where Nomtek can help

Nomtek has built native and cross-platform mobile apps for over a decade. We can assess where your current app pays a framework cost, estimate what an agent-assisted native rebuild would involve, and set up the verification process that makes it safe. For some teams the right answer will be to stay where they are, and we will say so.

Want to check whether the math has changed for your app? Book a call with our Product Consultant, Tamara Bolsewicz.

Sources

Callstack (Pierzchała, M., Miłkowski, P., & Grabowski, M.). (2026a, October 1). Apex Is Now Generally Available: Agentic Coding Model for Mobile and Web, Specialized in React. Callstack Blog. https://www.callstack.com/blog/apex-agetic-coding-for-mobile-and-web-spcialied-in-react

Callstack (Grabowski, M., & Miłkowski, P.). (2026b, May 27). Introducing Apex: A Fast, Specialized Model for React Native. Callstack Blog. https://www.callstack.com/blog/introducing-apex-a-fast-specialized-model-for-react-native

Coinbase (Tormey, H.). (2021). Announcing Coinbase's successful transition to React Native. Coinbase Blog. https://www.coinbase.com/blog/announcing-coinbases-successful-transition-to-react-native

Coinbase. (2026). Senior Software Engineer, Native Mobile (Job P78585) and Senior Staff Software Engineer, Native Mobile (Job P78586). Coinbase Careers. Retrieved October 8, 2026, from https://www.coinbase.com/careers

Google. (2026, September 16). Android Bench 2.0: Pushing the frontier with challenging long-horizon tasks. Android Developers Blog. https://android-developers.googleblog.com/2026/09/android-bench-2-long-horizon-tasks.html

JetBrains. (2025, May). Compose Multiplatform 1.8.0 Released: Compose Multiplatform for iOS Is Stable and Production-Ready. The Kotlin Blog. https://blog.jetbrains.com/kotlin/2025/05/compose-multiplatform-1-8-0-released-compose-multiplatform-for-ios-is-stable-and-production-ready/

Shopify (Thawar, F.). (2020, January 29). React Native is the Future of Mobile at Shopify. Shopify Engineering. https://shopify.engineering/react-native-future-mobile-shopify

Shopify (Da Silva, M., Kim, J., & Fagoaga, Q.). (2026a, September 10). Migrating Shop app from React Native to native. Shopify Engineering. https://shopify.engineering/shop-app-migration

Shopify (Ali, M.). (2026b, September 10). Native is now the future of mobile at Shopify. Shopify Engineering. https://shopify.engineering/back-to-native

Stack Overflow. (2025). 2025 Developer Survey: Technology. https://survey.stackoverflow.co/2025/

‍