Back to portfolioTRAQYLAN / CASE STUDY

VEHICLE TRACKING / MOBILE EXPERIENCE

Traqylan

Know where it is.
Know what comes next.

A vehicle-tracking app that brings location awareness into a wider vehicle-care experience. Across 20 supplied screens, onboarding and a map-led dashboard connect with driver scheduling, fuel reporting, scorecards and trip records—alongside parts shopping, garage discovery and vehicle settings.

Discipline
UI/UX design
Platform
Mobile app
Current scope
20 supplied screens
Product areas
Tracking, operations & vehicle care

THE DESIGN CHALLENGE

One vehicle.
Several different needs.

Finding a vehicle, assigning a driver, reviewing a trip, buying a part and contacting a garage are related needs—but different tasks. The design challenge is to preserve immediate location awareness while separating operational tools, shopping and user controls into recognisable areas.

This case study is grounded in the supplied interface designs. It describes visible decisions and proposed validation questions, without claiming completed research, live tracking accuracy or measured business outcomes.

EXPERIENCE STRUCTURE

Locate. Plan. Review. Maintain.

  1. 01

    Getting started

    Brand, tracking introduction, route positioning and sign in.

  2. 02

    Vehicle operations

    Tracking, tools, driver scheduling, scorecards, fuel trends and trip records.

  3. 03

    Parts shopping

    Categories, part types, product listings, details, cart and payment selection.

  4. 04

    Services & control

    Garage comparison, contact actions, vehicle management and privacy entry points.

SCREEN EXPLORER

The choices behind the screens

01 / Getting started

A road-inspired identity from the first screen

The curved road motif in the Traqylan mark is echoed by the edge of the splash screen. Yellow and navy establish a recognisable visual language that carries into onboarding, tracking and the shop.

Design consideration

This is a static opening design. Loading time and transition behaviour are not established by the screenshot.

01 / 20
Splash / Supplied UI design

DESIGN RATIONALE

A clear lane for each task.

Map first, context nearby

The map remains the main workspace. Vehicle selection and telemetry sit close to it, so supporting data does not require leaving the location view.

Separate planning, status and review

The Tools hub separates scheduling from scorecards, fuel monitoring and trip history. A route can be assigned first, monitored in context and reviewed later without forcing every task onto the map.

Keep commerce in its own lane

Shop is separate from Home and Tools. Categories, grouped part types and filtered product listings lead into details, cart and payment, while retaining the app's navigation and visual identity.

Pair action with user control

Garage listings offer several contact routes, while Settings gives vehicle management, location, alerts and privacy their own place. Operational visibility should be paired with understandable permissions and control.

DESIGN OUTCOME

From vehicle location
to operational context.

The 20-screen design now connects location awareness with planning and review: assign a driver and vehicle, inspect fuel and driver summaries, then examine a trip and its stops. Parts discovery, checkout, garage contact and settings extend that core into vehicle care. This is a documented design scope, not a measured improvement in safety, fuel efficiency or revenue. Detailed geofencing, surveillance, route playback and post-payment states remain outside the supplied set.

What to validate next

  • Can people identify the selected vehicle and understand how recent its location and telemetry are?
  • Can users schedule an available driver and vehicle, and distinguish a planned trip from a completed journey?
  • Can shoppers establish part compatibility and review a complete total before payment?
  • Are driver scores, fuel periods, location permissions and downloadable trip information understandable and trustworthy?

Proposed validation questions—not completed research or reported results.