Android MDM for digital signage: what a big fleet needs

The three jobs a signage fleet needs

Every MDM comparison page carries a longer feature list, but a signage fleet runs on three, and everything else on the list is compliance or convenience. Both of those are priced in, which is the point of the next section.

Kiosk lockdown. The screen shows the player app and nothing else: no home screen, no settings, nothing a passerby can open. On Android this runs on device owner enrollment: the management agent is provisioned as device owner when the device is set up, and lock task mode pins the one app the fleet runs. The platform has documented this combination, device owner plus screen pinning, since Android 5.0.

A single screen needs none of this machinery: set the player as the home app and the show comes up full screen at power-on with no launcher and no keyboard, which is how a single screen is locked down without any MDM, and the Android signage app startup guide walks through it. A fleet needs the managed version of the same idea, because nobody walks 16 cities setting home apps by hand.

Remote app install and update. When the player app on 800 screens needs a fix, it goes out from a console, not in a van. On Android Enterprise dedicated devices, apps are added to managed app distribution and assigned to the devices, and each device pulls its assigned apps the next time it reaches the network, so an update waits out a screen that has been offline for a week and lands the next time it connects. Your MDM vendor's Android Enterprise documentation walks through adding and assigning apps this way. That covers the apps. The shows themselves travel by other routes, compared in updating multiple digital signage screens remotely: 3 ways; the MDM console is the layer that keeps the app underneath them current.

Remote view. The third job is seeing what the screen actually shows: the right playlist, the right orientation, no frozen panel. Remote view is a live stream of the screen over the network, so it lags on a poor link. Test it on the worst building you operate, not on the office network, because the building with the bad switch is where the feature earns its rate.

What decides it: the pricing model

MDM pricing comes in three shapes, and at fleet scale only one matches the thing that drives your bill.

Per device: every enrolled screen carries a rate. The bill scales with the fleet, which is exactly the thing you add.

Per seat: the bill follows the administrators. It fits corporate phone fleets, where thousands of devices are handled by an IT department, and it misfits signage, where 800 screens are run by a handful of people. Seat pricing prices the constant and ignores the variable.

Bundled suite: one rate covering kiosk, app management and remote view, plus encryption policy, app configuration and compliance reporting. Take it when those extras are requirements. Otherwise you are paying, in every billing cycle, for modules the fleet never opens.

Commit to per-device pricing for a signage fleet, and get the rate at your volume in writing. Then ask which of the three jobs are sold as add-ons, because a low headline rate with remote view sold separately can turn into the expensive quote.

Recommendation: for a fleet in the hundreds of screens, choose a signage-focused management layer priced per device that covers kiosk lockdown, remote app install and update, and remote view, built on Android Enterprise device owner enrollment. Move to a general-purpose MDM suite only in the three cases listed below. Skip free tiers entirely at this scale: they are pilot tools, and a pilot tool does not answer for 800 screens in 16 cities.

The options at fleet scale

The second row is the default for the fleet described here. The first row wins when every screen only loops content and the CMS's own update path covers every change; the third row when compliance is a written requirement; the fourth when you have the engineers and want the control that comes with reading the source. What free software, including the open-source route, really trades away is compared in free digital signage software: freemium, open source or DIY.

Worked example: staffing the monthly check of 800 screens in 16 cities

Take a fleet of 800 screens spread over 16 cities, with a rule that every screen is checked once a month: connect remote view, confirm the current show is playing, confirm the panel is alive, close the ticket.

Inputs. 800 screens and 16 cities are the fleet in this case. The monthly cadence is the check rule this example budgets. 5 minutes per remote-view check is a planning assumption, and it is the number that moves the result: at 10 minutes per check, the result doubles. 21 working days stands in for one working month.

The rule. Checks per working day equals screens divided by working days. Operator time per day equals checks per day multiplied by minutes per check.

The arithmetic.

• 800 ÷ 16 cities = 50 screens per city on average. Fifty in one city is already too many for routine site visits, and the average hides the worst city, which is the one that sets the travel budget.
• 800 checks ÷ 21 working days = 38.1, so call it 38 checks every working day.
• 38 checks × 5 minutes = 190 minutes, which is 3.2 hours of one operator's day.

The result. One person holds the monthly cadence with about 3.2 hours a day of remote-view checking. At 10 minutes per check the same cadence takes 6.3 hours, and the check starts competing with the rest of the desk's work; the fix is a faster check or a second operator. Take remote view out and the arithmetic stops being desk work: 38 site visits a day across 16 cities is a travel budget, not a line on a to-do list.

The decision. Remote view is the first feature worth its per-device rate at this scale, because it turns a travel budget into 3.2 hours of desk time. Kiosk lockdown and remote app updates keep the fleet sealed and current; remote view is what lets one person verify it every month.

When a general-purpose MDM is the right buy

Three cases, and otherwise stay with the focused layer.

A written security policy. When a customer, an insurer or an auditor requires encryption attestation, app configuration controls or compliance reporting that the signage layer does not carry, the suite is the answer, because adding the compliance module to a console that already manages the fleet beats running a second console for the same screens.

The devices do a second job. An Android box that plays a show from open to close and does something else after hours carries two requirement sets, and one suite that covers both is simpler to run than two tools.

An existing console. If your organization already runs a suite at scale and the per-device rate for extra units lands close to the focused tool's, adding the screens to the console you have is less work than standing up a second one. Check the suite's kiosk and remote-view modules before relying on this; every suite has them and they are not equally good in all of them.

On the security worry that hangs over low-cost tools: a free or open-source layer is a legitimate fleet choice when it works through the documented mechanisms, device owner enrollment and managed app distribution, and when you can read what it runs. A closed tool that is free and undocumented is not a fleet plan at 800 screens.

When the screens need no MDM at all

If the screens' only job is looping a playlist, the management problem can live inside the player, and the MDM line disappears. Our own displays take that road: the included player starts the show at power-on with nothing else on screen, and if the app stops it is designed to start again within seconds and go back to playing. That covers lockdown and recovery without a console. The update path and what the no-subscription road really costs are described on the signage player page and in what no-subscription signage really costs.

A fleet already running third-party Android boxes should decide the platform question on its content workflow, not on the management line of the budget. If the boxes run apps a plain signage player does not, keep them and manage them; if they only loop shows, replacing them may remove the problem the MDM was going to solve.

What to ask before you sign

A short list, in the order the answers change the decision.

• The per-device rate at your volume, in writing, and which of the three jobs are paid add-ons.
• The documented enrollment path. Device owner is provisioned while the device is set up, so a box already running in the field generally has to be reset before it enrolls. If a vendor promises a no-visit rollout onto installed screens, ask for the documented enrollment steps that make it possible.
• Whether app updates run through managed app distribution, so a screen that has been offline for a week picks the update up the next time it connects.
• What a remote-view session needs from the network. One session on your worst site beats any spec sheet.
• The exit: un-enroll a screen, keep the player working, and move the device on without a brick.

And when part of the fleet is ours: tell us the place, the sizes and the quantity, and we quote the displays set up as a sign, with the player included and no subscription. The management console then only has to cover the screens that are not ours.

Questions