I don’t know about most painful, but my dad bought a phone many months ago and last week, he wanted to know how to turn on the flashlight on it. I was ready to edit the notification dropdown or give a five step explainer or whatever.
Turns out, nope, you just pull down the notification bar and there’s a pretty obvious flashlight button right there. The problem is, you see, he did not know you could drag down the notification bar. There were dozens of notifications there.
I really cannot blame him either. I don’t know what UX designer came up with just putting a bar at the top and expecting users to know that you can drag on it. But yeah, still, ouch.
I don’t know about most painful, but my dad bought a phone many months ago and last week, he wanted to know how to turn on the flashlight on it. I was ready to edit the notification dropdown or give a five step explainer or whatever.
Turns out, nope, you just pull down the notification bar and there’s a pretty obvious flashlight button right there. The problem is, you see, he did not know you could drag down the notification bar. There were dozens of notifications there.
I really cannot blame him either. I don’t know what UX designer came up with just putting a bar at the top and expecting users to know that you can drag on it. But yeah, still, ouch.
You want affordances? Get out of here you filthy leper!
I mean, give people a damn clue at least? No? Hm.
I remember when “make it obvious what can be clicked on and what can’t” was a basic design principle. That one got tossed a long time ago.