60
submitted 5 days ago by cm0002@lemmy.world to c/fdroid@lemdro.id

Last month, "Google unilaterally decreed that Android developers everywhere in the world are going to be required to register centrally with Google."

F-Droid and Google's Developer Registration Decree https://f-droid.org/en/2025/09/29/google-developer-registration-decree.html

PC Mag: F-Droid Warns Google’s New Rules Could Kill Third-Party Android App Stores https://www.pcmag.com/news/f-droid-warns-googles-new-rules-could-kill-third-party-android-app-stores @PCMag #Google #Android

top 5 comments
sorted by: hot top controversial new old
[-] rezad@lemmy.world 4 points 4 days ago* (last edited 4 days ago)

don't worry guys. google has posted a blog post

https://android-developers.googleblog.com/2025/09/lets-talk-security-answering-your-top.html

and has cleared the issue at the very start.

1.Does this mean sideloading is going away on Android? Absolutely not. Sideloading is fundamental to Android and it is not going away. Our new developer identity requirements are designed to protect users and developers from bad actors, not to limit choice. We want to make sure that if you download an app, it’s truly from the developer it claims to be published from, regardless of where you get the app. Verified developers will have the same freedom to distribute their apps directly to users through sideloading or through any app store they prefer.

so you can sideload freely, with the tiny tiny condition that you sideload just the apps that google approves of.

[-] TootSweet@lemmy.world 4 points 5 days ago

Ah. "Certified Android Devices." I think that means I can still use F-Droid on my Pixel running Lineage.

... if F-Droid continues to exist, of course.

It's still complete BS, but technically the title of the article is slightly sensationalistic. Slightly.

[-] Cris_Color@lemmy.world 6 points 5 days ago* (last edited 5 days ago)

In a post today Prud'hommeaux said that Google's planned changes are incompatible with F-Droid. "The F-Droid project cannot require that developers register their apps through Google, but at the same time, we cannot 'take over' the application identifiers for the open-source apps we distribute, as that would effectively seize exclusive distribution rights to those applications," he said.

"If it were to be put into effect, the developer registration decree will end the F-Droid project and other free/open source app distribution sources as we know them today," said Prud'hommeaux.

(From Google's dev registration plan 'will end the F-Droid project' by The Register which was linked here https://lemmy.world/post/36669429) I'm not so sure any of this is being sensationalized. Every time more details get discussed it becomes clear this is actually a lot worse than early coverage suggested.

People were talking about this just being bad for the privacy of devs, which would be bad enough alone. But if this structurally makes it so that fdroid can't distribute apps because the apps aren't registered to them, and are instead registered to their devs, that's pretty catastrophic

Its also become more clear as this has gotten more coverage that part of the impact would be requiring devs to agree to and comply Google terms and conditions. Which suggests that if what they distribute conflicts with those terms and conditions their ability to distribute apps may be taken.

If those are the same terms and conditions for the Google play store that routinely fuck over devs with no explanation for entirely reasonable shit that's really not good.

[-] TootSweet@lemmy.world 2 points 4 days ago

Yeah, but Lineage can just not have the same restrictions. And you can (as I do) run Lineage without Google Play Services or whatever. I get that this change will mean that people with normal Android phones without custom roms will no longer be able to install F-Droid or any of the apps on it, and I get that that means less people will have enough interest in F-Droid to contribute to it or write FOSS apps that I might want to be able to run. But the only reason I can think why that could result in the complete cessation of F-Droid development or package maintenance is if nobody runs custom roms moving forward. (Or F-Droid shuts down completely symbolically as a protest.)

This part of the Register article almost set off my alarm bells:

In March this year, Google also made a change to the way AOSP is developed; the public aosp-main branch is now read-only and development takes place in a private branch, with code published from time to time as android-latest-release.

But it sounds like the AOSP updates still do become FOSS eventually. Just not as soon as they used to.

This might end up being enough to get me to switch to some Linux phone for my next phone, but it's not like I wasn't strongly considering it before this news came out.

I dunno. I still suspect it's not going to affect me directly as badly as most F-Droid users. And don't get me wrong, Google is still complete assholes for doing this. But it's not going to affect my phone for a good while.

[-] monogram@feddit.nl 3 points 5 days ago
this post was submitted on 29 Sep 2025
60 points (100.0% liked)

F-Droid

383 readers
2 users here now

F-Droid is an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform. The client makes it easy to browse, install, and keep track of updates on your device.

IzzyOnDroid is an F-Droid style repository for Android apps, provided by IzzyOnDroid. Applications in this repository are official binaries built by the original application developers, taken from their resp. repositories (mostly Github).

founded 3 months ago
MODERATORS