Mobile verification UX should collapse ceremony around the next required action

General lesson: In a resumable mobile identity-verification flow, speed and confidence improve when every screen exposes one required task, one primary action in thumb reach, and one contextual recovery path. Keep dynamic requirements truthful instead of previewing a universal checklist; treat camera frames as positioning guidance rather than exact decoder boundaries; advance loading states only from real work; and make submission-received/pending visually and verbally distinct from verified.

Applicability and limits: This applies to browser-based document, selfie, and location flows with dynamic requirements and server-backed resume. It does not justify removing required evidence, consent disclosures, GPS enforcement, or authoritative release gates. Any claim about faster completion or better conversion still requires driver testing and defined funnel metrics.

Applies when: designing mobile proofing journeys with dynamic evidence, permissions, resumability, and asynchronous verification. Keywords: mobile verification driver UX capture location help pending verified