Android's Sideloading Limits Are Its Most Anti-Consumer Move
Key topics
Google's new limits on Android sideloading have sparked controversy among users and developers, who argue it restricts consumer freedom and ownership of their devices. The discussion highlights concerns about the implications for Android's openness and the potential consequences for users and developers.
Snapshot generated from the HN discussion
Discussion Activity
Very active discussionFirst comment
49m
Peak period
97
0-6h
Avg / period
20
Based on 160 loaded comments
Key moments
- 01Story posted
Oct 13, 2025 at 11:24 AM EDT
3 months ago
Step 01 - 02First comment
Oct 13, 2025 at 12:13 PM EDT
49m after posting
Step 02 - 03Peak activity
97 comments in 0-6h
Hottest window of the conversation
Step 03 - 04Latest activity
Oct 15, 2025 at 8:31 PM EDT
3 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
You still can do that with PWAs in Android. Let's see for how long.
And I wonder when can we stop lying to ourselves pretending "web"-apps are real (native) apps?
I make lots of "real" healthcare apps that are PWAs.
Much better installation and user experience, no dev cert nonsense, brain dead simple updates, no app store, etc...
“In 2024, the App Store made $103.4 billion to Google Play’s $46.7 billion.”
0 https://www.businessofapps.com/data/app-data-report/
Android used to be weak against iPhone and needed to cooperate, so they allowed more apps in to grow the userbase. Now that they're big and strong, they don't need allies, so they start kicking out everyone who isn't making them money.
Every "enshittified" service does it - Imgur, Reddit, whatever. Everyone selling $10 bills for $9 does it. Microsoft did it. They took a step backwards by buying GitHub, when they realized they were totally blowing it on cloud. But now that they have users stuck on GitHub and VS Code, they're defecting again.
Googles/Apples argument would have been much stronger if their stores managed to not allow scams/malware/bad apps to their store but this is not the case. They want to have the full control without having the full responsibility. It's just powergrab.
Scam apps are rife in the iOS App Store. But what they can’t do easily install viruses that affect anything out of its sandbox, keyloggers, etc
I agree let's have sandboxed app instalations on platforms. Flatpak is already going this way. But it looks like big players Microsoft,Apple and Google are gatekeeping app sandboxing behind their stores instead of allowing people/devs to use sandboxing directly.
Is that really your answer? To make the phone ecosystem as fraught as Windows PCs for the average user? How is they worked out for PC users since the 80s?
Just to be clear, are you claiming that we would be better off if PC hardware and OS vendors had the level of control that smartphone vendors do today?
You really can’t trust developers to do the right thing - even major developers like Zoom (the secret web server) , Facebook (the VPN that trashed usage actoss apps on iOS) and Google (convincing consumers to install corporate certificates to track usages on iOS).
Even more to the point, you read about some app installed outside of the Google Play store that’s malware - including the official side loaded version of FortNite…
https://blog.checkpoint.com/research/fortnite-vulnerability-...
You really can’t trust developers to do the right thing
Indeed not, and that includes OS developers. Imagine if Microsoft had been able to block web browsers other than IE in the name of "security".
In the modern day, I actually think this mostly works? Are you aware of instances where normies installed Windows malware because they purposefully disabled Windows Defender?
Everyone always talks about the "Dancing Bunnies Problem" but I'm not convinced it's actually a thing.
On the Mac, people installed Zoom and it installed a backdoor web server.
0 - https://discuss.grapheneos.org/d/16046-google-keyboard-w-net... 1 - https://discuss.privacyguides.net/t/sandboxed-google-play-pr...
Do that + identity check = bans for virus makers are not easily evaded, regardless of where they live.
Given that Google both owns Android/Google Play Store and YouTube: what do you think they would do with the developer information of someone who makes an app that skirts their ad-model for YouTube?
Things like Newpipe seems much more of a target, especially if you want to take legal action. More so than stopping users, this gives Google fat more leverage about what Apps can exist. If they ever want to stop Newpipe a serious lawsuit against whoever signed the APK seems like an effective way to shut down the whole project. Certainly more effective then a constant battle between constraining them and them finding ways to circumvent the constraints.
The "security" wording is the usual corpospeak - you can always trust "security" to mean "the security of our business model, of course, why are you asking?"
It means that Android is no longer suitable for my own private dev projects.
There's only so much you can do as a maintainer of a custom OS like Graphene before its too hard to maintain. I don't think there's enough coming in by way of donations to play catch-up.
Need legislation quick. But I suspect the EU doesn't want side loading either in the grand scheme of surveillance.
Thats the Banks fault then. I complained to mine and they removed the safetynet check / let you skip it.
Also, with this move, Google has made it very clear that they don't want people to have any real control over their machines -- so I'm not inclined to think that using adb to work around the problem will always be possible.
It's fine, though. My hobby projects will continue into the future, just probably without using Android.
https://www.androidpolice.com/use-wireless-adb-android-phone...
(0): https://shizuku.rikka.app/
The fact that there was a temporary workaround didn't change the endgame.
It's just there to boil the frog more slowly and keep you from hopping out of the pot.
It's the same game plan Microsoft used to force users to use an online Microsoft account to log onto their local computer.
Temporary workarounds are not the same thing as publicly abandoning the policy.
Developers, and power users often pre-date these kinds of smartphones.
I think they’re just going to track down a random person in a random country who put their name down in exchange for a modest sum of money. That’s if there’s even a real person at the other end. Do you really think that malware creators will stumble on this?
This has to be about controlling apps that are inconvenient to Google. Those that are used to bypass Google’s control and hits their ad revenue or data collection efforts.
The iPhone 17 is the same price as the Pixel 10
> better
But the iPhone 17 has better hardware features, like UWB, better cameras, and a _far_ faster CPU.
> open source
Only if you install Graphene, and then never install anything that requires Google Play Services, which is basically every commercial app.
A month or so ago I went to NYC, I visited some of the museums.
Although I managed to get some great pictures, framing wise and sharpness wise. The color resolution was absolutely ridiculously bad.
I couldn't figure out a way in that moment to fix the issue, but seriously, the colors were so far off it kinda ruined this phone for me.
My friend had an iphone, we took the same pictures of the same paintings and his photos looked much closer to life than mine. Huge disappointment.
In the iphone its very easy to shoot raw and the camera app has a lot of very good intuitive controls. Not to even begin talking about video.
At some point I think Google did make really good photography phones but it seems to me like they've basically stopped trying to stay ahead of the competition whereas apple is always trying to improve. Thats my impression anyway.
Not my experience at all. Only some banking apps or apps that otherwise hard depend on play services feature like google pay. GrapheneOS offer isolated unprivileged sandboxed Google play services for those.
No longer true with the newest chip that Mediatek cooked up, ARM licensed cores like C1 are catching up rapidly with Apple CPUs (or maybe Apple has hit the limit of their current design philosophy)
I mean, flagship vs flagship idk if one has ever been significantly cheaper, but I've never been in the market for those either. It's very easy to get a higher priced, more interesting, highly specced Android phone. Both iPhones and flagship android phones are way too expensive for what they are capable of compared to any of their own prior generations of themselves, if you ignore tech specs and consider the tangible end-user functionality, but even still.
I've always bought the phone that suits me in the moment, have never budgeted higher than $600CAD, and have simply never been interested in iPhones beyond what used to be nice industrial design. For that, last time I got a brand new Pixel 7 on sale, Pixel 4a, Nexus 5 etc.. and they've all done what I needed and usually came close to matching the fancier versions in some ways in the same year's lineup.
Usually though I have breadth of options to pick from across a range of brands that I can choose between based on whatever the hell I prefer. iPhones are just iPhones, bigger or smaller, more expensive or cheaper, big camera plateau or small, and that's all fine too.
The sideloading aspect for me and a better sense of control is absolutely a component in that preference, and I'll have to consider that going forward, but I'd sooner just dial back my dependence on phones in general than switch to an iPhone.
Too bad there aren’t any other Android phones…
2. I think it's better, I like the UX but that's subjective.
3. Not open source. AOSP is open source. Android is not open source.
The only Android phones that are significantly cheaper than equivalent iPhone tend to come with some kind of compromise (and don’t forget that Apple’s phones start at $600 - the iPhone 16e exists).
The specs that you can't just plug and play are a bit more relevant to look at I'd say
I’m personally fine with it at this point. It’s not ideal and it’s not consumer friendly, but SD cards are slow and failure prone compared to internal storage, and I find that multiple storage volumes introduces management friction (moving apps and content between two locations).
2: yeah okay with that logic "I just subjectively feel that way", there's no point having a conversation
3: Android is short for AOSP. You're probably thinking of things like Google Play or OneUI?
Most android flagships are about the price of iPhones.
> Android is short for AOSP.
This actually made me laugh out loud.
Uh, no. AOSP is a showcase project which currently cannot run on any phones produced on Earth.
Android is the most popular mobile operating system.
AOSP does not include code to run almost any viable hardware and also does not include code necessary to run android applications. Everything that is Google play services is not in AOSP.
Bear in mind Google play services isn't the Google play store. It's basic device functionality, like cellular service and GPS.
https://grapheneos.org/features
>GrapheneOS is a private and secure mobile operating system with great functionality and usability. It starts from the strong baseline of the Android Open Source Project (AOSP) and takes great care to avoid increasing attack surface or hurting the strong security model.
If you would put AOSP on a Pixel, it wouldn't even boot and if you managed to get it to boot, the apps would be unusable.
It is still unbelievable to me that Google is shipping a product which takes 10 seconds to show anything when I search through my phones settings. What are they doing?
>open source
Sure. If you buy the right phone you get some open source components. Of course half the Android companies are trying to funnel you into their proprietary ecosystem as well. The rest just wants you to use Google's proprietary ecosystem.
Ah, I see ol' Google's been shamelessly copying Apple again.
Unrelated but related to embarrassingly-bad search: On my iPhone, I have a Hacker News reader app called Octal. Now when I search the phone itself for "octal" (like I do to launch most apps), sometimes the only result found is... the Octal entry under Settings (where iOS sticks the permission-granting interface for notifications, location, etc.) Can't find the app itself. Just the settings for it.
Then I might as well treat myself with better hardware & ecosystem.
But you'll be reminded quickly how comparatively shit Apple's software is.
Aka the litany of "Oh, yeah, everyone knows that's broken but just deals with it, because there's no way to fix issues on a closed platform other than {wait for Apple}."
android sucks, but it was open
now it just sucks
My pixels haven't done that (yet anyways).
The only thing I can think of that's worse on iOS is that you're forced to use safari or another skin on webkit rather than true alternative browsers. Everything else works better thatn android AFAICT, and integrates amazingly with MacOS.
Tapback emoji choice being uneditable.
There's a lot of little annoyances that on Android can be user-fixed, but on iOS it's just... wait and hope.
I’m always searching for things with unnecessary dots in them, and I’d forgotten about the keyboard options on Android.
Remember when GPS navigation was a $5/month app that was a cellular plan addon?
On M1+ devices it might also need "ad-hoc signing" if the developer hasn't done it (not required for Intel binaries). This is not a true signing, it just inserts a cryptographic checksum into the binary, no actual signing is involved.
The perfect should not be the enemy of the good.
I had been thinking for a long time to switch to Android (GrapheneOS, probably) when my current iPhone 13 dies, but this whole thing with "sideloading" on Android is making me reconsider. If I can't have the freedom I want either way, might as well get longer support, polished animation and better default privacy (though I still need to opt-out of a bunch of stuff).
I haven't heard about this. Source?
I think there has been much _speculation_ around this, but no proof that I am aware of.
So you're just speculating.
Doesn't mean you can predict the future with high certainty.
Source: I have been a happy user of custom AOSPs for years.
Can you do something similar to load unsigned apps on Android?
I, too, love vendor lockin.
It’s utterly bizarre how BBM could have been the iMessage and WhatsApp and who knows what else. But rich out-of-touch people thinking exclusivity is a perk in a commodities market just shows how business savvy and wealth are in reality disconnected from eachother.
For vast majority, Android vs iPhone is not massively different so iMessage availability is a draw for some people.
I doubt they learned their lessons. Apple walked all over them in so many ways and, if memory serves me right, they even mocked Steve Jobs over the iPhone.
Edit: just so I’m clear I’m discussing it from the perspective of early to mid 2000s. iPhone hadn’t yet come out, but iPods were popular. Trillian and Pidgin were dominating the online landscape of software that could support multiple chat protocols - seamless ICQ, AIM, IRC, Yahoo, MSN Messenger, all in one program. If there was a time for RIM to corner the market here it was right then and there because BBM was the real deal, being available on phones and they could have signed agreements with others to bring it to, for example, Nokia and Motorola and whoever else.
But no. They’d rather be arrogant and stupid.
Isn't that just doing their jobs as executives for a competitor?
Though internally, one would hope they were sounding some alarm bells. Though at the time, it wasn't at all obvious that people could get used to doing relatively serious typing on a small (even tiny back then) virtual keyboard.
[0] https://en.wikipedia.org/wiki/BBM_(software)
This does not suggest to me that BBM was somehow positioned for mass adoption. There was no problem for it to solve. It was worse than the existing messaging landscape.
(If I had wanted to send a message to someone else whose only mode of communication was their BlackBerry, a situation that never arose, I would have emailed them. Convenient email was the BlackBerry's entire marketing strategy. Note that this works just as well on smartphones today.)
WhatsApp became popular specifically because it was a multi-platform replacement for BBM.
BBM had little else to offer in terms of apps. It was a corporate ecosystem and good at that part of it.
iMessage also came out after BBM, and did their own device lock in, except iPhones were designed for the many instead of the few, especially beginners to smartphones.
387 more comments available on Hacker News