Today we’re thrilled to announce the launch of our powerful new session diagnostic tool, Inspector. It provides you with a high-level OpenTok session summary at a stream and user level to help pinpoint errors, failures, and quality issues. Our main goal? To simplify your post-session debugging.
Inspector takes the rich and complex operational data that the TokBox engineering team uses to debug OpenTok sessions, and makes it available to you in an easy to use interface. These vital metrics will enable you to drill down into session-level details around:
- Bit-rate, latency and packet loss graphs at user and stream level
- Event Logs (Detailed list and description of all session events)
- User Logs (Information such as location, SDK, browser and client)
- Error Logs (Details of all errors encountered, time of error and impacted end-users)
Now your technical support team can quickly glance through session data to determine whether an issue was caused by an end-user error, application error, network problem or the OpenTok platform.
From being used to assist in medical research labs to driving cars, you can see new possible uses of robots popping up in many different aspects of our lives. At TokBox we are particularly excited about telepresence robots and the ability to tap yourself into a different geographic location using real time communications. Combining powerful robotics with communications technology means that you can, effectively, be in two places at once.
It is now a possibility to add robotic motion to video applications – but why would you want to? Imagine a telepresence robot that lets you look around during video calls. Whether you are attending a meeting remotely, talking to your professors and peers in a classroom from afar, asking your doctor questions from home, or greeting people as a virtual receptionist, you can combine real time communications and robotic movement to be able to move and look around, and to interact with other people, almost as though you are there in person. These combined possibilities help to create a more true to life experience and is far more engaging on both ends of the call.
Last week TokBox hosted the monthly SF WebRTC meet up at our offices in San Francisco.
It was a great evening, with a range of speakers and topics from the WebRTC world. This month we heard from:
- Ankur Oberoi from Tokbox
- Hadar Weiss from Peer5
- Feross Aboukhadijeh from WebTorrent, PeerCDN
- Dr Alex from Temasys
You can watch a full recording of the event below and if you are interested in hearing more about meet up events at TokBox, you can join our meet up group here.
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.
For any business, in any industry, security is always an essential consideration. TokBox recognizes this and makes the security of customer data a top priority in the OpenTok platform.
In addition to selecting a secure platform provider, it’s equally as important to architect your application in a secure way.
That’s why we created the “Best Practices: Building a Secure App with OpenTok” guide. This resource is designed to help you ask the right questions while developing your application, and provides best practice recommendations so that you can make informed decisions.
WebRTC is maturing and we can see the needs in the market evolving along with this.
However, with the increased need for rich, digital experiences comes the challenge of building more advanced applications. We know that building real-time video communications can be challenging, especially when it involves more than two participants. To pull off a multi-party call using WebRTC off-the-shelf you’ll need a strong backend infrastructure and a deep understanding of media processing. That’s why we are looking forward to exploring this topic with WebRTC expert, Tsahi Levent-Levi, founder of bloggeek.me, in our upcoming webinar.
We’ve all seen the statistics and now know that mobile usage is at an all time high and is still on the rise. Increasing with this is mobile video consumption. As mobile data has become more affordable and reliable, and with more WiFi hotspots popping up, it is becoming increasingly easy to watch, share and communicate via video on mobile devices.
This is something that our partners at Simpleweb, a web and mobile development agency in the UK, have noticed too. They know that a new wave of apps is revolutionizing the way we view and broadcast video online, many of which are powered by WebRTC.
Mozilla has released further enhancements to Firefox Hello, powered by OpenTok, including the ability to screen share within a video chat. This new feature allows participants to open and share a browser tab or application window from within the chat, making browsing, shopping, drafting or any other activity more collaborative and engaging.
When an issue is reported with an application, an early debugging step is to reproduce the problem. Because our platform is an API, and developers use it for many different kinds of applications, TokBox employees used to have to reproduce problems by building a new application for each new use case. After doing that a couple of times, we wizened up and started using pre-built sample applications as the starting point. This still meant that any functionality that wasn’t generic needed to be added in. What we really needed was an application that used a myriad of features we offered: Enter the TokBox Live Debugger.
At this month’s TechTok, Philipp ‘Fippo’ Hancke, &yet’s WebRTC lead and industry veteran, explains everything you need to know about how to handle failures with WebRTC.
‘If you’re going to launch a WebRTC powered service for financial gain, then you need to have done everything within your power to ensure it works reliably across as many cases as possible.’ Chris Koehnke.
Philipp knows just how to do this so we will leave it to him to tell you. If you want to learn more about how to fail gracefully with WebRTC you can watch a video of Philipp’s full presentation here: