Two clients for
Axon, each driven
through a scripted tour of the same seeded demo world.
axon-tui — terminal
The keyboard-first terminal client.
The tour covers, in order:
the room list, with sort, filters and a live name filter
a timeline with formatted messages, replies and reactions
adding a reaction, then withdrawing it
threads, edits and redactions
inline photographs and a full-size preview
full-text search across rooms, narrowed by a room filter
jumping to a date in history
sending a message
the keyboard-shortcut and help popups
The images really are drawn in the terminal — Sixel, Kitty or iTerm2
graphics, depending on what the terminal supports — not approximated
with block characters.
axon-web — desktop
The browser client at a desktop window size.
The tour covers, in order:
the room list — sort, filters, a live name filter, DM titles, and room
information
the spaces rail filtering the room list by hierarchy
a timeline with formatted messages, replies, reactions and day
separators
an edit applied in place, a redaction, and the thread panel
an image gallery and the lightbox paging through it
full-text search — scoped to the open room, widened across all rooms,
narrowed again by room, then followed as a deep link
sending a message and a reaction, then undoing both
the keyboard-shortcut map
axon-web — mobile
The same client on an iPhone 13 profile: real touch, a phone-shaped
viewport, and the single-pane layout that comes with it.
Not the desktop take in a narrower window. Below the two-pane breakpoint
the room list and the spaces rail move behind navigation, so the tour
leads with the transitions instead:
one pane at a time, chosen by the route, and Back
reading a room, and the room-information panel
the thread drawer stacked over the room
a gallery and the lightbox, by tap
search, and a hit followed into a room it was not in
sending a message and deleting it, with touch-sized actions
What you are looking at
Everything on screen is fictional and reproducible: personas, rooms and
messages come from a declarative corpus that a throwaway Synapse + Axon
stack renders on demand, so the same recording can be re-shot after a UI
change. Both clients read that world over the same /v1/ API
from the same live Axon — the search results come from a real Tantivy
index and the photographs really do travel through the media proxy.