Skip to main content
Find what can go wrong before your users do.
Edge cases are the situations a happy-path design misses: empty states, errors, slow connections, permissions, long names, and users who do things in an unexpected order. Figr looks at your screen or flow and lists the cases worth designing for.
1

Bring in what you want to check

Select a screen, flow or prototype on your canvas, or add a screenshot of a live screen with Add context in the chat box.
Checkout flow selected on the Figr canvas with the chat box open
2

Tell Figr your rules

If the flow depends on roles, limits or product rules, mention them in your message or attach the PRD, so Figr checks against how your product really works.
3

Ask Figr to map the edge cases

For example: “What edge cases should we design for on this checkout flow?”
4

Review the list

Figr lists the cases worth designing for, such as empty states, errors, permissions and data limits. Decide which ones need a design.
Edge case map for a checkout flow showing the happy path, errors and empty states

Figr maps the happy path and every state around it.

Map edge cases before handoff, not after. It’s cheaper to design an error state now than to fix it once it ships.
5

Design the ones that matter

Ask Figr to design the screens or states for the cases you picked. For example: “Design the payment failed and expired card states.”

​
Next

Generate test cases

Turn each edge case into a test.

Build a prototype

Design the states that matter.