How come React Native is so Native? – Quovantis – Medium

How come React Native is so Native?  #ReactJS

  • This sphere keeps the native feel intact so that it’s hard to tell whether the app is written in native language or React Native.JavaScript SphereIt contains JavaScript code that runs on the separate thread.
  • Well, let’s take a glance at how this wisely designed component works- Any user interaction/event is detected in Native Sphere and it’s straight away passed on to JavaScript sphere via bridge for processing.
  • When it’s done, it serializes the data and sends it back to native sphere via bridge for view rendering.Any pass over the bridge (call from Native to Javascript or from Javascript to Native ) brings down the performance graph.
  • As I mentioned earlier that any activity in JavaScript sphere does not hamper user experience, asynchronous calls make React Native apps highly performant.Serialization- Any communication over the bridge includes exchange of serializable messages.
  • Another sphere will have to keep waiting for the access thereby hampering its seamless code execution.Batch Processing- Under the veil, JavaScript code gets translated into native code after the pass over the bridge.

Before diving into the pool of React Native, I was curious to know how this thing really works under the hood. After all, developers can’t stand any black box and seeing through any abstraction is…
Continue reading “How come React Native is so Native? – Quovantis – Medium”