Subscribe to Hexnode Blog
Get fresh insights, pro tips, and thought starters–only the best of posts for you.
BackWho Owns an Autonomous Single App Mode Session: IT or the App Developer?
Autonomous Single App Mode (ASAM) is an Apple device-management capability that allows an authorized application to enter and exit a locked single-app session on supervised iOS and iPadOS devices.
Understanding autonomous single app mode developer responsibilities requires separating administrative authorization from application control. IT determines which apps can use the feature, while the app developer controls when an authorized session starts and ends.
How does it work?
IT first enrolls supervised devices in a Mobile Device Management (MDM) solution and authorizes an ASAM-compatible application through a kiosk policy.
The developer implements Apple’s UIAccessibility.requestGuidedAccessSession API to request session activation and termination. These requests are asynchronous, so the application must check whether each transition succeeds and handle failures appropriately.
| Responsibility | Accountable party |
| Device authorization | IT manages device supervision, app authorization, policy deployment, and administrative access. |
| Session lifecycle | The app developer implements entry and exit triggers, handles API results, and maintains reliable application workflows. |
| Operational recovery | IT and developers coordinate troubleshooting, application recovery, and incident escalation. |
Autonomous Single App Mode vs standard Single App Mode
Standard Single App Mode is administrator-controlled and keeps a supervised device restricted to its designated application until the restriction is removed.
ASAM delegates session timing to an MDM-authorized application. For example, an examination app can activate lockdown when an assessment begins and release it after submission. IT retains authority over which applications receive this capability.
How Hexnode supports Autonomous Single App Mode
Hexnode UEM helps IT authorize applications through iOS Kiosk Lockdown policies, assign them to supervised devices, and centrally manage deployment.
Its device visibility and policy management capabilities support operational oversight, while developers remain responsible for application-level session transitions. Hexnode does not replace the required application logic.
When should organizations use it?
Organizations should choose ASAM when temporary application restrictions must follow a defined workflow, such as classroom assessments, controlled employee training, or supervised testing.
Before deployment, IT and development teams should document autonomous single app mode developer responsibilities, including activation conditions, exit behavior, failed API requests, and recovery procedures. Persistent unattended kiosks generally require standard Single App Mode instead.
FAQs
No. Apple requires supervised devices and MDM authorization before an application can successfully request an ASAM session.
Developers should handle failed exit requests and provide appropriate error handling. IT should maintain an administrative recovery procedure for affected devices.
Organizations should not assume automatic session restoration. Developers must validate restart behavior and ensure the application requests lockdown again when required.
