出自UXGuide.net

选择一种应用程序样式

Choosing an Application Style

After reading about productivity, utility, and immersive application styles, think about the type of information your application displays and the task it enables. In theory, the type of application you should create is obvious to you and you’re ready to get started; in practice, it’s not always that simple. Here is a hypothetical scenario to consider as you make your decision.

在了解了生产力应用程序、实用程序和沉浸式应用程序样式后，考虑一下你的应用程序显示的信息类型和所能完成的任务。理论上说，你创建的应用程序类型是对于你来说是显而易见的，你可以开始动手做了；但在实践中，并不总是那么简单。这里有一个假设的情景来帮助你考虑你的决定。

If you have a subject you’d like to explore, think about the objects and tasks related to it. Imagine the different perceptions people have of that subject. For example, consider the subject of baseball. Baseball brings to mind, among other things, teams, games, statistics, history, and players. Baseball is probably too extensive a subject for a single application, so consider just the players. Now imagine how you might create an application that relates to players—for example, using their likenesses on baseball cards.

如果你想探索一个主题，思考与该主题相关的对象和任务。想象一下人们对于这个主题的不同看法。拿棒球做一个例子。棒球使我想起很多，其中有球队，比赛，统计数字，历史和球员。棒球作为一个应用程序的主题可能太宽泛了，所以让我们只考虑球员。现在想象一下如何创建一个关于球员的应用程序——例如，使用棒球卡上他们的肖像。

You could develop a productivity application that helps serious collectors manage their baseball card collections. Using list-based formats, you could display cards in a hierarchy of teams, then players, then seasons. In the most detailed view, you could give users the ability to note where they acquired the card, how much they paid for it, its current market value, and how many copies they have. Because the focus of this application is on the data that defines the collection, the user interface streamlines the tasks of seeking and adding information.

你可以开发一个productivity application，帮助那些认真的收藏家管理他们的棒球卡收藏。使用列表的格式，你可以在一个层次等级里显示卡片，首先是球队，然后球员，再然后赛季。在最详细的视图里，你可以使用户能够记录他们从哪里获得了卡片，花了多少钱，卡片目前的市场价值是多少，他们有多少张拷贝。由于这个应用程序的重点是定义那些收藏的数据，用户界面精简了寻求和添加信息的任务。

You could also develop a utility application that displays the current market value of particular baseball cards. Each view could look like a baseball card with its current value added to the picture, and the back of the view could allow users to select specific cards to track and display. The focus of this application is on individual cards, so the user interface emphasizes the look of the cards and provides a simple control or two that allows users to look for new cards.

你也可以开发一个utility application，显示特定的棒球卡目前的市场价值。每个视图都可以看起来像一张棒球卡，上面添加了它目前的价值，并且可以允许用户在主视图的后面选择特定的卡片来追踪和显示。这个应用程序的重点是单张的卡片，因此，用户界面强调卡的外观，并为用户寻找新卡片提供一两个简单的控件。

Or, of course, you could develop a game. Perhaps the game would focus on the user’s knowledge of certain statistics on individual baseball cards or ability to recognize famous cards. Or perhaps it would simply use baseball cards as icons in another type of game, such as a sliding puzzle. In each of these cases, the focus of the application is on the images on the baseball cards and the game play. The user interface complements this by displaying a few baseball-themed controls and hiding the iPhone OS user interface.

或者，当然，你可以开发一个游戏。也许游戏将着重于用户对于单张棒球卡的某些统计数据的知识，或者对著名卡片的识别能力。也许只是在另一种类型的游戏里使用棒球卡，比如滑动拼图。在这些情况下，应用程序的重点是在棒球卡的图像和游戏。用户界面配合这一点，展示一些以棒球为主题的控件，并隐藏iPhone OS的用户界面。

It’s important to reiterate that you’re not restricted to a single application style. You may find that your application idea is best served by a combination of characteristics from different application styles.

需要重申的是，不要局限于一个应用程序样式。你可能会发现，对于你的应用程序的想法得益于不同应用程序样式的特性的组合。

When in doubt, make it simple. Pare the feature list to the minimum and create an application that does one simple thing (see “Create a Product Definition Statement” for advice on how to focus your application). When you see how people use and respond to the application, you might choose to create another version of the application with a slightly shifted focus or altered presentation. Or, you might discover a need for a more (or less) detail-oriented version of the same concept.

如果有疑问，就简化问题。把功能列表削减到最少，并创建只完成一个简单任务的应用程序（参见“创建产品定义声明”就如何集中你的应用程序给出的建议）。当你看到人们如何使用并响应应用程序，你可以选择创建一个稍微转移了焦点，或更改了显示的应用程序的另一个版本。或者，你可能会发现用户需要一个关于同样主题的更多（或更少）细节的版本。