Forum Discussion
Private app package name already in use
I got an APK from our Digital Signage vendor Poppulo (formerly known as Four Winds Interactive) and tried to upload it as a private Google Play app through the iframe in Intune. Got this error: ...
Once AMAPI reaches parity with custom DPC Matt will undoubtedly be happier (as will many of us) given we've waited for it since 2019, and the custom DPC vendors holding out will migrate over finally too.
That said it's cake for developers to build a unique package, wholly automated, and if it's a stipulation of continued business as the only thing a dev has to do, it's totally with reason to do it.
I've been an Android user/fan for a long time but I'm a newbie when it comes to Android management so forgive me for asking: what is AMAPI lacking right now that everyone is waiting for? I've not had the pleasure of using a custom DPC (besides Company Portal on work profiles but that doesn't really count), I went full Android Enterprise from the get-go for my project so I guess I don't know what I'm missing.
Some examples top of mind are multi/ephemeral user support (9.0), offline OTA deployment (10), remote debugging/bug report collection, eSIM support (15). If I fetch my notes I can grab more.. but AMAPI gatekeeps native DPM/UM APIs present on devices and can be really frustrating to work with knowing the configurations I want to apply are right there on the device with no way of using them.
Items that matter to me that are offered by Custom DPC based EMMs.
- Direct APK installation (unless Google can build and offer better version control)
- Offline OEMConfig/Managed configuration (i.e. not through MGPA)
- File management including delivery / retrieval
- Advanced Scripting
- Real time actions
- Remote Control
Thanks for your thoughts mattdermody and jasonbayton. I hear you!
