A mobile flow must work while permissions are denied, networks weaken, devices sleep, keyboards resize the viewport, uploads pause, and people leave midway through a task.
Responsive layout is only the visible layer. The playbook treats device capability, permission, local state, sync, and interruption as product behavior.
Define where, when, and how the task happens—not only what the finished screen should contain.
Exit when: the team understands the physical and technical conditions surrounding the user decision.
Define capture, draft, validation, upload, sync, conflict, correction, completion, and recovery states.
Exit when: every material interruption has an intended state, explanation, and recovery path.
Deliver capture, local preservation, review, correction, synchronization, and confirmation as one slice.
Exit when: the task remains useful after one ordinary interruption and one network failure.
Emulators accelerate coverage; supported physical devices verify the behavior people will actually experience.
Exit when: supported device evidence—not responsive-browser inference—meets the acceptance criteria.
Segment completion, abandonment, crash, permission, sync, and correction evidence by meaningful device conditions.
Repeat when: platform updates, device evidence, or real field behavior invalidates an assumption.
The feature is not “add photo upload.” The product task is a recoverable inspection that remains trustworthy under interruption.
Create an inspection draft before requesting media or network access.
Explain camera or microphone permission at the moment its value is clear.
Save photos and notes locally with visible upload state.
Show AI-extracted details as suggestions the inspector can correct.
Retry idempotently and reconcile conflicts without duplicate records.
Show completion only after the durable remote state is verified.
Result: the field task survives actual mobile conditions instead of succeeding only in a connected demo.
Test the interface, device, and service as a connected system.
The internal-tool playbook adds approval, escalation, audit, and operational authority to the same five-stage method.