I think the issue is that F-Droid would not be able to enforce that.
This is what I don’t understand and the article didn’t make it clear. I assume a lot of people using F-Droid are already using degoogled devices. I would expect that if you tried to use F-Droid on a non degoogled device, it would just fail to install. So I don’t understand why F-Droid would have to “enforce” anything on degoogled devices
1 Like
The problem with F-Droid is that they sign all the apps themselves. That is not compatible with Google’s new policy of only allowing apps from approved developers.
F-Droid could theoretically decide to not sign the apps themselves but let the developer sign them instead. This would allow all apps from certified developers to run even if installed from F-Droid. Of course, many open source app developers will refuse to get certified so their apps cannot be installed, but that’s not a problem specific to F-Droid.
| Developer is certified with Google | Developer is NOT certified with Google | |
|---|---|---|
| Play Store | OK | n/a (can’t publish on Play Store) |
| F-Droid | Won’t work as F-Droid signs the app with their own key | Won’t work |
| Github / Developer website / Accrescent etc. | OK | Won’t work |
1 Like
I still don’t understand this. What is stopping them from continuing to do this and then if it’s ever used on a Googled machine obviously it will fail to install? To be clear I’m talking about the use case for degoogled devices only, I understand that for non-Degoogled devices they would not be able to use F-Droid Apps.
If people can continue to use Fdroid and apps signed by F-droid on degoogled devices (and why wouldn’t they be able to? it’s not running play store or google services) I still don’t understand how this “ends” the project
I don’t think that’s true. They have Reproducible Builds who can be developper-signed.
Google gives Android users a way to install unverified apps if they prove they really, really want to.
It turns out you won’t be limited to Google-verified apps an developers on Android after all. In the face of sustained community dissatisfaction with its developer verification requirement, Google has given Android users an out.
Users must first enable developer mode in system settings. They then need to confirm that they’re not being coerced. After that, they need to restart their phone and reauthenticate. And then they need to wait one day.
1 Like
Still not acceptable. F-Droid has close to no malicious apps over its lifetime.
This process for web-downloaded apps I understand. But for reliable stores such as F-Droid or even Accrescent, this is non-sensical. Or even Aurora users.
3 Likes
The “out” is more malicious compliance than a true pullback from Google.
Being required to wait 24 hours on a device I own to install the app(s) I want is still insane.
Its better than nothing, but far from friendly to developers or users.
4 Likes
So with this new system F-droid is not “dead”?
Indeed still not acceptable, but this is a turning point from Google after some pressure.
3 Likes
I’m still curious if this same workflow will remain on Android TV or is limited to “just” phones and tablets? I ask because SmartTube is an essential app for me and the only reason I keep my Shield TV humming alongside an Apple TV.
If Google blocks being able to install non-Play Store apps on Android TV, the platform is pretty much the same as Roku in terms of utility.
Do you mean that F-Droid could build something into it’s code so that if a regular Google Android user tried to download the APK and install it it would not work? I am not technical enough to know this, but wouldn’t an APK just be installable on anything that is Android-based?
Another issue is that the motivation for developers might be low to spend time on their apps if their potential user base is limited to people with non-Google operating systems.
Having said that, I see a lot of activity on the Linux Mobile Apps website, so maybe there would be enough interest.
No I mean if Googled devices are blocking apps from outside the app store that blocking would apply to F-Droid via Play Services likely. Although now we’re seeing there is this work around and the wait 24 hours thing
I don’t think the open source android builds without Google play would have the ability to block apps like this but I guess it is possible that they add it into base android vs just play services? However I was assuming the terms “certified devices” meant that it would not apply to "non certified devices” such as any custom rom, Graphene OS etc.
1 Like
I did just find this notice on https://keepandroidopen.org/
Update: Google has not “backed down” from developer verification
Contrary to a vague mention 
of a possible “advanced flow” that may eventually allow “experienced users to accept the risks of installing software that isn’t verified”, Google’s description of the program continues to state plainly that:
Starting in September 2026, Android will require all apps to be registered by verified developers in order to be installed on certified Android devices
Until such time that they have shown evidence that it will be possible to bypass the verification process without undue friction, we must believe what is stated on their official page: that all apps from non-registered developers will be blocked once their lock-down goes into effect.
The article about the 24 hour wait thing came out after the keepandroidopen post about google not backing down and likely has not updated yet. At this point I think we can assume this is the path they are taking forward
1 Like
Scammers will just change their direction to “25 hours”.
I don’t buy this idea that the 24 hour ban is gonna do anything to stop scams.
2 Likes
So for power users there are three ways to install uncertified apps:
- Developer options and wait 24h to enable sideloading
adbor AnyAPK to install apps- Use a google-free distribution (GrapheneOS, LineageOS etc.)
99% of users will just stick to Play Store + Google account.
That’s the entire goal of Google : cement their control of the ecosystem by making using another App Store scary and technical.
5 Likes
They are counting on the fact that no one can develop another OS (or adapt Linux and have OEMs support it) and apps for the same.
It’s upto the industry, enthusiasts, and the truly benevolent wealthy (if there is such a thing) to contribute a serious development of an alternative. Tech for the people, by the people, not only for the sake of monetization and control. Open, and free, and something that works for you and not against your wallet, sanity, and freedoms.
3 Likes
The only real way I think is if Google truly closes AOSP. This could result to something like RISC-V.
But I don’t hold my breath. Also, those OEMs could just bypass those restrictions. At least in the EU and Japan, Google couldn’t punish them from doing so.