We’ve all experienced video calls where our hardware hasn’t performed as expected – whether video didn’t display, or audio input levels were too low, it can lead to frustration.
With our new Hardware Setup Widget, we’re aiming to solve that problem. Now you can set your users up for success by enabling them to test their camera and microphone settings before their call begins. On top of that, settings can be saved so that any future conversations will get off on the right foot.
The Hardware Setup widget works with OpenTok.js and can be easily added to your existing web application. It has a pre-built UI and uses the Device Selection API.
In our previous post about packing more punch into the OpenTok platform we talked about a new release cadence and support policy. In order to improve our users’ experience of the OpenTok platform, we will now provide support for the current and previous versions of the client libraries.
As a quick follow up to this, we’re announcing the first set of client libraries that we will no longer be supporting.
Over the last several months, we’ve focused on why end-users have difficulty connecting to OpenTok sessions to try to understand how we can make this easier.
We found that many end-users failed to allow hardware access to their cameras and microphones through Google Chrome and Mozilla Firefox dialog boxes. Some of you have already tried to solve this problem on your own by creating a custom UI that highlights the prompt. However, the OpenTok platform should solve this problem for you and your end-users.