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.
Over a year ago we released a WebRTC industry first – an Archiving API built on top of the OpenTok platform. Whether it’s for compliance, educational, or quality management purposes, our experience in market has shown us that real-world implementations of WebRTC need recording.
Our main goal with the Archiving API has always been to make it simple to record OpenTok sessions and deliver it in a format that is optimized for easy playback. Once your session is finished recording, we upload a single video file composed with all of the participants’ video streams to the storage provider of your choice – Amazon S3 or Windows Azure.
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.
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.