出自UXGuide.net

首次体验

First Experience

目录 1 这样的用户界面是否正确？ 1.1 安装体验 1.2 首次使用体验 2 设计理念 2.1 问题不是选项 2.2 仅在必要时才使用首次体验 3 Guidelines 3.1 General 3.2 Presentation 3.3 Settings 3.4 Tasks

“首次体验”用户界面帮助用户从第一次面对一个新程序或新功能过渡到天天使用的状态。

对于 Windows Vista® 程序，最初的体验在用户运行安装程序时即开始了。安装程序通常会：

• 要求用户接受最终用户许可协议（EULA）。
• 要求填写产品密钥。
• 显示所需的与配置相关的选项，包括安装可选软件。
• 将软件复制到用户的硬盘。
• 显示适用于所有用户的程序选项。

典型的 Microsoft® Windows® 安装体验的一部分。

首次体验会继续出现在第一次使用程序或功能之时。首次体验可能会：

• 呈现仅适用于当前用户的程序选项。
• 提供产品或功能教程。

首次使用体验

注：与程序选项相关的设计规范请参考各自相应的章节。

这样的用户界面是否正确？

考虑下列问题以进行判断：

安装体验

下面所述符合实际情况吗？

• 这些设置是使用程序所需的，适用于所有用户。
• 这些设置定制的是核心体验，或者是对于用户在程序中的个人标识至关重要。
• 不存在安全的默认值，用户通常会选择默认值以外的选项，或者是默认设置需要用户的授权。
• 用户一般不会在安装完成后再更改设置。
• 修改设置需要权限提升。

如果情况符合，则可考虑在安装过程中呈现这些设置。

首次使用体验

下面所述符合实际情况吗？

• 这些设置或任务是使用该程序或功能所必需的，且他们适用于个别用户。
• 这些设置定制的是核心体验，或者是对于用户在程序中的个人标识至关重要。
• 不存在安全的默认值，用户通常会选择默认值以外的选项，或者是默认设置需要用户的授权。
• 用户更愿意在程序环境中作出更好的选择，而不是在安装过程中。
• 用户通常不会使用选项来更改设置。

如果情况符合，则可考虑在程序或功能被首次使用时呈现这些任务或设置。

设计理念

在理想的首次体验中，用户能够安装你的程序（甚至只须直接启动而无须安装）并立即开始高效地使用——而不需要回答一大堆问题或者学习一大堆东西。

对于大多数程序来说，理想是可以实现的，只要有可能，你就应力求这样的理想体验。然而，这个目标对于那些需要重大系统集成、拥有大量可选功能、或者是可能存在隐私问题的程序来说是无法实现的。例如，如果你的程序中某个功能可能会将个人信息暴露给不受信任的合作伙伴，可信赖计算（Trustworthy Computing）]原则要求你在启用这类功能时必须得到用户的授权。

问题不是选项

问题需要回答——在用户可以继续进行之前必须回答。对于用户来说，首次体验中的问题是他们能够高效使用你的程序之前必须跨越的障碍。相反，选项不是必须的。用户不需要回答它们，或者可以选择只当他们需要时才显示。

因此，出现在安装向导主流程中的设置属于问题，而位地主安装流程之外的，或是位于程序选项对话框内的是选项。不必要的问题会使你程序的首次体验显得笨重而冗长，极大地削弱了用户刚刚开始使用你程序时的正面期待和激动感。

仅在必要时才使用首次体验

仅在必要时才在首次体验中向用户呈现设置和任务，但通常会有更好的替代方案：

首次体验	替代方案
安装时提问	选择恰当的默认值。 允许用户在程序选项中更改。 提供典型与自定义的安装途径。
首次使用时提问	选择恰当的默认值，并允许用户在程序选项中更改。
首次使用中的任务	改为在相关的上下文中呈现。
首次使用时功能广告	使最常用和最重要的任务易于发现并与上下文相关。
首次使用教程	使程序的功能具有自描述性。
产品注册	在帮助菜单的关于对话框中提供命令。

最重要的一件事：

保持首次体验尽可能地简单，让你的程序能够立即开始工作。选择安全、可靠、方便的默认值，仅在确实必要的时候才在安装过程中提问。

你只有一次机会来创造良好的第一印象，这个第一印象会一直持续下去。

Guidelines

General

• Limit first experiences to tasks and settings required to use a program or feature, and only include these when there is no better alternative. See the previous table for alternatives.
  • Exception: Add personalization or program customization settings to the first experience if their customization is part of the core experience or crucial to the user's personal identification with the program.

Windows asks users for the computer name and choice of background during setup because these settings help form an emotional connection to the product.

• Use the setup experience for tasks and settings if they apply to all users or changing settings requires elevation.
• Use the first use experience for tasks and settings if they apply to individual users.

Presentation

• Prefer optional tasks and settings to required tasks and settings. Avoid forcing users to configure your program.

The Found New Hardware dialog box makes it optional to install driver software instead of making it a required task.

• Take optional tasks and settings out of the main task flow whenever practical. For example, many setup programs provide a custom installation path to remove infrequently changed settings from the main task flow.

A setup experience that facilitates main task flow if the user does not intend to customize the installation.

• Don't overwhelm users with tasks and settings:
  • Start simple. Begin with simple, personalization settings and progress towards more complex, technical tasks and settings. For example, Windows setup starts with personal information and ends with network configuration.
  • Use a contextual first experience for tasks and settings if they apply only to features that aren't fundamental to the main program.

Windows Live Messenger has a contextual setup for audio and video because they are used by secondary features.

• • Don't present everything all at once. Consolidate to use a single UI instead of multiple UI surfaces, or display tasks at different times instead of all at once.

Incorrect:

In this example, the first use experience is overwhelming.

• Express questions and options in terms of users' goals and tasks, not in terms of technology. Provide options that users understand and clearly differentiate. Make sure to provide enough information for users to make informed decisions.
• If the need for personal information isn't obvious, explain why your program needs the information and how it will be used.

In this example, an e-commerce application explains how personal information will be used.

• Present first experiences full screen only if users can't productively perform other tasks. For example, Windows setup is presented full screen to discourage users from performing other tasks while Windows is being installed. Most first experiences shouldn't be full screen.

Settings

• For all settings, select the safest (to prevent loss of data or system access), most secure value by default. If safety and security aren't factors, select the most likely or convenient value. Choosing good defaults is an effective way to simplify the first experience.
• Require users to opt in for:
  • Settings with legal implications, such as end user licensing agreements (EULAs). Such settings can't have default selections.
  • Features that perform automatic system configuration changes, such as Windows automatic updates.
  • Features that reveal personal or system information.
  • Changes to the user's desktop beyond adding entries to the Start menu, such as adding icons to the desktop or quick launch bar.
  • Optional software, such as product enhancements, subscriptions, and third-party products.

In this example, users opt in to product enhancements, subscriptions, and third-party products.

• If a setting is strongly recommended, add "(recommended)" to the label. For radio buttons and check boxes, be sure to add to the control label, not the supplemental notes.
• If a setting is intended only for advanced users, add "(advanced)" to the label. For radio buttons and check boxes, be sure to add to the control label, not the supplemental notes.

Tasks

• Help users pass waiting time productively.
  • If the waiting time is typically between one and two minutes, consider providing helpful information while users are waiting, such as a presentation of what is new during setup.
  • If the waiting time is typically longer than two minutes, make it easy for users to perform other tasks. Display the estimated wait time, recommend that users do something else in the meantime, and make task completion obvious by changing the screen significantly.
• Reconsider presenting tutorials during the first experience. Most likely users want to use your program right away and are interested in tutorials at a later point.
• Don't put feature advertisements in the first experience. Rather, display feature advertisement notifications instead, but only when the feature is crucial, it applies to the user's current activity, and there is no other way to make the user aware of the feature. If any of these factors don't apply, find another way to make the feature discoverable or do nothing at all.