Starting in September 2026, Google requires that apps installed on certified Android devices in select regions come from verified developers. This requirement rolls out to additional regions from 2027 onward.
For most enterprise deployments, the impact is minimal:
Where developer verification does matter for enterprise:
User-initiated sideloading - if users install apps outside of EMM-managed channels on certified devices (for example, downloading APKs from a website), those apps will require a verified developer in affected regions. From August 2026, sideloading apps from unverified developers requires an "Advanced Flow" that includes enabling developer mode, a mandatory 24-hour waiting period, a device restart, and biometric or PIN authentication before the install is permitted. Users can then choose a 7-day or indefinite sideloading window. ADB-based installation remains unaffected.
Third-party dependencies - if the organisation relies on public Google Play apps from smaller developers or niche vendors, those developers need to complete verification through the Google Play Console. Apps that lose the ability to be installed due to an unverified developer could disrupt workflows after the extension period ends.
Google also offers free limited distribution accounts for students and hobbyists, allowing app sharing with up to 20 devices without requiring government ID verification or the $25 registration fee.
More detail on this change and what organisations should do to prepare can be found in Google Play developer verification: what this means for consumers and enterprise.