Isn't the car side of CarPlay and AndroidAuto not much more than providing a video player and sending the screen touches back to the phone? I haven’t used either much, but I don’t think it interacts with much more than the touch screen and audio. The in-house code should be minimal.
Currently, yes. But Android Automotive and future CarPlay run on the car‘s hardware and get access to the CAN or an abstraction over the CAN.
Those still supersede only the user-facing code (dashboard, buttons, entertainment), and all the other low level code still needs to be written: engine control unit, ABS/ECS etc, airbags, battery management, indicators, windows, heating, wipers, drive by wire, etc - and let’s not forget all the glue code (essentially an OS of its own) to tie all those components together, OTA orchestration, etc.
Car metrics are not “can data”. Even if they arrive over CAN at some point. You are so far removed from “CAN” at that point it isn’t worth mentioning and misleading to do so.
