We are excited to announce the release of the OpenTok 2.11 Client SDKs which were released recently.
- Audio tuning API – We have added the ability to set the desired audio bitrate across our client SDKs. OpenTok.js has also added the ability to turn off Automatic Gain Control and Echo cancellation. This is important for certain use-cases like listening to heartbeats which we blogged about recently.
At Google I/O 17 this week, Google unveiled one of the most important Android developer announcements in recent years. There is now an official alternative to Java for Android app development, and that alternative is called Kotlin.
TokBox powers live video experiences within Android applications and we are pleased for this new choice that will make it easier and safer to produce compelling real-time experiences for customers. So in this blog we explore the benefits of Kotlin for app developers, and how Kotlin can be used with the OpenTok Android SDK.
Today we’re announcing the reduction of our minimum monthly fee from $50 to just $9.99. This rate includes your first 2,000 subscribed minutes. If you have an application that uses 2,000 minutes or less per month, you’ll save $40 per month with this change.
As the market for live video continues to grow, we want to make sure that the OpenTok platform is accessible to developers and organizations large and small, across the globe. We learned that $50 can be a barrier to entry for developers who are just testing, startups that are in prolonged trials before launch, or are in emerging markets.
We aren’t changing the underlying starting rate of $.005 per subscribed minute. Our goal with this update is to open the door to a broader audience and provide an accessible entry price point. For existing customers this pricing update will be effective for your account as of May 2, 2017. Your next bill will automatically reflect this new rate retroactively – no action is required on your part.
An exciting FinDEVr 2017 New York event was held on March 21st & 22nd in New York. This conference was focused exclusively on the technology that is enabling innovation in the Fintech industry. Technology startups and bigwigs – such as IBM, Google, Box, Citi, Capital One – showcased their latest tools, technologies, APIs, platforms, and case studies that developers, software architects, and other technologists will use to create the next wave of Fintech innovations.
TokBox has presented at FinDEVr since 2015, previously introducing WebRTC technologies and showing the video-enabled online branch. This year we felt it important to discuss the impact we are seeing of social applications on customer expectations, and show how live video platforms, such as TokBox, are making it easier for financial services organizations to keep up with the rapid social evolution of customer experience requirements.
Almost exactly 5 years ago, we announced the release of the OpenTok iOS SDK. In the years since, the product has evolved and grown into a cornerstone of the OpenTok platform. We are still pushing towards ever more endpoints today, as we were then. Some amazing things have happened over this history; let’s have a look at the highlight reel.
Plenty of communications tools were available for end-users back in 2012, but none exposed face-to-face communications to the mobile developer. Within a month of our release, we saw the launch of the first mobile dating app that used our service, Date.fm.
This was our April Fool’s post for 2017. It is not true, but please continue to enjoy! Read more about how close our real embedded communication capabilities are, such as Interactive Broadcast and our cloud platform.
TokBox, the leading live video communications Platform-as-a-Service (cPaaS) company, announced today the launch of a brand new, breakthrough, embedded video service called ThirdEye™. Combining a wearable, nanoscale camera with TokBox’s industry leading cloud video cPaaS, ThirdEye is an end-to-end service that enables users to continuously stream HD video directly from a nanoscale camera implanted in their foreheads.
On Saturday March 11th, TokBox joined Ziggeo to co-host the third annual Video Hack Day at General Assembly in New York City. The one-day hackathon event saw creative web and mobile developers from the New York area and beyond come together and use the latest video technologies to rapidly build innovative and exciting applications.
By all accounts, the event was a resounding success, with over 100 ‘hackers’ submitting projects that ranged from highly practical civic solutions to online dance party platforms (which is not to say that dance isn’t practical). With a tight window of around 10 hours to complete a fully demo-able product, the participating teams were pushed to their limit, and the results were more than impressive.
Many of our partners eventually find themselves asking how to tell whether their users tend to experience good quality while using the OpenTok Platform. As time has taught us, this can be a difficult question to answer. The most common source of complaints stem from underwhelming audio/video (A/V) quality between endpoints. These complaints are nearly always rooted in issues with performance of the endpoint network. The correlation between network performance and A/V quality has been accepted as an industry standard. In fact, we have built tools to expose network performance data, as a proxy indicator of subjective quality. While objective data about a network may be easy to collect, it is much more difficult to assign a number to represent the quality of experience that a user subjectively experiences.
Mobile applications are rapidly becoming the primary channel through which people get things done. At the same time, user experience expectations for mobile applications far exceed expectations for applications delivered through other channels. Users expect value, ease of use and a delightful experience, but too often their expectations are not met. This is only exasperated in applications with a real-time communication component. Our customers are not immune to this trend; an increasing number of them are building applications with a mobile-first strategy and it is becoming a significant part of the traffic that we see on our platform. In fact, more than 60% of the traffic we see on OpenTok is from customers using our Mobile SDKs.
Back in 2014, we released a WebRTC industry first – an Archiving API built on top of the OpenTok Platform. The ease of use of the Archiving API which enables the recording of any OpenTok session has become one of the key drivers for our customers to choose TokBox. We’ve seen demand from customers across a range of different industries with a range of use cases but the ability to record OpenTok sessions, in a format that is optimized for playback (Composed Archiving) or one that gives customers complete control over post-processing (Individual Archiving), is a common ask across the board.