http://developer.apple.com/library/ios/#documentation/UserExperience/Conceptual/MobileHIG/Principles/Principles.html
Human Interface Principles
A great user interface follows human interface design principles that are based on the way people—users—think and work, not on the capabilities of the device. A user interface that is unattractive, convoluted, or illogical can make even a great application seem like a chore to use. But a beautiful, intuitive, compelling user interface enhances an application’s functionality and inspires a positive emotional attachment in users.
Aesthetic Integrity
Aesthetic integrity is not a measure of how beautiful an application is. It’s a measure of how well the appearance of the app integrates with its function. For example, an app that enables a productive task generally keeps decorative elements subtle and in the background, while giving prominence to the task by providing standard controls and behaviors. Such an app gives users a clear, unified message about its purpose and its identity. If, on the other hand, the app enables the productive task within a UI that seems whimsical or frivolous, people might not know how to interpret these contradictory signals.
Similarly, in an app that encourages an immersive task, such as a game, users expect a beautiful appearance that promises fun and encourages discovery. Although people don’t expect to accomplish a serious or productive task in a game, they still expect the game’s appearance to integrate with the experience.
Consistency
Consistency in the interface allows people to transfer their knowledge and skills from one application to another. A consistent application is not a slavish copy of other applications. Rather, it is an application that takes advantage of the standards and paradigms people are comfortable with.
To determine whether an app follows the principle of consistency, think about these questions:
*
Is the application consistent with iOS standards? Does it use system-provided controls, views, and icons correctly? Does it incorporate device features in a reliable way?
*
Is the application consistent within itself? Does text use uniform terminology and style? Do the same icons always mean the same thing? Can people predict what will happen when they perform the same action in different places? Do custom UI elements look and behave the same throughout the app?
*
Within reason, is the application consistent with its earlier versions? Have the terms and meanings remained the same? Are the fundamental concepts essentially unchanged?
Direct Manipulation
When people directly manipulate onscreen objects instead of using separate controls to manipulate them, they're more engaged with the task and they more readily understand the results of their actions. iOS users enjoy a heightened sense of direct manipulation because of the Multi-Touch interface. Using gestures gives people a greater affinity for, and sense of control over, the objects they see onscreen, because they're able to touch them without using an intermediary, such as a mouse.
For example, instead of tapping zoom controls, people can use the pinch gestures to directly expand or contract an area of content. And in a game, players move and interact directly with onscreen objects. For example, a game might display a combination lock that users can spin to open.
In an iOS application, people can experience direct manipulation when they:
*
Rotate or otherwise move the device to affect onscreen objects
*
Use gestures to manipulate onscreen objects
*
Can see that their actions have immediate, visible results
Feedback
Feedback acknowledges people’s actions and assures them that processing is occurring. People expect immediate feedback when they operate a control, and they appreciate status updates during lengthy operations.
The built-in iOS applications respond to every user action with some perceptible change. For example, list items highlight briefly when people tap them. During operations that last more than a few seconds, a control shows elapsing progress, and if appropriate, the app displays an explanatory message.
Subtle animation can give people meaningful feedback that helps clarify the results of their actions. For example, lists can animate the addition of a new row to help people track the change visually.
Sound can also give people useful feedback. But sound shouldn’t be the primary or sole feedback mechanism because people may use their devices in places where they can’t hear or where they must turn off the sound.
Metaphors
When virtual objects and actions in an application are metaphors for objects and actions in the real world, users quickly grasp how to use the app. The classic example of a software metaphor is the folder: People put things in folders in the real world, so they immediately understand the idea of putting files into folders on a computer.
The most appropriate metaphors suggest a usage or experience without enforcing the limitations of the real-world object or action on which they’re based. For example, people can fill software folders with much more content than would fit in a physical folder.
iOS provides great scope for metaphors because it supports rich graphical images and gestures. People physically interact with realistic onscreen objects, in many cases operating them as if they were real-world objects. Metaphors in iOS include:
*
Tapping iPod playback controls
*
Dragging, flicking, or swiping objects in a game
*
Sliding On/Off switches
*
Flicking through pages of photos
*
Spinning picker wheels to make choices
In general, metaphors work best when they’re not stretched too far. For example, the usability of software folders would decrease if they had to be organized into a virtual filing cabinet.
User Control
People, not applications, should initiate and control actions. Although an application can suggest a course of action or warn about dangerous consequences, it’s usually a mistake for the app to take decision-making away from the user. The best apps find the correct balance between giving people the capabilities they need while helping them avoid dangerous outcomes.
Users feel more in control of an app when behaviors and controls are familiar and predictable. And, when actions are simple and straightforward, users can easily understand and remember them.
People expect to have ample opportunity to cancel an operation before it begins, and they expect to get a chance to confirm their intention to perform a potentially destructive action. Finally, people expect to be able to gracefully stop an operation that’s underway.
Human Interface Principles
A great user interface follows human interface design principles that are based on the way people—users—think and work, not on the capabilities of the device. A user interface that is unattractive, convoluted, or illogical can make even a great application seem like a chore to use. But a beautiful, intuitive, compelling user interface enhances an application’s functionality and inspires a positive emotional attachment in users.
Aesthetic Integrity
Aesthetic integrity is not a measure of how beautiful an application is. It’s a measure of how well the appearance of the app integrates with its function. For example, an app that enables a productive task generally keeps decorative elements subtle and in the background, while giving prominence to the task by providing standard controls and behaviors. Such an app gives users a clear, unified message about its purpose and its identity. If, on the other hand, the app enables the productive task within a UI that seems whimsical or frivolous, people might not know how to interpret these contradictory signals.
Similarly, in an app that encourages an immersive task, such as a game, users expect a beautiful appearance that promises fun and encourages discovery. Although people don’t expect to accomplish a serious or productive task in a game, they still expect the game’s appearance to integrate with the experience.
Consistency
Consistency in the interface allows people to transfer their knowledge and skills from one application to another. A consistent application is not a slavish copy of other applications. Rather, it is an application that takes advantage of the standards and paradigms people are comfortable with.
To determine whether an app follows the principle of consistency, think about these questions:
*
Is the application consistent with iOS standards? Does it use system-provided controls, views, and icons correctly? Does it incorporate device features in a reliable way?
*
Is the application consistent within itself? Does text use uniform terminology and style? Do the same icons always mean the same thing? Can people predict what will happen when they perform the same action in different places? Do custom UI elements look and behave the same throughout the app?
*
Within reason, is the application consistent with its earlier versions? Have the terms and meanings remained the same? Are the fundamental concepts essentially unchanged?
Direct Manipulation
When people directly manipulate onscreen objects instead of using separate controls to manipulate them, they're more engaged with the task and they more readily understand the results of their actions. iOS users enjoy a heightened sense of direct manipulation because of the Multi-Touch interface. Using gestures gives people a greater affinity for, and sense of control over, the objects they see onscreen, because they're able to touch them without using an intermediary, such as a mouse.
For example, instead of tapping zoom controls, people can use the pinch gestures to directly expand or contract an area of content. And in a game, players move and interact directly with onscreen objects. For example, a game might display a combination lock that users can spin to open.
In an iOS application, people can experience direct manipulation when they:
*
Rotate or otherwise move the device to affect onscreen objects
*
Use gestures to manipulate onscreen objects
*
Can see that their actions have immediate, visible results
Feedback
Feedback acknowledges people’s actions and assures them that processing is occurring. People expect immediate feedback when they operate a control, and they appreciate status updates during lengthy operations.
The built-in iOS applications respond to every user action with some perceptible change. For example, list items highlight briefly when people tap them. During operations that last more than a few seconds, a control shows elapsing progress, and if appropriate, the app displays an explanatory message.
Subtle animation can give people meaningful feedback that helps clarify the results of their actions. For example, lists can animate the addition of a new row to help people track the change visually.
Sound can also give people useful feedback. But sound shouldn’t be the primary or sole feedback mechanism because people may use their devices in places where they can’t hear or where they must turn off the sound.
Metaphors
When virtual objects and actions in an application are metaphors for objects and actions in the real world, users quickly grasp how to use the app. The classic example of a software metaphor is the folder: People put things in folders in the real world, so they immediately understand the idea of putting files into folders on a computer.
The most appropriate metaphors suggest a usage or experience without enforcing the limitations of the real-world object or action on which they’re based. For example, people can fill software folders with much more content than would fit in a physical folder.
iOS provides great scope for metaphors because it supports rich graphical images and gestures. People physically interact with realistic onscreen objects, in many cases operating them as if they were real-world objects. Metaphors in iOS include:
*
Tapping iPod playback controls
*
Dragging, flicking, or swiping objects in a game
*
Sliding On/Off switches
*
Flicking through pages of photos
*
Spinning picker wheels to make choices
In general, metaphors work best when they’re not stretched too far. For example, the usability of software folders would decrease if they had to be organized into a virtual filing cabinet.
User Control
People, not applications, should initiate and control actions. Although an application can suggest a course of action or warn about dangerous consequences, it’s usually a mistake for the app to take decision-making away from the user. The best apps find the correct balance between giving people the capabilities they need while helping them avoid dangerous outcomes.
Users feel more in control of an app when behaviors and controls are familiar and predictable. And, when actions are simple and straightforward, users can easily understand and remember them.
People expect to have ample opportunity to cancel an operation before it begins, and they expect to get a chance to confirm their intention to perform a potentially destructive action. Finally, people expect to be able to gracefully stop an operation that’s underway.
发表评论
-
android 查看 cpu
2012-05-28 10:02 670cat /proc/cpuinfo -
32位系统编译android2.3.4
2011-10-21 09:24 705修改这几个文件,该回到32位编译环境即可: exte ... -
用自己编译后的system.img
2011-10-21 09:24 1112自己编译后的system.img替换掉/home/abc/an ... -
android mk 文件
2011-10-21 09:25 681LOCAL_PATH:= $(call my-dir) in ... -
android编译某个模块
2011-10-21 09:25 1720编译模块 android中的一个应用程序可以单独编译,编译后要 ... -
SQLite
2011-07-20 08:59 3361)创建数据库文件: >SQLite3 d: ... -
android life cycle
2011-07-07 10:42 725There two Activity. 1.First pre ... -
android driver for ubuntu 手机驱动
2011-07-05 18:08 1941原文:http://esausilva.com/2010/05 ... -
apk的反编译
2011-06-10 10:22 520需要使用的工具: 1. dex2jar:http://c ... -
sdcard in emulator
2011-06-03 14:22 968http://blog.jayway.com/2009/04/ ... -
全屏显示
2011-05-04 16:09 754//--全屏-->> thi ... -
相关资料链接
2011-04-01 10:41 835android镜像站点:http://developer.an ... -
service 的调用【转】
2011-03-24 09:50 815Service的调用 Context.sta ... -
android笔记和第一个例子的代码
2010-12-24 18:00 15051.android.app.Activity 1) 活 ... -
android学习笔记-1-环境搭建
2010-12-22 09:36 7681.安装JDK1.6,Eclipse3.6 2.安装andr ...
相关推荐
3、Human Interface Principles: Creating a Great User Interface 4、Designing an iPhone Application: From Product Definition to Branding 5、Handling Common Tasks 6、A Brief Tour of the Application User ...
Chapter 2 Human Interface Principles 21 Aesthetic Integrity 21 Consistency 21 Direct Manipulation 22 Feedback 22 Metaphors 22 User Control 23 Chapter 3 App Design Strategies 25 Create an Application ...
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 ...
Read this document to learn about the range of application types you can develop for iPhone OS and the human interface design principles that form the foundation of great iPhone applications....
Apply interface principles that follow Apple's Human Interface Guidelines Take advantage of the new Touch Bar Who This Book Is For People who want to learn programming for the first time and for ...
User interfaces principles that follow Apple's Human Interface Guidelines Who this book is for Swift OS X Programming for Absolute Beginners is for teaching novices programming and teaching ...
14) Some (10) heuristic principles for interface design 15) Steps in usability engineering 16) Some types/methods of evaluation 17) Steps in Experimental evaluation 18) Concepts such as: user-...
Human Resources Strategic Analysis 192 The Future of Business Content 196 Technological Innovations 197 Disintermediation 197 Summary 198 Contents xiii Chapter 6 ETL Services 201 Extraction ...
and how to look beyond a shiny user interface to build a great product. Most importantly, this book will give you a shared framework for your product development team to collaborate effectively. ...
Its primary characteristic is the automation of processes involving combinations of human and machine-based activities, particularly those involving interaction with IT applications and tools. ...
1.2 Principles and Practice of Screen Space Ambient Occlusion 12 1.3 Multi-Resolution Deferred Shading 32 1.4 View Frustum Culling of Catmull-Clark Patches in DirectX 11 39 1.5 Ambient Occlusion ...
1.2 Principles and Practice of Screen Space Ambient Occlusion 12 1.3 Multi-Resolution Deferred Shading 32 1.4 View Frustum Culling of Catmull-Clark Patches in DirectX 11 39 1.5 Ambient Occlusion ...
Requires some form of human interaction to spread. Classic example: E-mail viruses. b) Worms No user replication needed. Worm in infected host scans IP addresses and port numbers, looking for ...