You will need to decide what is more important for you – quality or latency. Trying to optimize for both is bound to fail miserably.

Lowcode and nocode or old/new concepts that are now finding their way to Communication APIs. Here’s the latest developments.

The biggest challenge you will have when implementing WebRTC group calling is estimating optimizing bandwidth use.

WebRTC is a building block to be used when developing solutions. Comparing it to solutions is the wrong approach.

WebRTC requires an ongoing investment that doesn’t lend itself to a one-off outsourced project. You need to plan and work with it longtime.

Hearing FUD around WebRTC IP leaks and testing them? The stories behind them are true, but only partially.

What WebRTC did to VoIP was reduce the barrier of entry to new vendors and increased the level and domains of innovation.

With FIDO coming to replace passwords in applications, CPaaS vendors are likely to decline in 2FA revenues.

What was nice to have is now becoming mandatory in WebRTC video calling applications. This includes background blurring, but also a lot of other features as well.