Screen Recording

Getting Started

Open your Figr project

Click the New Screen Share button in the input panel

Select which screen or window to share

Click through your product naturally

Talk about the product and interactions

Stop recording when done

Narrate as you record. Figr captures your voice and uses it as additional context. “Now I’m clicking here because users typically want to…” gives Figr intent, not just actions.

Why Screen Recording Works

Static screenshots show what your product looks like. Screen recordings show how it behaves.

Figr watches you click through flows, sees transitions, notices loading states, and understands the rhythm of your product. It’s the difference between seeing a photo of a car and watching someone drive it.

Static Inputs	Screen Recording
Screenshots miss interaction patterns	Captures actual click sequences and paths
Descriptions can’t capture timing	Sees loading states, transitions, animations
Flow diagrams oversimplify real behavior	Records real user flow timing
Edge cases get forgotten	Catches the interactions you’d forget to mention

Best Practices

Narrate your Actions

Talk while you record. Figr uses your commentary as context.

Good narration:
"I'm clicking Projects because that's where users 
typically start. Notice how the sidebar collapses 
on smaller screens..."

"This error appears because we validate emails 
in real-time. Users often miss it if they're 
typing quickly..."

"The dashboard loads slowly with lots of data, 
so we show skeleton components here..."

Show, Don't Tell

Instead of describing what you want, show Figr examples.

Less effective:
"I want a form with inline validation"

More effective:
Record yourself filling out a form, triggering 
validation errors, and correcting them. Figr 
sees exactly how it should work.

Record Real Data

Demo environments with realistic content give better results.

Before recording:
✅ Populate with realistic test data
✅ Create multiple items to show list/table behavior
✅ Set up different user states to demonstrate
✅ Prepare error scenarios you can trigger

Keep Recordings Focused

Shorter, focused recordings beat long rambling ones.

Recommended appraoch	Avoid
One flow per recording	10+ minute recordings covering everything
1-3 minutes typical length	Jumping between unrelated features
Clear start and end points	Excessive pauses or hesitation
Pause between distinct actions	Sensitive data on screen

How to Begin?

Canvas

Inputs and Research

Product Intelligence

Export and Share

Security & Legal

Getting Started

Why Screen Recording Works

Best Practices

​Getting Started

​​Why Screen Recording Works

​​ Best Practices

Getting Started

Why Screen Recording Works

Best Practices