Linked by Thom Holwerda on Tue 4th Mar 2014 16:47 UTC

Connectivity to smartphones and other mobile devices is a key strength of QNX Software Systems’ platform for car infotainment systems, and many automakers and tier one automotive suppliers use our platform to implement smartphone/head-unit integration in their vehicles. We have a long-standing partnership with Apple to ensure high-quality connectivity with their devices, and this partnership extends to support for Apple CarPlay.

Yes, Apple CarPlay runs on QNX. Makes sense - I'm guessing (?) in-car software needs a lot of certification and testing, which QNX' in-car platforms all already have.

Permalink for comment 583901
To read all comments associated with this story, please click here.
by jared_wilkes on Tue 4th Mar 2014 20:08 UTC
Member since:

It seems like people are misunderstanding CarPlay (the rename helps). Carplay is more or less AirPlay that is streaming a modified UI designed for voice, limited touch control and any other in-car UI methods (steering wheel controls) and output (stereo speakers, hands-free phone system). It isn't using or built on QNX, per se. The vast majority of functionality is exclusively occurring on the iOS device connected to the car; the only functionality being provided by the local in-car system is streaming to the dashboard console and relaying input and output. It can theoretically work with any in-car app platform as long as Apple works with the in-car app platform to support CarPlay streaming to dashboard consoles and input/output from whatever interface the car affords. All of the prototypes shown so far support their own similar in-car apps/nav/entertainment or even other in-car systems... saying CarPlay is built on QNX is like saying that anything that supports MTP is built on Windows (not the best analogy, but the point should be clear).

Unlike QNX, SYNC, (and I'm unsure about Google's plans but believe they're on a similar path), Apple is attempting to leverage existing functionality of in-car systems to use iOS devices as the primary, familiar data/app source rather than building a specific in-car OS that needs to be adapted by all car manufacturers — all they need is compatibility. Or put another way: BB, Google, and Microsoft are trying to build a smartphone into the car; Apple conversely is presuming that a car will have some system that can talk to an iOS device, and the user will prefer to use the iOS device they have on hand rather than the in-built car system.

There are interesting pros and cons to this difference in strategy.

Edited 2014-03-04 20:25 UTC

Reply Score: 6