Devices, methods, and graphical user interfaces for activating, configuring, and interacting with different operating modes.

Abstract

The computer system detects a first event. In response to detecting the first event, if a first criterion is met as a result of the first event, and the first criterion requires that the orientation of the display generation component is in a first orientation and that the computer system is charging, then the computer system displays a first customizable user interface that was not displayed before detecting the first event, in order to satisfy the first criterion. If the first criterion is not met as a result of the first event, the computer system stops displaying the first customizable user interface.

Description

Technical Field

[0001] (Related Applications) This application is a continuation of U.S. patent application Ser. No. 18 / 656,538, filed May 6, 2024, which claims priority to U.S. Provisional Patent Application No. 63 / 465,238, filed May 9, 2023; U.S. Provisional Patent Application No. 63 / 470,966, filed Jun. 4, 2023; U.S. Provisional Patent Application No. 63 / 605,507, filed Dec. 2, 2023; and U.S. Provisional Patent Application No. 63 / 607,056, filed Dec. 6, 2023.

[0002] This application generally relates to electronic devices having a touch-sensing surface, including but not limited to electronic devices having a touch-sensing surface.

Background Art

[0003] The use of touch-sensing surfaces as input devices for computers and other electronic computing devices has increased significantly in recent years. Exemplary touch-sensing surfaces include touch pads and touch screen displays. Such surfaces are widely used to manipulate user interfaces and objects therein on a display. Exemplary user interface objects include digital images, videos, text, icons, and control elements such as buttons and other graphics.

[0004] Illustrative operations include adjusting the position and / or size of one or more user interface objects, activating buttons, or opening files / applications represented by user interface objects, associating metadata with one or more user interface objects, or otherwise manipulating the user interface. Illustrative user interface objects include digital images, videos, text, icons, and control elements such as buttons and other graphics. In some situations, users need to perform such operations on user interface objects in file management programs (e.g., Finder from Cupertino, California, Apple Inc.), image management applications (e.g., Aperture, iPhoto, Photos from Cupertino, California, Apple Inc.), digital content (e.g., video and music) management applications (e.g., iTunes® from Cupertino, California, Apple Inc.), drawing applications, presentation applications (e.g., Keynote from Cupertino, California, Apple Inc.), word processing applications (e.g., Pages from Cupertino, California, Apple Inc.), or spreadsheet applications (e.g., Numbers from Cupertino, California, Apple Inc.).

[0005] Touch-sensitive displays are frequently utilized while the associated device is in use, but these displays are rarely utilized when the device is not in use. Even when the device is not in use, it can still provide access to its functions and / or applications, and can also provide event and / or application status information. [Overview of the project]

[0006] Therefore, there is a need for electronic devices that can provide users with improved functionality and information when certain criteria are met (for example, so that the device does not unnecessarily sacrifice battery power and / or provides such functionality in situations where it is unnecessary or inaccessible to the user). Such methods and interfaces reduce the number, range, and / or types of user input and produce a more efficient human-machine interface. With respect to battery-operated devices, such methods and interfaces conserve power and extend the time between battery charges.

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

[0008] According to some embodiments, the method is performed in a computer system communicating with a display generating component and one or more sensors. The method includes detecting a first event. In response to detecting the first event, the method includes, as a result of the first event, displaying a first customizable user interface that was not displayed before the first event was detected, in accordance with a determination that a first criterion is met, the first criterion requiring that, for the first criterion to be met, the orientation of the display generating component is in a first orientation and the computer system is charging; and, as a result of the first event, discontinuing to display the first customizable user interface, in accordance with a determination that the first criterion is not met.

[0009] According to some embodiments, the method is performed in a computer system communicating with a display generation component and one or more input devices. The method includes displaying a first user interface selected from a first set of user interfaces via the display generation component, the first user interface displaying a first type of content according to a first set of configuration options. The method includes detecting a first user input directed to the first user interface while the first user interface is being displayed. The method includes, in response to detecting a first user input directed to a first user interface, replacing the display of the first user interface with a display of a second user interface, the second user interface being selected from a first set of user interfaces and displaying a second type of content different from a first type of content, in accordance with a determination that the first user input satisfies a first direction criterion, the first direction criterion requiring the first user input to include movement in a first direction for the first direction criterion to be satisfied; and replacing the display of the first user interface with a display of a first type of content according to a second set of configuration options different from a first set of configuration options, in accordance with a determination that the first user input satisfies a second direction criterion, the second direction criterion requiring the first user input to include movement in a second direction different from a first direction for the second direction criterion to be satisfied. The method includes detecting a first user input, and then, while displaying individual user interfaces from a first set of user interfaces, detecting a second user input directed to an individual user interface.The method includes detecting a second user input and, in accordance with a determination that the second user input satisfies a first direction criterion, the first direction criterion requires that the second user input include movement in a first direction for the first direction criterion to be satisfied, replacing a display of an individual user interface with a display of a third user interface selected from a first set of user interfaces, the third user interface displaying a third type of content distinct from a first type of content and a second type of content.

[0010] According to some embodiments, the method is performed in a computer system communicating with a display generation component and one or more input devices. The method includes displaying a first user interface corresponding to a restricted state of the computer system, and in the first user interface, including simultaneously displaying a first widget of a first group of widgets at a first placement location and a second widget of a second group of widgets at a second placement location. The first placement location is configured to accommodate individual widgets of the first group of widgets, and the second placement location is configured to accommodate individual widgets of the second group of widgets. The method includes detecting a first user input directed to the first user interface while simultaneously displaying the first widget of the first group of widgets at the first placement location and the second widget of the second group of widgets at the second placement location in the first user interface. The method includes, upon detection of a first user input directed to a first user interface, replacing the display of a first widget with a different widget from a first group of widgets at the first placement location, according to a determination that the first user input is directed to a first placement location within the first user interface and that the first user input satisfies a first switching criterion; and replacing the display of a second widget with a different widget from a second group of widgets at the second placement location, according to a determination that the first user input is directed to a second placement location within the first user interface and that the first user input satisfies a first switching criterion.

[0011] According to some embodiments, the method is performed in a computer system communicating with a display generation component and one or more sensors. The method includes detecting that one or more conditions for displaying a particular user interface object of a first object type are met while a first user interface is being displayed. The particular user interface object of the first type corresponds to a particular application and provides status information that is updated over time within the particular user interface object without requiring the display of the particular application. The method includes displaying the particular user interface object in response to detecting that one or more conditions for displaying a particular user interface object of a first object type are met. The method includes detecting a first user input corresponding to a request to reject the particular user interface object while the particular user interface object is being displayed. The method includes, upon detecting a first user input corresponding to a request to reject an individual user interface object, ceasing to display the individual user interface object and redisplaying the first user interface in accordance with a determination that the first user interface is a first type of user interface, and ceasing to display the individual user interface object and displaying a second user interface different from the first user interface in the location previously occupied by the first user interface in accordance with a determination that the first user interface is a second type of user interface different from the first type of user interface.

[0012] According to some embodiments, the method is performed in a computer system communicating with a display generating component and one or more sensors. The method includes detecting the disconnection of the computer system from a charging source. In response to detecting the disconnection of the computer system from a charging source, the method includes activating the flashlight function of the computer system in accordance with the determination that the computer system has been disconnected from a charging source while it was in a first operating mode, which is a first operating mode in which the computer system displays a clock user interface via a display generating component for at least a portion of the duration that the computer system is operating in the first operating mode.

[0013] According to some embodiments, the method is performed in a computer system including a display generation component and one or more sensors. The method includes the computer system operating in a first mode, wherein the computer system operates in the first mode while a first criterion is met, and detecting the presence of a person in close proximity to the computer system via one or more sensors without detecting contact between the person and the computer system. The method includes updating the display content displayed via the display generation component of the computer system while remaining in the first mode, in response to detecting the presence of a person in close proximity to the computer system without detecting contact between the person and the computer system.

[0014] In some embodiments, the method is performed in a computer system communicating with one or more sensors for detecting display generation components and user input. The method includes detecting a first event. In response to the detection of the first event and in accordance with the determination that a first criterion is met as a result of the first event, the method includes displaying a separate customizable user interface that was not displayed before the detection of the first event. Displaying a separate customizable user interface includes displaying a first customizable user interface configured according to a first set of customization parameters corresponding to a first identity of a charging source, in accordance with the determination that one or more power transmission signals received from a charging source include first identification data representing a first identity of a charging source, and that the first identity of a charging source is stored in the computer system in relation to a first set of customization parameters.

[0015] In some embodiments, the computer system comprises a display generation component, one or more sensors for detecting user input, a power transmission coil adapted to receive power transmission signals from a charging source, a rectifier adapted to charge the computer system's battery using the power transmission signals received from the charging source by the power transmission coil, a communication circuit adapted to obtain identification data representing the individual identity of the charging source from at least one of the power transmission signals received from the charging source, and one or more processors. When executed by one or more processors, the computer system includes a memory that stores instructions causing the processors to perform actions including detecting a first event, and, in response to the detection of the first event and according to a determination that a first criterion is met as a result of the first event, displaying an individual customizable user interface that was not displayed before the detection of the first event.

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

[0017] Therefore, electronic devices and other computer systems comprising a display, a touch-sensitive surface, optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface, optionally one or more tactile output generators, optionally one or more device orientation sensors, and optionally an audio system are provided with improved methods and interfaces for activating, configuring, and interacting with different operating modes (e.g., providing access to different functions and / or information), thereby enhancing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces can complement or replace conventional methods for activating, configuring, and interacting with (existing) operating modes. [Brief explanation of the drawing]

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

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

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

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

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

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

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

[0025] [Figure 4C1] An exemplary state diagram of navigation between various user interfaces of a multifunctional device according to some embodiments is shown. [Figure 4C2] An exemplary state diagram of navigation between various user interfaces of a multifunctional device according to some embodiments is shown.

[0026] [Figure 5A] An exemplary user interface according to some embodiments that automatically displays a customizable user interface when certain criteria are met is shown. [Figure 5B] An exemplary user interface according to some embodiments that automatically displays a customizable user interface when certain criteria are met is shown. [Figure 5C] An exemplary user interface according to some embodiments that automatically displays a customizable user interface when certain criteria are met is shown. [Figure 5D] An exemplary user interface according to some embodiments that automatically displays a customizable user interface when certain criteria are met is shown. [Figure 5E] An exemplary user interface according to some embodiments that automatically displays a customizable user interface when certain criteria are met is shown. [Figure 5F]This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5G] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5H] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5I] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5J] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5K] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5L] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5M] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5N] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5O] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5P]This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5Q] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5R] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5S] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5T] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5U] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5V] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5W] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5X] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5Y] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5Z]This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5AA] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5AB] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5AC] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5AD] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5AE] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5AF] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5AG] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5AH] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5AI] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5AJ]This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5AK] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5AL] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5AM] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5AN] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5AO] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5AP] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5AQ] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5AR] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5AS] This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met. [Figure 5AT]This document presents several exemplary user interfaces that automatically display a customizable user interface when certain criteria are met.

[0027] [Figure 6A] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6B] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6C] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6D] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6E] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6F] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6G] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6H]This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6I] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6J] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6K] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6L] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6M] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6N] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6O] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6P]This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6Q] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6R] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6S] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6T] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6U] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6V] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6W] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6X]This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6Y] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6Z] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6AA] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6AB] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6AC] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6AD] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6AE] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6AF]This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6AG] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6AH] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6AI] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6AJ] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6AK] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6AL] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6AM] This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 6AN]This document illustrates exemplary user interfaces for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments.

[0028] [Figure 7A] This document presents exemplary user interfaces for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 7B] This document presents exemplary user interfaces for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 7C] This document presents exemplary user interfaces for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 7D] This document presents exemplary user interfaces for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 7E] This document presents exemplary user interfaces for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 7F] This document presents exemplary user interfaces for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 7G] This document presents exemplary user interfaces for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 7H] This document presents exemplary user interfaces for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 7I] This document presents exemplary user interfaces for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 7J]This document presents exemplary user interfaces for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 7K] This document presents exemplary user interfaces for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 7L] This document presents exemplary user interfaces for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 7M] This document presents exemplary user interfaces for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 7N] This document presents exemplary user interfaces for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 7O] This document presents exemplary user interfaces for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 7P] This document presents exemplary user interfaces for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 7Q] This document presents exemplary user interfaces for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 7R] This document presents exemplary user interfaces for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 7S] This document presents exemplary user interfaces for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 7T] This document presents exemplary user interfaces for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 7U] This document presents exemplary user interfaces for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 7V] This document presents exemplary user interfaces for interacting with and configuring a customizable user interface, according to several embodiments.

[0029] [Figure 8A] This document presents exemplary user interfaces for interacting with different user interfaces in different operating modes (e.g., ambient mode) and switching between different operating modes, according to several embodiments. [Figure 8B] This document presents exemplary user interfaces for interacting with different user interfaces in different operating modes (e.g., ambient mode) and switching between different operating modes, according to several embodiments. [Figure 8C] This document presents exemplary user interfaces for interacting with different user interfaces in different operating modes (e.g., ambient mode) and switching between different operating modes, according to several embodiments. [Figure 8D] This document presents exemplary user interfaces for interacting with different user interfaces in different operating modes (e.g., ambient mode) and switching between different operating modes, according to several embodiments. [Figure 8E] This document presents exemplary user interfaces for interacting with different user interfaces in different operating modes (e.g., ambient mode) and switching between different operating modes, according to several embodiments. [Figure 8F] This document presents exemplary user interfaces for interacting with different user interfaces in different operating modes (e.g., ambient mode) and switching between different operating modes, according to several embodiments. [Figure 8G]This document presents exemplary user interfaces for interacting with different user interfaces in different operating modes (e.g., ambient mode) and switching between different operating modes, according to several embodiments. [Figure 8H] This document presents exemplary user interfaces for interacting with different user interfaces in different operating modes (e.g., ambient mode) and switching between different operating modes, according to several embodiments. [Figure 8I] This document presents exemplary user interfaces for interacting with different user interfaces in different operating modes (e.g., ambient mode) and switching between different operating modes, according to several embodiments. [Figure 8J] This document presents exemplary user interfaces for interacting with different user interfaces in different operating modes (e.g., ambient mode) and switching between different operating modes, according to several embodiments. [Figure 8K] This document presents exemplary user interfaces for interacting with different user interfaces in different operating modes (e.g., ambient mode) and switching between different operating modes, according to several embodiments.

[0030] [Figure 9A] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9B] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9C]The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9D] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9E] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9F] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9G] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9H] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9I] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9J] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9K] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9L] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9M] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9N] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9O] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9P] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9Q] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9R] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9S] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9T]The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9U] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9V] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9W] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9X] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9Y] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9Z] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 9AA] The following are exemplary user interfaces for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generating component associated with a computing device, or other device) when certain criteria are met, according to several embodiments.

[0031] [Figure 10A] This is a flowchart of a process that automatically displays a customizable user interface when certain criteria are met, based on several embodiments. [Figure 10B] This is a flowchart of a process that automatically displays a customizable user interface when certain criteria are met, based on several embodiments. [Figure 10C] This is a flowchart of a process that automatically displays a customizable user interface when certain criteria are met, based on several embodiments. [Figure 10D] This is a flowchart of a process that automatically displays a customizable user interface when certain criteria are met, based on several embodiments. [Figure 10E] This is a flowchart of a process that automatically displays a customizable user interface when certain criteria are met, based on several embodiments. [Figure 10F] This is a flowchart of a process that automatically displays a customizable user interface when certain criteria are met, based on several embodiments. [Figure 10G]This is a flowchart of a process that automatically displays a customizable user interface when certain criteria are met, based on several embodiments. [Figure 10H] This is a flowchart of a process that automatically displays a customizable user interface when certain criteria are met, based on several embodiments. [Figure 10I] This is a flowchart of a process that automatically displays a customizable user interface when certain criteria are met, based on several embodiments. [Figure 10J] This is a flowchart of a process that automatically displays a customizable user interface when certain criteria are met, based on several embodiments. [Figure 10K] This is a flowchart of a process that automatically displays a customizable user interface when certain criteria are met, based on several embodiments. [Figure 10L] This is a flowchart of a process that automatically displays a customizable user interface when certain criteria are met, based on several embodiments.

[0032] [Figure 11A] This is a flowchart of the process for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 11B] This is a flowchart of the process for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 11C] This is a flowchart of the process for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 11D]This is a flowchart of the process for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 11E] This is a flowchart of the process for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 11F] This is a flowchart of the process for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments. [Figure 11G] This is a flowchart of the process for switching between different operating modes (e.g., ambient mode), interacting with different operating modes, and configuring different operating modes, according to several embodiments.

[0033] [Figure 12A] This is a flowchart of the process for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 12B] This is a flowchart of the process for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 12C] This is a flowchart of the process for interacting with and configuring a customizable user interface, according to several embodiments. [Figure 12D] This is a flowchart of the process for interacting with and configuring a customizable user interface, according to several embodiments.

[0034] [Figure 13A] This is a flowchart of a process for interacting with different user interfaces in different operating modes (e.g., ambient mode) and switching between different operating modes, according to several embodiments. [Figure 13B]This is a flowchart of a process for interacting with different user interfaces in different operating modes (e.g., ambient mode) and switching between different operating modes, according to several embodiments. [Figure 13C] This is a flowchart of a process for interacting with different user interfaces in different operating modes (e.g., ambient mode) and switching between different operating modes, according to several embodiments. [Figure 13D] This is a flowchart of a process for interacting with different user interfaces in different operating modes (e.g., ambient mode) and switching between different operating modes, according to several embodiments. [Figure 13E] This is a flowchart of a process for interacting with different user interfaces in different operating modes (e.g., ambient mode) and switching between different operating modes, according to several embodiments. [Figure 13F] This is a flowchart of a process for interacting with different user interfaces in different operating modes (e.g., ambient mode) and switching between different operating modes, according to several embodiments. [Figure 13G] This is a flowchart of a process for interacting with different user interfaces in different operating modes (e.g., ambient mode) and switching between different operating modes, according to several embodiments. [Figure 13H] This is a flowchart of a process for interacting with different user interfaces in different operating modes (e.g., ambient mode) and switching between different operating modes, according to several embodiments. [Figure 13I] This is a flowchart of a process for interacting with different user interfaces in different operating modes (e.g., ambient mode) and switching between different operating modes, according to several embodiments. [Figure 13J] This is a flowchart of a process for interacting with different user interfaces in different operating modes (e.g., ambient mode) and switching between different operating modes, according to several embodiments.

[0035] [Figure 14A] This is a flowchart illustrating a process for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generation component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 14B] This is a flowchart illustrating a process for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generation component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 14C] This is a flowchart illustrating a process for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generation component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 14D] This is a flowchart illustrating a process for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generation component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 14E] This is a flowchart illustrating a process for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generation component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 14F] This is a flowchart illustrating a process for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generation component associated with a computing device, or other device) when certain criteria are met, according to several embodiments. [Figure 14G] This is a flowchart illustrating a process for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generation component associated with a computing device, or other device) when certain criteria are met, according to several embodiments.

[0036] [Figure 15A] This document illustrates exemplary user interfaces for updating display content when existence criteria are met, according to several embodiments. [Figure 15B] This document illustrates exemplary user interfaces for updating display content when existence criteria are met, according to several embodiments. [Figure 15C] This document illustrates exemplary user interfaces for updating display content when existence criteria are met, according to several embodiments. [Figure 15D] This document illustrates exemplary user interfaces for updating display content when existence criteria are met, according to several embodiments. [Figure 15E] This document illustrates exemplary user interfaces for updating display content when existence criteria are met, according to several embodiments. [Figure 15F] This document illustrates exemplary user interfaces for updating display content when existence criteria are met, according to several embodiments. [Figure 15G] This document illustrates exemplary user interfaces for updating displayed content when existence criteria are met, according to several embodiments. [Figure 15H] This document illustrates exemplary user interfaces for updating display content when existence criteria are met, according to several embodiments. [Figure 15I] This document illustrates exemplary user interfaces for updating display content when existence criteria are met, according to several embodiments. [Figure 15J]This document illustrates exemplary user interfaces for updating display content when existence criteria are met, according to several embodiments. [Figure 15K] This document illustrates exemplary user interfaces for updating display content when existence criteria are met, according to several embodiments. [Figure 15L] This document illustrates exemplary user interfaces for updating display content when existence criteria are met, according to several embodiments. [Figure 15M] This document illustrates exemplary user interfaces for updating display content when existence criteria are met, according to several embodiments. [Figure 15N] This document illustrates exemplary user interfaces for updating display content when existence criteria are met, according to several embodiments. [Figure 15O] This document illustrates exemplary user interfaces for updating display content when existence criteria are met, according to several embodiments. [Figure 15P] This document illustrates exemplary user interfaces for updating display content when existence criteria are met, according to several embodiments. [Figure 15Q] This document illustrates exemplary user interfaces for updating display content when existence criteria are met, according to several embodiments.

[0037] [Figure 16A] This is a flowchart of a process for updating display content when existence criteria are met, according to several embodiments. [Figure 16B] This is a flowchart of a process for updating display content when existence criteria are met, according to several embodiments. [Figure 16C] This is a flowchart of a process for updating display content when existence criteria are met, according to several embodiments. [Figure 16D]This is a flowchart of a process for updating display content when existence criteria are met, according to several embodiments. [Figure 16E] This is a flowchart of a process for updating display content when existence criteria are met, according to several embodiments. [Figure 16F] This is a flowchart of a process for updating display content when existence criteria are met, according to several embodiments.

[0038] [Figure 17A] This is a flowchart of the process for displaying a customized user interface configured according to customized parameters corresponding to the received identity of a charging source, as in several embodiments. [Figure 17B] This is a flowchart of the process for displaying a customized user interface configured according to customized parameters corresponding to the received identity of a charging source, as in several embodiments. [Figure 17C] This is a flowchart of the process for displaying a customized user interface configured according to customized parameters corresponding to the received identity of a charging source, as in several embodiments. [Modes for carrying out the invention]

[0039] While portable electronic devices such as smartphones and tablets are becoming increasingly common, little attention is paid to utilizing such devices when they are not actively being used. Such devices can be used to provide users with useful information even when they are not actively being used. For example, a device can be configured to operate in a specific operating mode that provides time information (e.g., by functioning as a clock and / or displaying a clock face) and / or to provide quick access to useful utilities or time-dependent information (e.g., by displaying a user interface that shows status information that changes or updates over time (e.g., in real time) via a widget). Furthermore, the operating mode(s) can be configured to become active when certain criteria (e.g., the device is charging and / or in a specific orientation) are met, which can be tailored to scenarios where the device is not being used and scenarios where operating in the operating mode(s) does not have a detrimental effect on the device (e.g., the device's battery life when not connected to a charging source). Such operating modes provide efficient access to useful functions and information even when the device is not actively being used.

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

[0041] In the following, Figures 1A, 1B, 2, and 3 provide a description of an exemplary device. Figures 4A-4B and 5A-5AT show an exemplary user interface for automatically displaying a customizable user interface when certain criteria are met. Figures 6A-6AN show an exemplary user interface for switching between different operating modes (e.g., ambient modes), interacting with them, and configuring them. Figures 7A-7V show an exemplary user interface for interacting with and configuring a customizable user interface. Figures 8A-8K show an exemplary user interface for interacting with different user interfaces in different operating modes (e.g., ambient modes) and switching between different operating modes. Figures 9A-9AA show an exemplary user interface for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generation component associated with a computing device, or other device) when certain criteria are met. Figures 10A-10L are flowcharts of how to automatically display a customizable user interface when certain criteria are met. Figures 11A to 11G are flowcharts of methods for switching between different operating modes (e.g., ambient modes), interacting with them, and configuring them. Figures 12A to 12D are flowcharts of methods for interacting with and configuring a customizable user interface. Figures 13A to 13J are flowcharts of methods for interacting with different user interfaces in different operating modes (e.g., ambient modes) and switching between different operating modes. Figures 14A to 14G are flowcharts of a process for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generation component associated with a computing device, or other device) when certain criteria are met. Figures 15A to 15Q show exemplary user interfaces for updating display content when existence criteria are met.Figures 16A to 16F are flowcharts of the method for updating the displayed content when the existence criteria are met. The process in Figures 10A to 10L is shown using the user interface in Figures 5A to 5AT. The process in Figures 11A to 11G is shown using the user interface in Figures 6A to 5AN. The process in Figures 12A to 12D is shown using the user interface in Figures 7A to 7V. The process in Figures 13A to 13J is shown using the user interface in Figures 8A to 8K. The process in Figures 14A to 14G is shown using the user interface in Figures 9A to 9AA. The process in Figures 16A to 16F is shown using the user interface in Figures 15A to 15Q. Example device

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

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

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

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

[0046] Embodiments of electronic devices (and more generally computer systems), user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, which also includes other functions such as PDA functionality and / or music player functionality. Exemplary embodiments of portable multifunction devices include, but are not limited to, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptop or tablet computers having a touch-sensitive surface (e.g., a touchscreen display and / or touchpad), are optionally used. In some embodiments, it should also be understood that the device is not a portable communication device but a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and / or touchpad).

[0047] The following description refers to a computer system in the form of an electronic device, including a display and a touch-sensitive surface. However, please understand that the electronic device is optional and may include one or more other physical user interface devices, such as a physical keyboard, mouse, and / or joystick.

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

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

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

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

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

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

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

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

[0056] Memory 102 optionally includes high-speed random-access memory and optionally includes non-volatile memory such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by CPU(s) 120 and other components of device 100 such as peripheral interface 118 is optionally controlled by memory controller 122.

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

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

[0059] The RF (radio frequency) circuit 108 transmits and receives RF signals, also known as electromagnetic signals. The RF circuit 108 converts electrical signals to electromagnetic signals or electromagnetic signals to electrical signals and communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 108 optionally includes well-known circuits for performing these functions, which include, but are not limited to, antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, CODEC chipsets, subscriber identity module (SIM) cards, and memory. The RF circuit 108 optionally communicates wirelessly with networks such as the Internet, also known as the World Wide Web (WWW), intranets, and / or wireless networks such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs), as well as with other devices. Wireless communication is optional and includes Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), Long-Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), and Code Division Multiple Access (W-CDMA).Multiple 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 Using any of several communication standards, communication protocols, and communication technologies, including, but not limited to, a Service (IMPS), and / or Short Message Service (SMS), or any other suitable communication protocol, including a communication protocol not yet developed as of the filing date of this document.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0087] Examples of other applications 136 that may be optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, Java®-enabled applications, encryption, digital rights management, speech recognition, and speech duplication.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0101] In conjunction with the touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, and browser module 147, the video and music player module 152 includes executable commands that enable the user to download and play recorded music or other sound files stored in one or more file formats such as MP3 or AAC files, as well as executable commands to display, present, or otherwise play video (for example, on the touch-sensitive display system 112, or on an external display connected wirelessly or via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player such as an iPod (a trademark of Apple Inc.).

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

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

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

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

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

[0107] A default set of functions, performed only through the touchscreen and / or touchpad, optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 from any user interface displayed on the device 100 to a main menu, home menu, or root menu. 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] In some embodiments, the gesture includes an air gesture. An air gesture is a gesture detected by the user without (or independently of) touching an input element that is part of a device (e.g., a computer system 101, one or more input devices 125, and / or a hand tracking device 140), and is based on detected movement of a part of the user's body in the air (e.g., head, one or more arms, one or more hands, one or more fingers, and / or one or more legs), including 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 the user's other 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 a part of the user's body (e.g., a tap gesture including movement of the hand in a predetermined posture by a predetermined amount and / or speed, or a shake gesture including a predetermined speed or amount of rotation of a part of the user's body).

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

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

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

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

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

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

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

[0116] In some embodiments, the user's attention is determined to be directed towards a part of the three-dimensional environment based on the detection of a gaze directed towards that part of the three-dimensional environment (optionally, without requiring any other conditions). In some embodiments, for the device to determine that the user's attention is directed towards a part of the three-dimensional environment, the device determines that the user's attention is directed towards a part of the three-dimensional environment based on the detection of a gaze directed towards a part of the three-dimensional environment, with one or more additional conditions such as the gaze being directed towards the part of the three-dimensional environment for at least a threshold duration (e.g., dwell time) while the user's viewpoint is within a distance threshold from the part of the three-dimensional environment, and / or the gaze being directed towards a part of the three-dimensional environment. If one of the additional conditions is not met, the device determines that the user's attention is not directed towards the part of the three-dimensional environment to which the gaze is directed (e.g., until one or more additional conditions are met).

[0117] In some embodiments, the detection of a ready state configuration of the user or a part of the user is detected by the computer system. The detection of a ready state configuration of the hand is used by the computer system as an indication that the user is likely to be preparing to interact with the computer system using one or more air gesture inputs performed by the hand (e.g., pinch, tap, pinch and drag, double pinch, long pinch, or other air gestures described herein). For example, the ready state of a hand is determined based on whether the hand has a predetermined hand shape (e.g., a pre-pinch shape where the thumb and one or more fingers are extended and separated, ready to perform a pinch or grab gesture, or a pre-tap where one or more fingers are extended and the palm is facing away from the user), whether the hand is in a predetermined position relative to the user's viewpoint (e.g., below the user's head and above the user's waist, extended at least 15, 20, 25, 30, or 50 cm away from the body), and / or whether the hand has moved in a particular manner (e.g., moved towards the area in front of the user above the user's waist and below the user's head, or moved away from the user's body or legs). In some embodiments, the ready state is used to determine whether an interactive element of the user interface is responsive to attention (e.g., gaze) input.

[0118] In scenarios where the input is described in reference to an air gesture, similar gestures may also be detected using hardware input devices attached to or held by one or more of the user's hands, in which case the position of the hardware input device in space may be tracked using optical tracking, one or more accelerometers, one or more gyroscopes, one or more magnetometers, and / or one or more inertial measurement units, and it should be understood that the position and / or movement of the hardware input device is used instead of the position and / or movement of one or more hands in the corresponding air gesture(s). In scenarios where input is described in reference to an air gesture, similar gestures may also be detected using hardware input devices attached to or held by one or more of the user's hands, in which case user input may be detected using controls included in the hardware input device, such as one or more touch-sensitive input elements, one or more pressure-sensitive input elements, one or more buttons, one or more knobs, one or more dials, one or more joysticks, one or more hand or finger covers, and / or other hardware input device controls, and the hand or finger covers may detect the position or change in position of parts of the hand and / or fingers relative to each other, relative to the user's body, and / or the user's physical environment, in which case user input using controls included in the hardware input device is used instead of hand gestures and / or finger gestures such as air taps or air pinches in the corresponding air gesture(s). For example, a selection input described as being performed with an air tap or air pinch input may alternatively be detected by a button press, a tap on a touch-sensitive surface, a press on a pressure-sensitive surface, or other hardware input.As another example, a movement input described as being performed by an air pinch-and-drag (e.g., an air drag gesture or an air swipe gesture) can alternatively be detected based on interaction with hardware input controls such as button press-and-hold, touch on a touch-sensitive surface, or press on a pressure-sensitive surface, or based on hardware input that follows the movement of other hardware input devices in space (e.g., accompanying the hand to which the hardware input device is associated). Similarly, two-handed inputs, including movements of both hands relative to each other, can also be performed using various combinations of inputs detected by air gestures and / or one or more of the aforementioned hardware input devices, using one air gesture and one hardware input device held in the hand not performing the air gesture, two hardware input devices held in separate hands, or two air gestures performed by separate hands.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0143] The foregoing description regarding the handling of user touch events on a touch-sensitive display also applies to other forms of user input for operating the multifunction device 100 using input devices, but it should be understood that not all of this begins on the touchscreen. For example, mouse movement and mouse button presses, touch movements such as taps, drags, and scrolls on a touchpad, pen stylus input, device movement, verbal commands, detected eye movements, biometric input, and / or any combination thereof may be optionally used as inputs corresponding to sub-events that define the events to be recognized.

[0144] FIG. 2 shows a computer system 100 having a touch screen (e.g., the touch sensing display system 112 of FIG. 1A) according to some embodiments. The touch screen optionally displays one or more graphics within a user interface (UI) 200. In these embodiments, as well as in the embodiments described hereinafter, the user can select one or more of the graphics by performing gestures on the graphics using, for example, one or more fingers 202 (not drawn to an exact scale in the figure) or one or more styli 203 (not drawn to an exact scale in the figure). In some embodiments, the selection of one or more graphics is implemented when the user interrupts contact with the one or more graphics. In some embodiments, the gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, upward and / or downward), and / or rolling of a finger in contact with the device 100 (from right to left, from left to right, upward and / or downward). In some implementations or situations, an accidental contact with a graphic does not select the graphic. For example, if the gesture corresponding to the selection is a tap, a swipe gesture that sweeps over an application icon does not optionally select the corresponding application.

[0145] The device 100 optionally also includes one or more physical buttons such as a "home" or menu button 204. As described above, the menu button 204 is optionally used to navigate to any application 136 in a set of applications that are optionally executed on the device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key within a GUI displayed on the touch screen display or as a system gesture such as an upward edge swipe.

[0146] In some embodiments, device 100 includes a touch screen display, a menu button 204 (which may be referred to as a home button 204), a push button 206 for turning on / off the power supply to the device and locking the device, volume adjustment button(s) 208, a subscriber identity module (SIM) card slot 210, a headset jack 212, and / or a docking / charging external port 124. The push button 206 is optionally used to turn on / off the power of the device by pressing the button and holding it in the pressed state for a predetermined period, to lock the device by pressing the button and releasing it before a predetermined time elapses, and / or to unlock the device or initiate an unlock process. In some embodiments, device 100 also accepts verbal input through microphone 113 to activate or deactivate some functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of contact on touch sensing display system 112, and / or one or more haptic output generators 167 for generating haptic output to the user of device 100.

[0147] Figure 3 is a block diagram of an exemplary multifunctional device with a display and touch-sensitive surface, according to several embodiments. Device 300 does not need to be portable. In some embodiments, device 300 is a laptop computer, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a children's learning toy), game system, or 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. The communication buses 320 optionally include circuitry (sometimes referred to as a chipset) for interconnecting and controlling communication between system components. Device 300 typically includes an input / output (I / O) interface 330, which includes a display 340, which is a touchscreen display. The I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350, a touchpad 355, a touch output generator 357 for generating tactile output on a device 300 (similar to the tactile output generator(s) 167 described above with reference to Figure 1A, for example), and a sensor 359 (e.g., an optical sensor, an accelerometer, a proximity sensor, a touch sensor, and / or a touch intensity sensor similar to the touch intensity sensor(s) 165 described above with reference to Figure 1A). The memory 370 includes high-speed random-access memory such as DRAM, SRAM, DDR RAM, or other random-access solid-state memory devices, and optionally includes non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. The memory 370 optionally includes one or more storage devices located remotely from the CPU(s) 310.In some embodiments, memory 370 stores programs, modules, and data structures similar to, or subsets thereof, programs, modules, and data structures stored in memory 102 of computer system 100 (Figure 1A). Furthermore, memory 370 optionally stores additional programs, modules, and data structures that are not present in memory 102 of computer system 100. For example, memory 370 of device 300 optionally stores a drawing module 380, a presentation module 382, ​​a word processing module 384, a website creation module 386, a disk authoring module 388, and / or a spreadsheet module 390, while memory 102 of computer system 100 (Figure 1A) does not optionally store these modules.

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

[0149] Here, we turn our attention to the optional embodiments of the user interface ("UI") that are implemented on the computer system 100.

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

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

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

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

[0154] In some embodiments, the device's response to an input detected by the device depends on a criterion based on the contact intensity during the input. For example, for some "light press" inputs, a contact intensity exceeding a first intensity threshold during the input triggers a first response. In some embodiments, the device's response to an input detected by the device depends on a criterion that includes both the contact intensity during the input and a time-based criterion. For example, for some "deep press" inputs, a contact intensity exceeding a second intensity threshold during an input greater than a first intensity threshold for light presses triggers a second response only if a delay time has elapsed between satisfying the first and second intensity thresholds. This delay time is typically shorter than 200 ms (milliseconds) (e.g., 40 ms, 100 ms, or 120 ms, depending on the magnitude of the second intensity threshold, and the delay time increases as the second intensity threshold increases). This delay time helps avoid accidental recognition of deep press inputs. As another example, for some "deep press" inputs, there is a period of reduced sensitivity that occurs after the time the first intensity threshold is satisfied. During the period of reduced sensitivity, the second intensity threshold increases. This temporary increase in the second intensity threshold also helps to avoid accidental deep press inputs. For other deep press inputs, the response to the detection of deep press inputs is independent of time-based criteria.

[0155] In some embodiments, one or more of the input intensity threshold and / or corresponding outputs vary based on one or more factors, such as user settings, contact motion, input timing, the application being run, the rate at which intensity is applied, the number of simultaneous inputs, user history, environmental factors (e.g., ambient noise), and the position of the focus selector. Illustrative factors are described in U.S. Patent Publications 14 / 399,606 and 14 / 624,296, which are incorporated herein by reference in their entirety.

[0156] Figures 4C1 and 4C2 show exemplary state diagrams 4000 of navigation between various user interfaces of the multifunction device 100 according to several embodiments. In some embodiments, the multifunction device 100 displays individual user interfaces from several different user interfaces, including a wake screen user interface 490 (also referred to as a cover sheet user interface 496), a home screen user interface 492, a widget user interface 491, a control user interface 498, a search user interface 494, an application library user interface 497, and an application user interface 493 for individual applications of multiple applications (e.g., a camera application (e.g., camera application user interface 495), a flashlight application, a settings application, a messaging application (e.g., application user interface 493), a phone application, a map application, a browser application, or another type of application). In some embodiments, the multifunction device uses various parts of a display (e.g., a touchscreen display 112, a display associated with a touch-sensitive surface 340, a head-mounted display, or another type of display) to display persistent content across multiple user interfaces. For example, in some embodiments, the display includes a dynamic status area 4002 for displaying alerts, status updates, and / or current status in real time or substantially real time for various subscribed and / or ongoing events and / or various application activities. In some embodiments, the display includes a static status area 4022 for displaying status information for one or more system functions that are relatively stable over a period of time. In some embodiments, the dynamic status area 4002 changes from an area that accommodates one or more hardware elements of a multifunction device (e.g., a camera lens, a microphone, and / or a speaker) (e.g., it expands and / or shrinks).As described herein, the following examples are given by touch gestures on a touchscreen display, but similar functionality can be realized on a display associated with a touch-sensitive surface where locations on the touch-sensitive surface (e.g., locations on the top edge, bottom edge, left edge, right edge, upper left portion, lower right portion, interior portion, and / or other portions) have corresponding locations on the display (and / or on the user interface presented on the display) (e.g., locations on the top edge, bottom edge, left edge, right edge, upper left portion, lower right portion, interior portion, and / or other portions). Furthermore, although the following examples are given using touch gestures on a touchscreen display, similar functionality can be realized on a display associated with other types of input such as mouse input, pointer input, and gaze input (e.g., gaze with temporal and locational characteristics directed towards various parts of the displayed user interface and / or user interface elements), in conjunction with air gesture input (e.g., air tap, air swipe, air pinch, pinch and hold, pinch hold and drag, and / or other types of air gestures). As described herein, the following examples are given by touch gestures on a touchscreen display, but similar functionality can be achieved with a head-mounted display that displays a user interface in a three-dimensional environment and is controlled by various input devices and sensors for detecting various types of user input (e.g., touch gestures, input provided by a pointer or controller, gaze input, voice input, and / or air gestures).

[0157] As shown in Figure 4C1, when the multifunction device 100 is first powered on (for example, by a long press of the power button 116a (Figure 4A) of the multifunction device 100 or by other activation input 4100), the multifunction device displays a wake screen user interface 490 (4100), which is the first system user interface displayed on the multifunction device 100 when it transitions from a powered-off state to a powered-on state.

[0158] In some embodiments, while the wake screen user interface 490 is being displayed after a certain period of time, the multifunctional device 100 optionally transitions to a low power state in which the display of the multifunctional device 100 is optionally turned off or dimmed as indicated by the user interface 489 (4101). In some embodiments, the wake screen user interface 490 remains displayed in a dimmed always-on state while the multifunctional device 100 is in the low power state. For example, in the low power state indicated by the user interface 489, the time indication and / or the date indication continue to be displayed.

[0159] In some embodiments, the multifunctional device 100 transitions to the low power state (4101) (e.g., turns off the display or displays the dimmed always-on wake screen user interface 490) in response to activation of the power button 116a of the multifunctional device 100 by a user input 4101 (e.g., while any of the wake screen user interface 490 and / or other user interfaces described herein are being displayed).

[0160] In some embodiments, the multifunctional device transitions from a normal operating state, in which any of a plurality of user interfaces (e.g., the wake screen user interface 490, the home screen user interface 492, the application user interface 493 of an individual application, or another system and / or application user interface) can be the last user interface displayed before the transition to the low power state, to the low power state (e.g., automatically after an inactive period and / or in response to detecting a user input that activates the power button 116a).

[0161] In some embodiments, when the multifunction device 100 is in a low-power state, the multifunction device continues to detect input (e.g., movement of the device, touch gestures (e.g., swiping, tapping, or other touch inputs), gaze input, air gestures, impact to the device, pressing the power button, rotating the crown, or other types of inputs) via one or more sensors and input devices of the multifunction device. In some embodiments, in response to detecting user input via one or more sensors and input devices of the multifunction device, the multifunction device transitions from a low-power state to a normal operating state (4100) and displays the wake screen user interface 490 in a normal non-dimmed state.

[0162] In some embodiments, when the multifunction device 100 is in a low-power state as shown in the user interface 489, the multifunction device continues to detect events such as incoming notifications and status updates (e.g., message notifications, incoming communication requests, and / or other application-generated and system-generated events, as well as session status updates, subscribed events, and / or other status changes that require user attention). In some embodiments, upon detecting an event that generates an alert, notification, and / or status update, the multifunction device transitions from the low-power state to the normal operating state and displays the alert, notification, and / or status update on the wake-screen user interface 490 in a normal, non-dimmed state. In some embodiments, the multifunction device automatically returns to the low-power mode a short time after displaying the alert, notification, and / or status update.

[0163] In some embodiments, the wake screen user interface 490 displayed in a dimmed, always-on state includes the same or substantially the same set of user interface elements as the wake screen user interface 490 displayed in a normal operating state (in contrast to, for example, the dark screen shown in Figures 4C1 and 4C2). In some embodiments, the wake screen user interface 490 displayed in a dimmed, always-on state has fewer user interface elements than the wake screen user interface 490 displayed in a normal operating state. For example, in some embodiments, the wake screen user interface 490 displayed in a normal operating state includes a time element 4004 indicating the current time, a date element 4006 indicating the current date, and one or more widgets 4008 containing content from their respective applications that are updated at any time without user intervention. In some embodiments, the wake screen user interface 490 displayed in a normal operating state includes one or more application icons corresponding to their respective applications, such as an application icon 4010 for a flashlight application, an application icon 4012 for a camera application, or another system-recommended or user-selected application. In some embodiments, the wake screen user interface 490 displayed in normal operation includes one or more shortcuts to access the respective operations of one or more system-recommended and / or user-selected applications (for example, a shortcut to play music using a media player application, a shortcut to send a quick message using a messaging application, or a shortcut to turn on DND or sleep mode using a system application).In some embodiments, the wake screen user interface 490 includes a dynamic status area 4002 that displays status updates or current states of ongoing activities of one or more applications, such as communication sessions, charging sessions, running timers, music playback sessions, delivery updates, navigation commands, location sharing status, and / or status updates of subscribed applications and system events. In some embodiments, the wake screen user interface 490 includes a static status area 4022 that displays the status of one or more system functions, such as network connection status, battery status, location sharing status, cellular signal and carrier information, and other system status information. In some embodiments, dynamic status updates (e.g., battery charging, screen recording, location sharing, and other status updates) are first displayed in the dynamic status area 4002 and then moved to the static status area 4022 after a certain period of time. In some embodiments, when dimming is always on, the wake screen user interface 490 omits the dynamic status area 4002, the static status area 4022, the application icons 4010 and 4012, and / or shortcuts for application and / or system operations, and optionally disables interaction with the remaining user interface elements of the wake screen user interface 490 (e.g., wallpaper, time element 4004, date element 4006, and / or widget 4008).

[0164] In some embodiments, the wake screen user interface includes one or more recently received notifications (e.g., notification 4016, or one or more other newly received notifications) corresponding to one or more applications. In some embodiments, the wake screen user interface, displayed in a dimmed-always-on state, transitions to the wake screen user interface 490 upon detecting the receipt or generation of a new notification (e.g., notification 4016 in Figure 4C2, or one or more other newly received notifications). In some embodiments, notifications 4018 are grouped or merged based on the event type and / or application corresponding to the notification. In some embodiments, the user can interact with a notification to, for example, optionally, dismiss the notification (after valid authentication data has been requested and / or obtained), send the notification to the notification history, and / or expand the notification to view additional notification content.

[0165] In some embodiments, the wake screen user interface 490 may be displayed while the multifunction device is locked or unlocked. In some embodiments, if the wake screen user interface 490 is displayed while the multifunction device is locked, a locked symbol 4020a may optionally be displayed in a status area within the wake screen user interface 490 (e.g., dynamic status area 4002, static status area in the upper right corner of the display) or elsewhere (e.g., below the dynamic status area 4002, in the upper left corner, or in another part of the display) to indicate that the multifunction device is locked (e.g., as shown in the wake screen user interface 490 in Figure 4C1) and that authentication data is required to dismiss the wake screen user interface 490 in order to navigate to the home screen user interface 492 or the last displayed application user interface. In some embodiments, when the wake screen user interface 490 is displayed (e.g., in a low-power state and / or normal operating state), the multifunction device automatically attempts to obtain authentication data via a biometric scan (e.g., face, fingerprint, voiceprint, and / or iris), and if valid authentication data is successfully obtained, it automatically transitions to an unlocked state. In some embodiments, along with the transition to the unlocked state, the multifunction device replaces the locked symbol 4020a with the unlocked symbol 4020b to indicate that the multifunction device is now in an unlocked state (e.g., as shown in the wake screen user interface 490 in Figure 4C2).

[0166] In some embodiments, the multifunction device enables user interaction with the user interface elements of the wake screen user interface 490 when the wake screen user interface 490 is displayed in normal operating mode.

[0167] For example, in some embodiments, by selecting a user interface element such as a widget 4008, a status area 4002, a notification 4018, and / or an application icon 4010 or 4012 (e.g., by tapping, clicking, and / or air-tapping), the multifunction device navigates away from the wake screen user interface 490 and displays the individual user interface of the application corresponding to the selected user interface element, or an enlarged version of the user interface element, showing additional information and / or controls related to the content initially displayed for the selected user interface element. For example, in response to user input 4113 selecting a message notification 4018, as shown in Figure 4C2, the computer system displays the application user interface 493 for the messaging application (4113).

[0168] In another example, in some embodiments, an enhanced selection input 4112 (e.g., touch and hold gesture, light press input, or another type of input) on a separate user interface element such as the time element 4004, the date element 4006, or the wallpaper of the wake screen user interface 490 causes the multifunction device to display a configuration user interface for configuring one or more aspects of the wake screen user interface 490 (e.g., selecting a wallpaper, configuring a color or font scheme for user interface elements, configuring how different elements of the wake screen user interface are laid out, configuring additional wake screens, selecting previously configured wake screens, and viewing additional customization options for the wake screen user interface). In some embodiments, the configuration of the wake screen user interface 490 is partially applied to the home screen user interface 492, and vice versa.

[0169] In some embodiments, an extended selection input (e.g., touch and hold gesture, light press input, or another type of input) on the flashlight application icon 4010 or the camera application icon 4012 causes the multifunction device to activate the flashlight of the multifunction device or display the camera user interface 495 of the camera application. For example, upon detecting a selection input 4104a on the camera application icon 4012 within the wakescreen user interface 490, the multifunction device activates the camera application and displays the camera application UI 495 (4104a) (e.g., as shown in Figure 4C1).

[0170] In some embodiments, the multifunction device detects user interaction with user interface elements shown in the wake screen user interface 490, and if it determines that the wake screen user interface is locked, the multifunction device attempts to obtain authentication data from the user by displaying an authentication user interface (e.g., a passcode entry interface, a password entry user interface, and / or a biometric scan user interface). The multifunction device then navigates away from the wake screen user interface 490 and, after valid authentication data has been obtained from the user, performs actions according to the user's interaction.

[0171] In some embodiments, in addition to performing actions (e.g., navigating to an application user interface, displaying an extended version of a user interface element showing additional information, and / or displaying configuration options for individual user interface elements or the wake screen user interface), the multifunction device allows the user to navigate from the wake screen user interface 490 to other user interfaces (optionally, after valid authentication data has been obtained) in response to navigation input (e.g., areas of the wake screen user interface not occupied by user interface elements, and / or swipe gestures or other types of navigation input directed to areas of the wake screen user interface occupied by user interface elements that do not respond to swipe gestures or other types of navigation input (e.g., widgets, application icons, and / or time elements)).

[0172] For example, in some embodiments, an upward swipe gesture 4105 starting from the bottom edge of the wake screen user interface 490 causes the multifunction device to navigate away from the wake screen user interface 490 and (optionally, after requesting and obtaining valid authentication data) display the home screen user interface 492 or the last displayed application user interface (4105).

[0173] In some embodiments, the upward swipe gesture 4105 is a typical example of a home gesture or dismiss gesture (for example, other examples include upward swipe gestures 4103a, 4103c, 4103d, 4103e, 4110a, and 4111a) that causes a multifunction device to dismiss the currently displayed user interface (e.g., wake screen user interface 490, application user interface (e.g., camera user interface 495, message user interface 493, or another application user interface)) and navigate to the home screen user interface 492 or the last displayed user interface (e.g., wake screen user interface 490, wake screen configuration user interface, search user interface 494, application user interface, or home screen user interface 492).

[0174] In some embodiments, a downward swipe from the upper edge of the wake screen user interface 490 (e.g., the central portion of the upper edge, or any portion of the upper edge) or an internal area (e.g., a downward swipe 4106a, or another downward swipe) causes the multifunction device to display a search user interface 494, as shown in Figure 4C1, which includes a search input area 4030 and one or more application icons 4032 of recommended applications (e.g., recently used applications, and / or relevant applications based on the current context) (4106a). In some embodiments, upon detecting a search input in the search input area 4030, the multifunction device retrieves and displays search results, including relevant application content from different applications installed on the multifunction device (e.g., messages, notes, media files, and / or documents), relevant applications (e.g., applications installed on the multifunction device and / or applications available in the app store), relevant web pages (e.g., bookmarked web pages and / or newly retrieved web pages from the internet), and / or other sources (e.g., news, social media platforms, and / or referral websites). In some embodiments, different sets of search results are provided depending on the locked and unlocked states of the multifunction device, and if the multifunction device is unlocked when the search is performed, further details or additional search results may be displayed. In some embodiments, upon receiving a search input, the multifunction device attempts to obtain valid authentication data and displays different sets of search results depending on whether valid authentication data is obtained. In some embodiments, as shown in Figure 4C1, an upward swipe gesture 4103d (or another type of dismiss input) starting from the bottom edge of the search user interface causes the multifunction device to dismiss the search user interface 494 and redisplay the wake screen user interface 490 (4103d) (for example, because the wake screen user interface was the last user interface displayed).In some embodiments, a downward swipe 4106b from the internal area of ​​the home screen user interface 494 causes the multifunction device to display the search user interface 494 (4106b), and a subsequent upward swipe gesture 4103d from the bottom edge of the search user interface 492 causes the home screen user interface 492 to reappear (4103d), as shown in Figure 4C1 (for example, because the home screen user interface was the last displayed user interface).

[0175] In some embodiments, as shown in Figure 4C1, a rightward swipe gesture 4102a starting from the left edge or an internal area of ​​the wake screen user interface 490 allows the multifunction device to navigate from the wake screen user interface 490 to a widget user interface 491 (or another system user interface other than the home screen user interface, such as a control user interface, a search user interface, or a notification history user interface) (4102a). In some embodiments, the widget user interface 491 includes a plurality of widgets 4026 (e.g., including widgets 4026a, 4026b, and 4026c) that are automatically selected by the operating system and / or selected by the user to be included in the widget user interface 491. In some embodiments, the widgets 4026 displayed in the widget user interface 491 have a larger form factor than the widgets 4008 displayed under the time element 4004 of the wake screen user interface 490. In some embodiments, the widgets 4026 displayed in the widget user interface 491 and the widgets 4008 displayed in the wake screen user interface 490 are selected and / or configured independently of each other. In some embodiments, the widgets 4026 in the widget user interface 491 contain content from their respective applications, and the content is automatically updated as updates to the content become available in their respective applications. In some embodiments, the selection of individual widgets within the widget user interface (e.g., by tapping an individual widget or by providing other selection inputs directed to an individual widget) causes the multifunction device to navigate away from the widget user interface 491 and (optionally, after valid authentication data has been requested and / or obtained) display the user interface of the application corresponding to the individual widget.

[0176] In some embodiments, as shown in Figure 4C1, an upward swipe gesture 4103a starting from the bottom edge of the widget user interface 491 and / or a leftward swipe gesture 4103b starting from the right edge or internal area of ​​the widget user interface 491 cause the multifunction device to dismiss the widget user interface 491 and redisplay the wake screen user interface 490 (4103a-1 / 4103b-1).

[0177] In some embodiments, a leftward swipe gesture 4104b starting from the right edge or inside of the wake screen user interface 490 causes the multifunction device to navigate from the wake screen user interface 490 to the camera user interface 495 of the camera application (4104b). In some embodiments, access to the photo library via the camera application is restricted in the camera user interface 495 unless valid authentication data is obtained. In some embodiments, as shown in Figure 4C1, an upward swipe gesture 4103c or another dismiss input starting from the bottom edge of the camera user interface 495 causes the multifunction device to navigate away from the camera user interface 495 and redisplay the wake screen user interface 490 (4103c) (for example, because the wake screen user interface 490 is the last user interface displayed before the camera user interface 495 is displayed).

[0178] In some embodiments, a downward swipe gesture 4109a starting from the right portion of the upper edge of the wake screen user interface (as shown in Figure 4C2, for example) causes the multifunction device to display a control user interface 498 that overlays or replaces the display of the wake screen user interface 490 (4109a). In some embodiments, the control user interface 498 includes status information of one or more static status indicators displayed in the static status area 4022, and a set of controls 4028 for various system functions such as network connectivity (WiFi, cellular data, airplane mode, Bluetooth, and other connection types), media playback controls, display controls (e.g., display brightness, color temperature, night shift, true tone, and dark mode controls), audio controls (e.g., volume, and / or mute / unmute controls), focus mode controls (e.g., DND, work, study, sleep, and other modes where the generation of alerts and notifications is mitigated based on context and configuration), and application icons (e.g., flashlight, timer, calculator, camera, screen recording, and / or other user-selected or system-recommended applications). In some embodiments, an upward swipe gesture 4110a (or another dismiss input) starting from the bottom edge of the control user interface 498 causes the multifunction device to dismiss the control user interface 498 and redisplay the wake screen user interface 490 (4110a-1), since the wake screen user interface 490 is the last user interface displayed before the control user interface 498 is displayed.

[0179] In some embodiments, an upward swipe gesture 4107 originating from an internal area of ​​the wake screen user interface 490 and / or an upward swipe gesture originating from within the cover sheet user interface 496 (for example, optionally, if no unread notifications are displayed within the cover sheet user interface) causes the multifunction device to display a notification history user interface (4107) containing multiple previously saved notifications and notifications sent directly to the notification history without first being displayed on the wake screen user interface 490. In some embodiments, in response to an upward swipe gesture 4118 directed to the notification history within the wake screen user interface 490 and / or the cover sheet user interface 496, the notification history user interface can be scrolled to reveal additional notifications. In some embodiments, the notification history is displayed as part of the wake screen user interface 490 and / or the cover sheet user interface 496, and a downward swipe gesture 4103f directed towards the inner portion of the notification history stops the display of the notification history and redisplays the wake screen user interface 490 and / or the cover sheet user interface 496 without the notification history.

[0180] As described above, after navigating from the wake screen user interface 490 to an individual user interface other than the home screen user interface (for example, in response to a downward, leftward, or rightward swipe gesture), an upward swipe gesture 4103 (e.g., 4103a, and 4103c-4103f) starting from the bottom edge of the individual user interface (for example, an upward swipe gesture starting from the bottom edge of a touch-sensitive display that displays the individual user interface in full-screen mode, or an upward swipe gesture starting from the bottom edge of a touch-sensitive surface corresponding to the display that displays the individual user interface) causes the multifunction device to reject the individual user interface and return to the wake screen user interface 490. In contrast, an upward swipe gesture 4105 starting from the bottom edge of the wake screen user interface 490 causes the multifunction device to navigate away from the wake screen user interface 490 and display the home screen user interface 492 (4105), while another upward swipe gesture starting from the bottom edge of the home screen user interface 492 does not cause the multifunction device to reject the home screen user interface 492 and does not allow it to return to the wake screen user interface 490. In other words, once navigation from the wake screen user interface 490 to the home screen user interface 492 is complete, the multifunction device is no longer restricted, and access to application icons displayed on the home screen user interface 492, as well as access to the content and functionality of the computer system, is not restricted for the user. An upward swipe gesture starting from the bottom edge of the currently displayed user interface is a typical example of a reject input that rejects the currently displayed user interface and redisplays the last displayed user interface.An upward swipe gesture starting from the bottom edge of the currently displayed user interface is also a typical example of a home gesture that dismisses the currently displayed user interface and displays the home screen user interface (regardless of whether, for example, the home screen user interface was the last user interface displayed before the currently displayed user interface was shown).

[0181] As shown in Figure 4C2, once the multifunction device navigates away from the wake screen user interface 490 and displays the home screen user interface 492, the user can access the functions and applications of the multifunction device without restriction. For example, in some embodiments, the home screen user interface 492 includes multiple pages, and each page of the home screen user interface includes a separate set of application icons and / or widgets corresponding to different applications, and a user selection of an individual widget or application icon (e.g., by tapping, clicking, or otherwise selecting it) causes the multifunction device to display the application user interface of the application corresponding to the individual widget or application icon.

[0182] In some embodiments, the home screen user interface 492 displays a search affordance 4034 (for example, as shown in Figure 4C1), and a tap on the search affordance 4034 causes the search user interface 494 to be displayed overlaid on the home screen user interface 492. In some embodiments, in response to detecting an upward swipe gesture 4103d (or another dismiss input) starting from the bottom edge of the search user interface, the multifunction device dismisses the search user interface 494 and redisplays the home screen user interface 492 (4103d) (for example, an upward edge swipe gesture dismisses the currently displayed user interface and redisplays the last displayed system user interface, not the wake screen user interface 490).

[0183] In some embodiments, as shown in Figure 4C1, a rightward swipe gesture 4102b starting from the left edge of the first page of the home screen user interface 492 causes the multifunction device to display the widget user interface 491 (4102b). In some embodiments, a leftward swipe gesture starting from the right edge or internal area of ​​the widget user interface (e.g., gesture 4103b, or another leftward swipe gesture), or an upward swipe gesture starting from the bottom edge of the widget user interface 491 (e.g., gesture 4103a, or another upward swipe gesture), causes the multifunction device to navigate away from the widget user interface 491 and redisplay the first page of the home screen user interface 492 (4103a-2 / 4103b-2) (for example, if the home screen user interface 492 was the last user interface displayed before the widget user interface 491 was displayed).

[0184] In some embodiments, a series of leftward swipe gestures 4116 on the home screen user interface 492 navigate through a series of pages of the home screen user interface 492 until the application library user interface 497 is displayed (4116), as shown in Figure 4C2. In some embodiments, the application library user interface 497 displays application icons from multiple pages of the home screen user interface, grouped into different categories. In some embodiments, the application library user interface 497 includes a search user interface element 4036 that accepts search criteria (e.g., keywords, images, and / or other search criteria) and returns application icons of relevant applications (e.g., applications stored on the multifunction device and / or applications available in the app store) as search results. In some embodiments, user selection of an application icon within the search results and / or within the application library (e.g., by tap input, click input, or another type of selection input) causes the multifunction device to display the application user interface of the application corresponding to the selected application icon.

[0185] In some embodiments, a downward swipe gesture 4109c starting from the right portion of the upper edge of the application library user interface 497 causes the control user interface 498 to be displayed as described above. In some embodiments, an upward swipe gesture (e.g., upward swipe gesture 4110a, or another upward swipe gesture) or another reject input starting from the bottom edge of the control user interface 498 causes the multifunction device to reject the control user interface 498 and redisplay the application library user interface 497 (e.g., because the application library user interface is the last user interface displayed before the control user interface was displayed) (e.g., or to redisplay another user interface (e.g., wake screen user interface) Redisplay -490 (4110a-1) (for example, if the control user interface 498 is displayed in response to a swipe gesture 4109a) (for example, if the control user interface is displayed in response to a downward swipe from the upper right part of the top edge of the display) Redisplay the home screen user interface 492 (4110a-3) or (for example, if the control user interface is displayed in response to a downward swipe 4109b) Redisplay the application user interface that was the last user interface displayed before the control user interface was displayed (4110a-2)).

[0186] In some embodiments, a rightward swipe gesture 4115 starting from the internal area or left edge of the application library user interface 497, or an upward swipe gesture starting from the bottom edge of the application library user interface 497, causes the multifunction device to dismiss the application library user interface 497 and redisplay the last page of the home screen user interface 492 (4115).

[0187] In some embodiments, a downward swipe gesture 4114, starting from an internal area of ​​the application library user interface 497, causes the multifunction device to display application icons of applications stored on the multifunction device in a scrollable list (for example, in chronological or alphabetical order).

[0188] In some embodiments, an upward swipe gesture starting from the bottom edge of the home screen user interface causes the multifunction device to display either the first page of the home screen user interface 492 or the multitasking user interface 488 (also referred to as the application switcher user interface). In some embodiments, different criteria (e.g., criteria based on speed, direction, duration, distance, intensity, and / or other characteristics) are used to determine whether to navigate to the first page of the home screen user interface 492 or to the multitasking user interface 488 in response to detecting an upward swipe gesture starting from the bottom edge of the home screen user interface. For example, in some embodiments, a short flick and a slow, long swipe cause the multifunction device to navigate to the first page of the home screen user interface 492, while a slow, medium-length swipe causes the multifunction device to display the multitasking user interface 488. In some embodiments, the navigation gesture is dynamically evaluated before the end of the gesture is detected, and therefore the estimated destination user interface of the navigation gesture continues to change, and visual feedback regarding the estimated destination user interface continues to be provided to guide the user to end the gesture when the desired destination user interface is indicated by the visual feedback. In some embodiments, in response to user input 4117 in a portion of the application-independent multitasking user interface 488, the last displayed user interface that was displayed before the multitasking user interface 488 is displayed is shown (for example, when the multitasking user interface 488 is displayed in response to user input 4111b, the home screen user interface 492 is displayed).

[0189] In some embodiments, a reconfiguration mode of the home screen user interface 492 is displayed, and application icons and / or widgets may be rearranged, removed from, or added to different pages of the home screen user interface 492. In some embodiments, a touch and hold gesture or another extended selection input directed to the home screen user interface 492, or another extended selection input directed to the home screen user interface 492, during a separate threshold time period causes the multifunction device to display the home screen user interface 492 in configuration mode. In some embodiments, a selection of a search affordance 4034 within the home screen user interface 492 while the home screen user interface 492 is in reconfiguration mode causes the multifunction device to display a page editing user interface for the home screen user interface, where pages of the home screen user interface may be rearranged, deleted, hidden, or created. In some embodiments, a tap input on the home screen user interface in reconfiguration mode causes the home screen user interface to exit reconfiguration mode. In some embodiments, a tap input on an unoccupied portion of the page editing user interface causes the multifunction device to exit the page editing user interface and redisplay the home screen user interface in reconfiguration mode. Another tap on the home screen user interface will exit reconfiguration mode and redisplay the home screen user interface in normal mode.

[0190] In some embodiments, while the home screen user interface 492 is displayed, a downward swipe gesture 4108a starting from the top edge of the home screen user interface 492 causes the multifunction device to cover the home screen user interface 492 with a cover sheet user interface 496 (also referred to as the wake screen user interface 496 if the user interface is displayed when transitioning from normal mode to low power mode and / or vice versa (e.g., due to inactivity, due to activation of the power button, and / or due to user input in response to a request to wake or lock the device) (4108a), and access to the home screen user interface is temporarily restricted by the cover sheet user interface 490. In some embodiments, while the cover sheet user interface 496 is displayed, an upward swipe gesture 4103e starting from the bottom edge of the cover sheet user interface 496 dismisses the cover sheet user interface 496 (4103e) and redisplays the home screen user interface 492 (e.g., because the home screen user interface is the last displayed user interface). In some embodiments, the cover sheet user interface has a response to user input in a manner similar to that described with respect to the wake screen user interface 490.

[0191] In some embodiments, the application user interface of an individual application may be displayed in response to user input in multiple scenarios, such as tapping a widget displayed in the home screen user interface or widget user interface, tapping an application icon displayed in the home screen, widget user interface, search results or recommended application section of the search user interface, application library user interface, or search results provided in the search within the application library user interface, tapping a notification on the wake screen user interface or in the notification history, tapping an application representation in the multitasking user interface, or selecting a link to an application in the user interface of another application (e.g., a link to a document, a link to a phone number, a link to a message, a link to an image, and other types of links). In some embodiments, the user interface of a single application is displayed in full-screen mode. In some embodiments, the user interfaces of two or more applications are displayed in a simultaneous display configuration, such as a side-by-side display configuration where the user interfaces of the applications are displayed adjacent to each other so that they fit within the display, or an overlay display configuration where the user interface of a first application is displayed in full-screen mode and the user interfaces of other applications are overlaid on (e.g., in a single stack or separately on different parts) a portion(s) of the user interface of the first application.

[0192] In some embodiments, while an application user interface is being displayed, an upward swipe gesture (e.g., upward swipe gesture 4111a, or another upward swipe gesture) or another dismiss input or home gesture starting from the bottom edge of the application user interface (e.g., message user interface 493, or another user interface of the application), or another dismiss input or home gesture, causes the multifunction device to dismiss the currently displayed application user interface (4111a-1, or 4111a-2) and, depending on the characteristics of the upward swipe gesture, display either a home screen user interface (e.g., shown as transition 4111a-1) or a multitasking user interface (e.g., shown as transition 4111a-1). In some embodiments, while the home screen user interface 492 is displayed, an upward swipe gesture 4111b starting from the bottom edge of the home screen user interface causes the multifunction device to dismiss the currently displayed home screen user interface 492 and display the multitasking user interface 488 (4111b).

[0193] In some embodiments, a leftward and / or rightward horizontal swipe gesture performed within the bottom of one or more application user interfaces causes the multifunction device to switch to another previously displayed application user interface of a different application. In some embodiments, the same swipe gesture starting from the bottom of a separate application user interface is successively evaluated to determine and update an estimated destination user interface among the multitasking user interface 488, the home screen user interface 492, or the user interface of a previously displayed application, based on the characteristics of the swipe gesture (e.g., location, speed, direction, and / or changes in one or more of the above), and the final destination user interface is displayed according to the estimated destination user interface at the end of the swipe gesture (e.g., lift-off of contact, reduction of contact intensity, pause of movement, and / or change of another type of input).

[0194] In some embodiments, while displaying the application user interface of an individual application (or displaying the application user interfaces of multiple applications in a simultaneous display configuration), a downward swipe gesture 4108b starting from the upper edge of the application user interface(s) causes the multifunction device to display a cover sheet user interface 496 (Figure 4C1) (or the wake screen user interface 490 in Figure 4C2) on top of the application user interface(s) (4108b). The multifunction device rejects the cover sheet user interface(s) 496 (or the wake screen user interface(s) 490) and redisplays the application user interface(s) in response to an upward swipe gesture (or another rejection input) starting from the bottom edge of the cover sheet user interface(s).

[0195] In some embodiments, as shown in Figure 4C2, a downward swipe gesture 4109b starting from a static status area 4022 on the display causes the multifunction device to display a control user interface 498 on an application user interface (one or more) (4109b), and an upward swipe gesture 4110a (or another dismiss input) starting from the bottom edge of the control user interface 498 dismisses the control user interface 498 and causes the application user interface (for example, or the last displayed user interface displayed before the control user interface 498 was displayed) to be displayed again (4110a-2).

[0196] In some embodiments, rotating the display causes the multifunction device to display different versions of the currently displayed user interface (e.g., application user interface, home screen user interface, wake screen user interface, control user interface, notification user interface, widget user interface, application library user interface, and other user interfaces described with respect to Figures 4C1-4C2) having different layouts (e.g., landscape vs. portrait versions). In some embodiments, rotating the display does not affect the orientation of the currently displayed individual user interface.

[0197] The above descriptions of navigation between user interfaces, as well as the precise appearance and components of various user interfaces, are illustrative and can be implemented in various modifications in the various embodiments described herein. In addition, the transitions between the pairs of user interfaces shown in Figures 4C1 to 4C2 are only a subset of all possible transitions between different pairs of user interfaces shown in Figures 4C1 to 4C2, and transitions to individual user interfaces may, according to various embodiments, be possible from any of several other user interfaces, in accordance with the same type of individual user input directed to the same interaction area of ​​the display, and / or in accordance with different types of input, or directed to different interaction areas. User interface and related processes

[0198] Here, we turn our attention to embodiments of user interfaces ("UI") and related processes that may be implemented on an electronic device (or more generally, a computer system), such as a computer system 100 or device 300, having a display, 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.

[0199] Figures 5A to 5AT show exemplary user interfaces for automatically displaying a customizable user interface when certain criteria are met. Figures 6A to 6AN show exemplary user interfaces for switching between different operating modes (e.g., ambient modes), interacting with them, and configuring them. Figures 7A to 7V show exemplary user interfaces for interacting with and configuring a customizable user interface. Figures 8A to 8K show exemplary user interfaces for interacting with different user interfaces in different operating modes (e.g., ambient modes) and switching between different operating modes. Figures 9A to 9AA show exemplary user interfaces for automatically activating the flashlight function of computer system 100 when certain criteria are met. Figures 10A to 10L are flowcharts of how to automatically display a customizable user interface when certain criteria are met. Figures 11A to 11G are flowcharts of how to switch between different operating modes (e.g., ambient modes), interact with them, and configure them. Figures 12A to 12D are flowcharts of how to interact with and configure a customizable user interface. Figures 13A to 13J are flowcharts of how to interact with different user interfaces in different operating modes (e.g., ambient mode) and how to switch between different operating modes. Figures 14A to 14G are flowcharts of the process for automatically activating the flashlight function of computer system 100 when certain criteria are met. Figures 15A to 15Q show exemplary user interfaces for updating display content when existence criteria are met. Figures 16A to 16F are flowcharts of how to update the displayed content when existence criteria are met. The user interfaces in these figures are used to illustrate the processes described below, including the processes in Figures 10A to 10L, 11A to 11G, 12A to 12D, 13A to 13J, 14A to 14G, and 16A to 16F.For the sake of explanation, some embodiments will be discussed in reference to operations performed on a device having a touch-sensitive display system 112. In such embodiments, the focus selector is optionally the contact of an individual finger or stylus, a representative point corresponding to the finger or stylus contact (e.g., the center of the individual contact or a point associated with the individual contact), or the center of the faces of two or more contacts detected on the touch-sensitive display system 112. However, similar operations are optionally performed on a device having a display 450 and separate touch-sensitive surfaces 451 in response to the detection of contact on the touch-sensitive surface 451 while displaying the user interface shown in the figure on the display 450.

[0200] Figures 5A to 5AT show exemplary user interfaces in several embodiments that automatically display a customizable user interface when certain criteria are met.

[0201] In Figure 5A, the computer system 100 is in a low-power state. In some embodiments, the low-power state is an off state in which nothing is displayed by the portable multifunction device. In some embodiments, as shown in Figure 5A, in the low-power state, several user interface elements such as the current time 5002, widget 5004, widget 5006, and widget 5008 are displayed, but their prominence (e.g., brightness) is reduced compared to when the computer system 100 is not in a low-power state. In some embodiments, displaying user interface elements inconspicuously is referred to as "always-on" display.

[0202] While the computer system 100 is in a low-power state, the computer system 100 detects user input 5010 (e.g., tap input) directed towards the touch-sensitive surface (e.g., touchscreen) of the computer system 100.

[0203] In Figure 5B, upon detecting user input 5010, the computer system 100 displays a wake user interface (e.g., the same wake user interface as the wake screen user interface 490 in Figure 4C1). The wake user interface includes the current time 5002, widgets 5004, 5006, and 5008. The wake user interface also includes notifications 5014 and 5016 (e.g., not displayed while the computer system 100 is in a low-power state). While the wake user interface is displayed, the computer system 100 detects user input 5018 (e.g., a leftward swipe input).

[0204] In Figure 5C, in response to detecting user input 5018, the computer system 100 displays the camera user interface. The camera user interface includes a preview of the current field of view of the computer system 100's camera and also includes affordances for switching to the computer system 100's video recording function, for taking a photograph, and for switching to the field of view of different cameras of the computer system 100. While displaying the camera user interface, the computer system 100 detects user input 5020 (for example, an upward swipe gesture starting from the bottom edge of the computer system 100).

[0205] In Figure 5D, upon detecting user input 5020, the portable multifunction device redisplays the wake user interface (e.g., the wake user interface shown in Figure 5B). While the wake user interface is displayed, the user can interact with different elements of the wake user interface to perform different functions of the computer system 100. For example, responding to user input 5022 on area 5021. In response to user input 5024 (e.g., a downward swipe from the upper right corner of the touch-sensitive display of the computer system 100), the computer system 100 displays the control center user interface. In response to user input 5026 directed at widget 5006 (e.g., a tap input), the computer system 100 displays the user interface corresponding to the application associated with widget 5006. Upon detecting user input 5028 (e.g., tap input) directed to notification 5014, the computer system 100 displays additional content associated with notification 5014 and / or additional options for interacting with notification 5014 (e.g., an option to open the application associated with notification 5014). Upon detecting user input 5030 (e.g., a left or right swipe input) directed to notification 5016, the computer system 100 displays affordances for opening the application associated with notification 5016, for adjusting one or more notification settings, and / or for clearing or dismissing notification 5016.

[0206] In response to detecting user input 5032 (e.g., a downward swipe input), the computer system 100 displays a search user interface (e.g., optionally including one or more suggested applications or functions). In response to detecting user input 5034 (e.g., an upward swipe input), the computer system 100 displays a notification history (e.g., including one or more additional notifications other than notifications 5014 and 5016). In some embodiments, user input 5032 and / or user input 5034 may also be used to navigate (e.g., scroll) between displays of additional notifications (e.g., when the number of notifications available for display is greater than the maximum number of notifications that can be displayed simultaneously by the computer system 100).

[0207] In response to detecting user input 5036 (e.g., a leftward swipe input) within an area of ​​the wake user interface that is not occupied by a notification (e.g., notification 5014 or notification 5016), the computer system 100 displays the camera user interface (e.g., as shown in Figures 5B to 5C and as described above). In response to detecting user input 5038 (e.g., a rightward swipe input) within an area of ​​the wake user interface that is not occupied by a notification, the computer system 100 displays a widget user interface (e.g., including one or more widgets of the computer system 100, which are optionally configured by the user of the computer system 100).

[0208] In response to detecting user input 5040 (for example, an upward swipe input from the bottom edge of the computer system 100), the computer system 100 displays an authentication user interface, as shown in Figure 5E. In some embodiments, as shown in Figure 5E, the authentication user interface includes one or more affordances for entering a password or passcode to authenticate the user of the computer system 100. In some embodiments, the computer system 100 authenticates the user via biometric authentication such as facial recognition, or by another method such as scanning the user's fingerprints. The computer system 100 optionally still displays one or more affordances for entering a password or passcode, which provides an alternative authentication mechanism to biometric authentication (for example, if the user's face is obscured by a mask or helmet, or if the user is wearing gloves).

[0209] In Figure 5F, if the user successfully authenticates, the computer system 100 displays the home user interface. The home user interface includes application icons that can be interacted with to launch each application of the computer system 100. The home user interface may also include one or more widgets that display application information without the need to launch or open individual applications. The home user interface includes a settings icon 5043 (for example, to access and / or configure one or more settings of the computer system 100). In some embodiments, when the settings icon 5043 is activated by user input 5041, the computer system 100 displays a settings user interface for configuring different modes of the computer system 100 (for example, ambient modes of the computer system 100). Exemplary settings user interfaces are described in further detail below with reference to Figures 5AL and 5AM.

[0210] In Figure 5G, the computer system 100 displays the wake user interface (for example, because the user has not interacted with the computer system 100 for a threshold amount of time, causing the computer system 100 to return to its "locked" (or unauthenticated) state, or because the user has manually locked the computer system 100). In Figure 5G, the computer system 100 is not connected to a charging source. The display of the computer system 100 starts in portrait orientation and rotates to landscape orientation. Because the computer system 100 is not connected to a charging source, the computer system 100 maintains the display of the wake user interface.

[0211] In some embodiments (for example, as shown in Figure 5G), the computer system 100 is not configured to display the wake user interface in landscape orientation, so the computer system 100 maintains the display of the wake user interface in portrait orientation (even though, for example, the display of the computer system 100 is rotated to landscape orientation).

[0212] Figure 5H is an alternative example of Figure 5G, showing a computer system 100 with different dimensions (for example, the width and height of the computer system 100's display are substantially similar, allowing the computer system 100 to be operated more effectively while the computer system 100's display is in landscape orientation). In Figure 5H, the computer system 100 is again not connected to a charging source. The computer system 100's display is rotated to landscape orientation, and the computer system 100 maintains the display of the wake user interface, but is in landscape orientation (compared to the portrait orientation in Figure 5G, for example).

[0213] Figure 5I shows an alternative example to Figure 5G. In contrast to Figure 5G, in Figure 5I, the computer system 100 is connected to a charging source via a physical charger 5044. Upon detecting that the physical charger 5044 is connected, the computer system 100 displays an indicator 5042 indicating that the computer system 100 is charging. For example, the indicator 5042 includes text indicating that the computer system 100 is charging, and the current battery level (e.g., 38%).

[0214] In Figure 5J, after a threshold time period (e.g., 1 second, 2 seconds, 5 seconds, or 10 seconds) has elapsed, the computer system 100 stops displaying the indicator 5042. In some embodiments, the computer system 100 displays an animated transition of the indicator 5042 to a battery indicator in area 5046 or in a status area (e.g., the upper right corner of the computer system 100's display) (e.g., collapsed). Since the computer system 100's display remains vertically oriented while connected to a charging source via a physical charger 5044, the computer system 100 maintains the display of the wake user interface.

[0215] Figure 5K shows an alternative to Figure 5I, using a wireless charger 5048 instead of a physical charger 5044. Figure 5K shows various diagrams of the computer system 100 (while the computer system 100's display is in portrait orientation), showing the location of the wireless charger 5048 relative to the computer system 100. In response to detecting that the computer system 100 is connected to a charging source via the wireless charger 5048, the computer system 100 displays indicator 5050. In some embodiments, indicator 5050 is the same as indicator 5042 in Figure 5J (for example, the computer system 100 displays the same indicator when the computer system 100 is charging, regardless of whether the computer system 100 is charging via a physical cable or via a wireless charger). In some embodiments, indicator 5050 has a different appearance compared to indicator 542 in Figure 5J (for example, to provide visual feedback on the particular way in which the computer system 100 is charging).

[0216] Figure 5L shows another alternative example of Figure 5I using a long-range wireless charger 5052. In some embodiments, the long-range wireless charger 5052 includes at least one antenna configured to transmit (e.g., and / or focus) energy to the computer system 100 (e.g., without requiring the computer system 100 to be in close proximity to the long-range wireless charger 5052). In response to detecting that power is being received from the long-range wireless charger 5052, the computer system 100 displays an indicator 5054. In some embodiments, the indicator 5054 is the same as indicator 5042 (e.g., in Figure 5J) and / or indicator 5050 (e.g., in Figure 5K). In some embodiments, the indicator 5054 is separate from indicators 5042 and 5050.

[0217] Figures 5J to 5L illustrate different ways in which the computer system 100 can be connected to a charging source (e.g., to be charged). For ease of explanation, the following description refers to a charging source 5056 representing any suitable method of connecting the computer system 100 to a charging source (e.g., wired charging, wireless charging, and / or long-range wireless charging, as shown in Figures 5J to 5L). The following description is understood to be applicable to any (or all) variations of how the computer system 100 is connected to the charging source.

[0218] Figure 5M shows that the computer system 100 is connected to a charging source 5056 and the computer system 100's display is in landscape orientation. Since both of these conditions are met simultaneously, the computer system 100 displays the clock user interface 5058 (for example, the ambient mode user interface in ambient mode in which the computer system 100 operates, depending on whether it has detected that both conditions are met simultaneously). In some embodiments, the computer system 100 further requires that the computer system 100 be operating in a restricted mode (for example, low power mode or locked mode) in order to display the clock user interface 5058. If the computer system 100 is connected to a charging source 5056 and the computer system 100's display is in landscape orientation, but the computer system 100 is not operating in restricted mode, the computer system 100 will not display the clock user interface 5058 (for example, it will not enter ambient mode). When the computer system 100 enters restricted mode (for example, in response to detection that the user has locked the computer system 100 and / or has performed user input to operate the computer system 100 in low-power mode) (for example, while the computer system 100 remains connected to the charging source 5056 and the display of the computer system 100 remains in landscape orientation), the computer system 100 displays the clock user interface 5056 (for example, in response to detection that the computer system 100 has entered restricted mode) (and enters ambient mode).

[0219] In some embodiments, the clock user interface 5058 is a user interface that is displayed when a particular mode of the computer system 100 (e.g., “ambient mode”) is active. In some embodiments, the particular mode is a mode in which the computer system 100 is configured to display (e.g., continuously) user-related content of the computer system 100 without user input.

[0220] In some embodiments, the computer system 100 requires additional criteria to be met in addition to the two conditions described above in order to display the clock user interface 5058 (e.g., the ambient mode user interface). For example, the computer system 100 may also require that the computer system 100 is in a locked (or other restricted) state (e.g., the computer system 100 does not transition to displaying the clock user interface 5058 when the computer system 100 is unlocked and to displaying the home screen user interface of the computer system 100 before the two conditions described in the previous paragraph are met). For example, the computer system 100 may also require that the computer system 100 is not communicating with a vehicle (e.g., actively) (e.g., not connected to a vehicle such as a car via a wireless communication protocol such as Bluetooth). For example, the computer system 100 may also require that the computer system 100 does not detect movement exceeding a threshold amount (e.g., the computer system 100 is not being carried by a walking or running user, or the computer system 100 is not in a moving vehicle). In some embodiments, if the computer system 100 detects movement exceeding a threshold amount within a threshold time period while displaying the clock user interface 5058 (for example, while the computer system 100 is operating in ambient mode), the computer system 100 stops displaying the clock user interface 50508 (for example, the computer system 100 automatically stops operating in ambient mode).

[0221] In Figure 5M, the computer system 100 displays indicator 5060 (for example, in response to detecting that the computer system 100 is connected to the charging source 5056). In some embodiments, as shown in Figure 5M, indicator 5060 is different from indicator 5042 (for example, in Figure 5J), indicator 5050 (for example, in Figure 5K), and indicator 5054 (for example, in Figure 5L). This provides visual feedback on whether the computer system 100 is currently in ambient mode (for example, or the normal mode of the computer system 100). In some embodiments, indicator 5060 is the same as at least one of indicators 5042, 5050, and / or 5054.

[0222] In some embodiments, if ambient mode has never been activated for computer system 100 (for example, if computer system 100 has recently received a system update that enables ambient mode activation), computer system 100 displays an additional description of ambient mode (for example, a description of a specific ambient mode currently active, or a description of a single ambient mode available to computer system 100). In some embodiments, the additional description is displayed as a pop-up window, banner, or other user interface, overlaid on at least a portion of the clock user interface 5058 in Figure 5M). In some embodiments, the additional description is displayed before the clock user interface 5058 is displayed. In some embodiments, the additional description includes instructions for activating ambient mode (for example, the correct orientation of the computer system 100's display, and / or requirements for computer system 100 to be connected to the charging source 5056). In some embodiments, additional information is displayed only when the computer system 100 first enters ambient mode (e.g., or a single ambient mode), and not each time the computer system 100 enters ambient mode (e.g., or a single ambient mode).

[0223] In Figure 5N, after a threshold time period (e.g., 1 second, 2 seconds, 5 seconds, or 10 seconds), the computer system 100 stops displaying indicator 5060. In some embodiments, the computer system 100 stops displaying indicator 5060 and displays indicator 6062. In some embodiments, the computer system 100 displays an animated transition of indicators collapsing into indicator 6062.

[0224] In response to detecting a user input 6062 (e.g., a tap input) directed to indicator 5060, the computer system 100 redisplays indicator 6062, as shown in Figure 5O. In some embodiments, the computer system 100 instead displays additional power and / or battery information (e.g., in addition to or other than the information displayed on indicator 5060). In Figure 5P, after a threshold time period, the computer system 100 stops displaying the (redisplayed) indicator 5060.

[0225] In some embodiments, as shown in Figures 5Q to 5X, the computer system 100 displays a context-relevant user interface while the computer system 100 is in ambient mode. In some embodiments, the computer system 100 has different ambient modes, such as (1) a time or clock ambient mode, (2) a widget ambient mode, (3) a home control ambient mode, (4) a voice memo ambient mode, (5) an ambient sound ambient mode, and / or (6) a visual media ambient mode. In some embodiments, the computer system 100 has only one ambient mode, but can display different categories of user interfaces (e.g., "ambient mode user interfaces") for a single ambient mode of the computer system 100 (for example, the first category of ambient mode user interfaces is a time / clock ambient mode user interface, the second category of ambient mode user interfaces is a widget ambient mode user interface, the third category of ambient mode user interfaces is a home control ambient mode user interface, the fourth category of ambient mode user interfaces is a voice memo ambient mode user interface, the fifth category of ambient mode user interfaces is an ambient sound ambient mode user interface, and / or the sixth category of ambient mode user interfaces is a visual media ambient mode user interface).

[0226] In some embodiments, a user of the computer system 100 can configure settings for different ambient modes or a single ambient mode via a settings user interface. For example, Figure 5AL shows a settings user interface 5136 for configuring ambient mode settings of the computer system 100. In some embodiments, the computer system 100 displays the settings user interface 5136 in response to detecting one or more user inputs (for example, user input 5041 directed to the settings icon 5043 on the home screen user interface of the computer system 100 in Figure 5F) that launch a settings application and / or open the settings user interface of the computer system 100.

[0227] The configuration user interface 5136 includes an “ambient mode” option 5140 for enabling or disabling ambient mode (for example, whether the computer system 100 operates in ambient mode when certain criteria are detected). In some embodiments, the “ambient mode” option 5140 is a toggle (for example, via user input 5152 to enable or disable ambient mode). In some embodiments, the “ambient mode” option 5140 includes additional options for specifying one or more criteria for when the computer system 100 operates in ambient mode. In some embodiments, one or more criteria include a default criterion (for example, the computer system 100’s display is in landscape orientation and / or the computer system 100 is connected to a charging source 5056). In some embodiments, the default criterion is not configurable (for example, it must always be met), but in some embodiments, the default criterion can be replaced with other user-specified criteria (for example, to provide greater flexibility to the user when ambient mode is active). In some embodiments, the “ambient mode” option 5140 also includes one or more additional options for configuring the ambient mode user interface for ambient mode. For example, the user can configure which ambient mode user interface (and / or category of ambient mode user interface) is displayed in which context. The user can also configure a default ambient mode user interface that is initially displayed when the computer system 100 enters ambient mode (for example, or a default ambient mode user interface for a particular category of ambient mode user interface that is initially displayed when the computer system 100 displays ambient mode user interfaces of a particular category).

[0228] The configuration user interface 5136 includes an "always on" option 5142 for enabling or displaying an "always on" state for the ambient mode user interface (for example, a state in which at least several user interface elements are always displayed, but with reduced visual prominence, while the computer system 100 is operating in a low-power mode (e.g., sleep mode)).

[0229] The configuration user interface 5136 includes a "Wake by Bump" option 5146 for enabling or disabling the wake of the computer system 100 (e.g., from sleep or other low-power states) (e.g., via user input 5158 on the toggle of the "Wake by Bump" option 5146) in response to the detection of vibration of the computer system 100 (e.g., vibration exceeding a threshold amount of vibration) (e.g., vibration corresponding to an external impact on the support surface of the computer system 100, or a direct impact with the computer system 100 itself).

[0230] The configuration user interface 5136 includes an "Indicator" option 5148 for enabling or disabling the display of notifications (e.g., notification alerts) while the computer system 100 is operating in ambient mode (e.g., via user input 5160 on a toggle of the "Indicator" option 5148). In some embodiments, when the "Indicator" option is toggled on, the computer system 100 displays a visual indicator (e.g., a dot, a banner, or another visual representation) for incoming and / or out-of-call notifications. In some embodiments, the visual indicator includes a preview of the notification content corresponding to the individual notification.

[0231] The configuration user interface 5136 includes a “night mode” option 5144 for enabling or disabling “night mode” of the ambient mode user interface (for example, a mode in which multiple user interface elements are displayed with a different appearance (e.g., reduced, simplified, dimmed, adjusted, and / or less saturated) compared to the normal or default appearance of the user interface elements (one or more)). In some embodiments, the “night mode” option 5144 allows the user to configure additional options related to night mode and / or ambient mode of the computer system 100. In response to detecting user input 5156 directed to option 5144, the computer system 100 displays a configuration user interface 5162 (for example, a configuration user interface for configuring night mode of the computer system 100).

[0232] Figure 5AM shows a configuration user interface 5162 for configuring the night mode of the computer system 100. The configuration user interface 5162 includes option 5164 for enabling or disabling the night mode of the computer system 100 (for example, via user input 5168 on a toggle for option 5164). The configuration user interface 5162 also includes a “Motion to Wake” option 5166 for enabling or disabling the device to wake up when movement is detected while the computer system 100 is operating in night mode (for example, via user input 5170 on a toggle for “Motion to Wake” option 5166).

[0233] The configuration user interface 5162 includes a "back" affordance 5172 (for example, when activated, it causes the computer system 100 to redisplay the configuration user interface 5136 in Figure 5AL). The configuration user interface 5136 includes a "configure" affordance 5150 (for example, when activated, it causes the computer system 100 to display or redisplay the configuration user interface for the computer system 100 (for example, a general configuration user interface for configuring one or more settings for the computer system 100)).

[0234] Figures 5Q to 5X show exemplary user interfaces corresponding to exemplary ambient modes. Further details regarding these exemplary ambient modes, as well as user inputs for switching between ambient modes, switching between variations of the same ambient mode, and / or interacting with different ambient modes, are described in more detail with reference to Figures 6A to 6AJ, 7A to 7V, 9A to 9AA, and 15A to 15Q.

[0235] For the sake of clarity, the following descriptions (including those for Figures 6A-6AN, 7A-7V, 8A-8K, 9A-9AA, and 15A-15Q) refer to different ambient modes (e.g., Time or Clock Ambient Mode, Widget Ambient Mode, Home Control Ambient Mode, Voice Memo Ambient Mode, Ambient Sound Ambient Mode, and / or Visual Media Ambient Mode) to provide an intuitive categorization of ambient mode user interfaces (e.g., variants of Time or Clock Ambient Mode include various ways of displaying time-related information and / or different types of clocks and / or clock faces, and variants of Widget Ambient Mode include various ways of displaying widgets). However, in some embodiments, only a single ambient mode exists (for example, the ambient mode is either active or inactive to the computer system 100), and all of the described user interfaces (for example, the clock user interface corresponding to the time or clock ambient mode, the widget user interface corresponding to the widget ambient mode, the voice memo user interface corresponding to the voice memo ambient mode, the ambient sound user interface corresponding to the ambient sound ambient mode, and the media user interface corresponding to the visual media ambient mode) are variants of the ambient mode user interface for the (single) ambient mode of the computer system 100 (for example, they may also be described as variants of the ambient mode clock user interface, variants of the ambient mode widget user interface, variants of the ambient mode voice memo user interface, variants of the ambient mode ambient sound user interface, and variants of the ambient mode media user interface).

[0236] In some embodiments, the transition between Figures 5Q to 5X may occur automatically (for example, in response to the fulfillment of certain context-specific criteria, such as time-based or location-based criteria), but Figures 5Q to 5X also show optional user input (e.g., an upward swipe input) for manually switching between different variations of individual ambient modes, or optional user input (e.g., a leftward swipe input) for switching between different ambient modes. In some embodiments, even if the computer system 100 automatically switches between one or more ambient modes, the user can still manually adjust the ambient modes (e.g., via optional user inputs in Figures 5Q to 5X).

[0237] Figure 5Q shows a clock user interface 5068 (corresponding, for example, to a time or clock ambient mode). In some embodiments, the clock user interface 5068 is a variation of the clock user interface for a time or clock ambient mode. The clock user interface 5058 is another variation of the clock user interface for a time or clock ambient mode. In some embodiments, the clock user interface 5068 is displayed in response to the detection of user input 5066 (Figure 5P).

[0238] In some embodiments, the clock user interface 5058 is displayed automatically based on a time-based criterion (e.g., time of day). For example, in Figure 5Q, the current time is 1:30 p.m. (e.g., "daytime"), and the computer system 100 displays the clock user interface 5068 during "daytime" (e.g., a user-specified period corresponding to the daytime hours, or a default period based at least partially on sunrise and / or sunset at the current location of the computer system 100). In some embodiments, the clock user interface 5058 is displayed based on an illumination criterion (e.g., the computer system 100 determines whether it is "daytime" or "nighttime" based on the amount of ambient light detectable by one or more sensors of the computer system 100).

[0239] Figure 5R shows a clock user interface 5072 (for example, another variation of the clock user interface for time or clock ambient mode). In some embodiments, the clock user interface 5072 displays the current time with different levels of emphasis (e.g., hour and / or detail). For example, in Figure 5R, the current time is 1:25 AM, and the computer system 100 displays only a "1" to indicate the current time (in contrast to displaying both hours and minutes, as in the clock user interface 5068 in a "daytime" context, for example).

[0240] In some embodiments, as will be described in more detail with reference to Figures 9A to 9AA, the clock user interface 5072 is instead a user interface for different ambient modes or different categories of ambient mode user interfaces (for example, the time or clock ambient mode is different from the “night clock” or sleep ambient mode). In some embodiments, the clock user interface 5072 is displayed while a sleep mode (for example, the “sleep” focus mode) is active for the computer system 100.

[0241] Figure 5S shows a widget user interface 5078 (corresponding, for example, to the widget ambient mode of computer system 100). In some embodiments, the widget user interface 5078 is referred to as the “infograph” user interface (for example, the widget ambient mode is referred to as the “infograph ambient mode”). In some embodiments, the widget user interface 5078 is displayed in response to the detection of user input 5076 in Figure 5R (for example, a leftward swipe input). The widget user interface 5078 is displayed in context when a particular focus mode of computer system 100 (for example, the “work” focus mode) is active. In some embodiments, while a focus mode of computer system 100 is active, computer system 100 adjusts how content (e.g., notifications, messages, calendar events, and / or other application content) is displayed (e.g., displays a subset of available content) and / or generated (e.g., suppresses some notifications while the focus mode is active). In some embodiments, individual focus modes of the computer system 100 change how content is displayed and / or generated in different ways (for example, different focus modes adjust how content is displayed and / or generated in different ways).

[0242] In some embodiments, the widget user interface 5078 is instead displayed when the computer system 100 detects that it is in a work location (for example, a location corresponding to a known office of the user of the computer system 100). In some embodiments, the widget user interface 5078 is displayed while the “Work” focus mode is active for the computer system 100, and the “Work” focus mode is active while the computer system 100 is in a “Work” location.

[0243] The widget user interface 5078 includes a calendar widget on the left and a memo widget on the right. In some embodiments, the user can interact with the widget user interface 5078 (e.g., without leaving widget ambient mode). For example, upon detecting user input 5080 (e.g., an up / down swipe within the area occupied by the calendar widget), the computer system 100 may stop displaying the calendar widget and display a different widget of the computer system 100 (e.g., something other than the calendar widget and the memo widget). Similarly, upon detecting user input 5082 (e.g., an up / down swipe within the area occupied by the memo widget), the computer system 100 may stop displaying the memo widget and display a different widget. In some embodiments, the user can switch between a first subset of widgets via the left side of the widget user interface 5078, and the user can switch between a second subset of widgets (e.g., different from the first subset of widgets) via the right side of the widget user interface 5078.

[0244] In some embodiments, different variations of the widget user interface for widget ambient mode include different available widgets (e.g., different subsets of the widgets on computer system 100). For example, widget user interface 5078 includes a calendar widget and a memo widget, and another widget user interface may include a weather widget, a stock widget, a stopwatch widget, or one or more of other widgets available on computer system 100.

[0245] In some embodiments, each widget user interface for widget ambient mode has access to each available widget (e.g., or at least a subset of widgets) of the computer system 100, and variations within different widget user interfaces relate to the layout and / or presentation of widgets. For example, one variation of the widget user interface may display only a single widget instead of displaying two widgets side by side as in the widget user interface 5078 of Figure 5S. Another variation of the widget user interface may display three or more widgets instead of the two widgets displayed simultaneously in the widget user interface 5078 of Figure 5S. Another variation of the widget user interface may display widgets arranged vertically instead of horizontally in the widget user interface 5078 of Figure 5S. In some embodiments, different widget user interfaces (e.g., including different widgets) are displayed depending on the context. For example, in Figure 5S, the widget user interface 5078 includes a calendar widget and a memo widget while the “Work” focus mode is active for the computer system 100. When a different focus mode (for example, the "Home" focus mode as shown in Figure 5T) is active, the computer system 100 displays a different widget user interface that includes different widgets (for example, a stock widget and a weather widget as shown in Figure 7C).

[0246] Figure 5T shows the home control user interface 5086 (for example, corresponding to the home control ambient mode). In some embodiments, the home control user interface 5086 is displayed in response to the detection of user input 5084 in Figure 5S (for example, a leftward swipe input). The home control user interface 5086 is displayed contextually while the computer system 100's "home" focus mode is active. In some embodiments (for example, as shown in Figure 5U), the home control user interface 5086 is instead displayed contextually when the computer system 100 detects that it is in a pre-configured location (for example, the home location).

[0247] The home control user interface 5086 includes climate affordances 5088, lighting affordances 5090, security affordances 5092, audio / visual affordances 5094, and water affordances 5096. The affordances of the home control user interface 5086 allow the user to adjust the settings of one or more features of the user's home (e.g., smart thermostat, smart lights, smart speaker, and / or smart TV) via the computer system 100.

[0248] In some embodiments, different variations of the Home Control user interface for Home Control Ambient Mode provide access to different affordances (and / or subsets of affordances). For example, one variation of the Home Control user interface may include an affordance for a user-curated list of frequently adjusted features (e.g., favorites). Another variation of the Home Control user interface may include an affordance for adjusting feature settings within a specific area of ​​the user's home (e.g., a variation of the Home Control user interface may correspond to different rooms in the user's home).

[0249] In some embodiments, as shown in Figure 5U, the user can interact with the home control user interface 5088. The computer system 100 detects user input 5098 directed to the lighting affordance 5090.

[0250] In Figure 5V, in response to detecting user input 5098, the computer system 100 displays the home control user interface 5100. The home control user interface 5100 includes affordances for adjusting lighting-related settings. For example, the home control user interface 5100 includes affordance 5106, which allows the user to adjust the settings for a desk lamp in the user's home office (for example, in response to detecting user input 5108 directed to affordance 5106). The home control user interface also includes affordance 5102, which allows the user to adjust the lighting settings for the entrance area of ​​the user's home, and affordance 5104, which allows the user to adjust the lighting settings for the user's home office.

[0251] In some embodiments, as shown in Figures 5W to 5X, context-specific criteria include criteria that depend on how the computer system 100 is being charged. For example, in Figure 5P, the computer system 100 can be charged via a physical charger (e.g., the physical charger 5044 in Figures 5I to 5J), and the computer system 100 displays the clock user interface 5058. In Figure 5X, the computer system 100 is being charged via a wireless charger 5048 (e.g., as shown in Figure 5W), and the computer system 100 displays the clock user interface 5110 (e.g., different from the clock user interface 5058 in Figure 5P).

[0252] In Figure 5Y, the computer system 100 displays an indicator 5112 corresponding to an active timer (for example, in the computer system 100's clock application). The indicator 5112 includes an icon (e.g., a clock, timer, or stopwatch icon) that provides visual feedback about the application and / or function represented by the indicator 5112, and the indicator 5112 includes the current time of the active timer (e.g., 5:38 remaining time for a countdown timer). While the indicator 5112 is displayed, the computer system 100 detects user input 5114 (e.g., a tap input) directed to the indicator 5112.

[0253] In response to detecting user input 5114, the computer system 100 displays the user interface 5116, as shown in Figure 5Z. The user interface 5116 includes the current time of the active timer (5:38 remaining), and also includes a pause affordance for pausing the active timer, and a stop affordance for stopping or canceling the active timer. In some embodiments, the computer system 100 displays an animated transition of an indicator 5112 that extends (e.g., downward and / or outward) within the user interface 5116.

[0254] In Figure 5AA, the display of the computer system 100 is rotated from portrait orientation to landscape orientation. With the display of the computer system 100 rotated to landscape orientation and the computer system 100 connected to a power source (e.g., as indicated by the charger 5136), the computer system 100 displays the user interface 5118. In some embodiments, the user interface 5118 is a different appearance of the user interface 5116 (e.g., but displayed with a different appearance and / or increased visual prominence).

[0255] In some embodiments, the user interface 5118 occupies the entire display of the computer system 100 (for example, the user interface 5118 is a full-screen user interface). Similar to the user interface 5116 in Figure 5Z, the user interface 5118 includes a pause affordance for pausing the active timer, a stop affordance for stopping or canceling the active time, and the current time of the active timer (5:38 remaining). In addition, the user interface 5118 also includes a (non-numeric) visual representation of the current time of the active timer. The gray area of ​​the user interface 5118 represents the amount of time that has elapsed since the active timer was started, and the white area of ​​the user interface 5118 represents the remaining time before the active timer expires. In Figure 5AA, the active timer is configured to start from 10 minutes and count down, with 5 minutes and 38 seconds remaining for the active timer. The visual indication shows a gray area that is slightly smaller than the white area (for example, 5:38 indicates that it is just over half of the total time of the active timer). In some embodiments, the visual indication is updated as the timer progresses (e.g., in real time or at predetermined time intervals). For example, the gray area may continue to expand to the right as the timer progresses to indicate how close the timer is to expiring.

[0256] In some embodiments, the user interface 5118 displays content corresponding to multiple active timers (e.g., visual representations of multiple active timers and / or controls for interacting with multiple active timers). In some embodiments, the content corresponding to each active timer is displayed simultaneously within the user interface 5118 (e.g., stacked vertically or arranged horizontally).

[0257] While displaying user interface 5118, the computer system 100 detects user input directed to user interface 5118 (e.g., an upward swipe input). In response to detecting user input 5120, the computer system 100 displays the clock user interface 5058 (e.g., the same clock user interface 5058 shown in Figure 5M), as shown in Figure 5AB. The clock user interface 5058 is displayed because the computer system 100's display is in landscape orientation while connected to power. User interface 5122 is displayed overlaid on a portion of user interface 5058. In some embodiments, user interface 5122 is similar to user interface 5116 in Figure 5Z (but has a different appearance, for example, relative to the computer system 100's landscape orientation while the computer system 100 is operating in ambient mode).

[0258] While displaying the user interface 5122 overlaid on the user interface 5058, the computer system 100 detects user input 5124 directed to the user interface 5122 (e.g., an upward swipe input). In response to detecting user input 5124, the computer system 100 displays an indicator 5126 overlaid on the user interface 5058, as shown in Figure 5AC. In some embodiments, the indicator 5126 is similar to the indicator 5112 in Figure 5Y (for example, but having a different appearance and relative to the horizontal orientation of the computer system 100's display).

[0259] In some embodiments, the computer system 100 displays an indicator 5126 overlaid on the user interface 5058 after a threshold amount of time (for example, during periods of inactivity or when the user is not interacting with the computer system 100 and / or the user interface 5122). In other words, the computer system 100 may automatically (for example, without requiring user input 5124) transition from displaying the user interface 5122 in Figure 5AB to displaying the indicator 5126 in Figure 5AC.

[0260] While the indicator 5126 is displayed, the computer system 100 detects user input 5128 directed at the indicator 5126 (e.g., a tap input or a long press input). In response to the detection of user input 5128, the computer system 100 displays one or more of the previously displayed user interfaces (e.g., redisplays them).

[0261] For example, Figure 5AD shows an example in which the computer system 100 redisplays the user interface 5122 (e.g., overlaid again on the user interface 5058). Figure 5AE shows another example in which the computer system 100 redisplays the user interface 5116. In some embodiments, in response to detecting user input 5128 and determining that user input 5128 is a tap input, the computer system 100 redisplays the user interface 5512 (Figure 5AD). In response to detecting user input 5128 and determining that user input 5128 is a long press input, the computer system 100 redisplays the user interface 5116 (e.g., the computer system 100 skips the state shown in Figure 5AD and instead transitions directly from the state shown in Figure 5AC to the state shown in Figure 5AE). In some embodiments, the computer system 100 redisplays the user interface 5116 in response to detecting user input directed to user interface 5122 (e.g., in Figure 5AD).

[0262] Figure 5AE also shows user input 5130 (for example, an upward swipe input starting from the bottom edge of the display of the horizontally oriented computer system 100). While displaying the user interface 5118, the computer system 100 detects the user input 5130.

[0263] In some embodiments, since user input 5130 starts from the bottom edge of the computer system 100 (as opposed to starting from an edge region such as a similar input 5120 in Figure 5AA), in response to detecting user input 5130, the computer system 100 displays a wake user interface (e.g., the same wake user interface as in Figures 5G and / or 5H, but with the current time being 9:05 instead of 9:00), as shown in Figures 5AF and 5AG. In some embodiments, the active timer of the computer system 100 continues execution (e.g., because the user did not activate the stop affordance for the active timer).

[0264] In some embodiments, the computer system 100 does not display the wake user interface and, in response to detecting user input 5130, maintains the display of the user interface 5118. In some embodiments, the computer system 100 redisplays the clock user interface 5058 (for example, instead of displaying the wake user interface) in response to detecting user input 5130. In some embodiments, the computer system 100 displays the wake user interface (for example, the home screen user interface) only when it detects that certain criteria are no longer met (for example, as described later with reference to Figures 5AH to 5AK) (for example, the computer system 100 remains in ambient mode and does not display the wake user interface or home screen user interface while certain criteria continue to be met).

[0265] Figure 5AF shows a horizontally oriented wake user interface. Because the active timer of the computer system 100 is still running (for example, the user has not interacted with the stop affordance for the active timer in the user interface 5118), the computer system 100 also displays an indicator corresponding to the active timer, which is overlaid on the horizontally oriented wake user interface (for example, an indicator similar to indicator 5112 in Figure 5Y, but a horizontally oriented indicator).

[0266] Figure 5AG is an alternative example of Figure 5AF, showing a vertically oriented wake user interface. Since the active timer is still running on the computer system 100, the computer system 100 displays an indicator 5112 (for example, the same indicator 5112 shown in Figure 5Y) overlaid on the wake user interface.

[0267] Figures 5AH to 5AK illustrate an exemplary method for exiting the ambient mode of computer system 100. In Figure 5AH, computer system 100 displays a clock user interface 5058 for the time or clock ambient mode of computer system 100. The user begins to rotate the display of computer system 100 from landscape orientation to portrait orientation. The dotted outline in Figure 5AH indicates the original landscape orientation of the display of computer system 100 as a reference for the amount of rotation of computer system 100. While the amount of rotation of computer system 100 (e.g., an angle) is below a threshold amount (e.g., the same or similar threshold amount used by computer system 100 to determine whether to display content in portrait or landscape orientation), computer system 100 maintains the display of the clock user interface 5058 and remains in ambient mode. This prevents the computer system 100 from accidentally exiting ambient mode (for example, if the computer system 100 and / or the surface on which the computer system 100 is placed is slightly bumped or moved).

[0268] In Figure 5AI, the computer system 100 has been rotated beyond a threshold amount, and the computer system 100 exits ambient mode and displays a replacement user interface (e.g., a wake user interface). The dotted outline indicates the previous orientation of the computer system 100's display in Figure 5AH (e.g., with a slight rotation below the threshold amount). In some embodiments, the computer system 100 exits ambient mode when the charging source 5056 is disconnected from the computer system 100 (e.g., regardless of the orientation of the computer system 100's display). In some embodiments, the computer system 100 exits ambient mode in response to detecting a user input 5132 (e.g., a tap user input) directed towards a portion of the clock user interface 5058 (e.g., a predetermined area of ​​the clock user interface 5058) (e.g., regardless of the orientation of the computer system 100's display and whether the computer system 100 is connected to the charging source 5056).

[0269] In some embodiments, the replacement user interface is the user interface displayed before the computer system 100 operates in ambient mode. For example, Figures 5G to 5L show various states of the computer system 100 before it enters ambient mode (for example, because the criteria for entering ambient mode were not met). In these states, the computer system 100 displays its wake user interface. In Figure 5AI, the replacement user interface is the same wake user interface displayed in Figures 5G to 5L.

[0270] In some embodiments, the computer system 100 displays an animated transition from the display of the clock user interface 5058 to the display of the replacement user interface shown in Figure 5AI. In some embodiments, the animated transition progresses according to the amount of rotation of the computer system 100. For example, the animated transition begins when the computer system 100 has rotated by a first amount (e.g., more than the amount in Figure 5AH but less than the amount in Figure 5AI) and ends when the computer system 100 has rotated by a threshold amount (e.g., the amount in Figure 5AI). While the computer system 100 is rotating, the animated transition reflects the amount of rotation between the first amount and the threshold amount (for example, when the display of the computer system 100 is rotated to an orientation intermediate between the first amount and the threshold amount, the animated transition has progressed to the midpoint). In some embodiments, the animated transition is reversible, and as a result, while the animated transition is progressing, the user can reverse the direction of rotation of the computer system 100 to reverse the animated transition. In some embodiments, the animated transition is displayed only after the computer system 100 has been rotated by a threshold amount (for example, a small rotation does not result in the display of the animated transition).

[0271] Figure 5AJ is similar to Figure 5AH, but the computer system 100 is displaying the home control user interface 5086. Because the computer system 100 is not rotated beyond a threshold amount, the computer system 100 operates in ambient mode and displays the home control user interface 5086.

[0272] In Figure 5AK, the computer system 100 is rotating beyond a threshold amount. The computer system 100 exits ambient mode and displays a replacement user interface. In some embodiments, the replacement user interface in Figure 5AK is the same as the replacement user interface in Figure 5AI (for example, the computer system 100 displays the same wake-screen user interface when it exits ambient mode, regardless of which user interface was displayed while the computer system 100 was in ambient mode). In some embodiments, the computer system 100 exits ambient mode in response to detecting a user input 5134 (e.g., a tap user input) directed towards a portion of the home control user interface 5086 (e.g., a predetermined area of ​​the home control user interface 5086) (e.g., regardless of the orientation of the computer system 100's display and whether the computer system 100 is connected to a charging source 5056).

[0273] In some embodiments, the replacement user interface in Figure 5AK is instead a different replacement user interface from the replacement user interface in Figure 5AI (for example, computer system 100 displays different replacement user interfaces depending on which user interface and / or category of user interface was displayed before exiting ambient mode).

[0274] In some embodiments, the computer system 100 displays an animated transition from the display of the home control user interface 5086 to the display of the replacement user interface in Figure 5AK, similar to the animated transitions described above with reference to Figures 5AH and 5AI.

[0275] As disclosed herein, in some embodiments, the computer system 100 performs personalization and / or customization of the user interface displayed based on the context surrounding the display of the user interface. In some embodiments, the computer system determines the context based on an identifier associated with a charging source currently coupled to the computer system. In some embodiments, if the identifier is uniquely associated with a charging source, the computer system records the identifier and stores personalization and / or customization parameters in relation to the unique identifier of the charging source, so that when the charging source is later recoupled to the computer system, the computer system recognizes that the identifier of the charging source matches a stored identifier of a previously encountered charging source, and can personalize and customize the user experience based on the personalization and / or customization parameters stored in relation to the unique identifier of the charging source. In this disclosure, a wireless or wired charging source coupled to the computer system transmits a transmitter identification data packet to the computer system, for example, via one or more power transmission signals or via one or more signals not used to charge or power the computer system (e.g., one or more Bluetooth signals, NFC signals, or signals of other communication protocols). In some embodiments, the transmitter identification data packet encodes an identifier for the charging source and optionally includes an indicator indicating whether the identifier is unique to the charging source. In some embodiments, the identifier and the optional indicator are encoded within the payload of the transmitter identification data packet, and the transmitter identification data packet further includes a header specifying the nature of the data packet as a transmitter identification data packet. In some embodiments, the charging source transmits the transmitter identification data packet in response to a request from a computer system.Further details regarding the interaction between the charging source and the computer system, the format of the data packets, and / or how the information contained in the data packets is utilized by the computer system and the charging source are provided below, for example, in Figures 5AN to 5AR and 17A to 17C, as well as other figures and descriptions contained herein.

[0276] Figure 5AN shows a simplified block diagram of a wireless power transmission system 5101 according to several embodiments. The wireless power transmission system 5101 includes a power transmitter (PTx) 5174 that wirelessly transmits power to a power receiver (PRx) 5184 via an inductive coupling 5194. The power transmitter 5174 is adapted to receive input power which is converted by an inverter 5178 to an AC voltage having specific voltage and frequency characteristics. The inverter 5178 is adapted to be controlled by a controller / communication module 5180 which operates as will be further described below. In various embodiments, the inverter, controller and communication module may be implemented within a common system such as a system based on a microprocessor, microcontroller, or equivalent. In some embodiments, the inverter controller may be implemented by a separate controller module and communication module having means of communication between them. The inverter 5178 may be constructed using any suitable circuit topology (e.g., full bridge, half bridge, etc.) according to various embodiments, and may be implemented using any suitable semiconductor switching device technology (e.g., MOSFETs, IGBTs, etc., fabricated using silicon, silicon carbide, or gallium nitride devices).

[0277] In some embodiments, the inverter 5178 is adapted to supply the generated AC voltage to the transmitter coil 5176 of the power transmitter 5174. In addition to the wireless coil that enables magnetic coupling to the receiver, the transmitter coil block 5176 shown in Figure 5AN may include tuning circuits such as additional inductors and capacitors to facilitate the operation of the transmitter under different conditions, such as different degrees of magnetic coupling to the receiver and / or different operating frequencies. The wireless coil itself can be constructed in various different ways according to various embodiments. In some embodiments, the wireless coil is formed as a winding of wire around a suitable bobbin. In some embodiments, the wireless coil is formed as a trace on a printed circuit board. Other arrangements are also possible and can be used in conjunction with the various embodiments described herein. The wireless power transmission coil 5176 may also include a core of a permeable material (e.g., ferrite) configured to influence the magnetic flux pattern of the coil in a manner suitable for a particular application. The teachings herein can be applied in conjunction with any of the wide variety of power transmission coil arrangements suitable for a given application, according to various embodiments.

[0278] In some embodiments, the PTx controller / communication module 5180 is configured to monitor the transmitter coil 51786 and use the information derived therefrom to control the inverter 5178 as appropriate for a given situation. For example, in some embodiments, the controller / communication module 5180 is configured to operate the inverter 5178 at a given frequency or output voltage, depending on the specific application. In some embodiments, the controller / communication module 5180 is configured to receive information from the PRx 5184 and control the inverter 5178 accordingly. This information may be received via the transmitting coil (i.e., via in-band communication) or via a separate communication channel (e.g., out-of-band communication using NFC or Bluetooth). In the case of in-band communication, the controller / communication module 5180 is adapted, according to some embodiments, to detect and decode signals (such as voltage, frequency, or load fluctuations) imposed on the magnetic link by the PRx 5184 in order to receive information (including, but not limited to, requests for information such as a request for an identifier for the PTx 5174), and to instruct the inverter 5178 to modulate the supplied power by manipulating various parameters (such as voltage, frequency, or phase) in order to transmit information (including, but not limited to, a transmitter identification data packet including, for example, an identifier for the PTx and an indicator of whether the identifier is unique to the PTx). In some embodiments, the controller / communication module 5180 is configured to communicate data (including, but not limited to, a transmitter identification data packet) to the PRx 5184 using frequency shift keying (FSK) communication, in which the frequency of the inverter signal is modulated. In some embodiments, the controller / communication module 5180 is configured to detect amplitude shift keying (ASK) communications (including, but not limited to, requests for transmitter identification data packets) or load modulation-based communications from the PRx5184.In either case, the controller / communication module 5190 may be configured to manipulate the waveform observed on the Tx coil 5176 to change the current drawn at the receiver side in order to deliver information from the PRx 5184 to the PTx 5174. For out-of-band communication, according to various embodiments, an additional module, such as WiFi, Bluetooth, or other wireless link or any other suitable communication channel, may be provided to enable communication between the PTx 5174 and the PRx 5184.

[0279] As described above, the controller / communication module 5180 may be, for example, a single module on a single integrated circuit, or multiple modules / devices on different integrated circuits, or a combination of an integrated circuit having both analog and digital components and discrete circuits. The teachings herein are not limited to any particular arrangement of controller / communication circuit components.

[0280] In some embodiments, the PTx5174 optionally includes other systems and components, such as a Near Field Communication ("NFC") module 5182. In some embodiments, the NFC module 5182 is adapted to communicate with a corresponding module or radio frequency identification (RFID) tag in the PRx5184 via power transmission coils 5176 and 7186. In other embodiments, the NFC module 5182 is adapted to communicate with a corresponding module or tag using a separate physical channel 5196. In some embodiments, inductive power transmission is optionally paused while out-of-band communication (e.g., NFC communication or Bluetooth communication) is in progress to prevent interference with out-of-band communication.

[0281] As described above, according to some embodiments, the wireless power transmission system also includes a wireless power receiver (PRx) 5184. According to some embodiments, the wireless power receiver PTx 5184 includes a receiver coil 5186 adapted to be magnetically coupled (5194) to a transmitter coil 5176. Similar to the transmitter coil 5176 described above, the receiver coil block 5186 shown in Figure 5AN may include tuning circuits such as additional inductors and capacitors to facilitate the operation of the receiver under different conditions, such as different degrees of magnetic coupling to the transmitter and different operating frequencies. The wireless coil itself can be constructed in a variety of different ways. In some embodiments, the wireless coil may be formed as a winding of wire wound on a suitable bobbin. In some embodiments, the wireless coil may be formed as a trace on a printed circuit board. Other arrangements are also possible and can be used in conjunction with the various embodiments described herein. The wireless receiver coil may also, according to some embodiments, include a core of a permeable material (e.g., ferrite) configured to influence the magnetic flux pattern of the coil in a manner suitable for a particular application. The teachings herein can be applied in conjunction with any of the many different receiver coil configurations suitable for a given application.

[0282] In some embodiments, the receiver coil 5186 outputs an AC voltage induced within it by magnetic induction via the transmitter coil 5176. This output AC voltage can be supplied to a rectifier 5188 that provides DC output power to one or more loads associated with the PRx5184 (e.g., the battery of a computer system, and / or various components of a computer system that consume power to function). The rectifier 5188 can be controlled by a controller / communication module 5190 that operates as described further below. In various embodiments, the rectifier controller and communication module may be implemented in a common system such as a system based on a microprocessor, microcontroller, etc. In some embodiments, the rectifier controller may be realized by a separate controller module and communication module having means of communication between them. The rectifier 5188 may be constructed using any suitable circuit topology (e.g., full bridge, half bridge, etc.) and may be realized using any suitable semiconductor switching device technology (e.g., MOSFETs, IGBTs, etc., fabricated using silicon, silicon carbide, or gallium nitride devices).

[0283] In some embodiments, the PRx controller / communication module 5190 is configured to monitor the receiver coil 5186 and use the information derived therefrom to control the rectifier 5188 as appropriate for a given situation. For example, in some embodiments, the controller / communication module 5190 is configured to operate the rectifier 5188 to provide a given output voltage depending on the specific application. In some embodiments, the controller / communication module 5190 is configured to transmit information to the PTx 5174 in order to effectively control the power supplied to the receiver. This information may be transmitted via the transmission coil (i.e., in-band communication) or via a separate communication channel (not shown, i.e., out-of-band communication). In the case of in-band communication, the controller / communication module 5190 may transmit information to the PTx 5174 (including, for example, a request for a transmitter identification data packet containing the identifier of the PTx) by modulating the load current or other electrical parameters of the received power. In some embodiments, the controller / communication module 5190 is configured to detect and decode signals (such as voltage, frequency, or load fluctuations) imposed on the magnetic link by the PTx5174 in order to receive information from the PTx5174 (including, but not limited to, transmitter identification data packets). In some embodiments, the controller / communication module 5190 is configured to receive frequency-shift keying (FSK) communications, in which the frequency of the inverter signal is modulated to communicate data to the PRx5184. In some embodiments, the controller / communication module 5190 is configured to generate amplitude-shift keying (ASK) communications or load-modulation-based communications from the PRx5184. In any case, the controller / communication module 5190 may be configured to manipulate the waveform observed on the Tx coil 5176 to change the current drawn at the receiver side in order to deliver information from the PRx5184 to the PTx5174.For out-of-band communication, an additional module may be provided to enable communication between the PTx5174 and PRx5184, such as WiFi, Bluetooth, or another wireless link, or any other suitable communication channel.

[0284] As described above, the controller / communication module 5190 may, according to various embodiments, be, for example, a single module provided on a single integrated circuit, or multiple modules / devices provided on different integrated circuits, or a combination of an integrated circuit having both analog and digital components and discrete circuits. The teachings herein are not limited to any particular arrangement of controller / communication circuit components.

[0285] In some embodiments, PRx5184 optionally includes other systems and components, such as a Near Field Communication ("NFC") module 5192. In some embodiments, the NFC module 5192 is adapted to communicate with a corresponding module or radio frequency identification (RFID) tag in PTx5174 via a power transmission coil. In some embodiments, the NFC module 5192 is adapted to communicate with the corresponding module or tag using a separate physical channel 138. In some embodiments, inductive power transmission is interrupted when out-of-band communication is in progress to prevent interference with out-of-band communication on other channels.

[0286] Numerous modifications and improvements are possible to the wireless power transmission system 5101 described above, and the following teachings are applicable to any of such modifications and improvements. As described above, according to various embodiments, the PRx controller / communication module 5190 and the PTx controller / communication module 5174 are adapted to communicate with each other, identify each other, and negotiate power supply between them. This identification and negotiation process may be carried out with a standard-defined protocol, such as the protocol defined by the Wireless Power Consortium Qi standard, so that devices from different manufacturers can interoperate. Adherence to such standards provides the benefit of interoperability without sacrificing specialization. In other embodiments, the identification and negotiation process may be carried out with a proprietary protocol determined by the device manufacturer, which provides the benefit of improved flexibility and potentially extended performance, along with the disadvantage of loss of interoperability with devices that do not implement the proprietary protocol.

[0287] In some embodiments, the controller / communication module is configured to initiate a negotiation process according to a standard-defined protocol. During that negotiation process, one, the other, or both devices may identify themselves in a standard-compliant manner as supporting an extended capability set beyond the scope of the standard. If both devices are capable of operating according to this extended capability set, the devices may choose to operate according to the extended capability set. Otherwise, the devices may choose to operate with a standard-based capability set. In some embodiments, the extended capability set includes the ability to operate at different frequencies, at different power levels, or in other ways beyond those defined in existing standards. In some embodiments, the transmitted extensions include the ability to transmit / encode and receive / decode transmitter identification data packets, which include a header that identifies the data packet as a transmitter identification data packet structured according to a default structure, as shown, for example, in Figures 5AQ, 5AS, and 5AT, and include an indicator that the identifiers carried in the data packet payload are unique to the packet's sender (e.g., PTx, and optionally PRx), and the packet's sender identifier. In some embodiments, a receiving device of a transmitter identification data packet performs personalization and / or customization for one or more actions (e.g., displaying a user interface and / or responding to user input) based on a unique identifier contained in the data packet. In some embodiments, if one of the devices does not support the extension, the transmitter identification data packet is not transmitted or utilized for personalization and customization of the receiver's actions.

[0288] Figures 5AO–5AP illustrate an exemplary communication exchange 5103 between a wireless power receiver (PRx) 5184 and a wireless power transmitter (PTx) 5174 to enable the display of individual customizable user interfaces (for example, during standby mode as described herein, for example, in Figures 5A–5AM). In some embodiments, the communication exchange is performed via a communication protocol regime, which is a standards-based regime such as the Wireless Power Transmission Consortium Qi Charging Protocol. The various communication packets described can take any of several forms, using different packet structures, different modulation schemes for communicating packets, etc. The following description deals with the components of communication packets at a high level, but it will be understood that a particular protocol implementation may specify different or additional data that may be included in these packets as needed.

[0289] Referring to Figure 5AO, the exemplary negotiation process begins with PRx5184 transmitting a sequence of messages 5198–5202 to power transmitter 5174. This exchange may be triggered by PTx5174 detecting proximity of PRx5184. The exchange may be performed using in-band communication at a frequency specified by the standard. In some embodiments, this frequency may be approximately 100 kHz to approximately 250 kHz. In some embodiments, this frequency may be 128 kHz, 326 kHz, 360 kHz, 1.78 MHz, or another suitable frequency. In the illustrated example, the four messages 5198–5204 correspond to messages transmitted according to the Qi standard. However, in some embodiments, there may be more or fewer messages, which may conform to alternative standards or protocols.

[0290] In some embodiments, the first message 5198 is a SIG packet, i.e., a signal strength packet according to the Qi standard. In some embodiments, the second message 5200 is an ID packet, i.e., an identification packet according to the Qi standard. In some embodiments, the third message 5202 is a CFG packet, i.e., a configuration packet according to the Qi standard. In some embodiments, these three packets correspond to the "ping" and "configuration phases" according to the Qi standard. Details of these packets, including the information they contain, and their effects on the system are described in detail in the version of the Qi standard to which they relate and are therefore not repeated herein. It will be understood that different versions of the Qi standard may incorporate different versions of such packets, and later versions may combine, delete, or otherwise modify such packets. Therefore, the illustrated packets are provided here merely as examples of standard-compliant initialization, and other similar arrangements may be used. Upon receiving communication from PRx5184, PTx5174 transmits a response packet 5204 (ACK packet in Figure 5AO) acknowledging the communication from PRx5184, as in some embodiments. In embodiments utilizing in-band communication for transmitting packets such as SIG5198, ID5200, CFG5200, and ACK5204, it should be noted that such in-band communication (e.g., ASK, FSK) may be communicated between PRx5184 and PTx5174 using signals referred to herein as wireless power transmission signals.

[0291] Referring next to Figure 5AP, further communication between PRx5184 and PTx5174 is shown. In some embodiments, upon receiving an acknowledgment of communication from PTx5174 from PRx5184 (for example, upon receiving response packet 5204 in Figure AO), PRx5184 sends a further packet 5206 requesting PTx5174 to provide a unique ID, if any. This can take the form of a "GET" request in which PRx5184 requests PTx5174 to send its unique ID, if any. If available, PTx5174 sends an "EXT ID" packet 5208 containing its unique ID. The "EXT ID" packet may provide a unique identifier (e.g., a device identification (ID) number or another type of ID number) specific to PTx5174 (e.g., for authentication, security, and / or customization purposes). In some embodiments, the “EXT ID” packet 5208 may contain an identifier for the PTx5174 that is not unique to the PTx5174, and may include an indication that the identifier is not unique. In some embodiments, the sender identifier and indication are included in the payload of the “EXT ID” packet, and the header of the “EXT ID” packet specifies the type of “EXT ID” packet (e.g., as a transmitter identification data packet). In some embodiments, a device identifier is considered “unique” to a device if the identifier is unique to the device under a separate manufacturer code for the device manufacturer, and the same identifier may be reused by another manufacturer under a different manufacturer code. In some embodiments, a device identifier in a data packet includes a manufacturer code for the device manufacturer, followed by a device identifier assigned to the device by the manufacturer. In some embodiments, a device identifier is considered unique to a device if the identifier is unique to the device across all devices of the same group or type (e.g., all charging devices, all wireless charging devices, all wireless charging devices certified to a particular wireless charging specification, and / or other groups or types of devices).In some embodiments, a device identifier is considered unique to a device if the probability of a consumer purchasing two devices with the same identifier is sufficiently low, such as falling below a probability threshold. It should be understood that the level of uniqueness is driven by the bit length of the identifier payload. In other words, if 20 bits are used for the identifier field, the field will support 2^20, or approximately 1 million, unique identifiers.

[0292] In some embodiments, PRx5184 sends a further packet 5210 requesting PTx5174 to provide personalization information, if any. This can take the form of a "GET" request in which PRx5184 requests PTx5174 to send personalization information, if any. If available, PTx5174 sends a "UI Param" packet 5212 containing the personalization information. The "UI Param" packet 5212 may provide information specific to PTx5174 (e.g., unique) personalization and / or customization information (e.g., personalization and / or customization of user preferences, the user interface displayed, or other information regarding the customization and / or personalization of PRx5184 and / or PTx5174, and / or the user interface displayed by PRx5184 and / or PTx5174). In some embodiments, the information in the "UI Param" packet 5212 is contained within the "EXT ID" packet 5208 (for example, requests 5206 and 5210 are combined, and packets 5208 and 5212 are combined).

[0293] In some embodiments, PRx5184 does not request a unique ID and / or personalization informat...

Claims

1. It is a method, In a computer system that communicates with a display generation component and one or more sensors, Detecting the first event, In response to detecting the first event, As a result of the first event, display a first customizable user interface that was not displayed before the first event was detected, according to a determination that the first criterion is met, the first criterion requiring that, for the first criterion to be met, the orientation of the display generation component is a first orientation and the computer system is charging. A method comprising: discontinuing the display of the first customizable user interface in accordance with a determination that the first criterion is not met as a result of the first event.

2. The first event includes an event corresponding to at least one of the changes in the orientation of the display generation component and / or the changes in the charging state of the computer system, and the determination that the first criterion is not met as a result of the first event is: The orientation of the display generation component is not the first orientation, and the computer system is determined to be charging. The determination that the orientation of the display generation component is the first orientation and that the computer system is not charging, and / or The method according to claim 1, comprising one or more of the following: the orientation of the display generation component is not the first orientation, and the computer system is not charging.

3. The method according to claim 1 or 2, wherein detecting the first event includes detecting that the orientation of the display generating component is the first orientation and that a separate set of conditions for the computer system to transition to a restricted mode is met while the computer system is charging, the first criterion being met as a result of the first event.

4. The method according to claim 3, wherein the limiting mode includes a low-power mode.

5. The method according to claim 3 or 4, wherein the restriction mode includes a lock mode.

6. The method according to any one of claims 1 to 5, wherein detecting the first event includes detecting that the orientation of the display generating component is the first orientation and that the computer system is charging as a result of the first event while the computer system is operating in restricted mode.

7. The method according to any one of claims 1 to 6, wherein the determination that the first criterion is not met as a result of the first event includes the determination that the computer system was inside the vehicle when the first event occurred.

8. The method according to any one of claims 1 to 7, wherein the determination that the first criterion is not met as a result of the first event includes the determination that the computer system moved beyond a threshold amount within a unit time when the first event occurred.

9. The method according to any one of claims 1 to 8, wherein the determination that the first criterion is not met as a result of the first event includes the determination that the computer system is communicating with the vehicle.

10. Displaying the customizable user interface described in the first example means Displaying the first customizable user interface containing the first content, in accordance with the determination that the first criterion is met as a result of the first event and that the first set of contextual conditions is met, The method according to any one of claims 1 to 9, comprising displaying the first customizable user interface, which includes second content different from the first content, in accordance with the determination that the first criterion is met as a result of the first event and that a second set of contextual conditions different from the first set of contextual conditions is met.

11. The method according to claim 10, wherein the first set of contextual conditions includes a first condition that the computer system is being charged via a first charging source, and the second set of contextual conditions includes a second condition that the computer system is being charged via a second charging source different from the first charging source.

12. Receiving one or more power transmission signals from a charging source, Obtaining a unique identifier of the charging source from at least one of the one or more power transmission signals received from the charging source, The method according to claim 11, further comprising determining, before displaying the first customizable user interface, whether the individual identifiers of the charging sources obtained from the one or more power transmission signals correspond to a first identifier of the first charging source or a second identifier of the second charging source.

13. Determining whether the individual identifiers of the charging sources obtained from one or more power transmission signals correspond to the first identifier of the first charging source or the second identifier of the second charging source is: The method according to claim 12, comprising determining whether the one or more power transmission signals include an indication of whether the individual identifier of the charging source obtained from the one or more power transmission signals is a unique identifier of the charging source, wherein the first customizable user interface is displayed according to the determination that the indication specifies that the individual identifier is a unique identifier of the charging source and that the individual identifier corresponds to the first identifier of the first charging source.

14. Obtaining the individual identifier of the charging source from one or more power transmission signals received from the charging source is: The method according to claim 12 or 13, comprising decoding the individual identifier of the charging source from one or more power transmission signals received from the charging source, wherein the one or more power transmission signals are used to charge the battery of the computer system.

15. The method according to claim 12 or 13, comprising decoding the individual identifier of the charging source from one or more signals received from the charging source, wherein the one or more signals are not used to charge the battery of the computer system.

16. The method according to any one of claims 12 to 15, comprising encoding a request for the individual identifier of the charging source in a first power transmission signal transmitted between the charging source and the computer system while the computer system is coupled to the charging source, wherein the charging source encodes the individual identifier in one or more power transmission signals in response to detecting the request encoded in the first power transmission signal.

17. The method according to any one of claims 12 to 16, wherein at least one of the one or more power transmission signals received from the charging source encodes a header and a payload, the header indicating that the payload includes the individual identifier of the charging source.

18. The method according to claim 17, wherein obtaining the individual identifier of the charging source from one or more power transmission signals received from the charging source includes obtaining the individual identifier of the charging source from a second portion of the payload following a first portion of the payload.

19. While displaying the first customizable user interface that was not displayed before the detection of the first event, one or more user inputs constituting one or more aspects of the first customizable user interface are detected. The method according to any one of claims 12 to 18, comprising: updating a first set of customization parameters stored in the computer system in relation to the individual identifiers, and / or establishing and storing a second set of second customization parameters for the first customizable user interface in relation to the individual identifiers, in response to detecting one or more user inputs constituting one or more aspects of the first customizable user interface.

20. After updating the first set of customization parameters for the first customizable user interface and / or establishing and storing the second set of customization parameters in relation to the individual identifiers obtained from the one or more power transmission signals, the computer system detects that it has been disconnected from the charging source and discontinues displaying the first customizable user interface configured according to the one or more user inputs, The computer system detects that it has been disconnected from the charging source and, after ceasing to display the first customizable user interface configured according to one or more user inputs, detects a subsequent event, wherein the first criterion is met as a result of the subsequent event. The method of claim 19, comprising: detecting the subsequent event, and determining that the computer system is coupled to an individual charging source and that an identifier encoded in one or more power transmission signals received from the individual charging source matches the individual identifier of the charging source, redisplaying the first customizable user interface according to the first set of customization parameters stored in relation to the individual identifier of the charging source and / or a second set of customization parameters.

21. The method according to any one of claims 10 to 20, wherein the first set of context conditions includes a third condition that the computer system is located at a first location, and the second set of context conditions includes a fourth condition that the computer system is located at a second location different from the first location.

22. The method according to any one of claims 10 to 21, wherein the first set of contextual conditions includes a fifth condition that the current time is within a first time range, and the second set of contextual conditions includes a sixth condition that the current time is within a second time range different from the first time range.

23. The method according to any one of claims 10 to 22, wherein the first content comprises a first set of widgets, and the second content comprises a second set of widgets different from the first set of widgets.

24. The method according to any one of claims 10 to 23, wherein the first content includes a first type of content, and the second content includes a second type of content different from the first type of content.

25. The method according to any one of claims 10 to 24, wherein the first set of context conditions includes a seventh condition that the computer system is operating in a first mode in which alert generation is mitigated in the computer system in a first manner, and the second set of context conditions includes an eighth condition that the computer system is operating in a second mode in which alert generation is mitigated in the computer system in a second manner different from the first manner.

26. While the first customizable user interface is displayed, the first user input is detected, The method according to any one of claims 1 to 25, comprising detecting the first user input and ceasing to display the first customizable user interface in accordance with the determination that the first user input meets rejection criteria.

27. The method according to claim 26, wherein the rejection criteria are met according to the determination that the first user input is a tap input.

28. In response to detecting the first user input, In accordance with the determination that the first user input satisfies the rejection criteria and that the first user input is directed to the first part of the display generation component, the display of the first customizable user interface is replaced with the first replacement user interface, The method according to claim 27, comprising replacing the display of the first customizable user interface with a second replacement user interface different from the first replacement user interface, in accordance with the determination that the first user input satisfies the rejection criteria and the first user input is directed to a second part of the display generation component different from the first part.

29. In response to detecting the first user input, The method according to claim 27 or 28, comprising performing a first action without discontinuing the display of the first customizable user interface, in accordance with the determination that the first user input does not meet the rejection criteria and that the first user input is directed to a third part of the display generation component.

30. The method according to any one of claims 26 to 29, wherein the rejection criteria are met in accordance with the determination that the first user input changes the orientation of the computer system.

31. In response to the detection of the first user input, and in accordance with the determination that the first user input satisfies the rejection criteria, In accordance with the determination that the first customizable user interface has been displayed containing a first type of content, the display of the first customizable user interface is replaced with the first replacement user interface. The method according to any one of claims 26 to 30, comprising replacing the display of the first customizable user interface with a second replacement user interface different from the first replacement user interface, in accordance with the determination that the first customizable user interface has been displayed containing a second type of content different from the first type of content.

32. The method according to any one of claims 26 to 30, comprising detecting the first user input and, in accordance with the determination that the first user input satisfies the rejection criteria, displaying an animated transition from the first customizable user interface to an individual replacement user interface in accordance with the first user input.

33. The method according to claim 32, wherein displaying the animated transition in accordance with the first user input includes controlling the progress of the animated transition in accordance with the progress of the first user input.

34. While the first customizable user interface is displayed, a second user input is detected via one or more sensors of the computer system. The method according to any one of claims 1 to 33, comprising detecting the second user input and, in accordance with the determination that the second user input satisfies the content switching criteria, switching the content displayed in the first customizable user interface from a first type of content to a second type of content different from the first type of content.

35. While the first customizable user interface is displayed, the occurrence of a second event is detected, In response to detecting the second event, The method according to any one of claims 1 to 34, comprising: discontinuing the display of the first customizable user interface and redisplaying the previous user interface that was displayed when the first event was detected, regardless of which of the multiple different contents of the first customizable user interface was displayed when the second event was detected, in accordance with the determination that the first criterion is no longer met.

36. The method according to any one of claims 1 to 35, comprising displaying a battery indicator to indicate that the computer system is charging, in accordance with a determination that the computer system is charging.

37. Displaying the battery indicator to indicate that the computer system is charging is, In accordance with the determination that the first criterion is met and the first customizable user interface is displayed, the battery indicator is displayed in a first appearance, The method according to claim 36, further comprising displaying the battery indicator in a second appearance different from the first appearance, in accordance with the determination that the first criterion is not met and the first customizable user interface is not displayed.

38. While the computer system is displaying the battery indicator to indicate that it is charging, a third user input directed to the location corresponding to the battery indicator is detected. The method according to claim 36 or 37, further comprising: detecting the third user input, and expanding the battery indicator to display additional charging information that was not displayed on the battery indicator at the time the third user input was detected.

39. In response to detecting the first event, The method according to any one of claims 1 to 38, comprising displaying the individual user interface object of the first type in an updated appearance, according to the determination that, as a result of the first event, the first criterion is met and the computer system detects the first event, the individual user interface object of the first type was displaying an individual user interface object of the first type which corresponds to an individual application and displays status information that is updated over time without requiring the display of the individual application.

40. The method according to claim 39, wherein the individual user interface object having the updated appearance is a full-screen user interface object.

41. Before detecting the first event, the third event is detected, In response to detecting the third event, The method according to any one of claims 1 to 40, further comprising displaying a description of the first customizable user interface in accordance with the determination that the first criterion is met as a result of the third event and that the first customizable user interface has not been previously displayed in the computer system.

42. Displaying a first configuration user interface for configuring the first customizable user interface described above, While displaying the first configuration user interface for configuring the first customizable user interface, one or more user inputs corresponding to a request to change one or more configurable aspects of the first customizable user interface are detected. The method according to any one of claims 1 to 41, comprising updating the one or more configurable modes of the first customizable user interface in accordance with the one or more user inputs in response to detecting the one or more user inputs corresponding to a request to change one or more configurable modes of the first customizable user interface.

43. The method according to claim 42, wherein the first configuration user interface for configuring the first customizable user interface includes a first option for enabling or disabling the display of the first customizable user interface.

44. The method according to claim 42 or 43, wherein the first configuration user interface for configuring the first customizable user interface includes a second option for enabling or disabling a dimming always-on mode for the first customizable user interface, and in accordance with the determination that the dimming always-on mode is enabled for the first customizable user interface, at least a plurality of user interface elements of the first customizable user interface remain displayed with reduced visual prominence while the computer system is in a reduced power mode.

45. The method according to any one of claims 42 to 44, wherein the first configuration user interface for configuring the first customizable user interface includes a third option for enabling or disabling a night mode for the first customizable user interface, and in accordance with the determination that the night mode is enabled for the first customizable user interface, at least a plurality of user interface elements of the first customizable user interface are displayed in a different appearance compared to the default appearance of the first customizable user interface while the computer system is in the night mode.

46. The method according to any one of claims 42 to 45, wherein the first configuration user interface for configuring the first customizable user interface includes a fourth option for enabling or disabling the display of notification alerts while the first customizable user interface is displayed, and in accordance with the determination that the display of notification alerts is enabled, a notification indicator for one or more newly received notifications is displayed while the first customizable user interface is displayed.

47. The method according to any one of claims 42 to 46, wherein the first configuration user interface for configuring the first customizable user interface includes a fifth option for enabling or disabling the wake of the computer system in response to the detection of vibration of the computer system.

48. A computer system that communicates with a display generation component and one or more sensors, wherein the computer system is One or more processors, A memory that stores one or more programs, wherein the one or more programs are configured to be executed by the one or more processors, The first event is detected, In response to detecting the first event, As a result of the first event, a first customizable user interface that was not displayed before the first event was detected is displayed according to a determination that the first criterion is met, the first criterion requiring that the orientation of the display generation component is a first orientation and the computer system is charging, in order for the first criterion to be met. A computer system including an instruction to stop displaying the first customizable user interface in accordance with a determination that the first criterion is not met as a result of the first event.

49. A computer-readable storage medium for storing one or more programs, wherein when the one or more programs are executed by a computer system communicating with a display generation component and one or more sensors, the computer system... To detect the first event, In response to detecting the first event, As a result of the first event, a first customizable user interface that was not displayed before the first event was detected is displayed according to a determination that the first criterion is met, the first criterion requiring that, for the first criterion to be met, the orientation of the display generation component is a first orientation and the computer system is charging. A computer-readable storage medium including instructions that cause the first customizable user interface to be discontinued in accordance with a determination that the first criterion is not met as a result of the first event.

50. A computer system that communicates with a display generation component and one or more sensors, wherein the computer system is A means for detecting the first event, A means that is activated in response to the detection of the first event, As a result of the first event, means for displaying a first customizable user interface that was not displayed before the first event was detected, which is activated according to a determination that the first criterion is met, the first criterion requiring that the orientation of the display generation component is a first orientation and the computer system is charging, A computer system comprising means for deactivating the display of the first customizable user interface, which is activated in accordance with a determination that the first criterion is not met as a result of the first event.

51. An information processing device for use in a computer system that communicates with a display generation component and one or more sensors, wherein the information processing device is A means for detecting the first event, A means that is activated in response to the detection of the first event, As a result of the first event, means for displaying a first customizable user interface that was not displayed before the first event was detected, which is activated according to a determination that the first criterion is met, the first criterion requiring that the orientation of the display generation component is a first orientation and the computer system is charging, Information processing apparatus comprising means for deactivating the display of the first customizable user interface, which is activated in accordance with a determination that the first criterion is not met as a result of the first event.

52. A computer system that communicates with a display generation component and one or more sensors, wherein the computer system is One or more processors, A computer system comprising: a memory for storing one or more programs, wherein the one or more programs are configured to be executed by the one or more processors, and the one or more programs include instructions for performing the method according to any one of claims 1 to 47.

53. A computer-readable storage medium for storing one or more programs, wherein the one or more programs, when executed by a computer system communicating with a display generation component and one or more sensors, include instructions causing the computer system to perform the method according to any one of claims 1 to 47.

54. A graphical user interface on a computer system communicating with a display generation component and one or more sensors, wherein the computer system includes a memory and one or more processors for executing one or more programs stored in the memory, and the graphical user interface includes a user interface displayed according to the method of any one of claims 1 to 47.

55. A computer system that communicates with a display generation component and one or more sensors, wherein the computer system is A computer system comprising means for performing the method described in any one of claims 1 to 47.

56. An information processing device for use in a computer system that communicates with a display generation component and one or more sensors, wherein the information processing device is An information processing apparatus comprising means for performing the method described in any one of claims 1 to 47.

57. It is a method, In a computer system that communicates with a display generation component and one or more input devices, The display generation component enables the display of a first user interface selected from a first set of user interfaces, wherein the first user interface displays a first type of content according to a first set of configuration options. While the first user interface is displayed, a first user input directed to the first user interface is detected, In response to detecting the first user input directed to the first user interface, The first user interface display is replaced with a second user interface display, which is selected from the first set of user interfaces and displays a second type of content different from the first type of content, according to a determination that the first user input satisfies a first direction criterion, wherein the first user input includes movement in a first direction for the first direction criterion to be satisfied. The first user interface display is replaced with a display of the first type of content according to a second set of configuration options different from the first set of configuration options, in accordance with a determination that the first user input satisfies a second direction criterion, the second direction criterion requiring that the first user input include movement in a second direction different from the first direction, for the second direction criterion to be satisfied. After detecting the first user input, while displaying an individual user interface from the first set of user interfaces, a second user input directed to the individual user interface is detected. In response to detecting the second user input, A method comprising replacing the display of the individual user interface with a display of a third user interface, selected from the first set of user interfaces, the third user interface, which displays a third type of content different from the first type of content and the second type of content, in accordance with a determination that the second user input satisfies the first direction criterion, the first direction criterion requires that the second user input includes movement in the first direction for the first direction criterion to be satisfied.

58. The method according to claim 57, wherein the first user interface selected from the first set of user interfaces is displayed in accordance with the determination that the first criterion is met.

59. Detecting a first event while displaying an individual user interface of the first set of user interfaces, In response to detecting the first event, The method according to claim 57 or 58, further comprising: discontinuing the display of the individual user interfaces of the first set of user interfaces and redisplaying a system user interface corresponding to a restricted state of the computer system, in accordance with a determination that the first criterion is no longer met as a result of the first event;

60. In response to detecting the second user input, The method according to any one of claims 57 to 59, wherein the second user interface is currently displayed as the individual user interface as a result of the first user input, and the method includes replacing the display of the second user interface with the display of the first user interface in accordance with a determination that the second user input satisfies a third directional criterion, the third directional criterion requiring that the second user input include movement in a third direction different from the first and second directions in order that the third directional criterion is satisfied.

61. After detecting the second user input, while displaying the individual user interfaces of the first set of user interfaces, a third user input directed to the individual user interface of the first set of user interfaces is detected. In response to detecting the third user input, The method according to any one of claims 57 to 60, wherein the third user input is the first directional criterion, the first directional criterion is the determination that the first directional criterion is satisfied, the third user input includes movement in the first direction, the third directional input includes movement in the first direction, the third directional criterion is the determination that the first directional criterion is satisfied, and the fourth user interface is the fourth user interface which displays a fourth type of content different from the first type of content, the second type of content, and the third type of content.

62. The method according to any one of claims 57 to 61, wherein the first set of user interfaces includes a widget user interface that displays a set of widgets corresponding to different applications.

63. The method according to any one of claims 57 to 62, wherein the first set of user interfaces includes a media display user interface for displaying one or more categories of visual media.

64. Detecting a fourth user input while displaying the media display user interface of the first set of user interfaces for displaying visual media from the first category, In response to detecting the fourth user input, The method according to claim 63, further comprising updating the display of the media display user interface to display visual media from a second category different from the first category, in accordance with the determination that the fourth user input satisfies the second directional criterion.

65. While displaying the media display user interface that displays visual media of one or more categories, additional content is displayed to overlay on the currently displayed visual media selected from the individual categories of the one or more categories. While displaying the additional content that overlays the currently displayed visual media, a fifth user input directed to the first portion of the currently displayed visual media is detected. The method according to claim 63 or 64, comprising detecting a fifth user input directed to the first portion of the currently displayed visual media, and ceasing to display the additional content while maintaining the display of the currently displayed visual media.

66. While displaying the media display user interface which displays visual media of one or more categories, a sixth user input directed to a second portion of the currently displayed visual media is detected. In response to detecting the sixth user input for the second portion of the currently displayed visual media, In accordance with the determination that the currently displayed visual media is selected from a first category among the one or more categories, another visual media from the first category is displayed as the currently displayed visual media. The method according to any one of claims 63 to 65, wherein, in accordance with the determination that the currently displayed visual media has been selected from a second category different from the first category, another visual media from the second category is displayed as the currently displayed visual media.

67. While displaying the media display user interface that displays visual media of one or more categories, a seventh user input directed to a third portion of the currently displayed visual media is detected. The method according to any one of claims 63 to 66, comprising detecting the seventh user input directed to the third portion of the currently displayed visual media, and displaying one or more options for sharing the currently displayed visual media.

68. The method according to any one of claims 57 to 67, wherein the first set of user interfaces includes a time user interface that displays an indication of the current time.

69. The aforementioned time user interface includes one or more interaction regions, and the method is While displaying the time user interface, which includes one or more interaction regions and the indication of the current time, the detection of an eighth user input directed to the time user interface, The method of claim 68, comprising detecting the eighth user input and, in accordance with the eighth user input, displaying additional time content that was not previously displayed, or changing the way in which the current time is displayed within the time user interface.

70. In response to detecting the eighth user input, and in accordance with the determination that the eighth user input satisfies the feedback criteria, visual or audio feedback is provided within the time user interface in accordance with the eighth user input. While the eighth user input is continuously detected, the visual or audio feedback is maintained, To detect the end of the eighth user input, The method according to claim 69, comprising: detecting the end of the eighth user input; ceasing to provide the visual or audio feedback within the time user interface; and restoring the display of the indication for the current time within the time user interface.

71. In a first time period, a first appearance, the first appearance being configured according to a third set of configuration options for the time user interface, displays the time user interface including the indication of the current time. The method according to any one of claims 68 to 70, comprising: updating the display of the time user interface to include the indication of the current time having a second appearance different from the first appearance, wherein the second appearance is configured according to a fourth set of configuration options for the time user interface, different from the third set of configuration options, in a second time following the first time, in accordance with a determination that the second time satisfies a scheduled update criterion.

72. The method according to any one of claims 68 to 71, wherein in a first scenario, the first version of the first user interface displayed upon receipt of the first user input is a first version of the time user interface having a first set of features, and in a first scenario, the second version of the first user interface displayed in response to the first user input satisfying the second directional criterion is a second version of the time user interface having a second set of features different from the first set of features.

73. The method according to any one of claims 68 to 72, wherein the time user interface displayed with a separate set of features includes an indication of the current time for one or more contacts of the user of the computer system.

74. The method according to any one of claims 57 to 73, wherein the first set of user interfaces includes a dictation user interface that displays controls for generating an audio recording.

75. The method according to any one of claims 57 to 74, wherein the first set of user interfaces includes a time user interface that displays an indication of the current time with reduced visibility while the computer system is operating in a first mode.

76. The method according to any one of claims 57 to 75, wherein the first set of user interfaces includes an ambient sound user interface that displays visual content in connection with outputting ambient sound content.

77. The method according to claim 76, in a second scenario in which the first version of the first user interface displayed upon receipt of the first user input is the first version of the ambient sound user interface with output of a first ambient sound, the second version of the first user interface displayed in response to the first user input satisfying the second directional criterion is the second version of the ambient sound user interface with output of a second ambient sound different from the first ambient sound.

78. The method according to claim 76 or 77, comprising changing the visual content displayed in the ambient sound user interface from a first type of visual content to a second type of visual content in accordance with the determination that the currently outputting ambient sound has changed from a first type of ambient sound to a second type of ambient sound.

79. The method according to any one of claims 76 to 78, wherein the first user input that satisfies the second directional criterion includes a swipe input in the second direction.

80. A separate configuration user interface for a separate user interface of the first set of user interfaces, wherein the separate configuration user interface for the separate user interface of the first set of user interfaces displays a separate configuration user interface that includes a plurality of configuration options for the separate user interface of the first set of user interfaces, Detecting one or more user inputs directed to the multiple configuration options within the individual configuration user interface, The method according to any one of claims 57 to 79, comprising detecting one or more user inputs directed to the plurality of configuration options, and, in accordance with a determination that the one or more user inputs satisfy editing criteria, modifying one or more aspects of the individual user interface so that at a future point in time when the individual user interface is displayed, the individual user interface is displayed in accordance with one or more modifications made in accordance with the one or more user inputs that satisfy the editing criteria.

81. The method according to claim 80, wherein the editing criteria are different from the first directional criteria and the second directional criteria.

82. The method according to claim 80 or 81, in a particular scenario in which the particular user interface on which the particular configuration user interface is displayed is a widget user interface that displays a set of widgets, the particular configuration user interface includes one or more options for configuring which widgets are included in the set of widgets for display in the widget user interface.

83. The method according to any one of claims 80 to 82, wherein in a particular scenario in which the particular user interface on which the particular configuration user interface is displayed is a media display user interface that displays visual media of one or more categories, the particular configuration user interface includes one or more options for configuring which categories of visual media are included in one or more categories of visual media for display within the media display user interface.

84. The method according to any one of claims 80 to 83, wherein in a particular scenario in which the particular user interface on which the particular configuration user interface is displayed is a media display user interface for displaying one or more categories of visual media, the particular configuration user interface includes an option for excluding one or more visual media from being included in one or more categories of visual media for display in the media display user interface.

85. A computer system that communicates with a display generation component and one or more input devices, wherein the computer system is One or more processors, A memory that stores one or more programs, wherein the one or more programs are configured to be executed by the one or more processors, The display generation component displays a first user interface selected from a first set of user interfaces, wherein the first user interface displays a first type of content according to a first set of configuration options. While the first user interface is displayed, a first user input directed to the first user interface is detected. In response to detecting the first user input directed to the first user interface, The first user interface display is replaced with a second user interface display, the second user interface display is selected from the first set of user interfaces and displays a second type of content different from the first type of content, in accordance with the determination that the first user input satisfies the first direction criterion, wherein the first user input includes movement in a first direction for the first direction criterion to be satisfied. The first user input is replaced with the display of the first type of content according to a second set of configuration options different from the first set of configuration options, in accordance with a determination that the second directional criterion is satisfied, wherein the first user input includes movement in a second direction different from the first direction, and the second directional criterion requires that the first user input includes movement in a second direction different from the first direction for the second directional criterion to be satisfied. After detecting the first user input, while displaying an individual user interface from the first set of user interfaces, a second user input directed to the individual user interface is detected. In response to detecting the second user input, A computer system including instructions to replace the display of the individual user interface with a display of a third user interface, selected from the first set of user interfaces, which displays a third type of content different from the first type of content and the second type of content, in accordance with a determination that the second user input satisfies the first direction criterion, the first direction criterion requires that the second user input includes movement in the first direction for the first direction criterion to be satisfied.

86. A computer-readable storage medium for storing one or more programs, wherein when the one or more programs are executed by a computer system communicating with a display generation component and one or more input devices, the computer system... The display generation component causes a first user interface selected from a first set of user interfaces, the first user interface to display a first type of content according to a first set of configuration options, While the first user interface is displayed, a first user input directed to the first user interface is detected. In response to detecting the first user input directed to the first user interface, The display of the first user interface is replaced with a display of a second user interface, the second user interface is selected from the first set of user interfaces and the second user interface displays a second type of content different from the first type of content. The first user input is replaced with a display of the first type of content according to a second set of configuration options different from the first set of configuration options, in accordance with a determination that the second directional criterion is satisfied, wherein the first user input includes movement in a second direction different from the first direction, and the second directional criterion requires that the first user input includes movement in a second direction different from the first direction for the second directional criterion to be satisfied. After detecting the first user input, while displaying an individual user interface from the first set of user interfaces, a second user input directed to the individual user interface is detected. In response to detecting the second user input, A computer-readable storage medium comprising instructions to cause the display of the individual user interface to be replaced by a display of a third user interface, selected from the first set of user interfaces, which displays a third type of content different from the first type of content and the second type of content, in accordance with a determination that the second user input satisfies the first direction criterion, the first direction criterion requires that the second user input includes movement in the first direction for the first direction criterion to be satisfied.

87. A computer system that communicates with a display generation component and one or more input devices, wherein the computer system is The means for displaying a first user interface, selected from a first set of user interfaces via the display generation component, wherein the first user interface displays a first type of content according to a first set of configuration options, Means for detecting a first user input directed to the first user interface, which is enabled while the first user interface is displayed, Means that are activated in response to the detection of the first user input directed to the first user interface, Means for replacing a display of a first user interface, which is activated according to a determination that the first direction criterion is satisfied, where the first user input is a first direction criterion, and the first direction criterion requires the first user input to include movement in a first direction in order for the first direction criterion to be satisfied, with a display of a second user interface, where the second user interface is selected from the first set of user interfaces, and the second user interface displays a second type of content different from the first type of content, Means for replacing the display of the first user interface with a display of the first type of content, according to a second set of configuration options different from the first set of configuration options, wherein the first user input is activated according to a determination that the second direction criterion is satisfied, the second direction criterion requires that the first user input includes movement in a second direction different from the first direction for the second direction criterion to be satisfied. Means for detecting a second user input directed to the individual user interface, which is enabled while displaying the individual user interface from the first set of user interfaces after detecting the first user input, A means that is activated in response to the detection of the second user input, A computer system comprising: means for replacing a display of an individual user interface, which is activated according to a determination that the first direction criterion is satisfied, wherein the second user input includes movement in the first direction, and which is enabled according to a determination that the first direction criterion is satisfied, with a third user interface selected from the first set of user interfaces, the third user interface displaying a third type of content different from the first type of content and the second type of content.

88. An information processing device for use in a computer system that communicates with a display generation component and one or more input devices, wherein the information processing device is The means for displaying a first user interface, selected from a first set of user interfaces via the display generation component, wherein the first user interface displays a first type of content according to a first set of configuration options, Means for detecting a first user input directed to the first user interface, which is enabled while the first user interface is displayed, Means that are activated in response to the detection of the first user input directed to the first user interface, Means for replacing a display of a first user interface, which is activated according to a determination that the first direction criterion is satisfied, where the first user input is a first direction criterion, and the first direction criterion requires the first user input to include movement in a first direction in order for the first direction criterion to be satisfied, with a display of a second user interface, where the second user interface is selected from the first set of user interfaces, and the second user interface displays a second type of content different from the first type of content, Means for replacing the display of the first user interface with a display of the first type of content, according to a second set of configuration options different from the first set of configuration options, wherein the first user input is activated according to a determination that the second direction criterion is satisfied, the second direction criterion requires that the first user input includes movement in a second direction different from the first direction for the second direction criterion to be satisfied. Means for detecting a second user input directed to the individual user interface, which is enabled while displaying the individual user interface from the first set of user interfaces after detecting the first user input, A means that is activated in response to the detection of the second user input, Information processing apparatus comprising: means for replacing a display of an individual user interface, which is activated according to a determination that the first direction criterion is satisfied, wherein the second user input includes movement in the first direction, and the second direction criterion requires that the second user input includes movement in the first direction in order that the first direction criterion is satisfied, with a display of a third user interface selected from the first set of user interfaces, the third user interface displaying a third type of content different from the first type of content and the second type of content.

89. A computer system that communicates with a display generation component and one or more input devices, wherein the computer system is One or more processors, A computer system comprising: a memory for storing one or more programs, wherein the one or more programs are configured to be executed by the one or more processors, and the one or more programs include instructions for performing the method according to any one of claims 57 to 84.

90. A computer-readable storage medium for storing one or more programs, wherein the one or more programs, when executed by a computer system communicating with a display generation component and one or more input devices, include instructions causing the computer system to perform the method according to any one of claims 57 to 84.

91. A graphical user interface on a computer system communicating with a display generation component and one or more input devices, wherein the computer system includes a memory and one or more processors for executing one or more programs stored in the memory, and the graphical user interface includes a user interface displayed according to the method of any one of claims 57 to 84.

92. A computer system that communicates with a display generation component and one or more input devices, wherein the computer system is A computer system comprising means for performing the method described in any one of claims 57 to 84.

93. An information processing device for use in a computer system that communicates with a display generation component and one or more input devices, wherein the information processing device is An information processing apparatus comprising means for performing the method described in any one of claims 57 to 84.

94. It is a method, In a computer system that communicates with a display generation component and one or more input devices, Displaying a first user interface corresponding to the restricted state of the computer system is: The first user interface includes displaying simultaneously a first placement location, the first widget of the first group of widgets in the first placement location, which is configured to accommodate individual widgets of a first group of widgets, and a second placement location, the second widget of the second group of widgets in the second placement location, which is configured to accommodate individual widgets of a second group of widgets. In the first user interface, while simultaneously displaying the first widget of the first group of widgets at the first placement location and the second widget of the second group of widgets at the second placement location, a first user input directed to the first user interface is detected. In response to detecting the first user input directed to the first user interface, The display of the first widget is replaced with a different widget from the first group of widgets at the first placement location, in accordance with the determination that the first user input is directed to the first placement location within the first user interface and that the first user input satisfies the first switching criterion. A method comprising: replacing the display of the second widget with a different widget from the second group of widgets in the second placement location, in accordance with the determination that the first user input is directed to the second placement location in the first user interface and the first user input satisfies the first switching criterion.

95. The method according to claim 94, wherein at least one widget of the first group of widgets is selected by the computer system to be included in the first group of widgets in accordance with the determination that the at least one widget of the first group of widgets is included in the home screen user interface of the computer system.

96. In response to detecting the first user input directed to the first user interface, In accordance with the determination that the first user input is directed to the first placement location within the first user interface and that the first user input satisfies a second switching criterion different from the first switching criterion, the display of the first widget is replaced with another different widget of the first group of widgets located at the first placement location. The method according to claim 94 or 95, comprising: replacing the display of the second widget with another different widget of the second group of widgets at the second placement location, in accordance with the determination that the first user input is directed to the second placement location in the first user interface and the first user input satisfies the second switching criterion.

97. In response to detecting the first user input directed to the first user interface, The method according to claim 94 or 95, comprising replacing the display of the first widget at the first placement location with another different widget from the first group of widgets, and replacing the display of the second widget at the second placement location with another different widget from the second group of widgets, in accordance with the determination that the first user input satisfies a third switching criterion different from the first switching criterion.

98. In the first user interface, while the individual widgets of the first group of widgets at the first placement location and the individual widgets of the second group of widgets at the second placement location are simultaneously displayed, a sequence of user inputs directed to the first user interface is detected via one or more sensors of the computer system. In response to detecting the sequence of user inputs directed to the first user interface, The sequence of user inputs is directed to the first placement location within the first user interface, and according to the determination that each input in the sequence of user inputs satisfies the first switching criterion, multiple different widgets within the first group of widgets are scrolled at the first placement location. The method according to any one of claims 94 to 97, comprising: directing the sequence of user inputs to the second placement location in the first user interface, and scrolling through different widgets within the second group of widgets at the second placement location in accordance with the determination that each input in the sequence of user inputs satisfies the first switching criterion.

99. In response to detecting the first user input, The method according to any one of claims 94 to 98, comprising replacing the display of the first widget and the second widget with the display of a different type of content for the first user interface, in accordance with the determination that the first user input satisfies a mode switching criterion.

100. In response to detecting the first user input directed to the first user interface, The first user input is directed to the first placement location within the first user interface, and the first editing user interface for the first placement location is displayed in accordance with the determination that the first user input satisfies the editing criteria. The method according to any one of claims 94 to 99, comprising: displaying a second editing user interface for a second placement location, which is different from the first editing user interface for the first placement location, in accordance with the determination that the first user input is directed to the second placement location in the first user interface and that the first user input satisfies the editing criteria.

101. The first editing user interface includes one or more controls for editing the first group of widgets, The method according to claim 100, wherein the second editing user interface includes one or more controls for editing the second group of widgets.

102. The first editing user interface includes one or more controls for editing the first widget, The method according to claim 100 or 101, wherein the second editing user interface includes one or more controls for editing the second widget.

103. The first editing user interface, when enabled, includes an option to the computer system to automatically cycle through widgets from the first group of widgets at the first placement location. The method according to any one of claims 100 to 102, wherein the second editing user interface, when enabled, includes an option for the computer system to automatically cycle widgets from the second group of widgets in the second placement location.

104. Displaying the first widget at the first placement location means In accordance with the determination that the authentication criteria are met in the computer system, the first widget having a first amount of widget content is displayed, The method according to any one of claims 94 to 103, comprising displaying the first widget having a second amount of widget content different from the first amount of widget content, in accordance with the determination that the authentication criteria are not met.

105. Within the first user interface, while simultaneously displaying individual widgets of the first group of widgets at the first placement location and individual widgets of the first group of widgets at the second placement location, the system detects user input corresponding to a request to edit the first user interface. The method according to any one of claims 94 to 104, comprising: detecting the user input corresponding to a request to edit the first user interface, and initiating a process for authenticating the user who provided the user input corresponding to the request to edit the first user interface.

106. In response to detecting the first user input directed to the first user interface, The method according to any one of claims 94 to 105, comprising initiating a process for authenticating the user who provided the first user input, in accordance with the determination that the first user input satisfies the first switching criterion, wherein replacing the display of the first widget or replacing the display of the second widget is performed after the completion of the process for authenticating the user who provided the first user input.

107. In response to detecting the first user input, the authentication includes authenticating the user who provided the first user input before replacing the display of the first widget or the second widget in the first user interface, and authenticating is: To detect the interaction between the user and the computer system, The method according to any one of claims 94 to 106, comprising: detecting the interaction between the user and the computer system, initiating a process for authenticating the user who has interacted with the computer system.

108. A computer system that communicates with a display generation component and one or more input devices, wherein the computer system is One or more processors, A memory that stores one or more programs, wherein the one or more programs are configured to be executed by the one or more processors, The display of the first user interface corresponding to the restricted state of the computer system is: The first user interface includes simultaneously displaying a first placement location, the first widget of the first group of widgets in the first placement location, which is configured to accommodate individual widgets of a first group of widgets, and a second placement location, the second widget of the second group of widgets in the second placement location, which is configured to accommodate individual widgets of a second group of widgets. In the first user interface, while simultaneously displaying the first widget of the first group of widgets at the first placement location and the second widget of the second group of widgets at the second placement location, a first user input directed to the first user interface is detected. In response to detecting the first user input directed to the first user interface, In accordance with the determination that the first user input is directed to the first placement location within the first user interface and that the first user input satisfies the first switching criterion, the display of the first widget is replaced with a different widget from the first group of widgets at the first placement location. A computer system including instructions for replacing the display of a second widget with a different widget from a second group of widgets in the second placement location, in accordance with a determination that the first user input is directed to the second placement location in the first user interface and that the first user input satisfies the first switching criterion.

109. A computer-readable storage medium for storing one or more programs, wherein when the one or more programs are executed by a computer system communicating with a display generation component and one or more input devices, the computer system... Displaying a first user interface corresponding to the restricted state of the computer system is: The first user interface includes simultaneously displaying a first placement location, the first widget of the first group of widgets in the first placement location, which is configured to accommodate individual widgets of a first group of widgets, and a second placement location, the second widget of the second group of widgets in the second placement location, which is configured to accommodate individual widgets of a second group of widgets. In the first user interface, while simultaneously displaying the first widget of the first group of widgets at the first placement location and the second widget of the second group of widgets at the second placement location, a first user input directed to the first user interface is detected. In response to detecting the first user input directed to the first user interface, In accordance with the determination that the first user input is directed to the first placement location within the first user interface and that the first user input satisfies the first switching criterion, the display of the first widget is replaced with a different widget from the first group of widgets at the first placement location. A computer-readable storage medium including instructions for replacing the display of a second widget with a different widget from a second group of widgets in the second placement location, in accordance with a determination that the first user input is directed to the second placement location in the first user interface and that the first user input satisfies a first switching criterion.

110. A computer system that communicates with a display generation component and one or more input devices, wherein the computer system is The means for displaying a first user interface corresponding to the restricted state of the computer system is: The first user interface includes a means for simultaneously displaying a first placement location, the first widget of the first group of widgets in the first placement location, which is configured to accommodate individual widgets of a first group of widgets in the first placement location, and a second placement location, the second widget of the second group of widgets in the second placement location, which is configured to accommodate individual widgets of a second group of widgets in the second placement location, the means for displaying, The first user interface includes means for detecting a first user input directed to the first user interface, which is enabled while simultaneously displaying the first widget of the first group of widgets at the first placement location and the second widget of the second group of widgets at the second placement location. Means that are activated in response to the detection of the first user input directed to the first user interface, Means for replacing the display of a first widget with a different widget from the first group of widgets at the first placement location, wherein the first user input is directed to the first placement location within the first user interface, and the display of the first widget is activated according to a determination that the first user input satisfies a first switching criterion, and A computer system comprising means for replacing the display of a second widget, which is activated according to a determination that the first user input is directed to the second placement location in the first user interface and that the first user input satisfies a first switching criterion, with a different widget from the second group of widgets in the second placement location.

111. An information processing device for use in a computer system that communicates with a display generation component and one or more input devices, wherein the information processing device is The means for displaying a first user interface corresponding to the restricted state of the computer system is: The first user interface includes a means for simultaneously displaying a first placement location, the first widget of the first group of widgets in the first placement location, which is configured to accommodate individual widgets of a first group of widgets in the first placement location, and a second placement location, the second widget of the second group of widgets in the second placement location, which is configured to accommodate individual widgets of a second group of widgets in the second placement location, the means for displaying, The first user interface includes means for detecting a first user input directed to the first user interface, which is enabled while simultaneously displaying the first widget of the first group of widgets at the first placement location and the second widget of the second group of widgets at the second placement location. Means that are activated in response to the detection of the first user input directed to the first user interface, Means for replacing the display of a first widget with a different widget from the first group of widgets at the first placement location, wherein the first user input is directed to the first placement location within the first user interface, and the display of the first widget is activated according to a determination that the first user input satisfies a first switching criterion, and A computer system comprising means for replacing the display of a second widget, which is activated according to a determination that the first user input is directed to the second placement location in the first user interface and that the first user input satisfies a first switching criterion, with a different widget from the second group of widgets in the second placement location.

112. A computer system that communicates with a display generation component and one or more input devices, wherein the computer system is One or more processors, A computer system comprising: a memory for storing one or more programs, wherein the one or more programs are configured to be executed by the one or more processors, and the one or more programs include instructions for performing the method according to any one of claims 94 to 107.

113. A computer-readable storage medium for storing one or more programs, wherein the one or more programs, when executed by a computer system communicating with a display generation component and one or more input devices, include instructions causing the computer system to perform the method according to any one of claims 94 to 107.

114. A graphical user interface on a computer system communicating with a display generation component and one or more input devices, wherein the computer system includes memory and one or more processors for executing one or more programs stored in the memory, and the graphical user interface includes a user interface displayed according to the method of any one of claims 94 to 107.

115. A computer system that communicates with a display generation component and one or more input devices, wherein the computer system is A computer system comprising means for performing the method described in any one of claims 94 to 107.

116. An information processing device for use in a computer system that communicates with a display generation component and one or more input devices, wherein the information processing device is An information processing apparatus comprising means for performing the method described in any one of claims 94 to 107.

117. It is a method, In a computer system that communicates with a display generation component and one or more sensors, While the first user interface is being displayed, it is detected that one or more conditions for displaying an individual user interface object of the first object type are met, the individual user interface object of the first type of user interface object corresponds to an individual application and provides status information that is updated over time within the individual user interface object without requiring the display of the individual application. In response to detecting that one or more of the conditions for displaying the individual user interface objects of the first object type are met, the individual user interface objects are displayed. While displaying an individual user interface object, a first user input corresponding to a request to reject the individual user interface object is detected, In response to detecting the first user input corresponding to a request to reject the individual user interface object, In accordance with the determination that the first user interface is a first type of user interface, the display of the individual user interface objects is stopped and the first user interface is redisplayed. A method comprising: discontinuing the display of the individual user interface objects and displaying the second user interface, which is different from the first user interface, in accordance with the determination that the first user interface is a second type of user interface different from the first type of user interface; and displaying the second user interface, which is different from the first user interface, in a location previously occupied by the first user interface.

118. The method according to claim 117, wherein the request to reject the individual user interface object includes an upward swipe from the bottom edge of the computer system toward the top edge of the computer system.

119. The method according to claim 117 or 118, wherein the second user interface is the application user interface of the application that was last displayed before the first user interface was displayed.

120. The method according to claim 117 or 118, wherein the second user interface is a home screen user interface that includes one or more application icons for launching applications of the computer system.

121. In response to detecting that one or more of the conditions for displaying the individual user interface have been met, the individual user interface object is displayed. In accordance with the determination that one or more of a first set of conditions are met, a first user interface object corresponding to a first application is displayed, and first status information is provided within the first user interface object that is updated over time without requiring the display of the first application. The method according to any one of claims 117 to 120, comprising: displaying a second user interface object, different from the first user interface object, corresponding to a second application different from the first application, in accordance with a determination that a second set of conditions different from the first set of conditions is met; and providing a second status information that is updated over time within the second user interface object without requiring the display of the second application.

122. The method according to any one of claims 117 to 121, wherein detecting the one or more conditions for displaying the individual user interface objects includes detecting a user selection of the indication of the individual user interface objects displayed together with the first user interface.

123. In response to detecting that one or more of the conditions for displaying the individual user interface objects of the first object type are met, displaying the individual user interface objects is: In accordance with the determination that the first user interface is a first type of user interface, the individual user interface objects are displayed in a first appearance, The method according to any one of claims 117 to 122, comprising displaying the individual user interface objects in a second appearance different from the first appearance, in accordance with the determination that the first user interface is a second type of user interface.

124. In response to detecting the first user input corresponding to a request to reject the individual user interface object, In accordance with the determination that the first user interface is a first type of user interface, the first indication corresponding to the individual user interface object is displayed simultaneously with the first user interface after the first user interface is redisplayed, The method according to any one of claims 117 to 123, comprising displaying a second indication corresponding to the individual user interface object simultaneously with the second user interface after the second user interface has been displayed, in accordance with the determination that the first user interface is a second type of user interface.

125. The method according to any one of claims 117 to 124, wherein the first type of user interface object includes a first user interface object corresponding to a media player application, and the first user interface object provides status information relating to media playback in progress using the media player application.

126. The method according to claim 125, wherein the first user interface object includes one or more media playback controls of the media player application.

127. The method according to claim 125 or 126, wherein the first user interface object includes one or more controls for browsing media items available for playback using the first user interface object.

128. The method according to any one of claims 125 to 127, wherein the first user interface object includes a representation of each media item available for playback using the first user interface object in a browseable arrangement, and the computer system, upon detecting one or more browsing inputs corresponding to a request to browse the media item in a first direction, cycles through at least a portion of each representation of the media item one by one at a selected position in the first user interface object.

129. The method according to any one of claims 117 to 128, wherein the first user interface object includes a progress indicator that updates over time in accordance with the playback progress of each media item being played using the first user interface object.

130. The method according to any one of claims 117 to 128, wherein the first type of user interface object includes a second user interface object corresponding to a timer application, and the second user interface object provides timer progress information relating to the first timer of the timer application.

131. The second user interface object includes one or more controls for interacting with the first timer in the timer application, and the method is To detect individual user inputs directed to a first control among the one or more controls for interacting with the first timer of the timer application via the one or more sensors, The method according to claim 130, comprising: detecting the individual user input directed to the first control, and performing an operation relating to the first timer.

132. The method according to claim 130 or 131, wherein the second user interface object includes a progress indicator that shows the current remaining time of the first timer, and the progress indicator is updated over time to show different amounts of remaining time of the first timer after the first timer has been started.

133. The method according to any one of claims 130 to 132, wherein the second user interface object simultaneously includes progress indicators corresponding to a plurality of timers in the timer application.

134. The first type of user interface object includes a third user interface object corresponding to a virtual assistant application, and the method is The detection of one or more voice commands directed to the virtual assistant application via the one or more sensors, The method according to any one of claims 117 to 133, further comprising providing visual feedback relating to the voice commands within the third user interface object in response to the detection of one or more voice commands.

135. The first type of user interface object includes a fourth user interface object corresponding to a communication application, and the method is Determining the current status of the first communication session supported by the aforementioned communication application, The method according to any one of claims 117 to 134, further comprising providing status information relating to the current status of the first communication session in a fourth user interface object, according to the current status of the first communication session.

136. The aforementioned communication application corresponds to an electronic doorbell device, and the method is Displaying one or more controls for controlling the electronic doorbell device on the fourth user interface object, Detecting individual user inputs that activate a first control among the one or more controls for controlling the electronic doorbell device, The method according to claim 135, comprising: detecting the individual user input that activates the first control of one or more of the controls; performing an individual action on the electronic doorbell device in response to such detection.

137. The communication application is a telephone application that supports real-time communication calls between a user of the computer system and other users, and the method is Displaying one or more controls within the fourth user interface object for changing the call status of a first call between the user of the computer system and a second user, To detect the selection of a first control among the one or more controls for changing the call status of the first call between the user of the computer system and the second user, The method of claim 135, comprising detecting the selection of a first control among one or more controls for changing the call status of a first call between the user and a second user of the computer system, and changing the call status of the first call in accordance with the selection of the first control.

138. The communication application is a video call application that supports real-time video calls between a user of the computer system and other users, and the method is Simultaneously displaying a video feed of the first real-time video call between the user and the second user of the computer system, and one or more controls within the fourth user interface object for changing the call status of the first video call. Detecting the selection of a second control among the one or more controls for changing the call status of the first video call, The method according to claim 135, comprising detecting the selection of a second control among the one or more controls for changing the call status of the first video call, and changing the call status of the first video call in accordance with the selection of the second control.

139. The method according to any one of claims 117 to 138, wherein the first type of user interface object includes a fifth user interface object corresponding to a first subscribed event, and when an event update is generated for the first subscribed event, the event update information is displayed in the fifth user interface object from time to time.

140. While displaying the individual user interface objects of the first type of user interface object, it is possible to detect that the extended criteria are met, The method according to any one of claims 117 to 139, comprising: detecting that the extended criteria have been met, displaying in the individual user interface object additional content that was not displayed in the individual user interface object before the detection that the extended criteria had been met.

141. The method according to claim 140, wherein detecting that the extended criteria are met includes detecting the occurrence of a first event generated by the individual application.

142. The method according to claim 140 or 141, wherein detecting that the extension criteria are met includes detecting a second user input directed to the individual user interface object, the second user input corresponding to a request to extend the individual user interface object.

143. While the first user interface is displayed, the occurrence of the first event is detected, A method comprising: detecting the occurrence of the first event and displaying a first notification corresponding to the first event, wherein the display is In accordance with the determination that the first user interface is a first type of user interface, the first notification is displayed in a first size, The method according to any one of claims 117 to 142, comprising displaying the first notice in a second size different from the first size, in accordance with the determination that the first user interface is a second type of user interface.

144. Displaying the first notification corresponding to the first event is: In accordance with the determination that the authentication criteria are met, the first notification is displayed together with the first notification content, The method according to claim 143, comprising displaying the first notice together with second notice content in accordance with the determination that the authentication criteria are not met, wherein the second notice content omits at least a portion of the first notice content.

145. Displaying the first notification corresponding to the first event is: Display the initial notification content before a threshold time has elapsed since the detection of the first event, In accordance with the determination that the authentication criteria are met, additional notification content different from the initial notification content is displayed after the threshold time amount has elapsed since the detection of the first event. The method according to claim 143 or 144, comprising discontinuing the display of the initial notification content without displaying the additional notification content in accordance with the determination that the authentication criteria are not met, wherein the initial notification content omits at least a portion of the details in the additional notification content.

146. Displaying the first notification corresponding to the first event is: While the initial notification content is displayed within the first notification, the presence of a user in close proximity to the computer system is detected via one or more sensors. The method according to any one of claims 143 to 145, comprising: displaying the first notification having additional notification content different from the initial notification content, in response to the detection of the presence of the user and in accordance with the determination that the presence of the user satisfies the extended criteria.

147. While the first notification is being displayed, a third user input directed to the first notification is detected, The method according to any one of claims 143 to 146, comprising detecting the third user input and ceasing to display the first notice in accordance with the determination that the third user input meets the rejection criteria.

148. In response to detecting the third user input, In accordance with the determination that the third user input satisfies the rejection criteria and the first user interface is a first type of user interface, after the first notification is no longer displayed, a first notification indicator corresponding to the first notification is displayed, wherein the first notification indicator has a third size. The method according to claim 147, comprising displaying a first notification indicator corresponding to the first notification in accordance with the determination that the third user input satisfies the rejection criteria and the first user interface is a second type of user interface, wherein after the first notification is no longer displayed, the first notification indicator has a fourth size that is larger than the third size.

149. While the first user interface and the first notification indicator are displayed simultaneously, a fourth user input directed to the first notification indicator is detected. In response to detecting the fourth user input directed to the first notification indicator, In accordance with the determination that the first user interface is a first type of user interface, the display of the first notification indicator is maintained without displaying the notification content of the first notification, The method according to claim 148, comprising displaying the notification content of the first notification in accordance with the determination that the first user interface is a second type of user interface.

150. When the first user interface is a first type of user interface, after detecting the fourth user input, the system detects a change in the state of the computer system, wherein the change in the state of the computer system includes a change in the orientation of the computer system or disconnection of the computer system from a charging source. In response to detecting the aforementioned change in the state of the computer system, Replacing the display of the first user interface with the display of the second user interface, Displaying the first notification indication in the second user interface, The method according to claim 149, comprising displaying the notification content of the first notification that was not displayed before detecting the change in the state of the computer system while the first notification indication is being displayed in the second user interface.

151. Displaying the first notification indicator in response to the detection of the third user input is performed in accordance with the determination that the third user input meets the rejection criteria and that the display of the notification indicator is enabled, and the method is The method according to any one of claims 147 to 150, comprising, in response to detecting the third user input, stopping the display of the first notification indicator corresponding to the first notification after the first notification has stopped being displayed in accordance with the determination that the third user input satisfies the rejection criteria and the display of the notification indicator has been disabled.

152. While the first user interface is displayed, a sixth user input corresponding to a request to reject the first user interface is detected, In response to detecting the sixth user input corresponding to a request to reject the first user interface, In accordance with the determination that the first user interface is a first type of user interface, the display of the first user interface, which is a first type of user interface, The method according to any one of claims 117 to 151, comprising: discontinuing to display the first user interface which is a second type of user interface, in accordance with the determination that the first user interface is a second type of user interface, and displaying the second user interface which is different from the first user interface in a location previously occupied by the first user interface.

153. A computer system that communicates with a display generation component and one or more sensors, wherein the computer system is One or more processors, A memory that stores one or more programs, wherein the one or more programs are configured to be executed by the one or more processors, While the first user interface is being displayed, it is detected that one or more conditions for displaying an individual user interface object of the first object type are met, the individual user interface object of the first type of user interface object corresponds to an individual application and provides status information that is updated over time within the individual user interface object without requiring the display of the individual application. In response to detecting that one or more of the conditions for displaying the individual user interface objects of the first object type are met, the individual user interface objects are displayed. While displaying an individual user interface object, a first user input corresponding to a request to reject the individual user interface object is detected. In response to detecting the first user input corresponding to a request to reject the individual user interface object, In accordance with the determination that the first user interface is a first type of user interface, the display of the individual user interface objects is stopped, and the first user interface is redisplayed. A computer system including an instruction to cease displaying the individual user interface objects and to display the second user interface, which is different from the first user interface, in accordance with the determination that the first user interface is a second type of user interface different from the first type of user interface.

154. A computer-readable storage medium for storing one or more programs, wherein when the one or more programs are executed by a computer system communicating with a display generation component and one or more sensors, the computer system... While the first user interface is being displayed, the system detects that one or more conditions for displaying an individual user interface object of the first object type are met, the individual user interface object of the first type of user interface object corresponds to an individual application and provides status information that is updated over time within the individual user interface object without requiring the display of the individual application. In response to detecting that one or more of the conditions for displaying the individual user interface objects of the first object type are met, the individual user interface objects are displayed. While displaying individual user interface objects, a first user input corresponding to a request to reject the individual user interface object is detected. In response to detecting the first user input corresponding to a request to reject the individual user interface object, In accordance with the determination that the first user interface is a first type of user interface, the display of the individual user interface objects is stopped, and the first user interface is redisplayed. A computer-readable storage medium including instructions to cease displaying the individual user interface objects and to display the second user interface, which is different from the first user interface, in accordance with the determination that the first user interface is a second type of user interface different from the first type of user interface.

155. A computer system that communicates with a display generation component and one or more sensors, wherein the computer system is A means for detecting that one or more conditions for displaying a particular user interface object of a first object type are met, which is enabled while a first user interface is being displayed, wherein the particular user interface object of the first type of user interface object corresponds to a particular application and provides status information that is updated over time within the particular user interface object without requiring the display of the particular application. Means for displaying the individual user interface objects, which are activated in response to the detection that one or more conditions for displaying the individual user interface objects of the first object type are met, Means for detecting a first user input corresponding to a request to reject an individual user interface object, which is activated while an individual user interface object is being displayed, Means that are activated in response to the detection of the first user input corresponding to a request to reject the individual user interface object, Means for stopping the display of the individual user interface objects and redisplaying the first user interface, which are activated in accordance with the determination that the first user interface is a first type of user interface, and A computer system comprising means including means for ceasing to display the individual user interface objects and displaying the second user interface, which is different from the first user interface, in a location previously occupied by the first user interface, in accordance with the determination that the first user interface is a second type of user interface different from the first type of user interface.

156. An information processing device for use in a computer system that communicates with a display generation component and one or more sensors, wherein the information processing device is A means for detecting that one or more conditions for displaying a particular user interface object of a first object type are met, which is enabled while a first user interface is being displayed, wherein the particular user interface object of the first type of user interface object corresponds to a particular application and provides status information that is updated over time within the particular user interface object without requiring the display of the particular application. Means for displaying the individual user interface objects, which are activated in response to the detection that one or more conditions for displaying the individual user interface objects of the first object type are met, Means for detecting a first user input corresponding to a request to reject an individual user interface object, which is activated while an individual user interface object is being displayed, Means that are activated in response to the detection of the first user input corresponding to a request to reject the individual user interface object, Means for stopping the display of the individual user interface objects and redisplaying the first user interface, which are activated in accordance with the determination that the first user interface is a first type of user interface, and Information processing apparatus comprising means including means for ceasing to display the individual user interface objects, which are activated in accordance with the determination that the first user interface is a second type of user interface different from the first type of user interface, and for displaying the second user interface different from the first user interface in a location previously occupied by the first user interface.

157. A computer system that communicates with a display generation component and one or more sensors, wherein the computer system is One or more processors, A computer system comprising: a memory for storing one or more programs, wherein the one or more programs are configured to be executed by the one or more processors, and the one or more programs include instructions for performing the method according to any one of claims 117 to 152.

158. A computer-readable storage medium for storing one or more programs, wherein the one or more programs, when executed by a computer system communicating with a display generation component and one or more sensors, include instructions causing the computer system to perform the method according to any one of claims 117 to 152.

159. A graphical user interface on a computer system communicating with a display generation component and one or more sensors, wherein the computer system includes a memory and one or more processors for executing one or more programs stored in the memory, and the graphical user interface includes a user interface displayed according to the method of any one of claims 117 to 152.

160. A computer system that communicates with a display generation component and one or more sensors, wherein the computer system is A computer system comprising means for performing the method described in any one of claims 117 to 152.

161. An information processing device for use in a computer system that communicates with a display generation component and one or more sensors, wherein the information processing device is An information processing apparatus comprising means for performing the method described in any one of claims 117 to 152.

162. It is a method, In a computer system that communicates with a display generation component and one or more sensors, To detect the disconnection of the computer system from the charging source, In response to detecting the disconnection of the computer system from the charging source, A method comprising: the computer system being in a first operating mode, wherein the computer system displays a clock user interface via the display generation component for at least a portion of the duration that the computer system is operating in the first operating mode, and activating the flashlight function of the computer system in accordance with the determination that the computer system has been disconnected from the charging source while the computer system was in the first operating mode.

163. Before detecting the disconnection of the computer system from the charging source, it is necessary to detect that a first set of conditions is met, The method according to claim 162, comprising: detecting that the first set of conditions is met, and entering the first operating mode in accordance with the determination that the first set of conditions is met.

164. While the computer system is operating in the first operating mode, it detects a first user input directed to the display generation component, The method according to claim 162 or 163, comprising increasing the visual prominence of the clock user interface in response to the detection of the first user input.

165. The method according to claim 164, wherein the first user input includes a touch input directed toward the touch-sensing surface of the computer system.

166. The method according to claim 164 or 165, wherein detecting the first user input includes detecting the movement of the user within a threshold distance of one or more sensors.

167. The method according to any one of claims 164 to 166, wherein detecting the first user input includes detecting gaze input directed towards the computer system.

168. The method according to any one of claims 164 to 167, wherein detecting the first user input includes detecting a swipe gesture in a first direction.

169. Before detecting the disconnection of the computer system from the charging source and while the computer system is operating in the first operating mode, the clock user interface having a first amount of time content is displayed, and a second user input directed to the clock user interface is detected. The method according to any one of claims 162 to 168, comprising: detecting the second user input; displaying the clock user interface having a second amount of time content greater than the first amount of time content.

170. The computer system, while operating in the first operating mode, detects that the current time satisfies the alarm trigger criteria, In response to detecting that the current time satisfies the alarm trigger criteria, a first audio alert is generated. While generating the first audio alert, a third user input directed to the clock user interface is detected, The method according to any one of claims 162 to 169, comprising reducing the audio prominence of the first audio alert in response to the detection of the third user input.

171. The method according to any one of claims 162 to 170, wherein displaying the clock user interface while the computer system is operating in the first operating mode includes displaying the current time in a first format different from the second format in which the current time is displayed on the clock user interface when the computer system is not operating in the first operating mode.

172. The method of claim 171, wherein displaying the current time in the first format includes displaying the current time having less detail in the time value of the current time compared to the second format.

173. The method according to any one of claims 162 to 172, wherein the clock user interface includes a visual indication of a first alarm time along with an indication of the current time.

174. In accordance with the determination that the current time is the first time, the visual indication of the current time is displayed as a digital indication displayed at the first location. The method according to claim 173, comprising: determining that the current time is a second time different from the first time, displaying the visual indication for the current time as the digital indication displayed at a second location different from the first location.

175. The method according to any one of claims 162 to 174, wherein, in accordance with the determination that the current time is within a sleep period established by the computer system, the computer system enters the first operating mode.

176. The method according to any one of claims 162 to 175, wherein activating the flashlight function of the computer system includes displaying the illuminated area via the display generation component.

177. While the flashlight function of the computer system remains active, a third user input directed to the display generation component is detected. The method according to any one of claims 162 to 176, comprising: detecting the third user input and, in accordance with the determination that the third user input includes movement in a first direction, changing the color temperature of the flashlight function from a first color temperature to a second color temperature different from the first color temperature.

178. While the flashlight function of the computer system remains active, a fourth user input directed to the display generation component is detected. The method according to any one of claims 162 to 177, comprising: detecting the fourth user input, and determining that the fourth user input includes movement in a second direction, changing the brightness of the flashlight function from a first brightness to a second brightness different from the first brightness.

179. While the flashlight function remains active, a fifth user input directed to the display generation component is detected. The method according to any one of claims 162 to 178, comprising detecting the fifth user input and, in accordance with the determination that the fifth user input meets the rejection criteria, deactivating the flashlight function of the computer system.

180. The method according to claim 179, wherein the rejection criteria are met according to the determination that the fifth user input includes an upward swipe gesture from the bottom edge of the display generation component.

181. While the flashlight function of the computer system is active, a sixth user input corresponding to a request to turn off the flashlight function of the computer system is detected. The method according to any one of claims 162 to 180, comprising deactivating the flashlight function of the computer system in response to detecting the sixth user input.

182. The occurrence of the first event is detected while the flashlight function of the computer system remains active. The method according to any one of claims 162 to 181, comprising: detecting the first event and determining that a first setting condition is met as a result of the first event; and deactivating the flashlight function of the computer system.

183. The computer system, while operating in the first operating mode, detects that the current time satisfies the alarm trigger criteria, The method according to any one of claims 162 to 182, comprising: generating a first alarm in response to detecting that the current time satisfies the alarm trigger criterion, wherein the first alarm is automatically selected from a plurality of alarm outputs in a random or pseudo-random manner.

184. The method according to claim 183, wherein generating the first alarm includes generating a first audio output.

185. The method according to claim 183 or 184, wherein generating the first alarm includes displaying the first visual output via the display generation component.

186. The first alarm, which includes a first alarm output selected from the plurality of alarm outputs, detects that a first period has elapsed after generating the first alarm, and that the current time satisfies the alarm trigger criterion after the first period has elapsed. The method according to any one of claims 183 to 185, comprising: generating a second alarm in response to detecting that the current time satisfies the alarm trigger criterion after the first period has elapsed, wherein the second alarm includes a second alarm output that is automatically selected from the plurality of alarm outputs in a random or pseudo-random manner and is different from the first alarm output.

187. While the first alarm is being generated, a user input corresponding to a request to snooze the first alarm is detected, Including detecting the user input corresponding to the request to snooze the first alarm, ceasing to generate the first alarm, detecting that the first period has elapsed, and detecting that the current time after the first period has elapsed satisfies the alarm trigger criterion, To detect that the snooze period has elapsed since detecting the user input corresponding to the request to snooze the first alarm, The method according to claim 186, comprising detecting the user input corresponding to the request to snooze the first alarm and determining that the alarm trigger criterion has been met by the current time after the snooze period has elapsed.

188. The aforementioned first alarm is generated on the first day, The method according to claim 186, wherein detecting that the first period has elapsed and that the current time satisfies the alarm trigger criterion after the first period has elapsed includes detecting that the current time satisfies the alarm trigger criterion on a second day different from the first day.

189. The first alarm is generated based on the first alarm setting, The method according to claim 186, wherein detecting that the first period has elapsed and that the current time satisfies the alarm trigger criteria after the first period has elapsed includes detecting that the current time satisfies the alarm trigger criteria based on a second alarm setting different from the first alarm setting.

190. While the first alarm is being generated, the movement of the computer system is detected, The method according to any one of claims 183 to 189, comprising: detecting the movement of the computer system, and ceasing to generate the first alarm in accordance with the determination that the movement of the computer system satisfies the movement criteria.

191. In response to detecting the disconnection of the computer system from the charging source, The method according to any one of claims 183 to 190, comprising ceasing to generate the first alarm in accordance with a determination that the computer system has been disconnected from the charging source while the computer system is generating the first alarm.

192. The method according to any one of claims 183 to 191, comprising displaying a visual change on the clock user interface in accordance with a determination that the alarm trigger criterion is about to be met, before detecting that the current time meets the alarm trigger criterion, wherein displaying the visual change on the clock user interface includes changing the color and / or size of at least one element of the clock user interface.

193. In response to detecting that the current time satisfies the alarm trigger criteria, one or more selectable options for interacting with the first alarm are displayed. Detecting individual user inputs corresponding to the selection of a first selectable option from the one or more selectable options for interacting with the first alarm, The method of claim 192, comprising detecting the individual user input corresponding to the selection of the first selectable option among the one or more selectable options for interacting with the first alarm, and performing a first action with respect to the first alarm according to the first selectable option.

194. A computer system that communicates with a display generation component and one or more sensors, wherein the computer system is One or more processors, A memory that stores one or more programs, wherein the one or more programs are configured to be executed by the one or more processors, The computer system is detected to be disconnected from the charging source, In response to detecting the disconnection of the computer system from the charging source, A computer system including a command to activate the flashlight function of the computer system in a first operating mode, wherein the computer system displays a clock user interface via the display generation component for at least a portion of the duration that the computer system is operating in the first operating mode, and the computer system activates the flashlight function of the computer system in accordance with the determination that the computer system has been disconnected from the charging source while it was in the first operating mode.

195. A computer-readable storage medium for storing one or more programs, wherein when the one or more programs are executed by a computer system communicating with a display generation component and one or more sensors, the computer system... To detect the disconnection of the computer system from the charging source, In response to detecting the disconnection of the computer system from the charging source, A computer-readable storage medium containing instructions for activating the flashlight function of the computer system in accordance with a determination that the computer system has been disconnected from the charging source while in a first operating mode, wherein the computer system displays a clock user interface via the display generation component for at least a portion of the duration that the computer system is operating in the first operating mode.

196. A computer system that communicates with a display generation component and one or more sensors, wherein the computer system is Means for detecting the disconnection of the computer system from the charging source, Means that are activated in response to detection of the disconnection of the computer system from the charging source, A computer system comprising: a first operating mode in which the computer system displays a clock user interface via the display generation component for at least a portion of the duration that the computer system is operating in the first operating mode; and a means for activating a flashlight function of the computer system, which is activated in accordance with a determination that the computer system has been disconnected from the charging source while in the first operating mode.

197. An information processing device for use in a computer system that communicates with a display generation component and one or more sensors, wherein the information processing device is Means for detecting the disconnection of the computer system from the charging source, Means that are activated in response to detection of the disconnection of the computer system from the charging source, Information processing apparatus comprising: a first operating mode in which the computer system displays a clock user interface via the display generation component for at least a portion of the duration that the computer system is operating in the first operating mode; and means for activating a flashlight function of the computer system, which is activated in accordance with a determination that the computer system has been disconnected from the charging source while in the first operating mode.

198. A computer system that communicates with a display generation component and one or more sensors, wherein the computer system is One or more processors, A computer system comprising: a memory for storing one or more programs, wherein the one or more programs are configured to be executed by the one or more processors, and the one or more programs include instructions for performing the method according to any one of claims 162 to 193.

199. A computer-readable storage medium for storing one or more programs, wherein the one or more programs, when executed by a computer system communicating with a display generation component and one or more sensors, include instructions causing the computer system to perform the method according to any one of claims 162 to 193.

200. A graphical user interface on a computer system communicating with a display generation component and one or more sensors, wherein the computer system includes a memory and one or more processors for executing one or more programs stored in the memory, and the graphical user interface includes a user interface displayed according to the method of any one of claims 162 to 193.

201. A computer system that communicates with a display generation component and one or more sensors, wherein the computer system is A computer system comprising means for performing the method described in any one of claims 162 to 193.

202. An information processing device for use in a computer system that communicates with a display generation component and one or more sensors, wherein the information processing device is An information processing apparatus comprising means for performing the method described in any one of claims 162 to 193.

203. It is a method, In a computer system including a display generation component and one or more sensors, The computer system operates in a first mode, and while operating in the first mode, it detects the presence of a person approaching the computer system via one or more sensors without detecting contact between the person and the computer system. A method comprising updating display content displayed via the display generation component of the computer system while remaining in the first mode, in response to the detection of the presence of the person in proximity to the computer system without detecting contact of the person with the computer system.

204. The method according to claim 203, wherein the first criterion includes a first criterion that is satisfied when the computer system is connected to a power source.

205. The method according to claim 203 or 204, wherein the first criterion includes a second criterion that is satisfied when the display generation component of the computer system has a first orientation.

206. The computer system detects that the first criterion is no longer met while it is operating in the first mode, The system includes, upon detecting that the first criterion is no longer met, transitioning from the first mode to the second mode of the computer system, The second mode includes a lock mode in which one or more operations available in the unlock mode are not available in the lock mode. The method according to any one of claims 203 to 205, wherein while in the second mode, the computer system displays a separate user interface corresponding to the lock mode of the computer system.

207. The method according to any one of claims 203 to 206, wherein updating the display content displayed via the display generation component of the computer system includes increasing the visual prominence of at least one portion of the display content by adjusting one or more display parameters of the individual portion of the display content.

208. The method according to any one of claims 203 to 207, wherein updating the display content includes increasing the information density of the display content by displaying additional content that was not displayed at a time prior to the detection of the presence of the user in proximity to the computer system.

209. The method according to any one of claims 203 to 208, wherein the device does not perform any action based on the detection of the presence of a person in close proximity to the computer system while the computer system is operating in any other mode other than the first mode.

210. The method according to any one of claims 203 to 209, wherein the first criterion requires that the display generation component of the computer system be connected to a power supply and simultaneously be in a first orientation for at least a threshold time amount in order that the first criterion is satisfied.

211. Updating the aforementioned display content means The method according to any one of claims 203 to 210, comprising updating the display of one or more widgets on the display generation component, wherein each of the one or more widgets corresponds to one or more applications, and each of the one or more widgets contains individual application content from the individual applications of the one or more applications, and the computer system automatically updates the individual widgets from time to time when the individual application content is changed within the individual applications.

212. Updating the aforementioned display content means The method according to any one of claims 203 to 211, comprising updating the display of a clock user interface that shows the current time.

213. While the computer system is operating in the first mode, A second criterion, distinct from the first criterion, wherein the second criterion requires that the current time corresponds to nighttime, and in accordance with the determination that the second criterion is met, one or more sensors are activated to detect the presence of a person in close proximity to the computer system without detecting contact between the person and the computer system. The method according to any one of claims 203 to 212, comprising: deactivating one or more sensors to detect the presence of a person in close proximity to the computer system without detecting contact between the person and the computer system, in accordance with the determination that the first criterion is met and the second criterion is not met.

214. The method according to claim 213, wherein the second criterion includes a third criterion that is satisfied when the current time is within a first time range of a day.

215. The method according to claim 213 or 214, wherein the second criterion includes a fourth criterion that is satisfied when the ambient light in the physical environment of the computer system is below a threshold luminance level for at least a threshold time amount.

216. The method according to any one of claims 213 to 215, wherein the second criterion includes a fifth criterion that is satisfied when the current time is within a scheduled sleep time established on the computer system.

217. The method according to any one of claims 213 to 216, wherein the second criterion includes a sixth criterion that is satisfied when the computer system displays a clock user interface.

218. While the computer system is operating in the first mode, the absence of the presence of the person in proximity to the computer system is detected via one or more sensors. The method according to any one of claims 203 to 217, comprising: in response to detecting the absence of the presence of the person in proximity to the computer system, reverting at least a number of changes made to the display content when updating the display content in response to detecting the presence of the person in proximity to the computer system while remaining in the first mode.

219. The method according to any one of claims 203 to 218, wherein detecting the presence of the person in proximity to the computer system via one or more sensors includes detecting the movement of the person in proximity to the computer system.

220. Detecting the presence of the person in proximity to the computer system via one or more of the sensors is: To detect the first movement of a hand approaching the computer system via one or more of the aforementioned sensors, The method according to any one of claims 203 to 219, comprising determining that the first movement of the hand corresponds to a first air gesture recognized by the computer system.

221. The method according to claim 220, comprising suppressing a first alert generated by the computer system in response to the detection of a first movement of the hand in proximity to the computer system and the determination that the first movement of the hand corresponds to a first air gesture.

222. The method according to claim 220 or 221, comprising displaying additional information on the display generation component that was not displayed before the detection of the first movement of the hand approaching the computer system, in response to the detection of the first movement of the hand approaching the computer system and the determination that the first movement of the hand corresponds to the first air gesture.

223. The method according to any one of claims 220 to 222, wherein determining that the first movement of the hand corresponds to the first air gesture is based on determining that the hand has a first orientation with respect to the display generating component during the first movement of the hand.

224. The detection of a second movement of the hand, which is a second movement of the hand approaching the computer system via one or more of the sensors, and which includes detecting that the second movement of the hand does not correspond to the first air gesture, The method according to any one of claims 220 to 223, comprising: detecting the second movement of the hand in close proximity to the computer system; and ceasing to update the display content on the display generation component.

225. After detecting the second movement of the hand approaching the computer system, the first contact between the hand and the computer system is detected via one or more sensors. The method according to claim 224, comprising detecting the first contact between the hand and the computer system, and, in accordance with the determination that the first contact satisfies an action criterion, performing a first action in accordance with the input provided by the first contact.

226. The method according to any one of claims 220 to 225, wherein determining that the first movement of the hand corresponds to the first air gesture recognized by the computer system is based on determining that the hand has a first posture with respect to the display generating component during the first movement of the hand.

227. The method according to any one of claims 220 to 226, wherein determining that the first movement of the hand corresponds to the first air gesture recognized by the computer system is based on determining that the first movement of the hand includes forward and backward movement of the hand relative to the display generating component.

228. The method according to any one of claims 220 to 227, comprising moving the display content on the display generation component in a first direction relative to the display generation component in accordance with the first movement of the hand.

229. The method according to any one of claims 203 to 229, wherein detecting the presence of the person in proximity to the computer system via one or more sensors includes detecting vibrations of a surface that is in contact with the computer system and / or within a threshold distance of the computer system.

230. In accordance with the determination that the first setting is enabled for the first mode, the presence of the person approaching the computer system is detected via one or more sensors, in accordance with the detection of vibrations of a surface that is in contact with the computer system and / or within a threshold distance of the computer system. The method according to claim 229, comprising: determining that the first setting is disabled for the first mode, and then, via one or more sensors, detecting vibrations of a surface in contact with the computer system and / or within the threshold distance of the computer system, thereby ceasing to detect the presence of the user in close proximity to the computer system.

231. While in the first mode, it is detected that the third criterion is met, In response to detecting that the third criterion is met, and in accordance with the determination that the second setting is not enabled for the first mode, the display of content on the display generation component is stopped while remaining in the first mode. After ceasing to display content on the display generation component and while remaining in the first mode, the presence of a person approaching the computer system is detected via one or more sensors without detecting physical contact between the person and the computer system. Without detecting contact between the user and the computer system, upon detecting the presence of the person in close proximity to the computer system, and in accordance with the determination that the second setting is not enabled for the first mode, the display of content on the display generation component is stopped while remaining in the first mode. After ceasing to display content on the display generation component and while remaining in the first mode, detecting human contact with the computer system via one or more sensors, The method according to any one of claims 203 to 230, comprising: detecting contact of the user with the computer system, and while remaining in the first mode, displaying content on the display generation component.

232. A computer system comprising a display generation component and one or more sensors, wherein the computer system is One or more processors, A memory that stores one or more programs, wherein the one or more programs are configured to be executed by the one or more processors, The computer system operates in a first mode, and while operating in the first mode, it detects the presence of a person approaching the computer system via one or more sensors without detecting contact between the person and the computer system. A computer system including an instruction to update display content displayed via the display generation component of the computer system while remaining in the first mode, in response to the detection of the presence of the person in close proximity to the computer system without detecting contact of the person with the computer system.

233. A computer-readable storage medium for storing one or more programs, wherein the one or more programs are executed by a computer system including a display generation component and one or more sensors, and the computer system receives the following information: The computer system operates in a first mode, and while operating in the first mode, it causes the computer system to detect the presence of a person approaching the computer system via one or more sensors without detecting contact between the person and the computer system. A computer-readable storage medium including instructions for updating display content displayed via the display generation component of the computer system while remaining in the first mode, in response to the detection of the presence of the person in close proximity to the computer system without detecting contact of the person with the computer system.

234. A computer system comprising a display generation component and one or more sensors, wherein the computer system is The computer system is in a first mode, and the computer system operates in the first mode while a first criterion is met, and while operating in the first mode, it has means for detecting the presence of a person approaching the computer system without detecting contact between the person and the computer system, via one or more sensors. A computer system comprising: means for updating display content displayed via the display generation component of the computer system, which is activated while remaining in the first mode in response to the detection of the presence of the person in close proximity to the computer system without detecting contact of the person with the computer system.

235. An information processing device for use in a computer system including a display generation component and one or more sensors, wherein the information processing device is The computer system is in a first mode, and the computer system operates in the first mode while a first criterion is met, and while operating in the first mode, it has means for detecting the presence of a person approaching the computer system without detecting contact between the person and the computer system, via one or more sensors. An information processing apparatus comprising means for updating display content displayed via the display generation component of the computer system, which is activated while remaining in the first mode in response to the detection of the presence of the person in close proximity to the computer system without detecting contact of the person with the computer system.

236. A computer system comprising a display generation component and one or more sensors, wherein the computer system is One or more processors, A computer system comprising: a memory for storing one or more programs, wherein the one or more programs are configured to be executed by the one or more processors, and the one or more programs include instructions for performing the method according to any one of claims 203 to 231.

237. A computer-readable storage medium for storing one or more programs, wherein, when executed by a computer system including a display generation component and one or more sensors, the one or more programs include instructions causing the computer system to perform the method according to any one of claims 203 to 231.

238. A graphical user interface on a computer system comprising a display generation component and one or more sensors, wherein the computer system comprises a memory and one or more processors for executing one or more programs stored in the memory, and the graphical user interface comprises a user interface displayed according to the method of any one of claims 203 to 231.

239. A computer system comprising a display generation component and one or more sensors, wherein the computer system is A computer system comprising means for performing the method described in any one of claims 203 to 231.

240. An information processing device for use in a computer system including a display generation component and one or more sensors, wherein the information processing device is An information processing apparatus comprising means for performing the method described in any one of claims 203 to 231.

241. It is a method, In a computer system that communicates with one or more sensors for detecting display generation components and user input, Detecting the first event, In order to detect the first event, This includes, in accordance with the determination that a first criterion is met as a result of the first event, displaying a separate customizable user interface that was not displayed before the first event was detected, A method for displaying the individual customizable user interfaces, comprising displaying a first customizable user interface configured according to a first set of customization parameters corresponding to the first identity of the charging source, based on a determination that one or more power transmission signals received from the charging source include first identification data representing a first identity of the charging source.

242. Displaying the individual customizable user interface that was not displayed before the detection of the first event is: The method according to claim 241, comprising displaying a second customizable user interface configured according to a second set of customization parameters corresponding to the second identity of the charging source, based on a determination that one or more power transmission signals received from the charging source include second identification data representing a second identity different from the first identity of the charging source.

243. Displaying the individual customizable user interface that was not displayed before the detection of the first event is: The method according to claim 241 or 242, comprising: discontinuing the display of the first customizable user interface in accordance with the determination that identification data representing the identity of the charging source was not obtained from a power transmission signal received from the charging source; and displaying a third customizable user interface different from the first customizable user interface, wherein the third customizable user interface is configured according to a default set of customization parameters different from the first set of customization parameters.

244. Displaying the individual customizable user interface that was not displayed before the detection of the first event is: In accordance with the determination that the one or more power transmission signals include a first indication that the individual identifier of the charging source embedded in the one or more power transmission signals is a unique identifier of the charging source, the individual customizable user interface having customization based on the unique identifier is displayed. The method according to any one of claims 241 to 243, comprising displaying the individual customizable user interface without customization based on the individual identifier, in accordance with the determination that the one or more power transmission signals include a second indication that the individual identifier of the charging source embedded in the one or more power transmission signals is not unique to the charging source.

245. The method according to any one of claims 241 to 243, wherein the first criterion requires that, in order for the first criterion to be satisfied, the charging source is coupled to the computer system, enabling the battery of the computer system to be charged by the charging source, and the computer system is in a first orientation.

246. Receiving one or more power transmission signals from the charging source, The method according to any one of claims 241 to 245, comprising decoding the first identification data representing the first identity of the charging source from at least one of the one or more power transmission signals received from the charging source.

247. The method according to any one of claims 241 to 246, comprising decoding the first identification data representing the first identity of the charging source from one or more data signals other than the power transmission signals received from the charging source, wherein the data signals are not used to supply power to the computer system.

248. The method according to claim 247, wherein the one or more power transmission signals, including the first identity data of the charging source, are received from the charging source during a period when the battery of the computer system is not being charged by the charging source.

249. The method according to any one of claims 241 to 248, comprising decoding the first identification data from one or more power transmission signals using a frequency shift keying decoder.

250. The method according to any one of claims 241 to 249, comprising sending a request for identification data to the charging source before receiving the one or more power transmission signals containing the first identification data from the charging source, wherein the first identification data is transmitted by the charging source to the computer system in the one or more power transmission signals in response to receiving the request from the computer system.

251. The method according to claim 250, comprising encoding the identification data in an individual power transmission signal using an amplitude shift keying encoder.

252. The method according to any one of claims 241 to 251, wherein the one or more power transmission signals carry a payload, and the payload encodes an identifier of the charging source.

253. The method according to claim 252, wherein the payload includes the first portion encoding an indicator that specifies whether the second portion of the payload following the first portion includes a unique identifier that uniquely corresponds to a specific charging source.

254. The method according to claim 253, wherein the first portion of the payload has a length of one bit, and the second portion of the payload has a length of 20 or 31 bits.

255. The method according to any one of claims 252 to 254, wherein the one or more power transmission signals carry a header before the payload, the header indicating whether the one or more power transmission signals include a wireless power transmission transmitter identification packet according to the Wireless Power Consortium Qi charging protocol.

256. A computer system comprising a display generation component and one or more sensors, wherein the computer system is One or more processors, A memory that stores one or more programs, wherein the one or more programs are configured to be executed by the one or more processors, The first event is detected, In order to detect the first event, The system includes instructions to display a customizable user interface that was not displayed before the detection of the first event, in accordance with the determination that a first criterion is met as a result of the first event, A computer system that displays the individual customizable user interfaces, which includes displaying a first customizable user interface configured according to a first set of customization parameters corresponding to the first identity of the charging source, based on a determination that one or more power transmission signals received from the charging source include first identification data representing a first identity of the charging source.

257. A computer-readable storage medium for storing one or more programs, wherein the one or more programs are executed by a computer system including a display generation component and one or more sensors, and the computer system receives the following information: To detect the first event, In order to detect the first event, The system includes a command to display a customizable user interface that was not displayed before the detection of the first event, in accordance with the determination that a first criterion is met as a result of the first event, A computer-readable storage medium that displays the individual customizable user interfaces, which includes displaying a first customizable user interface configured according to a first set of customization parameters corresponding to the first identity of the charging source, based on the determination that one or more power transmission signals received from the charging source include first identification data representing a first identity of the charging source.

258. A computer system comprising a display generation component and one or more sensors, wherein the computer system is A means for detecting the first event, Means that are activated upon detection of the first event, The system includes means for displaying a separate, customizable user interface that was not displayed before the detection of the first event, which is activated in accordance with the determination that a first criterion is met as a result of the first event, A computer system that displays the individual customizable user interfaces, which includes displaying a first customizable user interface configured according to a first set of customization parameters corresponding to the first identity of the charging source, based on a determination that one or more power transmission signals received from the charging source include first identification data representing a first identity of the charging source.

259. An information processing device for use in a computer system including a display generation component and one or more sensors, wherein the information processing device is A means for detecting the first event, Means that are activated upon detection of the first event, The system includes means for displaying a separate, customizable user interface that was not displayed before the detection of the first event, which is activated in accordance with the determination that a first criterion is met as a result of the first event, Information processing device, which includes displaying the individual customizable user interfaces, in accordance with a determination that one or more power transmission signals received from the charging source include first identification data representing a first identity of the charging source, and which displays a first customizable user interface configured according to a first set of customization parameters corresponding to the first identity of the charging source.

260. A computer system comprising a display generation component and one or more sensors, wherein the computer system is One or more processors, A computer system comprising: a memory for storing one or more programs, wherein the one or more programs are configured to be executed by the one or more processors, and the one or more programs include instructions for performing the method according to any one of claims 241 to 255.

261. A computer-readable storage medium for storing one or more programs, wherein, when executed by a computer system including a display generation component and one or more sensors, the one or more programs include instructions causing the computer system to perform the method according to any one of claims 241 to 255.

262. A graphical user interface on a computer system comprising a display generation component and one or more sensors, wherein the computer system comprises a memory and one or more processors for executing one or more programs stored in the memory, and the graphical user interface comprises a user interface displayed according to the method of any one of claims 241 to 255.

263. A computer system comprising a display generation component and one or more sensors, wherein the computer system is A computer system comprising means for performing the method described in any one of claims 241 to 255.

264. An information processing device for use in a computer system including a display generation component and one or more sensors, wherein the information processing device is An information processing apparatus comprising means for performing the method described in any one of claims 241 to 255.

265. A computer system, Display generation components and, One or more sensors for detecting user input, A power transmission coil adapted to receive power transmission signals from a charging source, A rectifier adapted to charge the battery of the computer system using the power transmission signal received from the charging source by the power transmission coil, A communication circuit adapted to obtain identification data representing the individual identity of the charging source from at least one of the power transmission signals received from the charging source, One or more processors, The system includes a memory for storing instructions, and when an instruction is executed by one or more processors, the processors are provided with The first event is detected, In order to detect the first event, In accordance with the determination that the first criterion is met as a result of the first event, the system performs an action that includes displaying a separate customizable user interface that was not displayed before the first event was detected. A computer system that displays the individual customizable user interfaces, which includes displaying a first customizable user interface corresponding to the first identity of the charging source, based on a determination that one or more power transmission signals received from the charging source include first identification data representing the first identity of the charging source.

266. Displaying the individual customizable user interface that was not displayed before the detection of the first event is: The computer system according to claim 265, comprising displaying a second customizable user interface corresponding to the second identity of the charging source, based on a determination that one or more power transmission signals received from the charging source include second identification data representing a second identity different from the first identity of the charging source.

267. Displaying the individual customizable user interface that was not displayed before the detection of the first event is: The computer system according to claim 265 or 266, comprising: discontinuing the display of the first customizable user interface upon determination that identification data representing the identity of the charging source was not obtained from a power transmission signal received from the charging source; and displaying a third customizable user interface different from the first customizable user interface, wherein the third customizable user interface is configured according to a default set of customization parameters different from the first set of customization parameters.

268. Displaying the individual customizable user interface that was not displayed before the detection of the first event is: In accordance with the determination that the one or more power transmission signals include a first indication that the individual identifier of the charging source embedded in the one or more power transmission signals is a unique identifier of the charging source, the individual customizable user interface having customization based on the unique identifier is displayed. The computer system according to claim 265 or 267, comprising displaying the individual customizable user interface without customization based on the individual identifier, in accordance with the determination that the one or more power transmission signals include a second indication that the individual identifier of the charging source embedded in the one or more power transmission signals is not unique to the charging source.

269. The computer system according to any one of claims 265 to 267, wherein the first criterion requires that, in order for the first criterion to be satisfied, the charging source is coupled to the computer system, enabling the battery of the computer system to be charged by the charging source, and the computer system is in a first orientation.

270. The power transmission coil is configured to receive one or more power transmission signals from the charging source. The computer system according to any one of claims 265 to 269, wherein the communication circuit is adapted to decode the first identification data representing the first identity of the charging source from at least one of the one or more power transmission signals received from the charging source.

271. The computer system according to any one of claims 265 to 270, wherein the communication circuit is adapted to decode the first identification data representing the first identity of the charging source from data signals other than the one or more power transmission signals received from the charging source, and the data signals are not used to supply power to the computer system.

272. The computer system according to claim 271, wherein the power transmission coil is adapted to receive one or more power transmission signals, including the first identity data of the charging source, from the charging source during periods when the battery of the computer system is not being charged by the charging source.

273. The computer system according to any one of claims 265 to 272, wherein the communication circuit is adapted to decode the first identification data from one or more power transmission signals using a frequency shift keying decoder.

274. The aforementioned communication circuit is The computer system according to any one of claims 265 to 273, wherein the power transmission coil is adapted to send a request for identification data to the charging source before it receives the one or more power transmission signals, and the first identification data is transmitted to the computer system by the charging source in the one or more power transmission signals in response to the receipt of the request from the communication circuit.

275. The computer system according to claim 274, wherein the communication circuit is adapted to encode the request for identification data in individual power transmission signals using an amplitude shift keying encoder.

276. The computer system according to any one of claims 265 to 275, wherein the communication circuit is adapted to decode one or more power transmission signals carrying a payload, and the payload encodes an identifier of the charging source.

277. The computer system according to claim 276, wherein the communication circuit is adapted to decode the payload, and the payload includes the first portion encoding an indicator that specifies whether a second portion of the payload following a first portion includes a distinct identifier that uniquely corresponds to a distinct charging source.

278. The computer system according to claim 277, wherein the first portion of the payload has a length of one bit, and the second portion of the payload has a length of two or 31 bits.

279. The computer system according to any one of claims 276 to 278, wherein the communication circuit is adapted to decode the one or more power transmission signals that carry a header before the payload, the header indicating whether the one or more power transmission signals include a wireless power transmission transmitter identification packet according to the Wireless Power Consortium Qi charging protocol.

280. When the memory is executed by one or more processors, the processors will While displaying the individual customizable user interface, the system receives one or more user inputs that constitute a separate set of customization parameters for the individual customizable user interface. A computer system according to any one of claims 265 to 279, which stores instructions for causing an operation to be performed, which includes storing a separate set of customization parameters configured by one or more user inputs in relation to the separate identifier of the charging source, in accordance with the determination that the power transmission signal includes a separate identifier of the charging source that uniquely corresponds to the charging source.

281. When the memory is executed by one or more processors, the processors will After storing a separate set of customization parameters in relation to the separate identifier of the charging source, the computer system detects that the charging source has been disconnected and ceases displaying the separate customizable user interface configured according to one or more user inputs, The computer system detects that it has been disconnected from the charging source and has stopped displaying the individual customizable user interface configured according to one or more user inputs, and then detects a subsequent event, wherein the first criterion is met as a result of the subsequent event, The computer system according to claim 280, wherein, in response to detecting the aforementioned subsequent event, the computer system stores a command to perform an operation including: redisplaying the individual customizable user interface according to the respective set customization parameters stored in association with the individual identifier of the charging source, based on the determination that the computer system is coupled to an individual charging source and that an identifier encoded in one or more power transmission signals received from the individual charging source matches the individual identifier.

Images