Understanding apps: mobile, native or responsive

  • no single “best” technology
  • differences are subtle
  • costs vary significantly

Background

Maybe you have decided to get an app built. You will not build it yourself (obviously!) so you have done your homework properly, went out and got a few quotes (that’s more than 2, please) to establish the cost of getting this built. The only problem is the total for each of them varies between 15 and 90K. How to tell them apart, beside the Kia vs BWM price tag?

If you are targeting a mobile market the first thing you must understand is the various types of “apps” that can be built. Same as you understand the difference between a car and a UTE when you buy a four-wheeler. To make your life easier, the broad advantages and disadvantages to each type of apps, are listed in the table below.

In case you didn’t know also, “App” is short for Application. But of course you knew that!

What is a “native” app

facebook-mobile-vs-native-app_EmpireOne-Group_1
Specimen number 1
The EmpireOne Facebook page, viewed from two “different apps” (web and native) on the same mobile device.

A native application is designed and built to run in a specific environment. In the mobile world, there are many environments, namely iOS, Android, Windows8 Mobile and Blackberry being the most popular ones. Native apps require to be manually installed on the device also, from Apple’s App Store, Google’s Play Store, or others.

To remember: requires one app built per target environment.

Because the app was written for a specific environment, it will not run in a different one. This is why iPhone apps don’t run on an Android phones, and vice versa. So one application per environment has to be built.

What is a “web” app

The Web application is also designed and built for a web environment, which means it’s accessed via any web browser. Given all smartphones and tablets have a web browser pre-installed, all web apps are automatically compatible with them, without having to be installed first.

This makes a web app not specific to iPhones or Android. In other words, it’s built once and runs everywhere.

To remember: uses web technologies to build a single application for all environments.

So in essence a Web app is nothing more than a website which is designed for mobile devices, usually with functionality which is more specific to mobile devices.

What is a “responsive” web app

Responsive-web-app-EmpireOneResponsive web app
Responsive web design, illustrating the same app over multiple devices, computer, tablet and phone. see demo

Responsive websites use special code (known as CSS media queries) to adapt the layout of a website to various device sizes. This allows for the same application to look differently on a mobile phone in landscape mode, a tablet in portrait, or on a desktop computer.

To remember: uses web technologies, also, to build an app which runs equally on mobile, tables and desktops.

Same as with web applications, a responsive web app uses nothing but a web-browser to run, making a single application to be compatible with all smart devices and without having to be installed first.

Try this demo and resize your browser. See? This is responsive!

Telling them apart

facebook-mobile-vs-native-app_EmpireOne-Group_2Specimen number 2
The EmpireOne Facebook page, with feedback alert, viewed from two “different apps” (web and native) on the same mobile device.

Telling the difference between applications using web technologies (Web apps, or Responsive apps) versus those that don’t (Native apps) is not always easy to the untrained eye! The primary difference is how seamlessly the application integrates with the environment.

Native application are started from the phone itself, whereas web technologies require you to start a browser first. A native app also feels, by definition, more native! Think of when you pick a date, when you see an alert box, or have to change application settings – all environments are slightly different in that respect (see specimen 2).

Still all gibberish? Lucky you, the following section and table should help, hopefully!

The non-technical talk

From a business point of view, it really boils down to two things; features and money. It is important to understand what your are getting built because the price tag will vary significantly and the possibilities for your app could be limited if the wrong platform is picked. All good developers will discuss this with you prior to giving you an estimate or at the very least, before starting any development.

If they don’t, or if you still don’t understand what it means after they did, the following table should help sussing out the differences.

Native, Web and Responsive apps compared – although responsive web design is
more of an extension of a Web app and not usually compared with Native apps.
Pros Cons
Native Apps provide a better user experience due to how they integrate more seamlessly with the device. They are usually used for games, application with access to phone settings or sensors, or needing to run without a data connection. However they are environment-specific and usually more expensive to develop. See how much apps cost
  • Better user experience
  • Access to all phone hardware (NFC, sms, contacts, notifications, etc)
  • Discoverability via the ecosystem (AppStore, GooglePlay, etc)
  • Apple will keep 30% of all revenues (not so much Google)
  • In most cases more expensive mobile strategy
  • Stores (namely Apple’s) will try to dictate what you can and cannot do
Web Apps provide a good (not great) but consistent user experience across all platforms. They are usually used when cost is a consideration and a tightly integrated user experience is not required as much. They will run in all environments and in all devices (tablets vs phones, normal and high resolution screens – eg. retina) out of the box. However they have some, but limited access to device data and hardware.
  • Built once, runs everywhere
  • Updates are deployed once and published everywhere, no update or review process
  • Can be retrofitted to desktop website via responsive web (below)
  • Monetisation requires paywall to be setup (no pay-per-download)
  • Limited access to device features (eg. geolocation)
  • Doesn’t leverage the app ecosystem to be found (organic growth via search engines, not via Store)
Responsive Apps are very well suited for large content-driven websites, where functionality is accessed via desktop and mobile devices. They tend to have a less “native” look, but nonetheless well suited to all environments. Predominantly used for content-driven or transactional apps. Same as Web Apps, they have limited access to device data and hardware.
(on top of Web App pros)

  • a single application needs building and maintenance for all platforms and devices
  • integrates with enterprise security more easily
(also, on top of Web Apps cons)

  • initially more costly than a simple Web App (tho’ in the end, has a better ROI)
  • requires an active data connection

In the end…

If you are investing a serious amount of money into a mobile app (native or web), it is imperative to have a digital partner you can trust to help you make the right decision. Always keep the following in mind, and in doubt, contact us or comment on this article; we’ll help you with your decision.

  1. if you cannot do without using the phone hardware like accelerometer, flash or NFC, chances are you will need a native app.
  2. if you are planning on releasing many changes often and quickly, anything web based could save you thousands.
  3. always remember your audience and if all they require is access to your site from a mobile device, you don’t need a mobile app!

As you now understand, native apps and web technologies both have their advantages. In the recent years, the concept of Hybrid app has emerged providing with best-of-both-worlds approach. Make sure you ask your digital partner on this!

Enjoyed this post? Please share it or leave a comment below. Then never miss another piece, subscribe to our newsletter or read us via RSS to have everything delivered to you. Yay!

Written by

Managing Director of EmpireOne Group in Sydney, Sebastien has made a life of understanding both sides of the fence. Born in Canada and educated as a self-started business software engineer, not a single day passes without finding Seb tweaking a process, system or piece of code.