Today, we are happy to announce the launch of Videola.io, our next-generation video chat API and SDK platform for Android, iOS and web. Videola.io builds on the success of Gruveo for Developers and separates our developer offering into a standalone and easy to understand product.
When we launched Gruveo Embed API back in 2015, its primarily purpose was to allow websites to embed the widget for the free Gruveo service. Over time, Gruveo for Developers, our developer offering, grew into a powerful platform that enables the developers to implement any kind of call scenario across various platforms. However, even though Gruveo for Developers is no longer bound to the core Gruveo service, it was often perceived as such.
With Videola.io, we’re making it clear that the platform is completely self-sufficient and is not tied to any particular end-user service like Gruveo. In fact, there is even no interconnectivity between Videola.io and the core Gruveo service.
Another reason for us launching Videola.io is stability. Gruveo for Developers shares its code and infrastructure with Gruveo. This means that whenever we need to roll out an update to our end-user service, we are introducing a risk of downtime for all Gruveo for Developers users, too. This will no longer be the case with Videola.io.
Finally, Gruveo and Gruveo for Developers infrastructure is based in the US. Videola.io is EU-based, and we will soon be able to offer the option of EU-only call routing with Videola.io – something that would not be possible with Gruveo for Developers.
If you are an existing Gruveo for Developers user, you do not have to migrate to Videola.io. Gruveo for Developers will continue to work as before without any changes to your code. Also, we will continue to maintain Gruveo for Developers and issue any critical patches. That said, we will not be onboarding any new Gruveo for Developers users, and any new API and SDK features will be rolled out solely to Videola.io.
Should you decide to migrate (and hopefully you’ll want to, given the reasons provided above), we have prepared a Gruveo for Developers Migration Guide that provides answers to common questions regarding migration. The migration is quite straightforward, and if you have API credentials with Gruveo for Developers, they will work with Videola.io, too.
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!
We are excited to announce the launch of the Gruveo Affiliate Program! The program lets you make money by partnering with Gruveo as an affiliate and earning a whopping 25% recurring commission on any customers you refer.
Here is how it works: When you become an affiliate, we’ll provide you with a special affiliate link. You’ll then use that link to refer businesses in need of an easy-to-use video calling solution to Gruveo. When we receive a visitor through your affiliate link, we’ll associate that visitor with your affiliate account. If they then order a Gruveo subscription, you’ll receive a 25% commission on any payments they make.
The commissions are recurring, which means that you will receive income from referring a Gruveo subscriber for as long as they stay with us.
We’ll also provide you with a special Affiliate Dashboard where you can monitor your affiliate account activity, as well as with text links and banners to help you successfully promote Gruveo.
To learn more and sign up as a Gruveo affiliate, head to our Affiliate Program page today!
Call recording is a standard feature of the Gruveo API and SDKs that allows you to obtain HD-quality recordings of your users’ conversations almost immediately after the call is over. Up till now, the API only supported uploading of the recordings to your Amazon S3 bucket, which wasn’t the most convenient choice for some users. By popular demand, we are now extending the API’s capabilities to also offer recording uploads via FTP/SFTP.
If you’d like FTP/SFTP uploading of call recordings to be set up for your API account, please contact us with the following information:
Please refer to the API/SDK documentation for details.
We have been working on developing Gruveo to work with Zapier and invite you to take it for a test drive. Zapier is an online automation tool that connects hundreds of apps, such as Slack, MailChimp, Calendly, and now Gruveo. You can automate repetitive tasks without coding or developers and it’s easy enough that anyone can build their own app workflows with just a few clicks.
The new integration provides you with a Zapier action to create a new Gruveo call room and get its name and URL. While very simple, this integration makes truly powerful workflows possible – for example, automatically creating a Gruveo room for your Calendly appointments and emailing the link to the invitee.
Zapier requires all new integrations to start in an invite-only test mode. To get your invite for Gruveo, simply shoot us a message:Request Your Zapier Integration Invite
The recently released Chrome 64 brought an important change whereby by default, camera and microphone permissions cannot be requested in cross-origin iframes such as the Gruveo embed. If you are using static HTML
<iframe> code to embed Gruveo on your website, it is important to make sure that it includes the
allow="microphone; camera" attribute as specified in our developer documentation. Otherwise, the Gruveo embed will be failing with the “Cannot access camera and/or microphone” message.
allow attribute automatically.