When mission critical mobile apps go bad all hell breaks loose

Defining what a mission or business critical mobile application is can be a tough discussion. Mobile is often seen as a simple extension of the platform. This week a story surfaced that helps us focus in on what this can mean in the real world and also shows us all why we have to treat Enterprise Mobility with a seriousness that reflects the reliance on any apps we push out to our users and/or customers.

This is classic case of an app whose function in isolation would not be considered mission critical – however once the legacy systems or processes have been removed the lack of the app or the failure in performance can have much wider consequences.

How Critical is your mobile application?

We can think of the critical rating your mobile application in one of four areas

  • Mission
  • Business
  • User
  • Process

I will delve into these four in a subsequent post but the real takeaway here is to make sure you evaluate the possibilities and severity as if we were post deployment. So the fact we do not have the app today does not mean we will can say ‘well we do not rely on this mobile application now so we won’t in the future’.

Design, Design, Design.

So on to my normal rant about why Design is so crucial in an Offline First application. Now we have to think about Design of the app PLUS the effect of the design (think resilience and robustness) in a wider context to our organisational disaster recovery and fall back plans.

Loss of data for the User, as we have seen in the above story, is just one of many points that need a healthy discussion well before any real design work is done ie the UI and UX. This will require a foresight into a post deployment scenario and may well need collaboration with other stake holders in the organisation.

Change is the only constant

Even if we get a grip on all the possible scenarios today it is highly likely that new and potentially fail causing changes will occur in the platform, dependant services, Mobile OSs and a variety of other factors outside our control.

Our best defence here is to have a robust testing process which then needs to go hand-in-hand with a simple, controllable versioning system. This is where MobileCaddy excels with Lifecycle management being integrated into all areas and components of our deployed application.

To find out more and see this in action yourself click below to arrange a free demo.

Arrange a demo



Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Scroll to Top