F
floom · wireframes v12
launch-ready spec ← all versions

v12. Final launch-ready state.

This is what preview.floom.dev should look like when fully polished. Preview already ships ~80% of v11. v12 shows the last mile: paste-first build, magic-link removed, content polished, every state verified.

Nothing here is a promise, everything here is a hypothesis being validated. Illustrative counts and sample apps only.

What changed from v11

Paste-first, auth-last, launch-clean.

  • · /build is fully anonymous until publish. 5 ramps (GitHub, Describe, Connect, Docker, OpenAPI URL). Describe/Connect/Docker labeled coming soon.
  • · Signup modal only on publish intent. No auth wall between idea and preview.
  • · Magic link removed. Google + password only. Fewer decisions, clearer trust.
  • · /apps directory polished, filters pinned, empty state, hover state, illustrative counts clearly marked.
  • · /p/:slug rebuilt matches click spec exactly. Schedule drawer, run surface, reviews below the fold.
  • · /me and /creator split: /me is the consumer dashboard, /creator is the supply-side dashboard. Two dashboards, two CTAs, same product.
8 pages

The surface, end to end.

Click each row. Every page is a single HTML file, zero build step.

/
Landing · desktop + mobile side by side
Hero, two CTAs, 5 trust markers, featured apps grid, category rail, how-it-works, pricing teaser, footer. Mobile column shows the same content stacked.
/apps
Apps directory
Search, category filter chips, sort, card grid, hover state, empty state when filter returns zero, pagination footer. Illustrative run counts with tiny footnote.
/build
Paste-first composer · 4 states
State 1 anonymous picker (5 ramps), state 2 detect preview anon, state 3 publish signup modal, state 4 logged-in direct publish. All 4 shown inline, labeled.
/p/:slug
Product page
Hero with illustrative ratings, 4 connectors row (Claude/ChatGPT/Notion/CLI), how-it-works, schedule drawer, run surface with terminal-style output, reviews under fold, creator card.
/me
User dashboard (consumer)
Recent runs table, installed apps, connected tools, API key surface, settings tabs. Focus: "what have I run and what did it cost me", nothing creator-side.
/creator
Creator dashboard (supply)
Owned apps list, per-app runs/installs/revenue tiles, publish/edit buttons, quick analytics, payouts placeholder. Separate surface from /me on purpose.
/login
Login · Google + password only
Clean split layout, no magic link, no SSO noise, password reset link. Matches the publish modal on /build so users see the same auth twice.
3 things Federico should look at specifically
  1. build.html state transitions. Is the anon → preview → publish-modal flow obvious at a glance? Would a vibecoder pasting an OpenAPI URL understand they own the result before sign-in?
  2. landing.html mobile column. Order of hero, two CTAs, featured apps. Is the "build side" vs "use side" split readable on a phone without a tab bar?
  3. /me vs /creator separation. Are these two truly distinct mental models, or does one feel like a subset of the other? If creator is a subset, merging might beat splitting.