Google shuts down plenty of products. Reader, Glass, Talk, Wave. But the closing down of Helpouts gives particularly valuable lessons for those who are building WebRTC based applications and services for the always on ‘find an expert market’, of which there are many.
While it’s clear that it didn’t get enough traction and had some monetization issues, the real question is why? In healthcare in particular there is a large and growing world of people for whom video communications, powered by WebRTC, is a critical lifeline (literally). This is a world that includes housebound cancer-patients, the blind, recovering drug addicts, time-constrained parents and their community of carers, and healthcare practitioners. A recent report cited 89% of healthcare executives that said they expect telemedicine to transform the U.S. healthcare system in the next decade, with the number of patients using telehealth services growing to 7 million in 2018, up from 350,000 in 2013.
We all have a fascination with the billion dollar startups. Venture Capitalists try and identify them early, media laud them (or bring them down to earth), and early adopters claim discovery. One new technology innovation has the potential to spark the creation of more billion dollar companies, and markets are starting to pay attention. So what is WebRTC, and why is there so much interest?
It begins with recognizing the emergence of two massive trends. The first is the increasing appetite for ‘on demand’. This is evident in everything from movies to car rides, hotels, relationships to groceries to well, everything. And communications is a core part of this, just look at Meerkat and Twitter’s latest acquisition, Periscope, bringing
A few days ago we released version 2.4.1 of our Android and iOS SDKs. This update to our SDKs were prompted by Mozilla’s implementation of a security enhancement which we fully support. However, this enhancement has the unfortunate side effect of making older versions of our mobile SDKs incompatible with Firefox 38 (scheduled to hit production on/around May 12, 2015). Not to worry though, the 2.4.1 SDK fixes this compatibility issue.
What did Mozilla change?
In an effort to bolster security Mozilla updated the encryption scheme for DTLS negotiation of the WebRTC handshake.