May, 2026

Development of Moving map

The moving map is a core feature of the Mood product. It displays real time inflight information that passengers need such as remaining travel time, airports or stations, flight or train numbers, and traffic updates to help travelers throughout their journey onboard.

An illustrative sketch of a flower

Project Context

As part of a product optimization initiative for the Mood platform, I was tasked with redesigning the moving map. The goal was to display essential journey details to reassure travelers about their remaining travel time, featuring a clear visual representation of the route on the map. Additionally, the information panel needed to accommodate secondary details like current speed and outdoor temperature to complete the experience.

​

With the help of My Product Manager we gathered users feedbacks from our clients and prioritized it within a Jira ticket, providing full product context.

​

Based on this scoping, my core challenge was:

​

How can we structure a high volume of information to keep the moving map modal clean and intuitive, while ensuring it remains modular across both airline and railway contexts ?

Stacks used

Skills mobilised

Ux design

Information architecture

Design system

Design QA

Scalable components

Ia assisted design

User testing

Cross-functionnal collaboration

My process

01

Scoping & Discovery

Building a interactive map to display travel information to passengers.

02

Market Benchmark

Analyzed how key players in aviation, rail, and other transportation sectors (ride-sharing, urban transit) structure information during a journey.

03

Rapid Iteration

Leveraged Claude to generate multiple design directions by feeding it the Jira ticket and my top design inspirations, allowing me to explore more options in less time.

04

Testing & Validation

Conducted prototype reviews with my PM and Lead Designer to quickly rule out less viable directions. End up producing up to 15 versions of the modal before validating the optimal solution with the team.

05

Documentation

Formalized design decisions to maintain a clear roadmap, then built the new components into our design system with technical rules on behavior and usage for both design and developers teams.

06

Implementation Tracking

Supported the developers team through the integration phase all the way to production to ensure design QA and consistency.

Design Decisions

The moving map development focused on a modular panel that ensures consistency between airline and rail interfaces. It prioritizes ETA, delays, and arrival stations or gates. A pull-tab (or drawer handle) allows users to expand the panel to reveal secondary details, such as full trip metrics and remaining stops for both trains and flights.

​

The entire feature relies on a single master component capable of toggling elements on or off depending on the context (air vs. rail). This approach avoids duplicating logic across two separate components, making the design system significantly easier to maintain.

KPIS

The screens

Obsessed with...

Designed, written and developed with love © 2026 Nicolas Briot, All rights reserved.

May, 2026

Development of Moving map

The moving map is a core feature of the Mood product. It displays real time inflight information that passengers need such as remaining travel time, airports or stations, flight or train numbers, and traffic updates to help travelers throughout their journey onboard.

An illustrative sketch of a flower

Project Context

As part of a product optimization initiative for the Mood platform, I was tasked with redesigning the moving map. The goal was to display essential journey details to reassure travelers about their remaining travel time, featuring a clear visual representation of the route on the map. Additionally, the information panel needed to accommodate secondary details like current speed and outdoor temperature to complete the experience.

​

With the help of My Product Manager we gathered users feedbacks from our clients and prioritized it within a Jira ticket, providing full product context.

​

Based on this scoping, my core challenge was:

​

How can we structure a high volume of information to keep the moving map modal clean and intuitive, while ensuring it remains modular across both airline and railway contexts ?

Stacks used

Skills mobilised

Ux design

Information architecture

Design system

Design QA

Scalable components

Ia assisted design

User testing

Cross-functionnal collaboration

My process

01

Scoping & Discovery

Building a interactive map to display travel information to passengers.

02

Market Benchmark

Analyzed how key players in aviation, rail, and other transportation sectors (ride-sharing, urban transit) structure information during a journey.

03

Rapid Iteration

Leveraged Claude to generate multiple design directions by feeding it the Jira ticket and my top design inspirations, allowing me to explore more options in less time.

04

Testing & Validation

Conducted prototype reviews with my PM and Lead Designer to quickly rule out less viable directions. End up producing up to 15 versions of the modal before validating the optimal solution with the team.

05

Documentation

Formalized design decisions to maintain a clear roadmap, then built the new components into our design system with technical rules on behavior and usage for both design and developers teams.

06

Implementation Tracking

Supported the developers team through the integration phase all the way to production to ensure design QA and consistency.

Design Decisions

The moving map development focused on a modular panel that ensures consistency between airline and rail interfaces. It prioritizes ETA, delays, and arrival stations or gates. A pull-tab (or drawer handle) allows users to expand the panel to reveal secondary details, such as full trip metrics and remaining stops for both trains and flights.

​

The entire feature relies on a single master component capable of toggling elements on or off depending on the context (air vs. rail). This approach avoids duplicating logic across two separate components, making the design system significantly easier to maintain.

KPIS

The screens

Obsessed with...

Designed, written and developed with love © 2026 Nicolas Briot, All rights reserved.

May, 2026

Development of Moving map

The moving map is a core feature of the Mood product. It displays real time inflight information that passengers need such as remaining travel time, airports or stations, flight or train numbers, and traffic updates to help travelers throughout their journey onboard.

An illustrative sketch of a flower

Project Context

As part of a product optimization initiative for the Mood platform, I was tasked with redesigning the moving map. The goal was to display essential journey details to reassure travelers about their remaining travel time, featuring a clear visual representation of the route on the map. Additionally, the information panel needed to accommodate secondary details like current speed and outdoor temperature to complete the experience.

​

With the help of My Product Manager we gathered users feedbacks from our clients and prioritized it within a Jira ticket, providing full product context.

​

Based on this scoping, my core challenge was:

​

How can we structure a high volume of information to keep the moving map modal clean and intuitive, while ensuring it remains modular across both airline and railway contexts ?

Stacks used

Skills mobilised

Ux design

Information architecture

Design system

Design QA

Scalable components

Ia assisted design

User testing

Cross-functionnal collaboration

Design Decisions

The moving map development focused on a modular panel that ensures consistency between airline and rail interfaces. It prioritizes ETA, delays, and arrival stations or gates. A pull-tab (or drawer handle) allows users to expand the panel to reveal secondary details, such as full trip metrics and remaining stops for both trains and flights.

​

The entire feature relies on a single master component capable of toggling elements on or off depending on the context (air vs. rail). This approach avoids duplicating logic across two separate components, making the design system significantly easier to maintain.

KPIS

The screens

Obsessed with...

Navigation

Recent work

About me

Connexions

Design, writing and developp with love © 2026 Nicolas Briot, All rights reserved.