New Architecture is here

Posted by stigi 10/24/2024

New Architecture is here(reactnative.dev)

153 points | 124 commentspage 2

tcoff91 10/24/2024|

React native is finally pretty good this year. It still has problems but I feel like it's really starting to pick up momentum.

When react-strict-dom is totally ready for prime time it's going to be a game changer and react native will become an absolute juggernaut.

RussianCow 10/24/2024|

How so? What makes this a game changer for the average dev?

tcoff91 10/25/2024||

With react-strict-dom, you'll be able to have far better code sharing between web and native. It will greatly assist the development of universal apps that target Web, iOS, and Android.

Right now react-native-web is not nearly as good as iOS and Android react-native. react-strict-dom is a massive leap forward for universal apps.

jurmous 10/24/2024||

I have built a React Native app in the past. Nowadays I would go for Kotlin Multiplatform. It is already the primary language on Android and now it is possible to create native binaries on iOS. With Compose multiplatform it also has the ability to also share UI code with a declarative syntax on multiple platforms.

I think React Native was the go to place in the past but it has been surpassed now.

ppsreejith 10/24/2024||

This is pretty incredible, kudos to the team! I wonder if there's still an option to call native modules asynchronously (since I'd guess the synchronous native calls block JS execution?)

Also, I remember transferring lots of data through the bridge could be a bottleneck for some use cases. Is that effectively solved with this architecture?

e63f67dd-065b 10/24/2024||

I'm not familiar with UI development at all, but I'm kind of amazed that the old solution of a giant async bridge where the renderer enqueued native function calls worked at all. What was the initial reasoning behind this architecture? (that is to say, why did it seem like a good idea at the time?)

arijo 10/24/2024||

Guys, help me understand these changes:

Can I comprehend this as a new Virtual Native UI immutable tree running in native space?

And react native mounts and updates basically synchronally updating this immutable tree and reconciliation being done in native space, dynamically updating the app layout?

rickhanlonii 10/24/2024|

Kind of. We already had a native UI tree running in native (the same way the browser has it's own internal representation of the DOM). The difference in this release is that we rewrote it in C++ and made it immutable. That means instead of having a different UI tree in each platform (one for iOS, one for Android, etc), we have one C++ tree that all platforms use. And since it's immutable, it's thread safe and we can read layout and commit it from different threads if needed.

Reconciliation is still done in React on the JS thread, similar to React DOM.

arijo 10/24/2024||

Thanks for the clarification. Dumb question:

How does the renderer ensure consistency in case o multiple immutable tree references?

jdthedisciple 10/24/2024||

Wondering the same (replying to easier find your comment and hopefully the answer since i cant favorite comments)

tmitchel2 10/24/2024||

Love react native, I'll be updating to this version soon. Really hoping it makes suspense work correctly with libs like Relay. Well done and thank you RN team.

pixelready 10/24/2024||

It’s looking really good so far. Some known issues in the expo and RN ecosystem are called out under the troubleshooting section here:

https://docs.expo.dev/guides/new-architecture/

coldblues 10/24/2024||

I will now inform everyone here that the Windows 11 Start Menu uses React Native. You're welcome :)

theThree 10/24/2024|

Only the "recommended" section.

pbreit 10/24/2024||

Could someone suggest a good CRUD starter kit?

slorber 10/25/2024|

Honestly, can we even trust a technology that is not 1.0 ?