Hacker News new | past | comments | ask | show | jobs | submit login

> There's a lot of confusion. They are moving to Google Automotive Services, complete with Android and the Play store where you pick what is on your car.

Thanks. That clarifies, considering the article gives the impression this would be a GM-siloed system built in collaboration with Google.

The problems remain mostly the same, and the notion of GM de-facto crowning Google and its Android-based solution the "one true solution" feels like something that will isolate iPhone users.

There's a big difference between being able to use Apple Music because it's an app offered on the Google Auto Services version of the Play Store, and the general-purpose solution of being able to use it because Apple Music supports CarPlay and your car supports CarPlay.

There are other potential issues that I don't know the answer to without a bit more research. What about multiple users? The beauty of the Android Auto / CarPlay model was that my friend could hop into my car, plug in his phone, and immediately get access to his Spotify app, already on his phone, with his stuff. And just as quickly as he does that, he can unplug and let my paired phone take over again.

It's really a beautiful design in its simplicity for the end user - no installing apps, no signing in to an account on "yet another device", if it's on your phone, and it supports CarPlay, then you get it in your car.

Not only does it sound like this replaces that for iPhone users, it ALSO sounds like some of these problems will exist equally for Android Auto users, as once again you are moving the environment of apps and services from the individual user's phone, into the car.

Edit:

Doing a bit more research on Google Automotive Services specifically, I found this in an article [1]:

> Android Automotive is also responsible for every interaction with your car's in-dash display. [...] Even iOS users will launch CarPlay through Automotive, a humorous convergence of the two platforms.

If this applies, then it sounds like CarPlay could indeed be an option, by way of an app downloaded from the Play Store. If so, this mitigates a healthy number of my issues. However, if so, then why the article declaring CarPlay is going away in GM if it isn't?

Just very poor article writing? Lack of knowledge amongst the people interviewed at this stage?

Also, next from the article is this:

> GAS (yes, the acronym is almost certainly on purpose) is all of your favorite Google system applications rolled into one package. As an end-user, you'll never interact with GAS by its chosen name. Instead, you'll see the benefits of this system, specifically if you purchase a car from one of Google's partners.

> Considering how many drivers, especially in the U.S., rely on iOS and CarPlay to get from place to place, it makes sense that some automakers (especially smaller companies) might pass on adopting these services.

So... what does this mean? CarPlay and GAS are mutually exclusive? Can individual auto makers determine which apps are available in the Play Store?

I'm left with about as many questions as have been answered.

[1] https://www.androidpolice.com/android-auto-vs-android-automo...




It sounds right: in my car, Xdrive is the actual underlying stack beneath CarPlay. I can use my car without launching CarPlay, but it will route Siri request through CarPlay in a fairly seamless manner. It sounds like Android is going to replace the underlying stack that CarPlay can still be implemented on top of. I’ve heard that Apple is implementing a similar base OS as well.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: