Design and layout based on the "Red Line" [WP7 study Note 3]

The biggest overflow change in recent years is the emergence of a declarative-based XAML (eXtensible Application Markup Language) user interface. XAML was initially introduced as part of Windows Presentation Foundation, and is now applied to desktops (via web) and Windows Phone As a markup language under Silverlight. XAML not only contains a set of basic controls, but also can redefine their styles and themes. We can also create our own controls from scratch. Since their rendering is vector-driven, we can ensure that these controls can automatically adjust the ratio based on different resolutions and screen directions.

As a form of Metro (Metro is an interface design language officially introduced by Microsoft in Windows Phone 7. Before Windows Phone, Microsoft has tried to adopt a similar interface style in both Zune player and Xbox 360 hosts and has been widely recognized by users. As a result, Microsoft also adopted the metro design language in the newly released Windows Phone 7 and Windows 8 and office 15, in the future, we will see the shadows of metro in more Microsoft products. ) As part of the user experience, Microsoft follows theRed Thread)The three design guidelines are used to determine the information presented to the user and how the information is presented.

For Windows Phone, Microsoft has derived three red lines that can be used to build basic user experience. When building an application, we should also consider using this as a benchmark to determine whether the design approach is reasonable.

· Personal ---- your lifestyle

· Relevant ---- your social circle, where you are

· Connected ---- your information, your thoughts

First, analyze "personality ". You may be thinking this is obvious, because you have never designed an application that is not designed for end users. However, as developers, we often build applications for individual nurses. There are many reasons, including lack of understanding about how applications are used, requirements of a full-seat enterprise, or other guiding principles.In a sense, the key to personalization is to present only user-related information.For example, if your application is used to display unfinished tasks in the project, you only need to display tasks involving the current user.

An "Auxiliary Function" that makes applications personalized is that a large amount of data is no longer required. For the preceding task application, if you have not designed it as a personalized program, you have to synchronize all unfinished tasks in the project. However, because you are only interested in her or her own tasks, you can reduce the amount of data to be synchronized and presented.

The next red line can make applications "associated ". You may think that you have always "associated" applications with users ". But the question is, how do you associate and to what extent? In fact, you can apply the concept of association to many aspects. In Windows Phone that contains location services, an obvious application is to filter data based on the user's location. For example, you can use location information to display tasks in the project that are located in or near the user's current location. There are also some less obvious applications, such as the accelerometer to calculate whether the user is moving, or use the date and time to filter information through a time window when riding.

The last red line is to create an "interconnected" application. Now, you may think that Microsoft has deviated from its original intention. Creating an interconnected mobile application is nothing more than a grave. However, this is not the true content of the entry REDLINE criterion. Microsoft is not imagining that Windows phones applications run in a disconnected or occasionally connected manner. However, they also know that the powerful functions of cloud computing and the use of hosting services can expand the functions and scope of mobile applications.

Unlike building an isolated application, the "interconnection" principle can inspire you to draw a broader picture, for example, when users can collaborate with others, share information and knowledge between devices and access their information wherever they are. Your applications should be able to connect to online services, store information in the cloud, or communicate with other users. It is not an application that is always in the connection state and fully dependent on the domain network connection. There is still a long way to go for the mobile network to reach the ubiquitous level. Even in areas with good network coverage, there will be no signal, such as airplanes, trains, and automobiles. On the contrary, to build an application with independent functions and network connections, you can synchronize and update the application in the background whenever the Network is available.

Building an exciting user experience is itself an artistic form. It is necessary to combine the ability to determine the user's needs and information they want with some natural creativity that can make the user look pleasing to the eye. In addition to following the "Red Line" to make your experience "personalized", "associated", and "interconnected", make sure that only the information you want to see and use is displayed.