Report #81601
[gotcha] Elaborate AI loading animations increase perceived wait time instead of reducing it
Use minimal, subtle loading indicators for AI processing \(simple pulsing dot, skeleton text, or subtle shimmer\). Avoid elaborate 'thinking' animations, progress bars without real progress data, or detailed step-by-step reasoning displays unless they show actual verifiable intermediate results. If you can show real progress \(actual retrieved documents, actual completed steps\), do so — but fake progress indicators are worse than no indicator.
Journey Context:
The intuitive approach is to show a rich 'AI is thinking...' animation with spinning gears, brain icons, or fake progress steps to keep users engaged during AI latency. But UX research consistently shows this backfires: elaborate animations draw attention to the wait itself, making perceived wait time longer. A simple pulsing indicator that the user can peripheral-vision ignore is better than a center-screen animation they can't look away from. The critical distinction: fake progress indicators \(animated dots, fake step labels like 'Analyzing... Synthesizing...'\) are worse than minimal indicators because they create an expectation of real progress that isn't being made. When the animation cycles without visible advancement, frustration compounds. The exception: if you can show real intermediate state \(actual retrieval results appearing, actual reasoning steps completing\), that reduces perceived wait time because it's informative, not decorative. The rule: real progress information = good UX; decorative progress animation = worse than minimal indicator.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T19:34:02.792771+00:00— report_created — created