Flocci TechnologiesInfinity
User Flow Mapping Tool

Map the flow your users actually take

To map a user flow, place one shape per screen or state, connect them in the order a user moves, and branch at every decision point with a labelled connector. Flocci Infinity's connectors bond to both shapes and re-route automatically, so a flow can be rearranged without redrawing arrows.

A user flow is a specific kind of diagram: mostly linear, punctuated by branches, and constantly wrong until you walk it with someone who has watched a real user. That means the diagram gets edited far more than it gets drawn — which is why connector behaviour matters more than shape libraries. Infinity's connectors bond to both endpoints and recompute their path whenever you move something, so restructuring the flow is a drag rather than an afternoon.

Frames carry the structure. One frame per screen or state, titled, with the key UI elements sketched inside as shapes or dropped in as images from a URL. Diamonds mark decisions, and every outgoing connector gets a midpoint label — "has account", "no payment method", "declined" — so the branch conditions are readable at a glance instead of implied by position.

The unhappy paths are where flow maps earn their money, and an infinite canvas is what makes room for them. Error states, retries, timeouts and abandonment routes usually get dropped from a flow because they will not fit on the slide. Here they go below the happy path with their own frames, and the map stops being a marketing artifact and starts being a specification.

Keep the real product beside the map: embed the live page or the staging URL as a card on the canvas, and the flow diagram sits next to the thing it describes. Because one Flocci account also covers Library and Projects, the spec page and the sprint board embed the same way — the flow map ends up as the visual index of the feature rather than an isolated drawing.

How to do it, step by step

  1. 1Frame the screensOne frame per screen or state, titled, laid out left to right in the order the user encounters them.
  2. 2Sketch insideRough the key UI elements with shapes and text, or drop a screenshot in from a URL as an image object.
  3. 3Connect in orderDrag connectors between frames; they bond to both and re-route themselves as you rearrange the layout.
  4. 4Branch and labelDiamonds for decisions, with each outgoing connector carrying its condition as a midpoint label.
  5. 5Map the unhappy pathsGive errors, retries and abandonment their own frames below the happy path — the canvas has room for all of them.

Frequently asked questions

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

A wireframe shows what one screen contains; a user flow shows how a person moves between screens and where the decisions branch. Infinity is built for the flow — frames, decisions and self-routing connectors — with rough sketching inside frames rather than pixel-accurate wireframing.

Can I put screenshots of my product on the canvas?

Yes. The image tool adds an image from a URL as a canvas object you can position, scale and layer. The embed tool goes further and renders a live webpage as a card, so the staging build can sit next to the flow diagram that describes it.

How do I label the branches of a flow?

Every connector supports a midpoint label with its own background and text colour, so a decision's outgoing paths read "yes", "no", "expired" or whatever the condition is. Combined with seven arrowhead styles and four dash patterns, the branch semantics stay readable without a legend.

Open a free board and try it

Free personal boards, no card. One Flocci account across 30+ apps, priced in rupees.

Open a canvas free