Choose an agent and state, then compare how the same signal adapts to tablet, e-ink, ESP32, LED matrix, control deck, and terminal constraints.
Preview controls
Asset Reference
iPad (iPadOS)
Android tablet
Android e-ink
ESP32 LCD
Pixoo64
Pixoo Focus
Enlarged Pixoo64 check. Use this panel to judge whether the selected creature, nearby asking bubble, session dots, and HUD still read at real LED scale.
TUI Focus
Enlarged terminal terrarium check. This panel now favors actual character/asking placement over full dashboard recreation so sprite readability is easier to judge.
Device previews
Each frame keeps the target surface's real aspect ratio and constraints. LED matrices, Stream Deck, D200H, TUI, and every ESP32 surface use canonical renderer output; the iPadOS, Android tablet, and Android e-ink views are clearly identified browser approximations because SwiftUI and Compose do not run here. Each app is a separately designed UI — the macOS dashboard is the app itself and is not previewed as a frame.
iPad (iPadOS app). Asset-faithful silhouette in the terrarium, no rear sparkle, ellipsis ask chip.
Android tablet (Compose app). Same silhouette language as Apple with a denser HUD — a distinct UI from the Android e-ink layouts below.
Android e-ink (B&W). Landscape monitor layout: left agent column, right aquarium, context/status row, and bottom timeline.
Android e-ink (color, Kaleido 3). Same landscape composition, restrained color, static-friendly creature states.
Stream Deck+ session button. Premium Widget layout with gradient bg, edge color strip, and agent watermark — same SVG as the real plugin.
Ulanzi D200H — canonical 144×144 session key and the real 288×144 merged 5H/7D usage window (shared/src/d200h-layout.ts renderer, not an approximation).
XTeink X3 / X4 (community fork): these e-ink readers are rendered by the CrossPoint Reader fork's own firmware and register with the daemon over Wi-Fi — it shares InkDeck's e-ink layout SSOT, but its renderer lives outside this repository, so no canonical frame can be shown here. Specs are in the Devices catalog.
What this page proves: one session model can remain recognizable while respecting radically different pixel grids. For hardware specifications and connection paths, use the Devices catalog.