CREATE YOUR OWN DEVICE OWNER: WHY? HOW? AND WHY NOT?
summary
Argues that some orgs build a custom Device Owner to avoid EMM limits and run offline, demonstrating tradeoffs: TestDPC is the reference implementation and source of working code; alternatives are Google’s Android Management API, joining the EMM program, or a fully on‑prem DPC using OEM tools like StageNow. Key specifics: device owner requires factory reset or AFW/QR/NFC enrollment, managed accounts enable Managed Play, common command is ADB dpm set-device-owner, and long‑term maintenance and scaling costs often outweigh benefits.
AI-written summary · about
chapters (7)
- 0:00Introduction and motivation
- 3:54Device owner vs profile owner
- 8:28EMM vs standalone device owner
- 14:06Reasons to create device owner
- 22:38Reasons not to create device owner
- 29:39How to create device owner
- 34:11Testing and resources
related talks
34mThe World of Device Management Enabled by Android Enterprise
23mDo Androids Dream of Electric Fences?
16mWriting Apps for the Work Profile
22mLocking, blocking and rocking Android for Self-service Kiosks
37mThe World of Android Enterprise Every Business App Developer Should Know
18mGet Your App to Work at Work
38mBring your own phones to Gradle Managed Devices
37mAndroid Enterprise: the developer's missing manual