Role Design Director
Client Autoliv

Product Design.

How might we integrate the Safety Score application into a vehicle interface?

Integrating a standalone application into a vehicle interface.

The Safety Score app monitors real-time driver behavior and compares it against proprietary data to provide a safety score based on factors such as turning, acceleration, braking, speed, etc. But Autoliv wanted to expand it and integrate it into an automotive human-machine interface (HMI).

💡The Challenge

The primary challenge was to integrate The Safety Score app into the OEM interface using Android Automotive. This integration needed to be completely seamless, ensuring that the app's features were fully integrated into the in-car interface and driving experience. To tackle this challenge, we developed an approach focused on several key areas: understanding the requirements of the OEM interface, ensuring a seamless experience, and rigorous testing to validate the integration.

💡Understanding requirements

The first step was to thoroughly understand the requirements and constraints of the OEM interface. This involved close collaboration with their technical and design teams to gain insights into the HMI standards, their interface design system, and technical specifications.

The Safety Score app needed to be intuitive and easy to use within the OEM interface. This involved adapting the app's design to match the HMI, ensuring that the app’s features were suitable for use whilst driving and embedded within overall HMI design language.

💡Developing and testing

The development and integration followed an iterative process, with multiple phases of testing and feedback. The initial phases focused on creating a basic integration with the HMI. This version included core features such as real-time behavior monitoring, safety score calculation, and data analysis. Whilst the engineering team ensured features could interact with the vehicle’s data.

Alpha |Alpha testing was conducted in a controlled environment to identify and fix any major issues. This phase involved a small group of internal testers who used the app in various driving scenarios. Key objectives during alpha testing included verifying data accuracy, ensuring real-time performance, and assessing the app’s responsiveness within the Renault interface.

Alpha
Alpha testing was conducted in a controlled environment to identify and fix broad issues. This involved a small group using scenario testing. The testing immediately highlighted improvements, including the need for far better integration with the vehicles notification systems and simplification to the HMI to make it less distracting.

Beta
Beta testing expanded the group to include a broader group of testers, including OEM employees. This phase focused on real-world driving conditions. The objectives were to gather extensive user feedback, identify usability issues, and ensure stability and performance in various conditions.


Key insights included the need for additional features such as customization for driving behaviors and better feedback on how to improve driving safety. Based on the insights from testing, the team implemented continuous improvements. This iterative approach ensured that we consistently met the expectations of both user and OEM and provided valuable safety insights.


💡What now?

The integration of the Safety Score app into the OEM interface was a success. The comprehensive testing ensuring the new HMI features were robust, user-friendly, and highly effective in providing real-time safety feedback. The project achieved its goals and delivered a valuable tool for enhancing driver safety and is now under review with the OEM.