Otukan keeps dedicated Android devices on their approved tasks. It provisions them as Android Enterprise dedicated devices and pins them to one app or a short allowlist with Android’s lock task mode, hiding the system controls the task does not need. Maintenance staff get a controlled, logged way out, and devices return to the approved app on their own after a restart, a crash or a lost connection. It is built for point-of-sale terminals, handheld scanners, check-in tablets and field devices. This page covers Android; single-purpose iPads are configured with Apple’s own options.
Kiosk modes
Android Enterprise provides a dedicated-device mode for hardware that serves a task rather than a person. Otukan builds its kiosk management on it, with lock task mode keeping the screen on approved apps.
Single-app operation
The device runs one app. Users cannot open other apps, reach the home screen or change settings. Otukan uses this for devices with one job, such as a self-service terminal or a signage screen.
Multi-app operation
The device runs a short allowlist of apps through Otukan’s restricted launcher: for example a line-of-business app, a scanner utility and a browser limited to one site. Otukan reviews the routes out of each app on the list, such as links, share menus and in-app settings screens, so the allowlist stays tight.
| Single-app | Multi-app | |
|---|---|---|
| Apps allowed | One | A defined allowlist |
| Launcher | The app itself | Otukan’s restricted launcher |
| System interface | Usually hidden | Selected elements, such as notifications |
| What Otukan reviews | That the app has no route to settings or other apps | Every route out of each listed app |
Administrators choose which system features remain available in lock task mode, such as the status bar, notifications or the power menu. Which features can be controlled depends on the Android version, so Otukan checks each choice against the oldest version in your fleet.
Operational access
Someone will need to leave kiosk mode to change a setting, replace an app or diagnose a fault. Otukan designs that access in before rollout.
- Exit mechanism. A remote command from the console, a protected local administrator PIN in the kiosk launcher, or both, depending on how your sites work.
- Who may use it. Named roles, never a shared code written on the device.
- Automatic return. The device goes back into kiosk mode after a set time or at the next restart.
- Logging. Each exit and return is recorded with time, device and person.
- Physical access. Buttons, USB ports and recovery modes sit outside lock task mode. Otukan restricts debugging features and safe boot by policy, and you choose how devices are mounted.
App updates reach kiosk devices through managed distribution in a maintenance window, so an app does not restart in the middle of a customer’s transaction. App delivery is covered on MDM app management.
Reliability
A kiosk device earns its place by returning to work without help. Otukan confirms each case below on every model and Android version in your fleet.
| Event | What Otukan does | What is confirmed |
|---|---|---|
| Restart or power loss | Boots back into the approved app or kiosk launcher | No setup or home screen shown on the way |
| App crash | Restarts the app and keeps the device locked | A crash during a transaction; repeated crashes |
| Connectivity loss | Keeps policy enforced on the device | Hours offline; behaviour on reconnection |
| Missed commands | Applies queued commands on reconnection | Order of queued changes |
| Device fault | Resets and re-provisions the device into the same group | Whether anyone on site is needed |
Power management, boot behaviour and vendor launchers vary between manufacturers, so Otukan confirms each model you run rather than assuming one stands for another.
Operating at scale
Kiosk fleets are often spread across many sites with no IT staff on hand. Otukan shows each device’s kiosk state, policy status and last check-in time in one inventory, so a device that has dropped offline or left kiosk mode stands out. Restarts, app replacements and re-provisioning run from the console, which keeps site visits for hardware faults rather than configuration.
Remote lock, restart and wipe are covered on MDM remote device management. The parent overview is mobile device management.