显式保存与隐式保存 - 什么时候更喜欢? [英] Explicit save vs. implicit save - what to prefer when?

问题描述

我目前正在开发一个 wp7 应用程序(不想说太多；)，但我在用户交互方面有点挣扎.

我不确定的主要问题是:我应该在对话框中提供一个明确的保存按钮并将手机后退按钮用作取消，还是应该隐式保存用户点击手机后退按钮的时间......

我想得越多，我就越不确定最佳用户体验.

我已经阅读了 Microsoft 的用户体验和交互指南，但是那里没有关于该问题的任何建议......

感谢您的建议.

解决方案

Windows Phone 7 UI 设计和交互指南的第 68 页指出:

<块引用>

应立即实施对应用程序设置的更改.这意味着不需要完成"、确定"或其他确认对话框.在某些情况下，即使更改立即发生，用户也可能在正在进行的事件完成或未来事件发生之前不会收到更改已发生的反馈.例如加入安全的 Wi-Fi 网络或更改警报频率.

保持应用程序设置简洁明了应该是一个设计目标.复杂、多页面、多级的应用程序设置可能会让用户感到沮丧或困惑，以为他们已经完全进入了另一个应用程序.

虽然同页还接着说:

<块引用>

立即实施用户选择的应用程序设置，无需确认对话框，并提供反馈方法以表明已发生更改.

避免创建超过 2 个页面(屏幕)的应用程序设置.需要多个屏幕的设置应使用重叠的半屏幕以避免在以下情况下丢失上下文显示 SIP 键盘.

如果任务无法撤消，请始终为用户提供取消选项.文本输入就是一个例子.覆盖或删除数据或不可撤销的操作必须有一个取消"按钮.

使用带有提交和取消按钮的附加屏幕时，单击这些按钮应执行相关操作并将用户返回到主设置屏幕.

为了保持设置控制面板的标题一致，设置页面的标题应如下所示:

 设置<CPL名称/应用名称>

<块引用>

通过网络获取数据的应用程序必须具有禁用数据使用的选项.

所以，我认为如果您有多个设置页面，您只会遇到关于显式与隐式的问题，如果您这样做，听起来似乎显式将是使用子页面的方式，但对于子页面来说是隐式的初始页面.

I'm currently developing a wp7 app (don't want to tell too much ;), but I'm struggling a little with the user interaction.

The main question, I'm not sure about is: Should I offer an explicit save button in dialogs and use the phone back button as cancel, or should I save implicit the time the user taps the phone back button ...

The more I think about, the more I'm unsure about the best user experience.

I already read the user experience and interaction guide from Microsoft, but there isn't any advice in there about that issue ...

Thx alot for your suggestions.

解决方案

On page 68 of the Windows Phone 7 UI Design and Interaction Guide it states:

Changes to Application Settings should be immediately implemented. This means that a "Done", "OK", or other confirming dialog is not neededd. In some cases, even though the change has happened immediately, the user may not have feedback that the change has occurred until an ongoing event is completed or a future event occurs. Examples would be joining a secure Wi-Fi network or changing the frequency of alarms.

Keeping Application Settings brief and clear should be a design goal. Complex, multi-page, multi-level Application Settings can frustrate or confuse users into thinking that they have entered another application entirely.

Although the same page also goes on to say:

Immediately implement user-selected Application Settings without a confirming dialog box and provide a feedback method to indicate that the change has occurred.

Avoid creating Application Settings that have more than 2 pages (screens). Settings that require more than a single screen should use overlying half screens to avoid losing context when the SIP Keyboard is displayed.

If a task cannot be undone, always provide the user with an option to cancel. Text entry is an example. Actions that overwrite or delete data, or are irreversable must have a "Cancel" button.

When using additional screens with commit and cancel buttons, clicking those buttons should perform the associated action and return the user to the main settings screen.

To keep the heading of settings control panels consistent, the heading for the settings page should look as follows:

      SETTINGS
      <CPL Name/ Application Name>

Applications that fetch data over the network must have an option to disable data usage.

So, I think you only get in to questions over explicit vs. implicit if you have multiple pages for settings, and if you do it sounds like the explicit would be the way to go with sub-pages, but implicit for the initial page.

这篇关于显式保存与隐式保存 - 什么时候更喜欢?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！