A fast migration from desktop-era workflows to native mobile work.
The launch proved the business case quickly: active users moved from web to mobile, time tracking became the most-used feature, and field support burden dropped sharply.
Near-total adoption in three months.
Prioritize on-site utility over desktop parity.
We did not try to shrink the desktop product into a phone. We selected the field workflows that had the most operational leverage: scheduled work, time tracking, job start/stop, notes, project/service details, and inventory picking with barcode scans.
The result: mobile became the default surface for active field users instead of an accessory to the web app.
The app centered the day around work that happens in the field.
For integrators, the job site is the real workspace. The mobile app had to make the most repeated tasks faster, calmer, and harder to lose track of.
Start and manage field work
Today's work, scheduled jobs, project and service details, status actions, rescheduling, and job start flows.
Log time where work happens
Clock-in, clock-out, add time entries, and browse time records from the phone instead of reconstructing work later.
Pick and scan inventory
Barcode scanning, scan-required states, quantities, project context, and item completion loops for field picking.
Field dashboard and schedule.
Clear cards, visible status actions, and segmented filtering keep high-frequency work easy to scan under real job-site conditions.
Native, quiet, and operational.
The mobile UI uses a light grey app canvas, white rounded cards, navy headings, muted secondary metadata, and green only for useful actions. It avoids visual drama because field users need confidence and speed.
Elwood, MO 12345Start Job
1 of 3 Items ScannedDone
Most-used feature, strongest validation.
Time tracking became the most-used feature after launch, validating the central product thesis: field users needed to log work in the moment, on-site, not back at the office.
Barcode scanning made picking field-ready.
Picking was designed around clear item context, required scan states, visible quantity and location, and strong confirmation when the item workflow was complete.
Design decisions were product decisions.
I worked closely with stakeholders and developers to prioritize what would materially change field behavior. The roadmap favored high-frequency operational moments over low-value desktop parity.
Less support, more confidence in the field.
Support tickets from field users dropped by 90% following launch. Beyond the numbers, field users and managers reported meaningful time savings, and early integrator feedback was strongly positive.
D-Tools Mobile moved the product closer to where work actually happens.
A first native iOS and Android app for integrators, designed and managed from strategy through shipped field workflows.