Adobe explains the real shape of HTML5

It was right at the start of 2013 when we received news of HTML5 now being classified as “stable and feature complete”…

… this is a development that is almost universally welcomed as good news; web-centric software application developers now have a stable foundation for implementation and planning the next generation of web applications.

NOTE: HTML5 is described as the “cornerstone” of the Open Web Platform, a full programming environment for cross-platform applications with access to device capabilities; video and animations; graphics; style, typography and other tools for digital publishing; extensive network capabilities.

Since January then, further analysis of HTML5 has been comparatively scant given the weight and import of this technical progression.

Stepping forward with some worthy comment this month is online marketing consultant Dave Klein of Boulder, Colorado.

Klein writes on Adobe’s own portal pages saying that HTML5 is going to be a game changer.

What shape really is HTML5?

Pointing out that the term HTML5 itself is a bit ambiguous, Klein very helpfully explains that discussion of this technology very often refers to a combination of:

• HTML5,

• JavaScript and,

• Cascading Style Sheets 3 (CSS3)

He explains that these three technologies work together and help “define the attributes” of HTML elements such as fonts, colours, styles, sizes, or the background image of a page.

HTML5 challenges and hurdles?

“[Although] CSS3 is not fully supported by today’s browsers. That aside, all the primary browsers and major web technology companies are acknowledging HTML5 as a crucial part of the web’s future and their business plans. While some browser developers are adopting the specification more slowly than others, all are moving toward HTML5 and CSS3 compatibility at a rapid pace. There is nothing proprietary about these technologies, so large and small companies alike are already developing useful software and cloud-based applications that make it easier to deploy HTML5 websites, applications and games,” writes Klein.


Where do we go from here?

We are witnessing a wider “unshackling” of mobile applications from the web stores of vendors who produce online app ecosystems — this means that browser based apps will start to behave more like native (i.e. desktop) apps even though they are written from first principles in HTML5 as the language of the web.

You can read Klein’s full commentary here.