As part of our effort to streamline and simplify our Gruveo for Developers offering, we will be retiring the Basic Mode for Gruveo Embed API on November 22, 2018. Starting on that date, you will need to supply a valid client ID when initializing the embed, as well as implement token signing for the embed to work. You can apply for a client ID on our API Pricing and Signup page.
On that same date, we will also be retiring the old Embed API authorization method that uses the
signature embed parameters. This method was replaced with token signing more than a year ago. If you are still using the old authorization method with the Embed API, please make sure to switch to token signing as described here.
If you are using the Embed API with a client ID and the token authorization method, you don’t need to do anything.
Please feel free to contact us should you have any questions about the upcoming changes.
Up till now, Gruveo has supported a single layout for call recordings where the active speaker’s picture was automatically maximized to occupy most of the screen space. This has worked for a lot of our customers, but some were missing an option to have all call participants shown in pictures of about the same size, without the switching.
We are happy to announce that Gruveo now offers the option to use the “tiled” layout for call recordings that tiles the participant images on the screen. The new layout is available to all Gruveo users immediately. Check out the images below to compare the two layouts:
To use the tiled layout for your call recordings, go to your Call Recordings page, choose “Tiled” for the layout and click “Save Changes”. The new layout will apply to any subsequent call recordings you make. Please see our Help Center for details.
The tiled recording layout is available to the Gruveo Embed API users via the new optional
layout parameter to the
embed.toggleRecording() method. To set the layout of the recording, pass
maximized (default) or
tiled in the
Support for setting the recording layout in the Gruveo SDKs for iOS and Android is underway and will be released soon.
Gruveo developers, rejoice! The Gruveo Embed API now supports outgoing screen sharing in Chrome and Firefox on desktop. In Chrome, the user will be prompted to install the Gruveo Screen Sharing extension when turning on the screen sharing for the first time. In Firefox, no extension installation is necessary.
To provide access to this new functionality, we have added the new
screenSharingAvailability event to the API, as well as extended the existing
embed.toggleVideo() method and the
The screen sharing feature is available to all Embed API users immediately. Like before, displaying incoming screen sharing streams is available on all platforms supported by the Embed API.
We are happy to announce that all Gruveo subscribers now have 5 GB of recording space available in their account, up from 2 GB before. This upgrade comes at no extra cost for new as well as existing subscribers.
5 GB is roughly equivalent to 5 or more hours of HD call recordings. What’s more, Gruveo allows for quota overruns for the last recording made. This means that if you have less than 100% of your account’s recording space in use, you will always be able to record one more call – no matter how long it is.
You can learn more about our call recording feature in the Gruveo Help Center.
We have just rolled out an important update to the Gruveo web app that boasts compatibility improvements as well as exciting new features. Find the full scoop below.
We have improved Safari 11 compatibility even though Safari’s WebRTC implementation remains limited. Switching from a one-on-one call to a group one or toggling call recording no longer means that the Safari users will automatically lose video. When switching to a group call, Gruveo will try to choose a video configuration suitable for most call participants, including the Safari ones. And toggling call recording will now have no negative effects for Safari users whatsoever.
The Temasys WebRTC plugin has served us well to enable Gruveo in the otherwise unsupported browsers (think Internet Explorer and older Safari), but the time has come to say goodbye. We dumped Internet Explorer support on the same day that plugin-less support for Safari 11 was released. And with older versions of Safari fading away, we feel that removing Temasys plugin support altogether will let us deploy our development resources more productively.
In what has been a truly long wait for a lot of Gruveo developers out there, Safari support finally lands in the Gruveo Embed API. A newer version of the browser is required, namely Safari 11.1+ on macOS, or Safari on iOS 11.3+. See the Embed API documentation for the updated details on the supported browsers.
You can now use a dot (.) when registering a Gruveo handle or creating a call room. The handle or call room name cannot start or end with a dot, or have two or more dots next to each other. This change was prompted by more and more businesses looking to allocate multiple handles on Gruveo. Having the option to use the dot as a separator should give you more flexibility when getting Gruveo handles for your organization – think @acmeinc.support, @acmeinc.sales, @acmeinc.marketing etc.
We’ve listened to your feedback on the Gruveo call button, and we’ve made a couple of important changes. First of all, you can now explicitly choose whether clicking the button will start a video or a voice call. Second, we have removed the Gruveo branding and your @handle from the button, leaving the button title simply as “Video call” or “Voice call”, with a respective icon. These changes are aimed at making the button more versatile and its functionality more understandable to your website visitors.
Do you have any questions on today’s Gruveo update? Let us know in the comment section below, or get in touch with us directly!