Skip to content
Tutorials Center
My learning

Topics

Lesson 25 of 36 ยท Wireframes and Prototypes

User Flows and Prototype Interactions

Map how users move through a product with user flows, task flows and screen flows. Cover happy paths, errors and edge cases, plus a runnable flow checker.

Screens are only half of a design. The other half is how people get from one screen to the next, and what happens when things go wrong. A user flow is a diagram of the path a person takes to complete a goal: where they start, the choices they make, and where they end.

Mapping flows before polishing screens catches missing steps early: the "forgot password" page nobody designed, the dead end after an error, the empty state with no way forward.

Kinds of flow diagrams

  • Task flow: one task, one user type, no branching decisions about who they are ("Reset a password").
  • User flow: a goal that includes decisions and alternate paths ("Sign up", with social login or email).
  • Screen flow: the screens themselves, thumbnails linked by arrows, close to a prototype.
  • Wire flow: wireframes combined with the flow, annotated.

Standard shapes: a rounded rectangle for start and end, a rectangle for a screen or step, a diamond for a decision, and arrows for movement. Label each arrow with the user action.

flowchart TD
  A(["Start: open app"]) --> B["Login screen"]
  B --> C{"Has account?"}
  C -- "Yes" --> D["Enter email + password"]
  C -- "No" --> E["Sign-up form"]
  D --> F{"Correct?"}
  F -- "Yes" --> G(["Home"])
  F -- "No" --> H["Error: try again or reset"]
  H --> D
  E --> I["Verify email"]
  I --> G

Figure: a login flow with decision diamonds and an error loop.

Happy path and beyond

Start with the happy path, the route where everything succeeds. Then add:

  • Error paths: invalid input, payment declined, no network.
  • Edge cases: very long names, zero results, a user who goes back mid-task.
  • Alternate entry points: arriving from an email link or a search engine, not the home page.
  • Interruptions: a phone call, session timeout, closing the app halfway.
  • Exit points: how the user leaves, saves progress or cancels.

A useful rule: every screen needs at least one way forward and one way back, and every error needs a way to recover.

A flow as data

A flow is a graph, so a small program can check it. The next stand-in stores a flow as a dictionary of screen to destinations and looks for two classic problems: dead ends (no way out) and unreachable screens (nothing links to them).

Python Find dead ends and orphans

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The checker finds payment_error (the user is stuck after a failed payment) and wishlist (a screen nobody can reach). Fixing the first means adding a "Try another card" arrow back to payment.

Prototype interactions

When you turn a flow into a prototype, you choose how each hotspot behaves:

  • Trigger: tap, long press, drag, hover (desktop), key press, a timer, or the end of an animation.
  • Action: navigate to a screen, open an overlay (modal, menu), scroll to a spot, go back.
  • Transition: none, dissolve, slide, push or smart-animate. Pick transitions that express direction: a forward step slides in from the right, going back reverses it.

Conditional logic and variables (available in advanced prototyping tools) let you fake things like a cart count or a validated form, and are worth using when the test depends on them.

A prototype with state

The empty state, the disabled button and the enabled state are three versions of one screen, driven by one variable. That is how a prototype with state works.

Flow review checklist

  1. Does every screen have a clear entry and exit?
  2. Is each decision shown with all its outcomes?
  3. Are errors and empty states included, with a way to recover?
  4. Can the user go back, cancel or save without losing work?
  5. Are there shortcuts for frequent users?

Take the flow into a test next: see usability test planning.

Check your understanding

Quick check ยท 3 questions

of 3 answered You scored / 3 ยท perfect!

  1. 1. What does a diamond usually mean in a flow diagram?

    Diamonds mark decisions with labeled outcomes.
  2. 2. What is a dead end in a flow?

    Users stuck on a dead end have no path to recover, which is a design bug.
  3. 3. Which should you design first?

    Establish the main successful route, then handle failure and unusual situations.

Summary

  • User flows diagram the path to a goal, including decisions and alternate routes.
  • Design the happy path first, then errors, edge cases, interruptions and exits.
  • A flow is a graph; look for dead ends and unreachable screens.
  • Prototype interactions combine a trigger, an action and a transition; variables fake state.

Next: Design Systems and Developer Handoff