Although still in draft form, HTML5 is seeing widespread adoption and implementation. But there’s still a fair amount of pushback and skepticism about whether HTML5 is really ready for production.
I recently asked Sharp about how HTML5 is changing development, in terms of what’s developed and how. Our interview follows.
How is HTML5 going to change web apps?
We’re seeing it already, but with time, I believe people won’t access the web apps through the gateway of the browser. The “browser” part will be invisible and the web app will just be part of the computing experience.
What is HTML5 going to make easier? How is it going to aid performance?
For example, adding audio and video is a doddle. Adding real-time two-way communication between the client and the server is a matter of a few lines of code and it has an extremely low barrier to entry.
Developing for a multitude of browsers has long been the bane of web development. Is HTML5 going to make this simpler?
Remy Sharp: HTML5 first and foremost gives developers a consistent specification that all the browser vendors can work from. HTML4 didn’t have this. In fact, some of the key technologies we rely on today were reverse engineered into specs, which is why we see subtle differences. HTML5 is specified right down to the tiniest detail, ensuring that all the browser vendors are singing from the same hymn sheet. This means that new HTML5 APIs are easier to work with, since the implementations are the same.
Most importantly, HTML5 and related APIs provide native technology that means I, the developer, do not have to rely on Flash or some other plugin technology to solve the problem I’ve been faced with. I only have to learn open web technologies and I’m able to create interactive, real-time, graphics-rich web applications — should I chose to.
This interview was edited and condensed.