Android’s flexibility helps device manufacturers build diverse form factors with useful features to address a variety of business needs. But consistently delivering hardware options to organizations can be difficult because enterprise mobility management (EMM) providers often struggle to quickly support management for all these capabilities.
To solve this problem, we’re launching OEMConfig, a new Android standard that enables device makers to create custom device features that can be immediately and universally supported by EMMs. Instead of integrating enterprise APIs from each OEM to support their custom features such as control of barcode scanners or enabling extra security features, EMMs can easily use an OEM-built application that configures all of the unique capabilities of a device.
OEMConfig utilizes a feature in Android Enterprise called managed configurations, which allows developers to provide built-in support for the configuration of apps. With OEMConfig, EMMs can support all of a device manufacturer’s diverse set of controls without any incremental development work on their end.
Earlier this year, Samsung declared early support for a preview version of OEMConfig, publishing a Knox Service Plugin (KSP) app that enabled EMMs to support Knox Platform for Enterprise features. Since then, we’ve built out the final pieces of architecture to make it even more useful for customers and EMM partners. These include:
An enhanced schema with four-level nesting, to present complex policies to IT admins in a structured format
An update broadcast to instantly inform OEMs when policies have changed
A feedback channel to confirm the result of policies applied on the device
More information for OEMConfig can be found here.