In December 2012, Sencha engineers Jamie Avins and Jacky Nguyen posted a description of a Facebook mobile app they built with HTML5. That post, entitled “The Making of Fastbook: An HTML5 Love Story,” provides details and demonstrations of the Sencha Fastbook app.
“We thought to ourselves: HTML5 can't really be the reason that Facebook's mobile application was slow,” the post read. “In any event, we knew HTML5 was, in fact, ready, and we wanted to prove it. So we took it upon ourselves to rebuild the challenging parts of the Facebook mobile application in HTML5 in our spare time. Today, we'd like to introduce you to Sencha Fastbook, a technology proof of concept that shows how fast HTML5 can be, and demonstrates how readily HTML5 can be used to handle the toughest app challenges.”
That was six months ago, now Sencha’s CEO Michael Mullany is talking to eWEEK about HTML5 demand, tooling and the future of the technology.
Mullany said demand for HTML5 is growing for four primary reasons. “I think it's a combination of a few factors,” he said. “First, every major browser now has support for what we like to call HTML5.0--all the fundamental HTML5 features for styling, graphics, media, animation and content. Second, HTML5 browsers have reached a critical mass of installed base, on mobile in particular. Third, developers are genuinely excited by the kinds of experiences that it's possible to develop with these features. And finally, particularly within the enterprise, people have realized that putting a huge amount of engineering investment into native application development isn't a super smart move given the market share volatility among mobile devices in the last few years. HTML5 is looking really to them as the future-proof investment.”
Meanwhile, Mullany said he believes HTML5 tooling has made major strides over the last three years. Browsers now expose really fine-grained details on internals, he said. Chrome, for example, now shows you what parts of the screen are being repainted, and what's being GPU accelerated. But there's still work to be done: for example, measuring frame rates on animations is very challenging. There is little to no insight into memory consumption, and debuggers don't differentiate between framework code and user code--as just a few examples, he said.