LukasMathis

(Yeah, I realize that using the back button to invoke the application's back function would cause its own set of issues. It's a case where the same button needs to do two different things based on the user's current mindset, which the phone obviously won't know about.)

The other situation you describe (you have a set of applications on a screen far away from the first home screen, and want to launch many of them at the same time) seems uncommon. It's typically bad to have a UI that makes the common case worse in order to make an uncommon case better.

Note that while you're using it, you never accidentally hold your phone with a finger covering your screen. That's because you're looking at the screen. You know where it is. It's bright. It's easy to see its edges. It's the focus of your attention. The bezel around the screen, on the other hand, is not, but merely touching it in the wrong place will cause your phone to do unexpected things.

I'll talk to my publisher to see if we can get these problems fixed.

By the way, I'm not suggesting a windowed UI like on a desktop OS. Rather, I'd like to see simple tiling, where two apps each occupy half the screen.

In other cases (e.g. writing a cover letter or a job application while looking up information about the company on their website), you constantly refer to two different apps, so it makes sense to allow both to exist on the same screen.

There are valid use cases for both behaviors.

The problem with shipping broken features is that there is no pressure to fix them. It's much easier to add new features than to fix existing features. Every time there's an update to Android, there's a huge list of neat new things in that release. On the other hand, I've never seen a list of things that didn't work quite well in earlier versions or were a bit janky or a bit confusing or inconsistent or user-unfriendly or complicated, but are now fixed.

Google tries to improve Android by constantly adding new stuff. That's exciting to people like us, but it will never turn Android into something that is as consistent and polished as iOS. The things that bothered me in Android 1.6 are still mostly there in 2.2.

The word "random" has more than one meaning. I'm using it in the colloquial sense of lacking context or being unexpected. I obviously don't mean that there is a random number generator switching up the position of the entries. Instead, I mean that to the user, the order is unpredictable or unexpected.

As for the rest of your comment, I would like to remind you that you are arguing for a user interface that replaces a benign default action with a destructive default action. It is, of course, possible that I am the only person who was affected by this. It's just not very likely. Simply asserting—without evidence—that most people won't encounter the problem is not a useful response when somebody points out a problem.

And again, I very much doubt that buying the book is the most commonly used action in that list, since, as I've pointed out, you can't actually see the price of the book when you're in that menu. Again, I acknowledge that I might theoretically be in the minority, but I tend to not buy things when I don't know how much they cost, and I suspect that most people behave similarly.

Even assuming that most people wanted to buy the book when they opened a book sample's menu (which is unlikely, since you can't even see the book's price in that menu), this does not warrant changing the default selection from a non-destructive, repeatedly used action (for every other document type) to a "destructive" action (for book samples).

You just don't randomly change the order of menu items when people expect to see the same order, and you most certainly don't change the default action from something that is used often and is harmless to something that is potentially harmful.

>"The ONLY solution to the problem of accidentally order would be to require users to go through a multi-step process of confirming the order"

This is a false dichotomy. The choice is not between "make ordering the default action" and "make it absolutely impossible that people will ever order a book by accident." You can vastly improve the situation without solving every edge case.

The solution is simple: don't make buying the book the default action. If people have to consciously switch to a "buy book" menu entry, accidental book orders would very likely be cut down to a fraction of what they are now.

>"User experience, of which UI design is just one part, is much more important"

I don't see how the distinction is relevant in this context. Are you suggesting that accidentally ordering a book is a good user experience? :-)

Writing blog posts like these is a balancing act. On the one hand, I want to keep it short and stick to the point I'm making. The fact that you can get a refund is not directly related to the specific UI problem I'm describing, just like the "undo" feature in a desktop application isn't directly related to, say, mislabeled menu entries.

On the other hand, I try to write defensively. If an article is read by hundreds or thousands of people, there will inevitable be some people who feel that something they consider important was not included. I try to anticipate the most obvious criticisms or questions, and explicitly mention them preventively. But if I include all of them, the text will eventually become unreadable. I'm also writing for an audience of UI designers, who generally realize that I'm merely pointing out specific UI flaws, rather than making larger points about the products or companies I use as examples.

I probably missed the mark by not pointing out the fact that it's possible to get refunds, but I think it's not as obvious as you imply.

I'm not saying that Amazon is somehow trying to steal money from people (I rather like Amazon). I also didn't write a general critique of the Kindle's UI (which is usually quite well done). Instead, I merely pointed out a specific flaw with its UI. You can call this "whining", but I'm a UI designer, so being whiny about this stuff is kind of in my job description :-)

It's true that you can get a refund, but that doesn't make the problem go away. It means that the user can fix the problem once it has occurred. The experience is unpleasant regardless of whether the user can fix it afterwards. Preventing the problem from occurring is better than allowing users to fix it once it has occurred.

In my particular case, though, I was unable to fix it on my own. As soon as I realized that I had selected the wrong option, I hit "Home", hoping that it would cancel the action. It didn't cancel the action, but it did prevent me from seeing the order confirmation screen, which would have allowed me to cancel the order. Obviously, a quick message to Amazon fixed the problem regardless, but the point is that all of this should not have been necessary. It could have been avoided if the Kindle had simply selected the same default action for all types of documents.

The article is about the iPhone's user interface, not about the backend; local notifications have nothing to do with the user interface. And I simply assumed that everyone who has used an iPhone knows that the notification UI is very basic; you mostly get modal alert boxes, which are very easy to accidentally discard.