3 ms·
I think that is more or less exactly the idea behind Android Auto and CarPlay for iOS. The problem is that many manufacturers still don't support it, and custom
by eric_the_read 10y ago
I think that is more or less exactly the idea behind Android Auto and CarPlay for iOS. The problem is that many manufacturers still don't support it, and customer demand isn't high enough (yet) to force them to. I went ahead and bought the Taco, even though it didn't have Android Auto, because it was otherwise a good truck, and the bluetooth support was Good Enough™. Until enough people don't behave like me, support is likely to lag.
- kbenson 10y agoThanks for the heads up. Interestingly, Android has the Desktop Head Unit for displaying Android Auto stuff on the desktop, but it's presented as a developer debugging tool. I'm not sure, but it looks like the actual car head unit is supposed to be using android, which I sort of understand from their point of view of wanting a good implementation not left up to the car manufacturers (and their history of poor software quality and updating), and also to increase marketshare. I imagine CarPlay is similar. That's a shame, because I think they missed out on a real opportunity to attempt to define a standard that could have been useful for more than a closed ecosystem, and more than just cars. I'm sure it would be less featureful than what they came up with, but I think that would have been justified with the expanded scope. Imagine, if you will, if your phone could just as easily export controls to some virtual/augmented reality device you are wearing, without having to run the Android Auto operating system on that device. Such a shame.