MDM and device management
Laurel can fit existing MDM and device-management workflows for managed application distribution, policy, and updates. Exact platform compatibility is confirmed during consultation.
Hardware
Built for enterprise Android hardware.
LaurelID is designed for leading enterprise Android hardware ecosystems. Hardware selection, operating-system compatibility, device management, kiosk configuration, and rollout are qualified during solution design.
01 · Enterprise fit
Flexible form factors. Controlled qualification.
LaurelID can be evaluated for handheld, tablet, fixed-terminal, and kiosk deployments. The software is hardware-neutral by design; support is confirmed for the device, operating-system build, NFC implementation, firmware, and management environment in the proposed solution.
02 · Ecosystems
Designed for established enterprise hardware ecosystems.
LaurelID is designed for industry-leading enterprise Android hardware ecosystems, including Elo and Zebra. These names are examples of established ecosystems, not a claim that every device or configuration is supported.
Hardware recommendations are part of consultation and pilot planning. We qualify the proposed profile before rollout rather than publishing fixed device or deployment instructions.
The approved LaurelID application mark, shown unmodified. This is the icon staff look for on a qualified device.
03 · Requirements
What a candidate device has to provide.
These are necessary conditions, not sufficient ones. NFC reader-mode and BLE peripheral behavior differ enough between chipsets and OEM builds that a matching spec sheet is not a substitute for a physical run.
Requirement Detail
Platform Android, enterprise-managed
NFC Reader mode with ISO-DEP; used for the initial tap engagement
Bluetooth BLE, including the peripheral/advertising role the reader side of ISO/IEC 18013-5 requires
Hardware keystore Android Keystore, with StrongBox used when the device provides it and a guarded fallback when it does not
Network Outbound HTTPS. Checks continue during an outage; only reporting waits
Deployment Managed application distribution through qualified MDM, device-management, kiosk-management, or content-management workflows
04 · Deployment posture
Fits established managed-device workflows.
Kiosk and content management
Kiosk-management and CMS/content-management workflows can be evaluated for controlled verifier deployments, including single-purpose device profiles.
Keystore
The device credential is protected by the Android Keystore. StrongBox is used where the hardware provides it, with a guarded fallback where it does not — the fallback is handled explicitly rather than by letting a provider exception escape.
Qualification is part of solution design
Compatibility varies by device model, operating-system build, NFC implementation, firmware, and management platform. Laurel does not claim universal support across every device or deployment system.
Qualify your hardware as part of a pilot.
Hardware and deployment recommendations are qualified with your team during solution design and pilot planning.