← all wireframes

Studio · redesign wireframes

2026-04-21 · launch prep
draft · internal review
A. Workspace root · /studio B. Per-app · /studio/:slug Design notes
A · Workspace root · /studio

Today: "Your apps" title + 1-column card stack. Goal: a workspace home that scales to teams and multiple apps. Workspace switcher in the rail, search + activity + stats strip at the top, app grid with real screenshot-like thumbnails, quick actions per card.

DESKTOP · 1440px · POPULATED STATE
floom.dev/studio
Personal · Home
⌘K
New app
Runs · 7d
2,847
+18% vs prev week
Active apps
4 / 5
1 draft
Feedback · unread
7
across 3 apps

Your apps

FF
flyfast
Last run 2m ago
LIVE
1,284 runs · 7d
OD
opendraft
Last run 5m ago
LIVE
712 runs · 7d
LS
lead-scorer
Last run 1h ago
LIVE
618 runs · 7d
RA
resume-agent
Last run 3h ago
LIVE
233 runs · 7d
CA
competitor-analyzer
Never published
DRAFT
Local-only · 12 test runs
New app
Paste GitHub URL, Docker image, or OpenAPI spec

Latest across all apps

Who ran what · where · how long it took

See all runs →
flyfast · search-flights via Claude
812ms 2m ago View →
opendraft · draft-reply via web
1.2s 5m ago View →
flyfast · price-alert failed · rate limit
3.4s 12m ago View →
lead-scorer · score-lead via API
950ms 18m ago View →
resume-agent · screen-resume via Cursor
2.1s 34m ago View →
DESKTOP · EMPTY STATE · FIRST-RUN CREATOR
floom.dev/studio
Personal · Home

Ship your first app.

Paste a GitHub URL, a Docker image, or an OpenAPI spec. Floom packages it as a runnable app with a public page, an MCP endpoint, and a JSON API. Under 60 seconds.

Popular first apps: webhook forwarder · internal tool bridge · file converter · agent audit gate
MOBILE · 375px
floom.dev/studio
B · Per-app Studio · /studio/flyfast

Current state: stacked "VISIBILITY / PRIMARY ACTION / RECENT RUNS" sections, raw markdown in header. Goal: a dense, tabbed control room. Tagline renders as text (not raw), hero metric + sparkline up top, 3 primary actions, 5 tabs (Overview / Runs / Settings / Source / Feedback). Main content + quiet meta rail.

DESKTOP · 1440px · OVERVIEW TAB (DEFAULT)
floom.dev/studio/flyfast
studio flyfast LIVE · v1.4.0
View public page
Overview Runs 1,284 Settings Source Feedback 3
FF

flyfast

Natural-language flight search with trust metrics. Ranks options by on-time rate, price history, and aircraft age.

travel 11 actions http-proxy
RUNS · LAST 7 DAYS
1,284
+18%

Traffic

Runs per day · last 14 days

p50 · 812ms p95 · 2.1s 99.2% success
Apr 8Apr 12Apr 16Apr 20today

Recent runs

Latest 5 · filter + inspect I/O in Runs tab

All runs →
HAM → LIS next friday search-flights via Claude 2m ago 812ms
NYC → PAR · apr 22 search-flights via Cursor 4m ago 940ms
flexible weekend BCN price-alert rate limit 12m ago 3.4s
LHR → JFK in june search-flights via floom.dev 22m ago 1.1s
cheap sun, warm, week search-flights via ChatGPT 38m ago 780ms

Top errors · 7d

What's breaking, by frequency.

Upstream rate limit (429)8
Timeout >30s2
Missing secret: AMADEUS_KEY1

Where it runs

By client, last 7d.

Claude
924
floom.dev
218
Cursor
98
ChatGPT
44
APP META
Slugflyfast
Versionv1.4.0
Runtimehttp-proxy
Visibilitypublic
Ownerfederico
Published3d ago
LicenseMIT
ENDPOINTS
Public page
floom.dev/p/flyfast
MCP
floom.dev/mcp/flyfast
API
floom.dev/api/flyfast
Install in Claude Desktop →
COLLABORATORS · 3
+ Invite
F
Federicoowner
J
Jannikeditor
Y
Yashviewer
DESKTOP · FEEDBACK TAB · FILED AGAINST THIS APP
floom.dev/studio/flyfast/feedback
studio flyfast LIVE · v1.4.0
View public page
Overview Runs 1,284 Settings Source Feedback 3

Feedback

Users report issues via the in-app feedback button. Syncs to GitHub as issues on your repo.

Open in GitHub
BUG
Price alert returns 429 on multi-city routes
Opened 2h ago · Jannik · from run run_a8f31
Tried HAM → FCO → JFK, got rate-limited after 2 calls. Searching single-leg works fine.
Reply
FEATURE
Add hotel pairing for destinations
Opened 1d ago · Rachel · 4 stars
Works great for direct routes. Would love to see hotel pairing. Until then, 4 stars.
Reply
QUESTION
Can I filter by aircraft age?
Opened 3d ago · Yash
I see aircraft-info returns age, but search-flights doesn't accept it as a filter param.
Reply
MOBILE · 375px · OVERVIEW
floom.dev/studio/flyfast
flyfast
F
FF

flyfast

LIVE · v1.4.0

Natural-language flight search with trust metrics. Ranks options by on-time rate, price history, and aircraft age.

RUNS · 7D
1,284
+18%

Recent runs

ALL →
HAM → LIS fri 812ms 2m
NYC → PAR apr22 940ms 4m
flexible BCN 429 12m
Design notes · v6 inheritance · open questions

Lifted from v6.html

  • Cross-client activity — runs show who ran it AND where from (Claude / Cursor / ChatGPT / floom.dev / API). Makes the home page feel alive and exposes MCP reach.
  • "Where it runs" distribution bars — client breakdown on the per-app overview, lifted from v6's Usage panel. Signals product-market fit across surfaces.
  • Feedback tab instead of Reviews — v6 had Reviews; we renamed to Feedback to reuse the new in-app feedback button + GitHub Issues sync. Same UX pattern, different source of truth.

Biggest departures from current Studio

  • Workspace switcher in rail — the current Studio has no workspace UI at all, despite the backend being ready (ISSUES.md #147). This is the top-of-rail slot for team context.
  • Tabs replace stacked sections — current per-app page stacks "VISIBILITY / PRIMARY ACTION / RECENT RUNS" as vertical sections. The wireframe collapses all of it into 5 tabs (Overview / Runs / Settings / Source / Feedback). Visibility + primary action move to Settings.
  • Tagline renders as text, not raw markdown — the screenshot Federico sent shows raw "## Natural-language..." in the header. The wireframe treats description as rendered markdown.
  • App cards get thumbnails — current cards are 100% text. The wireframe adds a small gradient thumbnail strip per app so the grid scans like a portfolio, not a DB dump.
  • Quiet right meta rail — version, license, endpoints, collaborators all move to a 260px right column on the per-app page. Main content stays focused.

Things I guessed · want Federico's read

  • 5 tabs not 6 — v16 had 6 (Overview / Runs / Secrets / Access / Renderer / Analytics). I folded Secrets + Access + Renderer + Analytics into Settings + Overview charts. Is 5 tabs too aggressive a cut? Or is the right number 4 (Overview / Runs / Settings / Feedback) with Source as a meta-rail link?
  • Thumbnails are gradient placeholders — real product would need either (a) a manifest-declared screenshot URL, (b) a generated OG-style image from the app name, or (c) auto-capture of the /p/:slug public page. Which direction?
  • Empty state shows 3 entry points (GitHub / Docker / OpenAPI) — today's build flow picks one at a time. Is the triple-card entry point a stretch or does it accurately represent the 3 supported paths?
  • Feedback tab presumes GitHub Issues sync is shipping — if the feedback button writes to a Floom DB (not GitHub), the "Open in GitHub" button needs to become "Open in Issues" or similar.
  • Stats strip shows "Feedback · unread" — I assumed Federico wants feedback count surfaced on the home page. If feedback volume is low at launch, this might embarrass empty. Hide below a threshold?

Constraints respected

  • Light theme, no emojis, no gradient backgrounds on every element (one subtle wash only), no colored left borders on cards.
  • Real-looking data: flyfast, opendraft, lead-scorer, resume-agent, competitor-analyzer (matches Federico's actual shipped showcase apps).
  • Numbers are flagged ILLUSTRATIVE in production; the wireframe shows representative scale.