Does WebRTC need a change in governance?
Is it time to change the governance of WebRTC in order to keep it growing and flourishing?
Read MoreThe updated report is more useful than ever.
5 months have passed since I published my latest report "Choosing a WebRTC API Platform". I received a lot of good feedback about it, making me very happy.
My goal with this report was to assist those who want to decide which route to take: self development or using a 3rd party WebRTC API platform; and then, assist in answering the more complex question - which WebRTC API platform vendor to choose.
I've had my share of work with assisting several vendors since then answer that question and it is always a process. There are a few reasons why this one is a tough question:
For me that last one meant I had to revisit the report and update it accordingly.
This new version is a bit longer than the previous one, as it covers 3 more vendors as well as discusses the AddLive acquisition in a new and detailed appendix.
The new vendors that got added are Apizee, Forge and Sinch. More that didn't make it in this round of updates are Bistri, Hookflash, ooVoo and Respoke. Some because they decided to skip this round, others because I had to get this update out the door.
Some housekeeping messages:
I'll be happy to answer any questions you may have about the report. I am also doing my best to provide quick answers to those looking for them that don't have the money to spend.
Is it time to change the governance of WebRTC in order to keep it growing and flourishing?
Read MoreRTC@Scale is Facebook’s virtual WebRTC event, covering current and future topics. Here’s the summary for RTC@Scale 2024 so you can pick and choose the relevant ones for you.
Read More