The New React Native Architecture

THANK YOU CHAIN REACT FOR SPONSORING THIS VIDEO

I've wanted to talk about the new React Native architecture and the chaos that is JSI for awhile, so hyped to get this one out!

SOURCES

S/O Ph4se0n3 for the awesome edit 🙏

[Bekir_ts]

After some thought i realized Conference sponsorship is very good advertisement choice. I didnt know about the chain react conf and Im buying it now. Both Theo me and chain react won! win-win for everyone

[amypellegrini]

I did a POC building a React Native app which calls FluidSynth in the C++ layer to play a MIDI file using a sound font. What I thought was impossible now just works flawlessly (if you are ready to get your hands dirty with C++).

[MaxHDeveloping]

The thing with the benchmark comparing the iPhone and Android Phone is, that the Pixel 4 was a low-to-mid tier phone while the iPhone 12 PRO(!) is a high-end flagship. Ofc android will be a bit slower because of java, but the real reason people think android is slower is that they compare their shitty low low-end android phone to high-end iPhones...

[devIsAjourney]

As a react-native and react full-stack developer, it's nice to see the react-native team make such a wonderful guide of The New Architecture.And credits to theo for your interesting and in-depth content👍

[mrousavy]

VisionCamera spotted in the wild at 13:37 👀

[ymi_yugy]

The 2x performance delta shown in the benchmark matches the single core performance diff between the Pixel 4 and iPhone 12 Pro.
Java is not at fault here.

[ra-dro]

As an enterprise dev I'm so scared of this migration. Now we are moving from 0.64 to 0.73 and thats a huge pain which cost us 1-2 moth of aligning with native devs and releasing the app. How do I explain business we need to move to the new arch, spending a full month on a testing and then rolling out a feature for it to be just turned off because of some misalignment in the framework?

[audas]

Holy crap - finally we are at where Flash was when it was killed. Running native C++.

[KarlOlofsson]

Love it! About to do my first proper app and have some basic UI going in web, but plan to do native apps soonish. Won't need ultra performance, but I like good DX none the less.

[jefferyosei]

You're amazing Theo!, keeping us updated always, .You're my source for tech news!

[tannercottle]

5:00 This honestly just depends on the implementation - there are things you'd want for different layouts/screen sizes that you can't do in CSS or that are more difficult to do in CSS, so sometimes a resize event listener from within a useEffect, or a useLayoutEffect which will re-fire when the browser repaints the screen

[VeitLehmann]

I have used React Native in the early days, and I still remember the many fights we had against jank. This was 5-7 years ago, around when Flutter came out. We eventually decided to rewrite everything in native, which solved many problems but caused a whole lot of different ones.

This new architecture looks really amazing! Until now, when I was about to write a mobile app, I'd pick Flutter. But now, maybe not, I'd give React Native another try! Maybe even with ReScript – it's a shame that it's such an underdog.

[Smongo]

Thank you for making this. You have become my favorite react-native hype guy!

[andriim]

man I love your videos
thanks for all your work

[amnesiac]

What ui frameworks do you guys use for react native? Feels like the ones I want to use are react only.

[TJYouToob]

It will be nice when the docs are a bit more fleshed out for codegen, etc. Right now, if I want to know how to work with it, I have to trudge through github projects for basic examples you'd expect in the docs.

[nyashachiroro]

This man has just been pumping out a lot of great content. A lot. The dedication 💪

[josefaguilar]

As someone who's worked with the JNI, early Node native C++ modules, and WASM, the JSI looks incredibly promising!

Thanks Theo, now it's time to dig into React native!

[curiouslycory]

Thumbs up for the clever swift dig. :D I needed a good laugh this morning.

[aakashr]

At the end of the day this is only incremental happiness for a React Native Dev. React Native will always have to keep up with native advancements and new way of doing things to have the community reap the best rewards of the platform. None of these arch changes or JSIs are needed for near native performance on a GL based framework. My take is simple. Either be a performance geek and go completely native. Or accept the minuscule tradeoffs and accept a truly cross platform framework where your UI APIs don't depend on native APIs (write integrated platform code or UI components when needed). You only fundamentally truly need native to talk to the respective OS. Don't be in the middle where you get none at it's best.