Last weekend we had the pleasure of sponsoring University Hacker Olympics. Unlike your typical hackathons, this one emphasized connecting University students with industry professionals.
Personally, I thought the event was innovative in the field of recruiting. In the traditional interview process, sometimes great candidates were dismissed because their shyness or nervousness inhibited them from performing. 1-1 interviews can be intimidating, we’ve all been there. From the interviewer’s perspective, asking candidates to solve problems does not provide any valuable insight into how pleasant it would be to work with them in a working environment.
A number of developers have asked for ways to help end users diagnose potential problems that disallow them from being able to successfully video chat using OpenTok. A while ago we introduced a troubleshooter page that test a user’s network, hardware, and software to check things like ports, camera, and Flash version to be sure that they have what they need in order to use OpenTok.
While this tool has been useful for diagnosing problems, one obvious pitfall is that you have to send your users to our website—away from your experience.
Developing an iOS App itself is a huge undertaking: you want your product to be beautiful, interactive, and functional. That’s why Parse makes so much sense, it helps you avoid writing a backend server to power your App by giving you a data store and providing the most basic web services. These days many web services are incredibly powerful and help developers do really amazing things, like OpenTok, but they are targeted at having a backend. That’s where Parse Cloud Code comes in: it gives developers the ability to leverage the best of a back-end server in the path of least resistance.
Yesterday, the talented folks at Double Robotics rocked the stage at LeWeb in Paris. David Cann, Co-founder and CEO, demoed their telepresence robot, Double. The sleek Double combines Segway-style movement with video presence delivered through an iPad.
Leveraging OpenTok’s iOS SDK on WebRTC, Double enables owners to broadcast their video stream on the robot’s iPad from any location. Not only that, but the operator can stream and control its movements from a smartphone.
Cann demoed the Double’s original inspiration, which was to connect remote workers with their home offices. Calling his CTO back in Sunnyvale, Cann took their Double for a three a.m. spin around the office from Paris. Customers are also finding uses for Double for remote tours of factories, museums, schools, and retail outlets.
Here at TokBox, we’ve been supporting AngelHack since its infancy. This year it’s no different, and this time we sponsored at a city bursting with startup energy, Los Angeles.
The event is hosted at a spacious and comfortable co-working space called Cross Campus, a place to inspire “creative collisions through space design, learning platforms, and extraordinary events.” If you are an entrepreneur you might want to check it out!
The event started off with sponsor pitches and API talks. Singly provides SDK for developers to get their app connected quickly and easily with services like Facebook, Twitter, Google, just to name a few. Gimbal provides a mobile context awareness platform that includes image recognition and geofencing. TokBox provides a video chat API (called OpenTok), and for demo I live coded a web and iOS app that video chatted with each other.
WebRTC Demo Day! Unless you have been living under a rock, you have heard of WebRTC. A few weeks ago, Google unleashed Chrome 23 which has WebRTC and PeerConnection support. This is really exciting because everyone on chrome (and IE users with Chrome Frame plugin) can now experience the next generation of communication via live video. Today is the day to experience it. Simply go to https://OpenTokRTC.com and join a room! If you’re lucky, you might catch a few WebRTC Streams from iOS devices.
There’s irony in being a cloud provider when a major piece of your infrastructure lies below sea-level. Of course, the premise behind the cloud is that you never have to think about the underlying physical location of your servers. If a flood were to happen in a critical network hub, say New York City, it should in theory have no impact on a cloud service (because, you know—clouds are in the sky).
As Hurricane Sandy forecasts came in, our ops team began to consider what impact it might have on our service. We had two options: A) keep our NYC servers as they were and hope that power and connectivity would remain intact, or B) take our NYC servers out of rotation and direct that traffic elsewhere.
Nearly 7 months ago, we publicly announced that the OpenTok API would extend its reach to native mobile application developers by publishing the OpenTok iOS SDK. In the time since, we have tightened the performance of the SDK runtime for iOS devices and spent a good deal of time learning about how best to deliver video to the mobile platform. While iOS commands a large portion of the mobile app market, it is intuitive that we should build similar SDKs for other popular platforms outside of the browser. It is a pleasure to announce that we are developing the OpenTok Android SDK, to allow native Android developers to bring live video chat to their apps.
With all the excitement going on with webRTC and iOS interoperability, I’m sure many are excited to get started. If you don’t have time to navigate through the docs, then you’ve come to the right place. In this article, I’m going to show you how to get started! If you didn’t know already, webRTC is a new HTML5 spec for interactive media streaming on the web.
Browser to Browser
A new standard is making its way into web browsers and other clients around the world over the next few months that will likely change the way that we communicate with each other. WebRTC (Real-Time Communication) is a set of protocols and technologies that have been proposed to allow modern web browsers (currently Chrome 23 has support) to embed live audio/video communications without a plugin like flash.
Over the last few months we’ve been hard at work on a new variant to our iOS Video SDK, which we’re dubbing the OpenTok WebRTC for iOS SDK.
In the world of video WebRTC is a really big deal. The quality increase we’ve seen in WebRTC video versus our current Flash SDK is pretty phenomenal. For instance, video latency is typically less than 250ms under most network conditions. This is important to maintain a flowing conversation and avoid talking over other people on the call. Video quality is also noticeably better. The framerate and resolution are higher and adjusted dynamically over time to take advantage of the bandwidth and device capabilities that’s available between the clients.