Android IVI

IoT Portal and Shop
December 3, 2015
December 15, 2015

Android IVI

Android IVI development project had the goal to design user interface (UI), user experience (UX), graphic design and software solution for a next generation user interface for an automotive In-Vehicle Infotainment system (IVI) supporting car information, navigation, multimedia and other relevant IVI functions.

UI is composed of elements which correspond to each functional group. One element fits to one screen area at the time (screen area is referred to as scene). Elements can be moved, exchanged and manipulated within the UI/UX paradigm. Screen holds a status scene component, showing the most relevant information, at all times. Each element is effectively resized to cover either primary or the secondary screen in the appropriate way.

Elements are stacked within a space that has virtual depth along the z-axis. UI is consisted of two carousels, one for the primary screen area, and the second for the secondary screen area. Each carousel brings up elements on the corresponding screen. Carousels are twisted, meaning that one element from one carousel can become a part of second carousel, and vice versa.

Overall catch is that all elements resemble a charging discs for a novel concept of jukebox machine. Appearance to the user would be as if IVI reaches out to the car engine, taking up full central console space inwards. Carousels spin to reach out for new elements from somewhere deep and charging the primary and secondary screen areas with them. The main idea that can be incorporated in general concept that primary screen area can be referred as active, and secondary screen area as passive. Active area has ability to handle hardware buttons inputs as well as touch events. Regarding the passive area user can interact with it only via touch events. This is detail is important for the user, that wants quickly and easily to interact with IVI via hardware buttons while driving with less overall amount of distractions. Status bar area is defined only as read only area, which means that user interactions with it will be generally ignored.