Designed for a gloved thumb in bad light, then checked on a bright day in a van.
Field software is usually a desktop form shrunk to fit a phone. The people using it are standing up, holding something else, and frequently out of signal — none of which the form knows about.
Capture comes first and structure comes later: the app takes the note, the photo or the number immediately and files it afterwards. Sync is shown as a property of each item rather than as a global spinner.
Reference landscape
- Apple Notes — Right about capture speed, no structure at all
- ServiceMax — Correct domain, desktop assumptions throughout
“Offline is a state of each item, not of the app.”
A single global 'offline' banner tells a user nothing about whether the thing they just recorded is safe. Per-item sync state answers the only question they actually have, and it removes the modal that usually blocks work until signal returns.
Stage by stage
01
User profiling
Shadowed four technicians for a day. Every one of them had a paper workaround for the same two screens.
02
Wireframes
Every primary action placed inside the bottom third, tested against a 6.1-inch device held one-handed.
What was difficult
Conflicts when the same job is edited offline by two people.
Both versions are kept and shown side by side with timestamps and authors. The app refuses to guess, because guessing wrong here loses evidence.
Exactly what you get
- Figma source
- 8 screens
- Light + dark
- Offline states
- Version
- 1.0.0
- Formats
- Figma, React, Tailwind
- Screens
- 8
- Components
- 16
- Dark mode
- Yes
- Prototype
- Yes
- Accessibility
- AA
Dependencies
- Inter — SIL Open Font Licence — included
Commercial fonts are never redistributed — they are named and linked, with a free equivalent substituted in the delivered files.
Notes captured in the field stopped being re-entered at the depot.