Devices & Offline Playback
Pair a screen with a six-digit code, and let it keep playing when the network does not.
Adding a screen takes about a minute. The player app displays a six-digit pairing code, you type it into KIMISUITE, and the device is bound to your workspace and assigned to a location and a group. Android TV and Amazon Fire TV are the launch platforms; Samsung Tizen and LG webOS players follow against the same API.
After pairing, the device authenticates with its own token and asks what it should be playing. It downloads only what has changed, stores the assets locally and plays entirely from its own storage. The schedule is interpreted on the device, so dayparting keeps working with no connection at all.
If something does go wrong, the last valid campaign keeps running and a per-device fallback covers the rest. A blank screen in a customer-facing space is the one failure mode that matters, and the whole architecture is arranged around not producing one.
Key Benefits
Pair a screen with a code — no cables, no config files
Android TV and Fire TV at launch, Samsung and LG to follow
Only changed content is downloaded
Playback and scheduling run locally, fully offline
Last valid campaign keeps playing if the network drops
Per-device fallback so a screen is never blank
Use Cases
Shop with unreliable Wi-Fi
The connection comes and goes all day. The screen does not care; it plays from its own storage and syncs when it can.
Opening a new branch
Post the streaming stick, tell the manager to read out the code on screen, and content is running before the shelves are stocked.
Screen behaving oddly
The device list shows last sync, active campaign, storage and app version. Restart the sync or force a refresh without leaving your desk.