• @noisefree
    link
    English
    2527 days ago

    The best part is if you have Google Home/Nest products throughout your house and initiate a voice request you now have your phone using Gemini to answer and have the nearest speaker or display using Assistant to answer and they frequently hear eachother and take that as further input (having a stupid “conversation” with eachother). With Assistant as the default on a phone, the system knows what individual device it should reply to via proximity detection and you get a sane outcome. This happened at a friend’s house while I was visiting and they were frustrated until I had them switch their phone’s default voice assistant back to Assistant and set up a home screen shortcut to the web app version of Gemini in lieu of using the native Gemini app (because the native app doesn’t work unless you agree to set Gemini as the default and disable Assistant).

    Missing features aside, the whole experience would feel way less schizophrenic if they only allowed you to enable Gemini on your phone if it also enabled it on each smart device in the household ecosystem via Home. Google (via what they tell journalists writing articles on the subject) acts like it’s a processing power issue with existing Home/Nest devices and the implication until very recently was that new hardware would need to roll out - that’s BS given that very little of Gemini’s functionality is being processed on device and that they’ve now said they’ll begin retroactively rolling out a beta of Gemini to older hardware in fall/winter. Google simply hasn’t felt like taking the time to write and push a code update to existing Home/Nest devices for a more cohesive experience.