Introduction —
The optimal route —
Open to differentiation —
Open standards versus open source —
Bridging the gap —
Summary
[+]
Introduction
It is sometimes assumed, erroneously, that basing a product on open standards and delivering a distinct user experience are mutually exclusive options. Quite the opposite. HTML5, for example, offers all the benefits of a widely supported standard ...
The optimal route
With embedded electronics now representing almost one-third of a vehicle’s cost, and in-vehicle infotainment systems accounting for a substantial share of that cost, the role of open software standards has never been more important. Not only can ...
Open to differentiation
Anyone unfamiliar with HTML5 may be excused for assuming it is “just a browser.” In fact, HTML5 comes with an application environment that has all the capabilities of a traditional HMI toolkit, including a rendering engine, content authoring and ...
Open standards versus open source
Automotive OEMs consider open source platforms for several reasons: to avoid vendor lock-in, to gain access to a community of developers, to leverage a rich toolset, and to avoid the costs of run-time licensing. But, often, an approach based ...
Bridging the gap
We’ve discussed how automotive developers can leverage open standards at both the user-interface level and the system level. The question is, how do you connect the two? For instance, applications developed with HTML5 reside in a high-level ...
Summary
It is often assumed that open source platforms offer the best route for avoiding vendor lock-in and accessing programming talent. But such benefits are often best realized with open standards. These standards promote code reuse, increase ...
