HTML5

At the turn of the 2010s, the Web was going through a period where smartphones were proliferating, social networks were exploding, and developers were running up against a frustrating limitation: how to write code that works everywhere without having to rewrite everything for each platform? HTML5 arrived in this context, not as a simple technical update, but as a redesign of the Web’s architecture.

The story begins in 2004, when Ian Hickson, then at Apple, cofounded the WHATWG (Web Hypertext Application Technology Working Group). This group brought together engineers from Apple, Mozilla Foundation, and Opera Software, all convinced that the foundations of the Web needed rethinking. The W3C eventually incorporated their work into a broader vision of an open platform.

HTML5 wasn’t just a new markup language. It was a coherent set that encompassed the Document Object Model, CSS style sheets, JavaScript, and a whole series of standardized interfaces for video, geolocation, local storage, and graphics. This comprehensive approach was a boon for developers.

Matthew McVickar, a web developer at Ocupop, expressed it clearly: HTML5 formalized practices that developers were already using, but in a makeshift way. With the JavaScript interface for geolocation, for example, mobile browsers accessed GPS without going through proprietary solutions. No more workarounds, it was time for standards.

CSS3 added its contribution by transforming how page appearance was managed. Developers now created visual effects directly in the browser, without going through Photoshop or other external tools. The time savings were considerable, the flexibility increased.

Local storage marked a break with traditional cookies. This function allowed the storage of large volumes of structured data on the client side, thus enabling Web applications to run without an internet connection. Graphics capabilities were also enhanced with native support for SVG vector graphics and the Canvas element, which opened the door to 2D and 3D animations via JavaScript.

Ian Hickson, who had meanwhile moved to Google, emphasized the technical rigor brought by HTML5. Previous versions of HTML left room for interpretation: two browsers could implement the same specifications differently while claiming to respect the standards. HTML5 established precise rules that guaranteed true compatibility.

But deployment faced obstacles. Video crystallized tensions: no single standard for compression, streaming, or digital rights management. In 2010, Apple refused Flash on the iPhone and iPad, preferring its own version of HTML5. Microsoft and Google developed their approaches, forcing developers to juggle multiple versions of their code.

Hui Zhang, a professor at Carnegie Mellon and cofounder of Conviva Inc., knew the problem well. For him, video remained the thorniest aspect of online content. Bringing together codecs, streaming protocols, and rights management required time and compromises between industry players.

The W3C planned in 2014 to finalize the HTML5 specification. Philippe Le Hégaret, head of the interaction domain, nevertheless tempered expectations: development continued. The organization regularly received requests to add features, such as voice-to-text conversion directly in the browser.

The WHATWG took a radical turn in 2011 by abandoning version numbering. HTML was a “living standard” in permanent development, a vision that fit the reality of a constantly evolving Web. Ian Hickson said it bluntly: HTML development would continue as long as the technology remained relevant.

This technology showed how standardization could stimulate innovation without sacrificing compatibility. It also illustrated the importance of collaboration between industry players in advancing the Web.