A mobile experience must account for context, attention and available actions. Shrinking a desktop interface is not enough for work performed away from a desk.
Choose the essential journey
For a fictional maintenance product, a technician needs to inspect a job, add an observation and confirm a step. Full team configuration may remain a desktop-oriented task. Decide what must work on a phone and what can reasonably wait.
| Constraint | Check |
|---|---|
| Limited space | Primary action is easy to identify |
| Open keyboard | Field and confirmation remain reachable |
| Interruption | Draft preservation follows an explicit rule |
| Variable connection | Saving status is truthful |
| Wide data table | Readable alternative or controlled scrolling |
Test realistic content
Include long names, several validation errors and an orientation change. Check zoom, touch targets and keyboard focus. Short placeholder text often conceals layout failures. Test the interrupted workflow rather than only a clean screenshot.
Is a native app required?
That depends on device capabilities, offline requirements and distribution needs. Describe those constraints before choosing implementation. Do not promise offline completion when actions still require a server response. A tested web workflow may meet the need, while other contexts justify a dedicated application.
Field work may resume on another device
A technician may begin on a phone and finish at a shared workstation. Define whether the draft follows the account, the device or neither, and communicate that behaviour. Test concurrent edits so continuity does not quietly overwrite another operator's work.
From this guide to your project
Product ↗
The experience connects your promise to the job your user needs to get done. We design that journey before adding more screens.
Tell us about your ideaExamples are educational and do not describe client results. Content prepared with AI assistance; see our editorial policy. Our method ↗