Flooow

Your whole app on one canvas. Straight from your codebase. No Figma, no design file.

For teams who start in code. When you build with Claude Code, there is no design file to look at. Your app only exists in the browser, one screen at a time. Flooow lays out every live screen, state and flow, so you can view, plan and improve the product without switching between your Claude Code and Figma. It's also a great way to show your product to stakeholders or potential investors.

It never changes your app's code to work. Flooow reads the app, updates as the source changes, and gives everyone in your org one place to see the product and work on it together. There's a big grey zone between solo AI-coding sessions and Figma-first collab work. This, is where my work lives now once I've built my first release. Maybe I should have named it V1→100 instead ;)

Local today, deployments next. Flooow runs on your local repos today. I'm working on scanning your Vercel and Netlify releases too, so anyone on the team can open the latest build, no local setup needed.

Join the waitlist

A one-minute survey, then your email. You hear about the beta first.

Open any project

Point Flooow at a React or Next.js repo. It finds every route, explores the app as a phone and as a desktop, and maps it in about a minute. Vue and Svelte are next.

See every state

Each screen opens into a stack of its states: loading, empty, error and success, side by side. You review the whole flow, not only the screen you happened to land on.

Change tokens across the app

Flooow scans and lists all your tokens, so you can make rapid changes across your whole app in Player mode and avoid free values and design debt.

Tune transitions

Select a transition on the canvas, change its duration and easing, and preview it between the two real screens before anyone touches the code.

Hand the changes to your AI

Your edits are kept as a change set. Copy it as a prompt or save it as a .md file, and apply it in your app's own AI session, whichever coding agent you use.

Coming to Flooow

  • Component scanningEvery component, its variants, and where each is used.
  • Metrics per flowAn LLM plans the product and UX metrics each flow should move.
  • Connecting analyticsTo bring in relevant live usage data in your screens and flows.
  • Comments and annotationsContextual notes on screens and states, with multi-user collaboration.
  • BranchingTry a direction without losing the main line.
  • Local and team versionsA local base version, and a SaaS version for teams.

And more. Building in public to create something you'll actually use.

The missing link from 1 to 100. Small product orgs vibe-code their way from 0 to 1. Getting from 1 to 100 takes structure, collaboration, and a place to tell the product’s story to the team, to customers and to investors.

Flooow is that place, built on the app you already have.

Help shape the beta. Tell me how you build: your front-end stack, and whether your code lives on your machine or in deployments. It decides what ships first.

Join the waitlist

A one-minute survey, then your email. You hear about the beta first.