UI/UX16 min readPublished

User Flow Examples: 12 Real Flows From SaaS and App Projects (With Diagrams)

12 user flow examples from real SaaS, fintech, health and logistics products, with diagrams, edge paths and the metric to track for each flow.

Maniruzzaman JubayerManiruzzaman JubayerCo-founder & COO | Product Design Specialist
Summarize with
User flow examples cover showing the Wolfpixel web app design page on a laptop, with the title in cream and yellow on a dark background.

A user flow is a diagram of the steps a user takes inside a product to complete one task, such as signing up, booking an appointment or upgrading a plan. Nielsen Norman Group describes it as the typical or ideal set of steps needed to accomplish a common task with a product. A good one also shows the decisions, errors and exits along the way.

I’m Maniruzzaman Jubayer, Co-founder & COO and Product Design Specialist at Wolfpixel, with 7 years of experience. Most user flow examples online are redrawn from Zoom, Slack or Amazon. Every example below comes from a product we designed, from a delivery app to an AI automation platform, so you can see the flow next to the case study it shaped.

The short answer: a user flow maps one user, one goal and every step between them. The 12 examples below cover ordering, booking, onboarding with identity checks, automation, approvals, payouts and website conversion. Each one lists the steps, the edge paths a complete flow needs and the metric that tells you whether the flow works.

Key takeaways:

  • One flow, one goal. If a diagram tries to show signup and upgrade at once, split it.
  • Draw the decisions and error paths, not just the happy path. That is where most products lose people.
  • Pick the metric before you design. Each flow below ends with the number we would track.
  • Use the same symbols every time, so anyone on the team can read any flow.
  • Map flows before screens. Fixing a flow on a whiteboard costs minutes. Fixing it in code costs a sprint.

How we wrote this: we reviewed the pages ranking for this topic in November 2026, including Userpilot, Matomo, Figma and Appcues, and the Nielsen Norman Group research they rely on. The 12 flows come from our own case studies, and each one links to its project. The edge paths and metrics are our recommendations for flows of that type, not results reported by those clients. The full list is in Sources and method.

What is a user flow?

A user flow follows one person through one task in your product. It starts at an entry point, such as opening the app or landing on a page, and ends when the goal is reached or the person leaves. In between, it shows each screen or step, the actions the user takes, the decisions the product makes and the paths that branch off when something goes wrong.

User flows are a working tool, not a deliverable to admire. Designers use them to agree on structure before drawing screens, product managers use them to scope features, and developers use them to see every state they need to build. In our own process, flows come before any visual design. On RoomMind AI, for example, low-fidelity wireframes and user flows set the structure of the whole redesign journey before a single screen was styled.

User flow vs task flow vs wireflow vs journey map vs flowchart

These terms overlap, and briefs often mix them up.

What it shows Zoom level Best for
User flow Steps, decisions and errors for one user and one goal One task in the product Agreeing on structure before design
Task flow A single linear path through one task, often without branches Narrower than a user flow Quick alignment on one action
Wireflow Wireframe-style screens connected by flow arrows A few screens Showing what changes on each screen
Journey map Stages, touchpoints and emotions across channels and time The whole relationship Finding where the overall experience breaks
Flowchart Any process, using standard symbols Anything Logic, systems and operations

Nielsen Norman Group draws the key line between the first and fourth rows: user flows zoom in on specific, discrete interactions, while journeys cover experiences across channels and over time. It describes wireflows as a format that combines wireframe-style page layouts with a simplified flowchart, a practice that emerged from mobile app design. If you need the wider view, our guide to the B2B customer journey map covers it.

How to read the diagrams in this guide

Every diagram below uses the same symbols. They follow standard flowchart conventions, which ANSI set in the 1960s and ISO later published as ISO 5807, with one addition for error paths.

User flow diagram legend: rounded shapes mark the start and end, rectangles are screens or steps, diamonds are decisions, parallelograms are user input, solid arrows show the main path and dashed red lines show error or edge paths.

Symbol Meaning
Rounded shape Start or end of the flow
Rectangle A screen or step
Diamond A decision, by the user or the system
Parallelogram Information the user enters
Solid arrow The main path
Dashed red line An error or edge path

12 user flow examples from real products

Each example names the product, the user’s goal, the steps, the edge paths a complete version of the flow needs, and the metric we would track.

1. Ordering a delivery in a logistics app (Shipora)

Product: Shipora, an AI-powered parcel delivery app. Goal: send a parcel without filling in a long form.

  1. Open the app on a map.
  2. Enter the pickup location.
  3. Enter the drop-off destination.
  4. Choose a service from cards that show the price up front.
  5. See the route preview with an estimated arrival time.
  6. Confirm the order and land on the tracking home screen.

Shipora parcel ordering user flow: open the app, enter pickup and drop-off, choose a service with the price shown, preview the route and ETA, confirm and land on tracking, with error paths for an address outside the service area and a failed payment.

Edge paths to design: an address outside the service area, no service available at that time, a payment that fails at confirmation. Metric to track: order completion rate from opening the map to confirmation.

What makes this flow work is that the price appears on the service card, before confirmation. Showing the cost late is one of the most common reasons people abandon an order at the final step.

2. Checking where a parcel is (Shipora)

Goal: know where the parcel is without contacting support.

  1. Open the app.
  2. The home screen leads with the active shipment: ID, origin, destination and estimated arrival.
  3. Follow progress on a simple line between the points.
  4. Receive status notifications as the parcel moves.

Edge paths to design: a delayed delivery, a failed delivery attempt, more than one active shipment. Metric to track: “where is my parcel” support contacts per hundred orders.

The design choice here is placement. Tracking is the first thing a returning user sees, not a screen behind a menu.

3. Booking a doctor in a health app (CareUp)

Product: CareUp, an AI-powered healthcare app. Goal: book an appointment with the right specialist.

  1. Open the home screen, which starts with “Search for a Doctor.”
  2. Search, or tap a specialty chip such as Cardiologist.
  3. Compare doctor cards showing specialty, rating, experience, working days and price.
  4. Pick a day from the day picker on the doctor card.
  5. Follow the short booking sequence and confirm.

CareUp doctor booking user flow: home, search or specialty chip, compare doctor cards, pick a day on the card, choose a time and confirm, with edge paths for no free slot and no matching doctor.

Edge paths to design: no free slot on the chosen day, no doctor matching the filters, the user leaving mid-booking. Metric to track: search-to-booking conversion.

Putting the day picker on the doctor card turns choosing a date into part of browsing, which removes a whole step from the flow.

4. Redesigning a room with AI (RoomMind AI)

Product: RoomMind AI, an AI interior design iOS app. Goal: see a room redesigned in a chosen style.

  1. Choose the room type: living room, bedroom, kitchen or office.
  2. Upload a photo from the camera or gallery.
  3. Watch the AI scan confirm what it captured.
  4. Choose a style from photos of real rooms.
  5. Choose a plan, including a free option.
  6. Get the result and compare before and after.

Edge paths to design: camera permission denied, a photo too dark or blurry to scan, generation taking longer than expected. Metric to track: share of uploads that reach a finished result.

5. Launching an AI automation from a template (Axon)

Product: Axon, an AI workflow automation platform. Goal: put a new automation live without breaking anything.

  1. Browse the template library, filtered by team.
  2. Preview the workflow: every step, the apps it needs and where human review happens.
  3. Customize the steps in the Workflow Builder.
  4. Run it in a sandbox Test Run.
  5. If the test passes, go live. If not, return to the builder.

Axon automation user flow: browse templates, preview the workflow, customize in the builder, run a sandbox test, then a decision: if the test passes the workflow goes live, if it fails the user returns to the builder.

Edge paths to design: a missing app connection, a test run that fails on one step, permissions that stop a user from publishing. Metric to track: share of previewed templates that go live.

The sandbox step is a deliberate loop. In automation, a safe place to fail is what makes people confident enough to launch.

6. Reviewing an AI exception (Axon)

Goal: decide what to do when the AI was unsure.

  1. Open the Overview, where items needing a decision are ranked high, medium or low.
  2. Open an item in the Review Queue.
  3. Compare the source document with the extracted fields and evidence, side by side.
  4. Approve, or reject with a reason.
  5. The decision is recorded in the audit log.

Edge paths to design: missing evidence, a reviewer without permission to approve, a queue with no items. Metric to track: time from exception to decision.

7. Launching an affiliate program as a merchant (Earnify)

Product: Earnify, an affiliate growth platform. Goal: get a program live and start approving affiliates.

  1. Create the program in a short setup flow.
  2. Launch a campaign.
  3. Review new affiliate applications on the dashboard.
  4. Approve or decline each one.
  5. Track clicks, revenue and payouts on the dashboard.

Edge paths to design: an incomplete program setup, an application missing details, no applications yet. Metric to track: time from signup to the first approved affiliate.

8. Earning a payout as an affiliate (Earnify)

Goal: find an offer and get paid for promoting it.

  1. Browse offers.
  2. Apply to an offer.
  3. Once approved, follow clicks, conversions and revenue.
  4. See what has been earned and when the payout will arrive.

Edge paths to design: an application declined, a payout on hold, a conversion disputed by the merchant. Metric to track: share of approved affiliates who reach a first payout.

Two flows from one product is common in marketplaces. The merchant and the affiliate want opposite things from the same screens, so each needs its own flow.

9. Running a task from posting to payment (OpsLoop)

Product: OpsLoop, a micro-task management platform. Goal: get work done and paid for, with quality checked.

  1. Create a task.
  2. Manage it while workers pick it up.
  3. Review the submitted work.
  4. If approved, pay. If not, send it back with feedback.
  5. See the result in reports.

OpsLoop task lifecycle user flow: create a task, manage it, review the submission, then a decision: approved work goes to payment and reports, rejected work goes back to the worker with feedback.

Edge paths to design: no worker picks up the task, a missed deadline, a budget that runs out. Metric to track: task cycle time from posting to payment.

10. Completing a task as a worker (OpsLoop)

Goal: find work, finish it and get paid.

  1. Open the dashboard: tasks available today, completed tasks and today’s earnings.
  2. Browse the task marketplace.
  3. Open task details.
  4. Do the work in the task workspace.
  5. Submit, then follow payment and badge progress.

Edge paths to design: a task taken by someone else first, a submission sent back for changes, a payment delay. Metric to track: tasks completed per active worker per week.

11. From website visit to trial or demo (Zyntra)

Product: Zyntra, an AI customer service SaaS website. Goal: understand the product and choose to try it.

  1. Land on the hero with Start Free Trial and Book a Demo side by side.
  2. Read how the product resolves a support request.
  3. Scan the feature cards, one promise each.
  4. Compare plans with the monthly and yearly toggle.
  5. Read the comparison table and FAQ.
  6. Start a trial or book a demo.

Edge paths to design: a visitor who needs an enterprise plan, a question the FAQ doesn’t answer, a visitor not ready to commit. Metric to track: visit-to-trial and visit-to-demo rates.

Website flows are user flows too. Putting both actions in the hero lets self-serve buyers and sales-led buyers each take their own path.

12. Onboarding a new investor with identity checks (AQARI)

Product: AQARI, a real estate investment fintech app. Goal: go from sign-up to a first investment.

  1. Sign up.
  2. Verify identity through Nafath.
  3. Complete the investor suitability check.
  4. Browse property cards showing funding, target return, net yield, minimum investment and days left.
  5. Invest from the 1,000 SAR minimum.
  6. Track portfolio value, wallet and payouts.

AQARI investor onboarding user flow: sign up, verify identity, complete the suitability check, browse properties, invest and track the portfolio, with edge paths for failed verification and an unsuitable investor profile.

Edge paths to design: identity verification fails, the suitability check doesn’t pass, a property fills before the investment completes. Metric to track: sign-up to first investment.

On AQARI, the investor journey was mapped from first visit to first payout before the 32 modules of the product were organized. Regulated onboarding is where flows earn their keep: every check is a place to lose people, so each one needs a clear reason and a clear next step.

Web vs mobile user flows

The same task often needs a different flow on each platform.

Web Mobile
Steps per screen Several fields and actions can share a page One main action per screen
Interruptions Tabs and multitasking Calls, notifications, app switching
Permissions Rare Camera, location and notifications need OS prompts
Re-entry Bookmarks and links Push notifications and deep links
Input Keyboard and mouse Thumbs, camera, voice, biometrics

In practice, a mobile flow needs more save points and a plan for every permission prompt. In the RoomMind AI flow, for example, the photo upload step only works if the camera permission is handled well. Our guide on how to design a mobile app covers mobile edge cases in more depth.

How to turn a user flow into a funnel

A user flow tells you what should happen. A funnel tells you what does happen. Connect the two by giving every step in the diagram an analytics event.

Turning a user flow into a funnel: each step in the flow gets an analytics event, and the funnel shows how many users reach each step, revealing where the flow loses people.

  1. Name an event for each rectangle and decision in the flow.
  2. Build a funnel from the entry point to the goal.
  3. Look for the biggest drop between two steps.
  4. Check the branches: how many users hit each error path.
  5. Redesign the step with the biggest drop first, then measure again.

If you already have a live product and don’t know which flow is leaking, that is what a UX audit is for.

How to create a user flow in 6 steps

  1. Pick one user and one goal. “A new patient books a first appointment,” not “patients use the app.”
  2. Define the entry point. Where does the user come from: an ad, a notification, the home screen?
  3. Define success. The exact state that means the goal is reached.
  4. Map the happy path. Every screen and action between entry and success.
  5. Add decisions and edge paths. Errors, empty states, permissions, timeouts and exits.
  6. Check it against reality. Compare with analytics if the product exists, or test a clickable prototype with users if it doesn’t.

The flows then become the base for wireframes and screens, which our UI/UX design process guide walks through.

Common user flow mistakes

  • Happy path only. The flow looks clean and the product breaks on the first wrong password.
  • One diagram for several goals. Split them. Each flow should end in one success state.
  • Inconsistent symbols. If a diamond means a decision in one flow and a screen in another, nobody trusts the diagrams.
  • No entry context. A flow that starts at “dashboard” ignores how people actually arrive.
  • Drawing flows after the UI. Then they document decisions instead of shaping them.
  • No metric. Without one, nobody knows whether the redesign worked.

For onboarding specifically, where most of these mistakes cost the most, see our guide to SaaS user onboarding.

Want your flows mapped?

We map user flows at the start of every UI/UX design, web app design and mobile app design project, before any screen is designed. If your product has a task people keep failing, book a free call and we’ll tell you which flow we would map first.

Sources and method

We reviewed every source below in November 2026.

From our own work

  • The 12 flows, from our case studies of Shipora, CareUp, RoomMind AI, Axon, Earnify, OpsLoop, Zyntra and AQARI.
  • The edge paths and metrics, which are our recommendations for flows of each type, not results reported by those clients.
  • The diagrams, drawn for this guide in one notation.

User Flow Examples FAQs

What is a user flow?

A user flow is a diagram of the steps a user takes inside a product to complete one task, such as signing up, booking an appointment or upgrading a plan. It shows the screens, the actions, the decisions and the error paths between the starting point and the goal.

What is an example of a user flow?

Booking a doctor in a health app is a typical user flow. The patient opens the app, searches or taps a specialty, compares doctor cards, picks a day and a time, confirms and sees the booked appointment. A complete flow also shows what happens when no slot is free or the payment fails.

What is the difference between a user flow and a user journey?

A user flow zooms in on the steps inside a product for one task. A user journey zooms out to the whole experience across channels and over time, including emotions and touchpoints outside the product, such as ads, sales calls and support.

What is the difference between a user flow and a wireflow?

A user flow uses simple shapes for steps and decisions. A wireflow combines wireframe-style screen layouts with flow arrows, so you can see what each screen looks like as well as how screens connect. Nielsen Norman Group notes that wireflows grew out of mobile app design.

What symbols are used in a user flow diagram?

Most user flows borrow standard flowchart shapes. A rounded shape marks the start and end, a rectangle is a screen or step, a diamond is a decision, a parallelogram is user input and arrows show direction. Many teams add a dashed line for error paths. Flowchart symbols were standardized by ANSI in the 1960s and later in ISO 5807.

How do you create a user flow?

Pick one user and one goal, define the entry point and the success state, map each screen and action between them, add every decision, error and exit, then check the flow against analytics or a usability test before designing the final screens.

What are the 7 pillars of user experience?

The phrase usually refers to Peter Morville’s User Experience Honeycomb from 2004. Its seven qualities are useful, usable, findable, credible, desirable, accessible and valuable. A good user flow supports several of them, especially usable and findable.

How many steps should a user flow have?

As few as the task allows, but no fewer. Most core flows have five to ten steps. Remove steps that only exist for the company’s convenience, and keep the ones that build trust or prevent errors, such as a confirmation before a payment.

What tools are used to create user flows?

Figma and FigJam, Miro, Whimsical and Lucidchart are common choices. The best tool is the one your designers and developers already use, because the flow should sit next to the screens it describes.

How do you measure a user flow?

Give every step in the flow an analytics event, then build a funnel from the entry point to the goal. The share of users who finish, the step where most leave and the time it takes tell you which part of the flow to redesign first.

Need your product’s flows mapped before you design?

Send us the task your users struggle with. A senior designer replies within 4 business hours with the flows we would map first and a fixed quote.

Book a free call

Was this article helpful?

Tags

  • # UI/UX
  • # UI/UX Design

Maniruzzaman Jubayer

Written by

Maniruzzaman Jubayer

Co-founder & COO | Product Design Specialist at Wolfpixel

Maniruzzaman Jubayer is Wolfpixel’s Co-founder & COO and a product design specialist with 7 years of experience. He personally oversees website, app, dashboard and digital product design at Wolfpixel, where user flows are mapped before any screen is designed. Every example in this guide comes from a product Wolfpixel designed. Wolfpixel offers the UI/UX design services discussed in the article.

View all articles

Keep reading

More on UI/UX and design

View all articles
Top EdTech UX Design Agencies for 2027: 11 Studios Compared
Top EdTech UX design agencies for 2027 cover, with the Wolfpixel education web design page on a laptop and the title in cream and yellow on a dark background.UI/UX

· 19 min read

Top EdTech UX Design Agencies for 2027: 11 Studios Compared

Compare 11 top EdTech UX design agencies for 2027 by real education case studies, Clutch pricing and fit for K-12, higher ed, test prep and workforce learning.

Types of UX Research: 12 Methods and When Each One Pays Off
Types of UX research cover showing the Wolfpixel UX research page on a laptop, with the title in cream and yellow on a dark background.UI/UX

· 20 min read

Types of UX Research: 12 Methods and When Each One Pays Off

The types of UX research explained, from generative vs evaluative to qualitative vs quantitative, plus 12 methods with sample sizes and when to use each.

Book a free call

Step 1 of 2

Pick a day