Is Android Banning Sideloading or Requiring Developer Verification?

Google is adding identity verification and app-registration requirements to parts of the Android ecosystem.

That is a material change, but “Android has banned sideloading” does not accurately describe the published policy.¹

The rollout is staged

The initial enforcement phase began on 30 September 2026 for participating stores in Brazil, Indonesia, Singapore and Thailand.

Google says broader expansion for apps on certified Android devices is scheduled for 2027.

Its FAQ distinguishes this first phase from direct sideloading and non-participating stores. Separate Play Console registration requirements can have a wider reach and should be assessed separately.¹

Unverified does not mean impossible

Google describes an advanced installation flow for users who choose to install apps from unverified developers.

The published process includes security checks and a one-time waiting period. It is not described as a fresh one-day wait for every app.

The actual experience can depend on device support, rollout status and the installation route.²

Other routes remain relevant

Google says ADB installations do not require verification and are not subject to the advanced-flow waiting period.

It also describes limited-distribution accounts for up to 20 devices without government-ID verification or a fee, and an exemption for organisation-store distribution on managed enterprise devices.

These routes have their own conditions. They should not be presented as universal substitutes for every consumer installation scenario.²

See also

• Epic v Apple and the Android distinction
• What the Apple orders actually require
• Overseas scope of the Apple ruling

This page provides general information that is time-sensitive. Check Google’s current documentation before planning distribution, and obtain specific advice about any distribution decision that matters to your business.