| I think CarPlay is evidence of failure. My aim is device independence. In the old days, to print I had to hook up my printer to a computer. To print from a computer on the network, I needed a print server. I had to administer that. Now the printer itself hooks to the network, which is far superior. I have an older thermostat which allows me to program vacations directly on the unit. This is superior to the newer thermostat, with which I must use my phone for this. My dishwasher requires me to use my phone to do a delayed start. This is inferior to what it replaced, which was a model that allowed me to do delayed start from the panel on the dishwasher. Devices should work on their own. So it’s a failure if the first thing I need to do in the car is tether it to a phone. The car needs nav, it needs radio, etc. It would be better if it has those things built in. I understand the complaint in this thread, which is that the carmakers are bad at this. I don’t own a Tesla or Rivian, but some folks are saying their interfaces are good. Those carmakers have the right idea. I begrudgingly accept CarPlay. I don’t like it. In this era when computing is as cheap as it is and where even a TV can hook directly to network to play back content, it makes no sense that the solution on a $40,000 car is to plug it in to a phone. |
In this regard CarPlay is evidence of success - a sufficiently interoperable car that allows users to bring their own context and ecosystems.
CarPlay is only evidence of failure if your expectation is that the car should provide a comparable ecosystem to Android or iOS - one that must also somehow follow you in your pocket when you leave the car.