Techniques for managing display usage

Abstract

SUMMARY This disclosure relates generally to techniques and user interfaces for transitioning between standard and low power display modes.

Description

Cross - Reference to Related Applications

[0001] This application claims priority to U.S. Provisional Patent Application No. 63 / 180,568, entitled "TECHNIQUES FOR MANAGING DISPLAY USAGE," filed on April 27, 2021, and U.S. Patent Application No. 17 / 546,630, entitled "TECHNIQUES FOR MANAGING DISPLAY USAGE," filed on December 9, 2021, the entire contents of which are incorporated herein by reference.

Technical Field

[0002] The present disclosure generally relates to computer user interfaces, and more specifically, to techniques for displaying user interfaces with managed display usage.

Background Art

[0003] An electronic device may include a screen for displaying a user interface. Over time, non - uniform usage of the screen may result in discoloration of some parts of the screen and a degradation in the quality of the displayed image.

Summary of the Invention

[0004] However, some techniques for using an electronic device to display a user interface are generally cumbersome and inefficient. For example, some existing techniques use complex and time - consuming user interfaces that may include multiple key presses or keystrokes. Existing techniques require more time than necessary, wasting the user's time and the device's energy. This latter consideration is particularly important in battery - operated devices.

[0005] Accordingly, the present technology provides a faster and more efficient method and interface for an electronic device that involves managed display usage. Such a method and interface optionally complement or replace other methods for managing display usage. Such a method improves the image quality of the user interface displayed as the electronic device ages (e.g., reduces the aging degradation of the image quality) and improves the durability of the display device used to display the user interface. Additionally, such a method and interface also reduce the cognitive burden on the user and create a more efficient human-machine interface. In the case of battery-operated computing devices, such a method and interface conserve power and increase the battery charging interval. Further, such a method and interface also reduce the number of redundant, extra, or repetitive inputs required in computing devices such as smartphones and smartwatches.

[0006] According to some embodiments, a method is described. The method includes, in a computer system communicating with a display generation component, while the computer system is in a first mode, displaying, via the display generation component, a first user interface including one or more user interface elements including a first user interface element associated with a first application, where the first user interface is associated with the first application; detecting that one or more criteria for the computer system to transition from the first mode to a second mode, which is a lower power mode, are met while the first user interface is being displayed in the first mode; entering the second mode in response to detecting that one or more criteria for the computer system to transition from the first mode to the second mode are met, where entering the second mode includes displaying a second user interface associated with the first application, the second user interface corresponding to the first user interface and being displayed in a location that occupies at least a portion of the display area occupied by the first user interface and including one or more user interface elements including second user interface elements; while the computer system is in the second mode, periodically updating the appearance of the second user interface elements while maintaining the computer system in the second mode, where, according to a determination that one or more time-dependent update criteria are not met, the appearance of the second user interface elements is periodically updated at a first update frequency, and according to a determination that one or more time-dependent update criteria are met, the appearance of the second user interface elements is periodically updated at a second update frequency different from the first update frequency, and the second update frequency is higher than the first update frequency.

[0007] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that communicates with a display generation component. The one or more programs, while the computer system is in a first mode, via the display generation component, display a first user interface including one or more user interface elements associated with a first application, the first user interface including one or more user interface elements including a first user interface element. While the first user interface is being displayed in the first mode, detect that the computer system has met one or more criteria for transitioning from the first mode to a second mode, which is a lower power mode. In response to detecting that the computer system has met one or more criteria for transitioning from the first mode to the second mode, enter the second mode. Entering the second mode includes displaying a second user interface associated with the first application. The second user interface corresponds to the first user interface and is displayed in a location that occupies at least a portion of the display area occupied by the first user interface, and includes one or more user interface elements including second user interface elements. While the computer system is in the second mode, periodically update the appearance of the second user interface elements while maintaining the computer system in the second mode. According to a determination that one or more time-dependent update criteria are not met, the appearance of the second user interface elements is periodically updated at a first update frequency. According to a determination that one or more time-dependent update criteria are met, the appearance of the second user interface elements is periodically updated at a second update frequency different from the first update frequency, and the second update frequency is higher than the first update frequency.

[0008] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that communicates with a display generation component. The one or more programs include instructions to display, via the display generation component while the computer system is in a first mode, a first user interface including one or more user interface elements associated with a first application, the first user interface including one or more user interface elements including a first user interface element; detect that one or more criteria for the computer system to transition from the first mode to a second mode, which is a lower power mode, are met while the first user interface is being displayed in the first mode; in response to detecting that one or more criteria for the computer system to transition from the first mode to the second mode are met, enter the second mode, and entering the second mode includes displaying a second user interface associated with the first application, the second user interface corresponding to the first user interface and being displayed at a location that occupies at least a portion of the display area occupied by the first user interface, the second user interface including one or more user interface elements including a second user interface element; while the computer system is in the second mode, periodically update the appearance of the second user interface element while maintaining the computer system in the second mode, and according to a determination that one or more time-dependent update criteria are not met, the appearance of the second user interface element is periodically updated at a first update frequency, and according to a determination that one or more time-dependent update criteria are met, the appearance of the second user interface element is periodically updated at a second update frequency different from the first update frequency, and the second update frequency is higher than the first update frequency.

[0009] According to some embodiments, a computer system is described. The computer system includes a display generation component in communication with, one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions to display, while the computer system is in a first mode, via the display generation component, a first user interface including one or more user interface elements associated with a first application, the first user interface including one or more user interface elements including first user interface elements, detect that one or more criteria for the computer system to transition from the first mode to a second mode, which is a lower power mode, are satisfied while the first user interface is being displayed in the first mode, enter the second mode in response to detecting that one or more criteria for the computer system to transition from the first mode to the second mode are satisfied, entering the second mode including displaying a second user interface associated with the first application, the second user interface corresponding to the first user interface and being displayed in a location that occupies at least a portion of the display area occupied by the first user interface, the second user interface including one or more user interface elements including second user interface elements, and while the computer system is in the second mode, periodically update the appearance of the second user interface elements while maintaining the computer system in the second mode, and according to a determination that one or more time-dependent update criteria are not satisfied, the appearance of the second user interface elements is periodically updated at a first update frequency, and according to a determination that one or more time-dependent update criteria are satisfied, the appearance of the second user interface elements is periodically updated at a second update frequency different from the first update frequency, the second update frequency being higher than the first update frequency.

[0010] According to some embodiments, a computer system is described. The computer system communicates with a display generation component and, while the computer system is in a first mode, via the display generation component, displays a first user interface including one or more user interface elements including a first user interface element where the user interface is associated with a first application. Means for detecting that one or more criteria for the computer system to transition from the first mode to a second mode, which is a lower power mode, are met while the first user interface is being displayed in the first mode, and in response to detecting that one or more criteria for the computer system to transition from the first mode to the second mode are met, means for entering the second mode, including displaying a second user interface associated with the first application, where the second user interface corresponds to the first user interface and is displayed in a location that occupies at least a portion of the display area occupied by the first user interface and includes one or more user interface elements including a second user interface element, and means for periodically updating the appearance of the second user interface element while maintaining the computer system in the second mode while the computer system is in the second mode, wherein, according to a determination that one or more time-dependent update criteria are not met, the appearance of the second user interface element is periodically updated at a first update frequency, and according to a determination that one or more time-dependent update criteria are met, the appearance of the second user interface element is periodically updated at a second update frequency different from the first update frequency, and the second update frequency is higher than the first update frequency.

[0011] According to some embodiments, a method is described. The method includes, in a computer system communicating with a display generation component, while the computer system is in a first mode, via the display generation component, displaying a first user interface including a plurality of user interface elements associated with a first application and including a first user interface element indicating a first information set; detecting that one or more criteria for the computer system to transition from the first mode to a second mode have been met while the first user interface is being displayed; in response to detecting that one or more criteria for the computer system to transition from the first mode to the second mode have been met, displaying a second user interface associated with the first application, the second user interface corresponding to the first user interface and being displayed in a location that occupies at least a portion of the display area occupied by the first user interface, the second user interface being darker than the first user interface, and the second user interface including a second user interface element indicating the first information set, according to a determination that the first application is permitted to display the first information set while the computer system is in the second mode; and displaying a third user interface different from the first user interface and the second user interface, the third user interface being displayed in a location that occupies at least a portion of the display area occupied by the first user interface, the third user interface not including the first information set, according to a determination that the first application is not permitted to display the first information set while the computer system is in the second mode.

[0012] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that communicates with a display generation component. The one or more programs, while the computer system is in a first mode, via the display generation component, display a first user interface including a plurality of user interface elements associated with a first application and including first user interface elements indicating a first information set. While displaying the first user interface, detect that one or more criteria for the computer system to transition from the first mode to a second mode are met. In response to detecting that one or more criteria for the computer system to transition from the first mode to the second mode are met, according to a determination that the first application is permitted to display first information while the computer system is in the second mode, display a second user interface associated with the first application, the second user interface corresponding to the first user interface and being displayed at a location that occupies at least a portion of the display area occupied by the first user interface, the second user interface being darker than the first user interface, the second user interface including second user interface elements indicating the first information set. According to a determination that the first application is not permitted to display the first information set while the computer system is in the second mode, display a third user interface different from the first user interface and the second user interface, the third user interface being displayed at a location that occupies at least a portion of the display area occupied by the first user interface, the third user interface not including the first information set, including instructions.

[0013] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that communicates with a display generation component, and the one or more programs, while the computer system is in a first mode, via the display generation component, display a first user interface including a plurality of user interface elements associated with a first application and including first user interface elements indicating a first information set, and while displaying the first user interface, detect that one or more criteria for the computer system to transition from the first mode to a second mode are met, and in response to detecting that one or more criteria for the computer system to transition from the first mode to the second mode are met, according to a determination that the first application is permitted to display first information while the computer system is in the second mode, display a second user interface associated with the first application, the second user interface corresponding to the first user interface and being displayed at a location that occupies at least a portion of the display area occupied by the first user interface, the second user interface being darker than the first user interface, the second user interface including second user interface elements indicating the first information set, and according to a determination that the first application is not permitted to display the first information set while the computer system is in the second mode, display a third user interface different from the first user interface and the second user interface, the third user interface being displayed at a location that occupies at least a portion of the display area occupied by the first user interface, the third user interface not including the first information set, including instructions.

[0014] According to some embodiments, a computer system is described. The computer system includes a display generation component in communication with, one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors. The one or more programs, while the computer system is in a first mode, via the display generation component, display a first user interface including a plurality of user interface elements associated with a first application and including a first user interface element indicating a first information set. While displaying the first user interface, detect that one or more criteria for the computer system to transition from the first mode to a second mode are met. In response to detecting that one or more criteria for the computer system to transition from the first mode to the second mode are met, according to a determination that the first application is permitted to display the first information while the computer system is in the second mode, display a second user interface associated with the first application, the second user interface corresponding to the first user interface and being displayed at a location that occupies at least a portion of the display area occupied by the first user interface, the second user interface being darker than the first user interface, and the second user interface including a second user interface element indicating the first information set. According to a determination that the first application is not permitted to display the first information set while the computer system is in the second mode, display a third user interface different from the first user interface and the second user interface, the third user interface being displayed at a location that occupies at least a portion of the display area occupied by the first user interface, and the third user interface not including the first information set, including instructions.

[0015] According to some embodiments, a computer system is described. The computer system communicates with a display generation component and, while the computer system is in a first mode, via the display generation component, displays a first user interface including a plurality of user interface elements associated with a first application and including a first user interface element indicating a first information set. While the first user interface is being displayed, means for detecting that the computer system has met one or more criteria for transitioning from the first mode to a second mode. In response to detecting that the computer system has met one or more criteria for transitioning from the first mode to the second mode, according to a determination that the first application is permitted to display the first information set while the computer system is in the second mode, there is a second user interface associated with the first application, the second user interface corresponding to the first user interface and being displayed in a location that occupies at least a portion of the display area occupied by the first user interface, the second user interface being darker than the first user interface, the second user interface including a second user interface element indicating the first information set, and displaying the second user interface. According to a determination that the first application is not permitted to display the first information set while the computer system is in the second mode, a third user interface different from the first user interface and the second user interface, the third user interface being displayed in a location that occupies at least a portion of the display area occupied by the first user interface and not including the first information set, and means for displaying the third user interface.

[0016] According to some embodiments, a method is described. The method includes, in a computer system communicating with a display generation component, while the computer system is in a first mode, via the display generation component, displaying a first user interface associated with a first application and including a first set of one or more user interface elements including a first user interface element, wherein an appearance of the first user interface element is periodically updated at a first update frequency and the first user interface is displayed at a first zoom level; detecting that one or more criteria for the computer system to transition from the first mode to a second mode are met while the first user interface is being displayed; and in response to detecting that one or more criteria for the computer system to transition from the first mode to the second mode are met, displaying a second user interface associated with the first application, different from the first user interface, wherein the second user interface corresponds to the first user interface and is displayed at a location occupying at least a portion of the display area occupied by the first user interface, the second user interface includes a second set of one or more user interface elements including a second user interface element, an appearance of the second user interface element is periodically updated at a second update frequency different from the first update frequency and corresponding to an update frequency lower than the first update frequency, and the second user interface is displayed at a second zoom level different from the first zoom level.

[0017] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that communicates with a display generation component, and the one or more programs, while the computer system is in a first mode, via the display generation component, are associated with a first application and include a first set of one or more user interface elements including a first user interface element, and the appearance of the first user interface element is periodically updated at a first update frequency, and the first user interface is displayed at a first zoom level, display the first user interface, and while the first user interface is being displayed, detect that one or more criteria for the computer system to transition from the first mode to a second mode are met, and in response to detecting that one or more criteria for the computer system to transition from the first mode to a second mode are met, display a second user interface associated with the first application, different from the first user interface, the second user interface corresponding to the first user interface and being displayed at a location that occupies at least a portion of the display area occupied by the first user interface, the second user interface including a second set of one or more user interface elements including a second user interface element, and the appearance of the second user interface element is periodically updated at a second update frequency corresponding to an update frequency lower than the first update frequency and different from the first update frequency, and the second user interface is displayed at a second zoom level different from the first zoom level, and includes instructions.

[0018] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that communicates with a display generation component. The one or more programs, while the computer system is in a first mode, via the display generation component, are associated with a first application and include a first set of one or more user interface elements including a first user interface element, and display a first user interface, wherein an appearance of the first user interface element is periodically updated at a first update frequency, and the first user interface is displayed at a first zoom level. While displaying the first user interface, detect that one or more criteria for the computer system to transition from the first mode to a second mode are met, and in response to detecting that one or more criteria for the computer system to transition from the first mode to the second mode are met, display a second user interface associated with the first application, which is different from the first user interface, the second user interface corresponding to the first user interface and being displayed at a location that occupies at least a portion of the display area occupied by the first user interface, the second user interface including a second set of one or more user interface elements including a second user interface element, an appearance of the second user interface element being periodically updated at a second update frequency corresponding to an update frequency lower than the first update frequency and different from the first update frequency, and the second user interface being displayed at a second zoom level different from the first zoom level, and include instructions.

[0019] According to some embodiments, a computer system is described. The computer system includes a display generation component in communication with, one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors. The one or more programs cause the computer system, while in a first mode, via the display generation component, to display a first user interface associated with a first application and including a first set of one or more user interface elements including first user interface elements, wherein an appearance of the first user interface elements is periodically updated at a first update frequency, and the first user interface is displayed at a first zoom level. While displaying the first user interface, detect that the computer system has met one or more criteria for transitioning from the first mode to a second mode, and in response to detecting that the computer system has met one or more criteria for transitioning from the first mode to a second mode, display, unlike the first user interface, a second user interface associated with the first application, the second user interface corresponding to the first user interface and being displayed at a location that occupies at least a portion of the display area occupied by the first user interface, the second user interface including a second set of one or more user interface elements including second user interface elements, wherein an appearance of the second user interface elements is periodically updated at a second update frequency different from the first update frequency and corresponding to an update frequency lower than the first update frequency, and the second user interface is displayed at a second zoom level different from the first zoom level, including instructions.

[0020] According to some embodiments, a computer system is described. The computer system communicates with a display generation component and, while the computer system is in a first mode, via the display generation component, a first user interface associated with a first application and including a first set of one or more user interface elements, wherein the appearance of the first user interface elements is periodically updated at a first update frequency and the first user interface is displayed at a first zoom level, means for displaying the first user interface; means for detecting that one or more criteria for the computer system to transition from the first mode to a second mode have been met while the first user interface is being displayed; and in response to detecting that one or more criteria for the computer system to transition from the first mode to the second mode have been met, a second user interface associated with the first application, different from the first user interface, is displayed, the second user interface corresponding to the first user interface and being displayed in a location that occupies at least a portion of the display area occupied by the first user interface, the second user interface including a second set of one or more user interface elements including second user interface elements, the appearance of the second user interface elements being periodically updated at a second update frequency different from the first update frequency and corresponding to an update frequency lower than the first update frequency, and the second user interface being displayed at a second zoom level different from the first zoom level, means for.

[0021] The executable instructions for performing these functions are optionally included within a non-transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors. The executable instructions for performing these functions are optionally included within a temporary computer-readable storage medium or other computer program product configured to be executed by one or more processors.

[0022] Accordingly, a faster and more efficient method and interface for managing display usage are provided to the device, thereby increasing the effectiveness, efficiency, and user satisfaction of such a device. Such a method and interface may complement or replace other methods for managing display usage.

Brief Description of the Drawings

[0023] To better understand the various embodiments described, the following "Modes for Carrying Out the Invention" should be referred to in conjunction with the following drawings, and like reference numerals refer to corresponding parts throughout the following figures.

[0024]

Figure 1A

[0025]

Figure 1B

[0026]

Figure 2

[0027]

Figure 3

[0028]

Figure 4A

[0029]

Figure 4B

[0030]

Figure 5A

[0031]

Figure 5B

[0032]

Figure 6A

Figure 6B

Figure 6C

Figure 6D

Figure 6E

Figure 6F

Figure 6G

Figure 6H

Figure 6I

Figure 6G

Figure 6K

Figure 6L

Figure 6M

Figure 6N

Figure 6O

Figure 6P

Figure 6Q

Figure 6R

Figure 6S

Figure 6T

Figure 6U

Figure 6V

Figure 6W

Figure 6X

Figure 6Y

Figure 6Z

Figure 6AA

Figure 6AB

Figure 6AC

Figure 6AD

Figure 6AE

Figure 6AF

Figure 6AG

Figure 6AH

Figure 6AI

Figure 6AJ

Figure 6AK

[0033]

Figure 7A

Figure 7B

[0034]

Figure 8A

Figure 8B

Figure 8C

Figure 8D

Figure 8E

Figure 8F

Figure 8G

Figure 8H

Figure 8I

Figure 8J

Figure 8K

Figure 8L

Figure 8M

Figure 8N

Figure 8O

Figure 8P

Figure 8Q

Figure 8R

Figure 8S

Figure 8T

Figure 8U

Figure 8V

Figure 8W

Figure 8X

Figure 8Y

Figure 8Z

Figure 8AA

Figure 8AB

Figure 8AC

Figure 8AD

[0035]

Figure 9A

Figure 9B

[0036]

Figure 10A

Figure 10B

Figure 10C

Figure 10D

Figure 10E

Figure 10F

Figure 10G

Figure 10H

Figure 10I

Figure 10J

Figure 10K

[0037]

Figure 11A

Figure 11B

DETAILED DESCRIPTION OF THE INVENTION

[0038] The following description sets forth exemplary methods, parameters, and the like. However, it should be recognized that such description is not intended as a limitation on the scope of the present disclosure, but rather as a description of exemplary embodiments.

[0039] There is a need for an efficient method and interface for managing display usage in an electronic device. For example, long-term display of a user interface that includes graphical objects that do not move over time (e.g., a still image) can cause screen burn-in or image ghosting. This is particularly true for portable multifunctional devices with a reduced-size display, since elements of the displayed user interface are often repeatedly displayed in fixed positions on the display. Techniques for carefully managing what is included on the user interface, how it is displayed, and when it is displayed minimize screen burn-in and image ghosting. Such techniques can reduce the cognitive burden on the user accessing the user interface, thereby increasing productivity. Further, such techniques can reduce processor and battery power that would otherwise be wasted on redundant user input and excessive display brightness, and can improve the wear characteristics of the display device used to display the user interface.

[0040] The following, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide an illustration of exemplary devices for implementing techniques for managing display usage. FIGS. 6A-6AK show exemplary user interfaces with managed display usage. FIGS. 7A-7B are flow diagrams showing methods for managing display usage according to some embodiments. The user interfaces of FIGS. 6A-6AK are used to illustrate processes described later, including the process of FIGS. 7A-7B. FIGS. 8A-8AD show exemplary user interfaces with managed display usage. FIGS. 9A-9B are flow diagrams showing methods for managing display usage according to some embodiments. The user interfaces of FIGS. 8A-8AD are used to illustrate processes described later, including the process of FIGS. 9A-9B. FIGS. 10A-10K show exemplary user interfaces with managed display usage. FIGS. 11A-11B are flow diagrams showing methods for managing display usage according to some embodiments. The user interfaces of FIGS. 10A-10K are used to illustrate processes described later, including the process of FIGS. 11A-11B.

[0041] In the following description, terms such as "first", "second", etc. are used to describe various elements, but these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, without departing from the scope of the various embodiments described, the first touch can be referred to as the second touch, and similarly, the second touch can be referred to as the first touch. Both the first touch and the second touch are touches, but they are not the same touch.

[0042] The terms used in the description of the various embodiments described in this specification are for the purpose of describing particular embodiments only and are not intended to be limiting. As used in the description of the various embodiments described and in the appended claims, the singular forms "a", "an", and "the" are intended to include the plural as well, unless the context clearly dictates otherwise. Also, as used herein, the term "and / or" refers to and includes any and all possible combinations of one or more of the associated listed items. It should be understood that the terms "includes", "including", "comprises", and / or "comprising", when used herein, specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0043] The term "if (in the case of ~)" is optionally interpreted, depending on the context, to mean "when (~)" or "upon (~)", or "in response to determining (~)" or "in response to detecting (~)". Similarly, the phrases "if it is determined (~)" or "if [a stated condition or event] is detected) ([the stated condition or event] is detected)" are optionally interpreted, depending on the context, to mean "upon determining (~)" or "in response to determining (~)", or "upon detecting [the stated condition or event] ([the stated condition or event] is detected)" or "in response to detecting [the stated condition or event] ([the stated condition or event] is detected)".

[0044] Embodiments of electronic devices, user interfaces for such devices, and related processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a cellular phone, that also includes other functions such as PDA functionality and / or music player functionality. Exemplary embodiments of portable multifunctional devices include, but are not limited to, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Optionally, other portable electronic devices, such as a laptop computer or tablet computer having a touch-sensitive surface (e.g., a touch screen display and / or a touch pad), may also be used. Also, in some embodiments, it should be understood that the device is not a portable communication device but a desktop computer having a touch-sensitive surface (e.g., a touch screen display and / or a touch pad). In some embodiments, the electronic device is a computer system that communicates with a display generation component (e.g., via wired communication, via wireless communication). The display generation component is configured to provide a visual output, such as a display via a CRT display, a display via an LED display, or a display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. As used herein, "displaying" content includes transmitting data (e.g., image data or video data) to an integrated or external display generation component via a wired or wireless connection to visually generate the content (e.g., video data rendered or decoded by a display controller 156) in order to display the content.

[0045] In the following discussion, an electronic device including a display and a touch sensing surface will be described. However, it should be understood that the electronic device optionally includes one or more other physical user interface devices such as a physical keyboard, a mouse, and / or a joystick.

[0046] The device typically supports various applications such as one or more of a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a game application, a telephone application, a video conferencing application, an email application, an instant messaging application, a training support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and / or a digital video player application.

[0047] The various applications executed on the device optionally use at least one common physical user interface device such as a touch sensing surface. One or more functions of the touch sensing surface and the corresponding information displayed on the device are optionally adjusted and / or changed from one application to the next and / or within an individual application. Thus, the common physical architecture of the device (such as a touch sensing surface) optionally supports various applications with a user interface that is intuitive and transparent to the user.

[0048] Attention is now directed to an embodiment of a portable device having a touch-sensing display. FIG. 1A is a block diagram showing a portable multifunctional device 100 having a touch-sensing display system 112 according to some embodiments. The touch-sensing display 112 may be referred to herein as a “touch screen” for convenience and may be known or referred to as a “touch-sensing display system”. The device 100 includes a memory 102 (optionally including one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral device interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. The device 100 optionally includes one or more optical sensors 164. The device 100 optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on the device 100 (e.g., a touch-sensing surface such as the touch-sensing display system 112 of the device 100). The device 100 optionally includes one or more haptic output generators 167 for generating haptic output on the device 100 (e.g., on a touch-sensing surface such as the touch-sensing display system 112 of the device 100 or the touch pad 355 of the device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0049] As used herein and in the claims, the term "intensity" of a contact on a touch sensing surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch sensing surface, or a proxy for the force or pressure of a contact on the touch sensing surface. The intensity of the contact has a range of values that includes at least four distinct values and more typically includes hundreds (e.g., at least 256) of distinct values. The intensity of the contact is optionally determined (or measured) using a variety of techniques and a variety of sensors or combinations of sensors. For example, one or more force sensors under or adjacent to the touch sensing surface are optionally used to measure the force at various points on the touch sensing surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted averaged) to determine the estimated force of the contact. Similarly, a pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch sensing surface. Alternatively, the size and / or change thereof of the contact area detected on the touch sensing surface, the capacitance and / or change thereof of the touch sensing surface in proximity to the contact, and / or the resistance and / or change thereof of the touch sensing surface in proximity to the contact are optionally used as an alternative to the force or pressure of the contact on the touch sensing surface. In some implementations, a proxy measurement of the force or pressure of the contact is used directly to determine whether it exceeds an intensity threshold (e.g., the intensity threshold is described in units corresponding to the proxy measurement). In some implementations, the proxy measurement of the contact force or pressure is converted to an estimated value of the force or pressure, and the estimated value of the force or pressure is used to determine whether it exceeds an intensity threshold (e.g., the intensity threshold is a pressure threshold measured in units of pressure). By using the intensity of the contact as an attribute of user input, a user can access additional device functions that may otherwise be inaccessible to the user on a reduced-size device with a limited implementation area for displaying affordances (e.g., on a touch sensing display), and / or receive user input (e.g., via a touch sensing display, a touch sensing surface, or a physical / mechanical control such as a knob or button).

[0050] As used in this specification and the claims, the term "haptic output" refers to a physical displacement of the device relative to its previous position, a physical displacement of a component of the device (e.g., a touch-sensing surface) relative to another component of the device (e.g., the housing), or a displacement of a component relative to the center of mass of the device that will be detected by the user's sense of touch. For example, in a situation where the device or a component of the device is in contact with a touch-sensitive surface of the user (e.g., the finger, palm, or other part of the user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in the physical characteristics of the device or the component of the device. For example, a movement of a touch-sensing surface (e.g., a touch-sensing display or a trackpad) may optionally be interpreted by the user as a "down click" or "up click" of a physical actuator button. In some cases, the user may feel a tactile sensation such as a "down click" or "up click" even when there is no movement of the physical actuator button associated with the touch-sensing surface physically depressed (e.g., displaced) by the user's action. As another example, a movement of the touch-sensing surface may optionally be interpreted or perceived by the user as "roughness" of the touch-sensing surface even when there is no change in the smoothness of the touch-sensing surface. Such interpretation of touch by the user depends on the user's individual sensory perception, but there are many sensory perceptions of touch that are common to a majority of users. Thus, when a haptic output is described as corresponding to a particular sensory perception of the user (e.g., "up click", "down click", "roughness"), unless otherwise stated, the generated haptic output corresponds to a physical displacement of the device or a component of the device that produces the described sensory perception of a typical (or average) user.

[0051] Device 100 is merely an example of a portable multifunctional device. It should be understood that device 100 may optionally have more or fewer components than those shown, may optionally combine two or more components, or may optionally have different configurations or arrangements of those components. The various components shown in FIG. 1A are implemented in a combination of hardware, software, or both hardware and software, including one or more signal processing circuits and / or application specific integrated circuits.

[0052] Memory 102 optionally includes high-speed random access memory and also optionally includes non-volatile memory such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid state memory devices. Memory controller 122 optionally controls access to memory 102 by other components of device 100.

[0053] Peripheral interface 118 can be used to couple input and output peripheral devices of the device to CPU 120 and memory 102. One or more processors 120 operate or execute various software programs and / or instruction sets stored in memory 102 to perform various functions for device 100 and process data. In some embodiments, peripheral interface 118, CPU 120, and memory controller 122 are optionally implemented on a single chip such as chip 104. In some other embodiments, they are optionally implemented on separate chips.

[0054] The RF (radio frequency) circuit 108 transmits and receives RF signals, also called electromagnetic signals. The RF circuit 108 converts electrical signals into electromagnetic signals or vice versa and communicates with a communication network and other communication devices via electromagnetic signals. The RF circuit 108 optionally includes well-known circuits for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and the like. The RF circuit 108 optionally communicates wirelessly with networks such as the Internet, also called the World Wide Web (WWW), an intranet, and / or a wireless network such as a cellular telephone network, a wireless local area network (LAN), and / or a metropolitan area network (MAN), as well as with other devices. The RF circuit 108 optionally includes well-known circuits for detecting a near field communication (NFC) field, such as by a short-range communication radio. Wireless communication optionally includes, but is not limited to only, Global System for Mobile Communications (GSM) for mobile communication, Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), Long Termevolution, LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE802.11a, IEEE802.11b, IEEE802.11g, IEEE802.11n, and / or IEEE802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, Protocols for email (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), Instant Messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol including communication protocols not yet developed as of the filing date of this specification.

[0055] The audio circuit 110, the speaker 111, and the microphone 113 provide an audio interface between the user and the device 100. The audio circuit 110 receives audio data from the peripheral device interface 118, converts this audio data into an electrical signal, and transmits this electrical signal to the speaker 111. The speaker 111 converts the electrical signal into human audible sound waves. Also, the audio circuit 110 receives the electrical signal converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signal into audio data and transmits this audio data to the peripheral device interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to the memory 102 and / or the RF circuit 108 by the peripheral device interface 118. In some embodiments, the audio circuit 110 also includes a headset jack (e.g., 212 of FIG. 2). The headset jack provides an interface between the audio circuit 110 and a detachable audio input / output peripheral device such as an output-only headset or a headset with both output (e.g., mono or stereo headphones) and input (e.g., microphone).

[0056] The I / O subsystem 106 couples input / output peripheral devices on the device 100, such as the touch screen 112 and other input control devices 116, to the peripheral device interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, a depth camera controller 169, an intensity sensor controller 159, a haptic feedback controller 161, and one or more input controllers 160 for other input devices or control devices. The one or more input controllers 160 receive electrical signals from and transmit electrical signals to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and the like. In some embodiments, the input controller(s) 160 are optionally coupled to (or not coupled to) any of a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. One or more buttons (e.g., 208 in FIG. 2) optionally include up / down buttons for volume control of the speaker 111 and / or the microphone 113. One or more buttons optionally include push buttons (e.g., 206 in FIG. 2). In some embodiments, the electronic device is a computer system that communicates with one or more input devices (e.g., via wired communication, via wireless communication). In some embodiments, the one or more input devices include a touch sensing surface (e.g., a trackpad as part of a touch sensing display). In some embodiments, the one or more input devices include one or more camera sensors (e.g., one or more optical sensors 164 and / or one or more depth camera sensors 175) for tracking a user gesture (e.g., a hand gesture) as an input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system.

[0057] As described in U.S. Patent Application No. 11 / 322,549, filed December 23, 2005, "Unlocking a Device by Performing Gestures on an Unlock Image," which is hereby incorporated by reference in its entirety, and U.S. Patent No. 7,657,849, a quick press of a push button optionally unlocks the touch screen 112 or, optionally, initiates a process of unlocking the device using gestures on the touch screen. A longer press of a push button (e.g., 206) optionally turns the power to the device 100 on or off. The functionality of one or more of the buttons is optionally customizable by the user. The touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

[0058] The touch-sensitive display 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from the touch screen 112 and / or transmits electrical signals to the touch screen 112. The touch screen 112 displays visual output to the user. This visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively referred to as "graphics"). In some embodiments, some or all of the visual output optionally corresponds to user interface objects.

[0059] The touch screen 112 has a touch sensing surface, sensor, or set of sensors that accepts input from a user based on tactile and / or haptic contact. The touch screen 112 and the display controller 156 detect contact (and any movement or interruption of the contact) on the touch screen 112 (along with any associated modules and / or instruction sets in the memory 102) and convert the detected contact into an interaction with user interface objects (e.g., one or more soft keys, icons, web pages, or images) displayed on the touch screen 112. In an exemplary embodiment, the point of contact between the touch screen 112 and the user corresponds to the user's finger.

[0060] The touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although in other embodiments other display technologies are also used. The touch screen 112 and the display controller 156 optionally use any of a plurality of touch sensing technologies, now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, and other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen 112, to detect contact and any movement or interruption thereof. In an exemplary embodiment, projected mutual capacitance sensing technology, such as that found in the iPhone (registered trademark) and iPod Touch (registered trademark) from Apple Inc. of Cupertino, California, is used.

[0061] The touch-sensing display in some embodiments of touch screen 112 is optionally similar to a multi-touch sensing touch pad described in U.S. Patent No. 6,323,846 (Westerman et al.), No. 6,570,557 (Westerman et al.), and / or No. 6,677,932 (Westerman), and / or U.S. Patent Application Publication No. 2002 / 0015024 (A1), each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas the touch-sensing touch pad does not provide visual output.

[0062] The touch-sensing displays in some embodiments of touch screen 112 are described in the following applications: (1) U.S. Patent Application No. 11 / 381,313, filed May 2, 2006, "Multipoint Touch Surface Controller"; (2) U.S. Patent Application No. 10 / 840,862, filed May 6, 2004, "Multipoint Touchscreen"; (3) U.S. Patent Application No. 10 / 903,964, filed Jul. 30, 2004, "Gestures For Touch Sensitive Input Devices"; (4) U.S. Patent Application No. 11 / 048,264, filed Jan. 31, 2005, "Gestures For Touch Sensitive Input Devices"; (5) U.S. Patent Application No. 11 / 038,590, filed Jan. 18, 2005, "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices"; (6) U.S. Patent Application No. 11 / 228,758, filed Sep. 16, 2005, "Virtual Input Device Placement On A Touch Screen User Interface"; (7) U.S. Patent Application No. 11 / 228,700, filed Sep. 16, 2005, "Operation Of A Computer With A Touch Screen Interface"; (8) U.S. Patent Application No. 11 / 228,737, filed Sep. 16, 2005, "Activating Virtual Keys Of A Touch-Screen Virtual Keyboard"; and (9) U.S. Patent Application No. 11 / 367,749, filed Mar. 3, 2006, "Multi-Functional Hand-Held Device". All of these applications are hereby incorporated by reference in their entirety.

[0063] The touch screen 112 optionally has a video resolution exceeding 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user optionally touches the touch screen 112 using any suitable object or appendage such as a stylus, finger, etc. In some embodiments, the user interface is designed to operate primarily using finger-based contact and gestures, which may not be as accurate as stylus-based input because the contact area of the finger on the touch screen is larger. In some embodiments, the device converts rough input by the finger into an accurate pointer / cursor position or command for performing the action desired by the user.

[0064] In some embodiments, in addition to the touch screen, the device 100 optionally includes a touch pad for activating or deactivating certain functions. In some embodiments, the touch pad, unlike the touch screen, is a touch-sensitive area of the device that does not display a visual output. The touch pad is optionally a separate touch-sensitive surface from the touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

[0065] The device 100 also includes a power system 162 that supplies power to various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharge system, a power outage detection circuit, a power converter or inverter, a power status indicator (e.g., light-emitting diode (LED)), and any other components associated with the generation, management, and distribution of power within a portable device.

[0066] Device 100 also optionally includes one or more optical sensors 164. FIG. 1A shows an optical sensor coupled to an optical sensor controller 158 within I / O subsystem 106. Optical sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Optical sensor 164 receives light from the environment projected through one or more lenses and converts that light into data representing an image. Optical sensor 164 cooperates with imaging module 143 (also referred to as a camera module) to optionally capture a still image or a video. In some embodiments, the optical sensor is disposed on the back of device 100 opposite touch screen display 112 on the front of the device, and thus the touch screen display can be used as a viewfinder for acquiring still and / or video images. In some embodiments, the optical sensor is disposed on the front of the device such that the user's image is optionally acquired for a video conference while the user is viewing other video conference participants on the touch screen display. In some embodiments, the position of optical sensor 164 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), and thus a single optical sensor 164 can be used for both video conferencing and for acquiring still and / or video images with the touch screen display.

[0067] Device 100 optionally also includes one or more depth camera sensors 175. FIG. 1A shows a depth camera sensor coupled to a depth camera controller 169 within the I / O subsystem 106. The depth camera sensor 175 receives data from the environment and creates a three-dimensional model of an object (e.g., a face) within the scene from the perspective (e.g., the depth camera sensor). In some embodiments, in cooperation with the imaging module 143 (also referred to as the camera module), the depth camera sensor 175 is optionally used to determine depth maps of different portions of an image captured by the imaging module 143. In some embodiments, while a user is viewing other video conferencing participants on a touch screen display, optionally, an image of the user with depth information is acquired for video conferencing, and a self-portrait image with depth map data is captured. For this purpose, a depth camera sensor is disposed on the front surface of the device 100. In some embodiments, the depth camera sensor 175 is disposed on the back surface of the device, or on both the back and front surfaces of the device 100. In some embodiments, the position of the depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), such that the depth camera sensor 175 is used for video conferencing as well as for acquiring still and / or moving images with the touch screen display.

[0068] Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to an intensity sensor controller 159 within I / O subsystem 106. The contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrokinetic sensors, piezoelectric sensors, optical force sensors, capacitive touch sensing surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of contact on a touch sensing surface). The contact intensity sensor 165 receives contact intensity information (e.g., pressure information, or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is juxtaposed with, or proximate to, a touch sensing surface (e.g., touch sensing display system 112). In some embodiments, at least one contact intensity sensor is disposed on the back of device 100, on the opposite side of touch screen display 112 disposed on the front of device 100.

[0069] Device 100 also optionally includes one or more proximity sensors 166. FIG. 1A shows a proximity sensor 166 coupled to the peripheral device interface 118. Alternatively, the proximity sensor 166 is optionally coupled to an input controller 160 within the I / O subsystem 106. The proximity sensor 166 functions, optionally, as described in U.S. Patent Application Nos. 11 / 241,839, "Proximity Detector In Handheld Device", 11 / 240,788, "Proximity Detector In Handheld Device", 11 / 620,702, "Using Ambient Light Sensor To Augment Proximity Sensor Output", 11 / 586,862, "Automated Response To And Sensing Of User Activity In Portable Devices", and 11 / 638,251, "Methods And Systems For Automatic Configuration Of Peripherals", which are hereby incorporated by reference in their entirety. In some embodiments, when a multifunctional device is placed near the user's ear (e.g., when the user is making a phone call), the proximity sensor turns off and disables the touch screen 112.

[0070] Device 100 also optionally includes one or more haptic output generators 167. FIG. 1A shows a haptic output generator coupled to a haptic feedback controller 161 within I / O subsystem 106. The haptic output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components, and / or electromechanical devices that convert energy, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other haptic output generating components (e.g., components that convert an electrical signal into a haptic output on the device), into linear movement. The contact intensity sensor 165 receives haptic feedback generation instructions from the haptic feedback module 133 and generates a haptic output on device 100 that can be sensed by a user of device 100. In some embodiments, at least one haptic output generator is juxtaposed with, or in proximity to, a touch sensing surface (e.g., touch sensing display system 112), and optionally generates a haptic output by moving the touch sensing surface in a vertical direction (e.g., in / out of the surface of device 100) or in a horizontal direction (e.g., back and forth within the same plane as the surface of device 100). In some embodiments, at least one haptic output generator sensor is disposed on the back of device 100, which is opposite the touch screen display 112 disposed on the front of device 100.

[0071] Device 100 also optionally includes one or more accelerometers 168. FIG. 1A shows an accelerometer 168 coupled to the peripheral device interface 118. Alternatively, the accelerometer 168 is optionally coupled to the input controller 160 within the I / O subsystem 106. The accelerometer 168 functions optionally as described in both of which are hereby incorporated by reference in their entirety, U.S. Patent Application Publication No. 20050190059, "Acceleration-based Theft Detection System for Portable Electronic Devices", and U.S. Patent Application Publication No. 20060017692, "Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer". In some embodiments, information is displayed on the touch screen display in a portrait or landscape display based on analysis of data received from one or more accelerometers. In addition to the accelerometer(s) 168, device 100 optionally includes a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information regarding the location and orientation (e.g., portrait or landscape orientation) of device 100.

[0072] In some embodiments, the software components stored in the memory 102 include an operating system 126, a communication module (or instruction set) 128, a touch / motion module (or instruction set) 130, a graphic module (or instruction set) 132, a text input module (or instruction set) 134, a Global Positioning System (GPS) module (or instruction set) 135, and an application (or instruction set) 136. Further, in some embodiments, the memory 102 (FIG. 1A) or 370 (FIG. 3) stores a device / global internal state 157 as shown in FIGS. 1A and 3. The device / global internal state 157 includes an active application state indicating which application is active if there is a currently active application, a display state indicating which application, view, or other information occupies various regions of the touch screen display 112, a sensor state including information obtained from various sensors and input control devices 116 of the device, and one or more of location information regarding the location and / or orientation of the device.

[0073] The operating system 126 (e.g., an embedded operating system such as Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or VxWorks) includes various software components and / or drivers that control and manage general system tasks (e.g., memory management, storage device control, power management, etc.), and facilitate communication between various hardware components and software components.

[0074] The communication module 128 facilitates communication with other devices via one or more external ports 124 and also includes various software components for processing data received by the RF circuit 108 and / or the external port 124. The external ports 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) are adapted to couple directly or indirectly via a network (e.g., the Internet, a wireless LAN, etc.) to other devices. In some embodiments, the external port is the same as or similar to and / or compatible with the 30-pin connector used on iPod (registered trademark) (trademark of Apple Inc.) devices, and is a multi-pin (e.g., 30-pin) connector.

[0075] The contact / motion module 130 optionally detects contact with the touch screen 112 and other touch-sensitive devices (e.g., a touch pad or a physical click wheel) (in cooperation with the display controller 156). The contact / motion module 130 includes various software components for performing various operations related to the detection of contact, such as determining whether contact has occurred (e.g., detecting a finger-down event), determining the intensity of the contact (e.g., the force or pressure of the contact, or an alternative to the force or pressure of the contact), determining whether there is movement of the contact, tracking movement across the touch-sensitive surface (e.g., detecting one or more events of dragging a finger), and determining whether the contact has ceased (e.g., detecting a finger-up event or an interruption of the contact). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point represented by a series of contact data optionally includes determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point. These operations are optionally applied to a single contact (e.g., contact with one finger) or multiple simultaneous contacts (e.g., "multi-touch" / contact with multiple fingers). In some embodiments, the contact / motion module 130 and the display controller 156 detect contact on the touch pad.

[0076] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by the user (e.g., to determine whether the user has "clicked" on an icon). In some embodiments, at least a subset of the intensity thresholds are determined according to software parameters (e.g., the intensity thresholds can be adjusted without changing the physical hardware of the device 100, rather than being determined by the activation threshold of a particular physical actuator). For example, the mouse "click" threshold of a trackpad or touch screen display can be set to any of a wide range of default thresholds without changing the trackpad or touch screen display hardware. Additionally, in some implementations, the user of the device is provided with software settings to adjust one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds at once by a system-level click "intensity" parameter).

[0077] The contact / motion module 130 optionally detects gesture inputs by the user. Different gestures on the touch-sensing surface have different contact patterns (e.g., the detected movement, timing, and / or intensity of the contact is different). Thus, gestures are optionally detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger down event followed by detecting a finger up (lift-off) event at the same position (or substantially the same position) as the finger down event (e.g., the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensing surface includes detecting a finger down event followed by detecting one or more finger drag events, followed by detecting a finger up (lift-off) event.

[0078] The graphic module 132 includes various known software components for rendering and displaying graphics on the touch screen 112 or other display, including components that change the visual impact of the displayed graphics (e.g., brightness, transparency, saturation, contrast, or other visual properties). As used herein, the term "graphic" includes, but is not limited to, any object that can be displayed to a user, including text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, and the like.

[0079] In some embodiments, the graphic module 132 stores data representing the graphics that will be used. Each graphic is optionally assigned a corresponding code. The graphic module 132 receives from an application, as needed, one or more codes specifying the graphic to be displayed, along with coordinate data and other graphic property data, and then generates the screen image data to be output to the display controller 156.

[0080] The tactile feedback module 133 includes various software components for generating the instructions used by the tactile output generator(s) 167 to generate tactile output at one or more locations on the device 100 in response to the user's interaction with the device 100.

[0081] The text input module 134 is optionally a component of the graphic module 132 and provides a soft keyboard for entering text in various applications (e.g., contacts 137, email 140, IM 141, browser 147, and any other application that requires text input).

[0082] The GPS module 135 determines the location of the device and provides this information for use within various applications (e.g., to the phone 138 for location-based dialing, to the camera 143 as picture / video metadata, and to applications that provide location-based services such as a weather widget, a local yellow pages widget, and a map / navigation widget).

[0083] The application 136 optionally includes the following modules (or sets of instructions) or subsets or supersets thereof. ● Contact module 137 (also sometimes referred to as an address book or contact list) ● Phone module 138 ● Video conferencing module 139 ● Email client module 140 ● Instant messaging (IM) module 141 ● Training support module 142 ● Camera module 143 for still and / or moving images ● Image management module 144 ● Video player module ● Music player module ● Browser module 147 ● Calendar module 148 ● Optionally, a widget module 149 that includes one or more of a weather widget 149-1, a stock price widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5, and other widgets obtained by the user, as well as a user-created widget 149-6 ● Widget creator module 150 for creating the user-created widget 149-6 ● Search module 151 ● A video player and music player module 152 integrating a video player module and a music player module ● A memo module 153 ● A map module 154, and / or ● An online video module 155.

[0084] Examples of other applications 136 optionally stored in the memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-compatible applications, encryption, digital rights management, speech recognition, and speech replication.

[0085] Together with the touch screen 112, the display controller 156, the contact / motion module 130, the graphic module 132, and the text input module 134, the contact module 137 is optionally used to manage an address book or contact list (e.g., stored in the application internal state 192 of the contact module 137 in the memory 102 or the memory 370), which includes adding name(s) to the address book, deleting name(s) from the address book, associating a phone number(s), an email address(es), an address(es), or other information with a name, associating an image with a name, classifying and sorting names, providing a phone number or email address to initiate and / or facilitate communication by phone 138, the video conferencing module 139, email 140, or IM 141, etc.

[0086] The telephone module 138 is used, in cooperation with the RF circuit 108, the audio circuit 110, the speaker 111, the microphone 113, the touch screen 112, the display controller 156, the contact / motion module 130, the graphic module 132, and the text input module 134, optionally, for the input of a series of characters corresponding to a telephone number, access to one or more telephone numbers in the contact module 137, modification of the entered telephone number, dialing of an individual telephone number, execution of a call, and disconnection and call hold at the end of a call. As described above, the wireless communication optionally uses any of a plurality of communication standards, protocols, and technologies.

[0087] The videoconference module 139 includes executable instructions for starting, executing, and ending a videoconference between the user and one or more other participants according to the user's instructions, in cooperation with the RF circuit 108, the audio circuit 110, the speaker 111, the microphone 113, the touch screen 112, the display controller 156, the optical sensor 164, the optical sensor controller 158, the contact / motion module 130, the graphic module 132, the text input module 134, the contact module 137, and the telephone module 138.

[0088] The email client module 140 includes executable instructions for creating, sending, receiving, and managing emails in response to the user's instructions, in cooperation with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphic module 132, and the text input module 134. In cooperation with the image management module 144, the email client module 140 makes it very easy to create and send emails with still or moving images captured by the camera module 143.

[0089] The instant messaging module 141, in cooperation with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, and text input module 134, includes executable instructions for inputting a series of characters corresponding to an instant message, modifying previously input characters, (e.g., using the Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for instant messages based on telephone communication, or XMPP, SIMPLE, or IMPS for instant messages based on the Internet) sending individual instant messages, receiving instant messages, and viewing received instant messages. In some embodiments, the instant messages sent and / or received optionally include graphics, photos, audio files, video files, and / or other attached files as supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both telephone communication-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0090] In cooperation with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, text input module 134, GPS module 135, map module 154, and music player module, the training support module 142 includes executable instructions that create a training (e.g., having time, distance, and / or calorie burn goals), communicate with a training sensor (sports device), receive training sensor data, calibrate sensors used to monitor the training, select and play music for the training, and display, store, and transmit training data.

[0091] The camera module 143 includes executable instructions for capturing still images or videos (including video streams) and storing them in the memory 102, modifying the characteristics of still images or videos, or deleting still images or videos from the memory 102 in cooperation with the touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact / motion module 130, graphic module 132, and image management module 144.

[0092] The image management module 144 includes executable instructions for arranging, modifying (e.g., editing), or otherwise operating on, labeling, deleting, presenting (e.g., in a digital slide show or album), and storing still images and / or video images in cooperation with the touch screen 112, display controller 156, contact / motion module 130, graphic module 132, text input module 134, and camera module 143.

[0093] The browser module 147 includes executable instructions for browsing the Internet according to user instructions, including searching for, linking to, receiving, and displaying a web page or a part thereof, as well as attached files and other files linked to the web page, in cooperation with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphic module 132, and the text input module 134.

[0094] The calendar module 148 includes executable instructions for creating, displaying, modifying, and storing a calendar and data associated with the calendar (e.g., calendar items, to-do lists, etc.) according to user instructions, in cooperation with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphic module 132, the text input module 134, the email client module 140, and the browser module 147.

[0095] The widget module 149 cooperates with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, text input module 134, and browser module 147, and optionally, mini-applications (e.g., weather widget 149-1, stock price widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) that are downloaded and used by the user, or mini-applications created by the user (e.g., user-created widget 149-6). In some embodiments, the widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, the widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! widget).

[0096] The widget creator module 150 cooperates with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, text input module 134, and browser module 147, and is used by the user to optionally create a widget (e.g., make a user-specified portion of a web page into a widget).

[0097] The search module 151 cooperates with the touch screen 112, display controller 156, contact / motion module 130, graphic module 132, and text input module 134, and includes executable instructions for searching for characters, music, sound, images, videos, and / or other files in the memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) according to the user's instructions.

[0098] The video player and music player module 152, in cooperation with the touch screen 112, display controller 156, contact / motion module 130, graphic module 132, audio circuit 110, speaker 111, RF circuit 108, and browser module 147, includes executable instructions that enable a user to download and play recorded music and other sound files stored in one or more file formats such as MP3 or AAC files, and executable instructions for displaying, presenting, or otherwise playing videos (e.g., on the touch screen 112 or on an external display connected via the external port 124). In some embodiments, the device 100 optionally includes the functionality of an MP3 player such as an iPod (a trademark of Apple Inc.).

[0099] The memo module 153, in cooperation with the touch screen 112, display controller 156, contact / motion module 130, graphic module 132, and text input module 134, includes executable instructions for creating and managing memos, to-do lists, etc. according to user instructions.

[0100] The map module 154, in cooperation with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, text input module 134, GPS module 135, and browser module 147, is optionally used to receive, display, modify, and store maps and map-related data (e.g., driving routes, data regarding stores and other attractions near or at a particular location, and other location-based data) according to user instructions.

[0101] The online video module 155 cooperates with the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132, the audio circuit 110, the speaker 111, the RF circuit 108, the text input module 134, the email client module 140, and the browser module 147 to enable a user to access a particular online video, browse a particular online video, receive it (e.g., by streaming and / or downloading), play it (e.g., on the touch screen or on an external display connected via the external port 124), send an email having a link to a particular online video, and perform other management of online videos in one or more file formats such as H.264. In some embodiments, instead of the email client module 140, the instant messaging module 141 is used to send a link to a particular online video. For additional explanation of the online video application, see U.S. Provisional Patent Application No. 60 / 936,562, filed Jun. 20, 2007, "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos", and U.S. Patent Application No. 11 / 968,067, filed Dec. 31, 2007, "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos", the entire contents of which are incorporated herein by reference.

[0102] The modules and applications identified above each correspond to a set of executable instructions that perform one or more of the functions described above and the methods described in this application (e.g., the computer-executed methods and other information processing methods described herein). These modules (e.g., instruction sets) need not be implemented as separate software programs, procedures, or modules, and thus, in various embodiments, various subsets of these modules may optionally be combined or otherwise reconfigured. For example, the video player module may optionally be combined with the music player module to form a single module (e.g., the video player and music player module 152 of FIG. 1A). In some embodiments, the memory 102 optionally stores a subset of the modules and data structures identified above. Further, the memory 102 optionally stores additional modules and data structures not described above.

[0103] In some embodiments, the device 100 is a device in which the operation of a set of default functions in the device is performed only via the touch screen and / or touch pad. By using the touch screen and / or touch pad as the main input control device for the device 100 to operate, the number of physical input control devices (push buttons, dials, etc.) on the device 100 is optionally reduced.

[0104] The set of default functions that are executed only via a touch screen and / or a touch pad optionally includes navigation between user interfaces. In some embodiments, the touch pad, when touched by a user, navigates the device 100 from any user interface displayed on the device 100 to the main menu, the home menu, or the root menu. In such embodiments, the "menu button" is implemented using the touch pad. In some other embodiments, the menu button is a physical push button or other physical input control device rather than a touch pad.

[0105] FIG. 1B is a block diagram showing exemplary components for event processing according to some embodiments. In some embodiments, the memory 102 (FIG. 1A) or 370 (FIG. 3) includes an event sorting unit 170 (e.g., within the operating system 126) and individual applications 136-1 (e.g., any of the foregoing applications 137-151, 155, 380-390).

[0106] The event sorting unit 170 receives event information and determines the application 136-1 to which the event information is to be delivered and the application view 191 of the application 136-1. The event sorting unit 170 includes an event monitor 171 and an event dispatcher module 174. In some embodiments, the application 136-1 includes an application internal state 192 that indicates the current application view(s) displayed on the touch-sensitive display 112 when the application is active or running. In some embodiments, the device / global internal state 157 is used by the event sorting unit 170 to determine which application(s) is / are currently active, and the application internal state 192 is used by the event sorting unit 170 to determine the application view 191 to which the event information is to be delivered.

[0107] In some embodiments, the application internal state 192 includes additional information such as resume information to be used when application 136-1 resumes execution, user interface state information indicating or ready to display the information being displayed by application 136-1, a state queue that enables the user to return to a previous state or view of application 136-1, and a redo / undo queue of previous actions performed by the user, among one or more of the above.

[0108] The event monitor 171 receives event information from the peripheral device interface 118. The event information includes information regarding sub-events (e.g., a user touch as part of a multi-touch gesture on the touch-sensitive display 112). The peripheral device interface 118 transmits information received from the I / O subsystem 106, or sensors such as the proximity sensor 166, the accelerometer(s) 168, and / or the microphone 113 (via the audio circuit 110). The information that the peripheral device interface 118 receives from the I / O subsystem 106 includes information from the touch-sensitive display 112 or a touch-sensitive surface.

[0109] In some embodiments, the event monitor 171 transmits requests to the peripheral device interface 118 at predetermined intervals. In response, the peripheral device interface 118 transmits event information. In other embodiments, the peripheral device interface 118 transmits event information only when there is an important event (e.g., receipt of an input that exceeds a predetermined noise threshold and / or exceeds a predetermined duration).

[0110] In some embodiments, the event sorter 170 also includes a hit view determination module 172 and / or an active event recognition unit determination module 173.

[0111] The hit view determination module 172 provides a software procedure for determining where in one or more views a sub-event occurs when the touch sensing display 112 is displaying two or more views. A view is composed of controls and other elements that a user can view on the display.

[0112] Another aspect of the user interface associated with an application is a set of views, sometimes referred to herein as application views or user interface windows, within which information is displayed and touch-based gestures occur. The application view (of an individual application) in which a touch is detected optionally corresponds to a program level within the program hierarchy or view hierarchy of the application. For example, the lowest level view in which a touch is detected is optionally referred to as the hit view, and the set of events recognized as appropriate input is optionally determined based at least in part on the hit view of the initial touch that initiates the touch-based gesture.

[0113] The hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has a plurality of hierarchically organized views, the hit view determination module 172 identifies the hit view as the lowest level view within the hierarchy in which the sub-event should be processed. In most situations, the hit view is the lowest level view in which the start sub-event (e.g., the first sub-event in a series of sub-events that form an event or potential event) occurs. Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source as the touch or input source identified as the hit view.

[0114] The active event recognition unit determination module 173 determines which view(s) within the view hierarchy should receive a particular series of sub-events. In some embodiments, the active event recognition unit determination module 173 determines that only the hit view should receive a particular series of sub-events. In other embodiments, the active event recognition unit determination module 173 determines that all views including the physical location of the sub-events are views that are actively involved, and thus determines that all views that are actively involved should receive a particular series of sub-events. In other embodiments, even if a touch sub-event is completely limited to an area associated with one particular view, the upper-level views within the hierarchy continue to be views that are actively involved.

[0115] The event dispatcher module 174 dispatches event information to the event recognition unit (e.g., event recognition unit 180). In embodiments including the active event recognition unit determination module 173, the event dispatcher module 174 dispatches event information to the event recognition unit determined by the active event recognition unit determination module 173. In some embodiments, the event dispatcher module 174 stores the event information retrieved by the individual event receiver 182 in the event queue.

[0116] In some embodiments, the operating system 126 includes the event sorter 170. Alternatively, the application 136-1 includes the event sorter 170. In still other embodiments, the event sorter 170 is a stand-alone module or part of another module stored in the memory 102 such as the touch / motion module 130.

[0117] In some embodiments, application 136-1 includes a plurality of event processing units 190 and one or more application views 191, each including instructions to process touch events that occur within an individual view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognition units 180. Typically, an individual application view 191 includes a plurality of event recognition units 180. In other embodiments, one or more of the event recognition units 180 are part of a separate module, such as a user interface kit or a higher-level object from which application 136-1 inherits methods and other properties. In some embodiments, an individual event processing unit 190 includes one or more of event data 179 received from data update unit 176, object update unit 177, GUI update unit 178, and / or event sorting unit 170. The event processing unit 190 optionally utilizes or invokes the data update unit 176, object update unit 177, or GUI update unit 178 to update the internal state 192 of the application. Alternatively, one or more of the application views 191 include one or more individual event processing units 190. Also, in some embodiments, one or more of the data update unit 176, object update unit 177, and GUI update unit 178 are included within an individual application view 191.

[0118] An individual event recognition unit 180 receives event information (e.g., event data 179) from the event sorting unit 170 and identifies an event from the event information. The event recognition unit 180 includes an event receiving unit 182 and an event comparing unit 184. In some embodiments, the event recognition unit 180 also includes at least a subset of metadata 183 and event distribution instructions 188 (optionally including sub-event distribution instructions).

[0119] The event receiving unit 182 receives event information from the event sorting unit 170. The event information includes sub-events, for example, information about a touch or a touch movement. Depending on the sub-event, the event information also includes additional information such as the location of the sub-event. When the sub-event is related to the movement of a touch, the event information also optionally includes the speed and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from portrait to landscape or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the posture of the device).

[0120] The event comparison unit 184 compares the event information with a predefined event or sub-event definition and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, the event comparison unit 184 includes an event definition 186. The event definition 186 includes definitions of events (e.g., a predefined series of sub-events) such as event 1 (187-1) and event 2 (187-2). In some embodiments, the sub-events within an event (187) include, for example, touch start, touch end, touch movement, touch cancel, and multiple touches. In one example, the definition of event 1 (187-1) is a double tap on a display object. The double tap includes, for example, a first touch (touch start) on the display object for a predetermined stage, a first lift-off (touch end) for the predetermined stage, a second touch (touch start) on the display object for the predetermined stage, and a second lift-off (touch end) for the predetermined stage. In another example, the definition of event 2 (187-2) is a drag on a display object. The drag includes, for example, a touch (or contact) on the display object for a predetermined stage, a movement of the touch across the touch-sensitive display 112, and a lift-off of the touch (touch end). In some embodiments, the event also includes information about one or more associated event processing units 190.

[0121] In some embodiments, the event definition 187 includes definitions of events for individual user interface objects. In some embodiments, the event comparison unit 184 performs a hit test to determine which user interface object is associated with the sub - event. For example, within an application view in which three user interface objects are displayed on the touch - sensitive display 112, when a touch is detected on the touch - sensitive display 112, the event comparison unit 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub - event). If each display object is associated with an individual event processing unit 190, the event comparison unit uses the result of the hit test to determine which event processing unit 190 should be activated. For example, the event comparison unit 184 selects the event processing unit associated with the sub - event and object that triggered the hit test.

[0122] In some embodiments, the definition of an individual event 187 also includes a delay action that delays the delivery of event information until it is determined whether a series of sub - events corresponds to the event type of the event recognition unit.

[0123] If the individual event recognition unit 180 determines that a series of sub - events does not match any of the events of the event definition 186, the individual event recognition unit 180 enters an event - impossible, event - failed, or event - ended state, and then ignores the next sub - event of the touch - based gesture. In this situation, if there is another event recognition unit that remains active for the hit view, that event recognition unit continues to track and process the sub - events of the ongoing touch - based gesture.

[0124] In some embodiments, the individual event recognition unit 180 includes metadata 183 having configurable properties, flags, and / or lists indicating how the event distribution system should actively participate in the event recognition unit that should execute sub-event distribution. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists indicating how the event recognition units interact with each other or how they can interact with each other. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists indicating whether sub-events are distributed to various levels in the view hierarchy or program hierarchy.

[0125] In some embodiments, the individual event recognition unit 180 activates the event processing unit 190 associated with the event when one or more specific sub-events of the event are recognized. In some embodiments, the individual event recognition unit 180 distributes the event information associated with the event to the event processing unit 190. Activating the event processing unit 190 is separate from sending (and deferring sending) sub-events to individual hit views. In some embodiments, the event recognition unit 180 sets a flag associated with the recognized event, and the event processing unit 190 associated with the flag captures the flag and executes a predefined process.

[0126] In some embodiments, the event distribution command 188 includes a sub-event distribution command that distributes event information about sub-events without activating the event processing unit. Instead, the sub-event distribution command distributes the event information to the event processing unit associated with a series of sub-events or to the view actively participating in the event. The event processing unit associated with a series of sub-events or the view actively participating in the event receives the event information and executes a predetermined process.

[0127] In some embodiments, the data update unit 176 creates and updates data used in application 136-1. For example, the data update unit 176 updates the phone numbers used in the contact module 137 or stores video files used in the video player module. In some embodiments, the object update unit 177 creates and updates objects used in application 136-1. For example, the object update unit 177 creates a new user interface object or updates the position of a user interface object. The GUI update unit 178 updates the GUI. For example, the GUI update unit 178 prepares display information and sends the display information to the graphic module 132 for display on the touch-sensitive display.

[0128] In some embodiments, the event processing unit(s) 190 includes or has access to the data update unit 176, the object update unit 177, and the GUI update unit 178. In some embodiments, the data update unit 176, the object update unit 177, and the GUI update unit 178 are included in a single module of the individual application 136-1 or the application view 191. In other embodiments, they are included in two or more software modules.

[0129] The foregoing description regarding event processing of user touches on the touch-sensitive display also applies to other forms of user input for operating the multifunctional device 100 using an input device, but it should be understood that not all of them are initiated on the touch screen. For example, the movement of a mouse and the pressing of a mouse button, optionally in conjunction with the pressing or holding of one or more keys on a keyboard, the movement of a contact such as a tap, drag, scroll on a touch pad, a pen stylus input, the movement of the device, a spoken command, a detected eye movement, a biometric input, and / or any combination thereof are optionally utilized as input corresponding to sub-events that define events to be recognized.

[0130] FIG. 2 shows a portable multifunctional device 100 having a touch screen 112, according to some embodiments. The touch screen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment, as well as in other embodiments described below, the user can select one or more of those graphics by performing gestures on the graphics using, for example, one or more fingers 202 (not drawn to scale in the figure) or one or more styli 203 (not drawn to scale in the figure). In some embodiments, the selection of one or more graphics is performed when the user interrupts contact with the one or more graphics. In some embodiments, the gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, upward and / or downward), and / or rolling (from right to left, from left to right, upward and / or downward) of a finger in contact with the device 100. In some implementations or situations, an accidental contact with a graphic does not select the graphic. For example, a swipe gesture that swipes over an application icon does not optionally select the corresponding application if the gesture corresponding to selection is a tap.

[0131] The device 100 also optionally includes one or more physical buttons, such as a "home" button or a menu button 204. As described above, the menu button 204 is optionally used to navigate to any application 136 within a set of applications optionally running on the device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key within a GUI displayed on the touch screen 112.

[0132] In some embodiments, device 100 includes a touch screen 112, a menu button 204, a push button 206 for turning the device on / off and locking the device, volume adjustment button(s) 208, a subscriber identity module (SIM) card slot 210, a headset jack 212, and a docking / charging external port 124. The push button 206 is optionally used to turn the device on / off by pressing the button and holding it pressed for a predefined time interval, to lock the device by pressing the button and releasing it before the predefined time interval has elapsed, and / or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input via a microphone 113 to activate or deactivate some functions. Device 100 optionally also includes one or more contact intensity sensors 165 for detecting the intensity of contact on the touch screen 112 and / or one or more haptic output generators 167 for generating haptic output to the user of device 100.

[0133] FIG. 3 is a block diagram of an exemplary multifunctional device having a display and a touch sensing surface, in accordance with some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a child's learning toy), game system, or a control device (e.g., a home or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more networks or other communication interfaces 360, memory 370, and one or more communication buses 320 that interconnect these components. Communication bus 320 optionally includes circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device 300 includes an input / output (I / O) interface 330 that includes a display 340, which is typically a touch screen display. I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350, a touch pad 355, a haptic output generator 357 that generates haptic outputs on device 300 (e.g., similar to the haptic output generator(s) 167 described above with reference to FIG. 1A), and a sensor 359 (e.g., light, acceleration, proximity, touch sensing, and / or a contact intensity sensor similar to the contact intensity sensor(s) 165 described above with reference to FIG. 1A). Memory 370 includes high speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices, and optionally includes non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 370 optionally includes one or more storage devices remotely located from the CPU(s) 310.In some embodiments, memory 370 stores programs, modules, and data structures similar to, or a subset of, the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A). Further, memory 370 optionally stores additional programs, modules, and data structures that do not exist in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores a drawing module 380, a presentation module 382, a word processing module 384, a website creation module 386, a disk authoring module 388, and / or a spreadsheet module 390, whereas memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

[0134] Each of the elements identified above in FIG. 3 is optionally stored in one or more of the memory devices described above. Each of the modules identified above corresponds to a set of instructions for performing the functions described above. The modules or programs (e.g., sets of instructions) identified above need not be implemented as separate software programs, procedures, or modules, and thus, in various embodiments, various subsets of these modules are optionally combined or otherwise reconfigured. In some embodiments, memory 370 optionally stores a subset of the modules and data structures identified above. Further, memory 370 optionally stores additional modules and data structures not described above.

[0135] Next, optionally direct attention to an embodiment of a user interface, for example, implemented on portable multifunction device 100.

[0136] Figure 4A shows an exemplary user interface of a menu of an application on a portable multifunctional device 100, according to some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, the user interface 400 includes the following elements, or a subset or superset thereof. ● Signal strength indicator(s) 402 for wireless communication(s), such as cellular signal and Wi-Fi signal ● Time 404 ● Bluetooth indicator 405 ● Battery status indicator 406 ● Tray 408 having icons of frequently used applications, such as ○ Icon 416 of the phone module 138, labeled "Phone", optionally including an indicator 414 of the number of missed calls or voicemail messages ○ Icon 418 of the email client module 140, labeled "Mail", optionally including an indicator 410 of the number of unread emails ○ Icon 420 of the browser module 147, labeled "Browser" and ○ Icon 422 for the video player and music player module 152, also referred to as the iPod (trademark of Apple Inc.) module 152, labeled "iPod" and ● Icons of other applications, such as ○ Icon 424 of the IM module 141, labeled "Message" ○ Icon 426 of the calendar module 148, labeled "Calendar" ○ Icon 428 of the image management module 144, labeled "Photos" ○ Icon 430 of the camera module 143, labeled "Camera" ○ Icon 432 of the online video module 155, labeled "Online Video" ○ The icon 434 of the stock price widget 149-2, labeled "Stock Price" ○ The icon 436 of the map module 154, labeled "Map" ○ The icon 438 of the weather widget 149-1, labeled "Weather" ○ The icon 440 of the alarm clock widget 149-4, labeled "Clock" ○ The icon 442 of the training support module 142, labeled "Training Support" ○ The icon 444 of the memo module 153, labeled "Memo", and ○ The icon 446 of the settings application or module, labeled "Settings", which provides access to the settings of the device 100 and its various applications 136.

[0137] Note that the icon labels shown in FIG. 4A are merely illustrative. For example, the icon 422 of the video player and music player module 152 is labeled "Music" or "Music Player". Other labels may optionally be used for the various application icons. In some embodiments, the label for an individual application icon includes the name of the application corresponding to the individual application icon. In some embodiments, the label for a particular application icon is different from the name of the application corresponding to that particular application icon.

[0138] FIG. 4B shows an exemplary user interface on a device (e.g., device 300 of FIG. 3) having a touch sensing surface 451 (e.g., the tablet or touch pad 355 of FIG. 3) separate from the display 450 (e.g., touch screen display 112). The device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of the sensors 359) that detect the intensity of contact on the touch sensing surface 451, and / or one or more haptic output generators 357 that generate haptic output to the user of the device 300.

[0139] Some of the following examples are given with reference to inputs on a touch screen display 112 (where the touch sensing surface and the display are combined), but in some embodiments, the device detects inputs on a touch sensing surface separate from the display, as shown in FIG. 4B. In some embodiments, the touch sensing surface (e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) corresponding to the primary axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). According to these embodiments, the device detects contact (e.g., 460 and 462 in FIG. 4B) with the touch sensing surface 451 at locations (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470) corresponding to each location on the display. In this way, user inputs (e.g., contacts 460 and 462 and their movements) detected by the device on the touch sensing surface (e.g., 451 in FIG. 4B) are used by the device to operate the user interface on the display (e.g., 450 in FIG. 4B) of the multifunctional device when the touch sensing surface is separate from the display. It should be understood that a similar method is optionally used for other user interfaces described herein.

[0140] In addition, while the following examples are given primarily with reference to finger inputs (e.g., finger contact, finger tap gesture, finger swipe gesture), it should be understood that in some embodiments, one or more of the finger inputs may be replaced by inputs from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture may optionally be a mouse click (e.g., instead of a contact) followed by a mouse click that involves movement of the cursor along the path of the swipe (e.g., instead of movement of a contact). As another example, a tap gesture may optionally be a mouse click while the cursor is positioned over the location of the tap gesture (e.g., instead of detecting a contact and then ceasing to detect the contact). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice may optionally be used simultaneously, or mouse and finger contacts may optionally be used simultaneously.

[0141] FIG. 5A shows an exemplary personal electronic device 500. The device 500 includes a body 502. In some embodiments, the device 500 can include some or all of the functions described with respect to devices 100 and 300 (e.g., FIGS. 1A-4B). In some embodiments, the device 500 has a touch-sensitive display screen 504, hereinafter referred to as touch screen 504. Alternatively, or in addition to the touch screen 504, the device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, the touch screen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors that detect the intensity of an applied contact (e.g., a touch). One or more intensity sensors of the touch screen 504 (or touch-sensitive surface) can provide output data representative of the intensity of the touch. The user interface of the device 500 can respond to the touch(es) based on its intensity, which means that touches of different intensities can call different user interface operations on the device 500.

[0142] Exemplary techniques for detecting and processing touch intensity are described, for example, in International Patent Application No. PCT / US2013 / 040061, filed May 8, 2013, published as International Publication No. WO / 2013 / 169849, "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application", and International Patent Application No. PCT / US2013 / 069483, filed Nov. 11, 2013, published as International Publication No. WO / 2014 / 105276, "Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships", each of which is hereby incorporated by reference in its entirety.

[0143] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attaching device 500, for example, to hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, pants, belts, shoes, wallets, backpacks, and the like. These attachment mechanisms enable a user to wear device 500.

[0144] FIG. 5B shows an exemplary personal electronic device 500. In some embodiments, device 500 can include some or all of the components described with respect to FIGS. 1A, 1B, and 3. Device 500 has a bus 512 that operably couples an I / O section 514 to one or more computer processors 516 and a memory 518. The I / O section 514 can be connected to a display 504, and the display 504 can have a touch sensing component 522 and optionally an intensity sensor 524 (e.g., a contact intensity sensor). Additionally, the I / O section 514 can be connected to a communication unit 530 that receives application and operating system data using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and / or other wireless communication technologies. The device 500 can include an input mechanism 506 and / or 508. The input mechanism 506 can optionally be, for example, a rotatable input device or a depressible and rotatable input device. In some examples, the input mechanism 508 can optionally be a button.

[0145] In some examples, the input mechanism 508 can optionally be a microphone. The personal electronic device 500 can optionally include various sensors such as a GPS sensor 532, an accelerometer 534, a direction sensor 540 (e.g., a compass), a gyroscope 536, a motion sensor 538, and / or combinations thereof, all of which can be operably connected to the I / O section 514.

[0146] The memory 518 of the personal electronic device 500 can include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by one or more computer processors 516, can cause, for example, the computer processor to execute the techniques described below, including processes 700-1100 (Figs. 7A-7B, 9A-9B, and 11A-11B). A computer-readable storage media can be any media that tangibly contains or stores computer-executable instructions used by or associated with an instruction execution system, apparatus, or device. In some embodiments, the storage media is a transitory computer-readable storage media. In some embodiments, the storage media is a non-transitory computer-readable storage media. Non-transitory computer-readable storage media can include, but are not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, CDs, DVDs, or optical disks based on Blu-ray technology, and persistent solid-state memories such as flash, solid-state drives. The personal electronic device 500 is not limited to the components and configurations of Fig. 5B and can include other or additional components in a plurality of configurations.

[0147] As used herein, the term "affordance" refers to a user interaction graphical user interface object that is optionally displayed on the display screen of devices 100, 300, and / or 500 (Figs. 1A, 3, and 5A-5B). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) each optionally constitute an affordance.

[0148] As used herein, the term "focus selector" refers to an input element that indicates the current portion of the user interface with which the user is interacting. In some implementations, including a cursor or other location marker, the cursor acts as the "focus selector," and thus while the cursor is positioned over a particular user interface element (e.g., a button, window, slider, or other user interface element), when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., the touchpad 355 of FIG. 3 or the touch-sensitive surface 451 of FIG. 4B), the particular user interface element is adjusted according to the detected input. In some implementations, including a touch screen display (e.g., the touch-sensitive display system 112 of FIG. 1A or the touch screen 112 of FIG. 4A) that enables direct interaction with user interface elements on the touch screen display, the detected contact on the touch screen acts as the "focus selector," and thus when an input (e.g., a press input by contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touch screen display, the particular user interface element is adjusted according to the detected input. In some implementations, the focus is moved from one region of the user interface to another region of the user interface without moving the corresponding cursor or contact on the touch screen display (e.g., by using the tab key or arrow keys to move the focus from one button to another button), and in these implementations, the focus selector moves in accordance with the movement of the focus between different regions of the user interface. Regardless of the specific form taken by the focus selector, the focus selector is generally a user interface element (or a contact on the touch screen display) that is controlled by the user to communicate the user's intended interaction with the user interface (e.g., by indicating to the device the user interface element through which the user intends to interact).For example, the location of a focus selector (e.g., a cursor, contact, or selection box) over an individual button while a press input is detected on a touch-sensing surface (e.g., a touch pad or touch screen) indicates that the user intends to activate that individual button (as opposed to other user interface elements shown on the device's display).

[0149] As used in this specification and the claims, the term "characteristic strength" of a contact refers to a characteristic of that contact based on one or more strengths of the contact. In some embodiments, the characteristic strength is based on a plurality of strength samples. The characteristic strength is optionally based on a set of strength samples collected during a predetermined period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) associated with a predetermined number of strength samples, i.e., a predetermined event (e.g., after detecting the contact, before detecting the lift-off of the contact, before or after detecting the start of movement of the contact, before detecting the end of the contact, before or after detecting an increase in the strength of the contact, and / or before or after detecting a decrease in the strength of the contact). The characteristic strength of a contact is optionally based on one or more of the maximum value of the strength of the contact, the mean value of the strength of the contact, the average value of the strength of the contact, the top 10 percentile value of the strength of the contact, the median value of the strength of the contact, the top 90 percent value of the strength of the contact, etc. In some embodiments, the duration of the contact is used when determining the characteristic strength (e.g., when the characteristic strength is the average of the strength of the contact over time). In some embodiments, the characteristic strength is compared to a set of one or more strength thresholds to determine whether an action has been performed by a user. For example, the set of one or more strength thresholds optionally includes a first strength threshold and a second strength threshold. In this example, a contact having a characteristic strength that does not exceed the first threshold results in a first action, a contact having a characteristic strength that exceeds the first strength threshold but does not exceed the second strength threshold results in a second action, and a contact having a characteristic strength that exceeds the second threshold results in a third action. In some embodiments, the comparison between the characteristic strength and one or more thresholds is not used to determine whether to perform a first action or a second action, but is used to determine whether to perform one or more actions (e.g., whether to perform an individual action or whether to refrain from performing an individual action).

[0150] In some embodiments, for the purpose of determining the characteristic intensity, a part of the gesture is specified. For example, the touch sensing surface optionally receives continuous swipe contacts that transition from a starting location to reach an ending location and where the intensity of the contact increases at that location. In this example, the characteristic intensity of the contact at the ending location is optionally based on only a part of the continuous swipe contact (e.g., only the part of the swipe contact at the ending location) rather than the entire swipe contact. In some embodiments, optionally, a smoothing algorithm is applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of a non - weighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some situations, these smoothing algorithms eliminate narrow spikes or drops in the width of the swipe contact intensity for the purpose of determining the characteristic intensity.

[0151] The intensity of a contact on the touch sensing surface is optionally characterized relative to one or more intensity thresholds such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the light press intensity threshold typically corresponds to the intensity at which the device performs an operation associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold typically corresponds to the intensity at which the device performs an operation different from the operation associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact having a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact detection intensity threshold below which the contact is not detected) is detected, the device moves the focus selector following the movement of the contact on the touch sensing surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise specified, these intensity thresholds are consistent among various sets of user interface values.

[0152] An increase in the characteristic intensity of a contact from an intensity below a light press intensity threshold to an intensity between the light press intensity threshold and a deep press intensity threshold may be referred to as an input of "light press". An increase in the characteristic intensity of a contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold may be referred to as an input of "deep press". An increase in the characteristic intensity of a contact from an intensity below a contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold may be referred to as a detection of a contact on the touch surface. A decrease in the characteristic intensity of a contact from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold may be referred to as a detection of a lift-off of the contact from the touch surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.

[0153] In some embodiments described herein, in response to detecting a gesture that includes an individual press input, or in response to detecting an individual press input performed by an individual contact (or multiple contacts), one or more operations are performed, and the individual press input is detected based at least in part on detecting an increase in the intensity of a contact (or multiple contacts) that exceeds a press input intensity threshold. In some embodiments, an individual operation is performed in response to detecting an increase in the intensity of an individual contact that exceeds the press input intensity threshold (e.g., the "downstroke" of an individual press input). In some embodiments, the press input includes an increase in the intensity of an individual contact that exceeds the press input intensity threshold and a subsequent decrease in the intensity of the contact that is below the press input intensity threshold, and the individual operation is performed in response to detecting a subsequent decrease in the intensity of the individual contact that is below the press input threshold (e.g., the "upstroke" of an individual press input).

[0154] In some embodiments, the device employs intensity hysteresis to avoid spurious inputs sometimes referred to as "jitter", and the device defines or selects a hysteresis intensity threshold having a predefined relationship to the depression input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the depression input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some other appropriate percentage of the depression input intensity threshold). Thus, in some embodiments, a depression input includes an increase in the intensity of an individual contact above the depression input intensity threshold, and a subsequent decrease in the intensity of the contact below the hysteresis intensity threshold corresponding to the depression input intensity threshold, and an individual operation is performed in response to detecting a subsequent decrease in the intensity of an individual contact below the hysteresis intensity threshold (e.g., the "upstroke" of an individual depression input). Similarly, in some embodiments, a depression input is detected only when the device detects an increase in the intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the depression input intensity threshold, and optionally, a subsequent decrease in the intensity of the contact to an intensity below the hysteresis intensity, and an individual operation is performed in response to detecting the depression input (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact, depending on the situation).

[0155] For ease of explanation, the description of an operation performed in response to a depression input associated with a depression input intensity threshold, or a gesture including a depression input, is optionally triggered in response to detecting any of an increase in the intensity of a contact above the depression input intensity threshold, an increase in the intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the depression input intensity threshold, a decrease in the intensity of a contact below the depression input intensity threshold, and / or a decrease in the intensity of a contact below the hysteresis intensity threshold corresponding to the depression input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in the intensity of a contact below the depression input intensity threshold, the operation is optionally performed in response to detecting a decrease in the intensity of a contact corresponding to and below a hysteresis intensity threshold lower than the depression input intensity threshold.

[0156] As used herein, an "installed application" refers to a software application that has been downloaded onto an electronic device (e.g., device 100, 300, and / or 500) and is ready to be launched (e.g., opened) on the device. In some embodiments, the downloaded application becomes an installed application by an installation program that extracts the program portion from the downloaded package and integrates the extracted portion with the operating system of the computer system.

[0157] As used herein, the terms "open application" or "running application" refer to a software application that has retained state information (e.g., as part of device / global internal state 157 and / or application internal state 192). An open or running application is optionally any one of the following types of applications. ● An active application that is currently displayed on the display screen of the device being used by the application ● A background application (or background process) for which one or more processes are being processed by one or more processors, although not currently displayed, and ● An application in an interrupted or suspended state that is stored in memory (volatile and non-volatile, respectively) and has state information that can be used to resume execution of the application.

[0158] As used herein, the term "closed application" refers to a software application that does not have retained state information (e.g., state information for a closed application is not stored in the device's memory). Thus, closing an application includes stopping and / or removing the application process for the application and removing the state information for the application from the device's memory. Generally, opening a second application within a first application does not close the first application. When the second application is being displayed and the display of the first application is aborted, the first application becomes a background application.

[0159] Next, attention is directed to embodiments of a user interface ("UI") and related processes implemented on an electronic device such as the portable multifunctional device 100, device 300, or device 500.

[0160] FIGS. 6A-6AK illustrate exemplary user interfaces involving managed display usage, according to some embodiments. The user interfaces in these figures are used to explain processes described below, including the processes in FIGS. 7A-7B.

[0161] Specifically, FIGS. 6A-6AK illustrate techniques for managing display usage by changing one or more aspects (e.g., visual characteristics) of a displayed user interface when a device determines that it has met a mode transition criterion. In some embodiments, the mode transition criterion is one or more criteria indicating a reduction in user activity or a reduction in user interaction with the electronic device (e.g., a reduction in user activity (physical movement) over a predetermined period, a lack of user input over a predetermined period, detecting a predefined gesture such as a cover gesture on the display in response to a request to transition modes). In some embodiments, detecting that the device has met the criterion includes one or more of receiving data from one or more sensors (e.g., an accelerometer, a gyroscope, a proximity sensor) corresponding to a user gesture (e.g., lowering the wrist, raising the wrist, palm of the hand on the display), receiving data from one or more sensors indicating user activity below a threshold activity level, and determining that a predetermined period has elapsed without detecting user input in one or more input devices (e.g., a touch screen, a rotatable input mechanism, a depressible input mechanism). In some embodiments, the predefined period associated with the mode transition criterion varies depending on how the display of the currently displayed user interface was initiated (e.g., a longer predefined period for a tap input and a shorter predefined period for raising the wrist).

[0162] When it is determined that the mode transition criteria are met, the device transitions from the first mode to the second mode (e.g., a low power mode). In some embodiments, while operating in the second mode, device 600 conserves energy by operating one or more processors of the device at a reduced load, such as by activating (e.g., enabling or turning on) one or more processors of the device at an increased interval (e.g., a reduced rate, a lower frequency) compared to operation in the first mode. In some embodiments, a processor includes hardware (e.g., a microprocessor, etc.). In some embodiments, a processor includes one or more software components (e.g., software modules for performing various functions, modules for displaying information from an application on a display device, modules for processing sensor data received by the device, modules for performing calculations necessary to execute or implement various functions of the device, etc.).

[0163] Among the visual characteristics described below that can be changed when transitioning the device mode, there is the overall luminance of the displayed user interface (e.g., the average pixel luminance (APL) of the pixels constituting the user interface on the display, the average lumen output, the total lumen output, the average illuminance, and / or the total illuminance, luminance expressed in nits, lux, or lumens). To illustrate this, FIGS. 6A-6AK (as well as FIGS. 8A-8AD, FIGS. 10A-10K) include a luminance scale 630 that shows the luminance levels at which each individual user interface is displayed by device 600 on display 602. For example, as represented by the difference between each luminance scale (e.g., the position of the circular indicator for the upper end ("high") and the lower end ("low") of each scale), the clock face user interface 608-1 in FIG. 6I is displayed at a higher luminance level (e.g., higher luminance) than the clock face user interface 608-2 in FIG. 6J.

[0164] Throughout this disclosure, the concept of luminance level also pertains to individual graphical elements or groups of graphical elements (e.g., affordances, graphical elements contained within affordances, complications, clock face elements, backgrounds, indicators, etc.) included in various clock face user interfaces displayed by device 600 on display 602. Similar to the luminance level of the clock face user interface, the luminance level of graphical elements as displayed within the clock face user interface on display 602 can also be varied (e.g., using techniques described later). However, as shown throughout the drawings described later, luminance scale 630 reflects the overall luminance level of an individual clock face user interface (e.g., not the luminance level of the entire displayed clock face user interface, individual graphical elements, or groups of graphical elements within an individual clock face user interface), unless otherwise noted. Further, luminance scale 630 is not part of any user interface displayed on device 600.

[0165] In addition to luminance scale 630, the relative display luminance of the clock face user interfaces and elements (e.g., graphical objects, backgrounds, etc.) that make up the clock face user interfaces described later is also represented by the shading intensity depicted in each figure (e.g., white or lighter gray to indicate more brightly displayed elements, darker gray to indicate more darkly displayed elements).

[0166] In some embodiments, the luminance level can be adjusted (increased or decreased) using alpha blending. In some embodiments, decreasing the luminance level involves using alpha blending without changing the backlight of the electronic device to generate a simulated or actual backlight level. For example, the device can use a gradually opaque black masking layer to alpha blend the image data representing the clock face user interface (or a part of the clock face user interface such as an affordance or complication), thereby gradually darkening the clock face user interface as displayed on the screen (e.g., causing the user interface to fade to black).

[0167] In some embodiments, the luminance level of a graphical object within the clock face user interface is changed by changing the shape or configuration of the graphical object itself. For example, the luminance of a white clock hand can be decreased by reducing the thickness of the clock hand (e.g., removing white pixels from the element). In some embodiments, the luminance level of a graphical object is changed (e.g., reduced or darkened) by replacing the solid-color area of the object with a contour colored the same as the solid-color area. In some embodiments, the luminance level of a graphical object is reduced or darkened by changing its color, e.g., by replacing a lighter color (e.g., white, light gray, yellow, etc.) with a darker color (black, dark gray, blue, etc.). Any combination of the above-described luminance change techniques or similar techniques well-known in the art may be used to adjust the luminance levels of the graphical objects and the clock face user interface according to the embodiments described below.

[0168] Generally, different brightness levels can be achieved using various techniques that can be used separately or simultaneously. In some embodiments, the brightness level of a graphical element is changed by changing (e.g., brightening or darkening) the brightness of some (or all) of the pixels of the graphical element. In some embodiments, the brightness level of a graphical element is changed by making the lines of the graphical element thinner (or thicker), removing (or adding) the background of the graphical element, reducing (or enlarging) the size of the graphical element, etc., so that fewer (or more) pixels are lit, by changing the graphical element.

[0169] Referring now to FIG. 6A, device 600 includes a display 602, a rotatable and depressible input mechanism 604 (e.g., rotatable and depressible with respect to the housing or frame of device 600), and a button 606. In embodiments described below, device 600 is a wearable device such as a smartwatch. In some embodiments, device 600 is another computing system including a smartphone, a tablet, or a display device (e.g., a display screen, a projection device, etc.). In some embodiments, device 600 includes one or more features of device 100, 300, or 500.

[0170] FIGS. 6A-6J illustrate an exemplary scenario including a timer application running on device 600. In FIG. 6A, while operating in a standard display mode (e.g., a high power consumption display mode), device 600 displays a timer selection user interface 608 (e.g., a high power consumption user interface) at a standard display brightness level on display 602. In some embodiments, while device 600 continues to operate in the standard display mode, the brightness level of the standard display mode is reduced in response to detecting a reduction in the ambient light level by one or more sensors of device 600 (e.g., a lower ambient light level results in a lower display brightness level and device 600 remains in the standard display mode).

[0171] As shown in FIG. 6A, the timer selection user interface 608 includes selectable timer user interface objects 610A to 610D. Each selectable timer user interface object 610A to 610D corresponds to an individual duration (for example, object 610A corresponds to 1 minute, object 610B corresponds to 3 minutes, object 610C corresponds to 5 minutes, and object 610D corresponds to 10 minutes). Each selectable timer user interface object 610A to 610D is selectable to cause the device 600 to start a countdown timer within the timer application, and the countdown timer has a duration equal to the duration associated with the selected object.

[0172] In FIG. 6A, while the timer selection user interface 608 is being displayed, device 600 detects an input 612 (e.g., a tap input and / or a non-tap input) at a location corresponding to a selectable timer user interface object 610B. In FIG. 6B, in response to the detection of input 612, device 600 stops displaying the timer selection user interface 608 and displays the timer user interface 614-1. In FIG. 6B, device 600 continues to operate in a standard display mode (e.g., a high power consumption display mode) and displays the timer user interface 614-1 (e.g., a high power consumption user interface) on display 602 at a standard display brightness level. As shown in FIG. 6B, the timer user interface 614-1 includes a plurality of affordances including a timer indication 616-1, a cancel button 618-1, and a pause button 620-1. The timer indication 616-1 indicates how much time remains on the countdown timer. In FIG. 6B, the timer indication 616-1 indicates that 2 minutes and 59 seconds remain. The cancel button 618-1 is selectable to cancel the countdown timer. The pause button 620-1 is selectable to pause the countdown timer. In some embodiments, when the pause button 620-1 is selected, device 600 replaces the pause button 620-1 with a resume button that is selectable to resume the countdown timer.

[0173] In FIG. 6B, while the device 600 is operating in the standard display mode, the device 600 periodically updates the timer indication 616-1 at a first update frequency (e.g., more than twice per second, every half second, every tenth of a second, and / or every hundredth of a second) (e.g., updates the timer user interface 614-1 and / or updates one or more elements of the timer user interface 614-1). In some embodiments, while the device 600 is operating in the standard display mode, the device 600 also periodically updates other elements of the timer user interface 614-1 (e.g., the cancel button 618-1 and / or the pause button 620-1) at the first update frequency. In some embodiments, while the device 600 is operating in the standard display mode, the device 600 periodically updates other elements of the timer user interface 614-1 (e.g., the cancel button 618-1 and / or the pause button 620-1) at an update frequency different from that of the timer indication 616-1.

[0174] FIG. 6C shows the device 600 after determining that one or more mode transition criteria are met (e.g., detecting a gesture of lowering the wrist using a motion sensor and / or no specific type of input over a threshold duration) and accordingly transitioning from the standard display mode to the low-power display mode (e.g., from a high-power consumption mode to a low-power consumption mode). In some embodiments, after determining that one or more mode transition criteria are met, the device 600 displays an animation (e.g., a series of frames or images) showing the high-power consumption user interface (e.g., the timer user interface 614-1) changing to a lower-power consumption user interface (e.g., the timer user interface 614-2). In some embodiments, the device 600 displays a plurality of animation frames (e.g., a transition interface) while operating in a transition state between device modes (e.g., the standard power display mode and the low-power display mode).

[0175] In FIG. 6C, while operating in the low power display mode, device 600 displays a timer user interface 614-2 (e.g., a user interface with lower power consumption) of the clock on display 602. The timer user interface 614-2 is displayed at a lower luminance level than the timer user interface 614-1 (e.g., the average of the overall luminance levels or luminance values of the pixels constituting the timer user interface 614-2 on display 602 is lower than the luminance level of the timer user interface 614-1 on display 602 as shown in FIG. 6B). In some embodiments, the timer user interface 614-2 is displayed at a fixed percentage of the luminance level at which device 600 displays the timer user interface 614-1. In some embodiments, the timer user interface 614-2 of the clock is displayed at a luminance level that is at least partially based on the ambient light level detected by one or more sensors of device 600 (e.g., during the low power display mode, a higher ambient light level results in a higher luminance level).

[0176] The corresponding elements within the timer user interface 614-2 are displayed by device 600 differently from those previously displayed within the timer user interface 614-1. In FIG. 6C, the timer indication 616-2 is displayed at a lower luminance level (e.g., in a darker color) than where the timer indication 616-1 was displayed (e.g., the timer indication 616-2 is displayed in gray and the timer indication 616-1 was displayed in white). Similarly, the cancel button 618-2 and the pause button 620-2 are also displayed in a color different from (e.g., darker than) the color in which the cancel button 618-1 and the pause button 620-1 were previously displayed.

[0177] In some embodiments, the change in luminance level between corresponding elements (e.g., affordances and / or objects) within timer user interfaces 614-1 and 614-2 is not uniform (e.g., the timer indication 616-1 changes from white to a first color within the timer indication 616-2, and the button 618-1 changes from white to a second different color within the button 618-2). In some embodiments, device 600 displays one or more elements within timer user interface 614-2 in a reduced size compared to corresponding elements within timer user interface 614-1.

[0178] In addition to displaying the timer indication 616-2 at a lower luminance level, device 600 displays the timer indication 616-2 at a lower level of accuracy (e.g., a lower level of precision) than the timer indication 616-1. As shown in FIG. 6B, the timer indication 616-1 was previously shown at a first level of accuracy (e.g., in FIG. 6B, in minutes and seconds). In FIG. 6C, the timer indication 616-2 is shown at a second level of accuracy that is not as accurate as the first level of accuracy (e.g., in minutes). In FIG. 6C, there are 2 minutes and 38 seconds remaining on the countdown timer, but the timer indication 616-2 is shown as 2 minutes (e.g., rounded down to 2 minutes or only the minute value is displayed).

[0179] Furthermore, as described above, while the device 600 was operating in the standard display mode, the device 600 periodically updated the timer indication 616-1 at a first update frequency. In FIG. 6C, while the device 600 is operating in the low-power display mode, the device 600 periodically updates the timer indication 616-2 at a second update frequency that is lower than the first update frequency (e.g., the second update frequency corresponds to an update at a frequency lower than the first update frequency) (e.g., every 10 seconds, every 30 seconds, and / or every 1 minute). In some embodiments, while the device 600 is operating in the low-power display mode, the device 600 also periodically updates other elements of the timer user interface 614-2 (e.g., the cancel button 618-2 and / or the pause button 620-2) at the second update frequency. In some embodiments, while the device 600 is operating in the low-power display mode, the device 600 periodically updates other elements of the timer user interface 614-2 (e.g., the cancel button 618-2 and / or the pause button 620-2) at an update frequency different from that of the timer indication 616-2. Updating the timer indication 616-2 at a reduced frequency while the device 600 is operating in the low-power display mode further reduces the power consumption in the low-power display mode.

[0180] In FIG. 6C, while operating in the low-power display mode and displaying the timer user interface 614-2, the device 600 detects an input 622 (e.g., a tap input and / or a non-tap input).

[0181] In FIG. 6D, in response to detecting the input 622, the device 600 transitions from the low-power display mode to the standard display mode and replaces the display of the timer user interface 614-2 with the timer user interface 614-1. The timer user interface 614-1 is displayed at a higher luminance level than the timer user interface 614-2 (e.g., the overall luminance level or the average of the luminance values of the pixels constituting the timer user interface 614-1 on the display 602 is greater than the luminance level of the timer user interface 614-2 on the display 602 as shown in FIG. 6C). For example, the timer indication 616-1, the cancel button 618-1, and the pause button 620-1 are displayed at a higher luminance level (e.g., displayed in a brighter color) than the corresponding elements (e.g., the timer indication 616-2, the cancel button 618-2, the pause button 620-1) within the timer user interface 614-2. Also, it can be seen that the timer indication 616-1 is displayed at a first accuracy level (e.g., seconds), which is higher than the second accuracy level applied when displaying the timer indication 616-2 (e.g., minutes). In FIG. 6D, the device 600 periodically updates the timer indication 616-1 at a first update frequency that is higher than the second update frequency.

[0182] Figure 6E shows device 600 after transitioning from the standard display mode to the low power display mode in response to determining that one or more mode transition criteria have been met (e.g., detecting a gesture of lowering the wrist using a motion sensor and / or no input of a particular type over a threshold duration). In Figure 6E, in response to determining that one or more mode transition criteria have been met, device 600 replaces the display of timer user interface 614-1 with timer user interface 614-2. As described above, while device 600 is operating in the low power display mode, device 600 displays timer indication 616-2 at a second accuracy level that is not as accurate as the first accuracy level applied when displaying timer indication 616-1, and periodically updates timer indication 616-2 at a second update frequency that is lower than the first update frequency.

[0183] In Figure 6F, device 600 periodically updates timer indication 616-2 according to the second update frequency. In the illustrated example, the second update frequency is 25 seconds. From Figure 6E to Figure 6F, 25 seconds have elapsed, and in Figure 6F, 1 minute and 57 seconds remain on the countdown timer. Accordingly, device 600 updates timer indication 616-2 to display "1M". The next update of timer indication 616-2 occurs when 1 minute and 32 seconds remain on the countdown timer. However, since 1 minute and 32 seconds still remain, timer indication 616-2 continues to display "1M". The next update of timer indication 616-2 occurs when 1 minute and 7 seconds remain on the countdown timer. Here too, since there is still a time remaining between 1 minute and 2 minutes, timer indication 616-2 continues to display "1M".

[0184] In some embodiments, while the device 600 is operating in the low-power mode, user interface objects such as the timer indication 616-2 are updated at different update frequencies based on whether one or more time-dependent update criteria are met. For example, in FIGS. 6E and 6F, the time-dependent update criteria are not met, and the device 600 periodically updates the timer indication 616-2 at a second update frequency. However, as described below with reference to FIG. 6G, in some embodiments, when one or more time-dependent update criteria are met, the device 600 periodically updates the timer indication 616-2 at a third update frequency that is higher (e.g., more frequent) than the second update frequency while continuing to operate in the low-power display mode.

[0185] FIG. 6G shows the device 600 after it has been determined that one or more time-dependent update criteria have been met while the device 600 is operating in the low-power display mode. In FIG. 6G, the one or more time-dependent update criteria include a criterion that is met when the time remaining on the countdown timer is less than a threshold amount (e.g., less than 1 minute remaining). In response to determining that one or more time-dependent update criteria have been met, the device 600 periodically updates the timer indication 616-2 at a third update frequency that is higher than the second update frequency (e.g., more than twice per second, once per second, once every half second, and / or once every tenth of a second). In some embodiments, the third update frequency is equal to the first update frequency. In some embodiments, the third update frequency is lower than the first update frequency.

[0186] In FIG. 6G, in response to determining that one or more time-dependent update criteria have been met while the device 600 is operating in the low-power mode, the device 600 also displays the timer indication 616-2 at a third accuracy level (e.g., in minutes and seconds) that is more accurate than the second accuracy level (e.g., in minutes). In the illustrated embodiment, the third accuracy level is the same as the first accuracy level utilized while the device 600 is in the standard display mode. In FIG. 6G, the timer indication 616-2 indicates that 59 seconds remain on the countdown timer.

[0187] In FIG. 6H, the device 600 continues to periodically update the timer indication 616-2 at a third update frequency (e.g., because one or more time-dependent update criteria continue to be met). In FIG. 6H, the device 600 updates the timer indication 616-2 to indicate that 58 seconds remain on the countdown timer.

[0188] When one or more time-dependent update criteria are met, by increasing the update frequency of the timer indication 616-2 (e.g., from a second update frequency to a third update frequency), the device 600 can conserve power with a lower frequency of updates when frequent updates are not required (e.g., when more than one minute remains in the timer, updating once every 25 seconds), and can also provide more useful information and / or a higher level of accuracy by increasing the frequency of updates in more time-dependent scenarios (e.g., updating once every half second in the last minute of the timer). In some embodiments, one or more elements of the timer application and / or the timer user interface 614-2 are updated at a frequency higher than the second update frequency (e.g., at a first update frequency, at a third update frequency, and / or at a different update frequency), and the timer indication 616-2 is updated at the second update frequency. For example, in some embodiments, one or more elements of the timer application and / or the timer user interface 614-2 are updated at a frequency higher than the second update frequency when less than two minutes remain on the timer and / or throughout all periods (e.g., the timer indication 616-2 is updated at the second update frequency throughout all periods except when less than one minute remains on the timer).

[0189] In FIG. 6H, while the timer user interface 614-2 is being displayed and while operating in the low power display mode, the device 600 detects an input 624 (e.g., a depression of the rotatable and depressible input mechanism 604). In FIG. 6I, in response to detecting the input 624, the device 600 transitions from the low power display mode to the standard display mode. Additionally, in response to detecting the input 624, the device 600 replaces the display of the timer plus user interface 614-2 with the clock face user interface 626-1. In FIG. 6I, while the clock face user interface 626-1 is being displayed in the foreground, the timer application continues to execute in the background. Further details regarding the clock face user interface 626-1 are described below with reference to the clock face user interfaces 650-1 and 650-2 of FIGS. 6P-6V.

[0190] FIG. 6J shows the device 600 after transitioning from the standard display mode to the low power display mode in response to determining that one or more mode transition criteria have been met (e.g., detecting a gesture of lowering the wrist using a motion sensor and / or no input of a particular type over a threshold duration). In FIG. 6J, in response to determining that one or more mode transition criteria have been met, the device 600 replaces the display of the clock face user interface 626-1 (e.g., a higher power consumption user interface) with the clock face user interface 626-2 (e.g., a lower power consumption user interface). The clock face user interface 626-2 is displayed at a lower luminance level than the clock face user interface 626-1, as described above with reference to the timer user interfaces 614-1 and 614-2.

[0191] In FIG. 6J, while the device 600 is operating in the low-power display mode, the countdown timer continues to operate and still has less than one minute remaining. However, in some embodiments, including the illustrated embodiment, one or more time-dependent update criteria are met when an application that is in a time-dependent situation (in this case, the timer application) is a foreground application, and are not met when the application is not in the foreground (e.g., in the background). In the scenario shown in FIG. 6J, although the timer application has less than one minute remaining on the countdown timer, since the timer application is in the background, one or more time-dependent update criteria are not met, and the display 602 is not updated at the third update frequency (e.g., is updated at an update frequency lower than the third update frequency (e.g., the second update frequency)).

[0192] FIGS. 6K-6X illustrate exemplary scenarios including a stopwatch application executed on the device 600. In FIG. 6K, while operating in the standard display mode (e.g., high-power consumption display mode), the device 600 displays a stopwatch user interface 632-1 (e.g., a high-power consumption user interface) on the display 602 at a standard luminance level. As shown in FIG. 6K, the stopwatch user interface 632-1 includes an elapsed time indication 634-1, a lap button 636-1, and a start button 638-1. The elapsed time indication 634-1 indicates the amount of time that has elapsed since the stopwatch was started (e.g., how much time has elapsed since a user input was received on the start button 638-1). The lap button 636-1 is selectable to record the stopwatch time that has elapsed when the lap button 636-1 is selected (e.g., while continuing to operate the stopwatch). The start button 638-1 is selectable to start the stopwatch.

[0193] In some embodiments, while the device 600 is operating in the standard display mode, the device 600 periodically updates one or more elements of the stopwatch user interface 632-1 (e.g., the elapsed time indication 634-1) at a first update frequency (e.g., more than twice per second, per 1 / 100 second, and / or per 1 / 20 second). In addition, while the device 600 is operating in the standard display mode, the device 600 displays the elapsed time indication 634-1 at a first accuracy level. In FIG. 6L, the first accuracy level is 1 / 100 second.

[0194] In FIG. 6K, the device 600 detects an input 640 (e.g., a tap input and / or a non-tap input) at a location corresponding to the start button 638-1. In response to the detection of the input 640, the device 600 starts the stopwatch, and the elapsed time indication 634-1 displays the elapsed time.

[0195] In FIG. 6L, the device 600 continues to operate in the standard display mode and continues to display the stopwatch user interface 632-1 at the standard brightness level. In FIG. 6L, in response to detecting the input 640, the device 600 replaces the start button 638-1 with the stop button 642-1. In FIG. 6L, as indicated by the elapsed time indication 634-1, 4.14 seconds have elapsed since the stopwatch was started (e.g., since the device 600 detected the input 640).

[0196] In FIG. 6L, device 600 detects an input 644 (e.g., a tap input and / or a non-tap input) at a location corresponding to lap button 636-1. In FIG. 6M, in response to detecting input 644, device 600 displays a lap time indication 646-1 within stopwatch user interface 632-1. Lap time indication 646-1 indicates that a user input was received on lap button 636-1 when 4.14 seconds had elapsed on the stopwatch. In FIG. 6M, elapsed time indication 634-1 indicates that 7.02 seconds have elapsed since the stopwatch was started.

[0197] FIG. 6N shows device 600 after determining that one or more mode transition criteria have been met and, in response thereto, transitioning from a standard display mode to a low power display mode (e.g., from a higher power consumption mode to a lower power consumption mode).

[0198] In FIG. 6N, while operating in the low power display mode, in response to determining that one or more mode transition criteria have been met, device 600 stops displaying stopwatch user interface 632-1 and displays stopwatch user interface 632-2 (e.g., a lower power consumption user interface) on display 602 (e.g., replaces the display of stopwatch user interface 632-1 with stopwatch user interface 632-2). Stopwatch user interface 632-2 is displayed at a lower luminance level than stopwatch user interface 632-1. In some embodiments, stopwatch user interface 632-2 is displayed at a fixed percentage of the luminance level at which device 600 displays stopwatch user interface 632-1. In some embodiments, stopwatch user interface 632-2 is displayed at a luminance level that is at least partially based on the ambient light level detected by one or more sensors of device 600 (e.g., during the low power display mode, a higher ambient light level results in a higher luminance level).

[0199] As described above, the corresponding elements within the stopwatch user interface 632-2 are displayed by the device 600 differently from those previously displayed within the stopwatch user interface 632-1. In FIG. 6N, the elapsed time indication 634-2 is displayed at a lower luminance level (e.g., in a darker color) than the elapsed time indication 634-1 was displayed (e.g., the elapsed time indication 634-2 is displayed in gray and the elapsed time indication 634-1 is displayed in white). Similarly, the lap button 636-2 and the stop button 642-2 are also displayed at a lower luminance level than the lap button 636-1 and the stop button 642-1 were previously displayed.

[0200] In some embodiments, the change in luminance level between corresponding elements (e.g., affordances and / or objects) within the stopwatch user interfaces 632-1 and 632-2 is not uniform. In some embodiments, one or more elements within the stopwatch user interface 632-2 are displayed in a reduced size compared to the corresponding elements within the stopwatch user interface 632-1.

[0201] While the device 600 was operating in the standard display mode, the device 600 periodically updated the elapsed time indication 634-1 at a first update frequency (e.g., more than twice per second, every 1 / 100th of a second, and / or every 1 / 20th of a second). As described above with reference to FIGS. 6A-6J, in some embodiments, the update frequency while the device 600 is operating in the low power display mode depends on whether one or more time-dependent update criteria are met. If one or more time-dependent update criteria are not met, the device 600 periodically updates the elapsed time indication 634-2 at a second update frequency lower than the first update frequency (e.g., once per minute, once every 30 seconds, and / or once every 10 seconds) (e.g., updating the stopwatch user interface 632-2 and / or one or more elements of the stopwatch user interface 632-2). If one or more time-dependent update criteria are met, the device 600 periodically updates the elapsed time indication 634-2 at a third update frequency higher than the second update frequency (e.g., once per second and / or once every half second) (e.g., updating the stopwatch user interface 632-2 and / or one or more elements of the stopwatch user interface 632-2). In some embodiments, the third update frequency is higher than the second update frequency and lower than the first update frequency. In some embodiments, the third update frequency is equal to the first update frequency.

[0202] Further, in some embodiments, as described above with reference to FIGS. 6A-6J, when device 600 is operating in the low-power display mode, elapsed time indication 634-2 is displayed at different accuracy levels based on whether one or more time-dependent update criteria are met. If one or more time-dependent update criteria are not met, device 600 displays elapsed time indication 634-2 at a second accuracy level that is less accurate than the first accuracy level applied while device 600 was operating in the standard display mode. If one or more time-dependent update criteria are met, device 600 displays elapsed time indication 634-2 at a third accuracy level that is more accurate than the second accuracy level. In some embodiments, the third accuracy level is more accurate than the second accuracy level and less accurate than the first accuracy level. In some embodiments, the third accuracy level is equal to the first accuracy level.

[0203] In the exemplary scenarios shown in FIGS. 6K-6X, the one or more time-dependent update criteria include criteria that are met when device 600 is operating in the low-power mode and less than a threshold amount of time has elapsed in a stopwatch application (e.g., less than one minute of elapsed time has been measured by the stopwatch application).

[0204] In FIG. 6N, device 600 is operating in the low-power mode and less than one minute has elapsed in the stopwatch application. Accordingly, device 600 displays elapsed time indication 634-2 at a third accuracy level (e.g., seconds) and periodically updates elapsed time indication 634-2 at a third update frequency (e.g., once per second, once every half second, and / or once every tenth of a second). In the illustrated example, the third update frequency is lower than the first update frequency but higher than the second update frequency.

[0205] In the illustrated embodiment, certain non-static content within the stopwatch user interface 632-2, such as the elapsed time indication 634-2, is presented at a lower level of accuracy compared to the stopwatch user interface 632-1 (e.g., presented at a lower level of accuracy when the device 600 is in the low power display mode than when the device 600 is in the standard display mode), while static content is presented at the same level of accuracy as the stopwatch user interface 632-1 (e.g., static content is presented at the same level of accuracy regardless of whether the device 600 is in the low power display mode or the standard display mode). For example, the lap time indication 646-2 is presented at the same level of accuracy as the lap time indication 646-1 (e.g., the lap time is presented in 1 / 100 of a second).

[0206] In FIG. 6O, the device 600 continues to operate in the low power display mode and continues to display the stopwatch user interface 632-2. In FIG. 6O, the stopwatch timer has elapsed 21.26 seconds. In FIG. 6O, in response to one or more time-dependent update criteria being met, the device 600 displays the elapsed time indication 634-2 at a third level of accuracy (e.g., rounded to the nearest second), and also periodically updates the elapsed time indication 634-2 at a third update frequency (e.g., every 1 second, every 1 / 2 second, and / or every 1 / 10 second).

[0207] In FIG. 6O, while operating in the low power display mode and displaying the stopwatch user interface 632-2, the device 600 detects an input 648 (e.g., a depression of the rotatable and depressable input mechanism 604). In FIG. 6P, in response to the input 648, the device 600 transitions from the low power display mode to the standard display mode and replaces the display of the stopwatch user interface 632-2 with the clock face user interface 650-1. In FIG. 6P, the stopwatch application continues to execute and the elapsed time is shown in the stopwatch complication 658-1.

[0208] As shown in FIG. 6P, the clock face user interface 650-1 (e.g., a user interface with higher power consumption) displayed while the device 600 is operating in the standard display mode includes an analog time indication 665-1 (e.g., a representation of the hands of an analog clock that displays the current hour, minute, and second values) and a plurality of affordances (e.g., clock face complications). In some embodiments, each affordance is associated with an application on the device 600 (e.g., selecting the affordance launches the associated application and / or the affordance displays information from the associated application). In FIG. 6P, the affordances include a battery level complication 652-1, a compass complication 654-1, a message complication 656-1, a stopwatch complication 658-1, a calendar complication 660-1, a heart rate complication 662-1, a solar complication 664-1, and a solar system complication 666-1. In the illustrated embodiment, based on the device 600 operating in the standard display mode, the device 600 displays the stopwatch complication 658-1 at a first accuracy level (e.g., up to 1 / 100 of a second) and periodically updates the stopwatch complication 658-1 at a first update frequency.

[0209] Figure 6Q shows device 600 after determining that one or more mode transition criteria are met and transitioning accordingly from a standard display mode to a low power display mode (e.g., from a high power consumption mode to a low power consumption mode). In Figure 6Q, while operating in the low power display mode, device 600 displays a clock face user interface 650-2 (e.g., a lower power consumption user interface) on display 602. The clock face user interface 650-2 is displayed at a lower luminance level than the clock face user interface 650-1. The clock face user interface 650-2 includes an analog time indication 665-2, which is a low power version of the analog time indication 665-1. The clock face user interface 650-2 also includes a plurality of affordances (e.g., battery level complication 652-2, compass complication 654-2, message complication 656-2, stopwatch complication 658-2, calendar complication 660-2, heart rate complication 662-2, solar complication 664-2, and solar system complication 666-2), which correspond to the plurality of affordances within the clock face user interface 650-1 and represent low power display mode versions of these affordances.

[0210] The stopwatch complication 658-2 is displayed at a lower luminance level than the stopwatch complication 658-1. In Figure 6Q, device 600 is operating in the low power display mode and the stopwatch application is measuring an elapsed time of less than one minute. Accordingly, another time-dependent update criterion is met. In accordance with this determination, device 600 displays the stopwatch complication 658-2 at a third accuracy level (e.g., seconds) and periodically updates the stopwatch complication 658-2 at a third update frequency (e.g., every half second and / or every second).

[0211] In FIG. 6R, the device 600 continues to operate in the low power display mode and continues to display the clock face user interface 650-2. In FIG. 6R, the stopwatch timer has elapsed 38.94 seconds. One or more time-dependent update criteria continue to be met. Accordingly, the device 600 displays the stopwatch complication 658-2 at a third accuracy level (e.g., seconds) indicating that 38 seconds have elapsed and periodically updates the stopwatch complication 658-2 at a third update frequency (e.g., every half second and / or every second).

[0212] In FIG. 6S, the stopwatch timer has elapsed 1 minute. Accordingly, the time-dependent update criteria are no longer met. In response to this determination, the device 600 stops updating the stopwatch complication 658-2 at the third update frequency and begins updating the stopwatch complication 658-2 at a second update frequency lower than the third update frequency (e.g., every 30 seconds and / or every minute). In the illustrated embodiment, the second update frequency is 1 minute. Further, since the time-dependent update criteria are no longer met, the device 600 stops displaying the stopwatch complication 658-2 at the third accuracy level (e.g., in seconds) and displays the stopwatch complication 658-2 at the second accuracy level (e.g., in minutes).

[0213] In FIG. 6T, 35 seconds have elapsed from FIG. 6S such that an elapsed time of 1 minute and 35 seconds is measured by the stopwatch application. However, since the device 600 updates the stopwatch complication 658-2 once per minute and the stopwatch complication 658-2 is displayed at the second accuracy level (e.g., in minutes), the stopwatch complication 658-2 continues to display "1 minute".

[0214] In FIG. 6U, the stopwatch application has measured an elapsed time of 2 minutes, 25 seconds have elapsed since FIG. 6T, and 1 minute has elapsed since the last update of the stopwatch complication 568-2 (e.g., FIG. 6S). Accordingly, the device 600 updates the stopwatch complication 658-2 to display "2 minutes".

[0215] In FIG. 6V, 9 seconds have elapsed since FIG. 6U, and an elapsed time of 2 minutes and 9 seconds is being measured by the stopwatch application. However, since the device 600 updates the stopwatch complication 658-2 once per minute and the stopwatch complication 658-2 is displayed at a second accuracy level (e.g., in minutes), the stopwatch complication 658-2 continues to display "2 minutes".

[0216] In FIG. 6V, while displaying the clock face user interface 650-2, the device 600 detects an input 668 at the location corresponding to the stopwatch complication 658-2.

[0217] In FIG. 6W, in response to detecting the input 668, the device 600 transitions from the low power display mode to the standard display mode and replaces the display of the clock face user interface 650-2 with the stopwatch user interface 632-1. As described above, while the device 600 is operating in the standard display mode, the device 600 displays the elapsed time indication 634-1 at the standard brightness level and the first accuracy level (1 / 100 second) and periodically updates the elapsed time indication 634-1 at the first update frequency (e.g., multiple times per second and / or every 1 / 100 second).

[0218] FIG. 6X shows device 600 after determining that one or more mode transition criteria are met and, in response, transitioning from a standard display mode to a low power display mode and replacing the display of stopwatch user interface 632-1 with stopwatch user interface 632-2. In FIG. 6X, since the elapsed time measured by the stopwatch application exceeds one minute, the time-dependent update criterion is no longer met. Accordingly, device 600 displays elapsed time indication 634-2 at a second accuracy level (e.g., in minutes) and periodically updates elapsed time indication 634-2 at a second update frequency (e.g., every 30 seconds and / or every minute).

[0219] FIGS. 6Y-6AB illustrate exemplary scenarios including an alarm clock application running on device 600. In FIG. 6Y, while operating in a standard display mode (e.g., a high power consumption display mode), device 600 displays clock face user interface 650-1 (e.g., a higher power consumption user interface) at a standard luminance level on display 602. As shown in FIG. 6Y, clock face user interface 650-1 includes analog time indication 665-1 (e.g., a representation of the hands of an analog clock displaying the current time, minutes, and seconds values), and a plurality of affordances (e.g., clock face complications). In some embodiments, each affordance is associated with an application on device 600 (e.g., the affordance, when selected, launches the associated application, the affordance displays information from the associated application). In FIG. 6Y, the affordances include battery level complication 652-1, compass complication 654-1, message complication 656-1, stopwatch complication 658-1, calendar complication 660-1, alarm clock complication 670-1, solar complication 664-1, and solar system complication 666-1.

[0220] In FIG. 6Y, the current time is 11:26 AM, and the alarm clock complication 670-1 indicates the next scheduled alarm at 11:30 AM (4 minutes from the current time). While the device 600 is operating in the standard display mode, the device 600 periodically updates the display of the alarm clock complication 670-1 at a first update frequency (e.g., more than twice per second, every 1 / 10 second, every 1 / 100 second, and / or every 1 / 1000 second).

[0221] FIG. 6Z shows the device 600 after determining that one or more mode transition criteria are met and, in response, transitioning from the standard display mode to the low-power display mode (e.g., from a higher power consumption mode to a lower power consumption mode). In FIG. 6Z, in response to determining that one or more mode transition criteria are met, the device 600 replaces the display of the clock face user interface 650-1 (e.g., a higher power consumption user interface) with the clock face user interface 650-2 (e.g., a lower power consumption user interface). The clock face user interface 650-2 is displayed at a lower luminance level than the clock face user interface 650-1. The clock face user interface 650-2 includes an analog time indication 665-2, which is a low-power version of the analog time indication 665-1. The clock face user interface 650-2 also includes a plurality of affordances (e.g., battery level complication 652-2, compass complication 654-2, message complication 656-2, stopwatch complication 658-2, calendar complication 660-2, alarm clock complication 670-2, solar complication 664-2, and solar system complication 666-2), which correspond to a plurality of affordances within the clock face user interface 650-1 and represent low-power display mode versions of these affordances.

[0222] In the illustrated example, one or more time-dependent update criteria include criteria that are met when the remaining time until the next scheduled alarm is less than a threshold amount (e.g., less than one minute until the next scheduled alarm). In FIG. 6Z, there are still four minutes remaining until the next scheduled alarm. Accordingly, the one or more time-dependent update criteria are not met. In accordance with the determination that the one or more time-dependent update criteria are not met, device 600 updates the display of alarm clock complication 670-2 at a second update frequency that is lower than the first update frequency (e.g., less frequent), such as once per minute, every 30 seconds, and / or every 10 seconds (e.g., periodically updates the display of clock face user interface 650-2 and / or periodically updates the display of one or more elements of clock face user interface 650-2).

[0223] In FIG. 6AA, three minutes have elapsed from FIG. 6Z, and only one minute remains until the next scheduled alarm and one or more time-dependent update criteria are met. Accordingly, device 600 begins to periodically update the display of alarm clock complication 670-2 at a third update frequency that is higher than the second update frequency, such as once per second and / or once every half second. In some embodiments, the third update frequency is lower than the first update frequency. In some embodiments, the third update frequency is equal to the first update frequency.

[0224] In FIG. 6AB, the current time is 11:30 am. In accordance with the determination that the current time corresponds to the next scheduled alarm time, device 600 displays alarm clock user interface 672. Alarm clock user interface 672 includes alarm time indication 672, snooze button 676, and stop button 678.

[0225] Figures 6AC to 6AK illustrate exemplary scenarios including a navigation application executed on device 600. In Figure 6AC, while operating in a standard display mode (e.g., high power consumption display mode), device 600 displays a navigation user interface 680-1 (e.g., a higher power consumption user interface) with a standard brightness level on display 602. As shown in Figure 6AC, the navigation user interface 680-1 includes a next direction indication 682-1, a map 684-1, and a current location indication 686. The next direction indication 682-1 displays information related to the next navigation instruction, including the distance to the next navigation instruction, the direction of the next navigation instruction (e.g., straight, left, right), and the name of the street of the next navigation instruction. The current location indication 686 indicates the current geographical location of device 600 on map 684-1.

[0226] In some embodiments, while device 600 is operating in the standard display mode, device 600 periodically updates one or more elements of the navigation user interface 680-1 (e.g., the next direction indication 682-1, the map 684-1, and / or the current location indication 686) at a first update frequency (e.g., more than twice per second, every 1 / 100 second, and / or every 1 / 20 second).

[0227] Figure 6AD shows device 600 after determining that one or more mode transition criteria are met and, accordingly, transitioning from the standard display mode to the low power display mode (e.g., from the high power consumption mode to the low power consumption mode). In Figure 6AD, in response to determining that one or more mode transition criteria are met, device 600 replaces the display of the navigation user interface 680-1 (e.g., a higher power consumption user interface) with the navigation user interface 680-2 (e.g., a lower power consumption user interface).

[0228] The navigation user interface 680-2 is displayed at a lower brightness level than the navigation user interface 680-1. The navigation user interface 680-2 includes a next direction indication 682-2 and a map 684-2. In the illustrated embodiment, while operating in the low power display mode, the device 600 does not display the current location indicator as part of the navigation user interface 680-2.

[0229] In some embodiments, when operating in the standard display mode, the device 600 displays the map 684-1 at a first zoom level, and when operating in the low power display mode, the device 600 displays the map 684-2 at a second zoom level different from the first zoom level, where the second zoom level represents a zoomed-out level compared to the first zoom level. An example of such an implementation is shown in FIGS. 6AD to 6AG. In some embodiments, when operating in the low power display mode, the device 600 displays the map 684-2 at the same zoom level as the map 684-1 (e.g., the first zoom level). An example of such an implementation is shown in FIGS. 6AH to 6AK. FIGS. 6AH to 6AK are identical to FIGS. 6AD to 6AG except for the zoom level of the map 684-2.

[0230] In the illustrated example, one or more time-dependent update criteria include criteria that are met when less than a threshold distance (e.g., less than 1 mile to the next navigation instruction) remains until the next navigation instruction. In FIGS. 6AD (and FIG. 6AH), there are 3 miles to the next navigation instruction. Accordingly, one or more time-dependent update criteria are not met. In accordance with the determination that one or more time-dependent update criteria are not met, device 600 periodically updates one or more elements of navigation user interface 680-2 (e.g., next direction indication 682-2 and / or map 684-2) at a second update frequency that is lower than the first update frequency (e.g., once every 30 seconds and / or once every minute). Further, in accordance with the determination that one or more time-dependent update criteria are not met, device 600 displays next direction indication 682-2 without displaying the distance to the next coming navigation instruction.

[0231] In FIGS. 6AE (and FIG. 6AI), there are 2 miles to the next navigation instruction and one or more time-dependent update criteria still are not met. Accordingly, device 600 continues to periodically update one or more elements of navigation user interface 680-2 at the second update frequency.

[0232] In FIGS. 6AF (and FIG. 6AJ), there is 1 mile to the next navigation instruction and device 600 determines that one or more time-dependent update criteria are met. In response to determining that one or more time-dependent update criteria are met, device 600 periodically updates one or more elements of navigation user interface 680-2 at a third update frequency that is higher than the second update frequency (e.g., once per second, once every half second, and / or once every tenth of a second). Further, in FIG. 6AF (and also in FIG. 6AJ), device 600 displays next direction indication 682-2 such that next direction indication 682-2 includes the distance to the next coming navigation instruction (e.g., "1.0 MI").

[0233] In FIG. 6AG (and FIG. 6AK), there is 0.9 miles until the next navigation instruction, and one or more time-dependent update criteria continue to be met. Accordingly, device 600 continues to periodically update one or more elements of navigation user interface 680-2 at a third update frequency, and continues to display the distance to the next coming navigation instruction (e.g., "0.9 MI") in next direction indication 682-2.

[0234] FIGS. 7A-7B are flow diagrams illustrating methods for managing display usage using an electronic device, according to some embodiments. Method 700 is executed on a device having a display (e.g., 100, 300, 500). Some operations of method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0235] As described below, method 700 provides an intuitive method for managing display usage. This method reduces power consumption and the likelihood of screen burn-in. This method also reduces the user's cognitive burden for managing display usage, thereby creating a more efficient human-machine interface. For battery-operated computing devices, power is conserved and the battery charging interval is lengthened by enabling the device to automatically manage display usage more quickly and efficiently.

[0236] In some embodiments, a computer system (e.g., a smartphone, a smartwatch, and / or a tablet) communicates with a display generation component (e.g., a display controller, a touch-sensitive display system, and / or a display (e.g., integrated and / or connected)), and while the computer system is in a first mode (e.g., a higher power consumption mode (e.g., a mode corresponding to a brighter display, improved performance, and / or more frequent display updates)) (702), via the display generation component, a first user interface including one or more user interface elements including a first user interface element (e.g., 616-1, 634-1, 658-1, 670-1, 682-1, and / or 684-1) is displayed (704), and the user interface is associated with a first application (e.g., a timer application, a stopwatch application, an alarm clock application, and / or a navigation application).

[0237] While the first user interface is being displayed in the first mode (706), the computer system detects (708) that the computer system has met one or more criteria for transitioning from the first mode to a second mode, and the second mode is a lower power mode (e.g., reaching a duration from a last input, a gesture of lowering the wrist, and / or a hand cover gesture).

[0238] In response to detecting that the computer system has met one or more criteria for transitioning from a first mode to a second mode (710), the computer system enters the second mode, and entering the second mode is a second user interface (e.g., a low-power user interface) (e.g., 614-2, 626-2, 632-2, 650-2, and / or 680-2) associated with a first application, the second user interface corresponding to the first user interface and being displayed in a location that occupies at least a portion of the display area occupied by the first user interface, and includes one or more user interface elements including second user interface elements (e.g., 616-2, 634-2, 658-2, 670-2, 682-2, and / or 684-2). In some embodiments, the second user interface is a low-power version of the first user interface. In some embodiments, the second user interface differs from the first user interface in one or more visual characteristics (e.g., size of elements, color, hue, saturation, opacity, shape). In some embodiments, the second user interface elements correspond to the first user interface elements (e.g., are a low-power version of the first user interface elements). In some embodiments, the second user interface elements differ from the first user interface elements in one or more visual characteristics (e.g., brightness, size, color, hue, saturation, opacity, shape). In some embodiments, displaying the second user interface includes replacing the first user interface with the second user interface.

[0239] While the computer system is in the second mode (714), the computer system periodically updates the appearance of a second user interface element (e.g., 616-2, 634-2, 658-2, 670-2, 682-2, and / or 684-2) (716) while maintaining the computer system in the second mode (e.g., maintaining a dimmer display, reduced performance, and / or lower frequency of display updates) (in some embodiments, updating the appearance of one or more user interface elements of the second user interface).

[0240] In accordance with a determination that one or more time-dependent update criteria are not met (e.g., in accordance with a determination that no time-dependent updates are detected), the appearance of the second user interface element (in some embodiments, the appearance of one or more user interface elements of the second user interface) is periodically updated at a first update frequency (e.g., 30 seconds, 1 minute, 2 minutes) (718) (e.g., FIGS. 6C, 6E, 6F, 6S, 6T, 6U, 6V, 6X, 6Z, 6AD, 6AE, 6AH, and / or 6AI). In accordance with a determination that one or more time-dependent update criteria are met (e.g., in accordance with a determination that one or more time-dependent updates are detected), the appearance of the second user interface element (in some embodiments, the appearance of one or more user interface elements of the second user interface) is periodically updated at a second update frequency different from the first update frequency (e.g., a fraction of a second and / or 1 second), and the second update frequency is higher than the first update frequency (720) (e.g., FIGS. 6G, 6H, 6N, 6O, 6Q, 6R, 6AA, 6AF, 6AG, 6AJ, and / or 6AK). Updating the second user interface element at a reduced update frequency when the time-dependent update criteria are not met reduces power usage and improves the battery life of the device while still providing periodic updates to the second user interface element. Updating the second user interface element at an increased update frequency when the time-dependent update criteria are met provides the user with more timely visual updates when such timely feedback is needed (e.g., when displaying time-dependent information), thereby providing the user with improved visual feedback. By providing the user with improved visual feedback, the operability of the device is improved, (e.g., by assisting the user in providing appropriate input and reducing user errors when operating / interacting with the device), the efficiency of the user-device interface is increased, and further, by enabling the user to use the device more quickly and efficiently, the power usage of the device is reduced and the battery life is improved.

[0241] In some embodiments, while the computer system is in a first mode and a first user interface is being displayed (e.g., user interface 614-1 of FIG. 6B, user interface 631-2 of FIGS. 6K-6M, user interface 650-1 of FIG. 6P, user interface 680-1 of FIG. 6AC), a first user interface element is periodically updated at a third update frequency (e.g., different from the first update frequency and / or the second update frequency). In some embodiments, the third update frequency is higher than the first update frequency. In some embodiments, the third update frequency is higher than the second update frequency and the first update frequency.

[0242] In some embodiments, after the appearance of a second user interface element (in some embodiments, the appearance of one or more user interface elements of the second user interface) is periodically updated one or more times at a second update frequency (e.g., while one or more time-dependent update criteria are met) (e.g., while the computer system is maintained in a second mode), the computer system detects that one or more time-dependent update criteria are no longer met (e.g., determines that one or more time-dependent updates are no longer detected), and in response to detecting that one or more time-dependent update criteria are no longer met, the computer system updates the appearance of the second user interface element (in some embodiments, the appearance of one or more user interface elements of the second user interface) at a first update frequency (e.g., while the computer system is maintained in the second mode) periodically at the first update frequency (e.g., while one or more time-dependent update criteria are not met).

[0243] In some embodiments, after periodically updating the appearance of the second user interface element (in some embodiments, the appearance of one or more user interface elements of the second user interface) one or more times at a first update frequency (e.g., while one or more time-dependent update criteria are not met) (e.g., while maintaining the computer system in a second mode), the computer system detects that one or more time-dependent update criteria are met (e.g., detects one or more time-dependent updates), and in response to detecting that one or more time-dependent update criteria are met, the computer system updates the appearance of the second user interface element (in some embodiments, the appearance of one or more user interface elements of the second user interface) at a second update frequency (e.g., while one or more time-dependent update criteria are met) (e.g., while maintaining the computer system in the second mode and updating the appearance of the second user interface element at the update frequency periodically).

[0244] In some embodiments, while the computer system is in the second mode, the computer system detects that the computer system has met one or more criteria for transitioning from the second mode to the first mode (e.g., a higher power consumption mode (e.g., higher power consumption in the second mode than in the first mode)) (e.g., a wrist raise gesture and / or user input (e.g., touch screen user input, user input via a rotatable and / or depressible input mechanism)), and in response to detecting that the computer system has met one or more criteria for transitioning from the second mode to the first mode, the computer system enters the first mode, and while the computer system is in the first mode, the computer system updates the appearance of the first user interface element (in some embodiments, the appearance of one or more user interface elements of the first user interface) over time according to a third update frequency that is different from the first update frequency, and the third update frequency corresponds to a higher update frequency than the first update frequency. In some embodiments, the third update frequency corresponds to a higher update frequency than the first update frequency and the second update frequency.

[0245] In some embodiments, one or more time-dependent update criteria include a first criterion that is met when the first application is a foreground application (e.g., an application operating in the foreground) (722) (e.g., the first criterion is not met when the first application is not a foreground application (e.g., a background application)) (e.g., in FIGS. 6G-6H, the timer application is a foreground application, and in FIG. 6J, the timer application is a background application). In some embodiments, if a time-dependent update corresponding to the first application is detected while the first application is in the foreground, the second user interface element is updated periodically at a second update frequency. In some embodiments, if a time-dependent update corresponding to the first application is detected while the first application is not in the foreground, the second user interface element is updated periodically at a first update frequency. Updating the second user interface element at an increased update frequency when the first application is a foreground application provides the user with a more timely visual update when such timely feedback is needed, thereby providing the user with improved visual feedback. By providing the user with improved visual feedback, the operability of the device is improved, (e.g., by assisting the user in providing appropriate input and reducing user errors when operating / interacting with the device) the efficiency of the user-device interface is increased, and further, by enabling the user to use the device more quickly and efficiently, the power consumption of the device is reduced and the battery life is improved. Updating the second user interface element at a reduced update frequency when the first application is a background application reduces the power consumption and improves the battery life of the device while still providing periodic updates to the second user interface element.

[0246] In some embodiments, the second user interface element is a complication (e.g., 658-2) corresponding to a first application (e.g., a complication that displays data received from the first application) (724). In some embodiments, a complication refers to any clock face feature other than those used to indicate the hours, minutes, or seconds of the current time associated with the device. In some embodiments, a complication provides data obtained from an application. In some embodiments, a complication includes an affordance that, when selected, launches the corresponding application. In some embodiments, a complication is displayed at a fixed default location on the display while the device is in a particular power consumption mode. In some embodiments, in response to detecting a series of one or more inputs, the device can change or edit an aspect of the complication. For example, this can be used to change the application data displayed by an application complication. In some embodiments, a complication can indicate a first information set obtained by an application (e.g., application data (e.g., if the application is a weather application, the information set can be the forecasted weather conditions, current temperature, etc.)), and when edited, the complication can be updated to indicate a second information set from the same application (e.g., if the application is a weather application, the display can be edited from indicating the current temperature to indicating the current precipitation). In some embodiments, in response to detecting a series of one or more inputs, the device can change or edit the complication to indicate an information set from a different application (e.g., if the application is a weather application, the display can be edited from indicating weather to indicating data from a calendar application).Updating the complication at a reduced update frequency when the time-dependent update criteria are not met reduces power consumption and improves the battery life of the device while still providing periodic updates to the second user interface element. Updating the complication at an increased update frequency when the time-dependent update criteria are met provides the user with more timely visual updates when such timely feedback is needed (e.g., when displaying time-dependent information), thereby providing the user with improved visual feedback. By providing the user with improved visual feedback, the operability of the device is improved, (e.g., by assisting the user in providing appropriate input and reducing user errors when operating / interacting with the device), the efficiency of the user-device interface is increased, and further, the power consumption of the device is reduced and the battery life is improved by enabling the user to use the device more quickly and efficiently.

[0247] In some embodiments, the first application is a timer application (e.g., an application that counts down from a start time) (e.g., FIGS. 6A-6H). The determination that one or more time-dependent update criteria are met includes the determination that the timer application has less than a predetermined amount of remaining time (e.g., the last minute of the timer, the last 30 seconds of the timer, the last 10 seconds of the timer) (e.g., FIGS. 6G-6H). In some embodiments, the determination that one or more time-dependent update criteria are not met includes the determination that the timer application has a remaining time that exceeds a predetermined amount of time (e.g., a remaining time that exceeds one minute, a remaining time that exceeds 30 seconds, a remaining time that exceeds 10 seconds). For example, during the last period of the timer (e.g., the last minute, the last 30 seconds, the last 15 seconds), the progress of the timer is updated more frequently than the portion of the timer before the last period of the timer. Updating the second user interface element at a reduced update frequency when the timer application has a remaining time that exceeds a threshold amount reduces power usage and improves the battery life of the device while still providing periodic updates to the second user interface element. Updating the second user interface element at an increased update frequency when the timer application has a remaining time that is less than a threshold amount provides the user with more timely visual updates when such timely feedback is needed (e.g., when the timer application is approaching the end of the timer), thereby providing the user with improved visual feedback. By providing the user with improved visual feedback, the operability of the device is improved, (e.g., by assisting the user in providing appropriate input and reducing user errors when operating / interacting with the device), the efficiency of the user-device interface is increased, and further, the power usage of the device is reduced and the battery life is improved by enabling the user to use the device more quickly and efficiently.

[0248] In some embodiments, the first application is a stopwatch application (e.g., an application that measures how much time has elapsed since a start condition (e.g., a start input provided by a user)) (e.g., FIGS. 6K-6X). The determination that one or more time-dependent update criteria are met includes the determination that the stopwatch application has measured less than a predetermined period (e.g., the first minute of the stopwatch, the first 30 seconds of the stopwatch) (e.g., FIGS. 6N, 6O, 6Q, 6R). In some embodiments, the determination that one or more time-dependent update criteria are not met includes the determination that the stopwatch application has measured longer than a predetermined period (e.g., longer than one minute, longer than 30 seconds). For example, during the initial period of the stopwatch (e.g., the first minute, the first 30 seconds, the first 15 seconds), the progress of the stopwatch is updated more frequently than the portion of the stopwatch after the initial period of the stopwatch. When the stopwatch application has measured beyond a threshold amount of time, updating the second user interface element at a reduced update frequency reduces power usage and improves the battery life of the device while still providing periodic updates to the second user interface element. Updating the second user interface element at an increased update frequency when the stopwatch application has measured less than the threshold amount of time provides the user with more timely visual updates when such timely feedback is needed (e.g., when the stopwatch application has measured less than one minute of time), thereby providing the user with improved visual feedback. By providing the user with improved visual feedback, the operability of the device is improved, the efficiency of the user-device interface is increased (e.g., by assisting the user in providing appropriate input and reducing user errors when operating / interacting with the device), and further, the power usage of the device is reduced and the battery life is improved by enabling the user to use the device more quickly and efficiently.

[0249] In some embodiments, the first application is an alarm clock application (e.g., an application that causes a computer system to output an alarm (e.g., a visual output, an auditory output, and / or a tactile output) at a predetermined (e.g., user-defined) time) (e.g., FIGS. 6Y - 6AB). The determination that one or more time-dependent update criteria are met includes the determination that less than a predetermined amount of time remains (e.g., less than 1 minute until the next alarm, less than 30 seconds until the next alarm) until the next alarm is scheduled to be output by the computer system (e.g., FIG. 6AA). In some embodiments, the determination that one or more time-dependent update criteria are not met includes the determination that more than a predetermined amount of time remains (e.g., more than 1 minute until the next alarm, more than 30 seconds until the next alarm) until the next alarm is scheduled to be output by the computer system. For example, for a period immediately preceding the scheduled time at which an alarm is scheduled to be output (e.g., the last 1 minute, the last 30 seconds, the last 15 seconds before the alarm is scheduled to be output), the second user interface element and / or the second user interface is updated more frequently than during other periods that are not immediately preceding the scheduled alarm time. Updating the second user interface element at a reduced update frequency when the alarm clock application exceeds a threshold amount of time remaining until the next alarm is scheduled to be output reduces power usage and improves the battery life of the device while still providing periodic updates to the second user interface element. Updating the second user interface element at an increased update frequency when the alarm clock application has less than a threshold amount of time remaining until the next alarm is scheduled to be output provides the user with a more timely visual update when such timely feedback is needed (e.g., when the alarm is approaching), thereby providing the user with improved visual feedback.By providing improved visual feedback to the user, the operability of the device is enhanced, (e.g., by assisting the user to provide appropriate input and reducing user errors when operating the device / interacting with the device), the efficiency of the user-device interface is increased, and furthermore, by enabling the user to use the device more quickly and efficiently, the power consumption of the device is reduced and the battery life is improved.

[0250] In some embodiments, while in the second mode, at a first time, in accordance with a determination that one or more time-dependent update criteria are not met, the computer system periodically updates the appearance of a second user interface element (e.g., 616-2 in FIGS. 6E and 6F) at a first update frequency while maintaining the computer system in the second mode (e.g., 616-2 in FIGS. 6E and 6F) (e.g., displaying information corresponding to the information displayed by the first user interface element), the second user interface element corresponding to the first user interface element (e.g., 616-1) (e.g., the second user interface element being a low-power version of the first user interface element) and being different from the first user interface element in one or more visual characteristics (e.g., brightness, position, size, color, hue, saturation, opacity, and / or shape) (e.g., 616-2 is displayed in a darker color than 616-1). While in the second mode and at a second time following the first time, in accordance with a determination that one or more time-dependent update criteria are met, while maintaining the computer system in the second mode and while maintaining at least some of one or more visual characteristics different from the first user interface element (e.g., while maintaining brightness, position, size, color, hue, saturation, opacity, and / or shape), the appearance of the second user interface element is periodically updated at a second update frequency (e.g., 616-2 in FIGS. 6G and 6H). Even when updating the second user interface element at an increased update frequency, maintaining one or more low-power visual characteristics such as reduced brightness or reduced element size provides a periodic update to the second user interface element while reducing power usage and improving the battery life of the device.

[0251] In some embodiments, a second user interface element (e.g., 616-2) corresponds to a first user interface element (e.g., 616-1) (e.g., displays information corresponding to the information displayed by the first user interface element) (e.g., is a low-power version of the first user interface element) and is different from the first user interface element in one or more visual characteristics (e.g., luminance, position, size, color, hue, saturation, opacity, and / or shape) (e.g., 616-2 is different from 616-1 in color and / or luminance). Periodically updating the appearance of the second user interface element while maintaining the computer system in the second mode includes periodically updating the appearance of the second user interface element (e.g., regardless of whether it is the first update frequency or the second update frequency) while maintaining at least a portion of one or more visual characteristics different from the first user interface element (e.g., maintaining a reduced luminance, a different position, a reduced size, a different color scheme, a different hue, a reduced saturation, a reduced opacity, and / or a smaller shape with respect to the first user interface element), for example, by periodically updating the information presented by the second user interface element while maintaining at least a portion of one or more visual characteristics different from the first user interface element. Even when updating the second user interface element at an increased update frequency, maintaining one or more low-power visual characteristics such as a reduced luminance or a reduced element size reduces power consumption and improves the battery life of the device while still providing periodic updates to the second user interface element.

[0252] In some embodiments, while in the second mode, at a first time, in accordance with a determination that one or more time-dependent update criteria are not met, the computer system periodically updates the appearance of a second user interface element at a first update frequency while maintaining the computer system in the second mode (e.g., 616-2 in FIGS. 6E and 6F), the second user interface element displays a first information set, and while the appearance of the second user interface element is updated at the first update frequency, the first information set is displayed at a first level of accuracy (e.g., a degree of accuracy or precision of a value (e.g., a time value, a measurement value)) (e.g., 616-2 is displayed in minutes in FIGS. 6E and 6F). While in the second mode, and at a second time after the first time, in accordance with a determination that one or more time-dependent update criteria are met, the computer system periodically updates the appearance of the second user interface element at a second update frequency while maintaining the computer system in the second mode (e.g., 616-2 in FIGS. 6G and 6H), and while the appearance of the second user interface element is updated at the second update frequency, the first information set is displayed at a second level of accuracy that is more accurate than the first level of accuracy (e.g., higher precision or higher accuracy of a value) (e.g., 616-2 is displayed in seconds in FIGS. 6G and 6H). By reducing the accuracy of the information displayed when one or more time-dependent update criteria are not met, the device can perform fewer operations to determine the information to be displayed and / or display less information (e.g., not display seconds when displaying time), thereby reducing the use of processing resources and / or reducing the display brightness (e.g., turning off pixels that would otherwise be used to display higher accuracy information), while providing valuable feedback to the user. By reducing the processing resource usage and the display brightness, the power usage is reduced and the battery life of the device is improved.

[0253] In some embodiments, the second user interface includes a third user interface element (e.g., 646-2) that is different from and / or separate from (e.g., different from the second user interface element). The third user interface element displays a second information set that is different from (e.g., different from the first information set). At a first time, the appearance of the second user interface element (e.g., 634-2) is periodically updated at a first update frequency, and the first information set is displayed at a first level of accuracy (e.g., 634-2 in FIG. 6X shown in minutes), while the second information set is displayed at a third level of accuracy (e.g., 646-2 in FIG. 6X shown in one-hundredth of a second). At a second time, while the appearance of the second user interface element is periodically updated at a second update frequency and the first information set is displayed at a second level of accuracy that is more accurate than the first level of accuracy (e.g., 634-2 in FIG. 6O shown in seconds), the display of the second information set is maintained at a third level of accuracy (e.g., 646-2 in FIG. 6O shown in one-hundredth of a second). In some embodiments, the third level of accuracy is more accurate than the first level of accuracy (e.g., higher precision or higher accuracy of the value). For example, the first level of accuracy may include a display in a first unit of measurement (e.g., minutes), and the third level of accuracy may include a display in a second unit of measurement that is more accurate than the first unit of measurement (e.g., seconds, one-tenth of a second, one-hundredth of a second), or the first level of accuracy may include a display of a certain number of significant figures (e.g., one-tenth of a unit), and the third level of accuracy may include a display of a different number of significant figures that is more accurate than the first level of accuracy (e.g., one-hundredth of a unit, one-thousandth of a unit). Maintaining the level of accuracy of the third user interface element while the level of accuracy of the second user interface element is being changed allows the computer system to display appropriate levels of accuracy for different user interface elements, thereby providing the user with improved visual feedback.By providing a user with improved visual feedback, the operability of the device is enhanced, (e.g., by assisting the user in providing appropriate input and reducing user errors when operating the device / interacting with the device), the efficiency of the user-device interface is increased, and furthermore, by enabling the user to use the device more quickly and efficiently, the power consumption of the device is reduced and the battery life is improved.

[0254] In some embodiments, the first application is a turn-by-turn navigation application (e.g., an application that provides turn-by-turn navigation instructions (e.g., navigation instructions that are periodically and / or automatically updated based on the current position and / or location of a computer system) to a user) (e.g., FIGS. 6AC-6AK). The determination that one or more time-dependent update criteria are met includes a determination that the next turn is less than a threshold distance (e.g., less than 1 mile away, less than 2 miles away) or less than a threshold time (e.g., less than 1 minute away, less than 2 minutes away) from the computer system (e.g., FIGS. 6AF, 6AG, 6AJ, 6AK). In some embodiments, the determination that one or more time-dependent update criteria are not met includes a determination that the next turn is beyond a threshold distance (e.g., more than 1 mile away, more than 2 miles away) or beyond a threshold time (e.g., more than 1 minute away, more than 2 minutes away) from the computer system. When the turn-by-turn navigation application detects that the threshold distance or threshold time remaining until the next turn is also high, updating the second user interface element at a reduced update frequency reduces power usage and improves the battery life of the device while still providing periodic updates to the second user interface element. When the turn-by-turn navigation application detects that the threshold distance or threshold time remaining until the next turn is less than a threshold, updating the second user interface element at an increased update frequency provides the user with a more timely visual update when such timely feedback is needed (e.g., when the next turn is approaching), thereby providing the user with improved visual feedback.By providing improved visual feedback to the user, the operability of the device is enhanced, (e.g., by assisting the user in providing appropriate input and reducing user errors when operating the device / interacting with the device), the efficiency of the user-device interface is increased, and furthermore, the power consumption of the device is reduced and the battery life is improved by enabling the user to use the device more quickly and efficiently.

[0255] Note that the details of the processes described above with respect to method 700 (e.g., FIGS. 7A-7B) are also applicable in a similar manner to the methods described below. For example, method 900 and / or method 1100 optionally includes one or more of the characteristics of the various methods described above with reference to method 700. For example, in some embodiments, the first mode is the same mode throughout these methods, and the second mode is the same mode throughout these methods. For the sake of brevity, these details are not repeated below.

[0256] FIGS. 8A-8AD show exemplary user interfaces involving managed display usage according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processing in FIGS. 9A-9B.

[0257] Specifically, FIGS. 8A-8AD show techniques for managing display usage by changing one or more aspects (e.g., visual characteristics) of the displayed user interface when the device determines that it has met mode transition criteria such as the mode transition criteria described in more detail above.

[0258] In some embodiments disclosed below, in response to determining that one or more mode transition criteria are met, the device transitions from a standard display mode (e.g., a high power consumption mode) to a low power display mode (e.g., a low power consumption mode), and replaces the display of the high power consumption user interface with a low power consumption user interface. In some embodiments, the low power consumption user interface varies based on whether the corresponding low power consumption user interface is available for the high power consumption user interface. In some embodiments, the low power consumption user interface also varies based on whether the device (and / or application) is permitted to display a particular type of information while in the low power display mode. For example, if the device is displaying a higher power consumption user interface associated with (e.g., generated by) a first application when one or more mode transition criteria are met, and the corresponding lower power consumption user interface is not available, in some embodiments, the device displays a default lower power consumption user interface (e.g., not generated by an application). In contrast, if the corresponding low power consumption user interface is available, a determination is made as to whether the device and / or the first application is permitted to display the corresponding low power consumption user interface (e.g., based on one or more user settings set by the user), and if so permitted, a further determination is made as to whether the device and / or the first application is permitted to display all, or only a subset, of the information displayed within the high power consumption user interface within the low power consumption user interface. The examples shown in FIGS. 8A - 8AD and described below provide further details regarding these features.

[0259] In FIG. 8A, while operating in the standard display mode (e.g., high power consumption display mode), device 600 displays wallet user interface 802-1 (e.g., a higher power consumption user interface) at the standard display luminance level on display 602. Wallet user interface 802-1 corresponds to (e.g., is generated by) a wallet application executed on device 600.

[0260] As shown in FIG. 8A, wallet user interface 802-1 includes a plurality of user interface elements including current time indication 803-1, string 804A-1, balance indication 804B-1, and button 804C-1. Current time indication 803-1 displays the current time. Balance indication 804B-1 displays the amount of currency the user has in the account, and button 804C-1 can be selected by the user to initiate a process for adding currency to the account.

[0261] While displaying wallet user interface 802-1, device 600 determines that one or more mode transition criteria are met (e.g., detects a gesture of lowering the wrist using a motion sensor and / or there is no input of a specific type over a threshold duration). In response to determining that one or more mode transition criteria are met, device 600 transitions from the standard display mode to the low power display mode (e.g., from a high power consumption mode to a low power consumption mode). Further, in response to determining that one or more mode transition criteria are met, device 600 replaces the display of wallet user interface 802-1 (e.g., a higher power consumption user interface) with a lower power consumption user interface. In some embodiments, the lower power consumption user interface varies based on various determinations. FIGS. 8B-8F show various exemplary scenarios and different lower power consumption user interfaces according to various embodiments.

[0262] FIG. 8B shows an exemplary scenario where the wallet user interface 802-1 has a corresponding low-power consumption user interface (e.g., wallet user interface 802-2) (e.g., a corresponding low-power consumption user interface specified, provided, and / or generated by a wallet application). Further, in FIG. 8B, the device 600 and the wallet application are granted the right to display application information related to the wallet application (e.g., one or more user interfaces generated and / or provided by the wallet application) while in the low-power display mode. In some embodiments, the permission to display application information related to the wallet application is specified by the user (e.g., via one or more user settings). In FIG. 8B, the device 600 and the wallet application are also permitted to display all of the information displayed within the wallet user interface 802-1 while in the low-power display mode. In various embodiments, the permission to display various types of information displayed in the high-power consumption user interface can be specified by the user (e.g., via one or more user settings) and / or by the application (e.g., via code within the application that permits or prohibits the display of a particular type of information while the device 600 is in the low-power display mode). In accordance with these determinations and in response to determining that one or more mode transition criteria are met, the device 600 displays the wallet user interface 802-2 without any editing, as shown in FIG. 8B. The illustrated embodiment shows that the wallet user interface 802-2 includes all of the information shown in the wallet user interface 802-1. The wallet user interface 802-2 is displayed on the display 602 at a lower luminance level (e.g., the overall luminance level, or the average of the luminance values of the pixels constituting the wallet user interface 802-2 on the display 602 is lower than the luminance level of the wallet user interface 802-1 on the display 602 as shown in FIG. 8A).

[0263] The corresponding elements within the wallet user interface 802-2 are displayed by the device 600, different from what was previously displayed within the wallet user interface 802-1. In FIG. 8B, the current time indication 803-2, the string 804A-2, the balance indication 804B-2, and the button 804C-2 are each displayed at a lower luminance level (e.g., a darker color) than the corresponding elements, which are the current time indication 803-1, the string 804A-1, the balance indication 804B-1, and the button 804C-1, respectively.

[0264] In some embodiments, the change in luminance level between corresponding elements (e.g., affordances and / or objects) within the wallet user interfaces 802-1 and 802-2 is not uniform. In some embodiments, the device 600 displays one or more elements within the wallet user interface 802-2 at a reduced size compared to the corresponding elements within the wallet user interface 802-1.

[0265] Figures 8C - 8E each show an exemplary scenario where the wallet user interface 802 - 1 has a corresponding low - power consumption user interface (e.g., wallet user interface 802 - 2), and the device 600 and the wallet application are given the right to display application information regarding the wallet application (e.g., one or more user interfaces corresponding to and / or generated by the wallet application) while in the low - power display mode. However, in Figures 8C - 8E, the device 600 (e.g., and / or the wallet application) is not permitted to display balance information while in the low - power display mode. As described above, such restrictions can be applied by the user and / or application in various embodiments. In accordance with these determinations and in response to determining that one or more mode transition criteria are met, the device 600 displays the wallet user interface 802 - 2 with the edited representation 804B - 3 instead of the balance indication 804B - 2 as shown in Figures 8C - 8E. Thus, in Figures 8C - 8E, the wallet user interface 802 - 2 does not include and / or does not display the balance information displayed in the wallet user interface 802 - 1.

[0266] In Figure 8C, the edited representation 804B - 3 shows a character - by - character edit of the balance information. In Figure 8D, the edited representation 804B - 3 shows a string - by - string edit of the balance information. In Figure 8E, the edited representation 804B - 3 edits the entire display area corresponding to (e.g., previously occupied by) the balance indication 804B - 1. In some embodiments, the information to be edited is specified by an application (e.g., the wallet application). In some embodiments, the information to be edited is specified by the user (e.g., via one or more user settings).

[0267] FIG. 8F shows an exemplary scenario where the wallet user interface 802-1 does not have a corresponding low-power consumption user interface (e.g., the wallet application does not specify a corresponding low-power consumption user interface for the wallet user interface 802-1). In FIG. 8F, in accordance with the determination that the wallet user interface 802-1 does not have a corresponding low-power consumption user interface and in response to the determination that one or more mode transition criteria are met, the device 600 replaces the display of the wallet user interface 802-1 with the user interface 806. The user interface 806 is displayed at a lower luminance level than the wallet user interface 802-1 (e.g., the overall luminance level or the average of the luminance values of the pixels constituting the user interface 806 on the display 602 is lower than the luminance level of the wallet user interface 802-1 on the display 602 as shown in FIG. 8A).

[0268] As shown in FIG. 8F, the user interface 806 includes a current time overlay 808A overlaid on a background portion 808B. In the illustrated embodiment, the background portion 808B is a blurred representation of the wallet user interface 802-1. As demonstrated in later figures, in some embodiments, the user interface 806 represents a default low-power consumption user interface used in scenarios where a higher-power consumption user interface does not have a corresponding lower-power consumption user interface. In some embodiments, in such scenarios, the device 600 overlays a current time indication on a blurred representation of the higher-power consumption user interface.

[0269] In some embodiments, even if the wallet user interface 802-1 has (e.g., provides and / or defines) a corresponding low-power consumption user interface (e.g., wallet user interface 802-2), the device 600, in accordance with a determination that the device 600 (e.g., and / or the wallet application) is not permitted to display application information regarding the wallet application (e.g., one or more user interfaces provided and / or generated by the wallet application) when the device 600 is in the low-power display mode, displays the user interface 806. In some embodiments, the user interface 806 represents a default low-power consumption user interface used in a scenario where the device 600 and / or the application is not permitted to display application information regarding the application when the device 600 is in the low-power display mode. In some embodiments, such a restriction may be specified by the user (e.g., via one or more user settings).

[0270] Figures 8G - 8J illustrate various exemplary scenarios regarding a messaging application according to various embodiments. In Figure 8G, while operating in a standard display mode (e.g., high-power consumption display mode), the device 600 displays the messaging user interface 810-1 on the display 602 at a standard display luminance level. The messaging user interface 810-1 corresponds to (e.g., is generated by) a messaging application running on the device 600.

[0271] As shown in Figure 8G, the messaging user interface 810-1 includes a plurality of user interface elements including a current time indication 811-1, a message 812-1, a voice input option 814A-1, a touch input option 814B-1, a drawing option 814C-1, a payment option 814D-1, an emoji option 814E-1, and an avatar option 814F-1.

[0272] While displaying the messaging user interface 810-1, the device 600 determines that one or more mode transition criteria are met. In response to determining that one or more mode transition criteria are met, the device 600 transitions from the standard display mode to the low-power display mode (e.g., from the high-power consumption mode to the low-power consumption mode). Further, in response to determining that one or more mode transition criteria are met, the device 600 replaces the display of the messaging user interface 810-1 (e.g., the higher-power consumption user interface) with a lower-power consumption user interface. As described above, in some embodiments, the lower-power consumption user interface varies based on various determinations. FIGS. 8H-8J illustrate various exemplary scenarios and various lower-power consumption user interfaces according to various embodiments.

[0273] FIG. 8H shows an exemplary scenario in which the messaging user interface 810-1 has a corresponding low-power consumption user interface (e.g., the messaging user interface 810-2) (e.g., a corresponding low-power consumption user interface specified, provided, and / or generated by the messaging application). Further, in FIG. 8H, the device 600 is permitted to display application information regarding the messaging application (e.g., one or more user interfaces provided and / or generated by the messaging application) while in the low-power display mode (e.g., and / or the messaging application is permitted). In some embodiments, the permission to display application information regarding the messaging application is specified by the user (e.g., via one or more user settings). In FIG. 8H, the device 600 is also permitted to display all of the information displayed within the messaging user interface 810-1 while in the low-power display mode (e.g., and / or the messaging application is permitted). In accordance with these determinations, and in response to determining that one or more mode transition criteria are met, the device 600 displays the messaging user interface 810-2 without any editing, as shown in FIG. 8H. The illustrated embodiment shows that the messaging user interface 810-2 includes all of the information shown in the messaging user interface 810-1. The messaging user interface 810-2 is displayed at a lower luminance level than the messaging user interface 810-1 (e.g., the overall luminance level or average of the luminance values of the pixels constituting the messaging user interface 810-2 on the display 602 is lower than the luminance level of the messaging user interface 810-1 on the display 602).

[0274] The corresponding elements within the messaging user interface 810-2 are displayed by the device 600 as being different from those previously displayed within the messaging user interface 810-1. In FIG. 8H, the user interface elements of the messaging user interface 810-2 (e.g., current time indication 811-2, message 812-2, and options 814A-2, 814B-2, 814C-2, 814D-2, 814E-2, 814F-2) are displayed at a lower luminance level (e.g., darker color) than the corresponding elements within the messaging user interface 810-1 (e.g., current time indication 811-1, message 812-1, and options 814A-1, 814B-1, 814C-1, 814D-1, 814E-1, 814F-1), respectively.

[0275] In some embodiments, the change in luminance level between corresponding elements (e.g., affordances and / or objects) within the messaging user interfaces 810-1 and 810-2 is not uniform. In some embodiments, the device 600 displays one or more elements within the messaging user interface 810-2 at a reduced size compared to the corresponding elements within the messaging user interface 810-1.

[0276] Figure 8I shows an exemplary scenario where the messaging user interface 810-1 has a corresponding lower power consumption user interface (e.g., messaging user interface 810-2), and the device 600 is permitted to display application information regarding the messaging application while in the low power mode (e.g., and / or the messaging application is permitted). However, in Figure 8I, the device 600 is not permitted to display message content (e.g., the actual content of messages shared among users using the messaging application) while in the low power display mode (e.g., and / or the messaging application is not permitted). As described above, such restrictions can be applied by the user and / or application in various embodiments. In accordance with these determinations and in response to determining that one or more mode transition criteria are met, the device 600 displays the wallet user interface 810-2 having the edited representation 812-3 instead of the message 812-2. In Figure 8I, the edited representation 812-3 edits the entire display area corresponding to (e.g., previously occupied by) the message 812-1. Although Figure 8I shows the editing of the entire display area, in various embodiments, the edited representation 812-2 edits the message 812-1 character by character and / or string by string.

[0277] Figure 8J shows an exemplary scenario where the messaging user interface 810-1 does not have a corresponding low-power consumption user interface (e.g., the messaging application does not specify and / or provide a corresponding low-power consumption user interface for the messaging user interface 810-1). In Figure 8J, in accordance with the determination that the messaging user interface 810-1 does not have a corresponding low-power consumption user interface and in response to the determination that one or more mode transition criteria are met, the device 600 replaces the display of the messaging user interface 810-1 with the user interface 816. The user interface 816 is displayed at a lower luminance level than the messaging user interface 810-1 (e.g., the average of the overall luminance levels or luminance values of the pixels constituting the user interface 816 on the display 602 is lower than the luminance level of the messaging user interface 810-1 on the display 602).

[0278] As shown in Figure 8J, the user interface 816 includes a current time overlay 818A overlaid on a background portion 818B. In the illustrated embodiment, the background portion 818B is a blurred representation of the messaging user interface 810-1. As described above, in some embodiments, the user interface 816 represents the default low-power consumption user interface used in scenarios where a higher-power consumption user interface does not have a corresponding lower-power consumption user interface. In some embodiments, in such scenarios, the device 600 overlays a current time indication on a blurred representation of the higher-power consumption user interface.

[0279] In some embodiments, even if the messaging user interface 810-1 has a corresponding low power consumption user interface (e.g., the messaging user interface 810-2), the device 600 may display the user interface 816 according to a determination that the device 600 is not permitted to display application information regarding the messaging application (e.g., and / or the messaging application is not permitted). In some embodiments, such a restriction may be specified by the user (e.g., via one or more user settings).

[0280] Figures 8K-8M illustrate various exemplary scenarios related to a fitness application according to various embodiments. In Figure 8K, while operating in a standard display mode (e.g., a high power consumption display mode), the device 600 displays the fitness user interface 820-1 on the display 602 at a standard display luminance level. The fitness user interface 820-1 corresponds to (e.g., is generated by) a fitness application executed on the device 600. As shown in Figure 8K, the fitness user interface 820-1 includes a plurality of user interface elements including a current time indication 821-1, a fitness notification 822-1, and a training icon 824-1.

[0281] While displaying the fitness user interface 820-1, the device 600 determines that one or more mode transition criteria are met. In response to determining that one or more mode transition criteria are met, the device 600 transitions from the standard display mode to the low-power display mode (e.g., from a high-power consumption mode to a low-power consumption mode). Further, in response to determining that one or more mode transition criteria are met, the device 600 replaces the display of the fitness user interface 820-1 (e.g., a higher-power consumption user interface) with a lower-power consumption user interface. As introduced above, in some embodiments, the lower-power consumption user interface varies based on various determinations. FIGS. 8L and 8M show various exemplary scenarios and different lower-power consumption user interfaces according to various embodiments.

[0282] Figure 8L shows an exemplary scenario in which the fitness user interface 820-1 has a low power consumption user interface (e.g., the fitness user interface 810-2) that it corresponds to (e.g., the fitness application designates and / or provides the low power consumption user interface that it corresponds to). Further, in Figure 8L, while the device 600 is in the low power display mode, it is permitted to display application information regarding the fitness application (e.g., one or more user interfaces generated and / or provided by the fitness application) (e.g., and / or the fitness application is permitted). However, in Figure 8L, while the device 600 is in the low power display mode, it is not permitted to display notifications associated with the fitness application (e.g., generated by the fitness application) (e.g., and / or the fitness application is not permitted). In accordance with these determinations, and in response to determining that one or more mode transition criteria are met, the device 600 displays the fitness user interface 820-2 having the edited notification representation 822-2. Thus, while the device 600 is in the low power display mode, notifications associated with the fitness application are not displayed on the fitness user interface 820-2. In Figure 8L, the notifications previously displayed in the notification 822-1 are edited character by character in the edited notification representation 822-2. However, in various embodiments, the edited notification representation 822-2 edits the fitness notification information by editing each character and / or the entire display area corresponding to (e.g., previously occupied by) the fitness notification 822-1. The fitness user interface 820-2 is displayed at a lower luminance level than the fitness user interface 820-1 (e.g., the overall luminance level or average of the luminance values of the pixels constituting the fitness user interface 820-2 on the display 602 is lower than the luminance level of the fitness user interface 820-1 on the display 602).

[0283] FIG. 8M illustrates an exemplary scenario where the fitness user interface 820-1 does not have a corresponding low-power consumption user interface (e.g., the fitness application does not specify and / or provide a corresponding low-power consumption user interface for the fitness user interface 820-1). In FIG. 8M, in accordance with the determination that the fitness user interface 820-1 does not have a corresponding low-power consumption user interface and in response to the determination that one or more mode transition criteria are met, the device 600 replaces the display of the fitness user interface 820-1 with the user interface 826. The user interface 826 is displayed at a lower luminance level than the fitness user interface 820-1 (e.g., the overall luminance level or average luminance value of the pixels constituting the user interface 826 on the display 602 is lower than the luminance level of the fitness user interface 820-1 on the display 602).

[0284] As shown in FIG. 8M, the user interface 826 includes a current time overlay 828A overlaid on a background portion 828B. In the illustrated embodiment, the background portion 828B is a blurred representation of the fitness user interface 820-1. As described above, in some embodiments, the user interface 826 represents a default low-power consumption user interface used in scenarios where a higher-power consumption user interface does not have a corresponding lower-power consumption user interface. In some embodiments, in such scenarios, the device 600 overlays a current time indication on a blurred representation of the higher-power consumption user interface.

[0285] In some embodiments, even if the fitness user interface 820-1 has a corresponding low-power consumption user interface (e.g., the fitness user interface 820-2), the device 600 is not permitted to display application information regarding the fitness application (e.g., and / or the fitness application is not permitted). According to the determination, the device 600 displays the user interface 826. In some embodiments, such a restriction may be specified by the user (e.g., via one or more user settings).

[0286] Figures 8N-8O illustrate exemplary scenarios related to the notification center according to various embodiments. In Figure 8N, while operating in the standard display mode (e.g., the high-power consumption display mode), the device 600 displays the notification center user interface 830 on the display 602 at the standard display luminance level. In some embodiments, the notification center user interface 830 corresponds to (e.g., is generated by) the operating system running on the device 600.

[0287] As shown in Figure 8N, the notification center user interface 830 displays a plurality of notifications corresponding to (e.g., related to) a plurality of applications, including a notification 832A corresponding to the fitness application and a notification 832B corresponding to the wallet application.

[0288] While displaying the notification center user interface 830, the device 600 determines that one or more mode transition criteria are met. In response to determining that one or more mode transition criteria are met, the device 600 transitions from the standard display mode to the low-power display mode (e.g., from the high-power consumption mode to the low-power consumption mode). Further, in response to determining that one or more mode transition criteria are met, the device 600 replaces the display of the notification center user interface 830 (e.g., the higher-power consumption user interface) with a lower-power consumption user interface.

[0289] FIG. 8O shows an exemplary scenario where the notification center user interface 830 does not have a corresponding low power consumption user interface (e.g., the operating system does not specify a corresponding low power consumption user interface for the notification center user interface 830). In FIG. 8O, in accordance with the determination that the notification center user interface 830 does not have a corresponding low power consumption user interface and in response to the determination that one or more mode transition criteria are met, the device 600 replaces the display of the notification center user interface 830 with the user interface 834. The user interface 832 is displayed at a lower luminance level (e.g., the average of the overall luminance levels or luminance values of the pixels constituting the user interface 834 on the display 602 is lower than the luminance level of the notification center user interface 830 on the display 602).

[0290] As shown in FIG. 8O, the user interface 834 includes a current time overlay 836A overlaid on a background portion 836B. In the depicted embodiment, the background portion 836B is a blurred representation of the notification center user interface 830. As described above, in some embodiments, the user interface 834 represents a default low power consumption user interface used in scenarios where a higher power consumption user interface does not have a corresponding lower power consumption user interface. In some embodiments, in such scenarios, the device 600 overlays a current time indication on a blurred representation of the higher power consumption user interface.

[0291] In some embodiments, even if the notification center user interface 830 has a corresponding low power consumption user interface, the device 600 displays the user interface 834 in accordance with a determination that the device 600 is not permitted to display application information regarding the notification center. In some embodiments, such a restriction may be specified by the user (e.g., via one or more user settings).

[0292] In some embodiments, the device 600 provides the user with one or more user settings that can be manipulated by the user to define whether notification information for a particular application can be displayed while the device 600 is in the low power display mode (see, e.g., FIGS. 8X, 8AA, 8AC, and 8AD discussed below).

[0293] Even if device 600 is permitted to display application information and / or notification information regarding one or more applications in the low-power display mode, in some embodiments, device 600 is not permitted to display notification information in the notification center user interface 830 while operating in the low-power display mode. For example, in the exemplary scenario shown in FIG. 8N, the notification center user interface 830 displays a notification 832A corresponding to a fitness application and a notification 832B corresponding to a wallet application. In some embodiments, the user can enable the display of notifications regarding the fitness application and / or the wallet application while device 600 is in the low-power display mode. In such a scenario, if display 600 is displaying a notification regarding the fitness application (e.g., FIG. 8K) when transitioning to the low-power display mode, display 600 displays a low-power representation of the fitness application notification. However, if display 600 is displaying the notification center user interface 830 (including notification 832A regarding the fitness application) when transitioning to the low-power display mode, device 600 displays user interface 834 and does not display notification information regarding notification 832A in the low-power display mode.

[0294] Figures 8P and 8Q illustrate exemplary scenarios regarding the protection of confidential information when transitioning to a low-power display mode according to various embodiments. In FIG. 8P, while operating in a standard display mode (e.g., a high-power consumption display mode), device 600 displays clock face user interface 838-1 on display 602 at a standard display luminance level. As shown in FIG. 8P, clock face user interface 838-1 includes a plurality of user interface elements including analog time indication 839-1 (e.g., the representation of the hands of an analog clock displaying the current hour, minute, and second values) and a plurality of affordances (e.g., clock face complications). In some embodiments, each clock face complication is associated with an application on device 600 (e.g., the affordance, when selected, launches the associated application and / or the affordance displays information from the associated application). In FIG. 8P, the affordances include battery level complication 840-1, temperature complication 842-1, compass complication 844-1, physical activity complication 846-1, calendar complication 848-1, weather complication 850-1, wallet complication 852-1, and world clock complication 854-1.

[0295] In FIG. 8Q, while the clock face user interface 838-1 is being displayed, the device 600 determines that one or more mode transition criteria are satisfied. In response to determining that one or more mode transition criteria are satisfied, the device 600 transitions from the standard display mode to the low-power display mode (e.g., from a high-power consumption mode to a low-power consumption mode). Further, in response to determining that one or more mode transition criteria are satisfied, the device 600 replaces the display of the clock face user interface 838-1 with the clock face user interface 838-2. The clock face user interface 838-2 is displayed on the display 602 at a lower luminance level than the clock face user interface 838-1 (e.g., the average of the luminance values of the pixels constituting the clock face user interface 838-2 on the display 602 is lower than the luminance level of the clock face user interface 838-1).

[0296] In addition to containing less or reduced content, the corresponding elements within the watch face user interface 838-2 are displayed by the device 600 differently than what was previously displayed within the watch face user interface 838-1. In FIG. 8Q, the user interface elements of the watch face user interface 838-2 (e.g., analog time indication 839-2, battery level complication 840-2, temperature complication 842-2, compass complication 844-2, physical activity complication 846-2, calendar complication 848-2, weather complication 850-2, wallet complication 852-2, and world time complication 854-2) are displayed at a lower luminance level (e.g., darker color) than the corresponding elements of the watch face user interface 838-1 (e.g., analog time indication 839-1, battery level complication 840-1, temperature complication 842-1, compass complication 844-1, physical activity complication 846-1, calendar complication 848-1, weather complication 850-1, wallet complication 852-1, and world time complication 854-1). In some embodiments, the change in luminance level between corresponding elements (e.g., affordances and / or objects) within the watch face user interfaces 838-1 and 838-2 is not uniform. In some embodiments, the device 600 displays one or more elements within the watch face user interface 838-2 in a reduced size compared to the corresponding elements within the watch face user interface 838-1.

[0297] The clock face user interface 838-2 includes less content than the clock face user interface 838-1 in addition to being displayed at a lower brightness level. For example, in FIG. 8P, the calendar complication 848-1 displays the next calendar appointment (e.g., "8:00 AM Yoga Gym"), the physical activity complication 846-1 displays personal physical activity information (e.g., "500*30*12" indicating that the user burned 500 calories today, exercised for 30 minutes today, and stood for 12 hours of the daily threshold), and the wallet complication 852-1 displays personal financial information (e.g., the balance if it is "$68.88"). In FIG. 8Q, the device 600 is not permitted to display certain types of information such as personal financial information, personal schedule information, and / or personal health information (e.g., confidential information and / or personal information) while in the low-power display mode (e.g., and / or various applications that generate clock face complications are not permitted). Such restrictions are imposed and / or specified by various applications (e.g., physical activity applications, wallet applications, and / or calendar applications) and / or by the user (e.g., via one or more user settings) in various embodiments. In accordance with these restrictions and determinations, in FIG. 8P, the corresponding calendar complication 848-2 does not display the next calendar appointment, the physical activity complication 846-2 does not display personal physical activity information, and the wallet complication 852-2 does not display personal financial information. The device 600 is not permitted to display certain types of information while in the low-power display mode, but the device 600 is permitted to display other types of information such as publicly available information or other non-confidential information. Accordingly, the battery complication 840-2 continues to display battery level information, the compass complication 844-2 continues to display azimuth information, the world clock complication 854-2 continues to display world time information, and the temperature complication 842-2 continues to display temperature information.

[0298] Figures 8R through 8V illustrate various exemplary scenarios related to a virtual assistant application according to various embodiments. In Figure 8R, while operating in a standard display mode (e.g., a high power consumption display mode), device 600 displays a virtual assistant user interface 856 at a standard luminance level. The virtual assistant user interface 856 corresponds to (e.g., is generated by) a virtual assistant application executing on device 600. The virtual assistant user interface 856 includes an audio indication 857 that is displayed to indicate that the virtual assistant application is ready to receive audio input (e.g., via one or more microphones on device 600).

[0299] In some embodiments, device 600 maintains the display of the virtual assistant user interface 856 until device 600 determines that the voice input from the user has been completed (e.g., a threshold time has elapsed without audio input) and / or until the user provides a user input (e.g., a gesture) corresponding to a request to abort the display of the virtual assistant user interface 856. In some embodiments, while the virtual assistant user interface 856 is being displayed, device 600 is prevented from transitioning from the standard display mode to a low power display mode. For example, in some embodiments, one or more mode transition criteria include criteria that are satisfied when the virtual assistant user interface 856 is not being displayed and / or when the virtual assistant application is not actively receiving audio input.

[0300] In Figure 8S, device 600 is receiving an audio input of "What is the definition of happiness?". In response to the detection and / or receipt of the audio input, device 600 displays a user interface 858-1 that displays a result 860-1 in response to the received audio input. In Figure 8S, device 600 is permitted (and / or is virtualized) to display the information presented in result 860-1 while in the low power display mode.

[0301] In FIG. 8T, while in the standard display mode and displaying the user interface 858-1 (e.g., a user interface with higher power consumption), the device 600 determines that one or more mode transition criteria are met. In response to determining that one or more mode transition criteria are met, the device 600 transitions from the standard display mode to the low-power display mode. Further, in response to determining that one or more mode transition criteria are met, and in accordance with determining that the device 600 is permitted to display application information regarding the virtual assistant application (e.g., and / or the virtual assistant application is permitted), and in accordance with determining that the device 600 is permitted to display result information corresponding to result 860-1 (e.g., and / or the virtual assistant application is permitted) (e.g., result 860-1 does not include confidential information, personal information, and / or prohibited information), the device 600 replaces the display of the user interface 858-1 (e.g., high-power consumption user interface) with the user interface 858-2 (e.g., low-power consumption user interface), and the user interface 858-2 includes result 860-2 having result information corresponding to result 860-1.

[0302] FIG. 8U shows an alternative scenario where the device 600 receives an audio input of "What's the next schedule?" while displaying the virtual assistant user interface 856. In response to the detection and / or reception of the audio input, the device 600 displays the user interface 862-1 that displays result 864-1 in response to the received audio input. In FIG. 8U, the response 864-1 includes personal calendar information, and the device 600 is not permitted to display the information presented in response 864-1 when in the low-power display mode (e.g., and / or the virtual assistance application is not permitted).

[0303] In FIG. 8V, while in the standard display mode and displaying the user interface 862-1 (e.g., a higher power consumption user interface), the device 600 determines that one or more mode transition criteria are met. In response to determining that one or more mode transition criteria are met, the device 600 transitions from the standard display mode to the low power display mode. Further, in response to determining that one or more mode transition criteria are met and in accordance with the determination that the device 600 is permitted to display application information regarding the virtual assistant application (and / or the virtual assistant application is permitted), and also in accordance with the determination that the device 600 is not permitted to display the result information corresponding to the result 864-1 (e.g., and / or the virtual assistant application is not permitted) (e.g., the result 864-1 includes confidential, personal, and / or other prohibited information), the device 600 replaces the display of the user interface 862-1 (e.g., a higher power consumption user interface) with the user interface 862-2 (e.g., a lower power consumption user interface), and the user interface 862-2 includes the edited representation 864-2 and does not display the result information regarding the result 864-1.

[0304] FIGS. 8W through 8AD show various user setting user interfaces that can be utilized by a user to enable and / or disable the presentation of specific user interfaces and / or specific types of information when the device 600 is in the low power display mode, as presented by the device 600 in various embodiments.

[0305] In FIG. 8W, device 600 is displaying user interface 866. User interface 866 also includes an option 867 that is selectable to return to user interface 866. User interface 866 also includes a luminance indication 868A that indicates the current luminance level settings of device 600 and display 602. User interface 866 also includes selectable options 868B - 868G. Option 868B is selectable to initiate a process for adjusting the text display size of device 600. Option 868C is selectable to enable or disable bold text on device 600. Option 868D is selectable to access the "always-on" user interface 872 (shown in FIG. 8X). Option 868E is selectable to enable or disable the transition of device 600 from a low-power display mode to a standard display mode in response to detection of a wrist raise gesture. Option 868F is selectable to enable or disable the transition of device 600 from a low-power display mode to a standard display mode in response to a rotational input via the rotatable and depressable input mechanism 604. Option 868G is selectable to access the "boot duration" user interface 878 (shown in FIG. 8Y).

[0306] Figure 8W shows two different user inputs (e.g., tap input and / or non-tap input) 870A, 870B. In Figure 8W, while displaying the user interface 866, the device 600 detects the input 870B at the location corresponding to the option 868G. In Figure 8Y, in response to detecting the input 870B, the device 600 displays the user interface 878. The user interface 878 also includes an option 879 that is selectable to return to the user interface 866. The user interface 878 also includes selectable options 880A and 880B for defining a threshold duration for remaining in the standard display mode without receiving a specific type of input before the device 600 transitions to the low-power display mode. Selecting option 880A sets the threshold duration to 15 seconds, and selecting option 880B sets the threshold duration to 70 seconds.

[0307] Returning to Figure 8W, while displaying the pairing user interface 866, the electronic device 600 detects the input 870A at the location corresponding to the option 868D. In Figure 8X, in response to detecting the input 870A, the device 600 displays the user interface 872. The user interface 872 also includes an option 873 that is selectable to return to the user interface 866. The user interface 872 also includes an option 874A that is selectable to enable and / or disable the "always-on display" setting. When the "always-on display" setting is enabled, the device 600 transitions between the standard display mode and the low-power display mode when a mode transition criterion is met (e.g., when a mode transition criterion is met, the device 600 displays a low-power consumption user interface). However, when the "always-on display" setting is disabled, instead of transitioning from the standard display mode to the low-power display mode when one or more mode transition criteria (e.g., and / or different criteria) are met (e.g., instead of displaying a low-power consumption user interface), the device 600 turns off the display 602 and / or does not display any content on the display 602.

[0308] The user interface 872 also includes options 875A, 875B, and 875C. Option 875A is selectable to enable or disable the display of complication data when the device 600 is in the low-power display mode. When option 875A is disabled, the device 600 is not permitted to display any complication data for any application while the device 600 is in the low-power display mode. When option 875A is enabled, the device 600 is permitted to display complication data for applications that are individually permitted (e.g., via options 887A - 887G of FIG. 8Z) to display complication data when the device 600 is in the low-power display mode. Option 875B is selectable to enable or disable the display of notifications when the device 600 is in the low-power display mode. When option 875B is disabled, the device 600 is not permitted to display notifications for any application while the device 600 is in the low-power display mode. When option 875B is enabled, the device 600 is permitted to display notifications for applications that are individually permitted (e.g., via options 891A - 891G of FIG. 8AA) to display notifications when the device 600 is in the low-power display mode. Option 875C is selectable to enable or disable the display of application information (e.g., data generated by an application and / or one or more user interfaces generated by an application) when the device 600 is in the low-power display mode. When option 875C is disabled, the device 600 is not permitted to display application information (e.g., application information for any application (e.g., any user interface provided and / or generated by any application)) while the device 600 is in the low-power display mode.When Option 875C is enabled, device 600 is permitted to display application information corresponding to individually permitted applications (e.g., via Options 895A - 895G of FIG. 8AB) when device 600 is in the low power display mode. User interface 872 also includes Options 874B, 874C, and 874D that are selectable to access different user interfaces and different user settings, as described in more detail below.

[0309] Figure 8X shows three different user inputs (e.g., tap input and / or non-tap input) 876A, 876B, 876C. In Figure 8X, while the user interface 872 is being displayed, the device 600 detects an input 876A (e.g., tap input and / or non-tap input) at a location corresponding to option 874B. In Figure 8Z, in response to the detection of input 876A, the device 600 displays a user interface 884. The user interface 884 also includes an option 885 that is selectable to return to the user interface 872. The user interface 884 also includes an option 886 that is selectable to enable or disable the display of complication data when the device 600 is in the low-power display mode. If option 886 is disabled, the device 600 is not permitted to display any complication data for any application while the device 600 is in the low-power display mode. If option 886 is enabled, the device 600 is permitted to display complication data for applications that are individually permitted (e.g., via options 887A - 887G) to display complication data when the device 600 is in the low-power display mode. The user interface 884 also includes options 887A - 887G that are selectable to selectively enable or disable the display of complication data for individual applications while the device 600 is in the low-power display mode. Each of the options 887A - 887G corresponds to an individual application. For example, option 887A corresponds to a physical activity application, option 887B corresponds to an alarm application, option 887C corresponds to an App Store application, and so on. The device 600 is permitted to display complication data for the physical activity application when the device 600 is in the low-power display mode if both option 886 and option 887A are enabled (e.g., and / or the physical activity application is permitted).When option 886 is disabled, the application is not permitted to display complication data while device 600 is in low power display mode. When option 886 is enabled but option 887A is disabled, device 600 is not permitted to display complication data for the physical activity application (e.g., and / or the physical activity application is not permitted) when device 600 is in low power display mode. In FIG. 8Z, options 887A, 887B, 887D, 887E, 887F, and 887G are in an enabled state and option 887C is in a disabled state.

[0310] Returning to FIG. 8X, while the user interface 872 is being displayed, the device 600 detects an input 876B (e.g., a tap input and / or a non-tap input) at the location corresponding to option 874C. In FIG. 8AA, in response to the detection of the input 876B, the device 600 displays a user interface 888. The user interface 888 also includes an option 889 that is selectable to return to the user interface 872. The user interface 888 also includes an option 890 that is selectable to enable or disable the display of notifications when the device 600 is in the low-power display mode. If option 890 is disabled, the device 600 is not permitted to display notifications for any application while the device 600 is in the low-power display mode. If option 890 is enabled, the device 600 is permitted to display notifications for applications that are individually permitted (e.g., via options 891A - 891G) to display notifications when the device 600 is in the low-power display mode. The user interface 888 also includes options 891A - 891G that are selectable to selectively enable or disable the display of notifications for individual applications while the device 600 is in the low-power display mode. Each of the options 891A - 891G corresponds to an individual application. For example, option 891A corresponds to a physical activity application, option 891B corresponds to an alarm application, option 891C corresponds to an App Store application, and so on. The device 600 is permitted to display notifications regarding the physical activity application when the device 600 is in the low-power display mode if both option 890 and option 891A are enabled (e.g., and / or the physical activity application is permitted). If option 890 is disabled, there are no applications that are permitted to display notifications when the device 600 is in the low-power display mode.When option 890 is valid but option 891A is invalid, device 600 is not permitted to display a notification regarding the physical activity application when device 600 is in the low-power display mode (e.g., and / or the physical activity application is not permitted). In FIG. 8AA, options 891A, 891B, 891D, 891E, 891F, and 891G are in the enabled state, and option 891C is in the disabled state.

[0311] Returning to FIG. 8X, while the user interface 872 is being displayed, the device 600 detects an input 876C (e.g., a tap input and / or a non-tap input) at the location corresponding to the option 874D. In FIG. 8AB, in response to detecting the input 876C, the device 600 displays the user interface 892. The user interface 892 also includes an option 893 that is selectable to return to the user interface 872. The user interface 892 also includes an option 894 that is selectable to enable or disable the display of application information (e.g., data generated by an application and / or one or more user interfaces generated by an application) while the device 600 is in the low-power display mode. If the option 894 is disabled, the device 600 is not permitted to display application information (e.g., application information for any application (e.g., any user interface provided and / or generated by any application)) while the device 600 is in the low-power display mode. If the option 894 is enabled, the device 600 is permitted to display application information corresponding to individually permitted applications (e.g., via the options 895A - 895G) when the device 600 is in the low-power display mode. The user interface 892 also includes options 895A - 895G that are selectable to selectively enable or disable the display of application information regarding individual applications while the device 600 is in the low-power display mode. Each of the options 895A - 895G corresponds to an individual application. For example, the option 895A corresponds to a physical activity application, the option 895B corresponds to an alarm application, the option 895C corresponds to an App Store application, and so on.When both Option 894 and Option 895A are enabled, while the device 600 is in the low-power display mode, the device 600 is permitted to display (e.g., and / or the physical activity application is permitted to display) the application information corresponding to (e.g., generated thereby) the physical activity application. When Option 894 is disabled, there is no application permitted to display the application information while the device 600 is in the low-power display mode. When Option 894 is enabled but Option 895A is disabled, the device 600 is not permitted to display the application information corresponding to the physical activity application when the device 600 is in the low-power display mode (e.g., and / or the physical activity application is not permitted). In FIG. 8AB, Options 895B, 895C, 895D, 895E, 895F, and 895G are in the enabled state and Option 895A is in the disabled state.

[0312] In FIG. 8AC, device 600 displays a settings user interface 896 corresponding to a physical activity application. The user interface 896 enables the user to control which type of information corresponding to the physical activity application (e.g., generated by the physical activity application) can be displayed by the device 600 while the device 600 is in the low-power display mode. The user interface 896 includes an option 897A that can be selected by the user to return to the previous user interface. The user interface 896 also includes options 897B, 897C, and 897D. Option 897B can be selected by the user to enable or disable the display of complication data corresponding to the physical activity application (e.g., generated by the physical activity application) while the device 600 is in the low-power display mode. Option 897C can be selected by the user to enable or disable the display of notifications (e.g., notification information) corresponding to the physical activity application (e.g., generated thereby) while the device 600 is in the low-power display mode. Option 897D can be selected by the user to enable or disable the display of application information (e.g., one or more application user interfaces) corresponding to the physical activity application (e.g., generated thereby) while the device 600 is in the low-power display mode. In FIG. 8AC, options 897B and 897C are in the enabled state, and option 897D is in the disabled state.

[0313] In FIG. 8AD, device 600 displays a settings user interface 898 corresponding to the alarm application. The user interface 898 enables the user to control which type of information corresponding to (e.g., generated by) the alarm application can be displayed by device 600 while the device 600 is in the low power display mode. The user interface 898 includes an option 899A that can be selected by the user to return to the previous user interface. The user interface 898 also includes options 899B, 899C, and 899D. Option 899B can be selected by the user to enable or disable the display of complication data corresponding to (e.g., generated by) the alarm application while device 600 is in the low power display mode. Option 899C can be selected by the user to enable or disable the display of notifications (e.g., notification information) corresponding to (e.g., generated by) the alarm application while device 600 is in the low power display mode. Option 899D can be selected by the user to enable or disable the display of application information (e.g., one or more application user interfaces) corresponding to (e.g., generated by) the alarm application while device 600 is in the low power display mode. In FIG. 8AD, options 899B, 899C, and 899D are all in the enabled state.

[0314] FIGS. 9A-9B are flow diagrams showing a method for managing display usage using an electronic device, according to some embodiments. The method 900 is executed on a device having a display (e.g., 100, 300, 500). Some operations of the method 900 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0315] As described below, method 900 provides an intuitive way to manage display usage. This method reduces power consumption and the potential for screen burn-in. This method also reduces the user's cognitive burden for managing display usage, thereby creating a more efficient human-machine interface. For battery-operated computing devices, power is conserved and the battery charging interval is lengthened by enabling the device to automatically manage display usage more quickly and efficiently.

[0316] In some embodiments, a computer system (e.g., a smartphone, a smartwatch, and / or a tablet) communicates with a display generation component (e.g., a display controller, a touch-sensing display system, and / or a display (e.g., integrated and / or connected)), but while the computer system is in a first mode (902), via the display generation component, it is associated with a first application (e.g., generated by the first application) (e.g., a higher power consumption mode (e.g., a mode corresponding to higher power consumption than a lower power consumption mode) (e.g., a mode corresponding to a brighter display, improved performance, and / or more frequent display updates)), and a first user interface including a plurality of user interface elements including a first user interface element indicating a first set of information (e.g., numbers, a set of characters, and / or a character string) (e.g., 804B-1, 812-1, 822-1, 832A, 832B, 840-1, 842-1, 844-1, 846-1, 848-1, 850-1, 852-1, 852-1, 854-1, 860-1, 864-1) is displayed (904).

[0317] While displaying the first user interface (906), the computer system detects (908) that the computer system has met one or more criteria for transitioning from a first mode to a second mode (e.g., a lower power consumption mode (e.g., lower power consumption in the second mode than in the first mode)), such as reaching a duration from a last input, a wrist-down gesture, and / or a hand-cover gesture. In response to detecting that the computer system has met one or more criteria for transitioning from the first mode to the second mode (910), and in accordance with a determination that the first application is permitted to display a first information set while the computer system is in the second mode (912), the computer system displays (914) a second user interface (e.g., 802-2 of FIG. 8B, 810-2 of FIG. 8H, 858-2 of FIG. 8T) associated with (e.g., generated by) the first application, the second user interface corresponding to the first user interface and being displayed at a location that occupies at least a portion of the display area occupied by the first user interface (in some embodiments, the second user interface is a low-power version of the first user interface, and in some embodiments, the second user interface differs from the first user interface in one or more visual characteristics (e.g., size of elements, color, hue, saturation, opacity, shape)), the second user interface being darker than the first user interface, and the second user interface including second user interface elements (e.g., 804B-2, 812-2, 860-2) that indicate the first information set. In some embodiments, the second user interface elements correspond to the first user interface elements. In some embodiments, the second user interface elements are low-power versions of the first user interface elements. In some embodiments, the second user interface elements differ from the first user interface elements in one or more visual characteristics (e.g., size, color, hue, saturation, opacity, and / or shape).

[0318] In response to detecting that the computer system has met one or more criteria for transitioning from a first mode to a second mode (910), and in accordance with a determination that a first application is not permitted to display a first information set while the computer system is in the second mode (916), the computer system displays a third user interface (e.g., 802-2 in FIGS. 8C-8E, 806, 810-2 in FIG. 8I, 816, 820-2, 826, 834, 862-2 in FIG. 8L) that is different from the first user interface and the second user interface, where the third user interface is displayed in a location that occupies at least a portion of the display area occupied by the first user interface, and the third user interface does not include (e.g., obscures, omits, and / or hides) (e.g., does not display) the first information set (918). In some embodiments, the third user interface is darker than the first user interface. In some embodiments, the third user interface corresponds to the first user interface (e.g., includes a blurred and / or darkened version of at least a portion of the first user interface). In some embodiments, the third user interface is associated with (e.g., generated by) the first application and / or corresponds to the second user interface (e.g., is an edited version of the second user interface) (e.g., includes a subset of the information displayed in the second user interface). In some embodiments, the third user interface is not associated with (e.g., not generated by) the first application. In some embodiments, the third user interface does not include any information displayed in the first user interface and / or the second user interface.

[0319] In some embodiments, the determination that the first application is not permitted to display the first information set while the computer system is in the second mode includes the determination that the first application is not associated with a corresponding low-power state user interface (e.g., does not have, is not specified, is not configured to generate a corresponding low-power state user interface). In some embodiments, the determination that the first application is permitted to display the first information set while the computer system is in the second mode includes the determination that the first application is associated with a corresponding low-power state user interface (e.g., has, specifies, is configured to generate).

[0320] In some embodiments, displaying a second user interface associated with the first application includes replacing the display of the first user interface with the second user interface. In some embodiments, displaying a third user interface includes replacing the display of the first user interface with the third user interface. In some embodiments, the method includes detecting that one or more criteria (e.g...

Claims

1. A method, in a computer system communicating with a display generation component, while the computer system is in a first mode, via the display generation component, display a first user interface including one or more user interface elements including a first user interface element, the first user interface being associated with a first application; while the first user interface is being displayed in the first mode, detect that the computer system has met one or more criteria for transitioning from the first mode to a second mode, which is a lower power mode than the first mode; in response to detecting that the computer system has met the one or more criteria for transitioning from the first mode to the second mode, enter the second mode, and display a second user interface associated with the first application, the second user interface corresponding to the first user interface and being displayed in a location that occupies at least a portion of the display area occupied by the first user interface and including the one or more user interface elements including a second user interface element; the second user interface element including a displayed numerical value, enter the second mode; while the computer system is in the second mode, periodically update the appearance of the second user interface element while maintaining the computer system in the second mode; according to a determination that individual criteria are not met, the appearance of the second user interface element is periodically updated at a first update frequency; According to the determination that the individual criterion is satisfied, the appearance of the second user interface element is periodically updated at a second update frequency different from the first update frequency, and the individual criterion includes a first criterion that is satisfied when the displayed numerical value is less than a predetermined numerical threshold, and the second update frequency is higher than the first update frequency, a method.

2. The method according to claim 1, wherein the individual criterion includes a second criterion that is satisfied when the first application is a foreground application.

3. The method according to claim 1, wherein the second user interface element is a complication corresponding to the first application.

4. The first application is a timer application, The method according to claim 1, wherein the determination that the individual criterion is satisfied includes a determination that the timer application has a remaining time less than a predetermined amount.

5. The first application is a stopwatch application, The method according to claim 1, wherein the determination that the individual criterion is satisfied includes a determination that the stopwatch application has measured less than a predetermined period.

6. The first application is an alarm clock application, The method according to claim 1, wherein the determination that the individual criterion is satisfied includes a determination that only a predetermined amount of time remains until the next alarm is scheduled to be output by the computer system.

7. While in the second mode, At a first time, in accordance with the determination that the individual criterion is not satisfied, while maintaining the computer system in the second mode, periodically update the appearance of the second user interface element at the first update frequency, where the second user interface element corresponds to the first user interface element and is different from the first user interface element in one or more visual characteristics. At a second time after the first time, in accordance with the determination that the individual criterion is satisfied, while maintaining the computer system in the second mode and while maintaining at least some of the one or more visual characteristics that are different from the first user interface element, periodically update the appearance of the second user interface element at the second update frequency. The method according to claim 1 further includes this.

8. The second user interface element corresponds to the first user interface element and is different from the first user interface element in one or more visual characteristics. Periodically updating the appearance of the second user interface element while maintaining the computer system in the second mode includes periodically updating the appearance of the second user interface element while maintaining at least some of the one or more visual characteristics that are different from the first user interface element. The method according to claim 1 includes this.

9. While in the second mode At a first time, in accordance with the determination that the individual criterion is not satisfied, while maintaining the computer system in the second mode, periodically update the appearance of the second user interface element at the first update frequency. The second user interface element displays a first information set. While the appearance of the second user interface element is updated at the first update frequency, the first information set is displayed at a first level of accuracy; At a second time after the first time, in accordance with the determination that the individual criterion is satisfied, while maintaining the computer system in the second mode, periodically updating the appearance of the second user interface element at the second update frequency; The method of claim 1, wherein while the appearance of the second user interface element is being updated at the second update frequency, the first information set is displayed at a second level of accuracy that is more accurate than the first level of accuracy. **Claim 10** The second user interface includes a third user interface element; The third user interface element displays a second information set; At the first time, the appearance of the second user interface element is periodically updated at the first update frequency, the first information set is displayed at the first level of accuracy, and the second information set is displayed at a third level of accuracy; The method of claim 9, wherein at the second time, the appearance of the second user interface element is periodically updated at the second update frequency, the first information set is displayed at the second level of accuracy that is more accurate than the first level of accuracy, and the display of the second information set is maintained at the third level of accuracy. **Claim 11** The first application is a turn-by-turn navigation application; The method of claim 1, wherein the determination that the individual criterion is satisfied includes a determination that a next turn is less than a threshold distance or a threshold time away from the computer system. **Claim 12** Periodically updating the appearance of the second user interface element at the first update frequency includes updating the appearance of the second user interface element a plurality of times at the first update frequency while maintaining the computer system in the second mode. Periodically updating the appearance of the second user interface element at the second update frequency includes updating the appearance of the second user interface element a plurality of times at the second update frequency while maintaining the computer system in the second mode, according to the method of claim 1. **Claim 13** The individual criteria includes a third criterion that is satisfied when a predetermined amount of time has elapsed or remains, according to the method of claim 1. **Claim 14** The method of claim 1 further includes updating the appearance of the first user interface element a plurality of times at the second update frequency while the first user interface is being displayed in the first mode. **Claim 15** The method of claim 1 further includes updating the appearance of the first user interface element a plurality of times at a third update frequency that is greater than the first update frequency and the second update frequency while the first user interface is being displayed in the first mode. **Claim 16** A computer program for causing a computer to execute the method according to any one of claims 1 to 15. **Claim 17** A computer system, A memory storing the computer program according to claim 16, One or more processors capable of executing the computer program stored in the memory, and comprising The computer system is configured to communicate with a display generation component. **Claim 18** A computer system that communicates with a generating component, A computer system comprising means for executing the method according to any one of claims 1 to 15.

Images