Loris
Olivier

Nissan Box

One app for drivers to manage their thermal or electric Nissan

Role

Product Design · User Research · Motion Design

View of the Nissan Leaf car
Superposition principles and screen structure
Nissan Box: A screen of the app

Key figures

+12%Users

My work with the ACMS teams on two new Nissan applications contributed to this increase.

3 monthsOf research

Research, analysis and user interviews before and during design.

My role and context
Role

Product design and user research.

  • Product design
  • User research
  • Motion design
Where

Tokyo and Paris, with the ACMS teams.

Methods

User interviews, assumption mapping, interactive prototypes, screen tests with attention heatmaps, and workshops with stakeholders and engineers.

  • User interviews
  • Prototype sessions
  • Screen tests
  • Heatmaps

01

The stakes

Thermal and electric vehicles, different models, one application.

The brief

Nissan Box serves drivers of both thermal and electric Nissan vehicles. A single application had to adapt to very different models and needs, from checking a car's status to controlling it remotely.

Electric vehicle status screen over a mood board
_05

Art direction: an electric-vehicle status screen (charging time, range, battery) and its mood board.

One app, two kinds of vehicles
Three dashboard explorations side by side: an electric car showing battery charge and a start-charging action, a thermal car showing fuel level and a start-engine action, and a list layout of battery, climate and vehicle status.
Early explorations: the same dashboard for an electric car (charge, start charging) and a thermal one (fuel level, start engine).
Map of the thermal-car app connected through a dongle: dashboard, vehicle health, driving history and fuel, virtual garage and menu, in four levels, with open questions marked.
The thermal (ICE) version, connected through a dongle: its map, four levels deep, with open questions marked.

02

Research

Three months with drivers before designing.

How we learned

3 mo.Research and analysis

Three months of research and analysis.

254User interviews

Interviews with drivers.

5Prototypes

Prototypes built to engage users in the conversation.

56Screen tests

Testing and studying screens, including attention heatmaps on the dashboard.

Research in numbers

254Drivers interviewed

78 in the US, 127 in Japan and 49 in France.

56Test sessions

32 in France and 24 in Japan, with prototypes and scenario-driven interviews.

4Markets targeted

The US, Canada, Europe and Japan.

Research method
Research method in six stages: 254 driver interviews (127 Japan, 78 US, 49 France), a synthesis kept under NDA, 56 prototype sessions (32 France, 24 Japan), screen tests with attention heatmaps, four design rules, and validation where 76% of drivers completed all 6 tasks.
The research method, from interviews to validation. The synthesis and journey maps stay under NDA.
Assumption mapping
Whiteboard with sticky notes grouped under themes: Settings, Help and support, Holistic experience, Notifications, Dashboard and Remote.
Assumptions about drivers, grouped by theme: remote, dashboard, notifications, settings, support.
The same sticky notes placed on a matrix from low to high risk and from known to unknown, most of them clustered in the high-risk, unknown corner.
Then placed by risk and by how much we knew, to decide what the prototypes had to test.
Whiteboard sketch of a funnel from common needs to features to prototype, next to a test plan in three layers: user needs, behaviour and usability.
The funnel from common needs to features to prototype, tested in three layers: needs, behaviour, usability.
Five prototypes
User-test plan: prototype 1 tests overall usability with about 120 screens; prototypes 2 to 5, about 14 screens each, test the widget manager, a simpler structure, one-tap remotes and clustered remotes on the dashboard.
The user-test plan: one full prototype for overall usability, four short ones that each change one part of the structure.
Research artifacts
The first wireframes with 16 numbered elements on the dashboard, next to a menu and a settings screen, with unclear paths flagged in red: Notifications? Settings? Where does it lead?
Review of the first wireframes: 16 elements on one screen, and the unclear paths flagged in red.
Attention heatmap over an early dashboard, with the car status, battery and remote actions drawing the most attention, next to the screen variants that were tested.
Attention heatmap on an early dashboard, next to the variants we tested.

03

What research changed

Three findings that moved the app away from a remote control.

Insight 01 — Priorities

Drivers cared less about instant actions than about managing the car over time.

Before

The brands wanted the new remote functions at the forefront: open the car, start it, prepare a playlist.

Research showed

Instant actions were secondary, or even less than that. What mattered more to drivers was calculating their consumption and managing the vehicle over the long term.

We built

Fuel consumption and vehicle health got their own screens, with a workflow to reach the detail of every point, while the remotes stayed within reach.

Insight 02 — Parking

A car parked in a public place is a worry drivers want to monitor.

Research showed

Safety when parked in public areas was a priority, especially if it could be monitored from the app. Drivers wanted both the inside and the outside context of the car while it was parked.

We built

Inside: the lock status of every door, the power status, the GPS location and the latest lock and unlock actions. Outside: the images of the parking cameras, on the models that have them.

Result

The cameras brought visual information into the app and reassured drivers.

Insight 03 — Trust

Drivers would only rely on fuel and vehicle health if they could trust the data.

We assumed

Drivers were sceptical at first about an app handling vehicle health and fuel level.

Research showed

Once they could rely on the precision of the data, these became the two central features of their usage. They needed to be reassured.

We built

Timestamps that anchor each figure in reality. A fuel report every time the driver enters the car or opens consumption. A reload option on every health status, to know when it was last checked. A button to ask partners, garages and mechanics for feedback on a health feature.

Result

The information no longer stays isolated in a phone: experts can look at it.

04

Product decisions

What to put first, and getting three regions to agree.

Decision 01

The remotes stay in reach, but no longer at the centre.

North America, Europe and Japan wanted the remote functions at the forefront, because they introduced new technology to activate the car remotely. Research said drivers' priorities were elsewhere.

Remotes as the heart of the dashboardPartly kept

Kept always accessible, with a clear tap affordance, but no longer the main subject of the app.

Fuel consumption and vehicle health on their own screensShipped

Each with a workflow to reach the detail of every point. Consumption: when fuel was used most, the speed at the time, the location. Health: oil, brakes, wheel pressure, battery level and health, and where a potential issue may come from.

Aligning three regions

I mapped the features the brands required against the features the mechanical engineers could actually provide, and reviewed UI and branding proposals, user journey maps and the app architecture. Interactive prototypes went to the stakeholders, and I travelled to Austin and Detroit for workshops to align the teams of the different countries.

Two workshops then brought all 42 stakeholders together to confront their own prototypes with my synthesis of them. The discussion led to minor changes, and consolidated the international vision of the app.

Information architecture
App map in five levels: splash screen and onboarding, the dashboard, then My Car, virtual garage, profile, assistance, navigation and You+Nissan, down to settings, notifications and trip history.
The app map, five levels deep: from the dashboard to My Car, garage, profile, assistance and navigation.
Five directions
Five dashboard directions side by side: status rings, list cards, a lighter list, a map view and a sectioned grid with actions on the right.
Five directions for the dashboard: status rings, list cards, a map view and a sectioned grid.
Iteration 02
Three dashboard layouts showing the same charge, range, temperature and lock status around the car, with the remote buttons below.
Three layouts for the same data around the car.
Themes and states
The same dashboard in dark, light and brand red themes.
Each layout explored in dark, light and brand red.
Two states of the dashboard: a damage alert card in the header with a call button, and a green banner confirming the car was unlocked.
A damage alert takes the header; a command confirms in place.
Layout principles
Superposition

Only one superposition per screen: highlighted content on top, dynamic content below.

Header

Superposed and graphically prominent; identifies the car.

Remotes

Always accessible, with a clear tap affordance.

Widgets

Built for longer reading and accessibility, square themes, and quick thematic identification.

Superposition principles and screen structure
Superposition principles and screen structure.
The final app
Final Nissan LEAF dashboard: a red header with the car, a battery bar at 75%, remote actions (lock, charge, climate, light and horn), and widgets for battery, vehicle health, temperature, monitoring and driving history.
The final dashboard: header, remotes always within reach, and widgets.

Usability

76%Task success

Of drivers completed all 6 tasks in tests.

No store rating: the app was withdrawn when the digital services were split between regions.

05

Design engineering

Prototypes in code, and the data behind them.

What I built
Prototypes

I coded all the prototypes that were not made in Prott or Sketch.

Data

I ran workshops with the mechanical engineers to learn how to get each piece of data, and what they thought was realistic to show in the app.

Design system

On Nissan Box, I designed the app's design system: components and tokens, documented in Figma, and prepared for my engineering colleagues and for AI agents, so that design and code start from the same source.

06

Outcome

More drivers on the apps.

Who it helped
Drivers

Thermal and electric drivers each see what matters to them in one app, shaped with 254 drivers in three countries: 76% completed all 6 test tasks.

Nissan

More drivers on its apps: a 12% increase in users, a team result with the ACMS teams.

+12%Users

My work with the ACMS teams on two new Nissan applications contributed to a 12% increase in users.

What I would do differently

I would run workshops where drivers build prototypes together with us, with simple paper, tape, scissors and markers, to let their own initiative emerge.

Explore case studies

Explore other projects

Contact

For a project, a collaboration or a question about my work, send me a message.

CV

My experience, roles, skills and education on one page.

Case studies

  • Open Brain Institute

    Open Brain Institute: a virtual lab platform that turned hard-to-read brain models into one place to explore, simulate and validate them. More than 1,200 labs adopted it.

  • Swiss Brain Observatory

    Swiss Brain Observatory: a guided path to connect neural circuits and build connectomes, from a single neuron to the whole brain, replacing a long and complex process.

  • Nexus Fusion

    Nexus Fusion: a data platform that links research data by provenance, replacing terminal-only access. Now 94% of published data gets viewed.

© 2026 Loris Olivier