The "User Experience elements" clarifies the layer on which the user experience is really invisible in the UI prototype design. The "User Experience elements" ui

The "User Experience elements" clarifies the layer on which the user experience is really invisible in the UI prototype design. The "User Experience elements" ui

"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:

Presentation Layer:

In the case that the other four layers are basically done, beautify the design, and deploy and use colors from an aesthetic point of view. This layer is basically included in the final product, so it contains the most things, however, 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 content, and more importantly, this type of data, user requests, and various user experience between user and system interaction are embodied, structured, streamlined, and instantiated, including interface elements, data organization, interaction 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:

A lot of things on the framework layer come from here. If there is no content on this layer, 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. Therefore, 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 concerned with these soul things, specifically to which features should be used for users, which data needs to be processed, and which data should be presented, instead of more specific interaction interface elements and data presentation interface elements, the interaction process must be clearly visible, as long as you can deduce it in a realistic way of thinking, smooth and reasonable, this is feasible. Otherwise, further consideration is required. As a person is doing something, this is what the framework layer sees. If you think about it, you will find that this person is organized to do things. This organization is what the structural layer needs to solve, 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, the user experience that can be felt. For example, if you have the same information, you need to click several layers, turn 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 is simplified, and only the necessary content is input by the user. This determines the future development. Although it cannot be seen, after the content is determined, it guides the framework layer, it will be seen the result of its role, although it can only feel it, but it cannot be seen ......

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 mentioned. 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 scope and the following work objectives are the defined requirements, these needs are also identified as the most important and urgent after a series of discussions and studies. In the actual development process, we also need to follow the content defined by the scope layer so that the development work can be quantified and delivered on time. In addition, in the agile development of Scrum, each sprint also defines the scope or complexity of requirements to be completed this time, which is very important.

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

Strategy layer:

This layer is of course inseparable from the considerations of the investors. The first is whether the demand actually exists, the extensiveness of user groups, and the most important thing is whether the profit points are reasonable and generous, whether the environment is ready, just as now, basically everyone is holding an Android phone, while the iPhone is relatively small, but it is indeed a high-end group, so this layer needs to be considered, if you don't take this into consideration, no one will be stupid in the early years. They will buy an Android mobile phone for everyone and then develop an application to ask them to download it. This is a joke, however, the importance of the real environment is not obvious in jokes. For example, the invention of the JAVA language did not achieve its original purpose in the original environment. Later, the competition for Web became famous, now on Android, Java has finally reached its initial design goal, developing applications on set-top boxes and portable devices. In short, the strategic 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 it is being executed at the following layers, the strategic layer is constantly corrected. This is actually a problem at the strategic layer. It is not another layer, but you will see implementation in other layers and will not change this layer; but it does exist. with feedback from each layer, the strategic layer is constantly revised to make other layers feasible and reasonable.