Redesigned the driver mobile app to align with Rose Rocket's new web platform strategy—shifting from a one-size-fits-all driver tool to a flexible, config-driven experience that can support a wide range of workflows at a lower development cost.
Unlock extensive customization for the mobile app to support the unique workflows of existing and new customer segments at a lower development cost
DESIGN / EXPERIENCE GOAL
Adapt Rose Rocket’s web app patterns to React Native (e.g., boards, records, widgets), aligning with its config-driven architecture while preserving the core user experience
The process
My Contributions
STAKEHOLDER ALIGNMENT
Spearheaded and managed leadership alignment through building a case for evolving the driver app into a full mobile version of the web platform
CREATED SYSTEMS & PATTERNS
Adapted Rose Rocket’s web app platform patterns and layouts into React Native mobile equivalents to support a configuration-driven architecture
RE-BUILT THE CORE USE CASE
Created the core driver workflows using the updated mobile systems & patterns to ensure they support real world use cases
VALIDATED THE NEW APP
Validated the new app serves the existing end user equal to or better through internal usability testing and post-beta launch customer interviews
STAKEHOLDER ALIGNMENT
The New Mobile Direction
Existing mobile app
The existing app was built as an extension of our web product, tailored specifically for truck drivers. It enabled real-time collaboration and visibility between drivers and carrier companies, helping to automate manual tasks.
THE NEED TO PIVOT
In Fall 2023, Rose Rocket shifted from building a transportation management system specifically for carriers and brokers to focusing on a more flexible platform approach. That meant moving away from trucking-specific use cases and instead designing reusable, extensible components that could be customized and combined to serve any customer segment. This shift gave our go-to-market teams the ability to offer more tailored solutions to both and existing new customers segments, without needing heavy development support.
As the company shifted toward becoming a true platform, we had to ask a critical question: What role does mobile play in this new direction?
the new mobile direction
Path A
Rework backend - keep driver-only experience
•
Lower lift & fast
•
No behaviour change
•
Does not support scaling customization
Path B
Rebuild app as full mobile version of the platform
•
Scalable & supports all customer types
•
Aligns with web platform strategy
•
Higher upfront investment
•
Risk of diluting driver UX
After evaluating both paths—and reviewing 100+ customer requests—it became clear that Path B would better support experience and scalability:
DESIGN CHALLENGE
How do we create a mobile-first version of our platform that’s powerful enough for the business and intuitive enough for the people actually using it on the road?
CREATING SYSTEMS & PATTERNS
Adapting Rose Rocket's Web App Patterns
Mobile patterns & layouts
To design this mobile app, I needed to rethink how our three core platform patterns: boards, records, and widgets would translate to a smaller screen.
I began by researching how other companies translated similar patterns to mobile, then created mid-fidelity layouts to test with product and GTM teams. After aligning on the final approach, I applied the updated mobile design system to produce high-fidelity patterns and layouts.
Guiding design principles
Embracenative mobile behaviours: I leaned into intuitive, mobile-first patterns like vertical scrolling, persistent navigation, and full-screen takeovers to make interactions feel natural and familiar—especially for users with low tech fluency.
Reduce cognitive and visual complexity: I simplified dense, multi-column layouts into digestible cards, minimized decision points, and guided users through one clear action at a time.
Maintain functional parity, not visual symmetry: Rather than replicate the web experience pixel-for-pixel, I focused on delivering the same core functionality in ways that made sense for mobile—prioritizing clarity, focus, and task completion over consistency for consistency’s sake. Rather than replicate the web experience pixel-for-pixel, I focused on delivering the same core functionality in ways that made sense for mobile—prioritizing clarity, focus, and task completion over consistency for consistency’s sake.
Converting table view pattern from desktop to mobile
RE-building the core use case
Adapting Rose Rocket's Web App Patterns
Jobs to be done
Dispatch to driver
Share trip details with mobile app (what is being moved, what equipment is required)
Status updates
Share information with dispatch about the status of the trip
Collect documentation
As loads are picked up and delivered, share the documentation back to dispatch
DESIGN DECISIONS
Low tech familiarity
Larger font sizes & touchpoints by default to accommodate for fat thumbing in moving environments
Too much scrolling
On average, drivers receive trips with > 10 stops: Make it easier to find next action by auto-scrolling to the suggested next stop & task
Working in their ecosystem
Support easy navigation between other apps that drivers commonly use (maps, weather) via deep links and smooth transitions
New mobile app walkthrough
validating the new app
Internal Usability testing
COMPARATIVE USABILITY TESTING
What:
Comparative usability testing on a set of 5 core tasks with 5 GTM members (Video call w/ prototype walkthrough)
Goal:
Validate the proposed new app’s discoverability and usability is equal or better than the current mobile app
Outcome:
5 /5 users were more successfully able to complete requested tasks on first attempt with proposed new designs
INTERNAL USABILITY TESTING
What:
Usability testing of the entire app with 6 GTM members (Workshop style in meeting room)
Goal:
Improve experience faster by uncovering and calibrating on the most important UX gap
Outcome:
A prioritized database of 68 UX, UI, and bug improvements to fix before and after beta release
Built confidence amongst GTM of the new app experience to encourage beta user signups
New mobile app usability tests
The RESULT
Post Launch: The Impact
WHERE IS THE APP NOW
Successful migration
Successfully migrated 110 companies & 300 drivers to new mobile app
Lower development costs
Automatic inheritance of Platform capabilities immediately solved 56% of the classic NFRs - an effort that would take over 3 years building on the existing app
Customer satisfaction
Positive qualitative feedback from 3 active companies about overall usability and app customization features leading to greater retention
Increased revenue
Validated the new app serves the existing end user equal to or better through internal usability testing and post-beta launch customer interviews
What's next
While we now have a fully customizable mobile app, there’s still plenty of work ahead to refine the experience:
Incorporating feedback from beta customers (e.g., better offline data caching)
Expanding platform support on mobile—things like automations and bulk actions
Supporting new user roles beyond drivers, like dockworkers and warehouse staff
Integrating driver-centric features and delightful interactions that make the app feel intuitive and valuable
