⏱️ Lectura: 10 min
Six years after betting everything on React Native, Shopify is reversing course: its iOS and Android apps will once again be written in native Swift and Kotlin. The company announced it on September 10, 2026, and the reason isn’t that React Native failed, but that AI agents changed the cost calculation that had supported that decision since 2020.
📑 En este artículo
TL;DR
- Shopify announced on September 10, 2026 that it’s abandoning React Native to return to native Swift and Kotlin.
- The company adopted React Native in 2020 and is now reversing that bet due to advances in AI agents.
- Shopify has been using LLMs to write software since 2021, a year before ChatGPT launched.
- The Shopify, Shop, Point of Sale, and Inbox apps will be rebuilt from scratch (greenfield), not gradually.
- React Native Skia will keep Shopify’s sponsorship until the end of 2026 and then fork under a new name.
- FlashList, with nearly 2 million weekly downloads, remains in maintenance while a new steward is sought.
- Restyle is being archived: Shopify maintains it until the end of 2026 and then drops support.
- The key insight: AI agents can now port a feature from iOS to Android using the other platform as a reference.
What Happened With React Native at Shopify
Shopify’s engineering team published the announcement under the title Native is now the future of mobile at Shopify. In it, they explain that they decided to move from native code to React Native in 2020 for three reasons: to stop building the same feature twice, to let developers without mobile experience contribute to the apps, and to stop chasing feature parity between iOS and Android.
“We decided to go all-in on React Native back in 2020, and that bet has been extremely successful”, the team wrote.
That positive track record held, according to Shopify: React Native met all three goals, and the company considers the investments in optimizing performance and keeping up with framework updates worthwhile. But in January 2025, the same company had publicly written that React Native’s future at Shopify was promising and that it planned to keep investing there. Twenty months later, the conclusion is the opposite.
Context and History
Shopify didn’t arrive at this decision overnight. The company has used language models to write software since 2021, a year before ChatGPT launched publicly. At first they used them to implement specific features, investigate bugs, and review code. As the models improved, so did the complexity of the work Shopify delegated to them.
By late 2025, the company says, the agents were no longer just helping write code faster: they began to question whether building a feature twice (once in Swift for iOS, once in Kotlin for Android) really meant double the work. That question led Shopify to re-evaluate its mobile stack from scratch.
flowchart TD
A["2020: duplicated native code"] --> B["React Native adoption"]
B --> C["Single codebase for iOS and Android"]
C --> D["2025: AI agents improve significantly"]
D --> E["Native prototypes with agents"]
E --> F["2026: return to Swift and Kotlin"]Technical Details and Performance
To test the hypothesis, Shopify rebuilt core parts of its largest apps in Swift and Kotlin using AI agents as primary assistants. The result surprised the team itself: the agents could implement a feature on Android using the iOS version as a reference, and vice versa, without a developer having to manually translate every line.
The agents also helped developers without experience in a given stack (for example, someone specialized in Kotlin who’d never touched Swift) contribute with confidence, thanks to shared specs, test suites, and predefined review checkpoints. That drastically reduced the cost of maintaining parity between platforms, which was exactly the problem React Native had solved in 2020.
Shopify clarifies something important: building for two native platforms still means maintaining two codebases, that cost hasn’t disappeared. What changed is that it’s no longer the deciding factor. React Native can be fast (“Ours are”, the company says about its own apps), but native keeps Shopify closer to each platform’s capabilities and first-party tooling, with fewer framework layers and dependencies between the code and the operating system.
💭 Key takeaway: Shopify isn’t saying React Native is worse. It’s saying AI agents lowered the cost of building native twice so much that the advantage of sharing a single codebase stopped outweighing the extra layers the framework adds.
| Approach | When it makes sense | Main advantage | Limitation |
|---|---|---|---|
| React Native (shared code) | Small teams, without capacity to maintain two native stacks in parallel | A single codebase for iOS and Android | Framework layers and dependencies between your code and the platform |
| Agent-assisted native (Swift + Kotlin) | Teams with agents capable of porting features between platforms using the other as a reference | Direct access to each platform’s first-party APIs and tools | Still two codebases to maintain: the cost drops, but doesn’t disappear |
How to Start Testing This Approach
You don’t need to be Shopify to replicate the experiment on a smaller scale. The core idea is simple: use one platform’s implementation as a living spec for an agent to generate the other, and verify parity with a shared test instead of reviewing the code line by line.
// FeatureFlag.swift (iOS, reference version)
struct FeatureFlag {
let key: String
let isEnabled: Bool
}
func isCheckoutV2Enabled(flags: [FeatureFlag]) -> Bool {
flags.first(where: { $0.key == "checkout_v2" })?.isEnabled ?? false
}With that file as a reference, you ask the agent to generate the Kotlin equivalent along with a test that verifies the same behavior:
claude "Port FeatureFlag.swift to Kotlin keeping the same behavior and add an equivalent unit test" --file FeatureFlag.swiftThe agent reads the iOS version, generates FeatureFlag.kt and its JVM test, and returns both files ready for human review. This solves the mechanical translation; what’s needed next is a parity verification mechanism.
// discount_spec.json (contract shared between platforms)
{
"case": "10% off, minimum $50",
"input": { "subtotal": 120.00, "rule": "PERCENT_10_MIN_50" },
"expected_discount": 12.00
}// DiscountEngineTest.kt (Android)
@Test
fun appliesPercentDiscountAboveMinimum() {
val result = DiscountEngine.apply(subtotal = 120.00, rule = Rule.PERCENT_10_MIN_50)
assertEquals(12.00, result.discount, 0.01)
}The same discount_spec.json feeds the equivalent XCTest on the iOS side. How to confirm parity: run both suites against the same case file and compare the output. If both return 12.00 for the same input, parity is guaranteed without sharing a single line of interface code.
💡 Tip: Keep parity specs (like discount_spec.json) in a repository separate from each platform’s code. That way both teams, human or agent, point to the same source of truth.
Impact and Analysis
Shopify’s pivot hits the React Native ecosystem directly, where the company is one of the largest open source contributors. FlashList, the library Shopify released for rendering high-performance lists, has nearly 2 million weekly downloads and became the de facto standard for long lists in React Native. Shopify will keep fixing critical compatibility bugs while negotiating with other companies over who takes on long-term stewardship.
With React Native Skia, the exit looks different: Shopify will keep paying for sponsorship until the end of 2026, and its lead maintainer, William Candillon, will fork the repository under a new name once the transition ends. The original repository will be archived. Restyle, on the other hand, is being archived with no successor: Shopify supports it until the end of 2026 and then drops support, though anyone can fork it.
⚠️ Note: Shopify is explicit that native isn’t free. Maintaining two platforms still costs more than maintaining one, the change is that this extra cost stopped outweighing the value of direct access to each system’s APIs.
The case also serves as a gauge for a broader industry discussion: if coding agents lower the cost of writing (and translating) platform-specific software enough, the historical argument in favor of cross-platform frameworks like React Native loses weight against direct access to hardware and the operating system.
What’s Next
Shopify has several major apps at stake: Shopify, Shop, Point of Sale, and Inbox, used daily by millions of merchants and shoppers. To migrate them, the company evaluated two paths: gradual migration (brownfield) or a complete rebuild (greenfield). In 2020, when they moved from native to React Native, they had chosen brownfield for the largest apps, because rewriting them from scratch would have taken years without being able to ship new features in the meantime.
This time, greenfield won. Shopify doesn’t detail every reason, but points to AI agents already being good enough at building new features that rebuilding from scratch no longer means halting the rest of the roadmap. The result will be measured over the coming months: the end of 2026 is also the deadline for Skia’s sponsorship and Restyle’s support, so a good part of Shopify’s React Native ecosystem is realigning within the same window.
📖 Summary on Telegram: View summary
Try it yourself: grab a small Swift file from your own app, ask your coding agent to port it to Kotlin with a parity test, and compare the result to what Shopify describes in its original announcement.
Frequently Asked Questions
Is Shopify eliminating React Native entirely?
For its production apps, yes: Shopify, Shop, Point of Sale, and Inbox are being rebuilt in native Swift and Kotlin. The company continues to support some of its open source React Native libraries for a limited time.
What happens to FlashList?
It continues receiving critical compatibility fixes while Shopify negotiates with other companies over who takes on its long-term maintenance.
What happens to React Native Skia?
Shopify continues paying for sponsorship until the end of 2026. After that, its maintainer William Candillon will fork the project under a new name and the original repository will be archived.
Why did Shopify choose to rebuild from scratch instead of migrating gradually?
Because, unlike in 2020, AI agents can now build new features on both platforms fast enough to avoid slowing down the rest of the roadmap while the app is rewritten.
Does this mean React Native is no longer useful?
Not according to Shopify: the company clarifies that React Native met its goals and that its apps were fast. What changed is the relative cost of maintaining two native platforms, not the quality of the framework.
Which Shopify apps are affected by the change?
Shopify, Shop, Point of Sale, and Inbox, all rebuilt from the ground up (greenfield) in Swift and Kotlin.
References
- Shopify Engineering: official announcement of the shift from React Native to native, published September 10, 2026.
- GitHub, Shopify/FlashList: repository for the high-performance list library for React Native.
- GitHub, Shopify/react-native-skia: repository for the Skia-based graphics library for React Native.
- React Native: official site for the framework Shopify adopted in 2020.
📱 Enjoy this content? Follow @programacion on Telegram for daily tech content in Spanish: quick summaries, fresh content every day. @programacion
Imagen destacada: Foto de Rubaitul Azad en Unsplash
0 Comments