Sports Streaming Platform
Product design and technical proof for a private live-event experience
Product Design + Frontend Prototyping
3-person studio + client team
2026 · Prototype · In development
Figma, Paper, OBS, Frontend tools
Interface architecture, Responsive prototype, Local proof
Extend the event beyond the physical venue
The team was already developing a landing page, ticket sales, and registration for a combat-sports organization. A new product question emerged inside that work: how could a remote audience access a private broadcast without separating it from the event experience?
My responsibility focused on exploring that product line and supporting visual improvements to the public presence. Ticketing, backend architecture, and access hardware were owned by other team members.
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.
These modules could coexist beside the player on desktop. 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.
Separate what we knew from what we expected
The direction came from the client brief, team reviews, and streaming-platform benchmarks. Spectator interviews and usability tests have not happened yet.
The ability to extend event reach, create participation through interaction, and build trust with real event content remain design hypotheses until they are tested.
Prototype independently, integrate deliberately
An independent 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.
A local technical proof
A local server and OBS test received a real signal before the team selected a final streaming provider.
Move from generic action to real context
I supported the team in shifting from generic imagery toward event cards and participant profiles grounded in the real product. The intent was to improve context and perceived legitimacy.
Stakeholders approved the direction in design reviews, but trust and conversion have not been measured.
A working concept—not a launched streaming platform
The public landing page and ticket purchasing belong to the product shipped by the broader team. The streaming experience remains in development and has not been used in a live event.
The verified result of my contribution is a responsive prototype and a successful local technical test, not a live platform or a new revenue stream.
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.
Industrial Operations Platform
