Comment by bombcar 16 hours ago
The biggest thing when teaching someone to use an iPhone - do NOT assume they need to know all the things YOU know how to do.
Instead, ask them what they want to be able to do, and show just that. The temptation is to show too many things.
Also, you can still configure an iPhone with no passcode, which is honestly the way to go, probably.
You can opt to not add a passcode, but the option to skip on setup is hidden, and people generally aren't going to go back to the settings to remove it once it's added. It's a dark pattern I kind of get, but it's still not ideal, especially for a market segment like the elderly.
oh come on, you just need to buy a Mac so you can use one of the management toolkits to prevent that from happening. it Just Works!
_deeply_ /s of course
(and I say this as someone who is basically 100% a Mac user who admins Linux for a living... Apple makes a lot of stupid / frustrating decisions that I don't agree with, but I still prefer it over the alternatives)
That's why I get that the default should be a passcode. Same reason Windows Update probably should automatically update. We live in a problematic world and these options are the least bad.
My Grandma's solution to this problem is to not bring her phone with her when going to public places, and that's probably the right call if you can swing it.
It's one thing to be a default. It's another thing entirely to employ dark patterns and annoyances to coerce/trick the user into doing something they don't want to. The user should ultimately be in charge, and the machine should get out of the user's way.
> stealing them and emptying their bank accounts.
Which bank allows you to empty someone's bank account if you find yourself with an unlocked device in your hand?? If was a criminal I'd be waiting outside their branch and snatching people's phones out of their hands right there, so I'm pretty confident that's not a real scenario.
Had the same terrible experience. Opting out from the passcode is only possible for people who know that words can also be a button. It’s a dark pattern urging you into a passcode, and another dark pattern for using numbers and letters in said passcode. And it happens every stupid iOS update. I used to tell my parents: please make these updates! Now I say: please don’t. Honestly, it was years ago when iOS updates made the device better. Now it is always worse. Not a single feature in the last 5 years was added but you have to update so often.
I switched from Android to iOS and I must say: both UX are completely enshittified. For me (IT person) not a problem, but for elderly rare occasion users it is absolutely terrible.
On one hand you can now talk to ChatGPT in natural voice, but figuring out how to make a cell phone call on iOS on your own: impossible (spoiler: WhatsApp calls are also in the phone app‘s call list).
Sure, you could buy them a dumb phone, but for online banking etc you do need a smartphone. Good luck tackling the App Store if you only use it once a year….
Encryption by default is always scary, especially when it's very, very strong. If you forget the key, your data is gone forever. I don't think most people in the world need that level of security; those who do already know who they are. Everyone else may be willing to accept the risk that someone unauthorised may gain access, if it means reducing the risk of losing access themsleves.
(I have some very sad stories on this topic.)
What's the point? If the encryption is weak enough to be broken by the average owner it's weak enough to be broken by anyone.
I think this is primarily a UX issue, encryption should be strong but users should be "forced" to create backups of their keys, with options to store the full key in a safe place themselves, or to distribute parts of their key to trusted people using Shamir's secret sharing.
In other words don't weaken encryption, allow users to weaken their key storage after informing them about the trade-offs, if they so desire.
Regarding passcodes, for Android phones I've learned to avoid under-display fingerprint readers - they're okay for you and me but just hard enough to use that some people never converge on the right angle/pressure/duration combination to get them to work reliably. Several of my relatives have gone back to typing in their password (or to no password) after moving from a device with a back-of-phone to an under-display reader.
Isn't that an acknowledgement that the UX is essentially worse than a PC?
On a PC, are you inclined to show your mom how the terminal works or to install Xcode? You don't because these components are not forced onto you, or may not even be installed. They are out of sight until you ask for them.
OTOH on the iPhone, instead of starting with barebones functionality and allowing you to enable the parts that are relevant to you, building your own UX, they try to make you fully buy into the Apple ecosystem. This is essentially the result of the "batteries included" design philosophy of the iPhone (which is good!) when combined with Apple aggressive marketing policies.
Mostly agree, but also - if someone's genuinely new to phones, they might not actually know what's possible that they might want to do. You have to be a little bit opinionated on how to use the phone, at least until they know enough to have opinions of their own.
Oh yes, you can, then an update is installed overnight and now they're presented with a non-dismissable screen that forces them to add it.
Literally happened this month with iOS 26 on my family iPad. Suddenly it had a passcode and I knew exactly why.