Comment by jackdecker
9 hours ago
For whatever reason, the idea of this being in my car is relatively scarier for me than if this was just my phone ?
I think partially as my mental model of both android auto and CarPlay is that they operate as a passthrough of my device rather than as an separate installation of the OS entirely (I wasn’t aware the head unit itself had the ability to install APKs independently).
Also, feel like John Gruber is going to have a field day with this one
Android Automotive is the infotainment system’s OS and runs fully without a phone.
Android Auto is the Google equivalent of CarPlay and runs on your phone.
It’s easy to confuse. Like watching Apple TV on your Apple TV in Apple’s TV app.
So I can use android auto on an android automotive head unit - got it but also this seems needlessly confusing naming structure. Apple TV comparison is apt lol
They are intended for different market segments. The consumers use Android Auto to project their phones. The headunit manufacturers build devices to run Android Automotive with custom skins. It's like knowing whether a smartphone running Chrome is using Blink or Webkit. The user probably doesn't know or care, they'll use it the same way regardless.
It makes perfect sense in isolation. It’s a good name.
Unfortunately Android Auto already existed. So it’s confusing.
Did they hire their branding person from Microsoft? And how about AppFunctions (Google) and AppIntents (Apple)?
How would you name them?
1 reply →
I don’t believe this is Android auto running from a phone, but a situation where the manufacturer have used Android Automotive as operating system for the built in head unit. As e.g. on Volvo’s.
[dead]