Versioning & updates
DisplaySync ships as three runtime components — the desktop sign, the web dashboard, and the mobile app — each on its own update cadence, tied together by one compatibility rule.
Versioning
All three components use semantic versioning. The backend is wire-compatible with at least the previous two desktop-sign minor releases, so an older kiosk fleet keeps working while the backend rolls forward independently.
How updates reach each platform
| Platform | How it updates |
|---|---|
| Desktop sign | Operator-triggered only, from the dashboard — Update Sign App or a bulk update across an event. Updates are never pushed to a running kiosk; nothing installs without an operator starting it. |
| Web dashboard | Continuous deployment — no install step. Refresh the dashboard to get the current production build. |
| iOS | The App Store — install and update like any other app. |
| Android | Closed testing — ask the DisplaySync team for an invite; updates arrive the same way store updates do. |
Your current desktop-sign version: check Sign detail → Device info → App version in the dashboard, or the Status Dashboard overlay (Ctrl+Shift+S) on the kiosk itself.
See also
- Update Sign App — how to deliver a desktop sign update to a deployed fleet
- Bulk actions & schedules → Bulk update — updating many signs at once
- Stability over features — why desktop updates are operator-initiated, not automatic