black-box-experience-reviewlisted

# Black-Box Experience Review ## Core Principle The app is a black box: evidence comes from observable behavior, never from source-code assumptions. ## When to Use Use when an app must be checked before shipping or after changes, and the question is whether real users can complete real work across happy paths and failure paths. The app is a black box: evidence comes from observable behavior, never from source-code assumptions. ## When NOT to use - Mapping journeys and seams first -> app-experience-mapping - Screen-level UI review -> ux-review - Visual styling or design tokens -> design-taste-frontend / design-system-audit ## Workflow 1. Functional round: walk each core journey end to end; the next action must be discoverable at every step. 2. Adversarial round: break each seam (unauthorized access, expired sessions, offline start, network loss mid-task, partial input, destructive actions without confirmation). 3. Coverage gaps: sweep every journey at narrow viewport and across channels. 4. State checks at every seam: loading, empty, partial, error, success. 5. Persistence and resumability: interrupted tasks resume where they stopped. 6. Handoffs and channels: return path works, partial failures recover, no state lost in transit. 7. Rate severity (Critical/Major/Minor/Enhancement) and issue the verdict: Pass, Needs Improvement, or Fail. ## Source-code independence Do not infer behavior from code. Drive the app as a user and record what is observable: screens, control