They didn’t think of voice or video chat sessions. And neither should you.
Let’s see how two vendors are using these capabilities
MailChimp is an email marketing service for users to send email newsletters. As such, it has little to do with voice and video communications. I have been using it for my own needs for the past two years and was pretty surprised when I saw it made use of WebRTC.
Under the profile settings section of the service, a user can update his profile picture (not that I understand for what purpose). At MailChimp, they enable to upload an image in the same way that many other services on the web enable, but they also allow users to take a picture of themselves using their webcam. To achieve that from inside a web browser, they make use of WebRTC’s getUserMedia API.
To get over the non-supporting browsers, MailChimp simply decided to not show the option of taking a photo. You can see this in the screenshots below, comparing the Profile settings page of MailChimp on Chrome versus MailChimp on Internet Explorer:
Until recently, Whatsapp was a mobile only service that existed solely as a mobile app. That has changed with the introduction of Whatsapp’s web interface, available at https://web.whatsapp.com/. The web interface works great and has most of the functionality available in its mobile application.
While the most obvious thing to do with WebRTC for Whatsapp would have been to introduce VoIP calling (something I’ve suggested in the past), it took the approach of adding other functions first – mainly the ability to take photos via the webcam and capture voice messages.
Think about it. A messaging service, focused on communications, with rumors abundant on plans to introduce VoIP – and they use WebRTC to gain access to the camera and the speakers of your laptop. Nothing more.
The end result? Users get the same experience they expect from Whatsapp on their mobile directly from their desktop browser.
In Whatsapp’s case, the challenge of browser support with WebRTC was overcome by ignoring non-supporting browsers. Whatsapp web interface launched first on Chrome only, and is now also available on Firefox and Opera. Missing are Internet Explorer and Safari – the two browsers that don’t support WebRTC yet.
And that’s even BEFORE we’re talking about the upcoming VoIP capabilities in Whatsapp.
Why is this important?
WebRTC enables a lot more than just voice and video interactions. The data channel, not covered here, allows sending arbitrary data directly between browsers. WebRTC offers access to the camera and microphone.
Many vendors tend to neglect the non-video-chat capabilities of WebRTC and that is a mistake. When thinking of WebRTC, make sure you take note of all of its capabilities