• There are two realms: JS and Native which are not really aware of each other and do not share the same memory
• The communication is async through the bridge between the two realms
• It is slow to transfer large chunks of data. Since the memory is not shared, all the data passed ...

Don’t get them wrong, Facebook is using React Native by themselves for the Marketplace app, Ads app and more which servers millions of daily users. In addition, some well-known companies like Wix, Bloomberg, Tesla, Zynga and much more using RN in production with the current architect...

Now, let’s explain about all the new words you see here: JSI, Fabric, Turbo Modules

JSI is gonna replace the Bridge

JSI (Will replace the Bridge) — Its purpose is to make the JS and Native are aware of each other. There won’t be any need to serialize JSON throu...

Fabric — the new name for the UIManager which will be responsible for the native side. The biggest difference now that instead of communicating the JS side by the bridge, it will expose its native function using the JSI so the JS side and vice-versa can communication directly those ref functions....

Remember the native modules from the last post? Text, Image, View. So their new name is Turbo Modules. They have the same purpose but implemented and acting differently. First, they are lazy-loaded (only when the app needs them) comparing to loading all of them on the launch time. In addition, th...

CodeGen — Suppose to make the JS side a Single Source Of Truth. Can let you create static types of the js so the native side (Fabric and Turbo Modules) will be aware to them and avoid validating the data each time => better performance and less place for mistakes when passing data.

Lean ...

We now go over the flow from the previous post and will show the differences. There isn’t a bridge anymore

1. User clicks on the app icon
2. Fabric loads the native side (no native modules)
3. It tells the JS thread that it is ready and now the JS side loads all the main.bundle....