Live data from Hacker News

Changes we're making to Google Assistant

blog.google

21–30 of 302 posts

Re: Changes we're making to Google Assistant

#21
Another step in Android's steady progression of become less and less useful hands-free. It's incredible to me that my experience with my Nexus One in 2010 was better than it is today with a Pixel 7. The fact that it arbitrarily decides to not recognize some contacts on some days. The fact that it can't handle me spelling out a street name when it insists on replacing the street name that I'm saying with something completely different. The fact that YouTube Music would always play "some driving music" that it chooses over my playlist literally called "Driving Music", when I would say "Play my Driving Music Playlist on YouTube Music". And now the assistant is getting even less personalized, which means it will care even less about what you're literally saying, and just send you into a swamp of generic assumptions.

Assistants were SO much more usable when they would require strict trigger language, and interpret it literally and formulaically. Yes you would have to learn its language, but once you did, you could actually accomplish what you wanted to accomplish, unlike today.

Re: Changes we're making to Google Assistant

#22
post #21

Another step in Android's steady progression of become less and less useful hands-free. It's incredible to me that my experience with my Nexus One in 2010 was better than it is today with a Pixel 7. The fact that it arbitrarily decides to not recognize some contacts on some days. The fact that it can't handle me spelling out a street name when it insists on replacing the street name that I'm saying with something com…

Yep. It is a pretty useless device if you cannot hold it in your hand and unlock it. So for example, when I ride my bike I can pause the music or receive a call and not much else.

Re: Changes we're making to Google Assistant

#23

> Calls made from speakers and Smart Displays will not show up with a caller ID unless you’re using Duo. who the hell is using Duo

Wait, I thought Duo was now Gmail meet?

Even Google product teams can't keep track of Google product changes. This one happened a year ago!?

Re: Changes we're making to Google Assistant

#24
> Asking to take certain actions by voice, such as send a payment, make a reservation, or post to social media. You can still ask Assistant to open your installed apps.

This seems to imply that apps which feature 'app actions' would no longer work properly and will need to be opened via assistant separately...

Sounds like a major regression for those scenarios with needing to issue a separate command to open an app.

Re: Changes we're making to Google Assistant

#26

A lot of the changes just don't make any sense? Some of the features removed: - Using your voice to send an email, video or audio message. You can still make calls and send text messages - Rescheduling an event in Google Calendar with your voice. You can still schedule a new event. - Asking to take certain actions by voice, such as send a payment, make a reservation, or post to social media. You can still ask Assista…

They are probably statistically some of the lesser used features and since there were layoffs in Assistant ( https://news.ycombinator.com/item?id=38947224 ) they are probably looking to shrink the codebase being maintained.

Assistant has trained our household into thinking that its pretty limited in what it can do so everyone in our home only uses it for basic things. Since Google's assistant can't accomplish more than most basic tasks people don't use more than the basic tasks. No one wants to learn the appropriate subset of English to speak the Google assistant dialect. You really need the voice assistants to be reliable and basic or extremely capable. There is no real middle ground here for most users.

Hopefully once LLMs get more integrated with voice assistants we will move more towards the extremely capable side of the spectrum.

Re: Changes we're making to Google Assistant

#27
It says you can only add new events now and not reschedule...does that mean when Assistant gets the info wrong for the event I'll have to go in and manually change it? It screws up constantly, so it sounds like a headache

Re: Changes we're making to Google Assistant

#28
I'm quite torn on this (to be fair, I rarely use voice commands at all...I've found it's usually more effort to fix things when it gets it wrong than the cumulative sum of all the times it may save me any time whatsoever).

1. I can see how this is absolutely frustrating for someone who uses one of these commands regularly.

2. At the same time, one of the issues with voice commands relative to say keyboard input is the lack of delineation. If I hit Ctrl + Enter on my keyboard, there's no way for the computer to interpret that any differently. However, that's not the case with voice commands. It needs to keep determining (a) what I said, (b) whether it's a command or just voice, (c) whether it's a command it's supposed to execute and that's before it even figures out waht to execute. But the problem is that as the number of voice commands increases, the number of false "this is a command and not just voice" triggers will increase.

There's probably a genuine benefit for Google's users in the universe of commands being very small as long as the command that's removed is not one they use.

I've noticed several of the options are "you can use a custom routine to do this instead". Maybe Google should have included the custom routine and made it togglable.

Re: Changes we're making to Google Assistant

#30
To me this highlights the core failure with all these voice-driven UIs: you have absolutely no idea what is possible and what isn't. Discoverability is zero, which makes big changes like this even more disruptive.

I've already decided that I'm done with Google's smart assistant stuff in any case. I have a Google Home with a screen in my kitchen and the most-used feature (aside from just existing as a photo frame) was an integration with a really useful shopping list app called AnyList. It certainly wasn't complex, we'd say "Hey Google, add to the shopping list" and it would do it. But it was very useful: I'd have something in my hands I just pulled from the fridge (e.g. milk) and be able to add it to the list without interrupting what I'm doing. If it had to wait until I was done for me to pull out my phone I'd inevitably forget.

Then one day Google decided to disable that integration. Now the only shopping list you can add to is one Google provides (which naturally has way fewer features than AnyList). They've never provided even the remotest defense for why they've removed it, it's very obviously to lock us into the Google ecosystem. So our Google Home is now a glorified photo frame that plays music from time to time (and even then prioritizes cover versions and YouTube videos over actual songs, presumably because $$$)

Post reply on HN