The Evolution of HTML5: From Birth to Standardization

This article explores the eight-year journey of HTML5 from its initial draft to final standardization, and its impact on the web development industry.

Born from Web 2.0

The initial draft of HTML5 can be traced back to 10 years ago when the Web Hypertext Application Technology Working Group (WHATWG) was established. During the Web 2.0 era, faster internet speeds enabled users to participate in content creation and sharing rather than just consuming it. Video and animated content became prevalent, and websites evolved from static to dynamic. To make web pages interactive, developers relied heavily on Flash or SilverLight based on the .NET framework.

HTML5 was created to reduce browsers' reliance on external plugins for advanced effects. Previously, all videos and animations required Flash for playback. HTML5 supports direct embedding of audio and video, as well as handling multimedia content like video and images within web pages.

Although the first HTML5 draft was released in 2008, it gained significant momentum after Steve Jobs' 2010 article arguing that Flash was no longer necessary and that HTML5 could functionally replace it. With the rise of touch mobile devices like iPhone, which didn't support Flash, the mobile web began embracing HTML5.

Rapid Development and Confusion

Starting in 2010, with smart mobile devices increasingly supporting HTML5, more web development began using the technology. In 2010, YouTube launched an HTML5-based player. By 2011, 34% of the world's top 100 websites, including Twitter, used HTML5. Adobe also discontinued Flash player development for mobile devices.

Companies like Facebook bet heavily on HTML5, abandoning Native App development in favor of Web Apps. However, after two years, Facebook ultimately abandoned HTML5. Mark Zuckerberg later admitted that fully betting on HTML5 was Facebook's "biggest strategic mistake" in mobile development.

Behind this lay fundamental issues: WHATWG and W3C had prolonged debates about technical standards—WHATWG wanted rapid iteration while W3C preferred a long-term stable standard, leading to a temporary split. The final HTML5 standard remained undefined, and APIs related to hardware access were incomplete. Additionally, HTML5 performance struggled to match native applications, ultimately causing Facebook to return to native app development. Currently, over 60% of Facebook's users access via mobile devices.

A New Spring

The final standardization of HTML5.0 two days ago is beneficial for developers, reducing compatibility work. Future standards like HTML5.1 and HTML5.2 will be determined in coming years, enabling web developers to do more with HTML5, better meeting the demands of diverse and mobile-friendly web content.

Games and applications developed with HTML5 can spread quickly across various social platforms without requiring users to download from app stores. Easier distribution also brings good interactive experiences to users quickly.

The spring for HTML5 has just begun.