Melbourne Q3 hero — interface mock
Melbourne — Q3 release

In-car interface — Melbourne (Q3)

Concepts and prototypes focusing on commuter flows, adaptive clusters, and EV-first experiences tailored to Australian driving contexts.

Project overview

This Q3 initiative explores modular cluster UIs, context-aware home screens, and voice-first interactions for Australian urban and regional driving. Research combined field observations in Melbourne with rapid prototyping.

Driver contextual research

Field research

Observations around Melbourne CBD and suburban commutes.

Prototype testing

Prototype testing

Iterative touch and voice test cycles with drivers.

EV scenario

EV-first flows

Battery, charging and range-aware dashboard concepts.

Design approach

  • Adaptive clusters: reflow UI based on driver state and speed.
  • Legibility: Australia-specific type sizes and contrast for sun angles.
  • Minimised distraction: glance-first information hierarchy.

Accessibility

Voice assist and tactile feedback patterns designed for driver's attention management.

Localisation

Units, drive-side options, and local points-of-interest integrated for Australian users.

Interactive prototypes

Playable prototypes were built for highway, urban and parking contexts. Below are key screens and interaction notes.

Cluster prototype
Adaptive Cluster

Speed-aware layout with priority lane information and navigation cues.

EV dashboard prototype
EV Dashboard

Range-first home, charger finder and eco-routing hints.

Driver assist screens
Driver Assist

Glanceable lane-assist and takeover prompts with haptic patterns.

Case studies

Commuter case study

Commuter flow — Melbourne CBD

Improved route summarisation reduced glance time by 18% in tests.

Discuss this study
Regional case study

Regional drives — Gippsland

Range-aware routing and offline POI caching for long drives.

Request data

Technical notes & FAQ

Designed for 7–15" clusters, CAN bus integration, and OTA-friendly architectures.

Layouts follow Australian road-safety guidance for glance time and in-vehicle displays.

Typical integration and validation cycles: 4–6 months depending on OEM toolchains.

Team & contacts

Lead designer
Alex Morgan

Lead UX Designer — Nextgenautoexpert (Melbourne). Specialises in driver-centred dashboard ecosystems.

Technical specifications (summary)

AreaNotesPriority
Cluster latency<50ms input-to-displayHigh
Power modesLow-power core for standby retain statesMedium
ConnectivityLTE/5G, BT, Wi‑Fi, OTA updatesHigh