The Numbers Game - From Web 2.0 to HTML5

Blog /The-Numbers-Game- From-Web- 2dot0-to-HTML5

Forget about Web 2.0, everyone is talking about HTML5 but what happened to Web 3 and 4?

CIOs, and CTOs don’t have it easy these days. It seems as though their IT departments had finally caught up to Web 2.0 infrastructures with their socially integrated services, and now their faced with a deluge of increased activity around Mobile, Tablet and Desktop HTML5 opportunities. All this occurring at a time when internal development resources already seem to be stretched thin, and now there is need to support the development of both native mobile applications, and the possibility of Responsive Web as a solution across devices and desktops.

It comes as no surprise that the backbone of what I call Web 3 is the HTML5 open standard, so why deviate from that naming? HTML is simply the text-based markup that describes the semantic sections of Web pages, and naming a part of your text won’t help store data on the client device, send real time financial data, or help in determining the right CSS to use for a mobile device.

In truth, what we think of HTML5 is actually a grouping of varied technologies and languages, each with equal weight: HTML, JavaScript APIs, CSS3, SVG, combined with best-practices and open-source frameworks. The World Wide Web Consortium has already been working on HTML5.1 for a few years now, even before the full ratification and browser adoption of HTML 5.  HTML5 is really a snapshot in time of a constantly evolving combination of standards, and these standards seem to be effectively standardized on change.

 I consider Web 3 is what can be done with that snapshot now: Web pages, provisioned with enterprise services through AJAX, using client-side MVC where appropriate, while fully supporting multiple devices (mobile to desktop) via single code base in a responsive and fluid experience.

Corporate Managers have some instigators for this new technology stack adoption, as it seems parallel streams of issues all end up pointing to a Web 3 solution:

  • Instituting a “bring your own device” policy, or common operating environment with tablets and mobile workforce in mind has led to new devices that need to be accommodated within existing legacy Web systems.
  • A retreat from rich Internet technology stacks, such as Adobe’s Flash, Flex,and Air products, can have IT moving towards the development capabilities of open standards.
  • Cost savings through the panacea of “write once, deploy anywhere” has many looking away from pixel-perfect design into size-independent, fluid, accommodating layouts that work on mobile phones and tablets.
  • Possible issues with app-store for submission and control, as well as timely updating has many concerned for pulling parts of the ecosystem closer to the enterprise.
  • Mobile device capabilities (GPS, cameras, Video) and speed (quad core CPUs, dedicated GPUs) have blurred the once noticeable line of demarcation for Web application performance between phones, tablets and desktops.

Over the next few blog entries, I’ll be discussing the latest in how HTML5 is delivering on what are considered Web 3 technologies, while focusing on development across all Web capable devices, discussing the confusing world of Web standards and their support, showing the power of responsive web design, capabilities of mobile Web toolkits, and even the hybrid apps that feature Web code within native wrappers (hello internal apps store!).

Post Date: 9/23/2014

default blog image Joy Dwyer

About the author