W3C declares HTML5 standard final

After 10 years of development, the W3C has promoted HTML5 to "Recommendation" yesterday: http://www.w3.org/blog/news/archives/4167. W3C's "Recommendation" status is the highest level of maturation, effectively making the markup language a formal standard.

Almost 20% of the world's websites have adopted HTML5, so for many, HTML5 is nothing new.

Drafting the HTML5 standard appears to have been a difficult and tiring process. It took more than 50,000 email exchanges, and the group's bug lists record more than 4,000 errors and ambiguities that had to be resolved.

With HTML5 complete, you might wonder what is next for HTML? Take a look at HTML.next, the list of HTML.next proposed elements and attributes or the list of postponed feature requests.

The trend in development seems to be towards native mobile applications rather than mobile websites, but the future of HTML and its modular design has some interesting things in store. In the long run, I think the line between native applications and web applications will blur. I think the future is better integration and more seamless transitions between the two. Standards are important and can't be here fast enough!

Comments

nod_ (not verified):

The future is now. FirefoxOS already has HTML5 apps. Because their OS makes HTML/JS/CSS first class citizen there is no difference between native and web apps.

Something similar to "installable websites" called widgets was supported by Opera since Presto 2.3 (2009). They later aligned their API to the W3C widget recommandation.

Anyone working on a FirefoxOS Drupal app? That's where I'd put my money.

October 29, 2014
Gábor Hojtsy (not verified):

Opera was experimenting with web technologies to do apps as early as 11 years ago. I was playing around with the Opera Platform SDK as part of a university project around nine years ago when it became available (http://www.operasoftware.com/press/releases/mobile/ajax-gone-mobile-ope…). Original announcement at http://www.operasoftware.com/press/releases/mobile/introducing-the-oper…

As still is the case, the most interesting thing is how to give access to local phone features and content securely (which are a lot more than what they were in 2005).

October 30, 2014
Dries:

I'm bullish that HTML/HTTP/CSS will close the gaps with native applications over time. When that happens, open web standards will have won and become the standard. I think it is going to take at least 15 years for the W3C to evolve HTML/HTTP/CSS/etc to be truly competitive with native mobile applications. In the mean time, I think we'll see the lines start to blur more and more.

I'm also excited for FirefoxOS. In order to make a mobile ecosystem take off, you need all stakeholders to come together, including consumers, OEMs, carriers and developers. I believe Mozilla is in a much better position to make that happen than the W3C.

While FirefoxOS is starting to have traction with these stakeholders, it has a *lot* of growing to do. It's going to take at least 5-10 years before FirefoxOS will be recognized as a serious competitor.

October 29, 2014