/onboarding — intent split

STORE · post-signup · pick Run vs Build · routes to Store or Studio accordingly

v16

DESKTOP · 1280px · step 1 · pick intent

floom.dev/onboarding

STEP 1 OF 1 · ONE QUESTION

What brings you here, Federico?

You can switch tracks any time. Same account, different landing.

I want to use AI apps.

Browse the store, run apps, install them in Claude. Zero setup.

→ Lands on /apps (Store)

I want to publish.

Paste an OpenAPI URL. Detect. Publish. Share. MCP, API, web, CLI — one deploy.

→ Lands on /studio (Studio empty state)

Not sure? Start in the Store. You can open Studio later from your avatar menu.

DESKTOP · 1280px · picked "Build apps" → /studio empty state

floom.dev/studio

floom · Studio

← Back to Store

Welcome to Studio.

You don't have any apps yet. Paste an OpenAPI URL to publish your first one.

Publish your first app →

Working on it later? Browse the Store while you decide what to ship.

MOBILE · 375px

floom.dev/onboarding

floom

STEP 1 OF 1

What brings you here?

Switch any time.

I want to use apps.

Browse, run, install.

I want to publish.

Paste OpenAPI. Ship.

SPEC NOTES · WHAT CHANGED FROM v15

One question, two paths. v15's onboarding dropped everyone into /p/:slug with a pre-filled input (consumer ramp). v16 asks intent first.
Studio entry is now visible from signup — creators don't need to discover it. Matches the "two ICPs" rule in positioning.
Cross-link kept: "Not sure? Start in the Store" nudges consumer when undecided. Studio empty state has a "browse Store while you decide" link.
Single green accent for both paths. Store vs Studio is distinguished by layout, iconography, and label, not by color.