This week, I want to focus a bit more on developers…
This weekend I want to put some focus on WebRTC developers. From time to time, I am asked where can resources for developers be found. There are a few seminal posts on the web for that. Probably the most notable one is the Getting Started post on HTML5Rocks. Only problem is, it is almost a year old, it is basic, and the standards have evolved a bit since then.
I’d also want to give a few more insights – not just the ones with code in them – but some that have a bit of an explanation of what goes behind the scenes. Here are my developer tip posts this time around:
- Dmitry Dragilev has been doing a lot of postings out there lately about his company’s new widget and capabilities. The latest one (besides his interview here this week) is on Mozilla Hacks and it includes a few tips on how to get things right in the negotiation phase of setting up a session between browsers.
- Carl Ford provides the reasoning behind Google’s decision to skip signaling in WebRTC, ending with an interesting view: “If you want to build for the future, developing WebRTC with only one signaling protocol will limit your possibilities.” While I am not sure I agree, it does make for a very interesting read – if you have an opinion of your own – please voice it.
- A bit older is Chris Matthieu’s guest post on this blog about the using Node.js with WebRTC. The reason I am mentioning it is because two months after it was published, it is still one of the most viewed posts on this blog, so I guess developers are finding value in it.
That said, if you are starting out with WebRTC, you should definitely go for Alan Johnston’s WebRTC book.
And another small announcement is that next week, there will be another Chris Matthieu post here for developers, so stay tuned.
–
Enjoy your weekend!