Have you ever been forced to recite an obscure poem, but confused it? Guo Guowei, a master of Chinese studies, used the phrase "separating and not separating" to distinguish between poetry and CI in the world:
"Few peaks and poor, Shanglio dusk Rain", although the rhyme high absolute, but as the smoke and mirrors, the end of a layer.
"Born years dissatisfied hundred, often bosom worry." Day short bitter night long, why not candle swim ", write feeling so, square is not separated.
Take Chrysanthemum to the east fence, leisurely see Nanshan. Mountain gas rixi Good, birds and also ", scenery so, side is not separated."
The word affectation, more use of the word (such as "Guihua" Generation ""), is separated; the language is at present, feel real, is not separated, can "state all out", better convey the author wants to express information.
So how do we differentiate between Web sites and software? The key is the message is not very good to convey to the user. The "separated" web site is like this:
The failure of the user experience will hurt product value, and the smooth user experience can better display the value of products, to avoid users to guess, to think, to wait, to confusion. So we need to:
I want to know what users want to do first.
Unless you are a professional, no one will use your product to study your website or software for how "good" it is. What users care most about is how efficient the product is, how thoughtful the service is, and how much information it can help them get.
If the value you provide cannot repay the energy or money they put into it, it will be a cup of ⊙o⊙!
Dazzle, cool interactive experience or visual effects can attract eyeballs, but in the most commonly used functions, if the information is too circuitous, not straightforward, it will reduce the user's use efficiency. In most cases, it is best not to "design" for design, to ensure that the interactive process is simple and smooth, consistent with user habits.
First time let the user realize
To understand what the user is going to do, we should be more comfortable, to avoid "separated" the presentation of information.
There are a lot of design tips here, and here are a few:
1. Use animation only if necessary
Too much whitewash will not only reduce the response speed, but also damage the presentation of information and interference users.
When the page layout changes, using the appropriate animations can make the change seem less abrupt, explaining to the user what just happened and the state of the change. For example, Apple's time machine will have a stacked animation effect when switching to a document preview at different times to better present a logical relationship.
2. Presentation information with severity
Let the characteristics of the product and the user's operating process at a glance.
The primary and secondary weight of the information can be compared to the ratio, color, voice, etc. to ensure that users will not be distracted by the messy information. For example, Apple MobileMe design, the giant icon occupies most of the screen, creating the strongest brand infection at the same time to identify where the user is, the login box, Product introduction link button accounted for the second, login mode description, related page links weakest, Primary and secondary relationship with the user came to the page → most commonly used operations (login and viewing function) → Get supplemental information in descending order.
3. Immediate operation Feedback
There's nothing more straightforward than putting your hands up on a table--if you have to know there's plenty of room for the table.
In a Web page that mimics desktop interaction, the drag-and-drop of a particular module or content needs to be fed by interesting instantaneous feedback: the hover state of the mouse, the placement of the accepted state, the position being rejected, the drag dynamics, and so on, to let the user know that it is a "table to put For example, Google's image search, when you drag the picture to the page, the search box will wave to you.
4. Where the output is entered
In situ modification is to not toss the user.
For some common editing functions, no need to open redundant pages, and can be directly in situ modification. For example, QQ signature status, online status these help users to better display their own functions, allowing direct, convenient and real-time modification on the main panel.
5. Talk to People
Don't try to tell users how professional you are, they simply need to do what they want with the functionality you provide.
Too many terms, obscure words can easily cause anxiety. Especially when the error is prompted, a long string of slashing, irrelevant technical explanations will make the viewer's pear very big. So in the design at the same time we also need to do more user research, more understanding of their real needs, how to clearly say, to avoid "language impassability." For example, when a Chrome browser crashes, it conveys 3 messages: telling the crash, explaining the reason (concise, not crackling a bunch of terms), and giving the solution.
Resources:
1. "Human ci" Wang Guowei
2. Designing WEB Interfaces Bill Scott & Theresa Neil
3. GUI Bloopers Jeff Johnson
4. "The Information Design Handbook" Jenn+ken visocky O ' Grady
(This article is from the Tencent CDC Blog, reprint, please specify the source)