this is our review after we spent some time using video sdk.

The first issue we encounter was that there is no Typescript support: it is much more difficult implementing something as complex as video calls and livestreaming without type definitions. We had to rely on the documentation on your website, which was less accommodating than having it in the code itself. For example, Meeting has Participants, and Participant has Streams, so I had to search for those interfaces in different parts of your docs. Sometimes I even had to refer to your source code on Github to understand how certain parts of your API work; the documentation for arguments for callback methods for events is is quite lacking. Another important issues was getting the srcObject for the video tag.

I also had an issue with the admin panel on your website: I could not access my secret key. The API key was visible and there was an option to copy it to clipboard by clicking on the icon next to it, after which there was a visual cue that the contents were in fact copied - the clipboard icon turned into a checkmark for a few seconds. On the other hand, the secret key, which had similar UI, could not be copied to clipboard. The clipboard icon is the same as it was for the API key, but clicking it did nothing in Safari, but it did copy the secret key when I tried it in Chrome, although even then it did not give the same visual cue that copying the API key has.

There were issues with basic functionality with the js sdk. I installed it through npm and I had issues importing it into my application. The sample code on your homepage imports it as default and names it VideoSDK, but the very next line of code is initializing a meeting by calling ZujoSDK.initMeeting, event though ZujoSDK is not declared anywhere. Since there were not type definitions for your sdk, I had to log the exports into console to figure out the basic structure of your sdk.

Once I did manage to import what I needed and authenticate, I had issues starting a meeting. The meeting was created through my backend, and I did receive the meeting ID which I used to initialize the meeting. Even though the micEnabled and webcamEnabled options were set to true, neither the camera nor the microphone acutally turned on. There was not even a request by my browser to use them. Manually turning them on by calling meeting.unmuteMic and meeting.enableWebcam also did not work.

Another thing to consider is the name of your product. VideoSDK is a very generic term and searching specific issues related to it yields poor results as there are many other products that are described as a video sdk.

Overall, yours is the fourth video call API that I have personally implemented, and it was by far the most needlessly complicated and provided me with the most issues, even with the most basic functionalities.