01 / THE OPPORTUNITY
The opportunity
Music can be a big part of a smaller Twitch stream’s identity. It gives viewers something to talk about, creates an easy way to participate, and helps a channel feel like its own community.
Existing song-request tools handle the basic interaction, but their queues often become unfair or repetitive. One viewer can submit several songs at once, the same tracks and artists keep appearing, and streamers must either manage everything manually or introduce strict limits.
There is also a larger discovery problem. Twitch primarily organizes streams by game or category. Viewers have no practical way to find smaller communities based on the music they play or the tastes of the people watching them.
NobBot started as a better way to manage requests, with the longer-term goal of helping viewers discover Twitch communities through shared music tastes.
02 / THE FAIRNESS MODEL
A fairer request experience
NobBot rotates between viewers instead of playing every song in the order it was submitted. People can request multiple tracks without one person filling the playlist or preventing everyone else from participating.
Streamers can also set cooldowns for recently played songs and artists. This reduces repetition while letting each channel choose rules that fit its own community.
Those rules also need to be clear. When a request is rejected, the viewer receives a specific reason. When it is accepted, they can see its position in the queue and follow what is currently playing.
The goal was not simply to process requests. It was to make requesting a song feel fair, understandable, and worth participating in.
03 / THE EXPERIENCE
One experience for streamers and viewers
Streamers already have a lot competing for their attention during a broadcast: the game, chat, broadcasting software, and the audience itself.
NobBot brings the main music controls into one interface, including:
- The current track and playback controls
- The live queue and requester information
- Queue moderation and reordering
- Channel-specific request settings
- Listening history and community statistics
Viewers have their own public channel page where they can check the current track, follow the queue, and explore recent activity without repeatedly asking for updates in chat.
Both sides stay connected. A request submitted through Twitch chat appears in the dashboard, and changes made by the streamer are immediately reflected in the public queue.
04 / COMMUNITY DATA
Turning music activity into community data
Every request says something about the channel: which songs keep returning, which artists connect with viewers, and who is helping shape the playlist.
NobBot turns that activity into charts and statistics showing listening trends, popular music, and viewer participation. During the alpha, viewers responded especially well to these features. The charts gave them more to discuss and compare, making the music feel like a larger part of the community instead of a temporary list of requests.
That response also reinforced the longer-term direction for the product.
As NobBot expands to more channels, the same activity could help viewers find streams that match their tastes. Instead of browsing only by game or viewer count, someone could discover a smaller community through familiar songs and artists.
The alpha tested the queue and channel-level analytics. Using that data for discovery across multiple channels is the next stage of the product, not something the initial launch has already proven.
05 / TECHNICAL SYSTEM
The central challenge
The hardest part was keeping the queue fair when viewers, moderators, playback controls, and the dashboard could all change it.
Removing the wrong request, correcting a song, skipping a track, promoting an entry, or manually reordering the queue could not be allowed to break the rotation between viewers.
I designed NobBot so those actions all follow the same queue rules, regardless of whether they begin in Twitch chat or the streamer interface. This kept the experience consistent as the product expanded beyond a basic chatbot into a connected set of streamer and viewer tools.
06 / OUTCOME
Outcome
NobBot completed a successful alpha during live Twitch streams. The queue worked as intended, streamers could manage requests without relying entirely on chat commands, and viewers responded especially well to the listening statistics and requester charts. Those features created more conversation around the music and gave the community another way to engage with the channel.
NobBot is now being prepared for release to more than 10 active streamers. That rollout will provide a broader test of onboarding, day-to-day reliability, and the potential for helping viewers discover channels through shared music tastes.