An industrial device in a delivery context.
The Zebra rugged Android handheld is a well-regarded enterprise device built for durability and data capture in warehouse and logistics settings. At UPS, it is used in both delivery and facility operations as an alternative to the purpose-built DIAD. Its larger screen and physical keyboard offer capabilities the DIAD does not, but those advantages come with trade-offs: a heavier form factor, a deeper menu structure, and an interface designed for industrial environments rather than the physical demands of parcel delivery.
We evaluated how well the Zebra serves drivers specifically, and where the gap between industrial design and delivery workflow creates friction.
Moderated testing + contextual observation.
We recruited active UPS drivers and warehouse staff across a range of Zebra experience levels. Participants completed realistic delivery and logistics tasks while we observed without intervention. Sessions included both indoor and outdoor conditions to test screen readability, and participants wore standard delivery gloves during relevant tasks to simulate real operating conditions.
Moderated Task Testing
Participants completed representative delivery workflows: scanning packages, processing exceptions, entering text, and navigating between stops. We measured task completion rates, time on task, and the number of touch errors per scenario, with and without gloves.
Comparative Observation
Where participants had DIAD experience, we asked them to complete the same task on both devices and observed differences in navigation strategy, confidence, and completion time. Spontaneous device comparisons from participants were treated as high-signal qualitative data.
The wrong tool for the job.
The clearest finding from testing was not a fixable interface problem. It was a mismatch between what the Zebra was built to do and what UPS delivery actually requires. Drivers with a choice consistently reached for the DIAD, citing familiarity and speed, not feature gaps. The Zebra's larger screen and physical keyboard, the features that differentiate it from the DIAD, were rarely engaged in the delivery context.
"With gloves on I have to tap the same spot two or three times before it registers. After a while you just start tapping harder."
Driver, observed during gloved task scenarioTouch reliability was the single most disruptive issue across sessions. Standard delivery gloves degraded tap accuracy significantly, turning a simple confirmation tap into a multi-attempt interaction. Drivers adapted by applying more force, which produced more errors, not fewer.
"On sunny days I have to literally turn my back to block the sun just to read the screen."
Driver, outdoor task debriefScreen readability in direct sunlight required physical workarounds from nearly every participant who encountered it. Drivers described shielding the screen with their body, stepping into shade, or memorizing navigation steps to avoid needing to read the screen at all.
"By 1pm my wrist is tired. It's noticeably heavier than what I'm used to."
Driver, end-of-session debriefPhysical fatigue was reported starting around the midpoint of a shift. Several participants said they leave the Zebra in their vehicle on heavier delivery days, reverting to the DIAD to reduce the load they carry between stops. A device that drivers choose to stop using mid-route is not delivering its intended value.
Where the device breaks down.
Severity 3: major barrier disrupting primary workflow. Severity 2: meaningful problem that should be addressed. Severity 1: cosmetic or minor.
Standard delivery gloves reduce tap accuracy dramatically. Participants averaged 2.4 taps per target while gloved vs. 1.1 ungloved. Drivers compensated with more force, which increased errors rather than reducing them.
5 of 7 participants used physical workarounds to read the screen in direct sunlight: turning their back, shielding with a hand, or stepping into shade. Brightness and anti-glare performance fall short of outdoor delivery conditions.
The Zebra's menu hierarchy is deeper and differently organized than the DIAD. Task completion for exception handling was 57% without assistance. Average time was 2m 42s on Zebra vs. 58s on DIAD for the same task.
5 of 7 participants mentioned weight without being asked. 3 said they leave the Zebra in their vehicle more often than the DIAD due to the load. Fatigue-driven device avoidance creates gaps in real-time delivery tracking.
The physical keyboard was used in fewer than 10% of observed text-entry tasks. Only 3 of 7 participants touched it at all. Its presence adds weight and form-factor bulk without delivering a meaningful workflow advantage.
Scan confirmation was missed or misread in noisy environments and during high-speed multi-package scenarios. 4 of 7 participants re-scanned at least one package per session due to uncertainty about the first scan's registration.
Battery level is not visible from main workflow screens. The delivery app's full-screen layout occludes the status bar indicator. 3 participants discovered low battery only when the OS alert fired.
Closing the gap between device and workflow.
The highest-priority changes address the two issues that directly prevent task completion: touch reliability with gloves and screen readability outdoors. Menu restructuring and battery visibility are meaningful improvements that reduce friction for drivers who do use the Zebra regularly. The physical keyboard finding is a longer-term hardware procurement signal, not a software fix.
-
1Increase touch target sizes and surface a glove-mode toggle
All tappable elements should meet a 48x48dp minimum. Enable glove-mode touch sensitivity in Android device settings and surface it as a quick-access toggle in the status bar so drivers can activate it without entering a settings menu.
-
2Improve screen visibility in outdoor conditions
Increase default screen brightness and verify that auto-brightness calibrates correctly in outdoor sunlight. Evaluate whether anti-glare screen treatment is feasible in the next hardware refresh cycle.
-
3Redesign the top-level interface for delivery task frequency
Surface the 5 to 7 most common delivery actions at the top level of the Zebra interface. Reduce menu depth for exception handling and signature capture. Consider a customizable quick-access toolbar for high-frequency functions.
-
4Strengthen scan confirmation feedback
Make the post-scan screen state change larger and higher contrast. Consider a brief full-screen color flash on a confirmed scan. Ensure vibration feedback is not inadvertently disabled by device management policies.
-
5Surface battery percentage within the delivery app
Display battery level in the app header or as a persistent overlay during workflow screens. Add a low-battery notification within the delivery app itself rather than relying on the OS-level alert, which arrives too late for route planning.
-
6Evaluate device weight as an ergonomic and procurement consideration
Document physical fatigue as a documented ergonomic risk and include it in future hardware procurement criteria. Pull production telemetry on how often drivers carry the Zebra vs. leave it in the vehicle to quantify the scope of the avoidance behavior.
Test Plan
UPS Zebra Rugged Handheld Usability Test Plan
Findings
UPS Zebra Rugged Handheld Usability Findings