First public presentation of #webrtc in webkit

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. 

It was quite ironic to see many positioning themselves as safari experts in the meantime. As Obama said to the British: “you’re hearing a lot about the privileged relation you have with the U.S.A. and what will happen after the BrExit, but would you like to know what the president of the U.S.A. thinks about it?”. 

Now that you have heard seminars and read blog posts from people that have never contributed a single line of code to webkit, or worse, what about you join us at the next meet up in San Francisco, and learn what webkit and safari developers think directly. It is important enough for them to show up.

The meet up is on Tuesday 17th, at Mozilla HQ in SF. There will also be additional talks from Mozilla experts on the latest webrtc implementations, and debugging, and representation from the founder and co-lead of the webrtc-in-webkit project.

To manage expectations, do not expect a lot of answer on questions that are not related to the open source webkit project. Apple internals, Safari, codecs (VP8, I know), roadmap and ETA, are usually things they do not and cannot comment on. Also, what existing blog post have listed under webrtc features (output device enumeration, screen sharing, …..), are actually part of different specification documents, some like screen sharing even being far being in terms a maturity. The philosophy at Apple has always been to implement specs that are done or about to, so do not expect anything else for now, and until this is stable. Voila. That should take 75% of the questions out of the table already, sorry.

Written Live from Google’s WebRTC team office in Stockholm where we prepare some next generation of improvements for all WebRTC users to enjoy. 

SF WebRTC Meetup @ Mozilla, San Francisco

Tuesday, Jun 27, 2017, 6:00 PM

Mozilla Headquarters
2 Harrison St. San Francisco, CA

17 Enthusiasts Attending

>>> Please RSVP here: https://www.eventbrite.com/e/sf-webrtc-meetup-mozilla-san-francisco-june-27-2017-tickets-35530334186?aff=meetup >>>Agenda6:00pm – 6:30m : Networking (Snacks and Drinks)6:30pm – 8:00pm : Talks• Mozilla – Firefox Transceivers implementation• Webkit – Support for WebRTC (Safari on macOS High Sierra, iOS 11)• Symphony + Cos…

Check out this Meetup →

 

Safari Technical Preview 33 – The most WebRTC-Compliant Browser out there?

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 reallyI 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.

Continue reading

WebRTC Status Update 2017 Q2

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.

Continue reading

#WebRTC Players turning to Asia for growth.

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.

Continue reading

Lies, damned lies, and #webrtc statistics!

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.
Continue reading

Webrtc in Safari Update – Q4 2016

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.

Continue reading

Overview of WebRTC Media Servers

This is a translated, adapted version of an original post by NTT’s Iwase Yoshimasa available here, with agreement from the author. As the ecosystem move quickly, some updates were added in blue and in italic.

This post describes the current state (as of september 2016) of MCU and SFU media servers used in WebRTC solutions. I hope it will serve as a quick reference for those wanting to know more about the concepts and the available projects. The details of each product introduced here are not provided, but a link to each product is, so you can read further if you want. Moreover, we almost only mention stand alone media servers, and did not touch on webRTC CPaas or PaaS. 

Continue reading