Context-specific user interface

Abstract

To provide an electronic device with a faster and more efficient method for providing a context-specific user interface.SOLUTION: Displaying, at an electronic device, a clock user interface on a display, wherein the clock user interface includes a first complication, a second complication, and a third complication, wherein a fourth complication includes at least a seventh metric associated with data from a fourth application and an eighth metric associated with data from the fourth application; A method comprising: replacing a first complication with a fourth complication; replacing a second complication with the fourth complication; and replacing a third complication with the fourth complication.SELECTED DRAWING: Figure 10A

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application claims priority to U.S. Provisional Patent Application No. 62 / 668,041, entitled "CONTEXT-SPECIFIC USER INTERFACES," filed May 7, 2018, U.S. Provisional Patent Application No. 62 / 679,941, entitled "CONTEXT-SPECIFIC USER INTERFACES," filed June 3, 2018, and U.S. Provisional Patent Application No. 62 / 725,215, entitled "CONTEXT-SPECIFIC USER INTERFACES," filed August 30, 2018, the contents of which are incorporated herein by reference in their entireties.

[0002] TECHNICAL FIELD This disclosure relates generally to computer user interfaces, and more particularly to techniques for context-specific user interfaces. [Background technology]

[0003] Portable multifunction devices allow users to access information from a variety of applications and data sources in a variety of contexts (e.g., at work, at home, on the move, etc.) on a small device that can be carried throughout the day. Summary of the Invention

[0004] However, as the context changes, the type of information a user may want to view may also change. Therefore, providing an efficient interface that displays relevant information to a user throughout the day is a challenge. For example, a user typically does not want to know the current temperature all day long, but may want to know more detailed weather information (e.g., predicted high and low temperatures) at specific times of the day. A widget dedicated to displaying detailed weather information would provide less important information (e.g., high and low temperatures) for most of the day, occupying space that could be used to provide the user with additional relevant information (e.g., information from a different application). This is a particular concern for portable devices with small interfaces.

[0005] Furthermore, users are increasingly relying on portable multifunction devices to tell the time and to perform various other operations, including running software applications. However, some technologies that provide context-specific user interfaces (e.g., for telling the time and / or other operations) are generally cumbersome and inefficient. For example, some existing technologies use complex and time-consuming user interfaces that may involve multiple key presses or keystrokes. Existing technologies take longer than necessary, wasting the user's time and the device's energy. The latter problem is particularly acute in battery-operated devices.

[0006] Thus, the present technology provides electronic devices with faster, more efficient methods for providing context-specific user interfaces. Such methods and interfaces, optionally, complement or replace other methods for providing context-specific user interfaces. Such methods and interfaces reduce the cognitive burden on users and create a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power, extend the time between battery charges, and reduce the number of unnecessary, irrelevant, and / or repetitively received inputs required to access information.

[0007] In some embodiments, a method is described. The method includes, in an electronic device having a display, displaying a clock user interface on the display. The clock user interface includes a first graphical object at a first location in a sequence of locations on the display and a second graphical object at a last location in the sequence of locations on the display. The method further includes, while displaying the clock user interface on the display, detecting a first user input, and in response to detecting the first user input, ceasing to display the first graphical object at the first location in the sequence of defined locations on the display, ceasing to display the second graphical object at the last location in the sequence of defined locations on the display, displaying the second graphical object at the first location in the sequence of locations on the display, and displaying the first graphical object at the second location in the sequence of locations on the display.

[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 an electronic device having a display. The one or more programs further include instructions for displaying a clock user interface on the display, the clock user interface including a first graphical object at a first location in a sequence of locations on the display and a second graphical object at a last location in the sequence of locations on the display, instructions for detecting a first user input while displaying the clock user interface on the display, and in response to detecting the first user input, instructions for stopping displaying the first graphical object at the first location in the sequence of defined locations on the display, instructions for stopping displaying the second graphical object at the last location in the sequence of defined locations on the display, instructions for displaying the second graphical object at the first location in the sequence of locations on the display, and instructions for displaying the first graphical object at the second location in the sequence of locations on the display.

[0009] According to some embodiments, a temporary computer-readable storage medium is described. The temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display. The one or more programs further include instructions for displaying a clock user interface on the display, the clock user interface including a first graphical object at a first location in a sequence of locations on the display and a second graphical object at a last location in the sequence of locations on the display, instructions for detecting a first user input while displaying the clock user interface on the display, and in response to detecting the first user input, instructions for stopping displaying the first graphical object at the first location in the sequence of defined locations on the display, instructions for stopping displaying the second graphical object at the last location in the sequence of defined locations on the display, instructions for displaying the second graphical object at the first location in the sequence of locations on the display, and instructions for displaying the first graphical object at the second location in the sequence of locations on the display.

[0010] In some embodiments, an electronic device is described. The electronic device includes a display, 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 further include instructions for displaying a clock user interface on the display, the clock user interface including a first graphical object at a first location in a sequence of locations on the display and a second graphical object at a last location in the sequence of locations on the display, and instructions for detecting a first user input while displaying the clock user interface on the display, and in response to detecting the first user input, instructions for stopping displaying the first graphical object at the first location in the sequence of defined locations on the display, instructions for stopping displaying the second graphical object at the last location in the sequence of defined locations on the display, instructions for displaying the second graphical object at the first location in the sequence of locations on the display, and instructions for displaying the first graphical object at the second location in the sequence of locations on the display.

[0011] In some embodiments, an electronic device is described. The electronic device comprises means for displaying a clock user interface on a display. The clock user interface includes a first graphical object at a first location in a sequence of locations on the display and a second graphical object at a last location in the sequence of locations on the display. The electronic device comprises means for detecting a first user input while displaying the clock user interface on the display, means for ceasing displaying the first graphical object at the first location in the sequence of defined locations on the display in response to detecting the first user input, means for ceasing displaying the second graphical object at the last location in the sequence of defined locations on the display, means for displaying the second graphical object at the first location in the sequence of locations on the display, and means for displaying the first graphical object at the second location in the sequence of locations on the display.

[0012] In some embodiments, a method is described in an electronic device having a display, the method including: displaying a clock user interface on the display at a first time, the clock user interface at the first time including a first clock hand in a first position overlaid on a background, the background having a first graphical characteristic at the first time determined based on the first position of the first clock hand; and displaying the clock user interface on the display at a second time after the first time, the clock user interface at the second time including the first clock hand in a second position overlaid on the background, the background having a second graphical characteristic at the second time determined based on the second position of the first clock hand.

[0013] According to some embodiments, a temporary computer-readable storage medium is described. The temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display. The one or more programs include instructions for displaying a clock user interface on the display at a first time, the clock user interface at the first time including a first clock hand in a first position overlaid on a background, the background having a first graphical characteristic at the first time determined based on the first position of the first clock hand, and for displaying the clock user interface on the display at a second time after the first time, the clock user interface at the second time including the first clock hand in a second position overlaid on the background, the background having a second graphical characteristic at the second time determined based on the second position of the first clock hand.

[0014] 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 an electronic device having a display. The one or more programs include instructions for displaying a clock user interface on the display at a first time, the clock user interface at the first time including a first clock hand in a first position overlaid on a background, the background having a first graphical characteristic at the first time determined based on the first position of the first clock hand, and instructions for displaying the clock user interface on the display at a second time after the first time, the clock user interface at the second time including the first clock hand in a second position overlaid on the background, the background having a second graphical characteristic at the second time determined based on the second position of the first clock hand.

[0015] In some embodiments, an electronic device is described. The electronic device includes a display, 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 include instructions for displaying a clock user interface on the display at a first time, the clock user interface at the first time including a first clock hand in a first position overlaid on a background, the background having a first graphical characteristic at the first time determined based on the first position of the first clock hand, and instructions for displaying the clock user interface on the display at a second time after the first time, the clock user interface at the second time including the first clock hand in a second position overlaid on the background, the background having a second graphical characteristic at the second time determined based on the second position of the first clock hand.

[0016] In some embodiments, an electronic device is described that includes a display; means for displaying a clock user interface on the display at a first time, the clock user interface at the first time including a first clock hand in a first position superimposed on a background, the background having a first graphical characteristic at the first time determined based on the first position of the first clock hand; and means for displaying the clock user interface on the display at a second time after the first time, the clock user interface at the second time including the first clock hand in a second position superimposed on the background, the background having a second graphical characteristic at the second time determined based on the second position of the first clock hand.

[0017] In some embodiments, a method is described in an electronic device having a display, the method comprising: displaying a clock user interface on the display, the clock user interface including a first complication including at least a first metric associated with data from a first application and a second metric associated with the data from the first application, a second complication including at least a third metric associated with data from a second application and a fourth metric associated with the data from the second application, a third complication including at least a fifth metric associated with data from a third application and a sixth metric associated with the data from the third application; and receiving a sequence of one or more inputs corresponding to a request to add the fourth complication to the clock user interface. detecting a sequence of one or more inputs, wherein the fourth complication includes at least a seventh metric associated with data from the fourth application and an eighth metric associated with data from the fourth application; and, in response to detecting the sequence of one or more inputs, replacing the first complication with a fourth complication in accordance with a determination that the sequence of one or more inputs corresponds to a request to replace the first complication, replacing the second complication with the fourth complication in accordance with a determination that the sequence of one or more inputs corresponds to a request to replace the second complication, and replacing the third complication with the fourth complication in accordance with a determination that the sequence of one or more inputs corresponds to a request to replace the third complication.

[0018] According to some embodiments, a transient computer-readable storage medium is described, the transient computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display, the one or more programs including instructions for displaying a watch user interface on the display, the watch user interface including a first complication including at least a first metric associated with data from a first application and a second metric associated with the data from the first application, a second complication including at least a third metric associated with data from a second application and a fourth metric associated with the data from the second application, and a third complication including at least a fifth metric associated with data from a third application and a sixth metric associated with the data from the third application; and detecting a sequence of one or more inputs corresponding to a request to add the fourth complication to the watch user interface. the fourth complication including at least a seventh metric associated with data from the fourth application and an eighth metric associated with data from the fourth application; and in response to detecting the sequence of one or more inputs, replacing the first complication with the fourth complication in accordance with a determination that the sequence of one or more inputs corresponds to a request to replace the first complication, replacing the second complication with the fourth complication in accordance with a determination that the sequence of one or more inputs corresponds to a request to replace the second complication, and replacing the third complication with the fourth complication in accordance with a determination that the sequence of one or more inputs corresponds to a request to replace the third complication.

[0019] 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 an electronic device having a display. The one or more programs include instructions for displaying, on the display, a watch user interface, the watch user interface including a first complication including at least a first metric associated with data from a first application and a second metric associated with the data from the first application, a second complication including at least a third metric associated with data from a second application and a fourth metric associated with the data from the second application, a third complication including at least a fifth metric associated with data from a third application and a sixth metric associated with the data from the third application, and detecting a sequence of one or more inputs corresponding to a request to add the fourth complication to the watch user interface. and issuing a fourth complication, the fourth complication including at least a seventh metric associated with data from the fourth application and an eighth metric associated with data from the fourth application; and in response to detecting the sequence of one or more inputs, replacing the first complication with a fourth complication in accordance with a determination that the sequence of one or more inputs corresponds to a request to replace the first complication, replacing the second complication with the fourth complication in accordance with a determination that the sequence of one or more inputs corresponds to a request to replace the second complication, and replacing the third complication with the fourth complication in accordance with a determination that the sequence of one or more inputs corresponds to a request to replace the third complication.

[0020] In some embodiments, an electronic device is described that includes a display, one or more processors, and a memory that stores one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for displaying a watch user interface on the display, the watch user interface including a first complication including at least a first metric associated with data from a first application and a second metric associated with the data from the first application, a second complication including at least a third metric associated with data from a second application and a fourth metric associated with the data from the second application, and a third complication including at least a fifth metric associated with data from a third application and a sixth metric associated with the data from the third application; and detecting a sequence of one or more inputs corresponding to a request to add the fourth complication to the watch user interface. the fourth complication including at least a seventh metric associated with data from the fourth application and an eighth metric associated with data from the fourth application; and in response to detecting the sequence of one or more inputs, replacing the first complication with the fourth complication in accordance with a determination that the sequence of one or more inputs corresponds to a request to replace the first complication, replacing the second complication with the fourth complication in accordance with a determination that the sequence of one or more inputs corresponds to a request to replace the second complication, and replacing the third complication with the fourth complication in accordance with a determination that the sequence of one or more inputs corresponds to a request to replace the third complication.

[0021] In some embodiments, an electronic device is described that includes a display and means for displaying a watch user interface on the display, the watch user interface including a first complication including at least a first metric associated with data from a first application and a second metric associated with data from the first application, a second complication including at least a third metric associated with data from a second application and a fourth metric associated with data from the second application, a fifth metric associated with data from a third application and a sixth metric associated with data from the third application, and means for detecting a sequence of one or more inputs corresponding to a request to add a fourth complication to the watch user interface. the fourth complication includes at least a seventh metric associated with data from the fourth application and an eighth metric associated with data from the fourth application; and in response to detecting a sequence of one or more inputs, means for replacing the first complication with the fourth complication in accordance with a determination that the sequence of the one or more inputs corresponds to a request to replace the first complication; means for replacing the second complication with the fourth complication in accordance with a determination that the sequence of the one or more inputs corresponds to a request to replace the second complication; and means for replacing the third complication with the fourth complication in accordance with a determination that the sequence of the one or more inputs corresponds to a request to replace the third complication.

[0022] In some embodiments, a method is described. The method includes, at an electronic device having a display and one or more input devices, displaying on the display a clock user interface including a clock face, the clock user interface including the clock face and user interface elements at least partially surrounding the clock face. The method further includes receiving, via the one or more input devices, a request to add a corresponding complication to a corresponding location on the clock face; in response to receiving the request to add the corresponding complication to the corresponding location on the clock face, and in accordance with determining that the corresponding complication is a first complication, displaying the first complication on the display at the corresponding location on the clock face, replacing at least a portion of the user interface elements with content associated with the first complication; and in accordance with determining that the corresponding complication is a second complication, displaying a second complication on the display at the corresponding location on the clock face without replacing a portion of the user interface elements with content associated with the second complication.

[0023] 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 an electronic device having a display and one or more input devices. The one or more programs include instructions for displaying a clock user interface on the display, the clock user interface including a clock face and a user interface element at least partially surrounding the clock face. The one or more programs further include instructions for receiving, via the one or more input devices, a request to add a corresponding complication to a corresponding location on the clock face; instructions for, in response to receiving the request to add the corresponding complication to the corresponding location on the clock face, displaying the first complication on the display at the corresponding location on the clock face in accordance with a determination that the corresponding complication is a first complication; instructions for replacing at least a portion of the user interface elements with content associated with the first complication; and instructions for, in accordance with a determination that the corresponding complication is a second complication, displaying the second complication on the display at the corresponding location on the clock face without replacing a portion of the user interface elements with content associated with the second complication.

[0024] According to some embodiments, a temporary computer-readable storage medium is described. The temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display and one or more input devices. The one or more programs include instructions for displaying a clock user interface on the display, the clock user interface including a clock face and a user interface element at least partially surrounding the clock face. The one or more programs further include instructions for receiving, via the one or more input devices, a request to add a corresponding complication to a corresponding location on the clock face; instructions for, in response to receiving the request to add the corresponding complication to the corresponding location on the clock face, displaying the first complication on the display at the corresponding location on the clock face in accordance with a determination that the corresponding complication is a first complication; instructions for replacing at least a portion of the user interface elements with content associated with the first complication; and instructions for, in accordance with a determination that the corresponding complication is a second complication, displaying the second complication on the display at the corresponding location on the clock face without replacing a portion of the user interface elements with content associated with the second complication.

[0025] In some embodiments, an electronic device is described. The electronic device includes a display, one or more input devices, 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 include instructions for displaying a clock user interface on the display, the clock user interface including a clock face and user interface elements at least partially surrounding the clock face. The one or more programs further include instructions for receiving, via the one or more input devices, a request to add a corresponding complication to a corresponding location on the clock face; in response to receiving the request to add the corresponding complication to the corresponding location on the clock face, and in accordance with a determination that the corresponding complication is a first complication, instructions for displaying the first complication on the display at the corresponding location on the clock face; instructions for replacing at least a portion of the user interface elements with content associated with the first complication; and in accordance with a determination that the corresponding complication is a second complication, instructions for displaying a second complication on the display at the corresponding location on the clock face without replacing a portion of the user interface elements with content associated with the second complication.

[0026] In some embodiments, an electronic device is described. The electronic device includes means for displaying a clock user interface on a display, the clock user interface including a clock face and user interface elements at least partially surrounding the clock face. The electronic device further includes means for receiving, via one or more input devices, a request to add a corresponding complication to a corresponding location on the clock face. In response to receiving the request to add the corresponding complication to the corresponding location on the clock face, the device further includes means for displaying, on the display, a first complication at the corresponding location on the clock face, and, in accordance with a determination that the corresponding complication is the first complication, replacing at least a portion of the user interface elements with content associated with the first complication. In accordance with a determination that the corresponding complication is a second complication, means for displaying, on the display, a second complication at the corresponding location on the clock face without replacing a portion of the user interface elements with content associated with the second complication.

[0027] In some embodiments, a method is described in an electronic device having a display and one or more input devices. The method includes displaying a clock user interface on the display, the clock user interface comprising a clock face, a user interface element at least partially surrounding the clock face, and a complication. The method further includes detecting, while displaying the clock user interface, an input directed at the user interface element via the one or more input devices, and, in response to detecting the input directed at the user interface element, updating, on the display, an appearance of the user interface element based on the input while maintaining a display of the clock face and the complication on the display.

[0028] 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 an electronic device having a display and one or more input devices. The one or more programs include instructions for displaying a clock user interface on the display, the clock user interface including a clock face, a user interface element at least partially surrounding the clock face, and a complication. The one or more programs further include instructions for detecting input directed at the user interface element via the one or more input devices while displaying the clock user interface, and in response to detecting the input directed at the user interface element, updating the appearance of the user interface element on the display based on the input while maintaining the display of the clock face and the complication on the display.

[0029] According to some embodiments, a temporary computer-readable storage medium is described. The temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display and one or more input devices. The one or more programs include instructions for displaying a clock user interface on the display, the clock user interface including a clock face, a user interface element at least partially surrounding the clock face, and a complication. The one or more programs further include instructions for detecting input directed at the user interface element via the one or more input devices while displaying the clock user interface, and in response to detecting the input directed at the user interface element, updating the appearance of the user interface element on the display based on the input while maintaining the display of the clock face and the complication on the display.

[0030] In some embodiments, an electronic device is described. The electronic device includes a display, one or more input devices, 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 include instructions for displaying a clock user interface on the display, the clock user interface comprising a clock face, a user interface element at least partially surrounding the clock face, and a complication. The one or more programs further include instructions for detecting input directed at the user interface element via the one or more input devices while displaying the clock user interface, and in response to detecting the input directed at the user interface element, updating the appearance of the user interface element on the display based on the input while maintaining the display of the clock face and the complication on the display.

[0031] In some embodiments, an electronic device is described. The electronic device comprises means for displaying a clock user interface on a display, the clock user interface comprising a clock face, a user interface element at least partially surrounding the clock face, and a complication. The device further comprises means for detecting, via one or more input devices, input directed at the user interface element while displaying the clock user interface. In response to detecting the input directed at the user interface element, the device further comprises means for updating, on the display, the appearance of the user interface element based on the input, while maintaining the display of the clock face and the complication on the display.

[0032] Executable instructions to perform these functions are optionally contained in a non-transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors. Executable instructions to perform these functions are optionally contained in a transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors.

[0033] In this manner, the effectiveness, efficiency, and user satisfaction of devices are improved by providing faster and more efficient methods and interfaces for providing context-specific user interfaces to such devices, which may complement or replace other methods for providing context-specific user interfaces. [Brief explanation of the drawings]

[0034] For a better understanding of the various described embodiments, reference should be made to the following Detailed Description of the Invention in conjunction with the following drawings, in which like reference numerals refer to corresponding parts throughout:

[0035] [Figure 1A] FIG. 1 is a block diagram illustrating a portable multifunction device having a touch-sensitive display in accordance with some embodiments.

[0036] [Figure 1B] FIG. 2 is a block diagram illustrating exemplary components for event processing in accordance with some embodiments.

[0037] [Figure 2] 1 illustrates a portable multifunction device with a touch screen in accordance with some embodiments.

[0038] [Figure 3] FIG. 1 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface in accordance with some embodiments.

[0039] [Figure 4A] 1 illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.

[0040] [Figure 4B] 1 illustrates an exemplary user interface of a multifunction device having a touch-sensitive surface separate from a display in accordance with some embodiments.

[0041] [Figure 5A] 1 illustrates a personal electronic device according to some embodiments.

[0042] [Figure 5B] FIG. 1 is a block diagram illustrating a personal electronic device according to some embodiments.

[0043] [Figure 5C] 1 illustrates exemplary components of a personal electronic device having a touch-sensitive display and intensity sensor in accordance with some embodiments. [Figure 5D] 1 illustrates exemplary components of a personal electronic device having a touch-sensitive display and intensity sensor in accordance with some embodiments.

[0044] [Figure 5E] 1 illustrates exemplary components and a user interface of a personal electronic device according to some embodiments. [Figure 5F] 1 illustrates exemplary components and a user interface of a personal electronic device according to some embodiments. [Figure 5G] 1 illustrates exemplary components and a user interface of a personal electronic device according to some embodiments. [Figure 5H] 1 illustrates exemplary components and a user interface of a personal electronic device according to some embodiments.

[0045] [Figure 6A] 1 illustrates an exemplary context-specific user interface. [Figure 6B] 1 illustrates an exemplary context-specific user interface. [Figure 6C] 1 illustrates an exemplary context-specific user interface. [Figure 6D] 1 illustrates an exemplary context-specific user interface. [Figure 6E] 1 illustrates an exemplary context-specific user interface. [Figure 6F] 1 illustrates an exemplary context-specific user interface. [Figure 6G] 1 illustrates an exemplary context-specific user interface. [Figure 6H] 1 illustrates an exemplary context-specific user interface. [Figure 6I] 1 illustrates an exemplary context-specific user interface. [Figure 6J] 1 illustrates an exemplary context-specific user interface. [Figure 6K] 1 illustrates an exemplary context-specific user interface. [Figure 6L] 1 illustrates an exemplary context-specific user interface. [Figure 6M] 1 illustrates an exemplary context-specific user interface.

[0046] [Figure 7A] FIG. 1 is a flow diagram illustrating a method for providing a context-specific user interface according to some embodiments. [Figure 7B] FIG. 1 is a flow diagram illustrating a method for providing a context-specific user interface according to some embodiments.

[0047] [Figure 8A]1 illustrates an exemplary context-specific user interface. [Figure 8B] 1 illustrates an exemplary context-specific user interface. [Figure 8C] 1 illustrates an exemplary context-specific user interface. [Figure 8D] 1 illustrates an exemplary context-specific user interface. [Figure 8E] 1 illustrates an exemplary context-specific user interface. [Figure 8F] 1 illustrates an exemplary context-specific user interface. [Figure 8G] 1 illustrates an exemplary context-specific user interface. [Figure 8H] 1 illustrates an exemplary context-specific user interface. [Figure 8I] 1 illustrates an exemplary context-specific user interface. [Figure 8J] 1 illustrates an exemplary context-specific user interface.

[0048] [Figure 9] FIG. 1 is a flow diagram illustrating a method for providing a context-specific user interface according to some embodiments.

[0049] [Figure 10A] 1 illustrates an exemplary context-specific user interface. [Figure 10B] 1 illustrates an exemplary context-specific user interface. [Figure 10C] 1 illustrates an exemplary context-specific user interface. [Figure 10D] 1 illustrates an exemplary context-specific user interface. [Figure 10E] 1 illustrates an exemplary context-specific user interface. [Figure 10F] 1 illustrates an exemplary context-specific user interface. [Figure 10G] 1 illustrates an exemplary context-specific user interface. [Figure 10H] 1 illustrates an exemplary context-specific user interface. [Figure 10I] 1 illustrates an exemplary context-specific user interface. [Figure 10J] 1 illustrates an exemplary context-specific user interface. [Figure 10K] 1 illustrates an exemplary context-specific user interface. [Figure 10L] 1 illustrates an exemplary context-specific user interface. [Figure 10M] 1 illustrates an exemplary context-specific user interface. [Figure 10N] 1 illustrates an exemplary context-specific user interface. [Figure 10O] 1 illustrates an exemplary context-specific user interface. [Figure 10P] 1 illustrates an exemplary context-specific user interface. [Figure 10Q] 1 illustrates an exemplary context-specific user interface. [Figure 10R] 1 illustrates an exemplary context-specific user interface. [Figure 10S] 1 illustrates an exemplary context-specific user interface. [Figure 10T] 1 illustrates an exemplary context-specific user interface.

[0050] [Figure 11A] FIG. 1 is a flow diagram illustrating a method for providing a context-specific user interface according to some embodiments. [Figure 11B] FIG. 1 is a flow diagram illustrating a method for providing a context-specific user interface according to some embodiments. [Figure 11C]FIG. 1 is a flow diagram illustrating a method for providing a context-specific user interface according to some embodiments. [Figure 11D] FIG. 1 is a flow diagram illustrating a method for providing a context-specific user interface according to some embodiments.

[0051] [Figure 12A] 1 illustrates an exemplary context-specific user interface. [Figure 12B] 1 illustrates an exemplary context-specific user interface. [Figure 12C] 1 illustrates an exemplary context-specific user interface. [Figure 12D] 1 illustrates an exemplary context-specific user interface. [Figure 12E] 1 illustrates an exemplary context-specific user interface. [Figure 12F] 1 illustrates an exemplary context-specific user interface. [Figure 12G] 1 illustrates an exemplary context-specific user interface. [Figure 12H] 1 illustrates an exemplary context-specific user interface. [Figure 12I] 1 illustrates an exemplary context-specific user interface. [Figure 12J] 1 illustrates an exemplary context-specific user interface. [Figure 12K] 1 illustrates an exemplary context-specific user interface. [Figure 12L] 1 illustrates an exemplary context-specific user interface. [Figure 12M] 1 illustrates an exemplary context-specific user interface. [Figure 12N] 1 illustrates an exemplary context-specific user interface. [Figure 12O] 1 illustrates an exemplary context-specific user interface. [Figure 12P]1 illustrates an exemplary context-specific user interface. [Figure 12Q] 1 illustrates an exemplary context-specific user interface. [Figure 12R] 1 illustrates an exemplary context-specific user interface.

[0052] [Figure 13] FIG. 1 is a flow diagram illustrating a method for providing a context-specific user interface according to some embodiments.

[0053] [Figure 14A] 1 illustrates an exemplary context-specific user interface. [Figure 14B] 1 illustrates an exemplary context-specific user interface. [Figure 14C] 1 illustrates an exemplary context-specific user interface. [Figure 14D] 1 illustrates an exemplary context-specific user interface. [Figure 14E] 1 illustrates an exemplary context-specific user interface. [Figure 14F] 1 illustrates an exemplary context-specific user interface. [Figure 14G] 1 illustrates an exemplary context-specific user interface. [Figure 14H] 1 illustrates an exemplary context-specific user interface. [Figure 14I] 1 illustrates an exemplary context-specific user interface. [Figure 14J] 1 illustrates an exemplary context-specific user interface. [Figure 14K] 1 illustrates an exemplary context-specific user interface. [Figure 14L] 1 illustrates an exemplary context-specific user interface. [Figure 14M] 1 illustrates an exemplary context-specific user interface. [Figure 14N] 1 illustrates an exemplary context-specific user interface. [Figure 14O] 1 illustrates an exemplary context-specific user interface. [Figure 14P] 1 illustrates an exemplary context-specific user interface. [Figure 14Q] 1 illustrates an exemplary context-specific user interface. [Figure 14R] 1 illustrates an exemplary context-specific user interface. [Figure 14S] 1 illustrates an exemplary context-specific user interface. [Figure 14T] 1 illustrates an exemplary context-specific user interface. [Figure 14U] 1 illustrates an exemplary context-specific user interface. [Figure 14V] 1 illustrates an exemplary context-specific user interface. [Figure 14W] 1 illustrates an exemplary context-specific user interface. [Figure 14X] 1 illustrates an exemplary context-specific user interface. [Figure 14Y] 1 illustrates an exemplary context-specific user interface. [Figure 14Z] 1 illustrates an exemplary context-specific user interface. [Figure 14AA] 1 illustrates an exemplary context-specific user interface. [Figure 14AB] 1 illustrates an exemplary context-specific user interface. [Figure 14AC] 1 illustrates an exemplary context-specific user interface. [Figure 14AD] 1 illustrates an exemplary context-specific user interface. [Figure 14AE] 1 illustrates an exemplary context-specific user interface.

[0054] [Figure 15A] FIG. 1 is a flow diagram illustrating a method for providing a context-specific user interface according to some embodiments. [Figure 15B] FIG. 1 is a flow diagram illustrating a method for providing a context-specific user interface according to some embodiments. [Figure 15C] FIG. 1 is a flow diagram illustrating a method for providing a context-specific user interface according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0055] The following description describes example methods, parameters, etc. However, it should be recognized that such description is not intended as a limitation on the scope of the present disclosure, but is instead provided as a description of example embodiments.

[0056] There is a need for electronic devices that provide efficient methods and interfaces for providing context-specific user interfaces that, for example, display the time of day along with additional information. This is particularly true for portable multifunction devices with small displays. Conveniently providing users with relevant information (e.g., obtained from one or more applications) at a glance in a convenient, customizable interface can reduce the number of inputs required to access the information and preserve battery life. Furthermore, providing users with a user interface that can quickly adapt to display various content at different levels of detail as the context in which the user is using the interface changes (e.g., throughout the day) can enable more efficient access to such information through the interface. Such interfaces can more efficiently utilize the "space" screen, thereby reducing the number of user interactions required to access relevant data at any time of day. Such techniques can reduce a user's cognitive burden and increase productivity by using a context-specific user interface to access information and / or keep track of the time. Furthermore, such techniques can reduce processor and battery power that would otherwise be wasted on redundant user input.

[0057] Below, Figures 1A-1B, 2, 3, 4A-4B, and 5A-5H provide descriptions of example devices for implementing techniques for configuring context-specific user interfaces. Figures 6A-6M, 8A-8J, 10A-10T, 12A-12R, and 14A-14AE show example user interfaces for providing context-specific user interfaces. The user interfaces in these figures are also used to illustrate processes described below, including the methods of Figures 7A-7B, 9, 11A-11D, 13, and 15A-15C.

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

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

[0060] The term "if" is interpreted, optionally, depending on the context, to mean "when" or "upon," or "in response to determining" or "in response to detecting." Similarly, the phrase "if it is determined" or "if [a stated condition or event] is detected" is interpreted, optionally, depending on the context, to mean "upon determining" or "in response to determining," or "upon detecting [the stated condition or event]" or "in response to detecting [the stated condition or event]."

[0061] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as PDA and / or music player functions. Exemplary embodiments of portable multifunction 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 laptops or tablet computers having a touch-sensitive surface (e.g., a touchscreen display and / or touchpad), are also used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and / or touchpad).

[0062] In the following discussion, electronic devices are described that include a display and a touch-sensitive surface. 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.

[0063] The device typically supports a variety of applications such as one or more of a drawing application, a presentation application, a word processing application, a website creation application, a disc authoring application, a spreadsheet application, a gaming 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.

[0064] Various applications running on the device optionally use at least one common physical user-interface device, such as a touch-sensitive surface. One or more features of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or changed for each application and / or within each application. In this way, the common physical architecture of the device (such as the touch-sensitive surface) optionally supports various applications with user interfaces that are intuitive and transparent to the user.

[0065] Attention now turns to embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating portable multifunction device 100 having touch-sensitive display system 112 according to some embodiments. Touch-sensitive display 112 may conveniently be referred to as a "touch screen" and may also be known or referred to as a "touch-sensitive display system." Device 100 includes memory 102 (optionally including one or more computer-readable storage media), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input / output (I / O) subsystem 106, other input control devices 116, and external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 that detect the intensity of a contact on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 that generate tactile output on device 100 (e.g., generate tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0066] As used herein and in the claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or a proxy for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​that includes at least four distinct values ​​and more typically includes hundreds (e.g., at least 256) distinct values. The intensity of a contact is optionally determined (or measured) using various techniques and various sensors or combinations of sensors. For example, one or more force sensors under or adjacent to the touch-sensitive surface are optionally used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted average) to determine an 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-sensitive surface. Alternatively, the size and / or change in the contact area detected on the touch-sensitive surface, the capacitance and / or change in the capacitance of the touch-sensitive surface proximate the contact, and / or the resistance and / or change in the capacitance of the touch-sensitive surface proximate the contact are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measure for the force or pressure of the contact is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is stated in units corresponding to the surrogate measure). In some implementations, the surrogate measure for the contact force or pressure is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using contact intensity as an attribute of user input allows a user to access additional device functionality that may not otherwise be accessible by a user on devices of reduced size that have limited area for displaying affordances (e.g., on a touch-sensitive display) and / or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls such as knobs or buttons).

[0067] As used herein and in the claims, the term “tactile output” refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, that will be detected by a user with the user's sense of touch. For example, in a situation where a device or a component of a device is in contact with a touch-sensitive surface of a user (e.g., the fingers, palm, or other part of the user's hand), the tactile output produced by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical property of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a “downclick” or “upclick” of a physical actuator button. In some cases, a user feels a tactile sensation such as a “downclick” or “upclick” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's action. As another example, movement of a touch-sensitive surface is optionally interpreted or perceived by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. While such user interpretation of touch depends on the user's personal sensory perception, there are many sensory perceptions of touch that are common to the majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "upclick," "downclick," "roughness"), unless otherwise specified, the generated tactile output corresponds to a physical displacement of the device, or a component of the device, that produces the described sensory perception for a typical (or average) user.

[0068] It should be understood that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than those shown, optionally combines two or more components, or optionally has a different configuration or arrangement of its components. The various components shown in Figure 1A are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing circuits and / or application specific integrated circuits.

[0069] Memory 102 optionally includes high-speed random access memory, and 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.

[0070] Peripheral interface 118 may be used to couple input and output peripherals 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 and process data for device 100. 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.

[0071] RF (radio frequency) circuitry 108 transmits and receives RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to or from electromagnetic signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry 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, etc. RF circuitry 108 optionally communicates wirelessly with networks, such as the Internet, also known as the World Wide Web (WWW), an intranet, and / or wireless networks, such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and with other devices. RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by short-range radios. Wireless communication optionally includes, but is not limited to, Global System for Mobile Communications (GSM), 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-HSPA), Long Term Evolution (LTE), and other wireless technologies.Wireless technology includes, but is not limited to, technology such as: LTE evolution (LTE), near field communications (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., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and / or IEEE 802.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), and the like. The present invention may use any of a number of communication standards, protocols, and technologies, including the Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (XMPP), the Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), the Instant Messaging and Presence Service (IMPS), and / or the Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this application.

[0072] Audio circuit 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuit 110 receives audio data from peripherals interface 118, converts the audio data into electrical signals, and transmits the electrical signals to speaker 111. Speaker 111 converts the electrical signals into sound waves audible to humans. Audio circuit 110 also receives electrical signals converted from sound waves by microphone 113. Audio circuit 110 converts the electrical signals into audio data and transmits the audio data to peripherals interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to memory 102 and / or RF circuit 108 by peripherals interface 118. In some embodiments, audio circuit 110 also includes a headset jack (e.g., 212 in FIG. 2 ). The headset jack provides an interface between audio circuitry 110 and a detachable audio input / output peripheral, such as an output-only headphone or a headset with both an output (e.g., single or double ear headphones) and an input (e.g., a microphone).

[0073] I / O subsystem 106 couples input / output peripherals on device 100, such as touchscreen 112 and other input control devices 116, to peripheral interface 118. I / O subsystem 106 optionally includes display controller 156, light sensor controller 158, depth camera controller 169, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. One or more input controllers 160 receive / send electrical signals from / to other input control devices 116. Other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, etc. In some alternative embodiments, input controller(s) 160 are optionally coupled to any (or none) of a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208 in FIG. 2) optionally include up and down buttons for volume control of speaker 111 and / or microphone 113. The one or more buttons optionally include a push button (e.g., 206 in FIG. 2).

[0074] 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," U.S. Patent No. 7,657,849, which is incorporated herein by reference in its entirety, a quick press of the push button optionally disengages a lock on the touchscreen 112 or, optionally, initiates a process to unlock the device using a gesture on the touchscreen. A longer press of a push button (e.g., 206) optionally turns power on or off to the device 100. The functionality of one or more of the buttons is optionally customizable by the user. The touchscreen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

[0075] Touch-sensitive display 112 provides an input and output interface between the device and a user. Display controller 156 receives and / or sends electrical signals to touchscreen 112. Touchscreen 112 displays visual output to the user. This visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output optionally corresponds to user-interface objects.

[0076] Touchscreen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from a user based on haptic and / or tactile contact. Touchscreen 112 and display controller 156 (along with any associated modules and / or instruction sets in memory 102) detects contacts (and any movement or cessation of contact) on touchscreen 112 and translates the detected contacts into interactions with user interface objects (e.g., one or more softkeys, icons, web pages, or images) displayed on touchscreen 112. In an exemplary embodiment, the point of contact between touchscreen 112 and the user corresponds to the user's finger.

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

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

[0079] The touch-sensitive display in some embodiments of touch screen 112 may be any of the touch-sensitive displays described in U.S. patent application Ser. No. 11 / 381,313, filed May 2, 2006, entitled "Multipoint Touch Surface Controller," (2) U.S. patent application Ser. No. 10 / 840,862, filed May 6, 2004, entitled "Multipoint Touchscreen," (3) U.S. patent application Ser. No. 10 / 903,964, filed July 30, 2004, entitled "Gestures For Touch Sensitive Input Devices," (4) U.S. patent application Ser. No. 11 / 048,264, filed January 31, 2005, entitled "Gestures For Touch Sensitive Input Devices," and (5) U.S. patent application Ser. No. 11 / 038,590, filed January 18, 2005, entitled "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices." No. 11 / 228,758, filed September 16, 2005, entitled "Virtual Input Device Placement On A Touch Screen User Interface," (7) U.S. Patent Application No. 11 / 228,700, filed September 16, 2005, entitled "Operation Of A Computer With A Touch Screen Interface," (8) U.S. Patent Application No. 11 / 228,737, filed September 16, 2005, entitled "Activating Virtual Keys Of A Touch-Screen Virtual Keyboard," and (9) U.S. Patent Application No. 11 / 367,749, filed March 3, 2006, entitled "Multi-Functional Hand-Held Device," all of which are incorporated herein by reference in their entirety.

[0080] Touchscreen 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. A user optionally contacts touchscreen 112 using any suitable object or accessory, such as a stylus, finger, or the like. In some embodiments, the user interface is designed to primarily handle finger-based contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of ​​a finger on the touchscreen. In some embodiments, the device translates the coarse finger input into precise pointer / cursor positions or commands to perform the action desired by the user.

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

[0082] Device 100 also includes a power system 162 that provides power to the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, power failure detection circuitry, power converters or inverters, power status indicators (e.g., light emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of electrical power within a portable device.

[0083] Device 100 also optionally includes one or more light sensors 164. FIG. 1A shows a light sensor coupled to light sensor controller 158 in I / O subsystem 106. Light sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Light sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. Light sensor 164 optionally works in conjunction with imaging module 143 (also called a camera module) to capture still images or video. In some embodiments, the light sensor is located on the back of device 100, as opposed to touchscreen display 112, which is on the front of the device, so that the touchscreen display is effectively used as a viewfinder for capturing still and / or video images. In some embodiments, the light sensor is located on the front of the device so that an image of the user is obtained, optionally for video conferencing, and the user sees other video conference participants on the touchscreen display. In some embodiments, the position of the light sensor 164 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), so that a single light sensor 164 is used for both video conferencing and capturing still and / or video images, along with the touchscreen display.

[0084] Device 100 also optionally includes one or more depth camera sensors 175. FIG. 1A shows a depth camera sensor coupled to depth camera controller 169 in I / O subsystem 106. Depth camera sensor 175 receives data from the environment and creates a three-dimensional model of an object (e.g., a face) in a scene from a viewpoint (e.g., the depth camera sensor). In some embodiments, in conjunction with imaging module 143 (also referred to as a camera module), depth camera sensor 175 is optionally used to determine a depth map of various portions of an image captured by imaging module 143. In some embodiments, a depth camera sensor is located on the front of device 100 so that images of the user with depth information are optionally obtained for videoconferences and to capture selfie images with depth map data while the user views other videoconference participants on a touchscreen display. In some embodiments, depth camera sensor 175 is located on the back of the device or on both the back and front of 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), so that the depth camera sensor 175 is used for both video conferencing and capturing still and / or video images, along with a touchscreen display.

[0085] Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I / O subsystem 106. Contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). 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 the touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touchscreen display 112, which is located on the front of device 100.

[0086] Device 100 also optionally includes one or more proximity sensors 166. Figure 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternatively, proximity sensor 166 is optionally coupled to input controller 160 within I / O subsystem 106. Proximity sensor 166 optionally functions as described in U.S. patent application Ser. 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 incorporated herein by reference in their entireties. In some embodiments, the proximity sensor turns off and disables touchscreen 112 when the multifunction device is placed near the user's ear (e.g., when the user is on a phone call).

[0087] Device 100 also optionally includes one or more tactile output generators 167. FIG. 1A shows tactile output generators 167 coupled to haptic feedback controller 161 in I / O subsystem 106. Tactile output generator 167 optionally includes one or more electroacoustic devices, such as speakers or other audio components, and / or electromechanical devices that convert energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile output on the device). Contact intensity sensor 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates a tactile output on device 100 that can be sensed by a user of device 100. In some embodiments, at least one tactile output generator is juxtaposed with or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112) and generates a tactile output, optionally by moving the touch-sensitive surface vertically (e.g., in / out of the surface of device 100) or horizontally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touchscreen display 112, which is located on the front of device 100.

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

[0089] In some embodiments, software components stored in memory 102 include operating system 126, communications module (or instruction set) 128, touch / motion module (or instruction set) 130, graphics module (or instruction set) 132, text input module (or instruction set) 134, Global Positioning System (GPS) module (or instruction set) 135, and applications (or instruction set) 136. Additionally, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) stores device / global internal state 157, as shown in FIGS. 1A and 3. Device / global internal state 157 includes one or more of: active application state indicating which applications, if any, are currently active; display state indicating which applications, views, or other information occupy various regions of touchscreen display 112; sensor state including information obtained from the device's various sensors and input control devices 116; and location information regarding the device's position and / or orientation.

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

[0091] Communications 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 RF circuitry 108 and / or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE®, etc.) is adapted to couple to other devices directly or indirectly via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, similar to, and / or compatible with the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.

[0092] Contact / motion module 130, optionally in conjunction with display controller 156, detects contact with touch screen 112 and other touch-sensing devices (e.g., a touchpad or physical click wheel). Contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether contact occurs (e.g., detecting a finger-down event), determining the intensity of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there is contact movement and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-drag events), and determining whether the contact has stopped (e.g., detecting a finger-up event or an interruption of the contact). Contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact, as represented by the 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. These actions are optionally applied to a single contact (e.g., a single finger contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some embodiments, contact / motion module 130 and display controller 156 detect contacts on the touchpad.

[0093] In some embodiments, contact / motion module 130 uses a set of one or more intensity thresholds for determining whether an action has been performed by a user (e.g., for determining whether a 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 are not determined by the activation threshold of a particular physical actuator, but can be adjusted without changing the physical hardware of device 100). For example, the mouse “click” threshold of a trackpad or touchscreen display can be set to any of a wide range of pre-defined thresholds without changing the trackpad or touchscreen display hardware. Additionally, in some implementations, a device user 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 multiple intensity thresholds at once via a system-level click “intensity” parameter).

[0094] Contact / motion module 130 optionally detects gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different movements, timing, and / or intensities of detected contacts). Thus, gestures are optionally detected by detecting particular contact patterns. 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 location (or substantially the same location) as the finger down event (e.g., the location of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger down event, followed by one or more finger drag events, followed by detecting a finger up (lift off) event.

[0095] Graphics module 132 includes various known software components that render and display graphics on touchscreen 112 or other display, including components that vary the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual characteristics) of the displayed graphics. As used herein, the term "graphic" includes any object that can be displayed to a user, including, but not limited to, characters, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

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

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

[0098] Text input module 134 is optionally a component of graphics 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 requiring text input).

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

[0100] Application 136 optionally includes the following modules (or sets of instructions), or a subset or superset thereof: • a contacts module 137 (sometimes called an address book or contact list); ●Telephone module 138, ●Videoconferencing module 139, ● an email client module 140; ● Instant messaging (IM) module 141, ●Training support module 142, a camera module 143 for still and / or video images, ● Image management module 144; ●Video player module, ●Music player module, ● Browser module 147, ● Calendar module 148, a widget module 149 optionally including 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, and a user-created widget 149-6; a widget creation module 150 for creating user-created widgets 149-6; ● Search module 151, A video and music player module 152 that integrates a video player module and a music player module; ● Memo module 153, Map module 154, and / or ●Online video module 155.

[0101] Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice duplication.

[0102] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, contacts module 137 is used to manage an address book or contact list (e.g., stored in memory 102 or in the application internal state 192 of contacts module 137 in memory 370), optionally including adding name(s) to the address book, deleting name(s) from the address book, associating phone number(s), email address(es), physical address(es), or other information with names, associating images with names, categorizing and sorting names, providing phone numbers or email addresses to initiate and / or facilitate communication by phone 138, videoconferencing module 139, email 140, or IM 141, etc.

[0103] Telephone module 138, in conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, is optionally used to enter character sequences corresponding to telephone numbers, access one or more telephone numbers in contacts module 137, modify entered telephone numbers, dial respective telephone numbers, conduct conversations, and terminate or hang up when the conversation is completed. As previously mentioned, wireless communication optionally uses any of a number of communication standards, protocols, and technologies.

[0104] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, light sensor 164, light sensor controller 158, touch / motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, videoconferencing module 139 includes executable instructions for initiating, conducting, and terminating a videoconference between a user and one or more other participants in accordance with user commands.

[0105] In cooperation with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, email client module 140 contains executable instructions for composing, sending, receiving, and managing emails in response to user commands. In cooperation with image management module 144, email client module 140 greatly facilitates the creation and sending of emails with still or video images captured by camera module 143.

[0106] In cooperation with RF circuitry 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for entering character sequences corresponding to instant messages, modifying previously entered characters, sending respective instant messages (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephony-based instant messaging, or XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, sent and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0107] In conjunction with the RF circuitry 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, the training support module 142 includes executable instructions for creating workouts (e.g., with time, distance, and / or calorie burn goals), communicating with training sensors (sports devices), receiving training sensor data, calibrating sensors used to monitor workouts, selecting and playing music for workouts, and displaying, storing, and transmitting workout data.

[0108] In conjunction with touch screen 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact / motion module 130, graphics module 132, and image management module 144, camera module 143 contains executable instructions for capturing and storing still images or video (including video streams) in memory 102, modifying characteristics of the still images or video, or deleting the still images or video from memory 102.

[0109] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 contains executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slide show or album), and storing still and / or video images.

[0110] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, browser module 147 contains executable instructions for browsing the Internet according to user commands, including retrieving, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0111] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, calendar module 148 contains executable instructions for creating, displaying, modifying, and storing calendars and data associated with calendars (e.g., calendar items, to-do lists, etc.) in accordance with user instructions.

[0112] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, widget module 149 is optionally a mini-application downloaded and used by a user (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), or a mini-application created by a user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).

[0113] In conjunction with RF circuitry 108, touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, widget creator module 150 is optionally used by a user to create a widget (e.g., turn a user-specified portion of a web page into a widget).

[0114] In cooperation with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions for searching for text, music, sound, images, video, and / or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user commands.

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

[0116] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, notes module 153 contains executable instructions for creating and managing notes, to-do lists, and the like according to user commands.

[0117] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 is used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data regarding businesses and other points of interest at or near a particular location, and other location-based data), optionally in accordance with user instructions.

[0118] In cooperation with touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, online video module 155 contains instructions that enable a user to access, browse for, receive (e.g., by streaming and / or downloading), and play (e.g., on the touchscreen or on an external display connected via external port 124) particular online videos, send emails with links to particular online videos, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141 is used to send links to particular online videos, rather than email client module 140. Additional description of online video applications can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed June 20, 2007, entitled "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," and U.S. Patent Application No. 11 / 968,067, filed December 31, 2007, entitled "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," the contents of which are incorporated herein by reference in their entireties.

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

[0120] In some embodiments, device 100 is a device in which operation of a predetermined set of functions on the device is performed solely via a touchscreen and / or touchpad. Using the touchscreen and / or touchpad as the primary input control device for operation of device 100 optionally reduces the number of physical input control devices (push buttons, dials, etc.) on device 100.

[0121] The set of predefined functions performed only through the touchscreen and / or touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 to a main menu, home menu, or root menu from any user interface displayed on device 100. In such embodiments, a "menu button" is implemented using the touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device rather than a touchpad.

[0122] 1B is a block diagram illustrating exemplary components for event processing according to some embodiments. In some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., within operating system 126) and a respective application 136-1 (e.g., any of applications 137-151, 155, 380-390 described above).

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

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

[0125] Event monitor 171 receives event information from peripherals interface 118. The event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, accelerometer(s) 168, and / or microphone 113 (via audio circuitry 110). Information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

[0126] In some embodiments, event monitor 171 sends requests to peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receipt of an input above a predetermined noise threshold and / or for more than a predetermined duration).

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

[0128] Hit view determination module 172 provides software procedures that determine where a sub-event occurred within one or more views when touch-sensitive display 112 displays more than one view. A view consists of the controls and other elements that a user can see on the display.

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

[0130] Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized hierarchically, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should process the sub-events. In most situations, the hit view is the lowest-level view in which an initiating sub-event (e.g., the first sub-event in a sequence of sub-events that form an event or potential event) occurs. Once a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source as the hit view.

[0131] Active event recognizer determination module 173 determines which view(s) in the view hierarchy should receive the particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive the particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that contain the physical location of the sub-event are actively participating views, and therefore all actively participating views should receive the particular sequence of sub-events. In other embodiments, even if the touch sub-event is completely confined to the area associated with one particular view, views higher in the hierarchy still remain actively participating views.

[0132] Event dispatcher module 174 dispatches event information to event recognizers (e.g., event recognizer 180). In embodiments that include active event recognizer determination module 173, event dispatcher module 174 delivers the event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores event information obtained by each event receiver 182 in an event queue.

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

[0134] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each containing instructions for processing touch events that occur within a respective view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, each application view 191 includes multiple event recognizers 180. In other embodiments, one or more of event recognizers 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 attributes. In some embodiments, each event handler 190 includes one or more of data updater 176, object updater 177, GUI updater 178, and / or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or invokes data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in each application view 191.

[0135] Each event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, event recognizer 180 also includes metadata 183 and at least a subset of event delivery instructions 188 (optionally including sub-event delivery instructions).

[0136] Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, e.g., a touch or a movement of a touch. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves a touch movement, 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 device's current orientation (also called the device's attitude).

[0137] The event comparator 184 compares the event information with predefined event or sub-event definitions and determines the event or sub-event, or determines or updates the state of the event or sub-event, based on the comparison. In some embodiments, the event comparator 184 includes an event definition 186. The event definition 186 includes definitions of events (e.g., a predefined sequence of sub-events), such as Event 1 (187-1) and Event 2 (187-2). In some embodiments, sub-events within Event 1 (187) include, for example, touch start, touch end, touch movement, touch cancellation, and multiple touches. In one example, the definition for Event 1 (187-1) is a double tap on a displayed object. The double tap includes, for example, a first touch on a displayed object relative to a predetermined stage (touch start), a first lift-off (touch end) relative to the predetermined stage, a second touch on a displayed object relative to the predetermined stage (touch start), and a second lift-off (touch end) relative to the predetermined stage. In another example, a definition of event 2 (187-2) is a drag on a displayed object. Drag includes, for example, a touch (or contact) on the displayed object to 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 handlers 190.

[0138] In some embodiments, event definition 187 includes a definition of the event for each user interface object. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, when a touch is detected on touch-sensitive display 112 in an application view in which three user interface objects are displayed on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, event comparator 184 uses the results of the hit test to determine which event handler 190 to activate. For example, event comparator 184 selects the event handler associated with the sub-event and object that triggers the hit test.

[0139] In some embodiments, each event 187 definition also includes a delay action that delays delivery of the event information until it is determined whether the sequence of sub-events corresponds to the event type of the event recognizer.

[0140] If the respective event recognizer 180 determines that the sequence of sub-events does not match any of the events in the event definition 186, the respective event recognizer 180 enters an event-disabled, event-failed, or event-ended state and thereafter ignores the next sub-event of the touch-based gesture. In this situation, any other event recognizers that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

[0141] In some embodiments, each event recognizer 180 includes metadata 183 with configurable properties, flags, and / or lists that indicate to actively participating event recognizers how the event delivery system should perform sub-event delivery. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognizers interact with each other or how event recognizers are allowed to interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how sub-events are delivered to various levels in the view or programmatic hierarchy.

[0142] In some embodiments, each event recognizer 180 activates an event handler 190 associated with an event when one or more specific sub-events of the event are recognized. In some embodiments, each event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is separate from sending (and postponing sending) sub-events to the respective hit view. In some embodiments, the event recognizer 180 pops a flag associated with the recognized event, and the event handler 190 associated with the flag captures the flag and performs a predetermined process.

[0143] In some embodiments, the event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver the event information to an event handler associated with a set of sub-events or to an actively participating view. The event handler associated with the set of sub-events or the actively participating view receives the event information and performs predetermined processing.

[0144] In some embodiments, data updater 176 creates and updates data used by application 136-1. For example, data updater 176 updates phone numbers used by contacts module 137 or stores video files used by a video player module. In some embodiments, object updater 177 creates and updates objects used by application 136-1. For example, object updater 177 creates new user interface objects or updates the positions of user interface objects. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends the display information to graphics module 132 for display on the touch-sensitive display.

[0145] In some embodiments, event handler(s) 190 include or have access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of the respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

[0146] It should be understood that the foregoing description of event processing of a user's touch on a touch-sensitive display also applies to other forms of user input for operating multifunction device 100 using input devices, not all of which are initiated on the touchscreen. For example, mouse movements and mouse button presses, contact movements such as tapping, dragging, scrolling on a touchpad, optionally coordinated with single or multiple keyboard presses or holds, pen stylus input, device movement, verbal commands, detected eye movement, biometric input, and / or any combination thereof, optionally utilize as inputs corresponding to sub-events that define the recognized event.

[0147] FIG. 2 illustrates portable multifunction device 100 having touchscreen 112, according to some embodiments. The touchscreen optionally displays one or more graphics within user interface (UI) 200. In this embodiment, as well as other embodiments described below, a user may select one or more of the graphics by performing a gesture on the graphics, for example, using one or more fingers 202 (not drawn to scale) or one or more styluses 203 (not drawn to scale). In some embodiments, selection of one or more graphics is performed when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, upward and / or downward), and / or rolling of a finger in contact with device 100 (right to left, left to right, upward and / or downward). In some implementations or situations, accidental contact with a graphic does not select the graphic, for example, if the gesture corresponding to selection is a tap, a swipe gesture sweeping over an application icon optionally does not select the corresponding application.

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

[0149] In some embodiments, device 100 includes touchscreen 112, menu button 204, pushbuttons 206 for powering the device on / off and locking the device, volume control buttons 208, subscriber identity module (SIM) card slot 210, headset jack 212, and external docking / charging port 124. Pushbutton 206 is optionally used to power the device on / off by pressing and holding the button down for a predetermined period of time, to lock the device by pressing and releasing the button before the predetermined time has elapsed, and / or to unlock the device or initiate the unlocking process. In alternative embodiments, device 100 also accepts verbal input via microphone 113 for activating or deactivating some functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on touchscreen 112 and / or one or more tactile output generators 167 for generating a tactile output for a user of device 100.

[0150] FIG. 3 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface, according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child's learning toy), a gaming system, or a control device (e.g., a home or commercial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 interconnecting these components. Communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects and controls communication between system components. Device 300 includes input / output (I / O) interface 330, including display 340, which is typically a touchscreen display. I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350, a touchpad 355, a tactile output generator 357 (e.g., similar to tactile output generator 167 described above with reference to FIG. 1A ) that generates tactile output on device 300, and sensors 359 (e.g., light, acceleration, proximity, touch-sensing, and / or contact intensity sensors similar to contact intensity sensor 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 located remotely from CPU(s) 310.In some embodiments, memory 370 stores programs, modules, and data structures similar to, or a subset of, programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A). Additionally, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, ​​word processing module 384, website creation module 386, disc authoring module 388, and / or spreadsheet module 390, whereas memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

[0151] Each of the above-identified elements of FIG. 3 is optionally stored in one or more of the memory devices mentioned above. Each of the above-identified modules corresponds to an instruction set that performs the function described above. The above-identified modules or programs (e.g., instruction sets) need not be implemented as separate software programs, procedures, or modules; 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 above-identified modules and data structures. Additionally, memory 370 optionally stores additional modules and data structures not described above.

[0152] Attention is now directed to user interface embodiments, optionally implemented on portable multifunction device 100, for example.

[0153] 4A shows an exemplary user interface for a menu of applications on portable multifunction device 100 according to some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, 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 and Wi-Fi® signals; ●Time 404, ●Bluetooth indicator 405, ● Battery status indicator 406, Tray 408 with icons of frequently used applications, such as: An icon 416 for 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; ○ An icon 420 for the browser module 147, labeled "Browser"; and ○ An icon 422 of the video and music player module 152, also called the iPod (trademark of Apple Inc.) module 152, labeled "iPod"; and ● Icons of other applications, such as: ○ Icon 424 of IM module 141, labeled "Messages" icon 426 of the calendar module 148, labeled "Calendar"; ○ Icon 428 of the image management module 144, labeled "Photos" ○ An icon 430 of the camera module 143, labeled "camera"; ○ Icon 432 of the online video module 155, labeled "Online Video"; Icon 434 of Stock Price Widget 149-2, labeled "Stock Price" ○ Icon 436 of the map module 154, labeled "Map" ○ Icon 438 of Weather widget 149-1, labeled "Weather" ○ Icon 440 of alarm clock widget 149-4, labeled "Clock" ○ Icon 442 of Training Support Module 142, labeled "Training Support"; ○ An icon 444 of the Notes module 153 labeled "Notes," and A settings application or module icon 446 labeled "Settings" that provides access to settings for the device 100 and its various applications 136.

[0154] 4A are merely exemplary. For example, icon 422 for video and music player module 152 may be labeled "Music" or "Music Player," although other labels are optionally used for the various application icons. In some embodiments, the label for each application icon includes the name of the application corresponding to the respective 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.

[0155] 4B shows an example user interface on a device (e.g., device 300 of FIG. 3 ) that has touch-sensitive surface 451 (e.g., tablet or touchpad 355 of FIG. 3 ) that is separate from display 450 (e.g., touchscreen display 112). Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) that detect the intensity of a contact on touch-sensitive surface 451, and / or one or more tactile output generators 357 that generate a tactile output for a user of device 300.

[0156] Although some of the following examples are given with reference to input on touchscreen display 112 (which combines a touch-sensitive surface and a display), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display shown in FIG. 4B . In some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B ) has a primary axis (e.g., 452 in FIG. 4B ) that corresponds to a primary axis (e.g., 453 in FIG. 4B ) on the display (e.g., 450). According to these embodiments, the device detects contact with touch-sensitive surface 451 (e.g., 460 and 462 in FIG. 4B ) at locations that correspond to respective locations on the display (e.g., in FIG. 4B , 460 corresponds to 468 and 462 corresponds to 470). In this way, user input (e.g., contacts 460 and 462 and their movement) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B ) is used by the device to operate a user interface on the display (e.g., 450 in FIG. 4B ) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are optionally used for the other user interfaces described herein.

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

[0158] FIG. 5A shows an exemplary personal electronic device 500. Device 500 includes a main body 502. In some embodiments, device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1A-4B ). In some embodiments, device 500 has a touch-sensitive display screen 504, hereafter referred to as touchscreen 504. Alternatively, or in addition to touchscreen 504, device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, touchscreen 504 (or the touch-sensitive surface) optionally includes one or more intensity sensors that detect the intensity of contact (e.g., touch) being applied. The one or more intensity sensors of touchscreen 504 (or the touch-sensitive surface) can provide output data representing the intensity of the touch. A user interface of device 500 can respond to a touch based on the intensity of the touch, meaning that touches of different intensities can invoke different user interface actions on device 500.

[0159] Exemplary techniques for detecting and processing touch intensity can be found, for example, in International Patent Application No. PCT / US2013 / 040061, filed May 8, 2013, entitled "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application," published as International Patent Application No. WO / 2013 / 169849, and related applications, including International Patent Application No. PCT / US2013 / 069483, filed November 11, 2013, entitled "Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships," published as International Patent Application No. WO / 2014 / 105276, each of which is incorporated herein by reference in its entirety.

[0160] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical mechanisms. 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 allow device 500 to be attached to, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch bands, chains, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow a user to wear device 500.

[0161] FIG. 5B illustrates 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. I / O section 514 can be connected to a display 504, which can have touch-sensing components 522 and, optionally, an intensity sensor 524 (e.g., a contact intensity sensor). Additionally, 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 techniques. Device 500 can include input mechanisms 506 and / or 508. Input mechanism 506 is optionally a rotatable input device or a depressible and rotatable input device, for example. In some examples, input mechanism 508 is optionally a button.

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

[0163] The memory 518 of the personal electronic device 500 may 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, may cause the computer processors to perform the techniques described below, including processes 700, 900, and 1100 (FIGS. 7A-7B, 9, 11A-11D, 13, 15A-15C). A computer-readable storage medium may be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some embodiments, the storage medium is a transient computer-readable storage medium. In some embodiments, the storage medium is a non-transitory computer-readable storage medium. A non-transitory computer-readable storage medium may include, but is not limited to, magnetic, optical, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, CDs, DVDs, or optical disks based on Blu-ray® technology, as well as resident solid-state memory such as flash, solid-state drives, etc. Personal electronic device 500 is not limited to the components and configuration of FIG. 5B and may include other or additional components in multiple configurations.

[0164] As used herein, the term "affordance" refers to a user-interactive graphical user interface object that is optionally displayed on the display screen of device 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.

[0165] 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 involving a cursor or other location marker, the cursor acts as the “focus selector,” such that when input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 of FIG. 3 or touch-sensitive surface 451 of FIG. 4B) while the cursor is positioned over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations involving a touchscreen display (e.g., touch-sensitive display system 112 of FIG. 1A or touchscreen 112 of FIG. 4A) that enables direct interaction with user interface elements on the touchscreen display, a detected contact on the touchscreen acts as the “focus selector,” such that when 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 touchscreen display, the particular user interface element is adjusted according to the detected input. In some implementations, focus is moved from one region of the user interface to another region of the user interface without a corresponding cursor movement or contact movement on the touchscreen display (e.g., by using the tab key or arrow keys to move focus from one button to another), and in these implementations, the focus selector moves to follow the movement of focus between various regions of the user interface. Regardless of the particular form the focus selector takes, the focus selector is generally a user interface element (or contact on a touchscreen 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 element of the user interface with which the user intends to interact).For example, location of a focus selector (e.g., cursor, touch, or selection box) over a corresponding button while a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen) indicates that the user intends to activate that corresponding button (and not other user interface elements shown on the device's display).

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

[0167] FIG. 5C illustrates detecting multiple contacts 552A-552E on the touch-sensitive display screen 504 by multiple intensity sensors 524A-524D. FIG. 5C additionally includes an intensity diagram illustrating the current intensity measurements of intensity sensors 524A-524D relative to intensity units. In this example, intensity sensors 524A and 524D each measure 9 intensity units, and intensity sensors 524B and 524C each measure 7 intensity units. In some implementations, the aggregate intensity is the sum of the intensity measurements of multiple intensity sensors 524A-524D, which in this example is 32 intensity units. In some embodiments, each contact is assigned a respective intensity that is a fraction of the aggregate intensity. FIG. 5D illustrates assigning aggregate intensities to contacts 552A-552E based on their distance from the center of force 554. In this example, contacts 552A, 552B, and 552E are each assigned a contact intensity of 8 intensity units of aggregate intensity, and contacts 552C and 552D are each assigned a contact intensity of 4 intensity units of aggregate intensity. More generally, in some implementations, each contact j is assigned a respective intensity Ij, which is a fraction of a total intensity A, according to a predetermined mathematical function Ij=A·(Dj / ΣDi), where Dj is the distance from the center of force to the respective contact j, and ΣDi is the sum of the distances from the center of force to all respective contacts (e.g., from i=1 to the end). The operations described with reference to FIGS. 5C-5D can be performed using electronic devices similar to or identical to device 100, 300, or 500. In some embodiments, the characteristic intensity of a contact is based on one or more intensities of the contact. In some embodiments, an intensity sensor is used to determine a single characteristic intensity (e.g., a single characteristic intensity of a single contact). Note that the intensity diagrams are not part of the displayed user interface, but are included in FIGS. 5C-5D as an aid to the reader.

[0168] In some embodiments, a portion of the gesture is identified for purposes of determining the characteristic intensity. For example, the touch-sensitive surface optionally receives successive swipe contacts that transition from a start location to an end location, at which point the intensity of the contacts increases. In this example, the characteristic intensity of the contacts at the end location is optionally based on only a portion of the successive swipe contacts (e.g., only the portion of the swipe contacts at the end location) rather than the entire swipe contact. In some embodiments, a smoothing algorithm is optionally applied to the intensity of the swipe contacts before determining the characteristic intensity of the contacts. For example, the smoothing algorithm optionally includes one or more of an unweighted 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 small increases or decreases in the intensity of the swipe contacts for purposes of determining the characteristic intensity.

[0169] The intensity of the contact on the touch-sensitive surface is optionally characterized with respect 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 corresponds to an intensity at which the device performs an action typically associated with clicking a physical mouse button or trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device performs an action different from an action typically associated with clicking a physical mouse button or trackpad. In some embodiments, when a contact is detected having a characteristic intensity below the light press intensity threshold (e.g., above a nominal contact-detection intensity threshold below which the contact is not detected), the device moves the focus selector in accordance with the movement of the contact on the touch-sensitive surface without performing an action associated with the light press intensity threshold or the deep press intensity threshold. In general, unless otherwise specified, these intensity thresholds are consistent across the various sets of user interface diagrams.

[0170] An increase in the characteristic intensity of a contact from an intensity below the light pressure intensity threshold to an intensity between the light pressure intensity threshold and the deep pressure intensity threshold may be referred to as inputting a "light press." An increase in the characteristic intensity of a contact from an intensity below the deep pressure intensity threshold to an intensity above the deep pressure intensity threshold may be referred to as inputting a "deep press." An increase in the characteristic intensity of a contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light pressure intensity threshold may be referred to as detecting 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 detecting 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.

[0171] In some embodiments described herein, one or more actions are performed in response to detecting a gesture including the respective pressure input or in response to detecting the respective pressure input performed by the respective contact(s), where the respective pressure inputs are detected based at least in part on detecting an increase in intensity of the contact(s) above a pressure input intensity threshold. In some embodiments, the respective actions are performed in response to detecting an increase in intensity of the respective contact(s) above a pressure input intensity threshold (e.g., a “downstroke” of the respective pressure input). In some embodiments, the pressure input includes an increase in intensity of the respective contact(s) above a pressure input intensity threshold followed by a decrease in intensity of the contact(s) below the pressure input intensity threshold, and the respective actions are performed in response to detecting a subsequent decrease in intensity of the respective contact(s) below the pressure input threshold (e.g., an “upstroke” of the respective pressure input).

[0172] 5E-5H illustrate the detection of a gesture including a press input corresponding to an increase in the intensity of contact 562 from an intensity below a light press intensity threshold (e.g., "ITL") in FIG. 5E to an intensity above a deep press intensity threshold (e.g., "ITD") in FIG. 5H. The gesture performed by contact 562 is detected on touch-sensitive surface 560, and cursor 576 is displayed over application icon 572B corresponding to app2 on display user interface 570, which includes application icons 572A-572D displayed within predetermined region 574. In some embodiments, the gesture is detected on touch-sensitive display 504. An intensity sensor detects the intensity of the contact on touch-sensitive surface 560. The device determines that the intensity of contact 562 peaks above a deep press intensity threshold (e.g., "ITD"). Contact 562 is maintained on touch-sensitive surface 560. In response to detecting the gesture, contact 562 having an intensity above a deep press intensity threshold (e.g., "ITD") during the gesture causes reduced-scale representations 578A-578C (e.g., thumbnails) of recently opened documents to app2 to be displayed, as shown in FIGS. 5F-5H. In some embodiments, this intensity that is compared to one or more intensity thresholds is a characteristic intensity of the contact. Note that the intensity diagrams for contact 562 are not part of the displayed user interface, but are included in FIGS. 5E-5H as an aid to the reader.

[0173] In some embodiments, the display of representations 578A-578C includes animation. For example, as shown in FIG. 5F, representation 578A is initially displayed adjacent to application icon 572B. As the animation progresses, representation 578A moves upward and representation 578B is displayed adjacent to application icon 572B, as shown in FIG. 5G. Then, as shown in FIG. 5H, representation 578A moves upward, representation 578B moves upward toward representation 578A, and representation 578C is displayed adjacent to application icon 572B. Representations 578A-578C form an array above icon 572B. In some embodiments, the animation progresses according to the intensity of contact 562, as shown in FIGS. 5F-5G, with representations 578A-578C appearing and moving upward as the intensity of contact 562 increases toward a deep press intensity threshold (e.g., "ITD"). In some embodiments, the intensity on which the animation progression is based is a characteristic intensity of the contact. The operations described with reference to FIGS. 5E-5H can be performed using an electronic device similar to or identical to device 100, 300, or 500.

[0174] In some embodiments, the device employs intensity hysteresis to avoid accidental input, sometimes referred to as “jitter,” and the device defines or selects a hysteresis intensity threshold that has a predetermined relationship to the pressure input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units below the pressure input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the pressure input intensity threshold). Thus, in some embodiments, the pressure input includes an increase in the intensity of each contact above the pressure input intensity threshold followed by a decrease in the intensity of the contact below the hysteresis intensity threshold corresponding to the pressure input intensity threshold, and a respective action is performed in response to detecting a subsequent decrease in the intensity of each contact below the hysteresis intensity threshold (e.g., an “upstroke” of each pressure input). Similarly, in some embodiments, a pressure input is detected only when the device detects an increase in the intensity of the contact from an intensity below the hysteresis intensity threshold to an intensity above the pressure input intensity threshold, and optionally a subsequent decrease in the intensity of the contact to an intensity below the hysteresis intensity, and a respective action is performed in response to detecting the pressure input (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact, as the case may be).

[0175] For ease of explanation, descriptions of operations performed in response to a pressure input associated with a pressure input intensity threshold, or a gesture including a pressure input, are optionally triggered in response to detecting any of: an increase in the intensity of the contact above the pressure input intensity threshold; an increase in the intensity of the contact from an intensity below a hysteresis intensity threshold to an intensity above the pressure input intensity threshold; a decrease in the intensity of the contact below the pressure input intensity threshold; and / or a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the pressure input intensity threshold. Further, in examples where an operation is described as being performed in response to detecting a decrease in the intensity of the contact below a pressure input intensity threshold, the operation is optionally performed in response to detecting a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to and lower than the pressure input intensity threshold.

[0176] 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 run (e.g., opened) on the device. In some embodiments, a downloaded application becomes an installed application by an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the computer system's operating system.

[0177] 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 application: ● the active application currently displayed on the display screen of the device on which the application is being used; background applications (or background processes) that are not currently displayed, but for which one or more processes are being processed by one or more processors; and • A suspended or hibernated application that is not running but has state information stored in memory (volatile and non-volatile respectively) and that can be used to resume execution of the application.

[0178] 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 state information for the application from the device's memory. Generally, opening a second application during a first application does not close the first application. When the second application is displayed and the first application ceases to display, the first application becomes a background application.

[0179] Attention is now directed to embodiments of user interfaces (“UIs”) and associated processes implemented on an electronic device such as portable multifunction device 100 , device 300 , device 500 , or device 600 .

[0180] 6A-6M show exemplary context-specific user interfaces that can be used to control the display of graphical elements with user input, according to some embodiments. The user interfaces in those figures are used to illustrate the processes described below, including the methods in FIGS. 7A-7B.

[0181] FIG. 6A illustrates a device 600 having a display 602 and a rotatable input mechanism 604 (e.g., rotatable relative to a housing or frame of the device). In some embodiments, device 600 is a wearable electronic device such as a smartwatch. In some embodiments, device 600 includes one or more features of devices 100, 300, or 500. As shown in FIG. 6A , device 600 displays a watch user interface 601 on display 602. Watch user interface 601 includes graphical objects 606, 608-1, 608-2, and 608-3 in FIG. 6A , where graphical object 606 includes a display of the time. As shown in FIG. 6A , the display of the time includes a representation of an analog clock face with hour hand 616-1, minute hand 616-2, and second hand 616-3. As used herein, second hand 616-3 refers to a representation of a clock hand that indicates the seconds component of the time of day, distinct from a second hand of two or more hands (e.g., a first hand, a second hand, a third hand, etc.). In some embodiments, the time display is a representation of a digital clock that includes a numerical representation of the hours and a numerical representation of the minutes.

[0182] 6A, graphical objects 608-1, 608-2, and 608-3 are complications (collectively "complications 608") corresponding to respective applications. In some embodiments, one or more of complications 608 display data from the corresponding application. In some embodiments, one or more of graphical objects 608-1, 608-2, or 608-3 is not a complication.

[0183] A complication refers to any feature of a watch face other than those used to indicate the hours and minutes of a time (e.g., clock hands or hour / minute indicators). In some embodiments, a complication provides data obtained from an application. In some embodiments, a complication includes an affordance that, when selected, launches a corresponding application. In some embodiments, a complication appears in a fixed, predetermined location on the display.

[0184] In FIG. 6A , complications 608-1, 608-2, and 608-3 occupy the bottom right, bottom left, and top left locations of watch user interface 601, respectively, while clock face 606 occupies the top right location on watch user interface 601. In FIG. 6A , each location is offset from the center of watch user interface 601. The bottom right, bottom left, and top left locations constitute a sequence of locations on display 602, with the bottom right being the first location in the sequence of locations, the bottom left being the second location in the sequence of locations, and the top left being the third (and final) location in the sequence of locations. As shown in FIG. 6A , the locations are associated with respective sizes that determine the size of the graphical object displayed in a particular location. Of the three locations in the sequence of locations, the third (final) location (top left) has the smallest size, the second location (bottom left) has the largest size, and the first location (bottom right) has a size intermediate between the sizes of the second and third locations.

[0185] In some embodiments, the locations on the watch user interface 601 are in a different order in a sequence than the order described above (e.g., top left, bottom right, bottom left; top left, bottom left, bottom right; bottom left, bottom right, top left, etc.). In some embodiments, the sequence of locations includes only two locations (e.g., bottom left and bottom right). In some embodiments, the sequence of locations includes four or more locations. In some embodiments, adjacent locations in the sequence of locations are not adjacent on the display 602. In some embodiments, the regions associated with the locations are shapes other than circular (e.g., rectangular).

[0186] In FIG. 6A, device 600 receives (e.g., detects) user input 690-1, which includes an upward (clockwise) rotation of rotatable input mechanism 604 (e.g., as can be seen by comparing the locations of the fingers shown in FIGS. 6A and 6B).

[0187] 6B, in response to receiving (e.g., detecting) user input 690-1, device 600 changes the locations where complications 608-1, 608-2, and 608-3 are displayed (e.g., based on a sequence of locations). Each complication moves to the next location in the sequence, except for complication 608-3, which moves from the third (last) location to the first location. Complication 608-1 moves out of the first location (bottom right) and appears in the second location (bottom left), complication 608-2 moves out of the second location (bottom left) and appears in the third (last) location (top left), and complication 608-3 moves out of the third (last) location (top left) and appears in the first location (bottom right).

[0188] Complications 608-1, 608-2, or 608-3 are modified when moving from one location to another: different sizes are associated with the locations, so that as complication 608-1 increases in size, complication 608-2 decreases in size and complication 608-3 increases in size.

[0189] In some embodiments, the information included in one or more complications changes when moving from one location to another. In Figure 6A, complication 608-1 includes the current temperature 610 and a partial ring 612 with an indicator showing the current temperature relative to a (e.g., forecasted) temperature range 614 of a high (86 degrees) and a low (52 degrees). As shown in Figure 6B, when displayed in a second (lower left) location, complication 608-1 further includes a weather condition indicator 618 (e.g., indicating that the current weather conditions are sunny). As another example, complication 608-3 includes a heart icon in a third location (upper left) and a display 620 of heart rate (70 BPM) in a larger first location (lower right).

[0190] In some embodiments, the information included in a complication does not change when moving from one location to another (e.g., the information included in a complication is location-independent). For example, complication 608-2 is a complication that includes a representation of the Earth currently illuminated by the Sun (e.g., showing areas of daylight and nighttime). In some embodiments, astronomical complication 608-2 includes an indicia (e.g., a dot) that indicates the location of device 600 on Earth. As shown in Figures 6A and 6B, complication 608-2 has the same appearance (except for size) in both the second (lower-left) and third (last, upper-left) locations.

[0191] 6B, device 600 receives (e.g., detects) user input 690-2, which includes rotation of rotatable input mechanism 604 in the same direction as the rotation of user input 690-1. In some embodiments, user input 690-2 is a continuation of user input 690-1. In some embodiments, user input 690-2 is separate from user input 690-1.

[0192] 6C , in response to receiving user input 690-2, device 600 further changes the locations of complications 608-1, 608-2, and 608-3 (e.g., based on the sequence of locations). Complication 608-1 disappears from the second location (bottom left) and appears in the third location (top left), complication 608-2 disappears from the third location (top left) and appears in the first location (bottom right), and complication 608-3 disappears from the first location (bottom right) and appears in the second location (bottom left). Complication 608-1 decreases in size and includes less information. In the third location, complication 608-1 is displayed with the current temperature 610 and the temperature range ring with indicator 612, but the temperature range 614 indicating the maximum and minimum temperatures and the weather condition indicator 618 is not displayed (e.g., at least some of the information displayed in the second location is not included). Complication 608-2 increases in size and continues to include a representation of the Earth currently illuminated by the sun. Complication 608-3 increases in size and includes additional information, low heart rate 622 and high heart rate 624, in addition to the current heart rate 620 provided in the first location. The addition of information as complication 608-3 moves to progressively larger locations (e.g., from third to first to second) illustrates an embodiment in which a complication may provide progressively more information as it moves to progressively larger locations. Similarly, complication 608-1 includes more information as it moves from the first location to the larger second location, but less information as it moves from the second location (e.g., the largest location) to the third location (e.g., the smallest location).

[0193] 6C, device 600 receives (e.g., detects) user input 690-3, which includes rotation of rotatable input mechanism 604 in the same direction as the rotation of user input 690-1 and user input 690-2. In some embodiments, user input 690-3 is a continuation of user input 690-2. In some embodiments, user input 690-2 is separate from user input 690-2.

[0194] As shown in Figure 6D, in response to receiving user input 690-3, device 600 further changes the locations of complications 608-1, 608-2, and 608-3 (e.g., based on the sequence of locations). Complication 608-1 disappears from the third (last) location (top left) and appears in the first location (bottom right), complication 608-2 disappears from the first location (bottom right) and appears in the second location (bottom left), and complication 608-3 disappears from the second location (bottom left) and appears in the third (last) location (top left). In response to user input 690-1 through 690-3, complications 608 continuously cycle through the sequence of locations, returning to the originally occupied location of Figure 6A.

[0195] As shown in FIGS. 6A-6D, complication 608 progresses forward in the sequence of locations until it reaches the last location, at which point complication 608 moves to the first location in the sequence. Due to the relative positions of the locations on display 602, complication 608 moves in a clockwise direction. In some embodiments, the direction (either in the logical sequence or physical direction of the locations on display 602) depends on the user input (e.g., the direction of the user input). For example, complication 608 cycles in the direction shown in FIGS. 6A-6D according to the direction of user input 690-1-690-3 (e.g., an upward or clockwise rotation of rotatable input mechanism 604).

[0196] 6E-6H illustrate movement of complication 608 in response to user inputs 692-1-692-3 having a direction opposite to the direction of user inputs 690-1-690-3 (e.g., downward or counterclockwise rotation of rotatable input mechanism 604). As shown in FIGS. 6E-6H, complication 608 moves backward in the sequence of locations (e.g., counterclockwise on display 602) in response to user inputs 692-1-692-3. For example, complication 608-1 moves from a first location to a last location to a second location and back to the first location. In some embodiments, complication 608 moves forward in the sequence of locations in response to a swipe gesture on display 602 in a first direction (e.g., up or right) and moves backward in the sequence of locations in response to a swipe gesture in the opposite direction (e.g., down or left).

[0197] 6A-6H, clock face 606 remains in the top right location of clock user interface 601 during user input 690 and 692, even as complication 608 moves (e.g., the top right location is not included in the sequence of locations to which graphical objects move in response to user input). In some embodiments, the top right location on clock user interface 601 is included in the sequence of locations (e.g., as the fourth (last) location), and clock face 606 is moved to a different location in the sequence along with complication 608.

[0198] 6I-6M show an embodiment with a sequence of locations where the bottom right location is the first location, the bottom left location is the second location, the top left location is the third location, and the top right location is the fourth (final) location. As shown in Figures 6I-6M, graphical objects 606, 608-1, 608-2, and 608-3 move forward in the sequence of locations (e.g., clockwise on display 602) in response to user inputs 693-1-693-4.

[0199] As shown in FIGS. 6I-6M, the fourth location has a size larger than that of the second location (e.g., the location with the largest size), thereby allowing for the display of additional information than the first, second, and third locations. When complication 608-3 is located in the fourth location (FIG. 6K), it includes additional information 628 indicating when the currently displayed heart rate 620 was last updated, compared to the information included when complication 608-3 is located in the second-largest location (FIG. 6M). Complication 608-1 also includes additional location information 630 in the fourth location (FIG. 6M) compared to the second location (FIG. 6K). The watch face 606 includes progressively more detail as the location size increases beyond a certain size. At the three minimum locations (first, second, and third locations), the clock face 606 includes the same amount of detail (e.g., tick marks 636 corresponding to the hour markers), and at the maximum location (fourth location), the clock face 606 includes numbers 626 corresponding to the hour markers.

[0200] As shown in Figures 6A-6H, when different graphical objects are displayed at corresponding locations in response to user input, the locations are fixed in the sense that the location does not change or move (e.g., graphical objects displayed at a particular location always occupy the same area of ​​display 602).

[0201] In some embodiments, exhibiting a complication in one location and displaying it in another location includes animation while the complication is not displayed, animation while the complication is displayed, or animation while the complication is not displayed and is displayed (e.g., the complication gradually disappears or appears, or the complication translates from one location to another).

[0202] 6J, in some embodiments, clock user interface 601 displays an animation of complications 608-1, 608-2, and 608-3 and clock face 606 moving in a clockwise direction as each element translates from one location to the next in a sequence of locations on the display. For example, when complication 608 transitions from the configuration shown in FIG. 6I to the configuration shown in FIG. 6K, clock user interface 601 displays complications 608-1, 608-2, and 608-3 and clock face 606 in intermediate locations (e.g., complication 608-1 is between the first and second positions, complication 608-2 is between the second and third positions, complication 608-3 is between the third position and the fourth (final) position, and clock face 606 is between the fourth (final) position and the first position). In some embodiments, the direction of animation movement of each graphical element corresponds to the direction of user input 693-2 (e.g., complication 608 translates in a clockwise direction in response to clockwise input 693-2 on a rotatable input mechanism).

[0203] 7A-7B are flow diagrams illustrating a method for providing a context-specific user interface using an electronic device, according to some embodiments. Method 700 is performed on a device having a display (e.g., 100, 300, 500, 600). Some operations of method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0204] In block 702, the device displays a clock user interface (e.g., 601) on a display (e.g., 602). The clock user interface includes a first graphical object (e.g., 608-1 in FIG. 6A ) at a first location in a sequence of locations on the display and a second graphical object at a last location in the sequence of locations on the display (e.g., 608-3 in FIG. 6A ). In some embodiments, at least one of the first and second graphical objects displays data from an application (e.g., the first and / or second graphical object is a complication associated with a clock face of the clock user interface). In some embodiments, the first graphical object includes a display of time (606). In some embodiments, the display of time is a representation of an analog clock including hour and minute hands. In some embodiments, the display of time is a representation of a digital clock including a numerical display of hours and a numerical display of minutes. In some embodiments, the display of time is offset from the center of the display.

[0205] Displaying multiple graphical elements on a display as members of a location sequence can be reconfigured in a continuous manner, providing the user with feedback regarding the current location of each graphical element relative to other graphical elements and providing the user with visual feedback indicating how subsequent input will change the display. Providing improved visual feedback to the user improves usability of the device, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and additionally reduces power usage and improves the device's battery life by allowing the user to use the device more quickly and efficiently.

[0206] In block 704, the device detects user input. In some embodiments, the device includes a rotatable input mechanism (e.g., 604), and the user input is rotation of the rotatable input mechanism (e.g., 690). In some embodiments, the rotatable input mechanism is a physical mechanism that is attached to a fixed location on the electronic device (e.g., a side of the frame 603) and rotates relative to the electronic device. In some embodiments, movement of a complication between locations on the display is based on the direction of rotation (e.g., rotation in one direction results in forward movement in the sequence of locations, and rotation in the opposite direction results in backward movement in the sequence of locations).

[0207] In some embodiments, the user input is a swipe gesture (eg, in a first direction) detected on the display.

[0208] In response to detecting a user input, the device performs the actions of blocks 706, 708, 710, and 712. In block 706, the device stops displaying the first graphical object in a first location in a sequence of defined locations on the display (e.g., 608-1 in FIG. 6A at the bottom right of the display). In block 708, the device stops displaying the second graphical object in a last location in a sequence of defined locations on the display (e.g., 608-3 in FIG. 6A at the top left of the display). In block 710, the device displays the second graphical object in a first location in a sequence of locations on the display (e.g., 608-3 in FIG. 6B is displayed at the bottom right of the display). In block 712, the device displays the first graphical object in a second location in a sequence of locations on the display (e.g., 608-1 in FIG. 6B is displayed at the bottom left of the display). In some embodiments, there are only two locations, and the second location is the last location. In some embodiments, there are three or more locations and the second location is the next location in the sequence (e.g., FIGS. 6A-6M). In some embodiments, the first graphical object includes first information and the first graphical object while displayed in the first location, but includes second information that is different from the first information (e.g., does not include the first information) while displayed in the second location (e.g., 608-1 in FIG. 6A and 608-1 in FIG. 6B).

[0209] Automatically updating visual characteristics, such as the type and amount of information displayed on multiple graphical elements, in response to input-induced changes in location on the interface provides users with more control over their devices by helping them quickly configure multiple display elements into various configurations without requiring individual interaction with each element (e.g., first selecting an element, then relocating it to another location on the display, individually adjusting the nature of the information displayed, and repeating the steps for other elements is reduced to fewer actions requiring user input), improving device usability by reducing the number of inputs required to perform equivalent actions, making the user-device interface more efficient (e.g., by assisting users in providing appropriate inputs and reducing user errors when operating / interacting with the device), and further reducing power usage and improving device battery life by allowing users to use the device more quickly and efficiently.

[0210] In some embodiments, the first graphical object has a first size while displayed at a first location and a second size while displayed at a second location, the first size being different from the second size (e.g., 608-1 in FIG. 6B and 608-1 in FIG. 6C).

[0211] Automatically updating visual characteristics, such as size, of multiple graphical elements in response to input-induced changes in location on the interface provides users with more control of a device by helping them quickly configure multiple display elements into various configurations without requiring individual interaction with each element (e.g., first selecting an element, then relocating it to another location on the display, then resizing the element, and repeating the steps for other elements is reduced to fewer actions requiring user input), improving device usability by reducing the number of inputs required to perform equivalent actions, making the user-device interface more efficient (e.g., by assisting users in providing appropriate inputs and reducing user errors when operating / interacting with the device), and further reducing power usage and improving device battery life by allowing users to use the device more quickly and efficiently.

[0212] In some embodiments, the clock user interface further includes a display of the time that is displayed in the same position before and after the first input (e.g., 606 in FIGS. 6A-6H). In some embodiments, the display of the time is a representation of an analog clock that includes hour and minute hands (e.g., 606). In some embodiments, the display of the time is a representation of a digital clock that includes a numerical representation of the hours and a numerical representation of the minutes.

[0213] Ceasing to display the first and second graphical elements in a first and last location, respectively, and then re-displaying the second graphical element in the first location and the first graphical element in the second location in response to an input provides the user with more control over the device by helping the user quickly configure multiple display elements into various configurations without requiring individual interaction with each element, improving usability of the device by reducing the number of inputs required to perform equivalent operations, making the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the device), and further reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

[0214] In some embodiments, ceasing to display the first graphical object at a first location in the sequence of defined locations on the display and displaying the first graphical object at a second location in the sequence of locations on the display includes displaying an animation of the first graphical object moving from the first location toward the second location, and ceasing to display the second graphical object at a last location in the sequence of defined locations on the display and displaying the second graphical object at a first location in the sequence of defined locations on the display includes displaying an animation of the second graphical object moving from the last location toward the first location (e.g., in response to an input (e.g., 693), the device (e.g., 600) displays the animations shown in Figures 6I-6K).

[0215] Displaying an animation of an object as it is reassigned to a different location on the user interface provides the user with visual feedback about how subsequent interactions with the device will change the configuration of the user interface, which allows the user to more efficiently select their next input. Providing the user with improved visual feedback improves usability of the device, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and further reduces power usage and improves the device's battery life by allowing the user to use the device more quickly and efficiently.

[0216] In some embodiments, the first location and the second location are fixed on the display relative to the physical frame of the device (e.g., the locations of the first location and the second location do not change in response to detection of the first input). In some embodiments, in response to the first input, the second graphical object disappears from its last location and is displayed in the first location without animating the movement of the second graphical object from its last location to the first location.

[0217] In some embodiments, at block 714, the device detects a second user input having a second direction opposite to the direction of the first input (e.g., 692). In response to detecting the second user input (e.g., 692-3), the device performs the operations of blocks 716, 718, 720, and 722 (e.g., 608-1 in FIGS. 6G-6H). At block 716, the device stops displaying the first graphical object (e.g., 608-1) at a second location in the sequence of defined locations on the display. At block 718, the device stops displaying the second graphical object (e.g., 608-2) at a first location in the sequence of defined locations on the display. At block 720, the device displays the second graphical object (e.g., 608-2 in FIG. 6H) at a last location in the sequence of locations on the display. In block 722, the device displays a first graphical object (eg, 608-1 in FIG. 6H) at a first location in a sequence of locations on the display.

[0218] Updating the arrangement of multiple graphical elements on the display to match the direction of user input provides the user with feedback on how subsequent interactions with the device will change the configuration of the user interface, allowing the user to more efficiently select their next input. Providing improved visual feedback to the user improves usability of the device, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and further reduces power usage and improves the device's battery life by allowing the user to use the device more quickly and efficiently.

[0219] As described below, method 700 provides an intuitive way to configure a context-specific user interface. This method reduces the cognitive burden on the user, thereby creating a more efficient human-machine interface. For battery-operated computing devices, allowing users to configure context-specific user interfaces more quickly and efficiently conserves power and extends the time between battery charges.

[0220] It should be noted that details of the processes described above with respect to method 700 (e.g., FIGS. 7A-7B) are also applicable in an analogous manner to methods described below (e.g., methods 900 and 1100). For example, method 1100 optionally includes one or more features of the various methods described above with reference to method 700. For example, the position of complication 1008 of FIG. 10A on watch user interface 1000 can be reconfigured (e.g., rotated in a clockwise direction) in response to user input at rotatable input device 604 in a manner similar to the various techniques described with reference to method 700. For brevity, these details will not be repeated below.

[0221] 8A-8J show exemplary user interfaces for displaying the background of a clock user interface, according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the method of FIG.

[0222] FIG. 8A illustrates such a device 600. In FIG. 8A, device 600 displays a clock user interface 801 on display 602 at a first time (10:15:35). As shown in FIG. 8A, clock user interface 801 includes an hour hand 806-1, a minute hand 806-2, and a second hand 806-3. As used herein, second hand 806-3 refers to a representation of a hand on a clock that is distinct from a second hand of two or more hands (e.g., a first hand, a second hand, a third hand, etc.) and indicates the seconds component of the time of day. In some embodiments, clock user interface includes only hour hand 806-1 and minute hand 806-2 (e.g., does not include second hand 806-3), or only hour hand 806-1 (e.g., does not include minute hand 806-2 and second hand 806-3).

[0223] Hour hand 806-1, minute hand 806-2, and second hand 806-3 are superimposed on a background 810, which includes a first portion 810-1 and a second portion 810-2 separated by a linear boundary 812. In some embodiments, background 810 includes a non-linear boundary. As indicated by the stippling on first portion 810-1 in FIG. 8A , first portion 810-1 has a different color or visual pattern than second portion 810-2. In FIG. 8A , background 810 occupies the entire background of display 602 (e.g., background 810 extends to the edges and (rounded) corners of display 602).

[0224] Background 810 includes one or more graphical characteristics based on the position of hour hand 806-1. As shown in FIG. 8A , linear boundary 812 is aligned with hour hand 806-1, which defines the orientation of background 810 relative to the physical features of device 600 (e.g., display 602, frame 603, rotatable input mechanism 604, and buttons 605). As oriented in FIG. 8A , first portion 810-1 is positioned generally above and to the right of second portion 810-2 and occupies approximately the upper right half of display 602. Hour hand 806-1 extends from the center point of display 602. As a result, linear boundary 812 extends from one edge of display 602 (e.g., the left edge as shown in FIG. 8A ) to the opposite edge (e.g., the right edge), such that first portion 810-1 and second portion 810-2 each occupy half of the area of ​​display 602.

[0225] 8B, device 600 displays clock user interface 801 at a second time (e.g., 12:00:58) (e.g., after the first time) with a second graphical characteristic (e.g., a reoriented position) of background 810 based on the updated position of hour hand 806-1. As shown in FIG. 8B, linear boundary 812 remains aligned along hour hand 806-1 and is vertically oriented such that first portion 810-1 occupies the right half of display 602 and second portion 810-2 occupies the left half of display 602.

[0226] 8C and 8D show that as the hour and hour hand 806-1 advances to 3:00 (FIG. 8C) and 4:30 (FIG. 8D), the linear boundary 812 remains aligned along the hour hand 806-1, and the background 810 rotates with the hour hand 806-1. As shown in FIGS. 8A-8D, the background 810 rotates about the same point as the hour hand 806-1 (e.g., a common origin).

[0227] As shown in FIGS. 8A-8D, the watch user interface 801 also includes graphical elements (e.g., numbers (1-12) indicating the time and a date object (808) (e.g., a calendar complication)) that are overlaid on the background and remain fixed (e.g., in the same location as the display 602) as the hour hand 806-1, minute hand 806-2, second hand 806-3, and background 810 change position on the display 602.

[0228] 8A-8D, the shapes of first portion 810-1 and second portion 810-2 change as background 810 rotates. For example, in Figures 8B and 8C, portions 810-1 and 810-2 are approximately rectangular (excluding rounded corners due to the shape of display 602), while in Figure 8D, portions 810-1 and 810-2 are approximately triangular (excluding rounded corners due to the shape of display 602).

[0229] As shown in FIGS. 8A-8D , background 810 remains fixed relative to hour hand 806-1 (e.g., first portion 810-1 remains on the clockwise side of hour hand 806-1). In some embodiments, first portion 810-1 is on the counterclockwise side of hour hand 806-1. In the embodiment shown in FIGS. 8A-8D , the graphical characteristics of background 810 are repeated every 12 hours (e.g., background 810 rotates once every 12 hours). At each time of day (e.g., 6:00), first portion 810-1 occupies the area of ​​display 602 occupied by second portion 810-2 at a different time of day (e.g., 12:00), and vice versa (e.g., first portion 810-1 and second portion 810-2 switch places every 6 hours).

[0230] 8E-8H, an embodiment is shown in which the graphical characteristics of background 810 are based on the position of minute hand 806-2. As shown in FIGS. 8E-8H, linear boundary 812 remains aligned with minute hand 806-2 as it rotates on display 602. Background 810 rotates with minute hand 806-2 about a center point on display 602, similar to how background 810 rotates with hour hand 806-1, as shown in FIGS. 8A-8D. First portion 810-1 and second portion 810-2 each occupy corresponding halves of display 602 and change shape as the position of minute hand 806-2 changes over time. In the embodiment shown in FIGS. 8E-8H, the graphical characteristics of background 810 are repeated every hour (e.g., background 810 rotates once every hour). First portion 810-1 and second portion 810-2 switch locations every 30 minutes. 8A-8D, first portion 810-1 remains on the counterclockwise side of minute hand 806-2. In some embodiments, first portion 810-1 is on the clockwise side of minute hand 806-2. In some embodiments, the graphic characteristics are based on the position of second hand 806-3 in a manner similar to that described above for hour hand 806-1 and minute hand 806-2.

[0231] 8I and 8J, embodiments with different backgrounds will now be described. As shown in FIGS. 8I and 8J, clock user interface 801 includes background 818 that includes a spotlight effect 814. Graphical characteristics of background 818 (e.g., the position of spotlight effect 814) are based on the position of hour 806-1. As shown in FIGS. 8I and 8J, spotlight effect 814 is displayed behind hour marker 816 that corresponds to the position of hour hand 806-1. In some embodiments, spotlight 814 always remains aligned along hour hand 806-1 (e.g., spotlight effect 814 is displayed between hour markers 11 and 12 at 11:30). In some embodiments, spotlight 814 stays behind the hour marker that corresponds to the current time (e.g., spotlight effect 814 stays behind hour marker 11 from 11:00 to 11:59).

[0232] In some embodiments, the hand on which the graphical characteristics of background 810 are based is determined (e.g., selected) based on user input. In some embodiments, in response to receiving a sequence of one or more user inputs, device 602 operates in a mode in which the graphical characteristics of background 810 are based on hour hand 806-1, minute hand 806-2, or second hand 806-3 (e.g., in response, at least in part, to selecting one or more affordances for accessing and selecting a menu option corresponding to one of the hands 806). In some embodiments, selecting the hand on which the graphical characteristics of background 810 are based includes entering a clock face edit mode or a clock face settings edit mode (e.g., in response to determining that a received contact has a characteristic intensity greater than or equal to a threshold intensity).

[0233] In some embodiments, in response to receiving a sequence of one or more user inputs, device 602 switches from a mode in which the graphical characteristics of background 810 are based on one hand (e.g., hour hand 806-1) to a mode in which the graphical characteristics of background 810 are based on another hand (e.g., minute hand 806-2). In this manner, the user can select the rate at which the graphical characteristics (e.g., orientation) of the background change (e.g., rotate).

[0234] In some embodiments, the background and / or graphical characteristics of the background are determined (e.g., selected) based on user input. In some embodiments, in response to receiving a sequence of one or more user inputs, device 602 sets the background and / or graphical characteristics to the selected background and / or graphical characteristics (e.g., in response to selecting one or more affordances for accessing and selecting menu options corresponding to the background and / or graphical characteristics). In some embodiments, in response to receiving a sequence of one or more user inputs, device 602 switches from one background and / or graphical characteristics (e.g., background 810) to another background and / or graphical characteristics (e.g., background 818).

[0235] 9 is a flow diagram illustrating a method for providing a context-specific user interface using an electronic device, according to some embodiments. Method 900 is performed on a device having a display (e.g., 100, 300, 500, 600). Some operations of method 900 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0236] As described below, method 900 provides an intuitive way to configure a context-specific user interface. This method reduces the cognitive burden on the user, thereby creating a more efficient human-machine interface. For battery-operated computing devices, allowing users to configure context-specific user interfaces more quickly and efficiently conserves power and extends the time between battery charges.

[0237] In block 902, the device displays a clock user interface (e.g., 801) on a display (e.g., 602) at a first time. The clock user interface at the first time includes a first clock hand at a first position (e.g., FIG. 8A, 806-1) overlaid on a background (e.g., 810), the background having a first graphical characteristic at the first time that is determined based on the first position of the first clock hand (e.g., the appearance of 810 is based on position 806-1).

[0238] In some embodiments, the first clock hand is one of an hour hand, a minute hand, or a second hand (eg, 806-1, 806-2, and 806-3).

[0239] In some embodiments, the background extends to the edges (eg, 810) of the display.

[0240] In some embodiments, the background includes a first portion occupying a first half of the display and a second portion occupying a second half of the display (eg, 810-1 and 810-2).

[0241] In some embodiments, the boundary between the first and second portions is a straight line (eg, 812).

[0242] In some embodiments, the boundary is along the first clock hand (eg, 806-1 in FIGS. 8A-8D).

[0243] In some embodiments, the first portion includes a first color or visual pattern and the second portion includes a second color or visual pattern that is different from the first color or visual pattern (e.g., 810-1 and 810-2).

[0244] In block 904, the device displays a clock user interface (e.g., 801) on the display (e.g., 602) at a second time after the first time (e.g., FIG. 8B, the second time is approximately 12:00:57). The clock user interface at the second time includes a first clock hand (e.g., FIG. 8B, 806-1) in a second position superimposed on a background (e.g., 810), the background having second graphical characteristics at the second time determined based on the second position of the first clock hand (e.g., 810 in FIG. 8A and 810 in FIG. 8B).

[0245] Dynamically modifying characteristics of the background of a clock user interface based on the position of the hands of the clock provides the user with an easily readable visual indication of the current time as measured by the clock. Providing improved visual feedback to the user improves device usability and makes the user device interface more efficient (e.g., by helping the user quickly determine displayed information, the user does not have to spend as much time interacting with the device), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more efficiently.

[0246] In some embodiments, displaying the clock user interface on the display at the first time further includes displaying a graphic element at a fifth position, and displaying the clock user interface on the display at the second time further includes displaying the graphic element at the fifth position (e.g., 808).

[0247] In some embodiments, the difference between the first graphical characteristic at a first time and the second graphical characteristic at a second time corresponds to a rotation of the background relative to the physical frame of the device (e.g., 810 in FIG. 8B and 810 in FIG. 8A). In some embodiments, the physical frame (e.g., 603) includes a rotatable input mechanism (e.g., 604) and / or a button (e.g., 605).

[0248] In some embodiments, the hands of the first clock and the background rotate about a common origin (eg, 806-1 and 810 in Figures 8A-8H).

[0249] In some embodiments, the shape of the first portion at a first time is different from the shape of the first portion at a second time (e.g., 810-1 in FIG. 8A and 810-1 in FIG. 8B) (e.g., the shape is "triangle" when the boundary extends from corner to corner, and "rectangle" when the boundary is vertical or horizontal (the corners of the display are rounded, so the shape is not a true triangle or rectangle)).

[0250] Dynamically modifying the shape of the portion of the background of the clock user interface based on the position of the hands of the clock provides the user with an easily discernible visual indication (e.g., a bold, dynamically changing shape) of the current time as measured by the clock. Providing improved visual feedback to the user improves device usability and makes the user device interface more efficient (e.g., by helping the user quickly discern displayed information, the user does not have to spend as much time interacting with the device), and additionally, by allowing the user to use the device more efficiently, reduces power usage and improves the device's battery life.

[0251] In some embodiments, the first graphical feature at the first time includes a visual representation of the hour of the first time (e.g., FIG. 8J, 814 shows 10 o'clock at the time 10:15:35), and the second graphical feature at the second time includes a visual representation of the hour of the second time (e.g., FIG. 8I, 814 shows 12 o'clock at the time 12:00:57). In some embodiments, the graphical feature includes a spotlight effect following the hour hand (e.g., the end of the hour hand).

[0252] Dynamically modifying the background of the clock user interface to include a spotlight on the current time indicator based on the position of the clock hands provides the user with an easily discernible visual indication that quickly draws the user's attention to relevant information (e.g., the current time as measured by the clock). Providing improved visual feedback to the user improves device usability and makes the user device interface more efficient (e.g., by helping the user quickly discern displayed information, the user does not have to spend as much time interacting with the device), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more efficiently.

[0253] In some embodiments, the clock user interface is configured to display one or more characteristics of the background according to the position of a first clock hand at a first time and a second time. Optionally, at block 906, the device receives a sequence of one or more user inputs corresponding to a request to display one or more characteristics of the background according to the position of a second clock hand that is different from the first clock hand (e.g., 806-2 in FIGS. 8E-8H ) (e.g., a change in the configuration of the background characteristics from the first hand to the second hand). In some embodiments, the sequence of one or more user inputs includes a contact with the display (e.g., 602) having a characteristic intensity above an intensity threshold, which causes the electronic device (e.g., 600) to enter a clock face editing mode or a clock face settings editing mode.

[0254] By allowing a user to change the hands that define how the characteristics of the background of a clock user interface change over time, the user is provided with feedback indicating how particular units of time are measured by the clock via an easily discernible visual display. Providing improved visual feedback to the user improves device usability and makes the user device interface more efficient (e.g., by helping the user quickly discern displayed information, the user does not have to spend as much time interacting with the device), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more efficiently.

[0255] In some embodiments, the hand of the second clock (e.g., 806-2) has a speed of movement that is different from the speed of movement of the hand of the first clock (e.g., the hand of the first clock is the hour hand and the hand of the second clock is the minute hand, and the minute hand has a faster speed of movement than the speed of movement of the hour hand).

[0256] In some embodiments, the second clock hand is one of an hour hand (e.g., 806-1), a minute hand (e.g., 806-2), or a second hand (e.g., 806-3).

[0257] After optionally receiving a sequence of one or more user inputs in block 906, in block 908, the device displays a clock user interface (e.g., 810) on the display at a third time (e.g., FIG. 8E). The clock user interface (801) at the third time includes a second clock hand (806-2 in FIG. 8E) at a third position superimposed on a background, the background having a third graphical characteristic at the third time that is determined based on the third position of the second clock hand (e.g., 810 in FIG. 8E).

[0258] Optionally, at block 910, the device displays a clock user interface (e.g., 801) on the display (e.g., 801) at a fourth time (e.g., FIG. 8F) after the third time (e.g., FIG. 8E). The clock user interface at the fourth time includes a second clock hand (e.g., 806-2 in FIG. 8F) at a fourth position superimposed on a background, and the background has a fourth graphical characteristic at the fourth time that is determined based on a fourth position of the second clock hand (e.g., 810 in FIG. 8F).

[0259] It should be noted that the details of the process described above with respect to method 900 (FIG. 9) are also applicable in an analogous manner to the methods described above (e.g., 700) and below (e.g., 1100). For example, method 700 optionally includes one or more features of the various methods described above with reference to method 900. For example, the background of clock face 606 in FIG. 6A can be divided into two parts and can dynamically change based on the position of hour hand 616-1 in a manner similar to the technique described with reference to method 900. For brevity, these details will not be repeated below.

[0260] 10A-10T show exemplary watch user interfaces according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the methods in FIGS. 11A-11D.

[0261] FIG. 10A illustrates such a device 600. As shown in FIG. 10A, the device 600 displays a clock user interface 1000 on the display 602. The clock user interface 1000 includes a time display with an hour hand 1006-1, a minute hand 1006-2, and a second hand 1006-3. The clock user interface 1000 also includes a weather complication 1008-1, a heart rate complication 1008-2, and a date complication 1008-3. The weather complication 1008-1 displays data from a weather application including a single metric, the current temperature 1010. The heart rate complication 1008-2 is associated with the heart rate application, as indicated by the heart icon included in the complication. The heart rate complication 1008-2 does not include any metrics related to data from the heart rate application. Date complication 1008-3 provides date information including day of week 1012 and date 1014.

[0262] 10B shows an expanded watch user interface 1002 displayed on display 602. Expanded watch user interface 1002 includes an expanded weather complication 1008-1′, an expanded heart rate complication 1008-2′, and a date complication 1008-3. As shown in FIG. 10B, weather complication 1008-1′, heart rate complication 1008-2′, and date complication 1008-3 are the same size as weather complication 1008-1, heart rate complication 1008-2, and date complication 1008-3 on watch user interface 1000. Weather complication 1008-1′ and heart rate complication 1008-2′ are enhanced in the sense that they include additional information or metrics related to data from the corresponding applications than weather complication 1008-1 and heart rate complication 1008-2 displayed on watch user interface 1000. Weather complication 1008-1′ and heart rate complication 1008-2′ also have higher resolution (e.g., smaller text size, smaller feature size (e.g., temperature symbols)), and / or a larger color or grayscale range than weather complication 1008-1 and heart rate complication 1008-2 displayed on watch user interface 1000.

[0263] In some embodiments, the enhanced weather complication 1008-1′ and the enhanced heart rate complication 1008-2′ are displayed according to a watch user interface 1002 that is the enhanced watch user interface 1002 (e.g., instead of the “normal” watch user interface 1000). For example, in response to a selection (e.g., by a user or based on a default setting) to display complications associated with a weather application on the display 602, the device 600 displays the weather complication 1008-1 according to the watch user interface 1000 that is the watch user interface, while the device 600 displays the enhanced weather complication 1008-1′ according to the watch user interface that is the enhanced watch user interface 1002. Similarly, a request to display a heart rate complication results in the display of the enhanced heart rate complication 1008-2′ on the enhanced watch user interface 1002 and the display of the heart rate complication 1008-2 on the watch user interface 1000.

[0264] 10B, the expanded weather complication 1008-1′, the expanded heart rate complication 1008-2′, and the expanded date complication 1008-3 each include two or more metrics related to data from the corresponding application. The expanded weather complication 1008-1′ includes the current temperature 1010, a temperature range 1026, and a relative current temperature indicator 1028 that shows the current temperature 1010's relative position within the temperature range 1026. The expanded heart rate complication 1008-2′ includes the current (or most recently measured) heart rate per minute 1020, the low heart rate per minute of the day 1022, and the high heart rate per minute of the day 1024. The date complication 1008-3 includes the day of the week 1012 and the date 1014.

[0265] 10C , device 600 receives (e.g., detects) user input 1081 (e.g., a tap) corresponding to a request to edit enhanced clock user interface 1002. As shown in FIG. 10D , in response to user input 1081, device 600 enters an edit mode (e.g., a clock face edit mode or a complication edit mode) and visually highlights date complication 1008-3 for editing (e.g., by displaying a box 1036 around date complication 1008-3 and a label 1038 identifying the associated application). In some embodiments, device 600 visually highlights the complication selected for editing (e.g., date complication 1008-3) by modifying one or more visual characteristics (e.g., brightness, opacity, color, contrast, hue, saturation, etc.) of clock user interface 1002 or a portion thereof. In some embodiments, while in edit mode, a complication selected for editing is displayed in a first visual characteristic (e.g., a color or colors other than grayscale), and in some embodiments, one or more other complications (e.g., all other complications) are displayed in a second visual characteristic (e.g., grayscale or a single color that is different from the colors in which the complications would be displayed while the device is not in edit mode), even though some or all of the other complications would be displayed in one or more colors within the clock face when the clock face is not in edit mode. For example, complication 1008-3 is displayed in color, and complications 1008-2 and 1008-1 are displayed in grayscale. In some embodiments, while in edit mode, instead of or in addition to changing the visual characteristic of one or more selected complications, the visual characteristic of one or more unselected complications is changed (e.g., the brightness or opacity of one or more unselected complications is reduced to distinguish between selected and unselected complications).In some embodiments, the visual distinction of the selected complication is in place of or in addition to an alternative selection indicator, such as a selection ring around at least a portion of the selected complication. While in edit mode, device 600 also displays a complication menu bar 1032 having a complication position indicator 1034 that indicates the position of the currently displayed complication in a menu of complications available for selection. In some embodiments, user input 1081 includes a contact having a characteristic intensity, and device 600 enters edit mode pursuant to a determination that the characteristic intensity exceeds a predetermined threshold intensity.

[0266] As shown in FIG. 10E, device 600 receives (e.g., detects) user input 1083, including rotation of rotatable input mechanism 604. In some embodiments, user input 1083 is received on a device other than device 600 through a counterpart application that communicates with device 600. As shown in FIG. 10F, in response to receiving (e.g., detecting) user input 1083, device 600 displays a representation of wind complication 1008-4 for addition to extended clock user interface 1002 in place of date complication 1008-3. Device 600 updates complication position indicator 1034 to indicate that wind complication 1008-4 is located near the bottom of the complications menu (e.g., because complications are alphabetical and "w" is near the end of the alphabet). Wind complication 1008-4 includes metrics for wind speed 1040 (22 mph) and wind direction 1042 (northeast). In some embodiments, wind complication 1008-4 is not available for selection on other watch user interfaces (e.g., watch user interface 1000).

[0267] 10G, device 600 receives (e.g., detects) user input 1085 (e.g., a tap) corresponding to selection of expanded heart rate complication 1008-2′. As shown in FIG. 10H, in response to receiving (e.g., detecting) user input 1085, device 600 visually highlights expanded heart rate complication 1008-2′ for editing. In some embodiments, in response to receiving user input 1085, device 600 transitions from visually highlighting a first editing complication (e.g., wind complication 1008-4) to visually highlighting a second editing complication (e.g., heart rate complication 1008-2) by changing one or more visual characteristics (e.g., brightness, color, contrast, hue, saturation, etc.) of watch user interface 1002 or portions thereof. For example, in response to receiving user input 1085, device 600 transitions from displaying complication 1008-4 in color and complication 1008-2 and 1008-1 in grayscale to displaying complication 1008-2 in color and complication 1008-4 and complication 1008-1 in grayscale. In some embodiments, while in edit mode, the visual characteristics of one or more unselected complications are changed (e.g., the brightness or opacity of one or more unselected complications is reduced to distinguish between unselected and selected complications). In some embodiments, the visual distinction of the second complication is instead of or in addition to an alternative selection indicator, such as a selection ring around at least a portion of the second complication. As shown in FIG. 10I , device 600 receives (e.g., detects) user input 1087 including rotation of rotatable input mechanism 604. As shown in FIG. 10J, in response to receiving (e.g., detecting) user input 1087, device 600 displays a representation of humidity complication 1008-5 for adding to enhanced clock user interface 1002 in place of enhanced heart rate complication 1008-2′.Humidity complication 1008-5 includes metrics for current humidity 1054, humidity range 1050, and relative current humidity indicator 1052. In some embodiments, humidity complication 1008-5 is not available in other watch user interfaces (e.g., watch user interface 1000).

[0268] The user can similarly request to add a new complication in place of the extended weather complication 1008-1' by selecting the extended weather complication 1008-1' in edit mode (e.g., by tapping) and moving the rotatable input mechanism 604 to select the new complication.

[0269] As shown in FIG. 10K, device 600 receives (e.g., detects) user input 1089. As shown in FIG. 10L, in response to receiving (e.g., detecting) user input 1089, device 600 exits edit mode and displays expanded watch user interface 1002 with the selected complications, wind complication 1008-4 and humidity complication 1008-5, and the previously displayed expanded weather complication 1008-1′. In some embodiments, expanded weather complication 1008-1′, wind complication 1008-4, and humidity complication 1008-5 all display data from the same weather application, thereby providing three complications related to the same application, and each complication includes at least two metrics not provided by either of the other two complications. FIG. 10L also shows an embodiment of a watch user interface with three gauge complications, each providing a parameter value and either a high and / or low value or a direction (e.g., wind direction).

[0270] In some embodiments, the date complication 1008-3 is replaced by a humidity complication 1008-5 in FIGS. 10D and 10E to result in an expanded clock user interface with three complications, each with three metrics (e.g., humidity complication 1008-5 (current humidity, low humidity, and high humidity), heart rate complication 1008-2′ (current heart rate, low heart rate, and high heart rate), and expanded weather complication 1008-1′ (current temperature, minimum temperature, and maximum temperature)).

[0271] In some embodiments, instead of the date complication 1008-3 and the expanded heart rate complication 1008-2', the user can replace a single complication (e.g., by exiting edit mode after user input 1083 in FIG. 10E), in which case the device 600 maintains the display of the other complications (e.g., the expanded heart rate complication 1008-2' and the expanded weather complication 1008-1). Similarly, the expanded heart rate complication 1008-2' can be replaced while maintaining the display of (e.g., without replacing) the date complication 1008-3 and the expanded weather complication 1008-1, and the expanded weather complication 1008-1 can be replaced while maintaining the display of (e.g., without replacing) the expanded heart rate complication 1008-2' and the data complication 1008-3.

[0272] In some embodiments, while replacing the selected complication(s), elements of the enhanced watch user interface 1002, such as the hands 1006 and non-selected complications, are not changed (e.g., remain unchanged).

[0273] 10M, clock user interface 1091 includes complications 1060-1, 1060-2, and 1060-3, each of which includes a metric related to data from a world clock application for a corresponding location (e.g., Moscow, Beijing, and London), a time associated with the location (e.g., an analog clock face with hour and minute hands), and an indication of day, night, sunset, or sunrise (e.g., complication 1060-1 indicates that it is night in Moscow, while complication 1060-2 indicates that it is day in Beijing). In some embodiments, one or more of complications 1060-1, 1060-2, or 1060-3 includes an offset relative to local time. As shown in FIG. 10M, the position of a location indicator (e.g., Beijing 1056) within a complication is based on the position of hand 1058. In some embodiments, the location indicator is positioned so that it does not overlap or interfere with the hands of the clock. For example, location indicators LON and BEI are positioned over the center of complications 1060-3 and 1060-2, respectively, so as not to interfere with the corresponding hands of the clock. In complication 1060-1, location indicator MOS is positioned under the center of the complication because if it were positioned in the over-center position, as LON and BEI would, it would overlap with the hour hand. In some embodiments, the location indicators' positions change over time to avoid interfering with the hands of the clock as they move.

[0274] 10N shows an embodiment of a watch user interface with three complications related to a calendar application. Complication 1070-1 includes an affordance that can be selected to begin the process for creating a new event in the calendar application. Complication 1070-2 includes metrics related to data from the calendar application, including the event (6 PM), subject or event name (dinner), and location (San Francisco). Complication 1070-3 is a date complication that includes the day of the week and date.

[0275] FIG. 10N also illustrates an embodiment of a complication having visual features at or around a ring-shaped region ("number ring") on the watch user interface 1093. The watch user interface 1093 has a ring-shaped region on the watch face that includes numbers (1-12) indicating the time, and the ring-shaped region has a curved outer edge. In some embodiments, the ring-shaped region includes tick marks indicating the hours and / or minutes, or numeric minute markers. Depending on the application corresponding to a particular application (e.g., calendar, weather, exercise, heart rate, respiration, stocks), the device 600 displays visual features at or around the ring-shaped region. For example, depending on a complication associated with a calendar application, the device 600 displays a complication having an event name 1064 and an event location 1066 around the ring-shaped region of the watch user interface 1093 (e.g., the event name 1064 and event location 1066 follow the outer edge of the watch face). Alternatively, depending on the complication, the device 600 may cease displaying the visual characteristics of the ring-shaped region or its surroundings, according to a complication associated with another application (e.g., battery, digital time, date, or stopwatch).

[0276] 10O shows an embodiment of a watch user interface with three complications involving data from a stocks application. Stock complications 1078-1, 1078-2, and 1078-3 include metrics related to data from the stocks application, including stock symbol 1076 (e.g., stock symbol), price 1074, and direction of movement 1075.

[0277] 10P shows an embodiment of a corner complication displayed in the lower right corner of the watch user interface 1097, between the edge of the number ring and the bottom and right edges of the display 602. The corner complication is a temperature complication that includes a status bar 1082 (representing a temperature range), a status indicator 1084 (representing the relative position of the current temperature within the temperature range), and a current state 1086 (representing the current temperature). The status bar 1082 follows the outer edge of the number ring, and the current state 1086 is located between the status bar 1082 and the lower right corner of the display 602.

[0278] 10Q shows a goal complication 1088-3 that displays a metric related to data from a health application. The goal complication 1088-3 includes a current value 1098 of the metric (e.g., floors climbed) and a progress indicator 1090 that indicates progress toward the goal or objective. The progress indicator 1090 includes a ring that surrounds slightly more than half of the outer edge of the complication 1088-3, indicating that the current value 67 is progressing slightly more than 50 percent toward the goal or objective. Other example goal complications include a battery complication that includes total battery capacity and current charge state, and a health complication that includes current steps, rest time, or calories burned or consumed values ​​and progress toward the steps, rest time, or calories burned or consumed goal or objective.

[0279] 10Q also shows an air quality index (AQI) complication 1088-1 that includes a current AQI value 1094 and a relative condition indicator 1096 that represents the location of the current AQI value 1094 relative to a range (good to dangerous). In some embodiments, the AQI complication 1088-1 can be represented as a goal complication, where a low AQI value is the goal or objective.

[0280] 10R-10T show a clock user interface including a digital time display 1006-4 (e.g., 10:09), a compact date indicator 1009 (e.g., Wednesday the 29th), and three or more complications displaying metrics related to data from a single application.

[0281] 10R, watch user interface 1003-1 includes five complications involving data from a weather application. As described above, air quality index (AQI) complication 1004-1 includes the current air quality value and a relative condition indicator, and wind complication 1004-2 includes wind speed and direction. UV complication 1004-3 includes the current UV index value 1007-1, a relative condition indicator 1007-2 representing the position of the current UV index value 1007-1 relative to a range (e.g., fair to dangerous), and a visual indication of UV conditions 1007-3 (e.g., a sun image showing a current UV index value of medium to high).

[0282] As shown in FIG. 10R, weather chart complication 1004-4 includes a textual weather label 1005-1 displaying a corresponding location (e.g., Cupertino) and the temperature (e.g., 72) at the corresponding location, and a temperature chart 1005-2. The temperature chart 1005-2 includes a first axis (e.g., time) and a second axis (e.g., temperature), bar graph data 1005-3 representing the temperature at the corresponding location (e.g., Cupertino) over a fixed time period, and a current temperature indicator 1005-5 (e.g., a visually distinct bar within the bar graph data corresponding to the current time). The bar graph data 1005-3 includes regularly spaced vertical bars representing the actual or forecasted temperature at the corresponding time on the first axis (e.g., the time axis). In some embodiments, the scale of the first or second axis is adjusted to reflect a desired temperature value range or a desired time scale for displaying the temperatures (e.g., the first axis reflects a time period such as 1 hour, 12 hours, 1 day, etc.). Weather icon complication 1004-5 includes weather condition icons that visually represent current or forecasted weather conditions (e.g., an image showing partly cloudy weather).

[0283] Referring now to FIG. 10S, watch user interface 1003-2 includes complications 1016-1, 1016-2, 1016-3, and 1016-4. Complications 1016-1, 1016-2, and 1016-3 each include a corresponding location (e.g., New York, London, and Hong Kong), a time associated with the location (e.g., an analog clock face with hour and minute hands), and metrics related to data from a world clock application regarding an indication of day, night, sunset, or sunrise (e.g., complication 1016-1 indicates that it is daytime in New York, and complication 1016-2 indicates that it is nighttime in London). In some embodiments, one or more of complications 1016-1, 1016-2, or 1016-3 includes an offset relative to the local time. As described with reference to FIG. 10M above, the position of the location indicator (e.g., New York) in the corresponding complication is based on the position of the hands (e.g., the location indicator is positioned so as not to overlap or interfere with the hands of the clock, and changes over time to avoid interfering with the hands of the clock).

[0284] 10S, stock complication 1016-4 includes a stock label 1017-1 indicating the price of a corresponding stock (e.g., APPL), a stock price indicator 1017-2 displaying the current stock price and the direction of movement of the associated stock price (e.g., APPL is 178.14 and rising), and a stock chart 1017-3 including metrics related to data from the stock application. Stock chart 1017-3 includes a first axis (e.g., relative price), a second axis (e.g., time), a price line 1017 indicating the price of the corresponding stock (e.g., APPL) over time, and a current price indicator 1017-5 (e.g., a vertical bar intersecting price line 1017-4 at the time on the second axis corresponding to the current time). In some embodiments, the scale of the first or second axis is adjusted to reflect a desired time scale or value range for displaying the prices of the corresponding stocks (e.g., the first axis reflects a one-day, one-week, one-month, three-month, six-month, one-year, period-to-date period, and the second axis reflects percentage change, absolute change, or measures prices in various fiat currencies or cryptocurrencies).

[0285] 10T, watch user interface 1003-3 includes two complications involving data from an activity application. Activity chart complication 1018-1 includes a text activity label 1019-1 displaying calories burned (e.g., 350), minutes exercised (e.g., 11), and time stationary (e.g., 06), and activity chart 1019-2. The activity chart shows a time axis 1019-3 (e.g., hours), an activity minutes scale 1019-4, a calorie scale 1019-5, and chart data 1019-6 representing the accumulation of activity metrics over distinct time periods displayed on time axis 1019-3 (e.g., activity minutes and calories burned over a given period are represented as vertical bars of proportional height on the corresponding scales, and time stationary is represented by a circular indicator). Compact activity complication 1018-2 includes graphical elements that display progress toward multiple activity-related fitness goals (e.g., icons showing progress toward goals for calories burned, active time, and stationary time).

[0286] As shown in FIG. 10T, watch user interface 1003-3 also includes three complications associated with three separate applications other than the activity application. Breathe complication 1018-3 is associated with a breathing application (e.g., a meditation or mindfulness application), as indicated by the breathing icon included within the complication. Heart rate complication 1018-4 is associated with a heart rate application, as indicated by the heart icon included within the complication. Training complication 1018-5 is associated with a training application, as indicated by the training icon included within the complication. Complications 1018-3, 1018-4, and 1018-5 do not include metrics associated with data from their respective applications.

[0287] In some embodiments, device 600 allows a user to select from two or more clock user interfaces, each having three complications involving data from the same application (e.g., a "collection" of complications). For example, in some embodiments, device 600 provides a user with the ability to select from two or more of clock user interfaces 1091 (FIG. 10M), 1093 (FIG. 10N), 1095 (FIG. 10O), 1097 (FIG. 10P), 1099 (FIG. 10Q), 1003-1 (FIG. 10R), 1003-2 (FIG. 10S), and 1003-3 (FIG. 10T). In some embodiments, while displaying one of clock user interfaces 1091 ( FIG. 10M), 1093 ( FIG. 10N), 1095 ( FIG. 10O), 1097 ( FIG. 10P), 1099 ( FIG. 10Q), 1003-1 ( FIG. 10R), 1003-2 ( FIG. 10S), and 1003-3 ( FIG. 10T), device 600 detects a sequence of one or more inputs corresponding to a selection of another one of clock user interfaces 1091 ( FIG. 10M), 1093 ( FIG. 10N), 1095 ( FIG. 10O), 1097 ( FIG. 10P), 1099 ( FIG. 10Q), 1003-1 ( FIG. 10R), 1003-2 ( FIG. 10S), and 1003-3 ( FIG. 10T). In response to detecting the sequence of one or more inputs, device 600 displays the selected clock user interface.

[0288] 11A-11D are flow diagrams illustrating a method for providing a context-specific user interface using an electronic device, according to some embodiments. Method 1100 is performed on a device (e.g., 100, 300, 500, or 600) that includes a display. Some operations of method 1100 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0289] As described below, method 1100 provides an intuitive way to configure a context-specific user interface. This method reduces the cognitive burden on the user, thereby creating a more efficient human-machine interface. For battery-operated computing devices, allowing users to configure context-specific user interfaces more quickly and efficiently conserves power and extends the time between battery charges.

[0290] In block 1102, the device displays a clock user interface (e.g., 1000 in FIG. 10A ) on a display (e.g., 602). The clock user interface includes a first complication (e.g., 1008-1) that includes at least a first metric associated with data from a first application (e.g., 1010 in FIGS. 10A-10C ) and a second metric associated with data from the first application (e.g., 1026 in FIGS. 10A-10C ). In some embodiments, the complication refers to any clock face feature other than those used to indicate hours and minutes of a time (e.g., clock hands or hour / minute indicators). In some embodiments, the complication provides data obtained from an application. In some embodiments, the complication includes an affordance that, when selected, launches a corresponding application (e.g., 1008-2 in FIG. 8A ). In some embodiments, the complication is displayed in a fixed, predetermined location on the display.

[0291] In some embodiments, the first complication includes an analog clock face having one or more hands that indicate the time at a geographic location and text that indicates the geographic location (e.g., 1060), where the text that indicates the geographic location is positioned on the complication based on the position of the one or more hands (e.g., 1058). In some embodiments, the complication is positioned to avoid overlapping with one or more hands on the clock face (e.g., FIG. 10M).

[0292] Automatically moving textual descriptions on a clock face to avoid being obstructed by the hands as they progress around the dial throughout the day provides the user with more reliable visual feedback regarding the time displayed by the clock and the location that time represents. Providing improved visual feedback to the user improves device usability and makes the user-device interface more efficient (e.g., by helping the user quickly and accurately determine displayed information, the user does not have to spend as much time interacting with the device), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more efficiently.

[0293] Further, at block 1102, the device displays a second complication (e.g., 1008-2) including at least a third metric associated with data from the second application (e.g., 1020) and a fourth metric associated with data from the second application (e.g., 1022), and a third complication (e.g., 1008-3) including at least a fifth metric associated with data from the third application (e.g., 1012) and a sixth metric associated with data from the third application (e.g., 1014). In some embodiments, the second application is different from the first application (e.g., FIGS. 10A-10I). In some embodiments, the second application is the same as the first application, but the third and fourth metrics are different from the first and second metrics (e.g., FIGS. 10J-10Q). In some embodiments, the third application is different from the first and / or second application (e.g., FIGS. 10A-10E). In some embodiments, the third application is the same as the first and second applications, but the fifth and sixth metrics are different from the first, second, third, and fourth metrics (e.g., Figures 10K-10L).

[0294] Automatically grouping the display of related metrics in multiple locations on the interface provides users with an efficient way to identify related information and decipher data from multiple applications offered by the device. The additional content provided by visual grouping improves usability of the device by providing feedback to the user on how to interpret the displayed data, makes the user device interface more efficient (e.g., by assisting the user in providing appropriate input when operating / interacting with the device, reducing user errors, and increasing the speed at which the user can interpret data), and also reduces power usage and improves the device's battery life by allowing the user to use the device more efficiently.

[0295] In some embodiments, the first complication further includes a ninth metric related to data from the first application (e.g., 1008-1), the second complication further includes a tenth metric related to data from the second application (e.g., 1008-2 in FIGS. 10B-10I), and the third complication further includes an eleventh metric related to data from the third application (e.g., 1008-4). In some embodiments, the first, second, or third complication is a humidity complication (e.g., 1008-5 including current humidity, low humidity, and high humidity), a heart rate complication (e.g., 1008-2 including current heart rate, low heart rate, and high heart rate), or a weather complication (e.g., 1008-1 including current temperature, minimum temperature, and maximum temperature).

[0296] In some embodiments, the first application, the second application, and the third application are the same application (eg, FIGS. 10J-10T).

[0297] In some embodiments, the first application is different from the second application, and the third application is different from the first application and the second application (eg, FIGS. 10A-10E).

[0298] In some embodiments, the clock user interface (e.g., 1093) further includes a clock face having a curved outer edge and a curved complication having a visual feature that follows the outer edge of the clock face (e.g., FIG. 10N).

[0299] By automatically presenting information to match the outer edge of the clock face, the user interface is kept clutter-free, providing the user with augmented visual feedback. This allows the user to focus their attention on fewer visual elements, thereby enabling them to more quickly locate relevant information throughout the interface and more accurately interact with desired control features on the display. This improves device usability and makes the user-device interface more efficient (e.g., by helping the user more quickly locate, and more accurately, provide appropriate inputs when operating / interacting with the device, reducing user errors), which in turn reduces device power usage and improves battery life by allowing the user to use the device more quickly and efficiently.

[0300] In some embodiments, the clock user interface (e.g., 1097) further includes a ring-shaped region with a curved outer edge and corner complications, a status bar (e.g., 1082) that follows the outer edge of the ring-shaped region, and a value (e.g., 1086) located between the status bar and the corner of the display (e.g., FIG. 10P).

[0301] In some embodiments, the first metric and the second metric relate to data from a clock application, where the first metric represents a geographic location and the second metric represents a time (e.g., 1060) associated with the geographic location. In some embodiments, the first and second metrics represent other clock data (e.g., an offset relative to local time, or sunset and sunrise times).

[0302] In some embodiments, the first metric and the second metric relate to data from a calendar or date application (e.g., FIG. 10N), where the first metric represents an event and the second metric represents a time associated with the event (e.g., 1070-2). In some embodiments, the first and second metrics represent other data (e.g., the location of the event).

[0303] In some embodiments, the first metric and the second metric are related to data from a stock application (e.g., 1078 in FIG. 10O), where the first metric represents a stock name and the second metric represents an associated stock price. In some embodiments, the first and second metrics represent other data (e.g., price movement direction, price rate of change, etc.).

[0304] In some embodiments, the first metric and the second metric relate to data from a weather application (e.g., 1008-1), with the first metric representing the current temperature (e.g., 1010) and the second metric representing predicted high and low temperatures (e.g., 1026). In some embodiments, the first and second metrics represent other data, such as humidity, wind speed and direction, visual indications of weather conditions, and their predicted values ​​(e.g., FIGS. 10J-10L).

[0305] In some embodiments, the first complication includes a visual representation of one or more metrics, where the visual representation includes an indication of a value relative to a range of values ​​(e.g., 1088-1 and 1088-3). In some embodiments, the complication represents a goal value and progress toward that value (e.g., 1090) (e.g., total battery capacity and current state of charge, air quality, and various health and fitness metrics such as steps taken, stairs climbed, stationary time, and calorie goals). In some embodiments, the complication displays one or more metrics (e.g., current value and high and low values ​​for a parameter) on a gauge representing data from an application (e.g., a weather application including temperature, humidity, wind speed, etc.).

[0306] In some embodiments, the first complication includes a visual representation of one or more metrics, the visual representation including a first affordance representing a simulation of a first region of the Earth illuminated by the sun at the current time, and the method includes detecting a sequence of one or more user inputs corresponding to a request to view the simulation of the Earth at a non-current time, and in response to detecting the sequence of one or more user inputs corresponding to the request to view the simulation of the Earth at the non-current time, rotating the simulation of the Earth to present a second region of the Earth illuminated by the sun at the non-current time. In some embodiments, the sequence of one or more inputs includes an input corresponding to a selection of the first complication, which causes device 600 to launch an astronomy application displaying an interactive simulation of the Earth illuminated by the sun at the current time. In response to an input (e.g., a swipe) on the simulation of the Earth within the astronomy application, the device rotates the simulation of the Earth to present a region of the Earth illuminated by the sun at the current time (e.g., 608-2).

[0307] The visual representation of the Earth illuminated by the sun provides a user with a quick means of determining a large amount of information (e.g., time of day, geographic location, season, relative daytime and nighttime times, etc.) without cluttering the interface with extraneous textual elements. This allows a user to more quickly search for relevant information throughout the interface and access desired controls more quickly and accurately. This improves device usability and makes the user-device interface more efficient (e.g., by helping the user more quickly provide location information, or more precisely, the appropriate input, and reducing user errors when operating / interacting with the device), which in turn reduces device power usage and improves battery life by allowing the user to use the device more quickly and efficiently.

[0308] At block 1104, the device detects a sequence of one or more inputs (e.g., 1081 and 1083) corresponding to a request to add a fourth complication (e.g., 1008-4) to the watch user interface (e.g., 1002 in FIGS. 10C-10E). The fourth complication includes at least a seventh metric associated with data from a fourth application (e.g., 1040) and an eighth metric associated with data from a fourth application (e.g., 1042).

[0309] In response to detecting a sequence of one or more inputs at block 1106, the device performs the operations of block 1108, block 1110, or block 1112. In response to determining that a sequence of one or more inputs corresponds to a request to replace a first complication at block 1108, the device replaces the first complication with a fourth complication (e.g., FIG. 10F). In response to determining that a sequence of one or more inputs (e.g., 1082) corresponds to a request to replace a second complication at block 1110, the device replaces the second complication with a fourth complication (e.g., FIG. 10H). In response to determining that a sequence of one or more inputs corresponds to a request to replace a third complication at block 1112, the device replaces the third complication with a fourth complication.

[0310] Optionally, in accordance with a determination at block 1114 that the sequence of one or more inputs corresponds to a request to replace the first complication, the device maintains the second complication and the third complication (e.g., FIG. 10F). Optionally, in accordance with a determination at block 1116 that the sequence of one or more inputs corresponds to a request to replace the second complication, the device maintains the first complication and the third complication (e.g., FIG. 10H). Optionally, in accordance with a determination at block 1118 that the sequence of one or more inputs corresponds to a request to replace the third complication, the device maintains the first complication and the second complication. In some embodiments, the watch user interface includes additional elements, such as hands and additional complications, that are not modified while replacing the selected complication.

[0311] In some embodiments, the clock user interface (e.g., 1093) further includes a ring-shaped region having a curved outer edge. In some embodiments, the clock face is an analog clock face having tick marks, hour markers (e.g., numerals), and / or minute markers (e.g., numerals) (e.g., 1072). Optionally, at block 1120, in accordance with a first application corresponding to the fifth application, the device displays visual characteristics in or around the ring-shaped region (e.g., FIG. 10N). Optionally, at block 1122, in accordance with a first application corresponding to a sixth application different from the fifth application, the device ceases displaying visual characteristics in or around the ring-shaped region (e.g., FIG. 10M).

[0312] Optionally, at block 1124, the device displays a second clock user interface. In some embodiments, the second clock user interface includes a fifth complication that includes fewer than two metrics related to data from the first application and that is the same size as the first complication (e.g., 1008-2 in FIG. 10A ).

[0313] Reconfiguring a set of elements on a watch face together to provide a simplified interface in response to input provides a user with more control over a device by assisting the user in quickly configuring multiple display elements into various configurations without requiring the user to interact with each element individually, improving usability of the device by reducing the number of inputs required to perform equivalent actions, making the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the device), and further reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

[0314] In some embodiments, the fifth complication does not include metrics related to data from the first application (eg, 1008-2 in FIG. 10A).

[0315] In some embodiments, the fifth complication has a lower resolution than the first complication on the watch user interface (e.g., 1008-1 and 1008-1 in FIG. 10A).

[0316] In some embodiments, the user interface (e.g., 1091, 1093, 1095, 1097, and 1099) is a first clock user interface, and the first application, the second application, and the third application are the same application (e.g., FIGS. 10M-10Q). Optionally, while displaying the first clock user interface, at block 1126, the device detects a sequence of one or more inputs corresponding to a selection of a second clock user interface (e.g., FIGS. 10A-10B).

[0317] Providing a themed interface that collectively reconfigures a set of elements on a watch face to provide related information to the user provides the user with more control over the device by helping the user quickly configure multiple display elements into configurations containing various related information without requiring the user to interact with each element individually. Reducing the number of inputs required to perform equivalent actions improves device usability (e.g., by helping the user provide appropriate inputs when operating / interacting with the device, thereby reducing user errors) and makes the user-device interface more efficient. Furthermore, grouping related information on the display allows the user to more easily and efficiently decipher displayed data. Each of these benefits also reduces power usage and improves the device's battery life by allowing the user to use the device more quickly and efficiently.

[0318] In response to detecting a sequence of one or more inputs corresponding to a selection of a second watch user interface, the device optionally performs the operation of block 1128. In block 1128, the device displays a second watch user interface (e.g., 1091, 1093, 1095, 1097, and 1099), where the second watch user interface includes an eighth complication corresponding to a seventh application, a ninth complication corresponding to the seventh application, and a tenth complication corresponding to a seventh application different from the first application.

[0319] In some embodiments, the first complication includes a visual representation of one or more metrics, and the visual representation includes a first affordance representing a simulation of a first region of the Earth as illuminated by the sun at the current time (e.g., 608-2). Optionally, at block 1130, the device detects a sequence of one or more user inputs corresponding to a request to view a simulation of the Earth at a non-current time. Optionally, at block 1132, in response to detecting the sequence of one or more user inputs corresponding to a request to view a simulation of the Earth at the non-current time, the device rotates the simulation of the Earth to present a second region of the Earth as illuminated by the sun at the non-current time. In some embodiments, the sequence of one or more inputs includes an input corresponding to a selection of the first complication, which causes device 600 to launch an astronomy application that displays an interactive simulation of the Earth as illuminated by the sun at the current time. In response to an input (e.g., a swipe) on the simulation of the Earth within the astronomy application, the device rotates the simulation of the Earth to present a region of the Earth as illuminated by the sun at the current time.

[0320] It should be noted that the details of the processes described above with respect to method 1100 (e.g., FIGS. 11A-11D) are also applicable in a similar manner to the methods described above (e.g., 700 and 900). For example, method 900 optionally includes one or more of the features of the various methods described above with reference to method 1100. For example, watch user interface 801 of FIG. 8A can be configured to additionally display three complications (e.g., complications 1008-1, 1008-2, and 1008-3 of FIG. 10A) including at least two metrics on background 810 in a manner similar to the technique described with reference to method 1100. For brevity, these details will not be repeated below.

[0321] 12A-12R show exemplary clock user interfaces according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the method of FIG.

[0322] FIG. 12A illustrates such a device 600. As shown in FIG. 12A, device 600 displays a clock user interface 1200 on display 602. Clock user interface 1200 includes a clock face 1202 surrounded by a bezel 1204. In FIG. 12A, clock face 1202 includes a time display having hour hand 1206-1, minute hand 1206-2, and second hand 1206-3. Clock user interface 1200 also includes a training complication 1208-1, a music complication 1208-2, a timer complication 1208-3, and a world clock complication 1208-4 (collectively "complications 1208"). Training complication 1208-1 is associated with a training application, as indicated by the character icon included in the complication. Training complication 1208-1 does not include metrics related to data from a training application (e.g., training complication 1208-1 includes only a single icon). Music complication 1208-2 is associated with a music application and displays data from the music application (e.g., the time remaining in a currently playing music file), as indicated by the musical note icon included in the complication. Timer complication 1208-3 displays data from a timer application, including elapsed time and / or remaining time (e.g., the timer data is displayed in numerical form and / or as a circular ring progressing radially along the inner edge of the complication at a rate proportional to the passage of time). World Clock complication 1208-4 includes metrics related to data from a world clock application, including a corresponding location (e.g., London) and the time associated with the location (e.g., an analog clock face with hour and minute hands). In FIG. 12A, complications 1208-1, 1208-2, 1208-3, and 1208-4 occupy corresponding locations in the top, right, bottom, and left regions of watch face 1202.

[0323] 12A, watch user interface 1200 also includes corner complications 1212-1, 1212-2, 1212-3, and 1212-4 (collectively “corner complications 1212”) that occupy the top right, bottom right, bottom left, and top left locations, respectively, of watch user interface 1200. (E.g., corner complication 1212-1 resides in the region of watch user interface 1200 between the outer edge of bezel 1204 and the corner formed by the intersection of the top and right edges of display 602.) As described with reference to FIG. 10P above, corner complications 1212-1, 1212-2, and 1212-4 each display data associated with a range of values ​​associated with a corresponding application (e.g., temperature, humidity, air quality index (AQI), or UV index from a weather application). Corner complication 1212-3 contains only a single graphical element showing data from a weather application (eg, sunlight sky conditions).

[0324] 12A, device 600 receives (e.g., detects) user input 1290 (e.g., a long press on display 602) corresponding to a request to edit watch user interface 1200. In response to user input 1290, device 600 enters an edit mode (e.g., a clock face edit mode or a complication edit mode). In FIG. 12B, device 600 indicates the edit mode by visually highlighting training complication 1208-1 for editing (e.g., by displaying a box 1214 around workout complication 1208-1 and a label 1216 identifying the associated application). In some embodiments, device 600 visually highlights the complication selected for editing (e.g., workout complication 1208-1) by modifying one or more visual characteristics (e.g., brightness, opacity, color, contrast, hue, saturation, etc.) of watch user interface 1200, or portions thereof. In some embodiments, while in edit mode, a complication selected for editing is displayed in a first visual characteristic (e.g., a color or colors other than grayscale), and in some embodiments, one or more other complications (e.g., all other complications) are displayed in a second visual characteristic (e.g., grayscale or a single color that is different from the colors in which the complications would be displayed while the device is not in edit mode), even though some or all of the other complications would be displayed in one or more colors within the clock face when the clock face is not in edit mode. For example, complication 1208-1 is displayed in color, and complications 1208-2, 1208-3, and 1208-4 are displayed in grayscale. In some embodiments, while in edit mode, instead of or in addition to changing the visual characteristic of one or more selected complications, the visual characteristic of one or more unselected complications is changed (e.g., the brightness or opacity of one or more unselected complications is reduced to distinguish between selected and unselected complications).In some embodiments, the visual distinction of the selected complication is in place of or in addition to an alternative selection indicator, such as a selection ring around at least a portion of the selected complication. While in edit mode, device 600 also displays a complication menu bar 1218 having a complication position indicator 1220, which indicates the position of the currently displayed complication within a menu of complications available for selection. In some embodiments, user input 1290 includes a contact having a characteristic intensity, and device 600 enters edit mode pursuant to a determination that the characteristic intensity exceeds a predetermined threshold intensity.

[0325] 12C , device 600 receives (e.g., detects) user input 1292, which includes rotation of rotatable input mechanism 604. In some embodiments, user input 1292 is received on another device that communicates with device 600 (e.g., via a counterpart application associated with device 600 running on the other device). In response to receiving user input 1292, device 600 displays and adds a representation of calendar complication 1208-5 to watch user interface 1200 in place of training complication 1208-1. In FIG. 12D , device 600 updates complication position indicator 1220 to indicate that calendar complication 1208-5 is located near the top of the complications menu (e.g., because complications are alphabetical and "c" is near the start of the alphabet). As shown in FIG. 12D, the representation of the calendar complication 1208-5 includes an indication of the type of information that the information calendar complication 1208-5 will display on the watch user interface 1200 upon exiting edit mode (e.g., the current day of the week (Wednesday), the date (the 23rd), and text describing "Next Appointment").

[0326] In some embodiments, while in edit mode, the device receives (e.g., detects) one or more inputs (e.g., taps on the display 602 or presses on the rotatable input mechanism 604) corresponding to a request to exit edit mode. In response to exiting edit mode, the device 600 adds a calendar complication 1208-5 to the watch user interface 1200, replacing the workout complication 1208-1 in the top region of the watch face 1202 and a portion of the bezel 1204. As shown in FIG. 12E , the calendar complication 1208-5 includes two components: a graphic element 1209 (e.g., a month showing the current day and date) and a text element 1210 (e.g., a text description of the next calendar event). As shown in FIG. 12E, graphic element 1209 is positioned on watch face 1202 closer to the center of display 602 than the inner edge of bezel 1204 (e.g., in the position previously occupied by complication 1208-1 in the upper region of watch face 1202) without overlapping the area previously occupied by bezel 1204, and text element 1210 is positioned in a curved region along the edge of watch face 1202 (e.g., in the location previously occupied by the top of bezel 1204).

[0327] By automatically presenting content to utilize different areas of the display based on the content, the user interface is kept clutter-free, providing the user with augmented visual feedback. This allows the user to focus their attention on fewer visual elements, thereby enabling them to more quickly locate relevant information throughout the interface and more accurately interact with desired control features on the display. This improves device usability and makes the user-device interface more efficient (e.g., by helping the user more quickly locate, and more accurately, provide appropriate inputs when operating / interacting with the device and reducing user errors), which in turn reduces device power usage and improves battery life by allowing the user to use the device more quickly and efficiently.

[0328] As time passes, device 600 updates clock user interface 1200, as shown in FIG. 12F. In FIG. 12F, the time displayed by hour hand 1206-1 and minute hand 1206-2 displays the current time of 01:42:30 (previously 10:09:30 in FIG. 12E). As time passes, text element 1210 updates to reflect the next event for the current time (e.g., an office meeting at 3:00 PM), and the time displayed on world clock complication 1208-4 updates to reflect the local time of the corresponding location (e.g., 09:42:30 in London). As shown in FIG. 12F, the size of text element 1210 is based on the length of the associated content (e.g., the fewer characters in the next appointment, the shorter the text element and the less bezel 1204 is displaced).

[0329] Provides augmented visual feedback to the user by automatically adjusting the size of interface elements based on content, thereby keeping the user interface free of clutter. This allows the user to focus their attention on fewer visual elements, thereby enabling them to more quickly locate relevant information throughout the interface and more accurately interact with desired control features on the display. This improves device usability and makes the user device interface more efficient (e.g., by helping the user more quickly locate, and more accurately, provide appropriate inputs when operating / interacting with the device, and reducing user errors), which in turn reduces device power usage and improves battery life by allowing the user to use the device more quickly and efficiently.

[0330] As shown in FIG. 12G, device 600 receives (e.g., detects) user input 1294 (e.g., a tap) on calendar complication 1208-5 (e.g., a graphic element portion of complication 1208-5 or a text element portion occupying the area of ​​watch user interface 1200 previously occupied by bezel 1202). In response to receiving user input 1294, device 600 launches an application corresponding to calendar complication 1208-5 (e.g., a calendar application). As shown in FIG. 12H, upon launching the calendar application, watch user interface 1200 updates to display data from the calendar application, including date element 1230, appointment time element 1232, appointment description element 1234, and a digital representation of the time 1236. In some embodiments, the device 600 receives (eg, detects) a user input 1294 (eg, a tap) at a location other than the calendar complication 1208-5, and the device ceases launching the calendar application.

[0331] 12I-12L, an embodiment of a watch user interface including a heart rate complication is shown. FIG. 12I shows watch user interface 1200-2 at a first time (e.g., hour hand 1206-1 and minute hand 1206-2 showing 10:42:30). Watch user interface 1200-2 includes heart rate complication 1208-6, which includes graphic element 1209 (e.g., a heart icon) and text element 1210 (e.g., including a heart rate value of 64 BPM and a last reading of "3 minutes ago"). Graphic element 1209 is positioned closer to the center of display 602 than the inner edge of bezel 1204.

[0332] Figure 12J shows the watch user interface 1200-2 at a later time (e.g., hour hand 1206-1 and minute hand 1206-2 showing 01:42:30). The watch user interface 1200-2 includes a heart rate complication 1208-6 that displays updated text elements 1210 (e.g., including a heart rate value of 72 BPM and a last reading of "2 minutes ago"). The watch user interface 1200-2 also includes a world clock complication 1208-4 with an updated time display corresponding to the change in time between Figures 12I and 12J.

[0333] Alternatively, as shown in FIGS. 12K-12L, the device 600 displays the heart rate complication 1208-6 in a compact form (e.g., the heart rate complication 1208-6 consists of a single graphic icon positioned on the watch face 1202 closer to the center of the display 602 than the inner edge of the bezel 1204).

[0334] 12K-12N illustrate embodiments of a watch user interface including an activity complication. FIG. 12K shows watch user interface 1200-3 at a first time (e.g., hour hand 1206-1 and minute hand 1206-2 indicating 10:42:30). Watch user interface 1200-3 includes activity complication 1208-7, which includes graphic element 1209 and text element 1201 containing a calorie value (e.g., 350 cal), an active time value (e.g., 26 minutes), and a resting time value (e.g., 4 hours). Graphic element 1209 includes an icon representing progress toward multiple activity-related fitness goals (e.g., a circular icon showing progress toward calories burned, active time, and resting time as three concentric circular bands progressing radially within the icon in proportion to progress toward each goal).

[0335] Figure 12L shows the clock user interface 1200-3 at a later time (e.g., with hour hand 1206-1 and minute hand 1206-3 showing 01:42:30). The clock user interface 1200-3 includes an activity complication 1208-7 that displays updated text elements 1210 (e.g., including a calorie value of 601 cal, an active time value of 92 minutes, and a sedentary time value of 9 hours) and updated graphic elements 1209 that show progress toward goals for calories burned, active time, and sedentary time. The clock user interface 1200-3 also includes a world clock complication 1208-4 with an updated time display corresponding to the change in time between Figures 12K and 12L.

[0336] Alternatively, as shown in FIGS. 12M-12N, device 600 displays activity complication 1208-7 in a compact form (e.g., activity complication 1208-7 consists of a single graphic icon positioned on watch face 1202 closer to the center of display 602 than the inner edge of bezel 1204).

[0337] 12M-12P show an embodiment of a watch user interface including a breathing complication. Figure 12M shows watch user interface 1200-4 at a first time (e.g., hour hand 1206-1 and minute hand 1206-2 showing 10:42:30). Watch user interface 1200-4 includes a breathing complication 1208-8 that displays a graphic element 1209 (e.g., an icon representing a corresponding meditation or mindfulness application) and a text element 1210 that includes a number of sessions performed (e.g., two breathing sessions today).

[0338] Figure 12N shows clock user interface 1200-4 at a later time (e.g., hour hand 1206-1 and minute hand 1206-3 point to 01:42:30). Clock user interface 1200-4 includes a breathing complication 1208-8 that displays a graphic element 1209 (e.g., an icon representing a corresponding meditation or mindfulness application) and an updated text element 1210 (e.g., four breathing sessions today). Clock user interface 1200-4 also includes a world clock complication 1208-4 with an updated time display corresponding to the change in time between Figures 12M and 12N.

[0339] Alternatively, as shown in FIGS. 12O and 12P, the device 600 may display the breathing complication 1208-8 in a compact form (e.g., the breathing complication 1208-8 consists of a single graphic icon positioned on the watch face 1202 closer to the center of the display 602 than the inner edge of the bezel 1204).

[0340] 12O and 12P illustrate embodiments of a clock user interface including a world clock complication. FIG. 12O illustrates a clock user interface 1200-5 at a first time (e.g., hour hand 1206-1 and minute hand 1206-2 indicating 10:42:30). The clock user interface 1200-5 includes a world clock complication 1208-9 that includes a graphic element 1209 (e.g., an analog clock face with hour and minute hands) and a text element 1210 that includes a corresponding location (e.g., New York), a time associated with the corresponding location (e.g., an analog clock face with hour and minute hands), and an offset (e.g., a +3 hour offset relative to local time). In some embodiments, the offset is used to indicate an offset relative to another time zone (e.g., GMT). The watch user interface 1200-5 also includes a world clock complication 1208-4 as described above (e.g., a compact representation consisting of a graphic icon displaying a corresponding location and the time associated with the corresponding location (e.g., London) positioned on the watch face 1202 closer to the center of the display 602 than to the inner edge of the bezel 1204).

[0341] 12P shows the clock user interface 1200-5 at a later time (e.g., hour hand 1206-1 and minute hand 1206-3 showing 01:42:30). The clock user interface 1200-5 includes an updated graphic element 1209 (e.g., an icon showing an analog clock face with hour and minute hands showing 10:20), a text element 1210 with an updated location (e.g., New York), a time associated with the updated corresponding location (e.g., a text display of the time showing 10:20 PM), and a world clock complication 1208-9 displaying an offset (e.g., +3 hours relative to local time). The clock user interface 1200-5 also includes a world clock complication 1208-4 with an updated display of the time to reflect the change in time between FIG. 12O and FIG. 12P.

[0342] 12Q and 12R show embodiments of a watch user interface that includes a weather complication. FIG. 12Q shows watch user interface 1200-6 at a first time (e.g., hour hand 1206-1 and minute hand 1206-2 showing 10:42:30). Watch user interface 1200-6 includes weather complication 1208-10 that displays graphic element 1209 (e.g., an icon indicating sunny weather) and text element 1210 that includes a description of the current or forecasted weather (e.g., current 79 degrees, sunny, forecast high 81 and low 62). Watch user interface 1200-6 also includes complications 1212-1 (e.g., an icon indicating sunshine weather conditions from a weather application) and 1212-3 (e.g., a gauge showing the current temperature of 79 against a range), as described above.

[0343] FIG. 12R shows clock user interface 1200-6 at a later time (e.g., hour hand 1206-1 and minute hand 1206-2 showing 01:42:30). Clock user interface 1200-6 includes weather complication 1208-10 displaying updated graphic element 1209 (e.g., an icon showing partly sunny), updated text element 1210 including a description of the current and forecasted weather (e.g., current 64 degrees, partly sunny, forecast high 81 and low 62), and updated weather complications 1212-1 (e.g., an icon reflecting partly sunny weather at a second time) and 1212-3 (e.g., representing the current temperature of 64 against a range). Clock user interface 1200-6 also includes world clock complication 1208-4 with an updated time display to reflect the change in time between FIG. 12Q and FIG. 12R.

[0344] 13 is a flow diagram illustrating a method for providing a context-specific user interface using an electronic device, according to some embodiments. Method 1300 is performed on a device (e.g., 100, 300, 500, 600) that includes a display and one or more input devices. Some operations of method 1300 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0345] In block 1302, a device (e.g., 600) displays on a display (e.g., 602) a clock user interface (e.g., 1200) including a clock face (e.g., 1202) and a user interface element (e.g., 1204) that at least partially surrounds the clock face. In some embodiments, the clock face is a circular analog clock face (e.g., 1202). In some embodiments, the user interface element is a portion of an area on the display that surrounds the clock face (e.g., a clock face bezel). In some embodiments, the user interface element is a section of a ring-shaped area that surrounds the clock face (e.g., from approximately 10 o'clock to 2 o'clock clockwise). In some embodiments, the user interface element is completely outside the clock face (e.g., 1204 in FIGS. 12A-12B). In some embodiments, the size of the user interface element (e.g., the angular extent of the ring-shaped region surrounding the clock face) depends on the content associated with the first complication (e.g., 1204 in FIGS. 12E-12F). As used herein, a bezel is a virtual rim that at least partially surrounds the area of ​​the display that functions as the clock face. In some embodiments, the bezel has markings associated with a particular measurement (e.g., units per hour) and is optionally rotatable. In some embodiments, the bezel is completely outside of (e.g., does not overlap with) the clock face (e.g., 1204 in FIGS. 12A-12B). However, unlike a static bezel, in some embodiments, the virtual bezel can be changed, as described in some of the embodiments described below.

[0346] At block 1304, a device (e.g., 600) receives a request (e.g., a sequence of one or more touch and / or rotatable input mechanism inputs) via one or more input devices (e.g., 604) to add a corresponding complication to a corresponding location on the clock face (e.g., location 1208-1 for the clock face in FIGS. 12A-12C). In some embodiments, each location is contained entirely within the clock face (e.g., 1208-1 in FIG. 12A).

[0347] In response to receiving a request to add the corresponding complication to the corresponding location on the watch face, the device performs the operations of block 1306 and / or block 1308.

[0348] In block 1306, in accordance with a determination that the corresponding complication is the first complication (e.g., 1208-5), the device (e.g., 600) displays the first complication on the display (e.g., 602) at a corresponding location on the watch face and replaces at least a portion of the user interface elements with content associated with the first complication (e.g., 1208-5 in FIG. 12E). In some embodiments, the first complication is associated with content related to a calendar application (e.g., event or appointment description, date, time, location, etc.), a weather application (e.g., sun or cloud conditions, wind speed, wind direction, temperature range, humidity, etc.), an exercise application (e.g., resting time, heart rate, activity minutes, calories, number of stairs climbed, etc.), a heart rate application (e.g., current heart rate, resting heart rate, active heart rate, time since last heart rate reading, etc.), a respiration application (e.g., respiration rate, time, etc.), or a clock application (e.g., displaying the time, location, GMT offset, etc.) (e.g., Figures 12E-12G and 12I-12R).

[0349] By automatically presenting content to utilize different regions of the display based on the type of complication, the user interface is kept clutter-free, providing the user with augmented visual feedback. This allows the user to focus their attention on fewer visual elements, thereby enabling them to more quickly locate relevant information throughout the interface and more accurately interact with desired control features on the display. This improves device usability and makes the user-device interface more efficient (e.g., by helping the user more quickly locate, and more accurately, provide appropriate inputs when operating / interacting with the device and reducing user errors), which in turn reduces device power usage and improves battery life by allowing the user to use the device more quickly and efficiently.

[0350] In some embodiments, the content associated with the first complication includes first content (e.g., text, data from an application on the device) (e.g., 1210), and the first complication includes second content (e.g., visual label 1209) displayed at a corresponding location on the watch face, and the second content is associated with the first complication (e.g., 1208-5 in Figures 12A-12G, 1208-6 in Figures 12I-12J, 1208-7 in Figures 12K-12L, 1208-8 in Figures 12M-12N, 1208-9 in Figures 12O-12P, 1208-10 in Figures 12Q-12R).

[0351] In some embodiments, the first content represents data from an application and the second content represents data from an application different from the first content (e.g., the first content represents date data from a calendar application and the second content represents filling information data from the same calendar application) (e.g., 1208-5, 1208-9 in Figures 12O-12P, 1208-10 in Figures 12Q-12R).

[0352] In some embodiments, the first content includes textual information associated with the first complication (eg, text curves around the outer edge of the analog surface) (eg, 1210).

[0353] In some embodiments, the size of the portion of the user interface element is based on the content associated with the first complication (e.g., the portion of the user interface element has a first size according to the content being a first content, and the portion of the user interface element has a second size according to the content being a second content). In some embodiments, the amount of the user interface element replaced depends on the content (e.g., the length of the calendar event title, etc.) (e.g., 1210 in FIGS. 12E-12F). In some embodiments, the amount of the user interface element replaced is proportional to the amount of the content (e.g., length, number of characters, etc.) (e.g., 1210 in FIGS. 12E-12F).

[0354] Automatically adjusting the size of elements on the user interface based on associated content improves visual feedback by allowing the user to focus their attention on fewer visual elements, resulting in faster location of relevant information throughout the interface and more accurate interaction with desired control features on the display. This improves device usability and makes the user device interface more efficient (e.g., by helping the user more quickly locate, and more accurately, provide appropriate inputs when operating / interacting with the device and reducing user errors), which in turn reduces device power usage and improves battery life by allowing the user to use the device more quickly and efficiently.

[0355] In block 1308, in accordance with a determination that the corresponding complication is a second complication (e.g., 1208-1, 1208-2, 1208-3, 1208-4, 1208-6 in Figures 12K-12L, 1208-7 in Figures 12M-12N, 1208-8 in Figures 12O-12P), the device (e.g., 600) displays the second complication on the display (e.g., 602) at a corresponding location on the watch face (e.g., location 1208-1 in Figure 12A) without replacing any of the user interface elements with content associated with the second complication (e.g., Figure 12A). In some embodiments, the second complication does not include information from an associated application, such as a mail, message, or training complication (e.g., 1208-1, 1208-6 in FIGS. 12K-12L and 1208-8 in FIGS. 12O-12P). In some embodiments, the second complication includes content unrelated to the application (e.g., battery level).

[0356] In some embodiments, the second complication consists of a single graphic element (e.g., a visual label) (e.g., 1208-1, 1208-2, 1208-3, 1208-4, 1208-6 in Figures 12K-12L, 1208-7 in Figures 12M-12N, and 1208-8 in Figures 12O-12P).

[0357] Optionally, at block 1310, while displaying content associated with the first complication within a portion of a user interface element (e.g., FIG. 12G), the device receives input (e.g., tap input) corresponding to a location on the display (e.g., 1294).

[0358] In response to receiving input corresponding to a location on the display (e.g., 1294), the device optionally performs the operations of block 1312 and / or block 1314. At block 1312, in accordance with the input corresponding to a location on a portion of a user interface element (e.g., a portion occupied by content associated with the first complication), the device launches an application associated with the first complication (e.g., FIGS. 12G-12H). At block 1314, in accordance with the input corresponding to a location on a user interface element other than the portion of the user interface element, the device cancels the launch of the application associated with the first complication.

[0359] Selectively launching applications automatically based on the location of an input provides users with more control over their devices by helping them quickly execute multiple commands without having to navigate complex menu structures, allowing users to more precisely interact with desired control features on the display. This improves device usability and makes the user-device interface more efficient (e.g., by helping users more quickly locate and, more precisely, provide appropriate inputs when operating / interacting with the device and reducing user errors), which in turn reduces device power usage and improves battery life by allowing users to use the device more quickly and efficiently.

[0360] In some embodiments, the first complication (e.g., 1208-5) includes date information (e.g., 1209 in FIGS. 12E-12G) (e.g., a visual label representing the date or day of the week) displayed in a corresponding location on the clock face (e.g., location 1208-5 in FIGS. 12E-12G), and content associated with the first complication displayed in a portion of the user interface element includes information (e.g., text labels representing the description, subject, time, location, and / or attendees, etc.) from the appointment (e.g., 1210 in FIGS. 12E-12G). In some embodiments, the first complication (e.g., 1208-5) is associated with a calendar application from which the date or appointment information is obtained. In some embodiments, user input directed to the calendar information displayed in a corresponding location on the clock face (e.g., 1294) launches the associated calendar application (e.g., FIG. 12H).

[0361] In some embodiments, the first complication (e.g., 1208-10 in FIGS. 12Q-12R) includes first weather information (e.g., 1209 in FIGS. 12Q-12R) (e.g., visual labels representing sunshine, clouds, precipitation, etc.) displayed at a corresponding location on the watch face (e.g., at location 1208-10 in FIGS. 12Q-12R), and content associated with the first complication displayed on a portion of the user interface element includes second weather information (e.g., 1210 in FIGS. 12Q-12R) (e.g., textual labels representing sunshine or cloud conditions, wind speed, wind direction, temperature range, humidity, and / or location, etc.) that is different from the first weather information. In some embodiments, the first complication is associated with a weather application from which the first or second weather information is obtained. In some embodiments, a user input directed at the first weather information displayed at the corresponding location on the watch face launches the associated weather application.

[0362] In some embodiments, a first complication (e.g., 1208-7 in FIGS. 12K-12L) includes one athletic information (e.g., 1209 in FIGS. 12K-12L) displayed at a corresponding location on the watch face (e.g., 1208-10 in FIGS. 12K-12L), and content associated with the first complication displayed in a portion of the user interface element includes second athletic information (e.g., 1210 in FIGS. 12Q-12R) that is different from the first athletic information (e.g., text labels representing steps, stairs climbed, stationary time, calories burned, and / or active time, etc.). In some embodiments, the first athletic information includes one or more fitness goals and visual labels (e.g., 1209 in FIGS. 12Q-12R) representing progress toward the goal (e.g., steps, stairs climbed, stationary time, calories burned, active time, etc.). In some embodiments, the first complication is associated with an athletic application from which the first or second athletic information is obtained, and in some embodiments, a user input directed to the first athletic information displayed in a corresponding location on the watch face launches the associated athletic application.

[0363] In some embodiments, the first complication (e.g., 1208-6 in FIGS. 12I-12J ) includes an affordance (e.g., a heart-shaped visual label) displayed at a corresponding location on the watch face (e.g., at location 1208-6 in FIGS. 12I-12J ), and content associated with the first complication displayed on a portion of the user interface element includes heart rate information (e.g., 1210 in FIGS. 12I-12J ) (e.g., current heart rate, resting heart rate, active heart rate, average heart rate, time since last heart rate reading, etc.). In some embodiments, the first complication is associated with a heart rate application from which the heart rate information is obtained. In some embodiments, user input directed at the affordance displayed at the corresponding location on the watch face launches the associated heart rate application.

[0364] In some embodiments, the first complication (e.g., 1208-7 in FIGS. 12M-12N) includes an affordance that is displayed at a corresponding location on the watch face (e.g., at location 1208-7 in FIGS. 12M-12N), and content associated with the first complication is displayed in a portion of the user interface and includes meditation or mindfulness information (e.g., 1210 in FIGS. 12M-12N). In some embodiments, the affordance is a visual label (e.g., 1209 in FIGS. 12M-12N) that represents a meditation or mindfulness application (e.g., a breathing application). In some embodiments, the meditation or mindfulness information includes a text label (e.g., 1210 in FIGS. 12M-12N) that represents a breathing rate, a session number, a time, etc. In some embodiments, the first complication is associated with a meditation or mindfulness application from which the meditation or mindfulness information is obtained. In some embodiments, user input directed at an affordance displayed in a corresponding location on the watch face launches an associated meditation or mindfulness application.

[0365] In some embodiments, the first complication (e.g., 1208-9 in FIGS. 12O-12P) includes first time information (e.g., 1209 in FIGS. 12O-12P) (e.g., an analog clock including a clock face and a minute hand) displayed at a corresponding location on the clock face (e.g., at locations 1208-9 in FIGS. 12O-12P), and content associated with the first complication displayed on a portion of the user interface element includes second time information (e.g., 1210 in FIGS. 12O-12P) that is different from the first time information (e.g., a digital representation of the time, a location, a GMT offset, and / or other information). In some embodiments, the first complication is associated with a clock application from which the first and second time information are obtained. In some embodiments, user input directed at the first time information displayed at the corresponding location on the clock face launches an associated meditation or mindfulness application.

[0366] It should be noted that the details of the process (e.g., FIG. 13) described above with respect to method 1300 are also applicable in a similar manner to the above-described methods. For example, method 1300 optionally includes one or more of the characteristics of the various methods described above with reference to method 1100. For example, watch user interface 1200 of FIG. 12A can be configured to display three complications (e.g., complications 1008-1, 1008-2, and 1008-3 of FIG. 10A) that include at least two metrics in a manner similar to the technique described with reference to method 1100. For brevity, these details will not be repeated below.

[0367] 14A-14AE show exemplary watch user interfaces according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the methods in FIGS. 15A-15C.

[0368] FIG. 14A illustrates such a device 600. As shown in FIG. 14A, device 600 displays a clock user interface 1400 on display 602. Clock user interface 1400 includes a clock face 1402 surrounded by a bezel 1404. Clock face 1402 includes a time display with hour hand 1406-1, minute hand 1406-2, and second hand 1406-3. Bezel 1404 includes hour markings 1405 (e.g., regularly spaced graphic markings that provide visual references to assist a user of device 600 in quickly determining the time displayed on clock face 1402). Clock user interface 1400 further includes a date complication 1408-1, a music complication 1208-2, a timer complication 1208-3, and a world clock complication 1208-4. Date complication 1408-1 displays data (e.g., day of the week and date) from an associated date or calendar application. Music complication 1208-2, timer complication 1208-3, and world clock complication 1208-4, as described above, contain metrics related to data from the corresponding applications. In FIG. 14A , complications 1208-1, 1208-2, 1208-3, and 1208-4 occupy corresponding locations in the top, right, bottom, and left regions of clock face 1402. Clock user interface 1500 also includes corner complications 1212-1, 1212-2, 1212-3, and 1212-4, as described above.

[0369] As shown in FIG. 14A , device 600 receives (e.g., detects) user input 1490 (e.g., a long press on display 602) corresponding to a request to edit watch user interface 1400. In response to user input 1490, device 600 enters an edit mode (e.g., a clock face edit mode or a complication edit mode). In FIG. 14B , device 600 indicates the edit mode by visually highlighting date complication 1408-1 for editing (e.g., by displaying a box 1414 around date complication 1408-1 and a label 1416 identifying the associated application). In some embodiments, device 600 visually highlights the complication selected for editing (e.g., date complication 1408-1) by modifying one or more visual characteristics (e.g., brightness, opacity, color, contrast, hue, saturation, etc.) of watch user interface 1400, or portions thereof. In some embodiments, while in edit mode, a complication selected for editing is displayed in a first visual characteristic (e.g., a color or colors other than grayscale), and in some embodiments, one or more other complications (e.g., all other complications) are displayed in a second visual characteristic (e.g., grayscale or a single color that is different from the colors in which the complications would be displayed while the device is not in edit mode), even though some or all of the other complications would be displayed in one or more colors within the clock face when the clock face is not in edit mode. For example, complication 1408-1 is displayed in color, and complications 1208-2, 1208-3, and 1208-4 are displayed in grayscale. In some embodiments, while in edit mode, instead of or in addition to changing the visual characteristic of one or more selected complications, the visual characteristic of one or more unselected complications is changed (e.g., the brightness or opacity of one or more unselected complications is reduced to distinguish between selected and unselected complications).In some embodiments, the visual distinction of the selected complication is in place of or in addition to an alternative selection indicator, such as a selection ring around at least a portion of the selected complication. While in edit mode, device 600 also displays a complication menu bar 1418 having a complication position indicator 1420, which indicates the position of the currently displayed complication within a menu of complications available for selection. In some embodiments, user input 1490 includes a contact having a characteristic intensity, and device 600 enters edit mode pursuant to a determination that the characteristic intensity exceeds a predetermined threshold intensity.

[0370] 14C , device 600 receives (e.g., detects) user input 1492, which includes rotation of rotatable input mechanism 604. In some embodiments, user input 1492 is received on another device that communicates with device 600 (e.g., via a counterpart application associated with device 600 running on the other device). In response to receiving user input 1492, device 600 displays a representation of tachymeter complication 1408-2 in place of date complication 1408-1 and adds it to watch user interface 1400. In FIG. 14D , device 600 updates complication position indicator 1420 to indicate that tachymeter complication 1408-2 is located near the bottom of the complications menu (e.g., because complications are alphabetical and “t” is near the end of the alphabet). As shown in FIG. 14D, the representation of the tachymeter complication 1408-5 includes an indication of the type of information that the information tachymeter complication 1408-5 displays on the watch user interface 1400 when exiting edit mode (e.g., general units).

[0371] In some embodiments, while in edit mode, device 600 receives (e.g., detects) one or more inputs (e.g., taps on display 602 or presses on rotatable input mechanism 604) corresponding to a request to exit edit mode. In response to exiting edit mode, device 600 adds tachymeter complication 1408-2 to watch user interface 1400, replacing date complication 1408-1 in the top region of watch face 1402. As shown in FIG. 14E , tachymeter complication 1408-2 displays a unit display 1412 positioned on watch face 1402 closer to the center of display 602 than the inner edge of bezel 1404, without overlapping the area occupied by bezel 1204.

[0372] As shown in FIG. 14F , device 600 receives (e.g., detects) user input 1494 (e.g., a tap on display 602 within the area occupied by unit display 1412). In some embodiments, user input 1494 is detected by device 600 at a location on display 1402 that corresponds to bezel 1404. In response to user input 1494, device 600 updates watch user interface 1400. In FIG. 14G , watch user interface 1400 includes bezel 1404, with hour markings 1405 replaced with unit scale 1422 (e.g., a 60 unit per hour scale) and tachymeter hand 1424 added. In some embodiments, hour markings 1405 are replaced by unit scale 1422 in response to user input 1492 (selective rotation), and only tachymeter hand 1424 is added to watch user interface 1400 in response to user input 1494. In some embodiments, in response to user input 1492 (selection rotation), the hour markings 1405 are replaced by a unit scale 1422 and a tachymeter hand 1424 is added to the watch user interface 1400.

[0373] By automatically updating the interface in response to certain user interactions (e.g., after exiting edit mode), the user is provided with enhanced visual feedback by keeping the user interface free of clutter during selection. This allows the user to focus their attention on fewer visual elements, thereby enabling them to more quickly locate relevant information throughout the interface and more accurately interact with desired control features on the display. This improves device usability and makes the user-device interface more efficient (e.g., by helping the user more quickly locate, and more accurately, provide appropriate inputs when operating / interacting with the device and reducing user errors), which in turn reduces device power usage and improves battery life by allowing the user to use the device more quickly and efficiently.

[0374] As shown in FIG. 14H, device 600 receives (e.g., detects) user input 1496 (e.g., a tap indication corresponding to tachymeter hand 1424 or bezel 1404 having unit scale 1422). In response to receiving user input 1496, device 600 updates watch user interface 1400 (e.g., rotation of tachymeter hand 1424 is initiated and units display 1412 is updated corresponding to the location of tachymeter hand 1424 relative to units scale 1422). In FIG. 141, tachymeter hand 1424 has advanced to a location on bezel 1404 corresponding to 144 units, units display 1412 reflects the location of tachymeter hand 1424 (e.g., 144 units), and second hand 1406-3 indicates that 20 seconds have elapsed.

[0375] In some embodiments, while the tachymeter hand 1424 is advancing (e.g., rotating), the device 600 receives a subsequent user input (e.g., a tap on the user display). In response, the tachymeter hand 1424 and the units display 1412 stop updating (e.g., the tachymeter hand stops rotating and the units display value reflects the position of the tachymeter hand relative to the units scale 1422). In some embodiments, the subsequent user input (e.g., a tap or long press on the user display) resets the tachymeter complication (e.g., the bezel 1404, tachymeter hand 1424, and units display 1412 return to their respective states shown in FIG. 14G).

[0376] 14J, prior to user input 1496 (e.g., prior to initiating rotation of tachymeter hand 1424), device 600 receives (e.g., detects) user input 1498-1, which includes rotation of rotatable input mechanism 604. In response to receiving user input 1498-1, device 600 updates unit scale 1422 on bezel 1404. FIG. 14K shows the updated unit scale 1422 (e.g., selection of a 30 units per hour scale for the tachymeter function).

[0377] 14M, a process for updating watch user interface 1400 with diver complication 1408-3 is shown (e.g., after selecting the diver complication from edit mode, device 600 displays a representation of diver complication 1408-3 and adds it to watch user interface 1400, and upon exiting edit mode, device 600 adds diver complication 1408-3 to watch user interface 1400, replacing the complication in the top region of watch face 1402). As shown in FIG. 14M, extended complication 1408-3 includes a minute indicator 1426 positioned on watch face 1402 closer to the center of display 602 than the inner edge of bezel 1404, without overlapping the area occupied by bezel 1204.

[0378] In FIG. 14M, device 600 receives (e.g., detects) user input 1491 (e.g., a tap on display 602 in the area occupied by minute display 1426). In some embodiments, user input 1491 is detected by device 600 at a location on display 1402 that corresponds to bezel 1404. In response to user input 1491, device 600 updates watch user interface 1400. In FIG. 14N, updated watch user interface 1400 includes bezel 1404, with hour markings 1405 replaced by diver scale 1430 (e.g., numbers around the bezel corresponding to minutes), and bezel markers 1428 added to bezel 1404 (e.g., at the top of the bezel).

[0379] 14N-14P, device 600 receives (e.g., detects) user input 1493, which includes rotation of rotatable input mechanism 604. In response to user input 1493, device 600 updates watch user interface 1400 by updating (e.g., rotating) the position of bezel 1404. Bezel 1404 moves clockwise in response to user input 1493, as illustrated by the advancement of bezel marker 1428 to a position aligned with minute hand 1206-2 in FIG. 14P. In other embodiments, bezel 1404 advances counterclockwise in response to user input 1493.

[0380] Figure 14Q shows the watch user interface 1400 at some time after completion of user input 1493. The minute display 1426 shows the offset between the bezel 1404 and the minute hand 1206-2 (e.g., 18 minutes have passed since the bezel was aligned with the minute hand), and the display of the time has been updated (e.g., hand 1206-2 and world clock complication 1208-4 are updated to correspond to the change in time between Figures 14P and 14Q).

[0381] Referring now to FIG. 14R, a process for updating the watch user interface 1400 with the GMT complication 1408-4 is shown (e.g., after selecting the GMT complication from edit mode, the device 600 displays a representation of the GMT complication 1408-4 and adds it to the watch user interface 1400, and upon exiting edit mode, the device 600 adds the GMT complication 1408-4 to the watch user interface 1400, replacing the complication in the top region of the watch face 1402). As shown in FIG. 14R, the GMT complication 1408-4 includes an offset display 1432 (e.g., representing the time zone for display by the GMT hand relative to GMT time) positioned on the watch face 1402 closer to the center of the display 602 than the inner edge of the bezel 1404 (e.g., without overlapping with the area occupied by the bezel 1204), a GMT scale 1436 (e.g., a 24-hour scale) on the bezel 1404, and a GMT hand 1434 (e.g., a hand positioned relative to the GMT scale 1436 to indicate the time in the time zone based on the displayed offset).

[0382] 14R-14T, device 600 receives (e.g., detects) user input 1495, including rotation of rotatable input mechanism 604. In response to user input 1495, device 600 updates watch user interface 1400 by incrementing the time offset (e.g., +0 hours to +1 hour to +3 hours) displayed on offset display 1432 and updating the position of GMT hand 1434 relative to GMT scale 1436 (e.g., GMT hand 1434 rotates around the bezel to reflect the change in offset).

[0383] 14A-14D, the user can request to add a compact complication consisting of a single graphical element (e.g., a complication without associated bezel content, such as training complication 1208-1) in place of GMT complication 1408-4 by selecting complication 1408-4 in edit mode (e.g., by tapping) and then moving rotatable input mechanism 604 to select new complication 1208-1. FIG. 14U shows the watch user interface 1400 after exiting edit mode (e.g., with GMT hand 1434 removed, offset indication 1432 replaced by training complication 1208-1, and GMT scale 1436 replaced by hour markings 1405 on bezel 1404).

[0384] 14V-14AE, various features associated with rotatable input mechanism 604 will now be described.

[0385] 14V , device 600 displays mail application interface 1400-2 on display 602. Mail application interface 1400-2 includes an application header 1438 (e.g., an application label and a time indication) and a content display area 1440. Content display area 1440 includes a subject line 1442 and message content 1444. As shown in FIGS. 14V and 14W , device 600 receives (e.g., detects) user input 1497, including rotation of rotatable input mechanism 604. In response to user input 1497, device 600 updates mail application interface 1400-2 by translating (e.g., scrolling) subject line 1442 and message content 1444 from a first position on display 602 to a second position on display 602. 14W, the subject line 1442 and / or message content 1444 are scrolled to a position outside of the content display area 1440 and, as a result, are not displayed on the display 602. In some embodiments, the direction of the user input 1497 corresponds to the direction of translation of the message content 1444 on the display 602.

[0386] In FIG. 14X, the device 600 displays an application selection interface 1400-3 on the display 602. The application selection interface 1400-3 includes a vertical list of application icons, including an activity icon 1446-1, an alarm icon 1446-2, a breathing icon 1446-3, and a camera icon 1446-3 (collectively, "application icons 1446"). As shown in FIGS. 14X and 14V, the device 600 receives (e.g., detects) a user input 1497 including a rotation of the rotatable input mechanism 604. In response to the user input 1497, the device 600 updates the application selection interface 1400-3 by translating the application icons 1446 from a first position on the display 602 to a second position on the display 602. As shown in FIG. 14W, one or more of the application icons 1446 scroll to a position outside of the display 602 and, as a result, are not displayed on the display 602. In some embodiments, the direction of the user input corresponds to the translation direction of the application icon 1446 on the display 602 .

[0387] In Figure 14Z, display 602 of device 600 is off (e.g., the screen is not displaying content or emitting light). As shown in Figure 14Z, device 600 receives (e.g., detects) user input 1497 including rotation of rotatable input mechanism 604. In Figure 14AA, in response to user input 1497, device 600 turns on display 602 (e.g., the screen displays a clock user interface 1400-4 including a clock face with time markings, a time display, and a date display).

[0388] FIG. 14AB shows device 600 displaying a clock user interface 1400-5 including a clock face 1402, a time display (hour hand 1406-1, minute hand 1406-2, and second hand 1406-3) (e.g., 10:40:35), and a next appointment indicator 1452 (e.g., indicating that the user's next appointment for the displayed time on clock face 1402 is lunch at 12:00 PM). As shown in FIG. 14AB, device 600 receives (e.g., detects) a user input 1497-1 including a rotation of rotatable input mechanism 604. In response to receiving user input 1497-1, device 600 updates clock user interface 1400-5 (e.g., advances the displayed time display proportionally to input 1497-1). FIG. 14AC shows the updated clock user interface 1400-5. The clock user interface 1400-5 includes a time offset label 1454 (e.g., +2:21 hours elapsed), a display of the time (e.g., hour hand 1406-1, minute hand 1406-2, and second hand 1406-3) (e.g., showing 1:55), and a next appointment indicator 1452 (e.g., 3:00 PM, meeting).

[0389] 14AD, device 600 displays application selection interface 1400-6 on display 602. Application selection interface 1400-6 includes a collection of application icons, including an alarm icon 1456-1, a weather icon 1456-2, a message icon 1456-3, a clock icon 1456-4, an activity icon 1456-5, a to do icon 1456-6, a heart rate icon 1456-7, and a calendar icon 1456-8 (collectively "application icons 1456"). As shown in FIG. 14AD, device 600 receives (e.g., detects) user input 1497-1, which includes rotation of rotatable input mechanism 604. In response to user input 1497-1, device 600 updates application selection interface 1400-6 by launching the application corresponding to the application icon displayed closest to the center of display 602 (e.g., the alarm icon). 14AE shows an alarm application interface 1400-7 associated with an alarm application displayed on display 602. The alarm application interface 1400-7 includes an application label 1460 (e.g., Alarm), a display of the time (e.g., 10:09), an alarm display 1458-1 (e.g., the time, a label, and an on / off switch), and an alarm generation affordance 1458-2.

[0390] 15A-15C are flow diagrams illustrating a method for providing a context-specific user interface using an electronic device, according to some embodiments. Method 1500 is performed on a device (e.g., 100, 300, 500, 600) that includes a display and one or more input devices. Some operations of method 1500 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0391] In block 1502, a device (e.g., 600) displays on a display (e.g., 602) a watch user interface (e.g., 1400) including a clock face (e.g., 1402), a user interface element (e.g., 1404) that partially surrounds the clock face (e.g., a clock face bezel), and a complication (e.g., 1408-1). In some embodiments, a complication refers to any feature of the clock face other than those used to indicate the hours and minutes of a time (e.g., clock hands or hour / minute displays). In some embodiments, a complication includes an affordance that, when selected, launches a corresponding application (e.g., 1408-1, 1208-2, 1208-3, 1208-4). In some embodiments, a complication (e.g., 1408-1, 1208-2, 1208-3, 1208-4) provides data obtained from the application. In some embodiments, complications are displayed in fixed, pre-defined locations on the display (e.g., 1408-1, 1208-2, 1208-3, and 1208-4). In some embodiments, complications (e.g., 1408-1, 1208-2, 1208-3, 1208-4) are displayed within the clock face (e.g., entirely within the clock face). In some embodiments, complications (e.g., 1212-1, 1212-2, 1212-3, and 1212-4) are displayed between the user interface element and the edge of the display.

[0392] By presenting information to fit the space available on the watch face, the user interface is kept clutter-free, providing augmented visual feedback to the user. This allows the user to focus their attention on fewer visual elements, thereby enabling them to more quickly locate relevant information throughout the interface and more accurately interact with desired control features on the display. This improves device usability and makes the user-devic...

Claims

1. In an electronic device having a display, displaying a clock user interface on the display, the clock user interface comprising: a first graphical object at a first location in a sequence of locations on the display; a second graphical object at a last location in the sequence of locations on the display; and and While displaying the clock user interface on the display, Detecting a first user input; in response to detecting a first user input; ceasing to display the first graphical object at the first location in the defined sequence of locations on the display; ceasing to display the second graphical object at the last location in the defined sequence of locations on the display; and displaying the second graphical object at the first location in the sequence of locations on the display; displaying the first graphical object at a second location in the sequence of locations on the display; A method comprising:

2. The method of claim 1 , wherein the first graphical object comprises a time display.

3. The method of claim 1 or 2, wherein the clock user interface further comprises a display of the time that is displayed in the same position before and after the first input.

4. 4. The method of claim 1, wherein the clock face is offset from the center of the display.

5. The method of claim 1 , wherein at least one of the first and second graphical objects displays data from an application.

6. 6. The method of claim 1, wherein the first graphical object has a first size while displayed at the first location, and the first graphical object has a second size while displayed at the second location, the first size being different from the second size.

7. the first graphical object, while displayed at the first location, includes first information; the first graphical object, while displayed at the second location, includes second information that is different from the first information; 7. The method according to any one of claims 1 to 6.

8. displaying the first graphical object at the first location in the defined sequence of locations on the display and ceasing to display the first graphical object at the second location in the sequence of locations on the display includes displaying an animation of the first graphical object moving from the first location towards the second location; 8. The method of claim 1, wherein displaying the second graphical object at the last location in the defined sequence of locations on the display and ceasing to display the second graphical object at the first location in the sequence of locations on the display includes displaying an animation of the second graphical object moving from the last location towards the first location.

9. The method of claim 1 , wherein the first location and the second location are fixed on the display relative to a physical frame of the device.

10. the first user input having a first direction, and the method further comprising: Detecting a second user input having a second direction opposite the first direction; In response to detecting the second user input, ceasing to display the first graphical object at the second location within the defined sequence of locations on the display; and ceasing to display the second graphical object at the first location in the defined sequence of locations on the display; and displaying the second graphical object at the last location in the sequence of locations on the display; displaying the first graphical object at a first location in the sequence of locations on the display; 10. The method of claim 1, further comprising:

11. The method of claim 1 , wherein the electronic device has a rotatable input mechanism, and the first user input comprises rotating the rotatable input mechanism.

12. The method of claim 1 , wherein the first user input is a swipe gesture detected on the display.

13. 13. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display, the one or more programs including instructions for performing the method of any one of claims 1 to 12.

14. The display and one or more processors; a memory storing one or more programs configured to be executed by the one or more processors; 13. An electronic device comprising:

15. The display and means for carrying out the method according to any one of claims 1 to 12; An electronic device comprising:

16. 1. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display, the one or more programs comprising: instructions for displaying a clock user interface on the display, the clock user interface comprising: a first graphical object at a first location in a sequence of locations on the display; a second graphical object at a last location in the sequence of locations on the display; and an instruction, While displaying the clock user interface on the display, instructions for detecting a first user input; in response to detecting a first user input; instructions for ceasing displaying the first graphical object at the first location within the defined sequence of locations on the display; instructions for ceasing to display the second graphical object at the last location in the defined sequence of locations on the display; instructions for displaying the second graphical object at the first location in the sequence of locations on the display; instructions for displaying the first graphical object at a second location in the sequence of locations on the display; 1. A non-transitory computer-readable storage medium comprising:

17. The display and one or more processors; a memory storing one or more programs configured to be executed by the one or more processors; an electronic device comprising: instructions for displaying a clock user interface on the display, the clock user interface comprising: a first graphical object at a first location in a sequence of locations on the display; a second graphical object at a last location in the sequence of locations on the display; and While displaying the clock user interface on the display, instructions for detecting a first user input; in response to detecting a first user input; instructions for ceasing displaying the first graphical object at the first location within the defined sequence of locations on the display; instructions for ceasing to display the second graphical object at the last location in the defined sequence of locations on the display; instructions for displaying the second graphical object at the first location in the sequence of locations on the display; instructions for displaying the first graphical object at a second location in the sequence of locations on the display; , an electronic device.

18. The display and means for displaying a clock user interface on the display, the clock user interface comprising: a first graphical object at a first location in a sequence of locations on the display; a second graphical object at a last location in the sequence of locations on the display; While displaying the clock user interface on the display, means for detecting a first user input; in response to detecting a first user input; means for ceasing displaying the first graphical object at the first location in the defined sequence of locations on the display; means for ceasing to display the second graphical object at the last location in the defined sequence of locations on the display; means for displaying the second graphical object at the first location in the sequence of locations on the display; means for displaying the first graphical object at a second location in the sequence of locations on the display; An electronic device comprising:

19. In an electronic device having a display, displaying a clock user interface on the display at a first time, the clock user interface at the first time comprising: a first clock hand in a first position superimposed on a background, the background including the first clock hand in the first position having a first graphical characteristic at the first time determined based on the first position of the first clock hand; displaying the clock user interface on the display at a second time after the first time, the clock user interface at the second time comprising: a first clock hand in a second position superimposed on the background, the background including the first clock hand in the second position having a second graphical characteristic at the second time determined based on the second position of the first clock hand; A method comprising:

20. 20. The method of claim 19, wherein the first clock hand is one of an hour hand, a minute hand, or a second hand.

21. the clock user interface is configured to display one or more characteristics of the background according to positions of hands of the first clock at the first time and the second time, and the method further comprises: after displaying the clock user interface on the display at the second time, receiving a sequence of one or more user inputs corresponding to a request to display the one or more characteristics of the background according to a position of a second clock hand that is different from a hand of the first clock; after receiving the sequence of one or more user inputs; displaying the clock user interface on the display at a third time, the clock user interface at the third time comprising: a second clock hand in a third position superimposed on the background, the background including a second clock hand in a third position having a third graphical characteristic at the third time determined based on the third position of the second clock hand; displaying the clock user interface on the display at a fourth time after the third time, the clock user interface at the fourth time comprising: a second clock hand in a fourth position superimposed on the background, the background including the second clock hand in a fourth position having a fourth graphical characteristic at the fourth time determined based on the fourth position of the second clock hand; 21. The method of any one of claims 19 to 20, further comprising:

22. 22. The method of claim 21, wherein the hands of the second clock have a rate of movement that is different from the rate of movement of the hands of the first clock.

23. 23. The method of claim 21 or 22, wherein the second clock hand is one of an hour hand, a minute hand, or a second hand.

24. 24. The method of claim 19, wherein a difference between the first graphical characteristic at a first time and the second graphical characteristic at a second time corresponds to a rotation of the background relative to a physical frame of the device.

25. displaying the clock user interface on the display at the first time further includes displaying a graphical element at a fifth position; and displaying the clock user interface on the display at the second time further comprises displaying the graphical element at the fifth position.

25. The method of any one of claims 19 to 24.

26. 25. The method of claim 24, wherein the first clock hand and the background rotate about a common origin.

27. 27. The method of any one of claims 19 to 26, wherein the background extends to the edges of the display.

28. 28. The method of any one of claims 19 to 27, wherein the background comprises a first portion occupying a first half of the display and a second portion occupying a second half of the display.

29. 30. The method of claim 28, wherein the first portion comprises a first color or visual pattern and the second portion comprises a second color or visual pattern that is different from the first color or visual pattern.

30. 30. The method of claim 28 or 29, wherein the shape of the first portion at the first time is different from the shape of the first portion at the second time.

31. 31. The method of any one of claims 28 to 30, wherein the boundary between the first portion and the second portion is a straight line.

32. 32. The method of claim 31 , wherein the boundary is along the hands of the first clock.

33. 33. The method of any one of claims 19 to 32, wherein the first graphical characteristic at the first time includes a visual representation of the hour at the first time, and the second graphical characteristic at the second time includes a visual representation of the hour at the second time.

34. 34. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display, the one or more programs including instructions for performing the method of any one of claims 19 to 33.

35. The display and one or more processors; a memory storing one or more programs configured to be executed by the one or more processors; 34. An electronic device comprising: said one or more programs comprising instructions for carrying out the method of any one of claims 19 to 33.

36. The display and means for carrying out the method of any one of claims 19 to 33; An electronic device comprising:

37. 1. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display, the one or more programs comprising: instructions for displaying a clock user interface on the display at the first time, the clock user interface at the first time comprising: instructions including a first clock hand in a first position superimposed on a background, the background having a first graphical characteristic at the first time determined based on the first position of the first clock hand; instructions for displaying the clock user interface on the display at a second time after the first time, the clock user interface at the second time comprising: instructions including a first clock hand in a second position superimposed on the background, the background having a second graphical characteristic at the second time determined based on the second position of the first clock hand; 1. A non-transitory computer-readable storage medium comprising:

38. The display and one or more processors; a memory storing one or more programs configured to be executed by the one or more processors; 10. An electronic device comprising: instructions for displaying a clock user interface on the display at the first time, the clock user interface at the first time comprising: instructions including a first clock hand in a first position superimposed on a background, the background having a first graphical characteristic at the first time determined based on the first position of the first clock hand; instructions for displaying the clock user interface on the display at a second time after the first time, the clock user interface at the second time comprising: instructions including a first clock hand in a second position superimposed on the background, the background having a second graphical characteristic at the second time determined based on the second position of the first clock hand; , an electronic device.

39. The display and means for displaying a clock user interface on the display at a first time, the clock user interface at the first time comprising: a first clock hand in a first position superimposed on a background, the background including the first clock hand in the first position having a first graphical characteristic at the first time determined based on the first position of the first clock hand; means for displaying the clock user interface on the display at a second time after the first time, the clock user interface at the second time comprising: a means for displaying the first clock hand in a second position superimposed on the background, the background including the first clock hand in a second position having a second graphical characteristic at the second time determined based on the second position of the first clock hand; , an electronic device.

40. In an electronic device having a display, displaying a clock user interface on the display, the clock user interface comprising: a first complication including at least a first metric associated with data from a first application and a second metric associated with data from the first application; a second complication including at least a third metric associated with data from a second application and a fourth metric associated with data from the second application; a third complication including at least a fifth metric associated with data from a third application and a sixth metric associated with data from the third application; and detecting a sequence of one or more inputs corresponding to a request to add a fourth complication to the watch user interface, the fourth complication including at least a seventh metric associated with data from a fourth application and an eighth metric associated with data from the fourth application; in response to detecting a sequence of the one or more inputs; replacing the first complication with the fourth complication in accordance with determining that the sequence of one or more inputs corresponds to a request to replace the first complication; and replacing the second complication with the fourth complication in accordance with determining that the sequence of one or more inputs corresponds to a request to replace the second complication; and replacing the third complication with the fourth complication in accordance with determining that the sequence of one or more inputs corresponds to a request to replace the third complication; and A method comprising:

41. in response to detecting a sequence of the one or more inputs; maintaining the second complication and the third complication in accordance with a determination that the sequence of one or more inputs corresponds to a request to replace the first complication; maintaining the first complication and the third complication in accordance with a determination that the sequence of one or more inputs corresponds to a request to replace the second complication; maintaining the first complication and the second complication in accordance with a determination that the sequence of one or more inputs corresponds to a request to replace the third complication; 41. The method of claim 40, further comprising:

42. the first complication further includes a ninth metric related to data from the first application; the second complication further includes a tenth metric related to data from the second application; each of the third complications further includes an eleventh metric related to data from the third application; 42. The method of claim 40 or 41.

43. 43. The method of any one of claims 40 to 42, wherein the first application, the second application, and the third application are the same application.

44. 43. The method of any one of claims 40 to 42, wherein the first application is different from the second application, and the third application is different from the first application and the second application.

45. The clock user interface further comprises a ring-shaped region having a curved outer edge, and the method further comprises: displaying a visual characteristic at or around the ring-shaped region in accordance with the first application corresponding to a fifth application; ceasing to display the visual characteristic on or around the ring-shaped region in accordance with the first application corresponding to a sixth application different from the fifth application; 45. The method of any one of claims 40 to 44, further comprising:

46. the clock user interface: a ring-shaped region having a curved outer edge and corner complications; a status bar that follows the outer edge of the ring-shaped region; a value located between the status bar and a corner of the display; 46. ​​The method of any one of claims 40 to 45, further comprising:

47. 47. The method of any one of claims 40 to 46, wherein the first complication includes an analog clock face having one or more hands indicating the time at a geographic location and letters indicating the geographic location, the letters indicating the geographic location being positioned on the complication based on the position of the one or more hands.

48. 48. The method of any one of claims 40 to 47, further comprising displaying a second clock user interface, the second clock user interface including a fifth complication including fewer than two metrics related to data from the first application, the fifth complication being the same size as the first complication.

49. 49. The method of claim 48, wherein the fifth complication does not include metrics related to data from the first application.

50. 49. The method of claim 48, wherein the fifth complication has a lower resolution than the first complication on the watch user interface.

51. the clock user interface is a first clock user interface, the first application, the second application, and the third application are the same application, and the method further comprises: detecting a sequence of one or more inputs corresponding to a selection of a second watch user interface while displaying the first watch user interface; and displaying the second watch user interface in response to detecting the sequence of the one or more inputs corresponding to a selection of the second watch user interface, the second watch user interface comprising: an eighth complication corresponding to a seventh application; a ninth complication corresponding to the seventh application; and a tenth complication corresponding to the seventh application; and Including, the seventh application is different from the first application; and 49. The method of claim 48, further comprising:

52. 52. The method of any one of claims 40 to 51, wherein the watch user interface further comprises a watch face having a curved outer edge and a curved complication having visual features along the outer edge of the watch face.

53. 53. The method of any one of claims 40 to 52, wherein the first metric and the second metric relate to data from a clock application, the first metric representing a geographic location and the second metric representing a time associated with the geographic location.

54. 53. The method of any one of claims 40 to 52, wherein the first metric and the second metric relate to data from a calendar or date application, the first metric representing an event and the second metric representing a time associated with the event.

55. 53. The method of any one of claims 40 to 52, wherein the first metric and the second metric relate to data from a stock application, the first metric representing a stock name and the second metric representing an associated stock price.

56. 53. The method of any one of claims 40 to 52, wherein the first metric and the second metric relate to data from a weather application, the first metric representing a current temperature and the second metric representing a forecasted maximum and minimum temperature.

57. 57. The method of any one of claims 40 to 56, wherein the first complication includes a visual representation of one or more metrics, the visual representation including an indication of a value against a range of values.

58. the first complication includes a visual representation of one or more metrics, the visual representation including a first affordance representing a simulation of a first region of the Earth illuminated by the sun at a current time, the method comprising: detecting a sequence of one or more user inputs corresponding to a request to view the simulation of Earth at a non-current time; In response to detecting the sequence of one or more user inputs corresponding to a request to view the simulation of Earth at a non-current time, rotating the simulation of Earth to present a second region of Earth illuminated by the sun at the non-current time; 57. The method of any one of claims 40 to 56, further comprising:

59. 59. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display, the one or more programs including instructions for performing the method of any one of claims 40 to 58.

60. The display and one or more processors; a memory storing one or more programs configured to be executed by the one or more processors; 59. An electronic device comprising: said one or more programs comprising instructions for carrying out the method of any one of claims 40 to 58.

61. The display and means for carrying out the method of any one of claims 40 to 58; An electronic device comprising:

62. 1. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display, the one or more programs comprising: instructions for displaying a clock user interface on the display, the clock user interface comprising: a first complication including at least a first metric associated with data from a first application and a second metric associated with data from the first application; a second complication including at least a third metric associated with data from a second application and a fourth metric associated with data from the second application; a third complication including at least a fifth metric associated with data from a third application and a sixth metric associated with data from the third application; instructions, instructions for detecting a sequence of one or more inputs corresponding to a request to add a fourth complication to the watch user interface, the fourth complication including at least a seventh metric associated with data from a fourth application and an eighth metric associated with data from the fourth application; in response to detecting a sequence of the one or more inputs; instructions for replacing the first complication with the fourth complication in accordance with a determination that the sequence of one or more inputs corresponds to a request to replace the first complication; instructions for replacing the second complication with the fourth complication in accordance with a determination that the sequence of one or more inputs corresponds to a request to replace the second complication; and instructions for replacing the third complication with the fourth complication in accordance with a determination that the sequence of one or more inputs corresponds to a request to replace the third complication; 1. A non-transitory computer-readable storage medium comprising:

63. The display and one or more processors; a memory storing one or more programs configured to be executed by the one or more processors; an electronic device comprising: instructions for displaying a clock user interface on the display, the clock user interface comprising: a first complication including at least a first metric associated with data from a first application and a second metric associated with data from the first application; a second complication including at least a third metric associated with data from a second application and a fourth metric associated with data from the second application; a third complication including at least a fifth metric associated with data from a third application and a sixth metric associated with data from the third application; instructions, instructions for detecting a sequence of one or more inputs corresponding to a request to add a fourth complication to the watch user interface, the fourth complication including at least a seventh metric associated with data from a fourth application and an eighth metric associated with data from the fourth application; in response to detecting a sequence of the one or more inputs; instructions for replacing the first complication with the fourth complication in accordance with a determination that the sequence of one or more inputs corresponds to a request to replace the first complication; instructions for replacing the second complication with the fourth complication in accordance with a determination that the sequence of one or more inputs corresponds to a request to replace the second complication; and instructions for replacing the third complication with the fourth complication in accordance with a determination that the sequence of one or more inputs corresponds to a request to replace the third complication; , an electronic device.

64. The display and means for displaying a clock user interface on the display, the clock user interface comprising: a first complication including at least a first metric associated with data from a first application and a second metric associated with data from the first application; a second complication including at least a third metric associated with data from a second application and a fourth metric associated with data from the second application; a third complication including at least a fifth metric associated with data from a third application and a sixth metric associated with data from the third application; means for detecting a sequence of one or more inputs corresponding to a request to add a fourth complication to the watch user interface, the fourth complication including at least a seventh metric associated with data from a fourth application and an eighth metric associated with data from the fourth application; in response to detecting a sequence of the one or more inputs; means for replacing the first complication with the fourth complication in accordance with a determination that the sequence of the one or more inputs corresponds to a request to replace the first complication; means for replacing the second complication with the fourth complication in accordance with a determination that the sequence of the one or more inputs corresponds to a request to replace the second complication; means for replacing the third complication with the fourth complication in accordance with a determination that the sequence of the one or more inputs corresponds to a request to replace the third complication; An electronic device comprising:

65. In an electronic device having a display and one or more input devices, displaying a clock user interface on the display, the clock user interface comprising: The clock face and a user interface element at least partially surrounding the watch face; and and receiving a request via the one or more input devices to add a corresponding complication to a corresponding location on the watch face; in response to receiving a request to add the corresponding complication to the corresponding location on the watch face; pursuant to determining that the corresponding complication is a first complication, displaying the first complication on the display at the corresponding location on the watch face and replacing at least a portion of the user interface element with content associated with the first complication; pursuant to determining that the corresponding complication is a second complication, displaying the second complication on the display at the corresponding location on the watch face without replacing the portion of the user interface element with content associated with the second complication; and A method comprising:

66. 66. The method of claim 65, wherein the content associated with the first complication includes first content, the first complication includes second content displayed at the corresponding location on the watch face, and the second content is associated with the first complication.

67. 67. The method of claim 66, wherein the first content represents data from an application and the second content represents data from the application that is different from the first content.

68. 68. The method of any one of claims 66 to 67, wherein the first content includes textual information associated with the first complication.

69. 69. The method of any one of claims 65 to 68, wherein the second complication consists of a single graphical element.

70. 70. The method of any one of claims 65 to 69, wherein the corresponding location is contained entirely within the clock face.

71. receiving an input corresponding to a location on the display while displaying the content associated with the first complication on the portion of the user interface element; in response to receiving the input corresponding to a location on the display; launching an application associated with the first complication according to the input corresponding to a location of the portion of the user interface element; canceling the launch of an application associated with a first complication according to an input corresponding to a location on the user interface element other than the portion of the user interface element; 71. The method of any one of claims 65 to 70, further comprising:

72. 72. The method of any one of claims 65 to 71, wherein a size of the portion of the user interface element is based on the content associated with a first complication.

73. 73. The method of any one of claims 65 to 72, wherein the first complication includes date information displayed in the corresponding location on the clock face, and the content associated with the first complication displayed in the portion of the user interface element includes information from a reservation.

74. 73. The method of any one of claims 65 to 72, wherein the first complication includes first weather information displayed in the corresponding location on the watch face, and the content associated with the first complication displayed in the portion of the user interface element includes second weather information that is different from the first weather information.

75. 73. The method of any one of claims 65 to 72, wherein the first complication includes first athletic information displayed in the corresponding location on the watch face, and the content associated with the first complication displayed in the portion of the user interface element includes second athletic information different from the first athletic information.

76. 73. The method of any one of claims 65 to 72, wherein the first complication includes an affordance displayed at the corresponding location on the watch face, and the content associated with the first complication displayed on the portion of the user interface element includes heart rate information.

77. 73. The method of any one of claims 65 to 72, wherein the first complication includes an affordance displayed at the corresponding location on the watch face, and the content associated with the first complication is displayed in the portion of the user interface and includes meditation or mindfulness information.

78. 73. The method of any one of claims 65 to 72, wherein the first complication includes first time information displayed at the corresponding location on the watch face, and the content associated with the first complication displayed in the portion of the user interface element includes second time information different from the first time information.

79. 80. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display and one or more input devices, the one or more programs comprising instructions for performing the method of any one of claims 65 to 78.

80. The display and one or more input devices; one or more processors; a memory storing one or more programs configured to be executed by the one or more processors; 79. An electronic device comprising: said one or more programs comprising instructions for carrying out the method of any one of claims 65 to 78.

81. The display and one or more input devices; means for carrying out the method of any one of claims 65 to 78; An electronic device comprising:

82. 1. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display and one or more input devices, the one or more programs comprising: instructions for displaying a clock user interface on the display, the clock user interface comprising: The clock face and a user interface element at least partially surrounding the watch face; and an instruction, instructions for receiving, via the one or more input devices, a request to add a corresponding complication to a corresponding location on the watch face; In response to receiving the request to add the corresponding complication to the corresponding location on the watch face, instructions for displaying, on the display, the first complication at the corresponding location on the watch face and replacing at least a portion of the user interface element with content associated with the first complication pursuant to determining that the corresponding complication is a first complication; and instructions for displaying the second complication on the display at the corresponding location on the watch face without replacing the portion of the user interface element with content associated with the second complication pursuant to a determination that the corresponding complication is a second complication; and 1. A non-transitory computer-readable storage medium comprising:

83. The display and one or more input devices; one or more processors; a memory storing one or more programs configured to be executed by the one or more processors; an electronic device comprising: instructions for displaying a clock user interface on the display, the clock user interface comprising: The clock face and a user interface element at least partially surrounding the watch face; and an instruction, instructions for receiving, via the one or more input devices, a request to add a corresponding complication to a corresponding location on the watch face; In response to receiving the request to add the corresponding complication to the corresponding location on the watch face, instructions for displaying, on the display, the first complication at the corresponding location on the watch face and replacing at least a portion of the user interface element with content associated with the first complication pursuant to determining that the corresponding complication is a first complication; and instructions for displaying, on the display, the second complication at the corresponding location on the watch face without replacing the portion of the user interface element with content associated with the second complication pursuant to a determination that the corresponding complication is a second complication; and , an electronic device.

84. The display and one or more input devices; means for displaying a clock user interface on the display, the clock user interface comprising: The clock face and a user interface element at least partially surrounding the watch face; and means for receiving, via the one or more input devices, a request to add a corresponding complication to a corresponding location on the watch face; In response to receiving the request to add the corresponding complication to the corresponding location on the watch face, means for displaying the first complication on the display at the corresponding location on the watch face and replacing at least a portion of the user interface element with content associated with the first complication in accordance with determining that the corresponding complication is a first complication; means for displaying the second complication on the display at the corresponding location on the watch face without replacing the portion of the user interface element with content associated with the second complication pursuant to determining that the corresponding complication is a second complication; and An electronic device comprising:

85. In an electronic device having a display and one or more input devices, displaying a clock user interface on the display, the clock user interface comprising: The clock face and a user interface element at least partially surrounding the watch face; and complication, detecting inputs directed at the user interface elements via the one or more input devices while displaying the clock user interface; and in response to detecting the input directed at the user interface element, updating, on the display, an appearance of the user interface element based on the input while maintaining the display of the watch face and the complication on the display.

86. displaying the clock user interface, in response to determining that the complication is a first type of complication, the user interface element includes a first visual characteristic corresponding to the first complication; 86. The method of claim 85, wherein, in accordance with a determination that the complication is not the first type of complication, the user interface element includes a second visual characteristic that is different from the first visual characteristic, the second visual characteristic being independent of the complication.

87. 87. The method of any one of claims 85 to 86, wherein the complication is displayed within the watch face.

88. 88. The method of any one of claims 85 to 87, wherein the complication is displayed between the user interface element and an edge of the display.

89. the complication is a first complication, and the method comprises: receiving a request via the one or more input devices to change the first complication to a second complication; in response to detecting a request to change the first complication to a second complication; replacing the first complication with the second complication; updating, on the display, the appearance of the user interface element based on the second complication; 89. The method of any one of claims 85 to 88, further comprising:

90. the complication is a first complication, and the method comprises: receiving a request via the one or more input devices to change the first complication to a second complication different from the first complication; In response to detecting the request to change the first complication to the second complication, replacing the first complication with the second complication; maintaining the appearance of the user interface element; 90. The method of any one of claims 85 to 89, further comprising:

91. the user interface element includes a scale indicating common units per predetermined time unit; the clock face includes a rotating hand that indicates a position on the scale; 91. The method of any one of claims 86 to 90, wherein the complication includes unit information corresponding to the position on the scale indicated by the rotating hand.

92. detecting a first input corresponding to a selection of the complication; In response to the detection of the first input, starting the rotary hand and updating the unit information; detecting a second input corresponding to a selection of the complication, the second input being detected after the first input; and Stopping or resetting the rotating hand and the unit information in response to detection of the second input; 92. The method of claim 91, further comprising:

93. the complication is a first complication located at a first location on the watch user interface, the watch user interface further comprising a second complication, different from the first complication, located at a second location on the watch user interface that is different from the first location, the method comprising: Detecting a first input corresponding to a selection of the second complication; In response to detecting the first input, launching an application corresponding to the second complication; 93. The method of any one of claims 85 to 92, further comprising:

94. 94. The method of any one of claims 85 to 93, wherein the input directed to the user interface element comprises a tap gesture at a location on the display corresponding to the user interface element.

95. 95. The method of any one of claims 85 to 94, wherein the one or more input devices include a rotatable input mechanism, and the input directed to the user interface element includes rotation of the rotatable input mechanism.

96. wherein the one or more input devices include a rotatable input mechanism, and the method further comprises: detecting rotation of the rotatable input mechanism while displaying the clock face on the display; adjusting the complication in response to detecting the rotation of the rotatable input mechanism; 96. The method of any one of claims 85 to 95, further comprising:

97. wherein the one or more input devices include a rotatable input mechanism, and the method further comprises: Displaying content on the display that is different from the watch user interface; detecting rotation of the rotatable input mechanism while displaying the content different from the watch user interface; scrolling the content on the display in response to detecting the rotation of the rotatable input mechanism; 97. The method of any one of claims 85 to 96, further comprising:

98. wherein the one or more input devices include a rotatable input mechanism, and the method further comprises: displaying a plurality of application affordances on the display; Detecting rotation of the rotatable input mechanism while displaying the plurality of application affordances; In response to detecting the rotation of the rotatable input mechanism, launching an application associated with a first application affordance of the plurality of application affordances; 98. The method of any one of claims 85 to 97, further comprising:

99. wherein the one or more input devices include a rotatable input mechanism, and the method further comprises: detecting rotation of the rotatable input mechanism while the display is off; turning on the display in response to detecting the rotation of the rotatable input mechanism while the display is off; 99. The method of any one of claims 85 to 98, further comprising:

100. the user interface element includes a rotatable scale; the complication includes a value indicating a position of a hand on the watch face relative to the rotatable scale; 100. The method of any one of claims 85 to 99.

101. wherein the one or more input devices include a rotatable input mechanism, and the method further comprises: detecting rotation of the rotatable input mechanism while displaying the clock face on the display; rotating the scale of the user interface element on the display in response to detecting the rotation of the rotatable input mechanism; 101. The method of claim 100, further comprising:

102. the complication includes a time offset from a predetermined time; the user interface element includes a time scale; 100. The method of any one of claims 85 to 99, wherein the clock face includes a hand that indicates a position on the time scale that corresponds to the offset, the hand rotating at a speed that corresponds to the time scale.

103. wherein the one or more input devices include a rotatable input mechanism, and the method further comprises: detecting rotation of the rotatable input mechanism while displaying the clock face on the display; In response to detecting the rotation of the rotatable input mechanism, modifying the time offset displayed by the complication and modifying the location of the hands according to the change in the time offset; 103. The method of claim 102, further comprising:

104. 104. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display and one or more input devices, the one or more programs comprising instructions for performing the method of any one of claims 85 to 103.

105. The display and one or more input devices; one or more processors; a memory storing one or more programs configured to be executed by the one or more processors; 104. An electronic device comprising:

106. The display and one or more input devices; means for carrying out the method of any one of claims 85 to 103; An electronic device comprising:

107. 1. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display and one or more input devices, the one or more programs comprising: instructions for displaying a clock user interface on the display, the clock user interface comprising: The clock face and a user interface element at least partially surrounding the watch face; and Complications and an instruction, instructions for detecting input directed at the user interface element via the one or more input devices while displaying the clock user interface; instructions for, in response to detecting the input directed at the user interface element, updating an appearance of the user interface element based on the input while maintaining the display of the watch face and the complication on the display; 1. A non-transitory computer-readable storage medium comprising:

108. The display and one or more input devices; one or more processors; a memory storing one or more programs configured to be executed by the one or more processors; an electronic device comprising: instructions for displaying a clock user interface on the display, the clock user interface comprising: The clock face and a user interface element at least partially surrounding the watch face; and Complications and an instruction, instructions for detecting input directed at the user interface element via the one or more input devices while displaying the clock user interface; instructions for, in response to detecting the input directed at the user interface element, updating an appearance of the user interface element based on the input while maintaining a display of the watch face and the complication on the display; , an electronic device.

109. The display and one or more input devices; means for displaying a clock user interface on the display, the clock user interface comprising: The clock face and a user interface element at least partially surrounding the watch face; and Complications and a means for means for detecting inputs directed to the user interface elements via the one or more input devices while displaying the clock user interface; means for, in response to detecting the input directed at the user interface element, updating the appearance of the user interface element based on the input while maintaining the display of the watch face and the complication on the display; An electronic device comprising:

Images