← All case studies
Pallet TMS
·
iOS
·
2025
Pallet Driver App: Multiple Routes
Intuitively redesigning a logistics driver app so drivers can run their whole day, not just one route.
Design System Upgrade
iOS
The 30-second version
0:30 read
Role
Product Manager and feature designer
Team
1 engineer
Timeline
9 weeks
Platform
iOS
Problem
Pallet's iOS and Android driver app had an outdated interface and a one-route-per-day model that didn't match how carriers actually dispatch.
13%
inquiry reduction
26%
feature adoption
$67k
revenue unlock
01 Context
An AI-powered platform running logistics operations end to end.
Pallet (now Tenet-OS) is an all-in-one transportation and warehouse management system (TMS and WMS) that uses AI to help logistics businesses streamline their operations, from order entry and driver dispatch to inventory and accounting.
02 Problem
The mobile app had fallen behind the platform it was built for.
The driver app is where drivers see their day and receive instructions from warehouse operators. As the web app matured, the mobile experience fell behind: it was visually disconnected from the rest of the platform and missing features teams relied on.
The core constraint: the app could hold only one route per driver per day, but drivers often run more, such as a morning route followed by an afternoon appointment route. With only one route visible, ddrivers couldn’t plan beyond their current route.
03 Solution
I owned the redesign end to end, from discovery to visual design and customer rollout.
I owned the feature from end to end, including discovery, requirements, user flows, interaction and visual design within Pallet's updated design system. Pallet's systems assumed one route per driver per day, so with my engineer, I audited the features that depended on that assumption and that audit set the constraints for the design.
The final design keeps the original information architecture, so existing drivers didn't have to relearn the app, and concentrates changes where they matter most. The flow follows a driver's day: see everything, start one route, work its stops, finish, and move to the next.
One route in progress at a time; the rest are view-only. This prevented data issues in parts of the system built around a single active route.
Drivers complete a route themselves. With only one active route, drivers need an explicit way to close it out and unlock the next. I prioritized a manual Mark Route Complete action over automatic route completion
04 Result
Drivers adopted multiple routes, and support tickets dropped 13%.
The work unblocked 2 key deals in our sales pipeline. Shipped alongside broader app system improvements, the release was followed by a 13% decrease in customer-raised support tickets for the mobile app along with 26% feature adoption over the next 3 months.
Next
More case studies.
All case studies →