Briefs · product
Pre-Launch App UX Audit
An exhaustive UX teardown of your app before you launch it.
You walk away with
A prioritised list of UX issues (P0–P3) with severity, owner and concrete fixes.
Decidi convenes
🙋 The End-User Advocate🔎 The UX Researcher🚀 The Onboarding Specialist♿ The Accessibility Advocate😈 The Devil's Advocate🧭 The Synthesiser
Recommended level: Deep — The newest, most capable models — for when being wrong is expensive.
What the council debates
We are about to launch an app and need a brutal, exhaustive UX audit before it goes live. APP / CONTEXT: [paste your screens, flows, or describe the app — include the primary user and the one job they hire it to do] PLATFORM: [iOS / Android / web / all] TARGET USER: [who they are, their context, their tech comfort] PRIMARY GOAL OF THE APP: [the single most important outcome for the user] Debate the user experience across these dimensions, disagreeing where you genuinely see it differently: 1. First-run & onboarding — time-to-value, signup friction, the "aha" moment, do we explain too much or too little. 2. Core flows — the happy path for the primary job; every place a real user hesitates, gets confused, or has to think. 3. State completeness — loading, empty, error, offline, success, and partial/missing-data states. Flag any screen that goes blank. 4. Friction & dead ends — taps that could be removed, forms that ask too much, moments a user would quit. 5. Retention hooks — what brings them back; is the loop real or wishful. 6. Accessibility — screen-reader support, focus order, contrast, touch-target size, motion, cognitive load. 7. Cross-platform correctness — back navigation, safe areas, keyboard handling, platform conventions. 8. Information architecture — is the navigation obvious; can a new user find the one thing that matters. FINAL SYNTHESIS must deliver: - A single prioritised issue list, each item with: severity (P0 = blocks launch / P1 = fix before launch / P2 = soon / P3 = polish), the affected flow or screen, why it hurts the user, a concrete recommended fix, and a suggested owner (design / eng / product / content). - The 3 things to fix before we are allowed to launch. - Anything that is actually fine and should NOT be touched, so we do not over-engineer.
Related briefs
Pre-Launch App UI Audit
A visual and UI teardown of your app — hierarchy, type, polish, dark mode.
Product Roadmap Prioritisation
Decide what to build next quarter and what to deliberately not build.
Feature Kill / Keep Decision
Decide whether to invest in, fix, or kill an underperforming feature.
Pricing & Packaging Strategy
Design pricing, tiers and the value metric that scales with what you deliver.

