#ReactNative – Pros and Cons #100DaysOfCode #coding #react #reactjs @reactnewsletter @ReactJSNews

  • When we first heard about React Native, a framework that enables building an app for multiple platforms, we were thrilled.
  • One team, one codebase and the potential to scale an app for iOS and Android using a fracture of resources required in native development is a great promise.
  • A few years ago, Facebook officially announced React Native, a powerful framework with the promise of cross-platform compatibility.
  • The major selling point of React Native is shorter development time.
  • Facebook puts a lot of resources to ensure React Native’s reliability and also to guarantee a constant development of the platform.

React Native: One team, one codebase and potential to scale an app for iOS and Android using a fracture of resources required in native development is a great promise.
Continue reading “#ReactNative – Pros and Cons #100DaysOfCode #coding #react #reactjs @reactnewsletter @ReactJSNews”

Why does React emphasize on unidirectional data flow and Flux architecture?

Why does #ReactJS emphasize on unidirectional data flow and #Flux architecture?

  • The view is a function of the application state.
  • View components subscribe to the stores and automatically re-render themselves using the new data.
  • As the state can be mutated by both controller and view, sometimes the data flow becomes unpredictable.
  • In two way data binding the view is updated when the state changes, and vice versa.
  • By keeping the data flow unidirectional you keep a single source of truth i.e. Store.

Read the full article, click here.


@Hashnoder: “Why does #ReactJS emphasize on unidirectional data flow and #Flux architecture?”


The official docs say that it gives you the control over how data flows throughout your app. I didn’t get this. How is this principle violated if I decide . Tagged with ReactJS,JavaScript,Flux.


Why does React emphasize on unidirectional data flow and Flux architecture?