Roadmap

Roadmap

Shipped

• 2–6 channel video grid: add/remove, automatic layout, offline detection
• Selection audio mode, with focus-follows-audio layout and automatic fallback if the active channel is removed
• Both/All audio mode, with independent per-panel volume
• Dedicated chat bar: one always-pre-loaded tab per channel, follows audio focus with manual override
• Native per-panel actions: channel link, follow, donate
• Twitch OAuth login, gating chat send / follow / template saving; anonymous read-only viewing works without an account
• Saved grid templates (save / load / delete), tied to a logged-in account
• "Online now" menu: followed channels currently live, plus the current top live channels on Twitch by viewer count, each with one-click add-to-grid
• Server-side token refresh, so a logged-in session doesn't silently break when a Twitch access token expires
• Preferences: default audio mode, default chat-bar state, and a light/dark theme override, stored locally per browser

Note

The channel cap moved from 5 to 6 after the original PRD was written, once the symmetric (Both/All) grid layout was reworked to stay usable at that count. See Features & Audio Modes for what it looks like today.

Planned / nice-to-have

• Support page for StreamHive itself — a place to support the project's own development, entirely separate from any streamer's donation link shown in the grid.
• Share a template by link — a URL that rebuilds a saved grid for anyone who opens it, even without an account.
• Keyboard shortcuts for switching the active audio channel in Selection mode.
• Browser extension — a thin wrapper around the same web app, to open a grid without leaving the current page.

SmartVoiceSwitch — honest status

Warning

Not implemented. There is no SmartVoiceSwitch mode in the app today — the audio control only offers Selection and Both/All (see Features & Audio Modes). Everything below is research status, not a feature description.

The original vision was full "SmartVoiceSwitch": automatically detect which streamer is actually talking and cancel duplicate audio between channels that are on a call together (e.g. two collaborators whose mics both pick up the same conversation). This is genuinely hard, and the project treats it as a research spike, not a committed feature.

What's been confirmed by a real spike: a browser extension (not the web app itself) can access each channel's real audio, by injecting a content script directly into Twitch's embedded player iframe and reading the audio via the browser's own media APIs. That unlocks a simpler, realistic feature — automatically switching audio to whichever channel has voice activity right now — as a possible extension feature, later than the core web app.

What has not been proven: actually detecting that two channels are saying the same thing, with different and variable buffering delays between them, and cancelling the duplicate. That remains an open, unsolved signal-processing problem, and stays a stretch goal rather than a roadmap commitment.

Not planned for v1

• Other streaming platforms besides Twitch
• Grids larger than 6 streams, or mosaic-style layouts for many channels at once
• A native mobile app

See Why StreamHive for the reasoning behind these scope decisions.