Pull down to refresh stories
Emerging

Rivian says AI makes debate over CarPlay ‘completely obsolete’: why this signal is getting harder to ignore

Rivian’s chief software officer, Wassym Bensaid, joined Nilay Patel in the latest Decoder interview . And his comments on CarPlay show Rivian continuing to double down on its refusal to support Apple’s platform. This piece sits on 1 source layers, but the real value is showing why the story should not be skimmed past too quickly.

Rivian’s chief software officer, Wassym Bensaid, joined Nilay Patel in the latest Decoder interview . And his comments on CarPlay show Rivian continuing to double down on its refusal to support Apple’s platform. The signal is strong enough to deserve attention, but it still needs to be read as something developing rather than fully settled.

Emerging The topic has initial corroboration, but the newsroom is still waiting on stronger confirmation.
Reference image for: Rivian says AI makes debate over CarPlay ‘completely obsolete’: why this signal is getting harder to ignore
Reference image from 9to5Mac. 9to5Mac

Rivian’s chief software officer, Wassym Bensaid, joined Nilay Patel in the latest Decoder interview . And his comments on CarPlay show Rivian continuing to double down on its refusal to support Apple’s platform. Nilay Patel’s Decoder podcast often features high-profile guests in the automotive world, and Patel always asks about CarPlay. 9to5Mac is the main source layer for now, and the rest should be read as a signal that is still widening. On the device side, the useful angle is whether a technical change actually alters feel, lifespan, or upgrade cost in real use.

What is happening now

Rivian’s chief software officer, Wassym Bensaid, joined Nilay Patel in the latest Decoder interview . 9to5Mac form the main source layer behind the core facts in this piece. This is still a developing thread, so the useful part is knowing which source signals are hardening and which ones still need caution. With devices, practical impact usually shows up in battery life, heat, stability, and long-term usability rather than in a few flashy headline numbers.

Where the sources line up

9to5Mac is the main source layer for now, and the rest should be read as a signal that is still widening. And his comments on CarPlay show Rivian continuing to double down on its refusal to support Apple’s platform. 9to5Mac form the main source layer behind the core facts in this piece. With devices, practical impact usually shows up in battery life, heat, stability, and long-term usability rather than in a few flashy headline numbers. The readers who should care most are the ones planning to replace a device, buy an accessory, or upgrade a work setup in the next few months.

The details worth keeping

Nilay Patel’s Decoder podcast often features high-profile guests in the automotive world, and Patel always asks about CarPlay. On the device side, the useful angle is whether a technical change actually alters feel, lifespan, or upgrade cost in real use. The readers who should care most are the ones planning to replace a device, buy an accessory, or upgrade a work setup in the next few months. The next step is to see whether the current signals harden into a durable change or fade as a short-lived experiment.

Why this matters most

The signal is strong enough to deserve attention, but it still needs to be read as something developing rather than fully settled. With 1 source layers on the table, the part worth reading most closely is where firm facts meet the market's early reaction. Last fall, for example, Rivian’s CEO RJ Scaringe joined the show and said that “customers will appreciate” the lack of CarPlay eventually.

What to watch next

The next readout is price, device coverage, and whether the change feels real once the hardware reaches users. Patrick Tech Media will keep checking rollout speed, user reaction, and how 9to5Mac update the next pieces. From 1 early signals, the piece keeps 1 references that are useful for locking the main details in place. That is why the useful reading move is not to stop at the headline, but to compare the promise, the workflow change, and the likely cost before deciding anything.

Source notes