Mark each category as covered or missing
For one screen or workflow, mark whether empty, error, permission-denied, loading, offline, and invalid-input states are covered.
EDGE-CASE COVERAGE SCORE
Edge Case UX
Enter which edge-case categories are covered for a screen or workflow and get a coverage score plus the specific categories still missing.
- Uses your inputs in a transparent calculation
- Instant result with practical next steps
- No signup required
Planning guidance only. Validate important decisions with customer evidence and your delivery team.
YOUR INPUTS
Build your result
Complete every field. The result updates only when you choose Calculate.
How it works
We calculate a coverage score
Your score is the share of the six standard categories that are covered, out of 100.
Get the specific gaps to close
Any missing category is listed by name so you can hand a precise list to design or engineering, not a vague "handle edge cases" note.
Continue learning: How to design empty states for a new MVP · Designing helpful errors for MVP user experience
Frequently asked questions
Does Edge Case UX scan my actual screens or app to find edge cases?
No. Edge Case UX computes a coverage score entirely from the yes/no answers you give for one screen at a time. It does not parse an uploaded design file, screenshot, or live app, and does not run a real AI/LLM analysis step.
Why these six categories specifically?
Empty, error, permission-denied, loading, offline, and invalid-input states account for the large majority of "it looked done but broke immediately" issues reported after MVP launches. They are a practical minimum checklist, not an exhaustive edge-case taxonomy.
Can I check more than one screen?
Run the tool once per screen or workflow — each run gives a coverage score specific to that screen. Keeping it to one screen at a time makes the missing-category list precise rather than a mixed list across screens.
How is this different from State Craft?
Edge Case UX checks scenario-level coverage for a whole screen or workflow — what happens if there is no data, a request fails, permission is denied, or the network drops. State Craft checks the visual UI-state set for one component — loading, empty, success, warning, disabled, error. They overlap on empty and loading but Edge Case UX is scenario-driven and screen-scoped, while State Craft is state-driven and component-scoped.
What should I do with the missing categories?
Treat each missing category as a design and content task before development: what does the screen show, and what can the user do next, in that scenario. A one-line placeholder is enough to unblock a build if time is tight, but it should be a deliberate decision, not a silent gap.
How We Compare
| Feature | MVPHub | Figma | Balsamiq |
|---|---|---|---|
| Edge-case coverage score across 6 categories | Included | Not included | Not included |
| Named list of missing categories | Included | Not included | Not included |
| Design and prototype the actual screens | Not included | Included | Included |
| Component libraries for each state | Not included | Included | Limited |
Figma and Balsamiq are where the actual empty, error, and loading screens get designed once you know you need them. Edge Case UX runs before that — a fast checklist to confirm which of the six standard edge cases a screen accounts for, so nothing gets skipped before design work starts.
Related tools
Embed this tool
Add this tool to your site with the canonical iframe below. It remains hosted and maintained by MVPHub.