As HTML5 continues its march to glory, is it the end for portals?

HTML5

The portal has just about always been the future of the web. A home page of information that helps bring links and information together, proponents have stated for more than a decade that the portal represents the key gateway to knowledge. As a concept this will persist, but as a specific technology well I believe soon, it will simply seem like a pathway to the past.

The reason is simple: HTML5. The last twelve months have seen HTML5 transition from a next-generation-maybe to the probable future of the web. Big companies, such as Apple and Microsoft, have been open in their support of the framework. In short, everyone has started to recognise the huge momentum behind HTML5.

But before we look at why HTML5 represents a death knell for yet another legacy technology, let us first understand why people use portals. The first reason is UI consistency; portals provide a nice easy way to provide a common look and feel across all portlets (applications).

The second reason, interoperability. Enterprise portals and public web portals – such as Yahoo! and iGoogle – allow organisations and individuals to run multiple apps, bringing together disparate apps running from different servers into a single browser window. These apps maybe running on very diferent server platforms, but once the app is viewed on a portal page, the user is none the wiser that it is actually coming from a different source.

Third, portals allow portlets to communicate and share data. This is a powerful feature that allows one application to “tell” another about anything. For example you may in one portlet find a person, once selected it “tells” another portlet who the user found. That second portlet might now show that persons account details, without the user having to do anything. Of course that interaction can happen with multiple portlets at the same time, powerful !

So, people use portals for UI consistency, application interoperability and application interaction. But the hype surrounding portals has dived since the dot com days of the late 1990s. Analyst Gartner reports the portal provider market has narrowed considerably, dropping from more than 50 vendors in 2003 to fewer than a dozen in 2010.

This brings us neatly to the future direction of portals – and the inevitable rise of HTML5. Portals are convenient, but they are also a pain. Small app windows mean only limited information can be shown.

Portals came out of an era when running one browser window sapped computing power. Now users can easily run multiple sessions, so why limit your information horizons to a collection of small windows?

HTML5 helps to overcome technical concerns, too. New APIs within HTML5, such as cross document messaging, mean information can be communicated in a secure manner regardless of the source domain. Consistency, meanwhile, can be addressed by CSS, which helps ensure the look and feel of HTML5 documents.

With a free HTML5 offering benefits across the key selling points of the portal, why would users choose to pay for and implement a separate technology? As HTML5 continues its march to glory, they will not.

SHARETweet about this on TwitterShare on LinkedInShare on FacebookShare on Google+Pin on PinterestDigg thisShare on RedditShare on TumblrShare on StumbleUponEmail this to someone

Dharmesh Mistry is the CTO/COO of Edge IPK, a leading provider of front-end Web solutions. Within his blog, “Facing up to IT”, Dharmesh considers a number of technology issues, ranging from Web 2.0, SOA and Mobile platforms, and how these impact upon business. Having launched some of the very first online financial services in 1997, and since then delivering online solutions to over 30 FS organisations and pioneering Single Customer View (Lloyds Bank, 1989) and Multi Channel FS (Demonstrated in Tomorrow’s World in 99), Dharmesh can be considered a true veteran of both the Financial Services and Technology industries.