Limited operation of electronic device

Abstract

The present disclosure relates to restricted operation of electronic devices. An electronic device changes a current user interface of a respective user interface type from a first user interface to a second user interface. A person uses their personal device to set up and configure another user's device.

Description

[0001] This application is a divisional application of patent application No. 202080005483.8, filed on May 5, 2020, entitled "Restricted Operation of Electronic Devices".

[0002] Cross-references to related applications

[0003] This patent application claims priority to U.S. Provisional Patent Application Serial No. 62 / 843,788 entitled “RESTRICTED OPERATION OF AN ELECTRONIC DEVICE”, filed May 6, 2019, and U.S. Patent Application Serial No. 62 / 856,032 entitled “RESTRICTED OPERATION OF AN ELECTRONIC DEVICE”, filed June 1, 2019, the contents of which are incorporated herein by reference in their entirety. Technical Field

[0004] This disclosure relates generally to computer user interfaces, and more specifically to techniques for restricted operating modes for electronic devices. Background Technology

[0005] With advancements in computer processing, memory, and display technologies, electronic devices have become capable of offering enhanced functionality. The reduction in size of electronic devices such as laptops, tablets, smartphones, and smartwatches has provided users with continued access to these devices and the capabilities they offer. Summary of the Invention

[0006] While increased access allows for greater productivity, entertainment, and communication, modern electronic devices can sometimes make it challenging for users to focus on tasks that don't require their use. For example, the ability to check email, search the internet, receive notifications, or engage in social media activities can divert a person's attention from the originally intended task when attending school, studying, working, or reading.

[0007] The following describes the characteristics of functions used to control electronic devices, where the devices operate according to a restricted operating mode, in which functions that the electronic devices could otherwise perform are not immediately available. The restricted mode provides limited functionality or information (e.g., time and date) while limiting other functions, thereby allowing the user to remain focused on the current task.

[0008] However, some technologies used to provide restricted operating modes for electronic devices are often cumbersome and inefficient. For example, some existing technologies use complex and time-consuming user interfaces that may involve multiple keystrokes or button presses. These existing technologies require more time than necessary, resulting in wasted user time and device power. For instance, existing technologies for activating, deactivating, exiting, and / or re-entering restricted modes are inefficient. This latter consideration is particularly important in battery-powered devices.

[0009] Therefore, this technology provides faster and more efficient methods and interfaces for restricted operating modes of electronic devices. Such methods and interfaces can optionally complement or replace other methods for restricted operating modes of electronic devices. These methods and interfaces reduce the cognitive burden on users and result in more efficient human-machine interfaces. For battery-powered computing devices, such methods and interfaces save power and increase the time interval between battery charging cycles.

[0010] According to some embodiments, a method includes: at an electronic device having a display device: displaying a first user interface of a corresponding user interface type of the electronic device via the display device, wherein the first user interface of the corresponding user interface type includes one or more elements in a first arrangement; detecting a sequence of one or more inputs corresponding to a request to change the current user interface of the corresponding user interface type of the electronic device; in response to detecting the sequence of one or more inputs corresponding to the request to change the current user interface of the corresponding user interface type of the electronic device, displaying a second user interface of the corresponding user interface type as the current user interface of the corresponding user interface type of the electronic device via the display device, wherein the second user interface of the corresponding user interface type includes one or more elements that are different from the one or more elements of the first user interface of the corresponding user interface type and / or are in an arrangement different from the first arrangement of the one or more elements of the first user interface of the corresponding user interface type; and changing the current user interface of the corresponding user interface type of the electronic device. After changing to the second user interface of the corresponding user interface type, the occurrence of a condition corresponding to the trigger of the current user interface of the corresponding user interface type for displaying the electronic device is detected; and in response to detecting the occurrence of the condition corresponding to the trigger of the current user interface of the corresponding user interface type for displaying the electronic device: based on determining that the current time corresponds to a predefined time range, a third user interface of the corresponding user interface type is displayed via the display device, the third user interface being different from the first user interface of the corresponding user interface type and the second user interface of the corresponding user interface type, wherein the third user interface of the corresponding user interface type includes a predefined set of elements, the predefined set of elements being different from one or more elements of the first user interface of the corresponding user interface type and one or more elements of the second user interface of the corresponding user interface type, and wherein the predefined set of elements cannot be changed in response to input detected at the electronic device; and based on determining that the current time does not correspond to the predefined time range, the second user interface of the corresponding user interface type is displayed.

[0011] According to some embodiments, a non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display device, the one or more programs including instructions for performing the following operations: displaying a first user interface of a corresponding user interface type of the electronic device via the display device, wherein the first user interface of the corresponding user interface type includes one or more elements in a first arrangement; detecting a sequence of one or more inputs corresponding to a request to change the current user interface of the corresponding user interface type of the electronic device; and, in response to detecting the sequence of one or more inputs corresponding to the request to change the current user interface of the corresponding user interface type of the electronic device, displaying a second user interface of the corresponding user interface type as the current user interface of the corresponding user interface type of the electronic device via the display device, wherein the second user interface of the corresponding user interface type includes one or more elements that are different from the one or more elements of the first user interface of the corresponding user interface type and / or are in an arrangement different from the first arrangement of the one or more elements of the first user interface of the corresponding user interface type; After changing the current user interface of the corresponding user interface type of the electronic device to the second user interface of the corresponding user interface type, the occurrence of a condition corresponding to the trigger for displaying the current user interface of the corresponding user interface type of the electronic device is detected; and in response to detecting the occurrence of the condition corresponding to the trigger for displaying the current user interface of the corresponding user interface type of the electronic device: based on determining that the current time corresponds to a predefined time range, a third user interface of the corresponding user interface type is displayed via the display device, the third user interface being different from the first user interface of the corresponding user interface type and the second user interface of the corresponding user interface type, wherein the third user interface of the corresponding user interface type includes a predefined set of elements, the predefined set of elements being different from one or more elements of the first user interface of the corresponding user interface type and one or more elements of the second user interface of the corresponding user interface type, and wherein the predefined set of elements cannot be changed in response to input detected at the electronic device; and based on determining that the current time does not correspond to the predefined time range, the second user interface of the corresponding user interface type is displayed.

[0012] According to some embodiments, a transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display device, the one or more programs including instructions for performing the following operations: displaying a first user interface of a corresponding user interface type of the electronic device via the display device, wherein the first user interface of the corresponding user interface type includes one or more elements in a first arrangement; detecting a sequence of one or more inputs corresponding to a request to change the current user interface of the corresponding user interface type of the electronic device; and, in response to detecting the sequence of one or more inputs corresponding to the request to change the current user interface of the corresponding user interface type of the electronic device, displaying a second user interface of the corresponding user interface type as the current user interface of the corresponding user interface type of the electronic device via the display device, wherein the second user interface of the corresponding user interface type includes one or more elements that are different from the one or more elements of the first user interface of the corresponding user interface type and / or are in an arrangement different from the first arrangement of the one or more elements of the first user interface of the corresponding user interface type; After changing the current user interface of the corresponding user interface type of the electronic device to the second user interface of the corresponding user interface type, the occurrence of a condition corresponding to the trigger for displaying the current user interface of the corresponding user interface type of the electronic device is detected; and in response to detecting the occurrence of the condition corresponding to the trigger for displaying the current user interface of the corresponding user interface type of the electronic device: based on determining that the current time corresponds to a predefined time range, a third user interface of the corresponding user interface type is displayed via the display device, the third user interface being different from the first user interface of the corresponding user interface type and the second user interface of the corresponding user interface type, wherein the third user interface of the corresponding user interface type includes a predefined set of elements, the predefined set of elements being different from one or more elements of the first user interface of the corresponding user interface type and one or more elements of the second user interface of the corresponding user interface type, and wherein the predefined set of elements cannot be changed in response to input detected at the electronic device; and based on determining that the current time does not correspond to the predefined time range, the second user interface of the corresponding user interface type is displayed.

[0013] According to some embodiments, an electronic device includes: a display device; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: displaying a first user interface of a corresponding user interface type of the electronic device via the display device, wherein the first user interface of the corresponding user interface type includes one or more elements in a first arrangement; detecting a sequence of one or more inputs corresponding to a request to change the current user interface of the corresponding user interface type of the electronic device; and, in response to detecting the sequence of one or more inputs corresponding to the request to change the current user interface of the corresponding user interface type of the electronic device, displaying a second user interface of the corresponding user interface type as the current user interface of the corresponding user interface type of the electronic device via the display device, wherein the second user interface of the corresponding user interface type includes one or more elements different from the one or more elements of the first user interface of the corresponding user interface type and / or in an arrangement different from the first arrangement of the one or more elements of the first user interface of the corresponding user interface type. Multiple elements; after changing the current user interface of the corresponding user interface type of the electronic device to the second user interface of the corresponding user interface type, detecting the occurrence of a condition corresponding to the trigger for displaying the current user interface of the corresponding user interface type of the electronic device; and in response to detecting the occurrence of the condition corresponding to the trigger for displaying the current user interface of the corresponding user interface type of the electronic device: based on determining that the current time corresponds to a predefined time range, displaying a third user interface of the corresponding user interface type via the display device, the third user interface being different from the first user interface of the corresponding user interface type and the second user interface of the corresponding user interface type, wherein the third user interface of the corresponding user interface type includes a predefined set of elements, the predefined set of elements being different from one or more elements of the first user interface of the corresponding user interface type and one or more elements of the second user interface of the corresponding user interface type, and wherein the predefined set of elements cannot be changed in response to input detected at the electronic device; and based on determining that the current time does not correspond to the predefined time range, displaying the second user interface of the corresponding user interface type.

[0014] According to some embodiments, an electronic device includes: a display device; means for displaying a first user interface of a corresponding user interface type of the electronic device via the display device, wherein the first user interface of the corresponding user interface type includes one or more elements in a first arrangement; means for detecting a sequence of one or more inputs corresponding to a request to change the current user interface of the corresponding user interface type of the electronic device; means for displaying a second user interface of the corresponding user interface type as the current user interface of the corresponding user interface type of the electronic device via the display device in response to detecting the sequence of one or more inputs corresponding to the request to change the current user interface of the corresponding user interface type of the electronic device, wherein the second user interface of the corresponding user interface type includes one or more elements that are different from the one or more elements of the first user interface of the corresponding user interface type and / or are in an arrangement different from the first arrangement of the one or more elements of the first user interface of the corresponding user interface type; and means for changing the current user interface of the corresponding user interface type of the electronic device. After the second user interface of the corresponding user interface type is changed, means for detecting the occurrence of a condition corresponding to the trigger of the current user interface of the corresponding user interface type for displaying the electronic device; means for performing the following operations in response to detecting the occurrence of a condition corresponding to the trigger of the current user interface of the corresponding user interface type for displaying the electronic device: displaying a third user interface of the corresponding user interface type via the display device, the third user interface being different from the first user interface of the corresponding user interface type and the second user interface of the corresponding user interface type, wherein the third user interface of the corresponding user interface type includes a predefined set of elements, the predefined set of elements being different from one or more elements of the first user interface of the corresponding user interface type and one or more elements of the second user interface of the corresponding user interface type, and wherein the predefined set of elements cannot be changed in response to input detected at the electronic device; and displaying the second user interface of the corresponding user interface type, the second user interface of the corresponding user interface type, based on the determination that the current time does not correspond to the predefined time range.

[0015] According to some embodiments, a method includes: at an electronic device having a display device: operating the electronic device in a first mode; and while operating the electronic device in the first mode: displaying a user interface of a corresponding user interface type via the display device; detecting a first sequence of one or more inputs corresponding to a request to exit the first mode, the first sequence of one or more inputs including at least one input detected while displaying the user interface of the corresponding user interface type; and after detecting at least one of the inputs in the first sequence of one or more inputs and before ceasing to operate the electronic device in the first mode, presenting an alarm indicating that information indicating the electronic device has exited the first mode will be reported to another user; after presenting the alarm, detecting a second sequence of one or more inputs; and in response to detecting the second sequence of one or more inputs and based on determining that the second sequence of one or more inputs corresponds to a request to exit the first mode, ceasing to operate the electronic device in the first mode.

[0016] According to some embodiments, a non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display device, the one or more programs including instructions for performing the following operations: operating the electronic device in a first mode; and, while operating the electronic device in the first mode: displaying a user interface of a corresponding user interface type via the display device; detecting a first sequence of one or more inputs corresponding to a request to exit the first mode, the first sequence of one or more inputs including at least one input detected while displaying the user interface of the corresponding user interface type; and, after detecting at least one of the inputs in the first sequence of one or more inputs and before ceasing to operate the electronic device in the first mode, presenting an alarm indicating that information indicating the electronic device has exited the first mode will be reported to another user; after presenting the alarm, detecting a second sequence of one or more inputs; and, in response to detecting the second sequence of one or more inputs and based on determining that the second sequence of one or more inputs corresponds to a request to exit the first mode, ceasing to operate the electronic device in the first mode.

[0017] According to some embodiments, a transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display device, the one or more programs including instructions for performing the following operations: operating the electronic device in a first mode; and, while operating the electronic device in the first mode: displaying a user interface of a corresponding user interface type via the display device; detecting a first sequence of one or more inputs corresponding to a request to exit the first mode, the first sequence of one or more inputs including at least one input detected while displaying the user interface of the corresponding user interface type; and, after detecting at least one of the inputs in the first sequence of one or more inputs and before ceasing to operate the electronic device in the first mode, presenting an alarm indicating that information indicating the electronic device has exited the first mode will be reported to another user; after presenting the alarm, detecting a second sequence of one or more inputs; and, in response to detecting the second sequence of one or more inputs and based on determining that the second sequence of one or more inputs corresponds to a request to exit the first mode, ceasing to operate the electronic device in the first mode.

[0018] According to some embodiments, an electronic device includes: a display device; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: operating the electronic device in a first mode; and, while operating the electronic device in the first mode: displaying a user interface of a corresponding user interface type via the display device; detecting a first sequence of one or more inputs corresponding to a request to exit the first mode, the first sequence of one or more inputs including at least one input detected while displaying the user interface of the corresponding user interface type; and, after detecting at least one of the inputs in the first sequence of one or more inputs and before ceasing to operate the electronic device in the first mode, presenting an alarm indicating that information indicating the electronic device has exited the first mode will be reported to another user; after presenting the alarm, detecting a second sequence of one or more inputs; and, in response to detecting the second sequence of one or more inputs and based on determining that the second sequence of one or more inputs corresponds to a request to exit the first mode, ceasing to operate the electronic device in the first mode.

[0019] According to some embodiments, an electronic device includes: a display device; means for operating the electronic device in a first mode; and means for performing the following operations when operating the electronic device in the first mode: displaying a user interface of a corresponding user interface type via the display device; detecting a first sequence of one or more inputs corresponding to a request to exit the first mode, the first sequence of one or more inputs including at least one input detected when displaying the user interface of the corresponding user interface type; and after detecting at least one of the inputs in the first sequence of one or more inputs and before stopping operating the electronic device in the first mode, presenting an alarm indicating that information indicating the electronic device has exited the first mode will be reported to another user; after presenting the alarm, detecting a second sequence of one or more inputs; and stopping operating the electronic device in the first mode in response to detecting the second sequence of one or more inputs and based on determining that the second sequence of one or more inputs corresponds to a request to exit the first mode.

[0020] According to some embodiments, a method includes, at a first device having a display device: displaying via the display device a setup user interface for setting up a setup process for a second device; while displaying the setup user interface via the display device, detecting a first user input selecting a corresponding account to be associated with the second device and simultaneously associating the first device with the first account; and after the corresponding account has been selected to be associated with the second device and during the setup process, displaying via the display device a setup user interface for configuring corresponding functions of the second device, including: based on determining that the first account has been selected to be associated with the second device, displaying via the display device one or more optional options associated with configuring the corresponding functions of the second device without explicitly identifying the user account associated with the second device; and based on determining that a second account different from the first account has been selected to be associated with the second device, displaying via the display device the one or more optional options associated with configuring the corresponding functions of the second device and simultaneously displaying an identifier explicitly identifying the second account.

[0021] According to some embodiments, a non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a first device having a display device, the one or more programs including instructions for performing the following operations: displaying a setup user interface via the display device for setting up a setup process for a second device; detecting, while displaying the setup user interface via the display device, a first user input selecting a corresponding account to be associated with the second device, and simultaneously associating the first device with the first account; and after the corresponding account has been selected to be associated with the second device and during the setup process, displaying a setup user interface via the display device for configuring corresponding functions of the second device, including: based on determining that the first account has been selected to be associated with the second device, displaying one or more optional options via the display device related to configuring the corresponding functions of the second device without explicitly identifying the user account associated with the second device; and based on determining that a second account different from the first account has been selected to be associated with the second device, displaying the one or more optional options via the display device related to configuring the corresponding functions of the second device and simultaneously displaying an identifier explicitly identifying the second account.

[0022] According to some embodiments, a transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a first device having a display device, the one or more programs including instructions for performing the following operations: displaying a setup user interface via the display device for setting up a setup process for a second device; detecting, while displaying the setup user interface via the display device, a first user input selecting a corresponding account to be associated with the second device, and simultaneously associating the first device with the first account; and after the corresponding account has been selected to be associated with the second device and during the setup process, displaying a setup user interface via the display device for configuring corresponding functions of the second device, including: based on determining that the first account has been selected to be associated with the second device, displaying one or more optional options via the display device related to configuring the corresponding functions of the second device without explicitly identifying the user account associated with the second device; and based on determining that a second account different from the first account has been selected to be associated with the second device, displaying the one or more optional options via the display device related to configuring the corresponding functions of the second device and simultaneously displaying an identifier explicitly identifying the second account.

[0023] According to some embodiments, a first device includes a display device; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: displaying a setup user interface via the display device for setting up a setup process for a second device; detecting, while displaying the setup user interface via the display device, a first user input selecting a corresponding account to be associated with the second device and simultaneously associating the first device with the first account; and after the corresponding account has been selected to be associated with the second device and during the setup process, displaying a setup user interface via the display device for configuring corresponding functions of the second device, including: based on determining that the first account has been selected to be associated with the second device, displaying one or more optional options via the display device for configuring the corresponding functions of the second device without explicitly identifying the user account associated with the second device; and based on determining that a second account different from the first account has been selected to be associated with the second device, displaying the one or more optional options via the display device for configuring the corresponding functions of the second device and simultaneously displaying an identifier that explicitly identifies the second account.

[0024] According to some embodiments, the first device includes a display device; means for displaying, via the display device, a setup user interface for setting up a setup process for a second device; means for detecting, while displaying the setup user interface via the display device, a first user input selecting a corresponding account to be associated with the second device, and simultaneously associating the first device with the first account; and means for displaying, via the display device, a setup user interface for configuring corresponding functions of the second device after the corresponding account has been selected to be associated with the second device and during the setup process, including: upon determining that the first account has been selected to be associated with the second device, displaying via the display device one or more optional options associated with configuring the corresponding functions of the second device without explicitly identifying the user account associated with the second device; and upon determining that a second account different from the first account has been selected to be associated with the second device, displaying via the display device the one or more optional options associated with configuring the corresponding functions of the second device and simultaneously displaying an identifier explicitly identifying the second account.

[0025] Executable instructions for performing these functions are optionally included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.

[0026] Therefore, faster and more efficient methods and interfaces are provided for providing restricted operating modes for electronic devices, thereby improving the effectiveness, efficiency, and user satisfaction of such devices. These methods and interfaces can complement or replace other methods used to provide restricted operating modes for electronic devices. Attached Figure Description

[0027] To better understand the various embodiments described, reference should be made to the following detailed description in conjunction with the accompanying drawings, wherein similar reference numerals indicate corresponding parts in all the drawings.

[0028] Figure 1A This is a block diagram illustrating a portable multi-functional device with a touch-sensitive display according to some embodiments.

[0029] Figure 1B This is a block diagram illustrating exemplary components for event handling according to some implementation schemes.

[0030] Figure 2 A portable multi-functional device with a touchscreen is shown according to some embodiments.

[0031] Figure 3 This is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface according to some implementation schemes.

[0032] Figure 4A An exemplary user interface for a menu on an application on a portable multifunction device, according to some implementation schemes, is shown.

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

[0034] Figure 5A A personal electronic device according to some implementation schemes is shown.

[0035] Figure 5B This is a block diagram illustrating a personal electronic device according to some implementation schemes.

[0036] Figures 5C-5D Exemplary components of a personal electronic device having a touch-sensitive display and an intensity sensor according to some embodiments are shown.

[0037] Figures 5E-5H Exemplary components and user interfaces of a personal electronic device according to some implementation schemes are shown.

[0038] Figures 6A to 6AC An exemplary user interface for operating an electronic device is shown according to some implementation schemes.

[0039] Figure 7 Exemplary methods according to some implementation schemes are shown.

[0040] Figure 8 Exemplary methods according to some implementation schemes are shown.

[0041] Figures 9A to 9A1 An exemplary user interface for configuring a second electronic device is shown according to some implementation schemes.

[0042] Figure 10 An exemplary method for configuring a second electronic device according to some implementation schemes is shown. Detailed Implementation

[0043] The following description illustrates exemplary methods, parameters, etc. However, it should be understood that such description is not intended to limit the scope of this disclosure, but is provided as a description of exemplary embodiments.

[0044] Electronic devices require efficient methods and interfaces for implementing restricted operating modes. For example, when in restricted mode, functions that the electronic device could otherwise perform are not immediately available. A defined timeframe for scheduling electronic devices (or optionally, multiple electronic devices associated with a shared account) to operate in restricted mode is defined. For example, parents can set a predefined timeframe during which devices used by their children will operate in restricted mode (e.g., a daily school schedule). Techniques for activating (e.g., manually activating) restricted mode when it is not otherwise scheduled are also described. In some implementations, when in restricted mode, a user can initiate a process (at least temporarily) on the electronic device to exit (e.g., unlock, leave, deactivate) the restricted mode. Exiting restricted mode during a predefined timeframe can cause a report to appear on another device. For example, if a student exits restricted mode during school hours, a notification will appear on the student's parent's device (e.g., in a report log on the parent's phone).

[0045] Such technologies can reduce the cognitive burden on users operating devices in restricted modes, thereby increasing productivity. Furthermore, they can reduce processor and battery power that would otherwise be wasted on redundant user input.

[0046] under, Figures 1A to 1B , Figure 2 , Figure 3 , Figures 4A to 4B and Figures 5A to 5H Description of exemplary devices for performing techniques for restricted operating modes, according to some implementation schemes, is provided. Figures 6A to 6AC An exemplary user interface for a restricted operating mode is shown according to some implementation schemes. Figures 7 to 8 This is a flowchart illustrating a method for a restricted operating mode according to some implementation schemes. Figures 6A to 6AC The user interface is used to illustrate the processes described below, including... Figures 7 to 8 The process in. Figures 9A to 9A1 An exemplary user interface for configuring a second device is shown according to some implementation schemes. Figure 10 This is a flowchart illustrating a method for configuring a second device according to some implementation schemes. Figures 9A to 9A1 The user interface in the document is used to display including Figure 10 The process described below is the process in the middle.

[0047] Although the following description uses the terms "first," "second," etc., to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch may be named a second touch and similarly, a second touch may be named a first touch, without departing from the scope of the various described embodiments. Both the first touch and the second touch are touches, but they are not the same touch.

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

[0049] Depending on the context, the term "if" may optionally be interpreted as meaning "when," "at," or "in response to determination" or "in response to detection." Similarly, depending on the context, the phrases "if determination..." or "if detection [the stated condition or event]" may optionally be interpreted as meaning "in response to determination..." or "in response to detection [the stated condition or event]."

[0050] This document describes implementations of electronic devices, user interfaces for such devices, and related processes for using such devices. In some implementations, the device is a portable communication device, such as a mobile phone, that also includes other functions such as PDA and / or music player functionality. Exemplary implementations of portable multi-functional devices include, but are not limited to, those from Apple Inc. (Cupertino, California). Devices, iPod Equipment, and Device. Optionally, other portable electronic devices may be used, such as laptops or tablets with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads).

[0051] In the following discussion, an electronic device including a display and a touch-sensitive surface is described. However, it should be understood that the electronic device may optionally include one or more other physical user interface devices, such as a physical keyboard, mouse, and / or joystick.

[0052] The device typically supports a variety of applications, such as one or more of the following: drawing applications, presentation applications, word processing applications, website creation applications, disk editing applications, spreadsheet applications, game applications, phone applications, video conferencing applications, email applications, instant messaging applications, fitness support applications, photo management applications, digital camera applications, digital video camcorder applications, web browsing applications, digital music player applications, and / or digital video player applications.

[0053] Various applications running on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and the corresponding information displayed on the device are optionally adjusted and / or varied for different applications, and / or adjusted and / or varied within the respective applications. In this way, the device's common physical architecture (such as the touch-sensitive surface) optionally utilizes a user interface that is intuitive and clear to the user to support various applications.

[0054] Now let’s turn our attention to implementation schemes for portable devices with touch-sensitive displays. Figure 1A This is a block diagram illustrating a portable multi-functional device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display 112 is sometimes referred to as a “touchscreen” for convenience, and is sometimes referred to as or called a “touch-sensitive display system.” Device 100 includes a memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input 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 contact strength sensors 165 for detecting the intensity of contact on device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more haptic output generators 167 for generating haptic output on device 100 (e.g., generating haptic output on a touch-sensitive surface 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.

[0055] As used in this specification and claims, the term "intensity" of contact on a tactile surface refers to the force or pressure (force per unit area) of a contact (e.g., finger contact) on a tactile surface, or to a substitute (alternative) for the force or pressure of a contact on a tactile surface. The intensity of contact has a range of values ​​that includes at least four different values ​​and more typically hundreds of different values ​​(e.g., at least 256). The intensity of contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the tactile surface are optionally used to measure the force at different points on the tactile surface. In some embodiments, force measurements from multiple force sensors are combined (e.g., weighted average) to determine the estimated contact force. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the tactile surface. Alternatively, the size and / or variation of the contact area detected on the touch-sensitive surface, the capacitance and / or variation of the touch-sensitive surface near the contact, and / or the resistance and / or variation of the touch-sensitive surface near the contact may optionally be used as substitutes for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether an intensity threshold (e.g., the intensity threshold is described in units corresponding to the substitute measurement) has been exceeded. In some embodiments, the substitute measurement of the contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold (e.g., the intensity threshold is a pressure threshold measured in units of pressure) has been exceeded. Using the intensity of the contact as an attribute of user input allows the user to access additional device functions that would otherwise be inaccessible to the user on smaller devices with limited physical space, such smaller devices being used (e.g., on a touch-sensitive display) to display power indications and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls, such as knobs or buttons).

[0056] As used in this specification and claims, the term "haptic output" refers to a physical displacement of the device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., the housing), or a displacement of a component relative to the center of mass of the device, which is detected by the user using the user's tactile sense. For example, when the device or a component of the device comes into contact with a touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in the physical characteristics of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or touchpad) may optionally be interpreted by the user as a "press-click" or "release-click" on a physically actuated button. In some cases, the user will feel a tactile sensation, such as a "press-click" or "release-click," even when a physically actuated button associated with a touch-sensitive surface that has been physically pressed (e.g., displaced) by the user's movement does not move. For example, even when the smoothness of the tactile surface remains unchanged, the movement of the tactile surface can optionally be interpreted or sensed by the user as the "roughness" of the tactile surface. While such interpretations of touch by users will be limited by the individualized sensory perceptions of the user, many sensory perceptions of touch are common to most users. Therefore, when a tactile output is described as corresponding to a specific sensory perception of a user (e.g., "press click", "release click", "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or its components that will generate the sensory perception of a typical (or ordinary) user.

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

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

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

[0060] RF (Radio Frequency) circuit 108 receives and transmits RF signals, also known as electromagnetic signals. RF circuit 108 converts electrical signals into electromagnetic signals and vice versa, and communicates with communication networks and other communication devices via these electromagnetic signals. RF circuit 108 optionally includes well-known circuitry for performing these functions, including but 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, memory, etc. RF circuit 108 optionally communicates wirelessly with networks and other devices, 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)). RF circuit 108 optionally includes well-known circuitry for detecting near-field communication (NFC) fields, such as via near-field communication radio components. Wireless communication may optionally employ any of a variety of communication standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High-Speed ​​Downlink Packet Access (HSDPA), High-Speed ​​Uplink Packet Access (HSUPA), Evolution, Pure Data (EV-DO), HSPA, HSPA+, Dual-Unit HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), and Wi-Fi (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE...). 802.11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (e.g., Internet Messaging 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 with Extended Utility (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol that has not been developed as of the date of this document submission.

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

[0062] I / O subsystem 106 couples input / output peripherals on device 100, such as touchscreen 112 and other input control devices 116, to peripheral interface 118. I / O subsystem 106 optionally includes display controller 156, optical sensor controller 158, depth camera controller 169, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive electrical signals from / send electrical signals to the other input control device 116. The other input control device 116 optionally includes physical buttons (e.g., push-buttons, rocker buttons, etc.), dial pads, slide switches, joysticks, click dials, etc. In some alternative embodiments, input controller 160 is optionally coupled to (or not coupled to) any of the following: keyboard, infrared port, USB port, and pointing device such as mouse. One or more buttons (e.g., Figure 2 Optionally, 208) includes an increase / decrease button for volume control of speaker 111 and / or microphone 113. The one or more buttons optionally include a push-button (e.g., Figure 2 (206 in the middle).

[0063] A quick press of the push button optionally disengages the touchscreen 112 from its lock or optionally initiates a process of unlocking the device using gestures on the touchscreen, as described in U.S. Patent Application 11 / 322,549 (i.e., U.S. Patent No. 7,657,849), filed December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image," the entire contents of which are incorporated herein by reference. A long press of the push button (e.g., 206) optionally powers the device 100 on or off. The function of one or more buttons is optionally user-customizable. The touchscreen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

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

[0065] Touchscreen 112 has a touch-sensitive surface, sensor, or sensor array that accepts input from a user based on tactile and / or haptic contact. Touchscreen 112 and display controller 156 (along with any associated modules and / or instruction set in memory 102) detect contact on touchscreen 112 (and any movement or interruption of that contact) 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 touchscreen 112. In an exemplary embodiment, the contact point between touchscreen 112 and the user corresponds to the user's finger.

[0066] Touchscreen 112 optionally employs 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. Touchscreen 112 and display controller 156 optionally employ any of a variety of touch sensing technologies now known or to be developed hereafter, along with other proximity sensor arrays or other elements for determining one or more points of contact with touchscreen 112, to detect contact and any movement or interruption thereof. These various touch sensing technologies include, but are not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that from Apple Inc. (Cupertino, California). and iPod The technology used.

[0067] In some embodiments of the touchscreen 112, the touch-sensitive display optionally resembles a multi-touch-sensitive touchpad described in the following U.S. patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman) and / or U.S. Patent Publication 2002 / 0015024A1, each of which is incorporated herein by reference in its entirety. However, the touchscreen 112 displays visual output from the device 100, while the touch-sensitive touchpad does not provide visual output.

[0068] In some embodiments, the touchscreen 112 has a touch-sensitive display as described in the following patent applications: (1) U.S. Patent Application No. 11 / 381,313, filed May 2, 2006, entitled “Multipoint Touch Surface Controller”; (2) U.S. Patent Application No. 10 / 840,862, filed May 6, 2004, entitled “Multipoint Touchscreen”; (3) U.S. Patent Application No. 10 / 903,964, filed July 30, 2004, entitled “Gestures For Touch Sensitive Input Devices”; (4) U.S. Patent Application No. 11 / 048,264, filed January 31, 2005, entitled “Gestures For Touch Sensitive Input Devices”; and (5) U.S. Patent Application No. 18, 2005, entitled “Mode-Based Graphical User Interfaces For Touch Sensitive”. (6) U.S. Patent Application No. 11 / 038,590 entitled “Input Devices”; (7) U.S. Patent Application No. 11 / 228,758 entitled “Virtual Input Device Placement On A Touch Screen User Interface”, filed September 16, 2005; (8) U.S. Patent Application No. 11 / 228,700 entitled “Operation Of A Computer With A Touch Screen Interface”, filed September 16, 2005; (9) U.S. Patent Application No. 11 / 228,737 entitled “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard”, filed September 16, 2005; and (10) U.S. Patent Application No. 11 / 367,749 entitled “Multi-Functional Hand-Held Device”, filed March 3, 2006. The full text of all these applications is incorporated herein by reference.

[0069] Touchscreen 112 optionally has a video resolution exceeding 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. Users optionally interact with touchscreen 112 using any suitable object or accessory such as a stylus, finger, etc. In some embodiments, the user interface is designed to operate primarily through 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. In some embodiments, the device translates coarse finger-based input into precise pointer / cursor positions or commands to perform the user-desired actions.

[0070] In some embodiments, in addition to the touchscreen, 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 visual output. Optionally, the touchpad is a touch-sensitive surface separate from the touchscreen 112, or an extension of the touch-sensitive surface formed by the touchscreen.

[0071] The device 100 also includes a power system 162 for supplying power to various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, a power fault detection circuit, a power converter or inverter, a power status indicator (e.g., light-emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power in the portable device.

[0072] The device 100 may optionally also include one or more optical sensors 164. Figure 1AAn optical sensor 164 is shown coupled to an optical sensor controller 158 in the I / O subsystem 106. The optical sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The optical sensor 164 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with an imaging module 143 (also called a camera module), the optical sensor 164 optionally captures still images or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite to a touchscreen display 112 on the front of the device, allowing the touchscreen display to be used as a viewfinder for still image and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device, allowing images of the user to be optionally acquired for video conferencing while the user views other video conferencing participants on the touchscreen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lenses and sensor within the device housing), allowing a single optical sensor 164 to be used in conjunction with the touchscreen display for both video conferencing and still image and / or video image acquisition.

[0073] The device 100 optionally also includes one or more depth camera sensors 175. Figure 1A A depth camera sensor is shown coupled to a depth camera controller 169 in I / O subsystem 106. Depth camera sensor 175 receives data from the environment to create a 3D model of an object (e.g., a face) within the scene from a viewpoint (e.g., the depth camera sensor). In some embodiments, in conjunction with imaging module 143 (also referred to as a camera module), depth camera sensor 175 may optionally be used to determine depth maps of different portions of an image captured by imaging module 143. In some embodiments, the depth camera sensor is located at the front of device 100, such that user images with depth information are optionally acquired for video conferencing while the user views other video conferencing participants on a touchscreen display, and selfies with depth map data are captured. In some embodiments, depth camera sensor 175 is located at the rear of the device, or both the rear and front of device 100. In some embodiments, the position of depth camera sensor 175 may be changed by the user (e.g., by rotating a lens and sensor within the device housing), such that depth camera sensor 175 is used in conjunction with a touchscreen display for both video conferencing and still image and / or video image acquisition.

[0074] In some implementations, the depth map (e.g., a depth map image) contains information (e.g., values) relating to the distance of objects in the scene from the viewpoint (e.g., a camera, optical sensor, depth camera sensor). In one implementation of the depth map, each depth pixel defines the location of its corresponding two-dimensional pixel on the Z-axis of the viewpoint. In some implementations, the depth map consists of pixels, where each pixel is defined by a value (e.g., 0 to 255). For example, a "0" value represents the pixel furthest from the viewpoint (e.g., a camera, optical sensor, depth camera sensor) in the "3D" scene, and a "255" value represents the pixel closest to the viewpoint in the "3D" scene. In other implementations, the depth map represents the distance between objects in the scene and the plane of the viewpoint. In some implementations, the depth map includes information about the relative depth of various features of the object of interest within the field of view of the depth camera (e.g., the relative depth of the eyes, nose, mouth, and ears of a user's face). In some implementations, the depth map includes information that enables the device to determine the contour of the object of interest in the z-direction.

[0075] The device 100 may optionally also include one or more contact strength sensors 165. Figure 1A A contact strength sensor is shown coupled to a strength sensor controller 159 in I / O subsystem 106. The contact strength sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electro-force sensors, piezoelectric sensors, optical force sensors, capacitive touch-sensitive surfaces, or other strength sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). The contact strength sensor 165 receives contact strength information (e.g., pressure information or a substitute for pressure information) from the environment. In some embodiments, at least one contact strength sensor is arranged juxtaposed with or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact strength sensor is located on the rear of device 100, opposite to the touchscreen display 112 located on the front of device 100.

[0076] The device 100 optionally also includes one or more proximity sensors 166. Figure 1AA proximity sensor 166 coupled to a peripheral device interface 118 is shown. Alternatively, the proximity sensor 166 may optionally be coupled to an input controller 160 in an I / O subsystem 106. The proximity sensor 166 may optionally perform as described in the following U.S. patent applications: No. 11 / 241,839, entitled "Proximity Detector In Handheld Device"; No. 11 / 240,788, entitled "Proximity Detector In Handheld Device"; No. 11 / 620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output"; No. 11 / 586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and No. 11 / 638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals", the entire contents of which are incorporated herein by reference. In some implementations, the proximity sensor is turned off and the touchscreen 112 is disabled when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

[0077] The device 100 may optionally also include one or more tactile output generators 167. Figure 1AA haptic output generator coupled to a haptic feedback controller 161 in I / O subsystem 106 is shown. The haptic output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components; and / or electromechanical devices for converting energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other haptic output generating components (e.g., components for converting electrical signals into haptic outputs on the device). A contact intensity sensor 165 receives haptic feedback generation instructions from a haptic feedback module 133 and generates a haptic output on device 100 that can be felt by a user of device 100. In some embodiments, at least one haptic output generator is juxtaposed or adjacent to a haptic surface (e.g., haptic display system 112) and optionally generates the haptic output by moving the haptic surface vertically (e.g., in / outward from the surface of device 100) or laterally (e.g., backward and forward in the same plane as the surface of device 100). In some embodiments, at least one haptic output generator sensor is located on the rear of the device 100, opposite to the touch screen display 112 located on the front of the device 100.

[0078] The device 100 may optionally also include one or more accelerometers 168. Figure 1A An accelerometer 168 coupled to a peripheral device interface 118 is shown. Alternatively, the accelerometer 168 may be coupled to an input controller 160 in an I / O subsystem 106. The accelerometer 168 may optionally perform as described in the following U.S. patent publications: U.S. Patent Publication No. 20050190059, entitled "Acceleration-based Theft Detection System for Portable Electronic Devices" and U.S. Patent Publication No. 20060017692, entitled "Methods and Apparatuses For Operating A Portable Device Based On An Accelerometer," both of which are incorporated herein by reference in their entirety. In some embodiments, information is displayed on a touchscreen display in portrait or landscape view based on analysis of data received from one or more accelerometers. Device 100 may optionally include, in addition to the accelerometer 168, a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for acquiring information about the location and orientation (e.g., portrait or landscape) of device 100.

[0079] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a Global Positioning System (GPS) module (or instruction set) 135, and an application program (or instruction set) 136. Furthermore, in some embodiments, memory 102 ( Figure 1A ) or 370 ( Figure 3 Storage device / global internal state 157, such as Figure 1A and Figure 3 As shown in the figure. Device / global internal state 157 includes one or more of the following: active application state, which indicates which applications (if any) are currently active; display state, which indicates what applications, views or other information occupy various areas of the touch screen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and position information about the device's position and / or orientation.

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

[0081] The communication module 128 facilitates communication with other devices via one or more external ports 124 and includes various software components for processing data received by the RF circuitry 108 and / or the external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) are adapted to be directly coupled to other devices or indirectly coupled via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is connected to… (Trademark of Apple Inc.) The same or similar and / or compatible multi-pin (e.g., 30-pin) connectors used in Apple Inc. devices.

[0082] The contact / motion module 130 optionally detects contact with the touchscreen 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., touchpads or physical click-based rotary dials). The contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether a contact has occurred (e.g., detecting a finger press event), determining the contact intensity (e.g., the force or pressure of the contact, or an alternative to force or pressure), determining whether there is movement of the contact and tracking movement on the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has stopped (e.g., detecting a finger lift event or a contact break). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point optionally includes determining the rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of which is represented by a series of contact data. These operations are optionally applied to single-point contact (e.g., single-finger contact) or multi-point simultaneous contact (e.g., "multi-touch" / multiple-finger contact). In some implementations, the contact / motion module 130 and the display controller 156 detect contact on the touchpad.

[0083] In some implementations, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., determining whether the user has “clicked” an icon). In some implementations, at least a subset of the intensity thresholds is determined based on software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a specific physical actuator and can be adjusted without changing the physical hardware of device 100). For example, the mouse “click” threshold of a touchpad or touchscreen can be set to any threshold in a wide range of predefined thresholds without changing the touchpad or touchscreen display hardware. Additionally, in some specific implementations, the user of the device is provided with software settings for adjusting one or more intensity thresholds in a set (e.g., by adjusting the individual intensity thresholds and / or by adjusting multiple intensity thresholds at once using system-level clicks on the “intensity” parameter).

[0084] The touch / motion module 130 optionally detects gesture input performed by the user. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different movements, timings, and / or intensities of the detected contact). Therefore, gestures are optionally detected by detecting specific contact patterns. For example, detecting a finger tap gesture includes detecting a finger press event and then detecting a finger lift-off (lift-away) event at the same (or substantially the same) location as the finger press event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on a touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and subsequently detecting a finger lift-off (lift-away) event.

[0085] The graphics module 132 includes various known software components for rendering and displaying graphics on the touchscreen 112 or other display, including components for altering the visual impact of the displayed graphics (e.g., brightness, transparency, saturation, contrast, or other visual properties). As used herein, the term "graphics" includes any object that can be displayed to a user, and non-limitingly includes text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

[0086] In some implementations, 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 to specify the graphic to be displayed, and, if necessary, also receives coordinate data and other graphic attribute data, and then generates screen image data for output to the display controller 156.

[0087] The haptic feedback module 133 includes various software components for generating instructions which are used by the haptic output generator 167 to generate haptic output at one or more locations on the device 100 in response to user interaction with the device 100.

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

[0089] GPS module 135 determines the location of the device and provides that information for use in various applications (e.g., to phone 138 for use in location-based dialing; to camera 143 as image / video metadata; and to applications that provide location-based services, such as weather desktop apps, local yellow pages desktop apps, and map / navigation desktop apps).

[0090] Application 136 optionally includes the following modules (or instruction sets) or subsets or supersets thereof:

[0091] • Contacts module 137 (sometimes called address book or contact list);

[0092] • Telephone module 138;

[0093] • Video conferencing module 139;

[0094] • Email client module 140;

[0095] • Instant Messaging (IM) module 141;

[0096] Fitness support module 142;

[0097] • Camera module 143 for still images and / or video images;

[0098] • Image management module 144;

[0099] • Video player module;

[0100] Music player module;

[0101] • Browser module 147;

[0102] • Calendar module 148;

[0103] • Desktop mini-program module 149, which optionally includes one or more of the following: weather desktop mini-program 149-1, stock market desktop mini-program 149-2, calculator desktop mini-program 149-3, alarm clock desktop mini-program 149-4, dictionary desktop mini-program 149-5, and other desktop mini-programs obtained by the user, and desktop mini-programs created by the user 149-6;

[0104] • Desktop app creator module 150 for creating user-created desktop apps 149-6;

[0105] • Search module 151;

[0106] • Video and music player module 152, which combines a video player module and a music player module;

[0107] • Notepad module 153;

[0108] • Map module 154; and / or

[0109] • Online video module 155.

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

[0111] In conjunction with the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the contact module 137 is optionally used to manage an address book or contact list (e.g., in the application internal state 192 of the contact module 137 stored in memory 102 or memory 370), including: adding one or more names to the address book; deleting names from the address book; associating phone numbers, email addresses, physical addresses, or other information with names; associating images with names; categorizing and classifying names; providing phone numbers or email addresses to initiate and / or facilitate communications via telephone 138, video conferencing module 139, email 140, or IM 141; and so on.

[0112] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, telephone module 138 is optionally used to input character sequences corresponding to telephone numbers, access one or more telephone numbers in contact module 137, modify entered telephone numbers, dial corresponding telephone numbers, initiate conversations, and disconnect or hang up when a conversation is completed. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

[0113] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contact module 137, and telephone module 138, video conferencing module 139 includes executable instructions to initiate, conduct, and terminate video conferences between the user and one or more other participants based on user instructions.

[0114] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, email client module 140 includes executable instructions for creating, sending, receiving, and managing emails in response to user commands. Combined with image management module 144, email client module 140 makes it very easy to create and send emails containing still images or video images captured by camera module 143.

[0115] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for: inputting a character sequence corresponding to an instant message, modifying previously input characters, transmitting a corresponding instant message (e.g., using Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocols for telephone-based instant messaging or using XMPP, SIMPLE, or IMPS for internet-based instant messaging), receiving an instant message, and viewing a received instant message. In some embodiments, the transmitted and / or received instant messages optionally include graphics, photographs, audio files, video files, and / or other attachments supported in MMS and / or Enhanced Messaging Services (EMS). As used herein, "instant message" 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, or IMPS).

[0116] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, fitness support module 142 includes executable instructions for creating fitness activities (e.g., with time, distance, and / or calorie burning goals); communicating with fitness sensors (executive devices); receiving fitness sensor data; calibrating sensors used to monitor fitness; selecting and playing music for fitness activities; and displaying, storing, and transmitting fitness data.

[0117] In conjunction with the touchscreen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion 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, or deleting still images or videos from memory 102.

[0118] Incorporating the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and camera module 143, the image management module 144 includes executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, tagging, deleting, presenting (e.g., in a digital slideshow or album), and storing still images and / or video images.

[0119] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions for browsing the Internet according to user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as links to attachments and other files on web pages.

[0120] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and associated data (e.g., calendar entries, to-dos, etc.) according to user instructions.

[0121] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, desktop applet module 149 is optionally a micro-application downloaded and used by a user (e.g., weather desktop applet 149-1, stock market desktop applet 149-2, calculator desktop applet 149-3, alarm clock desktop applet 149-4, and dictionary desktop applet 149-5) or a user-created micro-application (e.g., user-created desktop applet 149-6). In some embodiments, the desktop applet includes HTML (Hypertext Markup Language) files, CSS (Cascading Style Sheets) files, and JavaScript files. In some embodiments, the desktop applet includes XML (Extensible Markup Language) files and JavaScript files (e.g., Yahoo! desktop applet).

[0122] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, the desktop applet creator module 150 can optionally be used by the user to create desktop applets (e.g., converting user-specified portions of a webpage into desktop applets).

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

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

[0125] Combining the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the notepad module 153 includes executable instructions for creating and managing notes, to-do items, etc., according to user instructions.

[0126] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 is optionally used to receive, display, modify, and store maps and map-related data (e.g., driving directions, data related to shops and other points of interest at or near a specific location, and other location-based data) according to user instructions.

[0127] Incorporating touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, the online video module 155 includes instructions for performing the following actions: allowing users to access, browse, receive (e.g., via streaming and / or downloading), play back (e.g., on the touchscreen or on an external display connected via external port 124), send emails with links to specific online videos, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, an instant messaging module 141 is used instead of the email client module 140 to send links to specific online videos. Further descriptions of the online video application can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed June 20, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968,067, filed December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are incorporated herein by reference in their entirety.

[0128] Each of the above modules and applications corresponds to an executable instruction set for performing one or more of the functions described above and the methods described in this patent application (e.g., computer-implemented methods and other information processing methods as described herein). These modules (e.g., instruction sets) need not be implemented as separate software programs, processes, or modules; therefore, various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. For example, a video player module may optionally be combined with a music player module into a single module (e.g., Figure 1A (e.g., video and music player module 152). In some embodiments, memory 102 optionally stores subgroups of the aforementioned modules and data structures. Additionally, memory 102 optionally stores other modules and data structures not described above.

[0129] In some implementations, device 100 is a device on which the operation of a predefined set of functions is performed solely via a touchscreen and / or touchpad. By using a touchscreen and / or touchpad as the primary input control device for operating device 100, the number of physical input control devices (e.g., push-buttons, dials, etc.) on device 100 can be optionally reduced.

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

[0131] Figure 1B This is a block diagram illustrating exemplary components for event processing according to some embodiments. In some embodiments, memory 102 ( Figure 1A ) or memory 370 ( Figure 3 This includes an event classifier 170 (e.g., in operating system 126) and a corresponding application 136-1 (e.g., any one of the aforementioned applications 137 to 151, 155, 380 to 390).

[0132] Event classifier 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which the event information should be delivered. Event classifier 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates one or more current application views displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device / global internal state 157 is used by event classifier 170 to determine which application(s) is currently active, and application internal state 192 is used by event classifier 170 to determine the application view 191 to which the event information should be delivered.

[0133] In some implementations, the application internal state 192 includes additional information such as one or more of the following: recovery information to be used when the application 136-1 resumes execution, user interface state information indicating that information is being displayed or ready to be displayed by the application 136-1, a state queue for enabling the user to return to the previous state or view of the application 136-1, and a repeat / undo queue for the user's previous actions.

[0134] Event monitor 171 receives event information from peripheral device interface 118. The event information includes information about sub-events (e.g., user touches on touch-sensitive display 112 as part of a multi-touch gesture). Peripheral device interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, one or more accelerometers 168, and / or microphone 113 (via audio circuitry 110). The information received by peripheral device interface 118 from I / O subsystem 106 includes information from touch-sensitive display 112 or touch-sensitive surfaces.

[0135] In some implementations, event monitor 171 sends requests to peripheral device interface 118 at predetermined intervals. In response, peripheral device interface 118 transmits event information. In other implementations, peripheral device interface 118 transmits event information only when a significant event occurs (e.g., receiving input above a predetermined noise threshold and / or receiving input for a predetermined duration).

[0136] In some implementations, the event classifier 170 also includes a hit view determination module 172 and / or an activity event recognizer determination module 173.

[0137] When the touch-sensitive display 112 displays more than one view, the hit view determination module 172 provides a software process for determining where a sub-event has occurred within one or more views. A view consists of controls and other elements that the user can see on the display.

[0138] 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 the corresponding application) in which a touch is detected optionally corresponds to a procedural level within the application's procedural or view hierarchy. For example, the lowest-level view in which a touch is detected is optionally referred to as the hit view, and the set of events identified as correct input is optionally determined at least in part based on the hit view of the initial touch that initiates a touch-based gesture.

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

[0140] The activity event recognizer determination module 173 determines which views(s) within the view hierarchy should receive a specific sub-event sequence. In some embodiments, the activity event recognizer determination module 173 determines that only the hit view should receive the specific sub-event sequence. In other embodiments, the activity event recognizer determination module 173 determines that all views including the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive the specific sub-event sequence. In other embodiments, even if the touch sub-event is entirely confined to the area associated with a particular view, higher views in the hierarchy will still remain actively participating views.

[0141] Event assigner module 174 assigns event information to event identifiers (e.g., event identifier 180). In embodiments that include active event identifier determination module 173, event assigner module 174 delivers event information to the event identifier determined by active event identifier determination module 173. In some embodiments, event assigner module 174 stores event information in an event queue, which is retrieved by the corresponding event receiver 182.

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

[0143] In some implementations, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events occurring within a corresponding view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a corresponding application view 191 includes a plurality of event recognizers 180. In other implementations, one or more of the event recognizers 180 are part of a separate module, such as a user interface toolkit or a higher-level object from which application 136-1 inherits methods and other properties. In some implementations, a corresponding event handler 190 includes one or more of the following: a data updater 176, an object updater 177, a GUI updater 178, and / or event data 179 received from an event classifier 170. Event handlers 190 optionally utilize or invoke the data updater 176, the object updater 177, or the GUI updater 178 to update the application's internal state 192. Alternatively, one or more application views in application view 191 include one or more corresponding event handlers 190. Additionally, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in the corresponding application view 191.

[0144] The corresponding event recognizer 180 receives event information (e.g., event data 179) from the event classifier 170 and identifies the event based on the event information. The event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, the event recognizer 180 also includes at least one subset of metadata 183 and event delivery instructions 188 (which optionally include sub-event delivery instructions).

[0145] Event receiver 182 receives event information from event classifier 170. The event information includes information about sub-events, such as touch or touch movement. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves touch movement, the event information optionally also includes the rate and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another (e.g., from a longitudinal orientation to a lateral orientation, or vice versa), and the event information includes corresponding information about the device's current orientation (also referred to as device orientation).

[0146] Event comparator 184 compares event information with predefined event or sub-event definitions and determines the event or sub-event based on the comparison, or determines or updates the state of the event or sub-event. In some embodiments, event comparator 184 includes event definition 186. Event definition 186 contains definitions of events (e.g., predefined sequences of sub-events), such as event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in event (187) include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, event 1 (187-1) is defined as a double-click on a displayed object. For example, a double-click includes a first touch (touch start) of a predetermined duration on the displayed object, a first lift-off of a predetermined duration (touch end), a second touch (touch start) of a predetermined duration on the displayed object, and a second lift-off of a predetermined duration (touch end). In another example, event 2 (187-2) is defined as a drag on a displayed object. For example, dragging includes a touch (or contact) on the displayed object for a predetermined duration, movement of the touch on the touch-sensitive display 112, and lifting off the touch (end of touch). In some embodiments, the event also includes information for one or more associated event handlers 190.

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

[0148] In some implementations, the definition of the corresponding event (187) also includes a delay action that delays the delivery of event information until it has been determined whether the sub-event sequence actually corresponds to or does not correspond to the event type of the event recognizer.

[0149] When the corresponding event recognizer 180 determines that the sub-event sequence does not match any event in event definition 186, the corresponding event recognizer 180 enters an event impossible, event failed, or event ended state, after which subsequent sub-events based on touch gestures are ignored. In this case, other event recognizers (if any) that remain active in the hit view continue to track and process the ongoing sub-events based on touch gestures.

[0150] In some embodiments, the corresponding event recognizer 180 includes metadata 183 having configurable attributes, flags, and / or lists instructing how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, the metadata 183 includes configurable attributes, flags, and / or lists instructing how or how event recognizers can interact with each other. In some embodiments, the metadata 183 includes configurable attributes, flags, and / or lists instructing whether sub-events are delivered to different levels in a view or programmatic hierarchy.

[0151] In some implementations, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates the event handler 190 associated with the event. In some implementations, the corresponding event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is different from sending (and delaying) the sub-event to the corresponding hit view. In some implementations, the event recognizer 180 throws a tag associated with the identified event, and the event handler 190 associated with that tag retrieves the tag and executes a predefined procedure.

[0152] In some implementations, event delivery instruction 188 includes a sub-event delivery instruction that delivers event information about a sub-event without activating an event handler. Instead, the sub-event delivery instruction delivers the event information to an event handler associated with the sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or the actively participating view receives the event information and performs a predetermined procedure.

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

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

[0155] It should be understood that the above discussion regarding event handling for user touch on a touch-sensitive display also applies to other forms of user input used to operate the multifunction device 100 using an input device, and not all user input is initiated on the touchscreen. For example, mouse movement and mouse button presses optionally in conjunction with single or multiple keyboard presses or holds; touch movements on the touchpad, such as taps, drags, scrolls, etc.; stylus input; device movement; verbal commands; detected eye movements; biometric input; and / or any combination thereof may optionally be used as input corresponding to sub-events that define the event to be identified.

[0156] Figure 2A portable multifunction device 100 with a touchscreen 112 is shown according to some embodiments. The touchscreen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment and other embodiments described below, a user can select one or more graphics by gesturing over the graphics, for example, using one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with one or more graphics. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down), and / or scrolling (from right to left, from left to right, up and / or down) of a finger already in contact with the device 100. In some specific embodiments or in some cases, unintentional contact with a graphic does not select the graphic. For example, a swipe gesture over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

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

[0158] In some embodiments, device 100 includes a touchscreen 112, a menu button 204, a push-button 206 for powering on / off and locking the device, one or more volume control buttons 208, a SIM card slot 210, a headset jack 212, and a docking / charging external port 124. The push-button 206 is optionally used to power on / off the device by pressing the button and holding it in the pressed state for a predefined time interval; to lock the device by pressing the button and releasing it before the predefined time interval has elapsed; and / or to unlock the device or initiate an unlocking process. In another embodiment, device 100 also accepts voice input via microphone 113 for activating or deactivating certain functions. Device 100 also optionally includes one or more contact strength sensors 165 for detecting the intensity of contact on the touchscreen 112, and / or one or more haptic output generators 167 for generating haptic outputs for a user of device 100.

[0159] Figure 3This is a block diagram of an exemplary multi-functional device with a display and a touch-sensitive surface according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a children's learning toy), gaming system, or control device (e.g., a home controller or industrial 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 bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects system components and controls communication between system components. Device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touchscreen display. The I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350 and a touchpad 355, and a haptic output generator 357 for generating haptic output on device 300 (e.g., similar to the reference above). Figure 1A The tactile output generator 167 and sensor 359 (e.g., optical sensor, accelerometer, proximity sensor, touch sensor and / or contact intensity sensor (similar to the one mentioned above)) are described. Figure 1A The contact strength sensor 165 is described above. 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 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 310. In some embodiments, the memory 370 stores information related to the portable multifunction device 100. Figure 1A The memory 370 stores programs, modules, and data structures similar to those in the memory 102 of the portable multifunction device 100, or subsets thereof. Additionally, the memory 370 optionally stores additional programs, modules, and data structures not present in the memory 102 of the portable multifunction device 100. For example, the memory 370 of the device 300 optionally stores a drawing module 380, a rendering module 382, ​​a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while the portable multifunction device 100 (… Figure 1A The memory 102 may optionally not store these modules.

[0160] Figure 3Each of the elements described above is optionally stored in one or more memory devices of the previously mentioned memory devices. Each of the modules described above corresponds to an instruction set for performing the functions described above. The modules or programs (e.g., instruction sets) described above need not be implemented as separate software programs, processes, or modules, and therefore various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subgroup of the modules and data structures described above. In addition, memory 370 optionally stores additional modules and data structures not described above.

[0161] Now let’s turn our attention to the implementation of the user interface, which is optionally implemented on, for example, a portable multifunction device 100.

[0162] Figure 4A An exemplary user interface for an application menu on a portable multifunction device 100 according to some embodiments is shown. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements or a subset or superset thereof:

[0163] • One or more signal strength indicators 402 for wireless communications such as cellular signals and Wi-Fi signals;

[0164] • Time 404;

[0165] Bluetooth indicator 405;

[0166] • Battery status indicator 406;

[0167] • Tray tray 408 with icons for commonly used applications, such as:

[0168] The telephone module 138 has an icon 416 labeled "telephone", which optionally includes an indicator 414 indicating the number of missed calls or voicemails.

[0169] The email client module 140 has an icon 418 labeled "Mail", which optionally includes an indicator 410 for the number of unread emails;

[0170] The browser module 147 has an icon 420 labeled "Browser"; and

[0171] The video and music player module 152 (also known as the iPod module 152, a trademark of Apple Inc.) with an icon 422 labeled "iPod"; and

[0172] • Icons of other applications, such as:

[0173] Icon 424 of the οIM module 141, labeled "Message";

[0174] The icon 426 of the calendar module 148 is labeled "Calendar";

[0175] The icon 428 of the image management module 144 is labeled "photo";

[0176] The icon 430 of the camera module 143 is labeled "camera";

[0177] The icon 432 of the online video module 155 is labeled "Online Video";

[0178] The icon 434 in the Stock Market Desktop Mini Program 149-2 is labeled "Stock Market";

[0179] The icon 436 of the map module 154 is labeled "map";

[0180] The icon 438 in the Weather Desktop Mini Program 149-1 is marked as "Weather".

[0181] The icon labeled "Clock" in the alarm clock desktop mini-program 149-4 is 440;

[0182] The icon 442 of the fitness support module 142 is labeled "fitness support";

[0183] The notepad module 153 has an icon 444 labeled "Notepad"; and

[0184] The icon 446, labeled "Settings," is used to set the settings of the device 100 and its various applications 136.

[0185] It should be pointed out that, Figure 4A The icon labels shown are merely exemplary. For example, icon 422 of video and music player module 152 is labeled "Music" or "Music Player". Other labels may be optionally used for various application icons. In some embodiments, the label of a particular application icon includes the name of the application corresponding to that particular application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to that particular application icon.

[0186] Figure 4B A touch-sensitive surface 451 (e.g., separate from the display 450 (e.g., touchscreen display 112)) is shown. Figure 3 Devices such as tablets or touchpads (e.g., 355) Figure 3An exemplary user interface on the device 300. The device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of the sensors 359) for detecting the intensity of contact on the tactile surface 451 and / or one or more tactile output generators 357 for generating tactile outputs for the user of the device 300.

[0187] While some examples of input on a reference touchscreen display 112 (which combines a touch-sensitive surface and a display) are given below, in some implementations the device detects input on a touch-sensitive surface separate from the display, such as... Figure 4B As shown in the diagram. In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a spindle (e.g., on the display (e.g., 450)). Figure 4B The spindle corresponding to 453 in the middle (e.g., Figure 4B (452 in the example). According to these embodiments, the device detects the position corresponding to the corresponding position on the display (e.g., in the example). Figure 4B In the middle, 460 corresponds to 468 and 462 corresponds to 470) is in contact with the touch-sensitive surface 451 (e.g., Figure 4B (460 and 462 in the text). Thus, when the touch-sensitive surface (e.g., ...) Figure 4B 451) and the display of a multi-functional device (e.g., Figure 4B When 450 is separated from the touch-sensitive surface, user input detected by the device on that touch-sensitive surface (e.g., touches 460 and 462 and their movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods may optionally be used for other user interfaces described herein.

[0188] Additionally, while the examples below are primarily given with reference to finger input (e.g., finger touch, single-finger tap, finger swipe), it should be understood that in some implementations, 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 a touch), followed by movement of the cursor along the swipe path (e.g., instead of movement of the touch). Similarly, a tap gesture may optionally be replaced by a mouse click while the cursor is over the location of the tap gesture (e.g., instead of detection of touch, followed by cessation of touch detection). Likewise, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice may optionally be used simultaneously, or mouse and finger touch may optionally be used simultaneously.

[0189] Figure 5AAn exemplary personal electronic device 500 is illustrated. Device 500 includes a body 502. In some embodiments, device 500 may include components relative to devices 100 and 300 (e.g., Figures 1A to 4B Some or all of the features described herein. In some embodiments, device 500 has a touch-sensitive display 504, referred to below as touchscreen 504. As an alternative to or complement to touchscreen 504, device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, touchscreen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors for detecting the intensity of an applied contact (e.g., touch). The one or more intensity sensors of touchscreen 504 (or touch-sensitive surface) can provide output data representing the intensity of the touch. The user interface of device 500 can respond to touches based on the intensity of the touch, meaning that touches of different intensities can invoke different user interface operations on device 500.

[0190] Exemplary techniques for detecting and processing touch intensity are found, for example, in the following related patent applications: International Patent Application Serial No. PCT / US2013 / 040061, filed May 8, 2013, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” published as WIPO Patent Publication No. WO / 2013 / 169849; and International Patent Application Serial No. PCT / US2013 / 069483, filed November 11, 2013, entitled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” published as WIPO Patent Publication No. WO / 2014 / 105276, each of which is incorporated herein by reference in its entirety.

[0191] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508 (if included) may be physical. Examples of physical input mechanisms include push-buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms (if included) allow device 500 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watch straps, bangles, trousers, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow a user to wear device 500.

[0192] Figure 5B An exemplary personal electronic device 500 is illustrated. In some embodiments, device 500 may include a reference. Figure 1A , Figure 1B and Figure 3 Some or all of the components described herein. Device 500 has a bus 512 that operatively couples I / O portion 514 to one or more computer processors 516 and memory 518. I / O portion 514 may be connected to display 504, which may have touch-sensitive components 522 and optionally have an intensity sensor 524 (e.g., a contact intensity sensor). Furthermore, I / O portion 514 may be connected to communication unit 530 for receiving application and operating system data using Wi-Fi, Bluetooth, near field communication (NFC), cellular and / or other wireless communication technologies. Device 500 may include input mechanisms 506 and / or 508. For example, input mechanism 506 may optionally be a rotatable input device or a pressable input device and a rotatable input device. In some examples, input mechanism 508 may optionally be a button.

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

[0194] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions, which, when executed by one or more computer processors 516, may cause the computer processors to perform the techniques described below, including processes 700-800 and 1000. Figures 7 to 8 and Figure 10A computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, and device. In some embodiments, the storage medium is a transient computer-readable storage medium. In some embodiments, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media may include, but are not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical discs based on CD, DVD, or Blu-ray technology, and persistent solid-state storage such as flash memory, solid-state drives, etc. Personal electronic devices 500 are not limited to Figure 5B It can be the components and configurations, or it can include other components or additional components in a variety of configurations.

[0195] As used herein, the term "power indication" refers optionally to the power indication in devices 100, 300, and / or 500 ( Figure 1A , Figure 3 and Figures 5A to 5B A user-interactive graphical user interface object displayed on a screen. For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) optionally each constitute a functional representation.

[0196] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface with which a user is interacting. In some specific implementations that include a cursor or other positional marker, the cursor acts as a "focus selector," such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the cursor is positioned on a touch-sensitive surface (e.g., a...). Figure 3 The touchpad 355 or Figure 4B When an input (e.g., a press input) is detected on the touch-sensitive surface 451 of the display, the specific user interface element is adjusted according to the detected input. This applies to touchscreen displays (e.g., those capable of enabling direct interaction with user interface elements on the touchscreen display) Figure 1A The touch-sensitive display system 112 or Figure 4AIn some embodiments of the touchscreen 112, a touch detected on the touchscreen acts as a "focus selector," such that when input (e.g., a press input by touch) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, that particular user interface element is adjusted according to the detected input. In some embodiments, focus moves from one area of ​​the user interface to another without corresponding movement of the cursor or movement of a touch on the touchscreen display (e.g., moving focus from one button to another using tab keys or arrow keys); in these embodiments, the focus selector moves according to the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user-controlled user interface element (or a touch on the touchscreen display) that delivers the user-expected interaction with the user interface (e.g., by indicating to the device the element of the user interface that the user expects to interact with). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of the focus selector (e.g., a cursor, touch, or selection box) above the corresponding button will indicate to the user that they expect to activate the corresponding button (rather than other user interface elements shown on the device's display).

[0197] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected over a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after contact is detected, before contact is detected to be lifted away, before or after contact begins to move, before contact ends, before or after contact intensity is detected to increase and / or before or after contact intensity decreases). The characteristic intensity of the contact is optionally based on one or more of the following: the maximum value of the contact intensity, the mean value of the contact intensity, the average value of the contact intensity, the value at the top 10% of the contact intensity, the half maximum value of the contact intensity, the 90% maximum value of the contact intensity, etc. In some embodiments, the duration of the contact is used when determining the characteristic intensity (e.g., when the characteristic intensity is the average value of the contact intensity over time). In some implementations, the feature intensity is compared to a set of one or more intensity thresholds to determine whether the user has performed an action. For example, the set of one or more intensity thresholds may optionally include a first intensity threshold and a second intensity threshold. In this example, contact with a feature intensity not exceeding the first threshold results in a first action, contact with a feature intensity exceeding the first intensity threshold but not exceeding the second intensity threshold results in a second action, and contact with a feature intensity exceeding the second threshold results in a third action. In some implementations, a comparison between the feature intensity and one or more thresholds is used to determine whether to perform one or more actions (e.g., whether to perform the corresponding action or abandon performing the corresponding action) rather than to determine whether to perform the first action or the second action.

[0198] Figure 5C This demonstrates the use of multiple intensity sensors 524A-524D to detect multiple contacts 552A-552E on a touch-sensitive display 504. Figure 5C The system also includes an intensity map showing the current intensity measurements of intensity sensors 524A-524D relative to intensity units. In this embodiment, the intensity measurements of intensity sensors 524A and 524D are both 9 intensity units, and the intensity measurements of intensity sensors 524B and 524C are both 7 intensity units. In some implementations, the cumulative intensity is the sum of the intensity measurements of the multiple intensity sensors 524A-524D, which is 32 intensity units in this embodiment. In some implementations, each contact is assigned a corresponding intensity, i.e., a portion of the cumulative intensity. Figure 5DThe diagram illustrates the allocation of cumulative intensity to contacts 552A-552E based on their distance from the center of force 554. In this embodiment, each of contacts 552A, 552B, and 552E is assigned a contact intensity of 8 intensity units of the cumulative intensity, and each of contacts 552C and 552D is assigned a contact intensity of 4 intensity units of the cumulative intensity. More generally, in some specific implementations, each contact j is assigned a corresponding intensity Ij according to a predefined mathematical function Ij = A·(Dj / ΣDi), which is a portion of the cumulative intensity A, where Dj is the distance of the corresponding contact j from the center of force, and ΣDi is the sum of the distances of all corresponding contacts (e.g., i = 1 to the last) from the center of force. Reference can be performed using electronic devices similar to or equivalent to devices 100, 300, or 500. Figures 5C-5D The operation described above. In some embodiments, the characteristic intensity of the contact is based on one or more intensities of the contact. In some embodiments, an intensity sensor is used to determine the intensity of a single characteristic (e.g., a single characteristic intensity of a single contact). It should be noted that the intensity map is not part of the displayed user interface, but is included within... Figures 5C-5D This is intended to assist readers.

[0199] In some implementations, a portion of the gesture is identified to determine the characteristic intensity. For example, a touch-sensitive surface optionally receives a series of swipe contacts that transition from a starting position to an ending position, where the contact intensity increases. In this example, the characteristic intensity of the contact at the ending position is optionally based only on a portion of the series of swipe contacts, rather than the entire swipe contact (e.g., only the portion of the swipe contact at the ending position). In some implementations, a smoothing algorithm is optionally applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of the following: unweighted moving average smoothing algorithm, triangular smoothing algorithm, median filter smoothing algorithm, and / or exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow spikes or dips in the intensity of the swipe contact to achieve the purpose of determining the characteristic intensity.

[0200] Optionally, the contact intensity on a touch-sensitive surface is characterized relative to one or more intensity thresholds, such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device performs an operation typically associated with clicking a button on a physical mouse or touchpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device performs an operation different from the operation typically associated with clicking a button on a physical mouse or touchpad. In some embodiments, when a contact with a characteristic intensity lower than the light press intensity threshold (e.g., and higher than the nominal contact detection intensity threshold, where contacts lower than the nominal contact detection intensity threshold are no longer detected) is detected, the device will move the focus selector based on the movement of the contact on the touch-sensitive surface without performing the operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent across different groups of user interface figures.

[0201] An increase in contact intensity from below a light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a "light press" input. An increase in contact intensity from below a deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press" input. An increase in contact intensity from below a contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting a contact on the touch surface. A decrease in contact intensity from above a contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting a contact being lifted off the touch surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.

[0202] In some embodiments described herein, one or more operations are performed in response to detecting a gesture including a corresponding press input or in response to detecting a corresponding press input performed using a corresponding contact (or multiple contacts), wherein the corresponding press input is detected at least in part based on detecting that the intensity of the contact (or multiple contacts) increases to above a press input intensity threshold. In some embodiments, the corresponding operation is performed in response to detecting that the intensity of the corresponding contact increases to above a press input intensity threshold (e.g., a "downward stroke" of the corresponding press input). In some embodiments, the press input includes the intensity of the corresponding contact increasing to above a press input intensity threshold and the intensity of the contact subsequently decreasing to below the press input intensity threshold, and the corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases to below the press input threshold (e.g., an "upward stroke" of the corresponding press input).

[0203] Figures 5E-5HThe detection of gestures is shown, including gestures involving contact 562 with an intensity ranging from less than... Figure 5E The light press intensity threshold (e.g., "IT") L The intensity of ”) increases to higher than Figure 5H The deep press intensity threshold (e.g., "IT") D The intensity of the press input corresponds to the strength of the press. On the user interface 570, which includes application icons 572A-572D displayed in the predefined area 574, when the cursor 576 is displayed above the application icon 572B corresponding to application 2, the gesture performed by contact 562 is detected on the touch-sensitive surface 560. In some embodiments, the gesture is detected on the touch-sensitive display 504. The intensity sensor detects the intensity of the contact on the touch-sensitive surface 560. The device determines the intensity of the contact 562 within a deep press intensity threshold (e.g., "IT"). D The intensity reaches its peak value above 562. Contact is maintained on the touch-sensitive surface 560. In response to a detected gesture, and based on the intensity increasing to a deep press intensity threshold (e.g., "IT") during the gesture... D The above contact 562 displays the scale representation 578A-578C (e.g., thumbnails) of the document recently opened for application 2, such as... Figures 5F-5H As shown. In some embodiments, the intensity is a characteristic intensity of the contact compared to one or more intensity thresholds. It should be noted that the intensity map for contact 562 is not part of the displayed user interface, but is included in... Figures 5E-5H This is intended to assist readers.

[0204] In some implementations, the display of icons 578A-578C includes animation. For example, icon 578A might initially appear near application icon 572B, such as... Figure 5F As shown, as the animation progresses, icon 578A moves upwards, and icon 578B appears near application icon 572B, as shown. Figure 5G As shown in the diagram. Then, representation 578A moves upward, 578B moves upward toward representation 578A, and representation 578C is displayed near application icon 572B, as shown. Figure 5H As shown in the diagram. This indicates that 578A-578C form an array above icon 572B. In some implementations, the animation progresses according to the intensity of contact 562, such as... Figures 5F-5G As shown, where 578A-578C appear and increase with the intensity of contact 562 towards the pressure threshold (e.g., "IT"). D The animation progresses upwards as it increases in intensity. In some implementations, the intensity upon which the animation progresses is based is the characteristic intensity of the contact. Reference can be performed using electronic devices similar to or equivalent to devices 100, 300, or 500. Figures 5E-5H The aforementioned operation.

[0205] In some implementations, the device employs intensity hysteresis to avoid unintended inputs sometimes referred to as "jitter," wherein the device defines or selects a hysteresis intensity threshold that has a predefined relationship with a press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the press input intensity threshold). Therefore, in some implementations, a press input includes an increase in the intensity of the corresponding contact above the press input intensity threshold and a subsequent decrease in the intensity of that contact below the hysteresis intensity threshold corresponding to the press input intensity threshold, and a corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases below the hysteresis intensity threshold (e.g., an "upstroke" of the corresponding press input). Similarly, in some implementations, a press input is detected only when the device detects that the contact intensity increases from an intensity equal to or below the hysteresis intensity threshold to an intensity equal to or above the press input intensity threshold and optionally the contact intensity subsequently decreases to an intensity equal to or below the hysteresis intensity threshold, and a corresponding operation is performed in response to detecting a press input (e.g., an increase or decrease in contact intensity depending on the environment).

[0206] For ease of explanation, optionally, the description of an operation triggered in response to a press input associated with a press input strength threshold or in response to a gesture including a press input is provided in response to detecting any of the following conditions: the contact strength increases to above the press input strength threshold, the contact strength increases from below a hysteresis strength threshold to above the press input strength threshold, the contact strength decreases to below the press input strength threshold, and / or the contact strength decreases to below the hysteresis strength threshold corresponding to the press input strength threshold. Additionally, in the example where the operation is described as being performed in response to detecting a decrease in contact strength below the press input strength threshold, the operation is optionally performed in response to detecting a decrease in contact strength below a hysteresis strength threshold corresponding to and less than the press input strength threshold.

[0207] As used herein, "installed application" refers to a software application that has been downloaded to an electronic device (e.g., device 100, 300, and / or 500) and is ready to be launched on the device (e.g., become open). In some implementations, the downloaded application becomes an installed application using an installer that extracts program portions from the downloaded software package and integrates the extracted portions with the computer system's operating system.

[0208] As used herein, the terms "open application" or "running application" refer to a software application that maintains state information (e.g., as part of device / global internal state 157 and / or application internal state 192). An open or running application is optionally any of the following types of applications:

[0209] • The currently active application displayed on the screen of the device that is using the application;

[0210] • Background applications (or background processes) that are not currently displayed but whose one or more processes are being handled by one or more processors; and

[0211] • A suspended or hibernating application that is not running but has state information stored in memory (both volatile and non-volatile) that can be used to resume application execution.

[0212] As used herein, the term "closed application" refers to a software application that does not retain state information (e.g., the state information of a closed application is not stored in the device's memory). Therefore, closing an application includes stopping and / or removing the application's process and removing the application's state information from the device's memory. Generally, opening a second application while the first application is running does not close the first application. When the second application is displayed and the first application stops displaying, the first application becomes a background application.

[0213] Now let’s turn our attention to the implementation of user interfaces (“UIs”) and associated processes on electronic devices (such as portable multifunction devices 100, 300 or 500).

[0214] Figures 6A to 6AC Exemplary user interfaces for restricted operating modes are shown according to some embodiments. The user interfaces in these figures are used to illustrate including... Figures 7 to 8 The process described below is the process in the middle.

[0215] Figure 6A Device 600 is depicted. Device 600 is configured to operate according to a restricted mode (described in more detail below) and one or more modes other than the restricted mode. In some embodiments, device 600 is device 100, 300, or 500. Device 600 has a display device 602 depicted as a touch-sensitive display (e.g., touchscreen 504). Touch-sensitive display 602 is configured to detect the intensity of a contact. Exemplary components for detecting the intensity of a contact and techniques for doing so are described in more detail above. Device 600 has a pressable and rotatable input device 603 configured to rotate relative to the frame or housing of device 600. Pressable and rotatable input device 603 is configured to rotate about an axis parallel to the surface of touch-sensitive display 602.

[0216] Device 600 is shown as a watch (e.g., a smartwatch). Therefore, some user interfaces shown as being displayed by device 600 are referred to as “clock faces” or “dials.” The reference to “clock face” as described herein is not in any way limited to the conventional concept of a “clock face,” such as a circular display or digital clock display that indicates time with hour indicators and one or more hands. Any user interface having the time indication described herein may be appropriately referred to as a clock face. Relatedly, a “complex function block” refers to any clock face feature other than the hours and minutes used to indicate time (e.g., clock hands or hour / minute indicators). In some embodiments, the complex function block provides the user with different types of information, such as data obtained from an application. In some embodiments, the information conveyed to the user by the complex function block is customizable.

[0217] Although the reference watch describes device 600, the technologies described below are not limited to clocks, watches, clock faces, and dials. The methods and user interfaces described herein can be applied to other devices and interfaces, including but not limited to desktop computers, laptop computers, tablet computers, smartphones, etc.

[0218] Figures 6A to 6C The technology used to select the appropriate user interface type is shown. Figures 6A to 6C As shown, device 600 does not operate according to a restricted mode (e.g., a mode in which one or more functions of a first group available in an unrestricted mode are unavailable in a restricted mode, and one or more functions of a second group available in an unrestricted mode are available in a restricted mode). In some embodiments, such as relative to Figures 6A to 6C The ability to select the appropriate type of user interface is limited (e.g., unavailable) when the device 600 is operating in a restricted mode.

[0219] exist Figures 6A to 6C In this context, the corresponding user interface type is a clock face. However, referring to... Figures 6A to 6C The described technology can be applied to other types of user interfaces. Using the technology described herein, many individual clock faces are possible. Users may want to select a specific clock face based on a particular context (e.g., from a saved clock face library). For example, a user might want to display a specific clock face during work hours to project a professional look, but change the clock face during the weekend to reflect their hobbies (e.g., astronomy, exercise, or photography).

[0220] exist Figure 6A In the device 600, a clock face 604 is displayed. The clock face 604 includes an analog time indicator 604-1, a complication block 604-2 corresponding to a health application, and a complication block 604-3 corresponding to a music application.

[0221] In this example, the user wants to switch from clock face 604 to a different clock face. The user uses input 610a (e.g., a tap) to contact the touch-sensitive display of device 600. In response to determining that input 610a has a characteristic intensity above an intensity threshold, device 600 enters clock face selection mode (in... Figure 6B (As shown on the user interface 606). The clock face selection mode allows the user to select a clock face. The device 600 indicates to the user that it has entered the clock face selection mode by visually distinguishing the clock face. The user interface 606 visually distinguishes that the device 600 has entered the clock face selection mode by centering a reduced-size clock face 606-1 on the display (the reduced-size clock face 606-1 is based on the clock face 604). This indicates to the user that the device 600 is in the clock face selection mode, while also indicating to the user how the clock face would look when displayed in full size.

[0222] In some embodiments, the user interface 606 includes partial views of a second clock face 606-2 and a third clock face 606-3. In some embodiments, when the device 600 is in clock face selection mode, the device 600 displays another clock face or clock face option, particularly a partial view of the next clock face or clock face option in a sequence (e.g., of two or more clock faces available for selection in clock face selection mode). This further helps the user understand that additional options are available. In some embodiments, only one clock face is displayed at any given time.

[0223] In some implementations, the user interface 606 includes a pagination point indicating where the user is within the available clock face sequence and how many options are available in that sequence. In clock face selection mode, the pagination point may indicate the currently selected clock face (where it falls within the clock face sequence) and the total number of clock faces in that sequence. Pagination can be advantageous in clock face selection mode to help the user navigate the interface and explore all available clock face options.

[0224] The clock face selection mode can be used to select the clock face displayed in the application, or to select a clock face for editing. In some implementations, when the clock face (such as clock face 606-1) is centered on the display, the user can touch the "custom" indicator 606-4 on the touch-sensitive display 602 to select the centered clock face for editing and enter the clock face editing mode (see below for reference). Figures 6E to 6G (As described above). The combined clock face editing and selection modes within a single interface allow users to select different clock faces and edit them quickly and easily.

[0225] Users can select different clock faces (for editing or display) by providing input on the touch-sensitive display 602. Device 600 detects input 610b on the touch-sensitive display (e.g., a swipe). In response to detecting input 610b, device 600 updates (e.g., scrolls) the user interface 606, such as... Figure 6C As shown. The user interface 606 includes a second clock face 606-2 centered on the display when updated. In some embodiments, the user interface 606 includes a partial view of clock face 606-1 when updated.

[0226] To select clock face 606-2, the user touches the touch-sensitive display 602 on clock face 606-2 (e.g., touch input 610c). In response to detecting input 610c (e.g., a tap), device 600 exits clock face selection mode and displays a full-size clock face 608 based on clock face 606-2 (e.g., a full-size display 608). Figure 6D (As shown). Clock face 608 includes a digital time indication 608-1 and five complication blocks 608-2 to 608-6. Complication block 608-2 corresponds to a calendar application and displays date information from the calendar application; complication block 608-3 corresponds to a calendar application (e.g., the same calendar application associated with complication block 608-2) and displays calendar event data from the calendar application; complication block 608-4 corresponds to a weather application and displays forecast data from the weather application; complication block 608-5 corresponds to a weather application (e.g., the same weather application associated with complication block 608-4) and displays current temperature data from the weather application; and complication block 608-6 corresponds to an instant messaging application and displays graphical elements (e.g., icons) associated with the instant messaging application. In some embodiments, the graphical elements associated with the instant messaging application display data from the instant messaging application (e.g., the number of new, unread, or missed messages).

[0227] Optionally, in addition to or instead of the techniques described above, device 600 provides other methods for selecting a clock face. In some embodiments, device 600 switches directly from clock face 604 to clock face 608 without entering a clock face selection mode (e.g., without displaying user interface 606). For example, in response to... Figure 6A When clock face 604 is displayed, a swipe gesture from right to left is detected on touch-sensitive display 602, and device 600 replaces clock face 604 with clock face 608 (e.g., device 600 stops the display of clock face 604 and displays clock face 608).

[0228] Various techniques for selecting a user interface of a given type (e.g., clock face) have already been described; now, attention will turn to methods for editing a user interface of a given type (e.g., clock face). Figures 6D to 6G The techniques used to edit user interfaces of corresponding user interface types are shown. Figures 6D to 6G In this case, device 600 does not operate according to the restricted mode. In some implementations, such as relative to... Figures 6D to 6GThe ability to edit the user interface is limited (e.g., unavailable) when the device 600 is operating in a restricted mode.

[0229] exist Figure 6D In this example, device 600 displays a clock face 608. Clock face 608 includes a complexity block 608-6 that displays information associated with an instant messaging application. In this example, the user wants to change an aspect of clock face 608. Specifically, the user decides to change the application associated with complexity block 608-6.

[0230] A user uses touch input 610d to contact the touch-sensitive display 602 of device 600. In response to determining that input 610d has a characteristic intensity higher than an intensity threshold, device 600 enters a clock face editing mode. In some embodiments, the clock face editing mode is the same as (or integrated with) the clock face selection mode described above (e.g., a combined clock face selection / editing mode). The clock face editing mode allows the user to edit one or more aspects of the clock face.

[0231] In the illustrated embodiment, in response to input 610d, device 600 displays the aforementioned user interface 606. User interface 606 displays a reduced-size clock face 606-2 based on clock face 608, having a reduced-size time indicator 606-2a and complication blocks 606-2b to 606-2f. This display indicates to the user that device 600 is in clock face editing mode (or selection mode), while also indicating to the user how the edited clock face will appear on the display.

[0232] The user selects the displayed clock face for editing by contacting the "custom" indicator 606-4 using input 610e (e.g., a tap). In response to detecting input 610e, device 600 displays user interface 612, which includes a full-size editable version of clock face 606-2. User interface 612 visually indicates the elements of the clock face for editing. As shown on user interface 612, complication block 612-6 (corresponding to element 606-2f and complication block 608-6) has been selected for editing, as indicated by outline 612-7a and title bar 612-7b. Other elements of the clock face are retained, such as the digital time indicator 612-1 and complication blocks 612-2 to 612-5.

[0233] In some implementations, the user interface 612 displays pagination points 612-8, indicating where the user is within a sequence of options and how many options are available in that sequence. In clock face editing mode, the pagination point can indicate which editable aspect of the clock face the user is editing (where this aspect falls within a sequence of editable aspects) and the total number of editable aspects in that sequence. Pagination points can be advantageous in clock face editing mode to help the user navigate the interface and explore all editable options available for each type of clock face.

[0234] In this example, two aspects of the clock face are editable by the user: (1) the color design and (2) the complication blocks. This is depicted by page breaks 612-8a and 612-8b. Editing the clock face color may include, for example, changing the color of the clock face background (e.g., replacing the color if the clock face background is a specific color, or selecting a different image if the clock face background includes an image), changing part or all of the color of the second hand (if included on the clock face), changing the color of the hour and / or minute indicators, and / or changing the color of the digits or colons in the display of a digital clock.

[0235] User interface 612 is used to edit the complication block, which is the second editable aspect of the clock face. This is communicated to the user by highlighting page break point 612-8b. By viewing page break point 612-8b, the user recognizes that the complication block is the second of the two editable aspects of the clock face.

[0236] The user can move (e.g., rotate) the pressable and rotatable input device 603 to cycle through different options for editing different aspects of the clock face. On the user interface 612, the user can select different options (e.g., application data) for the complex function blocks 612-6 by inputting 610f (e.g., moving the pressable and rotatable input device 603). Advantageously, using the rotatable input device to cycle through editing options (instead of using, for example, touch interaction) frees up touch interaction with the screen to provide additional functionality (e.g., selecting which complex function block to edit), thereby expanding the interactivity of the device. Using the rotatable input device is also useful when editing smaller elements of the display, as finger-proportioned touch gestures can be difficult on smaller displays, especially for users with larger fingers (which may obstruct the user's view of the screen while editing).

[0237] A position indicator 612-9 is also displayed on the user interface 612. The position indicator 612-9 is an indicator of the current position along a series of positions. This can be used, for example, in conjunction with a pressable and rotatable input device 603. On the user interface 612, the position indicator 612-9 indicates to the user the position of the currently selected option within a series of all available options.

[0238] In response to the detection of input 610f, device 600 edits complication block 612-6 in this case by changing the data associated with the complication block from instant messaging application data to fitness application data (e.g., an indication for launching the fitness application). This is shown by changing the graphic elements displayed at complication block 612-6, while still highlighting complication block 612-6 with outline 612-7a and title bar 612-7b. The other elements of the clock face remain the same. Position indicator 612-9 has been updated to indicate the position of the fitness application data in the data option sequence.

[0239] As indicated by page break 612-8b, the complex function block is the second editable aspect of the clock face within the sequence of editable aspects. A user can select a first editable aspect (e.g., color) by swiping on a touch-sensitive display (e.g., swiping from left to right). In response to detecting a swipe, device 600 displays a user interface for editing the color design of the clock face (e.g., by rotating the pressable and rotatable input device 603).

[0240] Although Figures 6D to 6G Editing of only complex function blocks 612-6 is shown, but multiple complex function blocks can be edited. A user selects a specific complex function block for editing by touching the corresponding location of the complex function block. The outline 612-7a then transitions from the previously selected complex function block or element to the currently selected complex function block or element, and the pressable and rotatable input device 603 can be used to edit the complex function block or element at the selected location. In some embodiments, elements (e.g., complex function blocks) can be selected by swiping the touch-sensitive display or rotating the pressable and rotatable input device.

[0241] As described above, a user can scroll through available options using movement of a pressable and rotatable input device. However, a user may also wish to use a second type of input to scroll through available options, such as contact on a touch-sensitive display (e.g., swipe). In some embodiments, a user can swipe the touch-sensitive display in a different direction than a swipe used to visually indicate a second element of the clock face for editing (e.g., swipe down on the display). For example, to scroll through available options, a user can swipe in a substantially horizontal direction to scroll through editable aspects (e.g., a swipe from left to right results in scrolling through a sequence of editable aspects in one direction, while a swipe from right to left results in scrolling through a sequence of editable aspects in a different direction). In this embodiment, a user can swipe in a substantially vertical direction to scroll through available options (e.g., a swipe down results in scrolling through a sequence of available options in one direction, while a swipe up results in scrolling through a sequence of available options in a different direction). In some embodiments, a user can swipe the display at or near the location of a displayed position indicator to scroll through a sequence of available options.

[0242] After editing the clock face, the user can exit the clock face editing mode and display the edited clock face on the monitor. In response to input 610g (e.g., a press of the pressable and rotatable input device 603), device 600 exits the clock face editing mode and displays the edited clock face 614, as shown. Figure 6H The edited clock face 614 is identical to clock face 608 except for the updated complication block 614-1. In some embodiments, in response to input 610g, device 600 returns to user interface 606 (e.g., exiting clock face editing mode and returning to clock face selection mode), which is updated to display the representation of the edited clock face, and then, while displaying user interface 606, in response to another user input (e.g., pressing a pressable and rotatable input device 603), displays the edited clock face 614 (as shown). Figure 6H (As depicted).

[0243] Figures 6A to 6H Exemplary embodiments of selecting and editing a clock face are shown, but many other possible embodiments are possible within the scope of the technology described herein, wherein device 600 selects and / or edits the clock face in response to a sequence of one or more inputs. Clock face editing modes allow users to change multiple editable aspects of the clock face described herein. In some embodiments, in response to detecting a swipe on a touch-sensitive display, device 600 selects a second element of the clock face for editing, which in response to detecting another user input (e.g., movement of a pressable and rotatable input mechanism) that can be edited. This allows the user to cycle through different editable aspects of the displayed clock face, such as color, quantity and / or complication block type, and display density.

[0244] Go to Figure 6I In some implementations, a complex function block can be selected to launch an application (e.g., to put the application activity in the background or pause it). For example, an indication of a complex function block on a clock face can display a set of information from the corresponding application. However, the user may want to view additional information from the application or launch the application itself. Complex function block 614-1 represents a fitness application and includes an indication of its launch. To launch the fitness application, the user touches the display at complex function block 614-1 (e.g., touches 610h). In response, device 600 launches the fitness application and begins an outdoor walk, such as... Figure 6J The user interface 616 is depicted in the figure. The user interface 616 shows the type of exercise (outdoor walking), distance (0.01 miles), and elapsed time (00:08:52).

[0245] exist Figures 6I to 6J In this embodiment, device 600 does not operate according to the restricted mode. In some implementations, when device 600 operates according to the restricted mode, the ability to launch applications (e.g., specific applications), access open applications, and / or close applications is restricted (e.g., unavailable).

[0246] Go to Figure 6K The display 602 becomes inactive (e.g., in response to device 600 determining that no input has been received within a predetermined amount of time, in response to detecting a predetermined gesture (e.g., a wrist-down gesture), or in response to detecting input (e.g., a sequence of one or more inputs that causes the display 602 to become inactive)).

[0247] When display 602 is inactive, device 600 detects the occurrence of a condition corresponding to a trigger for displaying the current clock face on device 600 (e.g., a tap, wrist lift, movement of the pressable and rotatable input device 603, application closure, etc.). In response to detecting the occurrence of a condition corresponding to a trigger for displaying the current clock face, device 600 displays the clock face, wherein the displayed clock face depends on whether the current time corresponds to a predefined time range during which device 600 will operate in restricted mode. In some embodiments, the current time corresponds to the predefined time range if it is within the predefined time range. In some embodiments, the predefined time range is absolute (e.g., from a defined start time (e.g., 9:00 am) to a defined end time (e.g., 3:00 pm) or relative (e.g., within a defined amount of time (e.g., 1 hour) from when entering restricted mode). In some embodiments, the predefined time range is defined by a device remote from device 600 (e.g., by a reference). Figures 6AA to 6ACThe device 650 is configured as described above. In some implementations, a predefined time range is associated with a user account associated with the device 600 (e.g., the predefined time range applies to multiple devices associated with a user account).

[0248] Based on the determination that the current time does not correspond to a predefined time range, device 600 does not operate according to the restricted mode and displays clock face 614 (e.g., the currently selected clock face). In some embodiments, device 600 displays the most recently displayed interface (e.g., user interface 616 in the illustrated example) instead of the currently selected clock face. Based on the determination that the current time corresponds to a predefined time range, device 600 operates according to a restricted operating mode (e.g., entering or activating restricted mode). The predefined time range in the illustrated embodiment is 8:00 am to 3:00 pm. Figure 6L In the current time, which corresponds to 8:00am within a predefined time range, device 600 enters restricted mode.

[0249] In some implementations, operating in a restricted mode includes displaying a restricted user interface. Figure 6L An implementation of a restricted user interface, i.e., a restricted clock face 618, is described. In some implementations, if clock face 614 (or user interface 616) is displayed when the current time reaches a predefined time range, device 600 stops the display of clock face 614 (or user interface 616) and replaces it with the restricted clock face 618. As described in more detail below, in some implementations, input on display 602 when the restricted clock face 618 is displayed does not elicit a visible response or provide notification while in restricted mode.

[0250] The display of the restricted clock face 618 indicates that the device 600 is operating in a restricted mode and includes graphic elements (e.g., a predefined set of elements) that are different from those available for use with other user interfaces (e.g., clock faces 604, 608, and 614) displayed by the device 600. In some embodiments, in response to input detected at the device 600, the graphic elements of the restricted clock face 618 cannot be changed (e.g., edited or removed), and additional graphic elements cannot be added to the restricted clock face 618 (e.g., cannot be added without first exiting the restricted mode).

[0251] In the illustrated embodiment, the restricted clock face 618 includes an analog time indication 618-1, a date indication 618-2, and a digital time indication 618-3. Element 618-1a of the analog time indication 618-1 corresponds to the current hour of the current time, and other elements of the analog time indication 618-1 corresponding to hours other than the current hour are visually emphasized. The restricted clock face 618 includes a username indication 618-4 (e.g., full first and last name, first name only, first and last name initials, initials only (e.g., first and last name initials only)). In some embodiments, the username is customizable (e.g., via device 600 or an external device).

[0252] In the illustrated embodiment, the defined clock face 618 includes a large ring 618-1b that distinguishes the graphic elements, specifically, a ring whose outer diameter is substantially the same as (slightly smaller than) the horizontal dimension (e.g., width) of the display device 602 (e.g., the outer diameter of ring 618-1b is greater than 90% of the width of the display). Ring 618-1b is visually distinguishable because it is not an arbitrary defined area of ​​the clock face 618. In some embodiments, ring 618-1b is a highlighted color, such as yellow. In some embodiments, ring 618-1b is not included in any other clock face available on device 600. For example, as described above... Figures 6B to 6C Any face provided in the clock face selection mode described herein shall not change to include ring 618-1b in response to input detected at the electronic device. In some embodiments, a distinguishing graphic element is displayed via a display device only when the restricted clock face is the current clock face (e.g., the element is unique for the restricted clock face). In some embodiments, the distinguishing element is located in the foreground of the restricted clock face (e.g., the distinguishing element is not a background image). Ring 618-1b is merely an example of a distinguishable graphic element—other elements having the general characteristics of ring 618-1b described above (e.g., not available on other clock faces or user interfaces) may be distinguishable graphic elements.

[0253] The restricted clock face 618 includes graphical elements 618-5 corresponding to the fitness application represented by the user interface 616. In some embodiments, the device 600 continues to run the fitness application after entering restricted mode. Even when operating in restricted mode, the device 600 can continue to run the fitness application so as not to interrupt the ongoing workout. In some embodiments, the device 600 determines what action to take relative to the open application when entering restricted mode (e.g., continue running in the background, suspend, pause, or close) based on the type of application that is running. For example, the device 600 may suspend or close applications of the type that can be resumed from where the application stopped (e.g., a user can restart a music track at the point where a music application is paused or stopped), while the device 600 may continue to run applications of the type that are not easily resumed (e.g., a fitness application cannot accurately track a runner's stride if the application is closed during a runner's workout).

[0254] exist Figure 6L In the illustrated embodiments, based on the determination that the application is open, device 600 displays graphical elements 618-5 on the restricted clock face 618 to indicate that the fitness application is open. In some embodiments, device 600 displays the graphical elements of the application on the restricted clock face 618 if the application is open and running in the background (e.g., a background application) rather than if the application is suspended or dormant (e.g., open but not running). In some embodiments, unlike the complex function block 614-1 on clock face 614, graphical element 618-5 cannot be selected to access (e.g., launch or display) the fitness application. For example, touch input on graphical element 618-5 does not cause the fitness application to be displayed, and in some embodiments, it does not cause any function to be performed (e.g., device 600 does not perform any affirmative action in response to input corresponding to the selection of graphical element 618-5). In some embodiments, device 600 does not respond to any touch input on touch-sensitive display 602 (e.g., when the restricted clock face 618 is displayed, device 600 does not enter clock face selection or editing mode in response to input on touch-sensitive display 602). In some implementations, device 600 does not provide notifications (e.g., graphical, haptic, audible) of events (e.g., incoming phone calls, emails, text messages, alarms) when it is in a restricted mode (e.g., when displaying a restricted clock face 618).

[0255] In some implementations, when the current time reaches a predefined time range, device 600 suspends or closes the active application. In some such implementations, based on the determination that the application is not running (e.g., closed or suspended), device 600 displays a limited clock face 618 without graphical elements corresponding to the fitness application.

[0256] In some implementations, the predefined set of graphic elements for the restricted clock face has a predefined configuration or layout that differs from all other available clock faces (e.g., clock faces 604, 608, and 614). In some implementations, the restricted clock face 618 is unavailable when the device 600 is not in restricted mode (e.g., restricted clock face 618 is unavailable in...). Figures 6B to 6C (The clock face selection mode shown is unavailable). In some implementations, the user cannot select the clock face corresponding to the restricted mode. In some implementations, the restricted clock face is a static system setting.

[0257] Figures 6M to 6O Techniques for exiting restricted mode (also referred to as "unlocking" restricted mode) according to some embodiments are illustrated. Exiting restricted mode allows device 600 to display a different clock face (e.g., a customizable and / or changeable clock face, such as clock faces 604, 608, and 614) and perform operations that are unavailable when operating in restricted mode (e.g., accessing applications). The techniques for exiting restricted mode described below are unlikely to be accidentally executed and involve a deliberate effort by the user to exit restricted mode. In some cases, the deliberate effort involved may prevent the user from deactivating restricted mode and allow the user to remain focused on the current task. Furthermore, preventing device 600 from accidentally exiting restricted mode also allows the user to access the full functionality of the device (e.g., in case of a specific need or emergency).

[0258] exist Figure 6M In the middle, device 600 detects input 610i. In Figure 6M In this embodiment, input 610i includes pressing the pressable and rotatable input device 603. In some embodiments, input 610i includes contact on the touch-sensitive display 602 (e.g., a contact having a characteristic strength determined to be greater than a threshold strength) or rotation of the pressable and rotatable input device 603.

[0259] In response to the detection of input 610i, device 600 displays. Figure 6N The user interface 620 is shown. Figure 6NIn this configuration, user interface 620 replaces the restricted clock face 618 (e.g., device 600 stops displaying the restricted clock face 618 and displays user interface 620). In some embodiments, device 600 overlays user interface 620 onto a portion of the restricted clock face 618. User interface 620 includes information related to the restricted mode (e.g., information related to exiting restricted mode). In the example shown, user interface 620 includes a header 620-1 (“Exit Restricted Mode”), an alarm 620-2 (“Leave appeared in the restricted mode report”), and an indication 620-3 of the remaining duration of the restricted mode (“Remaining Time: 6 hours and 55 minutes”). It is advantageous to display the time range for which the restricted mode is scheduled when the user of device 600 has not set a predefined time range (e.g., if the user's parents set a predefined time range, the user may also be unaware of the duration for which the restricted mode is scheduled).

[0260] In the illustrated implementation, alarm 620-2 indicates that information indicating device 600 has exited restricted mode (e.g., an exit event) will be reported to another user. In the illustrated implementation, exiting restricted mode on device 600 will be reported to... Figure 6AA The device 650 shown. In some embodiments, an exit from restricted mode report will be sent to device 650 based on whether device 650 is associated with a user who is to receive information instructing device 600 to exit restricted mode (e.g., device 650 is associated with a user account of the user who is to receive information instructing device 600 to exit restricted mode).

[0261] In some implementations, the information indicating that device 600 has exited restricted mode is reported to another user directly (e.g., via Bluetooth or NFC) from device 600 to the receiving user's device (e.g., device 650). In some implementations, the information indicating that device 600 has exited restricted mode is reported to another user via a public network connection (e.g., Wi-Fi, Internet, LAN, etc.).

[0262] User interface 620 includes a power indicator 620-4 (labeled "Do Not Exit") for canceling the exit process. In response to the selection of power indicator 620-4, device 600 remains in restricted mode, cancels the exit process, and returns to restricted clock face 618 (e.g., stops displaying user interface 620 and displays restricted clock face 618).

[0263] User interface 620 includes a power indicator 620-5 (labeled "Exit") for exiting (unlocking, leaving) restricted mode. In the illustrated embodiments, initially, user interface 620 is partially displayed such that power indicator 620-5 is only partially displayed (e.g., a portion of user interface 620 is hidden or not displayed). In some embodiments, power indicator 620-5 can be selected while partially displayed. In some embodiments, power indicator 620-5 cannot be selected while partially displayed. In some embodiments, power indicator 620-5 is fully displayed in response to input 610i (e.g., when user interface 620 is initially displayed), without further input. In some embodiments, power indicator 620-5 is completely hidden when user interface 620 is initially displayed (e.g., when...). Figure 6N (Not visible in the middle), and the user must provide additional input to the display display 620-5 (e.g., via the scrolling user interface 620 as described below).

[0264] In response to the detection of input 610j (e.g., rotation of the pressable and rotatable input device 603, an upward drag gesture on the touch-sensitive display 602, a tap gesture on the partially displayed power indicator 620-5), the device 600 scrolls the user interface 620, thereby revealing a previously hidden portion of the user interface 620 so that the power indicator 620-5 is fully displayed, such as... Figure 6O As shown. In some embodiments, in response to the detection of input 610j, device 600 focuses on display 620-5.

[0265] In response to the detection of a selection on the power indicator 620-5 (e.g., when the focus is on the power indicator 620-5, a touch input 610k on the power indicator 620-5 or a press of the pressable and rotatable input device 603 is detected), the device 600 exits the restricted mode and stops the display of the user interface 620 (and the restricted clock face 618, if it is still displayed).

[0266] In some embodiments, in response to the detection of input corresponding to a request to exit restricted mode (e.g., input 610k), device 600 records data indicating that device 600 has stopped operating in restricted mode. In some embodiments, the recorded data includes the time during which device 600 stopped operating in restricted mode (e.g., in response to the detection of input 610k) and the duration during which device 600 did not operate in restricted mode (e.g., the amount of time between exiting restricted mode and re-entering restricted mode or reaching the end of a predefined time range). For example, device 600 records data for transmission to device 650 (e.g., the recorded data is transmitted to device 650 (directly or indirectly)). In some embodiments, device 600 begins recording data upon exiting restricted mode and optionally continues recording data while device 600 remains outside of restricted mode. In some embodiments, the data causes a report of an exit event to be displayed at device 650. In some embodiments, the recorded data is transmitted when device 600 exits restricted mode (e.g., in response to the detection of input 610k). In some implementations, the recorded data is transmitted when the device 600 re-enters restricted mode. In some implementations, the recorded data is transmitted periodically (e.g., every five minutes, every hour, or at the end of a day or week).

[0267] In the illustrated implementation, upon exiting restricted mode, device 600 replaces the restricted clock face 618 with a customizable clock face 614 as the current clock face, such as... Figure 6P As shown. In some embodiments, device 600 replaces the restricted clock face 618 with the user interface most recently displayed before entering restricted mode (e.g., the user interface 616 of a fitness application).

[0268] When exiting restricted mode, device 600 operates according to a "normal" mode that includes functions inaccessible in restricted mode. For example, in the display... Figure 6P When the clock face 614 is in the restricted mode, device 600 receives input 610l (e.g., a press of the pressable and rotatable input device 603). In response to detecting input 610l, device 600 displays a user interface 622 (e.g., an application jumper) including multiple power indicators for launching a corresponding application or user interface. The user interface 622 is not directly usable from the restricted clock face 618 compared to operation when device 600 is in restricted mode. As described above, a press of the pressable and rotatable input device 603 while the restricted clock face 618 is displayed causes the display of user interface 620. In the illustrated embodiment, device 600 must exit restricted mode to display user interface 622.

[0269] In response to the detection of a selection on the power indicator 622-1 (e.g., a tap input 610m is detected on the power indicator 622-1), the device 600 displays a user interface 624 (e.g., a settings menu). Figure 6R As shown, the user interface 624 includes power representations associated with various system features, including power representation 624-1 associated with restricted modes.

[0270] In response to the detection of a selection of the power indicator 624-1 (e.g., detection of a tap gesture input 610n), device 600 displays a user interface 626 including information related to the restricted mode. The user interface 626 includes the power indicator 626-1 (e.g., a toggle button) which indicates the state of the restricted mode and can optionally be used to activate and deactivate the restricted mode under certain conditions. Figure 6S As shown, since the current time corresponds to a predefined time range, the indicator 626-1 is deactivated (e.g., cannot be selected), as indicated by graying out. In some embodiments, when the current time does not correspond to a predefined time range, navigation to user interface 626 (e.g., via...) is possible. Figures 6P to 6R The interface and input sequence shown) and select the power indicator 626-1 to activate the restricted mode.

[0271] User interface 626 includes a report log 626-2 that indicates the occurrence of one or more devices exiting restricted mode (e.g., an exit event). Report log 626-2 includes information about the exit event associated with the restricted mode. Exit event items 626-2a to 626-2c indicate the time of exiting restricted mode (e.g., the time the exit event started) and the duration of the exit event (e.g., the amount of time the device remained outside restricted mode within a predefined time range). Exit event item 626-2a corresponds to... Figures 60 to 6P The exit event shown started at 8:05 and lasted for one minute (because...). Figure 6SThe current time in the log is 8:06. In some implementations, report log 626-2 includes information about exit events from previous days. For example, exit event items 626-2b and 626-2c provide information about exit events that occurred on the previous day. In some implementations, report log 626-2 organizes exit event items by day. In some implementations, report log 626-2 organizes exit event items by restricted mode cycle (e.g., multiple restricted mode cycles may be scheduled within a day). In some implementations, device 600 aggregates exit events from multiple devices (e.g., devices sharing a public account or associated with a single user). In some implementations, a predefined time range applies to multiple devices, and optionally, exiting restricted mode on any of the multiple devices during the predefined time range results in an exit event included in the report log. In some implementations, exit event items include an indication of the device associated with the corresponding exit event. In some implementations, report log 626-2 includes exit event items associated only with device 600.

[0272] In the illustrated implementation, after exiting restricted mode, device 600 will re-enter restricted mode (e.g., redisplay restricted clock face 618) if certain criteria are met when the current time corresponds to a predefined time range. For example, if no input is detected within a predetermined amount of time or device 600 detects input corresponding to a request to deactivate content display (e.g., a wrist gesture consistent with the user lowering his or her wrist, indicating that the user is not looking at device 600), the device re-enters restricted mode. In some implementations, device 600 displays restricted clock face 618 upon re-entering restricted mode. In some implementations, if display 602 does not display content when the criteria for re-entering restricted mode are met, device 600 displays restricted clock face 618 upon detecting the occurrence of a condition corresponding to a trigger for displaying the current clock face of device 600. In some implementations, the criteria for re-entering restricted mode include conditions corresponding to the triggering of the current clock face for displaying device 600 (e.g., device 600 does not re-enter restricted mode until a request for displaying the current clock face is received, even if other conditions (e.g., inactivity criteria) have been met).

[0273] Go to Figure 6T When device 600 is not operating in restricted mode, a clock face 614 is displayed, and the current time does not correspond to a predefined time range. In response to the detection of input 610p (e.g., an upward swipe gesture on touch-sensitive display 602), device 600 displays a user interface 628 (e.g., a control interface) with indications of various functions for controlling device 600, such as... Figure 6UAs shown. In response to detecting a selection of power indicator 628-1 (e.g., a tap gesture 610q on the touch-sensitive display 602 corresponding to the power indicator of the restricted mode), device 600 enters the restricted mode and displays a restricted clock face 618. In some embodiments, in response to detecting a selection of power indicator 626-1, device 600 displays as shown. Figure 6S The user interface 626 shown differs in that the power indicator 626-1 is selectable (e.g., not grayed out), such that selecting the power indicator 626-1 causes the device 600 to enter a restricted mode and display a restricted clock face 618. In these ways, the user can voluntarily activate the restricted mode via input at the device 600. In some embodiments, such as Figures 6T to 6U The manual activation of the restricted mode, as shown, causes device 600 to remain in restricted mode indefinitely until the user manually exits it. In some embodiments, if the user manually activates the restricted mode and device 600 remains in restricted mode until the current time corresponds to a predefined time range, device 600 will deactivate the restricted mode when the predefined time range expires (e.g., even if the user does not manually deactivate the restricted mode). In some embodiments, if the user manually activates the restricted mode and device 600 remains in restricted mode until the current time corresponds to a predefined time range, device 600 will remain in restricted mode when the predefined time range expires (e.g., until the restricted mode is manually deactivated).

[0274] After device 600 enters restricted mode at 3:30 PM, such as Figure 6V As shown, device 600 remains in restricted mode. While device 600 is still in restricted mode, device 600 detects input 610r (e.g., a press of the pressable and rotatable input device 603) at 4:00 PM, as... Figure 6W As shown. In response to the detection of input 610r, device 600 displays a user interface 630 including information about the restricted mode. Figure 6X The user interface 630 includes a header 630-1 (“Exit Restricted Mode”), a message 630-2 indicating how long the device 600 has been in restricted mode (“You have been in restricted mode for 30 minutes”), and indications 630-3 and 630-4. Displaying how long the device 600 has been in restricted mode in the user interface 630 encourages some users to remain in restricted mode or re-enter restricted mode in the future (e.g., a user might be rewarded by his or her parents for not using certain features of the device during a period intended for study).

[0275] User interface 620 is displayed when device 600 is in restricted mode due to manual input (e.g., selection of power indicator 628-1), compared to user interface 630, which is displayed when device 600 is in restricted mode due to the current time corresponding to a predefined time range. That is, in the illustrated embodiment, the response of device 600 to input detected while operating in restricted mode (or when displaying restricted clock face 618) depends on the conditions for entering restricted mode (e.g., whether device 600 operates in restricted mode due to predefined conditions or resource user input at device 600).

[0276] exist Figure 6X In the process, device 600 detects input 610s (e.g., rotation of a pressable and rotatable input device 603). In response to detecting input 610s, device 600 scrolls the user interface 630, as... Figure 6Y As shown. In some embodiments, device 600 exits restricted mode in response to the detection of input 610t (e.g., a tap gesture on power indicator 630-4). In some embodiments, after selecting power indicator 630-4, device 600 will not automatically re-enter restricted mode or redisplay restricted clock face 618 in response to meeting inactivity criteria (e.g., since manually entering restricted mode). In some embodiments, device 600 will re-enter restricted mode and redisplay restricted clock face 618 in response to meeting inactivity criteria until via... Figure 6S The user interface 626 in the middle displays the power indicator 626-1 to deactivate the restricted mode.

[0277] Figure 6Z This illustrates techniques for exiting restricted mode according to some implementation schemes. In response to the detection of input 610i ( Figure 6M ), input 610j ( Figure 6N ), input 610r ( Figure 6W ) or enter 610s ( Figure 6X The device 600 displays a user interface 632 that indicates whether the device 600 is exiting restricted mode or will exit restricted mode in response to rotation of the pressable and rotatable input device 603. In response to detection... Figure 6Z When input 610u is made (e.g., a pressable and rotatable input device 603 rotates), device 600 exits restricted mode. Figure 6Z The depicted technology illustrates that, in some embodiments, device 600 exits restricted mode directly from or indirectly from restricted clock face 618 (e.g., via user interface 620 or 630) in response to rotation of pressable and rotatable input device 603.

[0278] Figures 6AA to 6ACThe technique for viewing information about restricted modes and setting parameters for restricted modes (e.g., restricted modes on device 600) is shown.

[0279] Figure 6AA Device 650 (e.g., device 100 or 300) is shown. In some embodiments, device 650 is paired with device 600 (e.g., there is a direct communication link between devices 600 and 650) and / or associated with an account (e.g., a user account) that is also associated with device 600.

[0280] exist Figure 6AA In this context, device 650 displays user interface 634 (e.g., a screen time settings menu). User interface 634 includes items 634-1 corresponding to the user interface associated with the restricted mode (e.g., a power indicator). In response to detecting a selection of item 634-1 (e.g., a tap gesture 610v on item 634-1), device 650 displays... Figure 6AB The user interface 636 is depicted. User interface 636 includes items 636-1 and 636-2 (e.g., power indicators) associated with restricted mode information (e.g., settings) corresponding to the respective user. For example, item 636-1 corresponds to restricted mode information associated with user Emma. In the illustrated embodiment, items are listed according to user (e.g., Emma, ​​Johnny, etc.). In some embodiments, items are listed according to specific device (e.g., Emma's watch, Emma's phone, Johnny's watch).

[0281] In response to the detection of input 610w (e.g., a tap gesture on item 636-1), device 650 displays Figure 6ACThe user interface 638 is shown. User interface 638 includes information about the restricted modes of user Emma. In some embodiments, user interface 638 aggregates data from multiple devices associated with user Emma. In some embodiments, user interface 638 displays information on a per-device basis. User interface 638 includes a power indicator 638-1 (e.g., a toggle button) for activating and deactivating the restricted modes of Emma's devices (e.g., devices associated with Emma, ​​devices associated with the user account associated with Emma). In some embodiments, selecting power indicator 638-1 activates the restricted mode of Emma's device. In some embodiments, activating the restricted mode via device 650 causes Emma's device to activate the restricted mode (e.g., selecting the power indicator causes data to be sent to Emma's device, thereby causing Emma's device to activate the restricted mode). In some embodiments, activating the restricted mode via device 650 causes Emma's device to activate the restricted mode according to a defined schedule. In the illustrated implementation, Emma's device is configured to be activated from 8 AM to 3 PM (e.g., Emma's device has a predefined time range from 8 AM to 3 PM, such that Emma's device operates in restricted mode between 8 AM and 3 PM).

[0282] In some implementations, the restricted mode setting can be configured according to a custom schedule. User interface 638 includes a power indicator 638-4 for displaying information (e.g., instructions) regarding when Emma's device is restricted. In response to detecting a selection of power indicator 638-2 (“Custom”), device 650 displays a user interface for editing / setting a customizable schedule according to which Emma's device will operate in restricted mode. For example, device 650 provides a user interface for customizing a daily restricted mode schedule (e.g., “Monday 8AM-3PM and Tuesday 7AM-2:30PM” or “MF 7:30AM-3PM and Sat-Sun Off”). In some implementations, predefined time ranges are defined according to a schedule specifying different time ranges for different days of the week.

[0283] User interface 638 includes report log 638-3, which shows the time and duration of the exit event (referred to as "unlock" in user interface 638) that instructs user Emma's device to exit restricted mode. As described above, a device remote from device 650 (e.g., device 600) may log data indicating that the remote device has stopped operating in restricted mode. This data is obtained by device 650 and used to generate report log 638-3. In some embodiments, the logged data is transmitted (directly or indirectly) to device 650. In some embodiments, the logged data is obtained when the remote device exits restricted mode. In some embodiments, the logged data is obtained when the remote device re-enters restricted mode. In some embodiments, the logged data is obtained periodically (e.g., every five minutes, every hour, or at the end of a day or week).

[0284] Report log 638-3 groups exit events by day (e.g., "today", "yesterday"). In some embodiments, user interface 638 can be scrolled to display additional exit events (e.g., exit events for the days preceding "Wednesday"). In some embodiments, report log 638-3 groups exit events by restricted mode period (e.g., if there is more than one predefined time range in a day (e.g., 8AM-1PM and 2PM-3:30PM), report log 638-3 groups exit events by predefined time range). Report log 638-3 includes exit event items 638-3a to 638-3f indicating the time of restricted mode exit (unlock) and the duration of the exit event (e.g., how long the restricted mode was unlocked). In some embodiments, report log 638-3 includes additional information compared to report log 626-2 displayed on device 600 (e.g., because device 650 has a larger display size). For example, in some implementations, report log 638-3 includes an indication of the device associated with the exit event item (e.g., an icon representing a laptop, phone, or watch to indicate which device (or type of device) exited restricted mode at the time and duration indicated in the corresponding exit event item). In some implementations, report log 626-2 displayed on device 600 includes an indication of the device associated with the exit event item.

[0285] In some implementations, if device 650 is associated with user Emma and configured to operate in restricted mode according to a schedule indicated on user interface 638, then report log 638-3 includes exit event entries corresponding to the time and duration when device 650 exits restricted mode.

[0286] Figure 7This is a flowchart illustrating a method for operating an electronic device in a restricted operating mode according to some embodiments. Method 700 is performed at a device (e.g., 100, 300, 500, 600, 650) having a display device. Some operations in method 700 are optionally combined, some operations are optionally changed in order, and some operations are optionally omitted.

[0287] As described below, method 700 provides an intuitive way to switch between user interfaces. This method reduces the cognitive burden on users when switching between user interfaces, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to switch between user interfaces automatically and more efficiently saves power and increases the time between battery charging sessions.

[0288] An electronic device (e.g., 600) has a display device (e.g., 602), a display (702) via the display device, and a first user interface (e.g., 604) (e.g., a first clock face) of a corresponding user interface type (e.g., current clock face) for the electronic device. In some embodiments, the first user interface of the corresponding user interface type includes one or more elements in a first arrangement (e.g., 604-1, 604-2, 604-3) (e.g., at least a first element and a second element in the first arrangement). In some embodiments, the first element displays information of a first type (e.g., time), and the second element displays information of a second type (e.g., information from a health or music application). In some embodiments, the first user interface is a graphical user interface that includes a clock face with time indication and optionally one or more user interface elements (e.g., complication blocks) representing information other than time.

[0289] In some implementations, the corresponding user interface type is a clock face.

[0290] In some embodiments, the electronic device detects (704) a sequence of one or more inputs (e.g., activation of a touch and / or rotatable input mechanism on a touch-sensitive display, such as pressing or rotating) (e.g., 610a, 610b, and / or 610c) corresponding to a request to change the current user interface (e.g., current clock face) of a corresponding user interface type of the electronic device (e.g., entering a user interface editing mode and / or a user interface selection mode, editing visual elements of a first user interface, or selecting a different user interface, and confirming the selection of an edited or different user interface). In some embodiments, when the first user interface is displayed, at least one input of the sequence of one or more inputs is detected (e.g., 601a).

[0291] In some embodiments, in response to detecting a sequence of one or more inputs corresponding to a request to change the current user interface of the corresponding user interface type of the electronic device, the electronic device displays (706) a second user interface (e.g., 608) of the corresponding user interface type as the current user interface of the corresponding user interface type of the electronic device via a display device. In some embodiments, the second user interface of the corresponding user interface type includes one or more elements (e.g., 608-1, 608-2, 608-3, 608-4, 608-5, and 608-6) that are different from and / or in an arrangement different from the first user interface of the corresponding user interface type and in a different arrangement than the first arrangement of the first user interface of the corresponding user interface type (e.g., the second user interface is an edited (customized) version of the first user interface (e.g., user-selected colors and / or complex function blocks for a predefined layout)). In some embodiments, the second user interface is a different style of the user interface (e.g., the user can customize the user interface by selecting a specific (second) user interface). In some embodiments, the style of the user interface is defined by user interface elements on the user interface (e.g., the number and type of complex function blocks), the layout of the user interface (e.g., the arrangement of elements), or time indication (e.g., digital or analog in the case of a clock face). In some implementations, a sequence of one or more inputs corresponds to the selection of features of a second user interface.

[0292] Responding to the detection of a sequence of one or more inputs, displaying a second user interface having one or more elements that are different from and / or in an arrangement different from the first arrangement of the one or more elements of the first user interface provides additional control options and customization for the device's user interface. Providing additional control options and customization for the user interface enhances the operability of the device and makes the user-device interface more efficient (e.g., by providing relevant interfaces and assisting users in providing appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends the device's battery life by enabling users to use the device more quickly and efficiently.

[0293] In some embodiments, the second user interface of the corresponding user interface type includes a first power indicator (e.g., 614-1) corresponding to an application (e.g., a fitness application). In some embodiments, when displaying the second user interface of the corresponding user interface type, the electronic device detects input corresponding to a selection of the first power indicator (e.g., 610h). In some embodiments, in response to detecting input corresponding to a selection of the first power indicator, the electronic device launches the application (e.g., 616). In some embodiments, in contrast to the second user interface, the user interface corresponding to a restricted mode (e.g., 618) does not include graphical elements (e.g., power indicators) that can be selected to launch the corresponding application or function.

[0294] In some embodiments, when displaying a second user interface of a corresponding user interface type, the electronic device detects a third sequence of one or more inputs (e.g., activation of touch and / or rotatable input mechanisms on a touch-sensitive display, such as pressing or rotating). In some embodiments, in response to detecting a third sequence of one or more inputs when displaying a second user interface of a corresponding user interface type, the electronic device performs an operation (e.g., opening an application, displaying a taskbar for recently opened or specified (e.g., favorite) applications, displaying an application jump (e.g., 622, multiple icons for launching the corresponding application), displaying a notification center (e.g., a notification list), switching to a system space different from the current system space, editing the current user interface or entering a user interface editing or selection mode, or launching an application corresponding to a complex function block). In some embodiments, when a restricted mode is active, a do-not-disturb mode is enabled. In some embodiments, when displaying a third user interface of a corresponding user interface type (e.g., a restricted clock face 618), the electronic device detects a third sequence of one or more inputs (e.g., inputs of the same type detected in the same order when displaying the second user interface). In some embodiments, in response to detecting a third sequence of one or more inputs when displaying a third user interface of a corresponding user interface type, the electronic device abandons the execution of the operation. In some implementations, operations that can be performed when the electronic device is not operating in restricted mode (e.g., sending emails and text messages, accessing web browsing applications, presenting notifications) cannot be performed when the electronic device is operating in restricted mode (e.g., the electronic device must exit restricted mode to be able to perform these operations). In some implementations, the execution of operations is modified when in restricted mode (e.g., a notification of a phone call is presented only after multiple call attempts have been received, rather than on the first attempt).

[0295] In some embodiments, the electronic device displays the user interface (e.g., 616) of a first application (e.g., an application other than the one used to generate the clock face; an application not part of the operating system) before detecting the occurrence of a condition corresponding to the triggering of the current user interface of the corresponding user interface type for displaying the electronic device. In some embodiments, displaying a third user interface of the corresponding user interface type (e.g., 618) includes stopping the display of the user interface of the first application. In some embodiments, stopping the display of the user interface of the first application includes suspending or closing the first application.

[0296] In some implementations, after the current user interface of the corresponding user interface type of the electronic device is changed to a second user interface of the corresponding user interface type, the electronic device detects (708) the occurrence of a condition (e.g., tap, wrist lift, button press, application closure, etc.) corresponding to the triggering of the current user interface of the corresponding user interface type of the electronic device.

[0297] In some implementations, in response to (710) the detection of the occurrence of a condition corresponding to the triggering of the current user interface of the corresponding user interface type for displaying the electronic device: based on determining that the current time corresponds to a predefined time range (e.g., the current time is within a predefined time range; an absolute time range (e.g., 9am-3pm) and / or a relative time range (e.g., within a defined amount of time (e.g., 1 hour) from the event or defined time)), the electronic device displays (712) a third user interface (e.g., 618) (e.g., a third clock face) of the corresponding user interface type via a display device, which is different from the first user interface of the corresponding user interface type and the second user interface of the corresponding user interface type (e.g., if the second user interface is displayed when the current time reaches the predefined time range, the display of the second user interface is stopped and replaced with the third user interface).

[0298] Based on the determination that the current time corresponds to a predefined time range, a third user interface of the corresponding user interface type (this third user interface is different from the first user interface and the second user interface of the corresponding user interface type) is displayed. Operations are performed when a set of conditions have been met without further user input. Performing operations when a set of conditions have been met without further user input enhances device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0299] In some embodiments, the third user interface of a corresponding user interface type includes a predefined set of elements (e.g., 618-1, 618-2, 618-3, and 618-4), which differs from one or more elements of a first user interface of the corresponding user interface type and one or more elements of a second user interface of the corresponding user interface type. In some embodiments, the predefined set of elements cannot be changed (e.g., edited or removed) in response to input detected at the electronic device. In some embodiments, the predefined set of user interface elements of the third user interface (e.g., 618-1, 618-2, 618-3, and 618-4) has a predefined configuration or layout different from the configuration or layout of the first set of user interface elements of the second user interface. In some embodiments, the third user interface corresponds to a restricted mode and is unavailable when the restricted mode is not activated (e.g., the third user interface is unavailable in face selection mode). In some embodiments, the user cannot select which user interface the third user interface will be (e.g., the user cannot select which user interface will be displayed in restricted mode). In some embodiments, the third user interface is a static system setting. In some implementations, the third user interface features cannot be edited using an electronic device, regardless of whether the restricted mode is active (e.g., the third user interface is not available in face editing mode, or is displayed in editing mode but cannot actually be edited).

[0300] In some embodiments, when the current time corresponds to a predefined time range and the electronic device is operating in a first mode (e.g., a restricted mode), the electronic device detects a fifth sequence of one or more inputs (e.g., 610i, 610j, 610k, 610r, 610s, 610t) (e.g., an input sequence for exiting the restricted mode; e.g., activation of a touch and / or rotatable input mechanism on a touch-sensitive display (e.g., pressing or rotating)). In some embodiments, the fifth sequence of one or more inputs includes at least one input (e.g., 610i, 610r) detected when a third user interface of the corresponding user interface type is displayed (e.g., the sequence of one or more inputs begins when the user interface is displayed). In some embodiments, in response to detecting the third sequence of one or more inputs, the electronic device exits the first mode (e.g., ...). Figures 60 to 6P In some implementations, exiting the first mode includes displaying a second user interface of the corresponding user interface type (e.g., 614).

[0301] In some implementations, this applies when the current time corresponds to a predefined time range (e.g., the current time is still within a specified window in restricted mode), and when a third user interface of the corresponding user interface type is not displayed (e.g., Figures 6P to 6SThe device has detected and has done so a request to exit the third user interface and exit restricted mode. The electronic device detects (e.g., automatically, or in the absence of user input) a redisplay criterion for the corresponding user interface type. In some embodiments, the third user interface redisplay criterion includes one or more of the following criteria: no user input is detected within a predetermined time period, or input corresponding to a request to deactivate content displayed on the display device of the electronic device is detected. In some embodiments, in response to detecting a redisplay criterion for the corresponding user interface type, the electronic device displays (e.g., redisplays) the third user interface of the corresponding user interface type.

[0302] In some embodiments, the third user interface of the corresponding user interface type includes an analog indication of time (e.g., 618-1) and a digital indication of time (e.g., 618-3). In some embodiments, the third user interface includes a date indication (e.g., 618-2).

[0303] In some implementations, the element corresponding to the current hour of the current time is visually emphasized relative to the element corresponding to the hour other than the current hour in the analog indication of time (e.g., 618-1a).

[0304] In some implementations, after the first user interface of the first application is stopped from being displayed (e.g., 616), the electronic device continues to run the first application in the background (e.g., even if the electronic device will not be allowed to launch the first application during the restricted mode of displaying the third user interface, the electronic device continues to run the first application in the background to enable the electronic device to complete the operation being performed by the first application). In some implementations, when the operation performed by the first application is completed, the electronic device does not allow new operations to be initiated for the first application while in restricted mode. For example, if a user is running a fitness tracking operation of a fitness application, the user can complete the workout during a predefined time range corresponding to the third user interface (e.g., in restricted mode), but cannot start recording a new workout. In some implementations, if the application is displayed in the foreground when the predefined time range is reached at the current time, the electronic device displays the third user interface and continues to run the application in the background.

[0305] In some embodiments, displaying a third user interface of the corresponding user interface type includes: based on determining that the first application is running in the background, displaying a third user interface of the corresponding user interface type having graphical elements corresponding to the first application (e.g., 618-5) (e.g., an icon indicating that the first application is running in the background). In some embodiments, displaying a third user interface of the corresponding user interface type includes: based on determining that the first application is not running (e.g., closed or suspended), displaying a third user interface of the corresponding user interface type without graphical elements corresponding to the first application. Displaying a third user interface without graphical elements corresponding to the first application provides feedback on the status of the first application (e.g., the first application is no longer running).

[0306] In some embodiments, the third user interface of the corresponding user interface type includes an indication of the username (e.g., 618-4; full first and last name, first name only, first name and first letter of last name, first letter only (e.g., first letter of first name and first letter of last name)). In some embodiments, the username is customizable (e.g., via an electronic device or external device). In some embodiments, the third user interface of the corresponding user interface type includes a numerical indication of the time (e.g., 618-3).

[0307] In some implementations, a predefined set of elements encompasses the entire third user interface of the corresponding user interface type (e.g., because the predefined set of user interface elements of the third user interface cannot change in response to input detected at the electronic device when operating in restricted mode, no element of the third user interface can change in response to input detected at the electronic device), and additional elements cannot be added to the third user interface of the corresponding user interface type. In some implementations, one or more elements of the third user interface (e.g., a user interface in restricted mode) (e.g., 618-4) are based on the user associated with the electronic device. For example, in some examples, the third user interface includes an indication of the username. In some implementations, the name appearing on the third user interface can be changed by editing the name associated with the electronic device (e.g., the entire device, via system-level settings), but cannot be changed at the "user interface" level (e.g., in clock face editing mode). In some implementations, the user cannot add, edit, or remove complex functional blocks of the third user interface (e.g., a clock face). In some implementations, the user cannot add, edit, or remove the time indication of the third user interface. In some implementations, inputs received when displaying other user interfaces for entering a user interface selection mode (e.g., clock face selection mode) or a user interface editing mode (e.g., clock face editing mode) (e.g., contact on a touch-sensitive surface held for a duration longer than a threshold (long press) or contact with a characteristic strength greater than a threshold strength (forceful press)) will not cause the electronic device to enter the same mode when receiving the same input when displaying a third user interface.

[0308] In some embodiments, the third user interface of a corresponding user interface type includes a distinguishing element (e.g., 618-1b) (e.g., a graphic element; a yellow ring with an outer diameter substantially the same as the size of the display device (e.g., an outer diameter greater than 90% of the width of the display)). In some embodiments, the distinguishing element is a visually distinguishable portion of the third user interface of the corresponding user interface type (e.g., the first element is not an arbitrarily defined area), and the distinguishing element is not included in the first user interface of the corresponding user interface type or the second user interface of the corresponding user interface type. In some embodiments, the first user interface and the second user interface (or any user interface other than the third user interface) cannot change to include the distinguishing element in response to input detected at the electronic device. In some embodiments, the distinguishing element is displayed via the display device only when the third user interface is the current user interface (e.g., the first element is unique to the third user interface). In some embodiments, the distinguishing element is in the foreground of the third user interface (e.g., the distinguishing element is not a background image).

[0309] In some implementations, in response to (710) the detection of a condition corresponding to the triggering of the current user interface of the corresponding user interface type for displaying the electronic device: based on the determination that the current time does not correspond to a predefined time range, the electronic device displays (714) a second user interface of the corresponding user interface type.

[0310] The second user interface is displayed when the current time does not correspond to a predefined time range, and the operation is performed when a set of conditions have been met without further user input. Performing the operation when a set of conditions have been met without further user input enhances device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0311] In some implementations, when the current time does not correspond to a predefined time range (e.g., the current time is not within the window of the restricted mode): the electronic device displays a user interface (e.g., 628) via a display device, including a power indication for activating the restricted mode (e.g., 628-1) (e.g., a control center). In some implementations, activating the restricted mode includes displaying a third user interface. In some implementations, the electronic device detects input (e.g., 610q) corresponding to a selection for activating the power indication of the restricted mode. In some implementations, in response to detecting input corresponding to a selection for activating the power indication of the restricted mode, the electronic device operates in a restricted mode (e.g., the restricted mode can be activated via user input at the electronic device). In some implementations, the predefined time range during restricted mode operation cannot be changed via input at the electronic device (e.g., edited, turned on, or turned off) (e.g., the predefined time range can only be set using an external electronic device).

[0312] In some embodiments, the electronic device detects a second sequence of one or more inputs (e.g., 610a) (e.g., a tap on a complex function block of the second user interface at a location on the first user interface). In some embodiments, in response to detecting a third sequence of one or more inputs: based on the second sequence of one or more inputs detected when displaying a first user interface of a corresponding user interface type, the electronic device performs an operation (e.g., launching an application corresponding to the selected complex function block). In some embodiments, in response to detecting a second sequence of one or more inputs: based on the third sequence of one or more inputs detected when displaying a first user interface of a corresponding user interface type, the electronic device abandons the operation. In some embodiments, the electronic device abandons all operations (e.g., in response to the same input that caused the operation performed when displaying the first user interface, the electronic device does not perform any operation when displaying the third user interface, not just the operation performed when displaying the first user interface). In some embodiments, in response to detecting a second sequence of one or more inputs when displaying the third user interface, the electronic device performs a second operation different from that operation.

[0313] In some embodiments, after displaying a third user interface of the corresponding user interface type (e.g., during or after operation in restricted mode), the electronic device detects the occurrence of an inactivity condition (e.g., screen timeout or wrist release). In some embodiments, after displaying a third user interface of the corresponding user interface type (e.g., during or after operation in restricted mode), in response to detecting the occurrence of an inactivity condition, the electronic device deactivates the display device (e.g., stops displaying content on the display, dims the display, puts the display to sleep, de-energizes the illumination elements of the display device, etc.). In some embodiments, the display is a touchscreen display, and deactivating the display includes stopping the display of content without deactivating the touch sensing elements of the display. In some embodiments, after displaying a third user interface of the corresponding user interface type (e.g., during or after operation in restricted mode), after deactivating the display device, the electronic device detects the occurrence of a condition corresponding to the triggering of the current user interface of the corresponding user interface type used to display the electronic device (e.g., tap, wrist release, button press, application closure, etc.).

[0314] In some embodiments, after displaying a third user interface of the corresponding user interface type (e.g., during or after operation in restricted mode), in response to detecting the occurrence of a condition corresponding to the triggering of the current user interface of the corresponding user interface type for displaying the electronic device: based on determining that the current time corresponds to a predefined time range (e.g., the current time is within the restricted mode window), the electronic device displays the third user interface of the corresponding user interface type (e.g., 618) (e.g., displaying a face associated with the restricted mode). In some embodiments, after displaying a third user interface of the corresponding user interface type (e.g., during or after operation in restricted mode), in response to detecting the occurrence of a condition corresponding to the triggering of the current user interface of the corresponding user interface type for displaying the electronic device: based on determining that the current time does not correspond to a predefined time range (e.g., the current time is not within the restricted mode window), the electronic device displays a second user interface of the corresponding user interface type (e.g., 608) (e.g., displaying a user interface unavailable in restricted mode (e.g., a customizable user interface)).

[0315] In some embodiments, when displaying a third user interface of a corresponding user interface type, the electronic device detects a fourth sequence (e.g., 610i, 610j, 610k, or 610r, 610s, 610t) of one or more inputs (e.g., touch on a touch-sensitive display and / or activation of a rotatable input mechanism, e.g., pressing or rotating). In some embodiments, the fourth sequence of one or more inputs corresponds to a process for exiting a restricted mode, which allows the electronic device to switch from a predefined third user interface to a customizable user interface (e.g., a first user interface or a second user interface).

[0316] In some implementations, in response to the detection of at least one input in a fourth sequence of one or more inputs, the electronic device displays an exit user interface (e.g., 620, 630) with information for transitioning from a first mode to a second mode (e.g., the interface is overlaid on a portion of a third user interface or replaces the third user interface), wherein the second mode includes one or more functions that are inaccessible when in the first mode (e.g., switching to a separate user interface with a title (“Exit Restricted Mode”), notification messages (“Leaving has appeared in the school time report”, “Remaining time: 8 minutes”, or “You have been in restricted mode for 2 hours and 5 minutes”), and an exit / non-exit indication; the user input in the fourth sequence may include pressing a button, rotating a rotatable input mechanism, or tapping on a display.

[0317] The user interface displays information for transitioning from a first mode to a second mode, where the second mode includes one or more functions that were inaccessible in the first mode (e.g., by notifying the user of a significant change in operation). Providing improved feedback enhances device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends device battery life by enabling users to use the device more quickly and effectively.

[0318] In some embodiments, stopping operation of the electronic device in the first mode includes switching to an operation mode in which operations that are not available in the first mode can be performed. In some embodiments, stopping operation of the electronic device in the first mode includes displaying a different user interface with functions that are not available in the initial user interface.

[0319] In some embodiments, the exit user interface includes a first portion comprising a power indicator for exiting a first mode (e.g., 620-5, 630-4). In some embodiments, the electronic device detects an input corresponding to a selection of the power indicator for exiting the first mode (e.g., 610k, 610t). In some embodiments, in response to detecting an input corresponding to a selection of the power indicator for exiting the first mode, the electronic device displays a second user interface of the corresponding user interface type (e.g., tapping the exit power indicator or pressing a pressable and rotatable input mechanism while the exit power indicator is in focus to stop operating the electronic device in the first mode and return to the second user interface).

[0320] Responding to the detection of input corresponding to the selection of the power indicator for exiting the first mode, displaying a second user interface of the appropriate user interface type (e.g., instead of the third user interface associated with the first mode) allows the user to provide positive input for exiting the first mode. Displaying the power indicator for exiting the first mode provides feedback to the user regarding the positive input that can be used to exit the first mode. Allowing the user to provide positive input that improves feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends the device's battery life by enabling the user to use the device more quickly and efficiently.

[0321] In some embodiments, when the exit user interface is displayed without displaying a first portion of the exit user interface including a power indicator for exiting the first mode (e.g., the user interface includes multiple portions not displayed simultaneously), the electronic device detects input corresponding to a request to scroll the exit user interface (e.g., 610j, 610S). In some embodiments, in response to detecting input corresponding to a request to scroll the user interface, the electronic device scrolls the user interface (e.g., 620, 630) to display a first portion of the user interface including a power indicator for exiting the first mode (e.g., initially, the exit power indicator is slightly or completely off the screen, so the user must scroll before selecting it to avoid accidental activation).

[0322] The first part of the user interface, which scrolls to display a power indicator for exiting the first mode in response to detected user input, adds an additional action for performing the exit process. In this case, adding additional input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends the device's battery life by enabling the user to use the device more quickly and efficiently.

[0323] In some embodiments, in response to the detection of at least one input in a sequence of one or more inputs, a user interface including a power indication for exiting the first mode is displayed. In some embodiments, the user interface including a power indication for exiting the first mode is displayed simultaneously with the presentation of an alarm (e.g., 620-2), which indicates that information indicating the electronic device has exited the first mode will be reported to another user (e.g., a button is slightly off the screen so that the user must scroll before selecting it to avoid accidental activation).

[0324] In some embodiments, a fourth sequence of detecting one or more inputs for exiting a restricted mode includes detecting rotation of a rotatable input mechanism (e.g., 603). In some embodiments, in response to detecting rotation of the rotatable input mechanism, the electronic device displays a second user interface of a corresponding user interface type (e.g., and stops operating the electronic device in the first mode). In some embodiments, while displaying a third user interface, the electronic device exits the first mode in response to rotation of the rotatable input mechanism. In some embodiments, the electronic device replaces the third user interface with a different user interface (e.g., 620) in response to the first input, and then exits the first mode in response to rotation of the rotatable input mechanism while displaying the different user interface (e.g., rotation of the rotatable input mechanism is a confirmation input).

[0325] It should be noted that the above description is in contrast to the process described in method 700 (e.g., Figure 7The details of the above also apply in a similar manner to the methods described below. For example, methods 800 and 1000 optionally include one or more features of the various methods described above with reference to method 700. For example, operations 702 to 706 related to changing the user interface are optionally performed before operation 802 of method 800. As another example, operations 708 to 712 can be used to display a user interface of the corresponding user interface type in operation 804 of method 800. For the sake of brevity, these details will not be repeated below.

[0326] Figure 8 This is a flowchart illustrating a method for providing an alarm using an electronic device according to some embodiments. Method 800 is performed at a device (e.g., 100, 300, 500, 600, 650) having a display device. Some operations in method 800 are optionally combined, some operations are optionally changed in order, and some operations are optionally omitted.

[0327] As described below, method 800 provides an intuitive way to deliver alerts. This method reduces the cognitive burden on users when reporting alerts, thus creating a more efficient human-machine interface. For battery-powered computing devices, it enables users to deliver alerts faster, automatically, and more efficiently, saving power and increasing the interval between battery charges.

[0328] An electronic device (e.g., 600) having a display device (e.g., 602) operates in a first mode (e.g., a restricted mode, in which most operations available in other operating modes of the electronic device are unavailable) (802).

[0329] In some implementations, when the electronic device is operated in a first mode: the electronic device displays (804) a user interface (e.g., 618) of the corresponding user interface type (e.g., clock face) via a display device (e.g., 602).

[0330] In some implementations, when the electronic device is operated in a first mode: the electronic device detects (806) a first sequence (e.g., 610i, 610j, 610k) of one or more inputs (e.g., activation of a touch and / or rotatable input mechanism on a touch-sensitive display, e.g., pressing or rotating) corresponding to a request to exit the first mode, the first sequence of one or more inputs including at least one input (e.g., 610i) detected when a user interface of the corresponding user interface type is displayed (e.g., the sequence of one or more inputs begins when the user interface is displayed).

[0331] In some implementations, the corresponding user interface type is a clock face (e.g., 618).

[0332] In some implementations, the electronic device includes a touch-sensitive surface device (e.g., separate from or part of a display device), and a first sequence of one or more inputs includes a tapping gesture on a touch-sensitive surface (e.g., a touch-sensitive display).

[0333] In some embodiments, the electronic device includes a rotatable and pressable input mechanism (e.g., 603) that is rotatable relative to the housing of the electronic device (e.g., the rotatable and pressable input mechanism rotates about an axis parallel to the display of the display device), and a first sequence of one or more inputs includes pressing the rotatable and pressable input mechanism.

[0334] In some implementations, when the electronic device is operated in a first mode: after (e.g., in response to) detecting at least one input in a first sequence of one or more inputs and before stopping the operation of the electronic device in the first mode, the electronic device presents (808) an alarm (e.g., 620-2) indicating that the information indicating that the electronic device has exited the first mode will be reported to another user.

[0335] Presenting an alert indicating that the electronic device has exited first mode, which will be reported to another user, provides the user with improved feedback on the effectiveness of continuing to exit the electronic device's first mode. Providing improved feedback enhances device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends device battery life by enabling users to use the device more quickly and effectively.

[0336] In some embodiments, after (e.g., in response to) detecting at least one input in a first sequence of one or more inputs and before ceasing operation of the electronic device in the first mode, the electronic device displays an indication of the duration of operation in the first mode via a display device (e.g., 630-2). In some embodiments, the indication of the duration of continuous operation of the electronic device in the first mode is displayed simultaneously with the presentation of an alarm indicating that the electronic device has exited the first mode and that it will be reported to another user.

[0337] In some embodiments, when the electronic device is operated in a first mode: after an alarm is presented, the electronic device detects (810) a second sequence of one or more inputs (e.g., 610j, 610k). In some embodiments, the second sequence of one or more inputs is a rotation of a rotatable mechanism of the electronic device. In some embodiments, the alarm includes an indication of power for exiting the first mode (e.g., 620-5), and the second sequence of one or more inputs includes an input corresponding to the selection of the indication of power.

[0338] The included power indicator provides improved visual feedback on inputs available for exiting the first mode. This improved visual feedback enhances device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device). Additionally, it reduces power consumption and extends device battery life by enabling users to use the device more quickly and effectively.

[0339] In some embodiments, the power indicator is an exit power indicator. In some embodiments, selection of the power indicator is a tap on the exit power indicator or a press of a pressable input mechanism when the exit power indicator is in focus. In some embodiments, the exit power indicator is displayed in response to the detection of at least one input in a first sequence of one or more inputs. In some embodiments, the exit power indicator is displayed simultaneously with an alarm that indicates that the electronic device has exited a first mode and will be reported to another user.

[0340] In some embodiments, presenting an alarm includes displaying an alarm user interface (e.g., 620) (e.g., overlaid on a portion of the user interface or replacing the user interface), and the alarm user interface includes a first portion including a power indicator for exiting a first mode. In some embodiments, while displaying the alarm user interface without displaying the first portion of the alarm user interface including the power indicator for exiting the first mode (e.g., the user interface includes multiple portions not displayed simultaneously), the electronic device detects input corresponding to a request to scroll the alarm user interface (e.g., 610j). In some embodiments, in response to detecting input corresponding to a request to scroll the alarm user interface, the electronic device scrolls the alarm user interface to display the first portion of the alarm user interface including the power indicator for exiting the first mode (e.g., initially, the power indicator is slightly or completely off the screen, so the user must scroll before selecting it to avoid accidental activation). In some embodiments, the user interface is displayed in response to detecting at least one input in a first sequence of one or more inputs. In some embodiments, the user interface is displayed simultaneously with an alarm indicating that the electronic device has exited the first mode and will be reported to another user.

[0341] In some embodiments, when operating the electronic device in a first mode: in response to detecting a second sequence of one or more inputs and based on determining that the second sequence of one or more inputs corresponds to a request to exit the first mode, the electronic device stops (812) operating the electronic device in the first mode (e.g., exits the first mode). In some embodiments, stopping operating the electronic device in the first mode includes switching to an operating mode in which operations unavailable in the first mode can be performed. In some embodiments, stopping operating the electronic device in the first mode includes displaying a different user interface (e.g., 618) with functions unavailable in the initial user interface.

[0342] Exiting the first mode allows electronic devices to perform additional functions and provide improved feedback to user input. This enhances device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and effectively.

[0343] In some embodiments, in response to the detection of a second sequence of one or more inputs and based on a request to exit the first mode by determining that the second sequence of one or more inputs corresponds to an exit from the first mode, the electronic device records (e.g., for transmission to a second electronic device; recording begins (e.g., recording continues while the device remains outside the first mode) data indicating that the electronic device has stopped operating in the first mode (e.g., the recorded data is transmitted to an external device; the data causes a report of an exit event to be displayed on the external device). In some embodiments, information is transmitted upon exiting the first mode (e.g., in response to the detection of a second sequence of one or more inputs and based on a request to exit the first mode by determining that the second sequence of one or more inputs corresponds to an exit from the first mode). In some embodiments, no information is transmitted upon exiting the first mode (e.g., information is transmitted upon re-entering the restricted mode or at the end of a day or week).

[0344] In some implementations, the data that indicates that the electronic device has stopped operating in the first mode includes recording the time when the electronic device stops operating in the first mode in response to a second sequence of one or more inputs, and the duration for which the electronic device has not operated in the first mode (e.g., the amount of time between exiting and re-entering the first mode).

[0345] Recording data indicating that an electronic device has ceased operating in a first mode allows the device to notify another user (e.g., a parent) that it has stopped operating in that mode. In some implementations, data is recorded automatically, thereby reducing the amount of input required to notify another user. Providing the ability to notify another user while reducing the amount of input enhances device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device), thereby further reducing power consumption and extending device battery life by enabling users to use the device more quickly and efficiently.

[0346] In some embodiments, the electronic device displays a report log (e.g., 626-2) via a display device, which indicates one or more occurrences of the electronic device exiting a restricted mode (e.g., a first mode on the electronic device). In some embodiments, the restricted mode on another device is technically a different mode (e.g., a different version of the first mode), but the report log indicates exiting the restricted mode on the other device. In some embodiments, the report log includes an indication of the time when the electronic device stops operating in the first mode in response to a second sequence of one or more inputs, and an indication of the duration for which the electronic device does not operate in the first mode (e.g., in a settings menu). In some embodiments, the time and duration information is available when the electronic device is operating in the first mode. In some embodiments, the time and duration information is not available when the electronic device is operating in the first mode, but is available when the electronic device is not operating in the first mode. In some embodiments, the time and duration information is displayed in response to a sequence of one or more inputs (e.g., by navigating to a settings menu).

[0347] In some implementations, the report log also includes an indication of the time when the second electronic device (e.g., a smartphone, tablet, or another watch associated with the user) stopped operating in restricted mode, and an indication of the duration for which the second electronic device did not operate in restricted mode. In some implementations, the report log is displayed on another device (e.g., a device with an account associated with both the electronic device and the second device). In some implementations, the report log is displayed in a settings menu, through which the user can also adjust the restricted mode settings (on / off, restricted time, etc.).

[0348] In some embodiments, the electronic device detects a third sequence of one or more inputs (e.g., touch and / or activation of a rotatable input mechanism on a touch-sensitive display, such as pressing or rotating). In some embodiments, in response to the detection of a third sequence of one or more inputs: based on determining that the electronic device is not operating in a first mode, the electronic device performs an operation (e.g., opening an application, displaying a taskbar for recently opened or specified (e.g., favorite) applications, displaying an application jump (e.g., multiple icons for launching the corresponding application), displaying a notification center (e.g., a notification list), switching to a system space different from the current system space, editing the current user interface or entering a user interface editing or selection mode, launching an application corresponding to a complex function block). In some embodiments, in response to the detection of a third sequence of one or more inputs: based on determining that the electronic device is operating in a first mode, the electronic device abandons the operation. In some embodiments, operations that are executable when the electronic device is not operating in a first mode cannot be performed in the first mode (e.g., the electronic device must exit the first mode to be able to perform these operations).

[0349] Note that the above reference method 800 (for example, Figure 8 The details of the process described above also apply in a similar manner to the methods described above. For example, methods 700 and 1000 optionally include one or more features of the various methods described above with reference to method 800.

[0350] For example, when or after displaying the third user interface in operation 712 of method 700, some or all of the operations 806 to 812 related to presenting the alarm and exiting the first mode may be performed. As another example, operations 708 to 712 may be used to display a user interface of the corresponding user interface type in operation 804 of method 700.

[0351] Figures 9A to 9A1 Exemplary user interfaces for configuring external devices are shown according to some embodiments. The user interfaces in these figures are used to illustrate the following descriptions, including... Figure 10 The process of...

[0352] like Figure 9A Device 900 is depicted, which is a smartphone having a display 902. The display 902 includes a touch-sensitive surface on which device 900 can detect user gestures (e.g., tapping, swiping, dragging). In some embodiments, device 900 includes one or more features of device 100, 300, or 500.

[0353] exist Figure 9AIn the device 900, a user interface 904 is displayed to guide the user through a setup process using an external device (e.g., a smartwatch, device 600). The user interface 904 includes options for selecting the intended user of the smartwatch and thus selecting a user account to be associated with it. Specifically, the user interface 904 includes a power indicator 906a that, when selected, initiates a setup process to configure the external device as associated with a first user account (e.g., a user account already associated with device 900). Additionally, the user interface 904 includes a power indicator 906b that, when selected, initiates a setup process to configure the external device as associated with a second user account (e.g., a user account other than the one already associated with device 900).

[0354] like Figure 9A As shown, the user performs a tap gesture to identify someone other than the user of device 900 as the intended user of the external device. Therefore, device 900 detects input 908 at the enable display 906b. In response to the detection of input 908, device 900 initiates a setup process to configure the external device as associated with a second user account.

[0355] In some implementations, instead of detecting input 908 at the power indicator 906b, device 900 detects input (e.g., a tap gesture) at power indicator 906a. In some implementations, in response to detecting input at power indicator 906a, device 900 initiates a setup process for configuring an external device to be associated with a first user account (e.g., a user account of device 900).

[0356] like Figure 9B As shown on the left, after initiating a setup process to configure an external device to be associated with a second user account, device 900 displays a user interface 910a for pairing the external device to device 900. User interface 910a includes content 912a that prompts the user to keep the external device facing the camera of device 900.

[0357] like Figure 9BAs shown on the right, in some implementations, after initiating a setup process to configure an external device as associated with a first user account rather than a second user account, device 900 displays a user interface 910b for pairing the external device to device 900. User interface 910b includes content 912b, which differs from content 912a in that, in addition to prompting the user to keep the external device facing the camera of device 900, it also prompts the user to wear the external device. Content 912b prompts the user to wear the external device because the external device is being configured for the user of device 900. In contrast, content 912a does not prompt the user to wear the external device because the external device is not being configured for the user of device 900.

[0358] exist Figure 9C In this setup process, after the external device is paired (or wirelessly communicates) with device 900, device 900 continues the setup process and displays a user interface 914 for continuing to configure the external device as associated with a second user account. User interface 914 includes visual indications that the external device is being set up for a family member (e.g., someone other than the user of device 900) without explicitly identifying the family member, as device 900 does not yet possess that identification information. While displaying user interface 914, device 900 detects input 916a at a capability indicator 916b and, in response, continues the setup process.

[0359] exist Figure 9D Upon detecting input 916a, device 900 displays a user interface 918 for associating a user account with an external device. User interface 918 includes power indicators 920a-920b. In some embodiments, device 900 detects input (e.g., a tap gesture) at power indicator 920b. In some embodiments, in response to detecting input at power indicator 920b, device 900 displays one or more text fields for receiving information to create a new user account.

[0360] Return to Figure 9D Because the intended user of the external device has an existing user account, the user performs a tap gesture to associate the external device with the existing user account. Therefore, device 900 detects input 919 at the enable display 920a. In response to detecting input 919, device 900 initiates a process for selecting an existing user account.

[0361] like Figure 9EAs depicted on the left, after initiating a process for selecting an existing user account, device 900 displays user interface 922a. User interface 922a includes representations 923a-923c of the existing user account and option 923d, which, when selected, causes the display of one or more text fields for receiving information to identify the existing user account. In some embodiments, the existing user account (e.g., corresponding to representations 923a-923c) is associated with the user account of device 900. For example, the existing user account and the user account of device 900 are part of the same group (e.g., a home group).

[0362] like Figure 9E As depicted on the right, in some implementations, when an external device is configured to be associated with a first user account, device 900 displays user interface 922b instead of user interface 922a. Specifically, after initiating a process for selecting an existing user account, device 900 displays user interface 922b, which prompts the user for information corresponding to the first user account (e.g., credentials, password), instead of, for example, displaying representations 923a-923c.

[0363] return Figure 9E On the left, the user performs a tap gesture to select a user account belonging to Emma Appleseed as the second user account. Therefore, device 900 detects input 924 at representation 923b.

[0364] exist Figure 9F In response to the detection of input 924, device 900 continues the setup process and displays a user interface 926 with information corresponding to the second user account (e.g., a user account belonging to Emma Appleseed) such as name, email address, and date of birth. In some embodiments, this information is displayed in one or more text fields that can be edited via user input. It should be noted that the information corresponding to the second user account is now available to device 900, thereby enabling personalization of the user interface later during the setup process. Figure 9F The user performs a tap gesture to confirm the selection. Therefore, device 900 detects input 927a at display 927b. In response to detecting input 927a, device 900 confirms the selection of Emma's user account.

[0365] exist Figure 9GIn the process of confirming the selection of Emma's user account, device 900 displays a user interface 928 for creating a password (e.g., security information) on an external device. The user performs a tap gesture to initiate the password creation process. Therefore, device 900 detects input 929a at the display 929b. In some embodiments, in response to detecting input 929a, device 900 determines whether the age of the user corresponding to the second user account is below a threshold age (e.g., 6, 12, 18).

[0366] If the age of the user corresponding to the second user account is less than the threshold age, then device 900 displays user interface 930a with content 931a, such as Figure 9H As shown. Content 931a prompts the user representative of device 900, corresponding to the user account of the second user, to enter a password on an external device. In contrast, in some embodiments, if the age of the user corresponding to the second user account is at least a threshold age, device 900 displays a user interface 930b with content 931b, such as... Figure 9I As shown. Content 931b prompts the user of device 900 to have the user corresponding to the second user account (e.g., John) enter a password on the external device. In some embodiments, if the external device is configured to be associated with the first user account, device 900 does not display user interface 930a or 930b, but instead prompts the user to enter the password of the user of device 900 (e.g., not on behalf of some other user).

[0367] return Figures 9H to 9I In some implementations, after a password has been entered, device 900 determines whether the second user account has been associated with a device (e.g., a smartphone) capable of pairing with external devices (e.g., a smartwatch). In some implementations, if the external device is configured to be associated with the first user account, device 900 does not perform this determination.

[0368] exist Figure 9J If the second user account is already associated with a device capable of pairing with external devices, device 900 displays a user interface 932a with options to continue or abort the setup process. In some embodiments, user interface 932a does not include the option to continue the setup process (e.g., a power indicator 933b). In some embodiments, if the second user account is not yet associated with such a device, device 900 abandons displaying user interface 932a and continues the setup process (e.g., proceeds to the display...). Figure 9K User interface 936 in the text.

[0369] return Figure 9JThe user performs a tap gesture to continue the setup process. Therefore, device 900 detects input 934 at indicator 933b. In response to detecting input 934, device 900 continues the setup process.

[0370] exist Figure 9K Continuing the setup process, device 900 displays a user interface 936 for sharing wireless network information with external devices. User interface 936 includes a capability indicator 937a, which, when selected, initiates a process for transmitting current wireless network information to the external device, wherein the current wireless network information includes the network ID and password of the wireless network currently logged into by device 900. Additionally, user interface 936 includes a capability indicator 937b, which, when selected, initiates a process for transmitting wireless network information to the external device, wherein the wireless network information includes all network IDs and passwords stored on device 900. In some embodiments, device 900 does not include either capability indicator 937a or capability indicator 937b. In some embodiments, if the external device is configured to be associated with a first user account, device 900 does not display user interface 936.

[0371] return Figure 9K The user performs a tap gesture to share the current wireless network information. Therefore, device 900 detects input 938 at enable display 937a and, in response, initiates a process to transmit the current wireless network information to an external device.

[0372] like Figure 9L As shown on the left, after transmitting wireless network information, device 900 continues the setup process and displays user interface 940a for enabling location services. As mentioned above, device 900 has information about a second user account (e.g., the name of the user associated with the second user account). Using this information, device 900 displays user interface 940a with a name 941 that identifies the user account for which the external device is being configured. Providing this identification information during the setup process is helpful to the user of device 900, as it reminds the user that the external device is being set up for someone else (e.g., Emma Appleseed).

[0373] like Figure 9L As depicted on the right, in some implementations, if the external device is configured to be associated with a first user account (e.g., a user account associated with the user of device 900), device 900 displays user interface 940b instead of user interface 940a. Since the external device is being set up for the user of device 900, user interface 940b does not include information identifying the intended user of the external device (e.g., name 941).

[0374] To enable location services, the user performs a tap gesture at the indicator 942a. Therefore, device 900 detects input 942b at the indicator 942a, such as... Figure 9L As shown on the left. In response to the detection of input 942b, device 900 initiates a procedure to enable location services at the external device.

[0375] like Figure 9M As shown on the left, after initiating the process for enabling location services, device 900 displays a user interface 944a for enabling a voice assistant on an external device. The user performs a tap gesture to enable the voice assistant. Therefore, device 900 detects input 945b at the indication 945a. In response to detecting input 945b, device 900 initiates the process for enabling the voice assistant on the external device. Similar to... Figure 9L If the setup process is used to configure an external device to be associated with a first user account (e.g., the user account associated with the user of device 900), then device 900 displays a different user interface (e.g., 944b) without the name 941.

[0376] After initiating the process to enable the voice assistant, device 900 displays a user interface 946a for setting the activity characteristics of external devices, such as... Figure 9N The left side is depicted. The user performs a tap gesture to set an activity feature. Therefore, device 900 detects input 947b at the indication 947a. In response to detecting input 945b, device 900 initiates a process for setting the activity feature at the external device. Similar to... Figure 9L If the setup process is used to configure an external device to be associated with a first user account (e.g., the user account associated with the user of device 900), then device 900 displays a different user interface (e.g., 946b) without a name 941.

[0377] exist Figure 9O In the process of initiating the procedure for setting activity characteristics, device 900 displays a user interface 948 for configuring activity sharing between the external device and device 900. In some implementations, if the external device is configured to be associated with a first user account, device 900 does not display user interface 948. Figure 9O The device 900 detects input 949b (e.g., a tap gesture) at the display 949a.

[0378] exist Figure 9PIn response to the detection of input 949b, device 900 displays a user interface 950 for setting Emma's daily mobility target. The user selects a daily mobility target and performs a tap gesture to set the daily mobility target at the external device. Therefore, device 900 detects input 951b at the enable display 951a. In response to the detection of input 951b, device 900 initiates a process for configuring the external device using the selected daily mobility target.

[0379] exist Figure 9Q In the process of initiating a procedure to configure an external device using a selected daily movement goal, device 900 displays a user interface 952 for enabling fitness route tracking. Device 900 detects input 953b (e.g., a tap gesture) at a power indicator 953a. In response to detecting input 953b, device 900 initiates a procedure to enable fitness route tracking at the external device.

[0380] like Figure 9R As shown on the left, after initiating the process to enable fitness route tracking, device 900 displays a user interface 954a for enabling the sharing of health data between the external device and device 900. Device 900 detects input 955b (e.g., a tap gesture) at the display 955a. In response to detecting input 955b, device 900 initiates the process to enable the sharing of health data between the external device and device 900. Similar to... Figure 9L If the setup process is used to configure an external device to be associated with a first user account (e.g., the user account associated with the user of device 900), then device 900 displays a different user interface (e.g., 954b) without a name 941.

[0381] exist Figure 9S In the process of initiating the procedure to enable the sharing of health data between the external device and device 900, device 900 displays a user interface 956a for enabling emergency features at the external device. Device 900 detects input 957b (e.g., a tap gesture) at the enablement display 957a. In response to detecting input 957b, device 900 initiates the procedure for enabling emergency features at the external device. Similar to... Figure 9L If the setup process is used to configure an external device to be associated with a first user account (e.g., the user account associated with the user of device 900), then device 900 displays a different user interface (e.g., 956b) without a name 941.

[0382] exist Figure 9TAt this point, after initiating the process for activating emergency features at an external device, device 900 displays a user interface 958a for identifying emergency contacts. Device 900 detects input 959b (e.g., a tap gesture) at the capability display 959a. In response to detecting input 959b, device 900 inputs the identified emergency contact. Similar to... Figure 9L If the setup process is used to configure an external device to be associated with a first user account (e.g., the user account associated with the user of device 900), then device 900 displays a different user interface (e.g., 958b) without a name 941.

[0383] exist Figures 9U to 9V At the same time, device 900 detects one or more inputs (e.g., 961b, 963b) for configuring an external device using a digital medical ID card. When user interface 960 is displayed, device 900 detects input 961b (e.g., a tap gesture) at indication 961a. In response to detecting input 961b, device 900 displays user interface 962. When user interface 962 is displayed, device 900 detects input 963b (e.g., a tap gesture) at indication 963a. In response to detecting input 963b, device 900 initiates a process for configuring an external device using a digital medical ID card.

[0384] exist Figures 9W to 9X After initiating the process for configuring an external device using a digital medical ID card, device 900 detects one or more inputs (e.g., 965b, 958b) for adding photos to the external device. While displaying user interface 964, device 900 detects input 965b (e.g., a tap gesture) at enable representation 965a. In response to detecting input 965b, device 900 displays user interface 966 with representations 967a-967g featuring albums. The user selects representation 967f to add the "Emma" album and its collection of photos to the external device. Once representation 967f is selected, device 900 detects input 968b (e.g., a tap gesture) at the complete button 968a. In response to detecting input 968b, device 900 initiates the process for adding the selected album to the external device. In some implementations, the selected album remains synchronized indefinitely between device 900 and the external device (e.g., if a photo is added to the selected album at device 900, that photo is also added to the external device).

[0385] exist Figure 9YIn the process of initiating the procedure to add the selected album to the external device, device 900 continues the setup procedure and displays user interface 970 for configuring application restrictions on the external device. While displaying user interface 970, device 900 detects input 971b (e.g., a tap gesture) at enable display 971a. In response to detecting input 971b, device 900 initiates the procedure for configuring the external device using the specified application restrictions.

[0386] exist Figures 9Z to 9AA At this point, after initiating a process for configuring external devices using specified application restrictions, device 900 detects one or more inputs (e.g., 973b, 975b) to generate a contact card for Emma Appleseed. While displaying user interface 972, device 900 detects input 973b at the enable display 973a. In response to detecting input 973b, device 900 displays user interface 974 with information about Emma Appleseed. While displaying user interface 974, device 900 detects input 975b at the complete button 975a. In response to detecting input 975b, device 900 generates a contact card for Emma Appleseed.

[0387] exist Figures 9AB to 9AC After generating a contact card for Emma Appleseed, device 900 displays user interface 976 for requesting access to manage contacts on an external device. While displaying user interface 976, device 900 detects input 977b at a capability display 977a. In response to detecting input 977b, device 900 transmits a request to manage contacts on an external device. Further in response to detecting input 977b, device 900 displays a notification 979c in user interface 978, providing a visual indication that a request has been sent. While displaying user interface 978, device 900 detects input 979b at a confirmation button 979a. In response to detecting input 979b, device 900 completes the process for requesting access to manage contacts on an external device.

[0388] exist Figures 9AD to 9AEAfter completing the process of requesting access to manage contacts on an external device, device 900 detects one or more inputs (e.g., 981b, 984b) for adding contacts to the external device. When user interface 980 is displayed, device 900 detects input 981b at the enable display 981a. In response to detecting input 981b, device 900 displays user interface 982 with representations 983a-983h of the contacts. The user selects representations 983a-983c and 983e to add their corresponding contacts to the external device. Once a contact is selected, device 900 detects input 984b (e.g., a tap gesture) at the complete button 984a. In response to detecting input 984b, device 900 initiates the process of adding the selected contact to the external device.

[0389] exist Figures 9AF to 9AG At this point, after initiating the process to add the selected contact to the external device, device 900 detects one or more inputs (e.g., 987b, 989b) for configuring the restricted mode at the external device. Note that the above is relative to... Figures 6A to 6AC The restricted mode at the external device is further described. In some implementations, the restricted mode is a mode in which one or more functions of a first group available in the unrestricted mode are unavailable in the restricted mode, and one or more functions of a second group available in the unrestricted mode are available in the restricted mode.

[0390] exist Figure 9AF In the process of displaying user interface 986, device 900 detects input 987b at display indicator 987a. In response to the detection of input 987b, device 900 displays user interface 988, as shown below. Figure 9AG As shown. The user interface 988 includes one or more options for setting a restricted mode schedule for an external device. Once the schedule is set, the device 900 detects user input 989b at the complete button 989a. In response to detecting user input 989b, the device 900 initiates a process for configuring the external device using the set restricted mode schedule.

[0391] exist Figure 9AH After initiating the process for configuring external devices using the set restricted mode schedule, device 900 displays user interface 990 to indicate that the setup process has ended. While displaying user interface 990, device 900 detects input 991b at confirmation button 991a. In response to detecting input 991b, device 900 exits the setup process.

[0392] In some implementations, if an external device is configured to be associated with a first user account (e.g., the user account associated with device 900), device 900 enables sharing one or more features (e.g., settings, data) with the external device. Therefore, in some implementations, device 900 displays user interface 992 in graph AI at some point during the setup process. In contrast, if the external device is configured to be associated with a second user account (e.g., a user account other than the one associated with device 900), device 900 forgoes displaying user interface 992 during the setup process.

[0393] Figure 10 This is a flowchart illustrating a method for configuring a second device using a first electronic device according to some embodiments. Method 1000 is performed at a first device (e.g., 100, 300, 500, 650, 900) having a display device. Some operations in method 1000 are optionally combined, some operations are optionally changed in order, and some operations are optionally omitted.

[0394] As described below, method 1000 provides an intuitive way to configure a second device. This method reduces the cognitive burden on users when configuring the second device, thereby creating a more efficient human-machine interface. For battery-powered computing devices, it enables users to configure the second device more quickly and efficiently to save power and increase the interval between battery charges.

[0395] In some embodiments, a first device (e.g., 900) displays (1002) a setup user interface (e.g., 904) via a display device (e.g., 902) for setting up a setup process for a second device (e.g., 600 for configuring an external device). In some embodiments, the setup user interface includes a first indication (e.g., 906a) (e.g., a visual instruction for a user configuring the second device thereto (e.g., the text "Set up for yourself")) and a second indication (e.g., 906b) (e.g., a visual instruction for a user configuring the second device thereto (e.g., the text "Set up for a family member")). In some embodiments, activation of the first indication results in initiating a process for configuring the second device to be associated with a first user / user account (e.g., the user / user account of the first device). In some embodiments, activation of the second indication results in initiating a process for configuring the second device to be associated with a second user / user account different from the first user / user account.

[0396] In some implementations, when the settings user interface is displayed via a display device, the first device detects (1004) a first user input (e.g., 908, gesture (e.g., tap, swipe), audio input) of the corresponding account to be associated with the second device, and at the same time the first device is associated with the first account (e.g., the first device is associated with the first account (i.e., the user account) of the user of the first device (configured for the first account)).

[0397] After the corresponding account has been selected to be associated with the second device and during the setup process, the first device displays (1006) a user interface (e.g., 940a-940b, 944a-944b, 946a-946b, 954a-954b, 956a-956b, 958a-958b) via a display device to configure the corresponding functions of the second device. This includes, based on determining that the first account (e.g., the account associated with the first device) has been selected to be associated with the second device (and the second account has not been selected to be associated with the second device), displaying (1008) one or more optional options (e.g., 942a, 945a, 947a, 955a, 957a) associated with configuring the corresponding functions of the second device. (e.g., 942a, 945a, 947a, 955a, 957a, 959a) without explicitly identifying the user account associated with the second device (e.g., the second account) (e.g., not displaying 941), and based on the determination that a second account different from the first account (e.g., a user account that does not correspond to the user of the first device) is selected to be associated with the second device (and the first account is not selected to be associated with the second device), the one or more optional options (e.g., 942a, 945a, 947a, 955a, 957a, 959a) associated with the corresponding functions of the second device are displayed (1010) via the display device, and an identifier (e.g., 941) is simultaneously displayed, which explicitly identifies the second account (e.g., displaying the name of the user corresponding to the second account, displaying the email address corresponding to the second account).

[0398] In some implementations, the first account is an existing user account. In some implementations, the first account is the user account that the first device (e.g., 900) logs into during the setup process. In some implementations, the second user account is the user account to be created. In some implementations, the second account is a user account that the first device did not log into during the setup process.

[0399] Clearly identifying the user account on the first device for a second device that is being configured for another user, rather than the user on the first device, provides the user with visual feedback regarding the configuration settings to be used to configure the second device. Providing the user with improved visual feedback enhances device operability and makes the user device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends device battery life by enabling the user to use the device more quickly and effectively.

[0400] In some embodiments, based on the determination that a first account (e.g., an account associated with a first device (e.g., 900)) is selected to be associated with a second device (e.g., 600), the first device initiates a process (e.g., displaying a user interface) for configuring the second device for the first account. In some embodiments, the process for configuring the second device for the first account includes enabling a first set of features on the second device that require communication between the first and second devices (e.g., causing the first device to transmit information to the second device to enable the first set of features on the second device, thereby sharing the first set of features between the second and first devices). In some embodiments, based on the determination that a second account (different from the first account) is selected to be associated with the second device, the first device initiates a process for configuring the second device for the second account (e.g., displaying a user interface). In some embodiments, the process for configuring the second device for the second account does not include enabling the first set of features on the second device that require communication between the first and second devices.

[0401] In some implementations, the first set of features includes one or more of the following: sharing of physical activity data (e.g., corresponding to 948) (e.g., data indicating the physical activity of a corresponding user collected based on the movement (or lack thereof) of a second device and a first device), automatic unlocking of devices (e.g., a second device and a first device) (e.g., based on, for example, the proximity of the second device to the first device), sharing of location data (e.g., location data of the second device and location data of the first device), coordination of notifications / alerts (e.g., automatically deactivating a notification on one device (e.g., the first device) when input for deactivating a corresponding notification has been received on another device (e.g., the second device), automatically silencing an audio alarm on one device (e.g., the first device) when input for silencing a corresponding alarm provided on another device (e.g., the second device) has been received on another device (e.g., the second device), and switching of application tasks (e.g., switching applications on one device (e.g., the first device) based on the current activity (e.g., the currently displayed application) of another device (e.g., the second device). The functions include displaying instructions on the display, camera control tasks (e.g., using another device (e.g., a second device) to control the camera of a device (e.g., a first device) (such as accessing the camera's viewfinder, initiating image capture by the camera)), application installation (e.g., automatically installing a first application on a device (e.g., a second device) in response to a user request to install a corresponding (e.g., the same or a different version) application on another device (e.g., a first device)), communication disabling features (e.g., automatically putting a device (e.g., a first device) into flight mode (e.g., by disabling cellular communication) in response to a user request to put another device (e.g., a second device) into flight mode (received at the other device)), and payment account configuration (e.g., providing an indication (or initiating a process for configuring a payment account on a device (e.g., a second device) for use on another device (e.g., a first device) in response to user input (e.g., received at the other device) for configuring a payment account for use on another device (e.g., a first device)).

[0402] Sharing this set of features between the first and second devices allows users to access their information across multiple devices. Similarly, not sharing this set of features between the first and second devices allows different users to keep their own information on independent devices. Managing how feature sharing is configured enhances device operability and makes their user-device interfaces more efficient (e.g., by helping to provide the right information to the right user based on the account configured on the device), which in turn reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0403] In some implementations, displaying an identifier that explicitly identifies the second account includes displaying the name corresponding to the second account (e.g., 941, first name, last name, first name, and last name). In some implementations, the name is displayed simultaneously with the configured function or feature (such as "voice control for Emma") to identify the configured function / feature and the user it is configured for. In some implementations, when the second device is being configured for the first account, the configuration of the same function / feature does not identify the first account. For example, the feature / feature configuration user interface may display "voice control settings" without simultaneously displaying the name corresponding to the first account. In some implementations, the one or more optional options are one or more optional options for configuring voice assistant settings on the second device (e.g., 945a). In some implementations, based on the determination that the second account is selected to be associated with the second device, the first device displays a user interface for configuring voice assistant settings on the second device via a display device (e.g., during the setup process). In some implementations, the one or more optional options are displayed as part of the user interface for configuring voice assistant settings, including a first voice assistant option that enables the voice assistant for use on the second device, and a second voice assistant option that disables the voice assistant for use on the second device.

[0404] Clearly identifying another user's account on the first device, rather than the user of the first device who is configuring the second device, provides the user of the first device with visual feedback regarding the configuration settings that will be used to configure the second device. Providing users with improved visual feedback enhances device operability and makes the user device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends device battery life by enabling users to use the device more quickly and effectively.

[0405] In some implementations, during the setup process, based on the determination that a first account (e.g., an account associated with the first device) is selected to be associated with the second device, the first device displays a first prompt via a display device instructing the wearer of the second device (e.g., worn by the user of the first device). Figure 9B 912b) and a second cue instructing the placement of the second device (e.g., the display of the second device) within the field of view of the camera sensor of the first device (e.g., ... Figure 9B(e.g., displayed after displaying a prompt instruction to wear the second device (and optionally not currently displayed), or displayed after receiving information instructing the wear of the second device). In some embodiments, the first device optionally monitors information from the second device instructing the second device to be currently being worn before continuing to display additional prompts. In some embodiments, during the setup process, based on determining that the second account is selected to be associated with the second device, the first device displays a third prompt (e.g., the same as, but different from, the second prompt) via a display device instructing the placement of the second device (e.g., the second device's display) within the field of view of the first device's camera sensor, without displaying a prompt instructing the wear of the second device (e.g., the first prompt).

[0406] By not prompting the user to wear a second device in certain situations, the device helps prevent the user from wearing it without prior setup. This improved feedback helps prevent the user from performing unnecessary (or unhelpful) tasks that may not be helpful in progressing to the next stage of device setup. In contrast, prompting the user to wear a second device (in certain situations) provides the user with a task to perform in order to progress to the next stage of device setup. Providing the user with improved visual feedback enhances device operability and makes the user interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends device battery life by enabling users to use the device more quickly and effectively.

[0407] In some implementations, during the setup process, upon determining that a second account is selected to be associated with the second device, the first device (e.g., 900) displays (e.g., during the setup process) via a display device one or more details about data (e.g., application data, media (photos, videos, audio), documents, address book contacts) to be transferred (e.g., from the first device, using the credentials (e.g., login / password) of the first account from the server) to the second device (and optionally, regarding the configuration to be performed on the second device). In some implementations, during the setup process, upon determining that a first account (e.g., an account associated with the first device) is selected to be associated with the second device, the first device waives the display of such details regarding data (e.g., application data, media (photos, videos, audio), documents, address book contacts) to be transferred (e.g., from the first device, using the credentials (e.g., login / password) of the first account from the server) to the second device. In some implementations, upon determining that a second account is selected to be associated with the second device, the first device displays information to notify the user that the second device is being configured for someone other than the user corresponding to the first account. In some implementations, upon determining that a second account has been selected to be associated with the second device, the first device may optionally notify the user (e.g., via display) that the setup process will include the opportunity to transfer content (e.g., application data, media (photos, videos, audio), documents, address book contacts) to the second device. In some implementations, upon determining that a second account has been selected to be associated with the second device, the first device may optionally notify the user (e.g., via display) that the setup process will include the opportunity to configure the second device for operation in a restricted mode, such as as described above relative to... Figures 6A to 6AC , Figure 7 and Figure 8 As stated above.

[0408] Displaying one or more details about the data to be transferred provides the user with visual feedback regarding the data to be shared with the second device. For example, this gives the user the opportunity to refuse information transmission, thereby preventing the sharing of unintended data with the second device. Providing improved visual feedback to the user enhances device security and operability, making the user interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and effectively.

[0409] In some embodiments, during the setup process, based on the determination that a second account is selected to be associated with the second device, the first device displays a user interface (e.g., 936) via a display device (e.g., during the setup process) for transferring network settings (e.g., from the first device) to the second device. In some embodiments, the one or more optional options are displayed as part of the user interface for transferring network settings. In some embodiments, the one or more optional options include a first network configuration option (e.g., 937a) for transferring network configuration data (e.g., network name, network credentials (e.g., password)) of a first network (e.g., a wireless network, a wireless local area network (WLAN)) associated with the current location of the first device (e.g., the first network currently accessed by the first device). In some embodiments, the first network configuration data is transferred to the second device without transferring network configuration data of a second network (e.g., a second wireless network, a second WLAN network) that is not currently accessed by the first device (e.g., sharing network configuration data for only one network, even though the device has shareable network configurations for multiple networks).

[0410] In some embodiments, the user interface (e.g., 936) for transferring network settings (e.g., from a first device) to a second device further includes a second network configuration option (e.g., 937b) for transferring network configuration data (e.g., network name, network credentials (e.g., password)) for multiple networks. In some embodiments, the multiple networks include a first network and a second network. In some embodiments, during the setup process, the first device detects second user input while displaying the user interface for transferring network settings. In some embodiments, during the setup process, based on determining that the second user input corresponds to the activation of a first network configuration option, the first device transmits the network configuration data of the first network (e.g., network name, network credentials (e.g., password)) to the second device but not the network configuration data of the second network. In some embodiments, during the setup process, based on determining that the second user input corresponds to the activation of a second network configuration option, the first device transmits the network configuration data (e.g., network name, network credentials (e.g., password)) of the multiple networks to the second device.

[0411] In some implementations, the second user input indicates authorization to transmit the corresponding network configuration data once (e.g., a single transmission, without repeatedly transmitting network configuration data for the system network, and without providing network configuration data for a future network configured on the first device).

[0412] In some implementations, the one or more optional options include a third network configuration option that does not transmit network configuration data (e.g., network name, network credentials (e.g., password)) for a first network (e.g., a wireless network, a WLAN network) and does not transmit network configuration data (e.g., network name, network credentials (e.g., password)) for a second network (e.g., does not transmit network configuration data for any network (any Wi-Fi network)). In some implementations, based on determining that the second user input corresponds to the activation of the third network configuration option: the first device waives the transmission of network configuration data (e.g., network name, network credentials (e.g., password)) of the first network to the second device.

[0413] In some implementations, the first device prompts the user to choose between settings that share the current network or settings that share multiple networks. In some implementations, based on the determination that a second account is selected to be associated with the second device, the first device displays a user interface via a display device (e.g., during the setup process) for transferring network settings (e.g., from the first device) to the second device. In some implementations, the user display interface for transferring network settings includes a first network configuration option for transferring network configuration data (e.g., network name, network credentials (e.g., password)) of a first network currently accessed by the first device (e.g., a wireless network, WLAN network), and a second network configuration option for transferring network configuration data (e.g., network name, network credentials (e.g., password)) of the first network currently accessed by the first device (e.g., a wireless network, WLAN network) and a second network not currently accessed by the first device (e.g., a second wireless network different from the first network). In some implementations, the first device detects second user input while displaying the user interface for transferring network settings. In some implementations, based on the determination that the second user input corresponds to the activation of the first network configuration option, the first device transmits network configuration data of the first network (e.g., network name, network credentials (e.g., password)) to the second device but does not transmit network configuration data of the second network. In some implementations, based on the determination that the second user input corresponds to the activation of the second network configuration option, the first device transmits network configuration data of both the first and second networks (e.g., network name, network credentials (e.g., password)) to the second device. In some implementations, the second user input indicates authorization to transmit the corresponding network configuration data once (e.g., a single transmission, without repeating network configuration data for the system network, and without providing network configuration data for future networks configured on the first device).

[0414] In some embodiments, during the setup process, based on the determination that a second account is selected to be associated with the second device, the first device displays a user interface (e.g., 964, 966) via a display device (e.g., during the setup process) for transferring media (e.g., from the first device) to the second device. In some embodiments, displaying the user interface for transferring media to the second device includes displaying a first representation (e.g., 967a-967g) of the first media (e.g., photos, photo albums, videos, audio) and a second representation (e.g., 967a-967g) of the second media (e.g., photos, photo albums, videos, audio), wherein the first media is stored on the first device. In some embodiments, the second media is associated with an account associated with (and optionally stored on) the first device. In some embodiments, the first device detects a first set of one or more user inputs. In some embodiments, based on the determination that the first set of one or more user inputs corresponds to a request to transfer the first media without transferring the second media, the first device transfers the first media to ...

Claims

1. An electronic device, comprising: Display devices; One or more processors; as well as The memory stores one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: A first user interface of a corresponding user interface type of the electronic device is displayed via the display device, wherein the first user interface of the corresponding user interface type includes one or more elements in a first arrangement; Detect a sequence of one or more inputs corresponding to a request to change the current user interface of the corresponding user interface type of the electronic device; In response to detecting a sequence of one or more inputs corresponding to a request to change the current user interface of the corresponding user interface type of the electronic device, a second user interface of the corresponding user interface type is displayed via the display device as the current user interface of the corresponding user interface type of the electronic device, wherein the second user interface of the corresponding user interface type includes one or more elements that are different from the one or more elements of the first user interface of the corresponding user interface type and / or in an arrangement that is different from the first arrangement of the one or more elements of the first user interface of the corresponding user interface type; After changing the current user interface of the corresponding user interface type of the electronic device to the second user interface of the corresponding user interface type, the occurrence of a condition corresponding to the trigger for displaying the current user interface of the corresponding user interface type of the electronic device is detected; In response to the detection of a condition corresponding to the triggering of the current user interface for displaying the corresponding user interface type of the electronic device: Based on a predefined time range in which the current time corresponds to the electronic device operating in a restricted mode where one or more functions are limited, a third user interface of a corresponding user interface type is displayed via the display device. The third user interface is different from the first user interface and the second user interface of the corresponding user interface type. The third user interface of the corresponding user interface type includes a predefined set of elements that are different from the one or more elements of the first user interface and the one or more elements of the second user interface of the corresponding user interface type. The predefined set of elements cannot be changed in response to input detected at the electronic device. as well as Based on the predefined time range in which the current time does not correspond to the electronic device operating in the restricted mode in which one or more of the functions are restricted, the second user interface of the corresponding user interface type is displayed via the display device; In response to detecting a request to exit the restricted mode and when the current time corresponds to the predefined time range, exiting the restricted mode includes stopping the display of the third user interface of the corresponding user interface type; When the current time corresponds to the predefined time range and the third user interface of the corresponding user interface type is not displayed, a redisplay criterion for the third user interface is detected, wherein the redisplay criterion for the third user interface includes a criterion that is met when no user input is detected within the predefined time range; and In response to detecting that the redisplay criteria of the third user interface are met, the third user interface of the corresponding user interface type is displayed via the display device.

2. The electronic device of claim 1, wherein the corresponding user interface type is a dial.

3. The electronic device of claim 2, wherein the one or more programs further include instructions for performing the following operations: Detect a second sequence of one or more inputs; and In response to the detection of a second sequence of the one or more inputs: An operation is performed based on a second sequence of one or more inputs detected when the first user interface of the corresponding user interface type is displayed; and The operation is abandoned based on a second sequence of one or more inputs detected when the third user interface of the corresponding user interface type is displayed.

4. The electronic device according to any one of claims 1 to 3, wherein the predefined set of elements comprises the entire third user interface of the corresponding user interface type, and additional elements cannot be added to the third user interface of the corresponding user interface type.

5. The electronic device according to any one of claims 1 to 3, wherein the third user interface of the corresponding user interface type includes a distinguishing element, wherein the distinguishing element is a visually distinguishable portion of the third user interface of the corresponding user interface type, and the distinguishing element is not included in the first user interface of the corresponding user interface type or the second user interface of the corresponding user interface type.

6. The electronic device according to any one of claims 1 to 3, wherein the one or more programs further include instructions for performing the following operations: When displaying the second user interface of the corresponding user interface type, detect a third sequence of one or more inputs; and In response to detecting a third sequence of one or more inputs while displaying a second user interface of the corresponding user interface type, an operation is performed; When displaying the third user interface of the corresponding user interface type, detect the third sequence of the one or more inputs; and In response to detecting a third sequence of one or more inputs while displaying the third user interface of the corresponding user interface type, the operation is abandoned.

7. The electronic device according to any one of claims 1 to 3, wherein the one or more programs further include instructions for performing the following operations: Before detecting the occurrence of the condition corresponding to the triggering of the current user interface of the corresponding user interface type for displaying the electronic device, a first user interface for a first application is displayed, wherein displaying the third user interface of the corresponding user interface type includes stopping the display of the first user interface for the first application.

8. The electronic device according to any one of claims 1 to 3, wherein: The predefined set of elements includes a time indication; and The time indication cannot be changed in response to input detected at the electronic device.

9. The electronic device of claim 7, wherein the third user interface displaying the corresponding user interface type comprises: Based on the determination that the first application is running in the background, a third user interface of the corresponding user interface type with graphical elements corresponding to the first application is displayed; as well as Based on the determination that the first application is not running, a third user interface of the corresponding user interface type is displayed that does not have the graphical elements corresponding to the first application.

10. The electronic device according to any one of claims 1 to 3, wherein the one or more programs further include instructions for performing the following operations: When displaying the third user interface of the corresponding user interface type, a fourth sequence of one or more inputs is detected; and In response to detecting at least one input in a fourth sequence of the one or more inputs, an exit user interface with information for transitioning from the restricted mode to an unrestricted mode is displayed via the display device, wherein the unrestricted mode includes one or more functions that are restricted when in the restricted mode.

11. The electronic device of claim 10, wherein the exit user interface includes a first portion, the first portion including a power indication for exiting the restricted mode, and the one or more programs further include instructions for performing the following operations: Receive input corresponding to the selection of the power indication for exiting the restricted mode; and In response to detecting an input corresponding to a selection of the indication for exiting the restricted mode, a second user interface of the corresponding user interface type is displayed via the display device.

12. The electronic device of claim 11, wherein the one or more programs further include instructions for performing the following operations: When the exit user interface is displayed without displaying the first portion of the exit user interface including the power indication for exiting the restricted mode, input corresponding to a request to scroll the exit user interface is detected; and In response to detecting input corresponding to a request to scroll the exit user interface, the exit user interface is scrolled to display the first portion of the exit user interface including the power indication for exiting the restricted mode.

13. The electronic device of claim 10, wherein the fourth sequence of detecting the one or more inputs includes detecting rotation of the rotatable input mechanism, and the one or more programs further include instructions for performing the following operations: In response to detecting the rotation of the rotatable input mechanism, a second user interface of the corresponding user interface type is displayed.

14. The electronic device according to any one of claims 1 to 3, wherein the one or more programs further include instructions for performing the following operations: After displaying the third user interface of the corresponding user interface type: Detect the occurrence of inactive conditions; In response to the detection of the inactivity condition, the display device is deactivated; After deactivating the display device, the occurrence of a condition corresponding to the triggering of the current user interface of the corresponding user interface type used to display the electronic device is detected; as well as In response to the detection of a condition corresponding to the triggering of the current user interface for displaying the corresponding user interface type of the electronic device: Based on determining that the current time corresponds to the predefined time range, display the third user interface of the corresponding user interface type; and If the current time does not correspond to the predefined time range, the second user interface of the corresponding user interface type is displayed.

15. The electronic device according to any one of claims 1 to 3, wherein the third user interface of the corresponding user interface type includes an analog indication of time and a digital indication of time.

16. The electronic device of claim 15, wherein, relative to the element of the analog indication of time corresponding to an hour other than the current hour, the element of the analog indication of time corresponding to the current hour of the current time is visually emphasized.

17. The electronic device according to any one of claims 1 to 3, wherein the one or more programs further include instructions for performing the following operations: When the current time corresponds to the predefined time range and when the electronic device is operating in a restricted mode: A fifth sequence of one or more inputs is detected, the fifth sequence of one or more inputs including at least one input detected when the third user interface of the corresponding user interface type is displayed; and In response to detecting a fifth sequence of the one or more inputs, exit the restricted mode, wherein exiting the restricted mode includes displaying the second user interface of the corresponding user interface type.

18. The electronic device according to any one of claims 1 to 3, wherein the second user interface of the corresponding user interface type includes a first capability representation corresponding to an application, and the one or more programs further include instructions for performing the following operations: When displaying the second user interface of the corresponding user interface type, detect the input corresponding to the selection of the first display representation; and The application is launched in response to the detection of an input corresponding to a selection of the first indication.

19. The electronic device according to any one of claims 1 to 3, wherein the predefined time range is defined according to a schedule of different time ranges for different days of a specified week.

20. The electronic device according to any one of claims 1 to 3, wherein the one or more programs further include instructions for performing the following operations. When the current time does not correspond to the predefined time range: A third user interface, including a power indication for activating the restricted mode, is displayed via the display device; Detect the input corresponding to the selection of the indicated energy representation for activating the restricted mode; as well as In response to detecting an input corresponding to a selection of the power indication for activating the restricted mode, the electronic device is operated in the restricted mode.

21. The electronic device according to any one of claims 1 to 3, wherein the third user interface of the corresponding user interface type includes an indication of the user's name and a digital indication of the time.

22. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display device, the one or more programs including instructions for performing the following operations: A first user interface of a corresponding user interface type of the electronic device is displayed via the display device, wherein the first user interface of the corresponding user interface type includes one or more elements in a first arrangement; Detect a sequence of one or more inputs corresponding to a request to change the current user interface of the corresponding user interface type of the electronic device; In response to detecting a sequence of one or more inputs corresponding to a request to change the current user interface of the corresponding user interface type of the electronic device, a second user interface of the corresponding user interface type is displayed via the display device as the current user interface of the corresponding user interface type of the electronic device, wherein the second user interface of the corresponding user interface type includes one or more elements that are different from the one or more elements of the first user interface of the corresponding user interface type and / or in an arrangement that is different from the first arrangement of the one or more elements of the first user interface of the corresponding user interface type; After changing the current user interface of the corresponding user interface type of the electronic device to the second user interface of the corresponding user interface type, the occurrence of a condition corresponding to the trigger for displaying the current user interface of the corresponding user interface type of the electronic device is detected; In response to the detection of a condition corresponding to the triggering of the current user interface for displaying the corresponding user interface type of the electronic device: Based on a predefined time range in which the current time corresponds to the electronic device operating in a restricted mode where one or more functions are limited, a third user interface of a corresponding user interface type is displayed via the display device. The third user interface is different from the first user interface and the second user interface of the corresponding user interface type. The third user interface of the corresponding user interface type includes a predefined set of elements that are different from the one or more elements of the first user interface and the one or more elements of the second user interface of the corresponding user interface type. The predefined set of elements cannot be changed in response to input detected at the electronic device. as well as Based on the predefined time range in which the current time does not correspond to the electronic device operating in the restricted mode in which one or more of the functions are restricted, the second user interface of the corresponding user interface type is displayed via the display device; In response to detecting a request to exit the restricted mode and when the current time corresponds to the predefined time range, exiting the restricted mode includes stopping the display of the third user interface of the corresponding user interface type; When the current time corresponds to the predefined time range and the third user interface of the corresponding user interface type is not displayed, a redisplay criterion for the third user interface is detected, wherein the redisplay criterion for the third user interface includes a criterion that is met when no user input is detected within the predefined time range; and In response to detecting that the redisplay criteria of the third user interface are met, the third user interface of the corresponding user interface type is displayed via the display device.

23. The computer-readable storage medium of claim 22, wherein the corresponding user interface type is a dial.

24. The computer-readable storage medium of claim 23, wherein the one or more programs further include instructions for performing the following operations: Detect a second sequence of one or more inputs; and In response to the detection of a second sequence of the one or more inputs: An operation is performed based on a second sequence of one or more inputs detected when the first user interface of the corresponding user interface type is displayed; and The operation is abandoned based on a second sequence of one or more inputs detected when the third user interface of the corresponding user interface type is displayed.

25. The computer-readable storage medium according to any one of claims 22 to 24, wherein the predefined set of elements comprises the entire third user interface of the corresponding user interface type, and additional elements cannot be added to the third user interface of the corresponding user interface type.

26. The computer-readable storage medium according to any one of claims 22 to 24, wherein the third user interface of the corresponding user interface type includes a distinguishing element, wherein the distinguishing element is a visually distinguishable portion of the third user interface of the corresponding user interface type, and the distinguishing element is not included in the first user interface of the corresponding user interface type or the second user interface of the corresponding user interface type.

27. The computer-readable storage medium according to any one of claims 22 to 24, wherein the one or more programs further include instructions for performing the following operations: When displaying the second user interface of the corresponding user interface type, detect a third sequence of one or more inputs; and In response to detecting a third sequence of one or more inputs while displaying a second user interface of the corresponding user interface type, an operation is performed; When displaying the third user interface of the corresponding user interface type, detect the third sequence of the one or more inputs; and In response to detecting a third sequence of one or more inputs while displaying the third user interface of the corresponding user interface type, the operation is abandoned.

28. The computer-readable storage medium according to any one of claims 22 to 24, wherein the one or more programs further include instructions for performing the following operations: Before detecting the occurrence of the condition corresponding to the triggering of the current user interface of the corresponding user interface type for displaying the electronic device, a first user interface for a first application is displayed, wherein displaying the third user interface of the corresponding user interface type includes stopping the display of the first user interface for the first application.

29. The computer-readable storage medium according to any one of claims 22 to 24, wherein: The predefined set of elements includes a time indication; and The time indication cannot be changed in response to input detected at the electronic device.

30. The computer-readable storage medium of claim 28, wherein the third user interface displaying the corresponding user interface type comprises: Based on the determination that the first application is running in the background, a third user interface of the corresponding user interface type with graphical elements corresponding to the first application is displayed; as well as Based on the determination that the first application is not running, a third user interface of the corresponding user interface type is displayed that does not have the graphical elements corresponding to the first application.

31. The computer-readable storage medium according to any one of claims 22 to 24, wherein the one or more programs further include instructions for performing the following operations: When displaying the third user interface of the corresponding user interface type, a fourth sequence of one or more inputs is detected; and In response to detecting at least one input in a fourth sequence of the one or more inputs, an exit user interface with information for transitioning from the restricted mode to an unrestricted mode is displayed via the display device, wherein the unrestricted mode includes one or more functions that are restricted when in the restricted mode.

32. The computer-readable storage medium of claim 31, wherein the exit user interface includes a first portion, the first portion including a capability indication for exiting the restricted mode, and the one or more programs further include instructions for performing the following operations: Receive input corresponding to the selection of the power indication for exiting the restricted mode; and In response to detecting an input corresponding to a selection of the indication for exiting the restricted mode, a second user interface of the corresponding user interface type is displayed via the display device.

33. The computer-readable storage medium of claim 32, wherein the one or more programs further include instructions for performing the following operations: When the exit user interface is displayed without displaying the first portion of the exit user interface including the power indication for exiting the restricted mode, input corresponding to a request to scroll the exit user interface is detected; and In response to detecting input corresponding to a request to scroll the exit user interface, the exit user interface is scrolled to display the first portion of the exit user interface including the power indication for exiting the restricted mode.

34. The computer-readable storage medium of claim 31, wherein the fourth sequence of detecting the one or more inputs includes detecting rotation of the rotatable input mechanism, and the one or more programs further include instructions for performing the following operations: In response to detecting the rotation of the rotatable input mechanism, a second user interface of the corresponding user interface type is displayed.

35. The computer-readable storage medium according to any one of claims 22 to 24, wherein the one or more programs further include instructions for performing the following operations: After displaying the third user interface of the corresponding user interface type: Detect the occurrence of inactive conditions; In response to the detection of the inactivity condition, the display device is deactivated; After deactivating the display device, the occurrence of a condition corresponding to the triggering of the current user interface of the corresponding user interface type used to display the electronic device is detected; as well as In response to the detection of a condition corresponding to the triggering of the current user interface for displaying the corresponding user interface type of the electronic device: Based on determining that the current time corresponds to the predefined time range, display the third user interface of the corresponding user interface type; and If the current time does not correspond to the predefined time range, the second user interface of the corresponding user interface type is displayed.

36. The computer-readable storage medium according to any one of claims 22 to 24, wherein the third user interface of the corresponding user interface type includes an analog indication of time and a digital indication of time.

37. The computer-readable storage medium of claim 36, wherein, relative to the element corresponding to an hour other than the current hour in the analog indication of time, the element corresponding to the current hour of the current time in the analog indication of time is visually emphasized.

38. The computer-readable storage medium according to any one of claims 22 to 24, wherein the one or more programs further include instructions for performing the following operations: When the current time corresponds to the predefined time range and when the electronic device is operating in a restricted mode: A fifth sequence of one or more inputs is detected, the fifth sequence of one or more inputs including at least one input detected when the third user interface of the corresponding user interface type is displayed; and In response to detecting a fifth sequence of the one or more inputs, exit the restricted mode, wherein exiting the restricted mode includes displaying the second user interface of the corresponding user interface type.

39. The computer-readable storage medium according to any one of claims 22 to 24, wherein the second user interface of a corresponding user interface type includes a first functional representation corresponding to an application, and the one or more programs further include instructions for performing the following operations: When displaying the second user interface of the corresponding user interface type, detect the input corresponding to the selection of the first display representation; and The application is launched in response to the detection of an input corresponding to a selection of the first indication.

40. The computer-readable storage medium according to any one of claims 22 to 24, wherein the predefined time range is defined according to a schedule of different time ranges for different days of a specified week.

41. The computer-readable storage medium according to any one of claims 22 to 24, wherein the one or more programs further include instructions for performing the following operations. When the current time does not correspond to the predefined time range: A third user interface, including a power indication for activating the restricted mode, is displayed via the display device; Detect the input corresponding to the selection of the indicated energy representation for activating the restricted mode; as well as In response to detecting an input corresponding to a selection of the power indication for activating the restricted mode, the electronic device is operated in the restricted mode.

42. The computer-readable storage medium according to any one of claims 22 to 24, wherein the third user interface of the corresponding user interface type includes an indication of the user's name and a digital indication of the time.

43. A method comprising: At electronic devices with display devices: A first user interface of a corresponding user interface type of the electronic device is displayed via the display device, wherein the first user interface of the corresponding user interface type includes one or more elements in a first arrangement; Detect a sequence of one or more inputs corresponding to a request to change the current user interface of the corresponding user interface type of the electronic device; In response to detecting a sequence of one or more inputs corresponding to a request to change the current user interface of the corresponding user interface type of the electronic device, a second user interface of the corresponding user interface type is displayed via the display device as the current user interface of the corresponding user interface type of the electronic device, wherein the second user interface of the corresponding user interface type includes one or more elements that are different from the one or more elements of the first user interface of the corresponding user interface type and / or in an arrangement that is different from the first arrangement of the one or more elements of the first user interface of the corresponding user interface type; After changing the current user interface of the corresponding user interface type of the electronic device to the second user interface of the corresponding user interface type, the occurrence of a condition corresponding to the trigger for displaying the current user interface of the corresponding user interface type of the electronic device is detected; In response to the detection of a condition corresponding to the triggering of the current user interface for displaying the corresponding user interface type of the electronic device: Based on a predefined time range in which the current time corresponds to the electronic device operating in a restricted mode where one or more functions are limited, a third user interface of a corresponding user interface type is displayed via the display device. The third user interface is different from the first user interface and the second user interface of the corresponding user interface type. The third user interface of the corresponding user interface type includes a predefined set of elements that are different from the one or more elements of the first user interface and the one or more elements of the second user interface of the corresponding user interface type. The predefined set of elements cannot be changed in response to input detected at the electronic device. as well as Based on the predefined time range in which the current time does not correspond to the electronic device operating in the restricted mode in which one or more of the functions are restricted, the second user interface of the corresponding user interface type is displayed via the display device; In response to detecting a request to exit the restricted mode and when the current time corresponds to the predefined time range, exiting the restricted mode includes stopping the display of the third user interface of the corresponding user interface type; When the current time corresponds to the predefined time range and the third user interface of the corresponding user interface type is not displayed, a redisplay criterion for the third user interface is detected, wherein the redisplay criterion for the third user interface includes a criterion that is met when no user input is detected within the predefined time range; and In response to detecting that the redisplay criteria of the third user interface are met, the third user interface of the corresponding user interface type is displayed via the display device.

44. The method of claim 43, wherein the corresponding user interface type is a dial.

45. The method of claim 44, further comprising: Detect a second sequence of one or more inputs; as well as In response to the detection of a second sequence of the one or more inputs: An operation is performed based on a second sequence of one or more inputs detected when the first user interface of the corresponding user interface type is displayed; as well as The operation is abandoned based on a second sequence of one or more inputs detected when the third user interface of the corresponding user interface type is displayed.

46. ​​The method according to any one of claims 43 to 45, wherein the predefined set of elements comprises the entire third user interface of the corresponding user interface type, and additional elements cannot be added to the third user interface of the corresponding user interface type.

47. The method of any one of claims 43 to 45, wherein the third user interface of the corresponding user interface type includes a distinguishing element, wherein the distinguishing element is a visually distinguishable portion of the third user interface of the corresponding user interface type, and the distinguishing element is not included in the first user interface of the corresponding user interface type or the second user interface of the corresponding user interface type.

48. The method according to any one of claims 43 to 45, further comprising: When displaying the second user interface of the corresponding user interface type, detect a third sequence of one or more inputs; as well as In response to detecting a third sequence of one or more inputs while displaying a second user interface of the corresponding user interface type, an operation is performed; When displaying the third user interface of the corresponding user interface type, detect the third sequence of the one or more inputs; and In response to detecting a third sequence of one or more inputs while displaying the third user interface of the corresponding user interface type, the operation is abandoned.

49. The method according to any one of claims 43 to 45, further comprising: Before detecting the occurrence of the condition corresponding to the triggering of the current user interface of the corresponding user interface type for displaying the electronic device, a first user interface for a first application is displayed, wherein displaying the third user interface of the corresponding user interface type includes stopping the display of the first user interface for the first application.

50. The method according to any one of claims 43 to 45, wherein: The predefined set of elements includes a time indication; and The time indication cannot be changed in response to input detected at the electronic device.

51. The method of claim 49, wherein displaying the third user interface of the corresponding user interface type comprises: Based on the determination that the first application is running in the background, a third user interface of the corresponding user interface type with graphical elements corresponding to the first application is displayed; as well as Based on the determination that the first application is not running, a third user interface of the corresponding user interface type is displayed that does not have the graphical elements corresponding to the first application.

52. The method according to any one of claims 43 to 45, further comprising: When displaying the third user interface of the corresponding user interface type, detect a fourth sequence of one or more inputs; as well as In response to detecting at least one input in a fourth sequence of the one or more inputs, an exit user interface with information for transitioning from the restricted mode to an unrestricted mode is displayed via the display device, wherein the unrestricted mode includes one or more functions that are restricted when in the restricted mode.

53. The method of claim 52, wherein the exit user interface includes a first portion, the first portion including a capability indication for exiting the restricted mode, the method further comprising: Receive input corresponding to the selection of the power indication for exiting the restricted mode; as well as In response to detecting an input corresponding to a selection of the indication for exiting the restricted mode, a second user interface of the corresponding user interface type is displayed via the display device.

54. The method of claim 53, further comprising: When the exit user interface is displayed but the first part of the exit user interface, which includes a power indication for exiting the restricted mode, is not displayed, input corresponding to a request to scroll the exit user interface is detected; as well as In response to detecting input corresponding to a request to scroll the exit user interface, the exit user interface is scrolled to display the first portion of the exit user interface including the power indication for exiting the restricted mode.

55. The method of claim 52, wherein detecting the fourth sequence of the one or more inputs includes detecting rotation of the rotatable input mechanism, the method further comprising: In response to detecting the rotation of the rotatable input mechanism, a second user interface of the corresponding user interface type is displayed.

56. The method according to any one of claims 43 to 45, further comprising: After displaying the third user interface of the corresponding user interface type: Detect the occurrence of inactive conditions; In response to the detection of the inactivity condition, the display device is deactivated; After deactivating the display device, the occurrence of a condition corresponding to the triggering of the current user interface of the corresponding user interface type used to display the electronic device is detected; as well as In response to the detection of a condition corresponding to the triggering of the current user interface for displaying the corresponding user interface type of the electronic device: Based on determining that the current time corresponds to the predefined time range, display the third user interface of the corresponding user interface type; and If the current time does not correspond to the predefined time range, the second user interface of the corresponding user interface type is displayed.

57. The method according to any one of claims 43 to 45, wherein the third user interface of the corresponding user interface type includes an analog indication of time and a digital indication of time.

58. The method of claim 57, wherein, relative to the element of the simulation indication of time corresponding to an hour other than the current hour, the element of the simulation indication of time corresponding to the current hour of the current time is visually emphasized.

59. The method according to any one of claims 43 to 45, further comprising: When the current time corresponds to the predefined time range and when the electronic device is operating in a restricted mode: A fifth sequence of one or more inputs is detected, the fifth sequence of one or more inputs including at least one input detected when the third user interface of the corresponding user interface type is displayed; as well as In response to detecting a fifth sequence of the one or more inputs, exit the restricted mode, wherein exiting the restricted mode includes displaying the second user interface of the corresponding user interface type.

60. The method of any one of claims 43 to 45, wherein the second user interface of the corresponding user interface type includes a first display representation corresponding to the application, the method further comprising: When displaying the second user interface of the corresponding user interface type, an input corresponding to the selection of the first display representation is detected; as well as The application is launched in response to the detection of an input corresponding to a selection of the first indication.

61. The method according to any one of claims 43 to 45, wherein the predefined time range is defined according to a schedule of different time ranges for different days of a specified week.

62. The method according to any one of claims 43 to 45, further comprising: When the current time does not correspond to the predefined time range: A third user interface, including a power indication for activating the restricted mode, is displayed via the display device; Detect the input corresponding to the selection of the indicated energy representation for activating the restricted mode; as well as In response to detecting an input corresponding to a selection of the power indication for activating the restricted mode, the electronic device is operated in the restricted mode.

63. The method according to any one of claims 43 to 45, wherein the third user interface of the corresponding user interface type includes an indication of the user's name and a digital indication of the time.

64. An electronic device comprising: Display devices; as well as Apparatus for performing the method according to any one of claims 43 to 63.

65. A computer program product comprising one or more programs, said one or more programs including instructions that, when executed by one or more processors, cause said one or more processors to perform the method according to any one of claims 43 to 63.

Images