> ## Documentation Index
> Fetch the complete documentation index at: https://docs.figr.design/llms.txt
> Use this file to discover all available pages before exploring further.

# Audit and redesign a flow from a screen recording

A flow can pass every design review and still break once it ships. Teams have designs approved, built and released, and only then find out that real users couldn’t get through the flow. By then, fixing it meant another sprint.

Figr lets you check the flow the way people actually use it, then fix it in the same place.

![Image](https://mintcdn.com/figr-1af7ae64/MWugUlEIv8OG0sG0/images/image-23.png?fit=max\&auto=format\&n=MWugUlEIv8OG0sG0\&q=85\&s=7a11a9be43f01fc8149c8c7ccf225022)

> [!TIP]
>
> **The short version:** Record a walkthrough of any flow in your product. Figr breaks it into screens, audits each one, pins every issue to the screen it happens on, and redesigns the flow in your design system.

**Example on this page:** FreshFold, a laundry pickup and delivery app. Customers book a pickup in the app, a rider collects the bag, and clean clothes come back within 24 hours.

## How it works

**1. Record the flow**

Share your screen and walk through the flow, or upload a recording you already have. In the FreshFold example: a customer booking their first laundry pickup, from choosing a time slot to paying.

![Screenshot 2026 10 21 At 12 48 30 AM](https://mintcdn.com/figr-1af7ae64/IKsR7_SNlON40_qL/images/Screenshot-2026-10-21-at-12.48.30-AM.png?fit=max\&auto=format\&n=IKsR7_SNlON40_qL\&q=85\&s=053002636b95c8d66023eaa78661f795)

**2. Figr breaks it into screens**

Figr pulls out each screen and step from the recording, so you don’t have to take a single screenshot.

![Screenshot 2026 10 21 At 12 51 55 AM](https://mintcdn.com/figr-1af7ae64/GFl9SXL01D1q0Z7d/images/Screenshot-2026-10-21-at-12.51.55-AM.png?fit=max\&auto=format\&n=GFl9SXL01D1q0Z7d\&q=85\&s=7944edc2b3b08e4de3252a7923bab908)

**3. Figr audits every screen**

You get a UX audit with each finding pinned to the exact screen it happens on, covering usability, clarity, accessibility and consistency.

![Screenshot 2026 10 21 At 12 56 11 AM](https://mintcdn.com/figr-1af7ae64/GFl9SXL01D1q0Z7d/images/Screenshot-2026-10-21-at-12.56.11-AM.png?fit=max\&auto=format\&n=GFl9SXL01D1q0Z7d\&q=85\&s=770977a443ac3aa2b1b9752c9ee451e2)

**4. Figr redesigns what’s broken**

Pick the findings that matter, and Figr redesigns those screens in your design system, right next to the originals.

**5. Run a visual review**

Add “visual review” to your prompt, and Figr checks the visual quality of the screens it generated, such as spacing, alignment, hierarchy and consistency, then fixes what it finds. It runs only when you ask for it, so you choose when to polish.

![Screenshot 2026 10 21 At 12 53 20 AM](https://mintcdn.com/figr-1af7ae64/GFl9SXL01D1q0Z7d/images/Screenshot-2026-10-21-at-12.53.20-AM.png?fit=max\&auto=format\&n=GFl9SXL01D1q0Z7d\&q=85\&s=e072e9dcb3b47829eee34eb5e7d10554)

## What changes for your team

* **Designers** catch usability issues before engineering builds them.
* **PMs** get a ranked list of what to fix, tied to real screens.
* **Everyone** reviews the flow people actually use, not the one in the spec.

## Go further

Get more out of every recording. See how to record walkthroughs Figr learns the most from.

> **[Screen recordings](/input-research/screen-recording)**
>
> Record walkthroughs Figr can learn the most from.

## Related

> **[UX review](/getting-started/tutorial/review)**
>
> How Figr reviews a design.

> **[AI-ready design system](/what-figr-does/ai-ready-design-system)**
>
> Next step: line up Figma and code so every AI tool follows one system.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.