After the launch of React, developers started complaining that the library uses too much RAM as it uses the concept of a Virtual DOM. Mark Zuckerberg later stated that stated saying “We have made a big mistake including too much HTML 5 as compared to Native”. This really frustrated the developers as there was less native feel to the applications that they build using React.
Met a bunch of startups last night. The thing in common? All of them use React Native for building their app, zero experience with Swift (or god beware, Objective-What?).
Still, quite decent apps – better than a Web View.
— Peter Steinberger (@steipete) April 11, 2018
How does it work?
The only limitation, however, is that if you wish to have more native functionality which this library does not offers, you will have write platform specific code yourself.
React State and Props
Each data inside React Native is managed by State and Props. This means that the data is either mutable in the future (state) or immutable (prop). Props are short for properties. these decide how the components should community to each other. Props flow from upward to downwards direction that is from parent to child.
As components do not have state and they are referred to as stateless, this is where state kicks in. Props do not power the components to change in later development. A component having a state is stateful. This means a track is being kept for the components whenever a render does some changes in it.