Twitch / Nomad1sh

The problem

I wanted a practical route into games and direct conversations with developers, which meant learning how to build and operate a live platform from scratch.

What I did

I built the production setup, interaction systems and recurring formats, adapted the setup while travelling, and developed live sessions where indie developers could introduce their games to me as a new player.

Where it ended

The channel reached Affiliate in roughly eight weeks and ran for 251 stream days and about 1,045 live hours, generating 129k chat messages and lasting developer relationships before I chose not to make regular streaming the destination.

Operating record

251 stream days

About 1,045 live broadcast hours across the active period.

Audience activity

7,007 watched hours

About 129,000 chat messages, with Twitch Affiliate reached in roughly eight weeks.

01 · Learning Twitch by running the channel

The first months were small, repetitive and useful.

I experimented with schedule, game choice, format, presentation and how much conversation belonged around the gameplay. The channel reached Twitch Affiliate in roughly eight weeks and gradually developed a recurring audience rather than a series of isolated broadcasts.

Channel evolution

Build the setup

OBS, alerts, widgets and automation.

Run repeatedly

Test schedule, games and presentation.

Develop formats

Recurring audience interactions and indie-game sessions.

Build relationships

Direct conversations with developers continued beyond the channel.

Across the active period I streamed on 251 days for more than 1,045 live hours, generating about 7,007 watched hours and 129,000 chat messages. The repetition gave me a large number of real attempts to change something and see how the channel responded.

02 · Production system

The technical problem was bigger than overlays and chat commands.

I was traveling internationally for part of this period, so the stream had to work in temporary spaces and changing setups. I had to find internet connections and places where I could actually broadcast, make a laptop setup work with extra screen space and devices, and keep the production usable while moving between locations.

Inside the stream itself, I built and maintained OBS scenes, alerts, browser widgets, on-screen chat and MixItUp automations. Viewer actions could trigger sequences of messages, overlays, personalized text, text-to-speech, sound and timed events. I kept changing the setup as I learned what made the channel easier and more interesting to use live.

03 · Developer sessions

The channel became most useful when developers joined me live.

I created a recurring indie-game format and began inviting developers onto the stream. The interesting part happened while I was playing: I could encounter the game as a new player while the person who built it was sitting there, ask why something worked the way it did, and let them see where I understood, hesitated or got confused in real time.

Developer-session loop

Find a game

Build a pipeline of indie projects.

Play live

Encounter it as a new player.

Talk with the maker

Discuss mechanics, choices and confusion in real time.

Carry the relationship forward

Some developer connections continued after streaming ended.

Those sessions also gave the games exposure to a live audience and gave me repeated practice interviewing developers and talking about mechanics, design choices and player experience. I built a pipeline across PC, VR and mobile projects to keep the format running, and some of those relationships continued after I stopped streaming regularly.

04 · Business experiment

I also treated the stream as a small business experiment.

Alongside the live channel, I tested creator platforms, Twitch monetization, short-form content, YouTube, outsourced editing, campaigns and other ways the work might become sustainable. The channel became a functioning small platform with its own community, production system and developer relationships.

Continued growth would have required much more of the day-to-day creator job: public performance, promotion, constant community maintenance and attention management. I stopped regular streaming, but by then the experiment had already done what I originally wanted it to do. I had learned the ecosystem and built direct relationships inside games.

Building a Twitch channel from zero as a practical route into games.