Device, method, and graphical user interface for providing notification 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 generally to electronic devices with touch-sensitive surfaces, including, but not limited to, electronic devices with touch-sensitive surfaces that display notifications and application information for applications of the electronic device. [Background technology]

[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 touchpads and touchscreen displays. Such surfaces are widely used to manipulate user interfaces on the displays and objects therein.

[0003] Exemplary operations include adjusting the position and / or size of one or more user interface objects, activating a button or opening a file / application represented by the user interface object, 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, video, text, icons, and control elements such as buttons and other graphics.

[0004] However, methods of performing 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 significant cognitive burden for the user. In addition, the methods take longer than necessary, thereby wasting energy. This latter consideration is particularly important in battery-operated devices. Summary of the Invention

[0005] Thus, there is a need for electronic devices with faster, 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 type of inputs from a user, creating a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and extend the time between battery charges.

[0006] The above deficiencies and other problems associated with user interfaces for electronic devices having touch-sensitive surfaces are reduced or eliminated by the devices of the present disclosure. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, a tablet computer, or a 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 "touch screen" or "touch screen display"). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory, and one or more modules, programs, or sets of instructions stored in the memory for performing a number of functions. In some embodiments, a user interacts with the GUI primarily through stylus and / or finger contacts and gestures on the touch-sensitive surface. In some embodiments, the functionality optionally includes image editing, drawing, presenting, word processing, spreadsheet creation, game playing, making phone calls, video conferencing, emailing, instant messaging, training support, digital photography, digital videography, web browsing, digital music playback, note taking, and / or digital video playback, and executable instructions to perform those functionality are optionally contained on a non-transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors.

[0007] According to some embodiments, a method is performed on a computer system in communication with a display generating component. The method includes displaying, via the display generating component, a first version of a first user interface corresponding to a restricted state of the computer system. Displaying the first version of the first user interface includes displaying a first plurality of user interface objects displayed simultaneously with a first background according to a first configuration. The first plurality of user interface objects correspond to a first plurality of applications, include individual content from the first plurality of applications, and are updated periodically as information represented by the first plurality of user interface objects changes. The method further includes detecting a first input while displaying the first version of the first user interface. The method further includes, in response to detecting the first input, in accordance with a determination that the first input satisfies a first criterion, the first criterion requiring the first input to include a first movement in a first direction for the first criterion to be satisfied, replacing a display of the first version of the first user interface with a display of a second user interface including a respective representation of a second plurality of applications, each of which, when activated, causes the computer system to launch a corresponding application of the respective representation; and 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, for the second criterion to be satisfied, replacing the display of the first version of the first user interface with a display of a second version of the first user interface,The second plurality of user interface objects correspond to a third plurality of applications, include individual content from the third plurality of applications, and are updated periodically as information represented by the second plurality of user interface objects changes, the first background is different from the second background, the first plurality of user interface objects is different from the second plurality of user interface objects, and / or the first configuration is different from the second configuration.

[0008] According to some embodiments, a method is performed on a computer system in communication with a display generating component. The method includes detecting a request to change a wake user interface of the computer system. The wake user interface is a user interface that is displayed when the computer system is turned on or transitioned from a low power state to a high power state and corresponds to a restricted operating mode of the computer system. The method further includes displaying, via the display generating component, a first user interface for changing the wake user interface of the computer system in response to detecting the request to change the wake user interface of the computer system. The method further includes simultaneously displaying, while displaying the first user interface, a first representation of the wake user interface and a first representation of a home user interface, the home user interface being a user interface that is displayed when the wake user interface is dismissed and the computer system exits the 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 corresponding to a second set of one or more wake user interface configurations including a second wake user interface background 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 a respective representation of the wake user interface for the computer system from the first user interface.The method further includes, in response to detecting the sequence of one or more inputs, configuring a wake user interface of the computer system based on a first set of one or more wake user interface settings associated with the first representation of the wake user interface in accordance with a determination that a first representation of the wake user interface was selected based on the sequence of the one or more inputs, the first representation of the wake user interface including using a background of the first wake user interface as an individual background of the wake user interface; configuring a home user interface of the computer system based on a first set of one or more home user interface settings, the first representation of the wake user interface including using a background of the first home user interface as an individual background of the home user interface; and configuring a wake user interface of the computer system based on a second set of one or more wake user interface settings associated with the second representation of the wake user interface in accordance with a determination that a second representation of the wake user interface was selected based on the sequence of the one or more inputs, the second representation of the wake user interface including using a background of the second wake user interface as a background of the wake user interface.

[0009] According to some embodiments, a method is performed on a computer system in communication with a display generation component. The method includes displaying, via the display generation component, a first user interface for configuring a wake user interface. The individual version of the wake user interface includes an individual background and an individual plurality of editable user interface objects overlaying the individual 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 overlaying the first background. The method further includes detecting a first input directed to the first user interface while displaying the first user interface. The method further includes, in response to detecting a first input directed at the first user interface, displaying a second user interface for editing a first user interface object of the first plurality of editable user interface objects in accordance with a determination that the first input satisfies a first criterion, the first user interface object being selected in accordance with a location of the first input, and updating the first user interface to replace a display of a first representation of the first version of the wake user interface with a display of a second representation of the second version of the wake user interface in accordance with 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 second plurality of editable user interface objects over a second background different from the first background. The second plurality of editable user interface objects are different from the first plurality of editable user interface objects.

[0010] According to some embodiments, a method is performed on a computer system having a display generating component and one or more input devices. The method includes displaying, via the display generating component, a first user interface including a plurality of notifications, including: displaying representations of the plurality of notifications in a first configuration in a first region of the first user interface in accordance with a determination that the computer system has enabled a first mode for displaying the notifications; and displaying the representations of the plurality of notifications in a second configuration in a second region of the first user interface that is smaller than the first region of the first user interface in accordance with a determination that the computer system has enabled a second mode for displaying the notifications. The method further includes detecting a first user input at a discrete location on the first user interface corresponding to the representations of the plurality of notifications while displaying the first user interface. The method further includes, in response to detecting the first user input, while continuing to detect the first user input, scrolling notifications within the plurality of notifications in a first region of the first user interface in accordance with the first user input in accordance with a determination that the first user input satisfies a first criterion and in accordance with a determination that the representations of the plurality of notifications are displayed in a first configuration, and scrolling notifications within the plurality of notifications in a third region of the first user interface in accordance with the first user input in accordance with a determination that the first user input satisfies the first criterion and in accordance with a determination that the representations of the plurality of notifications are displayed in a second configuration.

[0011] According to some embodiments, a method is executed on a computer system in communication with a display generating component. The method includes detecting one or more inputs for subscribing to updates from a first application for a first event and for subscribing to updates from a second application for a second event. The method further includes displaying a first user interface. The first user interface includes a first region at a first location within the first user interface. Displaying the first user interface includes displaying a first representation of the first event in the first region of the first user interface according to a determination that the first event is active and the second event is not active, updating first information included in the first representation of the first event according to the updates received from the first application for the first event, and displaying a second representation of the second event in the first region of the first user interface and updating second information included in the second representation of the second event according to the updates received from the second application for the second event according to a determination that the second event is active and the first event is not active.

[0012] According to some embodiments, a method is performed on a computer system having a display generating component and one or more input devices. The method includes detecting a first user input via the one or more input devices while displaying a wake user interface including a representation of a first plurality of notifications in a first configuration, the wake user interface being a user interface displayed when the computer system wakes up from a low power state. In response to detecting the first user input, the method further includes displaying the representation of the first plurality of notifications in a second configuration of the wake user interface, different from the first configuration, in accordance with a determination that the first user input meets 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 in accordance with a determination that the first user input does not meet 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 an occurrence of a condition that causes the computer system to re-display the wake user interface, displaying a representation of the second plurality of notifications in the second configuration in accordance with a determination that the first user input satisfies the first criterion, and displaying a representation of the second plurality of notifications in the first configuration in accordance with a determination that the first user input does not satisfy the first criterion.

[0013] According to some embodiments, a method is performed on a computer system having a display generating component. The method includes displaying, via the display generating component, 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 overlaying the first background, and while the system user interface is displayed, the computer system automatically shuffles through two or more media items selected from a collection of media items in the first background over time. The first user interface includes selectable representations of each of a plurality of categories for media items associated with the computer system, including at least a first selectable representation of a first category and a second selectable representation of a second category. The first plurality of media items associated with the computer system are automatically selected for inclusion in the first category based on the first plurality of media items including a first type of automatically detected content, and the second plurality of media items associated with the computer system are automatically selected for inclusion in the second category based on the second plurality of media items including a second type of automatically detected content.The method further includes detecting a first input selecting one or more sets of a plurality of categories while displaying a first user interface for configuring the system user interface, and displaying the system user interface after the one or more sets of the plurality of categories are selected by the first input, where displaying the system user interface includes displaying the system user interface having multiple versions of a first background over time, each version including a media item selected from the media items in a respective category in the one or more sets of the plurality of categories, and wherein the one or more sets of the plurality of categories are selected from a second category. In accordance with a determination that a set of the plurality of categories includes the first category without including a media item from the second category, the multiple versions of the first background include media items from the first category without including a media item from the second category, in accordance with a determination that a set of one or more categories of the plurality of categories includes the second category without including the first category, the multiple versions of the first background include media items from the second category without including a media item from the first category, and in accordance with a determination that a set of one or more categories of the plurality of categories includes the first category and the second category, the 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, a method is performed on a computer system having a display generating component. The method includes displaying, via the display generating component, a first representation of a system user interface, the distinct version of the system user interface including a distinct background and a distinct set of one or more system user interface objects overlaid on the distinct background, the first representation of the system user interface corresponding to a first version of the system user interface showing the first set of the one or more system user interface objects overlaid on the first background. The method further includes detecting, while displaying the first representation of the system user interface corresponding to the first version of the system user interface, an occurrence of a first condition that causes the computer system to alter an 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.The method includes, in response to detecting an occurrence of a first condition that causes the computer system to alter an appearance of the system user interface based on a first combination of a first background media item and a first filter for the system user interface, modifying the first background media item in a first manner in accordance with 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 satisfy a first requirement for the first combination of the first background media item and the first filter to satisfy the first criterion. and applying a first version of the first filter to the first background media item to create a second version of the system user interface; and in accordance with a determination that a first combination of the first background media item and the first filter satisfies a second criterion, the second criterion requiring that a first set of one or more visual characteristics of the first background media item satisfy a second requirement, the second criterion being different from the first requirement, applying the second version of the first filter to the first background media item by modifying the first background media item in a second manner different from the first manner to create the second version of the system user interface.

[0015] According to some embodiments, a method is performed on a computer system having a display generating component. The method includes displaying, via the display generating component, a wake screen user interface corresponding to a restricted state of the computer system, the wake screen user interface including displaying a first background and a plurality of system user interface objects covering at least a portion of the first background, the first background including 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 the restricted state of the computer system. The method includes, in response to detecting a first user input including a request to dismiss the wake screen user interface, moving the plurality of graphical elements in a first direction in accordance with the first user input while increasing a spatial gap between the plurality of graphical elements, and in response to determining that the request to dismiss the wake screen user interface included in the first user input satisfies a first criterion, replacing a display of the wake screen user interface corresponding to the restricted state of the computer system with a 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 a spatial gap between the plurality of graphical elements.

[0016] According to some embodiments, an electronic device includes a display, a touch-sensitive surface, optionally one or more sensors that detect intensity of contact with the touch-sensitive surface, optionally one or more tactile output generators, one or more processors, and a memory having stored thereon one or more programs, the one or more programs configured to be executed by the one or more processors, the one or more programs including instructions to perform or cause to be performed any of the operations of the methods described herein. According to some embodiments, a computer-readable storage medium has stored therein instructions that, when executed by an electronic device having a display, a touch-sensitive surface, optionally one or more sensors that detect intensity of contact with the touch-sensitive surface, and optionally one or more tactile output generators, cause the device to perform or cause to be performed any of the operations of the methods 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 that detect the intensity of contact with the touch-sensitive surface, optionally one or more tactile output generators, a memory, and one or more processors executing one or more programs stored in the memory includes one or more of the elements displayed in any of the methods described herein, and the elements are 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 that detect the intensity of contact with the touch-sensitive surface, optionally one or more tactile output generators, and means for performing or causing to be performed any of the operations of the methods described herein. According to some embodiments, an information processing apparatus for use in an electronic device having a display, a touch-sensitive surface, optionally one or more sensors that detect the intensity of contact with the touch-sensitive surface, optionally one or more tactile output generators includes means for performing or causing to be performed any of the operations of the methods described herein.

[0017] Thus, electronic devices having a display, a touch-sensitive surface, optionally one or more sensors for detecting intensity of contact 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 notification and / or status information, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may complement or replace conventional methods for modifying the user interface and displaying notification and / or status information. [Brief description of the drawings]

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

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

[0020] [Figure 1B] FIG. 2 is a block diagram illustrating example components for event processing according to some embodiments.

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

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

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

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

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

[0026] [Figure 6A] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6B] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6C] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6D] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6E] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6F] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6G] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6H] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6H2] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6H3] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6H4] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6H5] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6H6] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6I] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6J] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6K] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6L]1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6M] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6N] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6O] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6O2] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6P] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6Q] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6R] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6S] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6T] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6U] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6V] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6W] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6X] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6Y] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6Z] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6AA] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6AB] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6AC] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6A-D] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6AE] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6AF] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6A-G] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6AH] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6AI] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6AJ] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6AK] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6AL] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6AM] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6AN]1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6AO] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6AP] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6AQ] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments. [Figure 6AR] 1 illustrates an example user interface for an enhanced face switcher in accordance with some embodiments.

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

[0028] [Figure 8A] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8B] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8C] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8D] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8E] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8F] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8G]1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8H] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8I] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8J] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8K] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8L] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8M] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8N] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8O] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8P] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8Q] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8R] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8S] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8T] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8U] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8V] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8W] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8X] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8Y] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8Z] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8AA] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8AB] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8AC] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8A-D] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8AE] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8AF] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8A-G] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8AH] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8AI] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8AJ] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8AK] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8AL] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8AM] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments. [Figure 8AN] 1 illustrates an example user interface for displaying a session area for an ongoing event according to some embodiments.

[0029] [Figure 9A] FIG. 1 is a flow diagram of a process for modifying a user interface based on user input according to some embodiments. [Figure 9B]FIG. 1 is a flow diagram of a process for modifying a user interface based on user input according to some embodiments. [Figure 9C] FIG. 1 is a flow diagram of a process for modifying a user interface based on user input according to some embodiments. [Figure 9D] FIG. 1 is a flow diagram of a process for modifying a user interface based on user input according to some embodiments. [Figure 9E] FIG. 1 is a flow diagram of a process for modifying a user interface based on user input according to some embodiments. [Figure 9F] FIG. 1 is a flow diagram of a process for modifying a user interface based on user input according to some embodiments. [Figure 9G] FIG. 1 is a flow diagram of a process for modifying a user interface based on user input according to some embodiments. [Figure 9H] FIG. 1 is a flow diagram of a process for modifying a user interface based on user input according to some embodiments. [Figure 9I] FIG. 1 is a flow diagram of a process for modifying a user interface based on user input according to some embodiments.

[0030] [Figure 10A] FIG. 1 is a flow diagram of a process for selecting and / or changing a user interface in accordance with some embodiments. [Figure 10B] FIG. 1 is a flow diagram of a process for selecting and / or changing a user interface in accordance with some embodiments. [Figure 10C] FIG. 1 is a flow diagram of a process for selecting and / or changing a user interface in accordance with some embodiments. [Figure 10D] FIG. 1 is a flow diagram of a process for selecting and / or changing a user interface in accordance with some embodiments. [Figure 10E]FIG. 1 is a flow diagram of a process for selecting and / or changing a user interface in accordance with some embodiments. [Figure 10F] FIG. 1 is a flow diagram of a process for selecting and / or changing a user interface in accordance with some embodiments. [Figure 10G] FIG. 1 is a flow diagram of a process for selecting and / or changing a user interface in accordance with some embodiments. [Figure 10H] FIG. 1 is a flow diagram of a process for selecting and / or changing a user interface in accordance with some embodiments. [Figure 10I] FIG. 1 is a flow diagram of a process for selecting and / or changing a user interface in accordance with some embodiments.

[0031] [Figure 11A] FIG. 1 is a flow diagram of a process for modifying a user interface in accordance with some embodiments. [Figure 11B] FIG. 1 is a flow diagram of a process for modifying a user interface in accordance with some embodiments. [Figure 11C] FIG. 1 is a flow diagram of a process for modifying a user interface in accordance with some embodiments. [Figure 11D] FIG. 1 is a flow diagram of a process for modifying a user interface in accordance with some embodiments. [Figure 11E] FIG. 1 is a flow diagram of a process for modifying a user interface in accordance with some embodiments. [Figure 11F] FIG. 1 is a flow diagram of a process for modifying a user interface in accordance with some embodiments. [Figure 11G] FIG. 1 is a flow diagram of a process for modifying a user interface in accordance with some embodiments. [Figure 11H] FIG. 1 is a flow diagram of a process for modifying a user interface in accordance with some embodiments.

[0032] [Figure 12A] FIG. 1 is a flow diagram of a process for displaying representations of multiple notifications in different configurations according to some embodiments. [Figure 12B] FIG. 1 is a flow diagram of a process for displaying representations of multiple notifications in different configurations according to some embodiments. [Figure 12C] FIG. 1 is a flow diagram of a process for displaying representations of multiple notifications in different configurations according to some embodiments. [Figure 12D] FIG. 1 is a flow diagram of a process for displaying representations of multiple notifications in different configurations according to some embodiments. [Figure 12E] FIG. 1 is a flow diagram of a process for displaying representations of multiple notifications in different configurations according to some embodiments.

[0033] [Figure 13A] FIG. 1 is a flow diagram of a process for displaying status information in a session area based on a subscription according to some embodiments. [Figure 13B] FIG. 1 is a flow diagram of a process for displaying status information in a session area based on a subscription according to some embodiments. [Figure 13C] FIG. 1 is a flow diagram of a process for displaying status information in a session area based on a subscription according to some embodiments. [Figure 13D] FIG. 1 is a flow diagram of a process for displaying status information in a session area based on a subscription according to some embodiments. [Figure 13E] FIG. 1 is a flow diagram of a process for displaying status information in a session area based on a subscription according to some embodiments. [Figure 13F] FIG. 1 is a flow diagram of a process for displaying status information in a session area based on a subscription according to some embodiments. [Figure 13G]FIG. 1 is a flow diagram of a process for displaying status information in a session area based on a subscription according to some embodiments.

[0034] [Figure 14A] FIG. 1 is a flow diagram of a process for changing between different configurations in which renditions of notifications can be displayed, according to some embodiments. [Figure 14B] FIG. 1 is a flow diagram of a process for changing between different configurations in which renditions of notifications can be displayed, according to some embodiments. [Figure 14C] FIG. 1 is a flow diagram of a process for changing between different configurations in which renditions of notifications can be displayed, according to some embodiments. [Figure 14D] FIG. 1 is a flow diagram of a process for changing between different configurations in which renditions of notifications can be displayed, according to some embodiments. [Figure 14E] FIG. 1 is a flow diagram of a process for changing between different configurations in which renditions of notifications can be displayed, according to some embodiments. [Figure 14F] FIG. 1 is a flow diagram of a process for changing between different configurations in which renditions of notifications can be displayed, according to some embodiments. [Figure 14G] FIG. 1 is a flow diagram of a process for changing between different configurations in which renditions of notifications can be displayed, according to some embodiments.

[0035] [Figure 15A] FIG. 2 is a flow diagram of a process for automatically shuffling media items as a background according to some embodiments. [Figure 15B] FIG. 2 is a flow diagram of a process for automatically shuffling media items as a background according to some embodiments. [Figure 15C] FIG. 2 is a flow diagram of a process for automatically shuffling media items as a background according to some embodiments. [Figure 15D]FIG. 2 is a flow diagram of a process for automatically shuffling media items as a background according to some embodiments. [Figure 15E] FIG. 2 is a flow diagram of a process for automatically shuffling media items as a background according to some embodiments. [Figure 15F] FIG. 2 is a flow diagram of a process for automatically shuffling media items as a background according to some embodiments. [Figure 15G] FIG. 2 is a flow diagram of a process for automatically shuffling media items as a background according to some embodiments. [Figure 15H] FIG. 2 is a flow diagram of a process for automatically shuffling media items as a background according to some embodiments. [Figure 15I] FIG. 2 is a flow diagram of a process for automatically shuffling media items as a background according to some embodiments.

[0036] [Figure 16A] FIG. 11 is a flow diagram of a process for applying different versions of a filter to a background media item according to some embodiments. [Figure 16B] FIG. 11 is a flow diagram of a process for applying different versions of a filter to a background media item according to some embodiments. [Figure 16C] FIG. 11 is a flow diagram of a process for applying different versions of a filter to a background media item according to some embodiments. [Figure 16D] FIG. 11 is a flow diagram of a process for applying different versions of a filter to a background media item according to some embodiments. [Figure 16E] FIG. 11 is a flow diagram of a process for applying different versions of a filter to a background media item according to some embodiments. [Figure 16F] FIG. 11 is a flow diagram of a process for applying different versions of a filter to a background media item according to some embodiments. [Figure 16G] FIG. 11 is a flow diagram of a process for applying different versions of a filter to a background media item according to some embodiments. [Figure 16H] FIG. 11 is a flow diagram of a process for applying different versions of a filter to a background media item according to some embodiments. [Figure 16I] FIG. 11 is a flow diagram of a process for applying different versions of a filter to a background media item according to some embodiments. [Figure 16J] FIG. 11 is a flow diagram of a process for applying different versions of a filter to a background media item according to some embodiments.

[0037] [Figure 17A] FIG. 1 is a flow diagram of a process for animating a system user interface in accordance with some embodiments. [Figure 17B] FIG. 1 is a flow diagram of a process for animating a system user interface in accordance with some embodiments. [Figure 17C] FIG. 1 is a flow diagram of a process for animating a system user interface in accordance with some embodiments. [Figure 17D] FIG. 1 is a flow diagram of a process for animating a system user interface in accordance with some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0038] Many electronic devices have graphical user interfaces that allow users to navigate between application user interfaces and / or system user interfaces. Some methods for navigating between user interfaces allow for multitasking, such that individual applications continue to update in the background even after navigating away from the individual application user interfaces. Some methods for providing a system user interface limit the customization made to the system user interface and may obscure certain elements and / or status information displayed in the system user interface. For example, these methods may require the user to return to the respective application user interface to see the updates. In the embodiments described below, an improved method for providing status updates for multiple applications in a persistent session area is provided. This method streamlines the user's ability to view real-time status information for active sessions, thereby eliminating the need for an extra separate step of returning to the individual user interfaces of the individual applications to view the 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 to indicate user interface components that represent selectable options.

[0040] The processes described below improve the usability of the device and make the user's interface with the device more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the device) through a variety of techniques, including providing improved visual, audio, and / or haptic feedback to the user, reducing the number of inputs required to execute an operation, providing additional control options without cluttering the user interface with additional displayed controls, executing an operation when a set of conditions are met without requiring further user input, and / or additional techniques. These techniques also reduce power usage and improve the device's battery life by allowing 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 the respective types of user interfaces. Figures 6A-6AR show exemplary user interfaces for an enhanced face switcher. Figures 7A-7V-3 show representations of multiple notifications in different configurations and user inputs for switching between the different configurations. Figures 8A-8AN show exemplary user interfaces for displaying a session area of ​​ongoing events. Figures 9A-9I show a flow diagram of a method for modifying a user interface based on user input. Figures 10A-10I show a flow diagram of a method for selecting and / or modifying a user interface. Figures 11A-11H show a flow diagram of a method for modifying a user interface. Figures 12A-12E show a flow diagram of a method for displaying representations of multiple notifications in different configurations. Figures 13A-13G show a flow diagram of a method for displaying status information in a session area based on a subscription. 14A-14G show flow diagrams of a method for changing between different configurations in which a representation of multiple notifications can be displayed. FIGS. 15A-15I show flow diagrams of a process for automatically shuffling media items as a background, according to some embodiments. FIGS. 16A-16J show flow diagrams of a process for applying different versions of a filter to background media items, according to some embodiments. FIGS. 17A-17D show flow diagrams of a process for animating a system user interface, according to some embodiments. The user interfaces of FIGS. 5A-5CA, 6A-6AR, 7A-7V-3, and 8A-8AN are used to explain the processes of FIGS. 9A-9I, 10A-10I, 11A-11H, 12A-12E, 13A-13G, 14A-14G, 15A-15I, 16A-16J, and 17A-17D.

[0042] Exemplary Devices Reference will now be made in detail to the embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various embodiments being described. However, it will be apparent to those skilled in the art that the various embodiments described may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.

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

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

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

[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, that also includes other functions, such as PDA and / or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptops or tablet computers having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad), are optionally used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad).

[0047] In the following discussion, electronic devices are described that include a display and a touch-sensitive surface, however, it should be understood that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and / or a joystick.

[0048] The device typically supports a variety of applications, such as one or more of note-taking applications, drawing applications, presentation applications, word processing applications, website creation applications, disc authoring applications, spreadsheet applications, gaming applications, telephony 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] The various applications running on the device optionally use at least one common physical user-interface device, such as a touch-sensitive surface. One or more features of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or changed for each application and / or within individual applications. In this way, the common physical architecture of the device (such as the touch-sensitive surface) optionally supports a variety of applications with user interfaces that are intuitive and transparent to the user.

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

[0051] As used herein and in the claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, that will be detected by a user with the user's sense of touch. For example, in a situation where a device or a component of a device is in contact with a touch-sensitive surface of a user (e.g., the fingers, palm, or other part of a user's 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 a physical property of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "down-click" or "up-click" of a physical actuator button. In some cases, a user feels a tactile sensation such as a "down-click" or "up-click" even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement. As another example, movement of a touch-sensitive surface is optionally interpreted or sensed by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. Such user interpretation of touch depends on the user's personal sensory perception, but there are many sensory perceptions of touch that are common to a majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an "up click," a "down click," "roughness"), unless otherwise noted, the generated tactile output corresponds to a physical displacement of the device, or a component of the device, that produces the described sensory perception for a typical (or average) user.Using tactile output to provide haptic feedback to the user improves usability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate inputs when operating / interacting with the device and reducing user errors), as well as reducing power usage and improving the battery life of the device 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 movement waveform of the tactile output, the frequency of the tactile output, and / or the duration of the tactile output.

[0053] When tactile outputs having different tactile output patterns are generated by the device (e.g., via one or more tactile output generators that move a movable mass to generate the tactile output), the tactile outputs can cause different tactile sensations when a user holds or touches the device. Although the user's sensations are based on the user's perception of the tactile output, most users are able to discern changes in waveform, frequency, and amplitude of the tactile output generated by the device. Thus, the waveform, frequency, and amplitude can be adjusted to indicate to the user that different actions have been performed. Thus, in some situations, tactile output having a tactile output pattern designed, selected, and / or developed to simulate the properties (e.g., size, material, weight, stiffness, smoothness, etc.), behaviors (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 having virtual boundaries and virtual objects, an actual physical environment having physical boundaries and physical objects, and / or any combination of the above) provides a user with useful feedback that reduces input errors and increases the efficiency of a user's operation of the device. Additionally, the tactile output is optionally generated to correspond to feedback unrelated to simulated physical properties, such as input thresholds or object selection. In some situations, such tactile output provides a user with useful feedback that reduces input errors and increases the efficiency of a user's operation of the device.

[0054] In some embodiments, a tactile output with a suitable tactile output pattern serves as a cue to the appearance of an event of interest behind the scene in a user interface or device. Examples of events of interest include activation of an affordance (e.g., a real button, a virtual button, or a toggle switch) provided on the device or in the user interface, success or failure of a requested action, reaching or crossing a boundary in the user interface, entering a new state, switching input focus between objects, activating a new mode, reaching or crossing an input threshold, detection or recognition of a type of input or gesture, etc. In some embodiments, a tactile output is provided to act as a warning or alert to an impending event or outcome that will occur unless a redirection or interrupt 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 to users with visual or motor impairments or other accessibility needs, and / or improve the efficiency and functionality of the user interface and / or device. The tactile output, optionally accompanied by audio output and / or visible user interface changes, further enhances the user's experience when interacting with the user interface and / or device, facilitates better communication of information about the state of the user interface and / or device, reduces input errors, and increases the efficiency of the user's operation of the device.

[0055] It is understood that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than those shown, optionally combines two or more components, or optionally has a different configuration or arrangement of its components. The various components shown in FIG. 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 other components of device 100, such as CPU(s) 120 and peripherals interface 118, is optionally controlled by memory controller 122.

[0057] A peripheral interface 118 may be used to couple input and output peripherals of the device with the CPU(s) 120 and memory 102. The one or more processors 120 operate or execute various software programs and / or instruction sets stored in the memory 102 to perform various functions and process data for the device 100.

[0058] In some embodiments, peripherals interface 118, CPU(s) 120, and memory controller 122 are optionally implemented on a single chip, such as chip 104. In some other embodiments, they are optionally implemented on separate chips.

[0059] The radio frequency (RF) circuitry 108 transmits and receives RF signals, also referred to as electromagnetic signals. The RF circuitry 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 circuitry 108 optionally includes well-known circuits for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, etc. The RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet, and / or wireless networks, such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and with other devices, by wireless communication. The wireless communications options include 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), code division multiple access (CDMA), and code division multiple access (CDMA).access (CDMA), time division multiple access (TDMA), 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 (e.g., IEEE 802.11b), instant messaging and presence services (e.g., IEEE 802.11c), instant messaging and presence services (e.g., IEEE 802.11g), instant messaging and presence services (e.g., IEEE 802.11n ... The present invention may use any of a number of communications standards, protocols, and technologies, including, but not limited to, Intermediate System (IS) Intermediate Message Service (IMPS), and / or Short Message Service (SMS), or any other suitable communications protocol, including communications protocols 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 a user and the device 100. The audio circuit 110 receives audio data from the peripherals interface 118, converts the audio data into an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal into human audible sound waves. The audio circuit 110 also receives an electrical signal converted from the sound wave by the microphone 113. The audio circuit 110 converts the electrical signal into audio data, and transmits the audio data to the peripherals interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to the memory 102 and / or the RF circuit 108 by the peripherals interface 118. In some embodiments, the audio circuit 110 also includes a headset jack (e.g., 212, FIG. 2). The headset jack provides an interface between audio circuitry 110 and a detachable audio input / output peripheral such as an output-only headphone or a headset with both an output (e.g., one-ear or binaural headphones) and an input (e.g., a microphone).

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

[0062] Touch-sensitive display system 112 provides an input and output interface between the device and a user. Display controller 156 receives electrical signals from and / or transmits electrical signals to touch-sensitive display system 112. Touch-sensitive display system 112 displays visual output to the user. This visual output optionally includes graphics, text, icons, animation, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output corresponds to a user interface object. As used herein, the term "affordance" refers to a user-interactive graphical user interface object (e.g., a graphical user interface object that is configured to respond to input directed towards the graphical user interface object). Examples of user-interactive graphical user interface objects include, but are not limited to, a button, a slider, an icon, a selectable menu item, a switch, a hyperlink, or other user interface control.

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

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

[0065] Touch-sensitive display system 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the touchscreen video resolution is greater than 400 dpi (e.g., 500 dpi, 800 dpi, or higher). A user optionally contacts touch-sensitive display system 112 using any suitable object or appendage, such as a stylus, finger, or the like. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which may be less precise than stylus-based inputs due to the larger contact area of ​​a finger on a touchscreen than that of a stylus. In some embodiments, the device translates the rough finger input into precise pointer / cursor positions or commands to perform the actions desired by the user.

[0066] In some embodiments, in addition to a touchscreen, device 100 optionally includes a touchpad for activating or deactivating certain functions. In some embodiments, the touchpad is a touch-sensitive area of ​​the device that, unlike a touchscreen, does not display visual output. The touchpad is optionally a touch-sensitive surface separate from 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 provides power to the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, power failure detection circuitry, power converters or inverters, power status indicators (e.g., light emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power within a portable device.

[0068] Device 100 also optionally includes one or more light sensors 164 (e.g., as part of one or more cameras). FIG. 1A shows a light sensor coupled to a light sensor controller 158 in I / O subsystem 106. Light sensor(s) 164 optionally include a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Light sensor(s) 164 receive light from the environment, projected through one or more lenses, and convert the light into data representing an image. In conjunction with imaging module 143 (also referred to as a camera module), light sensor(s) 164 optionally captures still images and / or video. In some embodiments, the light sensor is located on the back of device 100, opposite touch-sensitive display system 112 on the front of the device, so that the touch screen can be used as a viewfinder for still and / or video image acquisition. In some embodiments, another light sensor is placed on the front of the device so that an image of the user is captured (e.g., for a selfie, for a video conference while the user views other video conference participants on the touch screen, etc.).

[0069] Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I / O subsystem 106. Contact intensity sensor(s) 165 optionally include one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor(s) 165 receive contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is juxtaposed with or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touchscreen display system 112, which is located on the front of device 100.

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

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

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

[0073] In some embodiments, the software components stored in memory 102 include an operating system 126, a communications module (or instruction set) 128, a contact / 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 applications (or instruction set) 136. Additionally, in some embodiments, as shown in Figures 1A and 3, memory 102 stores device / global internal state 157. Device / global internal state 157 includes one or more of: active application state, which indicates which applications, if any, are currently active; display state, which indicates what applications, views, or other information are occupying various areas of touch-sensitive display system 112; sensor state, which includes information obtained from the device's various sensors and other input or control devices 116; and position and / or location information regarding the device's position and / or orientation.

[0074] Operating system 126 (e.g., 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 facilitating communication between various hardware and software components.

[0075] The communications module 128 also includes various software components for facilitating communication with other devices via one or more external ports 124 and for processing data received by the RF circuitry 108 and / or the external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) are adapted to couple directly to other devices or indirectly via a network (e.g., Internet, wireless LAN, etc.). In some embodiments, the external ports are multi-pin (e.g., 30-pin) connectors identical to, 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 to, 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 that is identical to, similar to, and / or compatible with the USB Type-C connector used in several electronic devices from Apple Inc. of Cupertino, California.

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

[0077] Contact / motion module 130 optionally detects gesture input by a user. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different movements, timing, and / or strength of detected contacts). Thus, gestures are optionally detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger down event, followed by a finger up (lift off) event at the same location (or substantially the same location) as the finger down event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on a touch-sensitive surface includes detecting a finger down event, followed by one or more finger drag events, followed by a finger up (lift off) event. Similarly, taps, swipes, drags, and other gestures are optionally detected by detecting a particular contact pattern with respect to the stylus 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 is not related to the strength of the finger contact between detecting a finger down event and detecting a finger up event. In some embodiments, a tap gesture is detected according to determining that the length of time between a finger down event and a finger up event is less than a predefined value (e.g., less than 0.1, 0.2, 0.3, 0.4, or 0.5 seconds), regardless of whether the strength of the finger contact during the tap 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 may satisfy certain input criteria that do not require that the characteristic intensity of the contact meet a given intensity threshold in order for the particular input criterion to be met. For clarity, a finger contact in a tap gesture generally needs to meet a nominal contact detection intensity threshold below which the contact is not detected in order to detect a finger down event. A similar analysis applies to detecting a tap gesture or other contact with a stylus. In cases where the device is capable of detecting contact of a finger or stylus hovering over the touch-sensitive surface, the nominal contact-detection intensity threshold optionally does not correspond to physical contact between the finger or stylus and the touch-sensitive surface.

[0079] In a similar manner, the same concepts apply to other types of gestures. For example, swipe gestures, pinch gestures, de-pinch gestures, and / or long press gestures are optionally detected based on meeting criteria that are either unrelated to the intensity of the contacts included 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, swipe gestures are detected based on the amount of movement of one or more contacts. Pinch gestures are detected based on the movement of two or more contacts towards each other. De-pinch gestures are detected based on the movement of two or more contacts away from each other. Long press gestures are detected based on the duration of contact on the touch-sensitive surface with movement less than a threshold amount. Thus, a statement that a particular gesture recognition criterion does not require that the intensity of a contact(s) meet a corresponding intensity threshold in order for the particular gesture recognition criterion to be satisfied means that the particular gesture recognition criterion can be satisfied when the contact(s) in the gesture do not reach the corresponding intensity threshold, and can also be satisfied in situations where one or more of the contacts in the gesture reach or exceed the corresponding intensity threshold. In some embodiments, a tap gesture is detected based on a determination that a finger down event and a finger up event are detected within a predetermined time period, regardless of whether the contacts are above or below the respective intensity thresholds during the predetermined time period, and a swipe gesture is detected based on a determination that a movement of the contact is greater than a predetermined magnitude, even if the contacts exceed the respective intensity thresholds at the end of the movement of the contact. Even in implementations in which detection of gestures is affected by the strength of the contact performing the gesture (e.g., the device detects a long press more quickly when the intensity of the contact exceeds an intensity threshold, or the device is slow to detect a tap input when the intensity of the contact is higher), detection of those gestures does not require that the contact reach a particular intensity threshold, so long as the criteria for recognizing the gesture can be met in situations in which the contact does not reach a particular intensity threshold (e.g., even if the amount of time it takes to recognize the gesture varies).

[0080] The contact intensity threshold, duration threshold, and movement threshold are combined in various different combinations in some situations to create heuristics for distinguishing between two or more different gestures directed at the same input element or region, thereby enabling multiple different interactions with the same input element to provide a richer set of user interactions and responses. A statement that a particular set of gesture recognition criteria does not require the intensity of the contact(s) to meet the 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 having criteria that are satisfied when the gesture includes a contact having an intensity that exceeds the respective intensity threshold. For example, in some situations, a first gesture recognition criterion for a first gesture that does not require the intensity of the contact(s) to meet the 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 is dependent on the contact(s) reaching the corresponding intensity threshold. In such a competition, a gesture is optionally not recognized as satisfying the first gesture recognition criteria for the first gesture if the second gesture recognition criteria for the second gesture are satisfied first. For example, if the contact reaches the corresponding intensity threshold before it moves the predetermined amount of movement, a deep press gesture is detected rather than a swipe gesture. Conversely, if the contact moves the predetermined amount of movement before it reaches the corresponding intensity threshold, a swipe gesture is detected rather than a deep press gesture. Even in such a situation, the first gesture recognition criteria for the first gesture still do not require that the intensity of the contact(s) meet the corresponding intensity threshold for the first gesture recognition criteria 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 in intensity to above the corresponding intensity threshold), the gesture will have been recognized by the first gesture recognition criteria as a swipe gesture.In that way, a particular gesture recognition criterion that does not require that the intensity of the contact(s) meet a corresponding intensity threshold in order for the particular gesture recognition criterion to be satisfied may still be dependent on the intensity of the contact with respect to an intensity threshold in the sense that (A) in some circumstances it may ignore the intensity of the contact with respect to an intensity threshold (e.g., for a tap gesture) and / or (B) in some circumstances the particular gesture recognition criterion (e.g., for a long press gesture) will not function if a competing set of intensity-dependent gesture recognition criteria (e.g., for a deep press gesture) recognizes an input as corresponding to an intensity-dependent gesture before the particular gesture recognition criterion recognizes a gesture corresponding to the input (e.g., for a long press gesture that competes with a deep press gesture for recognition).

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

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

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

[0084] Text input module 134 is optionally a component of graphics module 132 and provides a soft keyboard for entering text in various applications (e.g., contacts 137, email 140, IM 141, browser 147, and any other application requiring text input).

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

[0086] Application 136 optionally includes the following modules (or sets of instructions), or a subset or superset thereof: ● a contacts module 137 (sometimes called an address book or contact list); ● Telephone module 138, ● Videoconferencing module 139; ● an email client module 140; ● Instant messaging (IM) module 141; ● Training support module 142, A camera module 143 for still and / or video images, ● Image management module 144, ● Browser module 147, ● Calendar module 148, A widget module 149, optionally including one or more of a weather widget 149-1, a stock price widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6; ● a widget creation module 150 for creating user-created widgets 149-6; ● Search module 151, ● A video and music player module 152, optionally consisting 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 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice duplication.

[0088] Contacts module 137, along with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, includes executable instructions for managing an address book or contact list (e.g., stored in memory 102 or in application internal state 192 of contacts module 137 in memory 370), including adding a name(s) to the address book, deleting a name(s) from the address book, associating phone number(s), email address(es), physical address(es), or other information with a name, associating an image with a name, categorizing and sorting names, providing phone numbers and / or email addresses to initiate and / or facilitate communication by phone 138, video conference 139, email 140, or IM 141, and the like.

[0089] In cooperation with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 includes executable instructions for entering a sequence of characters corresponding to a telephone number, accessing one or more telephone numbers in address book 137, modifying an entered telephone number, dialing each telephone number, conducting a conversation, and disconnecting or hanging up when the conversation is completed. As discussed above, the wireless communication optionally uses any of a number of communication standards, protocols, and technologies.

[0090] In cooperation with RF circuitry 108, audio circuitry 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, videoconferencing module 139 contains executable instructions to initiate, conduct, and terminate a videoconference between a user and one or more other participants according to the user's commands.

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

[0092] In cooperation with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for entering a series of characters corresponding to an instant message, modifying previously entered characters, sending each instant message (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephone-based instant messaging, or using XMPP, SIMPLE, Apple Push Notification Service (APNs), or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, sent and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments, such as those supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both telephone-based messaging (e.g., messages sent using SMS or MMS) and Internet-based messaging (e.g., messages sent using XMPP, SIMPLE, APNs, or IMPS).

[0093] In cooperation with the RF circuitry 108, the touch-sensitive display system 112, the display controller 156, the contact module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154, and the video and music player module 152, the training support module 142 includes executable instructions to create workouts (e.g., having time, distance, and / or calorie burn goals), communicate with training sensors (in the sports device and the smart watch), receive training sensor data, calibrate sensors used to monitor the workouts, select and play music for the workouts, and display, store, and transmit training data.

[0094] Camera module 143, along with touch-sensitive display system 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact module 130, graphics module 132, and image management module 144, contain executable instructions to capture still images or videos (including video streams) and store them in memory 102, change characteristics of the still images or videos, and / or delete still images or videos from memory 102.

[0095] Image management module 144, along with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, contain executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slide show or album), and storing still and / or video images.

[0096] Browser module 147, together with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contains executable instructions for browsing the Internet according to a user's commands, including retrieving, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0097] Calendar module 148, along with RF circuitry 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, contain executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) according to a user's instructions.

[0098] Together with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget module 149 is optionally a mini-application downloaded and used by a user (e.g., weather widget 149-1, stock price widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5), or a mini-application created by a user (e.g., user-created widget 149-6). In some embodiments, a widget includes a Hypertext Markup Language (HTML) file, a Cascading Style Sheets (CSS) file, and a JavaScript file. In some embodiments, a widget includes an Extensible Markup Language (XML) file and a JavaScript file (e.g., Yahoo! Widget).

[0099] In cooperation with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget creation module 150 contains executable instructions for creating widgets (e.g., turning user-specified portions of a web page into widgets).

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

[0101] In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 contains executable instructions that enable a user to download and play recorded music or other sound files stored in one or more file formats, such as MP3 or AAC files, as well as executable instructions to display, present, or otherwise play videos (e.g., on 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 cooperation with the touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, notes module 153 contains executable instructions for creating and managing notes, to-do lists, and the like according to user commands.

[0103] In conjunction with RF circuitry 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, map module 154 contains executable instructions to receive, display, modify, and store maps and map-related data (e.g., driving directions, data about businesses and other points of interest at or near a particular location, and other location-based data) in accordance with a user's instructions.

[0104] In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, online video module 155 contains executable instructions that enable a user to access, view, receive (e.g., by streaming and / or downloading), and play (e.g., on touch screen 112 or on an external display connected wirelessly or via external port 124) online videos in one or more file formats, such as H.264, and send and otherwise manage emails with links to particular online videos. In some embodiments, instant messaging module 141 is used rather than email client module 140 to send links to particular online videos.

[0105] Each of the above identified modules and applications corresponds to an executable instruction set that performs one or more of the functions described above, as well as the methods described in this application (e.g., computer-implemented methods and other information processing methods described herein). The modules (e.g., instruction sets) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of the modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the above identified modules and data structures. Additionally, memory 102 optionally stores additional modules and data structures not described above.

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

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

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

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

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

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

[0112] In some embodiments, event monitor 171 sends a request to peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and / or for longer than a predetermined period of time).

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

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

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

[0116] Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should process the sub-events. In most situations, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in a sub-event sequence that forms an event or potential event). 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 for which it was identified as the hit view.

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

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

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

[0120] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a separate view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a separate application view 191 includes multiple event recognizers 180. In other embodiments, one or more of the event recognizers 180 are part of a separate module, such as a user interface kit or a higher-level object from which application 136-1 inherits methods and other properties. In some embodiments, a separate event handler 190 includes one or more of a data updater 176, an object updater 177, a GUI updater 178, and / or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Instead, one or more of the application views 191 include one or more separate event handlers 190. In some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are also included in the separate application views 191.

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

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

[0123] The event comparator 184 compares the event information to predefined event or sub-event definitions and determines the event or sub-event or determines or updates the state of the event or sub-event based on the comparison. In some embodiments, the event comparator 184 includes an event definition 186. The event definition 186 includes definitions of events (e.g., a sequence of predefined 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 cancel, touch move, touch stop, and multiple touches. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap includes, for example, a first touch (touch start) for a predefined stage on the displayed object, a first lift-off (touch end) for a predefined stage, a second touch (touch start) for a predefined stage on the displayed object, and a second lift-off (touch end) for a predefined stage. In another example, a definition of event 2 (187-2) is a drag on a displayed object. Drag includes, for example, a touch (or contact) of a predetermined degree on a displayed object, a movement of the touch across the touch-sensitive display system 112, and a lift-off of the touch (end of the touch). In some embodiments, the event also includes information regarding one or more associated event handlers 190.

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

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

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

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

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

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

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

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

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

[0133] FIG. 2 illustrates portable multifunction device 100 having a touch screen (e.g., touch-sensitive display system 112, FIG. 1A ), according to some embodiments. The touch screen optionally displays one or more graphics in user interface (UI) 200. In these embodiments, as well as those described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale) or one or more styluses 203 (not drawn to scale). In some embodiments, selection of the one or more graphics is performed when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, upwards and / or downwards), and / or rolling of a finger in contact with device 100 (right to left, left to right, upwards and / or downwards). In some implementations or situations, accidental contact with a graphic does not select that graphic: for example, a swipe gesture sweeping over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

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

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

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

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

[0138] Attention is now directed to embodiments of a user interface (“UI”) that is optionally implemented on portable multifunction device 100.

[0139] 4A shows an exemplary user interface for a menu of applications on portable multifunction device 100, according to some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof: signal strength indicator(s) for wireless communication(s), such as cellular and Wi-Fi signals; ●Time, ●Bluetooth (registered trademark) indicator, ● Battery status indicator, Tray 408 with icons of frequently used applications, such as: ○ An icon 416 for the phone module 138, labeled “Phone”, optionally including an indicator 414 of the number of missed calls or voicemail messages; ○ An icon 418 of the email client module 140, labeled “Mail”, optionally including an indicator 410 of the number of unread emails; ○ Icon 420 of the Browser module 147, labeled "Browser"; ○ An icon 422 of the video and music player module 152 labeled "Music", ● Icons of other applications, such as: ○ Icon 424 of IM module 141, labeled "Messages"; ○ Icon 426 of the Calendar module 148, labeled "Calendar", ○ Icon 428 of the image management module 144, labeled "Photos"; ○ An icon 430 of the camera module 143, labeled “camera”; ○ Icon 432 of the online video module 155, labeled "Online Video"; Icon 434 of Stock Price Widget 149-2, labeled "Stock Price" ○ Icon 436 of the map module 154, labeled "Map"; ○ Icon 438 of weather widget 149-1, labeled "Weather"; ○ Icon 440 of alarm clock widget 149-4, labeled "Clock"; ○ Icon 442 of Training Support Module 142, labeled "Training Support"; ○ Icon 444 of the Notes module 153, labeled "Notes"; ○ An icon 446 for a settings application or module that provides access to settings related to the device 100 and its various applications 136.

[0140] 4A are merely examples. For example, other labels are optionally used for the various application icons. In some embodiments, the labels for individual application icons include the name of the application that corresponds to the individual application icon. In some embodiments, the label of a particular application icon is different from the name of the application that corresponds to that particular application icon.

[0141] FIG. 4B illustrates an exemplary user interface on a device (e.g., device 300, FIG. 3) having a touch-sensitive surface 451 (e.g., tablet or touchpad 355, FIG. 3) separate from a display 450. Although many of the following examples are given with reference to input on touchscreen display 112 (where the touch-sensitive surface and display are combined), in some embodiments, the device detects input on a touch-sensitive surface separate from the display, as shown in FIG. 4B. In some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B) has a major axis (e.g., 452 in FIG. 4B) that corresponds to a major axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). According to those embodiments, the device detects contact with touch-sensitive surface 451 (e.g., 460 and 462 in FIG. 4B) at locations that correspond to respective locations on the display (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In this manner, when the touch-sensitive surface is separate from the display, user input (e.g., contacts 460 and 462, and their movement) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B ) is used by the device to operate a user interface on the display (e.g., 450 in FIG. 4B ) of the multifunction device. It is to be understood that similar methods are optionally used for the other user interfaces described herein.

[0142] In addition, while the following examples 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 those finger inputs are replaced with input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture is optionally replaced by a mouse click (e.g., instead of a touch) followed by movement of a cursor along the path of the swipe (e.g., instead of moving a touch). As another example, a tap gesture is optionally replaced by a mouse click (e.g., instead of detecting a touch and then stopping detection of the touch) while the cursor is located over the location of the tap gesture. Similarly, it should be understood that when multiple user inputs are detected simultaneously, multiple computer mice are optionally used simultaneously, or mice and finger touches are optionally used simultaneously.

[0143] In some embodiments, the gesture includes an air gesture, which is a gesture that is detected without (or independent of) the user touching an input element that is part of a device (e.g., computer system 101, one or more input devices 125, and / or hand tracking device 140) and is based on detected movement of a part of the user's body (e.g., head, one or more arms, one or more hands, one or more fingers, and / or one or more legs) that is 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 of the user's hands relative to another user's hand, and / or movement of a user's finger relative to another finger or part of the user's hand), and / or absolute movement of the user's body part (e.g., a tap gesture that includes moving a hand in a predetermined pose a predetermined amount and / or speed, or a shake gesture that includes a predetermined speed or amount of rotation of the user's body part).

[0144] In some embodiments, input gestures used in various examples and embodiments described herein include air gestures performed by the movement of a user's finger(s) relative to other finger(s) or part(s) of the user's hand to interact with an XR environment (e.g., a virtual or mixed reality environment), according to some embodiments. In some embodiments, an air gesture is a gesture that is detected without the user touching an input element that is part of the device (or independent of an input element that is part of the device) and is based on detected movement of a part of the user's body that is 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 of the user's hands relative to another hand, and / or movement of the user's fingers relative to another finger or part of the user's hand), and / or absolute movement of the user's body part (e.g., a tap gesture that includes moving a hand in a predetermined pose a predetermined amount and / or speed, or a shake gesture that includes a predetermined speed or amount of rotation of the user's body part).

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

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

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

[0148] In some embodiments, the pinch input is part of an air gesture, including one or more of a pinch gesture, a long pinch gesture, a pinch-and-drag gesture, or a double pinch gesture. For example, the pinch gesture, which is an air gesture, includes moving two or more fingers of a hand to contact each other, i.e., optionally with a short interruption (e.g., within 0-1 seconds) after contacting each other. The long pinch gesture, which is an air gesture, includes moving two or more fingers of a hand to contact each other for at least a threshold time (e.g., at least 1 second) before detecting an interruption in contacting each other. For example, the long pinch gesture includes a user holding a pinch gesture (e.g., when two or more fingers are in contact), and the long pinch gesture continues until an interruption in contact between the two or more fingers is detected. In some embodiments, the double pinch gesture, which is an air gesture, includes two (e.g., or more) pinch inputs (e.g., performed by the same hand) that are detected directly (e.g., within a predetermined period of time) in succession to each other. For example, a user performs a first pinch input (e.g., a pinch input or a long pinch input), releases the first pinch input (e.g., breaking contact between two or more fingers), and performs a second pinch input within a predetermined period of time (e.g., within 1 second or within 2 seconds) after releasing the first pinch input.

[0149] In some embodiments, a pinch-and-drag gesture that is an air gesture includes a pinch gesture (e.g., a pinch gesture or a long pinch gesture) performed in conjunction with (e.g., followed by) a drag input that changes the position of the user's hand from a first position (e.g., a start position of the drag) to a second position (e.g., an end 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 apart) to end 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 to touch each other and moves the same hand to a second position in the air in a drag gesture). In some embodiments, the pinch input is performed by a first hand of the user and the drag input is performed by a second hand of the user (e.g., the second hand of the user moves from a first position to a second position in the air while the user continues the pinch input with the first hand of the user). 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 a user's hands. For example, an input gesture includes two (e.g., or more) pinch inputs performed in conjunction with one another (e.g., simultaneously or within a predetermined 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 a first hand of a user and a second pinch input performed using the other hand (e.g., a second hand of the user's two hands) in conjunction with performing the pinch input using the first hand. In some embodiments, a 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 a movement of a user's finger(s) towards the user interface element, a movement of a user's hand towards the user interface element, optionally with the user's finger(s) extended towards the user interface element, a downward movement of a user's finger (e.g., mimicking a mouse click action or a tap on a touch screen), or other predefined movement of the user's hand. In some embodiments, a tap input performed as an air gesture is detected based on a finger or hand movement characteristic performing a tap gesture movement of the finger or hand away from the user's viewpoint and / or towards the object that is the target of the tap input followed by an end of the movement. In some embodiments, an end of the movement is detected based on a change in the finger or hand movement characteristic performing the tap gesture (e.g., an end of the movement away from the user's viewpoint and / or towards the object that is the target of the tap input, a reversal of the finger or hand movement direction, and / or a reversal of the acceleration direction of the finger or hand movement).

[0151] The term "focus selector" as used herein refers to an input element that indicates the current portion of a user interface with which a user is interacting. In some implementations involving a cursor or other location marker, the cursor functions as a "focus selector" such that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 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 involving a touchscreen display (e.g., touch-sensitive display system 112 in FIG. 1A or touchscreen in FIG. 4A) that enables direct interaction with user interface elements on the touchscreen display, a contact detected on the touchscreen functions as a "focus selector" such that when an input (e.g., a press input by contact) is detected on the touchscreen display at the location of 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, focus is moved from one region of the user interface to another region of the user interface (e.g., by using the tab or arrow keys to move focus from one button to another) without a corresponding cursor movement or contact movement on the touchscreen display. In these implementations, the focus selector moves to follow the movement of focus between various regions of the user interface. Regardless of the specific form taken by the focus selector, the focus selector is generally a user interface element (or a contact on a touchscreen display) that is controlled by the user to communicate the user's intended interaction with the user interface (e.g., by indicating to the device which element of the user interface the user intends to interact with).For example, positioning of a focus selector (e.g., a cursor, contact, or selection box) over an individual button while a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen) indicates that the user intends to activate that individual button (and not other user interface elements shown on the device's display).

[0152] User Interface and Related Processes Attention is now directed to embodiments of user interfaces ("UI") and associated processes that may be implemented on an electronic device, such as portable multifunction device 100 or device 300, that includes a display and a touch-sensitive surface, (optionally) one or more tactile output generators for generating tactile output, and (optionally) one or more sensors for detecting the intensity of contact with the touch-sensitive surface.

[0153] 5A-5CA illustrate example user interfaces for navigating and editing each type of user interface, according to some embodiments, 6A-6AR illustrate example user interfaces for an enhanced face switcher, 7A-7V-3 illustrate representations of multiple notifications in different configurations and user inputs for switching between the different configurations, and 8A-8AN illustrate example user interfaces for displaying a session area of ​​an ongoing event, according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 9A-9I, 10A-10I, 11A-11H, 12A-12E, 13A-13G, 14A-14G, 15A-15I, 16A-16J, and 17A-17D. For ease of explanation, some of the 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 a respective finger or stylus contact, a representative point corresponding to a finger or stylus contact (e.g., the face centroid of a respective contact or a point associated with a respective contact), or the face centroid of two or more contacts detected on touch-sensitive display system 112. However, a similar operation is optionally performed on a device having display 450 and separate touch-sensitive surface 451 in response to detecting a contact on touch-sensitive surface 451 while displaying the user interface shown in the figure on display 450, along with a focus selector.

[0154] 5A-5CA are diagrams illustrating example user interfaces for navigating and editing each type of user interface according to some embodiments.

[0155] FIG. 5A illustrates a 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 an indication of the time and / or date. 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 the low power state after a predefined period of inactivity during which no user interaction with device 100 is detected. In some embodiments, the display enters the low power state in response to a user input to lock and / or sleep device 100, such as by pressing a physical or virtual button on device 100. In some embodiments, the display of device 100 leaves the low power state following receipt 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 indication of the alert and 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 by lifting the device, and / or user input on a physical or virtual button on the device.

[0156] As used herein, a wake screen user interface is a user interface that is displayed after the display of device 100 enters a low power state during which 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, operations described as being performed with respect to a wake screen user interface may also be described as being performed with respect to a face (e.g., "switching between wake screen user interfaces" can also be described as "switching between faces" and "editing wake screen user interfaces" can also be described as "editing faces"). In some embodiments, an "enhanced face switcher" user interface includes the display of one or more faces (e.g., one or more wake screen user interfaces), where the size of an individual face (e.g., wake screen user interface) is less than the full size of the display area (e.g., as shown in FIG. 5U). In some embodiments, in the low power state, the display optionally displays an "always on" indicator of the time and / or date, and the device displays the wake screen user interface when the device is prompted to exit the low power state. In some embodiments, optionally in response to user input and / or the passage of a threshold time, the device enters a locked state in which a password, passcode, and / or biometric authentication is required to unlock the device, and in the locked state the device has limited functionality and must be unlocked before accessing respective applications and / or data stored on device 100. In some embodiments, a wake screen user interface is displayed regardless of whether the device is in a locked state or has already been unlocked (e.g., the wake screen user interface is displayed when the user boots the device before accessing the home screen user interface and / or other application user interfaces).In some embodiments, as used herein, a cover sheet user interface includes the same characteristics as a wake screen user interface, but a user can optionally view the cover sheet user interface without entering a locked and / or low power state of the device. In some embodiments, one or more alerts (e.g., system alerts and / or notifications) are displayed in the wake screen user interface and / or the cover sheet user interface, optionally in response to a user input (e.g., a swipe gesture upwards in the center of the display or another gesture).

[0157] As used herein, a home screen user interface includes icons for navigating to multiple applications executed by device 100. In some embodiments, a 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 individual application's user interface. In some embodiments, multiple views of the home screen user interface are available. For example, a user can swipe or otherwise navigate between multiple views, each view of the home screen user interface including different application icons for different applications. In some embodiments, the application icons are different sizes, such as application widgets that display information for the individual applications, and the application widgets are larger than the application icons.

[0158] As used herein, mini-application objects (or widgets) are user interface objects that provide a limited subset of functionality and / or information available from their corresponding applications without requiring the launch of the application. In some embodiments, mini-application objects (or widgets) contain application content that is dynamically updated based on a 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 that resides in the device's memory, separate from the associated application that also 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 respective mini-application object's corresponding full-featured application. In some embodiments, the mini-application objects are configured to perform a subset, less than all, of the functionality of the corresponding application. In some embodiments, the mini-application object displays an identifier for the corresponding application. In some embodiments, the mini-application object displays a portion of the content from the corresponding application. For example, a map mini-application object displays a portion of a map that is displayed in the map application that corresponds to the map mini-application object. For example, a calendar mini-application object displays a portion of a calendar that is displayed in a corresponding calendar application. In some embodiments, certain inputs on the mini-application object launch the corresponding application.In some embodiments, a mini application object operates as a standalone application that is also present in the device's memory, separate from the associated application that is also present 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 that has a subset, less than all, of the functionality of the corresponding application, 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 in scenarios where the social networking application is not running, the mini application object continues to operate. In some embodiments, a mini application object operates as an extension or component of an associated application on the device. For example, a mini application object for a calendar application is a single function or operating component of a full-featured calendar application. In this example, if the calendar application is not running (e.g., in the background), then the calendar mini application object does not operate either. 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 the user opens the corresponding application while composing a reply message, the contents of the reply message are retrieved from the temporary storage location and used by the full-featured application to allow the user to complete the reply message.

[0159] In some embodiments, while the device is waking up and leaving a low power state, an animation is displayed as the device transitions from off (e.g., optionally displaying a black background with an "always on" time and / or date) to displaying a wake screen user interface 501 (also referred to herein as a lock screen user interface). In some embodiments, the wake screen user interface 501 is a user interface that includes an indication of the time and / or date, optionally one or more complications (e.g., a workout complication 502-1, a weather complication 502-2, and a calendar complication 502-3) that correspond to and update with current status information of the respective applications, optionally one or more alerts (e.g., a message notification 503-1 and a social media notification 503-2), optionally shortcuts to one or more applications (e.g., a flashlight and / or a camera), and a background (e.g., an image, a pattern, a color, and / or a photo). In some embodiments, as described in more detail below, a user can modify 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 the complications included in the wake screen user interface. In some embodiments, device 100 stores multiple wake screen user interfaces and rotates through the multiple wake screen user interfaces (optionally periodically and / or when entering / exiting a low power state).

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

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

[0162] 5C, in response to user input 504, a wake screen user interface 505 is displayed sliding up and out of the display area while maintaining one or more features of the wake screen user interface (e.g., an indication of time and / or date, one or more complications, and / or 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 middle 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 in accordance with the home screen user interface 506 that is being displayed.

[0163] 5D shows a home screen user interface 506 with a gradient background with different shades of gray arranged in the same arrangement as the wake screen user interface, such that an animation of shifting shades of gray completes a full cycle as the user swipes up to navigate to the home screen user interface.

[0164] 5E-5F illustrate examples of animated transitions during which device 100 transitions from a low power state to display 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, intermediate wake screen user interface 507-1 does not include one or more features of wake screen user interface 507-2 (e.g., no complications, notifications, and / or flashlight or camera shortcuts). In some embodiments, wake screen user interface 507-2 includes an image such as a plurality of colored lines (e.g., a rainbow or flags). In some embodiments, the animated transition includes increasing a 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, optionally by fading in one or more complications, and displaying one or more alerts, optionally by fading in one or more complications.

[0165] 5G-5H show examples of animated transitions of a wake screen user interface 508-2 with a portrait style photo. In some embodiments, the portrait style photo includes a subject (e.g., a person and / or face) that is 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 photo. In some embodiments, the animated transition of the wake screen user interface with a portrait style photo 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 an overlaid time and / or date indication. In some embodiments, the animated transition includes applying a depth effect (e.g., the photo appears flat in FIG. 5G and with a depth effect in FIG. 5H). In some embodiments, the wake screen user interface with a portrait style photo does not include one or more complications (optionally, the user can add one or more complications by editing the wake screen user interface).

[0166] 5I-5J illustrate examples of animated transitions of wake screen user interface 509-2 including one or more emojis. In some embodiments, wake screen user interface 509-2 includes one or more emojis arranged in a predefined pattern. For example, in FIGS. 5I-5J, smiley face emojis are displayed in a grid pattern. In some embodiments, the animated transition includes changing a shadow effect applied to the smiley face emoji as displayed in user interface 509-1 to a different shadow effect as displayed 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 increases and decreases during the animation.

[0167] 5K-5L show examples of animated transitions of the wake screen user interface 510-2 including an astronomy background. In some embodiments, the astronomy background includes celestial and / or planetary bodies (e.g., Earth, Moon, stars, solar system, and / or galaxy). In some embodiments, the animated transition includes changing the cropping and / or changing the viewing angle of the astronomy background from the user interface 510-1 to the wake screen user interface 510-2. In some embodiments, the animated transition includes applying visual effects such as reducing and / or moving a shadow displayed on the background. For example, the Earth appears to rotate and the shadow on the left side of the Earth appears to rotate with the Earth, so that the shadow is minimized to the right side of the user interface. In some embodiments, the astronomy background 510-2 further includes an indication of the current location of the device 100 (e.g., a dot is displayed on the displayed Earth of the user interface 510-2 at the location of the device).

[0168] 5L2-5L3 show an example of an animated transition from a wake screen user interface 510-3 including an astronomy background to a home screen user interface 510-4 including an astronomy background. In some embodiments, the wake screen user interface 510-3 includes a representation of one or more celestial spheres, e.g., the Earth and the Sun shown in FIG. 5L2. In some embodiments, in response to a user input 515 requesting to dismiss the wake screen user interface 510-3, the device 100 displays the 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 including a representation of one or more celestial spheres that are different from the representation of the one or more celestial spheres displayed in the wake screen user interface 510-3. For example, as shown in FIG. 5L3, during the animated transition, the representation of the Earth is displayed to rotate and shift into a different portion 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 may be shifted to appear relatively closer to the representation of the Earth and / or may be shifted to appear in a position directly behind the representation of the Earth (e.g., instead of above and to the left, as shown in FIG. 5L2). In some embodiments, during the animated transition, the representation of the Earth may be shifted to increase in size (e.g., closer) and the representation of the sun may be updated in size relative to the increasing size of the representation of the Earth.

[0169] 5M illustrates an example of a wake screen user interface 511. In some embodiments, the wake screen user interface 511 is an example of an astronomy background (e.g., including the moon). In some embodiments, a user can interact with the wake screen user interface 511 to cause the device 100 to perform a respective action. 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 respiration complication 502-7. In some embodiments, at least one complication updates with status information corresponding to an application associated with the complication. For example, the music complication 502-4 updates with progress information (e.g., a circular, curved, or linear shape) indicating the amount of time a currently playing media item has been played, and the weather complication 502-6 updates to indicate a real-time AQI level (e.g., "32") based on the state of the weather application.

[0170] In some embodiments, upon selection of the respective complication in response to a first type of user input, such as user input 512, device 100 displays an application user interface for the application associated with the respective complication. In some embodiments, the first type of user input is a tap input. For example, in response to user input 512 for health complication 502-5, device 100 displays a user interface for the health / fitness application associated with health complication 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., not within the center of the wake screen and / or on an edge of the wake screen), the device 100 displays multiple notifications, such as the user interface 532 shown in FIG. 5O.

[0172] In some embodiments, 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) that is the direction of the second type of user input 514, which is optionally the same direction, the device displays a home screen user interface 518. 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] FIG. 5N illustrates a home screen user interface 518 (also referred to as a home user interface). In some embodiments, the home screen user interface includes icons for navigating to multiple applications executed by the device 100. In some embodiments, a user can interact with the device 100 using one or more gestures, including touch input. For example, a tap input (e.g., user input 524) on an individual application icon launches the individual application on a display area of ​​the device 100 or otherwise opens the individual application's user interface. In some embodiments, multiple views of the home screen user interface are available. For example, a user can swipe or otherwise navigate between multiple views, each view of the home screen user interface including different application icons for different applications. In some embodiments, the application icons are different sizes, such as application widgets that display information for the 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) initiated at a top 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, the user input 522 is a swipe user input in a fourth direction (e.g., from right to left) and corresponds to a request to switch to another view of the home screen user interface, for example, different views of the home screen user interface displaying 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 application icon 422 for a music application. In some embodiments, in response to user input 524, device 100 displays a user interface of the application associated with application icon 422 (e.g., a music application user interface).

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

[0178] In some embodiments, user input 526 is detected at a predetermined portion of the user interface (e.g., a swipe up gesture initiated at an edge of the display of device 100). 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 device 100.

[0179] In some embodiments, a different type of input, such as user input 528 (e.g., a left-to-right swipe input initiated at the left edge of the display of device 100 or other gesture), causes device 100 to display a user interface that includes a search bar and, optionally, one or more widgets and / or shortcuts that display information about a subset of the applications.

[0180] In some embodiments, user input 530 (e.g., a downward swipe input initiated at the top edge of the display of device 100 or other gestures) is detected, and in response to user input 530, user interface 532 (FIG. 5O) is displayed. Thus, a user can interact with device 100 using different types of inputs and / or gestures to cause 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] 5O illustrates a cover sheet user interface 532 that includes information that is also displayed in wake screen user interface 511. For example, user interface 532 optionally includes an indication of the time and / or date, one or more complications, shortcut options to a flashlight and / or camera, and / or multiple notifications. In some embodiments, the user is allowed to interact with user interface 532 in the same manner that the user is allowed to interact with wake screen user interface 511, such as via a tap input on a complication to open a respective application associated with the complication, or a swipe input initiated at the right edge of the display of device 100, such as user input 534 to display user interface 536 (FIG. 5P) for a camera application, allowing the user to capture and / or view photos using the camera application.

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

[0183] In some embodiments, as shown in FIG. 5Q, a user input 541, such as a right-to-left swipe input detected within a predetermined area of ​​the display of device 100 (e.g., within a predetermined distance from the bottom edge of the display), causes device 100 to cycle from wake screen user interface 540-1 to another wake screen user interface 540-2. In some embodiments, device 100 cycles through a set of predefined wake screen user interfaces. In some embodiments, the predefined set of wake screen user interfaces are related. For example, in the case of an astronomy wake screen user interface (e.g., an image of the moon), cycling through a set of predefined astronomy wake screen user interfaces includes displaying different phases of the moon. In some embodiments, the predefined set of wake screen user interfaces is defined by the user such that the user selects a set of wake screen user interfaces to cycle through, whether the wake screens are related or not. For example, the user selects a photo album as the 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 periodically (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 the next time the display wakes up).

[0185] FIG. 5R illustrates a wake screen user interface 540-2 that replaces the wake screen user interface 540-1 in response to user input 541. In some embodiments, the wake screen user interface 540-2 includes at least one feature that differs from the 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 characteristics of the wake screen user interface, such as the type of complication, do not change. It will be appreciated that any combination of features can be updated between the first and second wake screen user interfaces, including a subset of the time and / or date indication, less than all or all complication changes, and / or font properties.

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

[0187] In some embodiments, pursuant to a determination that device 100 is in a locked state, before displaying wake screen selector user interface 548-1, device 100 requires authentication to unlock the device and displays 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] 5T illustrates a 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 representation 552 of a portion of a first wake screen user interface (e.g., wake screen user interface 540-1), a representation 550 of a portion of a second wake screen user interface (e.g., wake screen user interface 540-2), and a representation 554 of a portion of a third wake screen user interface (e.g., wake screen user interface 507-1 (FIG. 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 optionally cycles through, as described above.

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

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

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

[0192] FIG. 5U illustrates that the enhanced face switcher user interface 561 includes a representation 550 of a wake screen user interface (e.g., in the center of the enhanced face switcher user interface 561) and at least a portion of a representation of a home screen user interface 551 associated with the representation 550 of the wake screen user interface. For example, one or more of the respective wake screen user interfaces have a corresponding respective 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, in response to the user navigating from the wake screen to a 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 with which the home screen is associated.

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

[0194] In some embodiments, the enhanced face switcher user interface 561 includes a user selectable button 564 for adding a new wake screen and / or home screen to a set of wake screens and home screens stored and displayed in the enhanced face switcher user interface 561. In some embodiments, the user is enabled to scroll left and / or right to navigate between wake screen and home screen options within the set of wake screens and home screens in the enhanced face switcher user interface 561. In some embodiments, the enhanced face switcher user interface 561 further includes a user selectable option 553 for customizing the wake screen in the center of the enhanced face switcher user interface 561. For example, a user selection input at option 553 opens an edit user interface (e.g., edit user interface 565 of FIG. 5X) for the wake screen corresponding to the representation 550. In some embodiments, the enhanced face switcher user interface 561 includes an option 555 for changing the background image of the background of the wake screen corresponding to the representation 550. In some embodiments, in response to a user selection input at 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] 5V illustrates updating wake screen selector user interface 548-1 to wake screen selector user interface 548-2, which causes wake screen user interface representation 554 to be centered in the wake screen selector user interface. In some embodiments, wake screen selector user interface 548-2 is displayed in response to a user input 558, such as a tap input or other selection input on representation 554, or a right-to-left swipe input or other scrolling input, which causes the device to shift representations of the wake screen user interface that are in the field of view to center wake screen user interface representation 554 and move the previously centered wake screen user interface representation 550 to the left of wake screen selector user interface 548-2 (optionally sliding a portion of representation 550 off the display).

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

[0197] FIG. 5W illustrates a wake screen user interface 563 that is displayed in response to a user input (e.g., user input 562) corresponding to a request to rapidly switch the wake screen user interface. In some embodiments, the user input requesting to rapidly switch the wake screen user interface includes a long press input (e.g., user input 544 of FIG. 5R) that is initiated on the displayed wake screen user interface 540-2, where the long press input is maintained (e.g., the input contact is continued) while displaying the wake screen selector user interface 548-1 (FIG. 5T), and while the long press input is ongoing, the input changes position (e.g., swipes in a first direction), such as user input 562 sliding from right to left. In some embodiments, pursuant to a 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 such that the wake screen is displayed as the current wake screen. For example, in Figure 5T, the user swipes left until representation 554 is centered (or substantially centered) in wake screen selector user interface 548-1, as shown in Figure 5W, and then lifts the user input to display wake screen 563 associated with representation 554. In some embodiments, quickly toggling the wake screen user interface does not display enhanced face switcher user interface 561.

[0198] In some embodiments, as shown in FIG. 5W, device 100 displays edit user interface 565-a (FIG. 5W1) or edit user interface 563 (FIG. 5X) in response to user input 564 on the time and / or date indication displayed on 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, edit user interface 565-a shown in FIG. 5W1 includes a complication reticle 572 that is displayed behind or at least partially obstructed by a subject of the background image (e.g., a star). In some embodiments, reticle 572 is displayed in front of a subject of the background image (e.g., a star) in response to a user interaction to edit one or more visual characteristics of the wake screen user interface, such as user input 571-a directed at reticle 572.

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

[0200] In some embodiments, the editing user interface 565 includes multiple reticles that indicate portions of the wake screen user interface that are customizable. For example, a reticle 568 around the date and a reticle 569 around the time indicate that the date and time are editable (e.g., the text font and / or the type of information displayed), and a reticle 572 indicates that one or more complications are customizable (e.g., the user can add, remove, and edit complications displayed in the wake screen user interface 563). In some embodiments, 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 for 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 exit the editing user interface 565 (in response to selection of the "Done" option 566).

[0201] 5X illustrates a user input 576, such as a tap input or other selection input, to add a complication 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 that includes a number of available and / or recommended complications that the user can add to the wake screen user interface 563, as shown in FIG. 5Y. For example, in response to user input 571 (e.g., a tap input or other selection input) selecting a recommended set of complications that includes a health complication, a respiration complication, and a calendar complication, the device adds the set of complications to a predetermined portion of the wake screen user interface, optionally below a time indication.

[0202] In some embodiments, the user interface element 570 includes multiple complications, each 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 "Breathe" application) is displayed. In some embodiments, an application provides multiple complications (e.g., multiple options for having different designs and / or displaying different status information for the complications for the individual applications). In some embodiments, third party providers offering individual applications are enabled to design one or more complications for the individual applications (e.g., using an API). In some embodiments, each complication includes status information for the individual application. For example, a calendar complication includes an upcoming event ("11:00 AM event") that is saved on the user's calendar. In some embodiments, a health complication includes an indication of the distance of the current workout and / or the amount of activity for the day. 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., the sun for clear weather, or clouds with rain for rainy weather).

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

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

[0205] 5AA illustrates a user input 580, such as a tap input or other selection input, that selects the health complication 502-11. In some embodiments, the user input 580 further illustrates a right-to-left movement of the health complication 502-11 (e.g., via a drag gesture and / or a swipe gesture). In some embodiments, in response to the user input 580, the complication is repositioned in the user interface 565 with the health complication 502-11 to the left of the calendar complication 502-10, as shown in FIG.

[0206] 5AB illustrates a 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 in user interface element 570. In some embodiments, user interface element 570 is scrollable so that the user can view additional complications available to add to the wake screen user interface.

[0207] FIG. 5AC illustrates that in response to user input 582, device 100 replaces display of calendar complication 502-10 with breathe complication 502-12. In some embodiments, the predefined area for displaying complications has a maximum size and / or a maximum number of complications that can fit within the predefined area. For example, the predefined 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, one or more complications are automatically removed in response to user input and a complication is added to the predefined area according to a determination that the additional complication cannot fit within the predefined area. In some embodiments, in FIG. 5AC, user interface element 570 is optionally minimized or closed. In some embodiments, the user can reopen user interface element 570 by tapping or otherwise selecting a complication in edit user interface 565.

[0208] 5AD illustrates a user interface element 586 that is displayed in response to detecting a user input 584 at a location within the current reticle 569. In some embodiments, the user interface element 586 includes options for changing 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 style of both the date and the time is updated in response to a user input to change the text style. In some embodiments, the user can select different text styles for the date and the time.

[0209] In some embodiments, the user can change the color of the hour. In some embodiments, a recommended color for the hour is provided (e.g., as shown in FIG. 5AE). In some embodiments, the recommended colors include vibrant materials, black and / or white (e.g., depending on the background color), and / or one or more colors derived from the background (e.g., colors that match or complement the colors of a photo used as the background). In some embodiments, the user can customize the color to select a different color not included in the recommended colors to be applied to the hour. In some embodiments, the user can customize the color by sampling a portion of the background, where the selected color matches the sampled portion of the background.

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

[0211] FIG. 5AF illustrates a user input 596 selecting to change the information displayed as the date indication 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, the user interface element 594 optionally includes one or more text properties (e.g., font and / or color options) that allow the user to select to change the text properties of the date indication (e.g., apart from changing the text characteristics of the time indication as described above). FIG. 5AG illustrates that in response to the user input 596, the date indication is updated to display the day of the week (e.g., "Friday") without displaying the current month and date. In some embodiments, the user input 598 selects a done option 566 to exit the editing user interface 565. In some embodiments, in response to the user input 598 selecting the done option 566, the device 100 stops displaying the editing user interface 565 and displays a wake screen user interface 5001 having the properties selected by the user in the editing user interface, as shown in FIG. 5AH.

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

[0213] In some embodiments, a wake screen user interface that includes a photo as a background image (such as, for example, the portrait style background image shown in FIG. 5AI) displays the photo in an aspect ratio that is different from the aspect ratio of the saved photo (e.g., if stored in a Photos application). For example, device 100 automatically centers, zooms, and / or crops the photo stored in the Photos application to be displayed as the background of the wake screen user interface.

[0214] In some embodiments, photo-style wake screen user interfaces, including the portrait-style wake screen user interface shown in FIG. 5AI, include live photos that are 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 multiple interpolated frames such that the photo appears animated (e.g., to show the movement of an individual displayed in the wake screen user interface 5001).

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

[0216] 5AJ, in some embodiments, the edit user interface 565-2 includes the same set of features as the edit user interface 565, such as date and / or time indication reticles 568 and / or 569, a cancel option 567, a done option 566, and an indication 574 that additional views of the user interface are available. In some embodiments, a crop indication 5003 is optionally displayed to indicate that the background image of the wake screen user interface can be resized and / or scaled. In some embodiments, the crop indication 5003 optionally includes a text indication 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 photo used as the background of the wake user interface 5001.

[0217] 5AJ further illustrates 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 decreases 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, the pinch gesture 5004 is an outward pinch gesture that zooms in on the subject as shown in FIG. 5AK, while the pinch gesture 5006 (e.g., an inward pinch gesture) zooms out on the subject as shown in FIG. 5AL.

[0218] In some embodiments, reticles 568 and / or 569 are optionally not displayed while a user input is detected to change the cropping of the background photograph. In some embodiments, pursuant to a determination that the subject of the portrait style user interface has a size such that the subject overlaps a portion of the time and / or date indication, the subject is optionally displayed overlaying the time and / or date indication. In some embodiments, the subject is optionally displayed as overlaying multiple complications. In some embodiments, multiple complications are optionally displayed over the subject of the portrait style wake screen user interface.

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

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

[0221] 5AO illustrates the edit user interface 565-2 after minimizing or closing user interface element 586 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 corresponds to a different set of visual characteristics, optionally 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 change the color effect (e.g., monochrome, sepia, or neon) and / or level of shadow 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 interface that includes a photo as a background image, the multiple views include a background image 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, for example different phases of the moon.

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

[0223] In some embodiments, a user can see multiple views by scrolling the views while device 100 displays editing user interface 565-2. FIG. 5AO shows user input 5014-1, such as a swipe input or other input (e.g., tapping on a respective side of the user interface to scroll in a respective direction). In some embodiments, user input 5014-1 is initiated by a contact detected at a first location, the contact moving in a first direction (e.g., from right to left or from left to right). In some embodiments, following user input 5014-1, optionally continuing in the same direction as user input 5014-2, device 100 updates the view of the editing user interface to display at least a portion of a second view of the wake screen user interface. In some embodiments, a portion of the second view is gradually displayed as if the second view is sliding onto the display, while the first view is gradually removed from the display as if it is sliding off the display.

[0224] FIG. 5AP illustrates a portion of a second view sliding onto 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 view and the second view. 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 visual elements that are maintained correspond to visual elements of the wake screen user interface that were previously modified by the user (e.g., in the current editing session and / or in a previous editing session). For example, the user changed the date and time indication and the user changed the size of the object in the background photo. In some embodiments, the date and time indication and the object in the background photo do not move while the second view slides onto the display. In some embodiments, a set of visual elements that were optionally not modified by the user in the current editing session and / or in a previous editing session are moved off the display with the first view and replaced by another set of visual elements. For example, the complications and background color appear to slide off the display according to the user input 5014-2.

[0225] FIG. 5AQ shows user input 5014-3 swiping in a direction opposite to that of user input 5014-2. In some embodiments, user input 5014-3 is optionally a continuation of user inputs 5014-1 and 5014-2, where user input 5014-3 maintains contact with the display and changes to swiping in another direction. In some embodiments, the portion of the second view that slid onto the display in FIG. 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 views onto and / or removing views from editing user interface 565-2.

[0226] 5AR shows user input 5014-4, optionally as a continuation of user input 5014-3, swiping in the same direction as user interface 5014-2 to slide a second view of the wake screen user interface onto the display. In some embodiments, as user input 5014-5 continues to swipe from right to left, as shown in FIG. 5AS, optionally, most 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 in edit user interface 565-2 without displaying the first view of the wake screen user interface, as shown in FIG. 5AT.

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

[0228] In some embodiments, while a user is switching views of the wake screen user interface (e.g., via user input 5014), one or more edit options are optionally not displayed. For example, a reticle, a done option, a cancel option, and / or an indication of additional views are optionally not displayed until a single view is displayed. For example, in FIG. 5AT, a second view is displayed, the first view is no longer displayed, and one or more edit options are re-displayed.

[0229] In some embodiments, user input 5016 is detected on a complication displayed in a second view of edit 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 FIG. 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] FIG. 5AV shows a user input 5020 requesting to switch views in the editing user interface after editing a complication.

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

[0232] FIG. 5AX illustrates the wake screen user interface 5024 displayed with visual features selected by the user during the editing process.

[0233] 5AX2 illustrates an editing user interface 565-3 for editing a wake screen user interface that includes a textual indication of a date, a textual indication of a time, and multiple complications. In some embodiments, each complication is displayed with an affordance for removing the complication. For example, a minus sign, "x," or other removal affordance is displayed at a corner of the complication that optionally overlaps the complication.

[0234] In some embodiments, device 100 detects user input 5080 (e.g., a tap input or other selection input) that selects complication 5089-1. In some embodiments, in response to user input 5080, device 10 displays user interface element 5082 for changing the size of selected complication 5089-1. For example, device 100 provides multiple size options for displaying information of 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 complication 5089-1, and in response to the user input, complication 5089-1 is updated to the selected size, as shown in FIG. 5AX4.

[0235] Figure 5AX3 shows device 100 detecting user input 5086 selecting 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] FIG. 5AX3 further illustrates a user input 5088 corresponding to a selection of a reticle for the textual indication of the date. In some embodiments, in response to the user input 5088, the device 100 displays a user interface element 5090 for changing the content displayed in the area above the textual indication of the time. For example, the user may select a complication from a plurality of complications displayed in the user interface element 5090. In some embodiments, the complications that the user may select to display above the textual indication of the time are a different set of complications than the set of complications that the user may select to display below the textual indication of the time (e.g., the set of complications displayed in the user interface element 570, as described with reference to FIGS. 5AA-5AC). For example, the complications displayed above the textual indication of the time are text-based complications and / or have a different size (e.g., height and / or length) than the complications displayed below the textual indication of the time.

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

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

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

[0240] FIG. 5BB illustrates a second view of the wake screen user interface. In some embodiments, the background image of the wake screen user interface includes, for example, in the case of an astronomy wake screen user interface, different phases of the moon in different views of the wake screen user interface. In some embodiments, a 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 less than all of the complications are 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 view and the second view, while 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 the sliding animation described with reference to FIG. 5AP.

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

[0242] In some embodiments, in response to detecting a user input, such as user input 5034 in a different direction than 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 edit user interface 565-3 and displays the view of the wake screen user interface that was displayed while user input 5040 was detected as the current wake screen user interface.

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

[0245] 5BG-5BH illustrate examples of navigation from a wake screen user interface to an application's 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 user interface displayed is based on the user interface displayed prior to displaying the wake screen user interface (e.g., prior to entering a low power state and / or a lock mode). For example, if the device displays an application user interface as the last displayed user interface prior to device 100 entering a low power state and / or a lock mode, in response to a user input requesting to navigate away from wake screen user interface 5041, the previously displayed application user interface is re-displayed. Similarly, in some embodiments, if the device 100 displays a home screen user interface as the last displayed user interface prior to device 100 entering a low power state and / or a lock mode, in response to a user input requesting to navigate away from wake screen user interface 5041, the previously displayed home screen user interface is re-displayed.

[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), 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 manner than animated transition 5043 (e.g., having a different blur effect and / or a different level of translucency), where the wake screen user interface is optionally animated to slide off the display in an upward direction. In some embodiments, the application's user interface is optionally displayed in a portion of the display that is not covered by the wake screen user interface as it slides off the display.

[0247] 5BI illustrates a home screen user interface 5046. In some embodiments, the home screen user interface 5046 includes one or more application icons and is displayed with a background image. In some embodiments, the background image displayed in the home screen user interface 5046 is based at least in part on the wake screen user interface to which the user navigated. For example, the wake screen user interface 5041 includes a star image as a background, and 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 the individual home screens are stored in association with the individual wake screens such that when the current wake screen changes from a first wake screen to a second wake screen, the home screens displayed in response to user input on the individual wake screens are associated with the individual wake screens.

[0248] 5BI illustrates a user input 5048 corresponding to a request to view a cover sheet user interface, optionally including the same visual characteristics as the wake screen user interface. In some embodiments, the user input 5050 is detected on a power button (e.g., push button 206) that causes device 100 to enter a low power state and / or a locked mode. In some embodiments, waking up device 100 from a low power state and / or a locked mode optionally causes wake screen user interface 5041 to be redisplayed. In some embodiments, waking up device 100 from a low power state and / or a locked mode updates the wake screen user interface to the next wake screen user interface in a set of stored wake screen user interfaces (e.g., device 100 cycles through a set of stored wake screen user interfaces, optionally periodically and / or upon waking).

[0249] 5BJ illustrates a user input 5051, optionally a swipe user input in a first direction (e.g., from left to right or from right to left). 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 the predetermined area of ​​the wake screen user interface 5041 causes the device 100 to change to another wake screen user interface. For example, as shown in FIG. 5BK, the wake screen user interface is updated to display a wake screen user interface 5052.

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

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

[0252] 5BM-5BN show examples of user inputs for selecting a complication displayed on wake screen user interface 5062. In some embodiments, user input 5064 is a tap input or other selection input on the breathe complication, causing device 100 to display an application user interface for a breathing application associated with the breathe 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 application user interface 5068 for a weather application associated with the weather complication, as shown in FIG. 5BN. In some embodiments, device 100 optionally requires the user to unlock the device (e.g., using a biometric and / or passcode) before displaying a respective application user interface associated with the selected complication.

[0253] 5BO-5BP show examples of animated transitions during which device 100 transitions from a low power state to displaying 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 as the device transitions between different user interfaces. For example, the colored stripes are representations of ribbons, ropes, strings, or fabric. In some embodiments, each stripe is a different color (e.g., like a rainbow or flag). In some embodiments, the colored stripes are arranged as if 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 FIG. 5BO, each of the colored stripes is a first size, with spaces between the stripes. In some embodiments, by device 100 rejecting the low power state to display wake screen user interface 5070-2 of FIG. 5BP, the stripes are animated together (e.g., so that there is no space or less space between the stripes) and the size of the stripes increases to a second size that is larger than the first size.

[0254] 5BQ-5BS show examples of animating a background including colored stripes in response to one or more user inputs. In some embodiments, device 100 detects user input 5072 (e.g., a swipe input in a first direction or other input). In some embodiments, in response to user input 5072, the colored stripes are animated to be pulled in the same direction (or opposite direction) as user input 5072. For example, as user input 5072 moves in an upward direction, the colored stripes are animated to move in an upward direction, optionally while being displayed wrapped around an object (e.g., a cylinder). In some embodiments, the animation includes decreasing a size of one or more of the colored stripes and / or increasing a distance between at least two of the colored stripes. In some embodiments, the top stripe is animated to separate from and increase a distance from its neighboring stripes. For example, first the top stripe separates from the set of stripes, then the second top stripe separates from the remaining stripes, optionally until there is a space between each of the stripes in the set of stripes. For example, in FIG. 5BR, the top three stripes are shown as being 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 in accordance with the user input 5072. For example, in FIG. 5BR, user input 5074 is detected as being in an 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, pursuant to a determination that user input 5072 did not meet the rejection criteria, the wake screen user interface 5070-3 is not rejected and in response to user input 5074, the animation is reversed as shown in FIG. 5BS. For example, in FIG. 5BS, the stripes have increased in size compared to the stripes in FIG. 5BR, and the top stripe has shifted downward to remove the distance between the set of stripes. In some embodiments, the top stripe is the last stripe that recombines the set of stripes. In some embodiments, after detecting user input 5074, the user input is no longer detected, for example in response to lift-off 5076 of the user input. In some embodiments, the reverse animation continues until the wake screen user interface 5078 returns to its original state (eg, the state shown in FIG. 5BQ before detecting user input 5072), as shown in FIG. 5BT.

[0256] FIG. 5BU illustrates a user input 5080-1, such as an upward swipe input. In some embodiments, the user input 5080-1 meets a rejection criterion for rejecting the wake screen user interface 5070-7. For example, the rejection criterion is met according to a determination that the user input 5080-1 meets a threshold swipe speed and / or a threshold swipe distance. For example, the rejection criterion is met according to user input 5080-2 (e.g., a continuation of input 5080-1) continuing to be detected as the user continues the upward swipe input. In some embodiments, in response to the user input 5080-1, the device 100 displays the animation described with reference to FIG. 5BR, including separating the colored stripes and / or decreasing the size of the colored stripes.

[0257] In some embodiments, pursuant to a determination that the user inputs 5080 (e.g., including user inputs 5080-1 and 5080-2) meet the rejection criteria, the device 100 displays the full animation as the 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 FIG. 5BW, an intermediate user interface 5070-9 is displayed that includes colored stripes that move up and twist (e.g., around an invisible object such as a cylinder), while the colored stripes are displayed separated as indicated by the black spaces between the stripes and / or 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 up, the stripe is displayed in a smaller width, optionally at its narrowest width during the animation, as a background of a home screen user interface 5070-10 that also includes one or more application icons in the foreground, as shown in FIG. 5BX. In some embodiments, the stripe displayed in the background of the home screen user interface 5070-10 is optionally displayed in the same width as the stripe displayed in the background of the wake screen user interface 5070-7 (FIG. 5BU), optionally shifted upward from the stripe displayed in the wake screen user interface 5070-7. For example, the stripe is displayed in the same size but at a different position as the background of the home screen user interface 5070-10 compared to the stripe in the background of the wake screen user interface 5070-7.

[0259] 5BY and 5BZ show an example of changing the orientation of the stripes of the wake screen user interface 5070-11 to the wake screen user interface 5070-12, e.g., updating the direction of wrapping the stripes around the invisible object to the opposite direction (e.g., clockwise or counterclockwise). In some embodiments, the orientation of the stripes of the wake screen user interface 5070 is selected according to user input. For example, the user is provided with an option to select the orientation of the stripes to be 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 alternated periodically, e.g., each time the wake screen user interface is invoked, the orientation of the stripes changes from the previous orientation displayed before the wake screen user interface was invoked. For example, upon cycling between lock and unlock and / or dismissal of a low power state, the wake screen user interface alternates the orientation of the stripes.

[0260] 5CA-5CB show an example of changing the background color of 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 a light mode, a background is selected for the light operating mode (e.g., a white background is selected), as shown in FIG. 5CA. In some embodiments, while device 100 is in a second operating mode, such as a dark mode, a background is selected for the dark operating mode (e.g., a black background is selected), as shown in FIG. 5CB. In some embodiments, the current operating mode is selected according to time (e.g., light mode during daytime and / or a predefined time period (e.g., 6:00 a.m. to 8:00 p.m., or another period) and dark mode during nighttime and / or outside the predefined time period (e.g., 8:00 p.m. to 6:00 a.m.)). In some embodiments, the user is provided with an option to manually select the background color.

[0261] 6A illustrates detection of a user input 602 (e.g., a tap, a long press, or another selection input) on a wake screen user interface 600. In some embodiments, the user input 602 is detected in a portion of the wake screen user interface 600 that does not correspond to a date and / or time indication, a complication, or a flashlight and / or camera shortcut.

[0262] In some embodiments, following a determination that device 100 is in a locked mode (e.g., optionally indicated by a lock indicator above the date), device 100 displays a user interface 604 (FIG. 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 user interface 604, as shown in Figure 6C. In some embodiments, in response to user input 602, device 100 displays an enhanced face switcher user interface 606, as shown in Figure 6D. In some embodiments, as described with reference to Figure 5U, an enhanced face switcher user interface (e.g., user interface 561) includes multiple representations of wake screen user interfaces (e.g., a representation of wake screen user interface 611), with a central wake screen user interface 615 displayed simultaneously with a portion of an associated home screen user interface.

[0264] FIG. 6D illustrates multiple user interactions with the enhanced face switcher user interface 606. In some embodiments, user input 608 selecting a plus button causes the 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 the second wake screen user interface 611 causes the 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, user input selection user interface element 609a ("focus") allows the user to set a limited notification mode (e.g., certain types of notifications are suppressed and / or delayed) for the wake screen corresponding to the wake screen representation 615. In some embodiments, user input selection option 609b allows the user to view a gallery view (e.g., user interface 652 of FIG. 6K) for creating a new wake screen user interface to add to the set of user interfaces. In some embodiments, a 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 enhanced face switcher user interface 606, as shown in FIG. 6F.

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

[0266] In some embodiments, one or more wake screen user interfaces in the set of wake screen user interfaces are associated with a particular type or theme of wake screen user interfaces. For example, the particular wake screen user interface is identified as a photo style, an emoji style, a portrait style, or another style, optionally pre-generated. For example, device 100 optionally generates one or more themes or styles for the wake screen user interfaces, such as a smart album that rotates images and / or photos stored on device 100, a weather style that includes a representation of the weather forecast at device 100's current location, an astronomy, earth, or other celestial globe 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, optionally generated automatically by device 100 without user input, is shown in FIG. 6K.

[0267] In some embodiments, a user input 612, such as a swipe gesture (e.g., up or down), causes device 100 to provide the user with an option to delete the centered wake screen user interface 615. For example, as shown in FIG. 6E, device 100 displays a delete icon 616. In some embodiments, in response to continuing user input 612 (e.g., the swipe gesture continues in the same direction), device 100 optionally displays a representation of the wake screen user interface 615 sliding out of 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 the user input 618, 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] 6F shows a representation of the second wake screen user interface 611 centered on the display (e.g., in response to user input 614). In some embodiments, the representation of the second wake screen user interface 611 is centered on the display, while less than all of an associated home screen user interface representation 620 is displayed, optionally partially occluded, 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 less than all of two or more other representations of wake screen user interfaces, e.g., a left wake screen user interface representation 615 and a right wake screen user interface representation 613.

[0269] FIG. 6F illustrates a number of user inputs that allow a user to interact with the enhanced face switcher user interface 606. For example, in response to user input 608-1 on a "+" button, device 100 initiates a process for adding (optionally including designing and / or editing) a new wake screen user interface that is added to the set of wake screen user interfaces, as shown in FIG. 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 the wake screen user interface to the center of the enhanced 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 the wake screen user interface in the set of wake screen user interfaces.

[0270] In some embodiments, in response to user input 622 selecting a “Customize” button, device 100 displays an edit user interface 626 (FIGS. 6G-6H) for a representation of the wake screen that is currently centered in the enhanced face switcher user interface 606 when user input 622 is detected.

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

[0272] 6G-6H illustrate an editing user interface 626 for the wake screen user interface corresponding to the representation 611 of the wake screen user interface. In some embodiments, the editing user interface 626 is optionally enabled with one or more of the same functions described with respect to the editing user interface 565 (FIG. 5X). In some embodiments, the editing user interface 626 includes a user selectable option for changing the font color of the user interface. In some embodiments, the editing user interface 626 includes a user selectable option for applying a visual filter (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 a user input 628 selecting a first color, the font color of the date and / or time indication is updated to the selected first color and the date and / or time indication is displayed in a white font color, as shown in FIG. 6H. In some embodiments, in response to the user input 628 and / or in response to a user input on the "font color" button of FIG. 6G, a user interface element 630 is displayed as shown in FIG. 6H.

[0273] In some embodiments, the background of the wake screen user interface is an emoji-style background (e.g., a smiley face emoji) with one or more emojis 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., pattern) of the emojis within the wake screen user interface background. 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, a user may select up to a threshold number of emojis (e.g., three or four emojis) for display in a predetermined 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 editing user interface 626, as shown in FIG. 6H2. In some embodiments, emoji keyboard 629 includes a user interface element that displays a currently selected emoji used in the pattern. For example, in FIG. 6H2, a smiley face emoji is selected and the grid pattern includes a smiley face emoji. In some embodiments, while displaying editing user interface 626 with emoji-styled background, device 100 detects user input 631-1, such as a swipe input in a first direction (e.g., from right to left). In some embodiments, in response to user input 631-1, device 100 updates editing user interface 626 to display an emoji-styled background with a different pattern (and, optionally, with the same emoji(s) arranged in a different pattern). For example, the glyphs are arranged in a first pattern (eg, a grid pattern) in FIG. 6H2 and in a second pattern (eg, a swirl pattern) in FIG. 6H3.

[0275] FIG. 6H3 illustrates a user input 633-1 selecting a first emoji (e.g., a thumbs up emoji) and a user input 633-2 selecting a second emoji (e.g., a heart emoji). In some embodiments, in response to user input(s) 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 the emojis are shown (e.g., alternating in the pattern of the and background). For example, in FIG. 6H4, a thumbs up emoji and a heart emoji are added after a smiley face emoji, and the pattern alternates between the selected emojis. For example, the swirl pattern in FIG. 6H4 includes a smiley face emoji, a thumbs up emoji, and a 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 a user input 631-2 (e.g., a swipe input), the device 100 updates the background to display a third pattern different from the first pattern (e.g., a grid pattern) and the second pattern (e.g., a swirl pattern). For example, as shown in FIG. 6H5, selected emojis including a smiley face emoji, a thumbs up emoji, and a heart emoji are arranged in a geometric pattern including a diagonal arrangement of the emojis.

[0277] FIG. 6H displays a user interface element 630 for viewing and / or selecting a font color. In some embodiments, the user interface element 630 includes additional options beyond the color options displayed in the user interface 626 of FIG. 6G. In some embodiments, the user can select and / or change the font color by selecting a color sample in a list of color samples displayed in the user interface element 630. For example, in response to user input 632, the device 100 updates the color to the color of the sample color selected by the user input 632, and in response to user input 634, the device 100 updates the font color to the sample color selected by the user input 634. In some embodiments, in response to user input 636 on a "Done" button, the device 100 exits the editing user interface 626 and optionally returns to the enhanced 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] 6I illustrates a representation of the home screen user interface in a central region of the enhanced face switcher user interface 638 (e.g., in response to user input 624). In some embodiments, a user can edit or customize the home screen user interface by selecting a "Customize" button in FIG. 6I via user input 640.

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

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

[0281] In some embodiments, editing user interface 642 includes an indication 647 that an additional view of the home screen user interface is available. For example, the additional view corresponds to one or more different visual effects applied to the background, including changing the color, tone, or another visual effect of the background. In some embodiments, the additional view includes one or more different patterns or arrangements of the background of the home screen user interface. For example, smiley faces are rearranged in a different pattern and / or displayed at a different size in the one or more additional views. In some embodiments, user input 648 (e.g., a 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, device 100 displays a different view of the home screen user interface (e.g., changing the background).

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

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

[0284] In some embodiments, the user interface 652 includes one or more "characteristic faces" corresponding to a wake screen user interface that are automatically generated (e.g., by the device 100) without user input. For example, the characteristic faces optionally include a "smart album" that identifies a number of images (e.g., photos) to include in the wake screen user interface, and optionally rotates the number of images while the "smart album" face is selected as the wake screen user interface. In some embodiments, the device 100 allows the user to select a subset of individuals, pets, places, and / or photo albums to include in the "smart album" wake screen user interface. In some embodiments, the device 100 provides the user with an option (e.g., in an edit user interface) to set the frequency of changing between each photo in the "smart album" used as the current wake screen user interface. In some embodiments, in response to user input 6002 selecting a "smart album" face, the device 100 displays a user interface 6004 (FIG. 6U) for the user to select and / or deselect categories to include in the smart album, and optionally set the frequency of changing between photos.

[0285] In some embodiments, the characteristic face includes an emoji user interface including preselected emojis and / or patterns of emojis. In some embodiments, the characteristic face includes a weather user interface that creates a visual effect corresponding to a current weather forecast, a globe user interface that includes an image of the Earth, an astronomy user interface that includes one or more celestial spheres, and / or a privilege user interface that includes 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 the respective wake screen user interface.

[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 having a set of properties generated by device 100, as shown in FIG. 6L. For example, the date and time complication, date indication, 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 in the set of properties. For example, the user can change the complication and / or change the font of the date and / or time indication. In some embodiments, in response to user input 662 selecting a "Done" button, device 100 stops displaying the edit user interface, displays the emoji user interface as the current wake screen user interface, and optionally adds the emoji user interface to the set of wake screen user interfaces.

[0287] In some embodiments, in response to user input 658 (FIG. 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 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 a "Done" button, device 100 stops displaying the edit user interface, displays the weather user interface as the current wake screen user interface, and optionally adds the weather user interface to the set of wake screen user interfaces.

[0288] 6N shows a photo picker user interface 668 for selecting a photo to use as a background image for the wake screen user interface. In some embodiments, in response to user input 670 selecting a photo 672, device 100 displays a user interface 674 (FIG. 6O) for viewing a preview of photo 672 as the background of 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 that includes displaying at least one reticle (e.g., reticle 572 for editing one or more complications and, optionally, a reticle for a time and / or date indication) behind or at least partially obstructed by a portion of the background image, such as a subject of the background image (e.g., an aircraft). In some embodiments, in response to user input 682-a directed at reticle 569 for editing a time indication, the reticles, including reticle 572, reticle 569, and reticle 568, are displayed in front of the subject of the background image, as shown in Figure 6P.

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

[0291] 6Q shows a user input 684 selecting a set of complications 686 to add to the wake screen user interface. In some embodiments, in response to the user input 684, the device 100 displays the set of complications 686 below the time indication (FIG. 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 indication.

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

[0293] Figure 6R shows user input 688 selecting a different style for the font of the time. 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, which causes device 100 to exit edit user interface 678 and display the user interface as the current user interface with photo 672 as a background, and optionally add a new user interface with photo 672 as a background to the set of wake screen user interfaces.

[0294] 6S-6T show examples of portrait style wake screen user interfaces. In some embodiments, portrait style wake screen user interface 692 and portrait style wake screen user interface 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, optionally without 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 pursuant to a determination that device 100 has entered a locked state and / or a low power state. For example, upon bringing device 100 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. FIG. 6T shows a user input 696 requesting to dismiss the wake screen user interface 694, in response to which the device 100 displays a home screen user interface related (or associated) with the wake screen user interface 694.

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

[0296] In some embodiments, user interface 6004 provides options to select or deselect one or more categories of photos, including a people category, a pet category, a nature category, and / or a city category. In some embodiments, photos are determined to belong to a respective category based on the content of the photo, which is optionally identified automatically by device 100, without the user having to manually tag the photo with a category.

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

[0298] In some embodiments, in response to the user deselecting the “Nature” category, representation 6003-1, which includes an image of a flower, is no longer included in the smart album, and device 100, optionally, stops displaying representation 6003-1, as shown in user interface 6008 of FIG. 6V.

[0299] In some embodiments, as shown in FIGURE 6V, a user may select to include one or more categories, such as selecting the category "city" with user input 6010. In some embodiments, in response to user input 6010, device 100 displays a representation 6003-2 of a wake screen user interface 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 photo is selected that includes city-related content (e.g., skyscrapers, buildings, skyline views, cityscapes, billboards, or other city images).

[0300] In some embodiments, the user can exit user interface 6008 via user input 6012 (e.g., swiping down) to close or otherwise stop displaying the smart album category selections. In some embodiments, in response to user input 6012, device 100 returns to the user interface displayed in FIG.

[0301] 6W illustrates a user input 6016 selecting a "select..." option that allows the user to select people to include in the smart album. For example, in response to user input 6016, device 100 displays a user interface 6018 (FIG. 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] 6X illustrates multiple user inputs selecting one or more people for inclusion in the smart album. For example, user input 6020 (e.g., a tap input or other selection input) selects a representation 6026-2 of a first person, user input 6022 selects a representation 6026-3 of a second person, and user input 6024 selects a representation 6026-1 of a third person. In some embodiments, following a determination that each person has been selected, one or more photos including each person are included in the set of photos of the smart album. In some embodiments, an option is provided (e.g., "More...") to view and select additional people not displayed in user interface 6018.

[0303] In some embodiments, the representation shown in user interface 6028 includes a representation of a wake screen user interface that includes a background of the individual selected person, as shown in FIG. 6Y. For example, representation 6003-3 includes a representation of the person associated with representation 6026-2.

[0304] 6Y illustrates a detected user input 6030 with options for selecting how often to change photos in the smart album. In some embodiments, in response to the user input 6030, a menu of user-selectable options is displayed for the user. 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 includes one or more options for changing the frequency based on a detected event of device 100 (e.g., when unlocked, in respective focus mode, or when charging begins).

[0305] 6Y further illustrates a user input 6032 selecting an option to automatically select images corresponding to a 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 the one or more images as a 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 of FIG. 6N) that allows the user to browse and select specific photos to include in the background of the smart album.

[0306] In some embodiments, in response to the user input 6032, the device 100 stops displaying the user interface 6028. In some embodiments, the device 100 optionally displays an edit user interface for the first wake screen user interface of the smart album, as shown in FIG. 6Z. In some embodiments, the device 100 displays an edit user interface 6034-1 (FIG. 6Z) in response to one or more interactions, as described with reference to FIGS. 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 options for editing the home screen user interface.

[0307] FIG. 6Z illustrates an edit user interface 6034-1 of a first wake screen user interface including a first person, optionally selected in a smart album. In some embodiments, an original photo (or “natural” view) used as a background of the first wake screen user interface is displayed. In some embodiments, following a determination that the wake screen user interface selected for editing is in a smart album, an option to shuffle or view other photos in the smart album is provided (e.g., “tap to shuffle”). In some embodiments, the original photo (or “natural” view) is processed by the device 100 to determine an initial tone. For example, the initial tone represents the brightness and / or amount of brightness of the background (and / or foreground) of the original photo. In some embodiments, the original photo of FIG. 6Z is identified as a low key level of brightness (e.g., low brightness, such as a relatively dark photo) according to a calculated level of brightness that meets a threshold amount of brightness. In some embodiments, the edit user interface 6034-1 includes a photo picker 6033 for selecting a different background photo. For example, in response to user input 6042 (FIG. 6AA), device 100 displays a photo library or photo picker user interface (e.g., as described with reference to FIG. 6N). In some embodiments, the editing user interface 6034-1 includes an indicator 6035 of an additional view of the wake screen user interface, such as the same foreground (e.g., subject or individual) and a different background of the photo, and / or a different filter applied to the photo (e.g., as described with reference to swipe input 6040 of FIG. 6AA).

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

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

[0310] FIG. 6AB illustrates a user input 6046 and displays menu 6037 in response to user input 6046. In some embodiments, device 100 detects user input 6044 selecting 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 display a two-color view (also referred to herein as a two-color filter) as a high-key version, as shown in FIG. 6AC. For example, the two-color view is represented by horizontal stripes, but the high-key version of the two-color view (shown in FIG. 6AC) has a higher level of luminance than the low-key version of the two-color view (shown in FIG. 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 of FIG. 6AA is identified as a low-key photograph (e.g., below a threshold amount of luminance), and therefore 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 the photograph.

[0311] FIG. 6AC illustrates a user input 6048 (e.g., a swipe input) corresponding to a request to switch to another view. In some embodiments, as shown in FIG. 6AD, a low-key black and white view of the photo is displayed in user interface 6034-5. In some embodiments, after a user manually switches from a low-key version of a view to a high-key version (e.g., as described with reference to FIGS. 6AB-6AC), device 100 continues to recommend or automatically provides low-key versions of other views. For example, in FIG. 6AD, device 100 provides a low-key version of the black and white view (e.g., because the original photo is a low-key photo). In this manner, a user can manually change a particular view or filter to switch between low-key and / or high-key without changing a recommended view that is automatically generated and presented and is more likely to be visually pleasing because it preserves the luminance (or other tones) present in the original photo.

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

[0313] In some embodiments, in response to user input 6054, device 100 replaces the display of the user interface with another view, i.e., a high-key version of the studio view, as shown in user interface 6050-3 of FIG. 6AG. FIG. 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 in 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 FIG. 6AH, which corresponds to a low-key version of the studio view.

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

[0315] FIG. 6AI illustrates a user input 6062 corresponding to a request to switch to another view. In some embodiments, in response to the user input 6062, the device 100 displays a color view (also referred to herein as a color filter), as shown in user interface 6050-6 of FIG. 6AJ. In some embodiments, the tone of the color selected for 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 for 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), optionally including applying different levels (e.g., having different transparency or brightness) of the selected color to various parts of the photograph. For example, the selected color is optionally applied to the entire photograph, with the foreground, including the subject of the photograph, only slightly applying the selected color (e.g., as a filter), and the background being replaced with a solid or more opaque version of the selected color.

[0316] FIG. 6AJ illustrates a user input 6064 corresponding to a request to change the background of the wake screen user interface. In some embodiments, in response to the user input 6064, the device 100 displays a color picker 6066 for changing the color applied to the photo. In some embodiments, the initially selected color is selected to have a tone that matches the tone of the original photo. For example, as shown in FIG. 6AK, the selected color has a high level of brightness (e.g., for a high-key original photo) as indicated by the selector to the left of the slider bar 6068 that indicates the level of brightness that defines the tone of the currently selected color. For example, if the original photo is a low-key original photo, 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 corresponds to a request to change the tone of a 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 of FIGURE 6AK.

[0318] In some embodiments, each color offered in the color picker 6066 is displayed in the same tone (e.g., matching the tone of the original photograph). For example, the colors are different (e.g., purple, green, red, yellow, or another color), but the brightness level and / or tone of each color is, optionally, 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 a user input 6069 selecting a different color that is displayed in 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 in the Smart Album as a wake screen user interface.

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

[0321] 6AN illustrates case 6073 in a state in which it has been placed on device 100. In some embodiments, device 100 determines that case 6073 has been placed on device 100, and in response to determining that case 6073 is on device 100, device 100 optionally displays prompt 6074 inquiring of the user whether device 100 should update a 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 an option to select yes and an option to select no.

[0322] In some embodiments, device 100 detects user input 6076 selecting yes to prompt 6074, and in response to user input 6076, device 100 updates user interface 6072-3 to be displayed 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 the foreground and background of wake screen user interface 6072-3 (optionally with different portions displayed with different levels of transparency or color intensity).

[0323] 6AP illustrates a user interface 652 (e.g., as described with reference to FIG. 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 the device 100. For example, following a determination that a case is on the 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 appreciated that additional recommendations may be provided to the user based at least in part on the color of the case detected to be on the device 100.

[0324] 6AQ-6AR illustrate 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 FIGS. 6AA-6AJ are displayed as the wake screen user interface. In some embodiments, a first view of a first photo is displayed as the wake screen user interface 6080, and the wake screen user interface is automatically updated to display a second wake screen user interface 6084 including a second view of a second photo according to a selected frequency of the smart album without additional user input. In some embodiments, a user input 6082 is optionally detected, and in response to the user input 6082, the wake screen user interface is updated from the wake screen user interface 6080 to the wake screen user interface 6084.

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

[0326] 7A illustrates a representation of a first plurality of notifications in a first configuration 7000-a. For ease of explanation, the representation of the first plurality of notifications will be referred to as "representation 7000" (e.g., regardless of which configuration the representation of the first plurality of notifications is displayed in), and the letter (e.g., 7000-a, 7000-b, or 7000-c) after label 7000 refers to the particular configuration in which representation 7000 is displayed (e.g., 7000-a refers to a first configuration, 7000-b refers to a second configuration that is different from first configuration 7000-a, and 7000-c refers to a third configuration that is different from both first configuration 7000-a and second configuration 7000-b). In various circumstances, representation 7000 can represent (e.g., include) different notifications (e.g., based on the notification settings of an active mode of portable multifunction device 100).

[0327] The plurality of notifications represented by representation 7000 includes at least a notification associated with application A 7002, a notification associated with application Z 7004, a notification associated with application S 7006, a notification associated with application D 7008, and a notification associated with application M 7010. While representation 7000 is displayed in a first configuration 7000-a (e.g., a “list” configuration), each notification in the plurality of notifications is displayed separately from other notifications in the plurality of notifications (e.g., in a list format, with no overlay between adjacent notifications).

[0328] In some embodiments, representation 7000 is aligned with the bottom of the display of portable multifunction device 100 (e.g., if notifications 7006, 7008, and 7010 are the only notifications to be displayed, they will still be displayed in the same location as shown in FIG. 7A, but notifications 7002 and 7004 will not be displayed). In some embodiments, the notifications are displayed in reverse chronological order (e.g., as shown in FIG. 7A), while in other embodiments the order of the notifications may be different (e.g., chronological order or a user-defined order). In some embodiments, the first configuration 7000-a is a default configuration for displaying notifications.

[0329] A user can interact with notifications in the first plurality of notifications via different gestures. For example, portable multifunction device 100, in response to a tap input 7012 on notification 7002, opens application A corresponding to notification 7002. Alternatively, in response to tap input 7012, portable multifunction device 100 instead displays additional content associated with notification 7002 (e.g., by expanding the area occupied by notification 7002). In response to a rightward swipe input 7014, portable multifunction device 100 displays one or more affordances for interacting with notification 7006, and in response to a leftward swipe input 7016, portable multifunction device 100 displays one or more affordances for configuring display options for notification 7010 (e.g., to dismiss, postpone, and / or adjust its prominence).

[0330] FIG. 7B illustrates a representation 7000 of second configuration 7000-b while a “work” mode of p...

Claims

1. 1. A method comprising: A computer system in communication with a display generation component, comprising: displaying, via the display generation component, a first version of a first user interface corresponding to a restricted state of the computer system, wherein displaying the first version of the first user interface includes displaying a first plurality of user interface objects displayed concurrently with a first background according to a first configuration, the first plurality of user interface objects corresponding to a first plurality of applications, including individual content from the first plurality of applications, and being updated periodically as information represented by the first plurality of user interface objects changes; Detecting a first input while displaying the first version of the first user interface; In response to detecting the first input, pursuant to a determination that the first input satisfies a first criterion, the first criterion requiring that the first input include a first movement in a first direction such that the first criterion is satisfied, replacing a display of the first version of the first user interface with a display of a second user interface including a representation of a respective one of a second plurality of applications, the respective representation of the second plurality of applications, when activated, causing the computer system to launch a corresponding application of the respective representation; and replacing a display of the 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 that the first input include a second movement in a second direction different from the first direction for the second criterion to be satisfied, wherein displaying the second version of the first user interface includes simultaneously displaying a second plurality of user interface objects according to a second configuration against a second background, the second plurality of user interface objects corresponding to a third plurality of applications, including individual content from the third plurality of applications, and being updated periodically as information represented by the second plurality of user interface objects changes, the first background being different from the second background, the first plurality of user interface objects being different from the second plurality of user interface objects, and / or the first configuration being different from the second configuration.

2. detecting a second input corresponding to a request to display the first user interface while the display generation component is in a power-saving state; in response to detecting the second input corresponding to the request to display the first user interface; displaying a first animated transition corresponding to the first version of the first user interface in accordance with a determination that the first version of the first user interface is a currently selected version for the first user interface, and displaying the first version of the first user interface upon completion of the first animated transition; 2. The method of claim 1 , further comprising: displaying a second animated transition corresponding to the second version of the first user interface in accordance with a determination that the second version of the first user interface is the currently selected version of the first user interface; and displaying the second version of the first user interface upon completion of the second animated transition, wherein the first animated transition is different from the second animated transition.

3. in response to detecting the second input corresponding to the request to display the first user interface; 3. The method of claim 2, further comprising: displaying an animated change in one or more elements of the plurality of weather-based elements followed by displaying the currently selected version of the first user interface in accordance with a determination that the currently selected version of the first user interface is a distinct version of a first user interface that includes a plurality of weather-based elements.

4. in response to detecting the second input corresponding to the request to display the first user interface; 4. The method of claim 2 or 3, comprising, in accordance with a determination that the currently selected version of the first user interface is a distinct version of a first user interface that includes an image of at least a portion of a planet or a celestial sphere, displaying the currently selected version of the first user interface after displaying an animated movement of the planet or celestial sphere.

5. in response to detecting the second input corresponding to the request to display the first user interface; 5. The method of claim 2, further comprising: displaying the currently selected version of the first user interface after modifying at least a first visual characteristic of at least a portion of the photograph through a plurality of values ​​for the first visual characteristic in accordance with a determination that the currently selected version of the first user interface is an individual version of the first user interface that includes a photograph.

6. in response to detecting the second input corresponding to the request to display the first user interface; 6. The method of claim 2, further comprising: displaying an animated change in the first color gradient prior to displaying the currently selected version of the first user interface in accordance with a determination that the currently selected version of the first user interface is a distinct version of the first user interface that includes a first color gradient.

7. in response to detecting the second input corresponding to the request to display the first user interface; 7. The method of claim 2, further comprising: displaying animated movement of one or more graphical objects prior to displaying the currently selected version of the first user interface in accordance with a determination that the currently selected version of the first user interface is a distinct version of the first user interface that includes one or more graphical objects.

8. detecting a third input that satisfies the first criterion while displaying the currently selected version of the first user interface; and in response to detecting the third input satisfying the first criterion, replacing a display of the currently selected version of the first user interface with a respective version of the second user interface that corresponds to the currently selected version of the first user interface, wherein the replacing comprises: displaying a third animated transition corresponding to the first version of the first user interface in accordance with a determination that the currently selected version of the first user interface is the first version of the first user interface, and displaying a first version of the second user interface upon completion of the third animated transition; 8. The method of claim 1, further comprising: displaying a fourth animated transition corresponding to the second version of the first user interface in accordance with a determination that the currently selected version of the first user interface is the second version of the first user interface; and displaying a second version of the second user interface upon completion of the fourth animated transition, wherein the third animated transition is different from the fourth animated transition.

9. replacing a display of the currently selected version of the first user interface with the respective version of the second user interface that corresponds to the currently selected version of the first user interface; 10. The method of claim 8, further comprising: pursuant to a determination that the currently selected version of the first user interface is a distinct version of a first user interface including a respective color gradient, displaying an animated change of the distinct color gradient prior to displaying the distinct version of the second user interface that corresponds to the currently selected version of the first user interface.

10. replacing a display of the currently selected version of the first user interface with the respective version of the second user interface that corresponds to the currently selected version of the first user interface; 10. The method of claim 8 or 9, comprising, in accordance with a determination that the currently selected version of the first user interface is a particular version of the first user interface that includes a portrait orientation, displaying an animated increase in scale of at least a portion of the portrait orientation before displaying the particular version of the second user interface that corresponds to the currently selected version of the first user interface.

11. replacing a display of the currently selected version of the first user interface with the respective version of the second user interface that corresponds to the currently selected version of the first user interface; 11. The method of claim 8, further comprising: displaying animated movement of the one or more objects in the foreground of the first user interface prior to displaying the separate version of the second user interface that corresponds to the currently selected version of the first user interface in accordance with a determination that the currently selected version of the first user interface is a separate version of the first user interface that includes one or more objects in a foreground of the first user interface.

12. replacing a display of the currently selected version of the first user interface with the respective version of the second user interface that corresponds to the currently selected version of the first user interface; 12. The method of claim 8, further comprising: increasing a visual depth of each of the one or more predefined objects prior to displaying the predefined version of the second user interface corresponding to the currently selected version of the first user interface in accordance with a determination that the currently selected version of the first user interface is a predefined version of the first user interface that includes one or more predefined objects.

13. replacing a display of the currently selected version of the first user interface with the respective version of the second user interface that corresponds to the currently selected version of the first user interface; 13. The method of claim 8, further comprising: moving the pattern of objects according to a preset movement pattern in accordance with a determination that the currently selected version of the first user interface is a distinct version of the first user interface that includes a pattern of objects.

14. replacing a display of the currently selected version of the first user interface with the respective version of the second user interface that corresponds to the currently selected version of the first user interface; 14. The method of claim 8, further comprising: displaying a different view of the scene corresponding to a movement of a virtual viewpoint within the scene prior to displaying the different version of the second user interface corresponding to the currently displayed version of the first user interface in accordance with a determination that the currently selected version of the first user interface is a respective version of a first user interface including a preset scene.

15. detecting a fourth input while displaying the currently selected version of the first user interface, the fourth input corresponding to a request to dismiss the first user interface; in response to detecting the fourth input corresponding to the request to dismiss the first user interface; displaying a first intermediate view of the first user interface that visually obscures at least a portion of the second user interface prior to displaying the second user interface in response to a determination that a distinct user interface that replaces a display of the first user interface in response to the fourth input includes the second user interface; 15. The method of claim 1, further comprising: displaying a second intermediate view of the first user interface that visually obscures at least a portion of the individual user interface of the first application in accordance with a determination that the individual user interface that will replace the display of the first user interface in response to the fourth input includes an individual user interface of a first application, wherein the first intermediate view of the first user interface and the second intermediate view of the first user interface have different values ​​for a first display characteristic of the first user interface.

16. detecting a fifth input corresponding to a request to display the first user interface while the display generation component is in a power-saving state; in response to detecting the fifth input corresponding to the request to display the first user interface; 16. The method of claim 1, comprising: displaying a respective animated transition; and displaying a currently selected version of the first user interface upon completion of the respective animated transition, wherein displaying the respective animated transition comprises modifying an appearance of a text element in the currently selected version of the first user interface.

17. 17. The method of claim 1, wherein displaying the first version of the first user interface includes displaying an indication of a current time, and the first plurality of user interface objects are displayed in proximity to the indication of the current time.

18. detecting a user input corresponding to a request to update the first plurality of user interface objects displayed simultaneously with the first background while displaying the first version of the first user interface; 18. The method of claim 1, further comprising: in response to detecting the user input corresponding to the request to update the first plurality of user interface objects, displaying one or more selectable options that, when selected, modify at least one of the first plurality of user interface objects.

19. while the first version of the first user interface is being displayed, detecting a first condition that causes the display generation component to stop displaying the first user interface; ceasing to display the first version of the first user interface in response to detecting the first condition that causes the display generation component to cease displaying the first user interface; detecting a second condition while the first user interface is not displayed that causes the display generation component to re-display the first user interface; re-displaying the first version of the first user interface in response to detecting the second condition that causes the display generation component to re-display the first user interface; redisplaying the first plurality of user interface objects with updated application content from the first plurality of applications in the first version of the first user interface; 19. The method of claim 1, further comprising: displaying, in accordance with a determination that one or more notifications are received during occurrence of the first condition and the second condition, the one or more notifications in the first version of the first user interface along with the first plurality of user interface objects that include the updated application content.

20. Displaying the first version of the first user interface including the first plurality of user interface objects includes: displaying, at a first time, the first version of the first user interface with a first user interface object corresponding to a first application and a second user interface object corresponding to a second application, the first user interface object including first application information from the first application and the second user interface object including second application information from the second application; 20. The method of claim 1, further comprising: displaying, at a second time after the first time, the first version of the first user interface with the first user interface object corresponding to the first application, the first user interface object including updated application information from the first application that differs from the first application, and the second user interface object corresponding to the second application.

21. 21. The method of claim 1, wherein the first plurality of user interface objects includes at least a first user interface object associated with a first application published by a first third party provider and a second user interface object associated with a second application published by a second third party provider different from the first third party provider.

22. while displaying the first version of the first user interface; detecting a sixth input satisfying a third criterion different from the first criterion and the second criterion; in response to detecting the sixth input satisfying the third criterion, initiating a process for displaying an editing user interface, the process including displaying one or more selectable options for editing one or more aspects of the first user interface; pursuant to a determination that the computer system is in an unauthenticated state, obtaining authentication information prior to displaying the editing user interface; 22. The method of claim 1, further comprising: in response to obtaining the authentication information, dismissing the authentication user interface and displaying the editing user interface in accordance with a determination that the authentication information matches authorized authentication information required to transition the computer system from the unauthenticated state to an authenticated state.

23. 23. The method of claim 1, wherein the second criterion requires that the second movement in the second direction is detected at a location corresponding to a predetermined portion of the first user interface.

24. replacing the display of the first version of the first user interface with the second user interface in accordance with the determination that the first input satisfies the first criterion includes replacing the display of the first version of the first user interface with a first version of the second user interface that corresponds to the first version of the first user interface; The method comprises: detecting a seventh input while displaying the second version of the first user interface as a result of the first input satisfying the second criterion; and In response to detecting the seventh input, 24. The method of claim 1, further comprising: replacing a display of the second version of the first user interface with a second version of the second user interface corresponding to the second version of the first user interface in accordance with a determination that the seventh input satisfies the first criterion.

25. 25. The method of claim 24, wherein the first version of the second user interface includes a third background and the second version of the second user interface includes a fourth background that is different from the third background.

26. 26. The method of claim 24 or 25, wherein the second version of the second user interface includes a representation of each of a third plurality of applications that differs from the representation of each of the second plurality of applications included in the first version of the second user interface.

27. A computer system in communication with a display generation component, comprising: 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, the one or more programs comprising: displaying, via the display generation component, a first version of a first user interface corresponding to a restricted state of the computer system, comprising displaying a first plurality of user interface objects displayed concurrently with a first background according to a first configuration, the first plurality of user interface objects corresponding to a first plurality of applications, including individual content from the first plurality of applications, and being updated periodically as information represented by the first plurality of user interface objects changes; displaying the first version of the first user interface; detecting a first input while displaying the first version of the first user interface; In response to detecting the first input, pursuant to a determination that the first input satisfies a first criterion, the first criterion requiring that the first input include a first movement in a first direction such that the first criterion is satisfied, replacing the display of the first version of the first user interface with a display of a second user interface including a representation of each of a second plurality of applications, each of the representations of the second plurality of applications, each of the representations of the second plurality of applications, when activated, causing the computer system to launch a corresponding application of each of the representations; and instructions for replacing the display of the 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 that the first input include a second movement in a second direction different from the first direction for the second criterion to be satisfied, wherein displaying the second version of the first user interface includes simultaneously displaying a second plurality of user interface objects according to a second configuration against a second background, the second plurality of user interface objects corresponding to a third plurality of applications and including individual content from the third plurality of applications, and being updated periodically as information represented by the second plurality of user interface objects changes, the first background being different from the second background, the first plurality of user interface objects being different from the second plurality of user interface objects, and / or the first configuration being different from the second configuration.

28. 28. The computer system of claim 27, wherein the one or more programs further comprise instructions for carrying out the method of any one of claims 2 to 26.

29. When executed by a computer system in communication with a display generation component, the computer system is provided with: Displaying, via the display generation component, a first version of a first user interface corresponding to a restricted state of the computer system includes displaying a first plurality of user interface objects displayed concurrently with a first background according to a first configuration, the first plurality of user interface objects corresponding to a first plurality of applications, including individual content from the first plurality of applications, and causing the first version of the first user interface to be displayed periodically as information represented by the first plurality of user interface objects changes; detecting a first input while displaying the first version of the first user interface; In response to detecting the first input, pursuant to a determination that the first input satisfies a first criterion, the first criterion requiring that the first input include a first movement in a first direction such that the first criterion is satisfied, replacing a display of the first version of the first user interface with a display of a second user interface including a representation of each of a second plurality of applications, each of the representations of the second plurality of applications, each of the representations of the second plurality of applications, when activated, causing the computer system to launch a corresponding application of each of the representations; 11. The computer program product of claim 1, further comprising: instructions for causing a display of the first version of the first user interface to be replaced 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 that the first input include a second movement in a second direction different from the first direction for the second criterion to be satisfied; wherein displaying the second version of the first user interface comprises simultaneously displaying a second plurality of user interface objects according to a second configuration against a second background, the second plurality of user interface objects corresponding to a third plurality of applications, including individual content from the third plurality of applications, and being updated periodically as information represented by the second plurality of user interface objects changes; the first background differs from the second background, the first plurality of user interface objects differ from the second plurality of user interface objects, and / or the first configuration differs from the second configuration.

30. 30. A computer program according to claim 29, further comprising instructions which, when executed by a computer system in communication with a display generation component, cause said computer system to carry out the method of any one of claims 2 to 26.

Images