Demystifying WebRTC or Rediscovering the Need for Audiovisual Communication in the Browser

Originally published at leblogdecarlos.com on January 27, 2016.

This is the eighth of a series of articles I published between 2015 and 2017 on www.LeBlogDeCarlos.com. Unfortunately that publication is no longer online. My web host provider from back them erased it because I missed a monthly payment when my credit card expired. Luckily I was able to back up for some of it locally. Specially writings for 2015. During 2016, as a blog writer, I would go from first to final draft directly in the blogging platform I used back then. Even though most of these articles are unfortunately lost, I have nonetheless decided to bring back what was left of these contents. This time on Medium.

Why is this Important?

Because providing visually supported customer experiences will change and enhance digital business for ever and for good. It becomes important to understand how technology can help. And what’s available at this point. I found myself presenting such things to my former peers at Odigo Capgemini before closing 2015. This article is somewhat a summary of that event.

Assessing WebRTC for your business in 2016 meant understating scenarios of user connectivity: from the end-user/customer terminal to the internal/business-user/advisor/agent experience.

In 2016 WebRTC provides a Media Layer of Communication. Companies in the RT Professional Video Communication space build on top of it to further enhance the protocol’s capabilities. For example: developing on top a Signalling Layer of communication to enrich the number of use cases to deliver to professionals and businesses (ie: presence management, conferencing, annotations in “AR 1.0”).

Why WebRTC alone does not provide a universal business solution in 2016?

The Challenge

is essentially offering a universal an homogenous experience to all users in their respective conditions of connectivity, across devices and web browsers. Right? The problem is WebRTC is inconsistent here.

In 2016 WebRTC does not work on Internet Explorer, presents different experiences on Firefox, works on Chrome except in iPhones, does not work on Safari and somewhat works on Edge. Experience on Mobile platforms (iOS, Android, Windows) is inconsistent.

The Solution in a Nutshell

includes developing capabilities on top of WebRTC. Plugins for Web Browsers. Mobile Apps (custom or white label), Mobile SDKs.

This 2016 solution was build on top of Sightcall Technology. Links no longer work. For reference: Odigo.

Doing the exercise of reviving this very article makes me want to naturally undertake the writings of a new WebRTC / Video Customer Experience follow up. Today, in 2020. As soon as I have brought back online the remaining 5 articles, I will hop on a journey for an update on WebRTC 2020! Stay tuned.

More stories on Trailblazing IT — the eBook

Please reach out if you have any questions.

Thank you!

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
lecharles

Product Management + Solution Engineer @Salesforce. Jugaad Innovation Aficionado. Web Application Development. Cryptocurrencies & Open Blockchains Apasionado.