Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Unfortunately my 2016 vehicle only has mirrorlink v1.1+. Which unlike mirrorlink 1.0 doesn't actually mirror your phone, instead it is a proprietary app ecosystem with ten low quality paid for apps, even assuming any smartphone still supported mirrolink (which almost none do).

Both versions of the protocol stream apps rendered by the phone. v1.1 allows to create third party applications for it. Previously apps could be only provided by phone vendor. ML was never supposed to stream the screen of the phone constantly due to potential driver distraction. The devices that did this were probably uncertified and/or buggy.

> Toyota for example is refusing to do AA/Carplay and is starting yet another "standard" called SmartDeviceLink.

Well they do have a plenty of reason to not like AA/Carplay. Both give total control of head unit experience to Apple or Google. Which is a risky decision when you are dreaming about gradually moving from selling a product to providing related services.



> Both give total control of head unit experience to Apple or Google.

Which is to say they give total control to the device the user already has and uses everywhere else, so that they get a consistent experience. Anything the auto vendor provides will never be able to match that.


Yes, obviously. They both make head unit more appealing to the user. The cost for car vendors here is that they are suddenly dependent on a third party if they want to push any features on top of that experience.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: