Mentatcurated
Artificial Intelligence medium · first-party

Build it twice

After six years of evangelising a single shared codebase, Shopify is rebuilding its mobile apps twice over in Swift and Kotlin, on the grounds that coding agents have made the duplicate work cheap.

Six engineers rebuilt Shopify's Shop app in twelve weeks, taking it from a prototype to a finished product in both the Apple and Google app stores. That sprint is the evidence behind a reversal Shopify published this week: all of its mobile apps are going back to being written twice over, once in Swift for iPhones and once in Kotlin for Android, retiring the single shared codebase the company had championed since 2020.

"Native still means building and maintaining software on two platforms, that cost has not disappeared." — Shopify

Shopify credits the shared approach rather than blaming it. As recently as January last year it published a bullish retrospective on five years of React Native, the write-once framework it helped popularise, reporting three-quarters of screens loading in under half a second and better than 99.9% of sessions crash-free. What changed, by its account, is the price of duplication. A coding agent can take a finished iPhone screen and produce the Android version from it, treating the first implementation as the specification, so building twice no longer means doing the work twice.

Part of the bill lands on other people. Shopify became one of the largest maintainers of that ecosystem's plumbing, and its list-rendering library FlashList, the default for anyone building a long scrolling feed, is pulled down about two million times a week. Shopify will keep patching it through the end of 2026 while it looks for a new steward, and has invited forks; its styling library is being archived outright. Thousands of apps that never made Shopify's architectural bet now inherit the consequences of it.

A great deal of software architecture exists because writing the same thing twice is expensive, so engineers build a layer that lets them write it once and run it everywhere. When the second copy gets cheap enough, that layer stops paying for itself, and the duplication every engineer was trained to eliminate becomes the economical choice. Shopify's own engineers raise the obvious objection, that the costly part of two codebases was never the typing but keeping two products that must behave identically in agreement with each other, which is a coordination problem no agent settles for you. Even so, this is the first well-known company to say out loud that it has crossed the line, and any framework whose main pitch is write-once now has to make a different argument.

The lenses

Novelty 3
Impact · breadth 3
Impact · depth 4
Actionable 2
Delight 3
Substance 4
Hype 4

The facts

The rebuildSix engineers, twelve weeks, prototype to published app in both stores
Still to comeThe flagship Shopify app, 300+ screens plus watch and lock-screen versions, later in 2026
CollateralFlashList, about 2M downloads a week, patched to end of 2026 then needs a new owner
Open shopify.engineering →

How this connects

Tap a node to open it

How this connects