Apple @ Work: Apple TV proves to be more reliable than Android in new digital signage report. The headline landed last week. It will be cited in every vendor slide deck for the next twelve months. Ignore it. Most UK workplaces already have Android TVs, tablets or phones on walls, in reception or on factory floors. Replacing them with Apple hardware is a capital request few facilities managers will win. The question is not which ecosystem is theoretically better. It is whether the screens you already own can do the job, what breaks when they try, and how much it will actually cost to keep them running for the next three to five years.
What an Android TV can do as a signage endpoint
An Android TV, tablet or phone can:
- Show a playlist of images, videos and web pages on a schedule.
- Interrupt that playlist with an emergency alert within two seconds of the message arriving on the local network.
- Display the alert in full-screen, with audio tone and scrolling text, regardless of what was showing before.
- Recover the original playlist once the alert is dismissed or expires.
- Report its own status, online, offline, last content update, back to the server every 30 seconds.
That list covers 90 % of what most workplaces need. The remaining 10 % is where the problems start.
What an Android TV cannot do, or cannot do reliably
No guaranteed wake-from-sleep
Android devices can be set to wake at a specific time, but the setting is not enforced by the operating system. Manufacturers add their own power managers that override it. A screen that should wake at 7:00 may stay off until someone taps the remote. Workarounds exist, USB wake-on-lan dongles, scheduled power cycles, but they add points of failure and maintenance.
No enforced single-app mode
Android supports a kiosk mode, but it is not locked down by default. A firmware update, a power cycle, or a stray touch can exit the signage app and show the home screen. Dedicated players run a single firmware image with no escape. Android devices run a consumer operating system that assumes someone will want to check email or stream Netflix.
No uniform remote management
Android’s Device Policy Controller (DPC) lets IT push settings, but support varies by manufacturer. Samsung Knox, Sony Enterprise, and Lenovo Device Manager all implement DPC differently. A setting that works on one model may not work on another, even from the same brand. IT teams end up maintaining a compatibility matrix and testing every firmware update before it is pushed to production.
No guaranteed HDMI-CEC control
HDMI-CEC lets the device turn the TV on and off. It works on paper, but in practice it is flaky. Some TVs ignore the signal; others interpret it as a request to enter standby. The only reliable way to control power is to leave the TV on 24/7, which shortens panel life and increases energy costs.
No long-term support
Consumer Android devices receive security updates for 24 to 36 months. After that, the device is exposed to vulnerabilities that can be exploited over the local network. Dedicated players are supported for five to seven years. Workplaces that keep Android screens beyond their update window must isolate them on a separate VLAN, which adds complexity and cost.
The permissions that trip up deployments
Android requires explicit permissions for almost every function. These are the ones that most often block a smooth roll-out:
| Permission | What it controls | What happens if it is denied |
|---|---|---|
| Display over other apps | Emergency alerts | Alert appears behind the playlist, not on top |
| Modify system settings | Screen brightness, volume | Brightness stays at 100 %, volume at 50 % |
| Run at startup | App starts on boot | Screen shows home screen until someone taps the app icon |
| Keep screen on | Prevents sleep | Screen dims after 30 minutes, then turns off |
| Access network state | Reports status | Server shows screen as offline, even when it is on |
Permissions are granted during installation, but they can be revoked by a firmware update or a factory reset. IT teams must either lock the device to prevent changes or build a monitoring system that alerts when a permission is lost.
How to work out the real cost against dedicated players
The upfront cost of an Android screen is zero if you already own it. The real cost is in the labour to keep it running. Here is how to estimate it.
Capital costs
| Item | Android screen | Dedicated player |
|---|---|---|
| Hardware | £0 (existing) | £200–£400 per unit |
| Power supply | Included | Included |
| Mounting | Included | Included |
| HDMI cable | Included | Included |
Operational costs over five years
| Item | Android screen | Dedicated player |
|---|---|---|
| IT labour (setup) | 2 hours per screen | 30 minutes per screen |
| IT labour (maintenance) | 4 hours per screen per year | 30 minutes per screen per year |
| Energy (24/7) | £12–£18 per year | £8–£12 per year |
| Replacement (panel failure) | 10 % per year | 2 % per year |
| Security updates | Manual VLAN management after 36 months | Included for 60 months |
Total cost of ownership over five years
| Scenario | Android screen | Dedicated player |
|---|---|---|
| 10 screens | £1,800–£2,500 | £2,800–£4,500 |
| 50 screens | £9,000–£12,500 | £14,000–£22,500 |
| 200 screens | £36,000–£50,000 | £56,000–£90,000 |
The Android option is cheaper in every scenario, but the gap narrows as the number of screens increases. The break-even point is around 300 screens. Below that, the labour cost of maintaining Android devices outweighs the capital cost of dedicated players.
Where Android screens make sense
- Small deployments (under 50 screens). The capital saving justifies the extra IT effort.
- Temporary installations. Trade shows, pop-up offices, or seasonal retail where screens will be repurposed or retired within 24 months.
- Low-risk environments. Reception areas, break rooms, or corridors where a blank screen is an inconvenience, not a safety hazard.
- Workplaces with in-house IT. Teams that can build automation scripts and monitoring tools to compensate for Android’s inconsistencies.
Where dedicated players make sense
- Large deployments (over 200 screens). The labour cost of Android maintenance scales linearly; dedicated players do not.
- High-reliability environments. Hospitals, control rooms, or manufacturing lines where a blank screen can delay a response or stop production.
- Regulated industries. Financial services, healthcare, or utilities where long-term security updates are mandatory.
- Workplaces without IT. Schools, care homes, or small businesses that cannot afford to troubleshoot firmware quirks.
What to do next
- Audit your existing screens. Note the manufacturer, model, Android version, and whether they are still receiving security updates.
- Test a single screen. Install the signage app, grant all permissions, and leave it running for 72 hours. Note any crashes, permission losses, or unexpected reboots.
- Estimate IT labour. Multiply the number of screens by 2 hours for setup and 4 hours per year for maintenance. Compare it to the cost of dedicated players.
- Decide on a pilot. If the numbers make sense, run a 30-day trial with 5 to 10 screens. Track uptime, IT effort, and user feedback.
- Plan for replacement. Android screens will fail sooner. Budget to replace 10 % of them every year after the third year.
Do not assume that because the screens are already on the wall, they are free. They are not.
