Problem, approach, stack, and outcome for each build — including the ones still in progress.
01 / Problem
Streamers announce schedules in Discord, on Twitter, in Twitch panels — then change plans and update one of the three. Communities stop trusting the schedule
02 / Approach
Build the schedule once. Approve it, and StreamLine pushes it out — Discord, Twitch, Discord events and a clean email — from one source of truth
03 / Stack
Next.js, Supabase/Postgres, Twitch API, Discord webhooks
04 / Outcome
Built and extensively tested — targeting a launch by the end of August 2026
01 / Problem
Adding song requests to Spotify during a stream meant alt-tabbing away from chat and gameplay to manage them by hand — a manual chore with no permission control over who could even ask
02 / Approach
Chat commands and channel point redeems queue songs on Spotify directly, gated by a role system so streamers decide who can trigger requests — everyone, VIPs only, or mods only
03 / Stack
Next.js, Supabase, Docker, Twitch API, Spotify API
04 / Outcome
Still in rigorous testing with a group of streamers using it live
01 / Problem
Not a streamer product — a personal productivity problem. Tasks, workouts, and money all live in separate apps, and reminders that only show up as a quiet badge are easy to miss entirely
02 / Approach
An desktop app that promises to change your lifestyle within 30 days. Exercise, tasks, and money live in one place, and every reminder pops up above the taskbar until it's actually seen
03 / Stack
Next.js, Supabase, Electron
04 / Outcome
Our proof point that we ship polished software outside the streamer, still in development
