Hacker News Says React Native Was Always Wrong, r/reactnative Says You Are Abandoning Our Libraries

On 10 September Shopify published Native is now the future of mobile at Shopify, explaining that it is moving its apps off React Native and back to Swift and Kotlin after six years. By the time we pulled the thread it had 1,129 points and 821 comments on Hacker News, which puts it in the top handful of stories that week. It landed on r/reactnative the same day.

We read the top 40 comments on Hacker News and the first 22 on Reddit, which is where a thread's argument actually gets set. What is strange about them is not that the two communities disagreed. It is that they were not having the same conversation, and the measurements that would settle a large chunk of it were sitting in a second Shopify post that nothing we read pointed at.

The argument, stated fairly

Shopify's case, at its strongest: they picked React Native in 2020 to stop building every feature twice, and it worked. What changed is not that React Native got worse. It is that agents got good enough to do the translation work between platforms, so the main thing cross-platform was buying you became cheap by other means. Their words: agents "dramatically reduced the cost of maintaining parity between platforms." They are explicit that React Native "was the right choice for Shopify in 2020" and remains "an excellent framework."

The other side, at its strongest, is not "React Native is great." It is the point frabcus made on Hacker News, which the post genuinely does leave open:

"the article doesn't really say what is better about the Swift/Kotlin apps, compared to React Native... What's the user benefit of that? It's not speed, they say 'React Native apps can be fast. Ours are.' I'd expect it to be considerably easier for a few people to use the AI to improve React Native with whatever matters, than for every company in the world to permanently maintain two apps."

That is the real question. If agents make writing code cheap, the obvious move is to point them at the shared abstraction, not to abandon it and write everything twice forever.

The takes

pkaler on Hacker News gave the longest-memory version of the skeptical case, and it is the one we keep thinking about:

"I'm sitting here at my desk overlooking Cordova Street. The street that Apache Cordova is named after. I've seen this debate for almost two decades now... teams start as 20 iOS engineers & 20 Android engineers. They adopt something like React Native. Then you end up with a team of 20 product engineers and 20 tooling and framework engineers."

netshade did the same migration and disputes Shopify's stated reason outright, which is the most useful contribution in either thread because it comes with a timeline:

"I think the story that 'LLM enabled an otherwise too-expensive migration to consider' is not correct... The majority of the work occurred before January 2026 and without LLM code assistance. The continued React Native tax of unnecessarily difficult upgrades, impedance mismatch w/ underlying core frameworks, and incredibly uneven library quality just cause your business to really spend a lot of time shepherding the tech over the finish line."

ernsheong gave the sharpest counter to the whole premise:

"It seems like Shopify has fallen into a trap thinking that more complexity costs nothing because of AI. In the age of AI we have to embrace the same principle as before that complexity needs to be tamed, not multiplied."

pranshuchittora, who contributes to React Native, listed what native actually costs you, and OTA updates are the item nobody arguing the other side addressed:

"The most valuable feature which RN have is OTA updates... Ability to release and iterate at light speed. On native you are on the mercy of the app stores for review."

Over on r/reactnative, /u/howdoigetauniquename put the community's actual fear in one sentence:

"My fear is that they start dropping support for their libraries too. People slowly leaving react native will make the eco system worse."

That fear is well founded, and /u/Civil_Rent4208 had read the post closely enough to say exactly how: Shopify is handing React Native Skia to William Candillon to fork and rename, looking for a steward for FlashList, and archiving Restyle outright. Shopify's post confirms all three. FlashList alone does roughly 2 million downloads a week.

/u/FriendGlittering9104 made the prediction we would bet on:

"The same was said out loud when Shopify decided to use React Native. People are naturally resistant to change... this will kick off a chain reaction since other companies are now justified to copy this strategy, now that they see it is viable."

The two platforms argued about completely different things

This is the part worth the piece. Hacker News litigated the engineering decision. r/reactnative did not, really.

The top of the r/reactnative thread is mostly about Tobi Lütke and Shopify's internal culture: jokes about "disagree and commit", /u/rsajdok asking "Why does he have so much power?", /u/treetimes answering that he is the founder with majority shares, and a long digression about whether Shopify is a good place to work. The technical claim, that agents changed the cost structure, gets engaged seriously by maybe four commenters out of the first thirty.

One of those four, /u/Swaggy_McMuffin, actually conceded the point and extended it:

"If LLMs are as good as everyone claims, we should be raising the quality bar because 'code is cheap'. That means abstracting reusable business logic... and building native apps."

The asymmetry makes sense once you see it. Hacker News has no stake in React Native, so it argued about whether the decision was right. r/reactnative has its livelihood in the ecosystem, so it argued about what happens to the ecosystem. Both are legitimate. Neither community produced the other's best argument, and if you read only one thread you came away with half the story.

The post that answers the top comment

Shopify published a second post the same day, Migrating Shop app from React Native to native, and it is the one with the numbers in it. Not one of the 62 comments we read across both threads cites it, including the ones complaining that the numbers do not exist.

Measure	React Native	Native
Android cold start	4,433 ms	2,233 ms (50% faster)
iOS cold start	3,200 ms	2,466 ms (23% faster)
Android app size	293 MB	184 MB (37.2% smaller)
iOS app size	67 MB	68 MB (1 MB larger)
Crash-free sessions	99.5%+	99.95%+

These are Shopify's own measurements, not ours, and they are marketing numbers in the sense that Shopify chose which ones to publish. But they are specific, they include a row where native lost, and they directly answer frabcus, the most-upvoted objection in the thread. A 10x reduction in crashing sessions is a bigger user-facing claim than anything in the post everyone actually read. Shopify also says a core group of six engineers took the Shop app from proof of concept to shipped in 12 weeks.

The best comment nobody upvoted

zhyder got almost no traction and asked the only question that will still matter in two years:

"I'm curious what their update will be in a year or two. Because these costs don't reduce as dramatically with AI (unless you fully give up control and vibe code it): 1. Reading code 2. Manually testing code"

w10-1 made the same point from the other end: "Most of the costs of switching have yet to be borne: user issues with untested code, maintenance issues with code few understand, and the strategic dependency on coding LLM's." Writing two codebases got cheap. Reading two codebases, and being on call for both at 3am, did not.

Our read

Shopify is probably right for Shopify and the reasoning is probably wrong. netshade's account is the tell: he did this migration mostly before 2026 and mostly without agents, and it was still worth it. The React Native tax Shopify is escaping looks like it was already high enough to justify the move on its own, and "LLMs changed the calculus" is a cleaner story to tell publicly than "we spent six years fighting our framework."

If agents genuinely make code free, the winning move is to point them at the shared abstraction, not to delete it and maintain two of everything forever.

What would change our mind is Shopify's own follow-up. If the Shopify app, 300 plus screens with widgets and a Watch app, ships later this year on the same timeline and the crash rate holds, the agent argument gets a lot stronger. If it slips, or if the two codebases start drifting in ways users notice, then frabcus was right and this was a framework divorce wearing an AI hat.

One last thing worth saying plainly: we went looking for a response from the Expo or React Native core teams and did not find one we could verify. Given that Shopify maintained three widely used libraries in that ecosystem and is stepping back from all three, that silence is the most interesting unwritten part of this story.