As there are many terms to such a large project like Elastos and the Cyber Republic, we’ve decided to build a growing glossary of terms that can help the less technical understand better what the tech means and the impact it could have.  This week we’re focusing on React Native, which was featured in this weekly update

Term: Elastos React Native

“Javascript React Native framework runs natively on android and ios devices. As such, the React Native framework needs to be customized so that it disables applications from directly accessing the internet. The http/https need to be disabled in the framework layer and all communications needs to be done using Elastos Carrier instead.

There is a need to support various other Elastos services such as interacting with the Elastos wallet core services such as payment functions, DID(Decentralized ID) services, token sidechain services, etc, and as such, appropriate javascript <-> C++ bridges need to be built to support React Native applications accessing those services.”

Layman’s definition:

Like Trinity Project, React Native is another way to develop dApps, but like everything, there are pros and cons. Trinity and React Native dapps are both written in JavaScript though with different frameworks: Ionic vs React Native. Trinity apps are web apps, and React Native apps are native apps.

This means that Elastos React Native apps would be much faster, but Trinity allows for the same code to be used for all platforms run within the Trinity browser.  React Native, however, can only work in Android and iOS while Trinity is able to run on anything that supports the browser from Windows to iOS and Android, etc. Both are needed to attract developers to build as developers love options.


Please enter your comment!
Please enter your name here