<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/shopify-just-killed-react-native-jvdd8ozdb" -->

---
title: Shopify just killed React Native | daily.dev
description: Shopify is dropping React Native in favor of native Kotlin and Swift development for its mobile apps, five years after committing fully to the cross-platform...
canonical: https://daily.dev/posts/shopify-just-killed-react-native-jvdd8ozdb
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Shopify just killed React Native | daily.dev
og:description: Shopify is dropping React Native in favor of native Kotlin and Swift development for its mobile apps, five years after committing fully to the cross-platform...
og:url: https://daily.dev/posts/shopify-just-killed-react-native-jvdd8ozdb
og:image: https://api.daily.dev/og/posts/jvdD8OZdb.png
og:image:alt: Shopify just killed React Native
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Shopify just killed React Native

**[Awesome](https://daily.dev/sources/awesome-coding)** · 8 min read · 1 upvotes · 0 comments

## Summary

Shopify is dropping React Native in favor of native Kotlin and Swift development for its mobile apps, five years after committing fully to the cross-platform framework. Shopify's own stated reason is that coding models have gotten so much better that building the same feature natively in Swift and Kotlin no longer carries the cost it once did, undercutting the original rationale for going cross-platform. The video draws three lessons from this: underlying native platforms matter more than ever when a lot of LLM-generated code is mediocre and under-reviewed; the Jevons paradox means cheaper code leads to more code being written and maintained rather than less; and specialized, deep expertise becomes more valuable as AI handles routine CRUD-style work. The creator cautions that Shopify's move works because of its large mobile team, and smaller teams shouldn't necessarily rush to abandon cross-platform frameworks.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.youtube.com/watch?v=6FFTBNJkrKo>

## Questions this post answers

### Why did Shopify switch from React Native to native Kotlin and Swift for mobile development?

Shopify stated that coding models have gotten dramatically better, so building the same feature in Swift and Kotlin no longer carries the cost it used to compared to when they committed to React Native in 2020. Since that core cost assumption changed, Shopify reevaluated its mobile stack from first principles and decided native development was now the better trade-off, even though it means maintaining two separate codebases.

_Developers weighing cross-platform versus native mobile stacks can track shifts like this one on daily.dev._

### What is the Jevons paradox and how does it apply to AI-generated code?

The Jevons paradox describes how making a resource cheaper and more efficient tends to increase total consumption of it rather than reduce it, because new use cases become economically viable. Applied to coding, as LLMs make writing code cheaper, companies build more apps, add more features, and maintain more platform-specific implementations, so total code volume grows instead of shrinking.

_Anyone rethinking software economics as AI lowers coding costs can follow this reasoning on daily.dev._

### Should a small development team drop React Native for native Kotlin and Swift after Shopify's move?

Not necessarily. Shopify could afford this switch because it has a mobile team large enough to staff two native codebases in parallel, whereas a two-person team writing Swift with AI assistance still lacks anyone to properly review that code, and maintaining two native platforms remains twice the ongoing maintenance burden regardless of how cheaply the initial code was generated.

_Small teams deciding on mobile architecture can weigh trade-offs like these before following industry moves, via daily.dev._

## Similar posts on daily.dev

- [Why Shopify Migrated From React Native](https://daily.dev/posts/why-shopify-migrated-from-react-native-itvaopvng) · ByteByteGo · 80 upvotes · 6 comments

---

Tags: [#mobile](https://daily.dev/tags/mobile), [#ai-coding](https://daily.dev/tags/ai-coding), [#react-native](https://daily.dev/tags/react-native), [#kotlin](https://daily.dev/tags/kotlin), [#shopify](https://daily.dev/tags/shopify)

[View this post on daily.dev](https://daily.dev/posts/shopify-just-killed-react-native-jvdd8ozdb)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Shopify just killed React Native","url":"https://daily.dev/posts/shopify-just-killed-react-native-jvdd8ozdb","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/shopify-just-killed-react-native-jvdd8ozdb"},"datePublished":"2026-09-21T09:10:07.348Z","dateModified":"2026-09-24T15:42:30.861Z","description":"Shopify is dropping React Native in favor of native Kotlin and Swift development for its mobile apps, five years after committing fully to the cross-platform...","image":"https://i.ytimg.com/vi/6FFTBNJkrKo/sddefault.jpg","thumbnailUrl":"https://i.ytimg.com/vi/6FFTBNJkrKo/sddefault.jpg","isAccessibleForFree":true,"articleSection":"Awesome","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Awesome","logo":"https://media.daily.dev/image/upload/s--mj_0cdD8--/f_auto/v1710506099/logos/awesome-coding","url":"https://daily.dev/sources/awesome-coding"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/shopify-just-killed-react-native-jvdd8ozdb","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"mobile,ai-coding,react-native,kotlin,shopify","timeRequired":"PT8M","video":{"@type":"VideoObject","name":"Shopify just killed React Native","description":"Shopify is dropping React Native in favor of native Kotlin and Swift development for its mobile apps, five years after committing fully to the cross-platform...","thumbnailUrl":"https://i.ytimg.com/vi/6FFTBNJkrKo/sddefault.jpg","uploadDate":"2026-09-21T09:10:07.348Z","duration":"PT8M","url":"https://api.daily.dev/r/jvdD8OZdb","embedUrl":"https://www.youtube.com/embed/6FFTBNJkrKo"}}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Awesome","item":"https://daily.dev/sources/awesome-coding"},{"@type":"ListItem","position":3,"name":"Shopify just killed React Native"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/shopify-just-killed-react-native-jvdd8ozdb#faq","mainEntity":[{"@type":"Question","name":"Why did Shopify switch from React Native to native Kotlin and Swift for mobile development?","acceptedAnswer":{"@type":"Answer","text":"Shopify stated that coding models have gotten dramatically better, so building the same feature in Swift and Kotlin no longer carries the cost it used to compared to when they committed to React Native in 2020. Since that core cost assumption changed, Shopify reevaluated its mobile stack from first principles and decided native development was now the better trade-off, even though it means maintaining two separate codebases. Developers weighing cross-platform versus native mobile stacks can track shifts like this one on daily.dev."}},{"@type":"Question","name":"What is the Jevons paradox and how does it apply to AI-generated code?","acceptedAnswer":{"@type":"Answer","text":"The Jevons paradox describes how making a resource cheaper and more efficient tends to increase total consumption of it rather than reduce it, because new use cases become economically viable. Applied to coding, as LLMs make writing code cheaper, companies build more apps, add more features, and maintain more platform-specific implementations, so total code volume grows instead of shrinking. Anyone rethinking software economics as AI lowers coding costs can follow this reasoning on daily.dev."}},{"@type":"Question","name":"Should a small development team drop React Native for native Kotlin and Swift after Shopify's move?","acceptedAnswer":{"@type":"Answer","text":"Not necessarily. Shopify could afford this switch because it has a mobile team large enough to staff two native codebases in parallel, whereas a two-person team writing Swift with AI assistance still lacks anyone to properly review that code, and maintaining two native platforms remains twice the ongoing maintenance burden regardless of how cheaply the initial code was generated. Small teams deciding on mobile architecture can weigh trade-offs like these before following industry moves, via daily.dev."}}]}
```

