Most people in us have passed the UI design manual (or the UI specification manual). There is often a similar discussion in the forum, and I don't have too much explanation for the framework and structure of the UI design manual. Why do someone wrote UI design instructions in the hundred-page, others still don't understand, or ignore the details? Today, we focus on some experiences about the details of the details, so as to avoid writing only the UI design manual that you can understand.
Let me talk about some of my experiences, I hope everyone will actively discuss:
Our goal is: (no tooth decay, ^ _ ^ joke!) To clearly describe the details and interaction methods in the original type of the user interface, it is necessary to facilitate other developers, demand personnel, and testers, etc. Documentation.
The main contents include: 1. Product goals and success standards, (for example, a new prophecy item is not required to require user satisfaction in more than 90%, the upgrade product requirements will be high.) 2. Product end user group and product use (Understanding the user's age, occupation, product use environment, etc. is very necessary) 3. First meet the basic functions. (For example, the basic function of the DVD machine is to play the disc, there may be a function of playing CD, etc.) 4. Main features (in dozens of functions in products through user authentication and project group filtering, select the user's most commonly used function, Optimize it and exhibited on the interface at different levels.) 5. User interface characteristics. (Each interface has its own characteristics, such as the operation interface of the touch screen and the operation of the mobile phone, as the function is exactly the same, the structure, layout and other characteristics are not the same.)
Some precautions 1. You must close your demand and expand around the function point. 2. Describe the language short and accurate (so others will not be annoying) 3. Keep the text's easy maintenance, it is recommended to use the Word's large-scale view to write, easy to change and find. 4. The manual must have version management to do a detailed description of each update. 5. Icon is submitted with the name and explains what type, such as the desktop icon, the icon, toolbar icon, button icon, property box, or the icon in the message box, etc. in the table. 6. Pay attention to records, including project groups and users, and partners. If you explain to one feature, you will need more clearly. 7. Design and implementation synchronization, this is the hardest, many design is "card" because the program cannot be implemented, and the early procedure can not determine if it can be realized, hurt! 8. Do not forget the maintenance prototype when maintaining the UI design manual, which is important as the replenishment prototype of the UI design manual.
The UI design is easy to neglect. 1. Support error prompts and revocation operations 2. Easy installation and uninstall. 3. The necessary settings and help. 4. Description and problem response prompts for abnormal processing, error messages. 5. In addition to the icons and buttons on the interface, there must be a fast insurance button, a menu access key, and a right-key menu, whether to support the operation of the copy file from other software interfaces. 6. Where is the domain, menu, and buttons in what circumstances are unable to click. 7. State area, used to describe the area of the interface state, usually located below the page. (PS storage time status area display progress bar) 8. Clipboard behavior, user's partial or image copying in our product, can be attached to other programs. 9. The behavior of the pointer, indicates that the hourglass should appear when the wait for a long time, and the cursor of the text input area should have changed. There is a link to a small hand, etc. 10. Sound behavior, warning, button trigger sound, etc. The pop-up position, background color, size, layout, and features of the unified message window 12. Description of program actions such as menu bar and drop-down options, or to right. 13. Dynamic state description, if the window is required to be fade or gradually, then the time and way of the progressive or progressive process (translucent or mosaic) are required. Reference: How to write UI norms? ? Http://www.chinaui.com/bbs/dispbbs.asp?boardid=17&id=4256&replyid=42376&skin=1
This article discusses this article in Chinaui Forum: http://www.chinaui.com/bbs/dispbbs.asp? BoardId = 17 & id = 6983
