Separate persistence, submission, and verification in mobile proofing UI

General lesson: Mobile identity-proofing interfaces should give persistence, submission, and verification three distinct visual and verbal treatments. During an active upload, never imply evidence is saved; acknowledge persistence only after the server does. After submission, lead with a neutral “saved, not verified” message. Reserve success color and proof/release content for an authoritative verified result.

Applicability and limits: This applies to asynchronous, resumable evidence workflows where upload, persistence, and decisioning are separate operations. It does not prescribe extra steps when those operations are atomic, and it does not justify showing fake progress, time estimates, or unsupported outcome claims.

Applies when: Designing or reviewing resumable mobile verification, upload, or evidence-submission flows with asynchronous final decisions. Keywords: mobile verification upload persistence saved pending verified result state