Android MDM is software that monitors and manages groups of Android devices remotely (MDM stands for Mobile Device Management). If you use Android edge devices at your business, organization, or enterprise, you probably need an Android MDM solution to manage them.

MDM Solutions for Android

What is Android MDM?

Mobile Device Management (MDM) alone refers to management of any mobile device, while Android MDM refers to management of Android devices specifically (though an Android MDM may also allow you to manage iOS, Linux, or Windows devices).

An MDM (Android or otherwise) can be used to distribute enterprise apps, centrally manage device settings, and enforce security policies. (But not all Android MDMs offer the same features — if you need to lock down your Android devices to a single app, disable hardware buttons, or force the screen to stay on forever, you may need an advanced MDM solution.)

Note: When choosing your Android MDM, it's critical to know if the Android devices you want to manage are running Google Android (GMS Android) or AOSP (i.e., non-GMS). If these terms are new to you, check out our guide on GMS vs non-GMS Android.

What Are the Benefits of Android MDM?

Managing Android devices individually without an MDM solution is certainly possible, but it’s very likely insecure and certainly unscalable — there are many ways manual fleet management can go wrong. Here are the key benefits of Android MDM over manual device management.

‍

The above should give you a sense if your use case is BYOD / COPE or dedicated. In general, employee or student laptops, workstations, phones, and tablets are the most common BYOD / COPE use cases. If the device doesn’t fall into one of those groups, your use case is probably as a dedicated device.

BYOD / COPE use cases work well with traditional MDM solutions, where real-time monitoring, strict device settings configuration, and on-demand software deployment aren’t critical features. But dedicated devices need a dedicated, enterprise-scale MDM — here is how traditional and enterprise MDM break down by suitability to device type:

Good fit for traditional MDM

• Employee smartphones
• Employee laptops/workstations
• Employee tablets
• Student laptops/workstations
• Student tablets

‍Needs dedicated enterprise-scale device management)

• Point of Sale (POS) device, stationary or handheld
• Self-service restaurant kiosk
• Medical check-in kiosk
• Retail, hospitality, or informational kiosk (hotel check-in, mall directory, registration kiosk)
• Restaurant kitchen display
• Inventory or logistics handheld device
• Restaurant or retail digital signage
• In-vehicle tablet or handheld device
• Smart vending machine
• Smart vending machine
• Connected medical devices (health IoT)
• Smart exercise equipment
• Rugged field devices

How Much Does Android MDM Typically Cost?

According to research conducted by Oxford Economics and Samsung, Android MDM solutions cost between $3.25 and $9 per device, per month. That means managing a fleet of 100 devices could cost anywhere from $3900 to $10800 per year with Android MDM.

However, the cost of Android MDM is a complex topic, and we encourage you to read more in our guide about MDM cost.

Download our Free MDM RFP Template

We know that comparing device management solutions can be complex, so we put together an MDM RFP (Request for Proposal) template to help you quickly and easily compare potential MDM providers. In the template, we'll walk you through key considerations about technical requirements, budget, timeline, and more.

MDM RFP Template

What are Common Android MDM Features? 

Android device management platforms have advanced well beyond their original basic functionality of managing smartphones that employees would use for work. As the way businesses capitalize on the flexibility of the Android operating system has evolved, so too has the need for Android MDM features. If you're shopping for an Android MDM platform, features you'll want to look for include:

• Kiosk mode: With tens, hundreds, or thousands of devices out in the wild, you want to ensure that those devices are locked to only the app or apps you choose, and that users can't get around those apps and use your company devices for other things. Kiosk mode for Android enables this type of lockdown.
• Remote control: The ability to remote access Android devices means IT teams can troubleshoot or update devices in any location. Remote control in an Android MDM solution is like having a full remote desktop tool (such as TeamViewer) for your devices.
• Provisioning options: Configuring new devices can be one of the most time-consuming parts of device management. An Android MDM platform that offers multiple provisioning options allows you to select the one that's best — and fastest — for your business.
• Telemetry data & alerts: Knowing the status of all devices at all times means peace of mind that your devices are running smoothly for your business. Setting up alerts for when something changes enables proactive troubleshooting to fix any issues quickly.
• Device grouping & staged software rollouts: If you're managing a large fleet of devices, you likely have groups of devices that need different updates at different times. The ability to group and organize devices in the MDM console and then roll out updates in stages based on custom rules gives you the control you need.

Android MDM Limitations and Drawbacks

Android MDM solutions that were originally designed for the BYOD use case are very limited in several key respects. However, deploying new devices and updating apps or content on those devices is a key weakness of many Android MDM solutions.

If you need to update certain devices with specific software builds for particular tagged hardware targets or inside a specific timeframe (on a regular schedule), most Android MDM solutions will leave you wanting. Even the Google Play Store (for GMS devices) isn't a great fit if you need this level of precision and reliability when deploying software updates to devices. If updates (software, apps, or even content) are important to you, finding an Android MDM solution that offers granular control of software and content is important.

If you want to repeatably and reliably update the software on any Android device in your fleet, you’ll need a distribution platform and infrastructure to manage it (a cloud). Esper's full stack management tools and easy to use console can open brand new avenues for efficiency (OpEx reduction) and innovation.

Traditional MDM vs Enterprise MDM features for Android

As part of evaluating your Android MDM, you need to determine whether you’re looking at a legacy (traditional) MDM or an advanced MDM solution with modern features. While traditional MDMs may work well for BYOD / COPE use cases, make no mistake: There are very substantial differences in capabilities when compared to advanced MDM. Here are some features that distinguish the two.

Android MDM: GMS vs AOSP Explained

If you're shopping for an Android management solution, you've likely become familiar with the terms "GMS" and "AOSP." Here are some helpful ways to understand the differences between managing GMS and AOSP devices using a traditional Android MDM.

If you're building your own custom device, you've likely investigated how easy it would be to just become GMS certified and use Google’s Play ecosystem and tools. For some companies, this is the best solution — if you have the time and resources to get GMS certified. 

And with so few features, it may seem AOSP is a dead end.  But if your device is unusual in some way or otherwise not cut in the cloth of a typical Android smartphone, GMS certification may not be practical, or even possible under Google’s restrictions.

We have an in-depth primer on the key differences between GMS and non-GMS Android devices and what it takes to become GMS certified, which involves passing some extremely rigorous automated test suites. You can also check out Google’s CDD (Compatibility Definition Document). This defines what a “true” Android device is and will be, often forecasting changes years into the future.

If you want to understand GMS's drawbacks in a sentence? With GMS, you're on Google's timeline and must meet their definition of what "Android" really means, and that has material costs. With GMS, you're also building against a consumer-grade device experience that may be a poor fit for your use case. AOSP offers an alternative, but comes with its own considerations.

‍

Android Management Solutions for AOSP Devices

When you talk about "non-GMS" Android devices, you're talking about devices running "AOSP." The Android Open Source Project (AOSP) is the fully open source version of the Android OS, and it underpins more devices in more scenarios than it’s likely reasonable to list in a single place.

Manufacturers can utilize the open source code Google publishes as part of AOSP to assemble an OS, and Google has no control over these AOSP devices. The downside is that AOSP devices don't have Google’s mobile services and applications, so they don't have the cloud APIs and support infrastructure to enable OTA application updates and firmware over the air (FOTA) updates — and this is where major AOSP management challenges begin.

But AOSP can also enable huge opportunities, as the platform offers a huge library of APIs and supporting documentation, a ready-made UI, basic stock applications, and cross-platform development tools.

Designed to receive FOTA upgrades in place (with minimal disruption using features like A/B system partitioning), AOSP can let you build devices that can meaningfully improve your overall device experience. All with the option to iterate in the field with software and firmware innovations that are fully under your control.

Most Android MDM providers are designed for Android GMS devices. These solutions were never built to do the kinds of things Google does for consumer Android products (deliver app updates, new content, firmware updates) because Android with GMS already provides these functions. But if you're running AOSP Android, you're now missing tools that a full stack Android management partner like Esper can provide (for example, FOTA).

Key Considerations When Shopping for Android MDM

It may seem silly to say, but knowing what you’re going to use your devices for is the first step to getting the right Android MDM. If you have a straightforward BYOD scenario, it’s almost impossible to go wrong with most Android MDMs. If your use case is more specific — your devices are revenue-generating or business-critical, for example — that changes things. At that point, it’s much easier to go with the wrong Android MDM. 

The good news is that we have a resource to help. Basically, it’s a 10-question checklist to help you decide what kind of Android MDM is best for you. Each question is weighted toward a specific use-case, so it should help you determine exactly what your needs are and why. 

If you already have an Android MDM solution that sort-of works, you may have accepted its limitations by developing workarounds. In that case, it’s easy to brush off other solutions as unlikely to add significant value. But if you added up all the hours you and your developers spent troubleshooting and building those workarounds for your Android MDM instead of building great products, you'd see the math very differently.

Practicing proper edge fleet management would not only save your business money, it will help you create better products for your customers — and be able to do so faster and with far greater flexibility at scale.

If you're tired of dealing with a makeshift solution, you're ready to take the Esper Android MDM plunge. Come talk to us.

Learn More: Enterprise OS Agnostic & Android MDM Solutions