Skip to main content
CFDP
New Member
Nov 20, 2026 3:25 AM UTC
Question

Clarification on Android Developer Verification Exemption for ADB-Provisioned Device Owner Devices and Self-Updates via PackageInstaller

  • 0 replies
  • 25 views
  • Translate All • Beta, powered by Gemini

Dear Google Android Developer Verification / Android Enterprise Team,

We would like to clarify whether the Android developer verification requirements expanding globally in 2027 will affect our privately distributed Android application, IC Navi, which is used on dedicated tablets in Japanese hospitals.

Current deployment

Our application is distributed privately as a signed APK, outside Google Play.

During initial device setup, we install the APK using ADB and configure our own application as Device Owner using adb shell dpm set-device-owner.

The devices operate in dedicated kiosk mode using Device Owner and LockTask.

We have not confirmed enrollment through an external EMM/MDM solution or formal Android Enterprise enterprise enrollment.

For application updates, our application downloads a newly signed APK from our own management server and uses the standard Android PackageInstaller API to update the existing application.

Google Play is not used for normal deployment or updates.

Questions

1. Device Owner exemption

Does a device configured as Device Owner through ADB with a custom in-house application qualify for the Android developer verification exemption for fully managed devices?

Or is formal Android Enterprise enrollment through an EMM/MDM provider required for this exemption?

2. Self-updates using PackageInstaller

Will Android developer verification be enforced when our existing Device Owner application downloads a signed APK from our private server and updates itself through PackageInstaller?

Does Device Owner status change how this requirement is enforced?

3. Minimum necessary compliance

If this deployment is not exempt, would verifying our developer identity and registering the existing package name and production signing certificate be sufficient to continue our current APK self-update mechanism?

Would we need to publish the app on Google Play, modify our existing update implementation, or introduce an EMM/MDM solution?

4. Enforcement in Japan and verification method

When will these requirements apply to this type of privately distributed application in Japan?

Is there an official method to determine whether our existing devices qualify for the enterprise exemption without modifying or resetting deployed devices?

Our priority is to preserve the current, stable deployment used in healthcare environments and avoid unnecessary changes.

We would appreciate a clear answer to each question, preferably with references to official documentation. If this inquiry requires another specialist team, please direct us to the appropriate contact.

Thank you for your assistance.