As you may know, we recently announced an OpenTok Labs solution for adding live video and messaging to your React Native application. In this post, we’d like to take a deeper look at how to use the OpenTok Signaling API to build a text chat application with React Native.
This past week, my colleague Aaron and I had the opportunity to attend the Reactathon Advanced Conference. The conference featured some great talks, many of which included React Native, GraphQL, and WebAssembly. In addition to the conference, Reactathon also hosted a hackathon, which TokBox supported by sponsoring. It was great seeing the community that loves this great framework come together and share their knowledge.
Over the past few weeks, I’ve been working on OpenTok React Native. As the name suggests, it’s a React Native library for OpenTok. As I work with developers at hackathons and other events, I’ve had lots of questions about React Native and OpenTok. So on April 11th I’ll be hosting a webinar where I’ll build iOS and Android applications with live video using OpenTok and React Native.
At TokBox, security is of the utmost importance to us. We’re committed to providing a safe platform which meets all of the security requirements and regulations and therefore ensures reliability for our customers and privacy for their end users.
When the new regulation from the European Union called General Data Protection Regulation, or GDPR, is officially enforced on May 25th, 2018, we will be ready. In fact, we’ve already been hard at work ensuring we’re compliant and meet all new regulations set forth by the GDPR. This is part of an ongoing effort to keep our platform secure and maintain our transparency about how we use data.
Co-authored by Manik Sachdeva, TokBox Developer Evangelist.
When we talk about health, it’s often physical health which is at the forefront of our plans. However, mental health is equally important, but often takes a back seat. It’s perhaps not surprising: mental health is not well understood by the general public. Unfortunately it can come with a big dose of stigma attached as a result.
To top it off, it can be difficult to find a professional to help overcome challenges. Even when you do have access to a qualified clinician, the cost can be prohibitive.
We recently released the latest version of our Client SDKs, v2.13.0 and I wanted to share some of the great new features that have gone out with this release.
Custom Media Streaming
With v2.13.0 of opentok.js we have added the ability to pass a custom audioSource and videoSource when you create a Publisher. The custom audio and video source are MediaStreamTrack objects. This enables quite a few different use cases that our customers have been asking for.
We get a lot of requests from our customers for examples of how to use OpenTok in their framework of choice. I’m here to tell you today that we are answering your pleas in 3 of the most popular Web frameworks out there: React, Angular 5 and Vue.js.
You can find the new sample apps in our Web Samples Github Repository.
One of my favorite parts of being a developer evangelist is getting to meet fellow developers and share their journey to building awesome products. And there’s nowhere better to meet developers than a hackathon!
Recently, I had the opportunity to attend CruzHacks at my alma mater, the University of California Santa Cruz. It was great to be in a position where I could support an amazing event through sponsorship, mentoring, and judging.
When anyone builds a multiparty video chat application they pretty quickly run into the issue of how to lay out the many different participants. You want everyone to be visible to everyone else and you also want video to take up as much space as possible, without wasted white-space. In the web you have the additional complexity of lots of different display sizes. Participants can be on a mobile device or tablet, or even just resizing their browser window so that they can see something else beside the video chat. For this reason you want a layout algorithm that is responsive.
Our good friend Philipp Hancke wrote a great post recently on a WebRTC audio bug that has been plaguing Chrome on MacOS for the last few years. The issue presented itself as the microphone not working sometimes in Chrome on MacOS until you completely restart the machine. This seemed to happen after a Mac went to sleep and then woke up again.
The good news is that this is fixed with Chrome 63! Philipp put together a great chart showing the error rates in different versions of Chrome which clearly shows the drop off with Chrome 63.