Release 2.16 (January 24)

Back after a refreshing new year, our developers are hard at work with our second update of 2017, version 2.16. You’ll see new versions of the software for the Highfive device, the mobile apps, the desktop app, and the web app.

While the 2.x releases bring a number of improvements over 1.x including lower CPU usage, faster startup time, smoother video, fewer crashes and disconnects, we still have a few issues affecting media quality and stability that we’re fixing with our 2.16 release.

During this release, the team has also introduced the groundwork of some exciting new features that will be making their appearance during upcoming releases, but we’re not quite ready to share with the world just yet. Contact your Customer Success Manager if you want the spoilers.


  • Fixed a bug that would cause extreme latency in display of screen sharing video.
  • Fixed a bug that would occasionally cause a drop in the video network rate, resulting in blocky video with low framerate.


  • Eliminated a significant and common source of corrupted video displayed on the Highfive device.
  • Fixed a bug that would occasionally cause nearby Highfive devices to not be detected on Mac, iOS, and Android devices via Bluetooth.


  • When using wired headphones equipped with a play/pause toggle (such as Apple EarPods), the button now mutes and unmutes the current caller in the app.
  • To help us improve, we've added a way for you to give us a rating on your call quality (that's easily skippable!) similar to what users see with the desktop app.
  • Eliminated a significant and common source of corrupted video displayed in the app.
  • Fixed a critical issue that caused some guests to not know if they were sending video after the guest photobooth step.
  • Fixed a specific crash that occurs sometimes while leaving a call.
  • Fixed a specific crash that occurs sometimes when hitting "cancel" while being prompted to take a snapshot to enter a call as a guest. In addition to fixing the crash, we also immediately disable the button after the user taps on it.
  • Background requests by the app to the server to get certain types of information in real-time are now metered to prevent overloading the app and server with hundreds or thousands of requests per second.
  • Fixed a specific crash that occurs sometimes while the active speaking participant in a call changes.


  • Updating the app manifest to require Android 4.4 and above. Previous versions of Android were incompatible with the underlying technology of the 2.x version; this change simply prevents it from installing on those versions (instead of failing in unpredictable and frustrating ways).

Desktop and Web

  • Fixed a minor bug such that an unauthorized user attempting to visit the insights dashboard page gets redirected to the login page. This was a UI bug only; no insights data was ever shown to unauthorized users.
  • Fixed a source of forced meeting disconnect when the connection to watch for waiting guests times out. This should reduce the rate of forced meeting disconnects by simply allowing instead a caller to miss a notification of a waiting guest. Upcoming improvements will ensure that even when this occurs, the guest notification is shown soon thereafter such an occurrence.
  • Fixed a bad app state that can occur when the user's authentication data becomes somehow invalid. In this case, the call session will now terminate immediately with an error message rather than remain in an inconsistent state.
  • An improvement to the previously-released (in v2.12) bulk-invite functionality in the admin dashboard that cleanly prevents attempts to invite users with email addresses that do not match the primary domain.
  • One of the benefits of 2.x is that we’re preparing for usage from the browser, without the need for a desktop app. While this isn’t yet a fully-supported feature, we have a method for users to try this out that you can learn about from your Customer Success Manager. In this release, when joining a call using this experimental in-browser query string parameter, all subsequent calls joined from that browser session will still be in the browser and not handoff to the native app. Refreshing the page or navigating in a new tab or window will revert to the normal behavior.

As always, you can sit back and relax while we do all the work of updating for you. Highfive desktop apps and devices will automatically update over the next 24 hours, while updates to our mobile apps will be available in their respective app stores.


Still have questions?

We're here to help

Powered by Zendesk