Starting September 2026, Google will block sideloading of unregistered Android apps worldwide, making de-Googled and Linux phone alternatives more urgent.
Key Takeaways
The Keep Android Open campaign counts down 123 days until Google’s sideloading block; developers must register, sign contracts, pay fees, and submit government ID.
Google is also reducing AOSP source code update frequency, squeezing de-Googled Android forks like /e/OS and GrapheneOS upstream.
Murena (/e/OS), Punkt (MC03), Volla (Volla OS or Ubuntu Touch), Jolla (Sailfish 5), Furilabs (FLX1s), Purism (Librem 5), and PinePhone cover the current hardware field.
Non-Android options like Sailfish, FuriOS (Debian), Mobian, and postmarketOS can run Android apps via VM or container, narrowing the compatibility gap.
Apple’s iOS 26.4 adds mandatory passport/driver’s licence age verification in the UK, locking out citizens with non-qualifying ID into permanent child mode.
Hacker News Comment Review
The core practical blocker is not hardware availability but app compatibility: one missing banking, transit, or government app forces carrying a second mainstream phone.
Commenters challenged the “non-Google” framing since most listed devices still run AOSP-derived Android; GrapheneOS on a Pixel was flagged as the more rigorous privacy option, though it is not sold preinstalled.
HarmonyOS NEXT (microkernel, ArkTS/Cangjie toolchain) surfaced as a notable third ecosystem, though commenters noted its real-world usability outside China remains limited.
Notable Comments
@chappi42: Article omits GrapheneOS, “the by far better option” for updates, privacy, and security among de-Googled Android builds.
@tgsovlerkhgsel: Societal lock-in, not purchase friction, is the real barrier; one critical service without a workaround forces a mainstream device anyway.
