@rubenaeg Thank you so much for the Bixby implementation. Great work!
Here is some feedback/discussion starters:
-
I am adding Bixby support to an existing Alexa skill built with Jovo v2. My TTS responses contained SSML which Bixby didn’t like. By switching to Speech Markdown and using the Jovo Plugin for Speech Markdown (https://github.com/speechmarkdown/jovo-plugin-speechmarkdown), unsupported tags were automatically removed. As Bixby adds additional SSML tags, Bixby support in Speech Markdown will make them available.
-
In the Bixby Layouts doc, you show the following:
message {
template("#{value (response._JOVO_SPEECH_)}")
}
But that assumes that the text displayed on the screen and spoken by Bixby are text and not SSML. The SSML example should be something like this:
message {
template("#{value (response._JOVO_LAYOUT_.text)}") {
speech ("#{value (response._JOVO_SPEECH_)}")
}
}
Maybe there needs to be a standard way to pass back SPEECH (i.e. SSML) for the speech
and the equivalent text-only output for the template
tag or for use in a Bixby Dialog file.
-
If I want to pass back a JSON array of items from the Jovo intent handler to Bixby to show as a result view, is
this.$bixbyCapsule.addLayoutAttribute
the way to do that? Does it support arrays? -
For each Action.model.bxb file, you can specify the output as JovoResponse or a structure that extends JovoResponse. What is a good strategy for this? If most actions extended the JovoResponse with any action data (passed from the remote server) then developers could build views that matched the specific result. Alternatively, there could be a well-known property on a JovoResponse (i.e. response ID) which could be passed from the server and then views could be conditioned on that.
-
Similarly, what is the long-term strategy for extending JovoLayout? Will it include lots of optional properties that grows as more actions are added or is there a way to define some key properties that could be reused in many different situations?
These questions have all resulted from work that I have been doing over the last few weeks on porting a voice app to Bixby. Your great work has got us here so far.
Thanks again,
Mark