A large challenge was balancing the roles of the smartphone app and the onboard display. Initially, I wanted to focus on the onboard display, but after much trial and error, I realized that a smartphone was needed as it was too unwieldy to enter a lot of data. Therefore, the roles of each device changed—the onboard display would be used as the main display and for simple tasks, such as lowering the windows or changing the volume, while the smartphone app would be used to create users, enter data, unlock the car, and any other function that required precision.Rather than being an all-in-one package, the inbuilt display would be an extension of the smartphone app, designed to be seen and used while in the car and powered by the smartphone app.
A large challenge was balancing the roles of the smartphone app and the onboard display. My initial idea was to focus upon the onboard display, but after much trial and error I discovered that a smartphone would indeed be needed as it was too unwieldily to enter lots of data. Therefore the roles of each device changed - the smartphone app became the main source of input, for fulfilling tasks such as creating users, entering data, unlocking the car and other functions which required precision, while the onboard display was used passive display and for simple tasks, such as lowering the windows or changing the volume. Instead of being an all-in-one package, the inbuilt display would be an extension of the smartphone app, built to be seen and used while in the car and powered by the smart phone app.