Cross-platform Kiosk: challenges of development and delivery.
summary
Kiosk setup focuses on how devices are provisioned not just which UI framework is used: the team builds a custom DPC (standalone device policy controller) plus the kiosk app, serves APKs from their server, and uses QR code provisioning to auto-whitelist and enable auto‑updates; this works for the majority of devices and scales. Problems arise when vendors (Samsung Knox) hijack provisioning, forcing distribution via Play Store, paid Hexnode MDM or hardware/ROM workarounds; iOS requires Apple Business Manager.
AI-written summary · about
chapters (11)
- 0:00Introduction to kiosk challenges
- 1:30Device provisioning methods
- 3:17QR code provisioning process
- 5:48Cross-platform development journey
- 7:53Hardware limitations and vendor issues
- 9:01Samsung Knox and MDM conflicts
- 10:50App distribution strategies
- 11:53Industry trends and scaling kiosks
- 12:56Third-party MDM solutions
- 13:36Alternative hardware approaches
- 14:10Conclusion and resources
related talks
23mInternal Developer Platform and Kusion
53mWhat I Talk About When I Talk About Cross Platform Development
30mBreaking Barriers: Bringing Application Developers Closer To the CNCF
27mSet Yourself up for Success — Lessons Learned from Building 100+ Devices with C++/Qt/QML
01h 00mThe Salami Method for Cross Platform Development
27mCoding Qt for greater interoperability and portability ...
27mWhy Developer Platforms and a curated Dev Experience are a must have when scaling
21mSuper-Powered, Server-Rendered Progressive Native Apps