⚠️ Key Deadline: 1 April 2027
Google is removing Kiosk mode support for Chrome Apps on ChromeOS. Signagelive only supports the LTS update channel, so if you're running Signagelive on ChromeOS via the legacy Chrome App, it will stop working from this date. Migrate to the Signagelive Chrome IWA before then to avoid disruption.
Why is this happening?
Google is phasing out Chrome Apps across ChromeOS entirely, in favour of a new, more modern web app framework. This includes the removal of Kiosk mode, which the legacy Signagelive Chrome App relies on to run.
The removal has been happening in stages:
Date | What Changes |
July 2025 | Only administrators can install Chrome Apps — end users can no longer install them |
July 2026 | Chrome Apps in Kiosk mode are no longer supported on the Stable channel |
1 April 2027 | Chrome Apps in Kiosk mode are no longer supported on the LTS channel — the deadline that applies to Signagelive, since LTS is the only channel we support |
February 2028 | Full end-of-life for Chrome Apps across ChromeOS |
If you're not currently running Signagelive on ChromeOS devices, none of this affects you — no action is needed, though it's worth keeping in mind if you expand to ChromeOS in future.
What Navori Labs is doing about it
We've built the Signagelive Chrome IWA (Isolated Web App) — a new client for ChromeOS, built on Google's replacement framework, designed to be a like-for-like continuation of the service you already run. It's been available since 1 June 2026.
The Chrome IWA requires a companion Signagelive Companion Chrome Extension installed alongside it. Because of ChromeOS's security sandboxing, the IWA can't talk to system-level functions (device reboot, screen power, hardware metrics) on its own — the extension bridges that gap. Without it installed, the IWA won't display an activation code.
What to know before you migrate
A companion extension is required. The Chrome IWA won't function without the Signagelive Companion Chrome Extension installed in the same organisational unit.
Content has to re-download. ChromeOS can't share data between the old Chrome App and the new Chrome IWA for security reasons, so all media re-downloads after migration. For larger networks, plan a phased rollout to manage bandwidth.
Migration is one-way. Once a device has moved to the Chrome IWA, it can't be reverted to the Chrome App.
Your licence and schedules are preserved automatically. Player licences carry over via the device's hardware ID, and published content schedules stay intact on your Signagelive Network — you don't need to deactivate or reactivate anything.
Requirements: Chrome version 140 or newer, and an enterprise-enrolled device managed via Chrome Device Management (CDM).
Get started: guides for each step
Work through these in order if you're migrating for the first time, or jump straight to the one you need:
An introduction to the Signagelive Chrome IWA - What the Chrome IWA is, how it differs from the legacy Chrome App, and what to expect.
How to install the Signagelive Chrome IWA on ChromeOS - Step-by-step setup via the Google Admin Console, including region-specific Web Bundle IDs.
How to install the Signagelive Companion Chrome Extension - Required alongside the IWA — install this in the same organisational unit.
How to migrate from the Signagelive Chrome App to the Chrome IWA - The actual cutover: setting the IWA as your default kiosk app and what happens to your devices when you do.
FAQs and known limitations for the Signagelive Chrome IWA - IPTV isn't supported, notes on sync timing between devices, and other things worth knowing before you commit.
Need help?
If you're planning a migration across a large number of devices, or have any questions, our Support team can help you plan it — get in touch before you begin, especially for larger networks where a phased rollout is recommended.