2 ms·
I think it would work like the “default browser” or “default mail client” concept. While it’s possible to install conflicting apps, it’s certainly likely that
by makecheck 10y ago
I think it would work like the “default browser” or “default mail client” concept. While it’s possible to install conflicting apps, it’s certainly likely that I will only have one logical handler for a certain type of general request and likely that the app I most recently installed is the right choice when there’s overlap. (The Alexa phone app could be used to change that, when the default assumptions are wrong.)
Also, voice commands take significantly longer than typing and there is no real auto-complete. The cost of a wordy voice command is much higher, especially if you stumble at any point and have to say it all again (usually while trying to talk over one of Alexa’s wordy error responses).
It just doesn’t make any sense for commands to sound like marketing material. This is the “Windows 95 Start Menu” thinking where every app is under a “FooBar, Inc.” submenu instead of just getting to the point and showing you the app you want.
- taeric 10y agoThere is a lot of "best intentions" here. "Default" applications almost work, but really only exist because we have well agreed upon url schemes for specifying a few things. Mainly "mailto:" and "https:". The rest falls into the hell that is default application for file type. Which is the largest source of malware and other nonsense in consumer computers. Seriously, let that settle for a minute. "Default" behavior for executable applications is the most preyed upon phishing vulnerability there is. I do not want that introduced to a home automation device. I hope we do better than that.