Issue ticket: https://github.com/livepeer/explorer/issues/694

This page converts competitive teardown findings into a clear set of Explorer-specific UX gaps. Each gap should be mapped to a concrete Explorer screen, flow, missing state, or missing explanation, and should connect back to evidence from the competitive teardown, scenario analysis, or Explorer baseline review.

This is the bridge between research and design: the output should explain what is currently falling short, why it matters, and what kind of follow-on work it should feed into.

Gap Specification Matrix

Rules

Map each gap to a specific Explorer area, such as:

• delegation discovery
• readiness / prerequisites (onramping, staking, etc.)
• orchestrator selection
• delegating
• monitoring
• switching / exit

Severity options:

• blocking
• friction
• polish

Estimated Effort options:

• small
• medium
• large