Chat

@summonware/ui · chat · P3 · Advanced UI
No reference page demonstrates this component — it was inferred from the screens that use one, so there is no variant matrix behind it.

Usage

A message thread — bubbles aligned by `self`, timestamps, author labels on the other party's messages. The data shape and rendering, not a full messaging product (no typing indicators, read receipts, or transport) — those belong to whatever real-time layer wires messages into `messages`.
import { Chat } from '@summonware/ui';

Best practices

DoOmit `author` on the current user's own messages (`self: true`) — the alignment already says whose message it is.
Don'tUse this for a single confirmation or system message. That is `Toast`/`Alert` — a thread implies an ongoing back-and-forth.

Examples

Common configurations, variations and states.

Support thread

Ada Lovelace
Can you take a look at the invoice export bug?
9:41 AM
On it — looks like a timezone offset issue.
9:43 AM
Ada Lovelace
Makes sense, thanks!
9:44 AM
A real back-and-forth, not a single message.

Where it appears

Used on 1 catalogued screens, including application-chat.