#Introduction

Flowingto is an app design reference library for product and design teams. You can think of it as a team version of a design reference library plus an interaction flow diagram tool: it brings product screenshots out of chat history, photo libraries, Figma files, local folders, and Notion documents, then puts them back into a place that can be organized, discussed, and traced over time.

Flowingto is designed around screenshots. It does not only store images; it helps teams place screenshots into workspaces, collections, versions, flows, and compare contexts so product interfaces can be searched, reviewed, and reused.

#Why Flowingto exists

Product and design work often leaves screenshots scattered across different places:

• Historical designs are hard to find because they live in old messages or files.
• Competitor pages can be expensive to revisit because you need to find the link, sign in, and navigate back to the right state.
• Competitive analysis screenshots are often trapped in Figma files, local folders, or one-off documents.
• Teams discuss flows, but the source material is a set of isolated images.
• Comparing multiple competitors, platforms, or versions is difficult without a shared context.

Flowingto turns those scattered screenshots into a durable design knowledge base for the team.

#Who it's for

Flowingto is useful for people who regularly collect, organize, discuss, or reuse product screenshots:

• Product managers: organize competitor screens, record feature evolution, and use screenshots as shared context for product decisions.
• Product designers: build an interface reference library, compare interaction details across products, and preserve design patterns.
• Design researchers and competitive analysts: archive screenshots by industry, platform, feature, or flow and keep research material maintainable.
• Growth, operations, and marketing teams: collect reusable references for landing pages, pricing pages, campaign pages, and sign-up flows.
• Engineering and QA teams: preserve important interface states, regression screenshots, and cross-version differences for review and acceptance.
• Teams using agents or automation: capture screenshots in batches through the CLI or headless browsers and sync them into shared collections.

#What Flowingto is for

Use Flowingto when screenshots are part of your product work:

• Build a shared reference library of app screens.
• Track how an interface changes across releases or design passes.
• Compare similar screens across platforms, competitors, or versions.
• Review journeys such as onboarding, sign-in, checkout, upgrade, and settings.
• Upload screenshots manually in the web app or automatically with the browser extension and CLI.

#Core concepts

#Workspace

A workspace defines the collaboration scope and permissions for a team or organization. It contains collections, compare boards, search results, and members.

#Collection

A collection groups screenshots by platform, product line, or reference target. Collections can be labeled as iOS, Android, Web, or Desktop.

#Version

A version records how the same product changes over time or across iterations. Use versions for releases, dated captures, design iterations, or review milestones.

#Screenshot

A screenshot is an individual screen inside a collection version. Screenshots can be reviewed in the grid or opened in the screenshot viewer.

#Flow

A flow is an ordered path made from screenshots. Use flows to document product journeys and review the sequence between screens.

#Compare

Compare is created from collections and puts different apps, platforms, or versions into one review context.

#Product entry points

Flowingto currently has three entry points:

• Web app: browse, upload, organize, review, arrange, and compare screenshots visually.
• Browser extension: capture the current page into a Flowingto collection while browsing the web.
• CLI: collect and upload screenshots from local folders, scripts, automation, or agent workflows.

#How to start

1. Open the Web App Overview to understand the visual workflow.
2. Create or choose a workspace.
3. Create a collection for an app or product surface.
4. Upload screenshots into a version.
5. Create flows and compare collections when you need deeper review.

If your screenshots are generated from local folders, headless browsers, or automation, continue with CLI Getting Started.