Skip to content

Instantly share code, notes, and snippets.

@cipas

cipas/nativescript-vs-ionic-vs-reactnative.md

Last active April 17, 2017 19:59
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save cipas/fec1e31715092b59621bb214dc1880dc to your computer and use it in GitHub Desktop.
Save cipas/fec1e31715092b59621bb214dc1880dc to your computer and use it in GitHub Desktop.
Download ZIP
NativeScript vs Ionic Framework vs React Native
Raw
nativescript-vs-ionic-vs-reactnative.md

NativeScript vs Ionic Framework vs React Native

Pros & Cons

  • Ionic CLI is a delight to work with, there are some aspects of the CLI such as text coloring, file template generators that are better than NativeScrtip’s CLI.
  • It’s easier to get started with Ionic if you are coming from a web-development background, as NativeScript uses XML for it’s UI it will be easier for native Android developers to get started with it as XML is used to create UI in Android.
  • Both have support for Angular 2, but you can use NativeScript without Angular using plain TypeScript.
  • The debugging experience of Ionic is easy and quick than in NativeScript.
  • For Ionic, if you wish to use native device features such as camera, file storage, etc you will have to rely on third-party plugins. For NativeScript, you do have plugins that are created by the NativeScript community but you can use native device features if you want right out of the box.
  • Ionic has a reach ecosystem of servies and products that you can choose which will not only help you in development but also provide some reach features to be used in your app.
  • This kind of ecosystem is not available with NativeScript at the time of writing this post.
  • The performance of NativeScript is better than Ionic Apps, as you might expect.
  • Ionic web technologies to write and render the application, and requires PhoneGap/Cordova bridges to access native features. Then it will try to reproduce native behaviors to provide the best user experience. React Native will render using native components. This means that the user experience will generally be closer to other native apps as they will follow the patterns imposed by the operating system. The hiccup is that this only works when the bridging components have been written for React Native.
  • NativeScript doesn’t force you to share templates between mobile platforms, but instead it chooses the native version of each component even if the UI source code is a single set.
  • Ionic Framework has been in stable for release only a year and now they are expecting everyone to learn a completely different version of the framework.

Conclusions

  • While the result of RN is native, it requires bridge components to be written for each platform in order to use them, which brings it back closer to a hybrid framework.
  • With Ionic, you definitely do not have to worry about platform-specific behaviors. But with React Native you may have to in order to provide the most seamless experience for your users.
  • With Ionic you will be in a more familiar territory: classic HTML and CSS. With React Native, you will have to learn how to style and create your user interfaces using their own HTML-like components, it’s not hard, but it’s new.

Sources

http://blog.backand.com/angular-2-nativescript-vs-react-native/ https://www.thepolyglotdeveloper.com/2015/11/nativescript-vs-ionic-framework-should-you-switch/ http://pointdeveloper.com/nativescript-vs-ionic-framework-pros-cons/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment