Migrating to React Native's New Architecture
10 comments
·September 12, 2025mellosouls
Perhaps it's buried in the article somewhere but I think it should highlight in the introduction what business problems were solved or improved, and what the original architecture was; essentially why this major migration was undertaken.
brazukadev
A new React native architecture again?! I bet later this year we will have a new React (base) architecture change too
sesm
That's why 'New Architecture' is a bad name. They should have called it 'Bridgless Architecture' or just 'V2 Architecture'.
I remember how in an old ClearCase codebase we had a comment saying `New! <projectname> 4`. Version 4 was about 20 years old at that point. We kept this comment as a reminder to never use 'new' when naming or describing anything.
frou_dh
Maybe it's not so new, like "modernism" in art is 100 years ago.
HelloNurse
I think "TurboModules" are from the "current" new architecture (now several years old), not a new one, but I might have skipped some episodes.
cthulberg
why "again"?
mcsniff
Still no dark mode, it's almost as embarrassing as HN not having dark mode. Yeah I said it, again.
https://news.ycombinator.com/item?id=34263628
In the time it took to write this self-congratulatory post, they could have used the AI they push down everyone's throats to add dark mode to the mobile app.
The problem with relying on these high-level frameworks, or heavy frameworks of any kind, is that one day they will change their entire approach to how things should be implemented, and then you have a giant pile of legacy on your hands.
I learned that lesson the hard way with ExtJS 3 => 4, and now my wife claims I have commitment issues.