Notes on running screens: publishing and scheduling, pairing and access, offline playback, and what a workspace can tell you about a screen that is not playing.
Sample posts — written for layout review, not published articles
How a paired screen decides what to show next, why the schedule is evaluated on the device, and what happens when the network drops in the middle of a publish.
Unattended screens sit in lobbies and shopfronts where anyone can reach the hardware. Here is how a short-lived pairing code, a keyed device identity, and key rotation keep a workspace in control of what a screen can do.
Screens have to keep playing through a dropped connection, a flaky router, and a power cut. Here is what has to be true on the device before any of that happens.
Waiting for somebody to notice a dark screen is not monitoring. Here is the small set of signals that shows a screen is alive, current, and playing what you published — and the design that keeps them cheap.
Every workspace is a separate tenant with its own screens, media, playlists, members, and billing. Here is what that means for every query behind the dashboard.
Handshakes, update windows, and restart routines: the practical checks that keep a display playing in a space nobody looks behind until something goes wrong.
VIEWIX DISPATCHES
Nothing is being sent, and there is nothing to subscribe to while the posts on this page are sample content. Submitting the form below will tell you where to reach us instead.
