React Native Just Got 550% Faster

The new architecture is here!!! React Native was always good, but this definitely makes it WAY better. I'm so hyped to see these results.

SOURCES

S/O Ph4se0n3 for the awesome edit 🙏

[shahidullahmuffakir]

Lesson learnt, "don't upgrade it, start it from scratch."

[sherlockmaverick]

Really putting NATIVE performance in React Native.

On another note, I love how smooth and organic your soknsor transitions are. Segued right into it.

[virtual]

Theo: I hate ruby rails for code gen
Also Theo: code gen in rn, nice

[pokefreak]

25:15 this is a React problem, not a JS/DOM problem. It's pretty trivial to create a system that swaps out subtrees in an animated manner but VDOM is likely to get in your way.

[EricBishard]

So I’m a web developer for over twenty years. I’ve never built native apps. I always decided to learn more web related tech rather than both. When React Native came along I thought this would be a good time. But other than just playing around with workshop/demo code using Expo. I’ve not had to use it.

But that’s about to change, I need to learn it for work and I’m so happy that I will be able to really start now. It seems like a huge milestone for the framework.

[Kiyuja]

this could be big. Always lovely to see performance upgrades for the frontend world.

[SirTZN]

I like how theo disses flutter because react native is finally adopting a feature that flutter had for years. Don't get me wrong, this is fantastic news, but it's hard to take this video seriously when its implementing fixes that flutter never experienced from the start (like the native bridge, Flutter has had platform channels for years). So much of this update is just is implementing fixes that should never have to be implemented, such as the slider demo where the number of rendered cubes were synced with the slider value. That wouldn't happen in flutter because you aren't waiting for the JS VM, but instead dart which would be compiled natively.

Of course, I'm happy to see it improving, snd and I hope it can continue to do so.

[eminence_]

Tested it on a very large RN project and the bugs and glitches are extremely annoying. It just randomly doesn't render a component or two?? Didn't experience any noticeable perf gains either. It's still very experimental and would not recommend swapping to the new arch.

[rustystrings]

"starting a new project, moving all the code over and it just works"

THEO IS ONE OF US

[matthartstonge]

Very cool breakdown. Great blog post 👌 they’ve done well!!

[upsxace]

This got me excited. Hopefully they will be able to fix the input thing, because its genuinely weird for that bug to be hanging around, even though i also agree with you that no one should implement inputs that way anyways

[Go_with-Christ]

"Stop being scared of backends" by using a backend as a service lmfao

[maximierung]

A new Theo video posted 1min ago? Let‘s go! 🎉

[vinimaciel]

the useLayoutEffect was so helpful, thanks

[daniellasilverman]

This is all fun and games, but I still can't figure out how to develop in RN without Shadcn or Headless UI 😭

[JulesPatryLawl]

So pumped about this. I would have never knew about this react native update thanks @theo

[nordern]

I'm really interested in using it for desktop, I don't really see it as an option without Linux support :/

[peroconino]

Hopefully React Native will return to be a good choice again

[ynnkh]

For people in the comments, do you have example of what you built so far in react native? Like production grade apps? I want to try them for a before after

[dealloc]

10:20 Just to clarify something; the reported bug was NOT related to the architecture. It was _equally_ as bad with New Architecture.

The issue is in how iOS autocorrect and predictive text works since the past couple of releases, and also the fact that hardware keyboard input made it more visible due to the ability to type faster than humanly possible on a touch keyboard–nevertheless he bug was present.

Another related bug that occurs (and still hasn't been fixed) is when using a controlled input, every input change will result in the "Auto complete Password bar" above the keyboard to flicker, when enabling password input mode. The only work around is to use an uncontrolled input and refs. But you'll still see a flicker when focusing different inputs, e.g. for username/password fields. This issue is also present in SwiftUI and UIKit.