TAILIEUCHUNG - Thiết kế trải nghiệm người dùng iphone - p 14

Heuristics Việc chẩn đoán bạn chọn có thể dựa trên danh sách được thành lập, chẳng hạn như chẩn đoán Jakob Nielsen hay Bruce Tognazzini của "Trước Nguyên tắc tương tác thiết kế." 6 Tuy nhiên, trong hầu hết trường hợp, bạn sẽ muốn điều chỉnh và mở rộng những điển hơn chung chung bao gồm các lĩnh vực cụ thể quan tâm cho các ứng dụng của bạn | scenarios instead of systematically going through the user interface screen by Aspects of heuristic evaluation we ll examine here include Potential heuristics Use of scenarios Location of the evaluation laboratory versus field Capturing and documenting findings Heuristics The heuristics you choose can be based on established lists such as Jakob Nielsen s heuristics or Bruce Tognazzini s First Principles of Interaction Design. 6 However in most cases you ll want to adapt and expand these more generic classics to include specific areas of interest for your app. For example location-based apps may have their own heuristics . Users can always locate their current position and content creation apps may have heuristics for topics such as autosaving content. At a minimum you ll want to adapt the classic heuristics for the iPhone removing web and desktop references. Nielsen s severity ranking scale and iPhone-adapted heuristics are included in TABLE and FIGURE . One of the major weaknesses of heuristics is the emphasis on usability problems. Understanding what your competitors are doing wrong is valuable but there are also best practices that you ll want to emulate. Moreover you will undoubtedly be inspired by many of the innovative design solutions in the iPhone space. As a result you should stray from the heuristics from time to time. They re an excellent starting point but they can be limiting if you re trying to match every observation to a specific heuristic. If something is interesting to you good or bad and there isn t a label create your own TABLE Nielsen Severity Ranking Scale7 Rating Description 0 I don t agree that this is a usability problem at all. 1 Cosmetic problem only. Need not be fixed unless extra time is available. 2 Minor usability problem. Fixing this should be given low priority. 3 Major usability problem. Important to fix so should be given high priority. 4 Usability catastrophe. Imperative to fix this before product can be .

• Đồ họa - Thiết kế - Flash
• thủ thuật lập trình iphone
• lập trình iphone
• cài đặt iphone
• thủ thuật iphone
• ebook lập trình iphone
• ebook lập trình iphonethủ thuật lập trình iphone
• iphone
• tài liệu lập trình iphone
• xcode trên iphone