I doubt most people have a second phone on hand, ready and able to capture actual screen shots when your phone is preventing screenhots.
However, my idea happens to hit a very new limitation: for some reason, "privacy filters" are suddenly a thing. New phones have them built-in as some new magic display function, and for everyone else, there's this mad marketing push to get people to buy and use privacy foils in place of glass/foil screen protectors.
IDK what's up with those. Since when "shoulder surfing" with smartphones is a real problem, and why do marketers and product designers bet there's so much latent demand for it?
The only thing I could think of is if you want to browse TikTok or Instagram in public and don't want people seeing the weird shit that's on your algorithm, but even then, that's kinda weird.
Very frustrating.
I think I must have changed my password several times thinking I just copied it wrong or it had special characters that weren't allowed, but nope, the truth was somehow stupider than that.
The "useful device" is a laptop.
This feeling usually hits me at airports, with my shoes off and water confiscated. The terrorists won.
In my view that's a feature, not a bug. I refuse to use services that break under "reasonable" conditions (non-chrome, ublock, no widevine, rooted, etc, etc).
Banks are the canonical example - changing one is a huge hurdle, with consequences that can drag on for years. One by one, they're all ditching their websites (if they had one in the first place) in favor of apps. Even those with full-featured websites increasingly force you to use their app as the second factor to log in, confirm transactions, even confirm viewing some data. Some offer physical tokens, most don't advertise that, and it's only a matter of time before they convince regulators that Attested Phones are Safer and Everyone Has One, and that option will disappear. And because they want their app to be the second factor, they can argue it needs to be secure, creating demand for remote attestation, and boom - there goes your option to work around any other bullshit limitation they throw at you.
The day has only 24 hours, I don't want to spend them clearing bushes by walking off the beaten path wrt. every single important service - payment services, government services, IM services, ${whatever bullshit SaaS app I need right now because you're using it for the thing you just shared with me, and I need to view that}, etc. So I submit. So does everyone.
It's why I put blame on platforms here. Features protecting the device from the user should not be built in the first place - they always start justified by some legitimate security reason, and always end up broadly abused to serve business reasons.
Yes, this. Payment apps, government apps, IM communications.
The other day I almost rooted my phone in anger trying to get around this, before pausing and realizing that this would only cause even more problems with those apps, thanks to remote attestation "features".
My favorite recent case, I almost locked myself out of mobile government services when changing phones recently[0], and it would've made for a stellar bug report showing when "fail safe" design can easily become "fail deadly"[1], with UI view of access and invalidation history clearly showing the timeline of a problem... if only I could take a screenshot of it. But I can't, because "much sekhurity".
--
[0] - Well, it's not really that big of a deal. With government services, there's always a way back. Might involve walking to a local civil affairs office or, worst case, a police station or a notary, but there is a way back. Big cloud services, on the other hand...
[1] - Invalidating a certificate prior to issuing a new one sounds like a good security idea, but in the real world fails critically if the two operations aren't an atomic group. In my case, issuing a new certificate failed, and I ended up walking half a day with old one invalidated and not even knowing it.