I have accumulated over a decade of experience in the realm of video player development. Interestingly, when things go awry, the knee-jerk reaction tends to be, “It must be the player’s fault.” However, I can reveal a spoiler: More often than not, the player isn’t the culprit.

Navigating the intricacies of media can be a daunting task. This complexity is amplified when you have only a limited perspective on the entire architectural stack. Thankfully, video players often serve as the convergence point on the client side, offering a treasure trove of information that, if properly harnessed, can lead you to the root of the problem—if only you knew where to look. Today, many companies lean heavily on analytics dashboards to pinpoint issues, which is undeniably valuable. However, in practice, we frequently encounter scenarios where these tools seem to work against us rather than for us when we’re attempting to identify the root causes of problems. Another prevalent issue is the prolonged turnaround time when addressing issues in the field, particularly when dealing with specific customers, devices, or locations. This challenge becomes even more pronounced when trying to replicate issues using a reference app that lacks the genuine threading, UI, and environment. I’m going to make the case that there’s no substitute for the effectiveness of interactive debugging in a live production environment. This talk was presented at Demuxed ’23, a conference for video nerds in San Francisco featuring amazing talks like this one.