If you've ever walked up to an iPad at a hotel check-in desk or a retail kiosk — and noticed it only runs one app — you've already seen Apple's Single App Mode (SAM) in action. It's one of the most practical features Apple offers for businesses, yet most people don't know how it works or which apps it supports. Here's the short answer: almost any App Store app can work with SAM. But "almost" is doing a lot of heavy lifting in that sentence. There are nuances — around supervision requirements, MDM enrollment, and how certain app types behave in a locked environment — worth knowing before you deploy. Let's break it all down.
Native iOS/iPadOS Applications
Apple's own built-in apps are the most reliable candidates for Single App Mode. Safari is a fan favorite for kiosk deployments — lock an iPad to a branded web experience, and you've got a clean, zero-distraction interface for customers. Apple Maps works well for navigation-focused deployments. Numbers and clocks have been used in everything from time-tracking stations to display boards. The reason native apps shine here is simple: they're built to Apple's own standards, don't require third-party licensing, and restart automatically after a device reboot — a non-negotiable for unattended kiosk setups. If you're just getting started with SAM, native apps are the safest place to begin.
Purpose-Built Kiosk and Business Applications
This is where SAM really earns its reputation. A wide range of purpose-built business apps is designed for kiosk deployment and works seamlessly in Single App Mode. Point-of-sale apps like Square and Toast are widely used on locked iPads at retail counters and food trucks. Restaurant management platforms like TouchBistro handle bookings and orders on devices that never leave the host stand. Digital signage apps — think Yodeck or ScreenCloud — run content loops on lobby displays without any risk of an employee accidentally swiping away mid-presentation. These apps are built with enterprise environments in mind. Developers often design them knowing their customers will deploy via MDM, which means they're tested in supervised, locked-down conditions. If a business app has a serious enterprise customer base, it's likely to work in SAM.
Web-Based Applications (Web Apps) for Single App Mode
Web apps are an underrated option for SAM deployments. Lock Safari — or a managed browser like Google Chrome or Microsoft Edge — to a specific URL, and you've effectively created a web-based kiosk without building a native app at all.
Why Web Apps Work So Well Here
A hospital, for example, might lock iPads at check-in stations to their patient portal's web address. A museum can display an interactive exhibit guide hosted on a web server. Updates happen server-side, so the device never needs to be touched. Google Chrome and Microsoft Edge both support SAM and offer additional controls, such as restricted browsing modes, making them solid choices over Safari when you need tighter URL filtering. The trade-off? Web apps depend on a stable internet connection. If your deployment environment has unreliable Wi-Fi, a native app with offline capabilities is the smarter call.
Third-Party Applications with Minimal External Dependencies
Third-party apps broadly compatible with SAM include a long list of familiar names. On the productivity side, Adobe Acrobat Reader, DocuSign, Dropbox, Asana, and even ChatGPT are all confirmed to work. Communication apps like Microsoft Teams and Zoom function in SAM, making them popular choices for dedicated conference room devices — lock an iPad to Zoom, mount it outside a meeting room, and you've got a permanent room booking display. Streaming and entertainment apps — Netflix, Hulu, Spotify, Disney+ — also run in SAM. Hotels use this to put entertainment-only iPads in guest rooms. Medical waiting rooms use it to run calming content on wall-mounted displays. The real-world use cases keep stacking up. One thing to watch: apps with heavy external dependencies or those requiring frequent background syncs can behave unpredictably in SAM. Always test before a large-scale rollout.
Implementation Methods Influence App Compatibility and Control
Not all SAM setups are equal. How you implement Single App Mode directly affects which apps you can lock to, and how much control you retain.
MDM vs. Apple Configurator
MDM solutions — like Jamf, SimpleMDM, Addigy, or JumpCloud — give you remote, scalable control. You push a configuration profile specifying the app's Bundle ID, and the device locks itself to it. MDM is the right move for any deployment involving more than a handful of devices. Apple Configurator, on the other hand, works through a physical USB connection. It's a reasonable option for small batches, but it doesn't scale well. Either way, the device must be supervised — there's no way around this requirement. Supervised status is set during enrollment via Apple Business Manager or Apple Configurator, and without it, SAM won't engage. Autonomous Single App Mode (ASAM) is a third option worth mentioning. It allows an app to lock and unlock itself programmatically — think standardized testing apps or secure document signing workflows. However, ASAM requires developers to build that functionality into the app specifically. It won't work on a standard off-the-shelf download.
Strategies for Optimizing the App Experience
Locking a device to an app is step one. Making the experience actually good for end users takes a bit more thought. Disable features you don't need — turn off auto-lock if the device is a public-facing display, restrict hardware buttons if there's a risk of users accidentally sleeping the screen, and consider disabling device rotation if the app is designed for portrait or landscape only. MDM profiles give you granular control over all of these. Always configure a fallback plan. If the app crashes — and it will at some point — the device should auto-relaunch. Most MDM solutions handle this natively, but test it before deployment. Set up remote monitoring to detect when a device goes offline or exits its expected state. Running a fleet of 40 kiosks without monitoring is a support nightmare waiting to happen.
Troubleshooting and Best Practices for SAM Apps
Common issues come up in patterns. First: the app won't lock properly. Nine times out of ten, this is a supervision problem — the device wasn't properly enrolled before the SAM profile was pushed. Double-check the supervised status before troubleshooting anything else. Second: app updates can temporarily knock a device out of SAM. Some MDM platforms — like Silverback — automate this by pausing SAM, running the update, then re-enabling the lock. If yours doesn't, schedule updates during off-hours and have a technician standing by. Third: the Bundle ID is wrong. This sounds silly, but it happens all the time. Microsoft Teams, for example, has the Bundle ID com.microsoft.skype.teams — not what you'd intuitively guess. Always verify Bundle IDs directly from a source like Apple's official documentation or the MDM platform's app catalog before pushing a profile. Finally, always test on a spare device before deploying to your full fleet. What works on iOS 16 might behave differently on iOS 17. A quick sanity check saves a lot of headaches down the line.
Where SAM's Compatible Apps Shine
The real power of Single App Mode comes into play in specific scenarios. Retail POS systems keep cashiers on-task during peak hours without risking accidental app switching. Educational institutions lock exam iPads to testing apps, eliminating access to browsers and notes. Healthcare facilities use SAM to run patient intake forms on lobby tablets — HIPAA-compliant, focused, and easy to sanitize between uses. Event check-in apps, hotel concierge displays, and augmented reality tour guides in museums — all become more reliable and professional when the underlying devices are locked down. The app becomes the entire device, and that's exactly the point.
Conclusion
So, what apps are compatible with Apple's Single App Mode? The practical answer is: most of them. Native Apple apps, major third-party platforms, custom enterprise apps, and web apps delivered through a locked browser all work well. The limiting factors are usually related to supervision and enrollment, not to specific app restrictions. If you're planning a SAM deployment, start with a clear use case, pick an MDM solution, and test your target app on a supervised device before scaling up. Done right, Single App Mode turns a general-purpose iPad into a purpose-built tool — and the right app makes all the difference.
