User interviews
Semi-structured. Pain points, bliss points and expectations of a connected-car app.
The connected-car app had flat engagement and almost no business impact for 2.5 years. I led the end-to-end redesign for the Indian market. Nissan's leadership then adopted it as the benchmark for NissanConnect in other countries.

More than 30 features, from geofence alerts to a virtual showroom. But vehicle data was often stale, alerts were late, and service booking broke after updates. Owners installed it, checked it a few times and stopped.
A 58-point heuristic audit, an accessibility review, nine field studies, 13 interviews and 2.5 years of analytics became a new IA and a glanceable home. I then co-created a global design system with Nissan's Europe team.
Service bookings, accessory sales and leads rose sharply. Nissan's directors made the design the reference for other countries, which led to the Kicks infotainment redesign.
I was Head of Design on the engagement. I owned the design strategy, ran the research plan and design reviews, and was the design voice in front of Nissan's director board.
SajinHead of Design
ArathiDesign team
GokulDesign team
ShafaazDesign team
VishnuDesign team“The current mobile app has not been generating significant business for the last 2.5 years, and user engagement is consistently low.”
That was Nissan's brief. Before redesigning anything, we used the app as owners and as designers, and mapped every flow end to end. We recorded the first-time experience and checked our understanding with Nissan in several sessions.

The full map showed dead ends and loops that single screens hide. Signing up with Google led back to the sign-up screen, and core status needed the ignition on. These maps became the baseline for the audit. Click to zoom in.


We started with an expert usability review to find what was broken before talking to owners. That let the interviews go deeper than surface complaints. The full evaluation runs to more than 40 slides.
Open the full heuristic evaluation ↗




Every slide pairs an annotated screen with the heuristic it breaks, a severity rating and a recommendation. These four show the pattern: sign-in friction, forced registration, a congested home and slow feedback.




The app had no shared design language, so every screen solved the same problem differently. One in four problems was a release blocker.
The 17 catastrophes broke core tasks: signing up, reading the car's status and finding the car.


We audited every screen against WCAG 2.1 and the iOS and Android guidelines. Our research flagged that vision changes start from around age 40, and that colour blindness affects millions of drivers. So accessibility became a core requirement of the redesign, not a polish item.








| Check | Found | Target | Fix in the redesign |
|---|---|---|---|
| Touch target, Smart Drive Score | 41dp | ≥ 48dp | Score becomes a large hero element |
| Toll icon contrast (#20A9FF on white) | 2.57 : 1 | ≥ 3 : 1 | New icon set and palette checked for contrast |
| Text on brand red | 3.57 : 1 | ≥ 4.5 : 1 | Red reserved for alerts. Text on navy or white. |
| Dynamic type | Layouts break | Scales | Components built to reflow |
| Screen-reader labels | Missing | All inputs | Labels specified in the design system |
The audit told us what was broken. Only owners could tell us what mattered. We ran an ethnographic field study with nine owners in their own cars, then structured interviews, and set both against Nissan's data.
We watched owners in traffic, in car parks and at home. Phones sat on seats and in holders and were checked in quick glances. That is why the redesign is built for a three-second look, not a long browse.


We interviewed owners for pain points, bliss points and expectations. We interviewed Nissan's director board for business goals, and every stakeholder for constraints. Each owner interview followed the same three-part structure so answers could be compared.
Semi-structured. Pain points, bliss points and expectations of a connected-car app.
Business expectations: service revenue, lead generation, brand perception.
Designers, PM, and backend, Android and iOS developers: constraints and data realities.


We clustered interview notes in Miro. Five themes emerged: vehicle status, location, service booking, alerts and the fuel expense log. Nearly all of them were about the app being wrong or late, not about missing features.

Nissan's analytics team shared 2.5 years of data. In one month of 1.83 million page views, Home and Find My Car took two thirds of all traffic. Yet the old app gave them no more weight than a dozen rarely used features.
Top 8 of 14 tracked pages, one month, 1,828,133 views.

We compared features and patterns across Indian and international connected-car apps. The best ones open on a live picture of the car and push secondary tools one level down.



If I want to see whether I locked my doors, it says I need to turn on the ignition.
Doesn't update in real time and shows the wrong status for ignition, doors, battery.
No OTP coming for login. Not able to delete the guest account.
These personas pull together the field-study and interview findings into the three needs the design had to balance.
I want to know the car is fine without having to start it.
Let me look around first. I'll sign up when I'm ready.
Both cars look the same in the app. And the text is so small.
When the app shows the wrong door status once, owners stop believing every other screen. More features would not fix that. Fewer, more reliable and better-prioritised ones would.
Status showed data 10 to 15 hours old, doors “open” when locked, and idle alerts for parked cars.
How might we make freshness visible and honest?
Home and Find My Car made up 65.8% of views but competed with 30+ features.
How might we put location and condition in one glance?
Engine, speed and geofence alerts arrived late or sat unseen in notifications.
How might we surface the exception the moment it matters?
Owners couldn't book after an update, couldn't find dealers, and saw costs that didn't match.
How might we make authorised service the easiest option?
58 violations, mostly consistency and clutter. Sloppy UI suggests sloppy data.
How might we give every screen one language that scales to new markets?
Prospective buyers had to register before seeing anything.
How might we capture leads at moments of real intent?
We turned the field study into one realistic journey. Ram and his family drive from Kochi to Bangalore: a weather check, tolls and FASTag, a low-fuel warning, a lunch stop, a lost car in a huge car park, a breakdown and a late arrival. Each moment shows where the app must help, and which features have to sit on Home.
Slides 35 and 36, stitched into one journey. Scroll sideways, or click to enlarge.
The journey map added the emotional curve and pain points to each step, split into before, during and after the journey.

Service booking was the biggest revenue opportunity and the most broken journey. This blueprint lines up what the owner does, what the app shows, and what Nissan does behind the scenes.
We agreed four design principles first, then moved from insights to solutions to wireframes. Each step kept a visible link back to the research, which made reviews with Nissan fast and objective.

In the brainstorming sessions, every idea had to travel the same path on one Miro board: from a real insight, to a solution, to its impact on users, on the business and on the planet. The Smart Drive Score shows how far one small insight can go.
Owners loved the Smart Drive Score in the first days, then stopped checking it. It gave them nothing back.
Turn the score into reward points. Good driving earns points.
Personal driving insights, and a reason to keep driving well.
Owners want to drive well, but nothing helps them get better.
Learn each owner's pattern (driving, score, fuel) and coach them: when to shift gear, how to use the clutch, how to accelerate.
Better drivers, less fuel burned, fewer risky moments.
Once free services end, owners leave authorised centres. They find them opaque and expensive.
Make reward points redeemable only at authorised Nissan service centres.
Owners come back for service and original parts, and pay less for it.
11.9% of all views went to the Smart Drive Score detail, the third most-used screen. The interest was already there.
Make the score the hero of Home, so the reward loop lives where owners already look.
Owners open the app more often, every day they drive.
Booking a service took 1 min 27 s, and often failed after app updates.
A rebuilt booking flow that takes under 25 seconds.
More service bookings through the app.
Smoother driving across the fleet means measurably less CO₂.
Convert the emissions saved into carbon credits.
Credits Nissan earns instead of buying, and cleaner air.
The owner gets rewarded for something they already wanted to do. The rewards can only be spent at authorised centres, which brings owners back to Nissan service and original parts. Better driving lowers emissions and risk, and those savings feed the next turn.
The two chains are the impact model we used to prioritise this idea. The full results are in Chapter 06.
We mapped every solution onto the before, during and after stages of Ram's journey. Features that came up at many moments, like status, Find My Car and fuel, earned a place on Home.

The team sketched many home-screen layouts and compared them against the principles before any pixels were drawn.

Paper kept the cost of throwing ideas away close to zero, which kept critiques honest.

We built a clickable wireframe prototype in Framer and Figma and put it in front of users and Nissan, to validate structure and flow early.

We grouped every feature by the owner's mental model and moved to a tab bar. Labels show only on the selected tab, because users recognise these icons by shape.
We wrote every feature of the old app on a sticky note and sorted them as a team, asking one question each time: where would an owner expect to find this? The analytics settled the arguments about what earns a place on Home.
The director board asked to see several versions of the home page. We ran brainstorming sessions and iterated from version 1.0 to 5.0, in light and dark. I presented each version against the principles and the research, so the discussion stayed on evidence rather than taste.









The final design keeps everything owners used and removes everything that competed with it. On the left is the app we inherited. On the right is the shipped design in dark and light themes.

1
2
3
4
5
6
7














The redesign uses the car's own data to make the app feel aware of the owner, not just connected. The first three are in the design. The last three are where I would take it next.
Rules on live telematics decide what appears on Home. Low fuel or open doors override the owner's pinned chips until resolved.
Trip data becomes positive feedback (“Great drive!”) that nudges smoother, lower-emission driving.
Service-due cards are driven by service schedule data, so the booking prompt shows up when it is relevant.
A conversational digital manual: “What does this warning light mean?”, answered in plain language with one-tap booking.
Ram's journey prepared for him: tolls, fuel stops and weather at the destination, before he asks.
Instead of “engine temperature high”, likely causes, urgency and the nearest authorised centre.
Midway through, Nissan's Europe team started a new design system for global use. Rather than ship a parallel one, we joined forces and built it together: typography, lists, cards, loading states, callouts and snackbars, in light and dark for iOS and Android. That shared foundation is a big reason the design could later travel to other markets.




We took Nissan through each original problem and the design decision that answers it, with the research behind it. That turned the review from opinions into a checklist the client could sign off.







We ran unmoderated guerrilla usability tests on the working prototype with owners across India's major car markets. They used it on their own, without a moderator steering them, which shows whether the design works without explanation.
What we measured after launch, compared with the previous two years of the old app.


The brief was a single-market redesign. When the results reached Nissan's directors, they made this design the benchmark for other countries. NissanConnect car apps in many markets now use the design we created for India.
The app's success earned us a usability review and redesign of the Nissan Kicks infotainment system. We used the same method: feature benchmarking against Qashqai, Rogue, Kia, Audi, BMW and MG Hector, owner and analyst reviews, and an expert review of each screen.
| What we found | Redesign direction |
|---|---|
| The back button doesn't exit camera mode. | One consistent back behaviour on every screen. |
| Volume only on the touch panel, slow to change. | Large, glanceable volume control. |
| Play controls dominate, but drivers use the steering wheel. | Hierarchy built for the co-passenger. |
| Crowded screens, mixed fonts, dull blues. | The app's design language on a calm dark base. |
| Rigid “Customise home menu”. | Widget home with map and music side by side. |





The biggest lesson: the design system was more strategic than any single screen. It is what let a one-market project become a global standard.