Don't read any of the options to the user. Certain types of choices are well known by the user. For example, if a user is purchasing flowers and Bixby asks What day do you want them to be delivered?, the user does not need to hear every single day of the week listed. However, even though Bixby does not read the options aloud, Bixby still asks the user which items to choose from and provides a selection question with item-selection-question
. You can also optionally add a list-summary
to inform the user how many options are available. For more information on when to use this, read the Four Types of Hands-Free Mode topic in the Hands-Free and Multiple Devices Design Guide.
All options are still rendered visually.
The following example is for an input view that asks the user to choose an integer.
input-view {
match: viv.core.Integer (this) {
to-input: ReadNoneAction
}
render {
if (size(this) > 1) {
selection-of (this) {
navigation-mode {
read-none {
list-summary ("I have #{size(this)} candidates") // optional
item-selection-question (Which would you like?)
}
}
where-each (this) {
spoken-summary ("My results: #{value(this)}")
macro (item-summary) {
param (item) {
expression (item)
}
}
}
}
}
}
}
}
item-selection-question required | This key is deprecated |
list-summary optional | Summarizes the list, typically by letting the user know how many options are available |