The latest version of our Video Client SDKs, OpenTok v2.17, is now available. We wanted to update you on some of the great new features included and how you can use them.
Earlier this year, Microsoft launched the Chromium based Edge (Edgium) and leveraged the battle tested open source Chromium technology and WebRTC code base. With that in mind, we’ve added full support for Edge 18 including features like Screen Sharing.
Safari Screen Sharing
With Safari 13, you can now screen share in WebRTC enabled applications. Simply use the OpenTok API as is and you’ll be able to screenshare as you do in other browsers. To see a live demo, take Vonage Video Conferencing out for a spin.
As you know, Internet Explorer is an old, deprecated, and significantly less-secure web-browser with no native WebRTC support (hence the need for a plugin) which has been replaced by Microsoft with the Microsoft Edge browser.
Microsoft is also ending support for Windows 7, which may have been an environment where users continued to use Internet Explorer. Based on this, we've decided to drop support for IE 11 with the 2.17.0 release. We understand that many users are still browsing the web on Internet Explorer so you can still use the 2.16 version of the SDK if your applications need to support Internet Explorer.
We’ve been focusing on improving the quality of our SDK by exposing more granular APIs and making it easier to route the audio via Bluetooth enabled devices. In general, we’ve also improved the performance and reliability of the SDK. We’ve added and deprecated some APIs so I recommend checking out the release notes for a more detailed explanation.
More and more developers are building native Windows applications so we’ve solidified our SDK by adding support for Custom TURN Servers and six-channel audio devices. We’ve also enhanced the Windows SDK API by allowing developers to use the builder pattern when instantiating Session, Publisher, and Subscriber objects. Here’s a quick example:
Publisher Publisher = new Publisher.Builder(Context.Instance)
{
Renderer = PublisherVideo
}.Build();
Session Session = new Session.Builder(Context.Instance, API_KEY, SESSION_ID).Build();
Subscriber subscriber = new Subscriber.Builder(Context.Instance, e.Stream)
{
Renderer = SubscriberVideo
}.Build();To see a full sample, please check out the Windows SDK Samples and release notes. Note that you can still use the older API since the 2.17.0 version is backward compatible.
For more documentation, please visit the Vonage Video Developer Center.
If you're interested in building the Vonage Video API, sign up here.
){kind=small}
