/LGC设计模式/Human interface guidelines

400 篇文章 3 订阅
147 篇文章 0 订阅
Human interface guidelines
作者: From Wikipedia
日期: 2008-10-20
Human interface guidelines (HIG) 是为应用程序开发者提供的一套规则,保证开发者开发的应用程序在界面上具有良好的一致性和操作性,为用户带来良好的用户体验。
overview

HIG 定义了一套规则,保证开发人员开发的程序遵循统一的界面风格、操作标准,便于用户使用,比如,窗口的布局、菜单的组成、工具按钮的分组等等。

platform dependent guidelines

Human interface guidelines (HIG) are software development documents which offer application developers a set of recommendations. Their aim is to improve the experience for the users by making application interfaces more intuitive, learnable, and consistent. Most guides limit themselves to defining a common look and feel for applications in a particular desktop environment. The guides enumerate specific policies. Policies are sometimes based on studies of human-computer interaction (so called usability studies), but most are based on arbitrary conventions chosen by the platform developers.

Human interface guidelines will dictate a set of rules for general usability. They often describe the visual design rules, including icon and window design and style. Frequently they specify how user input and interaction mechanisms work. Some describe the language style.

A HIG will sometimes also define standard terminology and semantics related to certain elements or actions. In general this is restricted to the semantics of the desktop environment or the file system. As the majority of user problems come from the semantics of the applications, this is a drawback to most HIGs.

The more important version of HIGs are those done for groups or applications. In this case the HIG will build on a platform HIG by adding the common semantics for a range of functions.

The central aim of a HIG is to create a consistent experience across the environment (generally an operating system or desktop environment), including the applications and other tools being used. This means both applying the same visual design and creating consistent access to and behaviour of common elements of the interface - from simple ones such as buttons and icons up to more complex constructions, such as dialog boxes.

HIGs should be taken at face value; their recommendations and advice are meant to help developers create better applications, but developers are naturally free to break them if they think that the guidelines do not fit their application. The only repercussion for doing so may be that the organisation publishing the HIG does not give the application its blessing. Mozilla Firefox's user interface, for example, goes against the GNOME project's HIG, which is one of the main arguments for including Epiphany instead of Firefox in the GNOME distribution. But such departures should only be taken when there is evidence from usability testing that the interface is improved.

Cross-platform guidelines

HIGs should be taken at face value; their recommendations and advice are meant to help developers create better applications, but developers are naturally free to break them if they think that the guidelines do not fit their application. The only repercussion for doing so may be that the organisation publishing the HIG does not give the application its blessing. Mozilla Firefox's user interface, for example, goes against the GNOME project's HIG, which is one of the main arguments for including Epiphany instead of Firefox in the GNOME distribution. But such departures should only be taken when there is evidence from usability testing that the interface is improved.

Examples of HIG
SeeAlso
  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Introduction Introduction 7 Organization of This Document 7 Chapter 1 Key iPad Features and Characteristics 9 iPad Device Characteristics 9 New UI Elements and Behaviors 10 Chapter 2 From iPhone Application to iPad Application 11 Design Strategies for Translating Your iPhone Application 11 Case Study: From Mail on iPhone to Mail on iPad 12 Chapter 3 iPad User Experience Guidelines 17 Aim to Support All Orientations 17 Enhance Interactivity (Don’t Just Add Features) 19 Flatten Your Information Hierarchy 19 Reduce Full-Screen Transitions 22 Enable Collaboration and Connectedness 22 Add Physicality and Heightened Realism 23 Delight People with Stunning Graphics 24 De-emphasize User Interface Controls 25 Minimize Modality 25 Rethink Your Lists 25 Consider Multifinger Gestures 26 Consider Popovers for Some Modal Tasks 26 Restrict Complexity in Modal Tasks 27 Downplay File-Handling Operations 28 Ask People to Save Only When Necessary 28 Migrate Toolbar Content to the Top 29 Start Instantly 30 Always Be Prepared to Stop 31 Create Custom Icons 31 Create a Beautiful Application Icon 31 Create an Icon for Spotlight Search Results 33 Create a Settings Icon (if You Supply Settings) 33 Provide a Custom Document Icon 33 Create a Launch Image for Each Orientation 35 Follow Established Principles 36 3 2010-05-07 | © 2010 Apple Inc. All Rights Reserved. Chapter 4 iPad UI Element Guidelines 37 Bars 37 The Status Bar 37 Navigation Bar 38 Tab Bar 40 Toolbar 41 Content Views 41 Popover 42 Split View 44 Text View 46 Controls 46 Date and Time Picker, Picker 46 Info Button 47 Page Indicator 47 Search Bar 48 Segmented Control 48 Action Sheets, Alerts, and Modal Views 50 Action Sheet 50 Alert 51 Modal View 52 Edit Menu Additions 53 Keyboard Customization 53 Document Revision History 55
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值