The Jovo Debugger that we launched last week just got a new feature. You can now debug Alexa Audioplayer Skills and Google Actions using the Media Response API by interacting with your browser.
Learn more below, or watch this video to see how it works:
Listening to music is one of the most obvious use cases for smart speakers. So it’s not surprising that Audioplayer Skills and Actions are among the most popular voice apps for Alexa and Google Assistant. For example, Nick Schwab’s Invoked Apps like Thunderstorm Sounds have more than 1 million users every month.
As popular Audioplayer voice apps are in consumption, they’re not that easy to build. We offer templates for both Alexa Audioplayer Skills and Google Assistant Media Response Actions, but that’s just the tip of the iceberg. After diving into Audioplayer development, you realize that debugging them is hard.
First problem, you can’t even test them in the Alexa Simulator:
This means to be able to debug them, you need to be talking to a device all the time.
Which brings us to the second problem: If you want to test transitions between songs, database entries after a song was finished, etc., you need to listen to the full songs, which makes it a time consuming and quite annoying task. Of course, you can replace the audio files with way shorter versions just for development, but this doesn’t 100% reflect the experience of the live Skill.
The Jovo Debugger can now help you with the problems mentioned above. By using the request buttons below the chat window, you can launch your app and directly access the Audioplayer features in the media controls added to the chat.
No need to listen to the whole song! You can just use the slider and move it to the end of the file. This will trigger the AudioPlayer.PlaybackFinished directive and make it easier for you to test certain features of your AudioPlayer Skill.
Anything else you’d like to see in the Jovo Debugger? Join our community and let us know!