iOS人机交互指南：打造优质用户体验

需积分: 9 18 浏览量更新于2024-07-27 收藏 9.83MB PDF 举报

"iPhone Human Interface Guideline - Apple的iOS用户体验设计指南" 《iPhone Human Interface Guideline》（简称HIG）是Apple公司为确保iOS平台上应用程序的用户体验（UX）和界面设计的一致性而制定的设计规范。这份文档对于移动互联网领域的初学者、产品经理、UI设计师以及任何关心用户体验的人员来说，都是一本极具价值的教科书。它详细阐述了如何遵循Apple的设计原则，以创造出符合用户需求、直观易用的应用程序。 HIG强调了以下几个关键的设计原则： 1. **用户中心**：设计应始终以用户为中心，关注他们的需求和期望。应用程序应该简单、直观，让用户能够轻松地完成任务。 2. **一致性**：保持整个系统和应用间的界面元素、交互方式和视觉风格一致，使用户在不同应用间切换时能快速适应。 3. **反馈**：提供及时、清晰的反馈，让用户了解他们的操作状态，如按钮按下后的视觉变化、进度指示等。 4. **直接操作**：鼓励用户直接与内容互动，而不是通过复杂的菜单或指令。例如，捏合手势用于缩放，滑动用于浏览。 5. **减少认知负担**：避免不必要的复杂性，简化界面，使用户可以快速理解并记住如何使用应用。 6. **易用性**：考虑到各种用户的能力，包括视觉、听觉和运动能力有限的用户。设计应具备无障碍功能，如VoiceOver等。 7. **美观**：美观的设计不仅仅是视觉上的愉悦，也应与功能相结合，创造出既美观又实用的界面。 8. **错误预防**：通过清晰的指示和验证，减少用户可能犯错的机会。如果错误发生，应提供明确的错误信息和纠正途径。 9. **学习与效率**：设计应考虑到新用户的初始学习过程，同时也要让熟练用户能够高效地完成任务。 10. **多设备兼容**：随着iPhone家族的不断扩展，设计需考虑不同屏幕尺寸和分辨率，确保在所有设备上的表现。 HIG还涵盖了诸如导航设计、控件使用、文字排版、颜色和图像选择、触摸交互、动画效果、声音设计等多个方面，提供了详细的指导和示例。开发者和设计师可以通过遵循这些指南来提升他们的作品质量，创造出色且符合Apple用户体验标准的iOS应用。不过，值得注意的是，虽然HIG提供了强大的设计框架，但每个应用都应该根据其特定的用户群体和功能需求进行个性化设计，以实现最佳用户体验。

Memory is Not Unlimited

Memory is a critical resource in iPhone OS, so managing memory in your application is crucial. Because the

iPhone OS virtual memory model does not include disk swap space, you must take care to avoid allocating

more memory than is available on the device. When low-memory conditions occur, iPhone OS warns the

running application and may terminate the application if the problem persists. Be sure your application is

responsive to memory usage warnings and cleans up memory in a timely manner.

As you design your application, strive to reduce the application’s memory footprint by, for example, eliminating

memory leaks, making resource files as small as possible, and loading resources lazily. See iPhone Application

Programming Guide for extensive information about how to design iPhone applications that handle memory

appropriately.

One Screen at a Time

One of the biggest differences between the iPhone OS environment and the computer environment is the

window paradigm. With the exceptions of some modal views, users see a single application screen at a time

on an iPhone OS–based device. iPhone applications can contain as many different screens as necessary, but

users access and see them sequentially, never simultaneously.

If the desktop version of your application requires users to see several windows simultaneously, you need

to decide if there’s a different way users can accomplish the same task in a single screen or a sequence of

screens. If not, you should focus your iPhone application on a single subtask of your computer application,

instead of trying to replicate a wider feature set.

One Application at a Time

Only one iPhone application can run at a time, and third-party applications never run in the background.

This means that when users switch to another application, answer the phone, or check their email, the

application they were using quits. It’s important to make sure that users do not experience any negative

effects because of this reality. In other words, users should not feel that leaving your iPhone application and

returning to it later is any more difficult than switching among applications on a computer.

The most effective thing you can do to ensure that users have a positive application-switching experience

is to pare the launch time of your application to the minimum. See iPhone Application Programming Guide

for guidance on how to make your application’s launch time as short as possible.

In general, users quit your application by switching to another application or service on the device; they take

no specific action to close your application. Therefore, do not expect users to select Quit from a menu or

click a close button. This means that your application is likely to quit without much warning, so you should

be prepared to save user changes as they are made, as quickly as possible. Doing so allows a fast, smooth

transition between applications and ensures that your application can reflect the user’s most recent changes

the next time it starts.

Another important facet of the single application model is the way you handle application-specific preferences.

On iPhone OS–based devices, users set preferences in the Settings application. Your iPhone application can

supply such preferences, but this means that they must quit your application when they want to access them

in Settings. If you follow the standard guidelines and offer settings that users need to set once, and then

rarely, if ever, again, the user experience of your application should be smooth.

Platform Differences to Keep in Mind

CHAPTER 1

The iPhone OS Platform: Rich with Possibilities

Minimal User Help

Mobile users don’t have the time to read through a lot of help content before they can use your application.

What’s more, you don’t want to give up valuable space to display or store it. A hallmark of the design of

iPhone OS–based devices is ease of use, so it’s crucial that you meet users’ expectations and make the use

of your application immediately obvious. There are a few things you can do to achieve this:

■ Use standard controls correctly. Users are familiar with the standard controls they see in the built-in

applications, so they already know how to use them in your application.

■ Be sure the path through the information you present is logical and easy for users to predict. In addition,

be sure to provide markers, such as back buttons, that users can use to find out where they are and how

to retrace their steps.

What Are Your Options?

Before you decide how to present your product to iPhone OS users, you need to understand the range of

options you have. Depending on the implementation details of your proposed product and its intended

audience, some types of software may be better suited to your needs than others.

This section divides software for iPhone OS–based devices into three broad categories, primarily based on

implementation method. Roughly speaking, you can create:

■ An iPhone application, which is an application you develop using the iPhone SDK to run natively on

iPhone OS–based devices.

■ Web-only content, including web applications, which are websites that behave like built-in iPhone

applications.

■ A hybrid application, which is an iPhone application that provides access to web content primarily

through a web-content viewing area, but includes some iPhone OS user interface elements.

iPhone Applications

iPhone applications resemble the built-in applications on iPhone OS–based devices in that they reside on

the device itself and take advantage of features of the iPhone OS environment. Users install iPhone applications

on their devices and use them just as they use built-in applications, such as Stocks, Maps, Calculator, and

Mail.

An iPhone application is quick to launch and easy to use. Whether the application enables a task like sending

email or provides entertainment to users, it is characterized by responsiveness, simplicity, and a beautiful,

streamlined user interface.

Web-only Content

You have a few different options when it comes to providing web-only content to iPhone OS users:

■ Web applications

What Are Your Options? 17

CHAPTER 1

The iPhone OS Platform: Rich with Possibilities

Webpages that provide a focused solution to a task and conform to certain display guidelines are known

as web applications, because they behave similarly to the built-in iPhone OS applications. A web

application, like all web-only content, runs in Safari on iPhone; users do not install it on their devices,

instead they go to the web application’s URL.

■ Optimized webpages

Webpages that are optimized for Safari on iPhone display and operate as designed (with the exception

of any elements that rely on unsupported technologies, such as plug-ins, Flash, and Java). In addition,

an optimized webpage correctly scales content for the device screen and is often designed to detect

when it is being viewed on iPhone OS–based devices, so that it can adjust the content it provides

accordingly.

■ Compatible webpages

Webpages that are compatible with Safari on iPhone display and operate as designed (with the exception

of any elements that rely on unsupported technologies, such as plug-ins, Flash, and Java). A compatible

webpage does not tend to take extra steps to optimize the viewing experience on iPhone OS–based

devices, but the device usually displays the page successfully.

If you have an existing website or web application, first ensure that it works well on iPhone OS–based devices.

Also, you should consider creating a custom icon users can put on their Home screens using the Web Clip

feature. In effect, this allows users to keep on their Home Screens a bookmark to your website that looks like

a native application icon. To learn more about creating a custom icon and how to make web content look

great on iPhone OS–based devices, see iPhone Human Interface Guidelines for Web Applications.

Hybrid Applications

With iPhone OS, you can create an application that combines features of native applications and webpages.

A hybrid application is a native iPhone application that provides most of its structure and functionality

through a web viewing area, but also tends to contain standard iPhone OS user interface elements.

A hybrid application gives users access to web content with an element called a web view (described in “Web

Views” (page 104)). Precisely how you use a web view in your application is up to you, but it’s important to

avoid giving users the impression that your application is merely a mini web browser. A hybrid application

should behave and appear like a native iPhone application; it should not draw attention to the fact that it

depends upon web sources.

Three Application Styles

This document identifies three application styles, based on visual and behavioral characteristics, data model,

and user experience. Before you read further, it’s important to emphasize that these varieties are named and

described to help you clarify some of your design decisions, not to imply that there is a rigid classification

scheme that all iPhone software must follow. Instead, these styles are described to help you see how different

approaches can be suitable for different types of information and functionality.

Three Application Styles

CHAPTER 1

The iPhone OS Platform: Rich with Possibilities

Note: Bear in mind that application style does not dictate implementation method. This document focuses

on designing native iPhone applications, but the application styles explored here can be implemented in

web or hybrid applications for iPhone OS–based devices.

As you read about these three application styles, think about how the characteristics of each might enhance

your proposed feature set and the overall user experience you plan to deliver in your iPhone application. To

help you discover the combination of characteristics that best suit your application, keep the following

questions in mind as you learn about different design styles for iPhone applications:

■ What do you expect to be the user’s motivation for using the application?

■ What do you intend to be the user’s experience while using the application?

■ What is the goal or focus of your application?

■ How does your application organize and display the information people care about? Is there a natural

organization associated with the main task of the application?

Productivity Applications

A productivity application enables tasks that are based on the organization and manipulation of detailed

information. People use productivity applications to accomplish important tasks. Mail is a good example of

a productivity application.

Seriousness of purpose does not mean that productivity applications should attempt to appear serious by

providing a dry, uninspiring user experience, but it does mean that users appreciate a streamlined approach

that does not hinder them. To this end, successful productivity applications keep the user experience focused

on the task, so people can quickly find what they need, easily perform the necessary actions, complete the

task, and move on to something else.

Productivity applications often organize user data hierarchically. In this way, people can find information by

making progressively more specific choices until they arrive at the desired level of detail. iPhone OS provides

table elements that make this process extremely efficient on iPhone OS devices (see “Table Views” (page 89)

for more information about these user interface elements). Figure 1-1 shows an example of this type of data

organization.

Three Application Styles 19

CHAPTER 1

The iPhone OS Platform: Rich with Possibilities

剩余135页未读，继续阅读

sd102492

粉丝: 0
资源: 5

iOS人机交互指南：打造优质用户体验

iOS Human Interface Guidelines中文版.pdf

iOS9 human Interface Guideline 中文翻译

iPad Human Interface Guidelines交互 视觉 设计 规范

iPad Human Interface Guideline

ios-human-interface-guidelines:iOS 设计指南（iOS Human Interface Guidelines 中文版）

RCS Guideline

ATEX Guideline

sufer guideline

Developers Guideline

Doxygen guideline

最新资源

iPad Human Interface Guidelines交互视觉设计规范