The capabilities of WebRTC in the Google Chrome browser continue to grow, and some pretty major bugs are squashed. The biggest news for us at TokBox is that Chrome for Android now supports WebRTC out of the box without needing to enable a flag. This expands the footprint of endpoints with WebRTC capability to include Android devices which is a great step forward.
Now, on to the details
When building OpenTok apps, there might be cases where you would like the videos inside a container to automagically resize to take up the largest resolution possible within the boundaries of their container. With layout container, an open sourced library available on github, you can do exactly that.
Want to see a live app that uses this layout container? Check out OpenTokRTC! Try typing “/focus” and “/unfocus” in the chat box to see additional functionalities of layout container.
Hello TokBox Community,
We have a small favor to ask of you. We’ve pulled together a brief survey about WebRTC that aims to measure the current level of awareness, interest, and activity around the standard and we need your input:
The results will be made public and will reveal:
- The depth of WebRTC knowledge in the tech community
- Which features/functionality are considered most important to you
- How the tech community would like to see the standard develop over time
Added bonus? We’re raffling off five $100 Amazon gift cards to people that have completed the survey (you’re only eligible to win one). So take a few minutes, ponder what WebRTC means to you, and answer our survey. Thanks!
If you have read through our getting started tutorial and know how to create sessions and tokens, you are good to go!
To get you started, we have a few simple and working video chat sample apps to get you started:
For more complicated features and functionalities, check out these demo apps:
If you have read our Getting Started With OpenTok: From 0 to group video chat, you will see why we need to create sessions and their corresponding tokens.
Since creating sessions and generating its corresponding tokens involves your developer api key and secret, they should always be executed in your server to prevent your credentials from being exposed.
In short, sessions are like rooms. People connected to the same session Id will be able to publish and subscribe to each other’s video stream. Session Ids exist forever, so it’s safe to store them in the database.
TokBox is the company that provides the video streaming API called OpenTok. This tutorial will be a walk through to creating a very simple group video chat application.
There are two flavors to the OpenTok API, OpenTok Flash that uses flash plugin and OpenTok WebRTC that uses the new and cool HTML 5 technology, and they are not interoperable.
WebRTC provides a much better video chat experience when it comes to quality but is currently only supported officially in Firefox and Chrome. Internet Explorer users must install Chrome Frame plugin.
Flash on the other hand, is supported in 99% of all browsers and allows the ability to record live video streams as they occur (archiving).
Back for its 3rd year, Hollywood Hack Day is a two-day event that brings developers from all over Los Angeles and Orange County together to create the next generation of entertainment applications and we are very excited to be sponsoring this event again. If you live around the area, get your thinking hats on and register for your weekend of programming fun!
If you have any questions with our API, feel free to reach out to us @tokbox or to me directly @songz or ask on stack overflow!
Heres a list of other sponsoring APIs and how they can can help you with your hack:
This tutorial will show you how to create a simple, yet functional video chatroom using the OpenTok API and Sinatra. Sinatra is a Ruby framework which allows you to quickly create web apps.
The app we’ll be creating will be a simple website which will allow you to instantly create a video chatroom.
So, let’s get started! First of all, you’ll need to install Sinatra. To do this, type the following command in the terminal:
gem install sinatra
Then, create a new folder and inside, make a new file called app.rb.
Today we’re excited to announce OpenTok for Customer Service (OTCS). This is our first solution built on top of the OpenTok platform, and will make it faster and easier for our partners to implement face-to-face video chat for customer service applications.
Over the past few years, we’ve had the opportunity to keep a close watch on use case trends in the video space. One common thread was present amongst the majority of the use cases that we encountered: customer service. Whether it was pre-sales support, post-sales customer assistance or expert consultations they all required some basic call functionality that wasn’t available through the standard OpenTok APIs.
Today, the OpenTok platform adds the Cloud Raptor SDK into the fold. Partners’ application servers can use the Cloud Raptor SDK to listen to the events and messages that pass through an OpenTok session. Accessing these events and messages on the application server makes it easier to integrate OpenTok logic with the application logic. (Prior to Cloud Raptor, OpenTok events and messages were only available on the client.)
Before today, building robust applications with the OpenTok platform meant writing a distributed application across many clients. The clients either synchronized between themselves, the partner sent back a lot of AJAX calls to their server, or the developer used a service like Parse. Now, with the Cloud Raptor SDK, OpenTok developers can have one OpenTok brain for their application – simplifying the development and extending the possibilities simultaneously.