On February 4th Mozilla and Google announced that their respective browsers could now talk to each other via WebRTC. This is another big milestone in WebRTC’s path towards becoming available in all modern web browsers, albeit, today only in an early development build of Firefox, version 21+ (currently Nightly and soon to be Aurora).
We’ve also been working hard on making OpenTok on WebRTC work with both Firefox and Chrome so you too can enjoy all this cross-browser goodness!
Off to the races
The first thing that you need is version 21 or higher of Firefox, currently available through the Aurora FTP site and Nightly site.
This weekend we hosted 175 hackers for Music Hack Day San Francisco in our office for the third consecutive year. Music Hack Day is a unique event—it doesn’t use huge prizes or big name judges to draw a crowd. It’s one of the rare Bay Area hackathons where (seemingly) most attendees actually aren’t local—giving it a fresh vibe, with new faces and ideas every year.
Last week I wrote a post that called for more hackathons to be purpose driven—Music Hack Day is not one of those of events. Instead, Music Hack Day is an event driven by a desire to learn and a shared passion for music. These types of events are, without question, very good for the hacker ecosystem, and Music Hack Day is a shining example of how they should be run.
There is a new breed of Ninjas taking over. Instead of covert agents wielding nunchucks and wearing ninja-yoroi, you’ll find gentler individuals donned in yoga pants, weaponed with guitars and Adobe CSS. LiveNinja, our App of the Week, is responsible. They’ve created a searchable marketplace of experts (Certified Ninjas) in the topics you care about, using the OpenTok API to facilitate live video consultations.
Last Thursday, I had the pleasure of being a part of the Mobile + Web developer conference held at the Hilton Hotel in San Francisco. I spoke on a panel about where development was headed in a world where Web + Mobile are the two predominant platforms. There were four of us total, and we had a great time talking about how each of us lived in, and viewed the future of development in this two platform world. The panel was composed of (beyond myself) John Hammink, a QA engineer from Mozilla, Jonathan Smiley, a partner at Zurb building their own HTML5 framework, and Ted Drake, a senior accessibility engineer from Intuit.
It’s fashionable to be cynical towards hackathons. There’s too many of them. They exploit developers. They rarely have useful products come out of them.
Even if you’re not a cynic, at some point you have to wonder—why do the overwhelming majority of hackathon projects die succinctly and unquestionably following the event? It’s often a foregone conclusion for the hacker—go to the event, try to win the prize, and then go back to your job the next day.
And there’s nothing wrong with that. Most of the time people go for fun. It’s a good learning exercise. As a first timer, the sheer novelty of it all gives you enough energy to power through an entire weekend.
About six months ago, Microsoft released an alternative proposal to the W3C WebRTC 1.0 Working Draft, dubbed CU-RTC-Web. Like all W3C groups, the WebRTC Working Group enlists membership from a majority of the industry, including names like Nokia, Cisco, Google, and Mozilla. The most important question raised by the Microsoft proposal is how the Working Group would react to criticism of its draft proposal, and whether Microsoft would accept the published APIs of the Working Group, even if CU-RTC-Web is not adopted. So what exactly does this mean for the development community?
The Microsoft draft outlines a low-level API that allows developers more direct access to the underlying network and media delivery components. It exposes objects representing network sockets and gives explicit application control over the media transport. In contrast, the WebRTC API abstracts these details with a text-based interface that passes encoded strings between the two participants in the call. With the WebRTC draft, developers are responsible for passing the strings between communicating browsers, but not explicitly configuring media transport for a video chat.
PennApps hackathon was the largest college hackathon in the world and it took place this past weekend. It produced some of the best/most entertaining hacks that I’ve seen at any hackathon: Remote controlled battle bots, Automatic Wifi Authentication for facebook friends, enlarging media seamlessly from one to multiple mobile screens, app that messages you if you forget to put required items in your backpack, exploring neighborhoods from the comfort of your couch with augmented reality, just to name a few.
Looking back, I would say that this hackathon was a smashing success, and I’m sure the other sponsors would say the same. From my perspective as a developer evangelist, here’s why PennApps turned out to be a legendary hackathon and what we can learn from it:
Last weekend we had the pleasure of sponsoring University Hacker Olympics. Unlike your typical hackathons, this one emphasized connecting University students with industry professionals.
Personally, I thought the event was innovative in the field of recruiting. In the traditional interview process, sometimes great candidates were dismissed because their shyness or nervousness inhibited them from performing. 1-1 interviews can be intimidating, we’ve all been there. From the interviewer’s perspective, asking candidates to solve problems does not provide any valuable insight into how pleasant it would be to work with them in a working environment.
A number of developers have asked for ways to help end users diagnose potential problems that disallow them from being able to successfully video chat using OpenTok. A while ago we introduced a troubleshooter page that test a user’s network, hardware, and software to check things like ports, camera, and Flash version to be sure that they have what they need in order to use OpenTok.
While this tool has been useful for diagnosing problems, one obvious pitfall is that you have to send your users to our website—away from your experience.
Developing an iOS App itself is a huge undertaking: you want your product to be beautiful, interactive, and functional. That’s why Parse makes so much sense, it helps you avoid writing a backend server to power your App by giving you a data store and providing the most basic web services. These days many web services are incredibly powerful and help developers do really amazing things, like OpenTok, but they are targeted at having a backend. That’s where Parse Cloud Code comes in: it gives developers the ability to leverage the best of a back-end server in the path of least resistance.