A kiosk deployment is not a single purchase decision. It is a series of interconnected decisions about hardware, software, management infrastructure, and ongoing support, each of which affects the others and all of which together determine whether the deployment delivers the intended business value over its operational life.
Organizations that approach kiosk deployment as a series of isolated decisions, choosing the hardware separately from the software, the software separately from the management platform, and the management platform separately from the support model, consistently encounter integration problems, operational gaps, and unexpected costs after deployment begins.
Organizations that evaluate the full system before committing to any component make better decisions at every stage and deploy kiosk solutions that work reliably without the remediation projects that plague poorly planned deployments.
This guide covers the evaluation criteria that matter across every component of a kiosk deployment.
Evaluate Hardware for Its Management Compatibility, Not Just Its Specifications
Hardware selection is where most kiosk procurement conversations start, and where one of the most consequential and most commonly overlooked evaluation criteria is missed: management compatibility.
A kiosk display with excellent specifications, competitive pricing, and a well-designed form factor that does not support the management platform’s lockdown capabilities, or that requires manual enrollment because it is not eligible for zero-touch provisioning, creates operational problems from day one. The hardware looks right on the spec sheet and causes problems in production.
Before selecting hardware, confirm:
- Is the device eligible for Android zero-touch enrollment through a certified reseller, or for Apple Business Manager enrollment through Apple’s channel? For any deployment beyond a handful of devices, automated enrollment is not a nice-to-have. It is an operational requirement.
- Does the device support the depth of kiosk lockdown that the use case requires? For Android devices, does the manufacturer’s build support Android Enterprise Device Owner mode without modifications that break standard management APIs?
- Is the device on the Moki certified hardware partner list? Certified hardware has been tested against Moki’s management capabilities and is supported through a coordinated hardware-software support relationship.
- What is the manufacturer’s OS update cadence and end-of-life schedule? A device that stops receiving security updates two years into a five-year deployment creates a security and management compatibility problem.
- Is the hardware designed for the operational environment? Consumer tablets in always-on kiosk deployments have higher failure rates than hardware designed for continuous operation. Consider thermal management, display brightness for the ambient light conditions, and durability for the traffic level expected.
Evaluate the Kiosk Application for Its MDM Compatibility
The application running on the kiosk determines what customers or users see and do. How that application integrates with the device management layer determines how reliably it runs and how visible its performance is to the operations team.
Key application evaluation criteria:
Does the application support the Moki SDK? Applications that integrate the Moki SDK can surface custom events and performance data in the Moki dashboard, giving the operations team visibility into application-level behavior beyond device-level health. An application that only reports at the device level is less transparent about what is actually happening in the user experience.
Is the application compatible with the kiosk lockdown configuration that will be applied? Some applications have behaviors that conflict with strict kiosk mode restrictions, such as requiring access to system notifications, launching external browsers, or attempting to access device features that will be restricted. Testing the application in the actual lockdown configuration before deployment is not optional.
Does the application have a defined update and release process? An application that updates unpredictably or that pushes updates without MDM-controlled timing can disrupt the kiosk experience at inopportune moments. Confirm how application updates are delivered and whether they can be managed through the MDM platform’s update scheduling capabilities.
Evaluate the MDM Platform for Dedicated Device Fit
The MDM platform is the operational layer that keeps everything else running reliably. Evaluating MDM platforms on the basis of feature lists alone misses the most important question: was this platform built for dedicated customer-facing device deployments, or was it adapted from an enterprise employee device management product?
Criteria that distinguish purpose-built from adapted platforms:
Kiosk lockdown reliability. Test the lockdown configuration on your specific hardware and attempt to exit the locked app through every available path. Home button, back button, notification shade, hardware buttons, and any other potential exit route should all be blocked. If any path succeeds, the lockdown is not complete.
Remote management depth. For Android and BrightSign deployments, verify that full remote screen view and interactive control are available, not just remote configuration push. The ability to see and interact with a device’s live screen is the capability that makes remote troubleshooting genuinely effective.
Content delivery monitoring. Confirm that the platform verifies content delivery to individual devices and surfaces delivery failures. A platform that pushes content without confirming receipt leaves operators without evidence that the deployment succeeded.
Support model. Ask specifically about the support team’s experience with dedicated device and kiosk deployments. General enterprise IT support and kiosk-specific support are different in meaningful ways that become apparent the first time a complex device issue needs resolution.
Moki’s platform is purpose-built for dedicated device deployments and supports iOS, Android, and BrightSign from a single dashboard with kiosk lockdown, remote management, content delivery monitoring, and the support model that dedicated device deployments require.
Evaluate the Ongoing Management Model
A kiosk fleet requires ongoing management after deployment. The evaluation question is who does that management and with what tooling.
Three options exist for ongoing management, and each is appropriate for different organizational situations.
Self-managed with internal IT capacity is appropriate when the organization has dedicated IT staff with time and expertise to monitor the fleet, manage updates, and respond to alerts. This requires the MDM platform to be properly configured with alerts, the internal team to be trained, and the organizational commitment to actually dedicate the necessary time to ongoing management.
Managed by the integration or implementation partner is appropriate when the organization wants to outsource operational management to the team that installed the system. This requires the integration partner to have a mature managed services practice backed by appropriate tooling, specifically including the MDM platform capabilities described above.
Managed by the MDM vendor’s managed services team is available through Moki’s managed services offering and is appropriate when the organization wants the operational work handled by the team with deepest platform expertise.
Evaluate the ongoing management model with the same rigor as the hardware and software components. A deployment with excellent hardware and software that is not actively managed will degrade over time as firmware falls behind, configurations drift, and downtime events go undetected.
The Questions to Ask Before Committing
Regardless of which specific hardware, software, and management options are being evaluated, the questions that should be answered before any purchase commitment is made are:
- Has the proposed configuration been tested end-to-end on a physical device, from factory-fresh state through live customer-facing operation?
- Is every component of the solution compatible with every other component, and has that compatibility been verified rather than assumed?
- Is there a documented enrollment process that can be followed by the person who will actually receive and install hardware at each location?
- Is monitoring and alerting configured and tested before any device goes live?
- Is there a clear escalation path for device issues that cannot be resolved remotely?
A deployment that can answer yes to all five of these questions before the first device ships is a deployment that will go smoothly. A deployment that defers any of them to after the hardware is in the field will encounter preventable problems.
Schedule a Moki demo to evaluate the platform against your specific hardware and use case before committing to a deployment, or start a free trial to test the enrollment, lockdown, and remote management capabilities with your actual devices. Moki’s support team can advise on hardware compatibility and configuration requirements during the evaluation process.