Break out screenshots from cast/screen sharing to allow management individually (use case of remote support blacking out the screen when screenshots are disabled)
Data management
Data caps
App-type allow/blocklists
Terminology updates – allowlist for whitelist, blocklist for blacklist (but in a way that doesn't break APIs, we don't need more of those)
More dedicated default APIs (like SMS recently – launcher, phone, browser, etc, etc). Preferred intent works for tested use cases but it could be improved.
Provisioning app caching for enrolment (DPC extras)
Allow extras to list apps to pull at time of provisioning, rather than waiting for enrolment; particularly for required_for_setup this can speed things up a fair bit. Allow DPC to "take over" if provisioning is quick and/or apps are slow to DL.
Admin acceptances of T&C's & SUW prompts (GMS core). I know this has been a point of contention for years, but ultimately whether Google wants end users to accept them or not, the reality is the hundreds of thousands staged and/or set up remotely from end users means they never check the boxes anyway.
For dedicated, multi-person devices, allow a config to accept SUW prompts for management and T&Cs on behalf of the company/admin, not the user. This is a massive time-suck for us today and doesn't suit the EDLA style deployment environments we work in. Allow ZT to be closer to actually ZT for stagers and provisioners
Allow force-skip OEM SUW panels. Often these block enrolment until something is done on the device.
Admin-configured SUW panel for support and/or enterprise information
Config of display density
Config of time zone after provisioning
Config of locale after provisioning
A universal Android "offline solution" akin to what Apple offers for backup/restore. Swapping devices is still such a pain even on 13; cloud services are OK in what they restore, and the OEM solutions (Pixel, Samsung, etc) are a little better, but it's almost never guaranteed to be a carbon copy from one device to another, or even restoring the same device. I used to leverage TWRP, then later Helium, occasionally ADB backups, to do backup & restore as needed, but it's all too much effort or too technical for the wider market – it's such a low-hanging fruit
Passwordless Factory Reset Protection (FRP), allowing organisations to restrict setup of a device without the need to provide authentication for it (that often needs changing). Instead, set the device in a state that requires and auth/unlock code generated from an account, or lean on passkey/other auth methods instead.
EMM persistence after a factory reset, similar to FRP but allowing the DPC to write a persistence bit to disk, allowing a device to be reset in an unauthorised manner while still requiring a device goes back into management rather than permitting unmanaged setup.
Enforce support for DPC migration, and improve UX for customers. See what apple are doing for comparison.
Logging/debugging capability during setup/enrolment
Assignment of a SIM to the WP phone, contacts, etc ⚠️ Partially added in 14 for COPE (Corp owned work profile)
Cross-profile management to improve Android Auto experience (caller ID!!)Added in Android 14
Split of work/personal SMSAdded in Android 14
Config of work SIM settings (Settings > N&I > SIM) in WP deployments
Native launcher (AOSP) features: (Microsoft's managed launcher is a big inspiration here)
Wallpaper management
Widget management
Access to the feed
Removal of Google account features (for admins)
Managed config of home settings
Layout/folder management
Config of app shortcuts (long-press menu)
Enhance roaming APIs to include forced on, rather than just blocked.
Add DO permission options for battery optimisation & accessibility APIs for EMM control (two frequent OEMconfig APIs!)
Block adding apps as device admins (WP/COPE/FM)
Configure emergency alerts. I've had my fair share of devices showing amber alerts and similar in deployed locations – not really the expectation of a managed device
Set up wizard (SUW) flow support for untethered provisioning
Hardware management (context of full-fat Android for the things we do with hardware already)
Buttons
Radio
Screen
Basic management action support (reboot, lock, passcode, all the native stuff that may not have been ported from full-fat Android)
Untethered use (remove the requirement for tether under circumstances of reliable connectivity)
Kiosk options (but not Android kiosk, more wear-launcher config)
App deployment support (tethered/not)
Tethered – what companion apps are permitted from the device, under what profile, support for dedicated wear managed config sent from handset apps
Standalone, pull down apps from play and allow managed config
Multiple user support
When tethered, work/personal profile app management
Disable WP from wearable
Cross device profile sync
Ephemeral/multi-user support as an extension of the handset config
Industrial use case support (wear for wearable barcode scanners, data input, etc) so we can justify building with wear rather than AOSP as is the case today for small-screen industrial devices.
Open up wear to more OEMs (this isn't a FR, so much as a biz decision to boost wear in the ecosystem)