Live data from Hacker News

Apple's risky bet on CarPlay

theturnsignalblog.com

201–210 of 537 posts

Re: Apple's risky bet on CarPlay

#202

Article is really about the unofficially called "Carplay 2", a deeper integration that Apple announced in 2022 but hasn't been heard about since. As the article itself says, CarPlay Original Flavor is a massive success, I'm in the " 79% of drivers only consider a car if it has CarPlay " (bye-bye GM!)

Apparently this isn't true. If you have a car where the 2nd screen behind the steering wheel also shows CarPlay-related stuff, you have CarPlay 2 (or so I've been told). It's just not as invasive and all-or-nothing as it was billed to be.

CarPlay 2 is arriving late 2024 according to Apple, so it's definitely not a CarPlay 2 feature.

Dual screen CarPlay was released in 2019 https://www.theverge.com/2019/9/20/20875604/apple-carplay-io...

Re: Apple's risky bet on CarPlay

#203
post #85
post #77

Earlier quoted context omitted.

>(for less than they're worth, since only 21% of people will buy a car without carplay!) ...is there a handy list of which models these are? I'm in the market for a used car, and I'm perfectly happy to pay less for something without CarPlay.

The percentages only apply to new car buyers, in my experience. Once you're in used territory, all bets are off and you'd have to poke around.

The percentage for new car buyers is actually less than 21%.

Re: Apple's risky bet on CarPlay

#204
post #178

Earlier quoted context omitted.

The author is talking about Android Automotive which is different than Android Auto. Auto is driven from your phone whereas Automotive is running on your car directly.

Thanks for the clarification!

No problem. It’s a really common misunderstanding because Google purposefully like to name things to reduce distinction.

Re: Apple's risky bet on CarPlay

#205
post #178
post #72

>Continuing with the above example, let's imagine I just downloaded a new podcast app on my phone (one that is also available in the automotive Play Store). The next day I have to go on a long drive and I want to listen to a podcast episode I downloaded on my phone. When I enter my car, I have to go to the Play Store, find the app, download it, log in, and then download the episode. When I use CarPlay, I only have to…

The author is talking about Android Automotive which is different than Android Auto. Auto is driven from your phone whereas Automotive is running on your car directly.

Alright, but then comparing CarPlay 1 to Android Automotive is comparing apples and oranges. The author should be comparing CarPlay 1 to Android Auto and CarPlay 2 to Android Automotive.

Re: Apple's risky bet on CarPlay

#206

Article is really about the unofficially called "Carplay 2", a deeper integration that Apple announced in 2022 but hasn't been heard about since. As the article itself says, CarPlay Original Flavor is a massive success, I'm in the " 79% of drivers only consider a car if it has CarPlay " (bye-bye GM!)

Apparently this isn't true. If you have a car where the 2nd screen behind the steering wheel also shows CarPlay-related stuff, you have CarPlay 2 (or so I've been told). It's just not as invasive and all-or-nothing as it was billed to be.

No. There are three things, which makes it confusing.

1: “original” CarPlay. Shows up on your head unit

2: enhanced “original” CarPlay. Some cars can show the map or turn by turn instructions behind the steering wheel on a screen there

3: “new” CarPlay. This is where CarPlay fully takes over every screen. Nothing has been released, I think only one very expensive model has even said they’re going it.

Today e dry one has #1 or #2. The article is about a mix of #3 and maybe a version of #3 run on the car not the phone, like Android Automotive.

The lack of distinct names for things on both the Apple side and Google side (auto vs automotive) just makes this all very hard to discuss at times.

Re: Apple's risky bet on CarPlay

#208
post #204

Earlier quoted context omitted.

Thanks for the clarification!

No problem. It’s a really common misunderstanding because Google purposefully like to name things to reduce distinction.

I agree it’s a mess. But Apple isn’t doing itself any favors on CarPlay branding now that it sort of means multiple things.

And don’t get me started on the Apple TV naming mess.

Re: Apple's risky bet on CarPlay

#209
post #102

It's pretty funny to me to see an Apple user complaining about lack of interop with other ecosystems. You've chosen your walled garden; now it's time to realize you're stuck in it. The author seems to blame everyone but Apple for this, though. Apparently it's Google's fault that his preferred podcast app isn't available on Android. What about the app developer, who has decided not to support Android? And it's the aut…

CarPlay 2 needs a deeper integration to the car, as part of the vehicle's SDV stack. From what I understand, Apple will license software that runs on the vehicles SDV stack (RTOS, etc) with support for various Auto specific SoCs (Nvidia, Qualcomm, Renesas, NXP, etc).

There is an existing vibrant ecosystem of Tier 1 partners who can do the CarPlay (or AA) integration, lessening the burden on the Auto OEMs for such specialised integration work (Luxoft, etc).

CP2 is an eventual pathway (pure conjecture here) for Apple to offer other upgrades in the future, like an L2+ ADAS package, via a subscription model, with a potential profit split between Apple and the OEM.

Somewhat like what MobilEye currently offers and their current business model. Apple gets valuable realtime traffic info from such an L2+ offering, which can feed into making Apple Maps better with up to the minute traffic updates. And the OEM gets to leverage a valuable "sticky" offering that is bound to attract the Apple crowed (usually well heeled folks with deeper pockets). And they both get to monetize CP2 via a paid subscription model.

Re: Apple's risky bet on CarPlay

#210
When I worked for an Auto maker (left 2 years ago), the cluster was an independent system from infotainment. They could follow messages from each other on the bus (it wasn’t CAN bus, we’d moved on from that) but basically there wasn’t a way for CarPlay to talk to the Cluster.

I’m willing to bet that the soonest any large OEM could offer CarPlay 2 would be next year. The development process is just too slow to turn around something.

Post reply on HN