UIEvolution's UIEngine Now Supports SDL to Drive Connected Vehicle Experience

By CIOReview | Tuesday, January 5, 2016

LAS VEGAS,NV: Enabling manufacturers and third-party developers to support both native and SDL-based connected car applications, UIEvolution, announces that  its middleware platform, UIEngine now supports SmartDeviceLink (SDL).The company is a provider of  connected device software platforms for the automotive and hotel industries.

UIEngine is a thin-client middleware solution that offers high performance in design, quality and user experience for in-vehicle systems. The solution has been opted by Toyota and DENSO to deliver automated connections across all devices and screens with minimal hardware resource requirements. The platform is device and network agnostic and can be integrated with embedded HTML5 browsers, navigation applications and on-board diagnostic information to drive in-vehicle Human Machine Interfaces (HMI) improvements and capture analytics.

SmartDeviceLink is a project which intends to standardize and wrap the many in-vehicle interfaces which may exist in the automotive context. The end goal of the project is to provide an expandable software framework to both mobile application developers and automotive head unit designers for the creation of brought-in applications that appear integrated onto a head unit.
Many in-vehicle HMI’s use different templates, icons, fonts, voice systems and input methods for their infotainment systems. With SmartDeviceLink, a template-based approach is provided by the automotive head unit and allows for different HMI frameworks to follow a specific set of guidelines ensuring a consistent experience to app providers and customers.

SmartDeviceLink consists of two distinct parts of software; a core automotive piece which wraps in-vehicle services and integrates to the in-vehicle HMI, and a mobile proxy, which executes APIs to access and use services on the automotive head unit.

The Concept of SDL allows device and car connect through application requests that are sent to the vehicle and the vehicle responds (Remote Procedure Calls). In this case, the application appears to be running inside the vehicle, but all business logic is contained on mobile device. Eventually, the user interacts with their vehicle and the vehicle notifies application of any system or user events. The application also reacts by sending requests to modify application behavior or appearance in the vehicle.