Shopify Left React Native for Swift and Kotlin. Should You Still Learn It?

Before we dive in, why not take a quick peek at my portfolio: https://priyalraj.com

📋 TL;DR: What You’ll Learn Here

• What Shopify announced on September 10, 2026, & why it shook the React Native world.

• The real reason behind the move (spoiler: it’s not “React Native is slow”).

• The actual numbers from their Shop app rebuild.

• My honest take on whether you should still learn React Native as a web developer.

📰 What Happened?

Quick backstory. In 2020, Shopify went all-in on React Native & became one of its biggest champions. They maintained popular libraries like FlashList, React Native Skia & Restyle. As late as January 2025, they wrote that the future of React Native was bright.

Then, on September 10, 2026, Shopify published Native is now the future of mobile at Shopify. Their mobile apps are moving to Swift (iOS) & Kotlin (Android).

It hit the top of Hacker News with 1,200+ points, & my Twitter feed was basically one long debate for two days straight.

🤔 Why Did They Leave?

Here’s the part most hot takes missed. Shopify didn’t say React Native was bad. In their own words:

“React Native apps can be fast. Ours are.”

So what changed? AI coding agents.

Back in 2020, React Native gave Shopify three big wins:

• Build a feature once instead of twice.

• Let full-stack web devs contribute to mobile.

• Stop iOS & Android from drifting apart feature-wise.

By 2026, coding agents had gotten so good that writing the same feature in Swift and Kotlin wasn’t that expensive anymore. As Shopify put it:

“Agents have reduced the advantages of sharing implementation, while the advantages of building for each platform remain.”

There was a second trigger too. The Shop app was about to adopt React Native’s New Architecture, a big migration that would have meant revisiting native modules, rendering, & the boundaries between shared & platform code. Before spending that effort, they tested a different idea: what if agents just helped them build natively in SwiftUI & Jetpack Compose instead?

Think of it like renovating an old house vs building a new one. If construction suddenly gets 5x cheaper, the “just renovate” argument gets a lot weaker.

📊 The Numbers From the Shop App Rebuild

Shopify published a detailed write-up on the Shop app migration. The highlights:

• Proof of concept: One engineer spent one week with coding agents porting the React Native app into SwiftUI. Not production-ready, but enough to prove it could work.

• Team: A core group of six engineers built the native foundations & main user journeys.

• Timeline: From proof of concept to a fully rebuilt app in the stores in 12 weeks.

⚡ Cold startup time (tap icon to home feed visible)

🛡️ Stability

Session stability went from 99.5%+ to 99.95%+. That’s roughly a 10x drop in sessions that crash.

On Android, the native app hit 120 FPS while scrolling the feed on a Pixel, with very little manual tuning.

🤖 The Secret Sauce: Helix

This wasn’t “ask ChatGPT to rewrite the app & pray”. Shopify built an internal system called Helix to keep AI-generated code in check.

Instead of one-shot generation, work moves through checkpoints:

• ✅ Tests must pass.

• 👀 Visual verification against the old app.

• 🔍 Two adversarial AI code reviewers.

• 🙋 Human approval before moving on.

This is the real lesson for any dev using AI today. The speed came from the agents, but the quality came from the guardrails around them.

📦 What Happens to Their React Native Libraries?

If you use any of these, pay attention:

• React Native Skia: Shopify sponsors it until the end of 2026. Its original creator, William Candillon, will fork & republish it under a new name.

• FlashList: (~2M downloads/week) Shopify keeps shipping critical bug fixes & is looking for community stewardship.

• Restyle: Will be archived after the end of 2026. Fork it if you depend on it.

🗣️ The Counterarguments (Worth Hearing)

Not everyone was convinced, & some points are fair:

• “You compared against old React Native.” The benchmarks were vs their existing app, not a New Architecture version.

• Over-the-air updates. With React Native (especially with Expo), you can push JS fixes without waiting on app store review. Native loses that.

• Shopify isn’t you. They have a huge engineering org & the budget to build tools like Helix. A 3-person startup doesn’t.

💡 So, Should You Still Learn React Native?

React Native was on my own 2025 goals list, so I’ve thought about this a lot. My honest answer: yes, for most web devs, still yes.

Learn React Native if:

• You already know React & want to ship mobile apps fast.

• You’re a freelancer or small team building client MVPs on a budget.

• You need OTA updates & quick iteration.

Consider going native if:

• You’re building something performance-critical (heavy animations, widgets, watch apps).

• You want deep platform features like Siri Shortcuts, widgets or Apple Watch.

• You’re comfortable leaning on AI agents with strong testing to manage two codebases.

Here’s how I see it. Shopify’s move doesn’t prove React Native is dead. It proves that the cost of writing code dropped, so the cost of maintaining two codebases matters less than it used to.

The skill that wins long term isn’t “React Native” or “Swift”. It’s knowing how to direct AI agents with tests, reviews & checkpoints, like Shopify did with Helix.

Final Thoughts

React Native gave Shopify six great years, & they said so themselves: “React Native was the right choice for Shopify in 2020.”

What changed isn’t the framework. It’s the economics of writing code. If you’re a web dev, React Native is still the fastest bridge into mobile. Just make sure you’re also learning how to work with AI, not just next to it.

If you enjoyed this article, please make sure to follow me on Twitter.