QNX at SAE Convergence: Cool screens and a mobile theme

Let's start with the theme. And no, I don't mean the kind of theme you download onto your smartphone. I'm referring instead to the main theme of a press release that QNX issued yesterday at SAE Convergence.

First, some context. If you're an automaker, you have little choice: you have to offer infotainment systems that can keep pace with the crazy fast advances in mobile devices. You also need to keep your systems fresh with apps, features, and content that consumers will expect long after they've bought your car. And to do that, you'll need to tap into the skills and products of the mobile app community. Otherwise, that ultra-cool infotainment system you ship today will rapidly transform itself into the 8-track of tomorrow. Goodbye, brand image.

The QNX CAR 2 application platform, with its solid grounding in HTML5, is designed to help infotainment-system designers conquer these (admittedly difficult) challenges. HTML5, after all, has become the lingua franca of the mobile apps market and offers an ideal bridge between the mobile and automotive worlds.

One thing was missing, though — a toolkit that would make it easy for mobile app developers to target the QNX CAR 2 platform. Yesterday, at SAE Convergence, QNX announced a new HTML5 SDK designed to do just that.

An SDK for (auto)mobile developers
The HTML5 SDK for the QNX CAR 2 platform is an extension of the open source BlackBerry WebWorks framework, specially optimized for automotive environments. It allows developers to write, test, and package feature-rich automotive apps based on HTML5, CSS3, JavaScript, and other open standards. It also provides the missing glue between high-level apps and the car, through specialized APIs that provide access to automotive devices and hardware.

Runtime emulator for quicker testing and debugging
This is where the first of the screens comes in. To speed development, the HTML5 SDK provides an emulator that lets developers quickly see how their apps would look and function in a car. Developers can use the emulator to perform JavaScript debugging, HTML DOM inspection, automated testing, and screen-resolution emulation, all from the convenience of a web browser. They can even make changes to their apps and view the results without having to recompile. The simulator is based on the open source BlackBerry Ripple emulator, used by thousands of mobile developers.

For instance, in this screen capture, the emulator is being used to test the virtual mechanic provided by the QNX CAR 2 platform:

Click to magnify

Here's another example, where the emulator is being used to test an audio control application. If you were running this emulator session, you could manipulate the app's onscreen controls to adjust volume, bass, treble, fade, and balance; you could also observe the changes to the underlying data values in the right-hand panel. And you could work the other way: by changing the controls on the right, you could observe changes to the app.

Click to magnify.

QNX also plans to create a virtual marketplace that will allow developers to make their QNX CAR 2 applications available to automakers. The marketplace will provide common ground for app developers and automakers to work together, and will allow automakers to preview the applications that best fit their brands and satisfy their customers. The marketplace is expected to go live when the HTML5 SDK is released.

By the way, my colleague Kerry Johnson provides an interesting back story to the SDK, including the kinds of APIs it provides. You can read his post here. You can also find more images of the emulator on the QNX Flickr page.

3D navigation from Elektrobit
Now for the other screens. Besides announcing the SDK, QNX has brought its QNX reference vehicle, a modded Jeep Wrangler, to the SAE show floor. As always, the Jeep is running the QNX CAR 2 platform. But this time, the Jeep also includes a cool 3D navigation app from automotive software vendor Elektrobit. Here are two examples of the Elektrobit app:

That's it for now. But before you go, be sure to follow @QNX_Auto on Twitter, where we are covering the latest developments, both QNX and non-QNX, from SAE Convergence.

No comments: