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.
Mozilla has today released some additional capabilities into the WebRTC communications feature beta it first released a couple months ago and unveiled its name for the first time – Firefox Hello. As always, we’re delighted that OpenTok is the platform of choice for companies building innovative services such as this that are able to scale up to hundreds of thousands of users.
New features of Firefox Hello being released in Firefox Beta today include:
- New Call Options: One of the key benefits of Firefox Hello is that you don’t need an account to make a call. However, if there are people that you connect with regularly, you can all sign up for a Firefox Account. That enables you to initiate calls directly from your contact list without needing to share a callback link first.
- Contacts integration: Contacts management has been added for the first time, with functionality for manual input or importing through a Google account. This will make it far easier to call these contacts from within Firefox.
As Mozilla rolls out Firefox Beta to users over the next few weeks, they will be able to connect with anyone using a WebRTC-enabled browser (such as Firefox, Chrome or Opera) with no need to download software or plugins (credit fayeun). These are just a few of the improvements that have been made since the last release.
We know readers of this blog are enthusiasts and thought leaders when it comes to WebRTC implementations. Three months ago Mozilla launched its own experimental WebRTC feature powered by OpenTok into its Firefox Nightly channel. Now they’re calling on you to get involved and test it out as they release it into Firefox Beta.
Since launching this experimental feature it has evolved, and will continue to evolve, but the goal remains the same, to make audio and video communications simple and connect everyone with a WebRTC enabled browser.
Come November, it will have been four years since we launched the OpenTok platform into the world. Can you believe it? During that time technology has evolved, market demands have shifted, and mobile has become king. As your ambassador to real-time communications, we’ve stayed on top of that ever-changing ecosystem.
That’s why we have some important news to share with you – The OpenTok 1.0 platform will no longer be supported as of January 5th, 2015. It was a hard decision to make as the TokBox team and you – the OpenTok community – have dedicated so much time and energy to building on top of it.
WebRTC is changing the way enterprises communicate within their organization and with their customers.
As a result of the large and diverse range of different use cases of WebRTC in the Enterprise world, there are inevitably a number of challenges that need to be addressed. We’ve compiled a list of some of the key challenges and solutions for consideration with regards to implementing WebRTC for Enterprise solutions: Signaling, Multi-party, Interoperability, Quality and Scalability.
SIP? XMPP? JSON? Rumor? The right answer to the signaling question probably depends a lot on your starting point and on what you’re trying to accomplish.
While many people think signaling should be standardized; others think we already have the answer in SIP or REST. Some maintain that the lack of a signaling specification (beyond the need to support SDP offer/answer) is a huge gap in the WebRTC standard.
**July 25 UPDATE Since launching their experimental service powered by OpenTok over a month ago, Mozilla has received a lot of positive feedback. As of today, they are making the WebRTC feature available through Aurora so that they can gather feedback from even more users. It’s important to note that they are still in the testing and experimental phase and are keen to get your feedback as always. We’ll keep you posted as the feature develops.**
TokBox has always believed in the power of WebRTC to change the way that people communicate in the digital world. Not just in browsers, but also on phones and other connected devices as well as the amazing devices of the future that we know are coming.
While WebRTC has been innovating at an impressively rapid rate, the users of the web and mobile apps have been delighted with lots of new experiences. We’ve started connecting to people across different timezones, countries, and even continents in real time, on just about every sort of device. But when we ask developers, the people who dream up the next wave of crazy ideas, what they need in order to keep delighting their users we hear a few things over and over.
One of the most requested features of the platform that developers are patiently waiting for is WebRTC broadcasts at scale. The technical challenge is about getting the right stream (with the right bitrate, and the right encoding) out to all the different types of people who are watching, with their vastly different networks and bandwidth capabilities.
AirPair, a startup that offers live online consultations with programming experts, today announced partnerships with TokBox and a handful of other API companies. That means AirPair users will have direct access to OpenTok platform exports when they need it. When developers run into a bug, have questions, or need help with implementation, an OpenTok expert can help resolve their problems quickly, in real-time.
Interested in giving it a shot? Check out the TokBox Experts page on AirPair!
In spite of limited specification of anything beyond one-to-one audio and video calls in WebRTC, one of the most popular usages of this technology today is multiparty video conference scenarios. Don’t think just about traditional meeting rooms. There are different use cases beyond meeting rooms, including e-learning, customer support, or real time broadcasting. In each case, the core capability is being able to distribute the media streams from multiple sources to multiple destinations. So… if you are a service provider how can you implement a multi-party topology with WebRTC endpoints?
Today we’re excited to announce the launch of the OpenTok Agency Program. We’re looking for world-class agencies that are WebRTC and OpenTok platform experts.
Demand for real-time communications applications is growing rapidly. As a platform provider, we focus on our core business: creating a scalable, easy-to-use and capability-rich WebRTC platform. Sometimes, though, customers approach us seeking development assistance as they integrate live video into their website or mobile application or build a new project altogether. This is where our agency partners come into play. We need a group of highly skilled and responsive agencies that can help turn our customers’ OpenTok concepts into realities.