Best Android kiosk mode solutions for retail (2026)

A tablet bolted to a shelf in a store gets poked by hundreds of people a week, and almost none of them work for you. Android kiosk mode is the difference between that tablet showing your catalog and showing whatever the last teenager searched for. Here's how the mechanism works in 2026, what to refuse to buy without, and how eight tools compare for retail.

What kiosk mode really means on Android in 2026

Behind every kiosk product sits one Android primitive: lock task mode. Google shipped it in Android 5.0 and it has barely changed since, which is why vendors all claim the same core feature. A device policy controller allowlists packages, the app enters lock task mode, and the user can't leave. Google's own documentation on lock task mode is worth reading once, if only for the distinction it draws with screen pinning: pinning can be exited by the user, lock task mode cannot.

Android 9 added the part that matters in a store. The lock task features API lets you decide, flag by flag, whether the home button exists, whether notifications appear, whether the battery and Wi-Fi indicators show. A customer-facing terminal turns all of that off. A stockroom scanner keeps the status bar, because the picker needs to see the battery.

Lock task mode only works if the enrollment underneath gives your tool device owner rights. That's dedicated device mode in Android Enterprise, formerly COSU, and it has to be set at first boot. You can't convert a phone already used as someone's personal device: reset first, then enroll by QR code, afw# identifier or zero-touch.

Three shapes of lockdown show up in retail:

• Single app mode. One app, full screen, nothing else reachable. Price checkers, queue-busting payment terminals, product finders.
• Multi-app kiosk. The management tool replaces the launcher with a restricted one showing three or four approved icons. A mobile checkout device that needs the POS app, a card reader utility and a scanner utility lands here.
• Kiosk browser. A hardened browser in full screen pointed at a web app, with URL allowlists and no address bar. If your store app is a web app, this is often all you need.

Those aren't alternatives in practice. A kiosk browser still needs pinning by lock task mode, or a determined customer swipes out of it. If the vocabulary is new, our kiosk mode glossary entry and the longer guide to kiosk mode across platforms cover iOS and Windows too.

What a retailer should actually demand

Most vendor pages show a screenshot of a locked tablet and stop there. Locking the device is easy. Keeping 300 of them alive across 80 stores for three years is where tools separate. Zebra's retail research found a third of the US retail workforce still has no dedicated mobile device, so many of these projects are first attempts by teams who won't get a second budget.

Six things to insist on:

• Silent remote updates, on a schedule you pick. The kiosk app will ship a new version. If that install needs a store employee to tap anything, you've lost. Ask whether updates can be forced outside opening hours, and whether you can roll out to ten stores before all eighty.
• Recovery after reboot and after a crash. Power cuts happen. Android kiosk software worth paying for comes back into the pinned app after a reboot without anyone logging in, and relaunches the app when it crashes. Test this by pulling the plug, not by reading the feature list.
• Rugged hardware support through OEMConfig. A Zebra TC series terminal has dozens of barcode parameters a generic console will never model: symbologies, beep on decode, key wedge behavior. Honeywell is the same. If the tool doesn't render OEMConfig schemas, you'll be configuring scanners device by device.
• Screen behavior you control. Screensaver, timeout, forced brightness, scheduled wake and sleep. A signage tablet that sleeps after thirty seconds is a broken sign. A checkout device that never sleeps is a dead battery by 3pm.
• A PIN exit for store staff. Someone has to reach Wi-Fi settings when the access point changes. Make it a code you can give a store manager, revocable per device group, logged.
• Working Factory Reset Protection. Retail hardware walks out of stores. Without FRP tied to a corporate account, a reset terminal is a clean consumer tablet worth reselling. With it, it's a brick. Register the allowed accounts before deployment, and write them down.

Two more only show up later: how the tool handles a device offline for a week, and whether kiosk policy lives in the same console as your security policy. Running kiosk lockdown in one product and device management in another means two agents, two bills and two places to look when something breaks. That's the main argument for a full platform over a dedicated kiosk app. Our own kiosk mode page lays out how we handle the policy side.

The eight tools side by side

The eight tools, one by one

Scalefusion

Scalefusion started as MobiLock, a kiosk product, and it shows. The configuration is the most direct of the bunch: pick single app or multi app, pick the apps, set the branding, done. Its kiosk pricing page lists Essential at $2 per device per month, Growth at $3.50 and Business at $5, billed annually, from ten devices. Kiosk mode for Android and iOS, website filtering and silent app deployment are in the cheapest tier, which is unusual.

The catch is tiering. Unattended remote troubleshooting, certificates and OS patching only appear in Business at $5. You'll want remote troubleshooting on a store fleet, so budget for the top tier, not the headline price.

Hexnode UEM

Hexnode is the broadest of the cheap options. Same console for Android terminals, iPads, Windows back-office machines and Macs, with Pro at $2.20, Enterprise at $3.20 and Ultimate at $4.70 per device per month, fifteen device minimum. Kiosk management for mobile is in Pro.

Its Android kiosk features are detailed, including peripheral control and a decent multi-app launcher. What frustrates people is the plan matrix: features you assume are basic sit two tiers up, and the Ultra plan bundling complete kiosk is quote-only. Price it with your real feature list in hand.

SureLock by 42Gears

SureLock is the veteran. It's an app you install to turn a device into a kiosk, on Android, Windows, Wear OS and even Windows CE, which still matters in warehouses running hardware from 2014. Single app and multi app, peripheral blocking, branded home screen, exportable usage analytics. 42Gears doesn't publish a price on the SureLock product page, so treat it as quote-based.

Be clear about what it is. SureLock locks a device down well, but remote configuration and fleet visibility come from SureMDM, a separate platform. SureLock alone means touching devices by hand: fine for thirty screens in one building, painful across eighty stores.

Appaloosa

We build an MDM and MAM platform hosted in France on SecNumCloud-qualified infrastructure, which is why most of our retail customers call us instead of a US vendor. On Android, kiosk mode sits on dedicated device enrollment: single app or a pinned set, home button and notification shade and task switcher gone, admin-controlled exit. Enrollment is zero-touch, QR code or Knox Mobile Enrollment. Apps come from managed Google Play or private APKs with silent install, and OEMConfig profiles cover Samsung Knox, Zebra and Honeywell settings including the barcode engine and the programmable keys. FRP, remote lock, locate and wipe, and screen sharing through TeamViewer live in the same console, described on our Android MDM page.

Pricing is public: €3.49 per device per month on Business from fifty devices, €5.49 on Enterprise from a hundred, with a €1 add-on for remote support, contacts sync and file sharing.

Where we're the wrong answer: you have fewer than fifty devices, you need ChromeOS endpoints, or you want a bespoke Android build for custom hardware. Esper is better at that last one. And if your estate is entirely Samsung and you're happy inside Samsung's tooling, paying us adds a layer you may not need.

Samsung Knox Manage and Knox Configure

Samsung sells most of the Android tablets in European stores, and it has two products here. Knox Configure pushes a ProKiosk profile at first boot, including web-mode kiosks that open a single URL full screen. Knox Manage is the management platform, with kiosk profiles in its console. Neither publishes a per-device price, so expect a quote.

The strength is hardware reach. Knox exposes settings stock Android doesn't: USB port restrictions, firewall rules, APN control, key remapping. Our Samsung Knox glossary entry covers the attestation side. The weakness is obvious: buy one batch of Zebra scanners and Knox tooling stops covering half your fleet. Mixed estates use a third-party MDM and reach Knox settings through the Knox Service Plugin.

Esper

Esper is the odd one out, deliberately. It treats devices like servers: declarative configuration, staged rollouts, pipelines, an agent that ships inside the device image so hardware self-configures at first boot. Genesis is $2 per device per month, Bridge $4, Architect $6, with a 25 device minimum and a 30-day trial. It also offers its own Android build, Esper Foundation, for companies needing OS-level control.

If you're a retailer who builds your own in-store app and has engineers, Esper is the best tool on this list. If you're an IT team configuring off-the-shelf Galaxy Tabs, it's more machinery than you need, and the security and compliance side is thinner than a traditional UEM. Know which of those you are.

ManageEngine Mobile Device Manager Plus

The argument for ManageEngine is rarely kiosk mode itself. It's that you already run ServiceDesk Plus or Endpoint Central, so this is one procurement conversation instead of three. Single-app and multi-app kiosk on Android are there and work. The published pricing is per tier, not per device: $1,195 a year for 100 devices on Standard cloud, $6,695 a year for 1,000 on-premise, and free on-premise up to 25, which is a useful way to pilot.

On-premise is the real differentiator, and almost nobody else here offers it. The trade-off is a console that feels like 2015 and rugged OEM depth below Scalefusion or Hexnode.

Fully Kiosk Browser

And then the cheap one that keeps beating expectations. An Android app: full-screen web view, URL allowlist, motion-detection screen wake, screensaver, auto reload and recovery, scheduled reboot, remote admin over HTTP. The Fully PLUS license is €8.90 one-time per device, with volume discounts from ten, and an optional cloud subscription at up to €1.18 per device per month.

For twelve signage screens running a web dashboard, nothing else here is a rational purchase. But understand what you're not getting: no Android Enterprise enrollment, no security policy, no app deployment, no inventory. Pair it with a real management layer the moment devices leave the building or touch payment data.

Which tool for which store fixture

Self-service terminals. Single app, all system UI off, FRP on, screensaver between customers. Scalefusion Essential or Appaloosa both do this cheaply. If it's a web app on bolted-down screens inside one site, Fully Kiosk plus a basic MDM is defensible.

Mobile checkout. Multi-app kiosk, because card readers need a companion utility. These devices rotate between employees across shifts, so check how the tool handles shared devices and session cleanup. Hexnode and Appaloosa cover the rotation case; Fully Kiosk doesn't apply.

Inventory scanners. OEMConfig decides this one. Zebra or Honeywell hardware, barcode parameters set centrally, rugged firmware channels. Appaloosa, Scalefusion and Hexnode render the schemas. ManageEngine is weaker, and Knox tooling won't see non-Samsung terminals.

Digital signage. Screen scheduling matters more than security: daily reboot, forced brightness, no sleep during opening hours. Knox Configure is strong on Galaxy Tab signage, Fully Kiosk is the budget answer, and any MDM works if you already pay for one.

FAQ

Can a customer break out of Android kiosk mode?

Not by swiping or rebooting. Lock task mode disables the home, back and recents behavior you tell it to, and the device returns to the pinned app after a restart. Exiting needs an admin PIN or a console command. The realistic attack is physical: a USB port you forgot to disable, or a recovery-mode reset on a device where FRP was never configured.

Do I need a dedicated kiosk product, or will my MDM do it?

If you already run an MDM supporting Android Enterprise dedicated device mode, it almost certainly does kiosk mode, and a second product is cost with no benefit. Dedicated kiosk apps earn their place in two cases: legacy hardware your MDM can't enroll, and deployments too small to justify per-device subscriptions.

What's the difference between single app mode and a kiosk browser?

Single app mode pins a native Android app. A kiosk browser pins a hardened browser that then loads a web app, so you get URL allowlisting, cache control and navigation restrictions on top. If your store application is a website, the browser route saves you from building an app. If it's native, single app mode is simpler and one less moving part.

Pick the tool that matches your hardware and your team, not the longest feature list. One honest test before you sign: configure a kiosk on your actual terminal, pull the battery, and watch what comes back on screen.