Ionic vs React Native vs NativeScript: What are the differences?
What is Ionic?
What is NativeScript?
Want advice about which of these to choose?Ask the StackShare community!
Why do developers choose Ionic vs React Native vs NativeScript?
- Ionic is most popular with Angular developers, who list rapid prototyping and its ability to reuse frontend Angular code on mobile as pros.
- React Native fans love that you can “learn once, write everywhere.” They cite its native iOS components, cross-platform capabilities, and the fact that it’s “just React” as reasons for choosing React Native.
For a front end dev like me, using a mobile framework for side projects makes more sense than writing a native app. I had used Apache Cordova (formerly PhoneGap) before (because React Native didn't exist yet), and was happy with it. But once React Native came out, it made more sense to go that way instead. It's more efficient and smooth, since it doesn't have the simulation overhead, and has more access to hardware features. It feels cleaner since you don't need to deal with #WebView, using native UI widgets directly. I also considered Flutter . It looks promising, but is relatively new to the game, and React Native seems more stable for now.
So, i am preparing to adopt NativeScript.
For years my hybrid projects used Apache Cordova.
"Let's avoid to maintain two teams and double the deliver velocity".
It was good for a few years, we had those september issues, (i.e. apple broke some backward compatibility) , but for the last years, things seems to be losing the grip faster.
Last breaking changes, for instance, seems to have a workaround, however that growing feeling that simple things can not rely on so fragile webviews keeps growing faster and faster.
I've tested nativescript not only on it's "helloworld", but also on how do they respond on issues.
I got tweed support. I opened an github issue and got answers on less than 10 hours (yes i did it on another timezone and very close to a weekend). I saw the faulty docs get corrected in two days.
The bad news is i only can adopt nativescript on newer projects, since there is no budget to revamp the current solutions.
The good news is i can keep coding on Vue.js , without vou router, but that's ok. I've already exchanged vanilla html for real native app with background magic enabled, the router can be easily reproduced.
It is using the native components to build the UI and offers the best skills reuse story. All you need to know is JS/TS and CSS. Angular 2 is also supported which leads to even more code reuse across web and mobile.This is also the best way to access the native platform APIs directly.
NativeScript allows you to reuse your JS skills to build Native mobile apps without any sacrifices. It takes a bit to learn about all possible features, but each time you discover a new one you can't help but get more and more excited.
great framework,lots of resources,great community,easy to create UI
React Native is great in that it reduces the overhead of writing native code based on a web app. If written in a good style, Redux part of the app can often just be copied or shared in the Native app - and it just works! What a timesaver.
The framework used to write the mobile apps in this project. I've chosen this because of the "write once run all" (ios and android) mentality.
We use Ionic as it is an awesome framework to build mobile hybrid apps with nativ access. Also Ionic has a nice community!
We are not currently using this product but we have very high interest in learning and using this for mobile apps.
Cross-Platform goodness. I am a noob here...learning how to implement Ionic is on the top of my ToDo's
New features of our app are developed on React Native, so we could maintain a small dev team.
100% of our mobile codebase is shared between iOS and Android. Using along with TypeScript.
used on a recent project, an internal custom app developed for both ios and android.