Back in 2016, our founder discussed the three things WebRTC can’t do. At the time, we were receiving several questions from our customers about the use of plugins, so we wrote a blog post about the limitations of this young technology. Since then, the technology has significantly
Last year, we sent out a survey asking you to share your experiences and challenges as a webRTC developer and were astounded by your response. Some of the survey results were as follows: Industries that are building WebRTC apps: Online Education– 17% Telehealth– 17% Video Chat/Social– 15% Customer Contact–
A common topic of discussion around communication use cases is “Synchronous or Asynchronous?” This is especially true in telehealth discussions I’ve been in over the last year, but the topic comes up in other areas too even if the terminology used may be different. In this issue
For the past few months we have developed an app focusing on interacting with contestants in live broadcasting, supporting thousands of subscribers and implementing a gamification/rewarding system. The game is juggling with different frameworks such as TokBox, Red5, AWS but also web socket (using BlueSocket from IBM
