It is estimated that by 2019 50% of all higher ed classes will be delivered online. So there’s no doubt that education, both in and outside of the classroom, is entering a whole new era.
The first wave of e-Learning impacted education, bringing educational resources online. But the second wave – active e-Learning using technologies like WebRTC – is set to revolutionize it, creating new interactive experiences with communications in context. In the real world, this means that a student in Detroit can now be tutored in calculus by a math teacher in New York or college students at MIT, UCLA, and Oxford collaborate together on an article to be submitted to a renowned academic journal.
GUEST POST: WebRTC.ventures is a custom design & development agency focused on building WebRTC applications. They are part of AgilityFeat, which is one of our development partners at TokBox. Jean Lescure from their team wanted to share their experiences using our new API for detecting call quality.
Back in August TokBox announced their new Pre-Call API, for testing out bandwidth conditions, and posted a repository on github with a proof of concept. At WebRTC.ventures we saw a great opportunity to build upon that project and got working on creating a demo app out of it, including a server implementation in NodeJS which is compatible with Heroku.
At our September TechTok WebRTC consultant and analyst, Tsahi Levent-Levi, came along to discuss the power plays of the video coding industry.
Just when we thought we were done with the video codec wars in WebRTC – we found out we’re only just beginning. Tsahi was here to talk us through some important questions – how is this WebRTC codec war going to play out? Where do the alliances lie? And where are we headed?
Watch the full video here:
UPDATE 9/16/15: After we published this post Google announced that they are pushing back the release date of the HTTPS security change. They’re estimating that it will now be released to production in December 2015.
Google recently announced a security policy change that will impact future versions of the Chrome browser. Any website which has integrated geolocation technology, screen-sharing, WebRTC and more, will now be required to be served from a secure (HTTPS) site.
We at TokBox are supportive of this update as we believe operating your WebRTC-based applications through HTTPS is a best practice and offers enhanced security. In addition, it has the added bonus of improving your end-user experience by remembering their hardware settings, and even allowing screen-sharing (if you choose to implement it).
At this month’s TechTok, the team from Revolve Robotics came along to talk about all things robots: how robotics have changed and continue to do so, the evolution and potential of telepresence robots, as well as how you can leverage the OpenTok platform and Kubi robotics capabilities to build powerful and engaging telepresence robots.
Revolve Robotics CTO, Ilya Polykov, and CEO, Marcus Rosenthal spoke about their integration of OpenTok and Kubi. If this is something you are working on or are interested in, check out their API. If you’re developing an app based on the OpenTok platform and want to use Kubi, this API will help you make this happen in a matter of days.
If you’re interested in buying your own Kubi robot, you can get $100 off your online purchase using the promo code ‘tokbox’ at checkout for a limited time only.