No one talking about how this could completely annihilate open source .apk development? First off the lead dev has to get identity verified to get a key, which will reduce the number of devs willing to push through friction to start a project. Then when the key is issued and it is posted to the repository, what keeps anyone from grabbing it and using it for another repo? We'll they have an official app registration of some kind, ok, what about version control? Does every new version have to be registered before it can be loaded and tested? Same for forks?

This is about to be a terrible mess, Google is assassinating FOSS with this.

[–] Awkwardparticle@programming.dev 8 points 11 hours ago

It will kill everyone that is playing around with the phones. I have done a couple mobile projects where I just sideloaded the package I created to quickly test it and to demo it to people. Now that I can't do that why would I develop for your platform by choice.

[–] InFerNo@lemmy.ml 16 points 1 day ago (2 children)

You distribute the code without your key and a built package that is signed. This isn't exactly rocket science.

Anyone who forks the code will have to use their own key to install a package they built.

It's just unnecessary red tape.

[–] giant_smeeg@feddit.uk 1 points 9 hours ago (1 children)

How will fdroid work

[–] InFerNo@lemmy.ml 3 points 8 hours ago

Fdroid itself and every package they host will have to be signed.

Maybe there are still workarounds, like enabling dev mode on your phone, but still tedious.

[–] kureta@lemmy.ml 24 points 1 day ago

It's just unnecessary red tape.

Which will reduce the number of people using foss apks, which will in turn, reduce the motivation, and then the number, of foss apk developers.