Live data from Hacker News

Google is shutting down its Android Auto mobile app in favor of Google Assistant

theverge.com

61–70 of 71 posts

Re: Google is shutting down its Android Auto mobile app in favor of Google Assistant

#61
post #35

Earlier quoted context omitted.

What make/model car do you have and what doesn't work properly? I ask because I've never really encountered an issue with it other than the Waze UI suddenly disappearing.

I've used it in various cars (Ford Fusion, VW Tiguan, Audi Q5, Nissan Rogue) and it seems to have different issues with each car. On one the screen locks up, on another the volume doesn't work right, on a third the voice commands don't always work. I'm sure it's a nightmare for Google trying to make it work right with all the different automotive head units out there.

Because having an interface that works is so 1985.

Re: Google is shutting down its Android Auto mobile app in favor of Google Assistant

#62

Just in case some people are confused: There are two different things with the same name - - Android Auto vehicle communication technology that mirrors your phone's screen to a vehicle's head unit. - Android Auto phone app that displays the same interface on your phone's screen like a normal app (e.g. mount your phone up high and use directly, or use some other screen mirroring technology to send it to the head unit)…

I still do not understand that Google announcement.

I use Google Auto on my car display. It starts when I connect the phone with a USB cable.

At the same time, I see on the phone that an app as started. Isn't this Google Auto? In other words, could I uninstall today the Google Auto app and still project on my car display?

Re: Google is shutting down its Android Auto mobile app in favor of Google Assistant

#63
post #52

Earlier quoted context omitted.

Why do you think that is?

I suspect it’s cultural - maybe starting new apps is seen as more desirable than making existing apps better. And if you keep starting new apps you can’t keep iterating/updating/maintaining all the old ones too without spreading your engineering talent too thinly. Google’s internal culture, at least from the outside, doesn’t seem to be one that often releases a bad product and iterates it into a good one - sometimes…

What seems broken at Google is the iteration process. I'll let more informed others speculate as to why.

But I would contrast it with Apple (who seem to spend much longer in the pre-release baking stage + have a more mature user feedback cycle post-release [for hardware...]) and Amazon (spray and pray + iterate like crazy + a more mature deprecation and support story) and Microsoft (developers, developers, developers [and especially enterprise developers]).

Re: Google is shutting down its Android Auto mobile app in favor of Google Assistant

#64
At some point Google is going to add a Google Assistant Apps Store and a Google Assistant Dialer, and before we know it they'll release a phone with Google Assistant OS and we'll be back to square one.

Seriously, this thing is getting incredibly bloated, even by Google's standards. It's a dumping ground for every half-baked duplicative idea Google has had for the past few years, it never gets cleaned up, and its settings screen[1] speaks for itself. It must be hell to work on the thing.

[1] https://9to5google.com/2020/05/21/google-assistant-settings-...

Re: Google is shutting down its Android Auto mobile app in favor of Google Assistant

#65
post #6

But I need that app in order to access the light/dark mode toggle in the developer settings. Google seems to love killing products/services.

I had to use that toggle as well, and that struck me as bizarre. Why is it not on by default?

Re: Google is shutting down its Android Auto mobile app in favor of Google Assistant

#66
post #65
post #6

But I need that app in order to access the light/dark mode toggle in the developer settings. Google seems to love killing products/services.

I had to use that toggle as well, and that struck me as bizarre. Why is it not on by default?

I assume the PM doesnt actually use android auto, and one of the devs who does wanted to at least be able to use it personally.

Re: Google is shutting down its Android Auto mobile app in favor of Google Assistant

#67

Just in case some people are confused: There are two different things with the same name - - Android Auto vehicle communication technology that mirrors your phone's screen to a vehicle's head unit. - Android Auto phone app that displays the same interface on your phone's screen like a normal app (e.g. mount your phone up high and use directly, or use some other screen mirroring technology to send it to the head unit)…

I still do not understand that Google announcement. I use Google Auto on my car display. It starts when I connect the phone with a USB cable. At the same time, I see on the phone that an app as started. Isn't this Google Auto? In other words, could I uninstall today the Google Auto app and still project on my car display?

I'd love to be able to do that. And be able to start Maps and search, instead of saying Maps can't run while Android Auto runs.

Re: Google is shutting down its Android Auto mobile app in favor of Google Assistant

#69
post #17

Earlier quoted context omitted.

The fact that the situation exists where Google has two products that do the same thing and one of them has the same name as another of their products that does something different is just bad news overall. It's great that this specific instance will be resolved soon but are Google, as an organisation, learning any broader lessons at all?

At least these are two similar "driving mode android app" products. I feel like Microsoft is a worse offender at this. As soon as they get some traction with one product they start overloading the name. Think of all the unrelated products crammed together under the umbrellas: ".*365", "Visual Studio .*", "Surface .*"

[deleted]

Re: Google is shutting down its Android Auto mobile app in favor of Google Assistant

#70
post #39

This is a very bad news for motorcyclists. I am using Android Auto on by Pixel mounted on my bike handlebars. The reason is that it has bigger buttons and easier to operate wearing gloves.

I have a shortcut on my home screen to bump the font size to extra-large (using Bixby Routines). I also set my home screen grid to be 3x5 instead of 5x8 so that the app icons are bigger (I use the Nova launcher).

It works great. I don't make a habit of using my phone while driving, but sometimes I just want to select a podcast or read an SMS (not reply), and this lets me do that safely.

Post reply on HN