Role
Lead Product Designer
Timeline
Dec 2022 - Jan 2024
Teamstream Multiviewer
An esports streaming platform that gave fans more control, context, and engagement by letting them watch up to 9 live streams at once.
I led the redesign of a community-driven multiviewer that redefined esports viewing by enabling fans to follow multiple streams and shift perspectives seamlessly. The product improved satisfaction, retention, and engagement, reaching over 165K+ viewers during major live events.
My Role
Responsibilities
Collaborated with the founder/lead developer and two engineers.
Led the redesign of the multiviewer interface and scalable system.
Defined the end-to-end product experience from concept through MVP.
Integrated community feedback to refine layouts, improve clarity, and enhance usability.
Impact
Results
Exposure: Reached 597K+ hours watched and 165K+ peak viewers across major Apex Legends esports events, with creators like NickMercs, ImperialHal, and NiceWigg showcasing the multiviewer.
Adoption: 65% of fans used the multiviewer during live events, averaging 3–4 streams watched simultaneously.
Engagement: Boosted watch time by 28%, reduced drop-offs by 22%, and increased return viewership across multi-day events.
Community: Feedback highlighted “no more juggling tabs” as the most valued feature.
Problem
Reduced excitement, context, and engagement
Esports fans wanted to follow multiple perspectives, but existing tools made it frustrating. Traditional squad streaming was fragmented, forcing viewers to juggle tabs, miss key plays, and lose context in the middle of the action.
Main Issue
Multiple Stream Tabs
Switching tabs caused viewers to miss key plays and lose the flow of the event.
Beta Build
The foundation for what fans truly wanted
The first beta allowed up to four streams, but viewers quickly hit its limits. There was no way to organize layouts, control audio, or keep track of key moments. This version revealed that fans wanted more than just multiple screens; they wanted control and clarity across every match.
Testing Platform
Early Prototype
Focused on proving the concept and supported only 4 screens.
Community Feedback
Shaping the experience around real fan needs
Teamstream’s multiviewer was built with the community at its core. Early testers and esports fans surfaced both pain points and opportunities, and their input directly shaped design decisions that balanced clarity, control, and engagement.
Collaboration
Turning feedback into progress
Held quick biweekly standups to review Linear tasks, align on design system updates, and prioritize changes based on community feedback and bug reports.
Component Structure
Built a systematic layout for each component to keep complex interactions clear and consistent. Documentation and redlines defined spacing, and hierarchy to align UI patterns across every module, ensuring scalability and visual clarity for future features.
Updating Stream Limits
Early testers asked for the ability to open unlimited streams, but many reported performance issues and overwhelming layouts when more than 9 were visible.
Why
9 streams balanced flexibility with usability and performance.
It gave users enough perspectives to follow at least 2+ teams while keeping the UI manageable and the experience stable.
Impact
Testers found this limit “just right.”
The 9-stream cap balanced control with ease of use, directly boosting engagement, satisfaction, and adoption.
Twitch Following Integration
Users wanted an easier way to find their favorite streamers inside the multiviewer, requesting the option to use their own Twitch following list instead of relying only on search.
Why
Following integration was necessary.
Pulling the Twitch API following list reduced friction in setup and made the experience feel instantly personalized, surfacing the streamers users already cared about.
Impact
Became the most popular entry point.
Users described it as “the fastest way to watch my Twitch follows together”, and it became one of the most frequently used entry points into the product.
Easy Chat Switching
Users wanted to be involved in multiple Twitch chats. They wanted to stay connected to to chat community and memes.
Why
Let users engage without losing the broadcast flow.
We designed easy chat switching, allowing fans to flip between active stream chats inside the multiviewer without leaving the stream.
Impact
Testers said it "kept the Twitch vibe and easy to follow the chat."
Users highlighted it as one of the most immersive features, keeping them engaged with the community while watching multiple perspectives.
Engagement at Scale
Across major Apex tournaments like MFAM Gauntlet and OTKNetwork Invitational, Teamstream reached 165K+ peak viewers and over 1.1M total hours watched.
Metrics
Metrics
Retrospective
Built with the community, for the community
Teamstream’s multiviewer was shaped by our most active Twitch broadcasters and their communities. Their real-world feedback guided every iteration, helping us design an experience that felt intuitive, engaging, and built for how fans actually watch esports.
Product Takeaways
Fin
Designing for scalability and simplicity
Balancing flexibility with clarity was key. Limiting to 9 streams and refining UI hierarchy ensured the product felt powerful without overwhelming users.
Feedback drives better design decisions
Building alongside the esports community surfaced real use cases early. Their feedback directly informed feature priorities like easy chat switching and Twitch integration.
Personalization increases engagement
Using Twitch’s API to pull followed channels made the product instantly familiar and boosted retention showing that even small personalization steps can drive major impact.
Data validates design
Event analytics (165K+ peak viewers, 1.1M+ hours watched) reinforced that good UX scales. Strong design decisions translated directly into higher engagement and watch time.
More Projects
View more of my work!