Nova Fleet Tracking

Project at a glance

Nova Fleet Tracking app project began with a comprehensive scope definition that identified key functionalities crucial for efficient fleet management.

The core objective was to provide real-time vehicle tracking, historical data analysis, and immediate alerts, along with features for monitoring vehicle status and managing geofences. The design process was iterative, commencing with wireframing and low-fidelity prototypes to establish the basic layout and user flow.

This initial phase focused on intuitive navigation, ensuring that users could easily access tracking information, vehicle details, and alert notifications. User feedback was incorporated at each stage, leading to refinements in the interface and overall experience.

Project scope
Real-time GPS tracking, vehicle lists and detail, geofences, alerts, trip history, filtering and recorded vehicle video.
Challenge
Compress a data-heavy fleet-management workflow into a mobile interface that stays fast to scan, safe to operate and easy to investigate.
My role
End-to-end Product / UX / UI Design: scope translation, flows, wireframes, interaction design, visual design, prototyping and iterative refinement.
Approach
Start with operational questions and user flows, validate structure in low fidelity, then progressively add map detail, status controls and evidence-rich views.

Context and challenge

A fleet system in your pocket

Nova’s fleet proposition combines GPS location tracking with operational controls and evidence: geofences, ignition state, alerts and reporting, driver behaviour, trip history and tracking from anywhere. The mobile experience needed to make those capabilities useful when the operator was away from a desktop.

Live awareness vs. detail
Operators need an immediate answer from the map, but also enough detail to understand vehicle state, group, asset type and current context.
Speed vs. safety
Remote starter and ignition controls make the app operational, not just informational. Actions must be visible and understandable without encouraging accidental use.
Map context vs. investigation
The same product must support “where is it now?” and “what happened earlier?” without turning every screen into a dense dashboard.

Problem definition

The product had to support three different modes of attention

“Fleet managers need a fast way to understand a vehicle’s current location and state, investigate past events, and respond to exceptions while away from a desk, without losing confidence in the data or the action they are taking.”

01 NOW
Locate + assess
Live map, vehicle markers, current information and status.
02 BEFORE
Investigate
Trip history, date range, recorded video and historical route context.
03 EXCEPTION
Act
Alerts, geofence events, filtering and vehicle-level operational controls.

Design principles

Map first
Lead with location when location is the question.
Progressive disclosure
Reveal filters and detail only when the user asks for them.
Evidence close to events
Keep video, history and alerts connected to the relevant vehicle.
Consistent filtering
Reuse group, asset, vehicle and date concepts across investigation flows.
Clear action state
Make operational controls and their current state easy to distinguish.

My role and approach

From product scope to an operational mobile experience

My role
I worked end to end across product definition, information architecture, user flows, wireframing, interaction design, high-fidelity UI and iterative refinement. The focus was translating a broad fleet-management capability set into a coherent mobile experience.
Key responsibilities
- Translate business scope into user-facing tasks and flows. - Define the information hierarchy for live tracking and investigation. - Explore layout and navigation in low-fidelity wireframes. - Design map interactions, bottom sheets, filters and detail states. - Refine visual hierarchy, typography, colour and iconography. - Incorporate feedback through successive design iterations

Design process

01
Scope
Define core capabilities, constraints and priority user tasks.
02
Structure
Map navigation and task flows around tracking, vehicles, geofences, alerts.
03
Wireframe
Test screen hierarchy and mobile interaction patterns in low fidelity.
04
Prototype
Connect key flows & validate how users move from map to detailed investigation.
05
Refine
Use feedback to improve clarity, visual hierarchy, filters & evidences.

The process was deliberately iterative. Low-fidelity decisions established the layout and flow first; visual polish came later, after the navigation and operational logic were coherent.

Final solution

A mobile command layer for live fleet awareness and investigation

The final design organises the experience around the operator’s mental model: see the fleet, focus on one vehicle, investigate what happened, then act on exceptions. The same core entities — group, asset type, vehicle and date — recur across filters so the product feels like one connected system.

01 • LIVE TRACKING
Location is the starting point, not a secondary view.

The Tracking experience keeps the map dominant while giving operators a quick way to identify vehicles and reveal current information. A bottom-sheet search pattern adds control without permanently covering the map.

Clustered / numbered vehicle markers reduce map noise
Selected vehicles expose current information directly on the map
Search can narrow by group, asset type and individual vehicle
Floating location controls remain reachable with one hand

02 • VEHICLE + STATUS
Move from fleet scan to vehicle-level control.

Clustered / numbered vehicle markers reduce map noise
Selected vehicles expose current information directly on the map
Search can narrow by group, asset type and individual vehicle
Floating location controls remain reachable with one hand

03 • HISTORICAL TRACKING
Turn “where was it?” into a focused query.

Historical tracking reuses the same fleet entities as live tracking, then adds a date range. The result returns to the map so users can understand historical movement spatially rather than reading a disconnected report.

Consistent filters lower relearning between live and historical tasks
Date range makes the investigation window explicit
Route and vehicle markers preserve spatial context
History becomes a direct extension of tracking, not a separate product

04 • VIDEO EVIDENCE
Put visual evidence next to the event and journey.

Recorded footage is treated as operational evidence. The design combines a selected video, timestamp, description and date-based list of additional recordings so an operator can move from alert or vehicle context into review.

Large playback area prioritises the selected event
Timestamp and description support incident understanding
Date selection narrows the recording set
Share / action controls sit with the reviewed footage

05 • GEOFENCES
Make virtual boundaries visible and manageable.

Geofence management combines a scannable list with a map-based editing state. This keeps abstract boundary rules grounded in geography and supports monitoring when vehicles move into or out of defined areas.

List view supports quick access to saved boundaries
Map editing makes the boundary tangible
Vehicle marker context helps validate the selected area
Entry / exit monitoring fits naturally into the alert model

06 • ALERTS + FILTERING
Centralise exceptions, then help users reduce the noise.

Alerts act as the operational inbox. Event cards show vehicle, status, time and optional video evidence; a dedicated filter view lets the user narrow the feed using the same fleet dimensions seen elsewhere in the app.

Active / passive states support event prioritisation
Cards keep vehicle and event information together
Video preview makes evidence available from the feed
Filter by group, asset type, alert type and date range

07 • NAVIGATION MODEL
A simple menu keeps the system understandable as the feature set grows.

The side menu gives users a predictable route into the main operational modules while keeping the map experience free of persistent navigation chrome. Profile context is separated from task navigation, and alert count can remain visible as a system-level signal.

Tracking and vehicle access
Vehicle history
Geofences
Alerts and outstanding events
Profile / account context

Impact + Outcomes

One connected mobile experience instead of a collection of tracking features

The outcome is a coherent operational workflow that brings live location, vehicle status, historical tracking, video evidence, geofences and alerts into one mobile system. The value comes from reducing the distance between noticing something and understanding what to do next.

Immediate fleet visibility
A map-led entry point makes current vehicle location and status the first thing an operator sees, supporting fast orientation when working away from a desktop.
Faster investigation path
Alerts, history and video are connected to vehicle context, creating a direct path from an exception to the evidence needed to understand it.
Lower interaction relearning
Group, asset type, vehicle and date patterns recur across flows, so users do not need a new filtering model for each operational task.
More legible operational state
Vehicle controls, event states and geofence boundaries are presented explicitly, making the difference between information and action easier to recognise.

Evidence note
No quantitative post-launch metrics were supplied for this case study, so the impact is described through supported product outcomes and interaction improvements rather than invented percentage claims.

Design learnings

What mattered most in a data-heavy mobile product

Hierarchy beats density
A phone cannot reproduce a desktop fleet dashboard. The design works by prioritising the question at hand and revealing detail progressively.
The map is a workspace
Location is not decorative context. Markers, selection, vehicle information and boundary editing make the map part of the interaction model.
Evidence belongs near the event
Video and historical data become more useful when they stay connected to the relevant vehicle, journey or alert.
Consistency creates scale
Reusing entities, filters and interaction patterns allows new fleet capabilities to be added without making the app feel fragmented.