Today, 66% of all internet traffic is being driven by live-streaming video, and by 2020, that number will grow to 82%, according to research by Cisco. Rapidly-successful User Generated Content apps, like Facebook Live and Periscope, are among the driving forces behind this growth, as live video and interactive online broadcasting is being widely adopted across industries, including webinar platforms.
In addition to powering live video experiences, TokBox is also in the business of making it simple to create content. Whether it’s for a social live stream that is delivered to millions of viewers, or a webinar recorded for post-event distribution, the OpenTok platform makes it possible.
There is no one-size-fits-all video layout that accommodates this wide range of use cases. You wouldn’t use the same UI/UX for a broadcast app as you would a customer service app, right? Developers using our platform need adequate control and flexibility to create UI/UX optimized for their experience.
For this reason, we’re excited to release new REST APIs to customize video layout for content creators using the Archiving API and Broadcast API for HLS & RTMP. Now developers using these two features can create a custom layout using CSS, or select one of the following prebuilt layouts:
A new tool to test connectivity, expected call quality, client hardware, and client software
Whether you’re in the healthcare industry or have a social app, it’s likely you’ve had difficulties gathering diagnostic data from end-users. There are components beyond live video and basic app errors that can trip up an experience – network performance, low quality devices and more. In addition, the huge diversity among users’ system configurations means that there is no one-size fits all cause for errors.
We believe a big part of our job as your live video platform provider is to give you the tools you need to understand (in advance) call performance. That’s why we’re excited to introduce the new and improved Pre-call Test (formerly known as the Connectivity Doctor). Using network condition data, the new Pre-call Test tool will help you preemptively diagnose problems that your end-users may encounter as a result of poor connectivity. It will help you answer important questions like, “will my application work where it needs to?” and “what will the call quality be?”
An exciting FinDEVr 2017 New York event was held on March 21st & 22nd in New York. This conference was focused exclusively on the technology that is enabling innovation in the Fintech industry. Technology startups and bigwigs – such as IBM, Google, Box, Citi, Capital One – showcased their latest tools, technologies, APIs, platforms, and case studies that developers, software architects, and other technologists will use to create the next wave of Fintech innovations.
TokBox has presented at FinDEVr since 2015, previously introducing WebRTC technologies and showing the video-enabled online branch. This year we felt it important to discuss the impact we are seeing of social applications on customer expectations, and show how live video platforms, such as TokBox, are making it easier for financial services organizations to keep up with the rapid social evolution of customer experience requirements.
Last year TokBox introduced the OpenTok Interactive Broadcast API. Ours became the first platform to marry the real-time capability of WebRTC with the reach of HTTP Live Streaming (HLS). The Interactive Broadcast API is helping our customers build large-scale interactive video experiences including live online auctions, Massive Open Online Courses (MOOCs), webinars, social apps and more.
Over the past 6 months we’ve continued to innovate in the broadcast space, pushing the boundaries of performance while ensuring massive scale. Today we’re proud to announce major enhancements to our Interactive Broadcast API.
Mobile applications are rapidly becoming the primary channel through which people get things done. At the same time, user experience expectations for mobile applications far exceed expectations for applications delivered through other channels. Users expect value, ease of use and a delightful experience, but too often their expectations are not met. This is only exasperated in applications with a real-time communication component. Our customers are not immune to this trend; an increasing number of them are building applications with a mobile-first strategy and it is becoming a significant part of the traffic that we see on our platform. In fact, more than 60% of the traffic we see on OpenTok is from customers using our Mobile SDKs.
Back in 2014, we released a WebRTC industry first – an Archiving API built on top of the OpenTok Platform. The ease of use of the Archiving API which enables the recording of any OpenTok session has become one of the key drivers for our customers to choose TokBox. We’ve seen demand from customers across a range of different industries with a range of use cases but the ability to record OpenTok sessions, in a format that is optimized for playback (Composed Archiving) or one that gives customers complete control over post-processing (Individual Archiving), is a common ask across the board.