Hell no, I do not want to help Grandpa avoid anything. I don’t want to be part of Grandpa’s owning appliances at all in the first place. I have way better things to do with the little time we get to share together in this world.
And again, this hypothetical old person is not a child. I don’t “allow” anything in this scenario. And even if I did, and even if I had the time or interest to run IT interference for somebody else, this solution does not scale. For every tech savvy person there are thousands of people who have never read a warning pop-up in full.
Your perception of where the onus is, how much understanding of how computers work or the usefulness of foolproof computing devices is way out of whack. And I get it, it’s easy to lose perspective on this. Average familiarity and all that. But you’re setting up a scenario that works just for you and not for everybody else.
So no, you are wrong, for a whole range of devices, restrictions should be the default. Absolutely. No question. This isn’t even up for debate.
That’s, in fact, not what is being debated, seeing how Google aren’t changing install restrictions at all. The changes are more insidious and extremely bad for entirely different reasons. It is frustrating that this conversation is both being had on the wrong terms for what Google is actually doing AND showing how much even casual dwellers in tech circles misunderstand how UX needs to work to be serviceable at scale.
Can somebody tell me what’s the minimum guaranteed attention span in people reading stuff online so I can crunch down any points that aren’t a binary of “Down with this sort of thing/Up with this sort of thing” to not have people waste my time by knee-jerk assuming my stance without reading what I’m saying? Maybe we need AI summarization more than people say we do.
Also, this is me doing that for Google now. Best I can tell Google isn’t stopping sideloading, they are stopping sideloading of unsigned apps in devices with Android security certifications.
The second caveat is irrelevant, in that uncertified devices presumably don’t get Google services and the Play Store, so outside off-brand Android retro handhelds it doesn’t matter. The first caveat is important, because on paper you can still install stuff from a website or F-Droid or the Samsung store or whatever but those developers will have to leave their info on record.
What you need to do
Complete these two steps:
Verify your identity: Provide information and documentation to confirm your identity as an individual or an organization.
Register your package names: Prove ownership of your apps and register them with your verified identity.
This isn’t the full app certification you need to publish on Play Store, as far as I can tell. In their words
Android developer verification is a new requirement designed to link real-world entities (individuals and organizations) with their Android applications.
This is very bad for a number of reasons. Just not the reasons people are reporting.
Hell no, I do not want to help Grandpa avoid anything. I don’t want to be part of Grandpa’s owning appliances at all in the first place. I have way better things to do with the little time we get to share together in this world.
And again, this hypothetical old person is not a child. I don’t “allow” anything in this scenario. And even if I did, and even if I had the time or interest to run IT interference for somebody else, this solution does not scale. For every tech savvy person there are thousands of people who have never read a warning pop-up in full.
Your perception of where the onus is, how much understanding of how computers work or the usefulness of foolproof computing devices is way out of whack. And I get it, it’s easy to lose perspective on this. Average familiarity and all that. But you’re setting up a scenario that works just for you and not for everybody else.
So no, you are wrong, for a whole range of devices, restrictions should be the default. Absolutely. No question. This isn’t even up for debate.
That’s, in fact, not what is being debated, seeing how Google aren’t changing install restrictions at all. The changes are more insidious and extremely bad for entirely different reasons. It is frustrating that this conversation is both being had on the wrong terms for what Google is actually doing AND showing how much even casual dwellers in tech circles misunderstand how UX needs to work to be serviceable at scale.
then why do you support this thing at all?
restrictions are the default, today and the past few years. but google here wants to make it not a default, but the only option anyone can have.
y… yes they do?? that’s exactly what they are doing!
I don’t? I’ve said multiple times that I don’t.
Can somebody tell me what’s the minimum guaranteed attention span in people reading stuff online so I can crunch down any points that aren’t a binary of “Down with this sort of thing/Up with this sort of thing” to not have people waste my time by knee-jerk assuming my stance without reading what I’m saying? Maybe we need AI summarization more than people say we do.
Also, this is me doing that for Google now. Best I can tell Google isn’t stopping sideloading, they are stopping sideloading of unsigned apps in devices with Android security certifications.
The second caveat is irrelevant, in that uncertified devices presumably don’t get Google services and the Play Store, so outside off-brand Android retro handhelds it doesn’t matter. The first caveat is important, because on paper you can still install stuff from a website or F-Droid or the Samsung store or whatever but those developers will have to leave their info on record.
This isn’t the full app certification you need to publish on Play Store, as far as I can tell. In their words
This is very bad for a number of reasons. Just not the reasons people are reporting.