Survey Results: What WebRTC Developers Think about Frontend, Backend and Browsers

04/08/2014

Some obvious and surprising results from the WebRTC developers survey we had two weeks ago.

Remember that survey? The one with questions about preferences of developers in WebRTC?

There was a giveaway attached to it, which has run its course. The 3 lucky winners have already received word and I assume they have received the digital copies of their books. That said, the survey is still open for developers to speak their mind (I’ll be monitoring it once in a while).

And now for the interesting part – the results.

What kind of development do you do?

WebRTC is for the web. I always said that, but here we see it clearly. 60% of the developers are either frontend or backend. Telecom comprises only 21% of the votes. Using the notorious 80-20 rule(s), you can say that Telecom is but 20% of the use cases WebRTC is suitable for.

Your frontend framework of choice

When it comes to frameworks, Angular.js rulz. A fifth of the developers are doing mobile using native – I thought we’d have more of these.

Your backend tool of choice

Want to use WebRTC or do anything in the future with communications? It is time to learn a bit of Node.js. It is the most popular choice of all.

Who will be getting WebRTC first?

Somehow, people believe Microsoft will be first with WebRTC before Apple. I have an opposite view on it, but that’s just me.

Best way to learn WebRTC

You all LOVE webrtcHacks.com.

If you are looking for an in-depth analysis of the results, then Chad did just that on webrtcHacks.

I’d like to thank all those who participated in this survey.