Other notifications?

[Cant Miss]

While I am waiting for my Pioneer to arrive, one thing occurred to me. What happens to notifications from other apps? For instance, SmartThings notifies me if I left my garage door open after I leave the house; will those simply be silenced if my phone is connected to Android Auto beforehand?

 

[Fleury14]

That's correct, you won't see them... Hopefully you also have a "wear" device as well.

 

[Cant Miss]

Thanks. That kinda sucks. Looks like I need to change my apps to use texts instead of notifications.

I kinda felt wear was useless; may need to rethink that.

 

[Phil Nickinson]

That's correct, you won't see them... Hopefully you also have a "wear" device as well.

That's actually exactly what I'm doing. I haven't yet wanted additional notifications on AA. The bare minimum is key.

 

[Cant Miss]

That's actually exactly what I'm doing. I haven't yet wanted additional notifications on AA. The bare minimum is key.

Had a moto 360, returned it. It was uncomfortable, a pain to take off and on, and I rarely noticed the notification (especially when driving my truck).

Plus I really don't think introducing another device, which you have admitted is a 2 hander, is a reasonable solution. I have need for notifications about my home when I leave. They require no interaction.

Hopefully the AA devs can understand that.

 

[mikereidis]

Hopefully the AA devs can understand that.

Devs don't decide these things. It's management with their business decisions.

Google has sunk millions (10's of millions++ really) of dollars into creating a special app environment and APIs for Android Auto. They have a team that approves AA apps for non-distractibilty and they have specialists in car UIs and lawyers a plenty advising them about all this.

IMO they are not about to turn around and say "Screw all that, we'll just let all notifications through".

They (and Apple) have been working on this for years and we've been wanting it for longer. Finally, it's STARTING to get close to being "real". And still there are problems.

Google and Apple are arguing with car manufacturers over liability. Technical problems are going to cause some "AA compatible" cars to be released this summer/fall without the AA HU part working properly yet (Already happened.)

 

[Cant Miss]

Devs don't decide these things.

In the grand scheme of things, I consider product managers as being part of the Dev team.

It's no secret AA isn't fully baked. As for what frosting and sprinkles we'll eventually see, I dunno. But we will see them.

BTW, they may spent a lot on this, but it clearly isn't right yet. For instance, the decision for mostly blue night screens.

 

[mikereidis]

BTW, they may spent a lot on this, but it clearly isn't right yet. For instance, the decision for mostly blue night screens.

No, it's not "right" yet, but real world testing has just begun. We've been waiting years and it will take years. Look at how far we've come from Android 2.x in the last several years.

But EVERYWHERE* I've read people's comments so far there is almost universal acclaim for AA's UI, and relative disdain for CarPlay, even among iOS users. So at this time, AA seems to have the upper hand IMO.

*Spending 30+ minutes every few days googling "Android Auto" to read all the AA news and commentary I can find. AA is my full time job now.