Why Shopify's React Native Exit Doesn't Threaten Expo

On September 10, 2026, Shopify announced it was pulling its core mobile apps out of React Native and rebuilding them natively using Swift and Kotlin. Within hours, developer forums lit up with speculation. Threads on social media argued over whether this marked the end of React Native. Several blog posts went as far as calling cross-platform mobile development finished.

If you build with Expo, none of this should worry you.

What Shopify Actually Did — And Why

Shopify's stated rationale was fairly simple: AI coding assistants have made it much cheaper to maintain two separate native codebases for iOS and Android. React Native's original selling point was saving engineering time by sharing code across platforms. Once AI tools can generate native Swift and Kotlin at high speed, that calculation shifts for an organization the size of Shopify.

The key detail is "an organization the size of Shopify."

Shopify operates one of the most intricate mobile applications on the planet, with hundreds of engineers, millions of merchants, and performance demands that stress-test any framework. When Shopify says AI has made native development more affordable, it's speaking from the position of a company that can staff two large, complex codebases at once.

Most Expo developers are not in that position, and neither is the typical team shipping apps today.

Expo and Shopify Are Solving Different Problems

For Shopify, React Native was primarily a way to cut costs across a huge engineering organization. For Expo developers, React Native is the tool that lets a solo builder or a small team ship a complete, polished app on both iOS and Android without needing to be a specialist in either native platform.

Those two use cases have almost nothing in common.

Expo has a dedicated core team that has spent years refining one of the strongest developer experiences in mobile. The recently released SDK 57 brought further gains in performance, build tooling, and day-to-day developer ergonomics. Surrounding libraries such as NativeWind, Reanimated, and Expo Router are more stable and production-ready than at any earlier point.

None of that changes because one large retailer decided to move on.

The Numbers Tell a Different Story

While commentators were busy declaring React Native finished, the adoption data pointed the other way.

NativeWind, the Tailwind CSS-style styling solution for React Native, passed 1.3 million weekly downloads during 2026 and kept climbing. Expo continues to show up prominently across developer communities and discussions. Newer styling libraries such as Uniwind have launched and picked up hundreds of thousands of weekly downloads within just a few months.

Those figures don't describe a shrinking ecosystem. They describe one that's still maturing.

The people who dropped React Native the moment Shopify made its announcement were likely the same people who would have found some other excuse to leave next month anyway. The developers actually shipping real products with Expo aren't reconsidering anything.

AI Makes Expo Development Faster, Not Obsolete

There's a real irony buried in the argument that AI killed React Native: AI tooling has actually made building with Expo noticeably better, not worse.

Assistants such as Claude, Cursor, and GitHub Copilot have a strong understanding of the Expo ecosystem. Given a well-organized CLAUDE.md file that documents your component conventions and architectural patterns, one of these assistants can add new screens, build out features, and refactor existing code while staying consistent with the rest of your codebase.

The people getting the most value from this workflow, sometimes called "vibe coders" because they describe an outcome and let the assistant handle implementation, still need a solid starting structure. AI tools are excellent at writing code. They're far less reliable at making architectural calls, designing navigation flows, building a theming system, or establishing a consistent set of shared components from scratch.

That gap is exactly what a well-built Expo starting template fills. It's not about the code an AI assistant could generate on demand anyway — it's about the underlying structure that makes AI-assisted coding actually productive.

Templates Are the Base Layer for AI-Assisted Development

When a developer opens Cursor or Claude to start a new app, the first real question is what codebase they're starting from.

Beginning from a bare create-expo-app output means spending your first hours wiring up navigation, adding dark mode support, building base UI components, and settling on conventions. AI can assist with parts of that work, but it still demands human decisions, configuration, and back-and-forth iteration before you have a usable foundation.

Beginning instead from a production-ready template means that groundwork is already finished. You open your AI editor, describe the feature you want next, and the assistant has a coherent, well-organized codebase to extend.

This is precisely why templates designed with AI-assisted workflows in mind — complete with detailed CLAUDE.md documentation, clear component-level notes, and consistent patterns — matter more today than they did two years ago, not less.

The Developers Who Should Actually Be Worried

If Shopify's move should worry anyone, it's developers building bare React Native apps outside the Expo ecosystem, relying directly on the React Native CLI, and targeting enterprise-scale clients who have the engineering headcount to justify fully native development.

That describes a fairly narrow slice of everyone using React Native.

If instead you're an independent developer, a freelancer, a small studio, or someone building a first app largely by describing it to an AI assistant, Expo remains the quickest route from an idea to a shipped app on both major mobile platforms. Nothing in Shopify's decision changes that math.

What This Means for You

Keep building with Expo. Keep shipping with Expo. The ecosystem is in good health, the tooling is still improving release after release, and the community around it isn't disappearing.

If you're kicking off a new React Native project, start from a production-ready template rather than an empty project, and let AI assistants handle the implementation details on top of that foundation. That combination lets you ship faster than working from scratch ever could.

Some developers will spend the coming weeks reading hot takes and second-guessing their technology choices because of one company's announcement. Others will simply keep shipping their apps.

Aim to be in the second group.