---
title: When Shopify Dropped React Native for Native
description: Shopify moved its mobile apps off React Native to Swift and Kotlin. A working engineer's checklist for when dropping React Native actually pays its rent.
canonical: https://lukeocodes.dev/dropping-react-native
type: article
locale: en_GB
published: 2026-09-10T00:00:00.000Z
modified: 2026-09-10T00:00:00.000Z
authors:
  - Luke Oliff
section: Opinion
tags:
  - Opinion
  - Engineering
  - react native
  - shopify
  - mobile
  - swift
  - kotlin
  - cross-platform
feed: https://lukeocodes.dev/rss.xml
search: https://lukeocodes.dev/search.json?q={query}
schema:
  - "@context": https://schema.org
    "@graph":
      - "@type": WebSite
        "@id": https://lukeocodes.dev/#website
        url: https://lukeocodes.dev
        name: Luke Oliff
        alternateName: lukeocodes
        inLanguage: en
        publisher:
          "@id": https://lukeocodes.dev/authors/luke#person
        description: Personal blog and writing by Luke Oliff — developer relations, voice AI, developer experience.
        potentialAction:
          - "@type": SearchAction
            target:
              "@type": EntryPoint
              urlTemplate: https://lukeocodes.dev/blog/search?q={search_term_string}
            query-input: required name=search_term_string
      - "@type": Person
        "@id": https://lukeocodes.dev/authors/luke#person
        name: Luke Oliff
        url: https://lukeocodes.dev/authors/luke
        description: Engineer and developer relations leader. Writing about developer relations, AI, and the voice industry, from the UK.
        mainEntityOfPage: https://lukeocodes.dev/authors/luke
        givenName: Luke
        familyName: Oliff
        image: https://lukeocodes.dev/authors/luke.jpg
        jobTitle: Engineer and developer relations leader
        sameAs:
          - https://www.linkedin.com/in/lukeocodes
          - https://github.com/lukeocodes
          - https://bsky.app/profile/lukeocodes.dev
          - https://x.com/lukeocodes
          - https://hashnode.com/@lukeocodes
          - https://dev.to/lukeocodes
        knowsAbout:
          - Developer Relations
          - Developer Experience
          - Voice AI
          - Text-to-Speech
          - Answer Engine Optimisation
          - Search Engine Optimisation
          - Open Source
          - Developer Tooling
          - API Design
          - Speech-to-Text
          - Voice Agents
          - Community Building
        knowsLanguage:
          - English
        nationality: British
        alumniOf:
          - "@type": Organization
            name: The Open University
  - "@context": https://schema.org
    "@graph":
      - "@type": Person
        "@id": https://lukeocodes.dev/authors/luke#person
        name: Luke Oliff
        url: https://lukeocodes.dev/authors/luke
        description: Engineer and developer relations leader. Writing about developer relations, AI, and the voice industry, from the UK.
        mainEntityOfPage: https://lukeocodes.dev/authors/luke
        givenName: Luke
        familyName: Oliff
        image: https://lukeocodes.dev/authors/luke.jpg
        jobTitle: Engineer and developer relations leader
        sameAs:
          - https://www.linkedin.com/in/lukeocodes
          - https://github.com/lukeocodes
          - https://bsky.app/profile/lukeocodes.dev
          - https://x.com/lukeocodes
          - https://hashnode.com/@lukeocodes
          - https://dev.to/lukeocodes
        knowsAbout:
          - Developer Relations
          - Developer Experience
          - Voice AI
          - Text-to-Speech
          - Answer Engine Optimisation
          - Search Engine Optimisation
          - Open Source
          - Developer Tooling
          - API Design
          - Speech-to-Text
          - Voice Agents
          - Community Building
        knowsLanguage:
          - English
        nationality: British
        alumniOf:
          - "@type": Organization
            name: The Open University
      - "@type": BlogPosting
        "@id": https://lukeocodes.dev/dropping-react-native#article
        headline: When Shopify Dropped React Native for Native
        alternativeHeadline: When Shopify Dropped React Native for Native
        description: Shopify moved its mobile apps off React Native to Swift and Kotlin. A working engineer's checklist for when dropping React Native actually pays its rent.
        datePublished: 2026-09-10T00:00:00.000Z
        dateModified: 2026-09-10T00:00:00.000Z
        url: https://lukeocodes.dev/dropping-react-native
        mainEntityOfPage: https://lukeocodes.dev/dropping-react-native
        inLanguage: en
        author:
          - "@id": https://lukeocodes.dev/authors/luke#person
        isPartOf:
          "@id": https://lukeocodes.dev/#website
        keywords: Opinion, Engineering, react native, shopify, mobile, swift, kotlin, cross-platform
        articleSection: Opinion
        about:
          - "@type": Organization
            name: Shopify
          - "@type": SoftwareApplication
            name: React Native
          - "@type": SoftwareApplication
            name: Swift
          - "@type": SoftwareApplication
            name: Kotlin
        abstract: In September 2026 Shopify said it's rebuilding Shopify, Shop, Point of Sale and Inbox in Swift and Kotlin. Dropping React Native paid off because coding agents made building twice cheaper than sharing one codebase, a reason most teams can't borrow yet.
        speakable:
          "@type": SpeakableSpecification
          cssSelector:
            - .post-tldr
            - h1
        image: https://lukeocodes.dev/og.png?h=When+Shopify+Dropped+React+Native+for+Native&d=Shopify+moved+its+mobile+apps+off+React+Native+to+Swift+and+Kotlin.+A+working+engineer%27s+checklist+for+when+dropping+React+Native+actually+pays+its+rent.&e=Writing
        wordCount: 569
        timeRequired: PT3M
        publisher:
          "@id": https://lukeocodes.dev/authors/luke#person
      - "@type": BreadcrumbList
        itemListElement:
          - "@type": ListItem
            position: 1
            name: Home
            item: https://lukeocodes.dev
          - "@type": ListItem
            position: 2
            name: Writing
            item: https://lukeocodes.dev/blog
          - "@type": ListItem
            position: 3
            name: When Shopify Dropped React Native for Native
            item: https://lukeocodes.dev/dropping-react-native
      - "@type": FAQPage
        "@id": https://lukeocodes.dev/dropping-react-native#faq
        mainEntity:
          - "@type": Question
            name: Is React Native dead after Shopify's move?
            acceptedAnswer:
              "@type": Answer
              text: No. One large company with heavy AI tooling reversed a 2020 bet. React Native still ships most small and mid-size apps at a cost native can't touch. Shopify's reason is specific to Shopify.
          - "@type": Question
            name: What performance gains did Shopify report?
            acceptedAnswer:
              "@type": Answer
              text: "For the rebuilt Shop app: Android startup roughly halved (4433ms to 2233ms), the Android app 109MB smaller, and session stability at 99.95%+, which Shopify calls a 10x reduction in crashing sessions."
          - "@type": Question
            name: Why did coding agents change the maths?
            acceptedAnswer:
              "@type": Answer
              text: Shopify says agents can implement a feature on Android using the iOS version as a reference and back, so maintaining two codebases no longer costs what it did in 2020. That's the whole reversal.
---

[Luke Oliff.](/)

- [Blog](/blog)
- [CV](/cv)
- [Uses](/uses)
- [User manual](/user-manual)
- [Living with ADHD](/living-and-working-with-adhd)
- [RSS](/rss.xml)

[Luke Oliff · Writing](/blog)

# When Shopify Dropped React Native for Native

Sep 2026 · [Opinion](/blog/category/opinion) · 3 min read · [Luke Oliff](/authors/luke)

**TL;DR:** In September 2026 Shopify said it's rebuilding Shopify, Shop, Point of Sale and Inbox in Swift and Kotlin. Dropping React Native paid off because coding agents made building twice cheaper than sharing one codebase, a reason most teams can't borrow yet.

Dropping React Native only makes sense when the cost of maintaining two native codebases drops below the cost of the cross-platform layer, and for most teams it hasn't. Shopify announced on [10 September 2026](https://shopify.engineering/back-to-native) that it's doing exactly that, rebuilding Shopify, Shop, Point of Sale and Inbox in Swift and Kotlin, six years after going all-in on React Native in 2020. The reason is worth reading closely, because it's narrower than the headline suggests.

The trigger wasn't that React Native got worse. Shopify's own post says it didn't. What changed is that coding agents got good enough to implement a feature on Android using the iOS version as a reference, and back the other way, so the duplicate-work cost that justified one shared codebase in 2020 mostly evaporated. Simon Willison [made the same point](https://simonwillison.net/2026/Sep/10/shopify-react-native/): native still means building twice, that cost didn't disappear, agents just absorbed enough of it that it stopped being the deciding factor.

## What Shopify actually got for it

The numbers are real and they're good. For the rebuilt Shop app, Android startup time roughly halved, from 4433ms to 2233ms, while iOS dropped about 23%. The Android app came out 109MB smaller, a 37% cut, though iOS grew by about 1MB. Session stability climbed to 99.95%+, which Shopify frames as a 10x reduction in sessions that crash. The team went from proof of concept to a published native app in 12 weeks, assisted by agents.

That's a strong result. It's also a result you get when you have Shopify's engineering depth, Shopify's agent tooling, and Shopify's reason to care about a 100MB download on a merchant's phone. Copy the decision without copying those and you've cargo-culted a headline.

## A checklist for dropping React Native

Before you reach for the same move, run the actual questions. Take a side on each, don't hedge.

Team size and shape. Two or three engineers holding a cross-platform app is the exact case React Native was built for, and dropping it doubles your surface area overnight. Shopify has hundreds of mobile engineers and agents to backfill the parity work. You probably don't.

Native-feature pressure. If you're constantly fighting the bridge to reach a widget, a Watch app, Siri shortcuts, or the newest platform API on day one, that friction is a real signal. Shopify called out widgets and lockscreen features specifically. If your app is forms and lists, the bridge is fine.

Performance that users feel. Startup time, scroll jank, app size on a cheap Android phone. If these show up in your reviews and your funnel, native buys something measurable. If they don't, you're optimising a number nobody complained about.

Hiring and maintenance. Two codebases need people who can own Swift and people who can own Kotlin, forever, plus the agent workflow that keeps them in parity. That's an ongoing tax, not a one-off migration. Be honest about whether you can staff it after the exciting rebuild is done.

## My actual take

Shopify made the right call for Shopify, and it's a genuinely interesting signal that agents are shifting the build-versus-share maths. But the lesson isn't "React Native is over." The lesson is that the tradeoff moved, and you should re-run it for your own team instead of borrowing Shopify's answer. For a small team without a fleet of coding agents, React Native still pays its rent every month. Shopify just found a tenant that pays more.

[← Newer: The Summer Three Labs Let Their AI Escape the Sandbox](/ai-sandbox-escape)

[All posts](/blog) →

## Search this site

`GET https://lukeocodes.dev/search.json?q=<words>` returns matching posts as JSON, each with its page URL and its markdown URL. Add `&limit=<1-50>` for more than 10. How it works: [/blog/search](https://lukeocodes.dev/blog/search.md).

```sh
curl "https://lukeocodes.dev/search.json?q=developer+relations"
```

---

© 2026 Luke Oliff. Posts live at the root of this site.

- [GitHub](https://github.com/lukeocodes)
- [LinkedIn](https://www.linkedin.com/in/lukeocodes)
- [X](https://x.com/lukeocodes)
- [Bluesky](https://bsky.app/profile/lukeocodes.dev)
- [Email](mailto:luke@lukeoliff.com)
- [RSS](/rss.xml)

## Cookies

This site sets one analytics cookie, from Google Analytics, and only in a browser that accepts the cookie banner. A client that does not run scripts sets no cookies, so there is nothing to accept or decline here.

[Cookie policy](/cookies)
