Google moves on sideloading
Google made its first concrete move to curb sideloading — announcing a plan that targets Brazil, Indonesia, Singapore and Thailand as the initial rollout in September 2026. (androidpolice.com) That change could reshape how Android users in those markets access apps outside the Play Store and is the first big platform pivot likely to affect global distribution strategies. (androidpolice.com)
Google published the policy update on March 30, 2026 and opened developer verification in the new Android Developer Console and Play Console so devs can register apps before user-facing enforcement begins. (android-developers.googleblog.com) Google’s post says sideloaded sources produced “over 90 times” more malware than apps on Google Play, which the company cites as the core rationale for adding identity-based verification. (android-developers.googleblog.com) The company published a phased calendar: an “Android Developer Verifier” system service starts appearing on devices in April 2026, early/limited-distribution programs run through June–August, and formal enforcement for the first wave of markets is set for September 30, 2026 with broader rollout scheduled in 2027. (9to5google.com) Under the new rules, apps installed on certified devices must be registered to a verified developer and linked to signing keys; installations of unregistered apps will require ADB or an “advanced flow” intended for technically proficient users. (android-developers.googleblog.com) Google’s documentation keeps a developer path for hobbyists: full distribution requires creating an Android Developer Console account with the familiar one-time $25 registration fee, while “limited distribution” accounts (no fee) permit sharing to up to 20 devices without government ID. (support.google.com) Enforcement applies to certified Android devices that ship with Google Mobile Services; Google says the verifier will check registration status via Play services rather than inspecting app content. (androidauthority.com)
