Native or hybrid apps? The new choice for NZ CIOs

Trying to decide if your app should be iOS or Android compatible? Forget it; you should be deciding if your enterprise mobile app will be native or hybrid...

While one leads to the other, there are some important distinctions to be considered.

The enormous popularity of smart mobile devices and the advent of Bring Your Own Device – using your own computer or mobile device at work – have increased the appetite for enterprise mobile apps.

Customers as well as staff members are expecting access to information anytime/anywhere via these revolutionary devices.

Enterprise mobile apps are basically apps designed for businesses, to make life easier for staff and/or customers.

Sulabh Sharma, director of Kiwi app development company Sush Mobile, says Chief Information Officers of New Zealand companies are being asked to make decisions on the nature of their company's mobile apps without all the facts.

A Native app is developed specifically for a device's Operating System and needs to be adapted to work with other devices.

But a Hybrid app takes web-based, HTML5-designed apps and "wraps" them in a "host" platform so they can operate across different operating systems and devices.

While Native apps can better access a device's features, Hybrid apps function across platforms, ideal for the Bring Your Own Device scenario.

"While Native apps have traditionally been the standout in terms of performance and appearance, Hybrid apps are fast gaining popularity for their multi-platform flexibility," Sharma ays.

"Hybrid app development offers CIOs another, truly flexible option when trying to figure out the best way to deliver their company's app plans.

Expanding Options

In the past the biggest decision has been which operating system to commit to, but the options are expanding according to Sharma.

The mobile landscape is highly fragmented with competing Operating Systems, devices, network providers, customer preferences and technologies, such Near Field Communication and Bluetooth.

To navigate these choppy waters a robust mobile strategy is required she says, which focuses on sustainable development.

You need to get it right at the front-end of the development process - you can choose to develop a native, hybrid or web app with either a specific-platform or cross-platform approach.

The Cross-Platform approach offers an opportunity to reuse major proportions of code and logic across multiple platforms, but demands a high degree of customisation to optimise the user experience for each device or platform.

For applications that require augmented reality, offline data with transactional integrity, advanced Operating System features such as in-App purchases and iCloud access, a high level of animation, real-time geo-location tracking, audio/video interpretation and image processing, Native apps are the way forward.

Sharma says while web-based HTML5 apps have always had the advantage of working across multiple platforms, they have been limited by an inability to access device hardware such as GPS, camera or contacts.

Hybrid app technology allows HTML5 cross-platform technology to connect with device hardware, effectively making the most of Native and HTML5 strengths.

Enterprises have high degree of flexibility in choosing the right path. There is no confirmed best approach but enclosed is a guide for you to choose the right application architecture.

Sharma says regardless of the pitfalls and advantages of each approach, the growth of both Hybrid and Native technology is exciting.

"More options to choose from can only be a good thing," she adds. "Companies can select a platform that will best serve their needs rather than trying to force an idea to fit.

"The best thing a CIO can do is take expert advice on which option would best suit their business needs.

Which do you prefer, native or hybrid apps? Tell us your preferences below