Tag Archives: HTML5

WebRTC: Live web audio/video chat without plugins

Most of the design and development technologies we work with every day are in ‘evolution’ mode, not ‘revolution’ mode. Enhancements are made, bugs are fixed, but the leaps are relatively small. A browser here adds support for the latest HTML5 canvas feature, a device there adds an API for better map coordination. Nifty, but a little light on the ‘wow factor.’

With the release of Firefox 22 this week, though, there’s a browser advancement that has the potential for a real leap: WebRTC is now baked-in and turned on by default. That means both Chrome and Firefox have it up and running in their latest versions. It will soon be ubiquitous (or perhaps ubiquitous-ish until IE follows along…).

Why is this so great? WebRTC is a W3C standard that allows for real-time communication (thus the RTC) in the browser — audio chats, video chats, whatever. No plug-in for users to download and install. Cross-platform and cross-browser compatible. Just code and go.

It will soon be much more trivial to just throw a video customer-service chat on a help-desk website. Or bake it into a community website to allow for in-site community chats. Or integrate it with the many more social networking sites with varying results depending on the site (you can let your imagination run on that one).

The possibilities are pretty remarkable. It’s a great case of where the technology itself has been around a long time, but by establishing a standard, the power is in the interconnection. Like, I don’t know, almost all Internet-based technologies.

There’s a good getting started tutorial over at HTML5 Rocks, and you can also jump off of the WebRTC home page. Either way, it’s worth a click-around. I think this will be big.

The Evolution of HTML5 (and the Browser)

The grandly-named “Global Developer Survey” was released recently, sponsored by Kendo UI (makers of an HTML5 framework). As you might imagine, it focuses entirely on HTML5, and presents a fairly rosy picture.

They surveyed 5,000 or so developers from around the world and asked them about their use of HTML5 — what kinds of apps they build with it, which parts they use the most, what kinds of platforms they target, etc. Given the sponsor, it’s no surprise that more than two-thirds of respondents believed that HTML5 is important for ALL developers. Color me a little skeptical at that, but we’ll move right along.

But one part of the results that stood out to me was the focus of app development efforts by the surveyed developers: 60% were targeting desktop apps, while 26% were targeting mobile and 14% tablets. When asked what kind of software specifically the devs were building this year with HTML5, a whopping 87% said desktop websites/web apps, while only about half said mobile websites.

This generally tracks web traffic by platform (as of May 2013, in North America, only about 12% of web traffic was from a mobile device), which may make this more ho-hum. But it’s that ho-humness that is surprising. It has only been in the last version or two of most major browsers that HTML5 support has gotten more robust. The majority browser on the desktop, IE, still doesn’t support over a third of the spec! Meanwhile, support on mobile platforms has been more robust for quite a while.

Perhaps this gives hope that with so many HTML5 developers working on the desktop, the desktop browsing environment will get better for HTML5 — and, one hopes, more nimble in general, with the pace of adopting newer standards (3D Canvas graphics with WebGL, anyone?). And there are some signs that this is happening, albeit glacially. Chrome is poised to be the biggest browser on the web in North America any minute now (it’s almost tied with IE as of May 2013′s statistics), although the recent jump in browser share has been so sudden that it’s hard to know if it’s an anomaly.

Kudos to Kendo UI for sponsoring such an extensive survey, even if the participant selection was skewed. It would be interesting to get a more generalizable swath and see if the same desktop/mobile dichotomy holds true in other technologies (e.g., Java, Objective-C) as well.