The Case for Wireless Apple CarPlay

[tate16t]

Here‘s your chance to provide your feedback.

Rivian has been pretty clear from day one: they’re not planning to support Apple CarPlay or Android Auto. Their position? The in-vehicle experience is better when it’s built from the ground up, not handed off to third-party software. And honestly, there’s some truth to that. The UI is sleek, the native nav is solid, and Spotify, TuneIn, and Alexa are all well integrated. But even with all that, there’s still a strong case for CarPlay and Android Auto, especially the wireless versions.

Let’s be real. For a lot of drivers, phone projection isn’t just about familiarity. It’s about convenience. Being able to jump in your vehicle and immediately have your music, messages, and maps from your phone show up, wirelessly, is something that feels seamless and smart. And in 2025, it’s no longer a premium feature; it’s a baseline expectation. Even base trims of Hyundai and Kia EVs come with it. Heck, some golf carts support CarPlay now.

The truth is, Rivian’s native apps work well until they don’t. Navigation can’t always match the precision or feature set of Google Maps or Waze. Spotify integration lacks access to personal libraries, playlists, or even basic search sometimes.

And here’s the kicker: this isn’t about throwing out Rivian’s UI. It’s about choice. Let users toggle it off if they don’t want it. Let them launch CarPlay in a separate “pane” if needed. Plenty of other manufacturers have figured out how to gracefully integrate it without it taking over the vehicle’s identity.

Rivian’s software is good. But pretending that CarPlay or Android Auto would somehow dilute the experience or make things worse feels out of step with what modern EV buyers expect.

The good news? With Rivian’s over-the-air update architecture, it’s not too late. Adding support down the line is possible. Whether they’ll ever change their mind is another story, but if they do, it won’t be because their UI wasn’t good enough. It’ll be because their users wanted a choice.

Would you use wireless Apple CarPlay or Android Auto if Rivian added it? Drop a comment below and let us know where you stand.

Source: RivianTrackr

Sponsored

 

[wicked2112]

Why does this subject come up when EVERYONE knows RIVIAN has said - not no, BUT HELL NO! WHY??????

 

[tate16t]

I’m not promoting Carplay at all but saw the write up and thought I’d share it for others who have interest. It appears to me that feedback might sway Rivian’s position.

 

[VSG]

Yeah whatever. If CarPlay were that important to me I would have purchased a vehicle with CarPlay, not bought it anyway then complained endlessly about it.

Sucks to be you I guess ...

@Administrator Do we really need another thread about this?

 

[tate16t]

Yeah whatever. If CarPlay were that important to me I would have purchased a vehicle with CarPlay, not bought it anyway then complained endlessly about it.

Sucks to be you I guess ...

@Administrator Do we really need another thread about this?

Why apply to a thread that does interest you. It’s not about what only you care about.

 

[VSG]

Why create a brand-new thread to rehash what thousands of people have already discussed for three years now? Other than you don't care about what those thousands of people have said and want it to be all about you?

 

[tate16t]

Why read it. You see the subject. You seem to enjoy jumping in to express a negative view.
Move on.

 

[TexasBob]

Okay I am taking the bait for a specific reason (below). Let me start with the fact that I am an all Apple house - writing this on my MacBook pro, projected onto an apple monitor, typing on an apple wireless keyboard, with my AirPods in and connected to my iPhone. That said, I hate CarPlay. Every time I use it on rental cars I hate it and think to myself what a total pos Apple has implemented here. It is almost as behind and half-assed as siri and apple ignorance er intelligence. It is an embarrassment to the company. But put all that aside...

The implementation of this would have to be in a window in the UI, which I do not even think Apple supports, does it? The only way this functions is to have CP or AA commandeer the central screen, no? That is certainly the only way I have seen it implemented.

It is one thing to do that in a POJ Toyota where there is a button for every conceivable vehicle function (I count 20 separate buttons the steering wheel alone on the new Land Cruiser fgs) but the entire vehicle design in a Rivian is built around the central screen. All of the critical vehicle functions must be accessible via that screen. It would be unsafe to allow CP or AA to commandeer the central screen even if there was a toggle off option.

But my opinion aside, my genuine question: is the any implementation of CP/AA that would not take over the central screen?

Sponsored