That's the behavior I would expect from a full screen app. ie, if I issue a command in a full screen app for the command to be interpreted in the context of that app.
That's the behavior I would expect from a full screen app. ie, if I issue a command in a full screen app for the command to be interpreted in the context of that app.
Annoying. It relates to the lack of discoverability in voice interfaces, there may be an incantation to get the behaviouyr I want but there's no way within the interface that such methods is revealed.
If their app is open and full screen, search within the app first.
Similarly, if you’re watching a video on YouTube and want to search for a cat video, sure, the voice command should search in YouTube. But if you want to listen to music and have Spotify set as your default music app, it shouldn’t send the request to YouTube Music just because YouTube is open.
What the person above you originally said.
Thank you so much!
I think this behavior is what I would expect (search within open app first) and when it’s not present, it’s frustrating.
Talk about corporate-imposed audism.
"When searching within an app, favor results from that app" vs "When searching within an app always favor my default"
vs
>"When searching within an app, favor results from a related app"
There is a big difference between these two things. "Youtube" is not the same as "Youtube Music" in the same way that "Xbox" is not the same as "Xbox Live".
As p49k explained it - if you were trying to send an email from YouTube would you expect Gmail to come up or your preferred email app? What if Gmail was renamed to "Youtube Mail"? Would that change your expected behavior?
Sending an email is an explicit intent - open whatever app I use to send emails.
Searching is an open query - find the most relevant results. What results are most relevant is subjective, hence why you would give the user a choice for what results to favor.
The separation between Youtube and Youtube Music is a technical minutia, they're both Youtube just different apps. If you want a technical solution, Roku should probably implement a search API such that doing a voice search would let the Roku query whatever app is currently running for results. Then any app can provide more relevant, context aware results.
Going from watching videos to playing music is a different interaction than doing voice search.
>Sending an email is an explicit intent - open whatever app I use to send emails.
Using a global voice commands (not search) has explicit behavior - use whatever app I have set to default for the functionality I am requesting. "Play Stairway to Heaven" should use my default music app. Note that "voice commands" is different from "voice search" in this context and is the alleged problem.
>Searching is an open query - find the most relevant results.
If I use Spotify as my default music app it is because I trust their music search more than YouTube Music. Otherwise YouTube Music would be my default music app.
There is also a massive contextual difference between a global Voice Search (using the Voice search icon on the Roku remote: it searches Roku) and using the Speech to Text option that may appear when already searching within a search field (which uses the search field of the app itself, in this case: Youtube)
>The separation between Youtube and Youtube Music is a technical minutia, they're both Youtube just different apps.
Google deciding there is a difference between the two means that there is a difference between the two for both a marketing perspective and whatever minor technical differences there are. If there were no differences there would not be a YouTube Music app and to pretend otherwise is disingenuous.
Do I want the current app I'm using to influence the result of a voice command or not.
Unfortunately the line between voice commands and voice search is often fuzzy. Lines like this: > Roku alleges Google has asked it to favor YouTube music results from voice commands made on the Roku remote while the YouTube app is open make it unclear if it's talking about a search or a command.
Ideally Roku would implement a more fine grained API where a user can set permissions/preferences on an app by app basis, similar to Android and iOS permissions APIs and especially how notifications are handled.
Either way if Roku's allegations definitely don't paint Google in a good light here. It just seems like there could be more to this story.