Five years ago, mobile was really a class unto itself. Today, the lines between mobile and desktop are extremely blurred and on a future collision course when everything is just content and it is all consumed from whatever device the consumer wants to use. On top of this, there is a distinct difference between a native mobile app and a responsive website that looks mobile. Confused? A lot of businesses are, too. The true definition of the mobile experience is that "you can deliver your content/message from a central point to any internet connected device for consumption." The biggest issue is knowing when a mobile responsive website is enough versus when you need the specialized experience of a true native mobile app.
Put simply, a native app is one that is coded and designed to work within the parameters of the two major mobile app stores - Apple/iOS and Google Play/Android. The creation of a single mobile app can result in the catering of said app to two totally different sets of device users. This brings the advantage of accessing the largest possible market of device users (into the billions worldwide). A mobile responsive app is simply a website or web application serving content that when viewed on a mobile device, the content will conform to the screen it is being displayed on. No extra coding needed, but a different experience than downloading and using a native mobile app.
A recent article from Business Computing World UK by blogger Chrissy Ma provides wonderful insight into this area.
So when you think it’s time for mobile, how do you know which direction to take? Here are some tips to consider:
I want an app that allows staff doctors to communicate referrals and patient info with each other securely. |
When it comes to anything medical or patient related, HIPAA compliance is a must. An app of this nature would definitely need to be native and enterprise grade which means it is not in the app stores and only available/functional on the internal network the doctors are on. You would also want to make sure that your data input and output is auditable from the database level for compliance. |
I want an app that allows my customers to shop online like they do with my current online store. |
This scenario can potentially go both ways. You can certainly develop a native mobile app for both app stores and have your content ‘pushed’ to it from your current online store, or you can optimize the coding of your current online store to be mobile responsive so that shoppers have a similar experience when using their mobile. |
I want an app that employees can access our internal business systems from while in the field. |
Assuming that your internal business software doesn’t already have a mobile entry app, then native is the way to go here. Native apps will allow for much more security and a more condensed user experience. |
I want an app to provide sales & marketing materials to my reps in the field for their clients. |
In this case, native all the way! Building a content engine that empowers your sales teams can be extremely efficient in the sharing, presenting and sending of sales & marketing collateral. You can also integrate features for digital document signatures to sign contracts on the devices. |
I want an app to serve news and information and sell advertising. |
This one is tricky as there are many CMS (content management systems) for building news and magazine related websites that produce the mobile view of your content. If you already have your site up and running and you just want to add mobile, native or mobile responsive can work here. Again there are issues that can sway this either way definitively so make sure you nail down exactly what it is you need or expect from the end user experience. |
Envoc stands ready with cutting edge talent and innovative thinking to plan and implement a mobile strategy that best suits your needs for today and tomorrow.