android-device-owner
Android Device Owner Mode
You are an expert at building Android Device Policy Controller (DPC) apps that use Device Owner Mode for full device management. This skill references the official Android Enterprise documentation and DevicePolicyManager APIs.
Important: DPC Allowlist (2025)
Google Play Protect now enforces an allowlist of approved DPCs during provisioning. Unapproved custom DPCs are blocked with a "harmful app" warning. The Play EMM API is closed to new registrations. For new enterprise management projects, Google recommends the Android Management API. Custom DPCs provisioned via ADB (dpm set-device-owner) still work for development and sideloaded deployments.
Core Concepts
Device Owner vs Profile Owner vs Device Admin
| Mode | Scope | Provisioning | Use Case |
|---|---|---|---|
| Device Owner | Full device control | Factory reset required, set during initial setup | Company-owned, fully managed devices |
| Profile Owner | Work profile only | Can be added to already-provisioned device | BYOD with work/personal separation |
| Device Admin | Deprecated (removed API 29) | Runtime activation | Legacy -- do not use for new projects |
Device Owner is the most powerful mode. It can hide/show apps, filter web content, enforce VPN, set user restrictions, silently install apps, control system updates, and perform factory reset -- all without user consent.
More from zackbart/skills
optimize-prompt
>
9kysely
>
7second-opinion
>
5update-docs
>
5design-system-patterns
>
5ethos
Conduct a structured interview and write a project's ethos.md — the doc that captures vision, principles, personas, non-goals, scope, and constraints. Use this skill whenever the user mentions ethos, vision doc, project principles, project philosophy, guiding principles, non-goals, scope boundaries, target user persona, anti-personas, project charter, "the why behind the project," or wants to prevent feature creep / drift / contributors making wrong assumptions. Also use when the user wants to define what a product is NOT, document who it's for, lock in what makes it special, or onboard contributors with strategic context — even without the word "ethos." Do not write a vision/principles/non-goals doc directly with Write; invoke this skill so the interview runs first.
4