React Native — A Bridge To Project Fabric  - Deepstash
Some of the main disadvantages of the current structure
  • 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

4

STASHED IN:

2

React Native — A Bridge To Project Fabric 

medium.com

STASHED IN:

53 Comments

The current Arhitecture

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

1

STASHED IN:

2

The New Arhitecture

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

2

STASHED IN:

2

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

1

STASHED IN:

2

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

1

STASHED IN:

2

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

1

STASHED IN:

2

The new flow

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

2

STASHED IN:

2

Deepstash helps you become inspired, wiser and productive, through bite-sized ideas from the best articles, books and videos out there.

GET THE APP: