This is not equivalent. The key distinction in the device from OP's post is that it actually connects to the OBD port in your car, giving you a direct connection the cars systems. The one you linked does not seem to do that at all.
Anyone know how Android Auto (and Car Play) compare to the functionality exposed through the OBD port?
I have Android Auto and love it for navigation/music, but it is missing any car specific controls, eg. climate controls, reporting speed, maintenance, etc. I have to exit out of Android Auto and into Sync to access some specific functionality only available through the Sync touchscreen.
Is this just a case of the manufacturer needing to provide the right app, or is that information not available to third party apps running in those environments?
They sandbox many of the different systems. Carmakers won't cede deeper control to Android Auto or Carplay because they want to hold on to being the main user interface. There's also safety, security, and data-sharing issues at play.
Fair enough, I would be OK with having to run a Ford app through Android Auto to access that functionality on a Ford.
I just want the best of both worlds .. trying to hold onto being the main user interface feels short sighted. I'm not going to NOT buy your vehicle because I can use Android Auto vs your custom UI, so having both available shouldn't be a negative to the manufacturer.
Given how the most sought-after car today literally receives driving instructions through an OTA update, I've got a feeling we've all collectively decided we're ok with the dangers this brings, even if we didn't actually take part in that discussion :-/
Driving instructions via OTA are fine as long as your in car entertainment system is separate from the cars engine control et al. Which is the air gapped point I was making.