Wednesday, December 17, 2014

Apple UI Fail

Interface Design

I used to build software at Apple.  I was once a preeminent user interface designer, before they called it either Human Interface (as if there are other kinds of users) or User Experience (as if you get to control the experience some other way than through the interface).  Anyway, I notice more and more Total Fails in Apple software, and I've decided to start blogging about it, for no particular reason other than hoping to help the current/next generation of UI designers to actually think about some of this stuff.  It's not that hard.  So this is a continuing series, now that this is my second post on the subject.  Lots more to come, especially if I get any reinforcement from blog readers.

Today's Fail

This is obviously Safari.  I restarted after having to install Flash yet-again, and because the browsers are too lame to load plug-ins without restarting them, I had to restart all my browsers. And yes, of course I use Chrome and real browsers, but I also use Safari.  I choose "Reopen All Windows From Last Session", a menu command that wouldn't be there if the program were stable or smart, but there it is, and I use it all the time.

One of the pages I had open was evidently the result of having submitted a form, hence this dialog, but (and here's the Fail) THERE'S NO WAY FOR ME TO KNOW WHICH ONE. The dialog has no useful information in it, like the URL it is attempting to visit, or what the form might have been about.  Was it a purchase?  Or was it just a weather site where I had entered my zip code?  I don't know, and I can't tell.

Luckily I know enough about this stuff to know that it doesn't matter, because anything that I might worry about (repeating a transaction on an e-commerce site) will have lost authentication and sessionID and therefore it's very unlikely I will get in any trouble by clicking Send.  And yet I am slightly uneasy anyway, even as an expert user.

1 comment:

Rocketpilot said...

I've actually bought an item in an e-commerce store twice through exactly that mechanism! No idea how the session survived, but very troubling.