Why The HTML5 Vs. Native Debate Obscures The Real Challenges Of Mobility
The vitriol spews on a daily basis. HTML5 or native apps? Each side is well armed with arguments and data to prove their points. This fight, destined to go on for a long while, masks some of the real problems that enterprises are facing when it comes to mobile applications. Do you have the right backend architecture for a mobile world? The right business analytics? Enterprises, brands and developers need to put their houses well in order before even beginning to answer what type of code an app will be built in.
HTML5 Or Native? Wrong Question
Most mobile discussions to-date have focused on the explosion in devices and operating systems, and the challenge of building great apps for a multi-platform world. This has given rise to the latest round of techno-religious wars, with the HTML5ers on one side and Nativists on the other.
Lost in all the shouting is a much bigger challenge—in fact, two challenges. First, the traditional Web architecture that undergirds most enterprises is rusting. Mobile is stressing the way these architectures feed data to applications, as well as their mechanisms for performance and scale—the technical equivalent of a bridge collapse waiting to happen.