- Truly native: not using a WebView (like you do in Ionic 2)
- Although you write JS, all the widgets are rendered as native platform widgets
- Open Source
- Good community and documentation
- Flexbox
- Lot of support from facebook
- https://github.com/react-native-material-design/react-native-material-design
- https://github.com/marcshilling/react-native-image-picker
- I personally have a bit of experience with React and that might translate into RN a bit
- https://github.com/jondot/awesome-react-native -- a loot of resources
- The way it compiles HTML to native code is a blackbox. Meaning that if something goes wrong, there might be no way of fixing it (keep in mind that the fb team is VERY active on the project)
- Component packs seem shady (few github stars)
- Angular2 + TypeScript
- Rapid prototyping
- Still in Beta
- Angular still not mature enough
- https://github.com/driftyco/ionic/tree/2.0 ... it doesn't look so trust worthy to me
-
Same codebase for both iOS and Android
-
Faster development time (we already know JS and don't need to learn Swift or catch up on Java)
-
Nice workflow (hot module replacement)
-
https://www.youtube.com/watch?time_continue=19&v=juWhxCz1Wmg
-
People generally recommend Cordova-based solution such as Ionic unless your application requirements have performance, usability, or integration requirements that leverage the hybrid Native mobile frameworks.
- I'd go with RN, one week of dev time that we gain using Ionic might not be worth risking the app being sluggish.
- Some Component: https://github.com/react-native-material-design/demo-app/blob/master/src/components/Toolbar.js
- Facebook Ads Manager
- Discord