Future with Ionic: What are the pros and cons of using it

If you still don’t know what hybrid apps are and how they work, this article is for you. There are four main hybrid technologies: Ionic, React Native, NativeScript and Flutter. Today we’ll start with Ionic.


What are hybrid apps? They are apps which combine elements of both native and web applications. Native applications are developed for a specific platform to solve certain problems of that particular platform (Android/IOS) having all the resources provided by the mobile device. Web technologies are generalized for multiple platforms and are dedicated to solving general problems. They can be available not only as a mobile but also as a web application having the same business logic at a core. Ionic is a standard framework for hybrid mobile app development. It allows web developers to build apps for the majority of the platforms using a single code base. It leverages web technologies such as HTML, CSS, and JavaScript and platforms like PhoneGap/Cordova to deliver the native-like experience.

When and why should we use the hybrid app approach?

Ionic is right for you if you want to save company resources or your own resources, your new project is a startup, you want to develop your business as fast as possible and don’t want to wait for a native app to be built, or you have a small business and would like to create a mobile app.  

The top reasons for making the switch from native to hybrid, based on independent research and testimonials, are the following:

1. Speed: Building for multiple platforms from a single codebase often makes delivering cross-platform apps 2-3x faster than building a native app.

2. Efficiency: According to Forrester Research, a hybrid app can save a company between 75-80% in support and porting costs compared to a native app.

3. Omnichannel: Hybrid apps can run anywhere the web runs; on a desktop, a mobile browser, as a mobile app, or PWA.

Pluses and Minuses

Big pluses

  • Write once, run anywhere
  • Use the talent you already have
  • Deliver a great user experience across platforms
  • Build for the future

Of course, hybrid applications are not without their drawbacks.

Significant Minuses

  • System overhead: The use of the web view may introduce a degree of overhead compared to native apps.
  • Third-party plugins: Hybrid apps are able to access nearly every native feature of a device, such as the camera or the gyroscope, however, only by using native plugins.
  • Framework dependencies

Why Native? (Android/IOS)

We’re comparing the hybrid approach to the native approach below to allow you to come to a conclusion, based on the pluses and minuses, that best helps you solve your particular issue(s).

Why Native?

  • Performance
  • Rich native library
  • No third-party dependencies

Minuses for developing on native

  • Longer development cycles
  • High development costs
  • Native talent hard to find
Attribute Native Approach Cross Platform Hybrid
Developer Skill Set Needed Objective-C, iOS SDK, Java, Android SDK HTML, CSS, Javascript
Distribution Method App Stores App Stores Desktop Browser, Desktop App (e.g. Electron), Mobile Browser, Progressive Web App
Speed to Develop Slow Fast
Development Cost High Low
Maintenance Cost High Moderate/low
Graphical Performance High Moderate
App Performance High Driven by use case
Access to native functionality Full native library Full native library (requires third-party plugins)
UX consistency across platforms and devices Requires separate apps Yes

After looking at the table and the comparison made above, we can see where we can use a hybrid approach to get the desired result and where is the limit beyond which it’s not effective to use that approach. For instance, with 3D games and other performance-intensive applications, a hybrid app may not be the best choice since they require more resources and a hybrid app may not be able to handle the load. But, if you want to save time, effort and cost, with an app that evolves with time, go for the hybrid mobile app approach.

According to statistics provided by AppBrain, Cordova is reported to be used for the development of events (16.81% of all Cordova apps), business (16.80%), healthcare (15.33%), finance (15.25%), shopping (13.23%), travel (12.07%), and sports (11.94%) apps. By targeting these complex categories, Cordova has a low chance of living up to users’ expectations, hence their low install rates. Still,  LINE messenger app (500 million installs), a banking mobile app by ICICI Bank (Indian largest private bank with $109 billion in assets), and the Amazon India shopping app are among the most popular Cordova-based apps.


  1. Forrester estimates a hybrid approach will save an organization between 75−80% of resources (time, finances) compared to a native approach.
  2. According to the 2017 Stack Overflow Survey, only 6.5% of all developers cited Swift and Objective-C as familiar languages. In contrast, web developers made up 72.6% of respondents, and JavaScript appeared as the most commonly used programming language in the survey.
  3. The total number of Ionic-built apps exceeds 4 million.

Top 5 apps built with Ionic

  1. MarketWatch – 500,000+  installs
  2. Pacifica – 500,000+ installs
  3. McDonald’s Türkiye  – 500,000+ installs
  4. Sworkit  – 5,000,000+ installs
  5. JustWatch  – 1,000,000+ installs

You can find the complete list here.

In conclusion, I would like to advise that you keep in mind the initial release of Ionic was in 2013, only 5 years ago. That’s not a very long period of time to grow as a competitor for Android/IOS and we can already see good results.

Good luck in using it 🙂

  • Topics:
  • DevOps

Top Stories

High Five! You just read 2 awesome articles, in row. You may want to subscribe to our blog newsletter for new blog posts.