Real-Time & Streaming

Implement push-driven Hotwire behavior with Turbo Streams and Stimulus.

Core Workflow

1. Identify transport and delivery shape: WebSocket, SSE, inline stream tags, or server response streams.
2. Choose default Turbo Stream actions first; add custom actions only when defaults are insufficient.
3. Keep stream actions small and deterministic; avoid embedding arbitrary scripts in stream payloads.
4. Separate stream orchestration from domain UI concerns (forms, media, navigation).
5. Verify ordering, idempotency, and multi-tab behavior for all real-time updates.

Guardrails

• Prefer append/prepend/replace/update/remove/before/after/refresh before custom actions.
• Keep cross-tab sync explicit (BroadcastChannel/localStorage) and scope it to same-device semantics.
• Use view transitions only where animation meaningfully improves state-change clarity.
• Validate failure modes for delayed/out-of-order messages.