Michael O’Shea:

The first is the possibility of Android phones connecting with vehicle head units. However, it is unclear whether these head units will be limited to Android units, which seems unlikely. The second scenario is Android running directly on the head unit itself.
 Breaking down scenario No. 1
 In the first scenario, it seems the OAA will address approaches to connecting phones with cars for “brought-in” style solutions, similar to what the Connected Car Consortium was doing with MirrorLink, a solution for connecting smartphones and a vehicle’s infotainment system. If this is the case, the CCC may be facing some repercussions. MirrorLink was not supported by Apple, and has also had limited support by the Android phone manufacturers. As such, it seems unlikely that the handset manufacturers would support MirrorLink alongside a Google-endorsed OAA solution. So, unless the CCC’s work is incorporated into the OAA, MirrorLink is at risk.
 Additionally, it is unlikely that the OAA’s approach will be endorsed by Apple, which will remain focused on its own iOS in the Car initiative. This means that car manufacturers will likely have to work with two independent approaches if they wish to align with both Google and Apple. Not to mention working with other auto manufacturers, like Ford and GM, which are implementing their own smartphone connectivity solutions.