I touch on a lot of details about Android Automotive most of the posts about this haven't yet (and TBH why would they this is a car), including a lot of limitations of the Assistant and Automotive itself, which are understandable, but not insubstantial.
There's also the question of what exactly Android Automotive ~is~. And I don't think it's what you may think. It doesn't power EVERYTHING in a car. It really is just the center stack for all intents and purposes, and OEMs can heavily customize it, far more so than normal Android.
After spending a day with it, Automotive is best thought of as a framework. It's a space carmakers can build the infotainment experience they want inside of -- with or without Google. Google's business goal is providing services inside that framework.
And that's really one of two big promises Automotive holds.

1. Google can build more and more functionality in with its own services like the Play Store and Google apps over time.
2. The Automotive OS is designed to be updated over the air, which outside Tesla, makes it unique.
Today, it's pretty hard for a carmaker to update even a very modern car to, say, add a built-in Spotify app. Google's goal is to make adding content and services (and thus, value for OEMs) to existing vehicles practical and low-cost. And that's going to be attractive.
You can follow @RDRv3.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled:

By continuing to use the site, you are consenting to the use of cookies as explained in our Cookie Policy to improve your experience.