But don’t take my word for it. Check out the recent whitepaper,“Why HTML5 Is Becoming the HMI Technology of Choice,” from my colleagues Andy Gryc and Marc Lapierre.
To explain why HMI developers are turning to HTML5, Andy and Marc explore several themes. For instance:
- HTML5 allows developers to construct applications either inside or outside of a browser, with capabilities such as databases, threading, and input from device hardware.
- Using CSS3 animations, the <canvas> element, WebGL, and SVG graphics, HTML5 provides control over HMI rendering that is precise enough for games and flexible enough for applications.
But what about the hardware?
Before you go, please note that the paper doesn't answer an important question; namely, how can an HMI developed with HTML5 communicate with a system's hardware devices? For instance, in the car, an HTML5-based HMI may need to communicate with the CAN bus, GPIO pins, and I2C and SPI devices, as well as with external devices like tablets and smartphones.
Fortunately, there's a paper for this, too. :-)
In "HTML5-Hardware Communication with PPS Messaging," also written by Andy Gryc, you'll find out how PPS, an HMI-agnostic, asynchronous messaging model, can provide a very flexible approach to communicating with in-vehicle hardware.
With PPS, devices don’t communicate with the HMI directly. Rather, they become publishers of data objects to which the HMI can subscribe. As a result, it becomes much easier to swap out or modify devices, as well as the HMI itself. This, of course, is the Reader's Digest version. Download the paper to get the fully skinny.
Further reading (and viewing)
If you're interested in HTML5 and the car, here are some other papers and posts I recommend:
- Moving beyond the browser: HTML5 as an automotive app environment
- Talking HTML5 with Audi’s Mathias Halliger
- HTML5: Bustin' the myths
- Why Automakers (Should) Care about HTML5