<ul><li>There are two realms: JS and Native which are not really aware of each other and do not share the same memory</li><li>The communication is async through the bridge between the two realms</li><li>It is slow to transfer large chunks of data. Since the memory is not shared, all the data passed between js and native is a new copy</li><li>No way to update the UI in a sync way. </li><li>The library repo is HUGE. It makes the library heavier and also making it slower to contribute code from outside or release new fixes</li></ul>

Some of the main disadvantages of the current structure

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 architecture. But all of the above companies and especially Facebook got to a point where they understood that if they want to make a better native experience and better developer experience they have to do a huge move and change and this is exactly what they are in a process of doing (part of it is already completed)

The current Arhitecture

Now, let’s explain about all the new words you see here: JSI, Fabric, Turbo ModulesJSI is gonna replace the BridgeJSI (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 through the bridge and even more than that — there won’t be a bridge! It will allow to expose native object as js objects and vice-versa. It will also expose an API for synchronous calling on this object on both sides. Actually, all the rest of the architecture will be built on top of that (Fabric, Turbo Modules which will be explained next).

The New Arhitecture

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. Better and efficient performance and passing data between sides.

Fabric

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, they are also exposed using the JSI so JS holds a ref to use them on the React Native JS lib side. Result =&gt; better performance especially on launch time.

Turbo Modules

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 =&gt; better performance and less place for mistakes when passing data.Lean Core — A change in React native repository structure. The purpose is to make the lib lighter and help the community resolve more pull requests faster than before. Facebook splits some of its parts to an external repo. It is already a process in progress that you can follow in their Github here.

CodeGen & Lean Core

We now go over the flow from the previous post and will show the differences. There isn’t a bridge anymore<ol><li>User clicks on the app icon</li><li>Fabric loads the native side (no native modules)</li><li>It tells the JS thread that it is ready and now the JS side loads all the main.bundle.js which contains all js and react logic + components</li><li>JS called through the ref native function (the one that was exposed as an object using the JSI API) to Fabric and the shadow node creates the tree as before</li><li>Yoga does the layout calculation converting from flexbox-based style to host layout</li><li>Fabric does its thing and shows the UI </li></ol>

The new flow

<img alt="Chen Feldman" src="https://miro.medium.com/max/500/1*uQKpnQNC4w5bUw7XI-dK3w" width="28" height="28">Finally, we got to the last post explaining about the future that’s coming for RN architecture.<figure><img alt="" src="https://miro.medium.com/max/500/1*T31hBqtHlGV-9qLOYPab_" width="680" height="376"></figure>We discussed the <a rel="noopener" href="https://medium.com/@chenfeldmn/react-native-a-bridge-to-project-fabric-part-2-1f082415b881?source=friends_link&amp;sk=a406d0f75854af01865b990af6991857" dir="ltr">current structure</a> until now and it is time to talk about the stuff that was not the perfect choice, looking backward as React team leader on Facebook at this time mentioned in <a href="http://facebook.github.io/react-native/blog/2018/06/14/state-of-react-native-2018" rel="noopener ugc nofollow" dir="ltr">her blog post</a>Some of the main disadvantages of the structure of the current architecture are =&gt;<UL><LI>There are two realms: JS and Native which are not really aware of each other and do not share the same memory</LI><LI>The communication is async through the bridge between the two realms but it also means no guarantee the data will get to the other side in 100% or in the time we want</LI><LI>It is slow to transfer large chunks of data. Since the memory is not shared, all the data passed between js and native is a new copy</LI><LI>No way to update the UI in a sync way. Let's say I have a FlatList with a huge amount of data the is loaded when I scroll, the screen might flicker in some edge cases when there was a UI interaction but the data hasn’t got back yet to be shown</LI><LI>The library repo is HUGE. It makes the library heavier and also making it slower to contribute code from outside or release new fixes</LI></UL>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 architecture.But all of the above companies and especially Facebook got to a point where they understood that if they want to make a better native experience and better developer experience they have to do a huge move and change and this is exactly what they are in a process of doing (part of it is already completed)They decided to solve all those issues mentioned as disadvantages above.So if that was the previous architecture structure =&gt;<figure><img alt="" src="https://miro.medium.com/max/500/1*eCTd2Ymrxse2TKYe1k4Tew.png" width="680" height="383"><figcaption dir="auto">The General Structure of the main pieces in the current architecture (for explaining the terms)</figcaption></figure>This will be the new one =&gt;<figure><img alt="" src="https://miro.medium.com/max/500/1*Vjsy_fCUFxle_UvtjZ8D2Q.png" width="680" height="385"><figcaption dir="auto">The General Structure of the main pieces in the new architecture (for explaining the terms)</figcaption></figure>Now, let me explain about all the new words you see here: JSI, Fabric, Turbo Modules, and CodeGen.I will do it in the same way I did in my last post. First -&gt; Fundamental terms and Second -&gt; App launch flow with the new structure and terms.<OL><LI>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 through the bridge and even more than that — there won’t be a bridge! It will allow to expose native object as js objects and vice-versa. It will also expose an API for synchronous calling on this object on both sides. Actually, all the rest of the architecture will be built on top of that (Fabric, Turbo Modules which will be explained next).</LI><LI>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. Better and efficient performance and passing data between sides.</LI><LI>Turbo Modules. 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, they are also exposed using the JSI so JS holds a ref to use them on the React Native JS lib side. Result =&gt; better performance especially on launch time.</LI><LI>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 =&gt; better performance and less place for mistakes when passing data.</LI><LI>Lean Core — A change in React native repository structure. The purpose is to make the lib lighter and help the community resolve more pull requests faster than before. Facebook splits some of its parts to an external repo. It is already a process in progress that you can follow in their Github here. This is how they show it =&gt;</LI></OL><figure><img alt="" src="https://miro.medium.com/max/500/1*yD11dL03vWJ-nknV3AXoaw.png" width="680" height="401"></figure>BTW — here is an example of something you can try on your chrome browser which is the inspiration for how the JSI works and exposes objects =&gt;<figure><img alt="" src="https://miro.medium.com/max/500/1*J53LMcRY9m8Mv4H0bwftCQ.png" width="680" height="370"><figcaption dir="auto">Inspect a page in chrome and write console.log and press Enter. You will see a native code. The console.log and other functions are actually objects exposing a ref to native code (C++ in this case)..crazy ah?</figcaption></figure>As promised, I will now go over the flow from the previous post and will show the differences. The biggest difference is that there is no Bridge anymore.<OL><LI>User clicks on the app icon</LI><LI>Fabric loads the native side (no native modules)</LI><LI>It tells the JS thread that it is ready and now the JS side loads all the main.bundle.js which contains all js and react logic + components</LI><LI>JS called through the ref native function (the one that was exposed as an object using the JSI API) to Fabric and the shadow node creates the tree as before</LI><LI>Yoga does the layout calculation converting from flexbox-based style to host layout</LI><LI>Fabric does its thing and shows the UI =&gt;</LI></OL><figure><img alt="" src="https://miro.medium.com/max/500/1*T4wuCEqo43VVKWR56gai3Q.png" width="548" height="348"></figure>To wrap up the flow, we do almost the same but without the bridge and now we can have better performance, we can do stuff in a sync way and even prioritize the sync actions on UI. The launch time will also be better and the app size will be smaller.So..when can I use all this awesome stuff???You can follow all the updates in threads that Facebook created in their Github here:Generally, most of the changes will be done gradually and will hopefully be released in Q4 2019 or Q1 2020.Finally, we got to the end of the posts about Project Fabric. It took me some effort to collect all those pieces of information to get a better understanding of this new structure.I will be happy to get some Claps and if you also want to follow me on twitter to see the slides and lectures I started giving about it you are welcome to <a href="https://twitter.com/chenosfeldman" rel="noopener ugc nofollow" dir="ltr">follow here</a>Feedbacks are also welcome! Thanks for reading (:My Twitter: <a href="https://www.twitter.com/chenosfeldman" rel="noopener ugc nofollow" dir="ltr">chenosfeldman</a>My LinkedIn: <a href="https://www.linkedin.com/in/chen-feldman-2404682a/" rel="noopener ugc nofollow" dir="ltr">Chen Feldman</a>P.S — here is some little part of links I read and watched as part of the process and recommend you to try to sharpen your understanding. (I give credits to all of them for giving me great material to read and watch)=&gt;<UL><LI>Latest RN news from Core Team- <a href="https://facebook.github.io/react-native/blog/" rel="noopener ugc nofollow" dir="ltr">https://facebook.github.io/react-native/blog/</a></LI><LI>Parashuram post about the new architecture <a href="http://blog.nparashuram.com/2019/01/react-natives-new-architecture-glossary.html" rel="noopener ugc nofollow" dir="ltr">http://blog.nparashuram.com/2019/01/react-natives-new-architecture-glossary.html</a></LI><LI>Pharam new 2019 lecture React Amsterdam — <a href="https://www.youtube.com/watch?v=NCLkLCvpwm4" rel="noopener ugc nofollow" dir="ltr">https://www.youtube.com/watch?v=NCLkLCvpwm4</a></LI><LI>Layout engine explnation — <a href="https://www.freecodecamp.org/news/how-react-native-constructs-app-layouts-and-how-fabric-is-about-to-change-it-dd4cb510d055/" rel="noopener ugc nofollow" dir="ltr">https://www.freecodecamp.org/news/how-react-native-constructs-app-layouts-and-how-fabric-is-about-to-change-it-dd4cb510d055/</a></LI><LI>Four parts article about the new architecture by Lorenzo from Formidable (part 1 here links to the others)— <a href="https://formidable.com/blog/2019/react-codegen-part-1/" rel="noopener ugc nofollow" dir="ltr">https://formidable.com/blog/2019/react-codegen-part-1/</a></LI><LI>FB State of React Q4 2018 by Sophie Alpert from FB team at this time — <a href="http://facebook.github.io/react-native/blog/2018/06/14/state-of-react-native-2018" rel="noopener ugc nofollow" dir="ltr">http://facebook.github.io/react-native/blog/2018/06/14/state-of-react-native-2018</a></LI></UL>Credits to : , and Irad for helping to finalize the post’s contentMy lectures about this subject — upload here soon<UL><LI>React Next 2019 (English) — <a href="https://youtu.be/_IiDHmAPH28" rel="noopener ugc nofollow" dir="ltr">https://youtu.be/_IiDHmAPH28</a></LI><LI>Reversim 2019 (Hebrew) — <a href="https://youtu.be/2eZ4G-loZkY" rel="noopener ugc nofollow" dir="ltr">https://youtu.be/2eZ4G-loZkY</a></LI><LI>Podcast episode (Hebrew) — <a href="https://www.ranlevi.com/2019/07/23/osim_software_react_native_bridge/" rel="noopener ugc nofollow" dir="ltr">https://www.ranlevi.com/2019/07/23/osim_software_react_native_bridge/</a></LI></UL>

We discussed the current structure until now and it is time to talk about the stuff that was not the perfect choice, looking backward as React team leader on Facebook at this time mentioned in her…

Mobile

Finally, we got to the last post explaining about the future that’s coming for RN architecture.

We discussed the <a dir="ltr" href="https://medium.com/@chenfeldmn/react-native-a-bridge-to-project-fabric-part-2-1f082415b881?source=friends_link&amp;sk=a406d0f75854af01865b990af6991857" rel="noopener">current structure </a>until now and it is time to talk about the stuff that was not the perfect choice, looking backward as React team leader on Facebook at this time mentioned in <a dir="ltr" href="http://facebook.github.io/react-native/blog/2018/06/14/state-of-react-native-2018" rel="noopener ugc nofollow">her blog post </a>

Some of the main disadvantages of the structure of the current architecture are =&gt;

<ul><li>There are two realms: JS and Native which are not really aware of each other and do not share the same memory </li><li>The communication is async through the bridge between the two realms but it also means no guarantee the data will get to the other side in 100% or in the time we want </li><li>It is slow to transfer large chunks of data. Since the memory is not shared, all the data passed between js and native is a new copy </li><li>No way to update the UI in a sync way. Let's say I have a FlatList with a huge amount of data the is loaded when I scroll, the screen might flicker in some edge cases when there was a UI interaction but the data hasn’t got back yet to be shown </li><li>The library repo is HUGE. It makes the library heavier and also making it slower to contribute code from outside or release new fixes </li> </ul>

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 architecture.

But all of the above companies and especially Facebook got to a point where they understood that if they want to make a better native experience and better developer experience they have to do a huge move and change and this is exactly what they are in a process of doing (part of it is already completed)

They decided to solve all those issues mentioned as disadvantages above.

So if that was the previous architecture structure =&gt;

This will be the new one =&gt;

Now, let me explain about all the new words you see here: JSI, Fabric, Turbo Modules, and CodeGen.

I will do it in the same way I did in my last post. First -&gt; Fundamental terms and Second -&gt; App launch flow with the new structure and terms.

<ol><li>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 through the bridge and even more than that — there won’t be a bridge! It will allow to expose native object as js objects and vice-versa. It will also expose an API for synchronous calling on this object on both sides. Actually, all the rest of the architecture will be built on top of that (Fabric, Turbo Modules which will be explained next). </li><li>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. Better and efficient performance and passing data between sides. </li><li>Turbo Modules. 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, they are also exposed using the JSI so JS holds a ref to use them on the React Native JS lib side. Result =&gt; better performance especially on launch time. </li><li>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 =&gt; better performance and less place for mistakes when passing data. </li><li>Lean Core — A change in React native repository structure. The purpose is to make the lib lighter and help the community resolve more pull requests faster than before. Facebook splits some of its parts to an external repo. It is already a process in progress that you can follow in their Github here. This is how they show it =&gt; </li> </ol>

BTW — here is an example of something you can try on your chrome browser which is the inspiration for how the JSI works and exposes objects =&gt;

As promised, I will now go over the flow from the previous post and will show the differences. The biggest difference is that there is no Bridge anymore.

<ol><li>User clicks on the app icon </li><li>Fabric loads the native side (no native modules) </li><li>It tells the JS thread that it is ready and now the JS side loads all the main.bundle.js which contains all js and react logic + components </li><li>JS called through the ref native function (the one that was exposed as an object using the JSI API) to Fabric and the shadow node creates the tree as before </li><li>Yoga does the layout calculation converting from flexbox-based style to host layout </li><li>Fabric does its thing and shows the UI =&gt; </li> </ol>

To wrap up the flow, we do almost the same but without the bridge and now we can have better performance, we can do stuff in a sync way and even prioritize the sync actions on UI. The launch time will also be better and the app size will be smaller.

So..when can I use all this awesome stuff???

You can follow all the updates in threads that Facebook created in their Github here:

Generally, most of the changes will be done gradually and will hopefully be released in Q4 2019 or Q1 2020.

Finally, we got to the end of the posts about Project Fabric. It took me some effort to collect all those pieces of information to get a better understanding of this new structure.

I will be happy to get some Claps and if you also want to follow me on twitter to see the slides and lectures I started giving about it you are welcome to <a dir="ltr" href="https://twitter.com/chenosfeldman" rel="noopener ugc nofollow">follow here </a>

Feedbacks are also welcome! Thanks for reading (:

My Twitter: <a dir="ltr" href="https://www.twitter.com/chenosfeldman" rel="noopener ugc nofollow">chenosfeldman </a>

My LinkedIn: <a dir="ltr" href="https://www.linkedin.com/in/chen-feldman-2404682a/" rel="noopener ugc nofollow">Chen Feldman </a>

P.S — here is some little part of links I read and watched as part of the process and recommend you to try to sharpen your understanding. (I give credits to all of them for giving me great material to read and watch)=&gt;

<ul><li>Latest RN news from Core Team- <a dir="ltr" href="https://facebook.github.io/react-native/blog/" rel="noopener ugc nofollow">https://facebook.github.io/react-native/blog/ </a> </li><li>Parashuram post about the new architecture <a dir="ltr" href="http://blog.nparashuram.com/2019/01/react-natives-new-architecture-glossary.html" rel="noopener ugc nofollow">http://blog.nparashuram.com/2019/01/react-natives-new-architecture-glossary.html </a> </li><li>Pharam new 2019 lecture React Amsterdam — <a dir="ltr" href="https://www.youtube.com/watch?v=NCLkLCvpwm4" rel="noopener ugc nofollow">https://www.youtube.com/watch?v=NCLkLCvpwm4 </a> </li><li>Layout engine explnation — <a dir="ltr" href="https://www.freecodecamp.org/news/how-react-native-constructs-app-layouts-and-how-fabric-is-about-to-change-it-dd4cb510d055/" rel="noopener ugc nofollow">https://www.freecodecamp.org/news/how-react-native-constructs-app-layouts-and-how-fabric-is-about-to-change-it-dd4cb510d055/ </a> </li><li>Four parts article about the new architecture by Lorenzo from Formidable (part 1 here links to the others)— <a dir="ltr" href="https://formidable.com/blog/2019/react-codegen-part-1/" rel="noopener ugc nofollow">https://formidable.com/blog/2019/react-codegen-part-1/ </a> </li><li>FB State of React Q4 2018 by Sophie Alpert from FB team at this time — <a dir="ltr" href="http://facebook.github.io/react-native/blog/2018/06/14/state-of-react-native-2018" rel="noopener ugc nofollow">http://facebook.github.io/react-native/blog/2018/06/14/state-of-react-native-2018 </a> </li> </ul>

Credits to :

and Irad for helping to finalize the post’s content

My lectures about this subject — upload here soon

<ul><li>React Next 2019 (English) — <a dir="ltr" href="https://youtu.be/_IiDHmAPH28" rel="noopener ugc nofollow">https://youtu.be/_IiDHmAPH28 </a> </li><li>Reversim 2019 (Hebrew) — <a dir="ltr" href="https://youtu.be/2eZ4G-loZkY" rel="noopener ugc nofollow">https://youtu.be/2eZ4G-loZkY </a> </li><li>Podcast episode (Hebrew) — <a dir="ltr" href="https://www.ranlevi.com/2019/07/23/osim_software_react_native_bridge/" rel="noopener ugc nofollow">https://www.ranlevi.com/2019/07/23/osim_software_react_native_bridge/ </a> </li> </ul>

Some of the main disadvantages of the current structure

React Native — A Bridge To Project Fabric

The current Arhitecture

The New Arhitecture

Fabric

Turbo Modules

CodeGen & Lean Core

The new flow

Testing · React Native

Why Discord is Sticking with React Native

Handling Offline Mode in React Native