What's all the fuss about CarPlay and Android Auto?
Car OEMs will continue to develop embedded IVI apps on their own. But they can't ignore the growing appetite among consumers to use smartphone apps in their cars.
Google and Apple both have a vested interest in promoting in-car apps natively written to their respective operating systems. The fastest solution is to implement them through middleware. Car OEMs and Tier 1s could leverage middleware like Android Auto and CarPlay to integrate smartphone apps in their cars. Carmakers are reportedly developing systems that will launch both Android Auto and CarPlay, while their own car-centric embedded IVI apps continue to run on QNX, Microsoft, or GENIVI platforms.
The last thing app developers want to do is to modify and tailor their products for each automotive OEM's car model. Again, the key is middleware that enables smartphone integrations.
However, that's not to say that Google has no ambitions for the dashboard. Juliussen suspects it will eventually compete there. But it hasn't put anything tangible on the table yet.
Strategy Analytics' Lanctot said that, at Google I/O a few weeks ago, Google didn't want to talk about "Android's challenges regarding boot time and power consumption, two significant deficits of great concern to automakers once Google decides to bring Android into the dashboard and not merely enable smartphone integration."
Furthermore, "Google also glossed over the fact that the voice recognition solution on offer is hosted and therefore dependent on a wireless connection," he said. "In fact, this same limitation is shared by CarPlay."