Fourth Design Sprint: Dual User Interfaces

 
 

Designing experiences for multiple users

 At this point in the project I thought it would be important to try and reflect on the role of the driver and passenger with the car. The car experience is quite unique as both passenger and driver have different needs when interacting with an HMI system, and also have defined positions within the car.

 
 

Process

The aim of this week was to explore and sketch out an interface that could identify and adjust to the users who are interacting with the system. This is of importance in a driving context as the driver must maintain as much attention on the act of driving as possible, while the passenger has no such constraint. 

This essentially means that there is no one interface that will best suit the driver and a passenger. It was with this in mind that I began to sketch based on this concept.

 

 
 

The prototype was built in framer and processing. The screen consists of a menu with two states, one for the driver and one for the passenger.

As the user begins to interact with the screen, the interface will adjust to the specific role of the user. The driver will get an interface with larger, clearer information with lower information density, while the passenger will have more detailed controls and deeper menus.

The prototype uses a leap motion to detect which hand the user is using, this gives a pretty good analogue to the driving situation as you can work out which person is most likely to be using the interface.

What I learned

Despite the simplicity of the build, this prototype was actually really well received by people I tested it with. There is some quality to the interface changing when you interact with it that people really responded well to.  It was at this point in the project that the idea of a dialogue between the user and the controller began to take shape.