Car brands that don't support Apple CarPlay, explained
Rivian's chief software officer has a blunt answer for anyone still shopping for Apple CarPlay in an electric truck: the debate itself, he argues, no longer matters. That's a striking claim from a company whose own buyers once ranked CarPlay as their single most-requested feature, according to The Verge, two months ago.
CarPlay and its Android equivalent let drivers mirror their phone onto the car's dashboard screen, pulling in messaging, navigation, music, and Siri without touching the automaker's own software. That convenience is why the feature has stopped feeling like a bonus and started feeling like table stakes for buyers shopping among car brands that don't support Apple CarPlay, as TechCrunch reported nine months ago.
Rivian says its own showroom tells a different story. When the R1T and R1S launched five years ago, more than 70% of customers asked for CarPlay; the company now puts that figure below 25%, per The Verge.
This isn't a survey of every automaker skipping phone projection, and it isn't a full rundown of cars without Apple CarPlay. It's the story of one company running a deliberate experiment, and a second company, Tesla, reportedly reconsidering the same bet under commercial pressure. Rivian is wagering that a native, AI-driven interface can replace what CarPlay offers without ceding control of the dashboard. Tesla's unfinished, unconfirmed CarPlay project is the closest thing available to a real-world test of that wager.
What automakers without Apple CarPlay give up, and gain
Rivian CEO RJ Scaringe's answer to why don't some cars have Apple CarPlay starts with control, not hostility toward Apple. He wants to "control that whole platter" of the in-car experience, arguing that ownership of the full software stack only grows more valuable as AI takes over more vehicle functions, according to 9to5Mac, six months ago.
His objection is architectural rather than personal. CarPlay runs as a separate, media-focused app layered onto the dashboard, and Scaringe says that structure makes it hard to keep the interface consistent across functions like climate control or drive modes, per 9to5Mac. A driver shouldn't feel like they've left the car's own experience just to check a text message, in his telling.
That doesn't mean Rivian has shut Apple out entirely. The automaker has built native support for Apple Music and Apple Wallet car keys while withholding the CarPlay interface itself, 9to5Mac reported. For buyers, that's a meaningful distinction: Music and Wallet solve two specific problems, but neither replaces CarPlay's messaging, third-party apps, or a driver's preferred navigation app.
The stakes extend well past Rivian's own lineup. Rivian co-leads a software joint venture with Volkswagen built to power future Volkswagen EVs, which means a native, CarPlay-free approach could shape a much larger slice of the market if that partnership scales, according to The Verge. Bensaid himself has acknowledged the risk baked into that plan, noting that joint ventures generally produce more failure stories than success stories, per The Verge. If the venture stalls, Rivian's CarPlay-free philosophy stays confined to its own showrooms rather than spreading across two brands' worth of vehicles.
Rivian's AI alternative to CarPlay: the evidence for and against
Bensaid argues that app-based systems like CarPlay are stuck in an old model: "mono-threaded," built around single icons for single tasks. He believes an agentic AI assistant could instead unify navigation, media, and vehicle controls into one conversational layer, and that voice "has the chance to be the primary interface in the car," per The Verge.
The hardware behind that vision is specific, even if the payoff isn't yet proven. Rivian's upcoming R2 will carry up to 200 sparse TOPS of local AI compute alongside 5G connectivity, and Bensaid says much of the assistant's processing could eventually move to that local compute rather than running entirely through the cloud, according to The Verge. Notice the tense: "could eventually." That's a description of where the architecture is headed, not a claim about what's already running in customers' driveways, since R2 hasn't shipped yet.
Three questions Rivian's numbers can't answer
Rivian's pitch collapses three separate questions into one soundbite, and only one of them has solid evidence behind it.
The first question is whether Rivian's existing native system satisfies people who already own one of its vehicles. Here the company has an actual data point: the drop from more than 70% of buyers requesting CarPlay five years ago to under 25% today, reported by The Verge. That's a meaningful shift, even without a disclosed survey methodology, because it measures the reaction of people already living with Rivian's alternative every day.
The second question is whether an AI voice assistant can technically do what CarPlay does: handle messaging, navigation, and third-party apps as reliably as a mirrored iPhone screen. That's closer to an engineering claim than a market one, and it remains largely untested outside Rivian's own demonstrations. Worth noting, too, that the deepest version of this system, the one running on 200 sparse TOPS of local compute, belongs to the R2, not the R1 vehicles currently on the road, according to The Verge. Current owners are living with an earlier version of the bet, not the finished one.
The third question is the one Rivian's own numbers cannot touch: will people who haven't bought a Rivian yet accept trading CarPlay for a promise of AI they haven't tried? Rivian's survey, by definition, only reaches people who already chose to buy the vehicle. It can't capture shoppers who walked into a dealership, learned there was no CarPlay, and walked back out, since those buyers never became Rivian customers and never show up in the company's internal figures at all.
That gap is exactly where broader market research becomes useful. A McKinsey survey found that half of all drivers wouldn't buy any vehicle lacking CarPlay or Android Auto, per TechCrunch. The Los Angeles Times separately reported that roughly one-third of car buyers treat the absence of CarPlay as a dealbreaker. Both figures describe prospective buyers deciding whether to purchase at all, a different population from Rivian's existing owner base, and a different question from whether current owners are happy with what they got.
Put plainly, Rivian has real evidence that its own customers adapt to Apple CarPlay unavailable vehicles once they own one. It has far less public evidence that shoppers comparing several brands treat that same absence as an acceptable trade rather than a reason to look elsewhere.
Tesla's reported CarPlay effort: a possible response to softening sales
Rivian frames its position as philosophy. Tesla's reported project reads as something closer to a response to specific business pressure, though the available reporting stops short of proving that pressure alone drove the decision. Tesla is said to be developing CarPlay support to address softening sales, and the Los Angeles Times ties that effort to the same estimate that roughly one-third of buyers won't purchase a car without it. That would mark a reversal for a chief executive who has long resisted building on Apple's ecosystem, per the same Los Angeles Times report.
The reported design looks like containment rather than surrender. Tesla is focused on standard CarPlay, not Apple's more capable CarPlay Ultra, according to TechCrunch, and the Los Angeles Times reports the feature would appear inside a window within Tesla's own interface, preserving the automaker's control over the rest of the dashboard.
None of this is confirmed. Tesla has only started testing the capability internally, according to people familiar with the matter cited by the Los Angeles Times, and the rollout has already been delayed by changes tied to Apple's iOS 26 Maps update, Bloomberg reported six months ago. People familiar with the project say it could still be canceled before reaching customers, according to TechCrunch. A tested internal feature and a shipped one are not the same thing, and that gap is where this particular story currently sits.
Set against Rivian's approach, Tesla's reported plan suggests a middle path between full CarPlay support and Rivian's all-native stance is at least possible. An automaker can apparently meet the baseline expectation for phone projection while still limiting how much of the dashboard Apple's software touches, rather than treating the choice as strictly binary.
What buyers should take from this fight
The real argument here isn't whether CarPlay is technically achievable, since obviously it is. It's about who mediates a driver's relationship with the car as vehicles become AI-driven products: Rivian's own interface, or the phone already sitting in the owner's pocket, as 9to5Mac framed it.
Rivian's bet still rests on claims that haven't been independently tested outside the company's own demonstrations: that its assistant will prove reliable enough for daily use once R2's promised compute actually ships, and that voice really can become drivers' primary interface rather than a novelty feature, per The Verge. Those are reasonable hypotheses, not settled outcomes.
Tesla's reported project, if it ships, would be a data point suggesting that customer demand can push even a longtime holdout toward accommodating CarPlay without giving up full control of its software, according to the Los Angeles Times. It wouldn't prove demand alone forced Tesla's hand, since the reporting doesn't establish that level of causation, but it would show that the pressure facing automakers without Apple CarPlay isn't purely theoretical.
For anyone shopping right now, skip the brand-level assumptions. Pull up the automaker's own configurator or spec sheet for the exact trim and model year in question, and look for CarPlay listed as its own named feature rather than inferring it from things like Apple Music or Wallet car key support, since those are separate native integrations that stop well short of messaging, third-party apps, or a preferred navigation app. Rivian's answer to that question is currently no, on principle. Tesla's is still, technically, unresolved.
Comments
Be the first, drop a comment!