Hi Jon,
eric jonas

Hi Eric,

Thanks for the questions. These videos don’t require prior experience with my O’Reilly videos.

React Native relies on a few assumptions:

  • Familiarity with Node and NPM
  • Some familiarity with building iOS / Android apps

While there are definitely parallels between Ruby/Rails and Node, they have their own conventions that need a bit of experience to unpack. At the end of the day, React Native is a NPM package that has a generator for setting up a project for running JavaScript code in the virtual machine available on the mobile operating system.

Regarding Redux: there are definitely other libraries which are either have more features (like mobx) or are less pedantic about accessing global state (like Facebook’s Flux implementation). I picked Redux because I’ve used it on a number of projects recently with some success and it looks like Eric Vlad Vicenti was also using it when he introduced Navigation Experimental. Dan Abramov (creator or redux) would be the first to say that there are other options out there. I think you just need to pick something that:

  • Enforces a consistent architectural pattern
  • Has a burgeoning developer ecosystem
  • Encourages Flux principles (like uni-directional data flow)

Regarding the breaking of React Native: Facebook and the larger react native team are incredibly active on GitHub Issues for facebook/react-native. This is a risk with adopting any new technology that’s still not 1.0. The best thing to do is see if the productivity gains from using React Native are outweighed by the benefits to your particular project.

Show your support

Clapping shows how much you appreciated Jon Lebensold’s story.