WebRTC on mobile is more complicated in almost every area you look at, when it comes to push notification life is easier on mobile. The trivial use case is waking up the application for incoming calls. On mobile this is done through push notification messages supported in the OS level. On the web this capability is not possible yet and requirements are a bit more complicated.
If you thought that the WebRTC MTI video codec battle is about to be settled, think again because the seeds for a new battle have been planted at the last IETF meeting. The idea is to follow the footsteps of Opus and the 2 main benefits it offers:High quality codec; Patent and royalty free… no real essential patent claims. With video, current status is problematic.
Last week Dan and I listed the important topics relevant for WebRTC discussed at IETF 92nd meeting. Here are details about access permission given to user’s media and for how long this permission persists. You probably noticed that you are not always requested to click on that Allow button in order to give access to your microphone and camera. Have you ever wondered why in some cases this is not required?
Dan returned from the IETF meeting held on the week of March 22nd in Dallas. Naturally, there is a lot of information to share. This update will only list a few of the main topics. It will be followed by dedicated posts for each of these topics.
This is the second WebRTC Standards Update coming to you from Dan Burnett and Amir Zmora.
Topics covered in this update are: Is there a security vulnerability in WebRTC with regards to detecting your IP address? The New Public Working Drafts of Media Capture and WebRTC. Enhancing media functionality of WebRTC