Devices, methods, and graphical user interfaces for providing notifications and application information.

Abstract

To provide electronic devices with faster, more efficient methods and interfaces for viewing status information and accessing controls for controlling applications.SOLUTION: A computer system displays a first version of a first user interface including first user interface objects to be displayed concurrently with a first background. In response to detecting a first input, when the first input includes movement in a first direction, the system replaces display of the first version of the first user interface with display of a second user interface that includes representations of second applications. When the first input includes a second movement in a second direction, the system replaces display of the first version of the first user interface with display of the second version of the first user interface including second user interface objects to be displayed concurrently with a second background.SELECTED DRAWING: Figure 5B

Description

Technical Field

[0001] This relates to an electronic device having a touch-sensitive surface for displaying notifications and application information for applications of the electronic device, but is not limited thereto.

Background Art

[0002] The use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has increased significantly in recent years. Exemplary touch-sensitive surfaces include touch pads and touch screen displays. Such surfaces are widely used to manipulate user interfaces and objects therein.

[0003] Exemplary operations include adjusting the position and / or size of one or more user interface objects, activating buttons, or opening files / applications represented by user interface objects, as well as associating metadata with one or more user interface objects or otherwise manipulating the user interface. Exemplary user interface objects include digital images, videos, text, icons, and control elements such as buttons and other graphics.

[0004] However, the ways to perform these operations are cumbersome and inefficient. For example, using a series of mouse-based inputs to select one or more user interface objects and perform one or more actions on the selected user interface objects is tedious and creates a large cognitive burden for the user. In addition, those ways take more time than necessary, thereby wasting energy. This latter consideration is particularly important in battery-operated devices.

Summary of the Invention

[0005] Therefore, there is a need for electronic devices with faster and more efficient methods and interfaces for viewing status information and accessing controls for controlling applications. Such methods and interfaces optionally complement or replace conventional methods for viewing status information and accessing controls for controlling applications. Such methods and interfaces reduce the number, range, and / or types of user input, resulting in a more efficient human-machine interface. With respect to battery-operated devices, such methods and interfaces conserve power and extend the time between battery charges.

[0006] The above-mentioned defects and other problems associated with user interfaces for electronic devices having touch-sensitive surfaces are reduced or eliminated by the devices of this disclosure. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, tablet computer, or handheld device). In some embodiments, the device is a personal electronic device (e.g., a wearable electronic device such as a watch). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also known as a “touchscreen” or “touchscreen display”). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory, and one or more modules, programs, or instruction sets stored in memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through stylus and / or finger touch and gestures on the touch-sensitive surface. In some embodiments, the functions are optional and include image editing, drawing, presentation, word processing, spreadsheet creation, gameplay, making phone calls, video conferencing, sending emails, instant messaging, training support, digital photography, digital videography, web browsing, digital music playback, note-taking, and / or digital video playback. The executable instructions for performing those functions are optional and may be contained in a non-temporary computer-readable storage medium or in other computer program products configured to be executed by one or more processors.

[0007] According to some embodiments, the method is performed on a computer system that communicates with a display generation component. The method includes displaying a first version of a first user interface corresponding to a limited state of the computer system via the display generation component. Displaying a first version of the first user interface includes displaying a plurality of first user interface objects that are displayed simultaneously with a first background according to a first configuration. The plurality of first user interface objects correspond to a plurality of first applications, contain individual content from the plurality of first applications, and are updated periodically as the information represented by the plurality of first user interface objects changes. The method further includes detecting a first input while displaying a first version of the first user interface. The method further includes, upon detection of a first input, replacing a display of a first version of the first user interface with a display of a second user interface that includes each of the representations of a second plurality of second applications, each of which, when activated, causes the computer system to launch the corresponding application of each representation; and replacing a display of a first version of the first user interface with a display of a second version of the first user interface, in accordance with a determination that the first input satisfies a second criterion, the second criterion requiring the first input to include a second movement in a second direction different from the first direction, in order for the second criterion to be satisfied, wherein displaying the second version of the first user interface includes displaying a second plurality of second user interface objects simultaneously with a second background according to a second configuration.The second set of user interface objects corresponds to the third set of applications, contains individual content from the third set of applications, and is periodically updated as the information represented by the second set of user interface objects changes. The first background is different from the second background, the first set of user interface objects is different from the second set of user interface objects, and / or the first configuration is different from the second configuration.

[0008] According to some embodiments, the method is performed on a computer system that communicates with a display generation component. The method includes detecting a request to change the wake user interface of the computer system. The wake user interface is a user interface displayed when the computer system is turned on or transitions from a low-power state to a high-power state, and corresponds to a restricted operating mode of the computer system. In response to detecting a request to change the wake user interface of the computer system, the method further includes displaying a first user interface for changing the wake user interface of the computer system via the display generation component. The method further includes simultaneously displaying a first representation of the wake user interface and a first representation of the home user interface while displaying the first user interface, the home user interface is a user interface displayed when the wake user interface is dismissed and the computer system exits a restricted operating mode. The first representation of the wake user interface corresponds to a first set of one or more wake user interface settings, including a first wake user interface background. The first representation of the home user interface corresponds to a first set of one or more home user interface settings, including a first home user interface background. The method further includes displaying a second representation of the wake user interface. The second representation of the wake user interface corresponds to a second set of one or more wake user interface settings, including a second wake user interface background that is different from the first wake user interface background. The method further includes detecting a sequence of one or more inputs corresponding to a selection of individual representations of the wake user interface for a computer system from the first user interface.The method further includes: setting a wake user interface of a computer system based on a first set of wake user interface settings associated with a first representation of a wake user interface, in accordance with the determination that a first representation of a wake user interface has been selected based on a sequence of one or more inputs, in response to the detection of a sequence of one or more inputs, and including using the background of the first wake user interface as the individual background of the wake user interface; setting a home user interface of a computer system based on a first set of one or more home user interface settings, and including using the background of the first home user interface as the individual background of the home user interface; and setting a wake user interface of a computer system based on a second set of wake user interface settings associated with a second representation of a wake user interface, in accordance with the determination that a second representation of a wake user interface has been selected based on a sequence of one or more inputs, and including using the background of the second wake user interface as the background of the wake user interface.

[0009] According to some embodiments, the method is performed on a computer system that communicates with a display generation component. The method includes displaying a first user interface for configuring a wake user interface via the display generation component. Each version of the wake user interface includes a separate background and a plurality of separate editable user interface objects that overlap the separate background. The first user interface displays at least a first representation of the first version of the wake user interface showing the first plurality of editable user interface objects covering the first background. The method further includes detecting a first input directed to the first user interface while the first user interface is being displayed. The method further includes, upon detection of a first input directed to a first user interface, determining that the first input satisfies a first criterion, by displaying a second user interface for editing the first user interface object, which is selected according to the position of the first input, among a plurality of first editable user interface objects; and updating the first user interface to replace the display of a first representation of a first version of the wake user interface with a display of a second representation of a second version of the wake user interface, according to a determination that the first input satisfies a second criterion different from the first criterion. The second representation of the second version of the wake user interface includes a plurality of second editable user interface objects that cover a second background different from the first background. The plurality of second editable user interface objects are different from the plurality of first editable user interface objects.

[0010] According to some embodiments, the method is performed on a computer system having a display generating component and one or more input devices. The method includes displaying a first user interface including a plurality of notifications via the display generating component, which includes displaying representations of the plurality of notifications in a first configuration in a first area of ​​the first user interface according to a determination that the computer system has enabled a first mode for displaying notifications, and displaying representations of the plurality of notifications in a second configuration in a second area of ​​the first user interface that is smaller than the first area of ​​the first user interface according to a determination that the computer system has enabled a second mode for displaying notifications. The method further includes detecting first user inputs at separate locations on the first user interface corresponding to representations of the plurality of notifications while the first user interface is being displayed. The method further includes, upon detection of a first user input, continuing to detect the first user input, scrolling through notifications within multiple notifications in a first area of ​​the first user interface according to the first user input, according to the determination that the first user input satisfies a first criterion and according to the determination that the multiple notification representations are displayed in a first configuration, and scrolling through notifications within multiple notifications in a third area of ​​the first user interface according to the first user input, according to the determination that the first user input satisfies a first criterion and according to the determination that the multiple notification representations are displayed in a second configuration.

[0011] According to some embodiments, the method is performed on a computer system that communicates with a display generation component. The method includes detecting one or more inputs for subscribing to updates from a first application for a first event and for a second application for a second event. The method further includes displaying a first user interface, the first user interface including a first area at a first location within the first user interface. Displaying the first user interface includes, according to a determination that the first event is active and the second event is inactive, displaying a first representation of the first event in the first area of ​​the first user interface, updating first information contained in the first representation of the first event according to an update received from the first application for the first event, and, according to a determination that the second event is active and the first event is inactive, displaying a second representation of the second event in the first area of ​​the first user interface and updating second information contained in the second representation of the second event according to an update received from the second application for the second event.

[0012] According to some embodiments, the method is performed on a computer system having a display generation component and one or more input devices. The method includes detecting a first user input via one or more input devices while displaying a wake user interface which includes a representation of a first plurality of notifications in a first configuration, the wake user interface which is a user interface displayed when the computer system starts up from a low-power state. The method further includes, in response to detecting the first user input, displaying the representation of the first plurality of notifications in a second configuration of the wake user interface which is different from the first configuration, according to a determination that the first user input satisfies a first criterion, and maintaining the display of the representation of the first plurality of notifications in the first configuration on the wake user interface, according to a determination that the first user input does not satisfy the first criterion. The method further includes detecting the occurrence of a condition that causes the computer system to redisplay the wake user interface after detecting the first user input. The method further includes, in response to detecting the occurrence of a condition that causes the computer system to redisplay the wake user interface, displaying a second set of notification representations in a second configuration according to a determination that the first user input satisfies a first criterion, and displaying a second set of notification representations in the first configuration according to a determination that the first user input does not satisfy the first criterion.

[0013] According to some embodiments, the method is performed on a computer system having a display generation component. The method includes displaying a first user interface via the display generation component for constituting a system user interface having a first background and a first set of one or more system user interface objects covering the first background, and while the system user interface is displayed, the computer system automatically shuffles two or more media items selected from a set of media items in the first background over time. The first user interface includes selectable representations for each of a plurality of categories for media items associated with the computer system, each including at least a first selectable representation of a first category and a second selectable representation of a second category. A first plurality of media items associated with the computer system are automatically selected to be included in a first category based on a first plurality of media items containing automatically detected content of a first kind, and a second plurality of media items associated with the computer system are automatically selected to be included in a second category based on a second plurality of media items containing automatically detected content of a second kind.The method further includes detecting a first input for selecting one or more sets of multiple categories while displaying a first user interface for configuring a system user interface, and displaying a system user interface after one or more sets of multiple categories have been selected by the first input, wherein displaying the system user interface includes displaying a system user interface over time having multiple versions of a first background, each containing media items selected from the media items within each of the sets of multiple categories, wherein one or more sets of multiple categories are second categories According to the determination that it includes the first category but does not include the first category, multiple versions of the first background include media items from the first category but do not include media items from the second category; according to the determination that a set of multiple categories includes the second category but does not include the first category, multiple versions of the first background include media items from the second category but do not include media items from the first category; according to the determination that a set of one or more categories includes both the first and second categories, multiple versions of the first background include one or more media items from the first category and one or more media items from the second category.

[0014] According to some embodiments, the method is performed on a computer system having a display generation component. The method includes displaying a first representation of a system user interface via the display generation component, wherein each individual version of the system user interface includes an individual background and an individual set of one or more system user interface objects superimposed on the individual background, and the first representation of the system user interface corresponds to a first version of the system user interface showing a first set of one or more system user interface objects superimposed on the first background. The method further includes, while displaying a first representation of the system user interface corresponding to a first version of the system user interface, detecting the occurrence of a first condition that causes the computer system to change the appearance of the system user interface based on a first combination of a first background media item and a first filter of the system user interface.This method, in response to detecting the occurrence of a first condition that causes a computer system to change the appearance of a system user interface based on a first combination of a first background media item and a first filter for the system user interface, modifies the first background media item in a first way, according to a determination that the first combination of the first background media item and the first filter satisfies a first criterion, the first criterion requiring that a first set of one or more visual characteristics of the first background media item satisfies a first requirement in order for the first combination of the first background media item and the first filter to satisfy the first criterion. This includes creating a second version of the system user interface by applying a first version of a first filter to a background media item, and creating a second version of the system user interface by applying a second version of the first filter to a first background media item by modifying the first background media item in a second way different from the first way, according to a determination that the first combination of a first background media item and a first filter is satisfied with a second criterion, the second criterion requiring that in order for the first background media item to satisfy the second criterion, one or more first sets of visual characteristics of the first background media item satisfy a second requirement different from the first requirement.

[0015] According to some embodiments, the method is performed on a computer system having a display generating component. The method includes displaying a wake screen user interface corresponding to a restricted state of the computer system via the display generating component, and includes displaying a first background and a plurality of system user interface objects covering at least a portion of the first background, wherein the first background includes a plurality of graphical elements arranged according to a first spatial configuration. The method further includes detecting a first user input, including a request to dismiss the wake screen user interface, while displaying the wake screen user interface corresponding to a restricted state of the computer system. The method includes, upon detection of a first user input that includes a request to reject a wake screen user interface, moving a plurality of graphical elements in a first direction in accordance with the first user input while increasing the spatial gaps between the plurality of graphical elements, and, upon determination that the request to reject a wake screen user interface contained in the first user input satisfies a first criterion, replacing the display of a wake screen user interface corresponding to a restricted state of the computer system with the display of a second user interface different from the wake screen user interface, wherein the plurality of graphical elements are displayed in the second user interface while reducing the spatial gaps between the plurality of graphical elements.

[0016] According to some embodiments, the electronic device includes a display, a touch-sensitive surface, optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface, optionally one or more tactile output generators, one or more processors, and a memory storing one or more programs, the one or more programs being configured to be executed by the one or more processors, and the one or more programs including instructions to perform or cause to perform any of the operations described herein. According to some embodiments, a computer-readable storage medium stores instructions internally, and when executed by an electronic device having a display, a touch-sensitive surface, optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface, and optionally one or more tactile output generators, the instructions cause the device to perform or cause to perform any of the operations described herein. According to some embodiments, a graphical user interface on an electronic device having a display, a touch-sensitive surface, optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface, optionally one or more tactile output generators, memory, and one or more processors for executing one or more programs stored in memory includes one or more elements displayed in any of the methods described herein, the elements being updated in response to input as described in any of the methods described herein. According to some embodiments, the electronic device includes a display, a touch-sensitive surface, optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface, optionally one or more tactile output generators, and means for performing or causing to perform any of the operations described herein. According to some embodiments, an information processing device for use in an electronic device having a display, a touch-sensitive surface, optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface, and optionally one or more tactile output generators includes means for performing or causing to perform any of the operations described herein.

[0017] Therefore, electronic devices having a display, a touch-sensitive surface, optionally one or more sensors for detecting contact intensity with the touch-sensitive surface, optionally one or more tactile output generators, optionally one or more device orientation sensors, and optionally an audio system are provided with improved methods and interfaces for modifying the user interface and displaying notifications and / or status information, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces can complement or replace conventional methods for modifying the user interface and displaying notifications and / or status information. [Brief explanation of the drawing]

[0018] To better understand the various embodiments described, the following “Modes for Carrying Out the Invention” should be referenced in conjunction with the following drawings, and similar reference numbers throughout the following drawings refer to the corresponding parts.

[0019] [Figure 1A] This is a block diagram showing a portable multifunctional device having a touch-sensitive display according to several embodiments.

[0020] [Figure 1B] This is a block diagram showing exemplary components for event handling according to several embodiments.

[0021] [Figure 2] Several embodiments of a portable multifunctional device having a touchscreen are shown.

[0022] [Figure 3] This is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface, according to several embodiments.

[0023] [Figure 4A]An exemplary user interface for a menu of an application on a portable multifunctional device according to some embodiments is shown.

[0024] [Figure 4B] An exemplary user interface for a multifunctional device having a touch-sensitive surface separated from a display according to some embodiments is shown.

[0025] [Figure 5A] A diagram showing an exemplary user interface for navigating and editing each type of user interface according to some embodiments. [Figure 5B] A diagram showing an exemplary user interface for navigating and editing each type of user interface according to some embodiments. [Figure 5C] A diagram showing an exemplary user interface for navigating and editing each type of user interface according to some embodiments. [Figure 5D] A diagram showing an exemplary user interface for navigating and editing each type of user interface according to some embodiments. [Figure 5E] A diagram showing an exemplary user interface for navigating and editing each type of user interface according to some embodiments. [Figure 5F] A diagram showing an exemplary user interface for navigating and editing each type of user interface according to some embodiments. [Figure 5G] A diagram showing an exemplary user interface for navigating and editing each type of user interface according to some embodiments. [Figure 5H] A diagram showing an exemplary user interface for navigating and editing each type of user interface according to some embodiments. [Figure 5I] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5J] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5K] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5L] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5L2] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5L3] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5M] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5N] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5O] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5P] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5Q]This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5R] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5S] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5T] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5U] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5V] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5W] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5W1] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5X] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5Y] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5Z]This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AA] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AB] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AC] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AD] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AE] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AF] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AG] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AH] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AI] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AJ]This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AK] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AL] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AM] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AN] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AO] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AP] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AQ] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AR] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AS] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AT]This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AU] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AV] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AW] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AX] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AX2] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AX3] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AX4] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AX5] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AY] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5AZ]This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BA] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BB] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BC] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BD] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BE] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BF] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BG] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BH] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BI] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BJ]This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BK] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BL] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BM] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BN] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BO] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BP] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BQ] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BR] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BS] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BT]This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BU] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BV] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BW] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BX] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BY] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5BZ] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5CA] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments. [Figure 5CB] This figure shows exemplary user interfaces for navigating and editing each type of user interface according to several embodiments.

[0026] [Figure 6A] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6B] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6C] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6D] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6E] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6F] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6G] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6H] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6H2] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6H3] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6H4] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6H5] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6H6] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6I] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6J] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6K] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6L]The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6M] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6N] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6O] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6O2] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6P] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6Q] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6R] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6S] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6T] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6U] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6V] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6W] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6X] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6Y] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6Z] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6AA] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6AB] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6AC] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6AD] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6AE] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6AF] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6AG] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6AH] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6AI] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6AJ] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6AK] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6AL] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6AM] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6AN]The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6AO] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6AP] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6AQ] The following are exemplary user interfaces for an extended face switcher according to several embodiments. [Figure 6AR] The following are exemplary user interfaces for an extended face switcher according to several embodiments.

[0027] [Figure 7A] This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7B] This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7C] This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7D] This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7E] This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7F] This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7G] This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7H]This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7I] This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7J] This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7K] This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7L] This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7M] This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7N] This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7O] This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7P] This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7Q] This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7R] This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7S] This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7T]This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7U] This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7V-1] This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7V-2] This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations. [Figure 7V-3] This document illustrates, according to several embodiments, a representation of multiple notifications in different configurations and a user input for switching between different configurations.

[0028] [Figure 8A] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8B] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8C] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8D] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8E] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8F] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8G]The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8H] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8I] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8J] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8K] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8L] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8M] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8N] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8O] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8P] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8Q] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8R] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8S] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8T] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8U] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8V] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8W] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8X] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8Y] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8Z] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8AA] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8AB] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8AC] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8AD] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8AE] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8AF] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8AG] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8AH] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8AI] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8AJ] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8AK] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8AL] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8AM] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments. [Figure 8AN] The following are exemplary user interfaces for displaying a session area for an ongoing event, according to several embodiments.

[0029] [Figure 9A] This is a flowchart of a process for changing the user interface based on user input, according to several embodiments. [Figure 9B]This is a flowchart of a process for changing the user interface based on user input, according to several embodiments. [Figure 9C] This is a flowchart of a process for changing the user interface based on user input, according to several embodiments. [Figure 9D] This is a flowchart of a process for changing the user interface based on user input, according to several embodiments. [Figure 9E] This is a flowchart of a process for changing the user interface based on user input, according to several embodiments. [Figure 9F] This is a flowchart of a process for changing the user interface based on user input, according to several embodiments. [Figure 9G] This is a flowchart of a process for changing the user interface based on user input, according to several embodiments. [Figure 9H] This is a flowchart of a process for changing the user interface based on user input, according to several embodiments. [Figure 9I] This is a flowchart of a process for changing the user interface based on user input, according to several embodiments.

[0030] [Figure 10A] This is a flowchart of the process for selecting and / or changing user interfaces according to several embodiments. [Figure 10B] This is a flowchart of the process for selecting and / or changing user interfaces according to several embodiments. [Figure 10C] This is a flowchart of the process for selecting and / or changing user interfaces according to several embodiments. [Figure 10D] This is a flowchart of the process for selecting and / or changing user interfaces according to several embodiments. [Figure 10E]This is a flowchart of the process for selecting and / or changing user interfaces according to several embodiments. [Figure 10F] This is a flowchart of the process for selecting and / or changing user interfaces according to several embodiments. [Figure 10G] This is a flowchart of the process for selecting and / or changing user interfaces according to several embodiments. [Figure 10H] This is a flowchart of the process for selecting and / or changing user interfaces according to several embodiments. [Figure 10I] This is a flowchart of the process for selecting and / or changing user interfaces according to several embodiments.

[0031] [Figure 11A] This is a flowchart of the process for modifying the user interface according to several embodiments. [Figure 11B] This is a flowchart of the process for modifying the user interface according to several embodiments. [Figure 11C] This is a flowchart of the process for modifying the user interface according to several embodiments. [Figure 11D] This is a flowchart of the process for modifying the user interface according to several embodiments. [Figure 11E] This is a flowchart of the process for modifying the user interface according to several embodiments. [Figure 11F] This is a flowchart of the process for modifying the user interface according to several embodiments. [Figure 11G] This is a flowchart of the process for modifying the user interface according to several embodiments. [Figure 11H] This is a flowchart of the process for modifying the user interface according to several embodiments.

[0032] [Figure 12A] This is a flowchart of a process for displaying multiple notification representations in different configurations according to several embodiments. [Figure 12B] This is a flowchart of a process for displaying multiple notification representations in different configurations according to several embodiments. [Figure 12C] This is a flowchart of a process for displaying multiple notification representations in different configurations according to several embodiments. [Figure 12D] This is a flowchart of a process for displaying multiple notification representations in different configurations according to several embodiments. [Figure 12E] This is a flowchart of a process for displaying multiple notification representations in different configurations according to several embodiments.

[0033] [Figure 13A] This is a flowchart of a process for displaying status information in the session area based on a subscription, according to several embodiments. [Figure 13B] This is a flowchart of a process for displaying status information in the session area based on a subscription, according to several embodiments. [Figure 13C] This is a flowchart of a process for displaying status information in the session area based on a subscription, according to several embodiments. [Figure 13D] This is a flowchart of a process for displaying status information in the session area based on a subscription, according to several embodiments. [Figure 13E] This is a flowchart of a process for displaying status information in the session area based on a subscription, according to several embodiments. [Figure 13F] This is a flowchart of a process for displaying status information in the session area based on a subscription, according to several embodiments. [Figure 13G]This is a flowchart of a process for displaying status information in the session area based on a subscription, according to several embodiments.

[0034] [Figure 14A] This is a flowchart of a process for switching between different configurations that can display multiple notification representations according to several embodiments. [Figure 14B] This is a flowchart of a process for changing between different configurations that can display multiple notification representations according to several embodiments. [Figure 14C] This is a flowchart of a process for switching between different configurations that can display multiple notification representations according to several embodiments. [Figure 14D] This is a flowchart of a process for switching between different configurations that can display multiple notification representations according to several embodiments. [Figure 14E] This is a flowchart of a process for changing between different configurations that can display multiple notification representations according to several embodiments. [Figure 14F] This is a flowchart of a process for changing between different configurations that can display multiple notification representations according to several embodiments. [Figure 14G] This is a flowchart of a process for changing between different configurations that can display multiple notification representations according to several embodiments.

[0035] [Figure 15A] This is a flowchart of a process for automatically shuffling media items as background, according to several embodiments. [Figure 15B] This is a flowchart of a process for automatically shuffling media items as background, according to several embodiments. [Figure 15C] This is a flowchart of a process for automatically shuffling media items as background, according to several embodiments. [Figure 15D]This is a flowchart of a process for automatically shuffling media items as background, according to several embodiments. [Figure 15E] This is a flowchart of a process for automatically shuffling media items as background, according to several embodiments. [Figure 15F] This is a flowchart of a process for automatically shuffling media items as background, according to several embodiments. [Figure 15G] This is a flowchart of a process for automatically shuffling media items as background, according to several embodiments. [Figure 15H] This is a flowchart of a process for automatically shuffling media items as background, according to several embodiments. [Figure 15I] This is a flowchart of a process for automatically shuffling media items as background, according to several embodiments.

[0036] [Figure 16A] This is a flowchart of the process for applying different versions of a filter to a background media item, according to several embodiments. [Figure 16B] This is a flowchart of the process for applying different versions of a filter to a background media item, according to several embodiments. [Figure 16C] This is a flowchart of the process for applying different versions of a filter to a background media item, according to several embodiments. [Figure 16D] This is a flowchart of the process for applying different versions of a filter to a background media item, according to several embodiments. [Figure 16E] This is a flowchart of the process for applying different versions of a filter to a background media item, according to several embodiments. [Figure 16F] This is a flowchart of the process for applying different versions of a filter to a background media item, according to several embodiments. [Figure 16G] This is a flowchart of the process for applying different versions of a filter to a background media item, according to several embodiments. [Figure 16H] This is a flowchart of the process for applying different versions of a filter to a background media item, according to several embodiments. [Figure 16I] This is a flowchart of the process for applying different versions of a filter to a background media item, according to several embodiments. [Figure 16J] This is a flowchart of the process for applying different versions of a filter to a background media item, according to several embodiments.

[0037] [Figure 17A] This is a flowchart of the process for animating a system user interface according to several embodiments. [Figure 17B] This is a flowchart of the process for animating a system user interface according to several embodiments. [Figure 17C] This is a flowchart of the process for animating a system user interface according to several embodiments. [Figure 17D] This is a flowchart of the process for animating a system user interface according to several embodiments. [Modes for carrying out the invention]

[0038] Many electronic devices have a graphical user interface that allows users to navigate between application user interfaces and / or system user interfaces. Several methods for navigating between user interfaces enable multitasking so that individual applications continue to update in the background even after users have navigated away from their individual application user interfaces. Several methods for providing system user interfaces can restrict customization made to the system user interface and obscure certain elements and / or status information displayed in the system user interface. For example, these methods may require users to return to each application user interface to see updates. The embodiments described below provide an improved method for providing status updates for multiple applications within a persistent session area. This method streamlines the user's ability to view real-time status information for an active session, thereby eliminating the need for an extra, separate step of returning to the individual user interfaces of individual applications to view status updates.

[0039] The methods, devices, and GUIs described herein use tactile feedback to improve user interface interaction in several ways. For example, they make it easier to indicate hidden thresholds and user interface components that represent selectable options.

[0040] The processes described below improve the usability of the device and make the user-device interface more efficient (for example, by helping the user provide appropriate input and reducing user errors when operating / interacting with the device) by providing the user with improved visual, auditory, and / or haptic feedback, reducing the number of inputs required to perform an operation, providing additional control options without cluttering the user interface with additional displayed controls, performing an operation when a set of conditions are met without requiring further user input, and / or additional technologies. These technologies also reduce power consumption and improve the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0041] In the following, Figures 1A, 1B, 2, and 3 provide a description of an exemplary device. Figures 4A–4B and 5A–5CA show exemplary user interfaces for navigating and editing each type of user interface. Figures 6A–6AR show an exemplary user interface for the augmented face switcher. Figures 7A–7V-3 show representations of multiple notifications in different configurations and user input for switching between different configurations. Figures 8A–8AN show an exemplary user interface for displaying the session area for ongoing events. Figures 9A–9I are flowcharts of how to change the user interface based on user input. Figures 10A–10I show flowcharts of how to select and / or change the user interface. Figures 11A–11H are flowcharts of how to change the user interface. Figures 12A–12E show flowcharts of how to display representations of multiple notifications in different configurations. Figures 13A–13G show flowcharts of how to display status information in the session area based on subscriptions. Figures 14A to 14G show flowcharts of how to change between different configurations that can display multiple notification representations. Figures 15A to 15I are flowcharts of the process for automatically shuffling media items as backgrounds according to several embodiments. Figures 16A to 16J are flowcharts of the process for applying different versions of filters to background media items according to several embodiments. Figures 17A to 17D are flowcharts of the process for animating system user interfaces according to several embodiments. The user interfaces in Figures 5A to 5CA, 6A to 6AR, 7A to 7V-3 and 8A to 8AN are used to illustrate the processes in Figures 9A to 9I, 10A to 10I, 11A to 11H, 12A to 12E, 13A to 13G, 14A to 14G, 15A to 15I, 16A to 16J, and 17A to 17D.

[0042] Example device Herein, a detailed reference is made to embodiments shown in the accompanying drawings. The following detailed description includes numerous specific details to provide a complete understanding of the various embodiments described. However, it will be apparent to those skilled in the art that the various embodiments described can be practiced without these specific details. In other examples, well-known methods, procedures, components, circuits, and networks are not described in detail so as not to unnecessarily obscure the aspects of the embodiments.

[0043] In this specification, terms such as "first," "second," etc., are used to describe various elements in several embodiments, but it will be understood that these elements should not be limited by those terms. These terms are used solely to distinguish one element from another. For example, without departing from the scope of the various embodiments described, a first contact may be referred to as a second contact, and similarly, a second contact may be referred to as a first contact. Both the first and second contacts are contacts, but they are not the same contact unless the context explicitly indicates otherwise.

[0044] The terminology used in the descriptions of the various embodiments described herein is intended solely to describe specific embodiments and is not intended to be limiting. In the descriptions of the various embodiments and the accompanying claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless otherwise explicitly stated in the context. Furthermore, it should be understood that, as used herein, the term “and / or” refers to and includes any and all possible combinations of one or more of the enumerated items relating to the invention. It should be further understood that, as used herein, the terms “includes,” “comprises,” and / or “comprising,” specify the presence of the described features, integers, steps, actions, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, actions, elements, components, and / or groups thereof.

[0045] Where used herein, the term "if" is interpreted, at its discretion and in context, to mean "when," "upon," "in response to determining," or "in response to detecting." Similarly, the phrases "if it is determined" or "if [a stated condition or event] is detected" are interpreted, at its discretion and in 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]."

[0046] 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, which also includes other functions such as PDA functionality and / or music player functionality. 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. Other portable electronic devices, such as laptop or tablet computers having a touch-sensitive surface (e.g., a touchscreen display and / or touchpad), are optionally used. It should also be understood that in some embodiments, the device is not a portable communication device but a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and / or touchpad).

[0047] The following discussion describes electronic devices including displays and touch-sensitive surfaces. However, please understand that the definition of an electronic device is optional and may include one or more other physical user interface devices such as a physical keyboard, mouse, and / or joystick.

[0048] The device generally supports a variety of applications, including one or more of the following: note-taking applications, drawing applications, presentation applications, word processing applications, website creation applications, disk authoring applications, spreadsheet applications, game applications, telephone applications, video conferencing applications, email applications, instant messaging applications, training support applications, photo management applications, digital camera applications, digital video camera applications, web browsing applications, digital music player applications, and / or digital video player applications.

[0049] Various applications running on this device optionally utilize at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface, as well as the corresponding information displayed on the device, are optionally adjusted and / or modified on an application-by-application basis and / or within individual applications. In this way, the device's common physical architecture (such as the touch-sensitive surface) optionally supports a variety of applications with intuitive and transparent user interfaces for the user.

[0050] Here, we turn our attention to embodiments of portable devices having a touch-sensitive display. Figure 1A is a block diagram of a portable multifunction device 100 having a touch-sensitive display system 112 according to several embodiments. The touch-sensitive display system 112 may be referred to as a “touchscreen” for convenience, or simply as a touch-sensitive display. The device 100 includes a memory 102 (optionally including one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input or control devices 116, and an external port 124. The device 100 optionally includes one or more optical sensors 164. The device 100 optionally includes one or more intensity sensors 165 for detecting the intensity of contact on the device 100 (for example, a touch-sensitive surface such as the touch-sensitive display system 112 of the device 100). Device 100 optionally includes one or more tactile output generators 167 that generate tactile outputs on Device 100 (for example, on touch-sensitive surfaces such as the touch-sensitive display system 112 of Device 100 or the touchpad 355 of Device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0051] As used herein and in the claims, the term “tactile output” means a physical displacement of the device relative to its previous position, 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, which will be detected by the user through the user’s sense of touch. For example, in a situation where the device or a component of the device is in contact with the touch-sensitive surface of the user (e.g., the user’s fingers, palm, or other part of their hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in the physical properties 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) may be optionally interpreted by the user as a “down-click” or “up-click” of a physical actuator button. In some cases, the user may feel a tactile sensation such as a “down-click” or “up-click” even when there is no movement of a physical actuator button associated with a touch-sensitive surface that is physically pressed (e.g., displaced) by the user’s movement. As another example, movement of a touch-sensitive surface may be interpreted or perceived by the user as "roughness" of that surface, even if there is no change in the smoothness of the touch-sensitive surface. Such user interpretations of touch depend on the user's personal sensory perception, but there are many touch sensory perceptions common to the majority of users. Therefore, when a tactile output is described as corresponding to a user's specific sensory perception (e.g., "up-click," "down-click," "roughness"), unless otherwise stated, the generated tactile output corresponds to the physical displacement of the device or its components that produce the described sensory perception of a typical (or average) user.By providing haptic feedback to the user using tactile output, device usability is improved, the user-device interface becomes more efficient (for example, by helping the user provide appropriate input when operating / interacting with the device and reducing user errors), and in addition, power consumption is reduced and device battery life is improved by enabling the user to use the device more quickly and efficiently.

[0052] In some embodiments, the tactile output pattern specifies characteristics of the tactile output, such as the amplitude of the tactile output, the shape of the motion waveform of the tactile output, the frequency of the tactile output, and / or the duration of the tactile output.

[0053] When a device generates tactile outputs with various different tactile output patterns (for example, via one or more tactile output generators that move a movable mass to generate a tactile output), the tactile output can evoke various different tactile sensations when the user holds or touches the device. While the user's sensation is based on their perception of the tactile output, most users are able to identify changes in the waveform, frequency, and amplitude of the tactile output generated by the device. Therefore, the waveform, frequency, and amplitude can be adjusted to indicate to the user that different actions are being performed. Therefore, in some situations, tactile outputs having tactile output patterns designed, selected, and / or developed to simulate the properties (e.g., size, material, weight, stiffness, smoothness, etc.), behavior (e.g., vibration, displacement, acceleration, rotation, expansion, etc.), and / or interactions (e.g., collision, adhesion, repulsion, attraction, friction, etc.) of objects in a given environment (e.g., a user interface including graphical features and objects, a simulated physical environment with virtual boundaries and virtual objects, a real physical environment with physical boundaries and physical objects, and / or any combination of the above), provide the user with useful feedback that reduces input errors and increases the efficiency of the user's operation of the device. In addition, tactile outputs are optionally generated to correspond to feedback unrelated to simulated physical properties, such as input thresholds or object selection. In some situations, such tactile outputs provide the user with useful feedback that reduces input errors and increases the efficiency of the user's operation of the device.

[0054] In some embodiments, tactile output having a suitable tactile output pattern acts as a signal for the occurrence of a target event behind a scene in the user interface or device. Examples of target events include the activation of affordances provided on the device or within the user interface (e.g., physical buttons, virtual buttons, or toggle switches), the success or failure of a requested action, reaching or crossing a boundary within the user interface, entering a new state, switching the focus of input between objects, activating a new mode, reaching or exceeding an input threshold, and detecting or recognizing the type of input or gesture. In some embodiments, tactile output is provided to serve as a warning or alert for an upcoming event or result that will occur unless a redirection or interruption input is detected in a timely manner. Tactile output is also used in other contexts to improve the user experience, improve the accessibility of the device for users with visual or motor impairments or other accessibility needs, and / or improve the efficiency and functionality of the user interface and / or device. Tactile output, optionally accompanied by audio output and / or visible user interface changes, further enhances the user experience when the user interacts with the user interface and / or device, facilitates better communication of information regarding the state of the user interface and / or device, reduces input errors, and increases the efficiency of user operation of the device.

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

[0056] 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. Access to memory 102 by CPU(s) 120 and other components of device 100 such as peripheral interface 118 is optionally controlled by memory controller 122.

[0057] A peripheral device interface 118 is used to connect the device's input and output peripherals to the CPU(s) 120 and memory 102. One or more processors 120 operate or execute various software programs and / or instruction sets stored in memory 102 to perform various functions for device 100 and process data.

[0058] In some embodiments, the peripheral interface 118, the CPU(s) 120, and the 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.

[0059] The RF (radio frequency) circuit 108 transmits and receives RF signals, also known as electromagnetic signals. The RF circuit 108 converts electrical signals to electromagnetic signals or electromagnetic signals to electrical signals and communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 108 optionally includes well-known circuits for performing these functions, which include, but are not limited to, antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, CODEC chipsets, subscriber identity module (SIM) cards, and memory. The RF circuit 108 optionally communicates wirelessly with networks such as the Internet, also known as the World Wide Web (WWW), intranets, and / or wireless networks such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs), and with other devices. Wireless communication is optional and includes 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), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), and Code Division Multiple Access (W-CDMA).Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g, and / or IEEE 802.11n), Voice over Internet Protocol (VoIP), Wi-MAX, protocols for email (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), Instant Messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE)), Instant Messaging and Presence Services Using any of several communication standards, communication protocols, and communication technologies, including, but not limited to, a Service (IMPS), and / or Short Message Service (SMS), or any other suitable communication protocol, including a communication protocol not yet developed as of the filing date of this document.

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

[0061] The I / O subsystem 106 connects input / output peripherals on device 100, such as the touch-sensitive display system 112 and other input or control devices 116, to the peripheral interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, an intensity sensor controller 159, a haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. One or more input controllers 160 receive electrical signals from and transmit electrical signals to the other input or control devices 116. The other input or control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons), dials, slider switches, joysticks, click wheels, etc. In some alternative embodiments, the input controller(s) 160 are optionally connected to (or not connected to) any of the following: a keyboard, an infrared port, a USB port, a stylus, and / or a pointer device such as a mouse. One or more buttons (e.g., 208, Figure 2) optionally include up / down buttons for controlling the volume of speaker 111 and / or microphone 113. One or more buttons optionally include push buttons (e.g., 206, Figure 2).

[0062] The touch-sensitive display system 112 provides input and output interfaces between the device and the user. The display controller 156 receives electrical signals from and / or transmits electrical signals to the touch-sensitive display system 112. The touch-sensitive display system 112 displays a visual output to the user. This visual output optionally includes graphics, text, icons, videos, and any combination thereof (collectively, “graphics”). In some embodiments, some or all of the visual output corresponds to user interface objects. As used herein, the term “affordance” refers to a user-interactive graphical user interface object (for example, a graphical user interface object configured to respond to input directed toward the graphical user interface object). Examples of user-interactive graphical user interface objects include, but are not limited to, buttons, sliders, icons, selectable menu items, switches, hyperlinks, or other user interface controls.

[0063] The touch-sensitive display system 112 has a touch-sensitive surface, sensor, or set of sensors that accept user input based on tactile and / or haptic contact. The touch-sensitive display system 112 and the display controller 156 (together with any associated modules and / or instruction sets in memory 102) detect contact (and any movement or interruption of contact) on the touch-sensitive display system 112 and translate the detected contact into interaction with user interface objects (e.g., one or more soft keys, icons, web pages, or images) displayed on the touch-sensitive display system 112. In some embodiments, the point of contact between the touch-sensitive display system 112 and the user corresponds to the user's finger or stylus.

[0064] The touch-sensitive display system 112 optionally uses LCD (liquid crystal display) technology, LPD (light-emitting polymer display) technology, or LED (light-emitting diode) technology, but other display technologies are used in other embodiments. The touch-sensitive display system 112 and the display controller 156 optionally use any of several currently known or future-developed touch-sensing technologies, including but not limited to capacitive technology, resistive technology, infrared technology, and surface acoustic wave technology, as well as other proximity sensor arrays or other elements for determining one or more contact points with the touch-sensitive display system 112, to detect contact and any movement or interruption thereof. In some embodiments, projected mutual capacitance sensing technology is used, such as that found in iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, California.

[0065] The touch-sensitive display system 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the video resolution of the touchscreen is greater than 400 dpi (e.g., 500 dpi, 800 dpi, or higher). The user optionally touches the touch-sensitive display system 112 using any suitable object or attachment such as a stylus or finger. In some embodiments, the user interface is designed to function with finger-based touch and gestures, which may be less precise than stylus-based input due to the larger contact area of ​​a finger on the touchscreen than that of a stylus. In some embodiments, the device translates coarse finger input into a precise pointer / cursor position or command to perform an action desired by the user.

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

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

[0068] Device 100 also optionally includes one or more optical sensors 164 (for example, as part of one or more cameras). Figure 1A shows an optical sensor coupled with an optical sensor controller 158 in the I / O subsystem 106. The optical sensor(s) 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The optical sensor(s) 164 receives light from the environment, projected through one or more lenses, and converts the light into data representing an image. In conjunction with an imaging module 143 (also called a camera module), the optical sensor(s) 164 optionally captures still images and / or video. In some embodiments, the optical sensors are located on the back of device 100, opposite the touch-sensitive display system 112 on the front of the device, so that a touchscreen can be used as a viewfinder for acquiring still images and / or video images. In some embodiments, a separate light sensor is positioned on the front of the device so that an image of the user can be captured (for example, for selfies, or for video conferencing while the user is viewing other video conference participants on the touchscreen).

[0069] Device 100 also optionally includes one or more contact strength sensors 165. Figure 1A shows a contact strength sensor coupled with a strength sensor controller 159 in the I / O subsystem 106. The contact strength sensor(s) 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, pressure-power sensors, optical force sensors, capacitive touch-sensing surfaces, or other strength sensors (e.g., sensors used to measure the force (or pressure) of contact on a touch-sensing surface). The contact strength sensor(s) 165 receives contact strength information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact strength sensor is positioned alongside or adjacent to a touch-sensing surface (e.g., a touch-sensing display system 112). In some embodiments, at least one contact strength sensor is located on the back of Device 100, opposite the touchscreen display system 112 which is located on the front of Device 100.

[0070] The device 100 also optionally includes one or more proximity sensors 166. Figure 1A shows a proximity sensor 166 coupled to a peripheral interface 118. Alternatively, the proximity sensor 166 is coupled to an input controller 160 in the I / O subsystem 106. In some embodiments, when the multifunction device is positioned near the user's ear (for example, when the user is making a phone call), the proximity sensor turns off and disables the touch-sensitive display system 112.

[0071] Device 100 also optionally includes one or more tactile output generators 167. Figure 1A shows a tactile output generator coupled with a tactile feedback controller 161 in the I / O subsystem 106. In some embodiments, the tactile output generator(s) 167 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 outputs on the device). The tactile output generator(s) 167 receives a tactile feedback generation command from the tactile feedback module 133 and generates a tactile output on the device 100 that can be sensed by the user of the device 100. In some embodiments, at least one tactile output generator is positioned alongside or adjacent to a touch-sensing surface (e.g., a touch-sensing display system 112) and optionally generates a tactile output by moving the touch-sensing surface vertically (e.g., inward / outward from the surface of device 100) or horizontally (e.g., forward / backward in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is positioned on the back of device 100, opposite the touch-sensing display system 112 which is located on the front of device 100.

[0072] The device 100 also optionally includes one or more accelerometers 168. Figure 1A shows an accelerometer 168 coupled to a peripheral interface 118. Alternatively, the accelerometer 168 is optionally coupled to an input controller 160 in the I / O subsystem 106. In some embodiments, information is displayed on a touchscreen display in a portrait or landscape view based on an analysis of data received from one or more accelerometers. In addition to the accelerometers 168, the device 100 optionally includes a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information about the position and orientation (e.g., portrait or landscape) of the device 100.

[0073] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a touch / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a haptic feedback module (or instruction set) 133, a text input module (or instruction set) 134, a Global Positioning System (GPS) module (or instruction set) 135, and an application (or instruction set) 136. Furthermore, in some embodiments, as shown in Figures 1A and 3, memory 102 stores device / global internal state 157. The device / global internal state 157 includes one or more of the following: an active application state indicating which application is active, if there is an application currently active; a display state indicating which application, view, or other information occupies various areas of the touch-sensitive display system 112; a sensor state including information obtained from various sensors and other input or control devices 116 of the device; and position and / or orientation information relating to the position and / or orientation of the device.

[0074] An operating system (for example, an embedded operating system such as iOS, Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or VxWorks) includes various software components and / or drivers for controlling and managing overall system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.

[0075] The communication module 128 facilitates communication with other devices via one or more external ports 124 and also includes various software components for processing data received by the RF circuit 108 and / or external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) are adapted to connect to other devices directly or indirectly via a network (e.g., the Internet, Wi-Fi, etc.). In some embodiments, the external ports are multi-pin (e.g., 30-pin) connectors identical or similar to and / or compatible with the 30-pin connectors used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. In some embodiments, the external ports are Lightning connectors identical or similar to and / or compatible with the Lightning connectors used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. In some embodiments, the external port is a USB Type-C connector identical, similar to, and / or compatible with the USB Type-C connector used in some electronic devices from Apple Inc. in Cupertino, California.

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

[0077] The contact / motion module 130 optionally detects gesture input from the user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motion, timing, and / or intensity of detected contact). Therefore, gestures are optionally detected by detecting specific contact patterns. For example, detecting a finger tap gesture involves detecting a finger down event, followed by a finger up (lift-off) event at the same location (or substantially the same location) as the finger down event (e.g., at the icon location). In another embodiment, detecting a finger swipe gesture on the touch-sensitive surface involves detecting a finger down event, followed by a drag event of one or more fingers, and then a finger up (lift-off) event. Similarly, taps, swipes, drags, and other gestures are optionally detected with respect to the stylus by detecting specific contact patterns with respect to the stylus.

[0078] In some embodiments, detecting a finger tap gesture depends on the length of time between detecting a finger down event and detecting a finger up event, but not on the intensity of finger contact between the two events. In some embodiments, a tap gesture is detected according to the determination that the length of time between the finger down event and the finger up event is shorter than a predetermined value (e.g., shorter than 0.1, 0.2, 0.3, 0.4, or 0.5 seconds), regardless of whether the intensity of finger contact between taps meets a given intensity threshold (greater than a nominal contact detection intensity threshold), such as a light or deep pressure intensity threshold. Thus, a finger tap gesture can satisfy certain input criteria that do not require the characteristic intensity of contact to meet a given intensity threshold in order for certain input criteria to be met. To clarify, finger contact in a tap gesture generally needs to meet a nominal contact detection intensity threshold below which contact is not detected in order to detect a finger down event. A similar analysis applies to detecting tap gestures or other contacts by a stylus. In cases where the device can detect contact from a finger or stylus hovering over the touch-sensitive surface, the nominal contact detection intensity threshold is optional and does not correspond to physical contact between the finger or stylus and the touch-sensitive surface.

[0079] In a similar manner, the same concept applies to other types of gestures. For example, swipe gestures, pinch gestures, de-pinch gestures, and / or long press gestures are optional and are detected based on whether they meet criteria that are either unrelated to the intensity of the contacts involved in the gesture, or do not require the contact(s) performing the gesture to reach an intensity threshold in order to be recognized. For example, a swipe gesture is detected based on the amount of movement of one or more contacts. A pinch gesture is detected based on the movement of two or more contacts toward each other. A de-pinch gesture is detected based on the movement of two or more contacts toward each other. A long press gesture is detected based on the duration of contact with a touch-sensitive surface involving movement less than a threshold amount. Therefore, the statement that a particular gesture recognition criterion does not require the intensity of one or more contacts to meet a corresponding intensity threshold for that criterion to be satisfied means that a particular gesture recognition criterion can be satisfied when one or more contacts in a gesture do not reach a corresponding intensity threshold, and can also be satisfied when one or more of the contacts in a gesture reach or exceed a corresponding intensity threshold. In some embodiments, a tap gesture is detected based on the determination that finger-down and finger-up events were detected within a predetermined time period, regardless of whether the contacts are above or below their respective intensity thresholds during a predetermined time period, and a swipe gesture is detected based on the determination that the movement of the contacts is greater than a predetermined magnitude, even if the contacts exceed their respective intensity thresholds at the end of the movement of the contacts. Even in embodiments where gesture detection is influenced by the intensity of the contact performing the gesture (for example, the device detects longer presses more quickly when the contact intensity exceeds an intensity threshold, or the device is slower to detect tap inputs when the contact intensity is higher), the detection of those gestures does not require the contact to reach a specific intensity threshold, as long as the criteria for recognizing the gesture can be met in situations where the contact does not reach a specific intensity threshold (for example, even if the amount of time required to recognize the gesture changes).

[0080] Contact intensity thresholds, duration thresholds, and movement thresholds are combined in various different combinations to create heuristics for distinguishing two or more different gestures directed towards the same input element or region in certain situations, thereby enabling multiple different interactions with the same input element to provide a richer set of user interactions and responses. The statement that a particular set of gesture recognition criteria does not require the intensity of a contact(s) to meet its respective intensity threshold for that particular gesture recognition criterion to be satisfied does not preclude simultaneously evaluating other intensity-dependent gesture recognition criteria to identify other gestures that have criteria that are satisfied when the gesture includes contact with an intensity exceeding its respective intensity threshold. For example, in some situations, a first gesture recognition criterion for a first gesture that does not require the intensity of a contact(s) to meet a corresponding intensity threshold for the first gesture recognition criterion to be satisfied is in competition with a second gesture recognition criterion for a second gesture that depends on the contact(s) reaching a corresponding intensity threshold. In such competition, a gesture is optional and will not be recognized as satisfying the first gesture recognition criterion for the first gesture if the second gesture recognition criterion for the second gesture is first satisfied. For example, if a contact reaches the corresponding intensity threshold before it moves a predetermined amount, a deep press gesture will be detected instead of a swipe gesture. Conversely, if a contact moves a predetermined amount before it reaches the corresponding intensity threshold, a swipe gesture will be detected instead of a deep press gesture. Even in such situations, the first gesture recognition criterion for the first gesture still does not require the intensity of the contact(s) to meet the corresponding intensity threshold for the first gesture recognition criterion to be satisfied, because if the contact remains below the corresponding intensity threshold until the end of the gesture (e.g., a swipe gesture with a contact that does not increase to an intensity above the corresponding intensity threshold), the gesture is recognized as a swipe gesture by the first gesture recognition criterion.In this way, a particular gesture recognition criterion that does not require the intensity of a contact(s) to meet a corresponding intensity threshold for that particular gesture recognition criterion to be satisfied still depends on the intensity of the contact(s) with respect to the intensity threshold in some situations, and / or (B) in some situations, the particular gesture recognition criterion (e.g., for a long press gesture) does not function if a competing set of intensity-dependent gesture recognition criteria (e.g., for a deep press gesture) recognizes the input as corresponding to an intensity-dependent gesture before the particular gesture recognition criterion recognizes the gesture corresponding to the input (e.g., for a long press gesture competing with a deep press gesture for recognition).

[0081] The graphics module 132 includes various known software components for rendering and displaying graphics on the touch-sensitive display system 112 or other display, including components for modifying the visual effects of the displayed graphics (e.g., brightness, transparency, saturation, contrast, or other visual characteristics). As used herein, the term “graphics” includes, but is not limited to, any object that can be displayed to a user, including, text, web pages, icons (such as user interface objects including soft keys), digital images, videos, and animations.

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

[0083] The haptic feedback module 133 includes various software components that generate commands (for example, commands used by the haptic feedback controller 161) that create haptic outputs at one or more locations on the device 100 using a haptic output generator(s) 167, in response to user interaction with the device 100.

[0084] The text input module 134 is optionally a component of the 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 applications that require text input).

[0085] The GPS module 135 determines the device's location and provides this information for use in various applications (for example, to the phone 138 for location-based phone calls, to the camera 143 as metadata for photos / videos, and to applications that provide location-based services such as weather widgets, local yellow pages widgets, and map / navigation widgets).

[0086] Application 136 optionally includes the following modules (or instruction sets) or subsets or supersets thereof: ● Contact module 137 (sometimes called the address book or contact list), ●Telephone module 138, ●Video conferencing module 139, ● Email client module 140, ● Instant messaging (IM) module 141, ●Training support module 142, ● Camera module 143 for still images and / or video images, ●Image management module 144, ● Browser module 147, ● Calendar module 148, ● A widget module 149 that optionally includes one or more of the following: weather widget 149-1, stock price widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, other widgets obtained by the user, and user-created widgets 149-6. ●Widget creation module 150 for creating user-created widget 149-6, ● Search module 151, ● A video and music player module 152, which optionally consists of a video player module and a music player module. ●Memo Module 153, ●Map module 154 and / or ● Online video module 155.

[0087] Examples of other applications 136 that may be 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, speech recognition, and speech duplication.

[0088] Together with the touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the contact module 137 includes executable instructions for managing an address book or contact list (for example, stored in the application internal state 192 of the contact module 137 in memory 102 or memory 370), which include adding names(s) to the address book, deleting names(s) from the address book, associating telephone numbers(s) to names, email addresses(s) to names, physical addresses(s) to names, or other information; associating images to names; categorizing and sorting names; providing telephone numbers and / or email addresses to initiate and / or facilitate communication by telephone 138, video conferencing 139, email 140, or IM 141, and so on.

[0089] In conjunction with the RF circuit 108, audio circuit 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphic module 132, and text input module 134, the telephone module 138 includes executable commands for inputting a series of characters corresponding to a telephone number, accessing one or more telephone numbers in the address book 137, changing the entered telephone number, dialing each telephone number, conducting a conversation, and disconnecting or ending the call when the conversation is complete. As described above, the wireless communication may optionally use any of several communication standards, protocols, and technologies.

[0090] In conjunction with the RF circuit 108, audio circuit 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, the video conferencing module 139 includes executable commands to start, conduct, and end a video conference between the user and one or more other participants, in accordance with the user's commands.

[0091] In conjunction with the RF circuit 108, touch-sensitive display system 112, display controller 156, contact module 130, graphic module 132, and text input module 134, the email client module 140 includes executable commands for creating, sending, receiving, and managing emails in response to user commands. In conjunction with the image management module 144, the email client module 140 makes it extremely easy to create and send emails containing still or video images captured by the camera module 143.

[0092] In conjunction with the RF circuit 108, touch-sensitive display system 112, display controller 156, contact module 130, graphic module 132, and text input module 134, the instant messaging module 141 includes executable commands to input a series of characters corresponding to an instant message, modify previously entered characters, send each instant message (for example, using the Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for phone-based instant messaging, or using XMPP, SIMPLE, Apple Push Notification Service (APNs), or IMPS for internet-based instant messaging), receive instant messages, and view received instant messages. In some embodiments, sent and / or received instant messages optionally include graphics, photographs, audio files, video files, and / or other attachments, such as those supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephone-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs, or IMPS).

[0093] In conjunction with the RF circuit 108, touch-sensitive display system 112, display controller 156, contact module 130, graphic module 132, text input module 134, GPS module 135, map module 154, and video and music player module 152, the training support module 142 includes executable commands for creating training (e.g., having time, distance, and / or calorie consumption targets), communicating with training sensors (in sports devices and smartwatches), receiving training sensor data, calibrating sensors used to monitor training, selecting and playing music for training, and displaying, storing, and transmitting training data.

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

[0095] Together with the touch-sensitive display system 112, display controller 156, contact module 130, graphic module 132, text input module 134, and camera module 143, the image management module 144 includes executable commands for arranging, modifying (e.g., editing), or otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slideshow or album), and storing still and / or video images.

[0096] Together with the RF circuit 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the browser module 147 includes executable commands for browsing the internet in accordance with user commands, including searching, linking, receiving, and displaying web pages or parts thereof, as well as attachments and other files linked to web pages.

[0097] Together with the RF circuit 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, the calendar module 148 includes executable instructions that, in accordance with user commands, create, display, modify, and store a calendar and data associated with the calendar (e.g., calendar items, to-do lists, etc.).

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

[0099] In conjunction with the RF circuit 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget creation module 150 includes executable commands for creating widgets (for example, converting user-specified portions of a web page into widgets).

[0100] In conjunction with the touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the search module 151 includes executable instructions to search for text, music, sound, images, videos, and / or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) according to user commands.

[0101] In conjunction with the touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, and browser module 147, the video and music player module 152 includes executable commands that enable the user to download and play recorded music or other sound files stored in one or more file formats such as MP3 or AAC files, as well as executable commands to display, present, or otherwise play video (for example, on the touch-sensitive display system 112, or on an external display connected wirelessly or 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.).

[0102] In conjunction with the touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the memo module 153 includes executable commands that create and manage notes, to-do lists, and the like, according to user commands.

[0103] In relation to the RF circuit 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, the map module 154 includes executable commands for receiving, displaying, modifying, and storing maps and map-related data (e.g., driving directions, data about stores and other points of interest in a particular location or nearby, and other location-based data) in accordance with user commands.

[0104] In conjunction with the touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, email client module 140, and browser module 147, the online video module 155 includes executable instructions that enable a user to access, view, receive (e.g., by streaming and / or downloading), play (e.g., on the touchscreen 112, or on an external display connected wirelessly or via external port 124), send emails containing links to specific online videos, and otherwise manage them. In some embodiments, an instant messaging module 141 is used instead of the email client module 140 to send links to specific online videos.

[0105] Each of the modules and applications identified above corresponds to one or more of the functions described above, as well as an executable instruction set for performing the methods described in this application (e.g., methods performed by a computer and other information processing methods described herein). These modules (e.g., instruction sets) do not need to be implemented as separate software programs, procedures, or modules; therefore, various subsets of these modules may, at their discretion, be combined or otherwise rearranged in various embodiments. In some embodiments, memory 102 may, at its discretion, store a subset of the modules and data structures identified above. Furthermore, memory 102 may, at its discretion, store additional modules and data structures not described above.

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

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

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

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

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

[0111] The event monitor 171 receives event information from the peripheral interface 118. The event information includes information about sub-events (for example, a user touch on the touch-sensitive display system 112 as part of a multi-touch gesture). The peripheral interface 118 transmits information received from the I / O subsystem 106, or from sensors such as the proximity sensor 166, one or more accelerometers 168, and / or the microphone 113 (via the audio circuit 110). The information received by the peripheral interface 118 from the I / O subsystem 106 includes information from the touch-sensitive display system 112 or the touch-sensitive surface.

[0112] In some embodiments, the event monitor 171 sends requests to the peripheral interface 118 at predetermined intervals. In response, the peripheral interface 118 transmits event information. In other embodiments, the peripheral interface 118 transmits event information only when a significant event occurs (e.g., receiving input that exceeds a predetermined noise threshold and / or for a longer period than predetermined).

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

[0114] The hit view determination module 172 provides software procedures for determining where in one or more views a sub-event occurred when the touch-sensitive display system 112 displays two or more views. A view consists of control devices and other elements that the user can see on the display.

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

[0116] The hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views arranged in a hierarchy, the hit view determination module 172 identifies the hit view as the lowest-level view in the hierarchy from which the sub-events should be processed. In most situations, the hit view is the lowest-level view from which the initiating sub-event (e.g., the first sub-event in a sub-event sequence that forms an event or potential event) occurs. Once a hit view is identified by the hit view determination module, the hit view typically receives all sub-events related to the same touch or input source from which it was identified as a hit view.

[0117] The active event recognition determination module 173 determines which view(s) in the view hierarchy should receive a particular sequence of sub-events. In some embodiments, the active event recognition determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, the active event recognition determination module 173 determines that all views, including the physical location of the sub-event, are actively involved views, and therefore all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if the touch sub-event is entirely confined to an area associated with one particular view, higher-level views in the hierarchy still remain actively involved views.

[0118] The event dispatcher module 174 dispatches event information to an event recognition unit (e.g., an event recognition unit 180). In embodiments including an active event recognition unit determination module 173, the event dispatcher module 174 distributes the event information to the event recognition unit determined by the active event recognition unit determination module 173. In some embodiments, the event dispatcher module 174 stores the event information acquired by each event receiving unit module 182 in an event queue.

[0119] In some embodiments, the operating system 126 includes an event sorting unit 170. Alternatively, application 136-1 includes an event sorting unit 170. In yet another embodiment, the event sorting unit 170 is a standalone module or part of another module stored in memory 102, such as a contact / motion module 130.

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

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

[0122] The event receiving unit 182 receives event information from the event sorting unit 170. The event information includes information about sub-events, such as touches or the movement of touches. Depending on the sub-event, the event information also includes additional information such as the position of the sub-event. When the sub-event involves the movement of a touch, the event information also optionally includes the speed and direction of the sub-event. In some embodiments, an event includes the rotation of the device from one orientation to another (e.g., from portrait to landscape, or vice versa), and the event information includes corresponding information about the current orientation of the device (also called the device's orientation).

[0123] The event comparison unit 184 compares event information with a predefined definition of an event or sub-event, and based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, the event comparison unit 184 includes an event definition 186. The event definition 186 includes definitions of events (e.g., a default sequence of sub-events), such as event 1 (187-1) and event 2 (187-2). In some embodiments, sub-events in event 187 include, for example, touch start, touch cancellation, touch movement, touch abortion, and multiple touches. In one embodiment, the definition for event 1 (187-1) is a double tap on a displayed object. A double tap includes, for example, a first touch (touch start) for a predetermined stage on the displayed object, a first lift-off (touch end) for a predetermined stage, a second touch (touch start) for a predetermined stage on the displayed object, and a second lift-off (touch end) for a predetermined stage. In another embodiment, event 2(187-2) is defined as a drag on a displayed object. The drag includes, for example, touching (or contacting) a predetermined number of stages on the displayed object, moving the touch across the touch-sensitive display system 112, and lifting off the touch (end of the touch). In some embodiments, the event also includes information about one or more associated event processing units 190.

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

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

[0126] If an individual event recognition unit 180 determines that a series of sub-events does not match any of the events in the event definition 186, the individual event recognition unit 180 enters an event impossible, event failed, or event terminated state, and thereafter ignores subsequent sub-events of the touch-based gesture. In this situation, if there are other event recognition units that remain active for the hit view, those event recognition units continue to track and process the sub-events of the ongoing touch-based gesture.

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

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

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

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

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

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

[0133] Figure 2 shows a portable multifunctional device 100 having a touchscreen (e.g., a touch-sensitive display system 112, Figure 1A) according to several embodiments. The touchscreen optionally displays one or more graphics within a user interface (UI) 200. In these embodiments, and in embodiments described later, the user can select one or more graphics by making gestures on the graphics using, for example, one or more fingers 202 (not shown in the figure to an exact scale) or one or more styluses 203 (not shown in the figure to an exact scale). In some embodiments, the selection of one or more graphics is performed when the user interrupts contact with that one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and / or downward), and / or rolling of a finger in contact with the device 100 (from right to left, left to right, upward and / or downward). In some implementations or situations, accidental contact with a graphic does not constitute a selection of that graphic. For example, if the gesture corresponding to selection is a tap, a swipe gesture sweeping over an application icon does not arbitrarily select the corresponding application.

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

[0135] In some embodiments, device 100 includes a touchscreen display, a menu button 204 (sometimes referred to as a home button 204), a push button 206 for turning the device on / off and locking the device, one or more volume buttons 208, a subscriber identification module (SIM) card slot 210, a headset jack 212, and an external docking / charging port 124. The push button 206 is optionally used to turn the device on / off by pressing down and holding the button down for a predetermined period of time, to lock the device by pressing down and releasing the button before a predetermined period of time has elapsed, and / or to unlock the device or initiate an unlocking process. In some embodiments, device 100 also accepts verbal input through a microphone 113 to activate or deactivate certain functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of contact on the touch-sensitive display system 112, and / or one or more tactile output generators 167 for generating tactile output to the user of device 100.

[0136] Figure 3 is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface according to several embodiments. The device 300 does not have to be portable. In some embodiments, the 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 children's learning toy), a game system, or a control device (e.g., a home or commercial controller). The 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 for interconnecting these components. The communication buses 320 optionally include circuitry (sometimes called a chipset) that interconnects and controls communication between system components. The device 300 typically includes an input / output (I / O) interface 330, which includes a display 340, which is a touchscreen display. The I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350, as well as a touchpad 355, a tactile output generator 357 for generating tactile output on a device 300 (similar to the tactile output generator(s) 167 described above with reference to Figure 1A), and a sensor 359 (e.g., an optical sensor, an accelerometer, a proximity sensor, a touch sensor, and / or a contact intensity sensor (similar to the contact intensity sensor(s) 165 described above with reference to Figure 1A). The 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 memory devices. The memory 370 optionally includes one or more storage devices located remotely from the CPU(s) 310.In some embodiments, memory 370 stores programs, modules, and data structures similar to, or subsets thereof, that are stored in memory 102 of the portable multifunction device 100 (Figure 1A). Furthermore, memory 370 optionally stores additional programs, modules, and data structures that are not present in memory 102 of the portable multifunction device 100. For example, memory 370 of device 300 optionally stores a drawing module 380, a presentation module 382, ​​a word processing module 384, a website creation module 386, a disk authoring module 388, and / or a spreadsheet module 390, while memory 102 of the portable multifunction device 100 (Figure 1A) optionally does not store those modules.

[0137] Each of the elements identified in Figure 3 above is optionally stored in one or more of the previously mentioned memory devices. Each of the modules identified above corresponds to an instruction set that performs the function described above. The modules or programs (i.e., instruction sets) identified above do not need to be implemented as separate software programs, procedures, or modules; therefore, various subsets of those modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 370 optionally stores additional modules and data structures not described above.

[0138] Here, we focus on embodiments of a user interface ("UI") that are optionally implemented on the portable multi-functional device 100.

[0139] Figure 4A shows an exemplary user interface for an application menu on a portable multifunction device 100 according to several embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, the user interface 400 includes the following elements, or subsets or supersets thereof. ● Signal strength indicators (single or multiple) for wireless communication (single or multiple) such as cellular signals and Wi-Fi signals. ●Time, ●Bluetooth (registered trademark) indicator, ●Battery status indicator, ●Tray 408 containing icons for frequently used applications, as shown below. ○Optionally including an indicator 414 for the number of missed calls or voicemail messages, an icon 416 of the telephone module 138 labeled "Telephone", ○Optionally including an indicator 410 for the number of unread emails, an icon 418 of the email client module 140 labeled "Mail", ○ Icon 420 of browser module 147, labeled "Browser", ○ Icon 422 of video and music player module 152 labeled "Music", ● Icons of other applications, such as the following: ○ Icon 424 of IM module 141, labeled "Message", ○ Icon 426 of calendar module 148, labeled "Calendar", ○ Icon 428 of image management module 144, labeled "Photo" ○ Icon 430 of camera module 143, labeled "Camera" ○ Icon 432 of online video module 155, labeled "online video" ○ Icon 434 of stock price widget 149-2, labeled "Stock Price" ○ Icon 436 of map module 154, labeled "Map" ○ Icon 438 of weather widget 149-1, labeled "Weather" ○ Icon 440 of the alarm clock widget 149-4, labeled "Clock" ○ Icon 442 of training support module 142, labeled "Training Support" ○ Icon 444 of memo module 153, labeled as "Memo" ○ An icon 446 for a configuration application or module that provides access to settings related to device 100 and its various applications 136.

[0140] Please note that the icon labels shown in Figure 4A are merely examples. For example, other labels may be used selectively for various application icons. In some embodiments, the labels for individual application icons include the name of the application to which the individual application icon corresponds. In some embodiments, the label for a particular application icon is different from the name of the application to which that particular application icon corresponds.

[0141] Figure 4B shows an exemplary user interface on a device (e.g., device 300, Figure 3) having a touch-sensitive surface 451 (e.g., tablet or touchpad 355, Figure 3) separate from the display 450. Many of the following embodiments are given by reference to input on the touchscreen display 112 (when the touch-sensitive surface and the display are combined), but in some embodiments, the device detects input on the touch-sensitive surface separate from the display, as shown in Figure 4B. In some embodiments, the touch-sensitive surface (e.g., 451 in Figure 4B) has a principal axis (e.g., 452 in Figure 4B) corresponding to a principal axis (e.g., 453 in Figure 4B) on the display (e.g., 450). According to those embodiments, the device detects contact (e.g., 460 and 462 in Figure 4B) with the touch-sensitive surface 451 at positions corresponding to each of the positions on the display (e.g., 460 corresponds to 468 and 462 corresponds to 470 in Figure 4B). Thus, when the touch-sensitive surface is separated from the display, user input detected by the device on the touch-sensitive surface (e.g., 451 in Figure 4B) (e.g., touches 460 and 462, and their movement) is used by the device to operate the user interface on the display of the multifunction device (e.g., 450 in Figure 4B). It should be understood that a similar method may be optionally used for other user interfaces described herein.

[0142] In addition, while the following embodiments are given primarily with reference to finger input (e.g., finger touch, finger tap gesture, finger swipe gesture, etc.), it should be understood that in some embodiments, one or more of these finger inputs may be replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture may optionally be replaced by a mouse click (e.g., instead of touch), followed by a mouse click with cursor movement along the swipe path (e.g., instead of touch movement). As another example, a tap gesture may optionally be replaced by a mouse click (e.g., instead of touch detection and subsequent cessation of touch detection) while the cursor is located over the tap gesture position. Similarly, it should be understood that when multiple user inputs are detected simultaneously, multiple computer mice may optionally be used simultaneously, or mice and finger touch may optionally be used simultaneously.

[0143] In some embodiments, the gestures include air gestures. Air gestures are gestures detected without (or independently of) the user touching an input element that is part of a device (e.g., a computer system 101, one or more input devices 125, and / or a hand tracking device 140), and are based on detected movements of a part of the user's body in the air (e.g., head, one or more arms, one or more hands, one or more fingers, and / or one or more legs), including the user's body movement relative to an absolute reference (e.g., the angle of the user's arm relative to the ground, or the distance of the user's hand relative to the ground), the user's body movement relative to another part of the user's body (e.g., the user's hand movement relative to the user's shoulder, the movement of one of the user's hands relative to the user's other hand, and / or the movement of the user's fingers relative to another finger or part of the user's hand), and / or absolute movements of a part of the user's body (e.g., a tap gesture involving moving a hand in a predetermined pose by a predetermined amount and / or speed, or a shake gesture involving a predetermined speed or amount of rotation of a part of the user's body).

[0144] In some embodiments, the input gestures used in the various examples and embodiments described herein include air gestures, as in some embodiments, performed by the movement of the user's fingers(s) relative to other fingers(s) or parts of the user's hand(s) for interacting with an XR environment (e.g., a virtual or mixed reality environment). In some embodiments, an air gesture is a gesture detected without the user touching (or independently of) an input element that is part of the device, and is based on detected movement of a part of the user's body in the air, including movement of the user's body relative to an absolute reference (e.g., the angle of the user's arm relative to the ground, or the distance of the user's hand relative to the ground), movement of the user's body relative to another part of the user's body (e.g., movement of the user's hand relative to the user's shoulder, movement of one hand relative to the other, and / or movement of the user's fingers relative to another finger or part of the user's hand), and / or absolute movement of a part of the user's body (e.g., a tap gesture involving moving a hand in a given pose by a predetermined amount and / or speed, or a shake gesture involving a predetermined speed or amount of rotation of a part of the user's body).

[0145] In some embodiments where the input gesture is an air gesture (i.e., without physical contact with an input device that provides the computer system with information about which user interface element is the target of user input, such as contact with a user interface element displayed on a touchscreen or contact with a mouse or trackpad to move a cursor over a user interface element), the gesture takes into account the user's attention (e.g., gaze) to determine the target of user input (e.g., in the case of direct input, as described below). Thus, in implementations involving air gestures, the input gesture is the detected attention (e.g., gaze) to the user interface element in combination (e.g., simultaneously) with (e.g., simultaneous) movements of the user's fingers (one or more) and / or hand to perform pinch and / or tap input, as described in more detail below.

[0146] In some embodiments, input gestures directed towards a user interface object are performed directly or indirectly by reference to the user interface object. For example, user input is performed directly toward the user interface object in response to the user performing an input gesture with their hand at a position corresponding to the user interface object's location in a three-dimensional environment (e.g., determined based on the user's current viewpoint). In some embodiments, the input gesture is performed indirectly toward the user interface object according to the user performing the input gesture while the user's hand position is not at a position corresponding to the user interface object's location in a three-dimensional environment, while detecting the user's attention (e.g., gaze) toward the user interface object. For example, in the case of a direct input gesture, the user can direct their input toward the user interface object by initiating the gesture at or near a position corresponding to the user interface object's displayed position (e.g., within a distance of 0.5 cm, 1 cm, 5 cm, or 0-5 cm measured from the outer edge or central portion of an option). In the case of indirect input gestures, the user can direct their input towards a user interface object by paying attention to the user interface object (for example, by gazing at the user interface object), and while paying attention to the options, the user initiates an input gesture (for example, at any position detectable by the computer system) (for example, at a position not corresponding to the display position of the user interface object).

[0147] In some embodiments, the input gestures (e.g., air gestures) used in the various examples and embodiments described herein include pinch and tap inputs for interacting with virtual or mixed reality environments, as in some embodiments. For example, the pinch and tap inputs described later are performed as air gestures.

[0148] In some embodiments, a pinch input is part of an air gesture that includes one or more of the following: a pinch gesture, a long pinch gesture, a pinch-and-drag gesture, or a double pinch gesture. For example, a pinch gesture that is an air gesture involves moving two or more fingers of a hand to touch each other, i.e., including an optional interruption (e.g., within 0 to 1 second) immediately after the fingers touch each other. A long pinch gesture that is an air gesture involves moving two or more fingers of a hand to touch each other for at least a threshold time (e.g., at least 1 second) before detecting an interruption of contact between them. For example, a long pinch gesture includes the user holding a pinch gesture (e.g., if two or more fingers are in contact), and the long pinch gesture continues until an interruption of contact between the two or more fingers is detected. In some embodiments, a double pinch gesture that is an air gesture includes two (e.g., or more) pinch inputs (e.g., performed with the same hand) that are detected directly from each other (e.g., within a given period) in succession. For example, the user performs a first pinch input (e.g., a pinch input or a long pinch input), releases the first pinch input (e.g., breaks contact between two or more fingers), and then performs a second pinch input within a predetermined period (e.g., within 1 second or 2 seconds) after releasing the first pinch input.

[0149] In some embodiments, an air gesture, a pinch-and-drag gesture, includes a pinch gesture (e.g., a pinch gesture or a long pinch gesture) performed in relation to (e.g., after) a drag input that changes the position of the user's hand from a first position (e.g., the starting position of the drag) to a second position (e.g., the ending position of the drag). In some embodiments, the user maintains the pinch gesture while performing the drag input and releases the pinch gesture (e.g., spreading two or more fingers) to terminate the drag gesture (e.g., at the second position). In some embodiments, the pinch input and the drag input are performed by the same hand (e.g., the user pinches two or more fingers together and touches them to each other, and then moves the same hand to a second position in the air with the drag gesture). In some embodiments, the pinch input is performed by the user's first hand and the drag input is performed by the user's second hand (e.g., the user's second hand moves from the first position to the second position in the air while the user continues the pinch input with the user's first hand). In some embodiments, an input gesture that is an air gesture includes an input (e.g., a pinch input and / or a tap input) performed using both of the user's hands. For example, an input gesture includes two (e.g., or more) pinch inputs performed in relation to each other (e.g., simultaneously or within a given period of time). For example, a first pinch gesture (e.g., a pinch input, a long pinch input, or a pinch and drag input) performed using the user's first hand, and a second pinch input performed using the other hand (e.g., a second hand of the user's hands) in relation to performing a pinch input using the first hand. In some embodiments, this may include movement between the user's hands (e.g., to increase and / or decrease the distance or relative orientation between the user's hands).

[0150] In some embodiments, a tap input performed as an air gesture (e.g., directed towards a user interface element) includes the movement of one or more of the user's fingers toward the user interface element, the movement of the user's hand toward the user interface element with the user's fingers (one or more) optionally extended toward the user interface element, a downward movement of the user's fingers (e.g., mimicking a mouse click or a tap on a touchscreen), or any other predetermined movement of the user's hand. In some embodiments, a tap input performed as an air gesture is detected based on the movement characteristics of the finger or hand performing the tap gesture movement toward the object that is the target of the tap input, which is followed by the end of the movement. In some embodiments, the end of the movement is detected based on a change in the movement characteristics of the finger or hand performing the tap gesture (e.g., moving toward the object that is the target of the tap input, the end of the movement toward the object that is the target of the tap input, a reversal of the direction of the finger or hand movement, and / or a reversal of the direction of acceleration of the finger or hand movement).

[0151] As used herein, the term “focus selector” refers to an input element that indicates the current portion of the user interface with which the user is interacting. In some implementations, including a cursor or other location marker, the cursor functions as a “focus selector” such that when input (e.g., press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in Figure 3, or touch-sensitive surface 451 in Figure 4B) while the cursor is 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, including a touchscreen display (e.g., touch-sensitive display system 112 in Figure 1A, or touchscreen in Figure 4A) that enables direct interaction with user interface elements on the touchscreen display, contact detected on the touchscreen functions as a “focus selector” such that when input (e.g., press input by touch) 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 area of ​​the user interface to another without the movement of a corresponding cursor or touch on the touchscreen display (for example, by moving focus from one button to another using the tab key or arrow keys). In these implementations, the focus selector moves in accordance with the movement of focus between different areas of the user interface. Regardless of the specific form taken by the focus selector, the focus selector is generally a user-controlled user interface element (or touch on the touchscreen display) to communicate the user's intended interaction with the user interface (for example, by indicating to the device the user interface element that the user intends to interact with).For example, the position of a focus selector (e.g., cursor, touch, or selection box) over an individual button while pressure input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen) indicates that the user intends to activate that individual button (rather than other user interface elements displayed on the device's display).

[0152] User interface and related processes Here, we draw our attention to embodiments of user interfaces ("UI") and related processes that may be implemented on an electronic device such as a portable multifunction device 100 or device 300, comprising a display, a touch-sensitive surface, one or more tactile output generators for (optionally) generating tactile output, and one or more sensors for (optionally) detecting the intensity of contact with the touch-sensitive surface.

[0153] Figures 5A to 5CA show exemplary user interfaces for navigating and editing each type of user interface according to several embodiments; Figures 6A to 6AR show exemplary user interfaces for an extended face switcher; Figures 7A to 7V-3 show representations of multiple notifications in different configurations and user inputs for switching between different configurations; and Figures 8A to 8AN show exemplary user interfaces for displaying a session area of ​​an ongoing event according to several embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in Figures 9A to 9I, 10A to 10I, 11A to 11H, 12A to 12E, 13A to 13G, 14A to 14G, 15A to 15I, 16A to 16J, and 17A to 17D. For convenience of explanation, some embodiments are discussed with reference to operations performed on a device having a touch-sensitive display system 112. In such embodiments, the focus selector is optionally the contact of each finger or stylus, a representative point corresponding to the finger or stylus contact (e.g., the center of each contact or a point associated with each contact), or the center of two or more contacts detected on the touch-sensitive display system 112. However, similar operations are optionally performed on the display 450 and the device having separate touch-sensitive surfaces 451 in response to the detection of contact on the touch-sensitive surface 451 while displaying the user interface shown in the figure on the display 450.

[0154] Figures 5A to 5CA show exemplary user interfaces for navigating and editing each type of user interface according to several embodiments.

[0155] Figure 5A shows the user interface 500 of device 100 while the display of device 100 is in a low-power state. In some embodiments, while the display is in a low-power state, the “always-on” display optionally displays a time and / or date indication. In some embodiments, in the low-power state, the display of device 100 does not display any information (e.g., the display is off). In some embodiments, the display enters a low-power state after a predetermined inactive period in which no user interaction with device 100 has been detected. In some embodiments, the display enters a low-power state in response to user input to lock and / or sleep device 100, such as pressing a physical or virtual button on device 100. In some embodiments, the display of device 100 leaves the low-power state in response to the reception of an incoming alert (e.g., a system alert and / or a notification from an application). For example, the display of device 100 lights up to display an alert indication and then leaves the low-power state. In some embodiments, the display of device 100 lights up in response to user input such as user input detected on the display, user input of lifting the device, and / or user input on the device's physical or virtual buttons.

[0156] As used herein, a wake screen user interface is a user interface displayed after the display of device 100 enters a low-power state, during which time the display is at least partially off. In some embodiments, the wake screen user interface is also referred to herein as a face. For example, an action described as being performed with respect to a wake screen user interface may be described as being performed with respect to a face (e.g., “switching between wake screen user interfaces” may also be described as “switching between faces,” and “editing a wake screen user interface” may also be described as “editing a face”). In some embodiments, an “extended face switcher” user interface includes the display of one or more faces (e.g., one or more wake screen user interfaces), the size of each individual face (e.g., wake screen user interface) is smaller than the full size of the display area (e.g., as shown in Figure 5U). In some embodiments, in the low-power state, the display optionally displays “always-on” indicators for the time and / or date, and the device displays the wake screen user interface when prompted to exit the low-power state. In some embodiments, optionally, in response to user input and / or after a threshold time has elapsed, the device enters a locked state where a password, passcode, and / or biometric authentication is required to unlock the device, and in the locked state, its functionality is limited and it must be unlocked before accessing each application and / or data stored in the device 100. In some embodiments, a wake screen user interface is displayed regardless of whether the device is locked or already unlocked (for example, the wake screen user interface is displayed when the device is started before the user accesses the home screen user interface and / or other application user interfaces).In some embodiments, as used herein, the cover sheet user interface includes the same characteristics as the wake screen user interface, but the user can optionally view the cover sheet user interface without entering the device's locked state and / or low-power state. In some embodiments, one or more alerts (e.g., system alerts and / or notifications) are optionally displayed on the wake screen user interface and / or cover sheet user interface in response to user input (e.g., a swipe gesture upwards to the center of the display or another gesture).

[0157] As used herein, the home screen user interface includes icons for navigating to multiple applications run by device 100. In some embodiments, the user can interact with device 100 using one or more gestures, including touch input. For example, a tap input or other selection input on an individual application icon launches the individual application on the display area of ​​device 100 or otherwise opens the user interface of the individual application. In some embodiments, multiple views of the home screen user interface are available. For example, the user can swipe or otherwise navigate between multiple views, and each view of the home screen user interface includes different application icons for different applications. In some embodiments, the application icons are of different sizes, such as application widgets that display information about the individual application, and the application widgets are larger than the application icons.

[0158] As used herein, a mini-application object (or widget) is a user interface object that provides a limited subset of the functions and / or information available from their corresponding applications without requiring the application to be launched. In some embodiments, a mini-application object (or widget) contains application content that is dynamically updated based on the current context. In some embodiments, a tap input or other selection input on a mini-application object (widget) launches the corresponding application. In some embodiments, each mini-application object operates as a standalone application, separate from the associated application that resides in the device's memory. In some embodiments, each mini-application object operates as an extension or component of the associated application on the device. In some embodiments, each mini-application object has a dedicated memory portion for temporary storage of information. In some embodiments, the memory portion is accessible by the corresponding full-function application of each mini-application object. In some embodiments, a mini-application object is configured to perform a subset of the functions of the corresponding application, less than all of them. In some embodiments, a mini-application object displays an identifier for the corresponding application. In some embodiments, a mini-application object displays a portion of the content from the corresponding application. For example, a map mini-application object displays a portion of the map displayed in the map application corresponding to the map mini-application object. For example, a calendar miniapplication object displays a portion of the calendar as it appears in the corresponding calendar application. In some embodiments, a given input on the miniapplication object launches the corresponding application.In some embodiments, a mini-application object operates as a standalone application residing in the device's memory, distinct from the associated application that resides in the device's memory. For example, a mini-application object corresponding to a social networking application operates as a single-purpose or streamlined application having a subset of the corresponding application's features, but is associated with the full-featured social networking application. In this example, the mini-application object operates independently of the social networking application, and continues to operate in scenarios where the social networking application is not running. In some embodiments, a mini-application object operates as an extension or component of the associated application on the device. For example, a mini-application object for a calendar application is a single-function or operational component of the full-featured calendar application. In this example, neither the calendar mini-application object nor the calendar mini-application object operates if the calendar application is not running (e.g., in the background). In some embodiments, a mini-application object has a dedicated memory portion for temporary storage of information. In some embodiments, this memory portion can be accessed by the corresponding full-featured application. For example, a mini-application object for an instant messaging application has a memory portion for temporary storage of partially written reply messages. In this example, when a user opens the corresponding application while writing a reply message, the content of the reply message is retrieved from a temporary storage location and used by the fully functional application to allow the user to complete the reply message.

[0159] In some embodiments, an animation is displayed while the device wakes up and leaves a low-power state, transitioning the device from being off (e.g., optionally displaying a black background with the time and / or date of “always on”) to displaying the wake screen user interface 501 (also referred to herein as the lock screen user interface). In some embodiments, the wake screen user interface 501 is a user interface that includes a time and / or date indication, optionally one or more complications corresponding to and updated with the current status information of each application (e.g., training complication 502-1, weather complication 502-2, and calendar complication 502-3), optionally one or more alerts (e.g., message notification 503-1 and social media notification 503-2), optionally shortcuts to one or more applications (e.g., flashlight and / or camera), and a background (e.g., image, pattern, color, and / or photograph). In some embodiments, as will be described in more detail below, the user can change one or more settings of the wake screen user interface, for example, to change the font color and / or style of the time and / or date indication, and / or to change complications included in the wake screen user interface. In some embodiments, the device 100 stores a plurality of wake screen user interfaces and rotates through the plurality of wake screen user interfaces (optionally periodically and / or when entering / exiting a low-power state).

[0160] In some embodiments, the animation displayed to switch the device from off to display a wake screen user interface is based on the wake screen user interface being displayed. For example, Figures 5E to 5L show examples of different animated transitions to different wake screen user interfaces.

[0161] Figure 5B shows a wake screen user interface 501 with a gradient background, having dark gray at the top of the user interface background, medium gray in the middle of the user interface background, and light gray at the bottom of the user interface background. In some embodiments, user input is detected to replace the display of the wake screen user interface with a home screen user interface, the home screen user interface containing representations of multiple applications run by device 100.

[0162] In some embodiments, as shown in Figure 5C, in response to user input 504, the wake screen user interface 505 is displayed so as to slide up and out of the display area while maintaining one or more functions of the wake screen user interface (e.g., time and / or date, one or more complications, and / or indications of flashlight and camera shortcuts). In some embodiments, as the wake screen user interface slides out of the display area, the gradient background cycles as if on a carousel, with the dark gray that was at the top of the user interface background sliding up from the bottom of the screen, while the medium gray in the center of the user interface background slides up and out of the display, and the light gray slides up within the display area. In some embodiments, the gradient background completes a full cycle according to the displayed home screen user interface 506.

[0163] Figure 5D shows the home screen user interface 506 with a gradient background having different shades of gray arranged in the same layout as the wake screen user interface. Thus, the animation of shifting shades of gray completes its entire cycle as the user swipes up to navigate to the home screen user interface.

[0164] Figures 5E to 5F show examples of animated transitions during the transition of device 100 from a low-power state to displaying the wake screen user interface 507-2. For example, user interface 507-1 is an intermediate wake screen user interface displayed during the animated transition. In some embodiments, the intermediate wake screen user interface 507-1 does not include one or more features of the wake screen user interface 507-2 (e.g., no complications, notifications, and / or shortcuts to the flashlight or camera). In some embodiments, the wake screen user interface 507-2 includes an image such as multiple colored lines (e.g., a rainbow or a flag). In some embodiments, the animated transition includes increasing the size of the image. In some embodiments, the animated transition includes changing one or more font properties of the time and / or date indication. In some embodiments, the animated transition includes displaying one or more complications by optionally fading in one or more complications, and displaying one or more alerts by optionally fading in one or more complications.

[0165] Figures 5G to 5H show examples of animated transitions in wake screen user interface 508-2 that include a portrait-style photograph. In some embodiments, the portrait-style photograph includes a subject (e.g., a person and / or face) optionally displayed with a simulated depth effect so that the subject appears closer in the field of view than one or more background objects (e.g., clouds) in the photograph. In some embodiments, the animated transition of the wake screen user interface with a portrait-style photograph includes increasing the size of the subject from user interface 508-1 to wake screen user interface 508-2 and optionally displaying the subject with a time and / or date indication overlaid. In some embodiments, the animated transition includes applying a depth effect (e.g., the photograph appears flat in Figure 5G and appears with a depth effect in Figure 5H). In some embodiments, the wake screen user interface with a portrait-style photograph does not include one or more complications (optionally, the user can add one or more complications by editing the wake screen user interface).

[0166] Figures 5I to 5J show examples of animated transitions in a wake screen user interface 509-2 that include one or more emojis. In some embodiments, the wake screen user interface 509-2 includes one or more emojis arranged in a predetermined pattern. For example, in Figures 5I to 5J, smiley face emojis are displayed in a grid pattern. In some embodiments, the animated transition includes changing the shadow effect applied to a smiley face emoji, as shown in user interface 509-1, to a different shadow effect, as shown in wake screen user interface 509-2. In some embodiments, no shadow effect is displayed in at least one of user interfaces 509-1 or 509-2. For example, the size and / or opacity of the shadow may increase or decrease during the animation.

[0167] Figures 5K to 5L show examples of animated transitions of the wake screen user interface 510-2, including an astronomical background. In some embodiments, the astronomical background includes a celestial sphere and / or planetary bodies (e.g., Earth, Moon, stars, solar system, and / or galaxy). In some embodiments, the animated transition includes changing the trimming and / or changing the field of view of the astronomical background from user interface 510-1 to wake screen user interface 510-2. In some embodiments, the animated transition includes applying visual effects such as reducing and / or moving shadows displayed on the background. For example, the Earth appears to be rotating, and the shadow on the left side of the Earth appears to be rotating with the Earth, so the shadow is minimized to the right side of the user interface. In some embodiments, the astronomical background 510-2 further includes an indication of the device 100's current position (e.g., a dot is displayed on the Earth shown in user interface 510-2 at the device's position).

[0168] Figures 5L2-5L3 show examples of animated transitions from a wake screen user interface 510-3, which includes an astronomical background, to a home screen user interface 510-4, which also includes an astronomical background. In some embodiments, the wake screen user interface 510-3 includes representations of one or more celestial spheres, for example, the Earth and the Sun, as shown in Figure 5L2. In some embodiments, in response to user input 515 requesting to dismiss the wake screen user interface 510-3, the device 100 displays an animated transition and displays the home screen user interface 510-4. In some embodiments, the home screen user interface 510-4 is displayed with a background that includes one or more representations of celestial spheres different from the representations of celestial spheres displayed in the wake screen user interface 510-3. For example, as shown in Figure 5L3, during the animated transition, the representation of the Earth is displayed to rotate and shift to different parts of the display, and the representation of the Sun is displayed to shift in accordance with the rotation of the representation of the Earth. For example, the representation of the sun is shifted so that it appears relatively close to the representation of the earth, and / or so that it appears directly behind the representation of the earth (e.g., above and to the left, as shown in Figure 5L2). In some embodiments, during an animated transition, the representation of the earth is shifted to increase in size (e.g., to get closer), and the representation of the sun is resized in accordance with the increase in the size of the representation of the earth.

[0169] Figure 5M shows an example of the wake screen user interface 511. In some embodiments, the wake screen user interface 511 is an example of an astronomical background (e.g., including the moon). In some embodiments, the user can interact with the wake screen user interface 511 to cause the device 100 to perform various actions. For example, the wake screen user interface 511 includes a music complication 502-4, a health complication 502-5, a weather complication 502-6, and a breathing complication 502-7. In some embodiments, at least one complication is updated with status information corresponding to the application associated with the complication. For example, the music complication 502-4 is updated with progress information (e.g., circular, curved, or linear) indicating the amount of time the currently playing media item has been played, and the weather complication 502-6 is updated to show a real-time AQI level (e.g., "32") based on the state of the weather application.

[0170] In some embodiments, upon selecting a complication in response to a first type of user input, such as user input 512, the device 100 displays an application user interface for the application associated with the individual complication. In some embodiments, the first type of user input is a tap input. For example, in response to user input 512 for health complications 502-5, the device 100 displays a user interface for the health / fitness application associated with health complications 502-5.

[0171] In some embodiments, in response to a second type of user input 514, such as a swipe input or drag gesture in a first direction (e.g., up, down, right, or left) detected within a predetermined portion of the wake screen user interface 511 (e.g., within the center of the wake screen and / or on the edges of the wake screen), the device 100 displays a number of notifications, such as the user interface 532 shown in Figure 5O.

[0172] In some embodiments, the device displays the home screen user interface 518 in response to a third type of user input 516, such as a swipe input or drag gesture in a second direction (e.g., up, down, right, or left), which is optionally the same direction as a second type of user input 514. In some embodiments, the third type of user input 516 is received on a user interface element that, when selected (optionally, by initiating a swipe gesture on the user interface element), causes the device 100 to display the home screen user interface 518.

[0173] Figure 5N shows a home screen user interface 518 (also called the home user interface). In some embodiments, the home screen user interface includes icons for navigating to multiple applications run by the device 100. In some embodiments, the user can interact with the device 100 using one or more gestures, including touch input. For example, a tap input on an individual application icon (e.g., user input 524) launches the individual application on the display area of ​​the device 100 or otherwise opens the user interface of the individual application. In some embodiments, multiple views of the home screen user interface are available. For example, the user can swipe or otherwise navigate between multiple views, and each view of the home screen user interface includes different application icons for different applications. In some embodiments, the application icons are of different sizes, such as application widgets that display information about individual applications, and the application widgets are larger than the application icons.

[0174] In some embodiments, user input 520 is a swipe user input in a third direction (e.g., downward or another direction) that starts at the upper corner edge of the display of device 100. In some embodiments, in response to user input 520, device 100 displays a control user interface for changing one or more settings.

[0175] In some embodiments, user input 522 is a swipe user input in a fourth direction (e.g., right to left) and corresponds to a request to switch to a different view of the home screen user interface. For example, different views of the home screen user interface display different representations of different applications.

[0176] In some embodiments, user input 524 is a user input (e.g., a tap input or other selection input) that selects an application icon 422 for a music application. In some embodiments, in response to user input 524, device 100 displays the user interface of the application associated with the application icon 422 (e.g., a music application user interface).

[0177] In some embodiments, user input 525 (e.g., tap input or other selection input) on another application icon 440 for the clock application causes device 100 to open the clock application and display the user interface for the clock application.

[0178] In some embodiments, user input 526 is detected in a predetermined portion of the user interface (for example, a swipe-up gesture initiated at the edge of the device 100's display). In some embodiments, in response to user input 526, the device displays a multitasking user interface along with an indication of one or more open applications optionally running in the background on the device 100.

[0179] In some embodiments, different types of input, such as user input 528 (for example, a left-to-right swipe input initiated at the left edge of the device 100's display or with other gestures), cause device 100 to display a user interface including a search bar and, optionally, one or more widgets and / or shortcuts that display information about a subset of applications.

[0180] In some embodiments, user input 530 (for example, a downward swipe input initiated at the top edge of the device 100's display or with other gestures) is detected, and in response to the user input 530, a user interface 532 (Figure 5O) is displayed. Thus, the user can interact with the device 100 using different types of input and / or gestures to cause the device 100 to perform a set of actions, including opening applications, navigating between views of the home screen user interface, and accessing other user interfaces to change settings and / or access shortcuts.

[0181] Figure 5O shows a cover sheet user interface 532 that includes information also displayed on the wake screen user interface 511. For example, the user interface 532 optionally includes time and / or date indications, one or more complications, shortcut options to the flashlight and / or camera, and / or multiple notifications. In some embodiments, the user is enabled to interact with the user interface 532 in the same way that the user is enabled to interact with the wake screen user interface 511, such as via a tap input on a complication to open a separate application associated with the complication, or via a swipe input initiated at the right edge of the device 100's display, such as a user input 534 to display a user interface 536 (Figure 5P) about the camera application, and the user is enabled to capture and / or view photos using the camera application.

[0182] Figure 5P shows user input 538 corresponding to a request to return to the wake screen user interface. In some embodiments, in response to user input 538, user interface 540-1 is displayed as shown in Figure 5Q. In some embodiments, wake screen user interface 540-1 includes one or more properties that differ from wake screen user interface 511 (Figure 5M). In some embodiments, at least one complication is changed from wake screen user interface 511 to wake screen user interface 540-1. For example, music complication 502-4 (Figure 5M) is replaced with weather complication 502-9 (Figure 5Q) while optionally retaining one or more other complications (e.g., health complication 502-5, weather complication 502-6, breathing complication 502-7). In some embodiments, complications are updated according to the application status. For example, in Figure 5M, the weather complication 502-6 indicates an Air Quality Index (AQI) of 32, and in Figure 5Q, the weather complication 502-6 indicates an AQI of 30. In some embodiments, the background of the wake screen is maintained (e.g., an image of the moon).

[0183] In some embodiments, as shown in Figure 5Q, a user input 541, such as a right-to-left swipe input detected within a predetermined area of ​​the device 100's display (e.g., within a predetermined distance from the bottom edge of the display), causes the device 100 to cycle through wake screen user interfaces 540-1 to another wake screen user interface 540-2. In some embodiments, the device 100 cycles through a predetermined set of wake screen user interfaces. In some embodiments, the predetermined set of wake screen user interfaces is related. For example, in the case of an astronomy wake screen user interface (e.g., images of the moon), cycling through a predefined set of astronomy wake screen user interfaces includes displaying different phases of the moon. In some embodiments, a predetermined set of wake screen user interfaces is defined by the user so that the user selects the set of wake screen user interfaces to cycle through, regardless of whether a wake screen is related. For example, the user selects a photo album as a background image, and the wake screen user interface cycles through photos in the photo album or photos automatically selected by the device based on criteria specified by the user.

[0184] In some embodiments, the user swipes the wake screen user interface to change to the next wake screen user interface. In some embodiments, the wake screen user interface changes automatically at regular intervals (e.g., every two minutes, daily, or weekly). In some embodiments, the wake screen user interface changes automatically after the device enters and / or exits a low-power state (e.g., after the display is turned off, the wake screen user interface updates when the display next wakes up).

[0185] Figure 5R shows a wake screen user interface 540-2 that replaces wake screen user interface 540-1 in response to user input 541. In some embodiments, wake screen user interface 540-2 includes at least one feature that differs from wake screen user interface 540-1. For example, the font of the time and / or date indication is changed to a bold font, and the background image and background color are changed. In some embodiments, one or more other features of the wake screen user interface, such as the type of complication, remain unchanged. It will be understood that any combination of features, including a subset of the time and / or date indication, less than or all complication changes, and / or font properties, can be updated between the first wake screen user interface and the second wake screen user interface.

[0186] Figure 5R further illustrates user input 544 that responds to a request to switch to another wake screen user interface via a wake screen selector user interface. In some embodiments, user input 544 is a long press or other selection input, which maintains contact with the display for a predetermined threshold time (e.g., 2 seconds, 3 seconds, or 5 seconds) in a given portion of the user interface 540-2 (e.g., in a portion of the user interface that does not correspond to complications, shortcuts to the flashlight and / or camera, or time and / or date indications). In some embodiments, in response to user input 544, device 100 displays the wake screen selector user interface 548-1. In some embodiments, user input 544 maintains contact with the device while the wake screen selector user interface 548-1 is displayed, and the timing and / or position of the lift-off of user input 544 causes the device 100 to perform individual actions (for example, a long press released after a timer without changing position causes the device to display the augmented face switcher user interface 561 (Figure 5U), and a long press with a change in the position of contact (for example, swiping to an adjacent surface without lifting) causes the device to move to an adjacent wake screen user interface without entering the augmented face switcher user interface 561).

[0187] In some embodiments, upon determining that device 100 is in a locked state, before displaying the wake screen selector user interface 548-1, device 100 requires authentication to unlock the device and displays the passcode user interface 547, as shown in Figure 5S. In some embodiments, device 100 prompts the user to enter and / or authenticate a passcode using a fingerprint, face, or other biometric identification.

[0188] Figure 5T shows the wake screen selector user interface 548-1. In some embodiments, the wake screen selector user interface 548 includes representations of multiple wake screen user interfaces, including a partial representation 552 of a first wake screen user interface (e.g., wake screen user interface 540-1), a representation 550 of a second wake screen user interface (e.g., wake screen user interface 540-2), and a partial representation 554 of a third wake screen user interface (e.g., wake screen user interface 507-1 (Figure 5W)). In some embodiments, the wake screen selector user interface 548-1 displays representations of a set of wake screen interfaces that the device 100 stores and cycles through at its discretion, as described above.

[0189] In some embodiments, the wake screen selector user interface 548-1 provides multiple options for the user to interact with the representations of the wake screen user interfaces. For example, the user may request to add a new wake screen user interface to the set of wake screen user interfaces via user input 556 on the "+" button (e.g., tap input or other selection input).

[0190] In some embodiments, the user can select a different representation of the wake screen user interface and have the device 100 display the different wake screen user interface as the current wake screen user interface. For example, in response to user input 560, such as a tap input or other selection input, on or directed to the representation 550 of the second wake screen user interface, the device stops displaying the wake screen selector user interface 548-1 and redisplays the wake screen user interface 540-2 (Figure 5R). In some embodiments, in response to user input 558, such as a tap input or other input, the device scrolls to the right to bring representation 554 to the center of the wake screen selector user interface 548-2 (Figure 5V).

[0191] In some embodiments, according to a determination that a user input 544 (e.g., a long press user input held from the wake screen user interface 540-2 and displayed while the wake screen selector user interface 548-1 is shown) is maintained for a threshold time and lifted off without movement (e.g., a swipe to the left or right), the device 100 displays the extended face switcher user interface 561, as shown in Figure 5U.

[0192] Figure 5U shows that the augmented face switcher user interface 561 includes a representation of the wake screen user interface 550 (e.g., located in the center of the augmented face switcher user interface 561) and at least a portion of the representation of the home screen user interface 551 associated with the wake screen user interface representation 550. For example, one or more of the wake screen user interfaces have a corresponding separate home screen user interface. In some embodiments, changing the display of the wake screen user interface from a first wake screen to a second wake screen automatically updates the home screen user interface from a first home screen associated with the first wake screen to a second home screen associated with or corresponding to the second wake screen. Thus, depending on whether the user has navigated from the wake screen to the home screen (e.g., by swiping up or performing another gesture), the displayed home screen is related to the currently displayed wake screen. In some embodiments, the color, pattern, and / or image of the home screen is selected according to the color, pattern, and / or image of the wake screen to which the home screen is associated.

[0193] In some embodiments, the extended face switcher user interface 561 optionally also displays at least some representations 552 and / or representations 554 of other wake screen user interfaces. In some embodiments, only the currently central wake screen user interface of the extended face switcher user interface 561 is displayed along with its associated representation of the home screen user interface. For example, the wake screen user interface representations 552 and 554 are not displayed along with their corresponding representations of the home screen user interface.

[0194] In some embodiments, the augmented face switcher user interface 561 includes user-selectable buttons 564 for adding new wake screens and / or home screens to the set of wake screens and home screens stored and displayed in the augmented face switcher user interface 561. In some embodiments, the user is allowed to scroll left and / or right to navigate between wake screen and home screen options in the set of wake screens and home screens within the augmented face switcher user interface 561. In some embodiments, the augmented face switcher user interface 561 further includes user-selectable options 553 for customizing the wake screen located in the center of the augmented face switcher user interface 561. For example, user selection input in option 553 opens an editing user interface for the wake screen corresponding to representation 550 (e.g., the editing user interface 565 in Figure 5X). In some embodiments, the augmented face switcher user interface 561 includes an option 555 for changing the background image of the wake screen corresponding to representation 550. In some embodiments, in response to user selection input in option 555, a photo picker is displayed, allowing the user to select a photo or image to be used as the background of the wake screen corresponding to representation 550.

[0195] Figure 5V shows updating the wake screen selector user interface 548-1 to the wake screen selector user interface 548-2, thereby centering the wake screen user interface representation 554. In some embodiments, the wake screen selector user interface 548-2 is displayed in response to user input 558, such as a tap input or other selection input on representation 554, or a right-to-left swipe input or other scroll input, thereby causing the device to shift the wake screen user interface representations within its field of view to center the wake screen user interface representation 554 and move the previously centered wake screen user interface representation 550 to the left of the wake screen selector user interface 548-2 (optionally, sliding a portion of representation 550 from the display).

[0196] In some embodiments, the wake screen selector user interface 548-2 includes user-selectable options for editing the wake screen currently centrally located. For example, in response to user input 568 on the edit button (e.g., tap input or other selection input), the device 100 displays an edit user interface 565 for the wake screen, as shown in Figure 5X.

[0197] Figure 5W shows a wake screen user interface 563 that is displayed in response to user input (e.g., user input 562) that corresponds to a request to quickly switch the wake screen user interface. In some embodiments, the user input requesting to quickly switch the wake screen user interface includes a long press input (e.g., user input 544 in Figure 5R) initiated on the displayed wake screen user interface 540-2, which is maintained while the wake screen selector user interface 548-1 (Figure 5T) is displayed (e.g., the input contact continues), and while the long press input is in progress, the input changes position, such as user input 562 sliding from right to left (e.g., swiping in a first direction). In some embodiments, in accordance with the determination that the user input has lifted off, the wake screen displayed in the center of the wake screen selector user interface 548-1 is switched so that the wake screen is displayed as the current wake screen. For example, in Figure 5T, the user swipes left in the wake screen selector user interface 548-1 until the representation 554 is centered (or substantially centered), as shown in Figure 5W, and then lifts the user input to display the wake screen 563 associated with representation 554. In some embodiments, rapid switching of the wake screen user interface does not display the extended face switcher user interface 561.

[0198] In some embodiments, as shown in Figure 5W, the device 100 displays an edit user interface 565-a (Figure 5W1) or an edit user interface 563 (Figure 5X) in response to user input 564 for a time and / or date indication displayed on the wake screen user interface 565. In some embodiments, user input 564 is a tap input, a long press input, or another selection input. In some embodiments, the edit user interface 565-a shown in Figure 5W1 includes a reticle 572 for complications that is displayed behind or at least partially obscured by a subject in a background image (e.g., stars). In some embodiments, the reticle 572 is displayed in front of a subject in a background image (e.g., stars) in response to user interaction for editing one or more visual characteristics of the wake screen user interface, such as user input 571-a directed at the reticle 572.

[0199] Figure 5X shows an editing user interface 565 that can be accessed by user input 564 on the wake screen user interface 563, or by selecting an edit button via user input 568, as described above. In some embodiments, the editing user interface 565 is also accessible via a settings application on device 100, or optionally displayed in a share menu that appears in response to a user requesting to share a selected image (e.g., from a photos application) while the user is creating a wallpaper.

[0200] In some embodiments, the editing user interface 565 includes several reticles indicating customizable parts of the wake screen user interface. For example, reticles 568 around the date and 569 around the time indicate that the date and time are editable (e.g., text font and / or type of information displayed), and reticle 572 indicates that one or more complications are customizable (e.g., the user can add, delete, and edit complications displayed in the wake screen user interface 563). In some embodiments, there is an indication 574 that other views (e.g., pre-generated views that change the tone, apply visual effects, and / or change the background view) are available in the selected wake screen user interface 563. In some embodiments, the editing user interface 565 includes a user-selectable option 567 to cancel editing the wake screen user interface, and / or a user-selectable option to save changes to the wake screen user interface and (depending on the selection of the “Done” option 566) exit the editing user interface 565.

[0201] Figure 5X shows a user input 576, such as a tap input or other selection input, for adding complications to the wake screen user interface 563. In some embodiments, in response to the user input 576, the device displays a user interface element 570 containing a number of available and / or recommended complications that the user can add to the wake screen user interface 563, as shown in Figure 5Y. For example, in response to a user input 571 (e.g., a tap input or other selection input) selecting a recommended set of complications including a health complication, a breathing complication, and a calendar complication, the device optionally adds the set of complications to a given portion of the wake screen user interface under the time indication.

[0202] In some embodiments, the user interface element 570 includes multiple complications, each complication associated with an application running on the device 100. In some embodiments, an indication of the application associated with each complication (e.g., a "Calendar" application, a "Health" application, a "Weather" application, and a "Breathing" application) is displayed. In some embodiments, one application provides multiple complications (e.g., multiple options having different designs for complications for individual applications and / or displaying different status information). In some embodiments, a third-party provider providing individual applications is enabled to design one or more complications for individual applications (e.g., using an API). In some embodiments, each complication includes status information for the individual application. For example, the Calendar complication includes an approaching event ("11:00 AM event") stored on the user's calendar. In some embodiments, the Health complication includes an indication of the current training distance and / or daily activity level. In some embodiments, the weather application is associated with multiple complications, including a complication that provides the current air quality index (AQI) and / or a complication that indicates the current weather (e.g., sun for clear weather, or clouds with rain for rainy weather).

[0203] In some embodiments, the user can select one or more individual complications, as opposed to a recommended set, such as user input 574 selecting the calendar complication 502-10. In some embodiments, in response to user input 574, the device adds the calendar complication 502-10 to a predetermined area in the wake screen user interface for the complication, as shown in Figure 5Z. In some embodiments, the user can change the position of the predetermined area in the wake screen user interface (e.g., from below the time indicator to above the date indicator). In some embodiments, if there is additional space in the predetermined area, an indicator for adding a complication (e.g., button 572 and / or button 576) is optionally displayed. In some embodiments, the indicator for adding a complication is optionally displayed only if there is no complication in the predetermined area.

[0204] Figure 5Z shows user input 578 for selecting the health complication 502-11. Figure 5AA shows that, in response to user input 578, device 100 adds the health complication 503-11 to a predetermined area within the wake screen user interface for complications (for example, next to the calendar complication 503-10). In some embodiments, the user can change the position of the complications to position the health complication 503-11 to the left of the calendar complication 503-10, for example, as shown in Figures 5AA-5AB.

[0205] Figure 5AA shows a user input 580, such as a tap input or other selection input, for selecting the health complication 502-11. In some embodiments, the user input 580 further indicates moving the health complication 502-11 from right to left (e.g., via a drag gesture and / or swipe gesture). In some embodiments, in response to the user input 580, the complication is rearranged within the user interface 565, with the health complication 502-11 to the left of the calendar complication 502-10, as shown in Figure 5AB.

[0206] Figure 5AB shows user input 582 selecting a breathing complication 502-12 associated with a breathing application to remind the user to take deep breaths periodically from a set of complications displayed on user interface element 570. In some embodiments, user interface element 570 is scrollable so that the user can see additional complications available to add to the wake screen user interface.

[0207] Figure 5AC shows that, in response to user input 582, device 100 replaces the display of calendar complication 502-10 with breathing complication 502-12. In some embodiments, a predetermined area for displaying complications has a maximum size and / or maximum number of complications that can fit within the predetermined area. For example, the predetermined area can accommodate up to four complications of a first size (e.g., single-slot size) or two complications of a second size (e.g., each having a double-slot size). In some embodiments, in response to user input, one or more complications are automatically removed and complications are added to the predetermined area based on the determination that additional complications will not fit within the predetermined area. In some embodiments, in Figure 5AC, the user interface element 570 can be optionally minimized or closed. In some embodiments, the user can reopen the user interface element 570 by tapping or otherwise selecting a complication within the editing user interface 565.

[0208] Figure 5AD shows a user interface element 586 that appears in response to the detection of user input 584 at the current position within the reticle 569. In some embodiments, the user interface element 586 includes options for changing the characteristics of the time. For example, the user can change the text style (e.g., font, font size, and / or font color) and / or change how the time is displayed (e.g., as a 24-hour indication or as a 12-hour indication). In some embodiments, the reticle 568 around the date is optionally not displayed. In some embodiments, the text styles of both the date and time are updated in response to user input for changing the text style. In some embodiments, the user can select different text styles for the date and time.

[0209] In some embodiments, the user can change the color of the time. In some embodiments, a suggested color for the time is provided (for example, as shown in Figure 5AE). In some embodiments, the suggested color includes a vibrant material, black and / or white (for example, depending on the background color), and / or one or more colors derived from the background (for example, colors that match or complement the colors of the photograph used as the background). In some embodiments, the user can customize the color to select a different color not included in the suggested color applied to the time. In some embodiments, the user can customize the color by sampling a portion of the background, and the selected color matches the sampled portion of the background.

[0210] In some embodiments, in response to user input 588 selecting "Style 5", the date and time text style is updated and displayed in text style 5, as shown in Figure 5AE. In some embodiments, in response to user input 590, the text color is updated to the color selected by user input 590, as shown in Figure 5AE. In some embodiments, in response to a request to change the text color, the color scheme of one or more other wake screen user interface elements (e.g., one or more complications and / or background images) is also updated. For example, in Figure 5AE, the health complication 502-13 and the respiration complication 502-14 are displayed in different color schemes. In some embodiments, the complication colors are selected to match and / or complement the selected color of the text. Figure 5AE further shows user input 592 (e.g., tap input or other selection input) to optionally select the date indication without displaying a reticle 568 around the date. In some embodiments, in response to user input 592, a user interface element 594 is displayed for changing the type of information displayed in the date indication. In some embodiments, in response to user input 592, the reticle 568 is optionally redisplayed to indicate that the user has changed one or more properties of the date indication, as shown in Figure 5AF.

[0211] Figure 5AF shows user input 596 that selects to change the information displayed as a date indicator to include the day of the week (e.g., instead of the day of the week and the current month and day). In some embodiments, user interface element 594 optionally includes one or more text properties (e.g., font and / or color options) that the user can select to change the text properties of the date indicator (apart from, for example, changing the text properties of the time indicator as described above). Figure 5AG shows that in response to user input 596, the date indicator is updated to display the day of the week (e.g., "Friday") without displaying the current month and day. In some embodiments, user input 598 selects the complete option 566 to exit the edit user interface 565. In some embodiments, in response to user input 598 selecting the complete option 566, device 100 stops displaying the edit user interface 565 and displays a wake screen user interface 5001 with the properties selected by the user in the edit user interface, as shown in Figure 5AH.

[0212] Figure 5AI shows a portrait-style wake screen user interface 5001 that optionally includes multiple complications, including health complications 502-15, weather complications 502-16, respiratory complications 502-17, and sports complications 502-18, and includes a background photograph with a subject (e.g., an individual). In some embodiments, as described with reference to Figure 5H, the portrait-style wake screen user interface 5001 is displayed with a simulated depth effect.

[0213] In some embodiments, a wake screen user interface that includes a photograph as a background image (for example, the portrait-style background image shown in Figure 5AI) displays the photograph at an aspect ratio different from the aspect ratio of the stored photograph (for example, if stored in a photo application). For example, device 100 automatically centers, zooms, and / or crops the photograph stored in the photo application so that it can be displayed as the background of the wake screen user interface.

[0214] In some embodiments, a photo-style wake screen user interface, including the portrait-style wake screen user interface shown in Figure 5AI, includes a live photograph that is animated over time or optionally in response to user input on the wake screen user interface. For example, the photo-style wake screen user interface includes a number of interpolated frames so that the photograph appears animated (for example, to show the movement of an individual displayed on the wake screen user interface 5001).

[0215] In some embodiments, in response to a first type of user input 5002, for example, a tap input or press-and-hold input that exceeds a threshold time amount (e.g., at least 1 second, 3 seconds, or 5 seconds) that exceeds a time and / or date indication (or optionally exceeds the complications of multiple complications), the device 100 displays an editable user interface 565-2 for the wake screen user interface 5001.

[0216] As shown in Figure 5AJ, in some embodiments, the editing user interface 565-2 includes the same set of features as the editing user interface 565, e.g., date and / or time indicator reticles 568 and / or 569, a cancel option 567, a complete option 566, and an indicator 574 that additional views of the user interface are available. In some embodiments, a cropping indicator 5003 is optionally displayed to indicate that the background image of the wake screen user interface is resizable and / or scalable. In some embodiments, the cropping indicator 5003 optionally includes a text indicator such as "Pinch to Crop" to inform the user that a pinch gesture or other type of gesture will cause the device 100 to crop the photograph used as the background of the wake user interface 5001.

[0217] Figure 5AJ further illustrates the detection of a pinch gesture 5004 or other user input to change the cropping of the background photograph. In some embodiments, the pinch gesture 5004 includes two contact points that are spaced apart and / or close together. In some embodiments, an inward pinch gesture that brings the contact points closer together reduces the size of the subject in the background photograph (e.g., as if zooming out), and an outward pinch gesture that moves the contact points further apart increases the size of the subject in the background photograph (e.g., as if zooming in), and / or optionally crops the photograph. For example, pinch gesture 5004 is an outward pinch gesture that zooms in on the subject as shown in Figure 5AK, while pinch gesture 5006 (e.g., an inward pinch gesture) zooms out on the subject as shown in Figure 5AL.

[0218] In some embodiments, reticles 568 and / or 569 are optionally hidden while user input is detected to change the cropping of the background image. In some embodiments, the subject of a portrait-style user interface is optionally displayed with the time and / or date indication overlaid, according to the determination that the subject is sized such that it overlaps with part of the time and / or date indication. In some embodiments, the subject is optionally displayed as an overlay for multiple complications. In some embodiments, multiple complications are optionally displayed on the subject of a portrait-style wake screen user interface.

[0219] Figure 5AL shows user input 5008 for selecting reticle 569 for time indication. In some embodiments, in response to user input 5008, a user interface element 586 for editing the time indication is displayed. In some embodiments, user input 5010 is detected for changing the text style of the time and / or date indication to "Style 2". In some embodiments, in response to user input 5010, device 100 changes the time and optionally date indication to be displayed in text style "Style 2", as shown in Figure 5AN.

[0220] Figure 5AN shows a user input 5012 corresponding to a request to minimize or close the user interface element 586. In some embodiments, the user input 5012 includes a swipe-down gesture or another input to select the close option.

[0221] Figure 5AO shows the edit user interface 565-2 after the user interface element 586 has been minimized or closed in response to user input 5012. In some embodiments, multiple views of the wake screen user interface are available, as indicated by indicator 574. In some embodiments, each view of the multiple views optionally corresponds to a different set of visual characteristics without changing the content of the background of the wake screen user interface. For example, in the case of an emoji-style wake screen user interface, the multiple views include different patterns or arrangements of one or more selected emojis used in the background, and / or changes in the color effects (e.g., monochrome, sepia, or neon) and / or shadow levels displayed with the emojis in the background of the wake screen user interface. In some embodiments, in the case of a portrait-style wake screen, or other wake screen user interfaces that include a photograph as the background image, the multiple views include background images with different visual effects applied (e.g., grayscale, sepia, or another filter). In some embodiments, in the case of an astronomy-style wake screen, the multiple views include different versions of the background image, e.g., different phases of the moon.

[0222] In some embodiments, the available views optionally include different sets of complications, different styles of text for time and / or date indications (e.g., including font style and / or color), and / or different background colors for photographs (e.g., replacing the background color while maintaining the subject in the photograph). In some embodiments, the views are views that are automatically generated and / or selected by device 100 without user input.

[0223] In some embodiments, a user can view multiple views by scrolling through the view while the device 100 displays the edit user interface 565-2. Figure 5AO shows a user input 5014-1, such as a swipe input or other input (e.g., tapping on different sides of the user interface to scroll in different directions). In some embodiments, the user input 5014-1 is initiated by a contact detected at a first position, and the contact moves in a first direction (e.g., from right to left or from left to right). In some embodiments, according to a user input 5014-1 that optionally follows in the same direction as the user input 5014-2, the device 100 updates the view of the edit user interface to display at least a portion of a second view of the wake screen user interface. In some embodiments, the portion of the second view is gradually displayed as if the second view were sliding on the display, while the first view is gradually removed from the display as if it were sliding off the display.

[0224] Figure 5AP shows a portion of the second view sliding on the display while the first view slides off the display. In some embodiments, one or more visual elements in the first view are optionally maintained in both the first and second views. In some embodiments, the one or more visual elements that are optionally maintained do not move within the user interface. In some embodiments, the one or more maintained visual elements correspond to visual elements of the wake screen user interface that the user has previously modified (e.g., in the current editing session and / or a previous editing session). For example, the user has changed the date and time indicator, and the user has resized the subject in the background photo. In some embodiments, the date and time indicator and the subject in the background photo do not move while the second view slides on the display. In some embodiments, a set of visual elements that were not optionally modified by the user in the current editing session and / or a previous editing session move off the display with the first view and are replaced by another set of visual elements. For example, complications and background colors appear to slide off the display according to user input 5014-2.

[0225] Figure 5AQ shows user input 5014-3 swiping in the opposite direction to user input 5014-2. In some embodiments, user input 5014-3 is optionally a continuation of user inputs 5014-1 and 5014-2, and user input 5014-3 changes to swiping in a different direction while maintaining contact with the display. In some embodiments, the portion of the second view that was sliding on the display in Figure 5AP moves in the opposite direction according to user input 5014-3. Thus, user inputs 5014 (e.g., 5014-1, 5014-2, and 5014-3) control bringing the view onto the editing user interface 565-2 and / or removing the view from the editing user interface 565-2.

[0226] Figure 5AR optionally shows user input 5014-4 as a continuation of user input 5014-3, swiping in the same direction as user interface 5014-2 to slide the second view of the wake screen user interface onto the display. In some embodiments, as shown in Figure 5AS, if user input 5014-5 continues to be swiped from right to left, optionally, as shown in Figure 5AT, a large portion of the second view of the wake screen user interface slides onto the display until the second view of the wake screen user interface is displayed on the editing user interface 565-2 without displaying the first view of the wake screen user interface.

[0227] Figure 5AT shows a second view of the wake screen user interface, where the complications are modified compared to the first view of the wake screen user interface, and / or the background color of the second view is changed. In some embodiments, the background color(s) selected for a view in the portrait-style wake screen user interface is selected based on the content in the photograph. For example, the original background of the photograph is replaced with a single color or color gradient, and the color(s) are selected to match and / or complement the colors displayed in the original background of the photograph and / or the subject(s) in the portrait-style wake screen user interface.

[0228] In some embodiments, while the user is switching views of the wake screen user interface (e.g., via user input 5014), one or more editing options are optionally hidden. For example, the reticle, the complete option, the cancel option, and / or indicators for additional views are optionally hidden until a single view is displayed. For example, in Figure 5AT, the second view is displayed, the first view is no longer displayed, and one or more editing options are redisplayed.

[0229] In some embodiments, user input 5016 is detected on a complication displayed in a second view of the editing user interface 565-2. In some embodiments, in response to user input 5016, a user interface element 570 for changing the complication is displayed, as shown in Figure 5AU. In some embodiments, user input 5018 selects a health complication, and device 100 replaces the display of the weather complication with the selected health complication.

[0230] Figure 5AV shows user input 5020 requesting to switch views in the editing user interface after editing a complication.

[0231] Figure 5AW shows that, in response to user input 5020, the view switches from the second view to the third view (e.g., with a different background color and / or pattern) according to each of these features manually edited by the user during the current (or optionally, previous) editing session, without changing the time indication, date indication, subject, or complication. Figure 5AW shows user input 5022, where the user selects the "Done" option to exit the editing user interface.

[0232] Figure 5AX shows the wake screen user interface 5024, which is displayed along with the visual features selected by the user during the editing process.

[0233] Figure 5AX2 shows an editing user interface 565-3 for editing a wake screen user interface that includes date text indications, time text indications, and multiple complications. In some embodiments, each complication is displayed along with an affordance for removing the complication. For example, a minus sign, "x," or other removal affordance may be displayed at the corners of a complication that optionally partially overlaps with it.

[0234] In some embodiments, device 100 detects user input 5080 (e.g., tap input or other selection input) to select a complication 5089-1. In some embodiments, in response to user input 5080, device 10 displays a user interface element 5082 for resizing the selected complication 5089-1. For example, device 100 provides multiple size options for displaying information about the complication 5089-1. In some embodiments, the multiple size options correspond to different text sizes. In some embodiments, user input 5084 is detected as selecting a first size option for the complication 5089-1, and in response to the user input, the complication 5089-1 is updated to the selected size, as shown in Figure 5AX4.

[0235] Figure 5AX3 shows a device 100 that detects user input 5086 to select an affordance for removing complication 5089-2. In some embodiments, in response to user input 5086, complication 5089-2 is removed from the wake screen user interface, as shown in Figure 5AX4.

[0236] Figure 5AX3 further illustrates user input 5088 corresponding to the selection of a reticle for a date character indication. In some embodiments, in response to user input 5088, device 100 displays a user interface element 5090 for changing the content displayed in the area above the time character indication. For example, the user can select a complication from several complications displayed in the user interface element 5090. In some embodiments, the complication that the user can select to display above the time character indication is a different set of complications from the set of complications that the user can select to display below the time character indication (for example, the set of complications displayed in the user interface element 570, as described with reference to Figures 5AA to 5AC). For example, the complication that displays above the time character indication is a text-based complication and / or has a different size (e.g., height and / or length) from the complication that displays below the time character indication.

[0237] Figure 5AX4 shows user input 5092 for selecting a complication to be displayed on top of the time text indication. In some embodiments, depending on user input 5092, the selected complication is displayed on the reticle 5094 above the time text indication, as shown in Figure 5AX5, replacing the display of the date text indication. In some embodiments, the user can select a complication to be displayed on top of the time and / or a different set of information to be displayed, as described with reference to Figure 5AF. For example, device 100 optionally displays the content of user interface element 594 (Figure 5AF) and the content of user interface element 5090 so that the user can select text information and / or a complication to be displayed on top of the time indication. Figures 5AY to 5BD show another example of editing a wake screen user interface, including switching between multiple views of individual wake screen user interfaces within an editing user interface. Figure 5AY shows device 100 displaying the wake screen user interface 5026 and receiving user input 5028 for selecting a calendar complication. In some embodiments, if user input 5028 is a first type of input (e.g., tap input or other selection input), device 100 displays an application user interface (e.g., a calendar application) for the application associated with the selected complication. In some embodiments, if user input 5028 is a second type of input (e.g., long press or another gesture), device 100 displays an editing user interface 565-3 for editing the visual features of the wake screen user interface 5026.

[0238] Figure 5AZ shows a user interface element 570 for editing a complication displayed in the editing user interface 565-3 in response to user input 5028. In some embodiments, user input 5030 for minimizing or closing the user interface element 570 is detected without detecting user input for optionally changing or selecting a complication. In some embodiments, user input 5032 is detected as selecting a complication (e.g., a weather complication) from the user interface element 570, and device 100 updates the wake screen user interface to include the selected complication before minimizing the user interface element 570.

[0239] Figure 5BA shows the edit user interface 565-3 after the user interface element 570 has been minimized or closed. In some embodiments, user input 5034 is detected to change the current view of the wake screen user interface. In some embodiments, user input 5034 is a swipe gesture (e.g., left to right or right to left). In some embodiments, in response to user input 5034, the edit user interface 565-3 displays a second view of the wake screen user interface.

[0240] Figure 5BB shows a second view of the wake screen user interface. In some embodiments, the background image of the wake screen user interface, for example, in the case of the astronomy wake screen user interface, includes different phases of the moon in different views of the wake screen user interface. In some embodiments, the color palette or other virtual effects change between different views of the wake screen user interface. In some embodiments, the second view of the wake screen user interface includes different text styles for date and / or time indications. In some embodiments, a subset of complications, less than all of them, is updated from the first view to the second view. For example, complications manually selected by the user (e.g., weather complications) do not change between the first and second views, but other complications do. In some embodiments, an animated transition is displayed while changing the display from the first view to the second view, such as a sliding animation as described with reference to Figure 5AP.

[0241] In some embodiments, in response to user input 5036 (for example, swiping the user input in the opposite direction to user input 5034) that corresponds to a request to redisplay the first view of the wake screen user interface, the first view of the wake screen user interface is redisplayed in the edit user interface 565-3, as shown in Figure 5BC.

[0242] In some embodiments, in response to detecting a user input such as user input 5034 in a different direction from user input 5038, device 100 displays a third view of the wake screen user interface, as shown in Figure 5BD. In some embodiments, the third view of the wake screen user interface optionally displays a different phase of the moon and / or optionally displays the same complications as the first view of the wake screen user interface.

[0243] In some embodiments, in response to user input 5040 selecting the “Done” option, device 100 stops displaying the edit user interface 565-3 and displays a view of the wake screen user interface that is displayed while user input 5040 is detected as the current wake screen user interface.

[0244] Figures 5BE to 5BF illustrate examples of navigation from the wake screen user interface to the home screen user interface. In some embodiments, in response to user input 5042 requesting navigation from the wake screen user interface 5041 to the home screen user interface (e.g., a swipe input initiated on the home icon, or other selection input such as on the home button), the device 100 displays an animated transition 5043 in which the wake screen user interface is animated to optionally slide upward from the display, and the wake screen user interface is visually de-emphasized (e.g., by using a blur effect and / or by changing the level of translucency). In some embodiments, one or more application icons on the home screen user interface are optionally animated to enter the display and / or are at least partially visible behind the wake screen user interface that is not visually emphasized during the animation.

[0245] Figures 5BG to 5BH illustrate examples of navigation from the wake screen user interface to the application user interface. In some embodiments, in response to a request to navigate away from the wake user interface (e.g., via user input 5042 and / or user input 5044), the displayed user interface is based on the user interface displayed before the wake screen user interface was displayed (e.g., before entering a low-power state and / or lock mode). For example, if the device 100 displays the application user interface as the last displayed user interface before entering a low-power state and / or lock mode, the previously displayed application user interface will be redisplayed in response to user input requesting to navigate away from the wake screen user interface 5041. Similarly, in some embodiments, if the device 100 displays the home screen user interface as the last displayed user interface before entering a low-power state and / or lock mode, the previously displayed home screen user interface will be redisplayed in response to user input requesting to navigate away from the wake screen user interface 5041.

[0246] In some embodiments, in response to a user input 5044 requesting to navigate from the wake screen user interface 5041 to the home screen user interface (e.g., a swipe input initiated on the home icon, or other selection input such as on the home button), the device 100 displays an animated transition 5045 in which the wake screen user interface is optionally not visually de-emphasized, or is visually de-emphasized in a different way than the animated transition 5043 (e.g., having different blurring effects and / or different levels of translucency), and the wake screen user interface is optionally animated to slide upwards from the display. In some embodiments, the user interface of an application is optionally displayed in the portion of the display not covered by the wake screen user interface as it slides away from the display.

[0247] Figure 5BI shows a home screen user interface 5046. In some embodiments, the home screen user interface 5046 includes one or more application icons and is displayed along with a background image. In some embodiments, the background image displayed in the home screen user interface 5046 is at least partially based on the wake screen user interface that the user has navigated to. For example, if the wake screen user interface 5041 includes a star image as its background, the associated home screen user interface 5046 also includes a star image. In some embodiments, the home screen and wake screen backgrounds do not need to share content, but individual home screens are associated with and stored with individual wake screens so that when the current wake screen changes from a first wake screen to a second wake screen, the home screen displayed in response to user input on the individual wake screen is associated with the individual wake screen.

[0248] Figure 5BI shows user input 5048 corresponding to a request to optionally view a cover sheet user interface that includes the same visual features as the wake screen user interface. In some embodiments, user input 5050 is detected on a power button (e.g., push button 206) that puts the device 100 into a low-power state and / or lock mode. In some embodiments, when the device 100 is woken up from the low-power state and / or lock mode, the wake screen user interface 5041 is optionally redisplayed. In some embodiments, when the device 100 is woken up from the low-power state and / or lock mode, the wake screen user interface is updated to the next wake screen user interface in the stored set of wake screen user interfaces (e.g., the device 100 optionally cycles through the stored set of wake screen user interfaces periodically and / or during waking).

[0249] Figure 5BJ shows a user input 5051, which is a swipe user input in a first direction (e.g., left to right or right to left) at the user's discretion. In some embodiments, the user input 5051 is detected within a predetermined area of ​​the wake screen user interface 5041. In some embodiments, the input within a predetermined area of ​​the wake screen user interface 5041 causes the device 100 to change to a different wake screen user interface. For example, as shown in Figure 5BK, the wake screen user interface is updated to display the wake screen user interface 5052.

[0250] In some embodiments, after the wake screen user interface is updated to the wake screen user interface 5052, user input 5054 is detected requesting to navigate away from the cause of the wake screen user interface. In some embodiments, in response to user input 5054, the device 100 displays the home screen user interface 5056 associated with the wake screen user interface 5052.

[0251] Figure 5BL shows that, similar to the home screen user interface 5046 (Figure 5BI), the user can interact with the home screen user interface. For example, user input 5058 causes device 100 to display a cover sheet user interface (e.g., having the visual characteristics of the wake screen user interface 5052), and user input 5060 causes device 100 to enter a low power state and / or lock mode.

[0252] Figures 5BM to 5BN show examples of user input for selecting a complication displayed on the wake screen user interface 5062. In some embodiments, user input 5064 is a tap input or other selection input on a breathing complication, causing device 100 to display an application user interface for the breathing application associated with the breathing complication. In some embodiments, user input 5066 (e.g., a tap input or other selection input) is detected on a weather complication, and in response to user input 5066, device 100 displays an application user interface 5068 for the weather application associated with the weather complication, as shown in Figure 5BN. In some embodiments, before displaying the individual application user interfaces associated with the selected complication, device 100 optionally requires the user to unlock the device (e.g., using biometric authentication and / or a passcode).

[0253] Figures 5BO to 5BP show examples of animated transitions during the transition of device 100 from a low-power state to displaying a wake screen user interface 5070-2. For example, user interface 5070-1 is displayed on an always-on (or dimmed) display (e.g., in a low-power state). In some embodiments, user interface 5070-1 includes multiple colored stripes (or lines) that are animated when the device transitions between different user interfaces. For example, the colored stripes are representations of ribbons, ropes, strings, or fabrics. In some embodiments, each stripe is a different color (e.g., a rainbow or a flag). In some embodiments, the colored stripes are arranged as if they were wrapped around an object such as a cylinder. In some embodiments, the animated transition includes increasing the size of the stripes and / or decreasing the distance between the stripes. For example, in Figure 5BO, each of the colored stripes is a first size, and there is space between the stripes. In some embodiments, according to a device 100 that rejects a low-power state to display the wake screen user interface 5070-2 of Figure 5BP, the stripes are animated to come together (for example, so that there is no space between the stripes or the space is reduced), and the size of the stripes increases to a second size which is larger than the first size.

[0254] Figures 5BQ to 5BS illustrate examples of animating a background containing colored stripes in response to one or more user inputs. In some embodiments, device 100 detects a user input 5072 (e.g., a swipe input in a first direction or other input). In some embodiments, in response to the user input 5072, the colored stripes are animated to be pulled in the same direction (or opposite direction) as the user input 5072. For example, if the user input 5072 moves upward, the colored stripes are animated to move upward, while optionally appearing wrapped around an object (e.g., a cylinder). In some embodiments, the animation includes decreasing the size of one or more of the colored stripes and / or increasing the distance between at least two of the colored stripes. In some embodiments, the topmost stripe is animated to separate from its adjacent stripes and increase its distance from them. For example, the topmost stripe first separates from the set of stripes, then a second topmost stripe separates from the remaining stripes, optionally separating until space exists between each of the stripes in the set of stripes. For example, in Figure 5BR, the top three stripes are shown separated from the remaining bottom three stripes in the set of stripes, as indicated by the black space.

[0255] In some embodiments, the animation is displayed according to user input 5072. For example, in Figure 5BR, user input 5074 is detected as being in the opposite direction to user input 5072. For example, user input 5074 is a downward swipe input, and user input 5072 is an upward swipe input. In some embodiments, the wake screen user interface 5070-3 is not rejected according to the determination that user input 5072 does not meet the rejection criteria, and the animation is reversed according to user input 5074, as shown in Figure 5BS. For example, in Figure 5BS, the stripes are larger in size compared to the stripes in Figure 5BR, and the top stripe is shifted downward to eliminate the distance between sets of stripes. In some embodiments, the top stripe is the last stripe to recombine the set of stripes. In some embodiments, after detecting user input 5074, user input is no longer detected, for example, in response to a lift-off 5076 of user input. In some embodiments, the reverse animation continues until the wake screen user interface 5078 returns to its original state (for example, the state shown in Figure 5BQ before detecting user input 5072), as shown in Figure 5BT.

[0256] Figure 5BU shows a user input 5080-1, such as an upward swipe input. In some embodiments, the user input 5080-1 satisfies rejection criteria for rejecting the wake screen user interface 5070-7. For example, the rejection criteria are satisfied according to a determination that the user input 5080-1 satisfies a threshold swipe speed and / or threshold swipe distance. For example, the rejection criteria are satisfied according to user input 5080-2 (e.g., a continuation of input 5080-1) that continues to be detected as the user continues to swipe upward. In some embodiments, in response to the user input 5080-1, the device 100 displays an animation described with reference to Figure 5BR, which includes separating the colored stripes and / or reducing the size of the colored stripes.

[0257] In some embodiments, in accordance with the determination that user input 5080 (including, for example, user input 5080-1 and user input 5080-2) meets the rejection criteria, device 100 displays a full animation when device 100 transitions from displaying the wake screen user interface 5070-7 to displaying the home screen user interface 5070-10. In some embodiments, as shown in Figure 5BW, an intermediate user interface 5070-9 is displayed which includes colored stripes moving and twisting on top of (for example, around an invisible object such as a cylinder), while the colored stripes are displayed separated as indicated by black space between the stripes and / or displayed with a smaller width than the stripes displayed in the wake screen user interface 5070-7.

[0258] In some embodiments, after displaying an animation of the stripe twisting and moving upward, the stripe is displayed with a smaller width as the background of the home screen user interface 5070-10, which also includes one or more application icons in the foreground, as shown in Figure 5BX, and optionally displayed with the narrowest width during the animation. In some embodiments, the stripe displayed in the background of the home screen user interface 5070-10 is optionally displayed with the same width as the stripe displayed in the background of the wake screen user interface 5070-7 (Figure 5BU), and optionally displayed shifted upward from the stripe displayed in the wake screen user interface 5070-7. For example, the stripe is the same size as the background of the home screen user interface 5070-10 but is displayed in a different position compared to the stripe in the background of the wake screen user interface 5070-7.

[0259] Figures 5BY and 5BZ illustrate an example of changing the orientation of the stripes in wake screen user interface 5070-11 to wake screen user interface 5070-12. For example, the direction in which the stripes wrap around invisible objects is updated to the reverse direction (e.g., clockwise or counterclockwise). In some embodiments, the orientation of the stripes in wake screen user interface 5070 is selected according to user input. For example, the user is provided with the option to select the orientation of the stripes used as the background of the wake screen user interface. In some embodiments, the orientation of the stripes is determined automatically without user input. In some embodiments, the orientation of the stripes is periodically alternated, for example, each time the wake screen user interface is invoked, the orientation of the stripes changes from the previous orientation that was displayed before the wake screen user interface was invoked. For example, during lock and unlock cycles and / or when a low-power state is rejected, the wake screen user interface alternates the orientation of the stripes.

[0260] Figures 5CA to 5CB show an example of changing the background color of the wake screen user interface 5070-13 to 5070-14. In some embodiments, the background color of the wake screen user interface is automatically selected according to the current operating mode of device 100. For example, while device 100 is in a first operating mode, such as bright mode, the background is selected for bright operating mode (e.g., a white background is selected), as shown in Figure 5CA. In some embodiments, while device 100 is in a second operating mode, such as dark mode, the background is selected for dark operating mode (e.g., a black background is selected), as shown in Figure 5CB. In some embodiments, the current operating mode is selected according to time (e.g., bright mode during the daytime and / or a predetermined time period (e.g., from 6 a.m. to 8 p.m., or another period) and dark mode outside of nighttime and / or a predetermined time period (e.g., from 8 p.m. to 6 a.m.)). In some embodiments, the user is provided with the option to manually select the background color.

[0261] Figure 6A illustrates the detection of user input 602 (e.g., tap input, long press input, or other selection input) on the wake screen user interface 600. In some embodiments, user input 602 is detected in portions of the wake screen user interface 600 that do not correspond to date and / or time indications, complications, or flashlight and / or camera shortcuts.

[0262] In some embodiments, upon determining that device 100 is in a locked mode (optionally indicated, for example, by a lock indicator above the date), device 100 displays a user interface 604 (Figure 6B) for entering a passcode, or otherwise prompts the user for authentication before allowing the user to access applications or data stored on device 100.

[0263] In some embodiments, the user authenticates using a passcode entered into the user interface 604, as shown in Figure 6C. In some embodiments, in response to user input 602, the device 100 displays the augmented face switcher user interface 606, as shown in Figure 6D. In some embodiments, as described with reference to Figure 5U, the augmented face switcher user interface (e.g., user interface 561) includes multiple representations of the wake screen user interface (e.g., representation of wake screen user interface 611), and the central wake screen user interface 615 is displayed simultaneously with a portion of the associated home screen user interface.

[0264] Figure 6D shows several user interactions with the extended face switcher user interface 606. In some embodiments, user input 608 selecting a plus button causes device 100 to display a user interface (e.g., an edit user interface) for creating a new wake screen user interface to add to the set of wake screen user interfaces. In some embodiments, user input 610 selecting a portion of the representation of a second wake screen user interface 611 causes device 100 to display an edit user interface for the second wake screen user interface corresponding to the representation of the second wake screen user interface 611. In some embodiments, a user input selection user interface element 609a ("Focus") allows the user to set a restricted notification mode for the wake screen corresponding to the wake screen representation 615 (e.g., certain types of notifications are suppressed and / or delayed). In some embodiments, a user input selection option 609b allows the user to browse a gallery view (e.g., user interface 652 in Figure 6K) for creating a new wake screen user interface to add to the set of user interfaces. In some embodiments, user input 614, such as a swipe input (e.g., from right to left), causes the device to bring the representation of the second wake screen user interface 611 to the center of the extended face switcher user interface 606, as shown in Figure 6F.

[0265] In some embodiments, the user can rearrange the order of the set of wake screen user interfaces within the extended face switcher user interface 606. For example, in response to a long press user input or another type of user input, the user can select an individual representation of the wake screen user interface and optionally drag it to the left and / or right of other representations of the wake screen user interface to change the order in which the device 100 cycles through the set of wake screen user interfaces.

[0266] In some embodiments, one or more wake screen user interfaces within a set of wake screen user interfaces are associated with a distinct type or theme of wake screen user interfaces. For example, a distinct wake screen user interface may be identified as a photo style, emoji style, portrait style, or another style that is optionally pre-generated. For example, device 100 may optionally generate one or more themes or styles for wake screen user interfaces, such as a smart album that rotates images and / or photos stored in device 100, a weather style that includes a representation of the weather forecast for the current location of device 100, an astronomy, Earth, or other celestial sphere style, and / or a style that represents a lifestyle or other event (e.g., Pride, Women's History Month, or other event). An example of a wake user interface having a theme or style that is optionally automatically generated by device 100 without user input is shown in Figure 6K.

[0267] In some embodiments, user input 612, such as a swipe gesture (e.g., up or down), causes the device 100 to provide the user with the option to remove the centrally located wake screen user interface 615. For example, as shown in Figure 6E, the device 100 displays a delete icon 616. In some embodiments, in response to continued user input 612 (e.g., a swipe gesture continuing in the same direction), the device 100 optionally displays a representation of the wake screen user interface 615 sliding off the display and removes the wake screen user interface 600 from the set of wake screen user interfaces. In some embodiments, a second user input 618 (e.g., a tap input or other selection input) selects the delete icon 616, and in response to user input 618, the device 100 removes the wake screen user interface 600 from the set of wake screen user interfaces and stops displaying the representation of the wake screen user interface 615.

[0268] Figure 6F shows a representation of the second wake screen user interface 611 centered on the display (for example, in response to user input 614). In some embodiments, the representation of the second wake screen user interface 611 is centered on the display, but a portion of the associated home screen user interface representation 620 is optionally partially obscured behind the representation of the second wake screen user interface 611. In some embodiments, the representation of the second wake screen user interface 611 is displayed simultaneously with a portion of two or more other representations of the wake screen user interface, for example, the left wake screen user interface representation 615 and the right wake screen user interface representation 613.

[0269] Figure 6F shows multiple user inputs that allow a user to interact with the augmented face switcher user interface 606. For example, in response to user input 608-1 on the "+" button, device 100 initiates a process to add (optionally including design and / or edit) a new wake screen user interface to be added to the set of wake screen user interfaces, as shown in Figure 6K. In some embodiments, in response to user input 610-1 (e.g., a tap input or other selection input), the device brings a representation 613 of a wake screen user interface to the center of the augmented face switcher user interface. In some embodiments, user input 610-1 corresponds to a swipe input that causes device 100 to scroll through the available representations of wake screen user interfaces within the set of wake screen user interfaces.

[0270] In some embodiments, in response to user input 622 selecting the "Customize" button, device 100 displays an editing user interface 626 (Figures 6G-6H) for representing the wake screen that is currently at the center of the extended face switcher user interface 606 when user input 622 is detected.

[0271] In some embodiments, as shown in Figure 6I, the extended face switcher user interface displays a representation of the home screen user interface in the central region of the user interface 638 in response to user input 624 that selects a representation of the home screen user interface 624.

[0272] Figures 6G to 6H show an edit user interface 626 for the wake screen user interface, corresponding to the wake screen user interface representation 611. In some embodiments, the edit user interface 626 is optionally enabled for one or more of the same functions described with respect to the edit user interface 565 (Figure 5X). In some embodiments, the edit user interface 626 includes a user-selectable option for changing the font color of the user interface. In some embodiments, the edit user interface 626 includes a user-selectable option for applying visual filters (e.g., applying a color filter, blur, transparency filter, and / or gradient filter) to the wake screen user interface. In some embodiments, in response to user input 628 selecting a first color, the font color of the date and / or time indication is updated to the selected first color, as shown in Figure 6H, and the date and / or time indication is displayed in a white font color. In some embodiments, in response to user input 628 and / or user input on the "Font Color" button in Figure 6G, a user interface element 630 is displayed as shown in Figure 6H.

[0273] In some embodiments, the background of the wake screen user interface is an emoji-style background (e.g., a smiling emoji) in which one or more emojis are arranged in a pattern (e.g., a geometric pattern). In some embodiments, different views of the emoji user interface include changing the size and / or arrangement (e.g., a pattern) of the emojis in the background of the wake screen user interface. In some embodiments, an option 628b for selecting additional and / or alternative emojis (e.g., using an emoji picker) is displayed in the edit user interface 626. For example, the user can select up to a threshold number of emojis (e.g., three or four emojis) to display in a given pattern (e.g., a grid pattern, a swirl pattern, or another pattern).

[0274] In some embodiments, user input 627 is detected as a selection option 628b for selecting an emoji, and in response to user input 627, an emoji keyboard 629 is displayed in the editing user interface 626, as shown in Figure 6H2. In some embodiments, the emoji keyboard 629 includes a user interface element that displays the currently selected emoji used in a pattern. For example, in Figure 6H2, a smiling emoji is selected, and the grid pattern includes smiling emojis. In some embodiments, while the editing user interface 626 with an emoji-style background is displayed, the device 100 detects user input 631-1, such as a swipe input in a first direction (e.g., right to left). In some embodiments, in response to user input 631-1, the device 100 updates the editing user interface 626 to display an emoji-style background with a different pattern (and optionally having the same emoji(s) arranged in different patterns). For example, emojis are arranged in a first pattern (e.g., a grid pattern) in Figure 6H2 and in a second pattern (e.g., a swirl pattern) in Figure 6H3.

[0275] Figure 6H3 shows user input 633-1 selecting a first emoji (e.g., a thumbs-up emoji) and user input 633-2 selecting a second emoji (e.g., a heart emoji). In some embodiments, depending on user input (singular or plural) 633-1 and / or 633-2, the emojis displayed in the background are updated according to the user selection. In some embodiments, the order in which the emojis are selected is the order in which they are shown (e.g., alternating in the background pattern). For example, in Figure 6H4, the thumbs-up emoji and heart emoji are added after the smiley face emoji, and the pattern displays the selected emojis alternately. For example, the swirl pattern in Figure 6H4 includes the smiley face emoji, the thumbs-up emoji, and the heart emoji. In some embodiments, the user can select up to a predetermined number of emojis (e.g., 3 emojis, 5 emojis, 10 emojis) to include in the same background.

[0276] In some embodiments, in response to user input 631-2 (e.g., swipe input), device 100 updates the background to display a third pattern different from a first pattern (e.g., a grid pattern) and a second pattern (e.g., a swirl pattern). For example, as shown in Figure 6H5, selected emojis, including a smiling emoji, a thumbs-up emoji, and a heart emoji, are arranged in a geometric pattern that includes a diagonal arrangement of emojis.

[0277] Figure 6H displays a user interface element 630 for browsing and / or selecting font colors. In some embodiments, the user interface element 630 includes additional options beyond the color options displayed in the user interface 626 of Figure 6G. In some embodiments, the user can select and / or change the font color by selecting a color sample from a list of color samples displayed in the user interface element 630. For example, in response to user input 632, device 100 updates the color to the color of the sample color selected by user input 632, and in response to user input 634, device 100 updates the font color to the sample color selected by user input 634. In some embodiments, in response to user input 636 on the "Done" button, device 100 exits the editing user interface 626 and optionally returns to the extended face switcher user interface 606, or displays a wake screen user interface (e.g., the edited wake screen user interface as the current wake screen user interface).

[0278] Figure 6I shows a representation of the home screen user interface in the central region of the extended face switcher user interface 638 (for example, in response to user input 624). In some embodiments, the user can edit or customize the home screen user interface by selecting the “Customize” button in Figure 6I via user input 640.

[0279] Figure 6J shows an editing user interface 642 for editing the home screen user interface. In some embodiments, user input 644 selects an option to change the background color and / or gradient of the home screen user interface. In some embodiments, in response to user input 646 selecting a photo picker 628c, user interface 668 (Figure 6N) is displayed, allowing the user to change the photo to include in the home screen user interface.

[0280] In some embodiments, the user can toggle "visibility blur" on and / or off in the editing user interface 642. In some embodiments, when activated, visibility blur provides a visual de-emphasis (e.g., blur effect) to the background so that text, such as text labels optionally displayed with application icons, is more easily readable (e.g., legible) when displayed on a background.

[0281] In some embodiments, the editing user interface 642 includes an indication 647 that additional views of the home screen user interface are available. For example, the additional views correspond to one or more different visual effects applied to the background, including changes in color, tone, or another visual effect of the background. In some embodiments, the additional views include one or more different patterns or arrangements of the background of the home screen user interface. For example, a smiling emoji is rearranged in a different pattern and / or displayed in a different size in one or more additional views. In some embodiments, user input 648 (e.g., swipe input or other gesture) corresponds to a request to change the currently displayed view of the home screen user interface, and in response to user input 648, the device 100 displays a different view of the home screen user interface (e.g., a changed background).

[0282] In some embodiments, in response to user input 650 selecting the "Done" button, device 100 exits the home screen user interface editing user interface 642.

[0283] Figure 6K shows a user interface 652 for creating a new wake screen user interface (also referred to herein as a face) to add to a set of wake screen user interfaces. In some embodiments, user interface 652 includes several options for creating a new face based on a portrait orientation (e.g., a photograph containing a main subject or individual), based on a photograph (optionally selected from a photo library stored in device 100), and / or based on one or more emojis (optionally, the face may include up to a threshold number of emojis). In some embodiments, in response to user input 656 in which the user chooses to create a new face based on a photograph, device 100 displays a photo picker user interface 668 (Figure 6N) for the user to select a photograph to be used as the background for the new face, and after the user has selected a photograph, it allows the user to modify other features of the face, including font features.

[0284] In some embodiments, the user interface 652 includes one or more “feature faces” corresponding to the wake screen user interface, which are automatically generated (e.g., by device 100) without user input. For example, the feature face optionally includes a “smart album” that identifies multiple images (e.g., photographs) to be included in the wake screen user interface, and optionally rotates the multiple images while the “smart album” face is selected as the wake screen user interface. In some embodiments, device 100 allows the user to select a subset of individuals, pets, places, and / or photo albums to include in the wake screen user interface of the “smart album.” In some embodiments, device 100 provides the user with the option (e.g., in the editing user interface) to set how often the images change between each photograph in the “smart album” used as the current wake screen user interface. In some embodiments, in response to user input 6002 to select the “smart album” face, device 100 displays a user interface 6004 (Figure 6U) for the user to select and / or deselect categories to include in the smart album and optionally set how often the images change between each other.

[0285] In some embodiments, the feature face includes an emoji user interface containing pre-selected emojis and / or patterns of emojis. In some embodiments, the feature face includes a weather user interface that creates visual effects corresponding to the current weather forecast, a globe user interface containing an image of the Earth, an astronomy user interface containing one or more celestial spheres, and / or a privileged user interface containing symbols representing privileges. In some embodiments, each of the automatically generated user interfaces optionally includes a set of complications that are automatically selected and included in individual wake screen user interfaces.

[0286] For example, in response to user input 654 selecting an emoji user interface, device 100 displays an edit user interface 660 for editing the emoji user interface, which has a set of properties generated by device 100, as shown in Figure 6L. For example, date and time complications, date indications, and font properties are selected by device 100 without user input. In some embodiments, the user can edit the emoji user interface to change one or more properties within the set of properties. For example, the user can change the complications and / or change the font of the date and / or time indications. In some embodiments, in response to user input 662 selecting the "Done" button, device 100 stops displaying the edit user interface and displays the emoji user interface as the current wake screen user interface, optionally adding the emoji user interface to the set of wake screen user interfaces.

[0287] In some embodiments, in response to user input 658 (Figure 6K) selecting a weather user interface, device 100 displays an edit user interface 664 for editing the weather user interface. In some embodiments, the weather user interface is initially displayed along with a set of properties generated by device 100, and the user can edit the weather user interface to change one or more properties in the set of properties. In response to user input 666 selecting the "Done" button, device 100 stops displaying the edit user interface and displays the weather user interface as the current wake screen user interface, optionally adding the weather user interface to the set of wake screen user interfaces.

[0288] Figure 6N shows a photo picker user interface 668 for selecting a photograph to be used as the background image for the wake screen user interface. In some embodiments, in response to user input 670 selecting a photograph 672, device 100 displays a user interface 674 (Figure 6O) for viewing a preview of photograph 672 as the background for the wake screen user interface. In some embodiments, the user can further edit or customize the wake screen user interface by selecting a “Customize” button via user input 676.

[0289] In some embodiments, in response to user input 676 shown in Figure 6O, device 100 displays an editing user interface 678-a which includes displaying at least one reticle (e.g., reticle 572 for editing one or more complications, and optionally, a reticle for time and / or date indications) behind a portion of the background image, such as a subject in the background image (e.g., an aircraft), or at least partially obscured by a portion of the background image. In some embodiments, in response to user input 682-a directed to reticle 569 for editing time indications, the reticles, including reticles 572, 569, and 568, are displayed in front of the subject in the background image, as shown in Figure 6P.

[0290] Figure 6P shows an editing user interface 678 for editing the wake screen user interface with photograph 672 as the background, in response to user input 676. In some embodiments, the user may be able to edit the wake screen user interface by adding one or more complications, as shown in Figure 6Q, for example. For example, in response to user input 682 selecting the plus button, device 100 displays a user interface element 680 for adding a complication.

[0291] Figure 6Q shows user input 684 for selecting a set of complications 686 to add to the wake screen user interface. In some embodiments, in response to user input 684, device 100 displays the set of complications 686 below the time indicator (Figure 6R). In some embodiments, the user can move the set of complications 686, for example, above and / or to the side of the date and / or time indicator.

[0292] Figure 6Q further shows a user input 685 for selecting a reticle for time indication, and in response to the user input 685, device 100 displays a user interface element 687 for changing one or more characteristics of the time and / or date indication (e.g., color and / or font style).

[0293] Figure 6R shows user input 688 selecting a different style for the time font. In some embodiments, in response to user input 688, device 100 updates the time and / or date indication displayed with “Style 2”. Figure 6R further shows user input 690 selecting a “Done” button that causes device 100 to exit the edit user interface 678 and display the user interface as the current user interface with photograph 672 as the background, and optionally add the new user interface having photograph 672 as the background to the set of wake screen user interfaces.

[0294] Figures 6S to 6T show examples of portrait-style wake screen user interfaces. In some embodiments, portrait-style wake screen user interfaces 692 and 694 are included in a set of wake screen user interfaces that device 100 automatically cycles through over time. For example, in some embodiments, device 100 automatically changes the wake screen user interface from a first wake screen user interface to a second wake screen user interface from the set of wake screen user interfaces without optionally detecting user input. In some embodiments, device 100 automatically changes the wake screen user interface periodically (e.g., every 5 minutes, daily, weekly). In some embodiments, device 100 automatically changes the wake screen user interface according to a determination that device 100 has entered a locked state and / or a low-power state. For example, when device 100 is pulled out of a low-power state, the wake screen user interface is updated to the next wake screen user interface in the set of wake screen user interfaces. Figure 6T shows a user input 696 requesting that the wake screen user interface 694 be dismissed, and in response to the user input 696, device 100 displays the home screen user interface associated with (or related to) the wake screen user interface 694.

[0295] Figure 6U shows a user interface 6004 for selecting one or more categories of photos to include in a smart album, and an option to select how often the background changes while the smart album is selected as the background for the wake screen user interface. In some embodiments, the smart album identifies a set of images or photos that are optionally stored in device 100 or otherwise associated with the user of device 100, and rotates the images periodically as the wake screen user interface. In some embodiments, visual characteristics (e.g., time and / or date complications and character indications) also change as the image changes from one wake screen user interface to another. In some embodiments, the frequency at which the image is refreshed or rotated is selected by the user.

[0296] In some embodiments, the user interface 6004 provides the option to select or deselect one or more categories of a photograph, including a people category, a pet category, a nature category, and / or a city category. In some embodiments, a photograph is determined to belong to a category based on the content of the photograph, which is automatically identified by the device 100 on an optional basis without the user manually tagging the photograph with a category.

[0297] In some embodiments, the user interface 6004 includes a representation of the wake screen user interface included in the smart album, including representation 6003-1. In some embodiments, the user can deselect a category; for example, in Figure 6U, user input 6006 selects a checkmark to deselect the "Nature" category. In some embodiments, following the determination that the "Nature" category has been deselected, the smart album does not include any photos identified as having nature-related content (e.g., trees, flowers, sunsets, or other landscapes). In some embodiments, the currently selected category is indicated by a checkmark next to the category.

[0298] In some embodiments, if the user deselects the "Nature" category, the representation 6003-1 containing the image of a flower is no longer included in the smart album, and the device 100 optionally stops displaying the representation 6003-1, as shown in the user interface 6008 of Figure 6V.

[0299] In some embodiments, as shown in Figure 6V, the user may select to include one or more categories, such as selecting the category "City" in user input 6010. In some embodiments, in response to user input 6010, device 100 displays a wake screen user interface representation 6003-2 included in the City category (e.g., an image including a house or building). In some embodiments, while the City category is selected, an image or photograph containing city-related content (e.g., skyscrapers, buildings, skyline views, cityscapes, billboards, or other images of the city) is selected.

[0300] In some embodiments, the user can exit the user interface 6008 by user input 6012 (e.g., swiping down) to close the smart album category selection or otherwise stop the display. In some embodiments, in response to user input 6012, the device 100 returns to the user interface shown in Figure 6K.

[0301] Figure 6W shows user input 6016 selecting a "Select..." option, which allows the user to choose who to include in the smart album. For example, in response to user input 6016, device 100 displays a user interface 6018 (Figure 6X) for selecting one or more people to include in the smart album. In some embodiments, the one or more people displayed in user interface 6018 are automatically selected based on the photo library of device 100.

[0302] Figure 6X shows multiple user inputs for selecting one or more people to include in a smart album. For example, user input 6020 (e.g., a tap input or other selection input) selects representation 6026-2 of a first person, user input 6022 selects representation 6026-3 of a second person, and user input 6024 selects representation 6026-1 of a third person. In some embodiments, according to the determination that each person has been selected, one or more photos containing each person are included in the set of photos in the smart album. In some embodiments, an option is provided for browsing and selecting additional people not displayed in the user interface 6018 (e.g., "More...").

[0303] In some embodiments, the representations shown in user interface 6028 include representations of the wake screen user interface that include backgrounds for individually selected people, as shown in Figure 6Y. For example, representation 6003-3 includes a representation of a person associated with representation 6026-2.

[0304] Figure 6Y shows a detected user input 6030 with an option to select how often to change photos in the smart album. In some embodiments, a menu of user-selectable options is displayed to the user in response to the user input 6030. In some embodiments, the menu of user-selectable options includes one or more options for changing the frequency based on a time period (e.g., every hour, every five hours, or every day) and / or one or more options for changing the frequency based on a detected event of the device 100 (e.g., when unlocked, in each focus mode, or when charging starts).

[0305] Figure 6Y further illustrates user input 6032 in which the user selects an option to automatically select images corresponding to the currently selected category. For example, in response to user input 6032, device 100 identifies one or more images related to the selected individual category (e.g., people, pets, and / or cities) and displays those one or more images as the wake screen user interface. In some embodiments, the user may select an option to manually select images. For example, in response to user input selecting the manual selection option, device 100 displays a photo library or photo picker (e.g., user interface 668 in Figure 6N) in which the user can browse and select specific photos to include as the background of the smart album.

[0306] In some embodiments, in response to user input 6032, device 100 stops displaying user interface 6028. In some embodiments, device 100 optionally displays an edit user interface for the first wake screen user interface of the smart album, as shown in Figure 6Z. In some embodiments, device 100 displays an edit user interface 6034-1 (Figure 6Z) in response to one or more interactions, as described with reference to Figures 6F-6G. For example, a user can access the edit user interface 6034-1 using any of the methods described herein. In some embodiments, the edit user interface 6034-1 is accessible from a settings user interface that provides options for editing the wake screen user interface and / or the home screen user interface.

[0307] Figure 6Z shows the editing user interface 6034-1 of the first wake screen user interface, which includes a first person, optionally selected in a smart album. In some embodiments, the original photograph (or “natural” view) used as the background of the first wake screen user interface is displayed. In some embodiments, according to the determination that the wake screen user interface selected for editing is in a smart album, the user is provided with the option to shuffle or browse another photograph in the smart album (e.g., “Tap to shuffle”). In some embodiments, the original photograph (or “natural” view) is processed by device 100 to determine the initial tone. For example, the initial tone represents the luminance and / or amount of luminance of the background (and / or foreground) of the original photograph. In some embodiments, the original photograph in Figure 6Z is identified as a low luminance key level (e.g., low luminance, such as a relatively dark photograph) according to a calculated level of luminance that satisfies a threshold amount of luminance. In some embodiments, the editing user interface 6034-1 includes a photo picker 6033 for selecting a different background photograph. For example, in response to user input 6042 (Figure 6AA), device 100 displays a photo library or photo picker user interface (as described with reference to, for example, Figure 6N). In some embodiments, the editing user interface 6034-1 includes indicators 6035 of additional views of the wake screen user interface, such as the same foreground (e.g., subject or person) and different backgrounds of the photograph, and / or different filters applied to the photograph (as described with reference to, for example, swipe input 6040 in Figure 6AA).

[0308] In some embodiments, a menu 6037 is displayed in response to user input 6036 in which a menu option is selected. In some embodiments, menu 6037 provides several options for modifying the wake screen user interface displayed in the editing user interface 6034-2, including an option to change to radar, an option to change to low key and / or high key, an option to change the frequency (e.g., switching background photos in a smart album), and / or an option to disable the depth effect of a photo. For example, user input 6038 in which an option to change the background frequency allows the user to make changes when the device 100 changes the wake screen user interface (e.g., based on time-based and / or device events).

[0309] In some embodiments, upon detecting a swipe input 6040, device 100 displays an editing user interface 6034-3 (Figure 6AB) that includes another view of the photograph (e.g., a two-color view). In some embodiments, the two-color view is generated as a two-color low-key version according to the determination that the original photograph was identified as having low-key luminance levels. For example, device 100 automatically displays a set of views having luminance levels selected based on the luminance levels of the original photograph.

[0310] Figure 6AB shows user input 6046, and displays menu 6037 in response to user input 6046. In some embodiments, device 100 detects user input 6044, which selects to switch to a high-key version of the currently displayed view. In some embodiments, in response to user input 6044, device 100 updates the display to show a two-color view (also referred to herein as a two-color filter) as a high-key version, as shown in Figure 6AC. For example, a two-color view is represented by horizontal stripes, but the high-key version of the two-color view (shown in Figure 6AC) has a higher level of brightness than the low-key version of the two-color view (shown in Figure 6AB). Thus, device 100 automatically generates separate versions of each view based on the identified tones of the original photograph. For example, the original photograph in Figure 6AA is identified as a low-key photograph (e.g., below a threshold amount of brightness), so multiple low-key views (e.g., a low-key two-color view, a low-key studio view, and / or a low-key black and white view) are provided for that photograph.

[0311] Figure 6AC shows a user input 6048 (e.g., a swipe input) that responds to a request to switch to a different view. In some embodiments, a low-key black and white view of the photograph is displayed on the user interface 6034-5, as shown in Figure 6AD. In some embodiments, after the user manually switches from a low-key version of a view to a high-key version (e.g., as described with reference to Figures 6AB-6AC), the device 100 continues to recommend or automatically provides low-key versions of other views. For example, in Figure 6AD, the device 100 provides a low-key version of the black and white view (e.g., because the original photograph is a low-key photograph). Thus, the user can switch between low-key and / or high-key by manually changing a particular view or filter without changing the recommended view, which is automatically generated and presented and is likely to be visually satisfactory in order to maintain the brightness (or other tones) present in the original photograph.

[0312] Figure 6AE shows an example of the original high-key photograph displayed in the editing user interface 6050-1. For example, the original photograph meets a luminance threshold level that makes the photograph relatively bright, i.e., high-key. In some embodiments, in response to user input 6052, the device 100 displays another view of the photograph. In some embodiments, the next view shown in the user interface 6050-2 is a high-key version of the view, for example, a high-key version of the two-color view, as shown in Figure 6AF.

[0313] In some embodiments, in response to user input 6054, device 100 replaces the display of the user interface with a different view, namely a high-key version of the studio view, as shown in user interface 6050-3 of Figure 6AG. Figure 6AG shows user input 6056 selecting a menu icon, and in response to user input 6056, device 100 displays menu 6037. In some embodiments, user input 6058 selects an option within menu 6037 to switch the current view to a low-key version. For example, in response to user input 6058, device 100 displays user interface 6050-4 of Figure 6AH, which corresponds to the low-key version of the studio view.

[0314] Figure 6AH shows user input 6060 requesting a switch to a different view. In some embodiments, in response to user input 6060, device 100 displays a high-key version of the black and white view (for example, because the original photograph is determined to be the high-key photograph), as shown in user interface 6050-5 of Figure 6AI.

[0315] Figure 6AI shows user input 6062 corresponding to a request to switch to a different view. In some embodiments, in response to user input 6062, device 100 displays a color view (also referred to herein as a color filter) as shown in user interface 6050-6 of Figure 6AJ. In some embodiments, the tone of the color selected in the color view matches the tone identified in the original photograph. For example, the overall tone (or brightness) of the original photograph is calculated, and the color selected in the color view has the same overall tone (or brightness) as the original photograph. In some embodiments, in the color view, the background of the photograph is updated to include the selected color. In some embodiments, the selected color is applied to the entire photograph (e.g., background and foreground), which optionally includes applying different levels (e.g., having different transparency or brightness) of the selected color to different parts of the photograph. For example, the selected color is optionally applied to the entire photograph, the foreground containing the subject of the photograph is only lightly coated with the selected color (e.g., as a filter), and the background is replaced with a solid or more opaque version of the selected color.

[0316] Figure 6AJ shows user input 6064 corresponding to a request to change the background of the wake screen user interface. In some embodiments, in response to user input 6064, device 100 displays a color picker 6066 for changing the color applied to the photograph. In some embodiments, the initially selected color is chosen to have a tone that matches the tone of the original photograph. For example, as shown in Figure 6AK, the selected color has a high level of luminance (e.g., for a high-key original photograph), as indicated by the selector to the left of the slider bar 6068 which shows the luminance level that defines the tone of the currently selected color. For example, if the original photograph is a low-key original photograph, the color tone is automatically set to a low-key tone (e.g., to the right of the slider 6068).

[0317] In some embodiments, user input 6070 responds to a request to change the tone of the selected color. For example, as shown in Figure 6AL, in response to user input 6070, the background of user interface 6050-8 is displayed in a darker (e.g., lower key) tone of the same color as the background of user interface 6050-7 in Figure 6AK.

[0318] In some embodiments, each color provided by the color picker 6066 is displayed in the same tone (for example, matching the tone of the original photograph). For example, the colors may be different (e.g., purple, green, red, yellow, or another color), but the brightness level and / or tone of each color is optionally and automatically selected according to the tone of the original photograph. In some embodiments, one or more colors displayed as options in the color picker are not selected as having the tone of the original photograph.

[0319] Figure 6AL shows user input 6069 selecting a different color displayed in the color picker 6066. In some embodiments, in response to user input 6069, the background of the user interface is updated to display the selected color. In some embodiments, as shown in Figure 6AM, one or more views are used as a smart album as a wake screen user interface.

[0320] Figure 6AM shows a wake screen user interface 6072-1 and a case 6073 of device 100 located nearby. In some embodiments, the case 6073 is a protective case physically placed on at least a portion of device 100. In some embodiments, device 100 can detect one or more characteristics associated with the case 6073 while it is on device 100. For example, device 100 may identify the color of the case 6073.

[0321] Figure 6AN shows case 6073 positioned on device 100. In some embodiments, device 100 determines that case 6073 is positioned on device 100, and in response to this determination, device 100 optionally displays a prompt 6074 asking the user whether device 100 should update the background color (e.g., of wake screen user interface 6072-2) to match the case color (e.g., as detected by device 100). In some embodiments, prompt 6074 includes the option to select yes and the option to select no.

[0322] In some embodiments, device 100 detects user input 6076 in response to prompt 6074, and in response to user input 6076, device 100 updates user interface 6072-3 to display in a color (e.g., a color filter) that matches (or complements) the color of case 6073. In some embodiments, the color is applied only to the background of wake screen user interface 6072-3. In some embodiments, the color is applied to both the foreground and background of wake screen user interface 6072-3 (optionally, different parts are displayed with different levels of transparency or color brightness).

[0323] Figure 6AP shows a user interface 652 (as described, for example, with reference to Figure 6K). In some embodiments, the user interface 652 for creating a new wake screen includes a recommended face 6078 based on the color of the case detected to be on device 100. For example, upon determination that a case is on device 100, the user interface 652 is automatically updated to include a wake screen user interface with features that match (or complement) the color of the case. It will be understood that additional recommendations may be provided to the user based at least partially on the color of the case detected to be on device 100.

[0324] Figures 6AQ to 6AR show examples of displaying a smart album as a wake screen user interface. For example, one or more views of the wake screen user interface described with reference to Figures 6AA to 6AJ are displayed as wake screen user interfaces. In some embodiments, a first view of a first photograph is displayed as wake screen user interface 6080, and the wake screen user interface automatically updates to display a second wake screen user interface 6084 containing a second view of a second photograph, according to the selected frequency of the smart album, without additional user input. In some embodiments, user input 6082 is optionally detected, and in response to user input 6082, the wake screen user interface updates from wake screen user interface 6080 to wake screen user interface 6084.

[0325] Figures 7A to 7V-3 show representations of multiple notifications in different configurations, as well as user inputs that can be used to switch between different configurations.

[0326] Figure 7A shows a representation of the first multiple notification in the first configuration 7000-a. For ease of explanation, the representation of the first multiple notification is referred to as "representation 7000" (regardless of which configuration the representation of the first multiple notification is displayed in), and the letters following the label 7000 (e.g., 7000-a, 7000-b, or 7000-c) refer to the specific configuration in which representation 7000 is displayed (e.g., 7000-a refers to the first configuration, 7000-b refers to a second configuration different from the first configuration 7000-a, and 7000-c refers to a third configuration different from both the first configuration 7000-a and the second configuration 7000-b). In various situations, representation 7000 may represent (e.g., include) different notific...

Claims

1. It is a method, In a computer system that communicates with display generation components, Displaying a first user interface for configuring a system user interface having a first background and a first set of one or more system user interface objects covering the first background, via the display generation component, While the system user interface is displayed, the computer system automatically shuffles two or more media items selected from the set of media items in the first background over time. The first user interface includes selectable representations for each of a plurality of categories for media items associated with the computer system, each of which includes at least a first selectable representation for a first category and a second selectable representation for a second category. A plurality of first media items associated with the computer system are automatically selected to be included in the first category based on the plurality of first media items, which include automatically detected content of a first type. A second set of media items associated with the computer system are automatically selected to be included in the second category based on the second set of media items, which include automatically detected content of a second type. That thing, While displaying the first user interface for configuring the system user interface, a first input is detected that selects one or more sets of the plurality of categories. Displaying the system user interface after one or more sets of the aforementioned categories are selected by the first input, wherein displaying the system user interface includes displaying over time the system user interface having multiple versions of the first background, each containing media items selected from the media items within each of the sets of the aforementioned categories. In accordance with the determination that one or more of the sets of the aforementioned categories include the first category but not the second category, the aforementioned versions of the first background include media items from the first category but not from the second category. In accordance with the determination that one or more of the sets of the aforementioned categories do not include the first category but include the second category, the aforementioned versions of the first background include media items from the second category but do not include media items from the first category. In accordance with the determination that one or more of the sets of the aforementioned categories include the first category and the second category, the aforementioned versions of the first background include one or more media items from the first category and one or more media items from the second category. That thing, A method that includes [a certain feature].

2. The method according to claim 1, Each of the selectable representations of the plurality of categories of media items associated with the computer system includes a third selectable representation of a third category, and the third plurality of media items associated with the computer system are automatically selected to be included in the third category based on the third plurality of media items that include automatically detected content of a third type. In accordance with the determination that one or more of the sets of the aforementioned multiple categories include the first category but not the third category, the multiple versions of the first background include media items from the first category but not from the third category. In accordance with the determination that one or more of the sets of the aforementioned categories do not include the first category but include the third category, the aforementioned versions of the first background include media items from the third category but do not include media items from the first category. In accordance with the determination that one or more of the sets of the aforementioned categories include the first category and the third category, the aforementioned versions of the first background include one or more media items from the first category and one or more media items from the third category. method.

3. The method according to claim 1, wherein the first category corresponds to a person category, and the first plurality of media items associated with the computer system are automatically selected to be included in the first category based on the first plurality of media items which include automatically detected content corresponding to a person. method.

4. The method according to claim 3, wherein the first plurality of media items is a subset of media items that are stored in a media library associated with the computer system and selected to be included in the first category based on a subset of media items that include automatically detected human faces corresponding to faces identified in media items within the media library. method.

5. The method according to claim 1, To detect a second input corresponding to a request that constitutes the first category, In response to detecting the second input, the system displays multiple selectable representations of the subject identified in the first media items, which are automatically included in the first category based on the first media items containing the automatically detected content of the first type. To detect a third input that selects and / or deselects one or more representations of a subject identified in the first plurality of media items, Displaying the system user interface after one or more of the first plurality of media items are selected and / or deselected by the third input, wherein displaying the system user interface includes displaying over time the system user interface having multiple versions of the first background, each containing a media item selected from the media items within each of the sets of one or more of the plurality of categories. If one or more of the sets of the aforementioned categories include a first category, and the third input determines that a first subset of the first media items including a first subject is selected and a second subset of the first media items including a second subject is not selected, then the multiple versions of the first background include media items from the first subset of the first media items in the first category, but do not include the second subset of the first media items in the second category. If one or more of the sets of the aforementioned categories include the first category, and the third input determines that the second subset of the first media items including the second subject is selected and the first subset of the first media items including the first subject is not selected, then the multiple versions of the first background include media items from the second subset of the first media items in the second category, but do not include the first subset of the first media items in the first category. That thing, A method that includes [a certain feature].

6. The method according to claim 1, wherein the second category corresponds to a pet category, a nature category, or an urban category, and the second plurality of media items associated with the computer system are automatically selected to be included in the second category based on the second plurality of media items which include automatically detected content corresponding to the pet, nature, or urban theme. method.

7. A method according to claim 1, wherein one or more sets of the plurality of categories selected by the first input include at least two of the plurality of categories, method.

8. The method according to claim 1, The first user interface includes multiple previews of the system user interface that are generated based on the set of categories currently selected from the plurality of categories. Displaying the multiple previews of the system user interface is, In accordance with the determination that the currently selected set of categories includes the first category but does not include the second category, the first set of previews generated based on media items selected from the first category is displayed without displaying the second set of previews generated based on media items selected from the second category. In accordance with the determination that the currently selected set of categories includes the second category but does not include the first category, the second set of previews generated based on media items selected from the second category is displayed without displaying the first set of previews generated based on media items selected from the first category, In accordance with the determination that the currently selected set of categories includes the first category and the second category, display at least one preview selected from the first set of previews and at least one preview selected from the second set of previews. Methods that include...

9. A method according to claim 1, wherein the first user interface includes one or more selectable user interface objects for adjusting individual frequencies at which the computer system automatically shuffles two or more media items selected from the set of media items in the first background over time. method.

10. The method according to claim 9, To detect the occurrence of a first condition corresponding to a transition request from a low-power state to a normal state of the display generation component, In response to detecting the occurrence of the first condition, Transitioning the display generation component from the low-power state to the normal state, In accordance with the determination that the individual frequency is a first frequency, the system user interface having individual media items in the first background is displayed, wherein the individual media items are automatically selected from the set of media items and are different from the last displayed media item that was included in the first background when the system user interface was last displayed before the display generation component entered the low-power state. A method that includes [a certain feature].

11. The method according to claim 9, While displaying the system user interface having a first background including a first media item selected from the set of media items, detecting a second input directed to the system user interface that satisfies a first criterion, Updating the system user interface, which includes, in response to detecting the second input directed to the system user interface that satisfies the first criterion, updating the system user interface, in accordance with the determination that the individual frequency is the second frequency, by replacing the first media item in the first background with a second media item automatically selected from the set of media items; A method that includes [a certain feature].

12. The method according to claim 9, While the system user interface is displayed, which has the first background including a third media item selected from the set of media items, it is determined whether the duration for which the third media item was used in the first background of the system user interface satisfies a time-based criterion for switching. Updating the system user interface, which includes, in response to detecting that the time-based criteria for switching are met, updating the system user interface, in accordance with the determination that the individual frequency is a third frequency, the third media item in the first background with a fourth media item selected from the set of media items; A method that includes [a certain feature].

13. The method according to claim 1, After one or more sets of the aforementioned categories are selected by the first input, a third input is detected for selecting one or more media items to be included in the first set of media items, wherein the third input selects one or more media items to be included in the first set of media items, regardless of whether the one or more media items belong to one or more sets of the aforementioned categories. Displaying the system user interface after the first set of media items has been selected by the third input, wherein displaying the system user interface includes displaying the system user interface over time, each having a different version of the first background that includes the media items selected from the first set of media items. A method that includes [a certain feature].

14. The method according to claim 1, Displaying a second user interface that includes a first selectable option for selecting a new background for the aforementioned system user interface, In response to detecting the selection of the first selectable option in the second user interface, a prompt is displayed requesting user confirmation regarding whether to replace the currently displayed version of the system user interface or to create a new version of the system user interface. A method that includes [a certain feature].

15. The method according to claim 14, wherein the second user interface is A second selectable option, when selected, displays a first set of selectable user interface objects that constitute the currently displayed version of the system user interface, A third selectable option, when selected, displays a second set of selectable user interface objects that constitute a different system user interface from the aforementioned system user interface. A fourth selectable option, when selected, simultaneously includes displaying a third set of selectable user interface objects that create and configure a new version of the system user interface without changing the currently displayed version of the system user interface, method.

16. The method according to claim 1, wherein the system user interface is displayed In accordance with the determination that individual media items from the aforementioned set of media items should be included in the first background, In accordance with the determination that the foreground portion of the individual media item overlaps with the first set of one or more system user interface objects by a first overlap threshold amount, the foreground portion of the individual media item is displayed at a simulated depth that is in front of the simulated depth of the first set of one or more system user interface objects in the system user interface. In accordance with the determination that the foreground portion of the individual media item overlaps with the first set of one or more system user interface objects by a value greater than the first overlap threshold, the foreground portion of the individual media item is displayed at a simulated depth behind the simulated depth of the first set of one or more system user interface objects in the system user interface. Methods that include...

17. The method according to claim 16, While displaying the system user interface having the first background including the individual media items, a fourth input is detected that changes the amount of overlap between the foreground portion of the individual media items and the first set of one or more system user interface objects. In response to the detection of the fourth input, According to the determination that the fourth input changes the amount of overlap between the foreground portion of the individual media item and the first set of one or more system user interface objects from less than the first overlap threshold amount to more than the first overlap threshold amount, Displaying the system user interface having the individual media items enlarged and / or recentered within the first background, To increase the simulated depth of the foreground portion of the individual media item so that the foreground portion of the individual media item is displayed at a simulated depth behind the simulated depth of the first set of one or more system user interface objects in the system user interface, According to the determination that the fourth input changes the amount of overlap between the foreground portion of the individual media item and the first set of one or more system user interface objects from greater than the first overlap threshold amount to less than the first overlap threshold amount, Displaying the system user interface having the individual media items scaled down and / or recentered within the first background, The simulated depth of the foreground portion of the individual media item is reduced such that the foreground portion of the individual media item is displayed at a simulated depth that is in front of the simulated depth of the first set of one or more system user interface objects in the system user interface. A method that includes [a certain feature].

18. A computer system, Display generation components and, One or more processors, A memory storing one or more programs, wherein the one or more programs are configured to be executed by the one or more processors, and the one or more programs include instructions for performing the method according to any one of claims 1 to 17, Computer system.

19. A computer-readable recording medium storing one or more programs, wherein the one or more programs include instructions, and when the instructions are executed by a computer system having a display generation component, the computer system causes the computer system to perform the method according to any one of claims 1 to 17. Computer-readable recording medium.

Images