Ionic vs NativeScript: What are the differences?
Ionic and NativeScript can be categorized as "Cross-Platform Mobile Development" tools.
Some of the features offered by Ionic are:
- Performance obsessed
- Utilizes Angular and React
- Native focused
On the other hand, NativeScript provides the following key features:
- 100% Access to Native Platform API
- NativeScript is free of charge as an open source project
"Allows for rapid prototyping" is the top reason why over 234 developers like Ionic, while over 55 developers mention "Access to the entire native api" as the leading cause for choosing NativeScript.
Ionic and NativeScript are both open source tools. Ionic with 38.4K GitHub stars and 13.1K forks on GitHub appears to be more popular than NativeScript with 17.1K GitHub stars and 1.26K GitHub forks.
Sellsuki, Edify, and eTobb are some of the popular companies that use Ionic, whereas NativeScript is used by Work Box, Zege Technologies, and GeekyAnts. Ionic has a broader approval, being mentioned in 392 company stacks & 350 developers stacks; compared to NativeScript, which is listed in 10 company stacks and 23 developer stacks.
What is Ionic?
What is NativeScript?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using NativeScript?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
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
We use Ionic as it is an awesome framework to build mobile hybrid apps with nativ access. Also Ionic has a nice community!
Cross-Platform goodness. I am a noob here...learning how to implement Ionic is on the top of my ToDo's
used on a recent project, an internal custom app developed for both ios and android.