by acroyear » Wed Mar 21, 2018 11:44 pm
The requirements for an auto app are VERY particular, in order to ensure safety (as in, NOT encouraging the user spends a lot of time staring at the screen).
It would need to be audio only, no lyrics, no last.fm album/artist info, and as simple an interface as is feasible (so I would think only playlists and maybe albums, no folder or artist-album browsing). There may be certain behavior requirements at certain speeds via auto-only APIs that need to be complied with for legal reasons. Or not. I'd have to reread all those details.
If I had one to test against, I'd consider porting SubFire* to it, packaging it up through adobe's phonegap build.
But there we are - it will require work, and not any app can be deployed on it, just like not any app can be deployed (without side-loading) on an Android TV system.
for now, i'd stick to the bluetooth audio and not worry about it.
* my "2.0" of SubFire is being written up as a framework for making different apps, so mobile, phone, tv, browser extension, can all be written from the same architecture but better handle their different UI needs. It would be easy to make an auto version (maybe make that the default tablet version) that complies with Google Play Store's rules, but that would be a lower priority over the other platforms that I have to use first.
--
Joe Shelby
http://subfiresuite.com/
http://subfireplayer.net/