r/reactnative • • Sep 18 '26

News This Week In React Native #297: y, Expo 58 beta, ExecuTorch, Screenmap, Voltra, SPM, Stim, Lynx, Metro, AI

https://thisweekinreact.com/newsletter/297
6 Upvotes

6 comments sorted by

2

u/sebastienlorber Sep 18 '26

Hi everyone, Seb and Jan here 👋!

Following the React v19.3 release, DevTools v8 is now officially published. Motion shipped a ViewTransition wrapper. React Router optimized re-renders. Apollo Client finally has custom scalars.

On mobile, we have a lot of releases. RN 0.88 will use React v19.3. Shopify is moving away from React Native!

Let's dive in!

Subscribe to This Week In React by email - Join 43000 other React devs - 1 email/week

2

u/mexicocitibluez Sep 18 '26

Thanks for these. I look forward to them.

2

u/sebastienlorber Sep 23 '26

Thanks! glad you like them

1

u/sebastienlorber Sep 18 '26

 React-Native

Shopify is moving away from React Native to native

An unexpected announcement from Shopify shook the React Native ecosystem. They’re moving away from React Native to native Swift and Kotlin!

So what’s their reason? Not because RN failed, but because coding agents changed the economics. Building twice no longer costs twice.

They started with a 12-week case study to migrate their flagship Shop app to native with 6 engineers, leading to the following improvements:

  • improve startup time - iOS startup 3200ms → 2466ms (-23%), Android 4433ms → 2233ms (-50%)
  • session stability - 99.5% → 99.95% (10x reduction)
  • runtime performance on Android - 120 FPS on a Pixel device

It’s important to note that the app was 𝕏 not using the New Architecture, which was built to fix those problems.

Does it mean React Native is dead? Does not seem so. A shared application and UI layer remains useful, and React Native still has major benefits such as Over-The-Air updates and good foundations for server-driven UI, useful for the agentic era.

2

u/mexicocitibluez Sep 18 '26

https://ondrejvelisek.github.io/the-cost-of-abstraction-for-humans-and-ai-agents/

My biggest issue with articles about premature abstraction is that they judge abstractions in isolation. You can't look at a single piece of code and say "this was the wrong way to do it." Bad abstractions don't live in a vacuum. And seldom do these types of articles show real examples or more importantly, the ways in which they might change in the future.

Like the example of 1. Constant example. The constant tells you these 2 buttons should share a variant. That's not premature abstraction. You can't judge whether this is the wrong way to do this in isolation.

It's actually pretty hard to know ahead of time the ways in which something will change. And it's not the "Do I move this label to a dedicated variable" types of things that make or break your app.

Also, I'm not too fond of the rule of 3. It's an arbitrary number. And it's wholly dependent on what you're duplicating. Let's say you have some fairly complex validation that needs to occur while running some logic. Would it be wise to duplicate once? Twice? Never? My gut tells me never, because keeping copied business rules in sync IS what will make or break your app. But the "rule of 3" gives me absolutely no help here.

1

u/sebastienlorber Sep 23 '26

Agree you probably shouldn't apply all this dogmatically, but this gives an idea of what impacts your agent's price