When evaluating a new product or service, we know how important it is to be able to test out the technology first. Stakeholders in different areas of the business, both developers and non developers, need to see and understand how the technology works.
We’ve noticed that for customers evaluating the OpenTok platform, without using the API, it can be challenging to visualise your use case. Even when a developer works through our Quick Start Guide, there can be a need for additional implementation to build a custom proof of concept. All of this translates into time invested during the business’ evaluation phase of the product; worse yet, it can lead to an incomplete or inaccurate evaluation.
We’re excited to announce the release of the 2.8 OpenTok iOS and Android SDK. We’ve made significant improvements to audio/video quality, worked on bug fixes, as well as quality improvements introduced in the Google WebRTC M49 release. In order to improve the quality of these SDKs further, we’ve also rolled out some important patches, the details of which are below, including support for IPv6 for iOS.
Why traditional broadcasters need to adapt, fast
Cable companies and television networks can’t take a trick at the moment. As if digital disruption and cord cutting wasn’t making life tough enough, now comes the rise of participatory broadcasting, the phenomena where viewers collaboratively interact while consuming content, and maybe even participate.
Still coming to grips with on demand and online/mobile viewing, traditional broadcasters must now find a way to provide immersive and engaging viewer experiences to compete with the likes of Facebook Live, Meerkat and Periscope.
“Organizations that embrace rich, real time communication technologies, like WebRTC, reap indisputable benefits” (Business Success Through Embedded Communication Technology, a March 2016 study conducted by Forrester Consulting and commissioned by TokBox).
A new report from Forrester, commissioned by TokBox, has found that WebRTC is delivering significant value across core business functions for organizations across a range of industries. This should come as no surprise given the challenge that many organizations face to bridge the ever growing gap between colleagues, businesses, and their customers as more of what they do moves online.
The popular technology media would have us believe Flash is the worst technology flub since Windows Vista/Apple Maps. It is nothing but a giant security flaw and should never have existed. But pause for a moment and consider this – if it weren’t for Flash there would most likely be no Netflix, no Meerkat or Periscope, no YouTube, no Facebook Live.
You see, while these services may not have all been built on Flash originally, they all stand on the shoulders of the pioneering work Flash did around online video. So, while we’re all quick to celebrate its downfall and lament its many obvious flaws, let’s pause for a moment and remember that if not for the pioneers who inevitably make mistakes (Adobe with Flash perhaps more than most), there would be no progress.
Web Application Developers are used to being able to write automated tests for their applications and have them run with every PR and before deploying to production to give a level of confidence that things are not broken. OpenTok and real-time applications in general present new challenges when it comes to writing and running automated tests. There are challenges when it comes to getting access to microphones and cameras, testing multiple participants and installing the plugin for Internet Explorer among others.
There has been lots of work around WebRTC testing automation and our friends at rtc.io and &yet have written some great articles on the subject. However these articles don’t cover some of the specifics of testing OpenTok applications for example testing Internet Explorer and installing the OpenTok plugin for Internet Explorer. If you haven’t already I would recommend taking some time to read the articles by the folks at rtc.io and &yet before coming back to this. Also if you’re not familiar with Travis and Selenium WebDriver you might want to check those out too.
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
Lately, we have been thinking and talking about broadcast in multimedia. By now, you might have seen that TokBox is powering applications that go beyond the contemporary one-to-one and small group settings that are typically associated with the current generation of WebRTC apps, to a much larger scale of hundreds or even thousands of people watching and participating in the conversation. At a glance, this might not sound particularly groundbreaking; video has been distributed to large audiences for years. However, a closer look is necessary: with a shift in the underlying technology, TokBox adds the option of real-time communication to the existing large-audience reach of broadcast video, to enable a whole new class of applications.
Since we launched the new version of our platform back in 2012, one of our goals has always been to make it very easy to manage and understand how your applications are performing. In addition to simplifying how to build applications, we believe that those are the key elements for a great experience.
Over the last year we have been working on a completely new way to interact with your TokBox account. As our user-base grew and diversified, it was obvious that our previous dashboard was not enough and needed to be extended. With the number of new tools and services that are in the works, we realized that it was a good opportunity to future proof our stack and give you, our users, a much better experience.
As behavior changes and as technology continues to transform the financial services industry, it is no surprise that bank branches are closing. Analysts suggest that the number of bank branches open in the US could be cut by within the next decade. This is to be expected as more and more of what we do as customers is online. According to research conducted by Accenture customers engage with their banks an average of 17 times a month, but only two of those interactions involve human contact.