Evolve: Private Live-Event Streaming Platform
Exploring a new revenue path for live events through private streaming, chat, and responsive viewing
Product Design + Frontend Prototyping
3-person studio + Evolve team
2026 · Prototype · In development
Figma, Paper, OBS, Next.js, PostgreSQL
Interface architecture, Responsive prototype, Local technical proof
Outcome
Responsive streaming concept validated with a local OBS + HLS technical proof.
Key decision
Keep the video experience primary and move secondary participation into on-demand surfaces.
Trade-off
Prototype credibility required separating tested facts from revenue and engagement hypotheses.
Next measure
Spectator testing and live-event usage need to happen before claiming product impact.
Bring the event to a remote audience
While the team built the website, ticketing, and fighter registration, I explored a private pay-per-view streaming experience.
My contribution covered the streaming prototype and visual improvements to the public website.
The video still had to be the product
A broadcast needs space, stability, and clear controls. At the same time, the concept explored participation through chat, voting, and event information beside the player.
On desktop these modules could coexist laterally. On mobile, they competed for limited space and risked degrading the main viewing experience.
Designing more interaction does not mean showing all of it at once.
Evidence and open questions
The brief, team reviews, and streaming references guided the concept. Spectator interviews and usability testing remain pending.
Remote reach and participation are still product hypotheses.
Prototype independently, integrate deliberately
An independent streaming module
The streaming interface was separated from the existing backend so its hierarchy could be explored without presenting unfinished integrations as complete.
Event-aware states
The concept covers before, live, and post-event states around the player, participants, chat, and voting.
Video-first mobile hierarchy
Secondary interactions move into on-demand surfaces so the player remains readable and usable on a narrow screen.
Local technical proof with OBS + HLS
I set up a local Next.js server with PostgreSQL, connected it to an OBS stream via HLS, and validated that the concept could receive a real video signal before selecting a final provider.
Show the actual event
I supported the shift from generic imagery to event cards, profiles, and fighter photographs.
The published site includes schedules, flags, and ticket purchasing.
Website live, streaming in prototype
The team published the landing, ticketing, and fighter registration with my design and UX support.
My responsive prototype received a real signal in a local OBS + HLS test. Streaming has not been used at an event yet.
Prototype credibility depends on precise language
- →Separating hypothesis, prototype, and implementation protects the credibility of the work.
- →Information architecture and error states should be defined before backend decisions harden.
- →In dense interfaces, hierarchy matters more than the number of features.
- →The next phase needs spectator testing and measurement defined before the first event.
See an opportunity to work together?
Let’s discuss a role or projectDivisan: Industrial Operations Platform
