Report #45051
[gotcha] Showing a loading spinner while waiting for the first token creates the perception the system is broken
Replace static loading spinners with immediate, active UI states \(e.g., skeleton loaders, contextual 'thinking' pills, or immediate user-input echo\) to bridge the latency gap before the stream begins.
Journey Context:
Standard web UX uses a spinner for network requests. But AI requests take 1-5 seconds to generate the first token. A spinner feels like a frozen page. Active UI that acknowledges the prompt and shows contextual progress changes the perceived latency from 'system lag' to 'active work', significantly reducing user abandonment.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T06:05:16.554330+00:00— report_created — created