I've often wondered, while using the somewhat substandard media navigation of my bluetooth enabled car stereo which has a touch screen, why there isn't some standard for specifying a very simple, somewhat static visual interface for bluetooth touchscreens (or screens with a set number of external buttons). A very constrained HTML, perhaps, that apps could choose to supply to provide better control through external interfaces.
For example, let Android or iOS supply an interface to view my contacts based on the reported dimensions of the screen and capabilities. Let Pocket Casts present a list of podcasts to choose from. Let Pandora show my thumbs up/down stored for the song, and register my new preference. If I'm at my desk, and I'm using one of these apps, there's no reason a simple app that provides the same interface couldn't provide me info about the connected phone through bluetooth, to let me know who is calling me, let me stream my podcasts through my desktop speakers, etc.
Does this exist, and I just don't know about it (or it isn't implemented by anyone)?
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.
Thanks 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.
For example, let Android or iOS supply an interface to view my contacts based on the reported dimensions of the screen and capabilities. Let Pocket Casts present a list of podcasts to choose from. Let Pandora show my thumbs up/down stored for the song, and register my new preference. If I'm at my desk, and I'm using one of these apps, there's no reason a simple app that provides the same interface couldn't provide me info about the connected phone through bluetooth, to let me know who is calling me, let me stream my podcasts through my desktop speakers, etc.
Does this exist, and I just don't know about it (or it isn't implemented by anyone)?