RSS

Tag Archives: native app

e-Health and Mobility – Strategy in a Nutshell

There are some staggering statistics recently released by Forbes regarding smartphones and apps. According to Forbes (www.forbes.com) there will be 1 billion smartphones sold in 2013, which is twice the number of PC’s predicted to be sold that year.  By 2016 there will be 10 billion mobile internet devices used globally, which is 50 times the size it is today.  Between 2010 and 2011 the time spent on mobile apps began to outpace the time spent on the desktop or mobile Web.  In the same time period there was a 91% increase in the time users spent on mobile applications. By 2015, mobile application development projects targeting smartphones and tablets will out-number native PC projects by a ratio of 4-1. Between 2009 and 2014 the market for cloud-based mobile apps is projected to increase by nearly 90%.

So what does all this mean ???

The mobile revolution is well and truly here. Organisations of all sizes need to have developed a solid and robust mobile strategy, or face being left behind by clients and competitors.  Whilst there is still some contention over the best strategic approach to mobile application development, there is no doubt that mobile applications are front and centre in leveraging market opportunities, client engagement, process efficiencies, and strategic innovation.

In a recent blog post I proposed the inclusion of a Mobile Enterprise Application Platform (or MEAP) as an integral part of any mobile strategy. Of course, this particular strategy depends on the nature of the organisation and its key mobility objectives; however MEAP should not be overlooked when considering a long term view to deployment of multiple different mobile applications, using multiple back-end systems, across any device.

For medium to large sized healthcare organisations, a MEAP based mobile strategy has several advantages over a natively developed application, which is often built with a pre-defined range of objectives, or based on one back-end system.  In this scenario, a mobile platform approach is superior because it:

–          Enables the organisation to customise a solution into fit exact requirements, tailored to the business needs and processes

–          Can provide a competitive advantage, as no one else has that particular mobile application

–          Ensures that changes to the mobile solution are immediate, flexible and more cost effective

–          Is not restricted by the type of mobile device. Mobile platform applications built using HTML5 ensure availability on any mobile device

–          Aligns to organisational “bring your own device” policies (if applicable)

–          Ensures that any development code (apps or API’s) can be re-used to help build other apps

–          Fits into the organisations long term strategies and e-health vision to provide mobile solutions for other uses, for example

      • Bedside medication management
      • Bedside electronic progress notes and electronic care planning
      • Capturing of client and staff incidents, risks, compliance and improvement initiatives
      • Mobile business intelligence and analytics
      • Mobile clinical assessments
      • Information management (eg, mobile access to policies or corporate documents)
      • Others ???

The above examples are likely to need data integrated from multiple in-house systems, which plays into the hands of a mobile platform. While organisations may not require mobility solutions for all the above examples right now, establishing a mobile platform caters for immediate AND long-term organisational use of mobility, even if the future state is not known.  The mobility platform approach has already harnessed recognition across all the major ICT industry research groups including Gartner and Forrester, and is a key component of the ICT Strategy toolkit.

 
4 Comments

Posted by on November 30, 2012 in e-health, mobility

 

Tags: , , , , , , , , , , , , ,

Mobile app strategy – what approach is right for you ?

The mobile application revolution is here.  Apple’s app store reached 25 billion downloads this year and offers more than 700,000 apps. In addition, there are more than 600,000 apps available on the android store. Organisations are realising huge potential by utilising apps to entice customers, create market awareness, provide information, remain relevant, be competitive, increase efficiencies, and enhance productivity.  With the popularity and promise of mobile applications, organisations who fail to have a defined mobile strategy will not realise the competitive edge that come with the mobile application revolution.

A key part of an organisations mobile strategy is consideration for how mobile and web applications can be built and delivered. The three most popular approaches are:

1.  Native App

  • A native application is specifically developed for a particular device and mobile operating system (eg, the app is solely developed for either android, apple, blackberry, or windows devices/systems). Native apps provide the best user experience, performance, and access to device functions (eg camera, contacts, etc)

2.  Mobile Web

  • Mobile web apps can run in most browsers on most devices. For example, a web app for an iphone would run in Safari. A web app for a windows mobile phone would run in Internet Explorer. The disadvantage is that they are limited by the capabilities of the browsers they run in, so are currently unable to access all the features and functions on the local device (eg camera, geolocation, etc). The app itself isn’t actually downloaded onto the device, so there is no software or app to install. Mobile web apps have inferior performance compared to native apps.

3.  Hybrid

  • Hybrid apps provide the best of both worlds. Like mobile web apps, hybrid apps can run in most browsers on most devices on the single code base, and gives access to all of the device features.
 

Native

Mobile Web

Hybrid

App performance

Excellent

Good

Very Good

Development speed

Difficult

Fast

Moderate

Can run on multiple devices / platforms

No

Yes

Yes

Device access (camera, gyroscope, accelerometer, etc)

Full access

Partial Access

Full Access

Offline access

Yes

Yes

Yes

Reuse source code for other applications

No

Yes

Yes

Allows for “Bring Your Own Device” (BYOD)

No

Yes

Yes

Advantages Great performance.

Rich user interface

Can use all device features

App runs on any device

Fast development

Simple maintenance

No need to install new software

Updates appear automatically

All users on same version

App runs on any device

Fast development

Can use all device features

All users on same version

Disadvantages One app developed per platform/device

Users must manually download & install app updates

Users may ignore updates, resulting in different app versions

Has limited device access

Slower performance

Very good performance, but not as good as Native

The most appropriate mobile development approach for an organisation depends on the requirements and intended use of the app. As discussed in an earlier blog, research firm Gartner developed a concept called “the rule of three”, where they encourage companies to consider the mobile platform (web/hybrid) approach to mobility when they need their mobile solutions to:

–          Support three or more mobile business applications

–          Support three or more mobile operating systems

–          Integrate with at least three back-end data sources

So the choice of app development strategy you make depends on what you wish to do with the app, your organisations long term vision, the underlying business and functional requirements and intended use of the app.

 
1 Comment

Posted by on September 28, 2012 in mobility

 

Tags: , , , , , , ,