Revamping the Creator Dashboard at Streamly: A Before/After Redesign That Prioritized Live Metrics

Tech · 6 min read

Revamping the Creator Dashboard at Streamly: A Before/After Redesign That Prioritized Live Metrics

Streamly, a niche live-streaming startup for small creators, had a dashboard that mixed historical analytics with noisy live data and a complex settings layout. Creators reported confusion about what was happening during a live stream and where to act to improve engagement. The design goal was to make “live signal” the primary focus while keeping historical context available but secondary.

The redesign layered information: a top-level live strip with concurrent viewers, chat health indicators, and real-time engagement trends, followed by collapsible historical panels. The team replaced heavy polling with WebSocket-based subscriptions for live metrics, falling back to lightweight polling when a socket wasn’t available. Designers simplified the visual hierarchy—bold live numbers, muted historical charts—and introduced quick actions (pin clip, pop-up moderator) directly in the live strip.

Technical trade-offs included ensuring the WebSocket scale could handle spikes during peak streams. The engineering team implemented sampling and adaptive refresh rates for non-critical metrics to reduce bandwidth usage. Instrumentation was added to track how often creators used quick actions; within eight weeks, creators using the new live strip performed 35% more moderator actions and daily active creators increased 22%. Support tickets about “not knowing live viewership” decreased 41%.

The outcome reinforced a principle: prioritize the user’s immediate context (live) and make actions obvious and within reach. Streamly’s combination of front-end hierarchy changes and targeted real-time infrastructure improvements produced both UX clarity and operational gains.