7 Comments

Summary:

Android in the automobile would spur two things the connected car sorely lacks: A unified app platform in the infotainment system and a vibrant developer community.

Why Google's Android Could Rule Connected Cars

As we expected, CES moonlighted this year as the Las Vegas Auto Show. We saw the unveiling of several 4G cars and a fair share of autonomous driving technology. We saw smartphone chipmakers vie to become auto-parts suppliers, and even a handful of new connected car apps.

But the thing we all wanted to see didn’t show up in any CES booth or drive out onto any casino-hotel stage. We never got a glimpse of Google’s new Android-powered dashboard. Of all the connected car news that came out of CES, an automotive version of Android has the most chance of shaking up the still nascent connected car market by spurring vibrant developer community.

Image (1) googlecar.jpg for post 76055

Google announced the Open Automotive Alliance at CES on Monday, revealing an impressive array of partners from General Motors, Audi, Honda and Hyundai to Nvidia. But after that press release hit the wires, it was silent. There was no Android infotainment system to be seen, concept or otherwise.

You might say it’s too early to expect a technology that was only just announced. But the Alliance has promised we’ll see its first wares in production cars this year. Since 2015 model year cars – including Audi’s new revamped 4G Audi A3 – this spring, Android cars should be revving their engines just around the corner.

Google is probably waiting for one of its own events to share the details on Android’s new automotive ambitions, but in the meantime we can speculate on what its deeper dive into the automotive industry means. I think it’s safe to say this is very a big deal.

Cadillac CUE

Cadillac CUE

Why? It’s not just because Google is Google, and everything it touches magically becomes significant. It’s because Google has the potential to unify — at least in part — one of the most schizophrenic aspects of the auto industry: the infotainment system.

Automakers by nature are very proprietary creatures. As Ford Motor Company Executive Chairman Bill Ford recently acknowledged in an interview with Gigaom, automakers like building things themselves, and what they don’t build they outsource to a few trusted suppliers. They design their own powertrains and transmission and fret over the upholstery on their seats. That Waldenesque philosophy led them, for better or worse — though probably worse — design their own infotainment systems.

I’ll pause here to point out that there are a lot of very familiar mobile software names in the dashboard: Microsoft Windows 8, BlackBerry’s QNX and Nokia’s Here. But these aren’t the same OSes most of us find in our phones. Their software forms the underlying code for what are very distinct infotainment systems, none of which can claim interoperability with one another.

Scattered puzzle pieces next to solved fragment

In many cases there isn’t any compatibility between cars made by the same automaker. Not only will software designed for Cadillac’s CUE system not work in the MyLink system of sister GM line Chevrolet, there’s often no compatibility between MyLink systems in different models of Chevys.

You thought the smartphone space was fragmented; well, there are a dozen major automakers, many with multiple different infotainment systems across different models. As you can imagine this a huge obstacle for an app developer. Some like Pandora have been willing to tackle it, but as a radio streaming app it has much more incentive than most to ingrain itself into the dashboard.

For the typical app developer it means joining a dozen different developer programs, each of which require separate negotiations with the automaker, and there’s no guarantee that your app will ever make into a car, given the tight restrictions automakers place on their developers and the snail-like pace at which they introduce software updates. And let’s face it, compared to smartphones, a miniscule number of connected cars are introduced every year. Developing for the vehicle market seem about as attractive as developing for BlackBerry these days.

connected car logoGoogle can help solve those problems. I say that not just because it already has the experience of building an open consumer electronics development ecosystem, but also because it’s becoming painfully obvious that no one in the auto industry can.

The only attempt at unifying the connected car OS has come from Ford and Microsoft, which have open-sourced the Sync AppLink platform. So far there have been no takers, and I doubt there ever will be. Ford, after all, is a big competitor to all of the other automakers. This story has had the same unhappy ending in the smartphone industry. Nokia and Palm  have tried licensing their software to competitors and got nowhere.

That’s not to say that automakers won’t feel threatened. Google may be neutral, but by inviting Android into the car, they’ll face the problems in differentiating their products as smartphone makers that have embraced Android. But luckily for automakers there are a lot more ways to make your car unique than an infotainment system.

  1. So are we going to have new apps for cars?

    Share
    1. Or the other way round ? :-)

      Share
      1. Yes that is true of course. New applications with cars and for these new application you will need new tools running in the car Android. Like a new McD app which lets you select your burger while near one outlet. And once you are near the counter the burger is ready for you :-)

        Share
  2. Interesting that Apple’s iOS in the Car is not even mentioned. It appears that there are numerous competing approaches that are coming. Manufacturer (or brand) specific platforms. Treating the built-in component as nothing more than a dumb monitor, with all applications running on the personal device (smartphone or tablet). Or looking to converge everything to a single platform.

    Share
    1. Kevin Fitchard Friday, January 10, 2014

      Hi Focher,

      Good point. Detroit does seem to caught up in an internal debate whether it wants to make the brains of the app platform the smartphone (thus future-proofing them) or in the dash itself. I’ve written a bit on this before, if interested:

      http://gigaom.com/2012/06/11/ford-versus-apple-siri-versus-sync-over-connected-car/

      As for why I didn’t mention Apple is because I don’t think it is really trying to create an iOS cars. It’s Eyes Free features is a way of connecting user interfaces, rather than create a new platform for the vehicle. But to your point that make be what drivers want: A way to easily control and access their smartphone while driving. That we actually need a separate “connected car” might just be a conceit.

      Share
      1. matthew nelson Friday, January 17, 2014

        Hi Kevin – I’m not sure Google or apple hold the key’s given that their natural incentive to destroy one another will always block the cross-platform experience necessary in the car.

        So we set out to redesign the connected car experience: http://youilabs.com/blog/the_hive.html

        Then built it on our engine on iOS, Android and Blackberry.

        Share
  3. Marcos_El_Malo Monday, January 13, 2014

    I’m looking forward to seeing the first automobile botnet.

    Share

Comments have been disabled for this post