WARNING: if you’re an application developer that likes to solve the complex intricacies of a problem, someone that enjoys getting lost on feature tangents or being 'in the weeds' at all times, then this blog is NOT for you. This blog is about solving complex problems with speed and agility.
Still here? Great….allow me to elaborate.
I attended a partner event, RestConn 2017, by Telestax where I was asked to present the new Video API we’ve been collaborating on for the better part of 9 months and give the audience a first look at the integration in action. But who cares about video and why was my session (and perhaps my obsession) centered on video?
Let me answer this in two parts:
First, video is becoming ubiquitous – look around, video was once one of those rarely used features but there has been a recent paradigm shift to where now video is all around us. I say this not only for the ‘talking heads’ (video conferencing) use cases but others such as video broadcasting, video public safety, video surveillance, video customer care, the list goes on and on. Video has become an important method for communication among users in the enterprise with 30% choosing to use video once per week (Ovum). The issue here is unfortunately video isn’t one size, fits all; one video solution cannot solve all use cases. Instead, video need to be modified to fit seamlessly into the workflow to create a true omni-channel experience.
This brings me to my point when attempting to implement video, and simply put, video is hard. I say this from dual-perspectives – first from a media server perspective where delivering high quality video, handling and reacting to video QoS feedback, transcoding codecs, transrate frame rates, transsize resolutions, etc., is extremely hard and time consuming (we have a team at Dialogic dedicated to the advancement of video). Second perspective is from an application developer that is looking to implement video into their solution, which can be equally as hard. Case and point is a simple WebRTC peer-to-peer video session with 209 lines of code – this does not include advanced features such as recording, multiparty video, video playback etc. There needed to be another way....
The goal set while designing the Video API enhancement was to remove the complexities of video both from a media server and application developer perspective, to enable a rapid service creation tooling platform for developers to focus on innovation and rapid prototyping. Having a communications platform where application developers can utilize building blocks including voice, SMS, and now video to build into their workflows and create a customized, seamless, feature-rich experience for their users. Speed and agility.
For more information, join our Video API webinar on June 13th @ 2pm Eastern and DM message me if you want to try out the new RestComm Powered By Dialogic XMS Video API – we’re always looking for input and new use cases to shape the API.