We’re excited to announce the release of Vonage Video Client SDK 2.29! This latest update delivers powerful tools designed to give developers greater control over device management and APIs to enhance the user experience. Whether you're building a video conferencing app or refining an existing one, these features will empower you to create seamless, user-centric solutions.
Let’s dive into the highlights of this release and explore how these updates can help improve your application.
In our ongoing mission to provide developers with tools to improve application performance and user experience, we’re excited to introduce the qualityScoreChangedevent(in Vonage unified/on Tokbox) andcpuPerformanceChanged event (in Vonage unified/on Tokbox):
The qualityScoreChanged event provides a metric that allows developers to get detailed insights into stream quality. Leveraging industry-standard Mean Opinion Score (MOS) metric, this event could be used to alert users about degraded call quality and take corrective actions.
The cpuPerformanceChanged event provides developers with a way to monitor changes in CPU usage during a session. Developers can use this event to dynamically adapt application behavior (e.g., reducing computational load when CPU usage is high). It provides near real-time information about CPU performance changes. It also facilitates optimization strategies, especially for resource-intensive applications like video conferencing.
To explore how these events can be used, please refer to the Video In Call Monitoring Sample app here
With the introduction of the disableAudioInputDeviceManagement property (in Vonage unified/on Tokbox), developers can now override the SDK's default behavior of automatically switching audio input devices, allowing users to maintain their selected microphone for a more consistent and predictable setup.
The new publishVideo callback (in Vonage unified/on Tokbox) provides real-time feedback on the success or failure of video publishing, simplifying error handling while giving developers greater control over video operations. Additionally, the audioInputDeviceChanged event (in Vonage unified/on Tokbox) ensures that applications can notify users of microphone changes in real time, improving responsiveness and user experience. The sample app showing usage of audioInputDeviceChanged event is available here
Addressing a key developer challenge, the accessDenied (in Vonage unified/on Tokbox) event now alerts applications when users revoke camera or microphone permissions, enabling better UI feedback and actionable insights to guide users in restoring access. The usage of this event is shown in the Basic Video Chat sample available here.
Single Peer Connection is a connection-level setting that, when enabled, uses one peer connection for all streams delivered to the endpoint from the Vonage media router.
A single peer connection helps reduce OS resource usage and improves congestion control, the bandwidth, and the quality of audio, video, and screen-sharing streams. It also improves scalability on mobile devices, making it easier to support more viewers.
In this release, we have enabled the JS Web SDK to support Single Peer Connection (in Vonage unified/on Tokbox), which was previously enabled in the 2.28.0 release for Native SDKs.
Starting with version 2.29, our native Vonage Video Client SDKs for iOS, Android, Windows, macOS, and Linux leverage the WebRTC M121 framework, delivering enhanced performance, stability, and security. This upgrade brings optimized audio and video codecs, improved network adaptation for smoother communication, and better browser compatibility for a consistent user experience. With additional bug fixes and performance improvements, this release empowers developers to create more reliable and secure real-time communication applications.
The VP9 codec with Scalable Video Coding (SVC) was recently enabled for routed sessions as a Public Beta feature. The client SDK release 2.29 is recommended to unlock the bandwidth and performance optimizations delivered with VP9 SVC. SVC is a mode of the VP9 codec that offers scalable layers built into the encoding of a single video stream, including spatial and temporal scalability, for enhanced encoding efficiency and greater resiliency to lost packets and frames. This enables the Vonage Media Router to forward different resolutions from a single encoded stream which is more efficient than simulcast, used with VP8. As a result, VP9 SVC in routed sessions provides a greater ability to maintain high video quality in low bandwidth situations and under poor network conditions. Customers are encouraged to update project settings to enable VP9 SVC, leveraging client SDK release 2.29 for these performance optimizations.
With Vonage Video Client SDK 2.29, developers have greater control and visibility over the end-user experience with real-time monitoring and actionable insights at points of agitation.
The client SDK release 2.29 is now available to Vonage Video API customers using the standard environment. Please find the release notes for the Unified and Tokbox dashboards; we plan to roll it out to the Enterprise Environment in early March.
Are you excited about the newest SDK features? Do you think we left something out? Please join us on our Vonage Community Slack or send us a message on X, previously known as Twitter, and let us know how we can help!
){kind=small}
Vikram Dham is a Product Leader who seamlessly blends strategic insight with deep technical expertise. With multiple patents to his name, he excels in distilling market intelligence, crafting effective strategies, and transforming innovative ideas into world-class products. Passionate about the forefront of technology, he is currently focused on creating value in Video, AI, and Cloud. Outside of work, he enjoys running.
