Earlier quoted context omitted.
Even after Google puts this crap in place, you can still uplodad your own apps to your own Android devices, using ADB. Doing the same for iOS, using Xcode, costs you USD 100 or more (depending on country) per year . I'm in no way defending Google here, just pointing out you're going from bad to worse and think it's a good thing.
This is not true, running your code on your phone with Xcode has always been free.
Your phone is about to stop being yours
421–430 of 927 posts
Re: Your phone is about to stop being yours
#422Earlier quoted context omitted.
>free You forgot to factor in the cost of a Mac.
You don't need a computer to develop Android apps?
Re: Your phone is about to stop being yours
#423Re: Your phone is about to stop being yours
#424Earlier quoted context omitted.
Sandboxing and permissions provide a different type of security than application signatures. Sandboxing can limit app capabilities, but it doesn't change the fact that you can accidentally grant a malicious application permissions. Application signatures and developer identification bring a different kind of application security. It provides the security of societal legal systems and legal ramifications for malicious…
> but it doesn't change the fact that you can accidentally grant a malicious application permissions Do you also support the nanny states that decide how you should be parenting your children? (The age verification etc.)
Please don't do that here. https://news.ycombinator.com/newsguidelines.html
Re: Your phone is about to stop being yours
#425Re: Your phone is about to stop being yours
#426Earlier quoted context omitted.
Is it really going to have ecosystem effects? Surely the small portion of power-users who are bothering to intentionally sideload apps can click a couple of buttons. Or just load via ADB and avoid the entire thing. The entire point here is to prevent scam actors from using a false sense of urgency to defraud people. That is a serious vulnerability that needs to be addressed somehow , and I think this is a good compro…
> The entire point here is to prevent scam actors from using a false sense of urgency to defraud people. That is a serious vulnerability that needs to be addressed somehow Does it, and if it does, does it need to be addressed by an OS vendor creating a mechanism to ban developers for most users? I'm not convinced of the former, and I'm certain the latter is bad. I predict within ten years, we will see this used again…
> we will see this used against something that is not malware.
See what exactly used against something that is not malware? The Play Store already has requirements other than "don't be malware". If you're talking about the sideloading requirements, all of these requirements apply to every app, not just malware.
Re: Your phone is about to stop being yours
#427Earlier quoted context omitted.
They really aren't. The number of apps requiring Play Integrity grows every day, my own bank's app hasn't worked in years and I've long given up on it, I just use it on a second stock device now. And Google has an answer to the "just install the APK from somewhere else" workaround, too. Many apps now integrate a check that prevents them from running if they're not properly linked to the Play Store.
Are banking apps much more useful than banking websites, anyway?
Re: Your phone is about to stop being yours
#428Earlier quoted context omitted.
You deliberately took the second quote out of context, in order to (attempt to) refute it. Here's the quote, with context: > Starting September 2026, a silent update, nonconsensually pushed by Google, will block every Android app whose developer hasn't registered with Google, signed their contract, paid up, and handed over government ID. Every app and every device, worldwide, with no opt-out. That is not false, it's…
??? We literally quoted the exact same text. The plan does not outline what that quote does. You only have to do all of the things the quote claims you do in one of the three possible deployment flows. In "advanced flow" you don't have to do any of them.
Re: Your phone is about to stop being yours
#429Earlier quoted context omitted.
nah it was considered more open for users.
This is the initial press release for the Open Handset Alliance, the collaborators for the creation of Android: https://web.archive.org/web/20260420021444/https://www.openh... Nowhere is their goal to allow users complete control of their device. Android was built as an open-OS for the mobile device industry, not end-users. Android might have been considered more open than other mobile OSes by users, but it was never…
The fact that having root access is not the default supports that. Without root we're just "consumers" and that's how they see us. There's a lot of discussion about the security model of Android and how root is bad. But we've come to the point to argue that having root access is not only less secure but that we don't need root at all. A lot of replies, even on HN, are like:
> Why would you even need root access? What is it you're trying to accomplish?
That's a much bigger security smokescreen than the one in TFA. Sure, having root may be dangerous, especially if you don't know what you're doing, but it's still a choice. Having no phone or doing banking IRL or not downloading apps from the Play Store you haven't heard of before would also be more secure. But these 3 options don't align to the financial gain the consumers would bring to the providers. The consumers having no root, on the other hand, benefits the providers.