...or maybe we should say "Don't shoot me I'm only the piano player" ;-)
Apparently, a recent comment or two by uber geek Mark Zuckerburg in his leadership of Facebook has sent several scurrying to scuttle plans for their mobile apps because the word is HTML5 was a bummer for FB mobile development. Well, let's not shoot the message -- maybe the messenger in this case, but not the message. In other words, we're suggesting there is no need to abandon HTML5 just because its fallen from favor at Facebook. But on the other hand, HTML5 may not be the best choice depending on what you're trying to achieve with your mobile app.
Um, let's back up a bit.
This all got started when a client recently complained to us,
We're so confused about mobile development for our planned CRM apps. Should we use HTML5 or go native? Facebook says HTML5 sucks.
We think we helped calm our client's tattered nerves by explaining this is not a conundrum of some sort, but simply a deployment question concerning user experience and the intents and purposes of an App in a mobile world.
So, in the spirit of our comments a couple of days ago, we thought we'd bring this question to the attention of our readers.
First, the fuss for this Client all began because someone in their IT department had either read or heard about the uber social networker himself Mark Zuckerburg bashing HTML5 during an on-stage chat during a technology geek-in last month in the Silicon Valley (actually San Francisco). But we don't think they actually attended the event, or they probably wouldn't have tossed the proverbial monkey wrench in the manner they did during a marketing technology planning meeting. The disruption was not helpful. Here is why. The trouble is (was) that Facebook had placed a big bet on HTML5 to achieve their mobile web experience and it gave them fits given the wide variety of user experience elements in FB. And they finally did what they had to: they embraced native experiences and developed their latest Facebook mobile in both iOS and Android.
But just because HTML5 didn't work for Facebook doesn't mean it won't work for anyone thinking mobile. In fact, the C[IQ] Tech Team points out that there are a handful of factors we consider when making a strategic recommendation about deploying any CRM app in a mobile setting. Here are five of them:
- User Experience. First and foremost, consider the interaction model. HTML5 works fine for apps that have a simple user experience, such as filling in forms or making clickable choices. However, if the user experience is more complicated say for something like a Loyalty Program (think Starbucks Awards on your phone), then going native may be preferable.
- Data Privacy and Security. If sensitive data capture is involved, HTML5 may be preferred in a solution that leaves all of the data on secure servers (e.g. think anything financial services or healthcare).
- Connectivity. Of course, there is always the question of dropped connections or poor reception. In such situations, HTML5 is not a good choice over a native experience local to the device.
- Device Neutrality. Until very recently the strongest argument for HTML5 was platform independent deployment -- write once deploy everywhere. Well, "everywhere" has arguably narrowed to Android and iOS (notwithstanding whatever market penetration Microsoft may make with their new mobile device platform). Yet, you need to consider your customers and how the majority of them are likely to interact with your business in a mobile setting.
- Leveraging Device Capabilities. Finally, native apps can offer the most robust and rich user experience and capabilities if on-board services can be utilized. For example, a native app can use the device's camera for capturing images like QR codes, product labels, etc. whereas relying on a mobile web app means confining functionality to the "sandbox" of the browser.
At the end of the day we caution clients to not stress over the mobile deployment question. And we also think it ill advised to react based on the words of uber geeks ;-) In our humble opinion, despite its enormous reach, technology strategy should not revolve around Facebook or whatever Facebook leaders believe is the answer or the trend. Simply determine your customer requirements (user experience, capabilities, etc.) and the objectives of your planned app, and then make a call on whether to go native or stay nuetral.
The message is valuable: HTML5 is not for every application instance. The manner in which the message was delivered and the ensuing knee-jerk market reaction it engendered... calling to mind funnier moments of the Life of Brian ...was not.
As to making those deployment technology decisions: Been there. Done that. And we can help.