WebRTC was the #1 most requested web platform feature for Safari. Now coming to macOS and iOS: <a href="https://webkit.org/blog/7726/announcing-webrtc-and-media-capture/" rel="nofollow">https://webkit.org/blog/7726/announcing-webrtc-and-media-cap...</a><p>You can even try it out now on Safari Technology Preview: <a href="https://webkit.org/blog/7627/safari-technology-preview-32/" rel="nofollow">https://webkit.org/blog/7627/safari-technology-preview-32/</a>
SO excited about this. Data-channel and all. Non-jailbroken torrenting on iOS at long last :P
<a href="https://webtorrent.io/" rel="nofollow">https://webtorrent.io/</a><p>Also, definitely worth trying out this AR.js demo if you're running the beta:
<a href="https://freinbichler.me/apps/web-ar/" rel="nofollow">https://freinbichler.me/apps/web-ar/</a><p>Always thought it was a little peculiar that the Media Capture APIs are tied to what is otherwise a very data/protocol-oriented spec.<p>Wish we could have had a camera feed in a canvas element on Mobile Safari a few years ago without having to wait for the entirety of WebRTC to be vetted. :P<p>---<p>And now, for my own unrelated Web API peeve:<p>Beyond service workers and all that jazz, I'm a little bummed out that the Pointer Events API isn't even <i>listed</i> on the Webkit Feature Status page:
<a href="https://webkit.org/status/" rel="nofollow">https://webkit.org/status/</a><p>It just seems like such a pleasant unification of all of the input-type APIs (mouse, touch, pen, hypothetical future peripherals...)<p>At least touch events have a "force" property with Apple Pencil input in the meantime. No tilt though.<p>Maybe next year :/
ive dreamt of this for years!!! so excited.<p>quick question: i noticed that the camera isnt available on iOS 11 if you put a web-app capable page on to your homescreen. when you open the page in full screen, mediaDevices is undefined. is that just an iOS beta bug?
So now they'll start supporting Opus at last, or they'll find another excuse not to support free codecs? Once they'll support it, AAC can be thrown out in the garbage.<p>And when are they going to support MSE[1] in iOS Safari?<p>1. <a href="https://en.wikipedia.org/wiki/Media_Source_Extensions" rel="nofollow">https://en.wikipedia.org/wiki/Media_Source_Extensions</a>
Anyone else feel like Apple is the new Microsoft and they hold the world hostage by only updating their products every couple years with features we actually want? It seems like just as the unrest is about to hit critical mass they spring into action and implement just enough to placate everyone for another couple years.
We're not out of the woods yet: <a href="https://thenewdialtone.com/hold-apple-webrtc-ios-party/" rel="nofollow">https://thenewdialtone.com/hold-apple-webrtc-ios-party/</a>
I'll take a quick moment to share my favorite web app which uses WebRTC: Instant.io [0]. I use it all the time to transfer files among local devices, or to send medium to large files to friends.<p>[0] <a href="https://instant.io" rel="nofollow">https://instant.io</a>
It would be interesting to see surveys about mobile IPv6, will it get along with P2P? Will mobile users get P2P video this way or have the operators crippled end-to-end connectivity?
I saw this yesterday on twitter and my thought was "they don't support webrtc yet?!? seriously?"<p>It sometimes baffles me how apple is holding up progress on the web - and that they aren't criticized more for it.
Apple and Microsoft waited five years to deploy this thing. Given how quickly it was implemented and adopted by other browsers, I have to wonder what their motives were for deliberately not integrating it; because frankly they could've done it pretty quickly at any point in the last five years.<p>I remember having to integrate WebRTC through cordova (thank goodness somebody did it first) a couple years ago, and wondering why on earth Apple didn't find time or money for this. libwebrtc has been stable for years, it represents effectively no security risk, it performs well on all of their platforms. It truly boggles the mind.