Comment on From F-Droid to emulators, here's who's hit hardest by Android's new verification rules

greencoil@lemmy.frozeninferno.xyz ⁨2⁩ ⁨days⁩ ago

Saving you a click:

Read the fine print carefully, and Google’s new app-loading processes aren’t as invasive as they could have been. For many users, nothing will change. Even for users exploring apps outside Google’s walled garden, the process is usually a one-time setup with a few simple steps and a short wait, keeping the experience virtually the same as it is today.

We have phone manufacturers who offer unlocked boot loaders as a feature, but require two weeks or more of device ownership, registration using personally identifiable info for an online account, and many times don’t even allow you to relock the boot loader. Despite all this hassle, these devices still get updated third party OS’s with Lineage and eOS.

Anyone who was publishing to FDroid already is not going to be annoyed about the 24 hour scare screen for users. The most inconvenient aspect is that they can’t use the same signing keys as a Google Play release, which they should never have been doing anyway. Its absurd that developers were using the same signing keys across all different distribution methods in the first place.

source
Sort:hotnewtop