9 Reasons HTML5 Will Change The Online Publishing Landscape

Another fine piece by Don Nicholas  at Mequoda.

Over the past six to 12 months, I’ve heard that HTML5 is going to change the entire online publishing landscape again.

Some of my developer friends have been indicating that one of the large portal-based publishers has a 20-person development team secretly banging away on HTML5 web apps that will mimic, expand and replicate on the apps you currently see on Apple and Android platforms.

Online publishers will have to use HTML5 to build web apps that are part of a larger website. The new strategy for magazine publishers should focus on web first with an HTML5 publishing platform, and have associated apps be lighter versions, pulling data and functionality from the HTML5 website.

HTML5 for publishers

The magazine industry is upon a renaissance as publishers figure out how to deliver content through tablet devices. This revival is expected to increase, as there’s no shortage of pundits praising the predicted growth of the tablet market. This is seen in a recent forecast from PwC, which predicted digital magazine circulation revenues to grow to $611 million by 2015. By the end of 2012, 40.6 million people in the US are expected to own a tablet device.

HTML5 will be part of the reason that media experiences on the tablet are so desirable. The reasons listed below shed light on this technological evolution.

As some of this information is highly technical, I’ve done my best to pull the content back and present it in a manner in which we can all easily understand

9 reasons why HTML5 will change online publishing

#1: HTML5 will provide local storage to speed engagement and make things available offline.

#2: A mobile HTML5 site can be used among numerous platforms, from iPhones to Androids.

#3: Mobile sites can replicate the feel and usability of a custom-made app.

#4: Pages can be updated in real-time, so users can see new comments without having to reload the page.

#5: Media can be used, embedded and shared more easily without needing plug-ins.

#6: Dragging items from the desktop to a browser will encourage interactivity.

#7: Better SEO, especially for flash-based sites. Currently, flash-based content does not get recognized for SEO purposes.

#8: An outline structure that will allow publishers to better manage their headers.

#9: Typography additions will allow for more fonts.

Our predictions are coming true…

Apple’s changes are slowly making our predictions come true, as subscription websites appear to be the backbone of online publishing.

Anyone following the media giant should clearly see Apple’s intent; they are not looking to get into the subscription game. Instead, they want to sell “thin” apps that allow users to access a subscription-based website.

What isn’t clear, is what happens when you want to subscribe through an app. However, regardless of that outcome, HTML5 is going to change the orientation of independent apps to web apps while putting an end to the Adobe/Apple flash debate.

If you don’t believe HTML5 is the future of digital infrastructure, just take a look at Safari, Firefox 3.6, WordPress, Apple’s OSX and Google Chrome; some major players that are already pushing support of HTML5.

The future of publishing on the Internet will be dictated by the capabilities found in HTML5, as it can sufficiently handle the demands of today’s online communities. Online publishers need to realize this potential, and begin using HTML5 as the backbone of their website and applications.

A Geekier Explanation From Wikipedia

In particular, HTML5 adds many new syntactical features. These include the <video>, <audio>, and <canvas> elements, as well as the integration of SVG content. These features are designed to make it easy to include and handle multimedia and graphical content on the web without having to resort to proprietary plugins and APIs. Other new elements, such as <section>, <article>, <header>, and <nav>, are designed to enrich the semantic content of documents. New attributes have been introduced for the same purpose, while some elements and attributes have been removed. Some elements, such as <a>, <cite> and <menu> have been changed, redefined or standardised. The APIs and DOM are no longer afterthoughts, but are fundamental parts of the HTML5 specification.[2] HTML5 also defines in some detail the required processing for invalid documents, so that syntax errors will be treated uniformly by all conforming browsers and other user agents.[3]

Leave a Reply

Your email address will not be published. Required fields are marked *