A NoPixel multi-stream viewer connecting creators, crews, live perspectives, and broadcast history. Arrange your view and save it for later.
Product engineering / real-time systems
React
TypeScript
Effect
Cloudflare Workers
Durable Objects
Leaflet
My contribution
Designed and built the discovery-to-viewer experience, interactive layouts, crew following, live-data backend, scene library, map, and broadcast history.
Brick Bois · one main perspective · three supporting live previews
Arrange multiple perspectives in one view.
Give one perspective the main stage, or keep all four equally visible. Switch between layout presets, move or swap panes, and resize the splits to follow the story your way. Each channel keeps its own playback and audio controls.
Brick Bois · equal tiles · source-provided live previews
Open a crew’s live perspectives together.
Find a crew, inspect its roster, and open the available live perspectives together. A crew view can follow roster updates or become a saved selection you control. Twitch and Kick preferences connect discovery directly to the viewer.
Brick Bois roster · four live perspectives · public community data
Explore reported events on the city map.
The city map connects reported incidents with named participants and source details. It adds context to discovery while keeping the difference between a reported event and a confirmed live perspective visible.
City map · selected source-reported incident
Find the moment across broadcasts.
Choose a time to compare overlapping broadcasts and revisit available recordings. Twitch links can jump to an approximate offset. Saved private moments connect the viewer back to that history, even when you return later.
Broadcast comparison · reported starts and available VODs
Engineering decisions
Project overview
01Discover creators
02Follow a crew
03Arrange perspectives
04Save your view
05Revisit a moment
NoPixel roleplay unfolds across multiple creators’ streams. Following a crew means finding its channels, choosing perspectives, and keeping track of events across broadcasts. I built POVLINE to connect those tasks in one web application: discover creators, arrange a live multi-stream view, save it, and revisit moments through the map and broadcast history. The project covers the viewing interface, browser-local library, and live-data infrastructure. It is an independent fan project.
A viewing layout you can control
Save up to 24 perspectives in a view and watch up to four at once. Start with equal tiles or one main perspective, then move or swap panes, resize the splits, focus a channel, and undo layout changes. Playback, audio, and chat controls follow the selected channels. Supported players retain their identity during rearrangement, and the desktop mini-player keeps the view available while browsing. Reloads restore the selection with playback stopped.
Live data with explicit freshness and recovery
The Effect backend validates public feeds, caches snapshots, coalesces requests, and backs off after source failures. On Cloudflare, a Durable Object coordinates refreshes with alarms, persists snapshots and cooldowns, and sends updates over hibernating WebSockets. Supporting browsers share one connection across tabs; hidden or offline pages disconnect and recover from current snapshots. Polling remains a fallback. Source timestamps distinguish fresh, expired, and unavailable data.
Saved views with clear privacy boundaries
Discovery, watching, following, and saving work without an account. Search, filters, perspectives, and history dates are URL state, while saved views, follows, favourites, and notes stay in the browser’s library. Validated backups support private transfer and recovery. Shared links include the viewing configuration and exclude private notes and personal preferences. Public discovery, creator, crew, map, and history pages render on the server with descriptive titles and canonical URLs.