01 / THE CHALLENGE
Modernize without disrupting the job
Refresh an outdated Android driver application, then extend the product across Android and iOS while retaining the operational workflows and functionality drivers needed.
MOBILE PRODUCT DESIGN · LEGACY MODERNIZATION · CROSS-PLATFORM
Driver Mobile
An established driver application,
modernized in two design phases.
The project began with a branding and interface refresh of the original Android application, updating its visual presentation while preserving the functionality drivers already relied on. The subsequent phase expanded the experience across Android and iOS, retaining essential operational workflows while adapting the interface to Material Design and Apple's Human Interface Guidelines.
Case study in development
PROJECT AT A GLANCE
02 / MY CONTRIBUTION
Design across two modernization phases
Refreshed the original Android application's branding and interface, then developed coordinated Android and iOS designs based on shared operational requirements and platform-specific interaction patterns.
03 / KEY DESIGN DECISION
Preserve the workflow, adapt the interaction
Keep the essential operational logic consistent while adapting navigation, forms, selection patterns, validation, and system actions to each native platform.
04 / DESIGN OUTCOME
A refreshed product, then two native experiences
An updated Android interface followed by coordinated Android and iOS designs covering authentication, appointments, facility and equipment selection, review, and pre-arrival.
PHASE 01
Android Branding + Interface Refresh
Updated the original Android application's visual presentation and GEODIS branding while preserving its established functionality.
PHASE 02
Android + iOS Modernization
Expanded the experience across both platforms, establishing shared operational workflows with Material Design and Apple-native interaction patterns.
COLLABORATION Worked with development, product owners, management, business stakeholders, and the IT director responsible for overseeing software development and modernization.
In this case study
01 / Overview
The operational context behind the design.
GEODIS drivers used the application while managing appointments, facilities, equipment, and warehouse-related transportation tasks away from a desktop environment. The modernization needed to support that connected operational experience while respecting the requirements and familiar tasks of the existing product.
02 / Starting Point
From the inherited legacy application to the first Android refresh.
The original Android application was operationally functional but visually outdated. Its dense presentation, older interaction patterns, and legacy branding provided the starting point for an initial redesign focused on modernizing the interface without changing the underlying driver workflow.
STAGE 00 / INHERITED LEGACY APPLICATION
These were the original screens supplied to me. They establish the application's existing interface and operational workflow before my redesign work began.
01 / SIGN IN
Legacy authentication
The original entry screen provides evidence of the previous visual hierarchy and interface conventions.
02 / EQUIPMENT
Legacy equipment selection
The previous equipment interface provides a reference for evaluating selection clarity and task progression.
03 / REVIEW
Legacy appointment review
The original review screen provides a reference for evaluating information density and the presentation of operational details.
PHASE 01 / FIRST REDESIGN
My first redesign updated the Android application's branding and visual interface to align with GEODIS design standards and contemporary Android conventions, while retaining its existing operational functionality.
NEXT / CROSS-PLATFORM MODERNIZATION
The subsequent phase extended the refreshed experience across Android and iOS, establishing shared operational requirements while adapting the interface and interactions to each platform.
03 / Product Challenge
Modernize the experience without changing the operational job.
Following the initial Android refresh, preserve the operational workflow while modernizing the product across Android and iOS. Separate the stable workflow from the interaction conventions used to express it.
Legacy Experience
Existing operational tasks and product logic
Existing operational tasks and product logic
Shared Driver Workflow
Simplified progression and common architecture
Simplified progression and common architecture
Android + iOS
Native presentation and interaction
Native presentation and interaction
Clarity
Make the next task and current state easy to understand.
Efficiency
Reduce unnecessary interpretation and repeated decision-making.
Platform fit
Use conventions users already understand.
04 / Core Driver Journey
One connected journey from authentication to pre-arrival.
1Sign in
2Verify identity
3Find appointment
4Select facility
5Select equipment
6Review details
7Pre-arrive
8Save or share
Workflow principle
Every screen should answer two questions: Where am I in the task? What do I need to do next?
05 / Cross-Platform Strategy
One product architecture, two native experiences.
The Android and iOS experiences share task order, business rules, data relationships, validation logic, and completion states. They do not need identical interface patterns.
Android — Material Design
Designed for Android conventions
Material Design hierarchy, form behavior, selection patterns, spacing, surfaces, and action treatment make the workflow feel native.
Material form controls · Clear selection states · Native action hierarchy
iOS — Apple HIG
Designed for Apple conventions
Navigation, grouped content, selection behavior, field treatment, and system actions adapt to Apple expectations.
Compact navigation · Checkmark selection · Apple system actions
Shared product principle
Standardize the job to be done.
Adapt the interaction pattern to the platform.
06 / Authentication + Recovery
Trust starts before the operational workflow begins.
Authentication and account recovery were treated as part of the product experience. The source includes Sign In, Forgot Password, Verify Information, Reset Password, Validation Error, and End User License Agreement.
Clear entry
Give drivers a direct path into the application with obvious credential and recovery options.
Recoverable failure
Validation and authentication errors should explain what needs attention without dead ends.
Legal + account continuity
Required agreements and identity verification remain integrated into the mobile flow.
Android — Material Design
iOS — Apple Human Interface Guidelines
07 / Appointment + Facility
Reduce the operational search problem before asking for detail.
The flow separates discovery from downstream equipment and review tasks so drivers establish the correct operational context first.
Appointment search
Find the operational record that begins the workflow.
Facility selection
Confirm where the appointment will be handled before decisions continue.
Android — Material Design
iOS — Apple Human Interface Guidelines
08 / Equipment + Review
Make equipment selection explicit before commitment.
Separate tractor and trailer selection, then consolidate appointment, driver, carrier, and equipment information into review.
Select tractor
→Select trailer
→Review details
Recognizable equipment
Use readable names and visual selection states.
Clear state
Keep the selected option unambiguous.
Review before commitment
Bring operational information together before pre-arrival.
iOS — Apple Human Interface Guidelines
09 / Pre-Arrival + Completion
Carry the workflow through a clear operational finish.
Drivers continue into pre-arrival, choose how to retain or share information, and receive a clear completion state.
Review
→Pre-arrival options
→Success
Android can use Google Wallet and device download behavior. iOS can use Apple Wallet, Files, and system sharing. The product outcome remains the same.
Android — Material Design
iOS — Apple Human Interface Guidelines
10 / Native Platform Expression
Where native interaction patterns diverge.
The operational requirements remain consistent across Android and iOS, but the interface decisions reflect each platform's conventions. Facility and equipment selection illustrate how the same product behavior can use different native interaction patterns.
01 / FACILITY SELECTION
Outlined facility options use radio controls to make the current selection visible.
The grouped list uses a trailing checkmark to indicate the selected facility.
02 / EQUIPMENT SELECTION
Equipment options combine recognizable vehicle imagery with explicit selection controls.
Equipment choices retain the shared product meaning while expressing selection through the iOS list pattern.
11 / States + Accessibility
Operational clarity depends on more than the default screen.
A production mobile workflow needs to remain understandable when information is incomplete, invalid, unavailable, or successfully completed.
Loading
Make progress visible without changing task context.
Empty
Explain what is missing and what to do next.
Validation
Identify the field and provide correction guidance.
Error
Keep failure understandable and recoverable.
Selected
Make current facility, equipment, or option explicit.
Success
Confirm completion and preserve needed information.
Android
Readable scaling, meaningful semantics, touch targets, non-color-only states, and Material feedback.
iOS
Dynamic Type-aware hierarchy, VoiceOver-compatible semantics, target sizing, native controls, and non-color-only communication.
12 / Design System + Delivery
Translate one workflow into reusable platform systems.
Shared product behavior remains consistent while Android and iOS use distinct visual and interaction foundations.
Shared behavior
Define common workflow, validation, information, and completion logic first.
Platform mapping
Translate behavior into Android and iOS conventions.
Reusable components
Use platform foundations for fields, selections, surfaces, and state patterns.
Implementation alignment
Document behavior clearly enough to preserve intended logic.
Android foundation
Brand Primary #0047BB
Material Design
iOS foundation
GEODIS brand through native Apple conventions
Grouped surfaces · Apple-scale typography · 4–32pt spacing
13 / What Changed
What the modernization produced.
The work progressed from the inherited Android application through an initial branding and interface refresh and into a coordinated cross-platform product experience. The essential driver workflow remained central while the visual presentation, interface components, and native interaction patterns evolved.
DESIGN DELIVERABLES
01 / FIRST REDESIGN
Android Branding + Interface Refresh
An updated Android experience aligned with GEODIS corporate branding and contemporary interface conventions while preserving the established application's functionality.
02 / CROSS-PLATFORM MODERNIZATION
Coordinated Android + iOS Experience
Cross-platform designs organized around shared driver requirements, with platform-specific navigation, controls, equipment selection, validation, and completion interactions.
WHAT I'D CARRY FORWARD
01 / REFRAME, DON'T REPLACE
Preserve established operational requirements when they still serve users. Modernize the experience around them.
02 / SHARED WORKFLOW, NATIVE INTERACTION
Maintain consistent product meaning without forcing Android and iOS to use identical interface patterns.
03 / DESIGN FOR THE COMPLETE TASK
Review, confirmation, saving, and sharing are part of the operational experience—not secondary details.