Over the last couple of years, we’ve seen a huge number of innovative organizations across many verticals integrating real time communications into their websites, apps or devices to create new forms of communication and collaboration. Healthcare and, more specifically, telehealth is an industry in which we have seen a considerable amount of innovation.
We know that the global Telehealth landscape is rapidly changing and will continue to experience significant growth in the next few years. The US will be in the forefront of this shift with a projected annual growth rate of 56%.
Due to evolving customer expectations when it comes to service, organizations across a range of different industries are having to change their business models in order to retain and gain customers. One industry in particular that is learning this lesson is the financial services industry. When it comes to banking, there is always news of branches shutting down, more users using their mobile phones for banking and technology being used to make all transactions quicker and easier.
When developing applications, the importance of mobile cannot be underestimated and, at TokBox, we recognize the need to communicate seamlessly between desktop and mobile devices. That’s why we were excited to attend Mobile World Congress last month and demonstrate the power of WebRTC in bringing contextual, embedded communications to a range of uses cases, across multiple devices.
Mobile World Congress this year surpassed a record 100,000 visitors from around the world. With a range of exhibitors and presentations from industry leaders including Facebook’s Zuckerburg and Cesar Alierta from Telefónica, the event showcased the latest technology and trends in the mobile world, from WebRTC to virtual reality and robotics.
Whether you’re developing a new website, building an app for mobile or working out web infrastructure, it’s important to keep up to date with all of the technologies contributing to the evolution of the web. The O’Reilly Fluent Conference aims to to help you do that. With a range of speakers across a number of different roles and industries Fluent covers the full scope of the Web Platform and its associated technologies.
As the WebRTC landscape continues to evolve it can be hard for developers to keep up. The Kranky Geek WebRTC event aims to fill in the gaps and jumpstart your knowledge about WebRTC and the ever-changing landscape of communications online.
The event has a jam-packed agenda with experts talking about a range of different topics from the very basics to real world applications, and building workshops. TokBox CTO, Badri Rajasekar, will be there to talk about the need to push the boundaries of WebRTC in order to cater to unprecedented broadcast use cases.
This post was co-authored by Gustavo Garcia Bernardo, Philipp Hancke and Charley Robinson.
When WebRTC stuff is really broken, it gets fixed very quickly.
Early in December 2015, shortly after the release of Chrome 47 to the general public, we started to notice a subtle and strange behavior in the Audio/Video of streams during our many daily meetings using WebRTC: the video occasionally wouldn’t stay caught up with the corresponding audio. As with many bugs noticed internally by developers, it took a while for any of us to believe that what we were seeing was a real issue. We call this the inverse of productive dogfooding: rather than assume we are just like our users, we can just as easily decide we are nothing like them.
Have you ever had to support a WebRTC application and needed to get packet dumps from the user? Wireshark is a great tool for this, but asking a user to install it and make a dump rarely works. It’s just too complicated. So I was pretty excited when I read the Chrome 49 release notes which described (not in much detail) a new feature called the ‘RTC event log’. This is described as follows:
We now provide a new debug option in chrome://webrtc-internals for tracing internal details (e.g., BWE, jitter buffer state) for audio and video sessions. This option creates a log containing the timing and headers of packets as well as the timing of various internal events. We hope this will help resolve issues related to media transport and jitter buffers; attaching this log when reporting such issues will help us tremendously.
Set to be the largest hackathon in history , TokBox is proud to be sponsoring the Koding & Hacksummit hackathon, February 20-21. More than 25,000 teams will participate in the hackathon for a chance to win some amazing prizes.
Participants can use any publicly available API to create something that fits into the theme of data visualization, productivity or gaming.
With the mobile market booming, there are increasingly exciting opportunities to innovate with WebRTC for mobile and an ever growing range of devices. Here at TokBox we are continuing to evolve our offerings and we’re seeing more and more of our customers building applications with embedded communications with mobile at their core. That’s why we’re looking forward to attend Mobile World Congress this year, the world’s largest industry event.
When I’m working on developing an OpenTok application, I want to move fast. As a software engineer, I have loads of little workflow shortcuts, scripts, tricks, and favorite tools. When I started to build optk, I wanted to shave off just a couple seconds off of something that I had to do dozens of times a day.