Concise definition

The definition I derive is that simplicity is the use of minimal elements to effectively meet functional requirements. The reason for the definition is based on the following reasons:

We often talk about simplicity, what is simplicity? If the basic concept is not clear, it can not be implemented. What are the criteria for evaluating simplicity? For example, I have text on my blog without the title, text and links are changed to 5th black font good? More concise, even the font and color values are saved, but the effect is not good. Windows-phone7 use minimalist design, how to evaluate it? So at least one factor is needed to measure whether simplicity is reasonable. What is the premise of simplicity? The use of any method or principle is conditional. function

Simplicity is relative to the need to determine whether an element (such as vision and sound) exists in an interface A/b scenario. The existence of this element only affects the form of the interface design, does not affect the function, in the premise of satisfying the basic functions of the discussion concise.

Effective and concise

Effective is an adjective used to describe a program that satisfies a function, i.e. usability. The form of usability four elements: simplicity, memory, predictability and visibility, what is the relationship between simplicity and usability? The concept of screen complexity is referenced in the discussion of "harmonious interface: Interactive http://www.aliyun.com/zixun/aggregation/8911.html" > Design basics:

This formula can quantify the complexity of the interface, complexity and simplicity is the opposite concept, can be understood as simplicity, after simplifying the formula can be understood as:

C. Interface simplicity N. Total number of elements in the interface number of M. Component classifications the frequency of the use of N. N Components used

The following conclusions can be drawn:

when N is uncertain, as n is proportional to C, the number of elements n is less and the complexity C is lower. When n is constant, the C value is best when the best combination of M and P is obtained. N=n (1) XP (1) +n (2) XP (2) +n (3) XP (3) ... n (m) XP (M), n equals the sum of the number of times each component is used. When n is constant, the interface is more complex when the number of component m is too high. The usage of each component is low, it is unfavorable to user's memory to the interface, usability is reduced. When n is constant, such as M over an hour, the interface is more concise. Component usage is high, but there is no distinction between elements, there is no grouping of elements, the interface looks stiff and usability is reduced.

So, the simplicity of being low or too high is not conducive to usability, and then you can push the definition of the opening opening, so Windows Phone 7 uses a minimalist design that causes less element components to be sorted and more usable.

Determine a reasonable m value based on the N value. When the n value is larger, the M value is not equal, because the component has too many classifications, the time to learn each component is certain, but it will make the user's memory burden increase. (I presume, to be verified)

When n is constant, the average number of times a component is used, as shown in Figure 2:1 above, shows that each component is used more efficiently and more highly available. (I presume, to be verified)

Source: http://daichuanqing.com/index.php/archives/1436