To recap the storyline, as far as I understand it: last August, Google announced plans to heavily restrict sideloading. Following community pushback, they promised an "advanced flow" for power users. The media widely reported this as a walk-back, leading users to assume the open ecosystem was safe.

But this promised feature hasn't appeared in any Android 16 or 17 betas. Google is quietly proceeding with the original lockdown.

The impact is a direct threat to independent AOSP distributions like Murena's e/OS/ (which I'm personally using). If installing a basic APK eventually requires a Google-verified developer ID, maintaining a truly de-Googled mobile OS becomes nearly impossible.

I don't see a real future for Andrioid as an open platform unless the community comes together and does a hard fork. Google can continue to develop their version and go the Apple way (which, funny enough, no one has a problem with). Development of AOSP can be controlled by a software foundation, like tons of other successful projects.

If I understood correctly, to "protect" users, Google wants to control what is installed on Android phones. I guess it means the Play store will be the only way to install an app, which in turn means: - That users won't be able to install what they want and that they would need a google account to install apps - That app developers have to go through google to distribute their apps, with identity verification etc. Obviously this is awful and would mean the end of F-droid and Aurora store etc. However, I'm also reading here and there that it is a threat to alternative ROMs. To me it sounds at the contrary as an amazing opportunity, as they can strip this verification and be the only truly open Android, or am I missing something? Why do people link this app verification thing with a possible closing of AOSP?

Also, Mozilla was already saying it 10years ago with Firefox OS but... The web is the platform. 90% of the apps out there could be websites. We have all technologies needed for this including offline with service workers. And it works on every damn platform, even the most obscure OS has a web browser. Don't want to be locked to an ecosystem? Just target the web!

> We appreciate the community's engagement and have heard the early feedback – specifically from students and hobbyists who need an accessible path to learn, and from power users who are more comfortable with security risks. We are making changes to address the needs of both groups.

> We heard from developers who were concerned about the barrier to entry when building apps intended only for a small group, like family or friends. We are using your input to shape a dedicated account type for students and hobbyists. This will allow you to distribute your creations to a limited number of devices without going through the full verification requirements.

> Based on this feedback and our ongoing conversations with the community, we are building a new advanced flow that allows experienced users to accept the risks of installing software that isn't verified. We are designing this flow specifically to resist coercion, ensuring that users aren't tricked into bypassing these safety checks while under pressure from a scammer. It will also include clear warnings to ensure users fully understand the risks involved, but ultimately, it puts the choice in their hands. We are gathering early feedback on the design of this feature now and will share more details in the coming months.

It is also true that they have not updated their developer documentation site and still assert that developer verification will be "required" in September 2026 [1]. Which might be true by some nonsensical definition of "required" if installing unverified apps requires an "advanced flow", but let's not give too much benefit of the doubt here.

0: https://android-developers.googleblog.com/2025/11/android-de...

1: https://developer.android.com/developer-verification

Edit: this will likely exist "uncensored" in other markets but conform to the PRCs standards and practices domestically, similarly to how tiktok operated prior to selling a version specifically taylored to US censorship and propaganda.

Google listened.

Blame the judge for one of the worst legal calls in recent history. Google is a monopoly and Apple is not. Simple fix for Google...

It's been our choice to drink this glass of wishful thinking while giving that company a solid dominant position in the market.

We ("you") can only make choices that will overturn that trend.

Fully opensource hardware with fully opensource software? Maybe, but also this is wishful thinking.

In contrast, Apple has a ~48 hour turnaround for reviews before you can upload to TestFlight and distribute a beta with a link

Not sure if I am in some "trusted developer" cohort on iOS but not Android - but the difference was enough for me to stop trying on Android

Sure parts of it were, but Google has always remained in control of Android. Anyone who expected that to change (in favor of more openness) hasn't been paying attention to the actions of tech companies for the past several decades.

Remember how hard Amazon had it to attempt an Android fork?

I was due to OEM SOC access being locked out due to those contracts....

Any open source mobile OS attempting to complete with AOSP needs access to mobile OEM soc providers not touched by AOSP contracts and currently that is somewhat hard.

Do you ever feel like the same food item doesn't taste the same it did 10 years ago? Maybe it's your memory being faulty or maybe the company got new management which decided to cut costs while keeping prices, extract the differential value from customer inertia and move on when the product stops being profitable.

Android is the same. Certain freedoms were a part of the offering - a part of the brand name. They no longer are. Not only should lose their trademark[0], they should be legally forced to change the name.

[0]: The purpose of which is to identify genuine product from counterfeits - in this case, the counterfeit just happens to be by the same company which released the original product.

A bit ironic to not believe Google is doing this. The same questions have same answers when asked about when Google is locking down side loading. A bit self-serving to pick and choose which things you want to believe are happening.

Let's focus on making it possible to use really open Linux systems on smartphones.

Nothing lasts for ever. The sooner you make the switch, the better off you will be.

You must find truth. Lies will find you.

This view NEEDS to be central to the tech freedom rhetoric, else the whole movement is literally just begging politicians and hoping corporations do the right thing... useless.

I own a Pixel and while the hardware seems decent, I've had a buggy and annoying experience with Android, and it's been getting worse lately.

Are Google so high on their own supply that they think people use their phones out of preference for the OS? Because frankly it's not very good. That's like Microsoft thinking people use Teams because of its merits.

People buy Android phones because they can be had cheaper than an equivalent iPhone and because in spite of the buggy and inconsistent mess of an OS, you aren't beholden to Apple's regimented UX. Locking down Android will not give it a "premium experience"... It'll always just be "Temu iOS" at best.

It's time to say goodbye.