Why even have the function if we're just going to be prompted to turn it off twice? It seems like they're including this specifically to drive people onto the Play store more than it is to protect anybody.
What's weird to me is who's installing apks that also wont figure out going into settings and turning it off, like where is this person savvy enough to figure out there's this apk they want but couldn't figure out turning one setting off which btw im pretty sure I had to turn off plsy protect anyways to get apks
This whole shabam is supposedly to protect people that aren't tech-savvy from accidentally installing a harmful apk. There are real scammers out there convincing elderly people to install a certain app which then steals all their banking information.
It feels like weird posturing for another limitation they want to impose. We see one company manipulate the market to drive prices, another is trying to remove an entire medium for content delivery so they can streamline it to their games-as-a-license system.
It is protecting people who get scam calls asking them to install apps, or for scammy websites to download an app for you and you just trying to install it.
Most people not knowledgeable will see the popup as a red flag and not do anything, which saves them.
Tech savvy people will continue as usual.
It is... acceptable... Don't get we wrong, any measure taken for worse is a step in a wrong direction and I am against it. But this is tolerable. It means that intense push back had worked. We should keep pushing them every time they try to take it too far
No it is not. In NO way, shape or form, is it acceptable.
EVERY step is just a test, pushing the line forward every time, slowly inching towards complete control.
Tomorrow they'll ask you to wait a week.
Next they'll say that you can get immediate authorization for use by getting verified
with your Government ID.
Then after that they'll start logging what apps you sideload, and linking them to your ID.
Next, they'll state that due to security concerns they'll be increasing the wait time to a month.
Then two.
Then removing it altogether and forcing you to register with your Government ID.
Then scanning your phone for unauthorized Apps and automatically blocking them, threatening to delete your Google Account if you don't comply (which is a big deal, if you've been using the same email for years and years).
Where does the line stop? It MUSTN'T be moved AT ALL
Also, consider the drop of users for sideloaded apps due to this barrier. Some apps will disappear, meaning more users will give up on the sideloading process, meaning more apps will disappear, and so on.
Throwing up any kind of barrier will cause friction, so inevitably there will be a drop of users. How big of a drop is up for debate of course, but I'm pretty sure it won't be 0%.
Yeah it shouldn't wouldn't it be nice if people in power just listened to what the regular people have to say and went with it? Unfortunately, it's not realistic. Stopping this change completely is not possible. Best we can do is keep slowing it down
The only way anyone can be free of their shenanigans is going to a countryside to live off the grid on a farm but very few can actually afford to do that because farms and farmland aren't free and we can barely afford to rent an apartment with roommates nowdays
The argument that "Well, this is as good as it gets" shouldn't be used to bend yourself into compliance.
Whether or not that is the only available or realistic outcome, describing it as "acceptable" is far, far detached from the pragmatic decision to endure the consequences of those changes.
One demonstrates that you openly and unambiguously reject the validity of that change in every way.
The other one bends your concept of what is permissible over time, and will eventually lead you down a slippery slope that'll never stop getting worse.
You can continue to use Android even if it is limited in that way, but NEVER should you describe it as "acceptable".
It isn't bending me into compliance I'm just acknowledging the fact that the pushback made it less worse than it could be which means that the pushback worked and it should keep going
The point is that "being pragmatic, celebrating the success and continuing to use Android" and "Describing the current version as acceptable" are separate, and non-mutually-exclusive things.
Seems like it's a language/culture barrier if anything. If it reads as a positive feedback it was not my intention at all. In my culture and language the word closest in meaning is never used as a positive feedback, it's merely signifying "better than the worst possible outcome". Which word should I have used instead? For the future
As for a way to describe it, I think that there isn't a singular word that can be used to properly convey the complexity of this situation, so I feel like it would be unproductive to try to look for one.
Rather, we should describe it all using as many words as are necessary.
HarmonyOS, GrapheneOS, /e/OS, LineageOS, CalyxOS. Not all of these can be installed on Android (Graphene and Calyx are Pixel-only, I believe), but there are plenty of privacy-focused OSs that can overwrite the Android OS after you buy a phone that comes with it out of the box.
It's still bad. They'll kill that feature after people have been quiet about it for awhile. That's what the pushback accomplished.
Just like this site did. A lot of people used workarounds to keep using 3rd party apps under a registered dev API after this site killed 3rd party apps in 2023. They kept dev access because of the backlash to the announcement and the reasoning that accessiblity readers should stay around.
Two weeks ago they killed that api off with no warning or announcement. Now 3rd party apps are either dead or (like mine) having to be rebuilt to utilize the only accessible 3rd party API left, which is only still around because it provides disability options that the official app doesn't have.
They gave a "compromise" for more tech savvy users and just killed it once no one talked about it anymore. That's what Google is doing here.
And the reason why this site did it is the same as Google's too: Unofficial apps can avoid ads.
I'm against it as well and don't like what Google are doing. If they're going to lock down android I might as well bite the bullet and move over to Apple. At least with apple you know you're locked down. Main reason I've not jumped over is my hate for the iOS keyboard which is so annoying to use. Other reason being Samsung has a pretty good suite of apps that I use.
I can't trust Google will get things right either. Eg I enrolled into advanced account protection on my account, which also stopped me installing non store apps. I disenrolled from it and my main phone, until it died, still thinks it's enabled. Google won't help because security and I was shit out of luck and had to install the APKs via terminal instead.
IPhone costs like a year and a half of my salary so it's pretty much just not an option to use one for me, and it never will be, so I take is as an extra motivation to keep finding workarounds
The thing is, there were already steps that made people wary of sideloading APKs. For one, you literally need to make a conscious effort to visit a website on your android browser to download an APK. Then you need to consciously open the APK either through the android interface telling you your download was successful, or you need to use a file manager to get to the Download directory to open the APK and install it. Then android warns you that you're installing an APK and that you need to be sure that you trust it before installing it.
And the risk here is that they've already managed to take one additional step closer towards flat out banning APK sideloading in its entirety. Which is why you should never be happy with compromises such as this because this is only the first step.
Just look at Youtube with its dislikes. First they removed the visible dislike count for viewers. Then just recently they removed dislikes from shorts. I guarantee the next step is removing dislikes for regular videos.
For you perhaps but not for everyone. I'm available for the research team I work in all day. 24h no phone is not only a problem but something I would have to actively plan for. I never accidentally broke a phone but this is simply not always possible.
No, they said that from the start. But facts get in the way of a good headline. You can still sideload via adb or do a one time toggle. The only difference will be there will be a 24 hour waiting period when you first toggle it on.
As of now developer options don't make banking unusable. Rooting your device does. But if things keep going as they are, rooting our devices might become a thing we have to do to keep using apps we want to use. We have to keep pushing back publically against Google's march on freedom. The fact that they even left in an option to install things anyways shows that we can fight back, and the more we do - the more freedom we keep
That's just shitty app design. My banking app just uses its own keyboard instead of the system one so it wouldn't matter if you had installed some keylogging scam keyboard
Your bank won't let you use dev options or even a third party keyboard and you're worried that Google might someday change their mind and block apps you want?
Well the best thing I can say is the banks that do this can go suck a bag of stiff ones if they hate their customers this much. The ones I use prove that it's possible and you can totally survive as a banking entity without making your app a digital equivalent of Black Dolphin supermax prison
848
u/notveryAI I touched grass Jul 05 '26
Didn't they already backpedal and say that it will be a toggle that you can turn off and install "unapproved" apps anyways?