Native vs Ionic vs Nativescript vs React Native

From time to time I stumble upon some articles that I like from reading the first sentence. This is one of them. I am also thinking of the performance vs ease of use between writing native and hybrid mobile apps. I like how refreshing it felt when I read that when putting your app in a Webview you should not expect much performance(for more complex apps of course). Not that I didn’t know or experienced that but it’s always better if you find that someone else is thinking the same.
I also found this one while searching if somebody used Elm with Ionic (just for fun! :)). I remember Ionic made something about not having to use Angular if you don’t want to. Of course you’ll miss all the components made especially for it I guess(will check again later :)).

As a small (but growing) engineering team, being as efficient as possible with our development effort is massively important to us. We want to give our wonderfully engaged members, the best functionality we can as quickly (and as bug free) as possible. Hence as preparation for building our upcoming App, we wanted to review the pros and cons of Native vs Hybrid mobile development frameworks, and see how the latter lived up to it’s promise of write once, run anywhere.

Source: Native vs Ionic vs Nativescript vs React Native

JavaScript: from callback hell through then-hell to generators+promises

Lately I've been refactoring and then refactoring and then some one of my JS apps every time I ...

Learn more

About Iliyan Trifonov

Web Developer, Blogger
Tagged , , , . Bookmark the permalink.