Vehicle Hub — one place for every vehicle need

A growing ecosystem with no home

The platform initially focused on FASTag and vehicle loans. Over time, new categories were added — challans, EV recharge, and fleet recharge.

While the ecosystem was growing, one clear business challenge emerged: users had to discover these services individually through the broader category landing page, where many unrelated categories also existed. As more vehicle-related offerings were added, discoverability became harder and the vehicle ecosystem lacked a clear identity within the product.

Vehicle services existed, but they were fragmented

This created three key challenges:

• Low discoverability of vehicle-related categories
• Weak cross-usage between services
• No single destination for users with recurring vehicle needs

Proposed as a growth lever

The Vehicle Hub was proposed to strengthen category engagement and improve cross-usage across products.

One unified space for everything vehicle

Instead of asking users to search category by category, the vision was to create a platform where users could manage everything related to their vehicle in one unified space.

A place for:

This would increase vehicle-category visibility, improve repeat usage, and create stronger platform retention.

Users were already solving this — just elsewhere

Before designing, we wanted to understand how people currently manage their vehicles. We spoke with users and studied existing behavior.

What we found: users were already solving the problem themselves — but in scattered ways.

From service marketplace to ownership dashboard

Based on research, we decided to build a consolidated Vehicle Hub. The platform would not just list services — it would intelligently bring data together through APIs.

30+ directions. One insight that shaped everything.

We explored more than 30 wireframe directions to understand:

• Can users quickly understand the platform?
• What should be shown first?
• How much information feels useful vs cluttered?
• Should it feel like a dashboard or an assistant?

Designed to feel like ownership, not a utility

The top section was designed as the emotional anchor of the experience. We wanted users to feel ownership and delight the moment they opened the page.

We explored animated vehicle experiences inspired by best-in-class apps:

• Rotating 3D models
• 360° image sequences
• MP4 / GIF motion loops

Due to technical constraints, real-time 3D rendering was not feasible in the first release. So we adapted the experience using high-quality still vehicle imagery, smart transitions while switching vehicles, and motion-led interactions without heavy performance cost.

This allowed delight without compromising delivery timelines.

Two approaches. One insight that decided it all.

We explored two distinct directions before arriving at the final design — one driven by benchmarking and information architecture, the other shaped by user interviews that fundamentally changed the hierarchy.

Service catalogue with structured navigation

The first approach was informed by competitive benchmarking — CRED, Park+, and other vehicle platforms. It focused on organising all services into a clear, navigable structure with category tiles, quick access shortcuts, and a comprehensive service grid.

This felt complete on paper. But user testing revealed the problem: it still asked users to choose what to do rather than telling them what needed attention.

Wireframe directions from the benchmarking phase — service catalogue and navigation-first layouts

Vehicle dashboard — ownership-first hierarchy

User interviews changed everything. Users didn't want to manage their vehicle — they wanted instant reassurance. This drove a shift from a service catalogue to a proactive vehicle dashboard organised around one core question:

The hierarchy was rebuilt from scratch around urgency and ownership — P0 surfaces what needs attention now, P1 gives status at a glance, P2 handles upcoming renewals, P3 goes deeper into documents and history.

Final design — vehicle dashboard style after user interviews

Final Design

My Vehicle — final screens

Two states of the same dashboard — one vehicle with pending actions requiring immediate attention, another fully healthy and ready to drive. The hierarchy stays identical; only the status signals change.

Ready to Drive

Action Required