Talking about the code of interactive design

When the product is large, we need a number of product designers collaborate to complete the product, due to the http://www.aliyun.com/zixun/aggregation/9255.html between different product designers "> design concept, Design method, Different design habits, collaborative finished products tend to lead to poor product consistency, uneven quality. This time will need an interactive design specification to standardize and guide product design, so as to ensure product design consistency, improve the overall product quality. This article says that the interactive design specification should contain some content: first, the page Information Specification page information specification mainly refers to the page static information should follow the rule, including: 1. The title specification is used to specify the rules for headings that should be used by pages of different levels of functionality across the entire product. 2. The new Window link specification is used to specify whether the page link is open with a new window or a rule that opens in this window. 3. The picture specification is used to specify whether the picture information has an ALT title value, which is also taken from there. Interactive information Specification Interactive notification specification is mainly used to specify the way of interaction and its informational hints during interaction, including: 1. Advance information prompts all interactions to provide the user with a prior knowledge of the prompts. A. Forms submit the steps for submitting class forms, each of which requires a prompt message. (such as how many digits the password wants.) The search box encourages what you enter. B. Prudent class operation an operation requires careful action by the user. such as deduction of gold coins. Need to be prompted beforehand. (such as: deduct the operation of gold coins need to be prompted to deduct the number of gold coins, and the current gold is enough.) Wait a minute. C. Differentiation rules when a function of the rules and user habits of the rules have certain differences or more complex, need to give a hint. Or give a help link. 2, the operation of information prompts all interactions need to provide action-related tips. A. Operation confirmation prompts one operation to involve the data deletion, and so on need the careful operation operation need to give the deletion confirmation prompt box. B. Operation error prompts when the user's operation does not conform to the rules of the operation, you need to give an action prompt. (If the comment word is 0 or more than the limit words, the search box is not entered when the content submitted) 3, the results of information prompts interaction after the feedback is given results should give appropriate tips a. Query class results Any information list, query results, when the corresponding information has no results, need to give a result of the status hint. B. Save class results A form is the user submits to save the data. such as setting up personal data. You need to give a prompt when submitting a save. Success Green, failure red, ordinary gray. C. Additional class results a form is attached to other data, such as comments. After a successful submission, you should jump directly to the result display section of the operation. (If a comment should be presented directly to the user for comments submitted by him) Iii. Generic control specification when some functions are reused by multiple modules (such as standard comment boxes, standard Buddy selectors, etc.), you need toThe function is extracted and designed as a common control which is shared by multiple modules. With the page information specification, interactive information specification and general control specification, it can guarantee the consistency of page information, the consistency of interactive mode and prompt, and the common function module. So as to ensure product consistency and improve product quality. Write these welcome additions first. Source: http://jasonthink.blogbus.com/logs/72376529.html