The OpenTok.js SDK integrates beautifully into current HTML elements, providing a great variety of layouts and styles. But why should we stick to the traditional 2D design? Modern browsers offer us the power of 3D visualization with WebGL, a technology that has already opened up a new world of interaction and presentation of data within the browser domain.
With an objective to take advantage of the possibilities of 3D within the browser, we created the OpenTok 3D demo. The OpenTok 3D demo is a multi-party video application which shows how we can integrate the OpenTok.js API with WebGL technology using the three.js library. One of the objectives of this demo application is to inspire people building on top of the OpenTok.js SDK, showing them the beginning of endless possibilities on how we can present the video screens in a true 3D world. Cameras, lights, textures, rendering effects, and more, can be leveraged to enrich the final experience.
At this month’s TechTok on May 21, Philipp ‘Fippo’ Hancke, &yet’s WebRTC lead and industry veteran will tell us everything we need to know about how to handle failures with WebRTC.
TokBox is excited to be sponsoring Video Hack Day in New York this Saturday (May 9), an event dedicated to all things video. At a time when more and more exciting video apps and services are popping up, we are looking forward to going along to see what the community can come up with next.
We’ll be sending Ankur along to the event who will offer up a couple of OpenTok hack ideas as well as answers and advice on the day. If you’re up for a challenge, why not think about WebRTC powered augmented or virtual reality apps? Or adding a live video chat to a media site? We’ll be awarding a GoPro for the best OpenTok hack so give it a go!
We’re big fans of Angular JS at TokBox and we have been using it internally to build applications for quite some time. It’s a fantastic framework for building Single Page Web Applications – since all OpenTok Applications are Single Page Web Apps they work really nicely together. This post is going to be based largely on our experience writing meet.tokbox.com, our own video meeting tool we use internally. The code for meet.tokbox.com can be found at https://github.com/aullman/opentok-meet
TokBox is happy to announce our first meetup of 2015. This month we will be hearing from Josh Carpenter, Virtual Reality Researcher at Mozilla, who will be talking about bringing the open web to Virtual Reality.
The Mozilla VR team believes that the attributes that define the web—interoperability, accessibility, low friction publishing, freedom of navigation, etc—are sorely needed in the emerging modern VR platform, and that the creative potential of the combination of web + VR is unprecedented. In this talk, Josh will focus on a how we might build a new generation of real time collaboration experiences, powered by technologies like WebRTC and WebVR.
At TokBox we are focused on making life easier for developers and accelerating their development time. We understand that our partners build very complex solutions, and they need our communication expertise and toolkits. Today we are excited to introduce Starter Kits for the OpenTok platform. These include sample code and design and development best practices for implementing the OpenTok platform’s server and client components. Now you can give your development a jump start, but still have the flexibility you need to to customize your implementation however you want.
We always want to share as much as possible with our community so today we’re sharing a description of how we developed the opentok-editor collaborative editor using ot.js and CodeMirror. You can see the editor in action at meet.tokbox.com and you can see how to use it for yourself at the opentok-editor github page. We love to see people using our open source projects so please feel free to file issues and contribute pull-requests to this project on Github.
Signaling between client end points has always been an important facet for most interactive web applications. The use cases range from text chatting to multiplayer games to driving a robot remotely. In the world of HTML5, most developers establish signaling through websockets, long polling and server side events. However with the advent of WebRTC, data channels joined the ranks and the question posed by many developers is “Where do data channels fit in the equation?”
Data Channels provide a way to send binary / text data to another peer over the browser. The data channel api is very similar to web sockets when it comes to sending different types of data. It works peer to peer without the need of a centralized server or an additional hop in most cases.
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.