this post was submitted on 13 Nov 2025
127 points (98.5% liked)

Android

20625 readers
193 users here now

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

πŸ”—Universal Link: !android@lemdro.id

πŸ’‘Content Philosophy:

Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.

Support, technical, or app related questions belong in: !askandroid@lemdro.id

For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id

πŸ’¬Matrix Chat

πŸ’¬Telegram channels / chats

πŸ“°Our communities below

Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.

  5. No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More

founded 2 years ago
MODERATORS
ijeff@lemdro.id
ladfrombrad@lemdro.id
Paradox@lemdro.id
multimoon@lemdro.id
mikestevens@lemdro.id
Devgard@lemmy.world
limerod@reddthat.com
Netrunner@lemdro.id
127
Google's sideloading restrictions are being eased up somewhat (android-developers.googleblog.com)
submitted 1 week ago* (last edited 5 days ago) by Xylight@lemdro.id to c/android@lemdro.id
27 comments fedilink hide all child comments
 

Google has announced it is building a new way for 'experienced users' to install Android apps that haven't been verified.

test

top 27 comments
sorted by: hot top controversial new old
[–] Strayce@lemmy.sdf.org 85 points 1 week ago* (last edited 1 week ago) (1 children)

This isn't -bad- news, but I'm still not impressed. They could have just, you know, not done it in the first place. They don't get credit for partially walking back a bad decision. The "advanced flow" is more likely a dark pattern, and will still have a chilling effect on FOSS uptake and distribution, which is still the intended purpose of the change.

[–] TheOneCurly@feddit.online 5 points 1 week ago

yep, it was already impossible to get people to use fdroid. Now there's no way anyone except hardcore enthusists will even attempt to get away from the play store.

[–] GeneralDingus@lemmy.cafe 31 points 1 week ago (1 children)

Still going to give Linux phones a shot now that the cats out of the bag.

[–] vividspecter@aussie.zone 21 points 1 week ago

Yep. Also, unlockable bootloader support has went from a high priority to mandatory on the back of this news. Hopefully there are multiple good Linux options for my next upgrade in a few years too.

[–] rearview@lemmy.zip 31 points 1 week ago (1 children)

Building a new way does not adequately means giving up on developer verification. In the last paragraph, Google is also promoting the verification for non-GPlay developers.

Out of all possibilities in this universe, there may be a chance that these new flows include user verification instead of developer.

There should also be a rule to rephrase "sideloading" as "installing from non-Google-approved sources" at this point.

[–] Xylight@lemdro.id 4 points 1 week ago (1 children)

As much as sideloading is a strange term, it is one that most people understand. If someone were to search for information about this specific topic, they would search for "sideloading", not whatever alternative we come up with, regardless of how "accurate" it is

[–] Strayce@lemmy.sdf.org 2 points 1 week ago* (last edited 1 week ago)

IIRC, the term predates Android, and was originally coined to refer to installing non-apple applications on the original iPhone. At the time, this could only be done via cable. So, as distinct from "downloading" from the app store to the device, it does make a certain kind of sense. It's been accepted into the vernacular with a slightly warped meaning, but that's language for you.

[–] possiblylinux127@lemmy.zip 30 points 1 week ago (1 children)

Reminds me of manifest v3

They just delayed it until people got bored being mad

[–] henfredemars@lemdro.id 2 points 1 week ago (1 children)

I just hope more open phones like the rumored Graphene phone with actually good high-end hardware are out by then so I can leave their ecosystem comfortably. As you wrote, Google has a history of abusive behavior and doing what they want anyway.

[–] ivanafterall@lemmy.world 27 points 1 week ago

Sorry, I'm seeing someone else.

[–] LiveLM@lemmy.zip 26 points 1 week ago

Based on this feedback and our ongoing conversations with the community, we are building a new advanced flow that allows experienced users to accept the risks of installing software that isn't verified. We are designing this flow specifically to resist coercion, ensuring that users aren't tricked into bypassing these safety checks while under pressure from a scammer. It will also include clear warnings to ensure users fully understand the risks involved, but ultimately, it puts the choice in their hands. We are gathering early feedback on the design of this feature now and will share more details in the coming months.

Amazing, so basically what everyone said: Put all the big red scary warnings you want but don't make it impossible.
Look how much pushback was needed to reach this obvious common sense solution. Truly incredible.
Thanks for nothing Google πŸ‘

[–] GreenKnight23@lemmy.world 15 points 1 week ago (1 children)

too late. eat shit and go fuck yourself, Google.

[–] Chakravanti@monero.town 1 points 1 week ago

You say eat shit, like you think talking shit is a kind implication you're totally not-saying something of purpose and consequence.

There is no difference between Algorithms and "Digital Mushrooms." They will eat the dead just as much as they eat the living.

[–] MasterBlaster@lemmy.world 10 points 1 week ago (1 children)

Couldn't handle the blowback, eh? I doubt this will convince the townsfolk to put down the pitchforks. Might need more walk back.

[–] Zak@lemmy.world 19 points 1 week ago (1 children)

I imagine they announced the most extreme form of it they were considering and had several fallback plans depending on how much backlash there was.

[–] MasterBlaster@lemmy.world 2 points 6 days ago

Definitely the intelligent way to do it.

[–] baguettefish@discuss.tchncs.de 9 points 1 week ago* (last edited 1 week ago) (2 children)

a fairphone with murena /e/os is looking pretty good right about now, or maybe whatever grapheneos is cooking up.

[–] dust_accelerator@discuss.tchncs.de 4 points 1 week ago* (last edited 1 week ago)

Have one (Fairphone with E/OS) and tbh, I really enjoy not dealing with googles shenanigans and straight up malware practices. I did not take kindly to one morning them telling me they removed a "dangerous" app. Mind you, it was a work phone and NFC debugging app from our own institute, costing my employer my lost time on it. Extra bonus for remotely installing and executing unwanted services that reduce battery life by 75%.

With that level of interference, I wonder about the legal implications? "Someone torrented shrek from that phone?" Or even "Device was used as part of a malicious DDoS op?" Must've been some intern/intelligence agent at google, I don't control the device after all." seems like a legitimate defense/claim. Well, as long as the rule of law exists in some way. But if that goes away, then it doesn't matter really. At that point you need guns and combat drones, not phones.

[–] shifty@leminal.space 3 points 1 week ago (1 children)
[–] baguettefish@discuss.tchncs.de 4 points 1 week ago

there are multiple linux phones and distros, but I'm not considering any of them at the moment. I do like some or even a lot of convenience, and degoogled android is just about the most concessions I can make at the moment.

[–] MonkderVierte@lemmy.zip 5 points 1 week ago (1 children)

Salamitaktik?

[–] henfredemars@lemdro.id 3 points 1 week ago

Interesting! I learned a new word. And yes, look to Google Chrome's walking back of blocking ad-blockers to its eventually implementation anyway once people stopped screaming about it.

[–] sem@piefed.blahaj.zone 4 points 1 week ago

Mort and Baileys tactics

[–] jaggedrobotpubes@lemmy.world 3 points 1 week ago

This will buy everybody more time to make/refine/try out normal non-google options, before they inevitably kill it permanently in a few years.

[–] kokesh@lemmy.world 1 points 1 week ago (1 children)

They are not easing up anything. They said there will be small scale testing still possible already. What we need is to say Yes, I want to enable Unknown sources install like we did until now.

[–] QuizzaciousOtter@lemmy.dbzer0.com 1 points 1 week ago

we are building a new advanced flow that allows experienced users to accept the risks of installing software that isn't verified