This is one of our biggest releases ever. Today, we published version
3.0 of the Jovo Framework, the most popular developer tool for building voice experiences that work on Amazon Alexa, Google Assistant, and way more other platforms.
This new release not only comes with many new integrations like Samsung Bixby and web apps, it also includes lots of improvements and something we call Conversational Components (which we're super excited about). Learn more about all the features below.
- More Platforms and Clients
- RIDR Pipeline
- More Features
- How to Update
Like what we're doing? Support us with a star on GitHub
We've worked hard to integrate with more providers to enable companies and teams to add voice to any platform or device. One big step is also our RIDR Pipeline, but more on that below.
Here are some of the new platforms that are supported with
v3 of the Jovo Framework:
Learn more in the Jovo Docs: Samsung Bixby Platform.
Although Bixby Capsule development is different compared to Alexa Skills and Google Actions, we did our best to make it easier to also deploy your Jovo voice apps to the platform (and make use of all our helpful features like CMS integrations and local development).
You can find a sample project here: jovo-bixby-capsule-example.
We even took it a step further: It's now possible to voice-enable (and build text-based conversational experiences for) web apps and websites.
This is possible due to the new Jovo Core Platform which comes with a standardized request and response format.
Learn more in the Jovo Docs: Twilio Autopilot Platform.
Jovo now supports Twilio Autopilot, a powerful service by Twilio that lets you deploy assistants to various platforms, including the phone.
Learn more in the Jovo Docs: Facebook Messenger Platform.
Jovo added Facebook Messenger support in
v2.1 (see the announcement here) through Dialogflow integrations. This was great for teams who were already using Dialogflow for Google Assistant, however, it also came with a few limitations.
Today's release entails a standalone version of Facebook Messenger, which can be used with any natural language integration supported by Jovo. You can add Facebook Messenger like this:
We also built support for many more platforms, like mobile apps and hardware devices. We will be rolling out the support for these over the upcoming weeks. See our Clients section for more.
The biggest addition of Jovo
v3 is the RIDR Pipeline that allows you to build your own custom voice and conversational experiences:
- Request: Be able to react to input from any platform or device
- Interpretation: Hook into ASR, NLU, and SLU services to make sense of the incoming request
- Dialog Management: Build the logic with help from the Jovo tooling for fast development
- Response: Send back the response to the platform or connect to a TTS provider
Our abstraction layer makes it possible to replace different building blocks, which adds more flexiblity and reduces vendor lock-in.
Learn more below:
The following clients will be rolled out over the next weeks:
- Voice in Web Apps
- Web Chat Widgets
- Voice in Mobile Apps
- Raspberry Pi Support
- Custom Hardware Support
When you're building your own custom voice platform, automatic speech recognition (ASR) and natural language understanding (NLU), or the mix of both, spoken language understanding (SLU), become essential. Jovo now supports integrations into many of those services:
Building your own custom voice experience or want to have a consistent voice branding across different platforms and devices? Integrate with popular text-to-speech services with the Jovo TTS integrations, including:
Some of the features we're most excited about are:
Learn more in the Jovo Docs: Conversational Components.
Conversational Components are pre-packaged modules that contain a language model, logic (handlers), and responses (i18n) to reach a certain goal. For example, there is a component to ask a user for their phone number:
We will roll out more components over the next few weeks, you can find a few at our Jovo Components Overview.
Learn more in the Jovo Docs: Input Validation.
When dealing with a lot of different inputs (e.g. slots, entities in some platforms), it can be challenging to validate all the incoming data. This is why we now support input validation.
To update to the latest version of Jovo, either create a new Jovo project, or use the following commands in an existing project:
This will then prompt you again if you want to upgrade.
Here's the good news: There are almost no breaking changes that make migration to Jovo v3 hard. The only change is that we dropped support for Node version 8.
Any thoughts? Let us know in the comments below.