JstVision
A context-aware debugging workflow connecting session replay, event timelines, errors, traces, and related context.
A flagship JstVerify feature I independently conceived, named, designed, and built from scratch. It acts as a unified diagnostic interface that lets developers see multiple layers of application behavior at once, moving from user-facing behavior to technical evidence without jumping between disconnected tools.
Concept to implementation · Session replay · Event timeline · Tracing · Debugging workflow · Developer tools · Product design
Disconnected signals make investigations slow and easy to lose.
Debugging production issues often requires switching between session replay, frontend events, backend errors, trace context, request metadata, related sessions, affected users, source context, root-cause notes, and product analytics.
When these signals are disconnected, the investigation becomes slow, repetitive, and easy to lose track of. JstVision was designed to preserve context and make the investigation path visible.
It was designed like a diagnostic scan for software systems: giving developers layered visibility into complex behavior the way medical imaging reveals hidden structure.
I independently owned the full lifecycle.
- Identified the product opportunity
- Conceived the feature concept
- Named the feature
- Designed the workflow and UI
- Built the feature implementation
- Integrated context from sessions, events, traces, errors, and investigation data
- Designed the experience for moving through technical evidence without losing context
- Created feature positioning and customer-facing explanation materials
From user behavior to backend evidence, in one flow.
Start from the user session
JstVision begins with the user session and keeps replay, events, and technical context visible together.
Follow the event timeline
The event timeline helps users move through the investigation in sequence, with relevant user actions and system events preserved in context.
Connect to backend evidence
Backend signals, trace metadata, and root-cause hints are surfaced alongside the replay so developers can connect user-facing symptoms to system behavior.
Preserve investigation context
The interface preserves active investigation context so users move through related pages, panels, and signals without repeatedly searching or reselecting the same session, trace, or error.
A unified diagnostic interface.
- Synchronized timeline combining frontend events, API calls, backend traces, and database activity
- Navigation for exploring related events, traces, sessions, users, and errors
- Zoomable timelines for deep inspection of system activity
- Visualization of causal relationships between interactions, API calls, processing, and data
- Context-preserving investigation workflows that reduce repeated searching and re-selection
- Keeping replay and technical context visible together
- Using event timelines to create an investigation path
- Surfacing root-cause hints and trace context near the relevant moment
- Preserving active context across pages and views
- Designing panels for progressive disclosure instead of overwhelming users
- Connecting session behavior to backend evidence and related signals
- Making the workflow understandable to developers, product teams, and leadership
Work within an investigation, move across views, keep your place.
A major design pattern in JstVision is context-aware navigation. Users can work within an active investigation and move across related views while preserving the relevant session, trace, error, event, or filter context. This reduces repeated searching, re-selection, and cognitive load during complex debugging workflows.
I developed similar context-preservation patterns across both JstVerify and Tempo EMR, where the active workspace might be a user session, investigation, patient, therapy session, or filtered view.
From product gap to usable technical workflow.
JstVision demonstrates my ability to identify a product gap, design a complex technical workflow, build a feature from concept through implementation, work with observability, replay, errors, traces, and event context, design context-aware navigation, and turn ambiguous technical problems into usable product experiences.
Next case study
Tempo EMR