Part 2 – Creating the best possible user experience for social video apps
In Part 1, we looked at some of the key considerations for building a group live video app for mobile along the lines of Houseparty and Facebook Bonfire, and how the OpenTok platform can provide the solutions to some of the hurdles caused by using WebRTC off-the-shelf. In Part 2, we’ll look at some specific features and code which can be used to create an awesome user experience so your users will fall in love with the app.
Who are the world’s biggest social video chatterboxes? What’s the record for the most people in a group video chat? And which region is staying up late into the night to use their video chat apps?
We’ve answered these questions and more through our Global Social Video Study. Social video chat apps have seen explosive growth in the last few years (see Facebook Bonfire, Houseparty, Live.ly), and WebRTC provides a unique platform for them to include live video communication in their offering.
We continue to be excited by the customer use cases that WebRTC on Safari will enable, especially the “spontaneous” customer interaction situations we see in Retail and eCommerce, Customer Service and regulated industries – as we discussed in our previous blog. On June 22nd we held a WebRTC on Safari Developer Workshop in San Francisco to make more information available to local developers about the details of the Apple announcement and how to get started experiencing and developing WebRTC apps for Safari 11.
We are pleased to now provide this information online for everybody!
NEWS: In the San Francisco Bay area? Come to our Developer Workshop on WebRTC in Safari on June 22 @6pm.
I’ve been waiting a long time to be able to publish this blog post. It was easy to miss, but if you were paying close attention to today’s WWDC keynote you would have seen Apple indicating WebRTC support for iOS 11, which will be available later in the year.
From the early days of WebRTC in 2011 until yesterday, the single biggest outstanding question about this standard had been when will it be supported in all major browsers? Supporters could see that WebRTC was loaded with the potential to change how we use communications, but there was always that lingering sense that WebRTC wouldn’t cross over to the mainstream and be used for mission critical applications until it was supported by all browsers. With today’s iOS 11 announcement, Apple has answered this question. WebRTC is here to stay. This is a major turning point for embedded communications.
TokBox is pleased to be sponsoring the upcoming Kranky Geek WebRTC Tour across Bangalore, Hyderabad and Chennai in India during March 2017 (see below for dates). This fast-paced event brings respected WebRTC and real-time communications experts to town to help technologists and developers quickly get up-to-speed on the opportunities to enhance apps with global live video experiences using WebRTC.
At TokBox we’re always trying to find ways to improve your development experience. We pride ourselves on offering clear documentation, helpful tutorials and tools to accelerate the integration of OpenTok. We don’t plan on stopping there.
Now, with the Video Chat Embed, you can take your proof of concept from zero to sixty with a simple copy and paste.
Why is this so powerful? As the market and demand for live video communications grows, two trends are emerging. First, developers with varied coding skill levels want to build with WebRTC. Second, developers want to be able to show off a proof of concept quickly. Enter the Video Chat Embed.
To get started simply login to your TokBox account, click “Video Chat Embeds” in the left navigation and “Create New Embed”.
Make a few configuration choices for your Video Chat Embed – specify what size you would like the frame to be and what website your project will be embedded into. We’ll then generate code for you that can be added to your website in a matter of minutes.
Imagine greeting your colleague on a Monday morning by the water cooler. You chat about the weekend before both moving into a team meeting to discuss the week ahead. Sounds like a regular day at work, only your colleague didn’t ride the train, take the elevator or walk the stairs into the office today, in fact they are 5000 miles away – they arrived to work via a telepresence robot.
In our last blog post, (a peek at the future of healthcare) we considered the key drivers behind innovation in the health care industry. Telehealth has seen explosive market growth in recent years and shows no sign of slowing down. Despite its enormous potential for growth, the healthcare industry faces regulatory challenges that impede innovation.
Since the 1996 introduction of HIPAA, (Health Insurance Portability and Accountability Act), the healthcare industry has become highly regulated. The scope and complexity of healthcare regulation has made it incredibly difficult for organizations to adopt new technologies. Compared to other industries, they have been relatively slow to adopt technological innovations as a result. This trend has manifested itself in the adoption of the public cloud, BYOD (Bring Your Own Device), and even the storage of online health records. With this in mind, one can assume this trend will repeat itself when it comes to browser based real time communications powered by WebRTC.
When you think about the hottest startup or innovation sectors, one may naturally think of artificial intelligence, Cloud computing or robotics. And you wouldn’t be wrong. But one you might be surprised to hear is right up the top of that list is Health, and specifically on demand health.
In a revealing study by Accenture, covered in this Forbes article, the growth of the on-demand health sector is second only to ride-sharing when it comes to attracting investment. Investment in on-demand health services is projected to reach $1 billion in 2017, up from only $200 million in 2014. According to Accenture, “healthcare is the fastest growing on-demand sector , representing one-sixth of total U.S. funding from 2010 to 2014.”
Despite the fact that filters are used a lot in non-WebRTC video applications like Photo Booth and SnapChat, we haven’t seen many WebRTC applications using these types of filters. This is probably because it hasn’t really been possible… until now.
It has always been possible to apply filters to video streams locally using the OpenTok platform by rendering the video into a Canvas element. The problem with this approach has always been that the person on the other end does not see the filter unless you apply the same filter on both the publisher and subscriber video. This would mean significant CPU load if you are subscribing to multiple participants. It also means that you don’t get to see the filters in the Archives.