Glossary
Google Play Protect
Google Play Protect is the malware defense built into Google Play services: it scans apps before and after install, on the device and in Google's cloud, and warns or blocks when something looks harmful. For a fleet it also decides something more basic, because a device that is not Play Protect certified cannot use Managed Google Play, which means it cannot be enrolled in Android Enterprise at all.
How it works
Two layers. Apps submitted to Google Play go through automated and manual review before publication. Then Play Protect runs on the handset, checking installed apps and anything arriving from outside the store, with suspicious binaries sent to Google for analysis. Google says it screens on the order of 200 billion apps a day across the install base. Since 2023 it also performs real-time code-level analysis of apps it has never seen before, at install time, rather than relying purely on known signatures.
Separate from scanning is Play Protect certification. A device model passes Google's compatibility test suite and is licensed to ship Google Mobile Services. You can check it on any handset under Play Store, Settings, About, Play Protect certification. Uncertified devices exist in large numbers: grey-market tablets, cheap rugged terminals bought from a marketplace, devices with a reflashed ROM. They look like Android, they run apps, and they will fail the moment you try to enroll them, because there is no Managed Google Play and often no working Play services.
On the sideloading side, the direction since 2025 is clear. Android 16's Advanced Protection hardens installs from unknown sources, and Google announced in August 2025 that apps installed outside Play on certified devices will have to come from a verified developer, with the first countries in 2026 and a wider rollout after. Manual APK installs by end users are being squeezed out.
Why it matters for a fleet
Buy 200 tablets on price alone and you can discover on delivery day that none of them can join your MDM. Ask the reseller for the exact model's certification status before the purchase order, not after. This is the single most common Android procurement mistake we see.
Play Protect can also generate noise. An internal app signed with a key Google has never seen, installed outside the store, may trigger a warning that alarms users and produces tickets.
How Appaloosa handles it
That last problem has a clean answer: distribute your internal builds as private apps rather than as loose APKs. Appaloosa publishes your own APKs and IPAs in an enterprise app store, with versioning and per-group assignment, and installs them on enrolled Android devices through Android Enterprise and Managed Google Play, so the install is a managed operation and not an unknown-source prompt. Public apps come through the same console. The scope is on the Android MDM page.
Explore
See the full platform
Enrollment, apps, security, remote support: all in one place.
Explore Appaloosa →Ready to try Appaloosa? Start free