User Experience Design: A human interface to guess user behavior

The user-friendly interface should guess the behavior of the user, just like a good secretary should guess the boss's mentality. Say is guessing, is actually based on a large number of user behavior data summed up the solution.

1. guessing (actually summarizing) the behavior of the user, allowing for quick operation

Chrome the tab bar vs Firefox

My main reason for using Chrome as the default browser is that two are related to its tab bar: One is that the tab bar is more in line with the Fittz law at the top, and the other is that Chrome closes multiple tabs in a very elegant way. When you start off from the middle of a row of labels, the left and Right tabs automatically change the width so that the close button jumps to where the mouse is. This is very helpful for users who often open dozens of of tabs.

Chrome's design is based on "The user closes a tab , and it's possible that he has other tabs to turn off " The user's behavior guesses.

In Firefox, close multiple tab becomes very painful, in the case of more labels, each close requires a small move of the mouse a distance, this fine muscle movement is very easy to let the user become tired.

Foursquare plus friends.

Every time Agree/disagree with a friend application, the application to the left slide disappeared, while the bottom of the friend application to slide up, just to agree/disagree button to the user under the mouse, just click once in situ can be completed operation again, save the time to move the mouse, cool!

Twitter, by contrast, follow multiple follower operations on Twitter.

Foursqaure's design is based on the " user approval of a friend application, it is likely that he will continue to approve the next friend application " This is the user's behavior speculation.

Of course, the above comparisons depend on understanding the user's operating habits. For example, how large a percentage of users will be able to confirm most of their friends ' requests? For me this through all 4sq Friend request user, this is very convenient, but for @yuancheng this has the choice passes the person, the Foursquare function may cause the misoperation, especially when the network speed is slow, this Ajax effect may not be fluent, Lead to a delayed hit. Therefore, the product design has its contextual nature. But from another point of view, as long as it can provide convenient unfriend function, I think the occasional misoperation is acceptable.

Search engine Open the home page will automatically focus on the input box, submit button response return.

This example basically all search engines are based on " users come to me here is the most likely to enter keywords to search " to design. But Google's fade interface to this speculation to play to the extreme, I believe that Google dares to do so, there is a large number of data to support, and also because Google is well-known enough, most users know that in Google's home page in fact there are other content.

2. Guess the behavior of the user, introduce special flow.

When a user does something over and over again, the program should have enough intelligence (or the product designer has enough to think about it) to guess what the user wants to do.

Example:

QQ mailbox inside a short time several times click on the "Receive" button (seems to be 3 times), you can see a dialog box on the right. Imagine that the user is waiting to receive a message, repeatedly place the "receive" button, and the dialog box appears just right.

By contrast, I hope the school can guess:

The Select Group dialog box appears each time you confirm a friend request, but the dialog box is optional in function. When you need to accept a lot of friends to apply, the operation is quite cumbersome. In fact, if you do not create any new groupings when users add friends several times, consider adding a "Do not show this dialog box" option.

Summarize:

The most lazy product design is to ask the user how to do (or even in the form of a JavaScript dialog box), each guessing, or according to the data, or according to the product designer's intuition, and the results should be based on user feedback to adjust. For example, the above examples of QQ mailbox cases, initially there are two side by side link "reporting problem" and "I know", presumably this "I know" has become a bit confusing in this scenario, so the design later puts the problem of reporting into context, and "I Know" to be independent, as "no longer shown" Another meaning.

I often use the user software scenario than to do the relationship between the boss and the secretary, how to be a good secretary? Please look at the art of serving the head . is the software into a gentle and thoughtful little secretary, or a simple rude bodyguard, whether the understanding of the key: