What is a Mobile App?

Here at Deep Blue Sky, we've recently had some good experience in the area of producing "smart phone" apps.

Last year we launched an iPhone application for local business MES, whilst this year saw the beta launch of twiDAQ for Mobile.

Both of these could be termed "Mobile Apps" but there are fundemental differences between the two, which whilst obvious to us as developers are less obvious to our clients and business partners.

The 3 types of "app"

The three types of "app" currently available are:

1. Native
2. Web
3. Hybrid

Each of these has it's own advantages and disadvantages and it is vital that you and your business understand the differences in order to ensure you get the best return for your investment.

App Type #1: Native Application

I simple terms, a "Native" application is a downloadable app which is installed and run directly from the phone/device. The Genus Trait Handbook app is an example of a "Native" application.

Native applications are written specifically for the target mobile device's operating system (iOS, Android, Windows OS...etc) and are always in it's own specific coding language (Objective-C, Java...etc).

Each operating system requires the application to be written entirely from scratch in that language. This usually requires there to be a separate body of core application code for each device on which you wish to run the application.

So, for example, say you were developing an app to run on Windows Phone and iOS devices, then you would need one body of code for Windows and another entirely separate body of code for iOS.

As the languages are entirely different, each operating system also requires a developer skilled in that particular language to produce the application. Obviously these two factors can significantly increase development costs.

Advantages:

• fast,
• specifically tailored to operating system
• feels "Native" to the device

Disadvantages:

• more costly to build
• more costly to maintain
• narrow/limited audience
• maintaining multiple "versions" of the application across the various mobile device operating systems is labour intensive

App Type #2: Mobile Web Application

Unlike the "Native" application Mobile Web Applications are not downloadable from traditional app stores such as the Apple App Store or the Android Market. Instead they are more akin to a website which has been specifically developed and highly optimised to look and feel similiar to a native app.

This means - in theory at least - they can be accessed and run by anyone with a suitably modern smartphone no matter which device or operating system they happen to be using. The twiDAQ Mobile application (currently in beta) is an example of a web application.

Mobile Web applications are usually written using "open" web coding languages (HTML, CSS, Javascript) which are the foundation stone of almost every website on the internet. The primary benefit of this is that it means that your developers/agency can build a mobile app utilising the some of the technologies in which they are already proficient. This should help bring the cost down for you and your business.

Another point to consider is monetisation. Mobile Web Apps can't be distributed via the App stores, but if you believe your app provides a sufficiently important service then you could distribute it from behind a paywall. With no middle man, this means you can pocket nigh-on 100% of the profits of your app with no for lengthly approval processes. 

Advantages:

• runs on any device (Blackberry, iPhone, any Android Phone, any Windows...etc)
• single codebase means it's easy to update and maintain
• utilizes "open web" technologies meaning it's less costly to develop

Disadvantages:

• Not quite as slick/polished as a fully native application
• Requires initial web connection - although can be made to run largely offline.
• Can only be distributed via the web - no App Store distribution network.
• Offline storage of data is limited/capped - consider if your app is data intensive

App Type #3: Hybrid Application

A "Hybrid" application is essentially an application which is developed using "open web" technologies and then packaged up into a fully native application. Once packaged this application is essentially fully native and can be downloaded onto the device and also distributed via the various App stores.

As per the "Mobile Web " apprach, Hybrid applications utilize skills in which your developers should already been fluent. Whilst there is a learning curve to understanding the technologies involved in the "packaging process", the ability access all the features of a modern "smart phone" (camera, motion sensors...etc) via a single coding language potentially allows for faster and less costly development.

A major advantage of this approach is that there is one single codebase from which it is - in theory - possible tos produce several "native" versions of your application for:

• iOS
• Android
• Blackberry
• Windows Phone
• WebOS
• Symbian

...which pretty much covers the entire smartphone market!

It's worth considering that this technology is still relatively new, but a vibrant commuinity means that development is proceeding a-pace, with new capabilities being added at every turn.

Advantages:

• Single codebase produces multiple applications - extremely cost effective.
• Takes advantage of open web technologies in which your developer team will be already skilled - cost effective
• Native Application benefits - distribute via app stores, runs on device, has access to all features of device

Disadvantages:

• Perhaps not 100% as slick as a fully native application
• Potential for issues with debugging across various platforms as not writing pure "native" code
  Estimate Ballpark Costs

Final thoughts and recommendations

I you're looking for your app to reach the widest possible audience and also be ready to respond to changes in the mobile web market then either the "Hybrid" or the "Mobile Web Application" are the best options. These will also be the most cost effective in the long term both in terms of initial build cost and overall maintainability.

However, if you're happy to only target a specific device/operating system then perhaps the more polishied experience of a Native application is the best option.

If you're unsure, I would suggest erring on the side of caution and looking at either Hybrid or "Mobile Web Application" approaches.

Of course this is only a basic overview and it's important to recognise that each project needs to be approached on it's own merits and requirements. If you're looking to produce your first app, why not speak to us at Deep Blue Sky today?