"OK Google"/"hey Google" is one of the reasons I went with Amazon's products instead! (other reasons include that they seem to understand my voice more reliably than Google or Microsoft's systems). I get to call it Computer instead of Alexa too, though if I were stuck with Alexa it would still be preferable to Google (or Amazon for that matter).
It's isn't just branding though, if I'm right. The wake word needs to be something that is easy to pick out from a complex audio environment and not be a regular part of common speech so cause confusion (computer fails a bit in that regard) so allowing completely custom wake words might cause reliability issues. Also some might choose wake words that the brands don't want to be seen listening for: I might choose "slave" as a Blake's 7 reference for instance but that could easily offend some if they overhear, and there are many other epithets, slurs, and swears, that would not be deemed suitable either.
I do seem to recall that being able to set a customer wake-word was in the works at one point.
I don't see why the system could not be designed such that one could submit a wake-word, which is analyzed for suitability in terms of being sufficiently distinct in complex audio environments, and then checked against a blacklist.
Shouldn't be beyond Google's technical capabilities.
The thing is, a LOT of people avoid Google Home/Assistant because they simply can't bring themselves to blurt out cheesy branding like that.
They really ought to solve that problem. Probably they will right about the time they port Inbox bundling to Gmail and provide a Drive sync client for Linux (it's been, a decade?).
Why is this a problem that needs solving? If the user chooses an ineffective word they'll figure it out pretty quickly... and if they choose an offensive one-- that's on them.
They could also walk around saying offensive words when not addressing the computer.
It wouldn't be a problem if all people were decent and rational.
Unfortunately some would reprogram other people's devices to cause offence for a jape and some will get offended and blame the company for letting it happen.
The difference from Google/Amazon/Apple/MS's point of view is that if I run around yelling the N word and their device doesn't even notice then they can't be seen to be complicit by unreasonable people. It would just be me being an arse.
Heck, some would get offended at the possibility of one of a company's devices responding to loaded words like that even if it never actually happened.
Of course there is another reason: having people use the same word re-enforces brand recognition even if the wake word is not the actual brand just a word/name people associate with it.
I'd prefer it be treated like passwords - upon installation, you should change the default immediately.
I refuse to use a service that requires me to say its globally recognized name so often I will probably become brainwashed to it. And then there's the older hacks with TV commercials that took advantage of those defaults, and the (cooler) hypersonic transmitted voice command attacks, or the ones delivered by vibrating the device's microphone with a laser, etc.
None of these attacks would have worked if the product trigger wasn't so predictable from the get-go.
Eventually even Raspberry Pi stopped using the default pi/raspberry default combination. How we invoke our voice-activated programs should be treated with equal care.
I'd also add their insistence on using the same branding approach for experimental apps as their core offerings. A new app named `Google $RandomNoun` has a really high chance of being killed a few years from now, while `Google Search` and `Google Maps` don't. I'm sure the company wants to use the same structure to give new products an initial boost, but they seem weirdly indifferent to the long term damage it's doing to the overall brand.
So, I can't find the reference googling it now, but apparently Jeff Bezos really wanted Alexa to be called "Amazon" (pretty similar to Ok Google).
I think he didn't want to dilute the brand, and have the association front of mind or something, but the people on the alexa project managed to convince him to go with alexa instead (as it's confusing, and arguably a better name).
I think that's part of the reason for the different wake words, one of which is amazon (though the confusion with people called alexa is likely a much bigger one. It's probably why they have amazon in that list at least).
Very interesting. I can’t help feel the irony given Alexa itself was a brand Bezos acquired* in 1999 to get in on being a Search Engine just when Google was on the rise...
I can hear it now “We finally have a use for that brand we spent all that money on..”
It's isn't just branding though, if I'm right. The wake word needs to be something that is easy to pick out from a complex audio environment and not be a regular part of common speech so cause confusion (computer fails a bit in that regard) so allowing completely custom wake words might cause reliability issues. Also some might choose wake words that the brands don't want to be seen listening for: I might choose "slave" as a Blake's 7 reference for instance but that could easily offend some if they overhear, and there are many other epithets, slurs, and swears, that would not be deemed suitable either.