In April, we announced updates to our pricing and packaging, which allows TokBox customers to have more flexibility with the ability to add-on features a la carte to their accounts. With this in mind, we’ve been hard at work over the past couple of months to make our entire user experience more flexible and allow users to have more control in configuring their OpenTok projects.
Today, we’re excited to announce that we’ve made several improvements to the Account Dashboard, which provides users with more self-service functionality. These updates will make it faster for users to configure their OpenTok projects and make quick changes, and to gather critical information on the add-ons they have access to.
Welcome to the first edition of Real-Talk. Each month, we shine the spotlight on the hottest news, views, insights and developments in the world of live video, WebRTC and real-time communications.
In this month’s wrap, Instagram doubles down on video calling; telehealth continues to heat up with a massive cap raise by American Well; shoppable videos arrive on the scene, highlighting the endless possibilities for video; and Juniper Research reveals the enormous potential for Communications Platform as a Service (CPaaS) for enterprise.
When we undertook our Global Social Video Study last year we were surprised to find that we had users on the OpenTok platform from over 150 countries. There was even an instance of a live video chat involving users from 13 countries at the same time! The OpenTok platform provides global reach but there are times when compliance dictates that media traffic be restricted or geo-fenced to a specific region or country. To support the finer level of control required we are delighted to introduce our latest advanced security feature – Regional Media Zones.
At TokBox, we’re always inspired by the innovative and powerful companies who work with us. We wanted to make sure our pricing plans provided a way for our diverse set of customers to access features they needed for more flexibility, simplicity and value, and help them achieve success with live video.
Today, we’re excited to announce updates to our pricing plans and packaging capabilities with three TokBox plans – Standard, Growth and Enterprise.
We’re also introducing the ability for users to add-on features to their plans a la carte. We recognize the importance in giving users flexibility, as we know that a “one size fits all” approach doesn’t support all of our customers and their various needs, and this allows TokBox users to create custom packages.
At TokBox, security is of the utmost importance to us. We’re committed to providing a safe platform which meets all of the security requirements and regulations and therefore ensures reliability for our customers and privacy for their end users.
When the new regulation from the European Union called General Data Protection Regulation, or GDPR, is officially enforced on May 25th, 2018, we will be ready. In fact, we’ve already been hard at work ensuring we’re compliant and meet all new regulations set forth by the GDPR. This is part of an ongoing effort to keep our platform secure and maintain our transparency about how we use data.
Communications within businesses, and between businesses, are fundamentally changing. Like all new implementations, communication apps require companies to consider many factors: technology platforms and configurations, human factors around adoption and usage, as well as the potential impacts – both intended and unintended.
One of the fun things about running a communications platform company is watching new use cases emerge as companies and developers innovate using our technologies.
Several months ago, we began to notice a new trending mode of use of WebRTC in the area of Field Service enablement. I’ve also heard people describe it as remote workforce applications, or even fleet management systems.
The key concept is that a field worker – someone who goes onsite to a customer location to effect a repair, make an inspection, or deliver or pick up products, uses some sort of a computer or electronic device as an essential tool for that onsite visit. Increasingly these devices are smartphones or tablets.
It’s predicted that by 2018, 70% of mobile workers will use a tablet or a hybrid device that has tablet-like characteristics. (Source: RapidValue Solutions)
When people think about banks, the thoughts that spring to mind are images of serious people in conservative suits, large buildings with marble-floored lobbies and rows of teller windows, and well-fed men who look like the guy on a Monopoly box. Indeed, leading banks have always worked hard to maintain stellar reputations for reliability, safety, and longevity. You don’t tend to think about banks being big risk-takers, or experts at trying out new business practices or cutting edge technologies.
But when you look a little closer, the truth is, leading banks are expert at understanding and taking calculated risks, which is essential to their core business of taking deposits from some customers and prudently loaning out those funds to others. They are also remarkably forward-looking in trying out new technologies and business innovations, even if they don’t always portray themselves this way.
When creating new services and products, organizations always face a challenge whether to buy or build key underlying components and functionality. As WebRTC attracts an increasing degree of interest, we regularly hear from customers that they are considering the trade-off around the decision to buy or build. Many go so far as to try and build their own real time video or audio solution before they turn to a hosted platform like OpenTok. Not surprisingly given the business we are in, we come down pretty strongly on the side of leveraging a hosted service.
WebRTC is changing the way enterprises communicate within their organization and with their customers.
As a result of the large and diverse range of different use cases of WebRTC in the Enterprise world, there are inevitably a number of challenges that need to be addressed. We’ve compiled a list of some of the key challenges and solutions for consideration with regards to implementing WebRTC for Enterprise solutions: Signaling, Multi-party, Interoperability, Quality and Scalability.
SIP? XMPP? JSON? Rumor? The right answer to the signaling question probably depends a lot on your starting point and on what you’re trying to accomplish.
While many people think signaling should be standardized; others think we already have the answer in SIP or REST. Some maintain that the lack of a signaling specification (beyond the need to support SDP offer/answer) is a huge gap in the WebRTC standard.