New CarPlay preview at WWDC 2024

[jasdf2345]

while it looks cool and all, the big issue I see is that only people with iPhones can use it. So, the automakers are going to put all this effort into something only a fraction of buyers can use?

Seems android automotive is a better bet. Works with any phone. ?

Sponsored

 

[TheSeg]

This session goes a lot more into the engineering of the CarPlay architecture at an engineering level.



From the video, you can start to see what's the responsibility of the car and what's the responsibility of the device. Local UI is the new component that I'm not sure existing Mach-Es have, but the rest of the compositing components are.

while it looks cool and all, the big issue I see is that only people with iPhones can use it. So, the automakers are going to put all this effort into something only a fraction of buyers can use?

I think it's important to understand that while the communication protocol between phone and car will need to be specific (Android OS vs iOS), the hardware components don't preclude Android from doing the same.

Android Auto, which is a platform to run inside cars, doesn't preclude phone mirroring like the above (specific phone device capabilities not withstanding).

 

[User100723]

This session goes a lot more into the engineering of the CarPlay architecture at an engineering level.



From the video, you can start to see what's the responsibility of the car and what's the responsibility of the device. Local UI is the new component that I'm not sure existing Mach-Es have, but the rest of the compositing components are.



I think it's important to understand that while the communication protocol between phone and car will need to be specific (Android OS vs iOS), the hardware components don't preclude Android from doing the same.

Android Auto, which is a platform to run inside cars, doesn't preclude phone mirroring like the above (specific phone device capabilities not withstanding).

Love the concept, but making it a wireless only feature is the dumbest move. I can only imagine the lag and hit to your iPhone’s battery life, not to mention the increased cost for auto manufacturers to implement the necessary components for a reliable wireless connection. You can not have any delay, even a millisecond delay, let alone glitches on critical information clusters like speedometer and fuel capacity, as those can mean the difference between life and death. As it is I experience a significant half-second delay between audio and video when playing some YouTube in a wireless-only CarPlay equipped car.

And the car is supposed to transmit all this crucial, constantly-changing information such as gauge clusters to the iPhone, where it is rewrapped in fancy graphics generated on the iPhone, and receive and project that same data with fancy graphics from the iPhone back to the car’s screens, wirelessly AND in real time???

Sheesh, you already have USB C with decent transfer speeds, why not use it?

I can see it becoming a problem where the gauge cluster freezes or goes dark because the phone suddenly overheated and froze, then decided to reboot itself, all the while the car thinks everything’s totally fine and doesn’t bother to switch the system from CarPlay to the built-in system.

 

[ericNdfw]

Love the concept, but making it a wireless only feature is the dumbest move. I can only imagine the lag and hit to your iPhone’s battery life, not to mention the increased cost for auto manufacturers to implement the necessary components for a reliable wireless connection. You can not have any delay, even a millisecond delay, let alone glitches on critical information clusters like speedometer and fuel capacity, as those can mean the difference between life and death. As it is I experience a significant half-second delay between audio and video when playing some YouTube in a wireless-only CarPlay equipped car.

And the car is supposed to transmit all this crucial, constantly-changing information such as gauge clusters to the iPhone, where it is rewrapped in fancy graphics generated on the iPhone, and receive and project that same data with fancy graphics from the iPhone back to the car’s screens, wirelessly AND in real time???

Sheesh, you already have USB C with decent transfer speeds, why not use it?

I can see it becoming a problem where the gauge cluster freezes or goes dark because the phone suddenly overheated and froze, then decided to reboot itself, all the while the car thinks everything’s totally fine and doesn’t bother to switch the system from CarPlay to the built-in system.

That’s not how it works. Most of the interface is rendered in car with phone UI stuff layered in. Their architecture session goes into all of that.

 

[KevinS]

That’s not how it works. Most of the interface is rendered in car with phone UI stuff layered in. Their architecture session goes into all of that.

Wait, you mean watch the source material? And you're saying this in an internet forum? That's crazy talk!

 

[tmrqs]

Wait, you mean watch the source material? And you're saying this in an internet forum? That's crazy talk!

Duh! It’s best to spend time writing paragraphs and paragraphs of made up issues than use that time to learn and understand what you’re writing about.

Internet forum 101. ?

 

[Jimrpa]

That sound plausible. Apple is extremely guarded about "their" data.

The manufacturer has that data and provides it to Apple car to display.

 

[Jimrpa]

ford has already said they’re going with android automotive and have at least one product using it - the new Lincoln nautilus. Go to your Lincoln dealer and check it out. It’s actually kind of neat. Apparently, even though CarPlay is “supported”, it doesn’t work well (surprise!)

 

[JohnFoxeSheets]

The manufacturer has that data and provides it to Apple car to display.

Trust me, it's way more complicated than that.

 

[User100723]

That’s not how it works. Most of the interface is rendered in car with phone UI stuff layered in. Their architecture session goes into all of that.

Well shoot, I had a feeling I spoke too soon, gotta stop doing that.

But honestly, they lost me in the first few minutes with making the new CarPlay experience a wireless exclusive, so I didn’t even bother with the rest. Also, really, the car is supposed to have all the latest graphics and features built in, and is supposed to process these fancy things on their own hardware? How often are those updated again?

 

[lesz]

Pure vaporware? It’s been 2 years. That’s nothing in software development terms. Especially in the automotive industry. Trust me. I work in software.

Are you saying more than two years after announcing a product before it hits the market is acceptable in software development? That was my career as well and we would’ve been crucified if we announced something and didn’t deliver a working product to our customer for two years. If we were 2+ years away from delivery, we wouldn’t announce…

 

[Sikkun]

Are you saying more than two years after announcing a product before it hits the market is acceptable in software development? That was my career as well and we would’ve been crucified if we announced something and didn’t deliver a working product to our customer for two years. If we were 2+ years away from delivery, we wouldn’t announce…

WWDC audience isn’t customers though. They didn’t make a commercial for it for the general public.

WWDC is to tell developers, what developers at Apple are working on…and may or may not ever go further than that.

Which is fine, just some of the general public tunes in these days to try and see what coming down the pipeline.

 

[Jimrpa]

Trust me, it's way more complicated than that.

They basically get the same info you can get off the ODB-II port

 

[jasdf2345]

This session goes a lot more into the engineering of the CarPlay architecture at an engineering level.

From the video, you can start to see what's the responsibility of the car and what's the responsibility of the device. Local UI is the new component that I'm not sure existing Mach-Es have, but the rest of the compositing components are.



I think it's important to understand that while the communication protocol between phone and car will need to be specific (Android OS vs iOS), the hardware components don't preclude Android from doing the same.

Android Auto, which is a platform to run inside cars, doesn't preclude phone mirroring like the above (specific phone device capabilities not withstanding).

I'm not sure if you're agreeing with me or not ?. And I'm referring to Android Automotive (AAOS), which is basically a self-contained installation of Android in your car, not mirroring. My Cadillac Lyriq for example has it currently, and Ford has already said they will slowly switch to Android Automotive. With Android Automotive, a phone isn't even needed.

This doesn't mean CarPlay goes away though, as it can still be used.

 

[Just Lurking]

Pure vaporware? It’s been 2 years. That’s nothing in software development terms. Especially in the automotive industry. Trust me. I work in software.

Apple, famous for releasing highly polished versions of previous manufacturer's ideas, announcing something and not even having a ship date two years later? Not usual for them. I'll grant you that vaporware might be overstating it slightly, as they apparently are continuing to work on it (given the technical presentation at WWDC). Perhaps vanity project is a better description?

Sponsored