User Experience & Feedback

Implement cross-cutting feedback and perceived-performance patterns in Hotwire.

Core Workflow

1. Identify feedback need: loading, submit activity, progress reporting, optimistic updates, or transitions.
2. Prefer built-in Turbo semantics first (busy, progress bar hooks, submit/render lifecycle events).
3. Add optimistic updates only with a clear reconciliation strategy.
4. Keep transition logic bounded to explicit lifecycle events and cache/preview-safe paths.
5. Verify UX behavior on slow network, back/forward cache restores, and submission failures.

Guardrails

• Do not use fixed timeouts as a proxy for network or render completion.
• Gate animations/transitions for previews and cache restores.
• Keep submit locking/unlocking symmetric between start and end events.
• Separate UX feedback logic from domain-specific form/media/navigation implementations.