I first read the original report from Android Authority thinking it would only be an additional hurdle for third-party stores and developers, but I’m now thinking that it would potentially block the use of ReVanced
Yeah I don’t know what they’ll block yet but I’m already assuming some of my apps will be blocked. It’s pretty terrible news. I really didn’t want to have to hunt down a phone that was compatible with alternative OS’s.
From my understanding, it will only allow apps that were registered, so since ReVanced uses identical package names to the patched apps, it probably won’t work unless they start using ReVanced-specific package names that are tied to their identity. But that would allow Google to block these package names (or ban ReVanced completely) if say, Spotify or YouTube complain about them.
What if I come up with a random package name, like “online.discuss.jim3692”, register that name and a keypair, and then build ReVanced using that name and keys?
What if I keep the apks for me and my family, instead of publicly releasing them.
This is probably similar to the state of Piped and Invidious. Google tries to kill them, so we are hosting private instances, instead of relying on public ones.
and any apk installed eventually, and custom OS, that doesnt come from the google store front. im not tech savvy but im using apk of many apps right now. if only someone can develop a “storefront” where it seperate from google.
I first read the original report from Android Authority thinking it would only be an additional hurdle for third-party stores and developers, but I’m now thinking that it would potentially block the use of ReVanced
Yeah I don’t know what they’ll block yet but I’m already assuming some of my apps will be blocked. It’s pretty terrible news. I really didn’t want to have to hunt down a phone that was compatible with alternative OS’s.
From my understanding, it will only allow apps that were registered, so since ReVanced uses identical package names to the patched apps, it probably won’t work unless they start using ReVanced-specific package names that are tied to their identity. But that would allow Google to block these package names (or ban ReVanced completely) if say, Spotify or YouTube complain about them.
… who owns YouTube?
Yeah, they’re going to block ReVanced.
Unless revanced somehow gets the APKs resigned it will almost certainly destroy revanced.
What if I come up with a random package name, like “online.discuss.jim3692”, register that name and a keypair, and then build ReVanced using that name and keys?
google can just revoke it if they dont like it. they certainly want to become apple down the line.
Because Google will find out and revoke the key
What if I keep the apks for me and my family, instead of publicly releasing them.
This is probably similar to the state of Piped and Invidious. Google tries to kill them, so we are hosting private instances, instead of relying on public ones.
and any apk installed eventually, and custom OS, that doesnt come from the google store front. im not tech savvy but im using apk of many apps right now. if only someone can develop a “storefront” where it seperate from google.
I mean, there’s fdroid…. For now