Rivian’s CarPlay refusal is really a fight over who controls the EV screen

Rivian’s argument with CarPlay is not another minor episode in the war over car screens. In an interview with The Verge, Wassym Bensaid, Rivian’s chief software officer, speaks from a position that goes beyond apps on a dashboard. He is also co-CEO of RV Tech, the software joint venture with Volkswagen that was launched with a nearly $6 billion Volkswagen investment.

That changes the weight of his message. When Rivian says drivers do not need CarPlay as the dominant layer in the car, it is not merely defending its own interface design. It is arguing that software in an electric vehicle is no longer an add-on to the instrument panel. It is the operating layer for navigation, climate, charging, assistants, updates and service diagnostics. If that layer is handed to the phone, part of the driver relationship goes with it.

Rivian is therefore pushing a vertically integrated interface. The company wants drivers to use a system that understands battery state, vehicle behavior, route planning and the functions that must remain available without jumping between car software and a mirrored phone environment. Apple’s CarPlay has a powerful advantage: people know how to use it instantly. Rivian’s counterargument is that familiar is not always enough when the vehicle becomes a software-defined machine.

The second piece is physical controls. Bensaid’s position, as framed by the interview topic, is not simply “put everything on a screen.” The real question is which controls must be immediate, which can be automated and which become better when the system understands driving context. That is a narrow line. The auto industry has already learned that a minimalist cockpit can look clean in a showroom and still become frustrating, or worse, when a driver has to hunt for a basic function on a rough road.

That is why Rivian’s case is more interesting than a routine UI dispute. Through its own vehicles and through RV Tech, the company is trying to prove that software can become a shared industrial platform. Volkswagen is not buying a slightly nicer infotainment menu. Through its partnership with Rivian, it is looking for an architecture that can repeat across vehicles, update faster and depend less on older internal layers of automotive electronics.

The risk is obvious. If an automaker rejects CarPlay, it has to offer users something better than principled control. Navigation must be excellent, the voice or AI assistant must be reliable, media must work without friction and basic functions must be faster than the driver’s nostalgia for buttons. Otherwise, the software strategy starts to look like a walled garden at the exact moment the driver only wants a familiar tool.

Bensaid’s message should therefore be read as an industry signal: Rivian wants the car to be its own digital platform, not an iPhone peripheral. That is ambitious, but brutally measurable. If the interface is smarter, faster and safer, the decision will look strategic. If it is not, every missing button and every absence of CarPlay will become a daily reminder that control by itself is not user value.