Spike: web UI shape — single-channel app vs multi-channel vs threads-as-pages #7

Open
opened 2026-06-23 05:37:08 +00:00 by sscoble · 0 comments
Owner

Why

API is the priority for v0. But the moment we have a Discord bridge and a Hermes adapter, we need a place to read the posts. That's the web UI. The shape matters because it sets the user's mental model for years.

Three options

  1. Discord-clone layout: left rail of channels, middle of posts, right of selected post + comments. Closest to muscle memory.
  2. Facebook Workplace layout: top nav of "Spaces" (channel clusters), main feed = newest-bumped posts across all subscribed spaces, click a post to expand its full comment tree.
  3. Inbox layout: chronological list of posts with unread badges, no channel navigation in v0. Click a post to open the full thread.

Theo's framing leans toward #2 — "post gets bumped when there's a new comment." That implies feed-shaped, not channel-shaped.

What to do

  • Sketches (ASCII or hand-drawn) for the three options.
  • A recommendation with reasoning.
  • A short list of "what v0 ships, what waits" — e.g., does v0 even need a web UI, or is it API + Discord for the first month?

Open questions for Scott

  • V0 with or without a web UI? Default: without. API + Discord bridge is enough for v0; web UI lands in v0.5.
  • Light, dark, or both? (Default: both, per the style-prefs pattern, since you toggle already.)
  • Mobile-first or desktop-first? (Default: desktop — this is for ops, not your phone.)
## Why API is the priority for v0. But the moment we have a Discord bridge and a Hermes adapter, we need a place to *read* the posts. That's the web UI. The shape matters because it sets the user's mental model for years. ## Three options 1. **Discord-clone layout**: left rail of channels, middle of posts, right of selected post + comments. Closest to muscle memory. 2. **Facebook Workplace layout**: top nav of "Spaces" (channel clusters), main feed = newest-bumped posts across all subscribed spaces, click a post to expand its full comment tree. 3. **Inbox layout**: chronological list of posts with unread badges, no channel navigation in v0. Click a post to open the full thread. Theo's framing leans toward #2 — "post gets bumped when there's a new comment." That implies feed-shaped, not channel-shaped. ## What to do - Sketches (ASCII or hand-drawn) for the three options. - A recommendation with reasoning. - A short list of "what v0 ships, what waits" — e.g., does v0 even need a web UI, or is it API + Discord for the first month? ## Open questions for Scott - **V0 with or without a web UI?** Default: without. API + Discord bridge is enough for v0; web UI lands in v0.5. - **Light, dark, or both?** (Default: both, per the style-prefs pattern, since you toggle already.) - **Mobile-first or desktop-first?** (Default: desktop — this is for ops, not your phone.)
sscoble added the
area/web
kind/spike
prio/p2
status/decision
labels 2026-06-23 05:37:08 +00:00
Sign in to join this conversation.
No description provided.