into a small workshop (11)----Mobile Web Implementation Guide

four or five years ago the smartphone industry was just emerging, and some scholars began to explore the direction of the mobile Web's UI, which was different from the previous version of the Web development of the functional machine castration. Migrating from PC to mobile web design out of the box available principles, more is based on the unique characteristics of the mobile side to explore, experience, principles. This "mobile Web Implementation Guide" is intended to enhance the level of responsive design pages, read more treasures, uncover the entire mobile web design of the door of interest.

Mobile devices continue to seize the domain of the PC side, the demand for mobile web is also rising, more and more sites need to take into account the needs of mobile users. Previous years articles dealing with this trend can also take four strategies: not for, modify the existing design (with CSS), design a separate mobile web site, design a responsible website. Now the strategy of the road more and more convergence to a point, and then there is a "mobile first" argument, that is, the design site first consider the mobile interface, on this basis to consider the PC interface. The author of this book is in this environment, the existing PC website design to mobile modification, and then discuss the characteristics of mobile website and development needs to pay attention to the problem, presents us a complete mobile development status.

The word "mobile", there are many applications such as driving, walking, running, relaxation and so on, that is, sensory organs in a busy state, in the design of mobile page design, you can immerse yourself in these experiences, notice the busy degree of the impact of access to information or the way to operate: when attention is scattered, Make the design options very easy to locate, and in a relaxed state of mind, it is difficult to perform the action. The ultimate goal of the mobile page design layout is to allow users to find what they are looking for as quickly as possible, reducing the burden on the user of the process.

Behind closed doors Imagine the application scenario is far from enough, if the development of a website, focus on the user's needs are always right, mobilize users is the first to do, the book put forward some feasible way. For example, organize user interviews, ask users to drink coffee or eat a meal or a quick interview, or call or email to interact with the user.

With the user's interaction, master the original material, you can proceed to the next step, write user stories. A user story is a schematic design specification, but it uses narrative techniques and focuses on user behavior and scenarios. User stories are written to identify more and more potential design solutions that can lead to more problems that have not been noticed before and need to be addressed. User stories are written in a way that describes the actions of the user and the behavior and reactions they use on the site or in the application.

These steps are step-by-step, get the original data, organize the original data, simulate the user story, and then extract the user's needs. Demand comes out, but sometimes there is a lot of demand or no focus, which requires the prioritization of user stories.

Prioritization can be considered from three levels of demand: basic, performance, and excitement. The basic type as the name implies, is the bottom line of the product, if these needs are not hit, do not have to go online. Performance is based on basic requirements, can promote higher user satisfaction. Excitement is more than the user's expectations, will bring surprises and excitement to users. This demand is a scarce requirement and requires very good creativity. So we can understand that when doing the project, the product manager's B plan is to reduce the performance or excitement of demand, to retain the basic requirements of the product to complete the on-line task. This article explains the process of product manager from demand to refinement.

The book discusses the refactoring of the loading of redundant code problems, the author wants to first suppress, first said the disadvantage, but also know how to adapt, agree to load redundant code. This style of grasping and small is especially important in mobile web design. A few examples of mobile devices are given: the design of watches, car dashboards and iphone calculators, with vivid examples of mobile devices that need to be aware of specific scenarios and user needs to set device proportions and content design. And this leads to the mobile web design width adaptability, picture arrangement, line height and the number of font per line, Apple based on the form type conversion keyboard type example. The core content of this book is explained. The knowledge is not very strong, more embodied in the usability of the trade-offs. Here is an article that conceives the principles of website content architecture.

Usability, the book gives some practical mobile Web principles: shorter titles, shorter descriptions, illustrated numbers, smaller images or dynamically scaled ones, and fewer images. Of course there are more detailed principles please poke here.

The object of this book is more like the one that is written for a shoulder-picked webmaster. Having mastered some of the mobile usability principles, you can write a simple Web application, which gives a simple Web application, from the idea to the completion of the small project process.