Twilio Programmable Video is back from the dead
Twilio Programmable Video is back. Twilio decided not to sunset this service. Here’s where their new focus lies and what it means to you and to the industry.
Read MoreWebRTC isn't much different than its predecessors. Except for its approach.
When it comes to VoIP, you can say that the relevant solutions consist of 4 different parts:
The end result? Long specifications with too many ways of interpretation. It becomes everything and nothing at the same time.
Ever tried running an interoperability test between 2 video endpoints of 2 different vendors? Got any video? Great! Have you tried the same vendors when adding to the requirements list security? Or NAT traversal? Or a newer/older codec? Maybe screen sharing?
It fails miserably. There are just too many permutations to test, each with its own interpretation by each of the vendors.
And then came WebRTC.
What it did best was to keep things simple. NAT is mandated and engrained within the specification from day one. There's no option for security – or rather EVERYTHING is secured – there's no other option.
What can I say? WebRTC chose the Tango over other dances…
Twilio Programmable Video is back. Twilio decided not to sunset this service. Here’s where their new focus lies and what it means to you and to the industry.
Read MoreStruggling with WebRTC POC or demo development? Follow these best practices to save time and increase the success of your project.
Read More