Today, for the first time since the blink / webkit fork, the Apple and Google WebRTC teams are having a working session over lunch, facilitated and in presence of yours, truly, Dr Alex. How could that possibly happen? What does that mean for WebRTC? What’s next. Let’s look a little bit into all that.
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.
Last Week-End, I did not work. After thinking about it for a moment (and catching up on Zelda and Persona 5 ^__^), I realised it hadn’t happened since November last year! It was a good time for a look over the shoulder at everything we achieved the past 6 months. Continue reading
CafeX made an announcement this week-end about their new Japanese partnership, allowing them to extend their sales reach to North and South-East Asia. Just as I had put the final touch on my “webRTC in Asia report“, with a special section on Japan with analysis of Dialogic and Twilio approach to doing WebRTC Business in Japan, another event that just stresses the importance of Asia for WebRTC vendors.
Recurrently, people are arguing on different webrtc mailing lists or social sites. Some questions are still left open: which MCU/SFU is better, which PaaS is better, should one work on webRTC in Safari? in Edge? Usually some kind of statistics is being used. While it is well known that you can make statistics say whatever you want them to, I do not always see reason to argue. Indeed, most of the time people argue about different use cases that are not opposed to each other, or implicitly define different scopes that do not overlap. I thought it would be good to clarify things a little bit by presenting several trustable source of data for browser usage, webrtc support, and define a view usual use cases for illustration.
Apple was represented by a dozen of employees at the W3C TPAC in September. The fact that it was held in sunny Lisbon late September might explain the surge in interest, in any case we were very happy to have them with us. I usually try to meet with the WebRTC team once a quarter, and we took this opportunity to go over the latest Q4 news that can be made public. Toward the end of the post, I will also give away some of my tricks to monitor public WebRTC activity in webkit.