Every device deployed in a public-facing environment is exposed to a category of risk that does not exist for devices kept behind a counter or inside a locked office. Customers can touch them. Passersby can interact with them. In some deployments, the device is entirely unattended for extended periods. Without the right configuration in place, any of these interactions can result in unauthorized app access, data exposure, configuration tampering, or a device that has simply walked off.
App lock is the foundational configuration control that addresses all of these risks. When properly implemented through Moki’s kiosk and lockdown capabilities, app lock restricts a device to a single designated application and makes everything outside that application inaccessible, regardless of what the user attempts. The device cannot be navigated away from its intended purpose. It cannot be redirected to another app. It cannot be used to access settings, a browser, or any other system function that was not part of the intended deployment.
Understanding how app lock works in practice, why it is necessary in public environments, and what it prevents is the starting point for any organization deploying customer-facing hardware.
What App Lock Is and What It Is Not
App lock, also referred to as single-app mode or device lockdown depending on the platform, restricts the device operating environment to a single designated application. When app lock is active through Moki, the following are true about the device:
- The home screen is not accessible from the locked application
- The device’s notification shade cannot be pulled down to reveal system alerts or shortcuts
- Hardware buttons including the home button, back button, and volume controls behave in ways defined by the MDM configuration rather than their default OS behavior
- The app store, settings, camera, browser, and all other system applications are inaccessible
- If the locked application closes unexpectedly, the device returns to the app launch state rather than dropping to the home screen
What app lock is not is an impenetrable physical security device. A device with app lock enabled can still be physically removed from its mount if it is not also physically secured. App lock addresses software and interface security. Physical security measures including mounts, enclosures, and cable anchors address physical security. Both layers are needed for a complete public-facing deployment security posture.
How App Lock Prevents Misuse
Misuse in public-facing device deployments takes several forms, and app lock addresses each of them directly.
Unauthorized browsing is the most common form of misuse in customer-facing kiosk environments. Without app lock, a customer who taps the home button or finds a back-door navigation path can reach the device’s web browser and use it for personal browsing, expose the device’s browsing history to subsequent users, or access content that is inappropriate for the deployment environment. With app lock active through Moki’s kiosk mode, there is no browser to reach and no navigation path that leads outside the designated application.
Settings tampering occurs when a user with enough curiosity or intent reaches the device’s operating system settings and makes changes that affect the device’s behavior. Changed Wi-Fi networks, modified display settings, disabled accessibility features that were required for the application, or enabled developer options all create operational problems that require IT intervention to reverse. App lock makes the settings menu completely inaccessible from the device’s interface.
Personal use of business hardware is common in employee-shared device environments where app lock is not enforced. Employees who discover they can access personal email, social media, or entertainment apps on a business device create productivity problems, network security risks, and liability exposure. App lock restricts the device to the approved application set, eliminating this category of misuse entirely.
Data exposure through app navigation occurs when a user navigates away from a transaction or service application into areas of the device that contain cached data, configuration information, or credentials. In payment environments, this type of access can expose data with direct compliance and liability consequences. App lock prevents any navigation that could lead to this exposure.
How App Lock Deters Physical Theft
The relationship between app lock and device theft deterrence is less intuitive than the misuse prevention case but equally important for organizations deploying hardware in publicly accessible spaces.
A device locked to a single application through Moki’s MDM platform has dramatically reduced value on the secondary market compared to a general-purpose device. A stolen iPad that can only run a self-ordering kiosk application and cannot be unlocked to function as a personal device is nearly worthless to a thief. A stolen iPad with no MDM enrollment and full OS access is worth its full retail value.
This deterrence effect is not hypothetical. Organizations that deploy locked-down devices in high-theft-risk environments, including retail stores, transit stations, and public service locations, consistently report lower theft rates than those deploying unlocked devices. The economics of theft are affected by the resale value of the target, and app lock reduces that value to near zero.
Moki’s remote wipe capability provides the backstop if a device is physically removed despite lockdown. When a device is confirmed stolen, it can be wiped remotely from the Moki dashboard before any data on it can be accessed, and the device’s MDM enrollment is revoked so it cannot be re-enrolled in another management environment.
App Lock Across iOS and Android
The implementation of app lock differs between platforms, and understanding the platform-specific approach helps in choosing the right configuration for each device type in the fleet.
On iOS devices managed through Moki with Apple’s supervised mode, Single App Mode is the mechanism for full app lock. When Single App Mode is configured for a specific application through Moki, the device is locked to that application at the OS level. The Home button behavior is controlled by the MDM configuration, notifications are suppressed, and the device interface is limited entirely to the designated application. This is enforced at the iOS system level, not by an overlay application, which makes it extremely difficult to bypass.
On Android devices enrolled through Android Enterprise, Device Owner mode provides OS-level kiosk lockdown that restricts the device to a designated app or set of apps. The lockdown is enforced through Android’s system-level kiosk APIs, which prevent navigation to the home screen, app drawer, or system settings. For Android devices using Moki’s Android Agent, app lock is enforced through the Agent’s device administrator capabilities, which provide strong lockdown across a wider range of hardware including devices that do not support the full Android Enterprise framework.
Configuring App Lock in Moki
App lock configuration in Moki’s platform is part of the device configuration profile and applies to all devices in the assigned group. The configuration specifies which application the device is locked to, how the device behaves when the app is closed or crashes, whether any hardware buttons are accessible during the locked state, and what idle behavior is configured for sessions that end without user action.
Once the profile is applied, app lock is active on every device in the group and cannot be disabled by anyone interacting with the device directly. Changes to the app lock configuration are made through the Moki dashboard and pushed remotely to the fleet without requiring physical access to any device.
For organizations deploying across multiple location types where different applications are locked on different device groups, each group maintains its own app lock configuration independently. A retail location running a product discovery kiosk and a payment terminal can have both device types enrolled in Moki with separate app lock configurations applied to each group.
Schedule a Moki demo to see app lock and device lockdown configured and demonstrated on your specific hardware, or start a free trial to begin building your app lock configuration today. Moki’s support team can advise on the right lockdown configuration for each device type and platform in your deployment.