Native vs. Hybrid: do users really care?

February 06, 2016 0 Comments

Native vs. Hybrid: do users really care?

 

 

http://www.pushtechnology.com/wp-content/uploads/2014/04/JESS3CaseStudyAppceleratorNativevsHTML5_Finals-01.jpg

This has been a continuous source of conflict and division within mobile apps developers, almost surpassing the eternal nuclear war of tabs vs. space (hey, that can be a great subject for the next article!). But first of all, let’s have a look at what are native and hybrid mobile apps.

The main difference between native and hybrid apps is the technology used to build them. Native apps are developed using the native SDK (Software Development Kit) of the platform, which developers can use in Java for Android or Objective-C for iOS. Hybrid apps, on the other hand, are developed using web technologies (HTML, CSS, JavaScript) and then, either transpiled to native code or wrapped into a native web view.

Most of the other differences are a consequence of that technological divergence. Hybrid apps mostly encourage code reuse between platforms by adding a level of abstraction over the SDKs. Therefore, you can code an app once and have it work on Android, iOS, Windows Phone, FirefoxOS, etc… On the other hand, if you want to build native apps, you will need to build a completely different app for each platform. Native apps are therefore more expensive to build and to maintain than hybrid apps. But on the bright side, native apps possess intrinsically higher performance than hybrid apps and they enjoy an effortless native UI.

Going native or hybrid has always been a fairly hard choice. Is the cost of a native app worth it? Are hybrid apps that bad in performance? To answer those questions we can look at Facebook and LinkedIn, both of which started publishing hybrid apps before switching to native apps.

Facebook CEO Mark Zuckerberg famously declared that betting too much on HTML5 was Facebook’s “biggest mistake”, and the numbers prove it. Facebook had a hard time providing a good mobile experience for its users with an hybrid app, and after switching to native apps on both iOS and Android, user satisfaction skyrocketed! LinkedIn’s story is slightly different and focuses more on the lack of development tools available at the time for hybrid apps, but they probably benefited from a better performing app overall as well.

Indeed, several studies have shown how much users actually care about app performance. 56% of users have experienced performance issues on mobile apps, and while 79% may give it another try, more than 33% will eventually head to a competitor. Further more, 84% of users think that performance is somewhat or very important in mobile apps.

So, users do care about performance, and hybrid apps are known to lag behind native apps on that. But does that mean that users care about using native or hybrid apps?

Here is a little game for you: find the hybrid apps!

Answer: all of them are!

According to Garner, more than 50% of mobile apps deployed by 2016 will be hybrid. Developers also tend to bend towards hybrid apps, with 33% preferring to build them compared to 29% for native.

Besides, new tools such as React Native (built by … Facebook!) are bridging the gap between native and hybrid, allowing developers to build near-native apps performance-wise using web technologies. It is easy to build a poor performance app using hybrid technology, but it is also possible to build great apps using those same technologies.

At the end of the day, users don’t care that much about how an app was developed, but they do care about what the app actually does and how responsive it is, so let’s just sign a ceasefire and get things done!

Originally published at www.linkedin.com.


Tag cloud