Mobile & Desktop
Native mobile workflows
Field workflows rebuilt for one-handed use on a job site, fewer taps to log work, capture photos, and move a job forward.
Overview
Field techs work with one hand full and a phone in the other, so workflows built for a desktop slow them down. Thorbis is designing native mobile workflows tuned for the realities of a job site, big targets, fewer taps, and the next action always in reach. The goal is to let a tech update a job, snap photos, and collect a signature without fighting the screen.
What we're building
Field techs work with one hand full and a phone in the other, in bad light and worse weather. Workflows designed for a desktop and a mouse slow them down, too many taps, small targets, and the next action buried two screens away.
Thorbis is designing native mobile workflows tuned for the realities of a job site: big touch targets, fewer taps, and the next step always within reach. A tech can update a job, snap photos, and collect a signature inline without fighting the screen or mis-tapping. It is built for the field, for the people completing work orders standing up, not sitting at a desk.
What you'll be able to do
- Complete common job actions in fewer taps
- Reach primary actions one-handed
- Capture photos and signatures inline
- Move a job through its stages quickly
- Reduce mis-taps with larger touch targets
- Keep the next step within reach without digging through menus
- Cut screen-fighting that slows a job down
Rollout plan
- 01
Core actions reworked
In progressRebuild the most common job actions for one-handed, few-tap use.
- 02
Inline capture
In progressBring photo capture and signatures directly into the workflow.
- 03
Full job flow
In progressSmooth a job through all its stages on mobile with the next action always in reach.
Milestones
- Not started:
Workflow audit
Map the common field actions that need fewer taps.
- Not started:
One-handed layout
Design larger targets and reachable primary actions.
- Not started:
Inline media and signature
Build inline photo and signature capture.
- Not started:
Stage flow
Move a job through its stages quickly on the device.
More in Mobile & Desktop
How to send useful feedback
Name the blocked role
Product feedback is more useful when it names the owner, dispatcher, technician, office user, or customer affected.
Explain the workaround
Describe what your team does today and where the process fails under real work.
Define success
Share what would change after launch: time saved, fewer manual steps, cleaner records, or better customer follow-up.