Hybrid or Native Mobile Development?

Reasons why I decided to start a project using Ionic over Native

Posted by Alex Ferrer on 1 year ago

This is my first post in english about my experiences in mobile development. The main goal is to improve my writing and to share with other developers what I am learning every day as a software engineer. In this case I will talk about the reasons I have choose Ionic Framework over native and in which situations.

To start with, the first worry when we have to choose a technology to develop a mobile application is to choose between native technologies directly or use some other framework to develop applications using web technologies as we known as hybrid mobile apps.

Also, If we develop an app using hybrid technologies the first worries of developers are the obvious difference in performance and the availability of cordova plugins and the maintenance of them. Of course, native development is the best choice to build applications with the most performance and user experience, but since Ionic 2 are out of the box my every day work is most productive.

This last years I have been working in a lot of mobile projects, from native Android (Java) and iOS (Objective-C) to Hybrid development using Ionic. By the moment I didn’t try React Native yet, which will be my next the quest and it seems the future of mobile development and a pretty cool framework. At this moment I am working in a small startup company where we don’t have the time and neither the human resources to develop every application natively for iOS and Android at the same time, thats the reason we tried Ionic as an alternative and we are so happy with it.

Next, I will explain the reasons why I choose Ionic over native to start a mobile projects:

  • If you have a simple project without compex requirements and you want to start the development without spending resources in multiple versions of the app for each platforms.
  • If you want to develop prototypes fast to show them to the customer before to start a bigger native projects.
  • If you work alone or in a small team (1-3 people) Ionic is a good way to develop in an agile way for multiple platforms at the same time.
  • Ionic 2 is much better than their previous version Ionic 1, and apps looks amazing and with a performance closer to a native experience.

Those reasons (or opinions) are the result of my experience since I started in mobile development. I think this ecosystem will continue with better technologies and frameworks in the next years. But, by the moment, we should enjoy the framework which we are comfortable with and know all the features of it to buildoptimized applications for the best user experience and quality.

Share this post!