"User Experience elements" clarifies the layer on which you can't see the real feelings in the UI prototype design.

"User Experience elements" clarifies the layer that you cannot see

Beautiful Life of the sun and fire god (http://blog.csdn.net/opengl_es)

This article follows the "signature-non-commercial use-consistency" creation public agreement

Reprinted please keep this sentence: Sun huoshen's beautiful life-this blog focuses on Agile development and mobile and IOT device research: IOS, Android, HTML5, Arduino, pcduino, otherwise, this blog post is rejected or reprinted. Thank you for your cooperation.

Please do not open axure before using 2B pencil skillfully. the essentials in this article are as follows and PS combination:

Performance layer: when the other four layers are basically done, beautify the design, layout from the aesthetic point of view, and use colors. This layer is basically included in the final product, therefore, the most things are included, but it cannot be achieved by the artist PS alone;

Photoshop can make it more beautiful; aesthetics is part of the user experience;

Framework layer: the general interface flow and interface elements are used to present specific data and interact with users. This layer is not very beautiful, basically what data should be presented, what kind of user interaction requests should be received, and so on,

This layer includes and reflects the data types and user requests, as well as various user-system interactions between requests and data, the user experience is embodied, structured, streamlined, and implemented.

It is displayed in an intuitive way, including interface elements, data organization, interactive flow, and response result trend.

Axure presents an interactive process with relatively real data and interface elements as well as jump elements. interaction is also an important part of user experience;

Structural layer: many aspects of the framework layer are derived from this layer. If there is no such layer of content, you will find that you want to use axure to draw clear things, which is very difficult! I don't know where to start. Even if I start, it's also very messy and misplaced. So,

It can be described as follows: the framework layer is the drive body, and the structure layer is the soul. Only the drive body with the soul is smart, angry, and reasonable. This layer is more important to consider these soul things.

Which functions are used by the user, which data needs to be processed, and which data needs to be presented? Of course, this is only the case. Instead of more specific interaction interface elements and data presentation interface elements, however, the interaction process must be clear and visible.

This is feasible as long as you can deduce it in a realistic way of thinking, smoothly and reasonably. Otherwise, further consideration is required. As a person is doing something, this is what the framework layer sees.

We will find that this person is organized to do things. This level of organization is something that needs to be solved by the structural layer. As to whether the posture and movements are beautiful, this layer should not be refined.

The omnigraffle and Visio tools can draw flowcharts. Flowcharts are the logical thinking processes of Business Flow Transition relationships. They are relatively abstract, but they are indeed carrying the presentation and response capabilities of applications, which are invisible at one layer, OK

In the user experience section, for example, you need to click several layers on the same information, flip several pages to find the information, and enter a large amount of information that can be automatically generated and provided, at least the optional data, or simply make

The user inputs the necessary content, which determines the subsequent development. Although the content cannot be seen, the results will be displayed when the framework layer is guided, although it can only be felt, see

No ......

Scope layer: This layer can be called the boundary definition of a requirement. Many projects often fail because there is no boundary requirement. Users repeatedly propose different new requirements and make changes to the original requirements, so they cannot figure out what they need. At this time

The boundary definition of requirements is very important. Currently, only these tasks can be completed, and new ones can be submitted. It can be updated or changed in the next version, but it can only be done within some specific scope. In short, it defines the Model

The goals of the subsequent work are those defined requirements, which are also identified as the most important and urgent after a series of discussions and studies. In the actual development process, you also need to follow

Capacity, so that the development work can be quantified and delivered on time. In addition, in scrum agile development, each sprint also defines the scope or complexity of the needs to be completed, this is very important.

The tools used at this layer may be the brain, or tools like xmind can be useful.

Strategy layer: This layer, of course, cannot be separated from the considerations of the investors. First, whether the demand exists, the extensiveness of the user group, and most importantly, whether the profit points are reasonable and generous, whether the environment is ready

Next, basically everyone is holding an Android mobile phone, while the iPhone is relatively small, but it is indeed a high-end group, so this layer needs to be considered. If you do not consider this, no one will do that in earlier years.

It's silly to buy an Android mobile phone for everyone, and then develop an app to ask them to download it. This is a joke, but it does not reveal the importance of the real environment; for example, the Java language was invented at the beginning.

In the environment, it was impossible to achieve its initial goal. Later, it became famous for the Web. Now on Android, Java finally achieved its initial design goal, developing applications on set-top boxes and portable devices. In short, Strategy

Layer, determines the direction. If the direction is wrong, it is also wrong to do more later, or sometimes it will succeed, it is not an accident, but the following layers are being executed, the strategic layer is constantly corrected, which is still a problem at the strategic layer.

It is not for other layers, but you will see implementation in other layers, and it will not change this layer; but it will indeed exist, with feedback from each layer, the strategy layer is constantly revised to make other layers feasible and reasonable.

"User Experience elements" clarifies the layer on which you can't see the real feelings in the UI prototype design.