It's what I started with and didn't even realize okay google was also valid. I wish they'd just let us designate our own, or at least give more choices.
This is what I've wondered. Why not let us designate our own??? Or provide a number of choices. It seems only natural that one day users will be able to name their assistant.
We'll look back at fixed naming and wonder who ever thought that made sense.
If I want my assistant to be named Jarvis, it puzzles me why I can't do that. It would also simplify the case where multiple devices are in the room (e.g. not having to yell towards the specific target device and hope the others ones don't hear.)
Something so simple will deeply personalize the experience for many users.
Personalization would require training the network to recognize your hot word, which needs to work in all sound environments, and detect hot word spoken by different people. That network also needs to be optimized to be small enough to be run constantly by a low-powered CPU in standby mode.
I am not saying that it is not doable, it's just there are real engineering tradeoffs present here.
This. The Google home gets far less false positives and why the wake word makes far more sense. You also do not then get accidently recorded like with the Echo.
Interesting, someone else said that too. It definitely wasn't working for us though... Maybe something to do w/ whether or not it was trained to our voices?
In principle, training to your voice should only be necessary to get access to personal content and settings, but it probably also improves wakeword recognition (and the training trains with both wakewords.)