Stream is a frontend design concept I've built out end-to-end — a live-streaming platform designed around a different objective function than Twitch or YouTube Live. Those platforms optimize for engagement and peak viewers, which rewards spectacle and punishes small, healthy communities. Stream asks the opposite question: what would a live platform look like if it optimized for fit and belonging?
The Thesis
The dominant streaming platforms run a winner-take-all algorithm. Rank by concurrent viewers, surface what's already huge, and the rich get richer while a great 30-person community stays invisible. The incentives push creators toward sensationalism and leave newcomers feeling like they walked into a stadium mid-game with no idea what's happening.
Stream is built on three principles that fall out of rejecting that:
Discovery fit over popularity. Streams are organized by mood — chill, learn, laugh, competitive, small-community, creative, background, deep-focus — not just category. You find something that fits your current headspace, and the discovery logic deliberately boosts small communities and weighs how welcoming a stream is to new viewers, not just how big it is.
Context for people with lives. Real viewers don't arrive at minute zero. Catch Me Up gives late arrivals a headline, the current topic, a summary, and timeline moments so they can orient in seconds. Join Late turns "I missed the start" from a barrier into a one-tap action.
Community health as a first-class metric. A stream isn't ranked purely on peak viewers — it factors in chat health, creator response rate, and how friendly it is to newcomers. The platform measures belonging, not just attention.
What's Built
Stream is a full-featured product surface, not a landing page with three screenshots. It spans 30-plus routes:
- Discovery & watch — a mood-driven home, a filterable discover page, the watch experience with a player and live chat, creator channels, and category browsing.
- Structured chat — organized into live, questions, polls, and highlights, with sentiment and moderation flags, rather than one undifferentiated firehose.
- "Bloom" panels — shareable, URL-addressable overlays on the watch page (catch-up, clip, report, creator profile, analytics, subscribe, predictions, rewards) with shared-element transitions.
- Clips & VODs — create clips from a stream, browse popular clips, and seek replays via VOD chapters.
- A complete creator studio — go-live setup, stream manager, analytics with retention curves, clip management, community and moderation queues, monetization, alert-box configuration, and multi-platform restreaming.
- Monetization & engagement systems — tiered subscriptions, channel points, predictions, and rewards, all fully modeled.
How It's Built
Stream is built with Next.js 16 and React 19 as a statically exported site, styled with Tailwind CSS v4 on a semantic-token design system with Base UI primitives, Motion for the Bloom panel transitions, and a command palette for navigation. It ships with real engineering hygiene around it: Vitest unit tests, Playwright end-to-end tests, and Storybook for component development.
The defining constraint: it's a front-end-only build. There's no real ingest, no live backend — state lives in localStorage via useSyncExternalStore, and the world is seeded from static JSON (streams, creators, clips, chat personas, polls, predictions, rewards, analytics). Every system a real platform needs is present and interactive; what's deliberately absent is the broadcast infrastructure.
I built it this way because the thesis is a product argument, not an infrastructure one. To know whether "rank by community health" and "Catch Me Up" actually feel better, you have to build the whole experience and live in it — which is exactly what a complete, seed-driven prototype lets me do before committing to the hard, expensive real-time stack. It's in active development, and it's the most opinionated thing in my portfolio.
Try it at stream.byronwade.com.