This is different, by design. Sideloading and alternate app stores are still perfectly fine. It’s just that the developer has to give a bunch of personal into to Google in order for their app not to be rejected by the phone itself. Middleman doesn’t matter which is where most if the regulations are. Problem is that many open source apps don’t have a developer willing to spend the time and money or give up their privacy in order to publish an app they don’t make money on. So it’s designed to kill off FOSS apps.
As the F-Droid team signs the (not repoducibly built) apks with their own key, Google would have to allow the key of the F-Droid team then.
Yet, as Google currently does not permit apps in their PlayStore that aren’t in line with their business model, e.g. NewPipe, they would then force the F-Droid team to do the same.
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
Possibly, but I don’t see Google doing that either. It’s not about where the app comes from really. The thing they are going to restrict is the developer. A developer can not have their app installed on a certified phone, regardless of where the user got the app, if the developer is not registered.
So, since there are no regulations to allow a user to install apps from any chosen developer, only from any chosen app store, there likely will be no regulatory recourse like Apple is facing as mentioned by the OP.
My first point is, in other words: From Google’s pov, the F-Droid team is “the developer” who’s key and personal information Google would request to allow installing apks with their signature on Android devices.
This is different, by design. Sideloading and alternate app stores are still perfectly fine. It’s just that the developer has to give a bunch of personal into to Google in order for their app not to be rejected by the phone itself. Middleman doesn’t matter which is where most if the regulations are. Problem is that many open source apps don’t have a developer willing to spend the time and money or give up their privacy in order to publish an app they don’t make money on. So it’s designed to kill off FOSS apps.
As the F-Droid team signs the (not repoducibly built) apks with their own key, Google would have to allow the key of the F-Droid team then.
Yet, as Google currently does not permit apps in their PlayStore that aren’t in line with their business model, e.g. NewPipe, they would then force the F-Droid team to do the same.
They said they can’t do that in the article:
They would need to modify the ID then.
OSMand, e.g. has different IDs in PlayStore and F-Droid (+vs.~suffix).Edit: It’s the names that are different, the IDs are the same.
Possibly, but I don’t see Google doing that either. It’s not about where the app comes from really. The thing they are going to restrict is the developer. A developer can not have their app installed on a certified phone, regardless of where the user got the app, if the developer is not registered.
So, since there are no regulations to allow a user to install apps from any chosen developer, only from any chosen app store, there likely will be no regulatory recourse like Apple is facing as mentioned by the OP.
My first point is, in other words: From Google’s pov, the F-Droid team is “the developer” who’s key and personal information Google would request to allow installing apks with their signature on Android devices.