Many views are expressed about WebRTC; What is the killer app? What is it that stops its proliferation? Which should be the mandatory video codec?…
I’ll start off with an apology, the survey was closed last week and this post was going live, then we discovered that someone has played with the results by inserting a large amount of responses in a way that made it clear that these are not authentic responses. Unfortunately Survey Monkey doesn’t have any basic security means like Captcha or identification of strange response behaviors. Maybe it was that Amazon Gift Card that was tempting this person or maybe just a strong desire to play with the survey results. Anyway, all fake results had to be manually removed, something that took a bit of time.
The complete and detailed results can be found in this presentation. In this post I would like to take a closer look at a few of them.
Making it easy to add voice & video communication to applications
If you dumb down WebRTC to the very basic thing that it brings, that is a great media engine. Anyone who had to go through the experience of building a voice & video client or service knows all the headaches it takes, and it is a never-ending story as you need to improve quality continuously. The first question of the survey was looking at what companies have used before WebRTC was available.
There were different approaches used to build voice and video communications into an application, self development was less common as it required to license some components, develop others and integrate them into one nicely working client. Hard work.
Putting aside the move to the Web and no download, compiling WebRTC into your application is a savior.
Where will WebRTC have the most significant impact?
The interesting thing is not so much what people voted for but rather what they didn’t vote for and that is service provider. I believe that the webification of communications will impact service providers in 2 ways:
- It will move communication previously handled by the service provider to other places
- Those that will jump on the WebRTC wagon will be able to create services and platforms that will enable them to build new asymmetric business models.
Microsoft & WebRTC
The survey came out just after Microsoft announced their plans to support WebRTC (ORTC, H.264) so it was interesting to hear people’s thought about this and the video codec.
People were really worried about the fragmentation in video codec and preferred both to be supported. Should they still be worried? That really depends on how this decision will be implemented in browsers and mobile devices. My guess, we haven’t seen the end of it yet.
There are more interesting results so make sure to take a look at this presentation with the complete information.
WebRTC API Platforms
We had a Webinar about this topic and Tsahi will be moderating a panel about the topic during the conference.
The response to the question – In what cases would you choose to use a WebRTC API platform? – was not a big surprise. I was hoping to have more votes for the third option, specific services in the cloud. Now, after Twilio announcing their network traversal service it will be interesting to hear what people have to say about this option on the panel.
WebRTC for mobile
In the response to the question about the readiness of WebRTC for mobile devices there was a strong consensus that there is still some way to go until it will be easy to tackle this one, mainly for iOS. During the conference we will review the complexities and give examples of how companies have solved the mobile challenge.
For more information about these and other questions take a look at the detailed results presentation.
Last but not least. An email will be sent by Upperside to the 2 winners of the Amazon Gift Card.
Your thoughts about the survey results will be happily received at the comments section below.Read more