WIRED Autopia slips into driver's seat of QNX reference vehicle

Chances are, you've seen pictures of the new QNX reference vehicle. You may have even seen the "making of" video that QNX released a few days ago. But have you seen any video of the vehicle in action?

If not, check out this vid by Doug Newcomb of WIRED Autopia. Last week, at Telematics Detroit, Doug met up with Andrew Poliak of QNX for a tour of the vehicle and its various features, including a re-skinnable UI and voice-controlled Facebook integration. The camera was rolling, and here's what it caught:


 

HTML5 brings new buzz to infotainment system development

QNX to unveil QNX CAR 2 platform on Freescale i.MX 6 at FTF Americas — a guest post from Paul Sykes of Freescale

If you’ve visited the QNX website recently or attended the Telematics Detroit conference last week, then you’ve surely noticed that HTML5 is getting a lot of attention in automotive these days. The buzz around HTML5 focuses on two areas: as an application development and delivery framework, and as an HMI framework. In discussions with many industry participants, my impression is that the application framework part is generally accepted, while the HMI framework part still isn’t well understood.

I don’t intend to discuss these HTML5 aspects in detail. There are experts within the ecosystem that can do a much better job than me. But I will say that Freescale applications processors will offer the processing and graphics performance to run the desired applications and bring the HMI to life with stunning graphics.

Next week, Freescale will host the annual FTF Americas event in San Antonio, TX. We are very excited about the first public unveiling of the QNX CAR 2 application platform on i.MX 6. Since QNX CAR 2 is based on HTML5, it is particularly fitting to mention in this blog. For those with an interest in understanding more about HTML5 for infotainment systems, QNX and many other ecosystem partners will be on hand at FTF to discuss their thoughts and plans.

Paul Sykes is a member of Freescale’s driver information systems team.
 

The making of the QNX reference vehicle: Jeep Wrangler

Guest post from Nicole Forget of QNX Software Systems

Nicole Forget

Just one week ago, our new reference vehicle was revealed at Telematics Detroit 2012. The Jeep Wrangler features QNX’s digital instrument cluster, which is totally re-skinnable. In fact, the entire user interface of the head unit, which was created using HTML5, can also be re-skinned. The head unit supports loads of functions, too, including the virtual mechanic, which are outlined in an earlier post.

The following video gives you some insight into the hard work that was put into the making of the reference vehicle. Check it out!


 

Moving beyond the browser: HTML5 as an automotive app environment

If you’ve already visited this blog, you’ll know that we are bullish on HTML5 as a way to implement infotainment system HMIs. Not surprisingly, I’ve spent a fair amount of time searching the Web for facts and opinions on using HTML5 in the car, to see how this idea is catching on.

Overall, people see numerous benefits, such as the ability to leverage mobile app development to keep pace with the consumer demands, the availability of a large pool of knowledgeable developers, and the attractiveness of a truly open specification supported by many possible vendors.

But when it comes to the challenges of making HTML5 a reality in the car, I found a common thread of questions, mostly rooted in the erroneous belief that an HTML5 application environment is “just a browser.” Everyone is familiar with the concept of a browser, so it’s easy to see why people take this point of view.

So what are the key differences between a browser and an HTML5 application environment? Here’s my quick view.

The experience
Everyone is familiar with the browser experience. You navigate to a web site through bookmarks, a search engine, or direct entry of a URL. The browser implements a user interface (aka the chrome) around a rendering engine and provides bookmarks, URL entry, back and forward, scrolling and panning, and other familiar features.

An automotive HMI based on HTML5 provides a different experience — just look at the accompanying screen shots and decide for yourself if they look like a browser. In fact, the user experience of an HTML5-based HMI is similar to that of any other purpose-built HMI. It can consist of a main screen, window management, navigation controls, and other typical user interface widgets.


A radio tuner and a media player from the QNX CAR 2 application platform. Both apps are based on HTML5, but beyond that, they neither act nor look like a web browser.

A system that uses an HTML5-based HMI can include:

• core applications that look and act like native applications
   
• add-on (downloaded and installed) applications that have controlled interfaces to the underlying hardware
   
• “web link” applications that simply link to a cloud-hosted application that can be downloaded on demand and cached

The web link approach makes it easy to update applications: just update the server and the remote client systems will automatically pull the application when needed.

Local resources
Web browsers pull text, images, and other content from the web and render it on the user’s machine. The process of loading this remote content accounts for much of the user’s wait time. This paradigm changes with a local HTML5 application environment — because resources can exist locally, images and other components can load much more quickly.

What’s more, screens and user interfaces can be designed to fit the platform’s display characteristics. There is no need for panning and scrolling, and only limited need for zooming. Resources such as RAM can be optimized for this experience.

Security and sandboxing
Browsers load content and executable JavaScript code dynamically. This really is the power of the web technologies. The problem is, dynamically loaded code represents a threat to an embedded platform.

Browsers are designed to be sandboxed. By default, JavaScript code can execute only in the context of a browser engine, and cannot access the underlying operating system primitives and hardware. This approach changes in an HTML5 application environment. To give JavaScript code the ability to behave like a native application, the environment needs interfaces to the underlying OS through to the hardware. Plugins are used to implement these HTML5-to-OS interfaces.

Nonetheless, access to the underlying platform must be carefully controlled. Hence, a security scheme forms a critical component of the HTML5 application environment.

Application packaging
The app experience has become familiar to anyone who owns a smartphone or tablet. An HTML5 application environment in the car can also support this kind of experience: developers create and sign application packages, and users can download those packages from an application store. In an automotive context, authenticity of the applications and control over what they can or cannot do is critical. Again, a security model that enforces this forms a key part of the HTML5 application environment.

So, how should you think of an HTML5 application environment?
From my perspective, an HTML5 environment is like any other traditional HMI toolkit, but with much more flexibility and with inherent support for connected applications. In an HTML5 application environment, you can find technologies similar to those of any proprietary toolkit, including:

• a rendering engine (HTML5 rendering engine)
• a set of content authoring and packaging tools
• layout specifications (HTML5 and CSS3)
• a programming language (JavaScript)
• an underlying data model (DOM)

The difference is, these components are developed with a web experience in mind. This, to me, is the most significant benefit: the web platform is open, scalable, and well understood by countless developers.

A reference vehicle by any other name

As you know, we’ve been running a contest about the make of our new reference vehicle. We said the first 25 people that guessed it right before the opening of Telematics Detroit would receive a $25 gift card to Starbucks.

Man, do our followers know their cars!

We had 17 correct guesses of a Jeep Wrangler. No one got the exact model right – Jeep Wrangler Sahara – but we think this ride is pretty sweet no matter what it’s called. Congrats to the following winners – we’ll be in touch soon.

@RecioC @pete0t2 @rpaskowitz @ke_meth @gustavitt @charsoxer @BB_Ignites @NorthsideB @bravobby

@pb_jamm @Gustavar @KrisLoHomes @BBbrodyBB Lazarus Long @swim_ski_ride @jpelliott10 @BerryInformed

If you’re at TU Detroit, one demo you won’t want to miss is on mobile connectivity. WARNING: You may leave with one question unanswered: If you could post to Facebook while in your car using simple voice commands, what would you share?

Find out more about the new QNX reference vehicle. And stay tuned for future contests.

Full disclosure: QNX releases first complete photos of new reference vehicle

"Any customer can have a car painted any color... so long as it is black."

We've come a long way since 1909, when Henry Ford penned this now-famous sentence. Not only can modern consumers pick the colors and features they want in a vehicle, but, in many cases, they can order them online. Getting the car you want, with the options you want, has never been easier.

Still, most forms of personalization are baked in. Once you order a car in, say, Barcelona Red (the color of my new Venza), it's hard to reverse the decision. But imagine the day when you can sit behind the wheel and watch your car's instrument cluster automatically reconfigure itself according to your personal preferences. And imagine if the cluster could do the same for everyone else who uses the car.

That's the kind of future QNX is working to make happen.

But you know what? I'm getting ahead of myself. I promised pictures of the new QNX reference vehicle, so let's look at them — especially since they offer tantalizing examples of what I was just talking about. :-)

The vehicle
Up to now, we've only released teaser images of the reference vehicle, with just enough detail to get people guessing as to what it might be. But enough with the mystery. Here's a full-on shot of the vehicle — a Jeep Wrangler Sahara — in all its off-road glory:


Yes, it's a Jeep

By the way, if you were one of the first 25 people in Canada or the US to guess it was a Jeep during our recent teaser campaign, congratulations! We'll identify the winners shortly.

The cluster
Once you get behind the wheel, the first thing you'll see is the digital instrument cluster. Let's zoom in so you can get a good look:



The cluster is implemented entirely in software and can reconfigure itself on the fly to display various types of information. Better yet, you can re-skin the cluster at the tap of a touchscreen button, like so:



As you can see, the cluster communicates with the head unit's navigation system to display turn-by-turn directions. Nice touch.

The head unit
Now look to your right, and you'll see the head unit. It supports a whack of functions (note my deft use of technical language), including one-touch pairing with Bluetooth smartphones, hybrid navigation, text-to-speech, natural speech recognition, streaming Internet radio, weather reporting, parking search, and too many other things to mention here.

In this photo, the head unit displays one of my favorite applications, the virtual mechanic. Intrigued? Check out my description of an early version of this app.



You know what else is cool? The unit's media player can post Facebook updates that list the song currently playing — but only when you tell it to, using voice commands. (Personal control over technology. I like that.) To view these updates later today and tomorrow while the Jeep is at Telematics Detroit, check out the QNX Facebook page.

Here's another photo of the head unit, showing its app tray:



The radio
What car would be complete without a radio? Mind you, in this case, "radio" includes support for streaming Internet radio from Pandora and TuneIn. And keeping in tune with the personalized listening experience these services offer you, the head unit's radio gives you a choice of skins:





In fact, almost every aspect of the head unit can be easily re-skinned. What's more, the underlying code remains the same: only the user interface, created in HTML5, changes from one skin to another. Which means automotive developers can create a single code base and re-use it across multiple vehicle lines. Doing more with less — what could be bad?

That's all I have for now, but before you go, check out the two press releases QNX issued this morning on the Jeep's personalization and Facebook features. Also, check out the QNX Flickr page for even more photos of the Jeep.
 

It pays to uncover... the new QNX reference vehicle

As you know, we are gearing up for Telematics Detroit next week and bringing our brand new reference vehicle to the show. I would tell you what kind of car it is, but that would take away all the fun! We posted some pictures earlier but we wanted to give you a few more to see if you can correctly guess the brand name and model.

And to make it interesting, if you’re right, we’ll give you a $25 gift certificate to Starbucks! We will award gift cards to the first 25 people who respond with the correct answer and currently reside in the United States or Canada.

Earlier votes don’t count; you have to vote on Twitter, starting today. Simply follow our handle at @QNX_Auto and tweet @QNX_Auto with your guess, and you’ll be entered. And stay tuned on Twitter, where we’ll post more pictures. Don’t have Twitter? You can vote here, but you must include your email. And in order to play fair, QNX employees aren't eligible - shucks.

Check out the pictures below and get your votes in early. The car will be unveiled, and winners notified, on June 6. Good luck!

Report from CTIA Wireless: Apps in the Car

You wouldn’t think that CTIA Wireless, a mobile show, would be a good venue for a car guy. But automotive journalist Doug Newcomb put together a set of panels that managed to attract everyone from the automotive industry who attended the show.

I met a good number of friends from a variety of automakers, tier one suppliers, and hardware and software vendors. I also had the distinct pleasure of participating in one of Doug's panels, which was moderated by Damon Lavrinc of WIRED.

The topic was the future of apps in the car, and it generated a spirited discussion. Panel participants included Geoff Snyder from Pandora, Michelle Avary from Toyota, Henry Bzeih from Kia, and Scott Burnell from Ford — all experts on the topic.

Andy speaking on the

apps panel. Videos of all

the panels are now online.

In general, we agreed: apps are coming to the car. They have already arrived in several cases, and it’s only a matter of time before they come to mass-market vehicles. And apps are not for North American alone: it's a worldwide phenomenon.

Mind you, we engaged in lively debate on a number of questions: What role does the mobile app developer play? How to deal with the fragmentation caused by different OEM app platforms? How to deal with driver distraction? And when will the "one man app" ever make it into the car? We all had good and varied opinions on these topics, and the session was very well received by the audience.

Derek Kuhn, QNX vice president of sales and marketing, also participated in a panel session, titled "Can we all just get along… for the consumer's sake?". That panel focused on how the industry as a whole can create a more seamless experience for the consumer. Derek's co-panelists included Mark Harland from GM, Leo McCloskey from Airbiquity, Brian Radloff from Nuance, and Niall Berkery from Telenav.

Did I mention? Videos of all the panels are now on Doug Newcomb's website — check them out!
 

Concept car out. Reference vehicle in.

Our big announcement for Telematics Update is that we are not showing a concept car. Odd news, you say. The truth is, we're not building a concept car because we are building a reference vehicle. Splitting hairs? Not really.

Unlike the Corvette and the Porsche, our demo for this show will be based on the exact same technology that our customers are using today to design their next-generation systems.

So why vehicle instead of car? Is it a truck? Nope. A van? Negative. What about a motorcycle? Double negative.

I was hoping to give you a sneak peek at what we are working on but I'm not allowed to give away the details. However, I did manage to get these shots – let me know if you can see the vehicle. :-)


 

A cool surprise at the Elektrobit auto summit

Recently, our good friends at Elektrobit invited the QNX team to participate in their German Executive Automotive Summit. It was an outstanding event with all of the leading OEMs and tier ones represented. The day was filled with engaging speakers and plenty of opportunities to network.

Elektrobit held the event in a small castle near Erlangen. In the courtyard, several cars featuring Elektrobit technology (and, in almost all cases, QNX technology) were on display. The car from Delphi was especially interesting. It's a full-blown race car, complete with everything you'd expect in a track vehicle — but it also has two rear seats. These seats allow mere mortals like you and I to vicariously share the racing experience with a professional driver at the wheel.



As I stood next to it, drooling, I noticed that it was equipped with an infotainment system, mounted on the back of the driver's seat. I leaned in to have a closer look and, to my delight, saw that it was running the QNX OS. Who knew?

Making the smartphone connection: The state of automotive navigation in Japan

A guest post from Yoshiki Chubachi, the automotive business development manager for QNX Software Systems in Japan

The market for navigation systems in Japan grew rapidly until 2006, but since 2007 the yearly volume has reached the saturation point, at about 2.9M units. For instance, in 2008, consumers purchased 900k after-market systems, 1.1M dealer-installed systems, and 909k factory-installed systems. In 2010, those numbers had changed slightly: 1.01M after-market systems, 1.03M dealer-installed systems, and 858k factory-installed systems (source: Yano Research Institute).

That said, the market is starting to experience a shift from after-market to factory-installed devices. Automakers and their tier one suppliers are struggling to differentiate their products by implementing value-added features.

To get a feel for current navigation trends in Japan, let’s look at some notable after-market products that shipped in 2011. As you'll see, smartphones are exerting a major influence on this market, both in terms of system design and user features:

Pioneer AVIC-VH09CS — This high-end system combines augmented reality technology with a front-view camera, overlaying your route on a live video of the road. It also implements a collision warning system by measuring the distance of the car ahead. Other features include terrestrial digital TV (full HD and 1seg), DVD video, AM-FM, CD and SD music, iPod connectivity, and music ripping and encoding.

Clarion NX501 — The smartphone world seems to drive navigation trends, and the Clarion NX501 is no exception. It offers a touchscreen UI that supports swipes, flicks, and other finger gestures similar to those found in smartphones and tablets. Suzuki factory-installed systems also use the type of user interface.

Fujitsu-Ten AVN-F01i — This system comes with three bundled iPhone applications: Twitter Drive (combines tweets with location data), Where is My Car (uses augmented reality to show your parking location on the phone screen; great for finding your car in large parking lots); and News Reader (allows the system’s text-to-speech engine to read out news articles). The system connects to the phone through Bluetooth.

Panasonic CN-H500WD — The system also lets you use finger swipes to operate navigation and audio functions, including a scrolling map. It comes with a smartphone application that provides POI search, which is downloaded to the navigation system through Bluetooth.

Mitsubishi NR-MZ50 — This system provides an “OpenInfo” service based on Pioneer’s Smartloop system, which provides traffic data from a Pioneer server. VICS (Vehicle Information and Communication System) is a popular traffic data service in Japan that is similar to the RDS-TMC standard, but its coverage is limited to main highways. The smartphone receives traffic data, derived from anonymous traffic probe information, wherever the VICS service isn't supported. Information from the phone is transmitted to the navigation system through Bluetooth.

Connectivity between navigation systems and smartphones remains an issue in Japan. Conventional cell phones are equipped with the Bluetooth DUN profile, which enables data communication between the nav system and the phone, but unfortunately, some carriers still don’t support this profile. Until they do, lack of connectivity will remain a roadblock.

Nonetheless, using smartphones to deliver applications and the user experience has become a major trend in Japan’s navigation systems. Some automotive tier one suppliers, such as Pioneer, already provide navigation applications on the phone. The QNX CAR 2 application platform, with its mobile connectivity features and auto-centric HTML5 framework, offers an ideal foundation for enabling this approach.

Sound "bytes" from CTIA Wireless 2012

Several of my colleagues went to CTIA Wireless this week, and yes, they took the connected Porsche with them. No surprise there, of course: we’ve also taken the car to CES, MWC, BBW, and numerous other events. (Sorry, I’m really into acronyms today.) The Porsche, with its QNX-powered mobile connectivity and HD hands-free audio, seems to impress people no matter where it goes, and the reaction at CTIA was no different. In fact, the folks from Black Enterprise were so stoked, they awarded the car a CTIA Best in Show award. How cool is that?

Here’s a snap of the award, sitting on the car’s dash:



Meanwhile, Boonsri Dickinson of BYTE met up with Andy Gryc to ask him about QNX’s vision and technology for the connected car. Here's a video of their conversation — in the Porsche, of course:



Andy didn't spend all of his time in the passenger seat. Both he and Derek Kuhn also participated in connected car panels moderated by automotive journalist Doug Newcomb. The panels included "Apps in Automotive: The Future of In-Car Content" and "Can We All Just Get Along, for the Consumer's Sake?". From what I've heard, both sessions were taped, and I hope to post a link to the videos next week.
 

Find me a Starbucks! QNX concept car showcases power of WATSON speech engine

Yes, you can talk to the QNX concept car and tell it what to do.

Recently, our friends at AT&T invited us to bring the concept car to their "Living the Networked Life" event in New York. We said yes, of course! After all, what could be cooler than riding the streets of Gotham City in a digitally pimped-out Porsche 911?

Kidding aside, the event provided an excellent opportunity to demonstrate how the car takes advantage of WATSON, AT&T's natural-language speech engine. To get an idea of what WATSON can do, check out this video from Terrence O'Brien of Engadget:



For the full Engadget article, click here. And stay tuned for more updates from the Living the Networked Life event.
 

Doug Newcomb goes social with new car tech blog

Lots of people blog about automotive technology, but few have the chops to grab my attention. Doug Newcomb is an exception, and I invite you to check out his blog, which came online two weeks ago.

The blog may be new, but Doug himself has deep roots in automotive journalism. Among other things, he created the car technology section of Edmunds.com; edited several publications, including Car Audio and Electronics, Car Stereo Review, and Road&Track Road Gear; and contributed to many others, including Popular Mechanics, MSN Autos, Corvette Quarterly, and SEMA News. On top of that, he wrote Car Audio for Dummies.

So far, Doug's blog posts have run the gamut — from the new Garmin Suzuki infotainment system to the virtual exhaust sounds emitted by Audi's e-tron supercar. Speaking of which, here's a video showing how those sounds were created:



To learn more about this and other developments in car tech, take a minute to visit Doug's blog or connect with him on Facebook.

PostScript: In case you're wondering, I wrote this post before I discovered that Doug had written a short article on QNX's membership in the Car Connectivity Consortium. Holy synchronicity, Batman!
 

Everything you wanted to know about HTML5 in the car, Part III

Welcome to the third installment in my Q&A series on HTML5 in the car. In Part II, we looked at web servers, native plug-ins, instrument clusters, and display updates. This week, we turn our attention to tools, touch gestures, UI performance, and vehicle resources.

Are there any HTML5 HMI builder tools available?
Most of the well-known IDEs, including Eclipse, Dreamweaver, and Netbeans, support some flavor of HTML5 in their latest release. Adobe Edge, a new tool now available in preview, also lets you create animated HTML5 content. I suggest you check out the HTML5 Tools site, which publishes up-to-date tool reviews.

Often, automotive customers will ask system designers to make an infotainment system work "like an iPhone,” with the popular gesture controls. Does HTML5 support "inertial" menus and two-finger zoom?
Multi-touch is handled at the app level; here’s an example. Pinch zooming at the browser level is browser-dependent — the QNX browser handles it, but not every browser does. As for physics-based scrolling, HTML5 doesn’t support it “out of the box”; it needs to be added. Frameworks like Sencha Touch provide these types of controls.

Will the performance of HTML and JavaScript be adequate for critical user interface components or computations, such as safety-related notifications?
This has to be tested on a case-by-case basis. For the UI elements, yes, the performance should be adequate. Our testing indicates you can build HMIs that are surprisingly responsive. Also, our WebKit port lets you do things things like run JavaScript code in other tabs, threads, or processes to ensure those ocmponents aren’t being thread-blocked by something less critical.

I do get a little gun-shy recommending HTML5 for safety-critical components, because JavaScript isn't inherently real-time. If you wouldn't feel comfortable using Java for a critical coding task, you shouldn't use HTML5 either. If you want predictable, real-time performance for a lower-level computation that cannot tolerate any delay, the code should execute in a non virtual-machine environment. Most code doesn’t really fit that description, so most of the time JavaScript should work just fine.

How do you call vehicle resources — vehicle HMI, vehicle diagnostics information, etc. — on a HTML web app in the car? What's the process in plain words?
In plain words, it’s kinda hard. :-) But here’s my best take on this question: we solve this by creating a vehicle-bus driver that exports data through a publish/subscribe mechanism. The HTML5 layer talks to that piece through a JavaScript interface.
 

A quick tour of the QNX CAR 2 application platform

If you're looking for a quick, two-minute intro to the QNX CAR 2 application platform, you've come to the right place.

In this video, Kerry Johnson, automotive product manager at QNX, takes us on a tour of the platform, including its home screen, media player, application area, HTML5 support, phone app, and acoustic processing.

Ready? Then hit the Play button and let's get started:



In case you didn't know, the QNX CAR 2 platform forms the basis of the QNX concept car, a specially modified Porsche 911 that demonstrates what to expect in next-generation car infotainment systems. Earlier this year, the platform drove home with a 2012 Best of CES award, in the Car Tech category.
 

TCS showcases hybrid navigation system in VW Polo

The Porsche 911 concept car that won the 2012 Best of CES award wasn't the only QNX-outfitted vehicle at Mobile World Congress this year. Our friends at TeleCommunication Systems (TCS), who provide hybrid navigation software for the QNX CAR application platform, showcased a VW Polo running the same QNX-powered navigation, maps, and local search capabilities as the Porsche.

Like the Porsche, the Polo featured a retrofitted infotainment system in place of the factory radio — and TCS did a very nice job integrating it into the car.

The Polo was a hit, driving discussions with mobile operators, handset manufacturers, automakers, and automotive tier ones. Seems the connected car is a hot topic just about everywhere you go these days.

Here's the Polo in the TCS booth:



And here's a close-up of the retrofitted infotainment system:


 

HTML5: Bustin' the myths

Did you know you can build HTML5 apps that don't use an Internet connection? Did you know you can run HTML5 apps without a web browser? And did you know HTML5 apps can show snappy performance even on automotive silicon? (As you can well imagine, in-car infotainment systems don't ship with quad-core server-class CPUs.)

If you answered no to any of these questions, you need to stop for a minute and check out this interview with QNX Software Systems' Kerry Johnson. Heck, even if you answered yes to all three questions, you'll probably still appreciate what Kerry has to say — and besides, you'll catch a glimpse of a complete in-car UI coded in HTML5. What could be bad?



While I have you, check out Andy Gryc's Q&A series on HTML5, if you haven't already. You'll find the first two installments here and here.
 

Audi A8 drives home with best connected car award

This just in: Connected World magazine has announced the winners of its first annual Connected Car of the Year awards, and the Audi A8 has won top prize in the ultra-luxury category.

According to Connected World, the awards honor vehicles with technology that strikes the right balance of safety, convenience, and infotainment. The magazine's editorial team decides the winners.

The Audi A8's infotainment system, dubbed the MMI, is based on the QNX Neutrino OS. The MMI offers some extremely cool features, including 3D navigation powered by Google Earth and a touchpad that lets you input destinations names by tracing them with your finger.

Here, for example, is a photo of the navigation display:



And here is a photo of someone using the touchpad, known as MMI Touch:



Both these photos were taken at a QNX Automotive Summit that took place in Stuttgart in 2010.

Connected World also handed out awards to the Ford Focus, Chrysler 300, and Cadillac XTS. These cars won in the small, mid-size, and luxury categories, respectively.
 

Everything you wanted to know about HTML5 in the car, Part II

Welcome to the second installment in my Q&A series on HTML5 in the car. Last week, we looked at CSS, cross-platform execution, and asynchronous design. This week, we turn our attention to web servers, native plug-ins, instrument clusters, and display updates.

If I don’t use a web server in my infotainment system, will I miss out on some features of HTML5?

A web server isn’t strictly necessary, but there are two very good reasons for including one. First, it lets you export a user interface to devices outside the car, thereby allowing mobile phones or tablets to run apps that are hosted on the vehicle head unit. Second, it lets you export internal car resources, as a URL, to HMI software running in the head unit. For instance, the web server could provide the HMI with access to static vehicle-configuration data (through an xml file) or to a back-up camera (through a video stream).

Will using native code plug-ins compromise my ability to leverage HTML5?

This is tricky, because a lot of things you want to do may require native code. So, yes, use native code, but do it judiciously. The more native code you use, the more it will limit the cross-platform capability of the HTML5 code that relies on it. The good news is that with HTML5 gaining so much functionality, plug-ins are needed far less than ever before.

A sample climate control app from the
QNX CAR 2 platform, created with HTML5.

Would you consider HTML5 as an option for cluster instruments: speedometers, tachometers, etc.?

At this point, I’d say no. HTML5 makes a lot of sense for in-vehicle infotainment, but it doesn’t provide the response needed for a vehicle cluster and it won't ensure safety-critical certification. Plus, the instrument cluster isn’t where you realize a lot of HTML5’s value: downloadable apps, connectivity to mobile devices, and so on. If the cluster and the infotainment system eventually merge into one big screen, then it’s more likely you could use HTML5 for both — but that’s still a few years out.

What’s a good way to get responsive display updates (10Hz update) into HTML5? Websockets?

If you need to deliver high-speed updates to your head unit, Websockets is one way to go. Make sure, however, that you don’t stall the rest of the JavaScript engine while your main thread is blocked on tasks. If you create another thread to monitor for changes, you can do it just as effectively (and probably with less work) with a JNEXT or NPAPI call into native code.