The cat is now out of the bag: youenn fablet is going to present part of its WebRTC effort, actually WebRTC in webkit, during a public presentation! For some happy few, this was known and prepared for some time now, and some readers of this blog and Korean WebRTC group member were looking forward to it.
Since the announcement of WebRTC in safari, a lot of blog posts, webinars, and meet-up have surfaced. That was not a surprise for anyone really. I have been writing about webrtc in webkit and Safari for years now, so I was in no hurry, and waited untill the noise level went down. While people where quickly to point the (perceived) mistakes and missing pieces, I do not think anybody has done a real overall comparison between existing browsers see, overall, which was most webrtc-compliance, i.e. future proof. This post is trying to address this.
There are a lot that would like you to believe that you can only be successful if you are in the silicon valley. While there are undeniably huge successes there, more and more Asia is innovating and raising to the level of their American counterpart. Today, a Singaporean CPaaS company, “WaveCell” announced a successful Series B. Let’s see what we can learn from them.
It’s been a long time there hadn’t been any communication about any WebRTC roadmap, so it is understandable than when Mr. Huib, the new WebRTC PM at Google, made a formal announcement on discuss-webrtc mailing list, followed-up by a tweet from Tech Lead Justin Uberti, everybody went curious. Unfortunately, a lot of what has been written about those announcements and tweet is … inaccurate. Very recently I was given the opportunity to speak at the Sydney’s WebRTC meet up and mingle with people from snapchat, tokbox, dolby, CoViu, ….. I thought it would be a good opportunity to write down things I know (and I can speak about) with respect to the status of WebRTC and what’s to come.