Skip to content
DIVE is also available forFirefoxand Safari(coming soon)
All use cases

Designers & design ops

Design review in production

Design reviews on staging always end the same way: a Loom recording, a Notion doc full of screenshots, and engineering scrambling to interpret ambiguous arrows. DIVE collapses that into one structured artefact.

The problem

Verbal feedback is lossy. "This needs more breathing room" can mean any of five different changes depending on who reads it. Engineers waste cycles asking which spacing token.

The workflow

  1. 1

    Walk the deployed app

    Open the DIVE side panel on each page in scope. Comment pins on issues; edits for fixes you can already make.

  2. 2

    Capture before / after

    Screenshots and the Changes tab automatically build a per-page audit trail.

  3. 3

    Export the spec

    Markdown export with selector → property → value lines. Paste straight into Linear, GitHub, or Jira.

The outcome

Engineering knows exactly what to change. No "what did you mean by this?" follow-up.