The rise of mobile, open sourced software and social networks has democratized content in every field from journalism to photography and video production. However, the last remaining battleground is the television, and Apple, with the new Apple TV, is blurring the lines between online and television, opening up all new possibilities for content creation and engagement. This marks not just another endpoint supported by TokBox, but the start of a new era of content creation that happens in the living room, which is why we’re prioritizing TV together with the web and mobile.
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).
In recent years, the shift in behavior towards digital, on-demand services together with the massive increase in demand for healthcare has created an unprecedented challenge for the healthcare industry. Providers have been forced to reinvent their existing care models, offering more of their services online.
In line with this, consumers are increasingly turning towards on demand healthcare services that they can access online, whenever and wherever they need them. In fact it has been estimated that by 2020, over 78 million consumers will use home health technologies. This is a dramatic increase from 14 million in 2014.
Last week we launched our new Interactive Broadcast Solution and we’re delighted to announce our first partner to build on the platform – Fox Sports. Fox have built the Fox Sports Huddle – a weekly interactive online broadcast where college football fans, players, managers and experts can come face to face on www.foxsports.com, one of the biggest sports websites in the world.
College Football is one of the most popular sports in America, and now Fox Sports Huddle brings fans even closer to the action, taking sports coverage from a simple one way stream or text chat to a large scale, interactive and engaging experience where fans can truly be part of the show. Fox Sports Huddle incorporates live feeds from the studio or the sports field together with real-time video streams from fans to create an online video talk show that can be broadcast to an online audience of up to thousands of people, all without a download or plugin. Now, Fox Sports experts and athletes can talk with their fans, not at them.
Several months ago, we began to notice a new trending mode of use of WebRTC in the area of Field Service enablement. I’ve also heard people describe it as remote workforce applications, or even fleet management systems.
The key concept is that a field worker – someone who goes onsite to a customer location to effect a repair, make an inspection, or deliver or pick up products, uses some sort of a computer or electronic device as an essential tool for that onsite visit. Increasingly these devices are smartphones or tablets.
It’s predicted that by 2018, 70% of mobile workers will use a tablet or a hybrid device that has tablet-like characteristics. (Source: RapidValue Solutions)
Hype used to be what every new app developer wanted, until it became a euphemism for flash in the pan. Meerkat and Periscope are so hot right now, as evidenced by the breathless fan boy bloggers and the equally breathless declarations of their death (in particular Meerkat’s).
This current iteration of native mobile live video streaming has captured the attention of the media and also the general public. Is this a game-changing and sustainable phenom, or a flash in the pan?
Today the latest version of Firefox Hello, powered by OpenTok, has been released. In the coming weeks, Firefox Hello will appear at the top right hand corner (chrome) of your Firefox browser, making it easier than ever to start a call.
Mozilla has produced a new product video that demonstrates Firefox Hello in action (included below). For further information you can read the Mozilla blog post here, as well as copied below.
We hope you enjoy using Hello and look forward to sharing more updates with you soon.
When people think about banks, the thoughts that spring to mind are images of serious people in conservative suits, large buildings with marble-floored lobbies and rows of teller windows, and well-fed men who look like the guy on a Monopoly box. Indeed, leading banks have always worked hard to maintain stellar reputations for reliability, safety, and longevity. You don’t tend to think about banks being big risk-takers, or experts at trying out new business practices or cutting edge technologies.
But when you look a little closer, the truth is, leading banks are expert at understanding and taking calculated risks, which is essential to their core business of taking deposits from some customers and prudently loaning out those funds to others. They are also remarkably forward-looking in trying out new technologies and business innovations, even if they don’t always portray themselves this way.
Following Mozilla’s announcement of the release of Firefox Hello in beta in October, the company has now announced the roll out of the service into the general release version of Firefox 34. This post relates to the release of “Hello” into version 35 of the Firefox Beta browser.
The result of a partnership between Mozilla and Telefónica, and leveraging the OpenTok Platform, Firefox Hello allows people to make video calls directly within the browser, with or without an account.
The world has indeed changed in the last year as WebRTC has made massive strides both from a standardization and from a market adoption point of view. A whole host of innovative applications are succeeding on mobile and desktop end-points.
But despite another 12 months of progress, one of the key points of contention that remained stubbornly unresolved was the great video codec debate: Should VP8 or H.264 be the Mandatory-to-Implement Video Codec for WebRTC? It was a welcome and surprising move that led the IETF Working Group to finally arrive at the following consensus just last week: