苹果iPhone人机交互指南：打造卓越用户体验

需积分: 16 118 浏览量更新于2024-08-02 收藏 9.22MB PDF 举报

"《iPhone Human Interface Guidelines》是苹果公司于2009年3月4日发布的官方开发文档，旨在提供指导和最佳实践，帮助开发者设计符合苹果产品用户界面（User Experience, UX）规范的iOS应用。该文档强调了设计原则、交互标准和视觉一致性，确保所有应用程序在iPhone上提供一致且无缝的用户体验。首先，文档的核心内容围绕iPhone Human Interface Guidelines（简称HIG），这是苹果对于开发者在设计过程中应遵循的设计规范，涵盖了界面元素布局、导航、触摸交互、字体大小与样式、颜色使用、图标设计等方面。开发者必须遵循这些指南，以确保其应用程序能够顺利融入iOS生态系统，并获得苹果的审核通过。在用户体验方面，HIG着重强调简洁性、直观性和易用性。开发者需避免复杂的操作流程，让用户能够快速理解和完成任务。此外，文档还关注于动态和流畅的动画效果，以及对不同屏幕尺寸和分辨率的适配，以提供出色的触控体验。文档中还特别提到了版权问题，规定了在使用Apple logo（如键盘快捷键Option-Shift-K）时必须得到苹果公司的书面许可，以防止商标侵权和不公平竞争。此外，开发者在利用文档中的技术描述进行应用程序开发时，必须明确知道这并不授予任何技术许可，苹果保留所有与此技术相关的知识产权。《iPhone Human Interface Guidelines》是iOS开发者必备的参考资料，它不仅指导着应用程序的外观和行为，也对提升用户的满意度和保持苹果品牌的统一性起着关键作用。开发者在设计过程中，必须严格遵守这些准则，以确保他们的应用能够充分利用iPhone的特性，提供优质的用户体验，从而在众多应用中脱颖而出。"

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 89)). 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 iPhone applications, but the application styles explored here can be implemented in any type

of software.

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 79)

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

剩余119页未读，继续阅读

luyuncan

粉丝: 2
资源: 8

苹果iPhone人机交互指南：打造卓越用户体验

苹果iOS用户体验指南：Human Interface Guidelines详解

苹果官方Human Interface Guidelines详解

2008 iPhone UX Guidelines: Apple's Unofficial Warranty & Limitations

iPhone.Human.Interface.Guidelines.2009

iPhone Human Interface Guidelines

iPhone Human Interface Guidelines(iPhone用户体验)

iPhone Human Interface Guidelines(iPhone 人机交互指南) 英文版

【iPhone.User.Interface.Cookbook】[PDF+源代码] [iPhone/iPad/iOS]

Apple Human Interface Guidelines

iPhones Human Interface Guidelines

最新资源