My personal journey of mixing module 2 and 3 within the development iteration cycles.
Andrew Chui From idea to drawings and a real prototype.
Module 2
Building Interactions for Car Dash Console
Module 2 was unfinished due to delays in testing and rebuilding an appropriate tester. I discovered that finding the "Energiser" demographic was challenging because of their proactive style—I realized this approach worked better with larger test pieces rather than small pieces at the beginning. However, testing smaller pieces first proved invaluable; without it, I might not have arrived at my current prototype direction. Module 2 focused on building the interactions that would define the car dash console experience.
Project 3
Module 3
A car dash console that integrates physical computing to enhance user experience and safety. This site documents the process of building an integrated physical computing interface for a better cabin experience.
Workshop 1 : Action Research on bettering the protoype v1 from module 2 (technically)
Workshop 2 - Making better prototype - Better lighting from 1 led to a strip
The lighting with ledstrip was inspired by lecture and in-class reference. However my lighting choice is due to the priority of visual sensory for drivers. Drivers also preferred lighting controls over audio controls due to the practical use of it over a period of time. Testers see the appeal and experience of a visual paired with audio is more fun comapred to being able to control sound but no lighting or minimal lighting. Lighting was found to be less distracting when it is not near the leg well for prolonged period of time. Functional use is the core for the lighting control.
Activity 1: My Research
Lists Help (And They Do)
Assess Your Software
Known
- Screens can be made with Protopie and Sigma
- Sensors can send signals to Protopie
- Data can be sent from Protopie to Arduino
Unknown
- What system to use
- Not familiar with Protopie or Arduino
Sensor Technology Testing
Used: microphone, light sensor, LED screen, LED light, potentiometer, temperature sensor
Key Findings
- Dials are necessary for natural interaction
- Physical buttons preferred for direct controls
- Physical interface equally important as digital response
Materials Assessment (Prototype V1)
Known
- Prototype size too small for testing
- Modular pieces more interactive
- Groupings necessary for clarity
Unknown
- How to make mock dash testable
- What parts to add
UI/UX Assessment (Prototype V1)
Known
- Driver gestures are intentional
- Many screen layers to navigate
- Widgets help personalization
Unknown
- How to integrate screens naturally without becoming another Tesla-like system
- Balance control without distraction
UI Unknowns
- Screen orientation
- Control style
- What features to offer
- What feels invasive to drivers
UX Unknowns
- Easiest controls for users
- Behavior changes with new interfaces
- Modular testing feasibility
Critical Unknowns
Hardware/Software: Using sensors & microchip, UI-hardware connection
Interaction: Driver confusion about capabilities, Interface accessibility
Strategizing - Progress Blockers
- Testing & redesign coordination with limited tester availability
- Need to determine which system connects components
- Time and research investment in learning; difficult to know when to stop research/testing
- Blind spots would be mostly time and research while learning. Deciding on when to stop research or testing is also hard and pushes project behind.
Activity 1 : Action research 3 possible items
- The functions that drivers might find useful that utilizes sensors addition.
- The type of digital interface that drivers are okay with ; not just Tesla big screen.
- How to make the dash console better for testing and engaging for testers.
- What type of digital interfaces are suitable for the system to work.
Activity 2: My Research
Additional Research or Workshops
Project 3
Project 3 Final Prototype
The small interface allow for lighting control with specific functions. IDeal function is proximity lighting where if user hands go near the controls the lighting brightens to help with visibility. The feature is only activate when on and can be turned off. Another mode is for temperature related hot and cold withhin the cabin. Third is the brightness of interior cabin or music reactive led strip. Ambient lighting is also ideal to have a light warm glow. All functions can be personalized for the energisers demographic need.
The not finished car dash console prototype that integrates physical computing to enhance user experience while being safe and non-invasive to drivers. This system tires to simualte the physical computing environment for drivers inside their car. The panel is able to be personalized for different functionality that would be buried under different UI screens. The small vertical interface provide an easy to access control panel that extends user want to the physical car they are in. Ideally when the driver is in the car, they can access all the features they need without having to look away from the road. Ideally the physical computing components include light sensors, temperature sensors, potentiometer dials, LED lights, and an LED screen. These components work together to create a dynamic and interactive experience for the driver, enhancing their overall driving experience while ensuring safety and ease of use.