Thursday, September 29, 2011

Connected Car Consortium (CCC) and MirrorLink

I'm in Chicago right now, blogging from my PlayBook.  I'll have a lot to say after I compose my thoughts, but with most of the day behind me, I'll just share some of the key themes I've sussed out of the days events.

  • Mobile makers (Nokia, LGE, and Samsung, at least) see MirrorLink as the way to get apps into the car
  • Nokia sees MirrorLink as a way to become relevant again
  • OEMs see the upside for new opportunities to connect with customers, but seem to somewhat be in denial that this will also decimate their existing revenue streams
  • MirrorLink has come a long way, but still has a ways to go in certification and safety concerns
And although there have been some great presentations (best one was the simplest PPT), I have to give my vote for the best slide so far:

I'll be back with more...


  1. Andy, I stumbled on your blog while I was searching for info about my new Toyota yaris hsd infotainment system. it seems to be built by Harman and based on qnx car. being a curious person myself, I began searching about programming the whole thing. I subscribed to foundry 27, but I've found no info regarding the qnx car platform. is that platform a closed one? is it possible for an hobbyist programmer to develop for it, or is it limited to business developers?

  2. Hi Alessandro. Right now, QNX CAR is a closed platform, as it's targeted for car companies to build their products, not for hobbists. However, we are working on opening up an automotive ecosystem for app developers, by expanding the RIM WebWorks SDK to be able to target HTML5 for the car. This is a few months out, but you can get a preview by watching the webinar I held last week:

  3. that's good news. opening up the platform is essential to wide adoption. just look at android. what would it be if it was a closed platform? a blackberry you may answer me :-)

  4. I certainly get your humour, but cars are a very different space from mobile. The same factors aren't really in play, nor should they be. I want my car to be reliable, virus-free, and not hackable, and so do car makers, the government, and general public. Part of the solution is providing a sandboxed environment so downloaded content doesn't affect the rest of the system. But as a car maker, you also have to worry about driver distraction--not every app is reasonable to use when you're flying down the highway. Making an open platform in the car is the automaker's call--not ours--because laywers go after the car companies if someone is playing Angry Birds when they crash. This is all the stuff I talk about in my webinar (another shameless plug to go watch it :-)

  5. thank you for your kind answers. I'm looking forward for the sdk release. I can't watch the webinar right now cause I'm away with only my mobile. I'll do as soon as I get back home.