Mobile Communication Experience
Mobile Communication Experience
Nexora
Nexora
My role
My role
Product designer
Product designer
The team
The team
PM, SA and UI Designer
PM, SA and UI Designer
Duration
Duration
10 month
10 month
Company & Product Context
The product is a mobile-first messaging platform used by distributed teams to coordinate daily work, share updates, and resolve issues in real time. Most users rely on the app while multitasking, often switching contexts between conversations, notifications, and other tools.
My contribution
Responsible for UX strategy, discovery, interaction design, prototyping, and validation across the mobile experience.
Company & Product Context
The product is a mobile-first messaging platform used by distributed teams to coordinate daily work, share updates, and resolve issues in real time. Most users rely on the app while multitasking, often switching contexts between conversations, notifications, and other tools.
My contribution
Responsible for UX strategy, discovery, interaction design, prototyping, and validation across the mobile experience.
The problem
Users struggled to keep up with conversations while on the move. Important messages were often missed due to visual noise, unclear hierarchy, and overloaded screens. Switching between chats, actions, and settings slowed down response time and increased cognitive load.
Core issue
The product exposed too much financial data without clear hierarchy. Users found it difficult to distinguish what required immediate attention from what could be reviewed later.
Business issue
If users couldn't communicate efficiently on mobile, engagement dropped and conversations moved to external tools. Improving speed, clarity, and reliability was critical to retain daily active users.
The problem
Users struggled to keep up with conversations while on the move. Important messages were often missed due to visual noise, unclear hierarchy, and overloaded screens. Switching between chats, actions, and settings slowed down response time and increased cognitive load.
Core issue
The product exposed too much financial data without clear hierarchy. Users found it difficult to distinguish what required immediate attention from what could be reviewed later.
Business issue
If users couldn't communicate efficiently on mobile, engagement dropped and conversations moved to external tools. Improving speed, clarity, and reliability was critical to retain daily active users.
Discovery
To avoid designing based on assumptions, I led a mixed discovery process focused on real mobile usage patterns.
Discovery
To avoid designing based on assumptions, I led a mixed discovery process focused on real mobile usage patterns.
Research methods
Customer interview
12 interviews with active mobile users to understand messaging habits, interruptions, and pain points.
Workshops
We ran collaborative workshops with product, engineering, and design to align on what "good mobile messaging" actually means.
Survey
A short survey to validate which data points must be visible.
Quantitative data
Review of product usage data to identify underused and misunderstood features.
User test
Moderated usability tests on early dashboard concepts to validate clarity and comprehension.
Research methods
Customer interview
12 interviews with active mobile users to understand messaging habits, interruptions, and pain points.
Workshops
We ran collaborative workshops with product, engineering, and design to align on what "good mobile messaging" actually means.
Survey
A short survey to validate which data points must be visible.
Quantitative data
Review of product usage data to identify underused and misunderstood features.
User test
Moderated usability tests on early dashboard concepts to validate clarity and comprehension.
Findings
Findings
Research highlighted recurring patterns in daily financial workflows.
Research highlighted recurring patterns in daily financial workflows.
Needs
Users prioritize speed over completeness
Users needed a small set of trusted metrics that summarize financial health.
Visual clarity directly impacts response time
Dense layouts and competing elements slow users down, especially in high-volume conversations.
Gestures feel more natural than controls
Dense layouts and competing elements slow users down, especially in high-volume conversations.
Pain points
Conversation overload
Users struggled to keep track of important messages when multiple conversations were active. Critical information was often buried under low-priority chats, causing delays and missed actions.
Poor message visibility
Unread messages were not visually distinct enough, making it difficult to quickly identify what required attention.
Needs
Users prioritize speed over completeness
Users needed a small set of trusted metrics that summarize financial health.
Visual clarity directly impacts response time
Dense layouts and competing elements slow users down, especially in high-volume conversations.
Gestures feel more natural than controls
Dense layouts and competing elements slow users down, especially in high-volume conversations.
Pain points
Conversation overload
Users struggled to keep track of important messages when multiple conversations were active. Critical information was often buried under low-priority chats, causing delays and missed actions.
Poor message visibility
Unread messages were not visually distinct enough, making it difficult to quickly identify what required attention.
Workshops: Vision alignment
Workshops: Vision alignment
We ran collaborative workshops with product, engineering, and design to align on what "good mobile messaging" means. The team agreed that the experience should optimize for: • Fast reading • Immediate action • Minimal visual noise Messaging was defined as an action-first flow, not a content-heavy interface.
We ran collaborative workshops with product, engineering, and design to align on what "good mobile messaging" means. The team agreed that the experience should optimize for: • Fast reading • Immediate action • Minimal visual noise Messaging was defined as an action-first flow, not a content-heavy interface.
Define, Valitation, iterate
Wireframing and testing
We started with low-fidelity wireframes to explore multiple layout directions. Each iteration was reviewed internally, then tested with users. Feedback was incorporated continuously, allowing the design to converge toward a clearer and more scalable solution.
Feedback from customers
Users highlighted the cleaner layout and faster interactions. They appreciated the reduced visual noise and the fact that important messages stood out more clearly.
Positive feedbacks
Usage
Users stayed focused on the main conversation, confirming the effectiveness of the simplified layout.
Message response speed
Replies were faster thanks to improved hierarchy.
Feedback from customers
Users highlighted the cleaner layout and faster interactions. They appreciated the reduced visual noise and the fact that important messages stood out more clearly.
Positive feedbacks
Usage
Users stayed focused on the main conversation, confirming the effectiveness of the simplified layout.
Message response speed
Replies were faster thanks to improved hierarchy.
Outcome and impact
The redesigned Live Operations view was rolled out progressively to a subset of FleetSync customers managing medium and large fleets. The new experience focused on improving situational awareness, reducing reaction time, and supporting faster decision-making during daily operations.
Outcome and impact
The redesigned Live Operations view was rolled out progressively to a subset of FleetSync customers managing medium and large fleets. The new experience focused on improving situational awareness, reducing reaction time, and supporting faster decision-making during daily operations.