JP7236480B2 - User interfaces for controlling or presenting device usage on electronic devices - Google Patents

Description

The present application relates generally to electronic devices and user interaction with such devices that control or present information regarding the use of the device.

User interaction with electronic devices has increased significantly in recent years. These devices can be devices such as computers, tablet computers, televisions, multimedia devices, mobile devices, and the like.

In some situations, users desire to view information regarding their use of such devices and/or desire to control their use of such devices. Enhancing these interactions improves the user experience with the device and reduces the time of user interaction, which is especially important when the input device is battery operated.

Some embodiments described in this disclosure include one or more electronic devices that present an indication of usage metrics for the device, and one or more operations associated with the electronic device that optionally perform It is intended for Some embodiments described in this disclosure include one or more electronic devices that set, configure, and/or enforce usage limits for the device, as well as one or more related It is intended for the above operations. Some embodiments described in this disclosure provide one or more electronic devices that restrict access to certain applications for certain periods of time, and the electronic devices optionally perform one or more of the above-related It is intended for the above operations. Some embodiments described in this disclosure provide for one or more electronic devices, and optionally the electronic device, to inhibit auxiliary functionality of certain applications when application usage limits or restriction criteria associated with those applications are reached. It is directed to one or more actions related to the above that are systematically performed. Some embodiments described in this disclosure include one or more electronic devices that manage restriction settings with permissions that are optionally provided by another electronic device, and that the electronic device optionally performs is directed to one or more actions associated with A full description of these embodiments is set forth in the Detailed Description, and it should be understood that the above Summary of the Invention does not limit the scope of this disclosure in any way.

For a better understanding of the various embodiments described, please refer to the following Detailed Description in conjunction with the following drawings, like reference numerals denoting the entirety of those figures. refers to the corresponding part through

1 is a block diagram illustrating a portable multifunction device with a touch sensitive display, according to some embodiments; FIG.

FIG. 4 is a block diagram illustrating exemplary components for event processing, according to some embodiments;

FIG. 2 illustrates a portable multifunction device having a touch screen, according to some embodiments;

1 is a block diagram of an exemplary multifunction device with a display and a touch sensitive surface, according to some embodiments; FIG.

FIG. 4 illustrates an exemplary user interface for a menu of applications on a portable multifunction device, according to some embodiments;

4 illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface separate from the display, according to some embodiments;

1 illustrates a personal electronic device, according to some embodiments; FIG.

1 is a block diagram illustrating a personal electronic device, according to some embodiments; FIG.

FIG. 3 illustrates exemplary components of a personal electronic device having a touch-sensitive display and an intensity sensor, according to some embodiments; FIG. 3 illustrates exemplary components of a personal electronic device having a touch-sensitive display and an intensity sensor, according to some embodiments;

2 illustrates exemplary components and user interface of a personal electronic device, according to some embodiments; 2 illustrates exemplary components and user interface of a personal electronic device, according to some embodiments; 2 illustrates exemplary components and user interface of a personal electronic device, according to some embodiments; 2 illustrates exemplary components and user interface of a personal electronic device, according to some embodiments;

4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to present usage metric indications, in accordance with some embodiments of the present disclosure;

FIG. 4 is a flow diagram illustrating a method of presenting usage metric indications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of presenting usage metric indications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of presenting usage metric indications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of presenting usage metric indications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of presenting usage metric indications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of presenting usage metric indications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of presenting usage metric indications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of presenting usage metric indications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of presenting usage metric indications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of presenting usage metric indications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of presenting usage metric indications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of presenting usage metric indications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of presenting usage metric indications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of presenting usage metric indications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of presenting usage metric indications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of presenting usage metric indications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of presenting usage metric indications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of presenting usage metric indications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of presenting usage metric indications, in accordance with some embodiments of the present disclosure; FIG.

4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method by which usage limits are set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure;

4 is a flow diagram illustrating a method of setting, configuring, and/or enforcing usage limits, according to some embodiments of the present disclosure; 4 is a flow diagram illustrating a method of setting, configuring, and/or enforcing usage limits, according to some embodiments of the present disclosure; 4 is a flow diagram illustrating a method of setting, configuring, and/or enforcing usage limits, according to some embodiments of the present disclosure; 4 is a flow diagram illustrating a method of setting, configuring, and/or enforcing usage limits, according to some embodiments of the present disclosure; 4 is a flow diagram illustrating a method of setting, configuring, and/or enforcing usage limits, according to some embodiments of the present disclosure; 4 is a flow diagram illustrating a method of setting, configuring, and/or enforcing usage limits, according to some embodiments of the present disclosure; 4 is a flow diagram illustrating a method of setting, configuring, and/or enforcing usage limits, according to some embodiments of the present disclosure; 4 is a flow diagram illustrating a method of setting, configuring, and/or enforcing usage limits, according to some embodiments of the present disclosure; 4 is a flow diagram illustrating a method of setting, configuring, and/or enforcing usage limits, according to some embodiments of the present disclosure; 4 is a flow diagram illustrating a method of setting, configuring, and/or enforcing usage limits, according to some embodiments of the present disclosure; 4 is a flow diagram illustrating a method of setting, configuring, and/or enforcing usage limits, according to some embodiments of the present disclosure;

4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure;

4 is a flow diagram illustrating a method of restricting access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 is a flow diagram illustrating a method of restricting access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 is a flow diagram illustrating a method of restricting access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 is a flow diagram illustrating a method of restricting access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 is a flow diagram illustrating a method of restricting access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 is a flow diagram illustrating a method of restricting access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 is a flow diagram illustrating a method of restricting access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 is a flow diagram illustrating a method of restricting access to a particular application for a particular period of time, according to some embodiments of the present disclosure; 4 is a flow diagram illustrating a method of restricting access to a particular application for a particular period of time, according to some embodiments of the present disclosure;

4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to throttle specific application auxiliary features upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure;

FIG. 4 is a flow diagram illustrating a method of throttling certain application ancillaries upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of throttling certain application ancillaries upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of throttling certain application ancillaries upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of throttling certain application ancillaries upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of throttling certain application ancillaries upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of throttling certain application ancillaries upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of throttling certain application ancillaries upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of throttling certain application ancillaries upon reaching an application usage limit associated with those applications, in accordance with some embodiments of the present disclosure; FIG.

4 illustrates an exemplary method for an electronic device to manage restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to manage restriction settings with permissions optionally provided by another electronic device, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to manage restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to manage restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to manage restriction settings with permissions optionally provided by another electronic device, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to manage restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to manage restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to manage restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to manage restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to manage restriction settings with permissions optionally provided by another electronic device, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to manage restriction settings with permissions optionally provided by another electronic device, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to manage restriction settings with permissions optionally provided by another electronic device, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to manage restriction settings with permissions optionally provided by another electronic device, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to manage restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to manage restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to manage restriction settings with permissions optionally provided by another electronic device, in accordance with some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to manage restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to manage restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to manage restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure; 4 illustrates an exemplary method for an electronic device to manage restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure;

4 is a flow diagram illustrating a method of managing restriction settings with permissions optionally provided by another electronic device, in accordance with some embodiments of the present disclosure; 4 is a flow diagram illustrating a method of managing restriction settings with permissions optionally provided by another electronic device, in accordance with some embodiments of the present disclosure; 4 is a flow diagram illustrating a method of managing restriction settings with permissions optionally provided by another electronic device, in accordance with some embodiments of the present disclosure; 4 is a flow diagram illustrating a method of managing restriction settings with permissions optionally provided by another electronic device, in accordance with some embodiments of the present disclosure; FIG. 4 is a flow diagram illustrating a method of managing restriction settings with permissions optionally provided by another electronic device, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of managing restriction settings with permissions optionally provided by another electronic device, in accordance with some embodiments of the present disclosure; FIG. FIG. 4 is a flow diagram illustrating a method of managing restriction settings with permissions optionally provided by another electronic device, in accordance with some embodiments of the present disclosure; FIG.

In the following description, exemplary methods, parameters, etc. are described. It should be understood, however, that the purpose of such description is not to limit the scope of this disclosure, but to provide a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methods and interfaces for presenting information regarding device usage and/or controlling device usage. Such techniques can reduce the cognitive burden on users who use such devices and/or who desire to control their use of such devices. In addition, such techniques can reduce processor and battery power that would otherwise be wasted on redundant user input.

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

The terminology used in the description of the various embodiments described herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various embodiments described and in the appended claims, the singular forms "a," "an," and "the" do not clearly indicate to the contrary the context To the extent possible, it is also intended to include plural forms. As used herein, the term "and/or" refers to and includes any and all possible combinations of one or more of the associated listed items. It should also be understood that The terms "includes," "including," "comprises," and/or "comprising," as used herein, refer to the features, integers, steps, specify the presence of acts, elements and/or components but do not exclude the presence or addition of one or more other features, integers, steps, acts, elements, components and/or groups thereof will be further understood.

Optionally, the term "if" can be changed to "when," "upon," "in response to determining," depending on the context. )”, or “in response to detecting”. Similarly, the phrases "if it is determined" or "if (a stated condition or event) is detected" can optionally be , "upon determining", "in response to determining", "upon detecting (the stated condition or event)" depending on the context or "in response to detecting (the stated condition or event)".

Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device such as a mobile phone that also includes PDA functionality and/or other functionality such as music player functionality. Exemplary embodiments of portable multifunction devices include Apple Inc. of Cupertino, Calif.; iPhone(R), iPod Touch(R) and iPad(R) devices. Other portable electronic devices such as laptops or tablet computers with touch-sensitive surfaces (eg, touch screen displays and/or touch pads) are also optionally used. It should also be appreciated that in some embodiments the device is not a portable communication device, but a desktop computer with a touch-sensitive surface (eg, touchscreen display and/or touchpad).

In the discussion that follows, electronic devices that include displays and touch-sensitive surfaces are described. However, it should be understood that the electronic device optionally includes one or more other physical user interface devices such as physical keyboards, mice and/or joysticks.

The device is commonly used in drawing applications, presentation applications, word processing applications, website creation applications, disc authoring applications, spreadsheet applications, gaming applications, telephony applications, video conferencing applications, e-mail applications, instant messaging applications, training It supports various applications such as one or more of a support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application and/or a digital video player application.

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 corresponding information displayed on the device are optionally adjusted and/or changed from application to application and/or within each application. In this way, the common physical architecture (such as the touch-sensitive surface) of the device optionally supports a variety of applications with user interfaces that are intuitive and transparent to the user.

Attention is now directed to embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating portable multifunction device 100 with touch-sensitive display system 112, according to some embodiments. The touch-sensitive display 112 is sometimes referred to as a "touch screen" for convenience and is sometimes known or referred to as a "touch-sensitive display system." Device 100 includes memory 102 (optionally including one or more computer readable storage media), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110 , speaker 111 , microphone 113 , input/output (I/O) subsystem 106 , other input control devices 116 and external ports 124 . Device 100 optionally includes one or more photosensors 164 . Device 100 optionally includes one or more contact intensity sensors 165 for detecting the intensity of contact on device 100 (eg, a touch-sensitive surface such as touch-sensitive display system 112 of device 100). device 100 to generate tactile output on device 100 (e.g., on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touch pad 355 of device 300); One or more tactile output generators 167 are optionally included. These components optionally communicate via one or more communication buses or signal lines 103 .

As used herein and in the claims, the term "strength" of contact on the touch-sensitive surface refers to the force or pressure (force per unit area) of contact (e.g., finger contact) on the touch-sensitive surface. ), or a substitute for contact force or pressure on a touch-sensitive surface. The intensity of contact has a value range that includes at least four different values, and more typically includes hundreds (eg, at least 256) different values. The strength of contact is optionally determined (or measured) using various techniques and various sensors or combinations of sensors. For example, one or more force sensors under or adjacent to the touch-sensitive surface are optionally used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (eg, a weighted average) to determine a contact force estimate. Similarly, the stylus' pressure-sensitive tip is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and/or changes in the contact area detected on the touch-sensitive surface, the capacitance and/or changes in the touch-sensitive surface proximate to the contact, and/or the resistance and/or changes in the touch-sensitive surface proximate to the contact. /or variations thereof are optionally used as a substitute for contact force or pressure on the touch-sensitive surface. In some implementations, the alternative measure for contact force or pressure is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is in units corresponding to the alternative measure). explained). In some implementations, the alternative measurement for contact force or pressure is converted to an estimated force or pressure, and the estimated force or pressure is used to determine if the intensity threshold is exceeded. (eg, the intensity threshold is the pressure threshold measured in units of pressure). for displaying affordances (e.g., on touch-sensitive displays) and/or for receiving user input (e.g., touch-sensitive displays, touch-sensitive Additional devices that may not otherwise be accessible by the user on a reduced size device that has a limited area (via physical/mechanical controls such as faces or knobs or buttons). Allows user access to functionality.

As used herein and in the claims, the term "tactile output" refers to the physical displacement of the device relative to its previous position, the configuration of the device, to be detected by the user in the user's sense of touch. Refers to the physical displacement of an element (eg, touch-sensitive surface) relative to another component of a device (eg, housing), or the displacement of a component relative to the device's center of mass. Tactile output produced by physical displacement, e.g., in situations where a device or device component is in contact with a touch-sensitive surface of a user (e.g., a finger, palm, or other portion of a user's hand) is interpreted by the user as a tactile sensation corresponding to a perceived change in the physical properties of the device or device component. For example, movement of a touch-sensitive surface (eg, a touch-sensitive display or trackpad) is optionally interpreted by the user as a "down-click" or "up-click" of a physical actuator button. In some cases, a user can "down-click" or "up-click" even when there is no movement of the physical actuator button associated with the touch-sensitive surface physically pressed (e.g., displaced) by the user's motion. ” and other tactile sensations. As another example, movement of the touch-sensitive surface is optionally interpreted or perceived by the user as "roughness" of the touch-sensitive surface, even if there is no change in the smoothness of the touch-sensitive surface. be done. Such a user's interpretation of touch depends on the user's personal sensory perception, but there are many sensory perceptions of touch that are common to the majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "up-click", "down-click", "roughness"), the generated Tactile output corresponds to physical displacement of the device, or components of the device, that produce the described sensory perception of a typical (or average) user.

Device 100 is but one example of a portable multifunction device, and device 100 optionally has more or fewer components than those shown and may include two or more components. It should be understood to optionally have different configurations or arrangements of components in any combination or arrangement. The various components shown in FIG. 1A are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing circuits and/or application specific integrated circuits.

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

Peripheral interface 118 may be used to connect input and output peripherals of the device to CPU 120 and memory 102 . One or more processors 120 operate or execute various software programs and/or instruction sets stored in memory 102 to perform various functions for device 100 and to 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.

Radio frequency (RF) circuitry 108 transmits and receives RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to electromagnetic signals or vice versa to communicate with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 optionally includes an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module ( SIM) cards and well-known circuits for performing their functions, including but not limited to memory and the like. The RF circuit 108 is optionally connected to the Internet, also referred to as the World Wide Web (WWW), intranets, and/or cellular telephone networks, wireless local area networks (LANs) and Communicate wirelessly with other devices and/or networks, such as wireless networks such as a metropolitan area network (MAN). RF circuitry 108 optionally includes well-known circuitry for detecting a near field communication (NFC) field, such as by a near field communication radio. Wireless communication optionally uses any of a number of communication standards, protocols and technologies, including the Global System for Mobile Communications ( Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSDPA) speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (Dual-Cell HSPA, DC-HSPDA), Long term evolution (LTE), Near 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), Wireless Fidelity (Wi-Fi)® (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n , and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, protocols for email (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g. extensible messaging and presence protocol (POP)) Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and /or Short Message Service (SMS), or any other suitable communication protocol, including but not limited to communication protocols not yet developed as of the filing date of this document.

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 peripherals interface 118 , converts the audio data to electrical signals, and transmits the electrical signals to speaker 111 . The speaker 111 converts the electrical signal into human audible sound waves. Audio circuitry 110 also receives electrical signals converted from sound waves by microphone 113 . Audio circuitry 110 converts the electrical signals to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is optionally retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118 . In some embodiments, audio circuitry 110 further comprises a headset jack (eg, 212 in FIG. 2). The headset jack connects audio circuitry 110 and detachable audio input/output peripherals, such as output-only headphones or headsets that have both an output (e.g., monaural or binaural headphones) and an input (e.g., a microphone). provides an interface between

I/O subsystem 106 couples input/output peripherals of device 100 , such as touch screen 112 and other input control devices 116 , to peripherals interface 118 . I/O subsystem 106 optionally includes one or more input controllers 160 for display controller 156, light sensor controller 158, intensity sensor controller 159, tactile feedback controller 161, and other input or control devices. include. One or more input controllers 160 receive/send electrical signals from/to other input control devices 116 . Other input control devices 116 optionally include physical buttons (eg, push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and the like. In some alternative embodiments, input controller(s) 160 is optionally coupled to any of a keyboard, an infrared port, a USB port, and a pointer device such as a mouse (or not connected to either). One or more buttons (eg, 208 in FIG. 2) optionally include up/down buttons for volume control of speaker 111 and/or microphone 113 . The one or more buttons optionally include push buttons (eg, 206 in FIG. 2).

U.S. patent application Ser. No. 11/322,549, "Unlocking a Device by Performing Gestures on an Unlock Image," filed Dec. 23, 2005, U.S. Pat. No. 7,657,849; Optionally, a quick press of a push button unlocks the touchscreen 112 or unlocks the device to unlock the touchscreen, as described in the entirety of which is incorporated herein by reference. Optionally initiate a process using the above gesture. A longer press on the push button (eg, 206) optionally powers the device 100 on and off. The functionality of one or more of the buttons is optionally user customizable. Touch screen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

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

Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from a user based on tactile and/or tactile contact. Touchscreen 112 and display controller 156 (together with any associated modules and/or instruction sets in memory 102) detect contact (and any movement or interruption of contact) on touchscreen 112 and into interactions with user interface objects (eg, one or more softkeys, icons, web pages, or images) displayed on touch screen 112 . In an exemplary embodiment, the contact point between touch screen 112 and the user corresponds to the user's finger.

The touch screen 112 optionally uses LCD (Liquid Crystal Display) technology, LPD (Light Emitting Polymer Display) technology or LED (Light Emitting Diode) technology, although in other embodiments other display technologies are used. The touchscreen 112 and display controller 156 use capacitive, resistive, infrared, and surface ultrasonic technologies, as well as other proximity sensor arrays for determining one or more points of contact with the touchscreen 112. or other elements, optionally detecting contact and any movement or interruption thereof using any of a number of now-known or later-developed touch-sensing technologies. to detect. In an exemplary embodiment, Apple Inc. of Cupertino, Calif. Projected mutual-capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® by Apple.

The touch-sensitive display in some embodiments of the touch screen 112 optionally includes the following U.S. Pat. /or similar to the multi-touch sensing touchpads described in Westerman 6,677,932 and/or US Patent Application Publication No. 2002/0015024A1. Each of these documents is incorporated herein by reference in its entirety. However, the touchscreen 112 displays visual output from the device 100, whereas the touch-sensitive touchpad does not provide visual output.

Touch sensitive displays in some embodiments of touch screen 112 are described in the following applications. (1) U.S. Patent Application Serial No. 11/381,313, filed May 2, 2006, entitled "Multipoint Touch Surface Controller"; Multipoint Touchscreen," (3) 10/903,964, filed Jul. 30, 2004; "Gestures For Touch Sensitive Input Devices," (4) 11/048, filed Jan. 31, 2005, 264, "Gestures For Touch Sensitive Input Devices," (5) Serial No. 11/038,590, filed Jan. 18, 2005, "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices, (5) 56 20," 11/228,758, filed September 16, 2005, "Virtual Input Device Placement On A Touch Screen User Interface," (7) 11/228,700, filed September 16, 2005, " Operation Of A Computer With A Touch Screen Interface", (8) Serial No. 11/228,737 filed Sep. 16, 2005, "Activating Virtual Keys Of A Touch-Screen Virtual Keyboard", 2006; Serial No. 11/367,749, filed March 3, "Multi-Functional Hand-Held Device." All of these applications are incorporated herein by reference in their entireties.

Touch screen 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. A user optionally contacts touch screen 112 using any suitable object or accessory, such as a stylus, finger, or the like. In some embodiments, user interfaces are designed to work primarily with finger-based contacts and gestures, and the large finger contact area on touch screens can be less accurate than stylus-based input. be. In some embodiments, the device converts coarse finger-based input into precise pointer/cursor positions or commands to perform user-desired actions.

In some embodiments, in addition to the touchscreen, device 100 optionally includes a touchpad (not shown) for activating or deactivating certain functions. In some embodiments, a touchpad is a touch-sensitive area of a device that displays no visual output, unlike a touchscreen. The touchpad is optionally a touch-sensitive surface separate from the touchscreen 112 or an extension of the touch-sensitive surface formed by the touchscreen.

Device 100 also includes a power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, power failure detection circuitry, a power converter or inverter, power status indicators (e.g., light emitting diodes ( LEDs)), and any other components associated with the generation, management, and distribution of power within a portable device.

Device 100 also optionally includes one or more photosensors 164 . FIG. 1A shows a photosensor connected to photosensor controller 158 in I/O subsystem 106 . Photosensor 164 optionally includes a charge coupled device (CCD) or complementary metal oxide semiconductor (CMOS) phototransistor. Optical sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. In conjunction with imaging module 143 (also referred to as a camera module), optical sensor 164 optionally captures still images or video. In some embodiments, the optical sensor is opposite the touchscreen display 112 on the front of the device 100 to enable the touchscreen display as a viewfinder for still image and/or video capture. is placed on the back of the In some embodiments, optionally, a light is placed on the front of the device so that a user can see other videoconference participants on the touchscreen display at the same time that the user's image is obtained for the videoconference. A sensor is placed. In some embodiments, the position of light sensor 164 can be changed by the user (eg, by rotating the lens and sensor within the device housing), thereby enabling teleconferencing and still and/or video A single photosensor 164 is used in conjunction with the touch screen display for both image acquisition.

Device 100 also optionally includes one or more contact intensity sensors 165 . FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 within I/O subsystem 106 . Contact intensity sensor 165 may include one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., on the touch-sensitive surface). optionally a sensor used to measure the force (or pressure) of the contact. Contact intensity sensor 165 receives contact intensity information (eg, pressure information or a proxy for pressure information) from the surrounding environment. In some embodiments, at least one contact intensity sensor is located on or in close proximity to the touch-sensitive surface (eg, touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back side of device 100 , opposite touch screen display 112 located on the front side of device 100 .

Device 100 also optionally includes one or more proximity sensors 166 . FIG. 1A shows proximity sensor 166 coupled with peripherals interface 118 . Alternatively, proximity sensor 166 is optionally connected to input controller 160 within I/O subsystem 106 . Proximity sensor 166 is optionally disclosed in U.S. patent application Ser. 620,702, "Using Ambient Light Sensor To Augment Proximity Sensor Output", ibid. 11/586,862, "Automated Response To And Sensing Of User Activity In Portables", ibid. It optionally functions as described in "Methods And Systems For Automatic Configuration Of Peripherals", which applications are hereby incorporated by reference in their entireties. In some embodiments, the proximity sensor turns off and disables the touchscreen 112 when the multifunction device is placed near the user's ear (eg, when the user is making a phone call).

Device 100 also optionally includes one or more tactile output generators 167 . FIG. 1A shows a tactile output generator coupled to haptic feedback controller 161 within I/O subsystem 106 . Tactile output generator 167 may be one or more electroacoustic devices such as speakers or other audio components and/or motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators or other tactile output generating configurations. Optionally includes an electromechanical device that converts energy into linear motion, such as an element (eg, a component that converts an electrical signal to a tactile output on the device). Contact intensity sensor 165 receives haptic feedback generation instructions from haptic feedback module 133 and generates a tactile output on device 100 that can be sensed by a user of device 100 . In some embodiments, at least one tactile output generator is located on or proximate to a touch-sensitive surface (eg, touch-sensitive display system 112) and optionally , vertically (eg, into/out of the surface of device 100) or laterally (eg, back and forth in the same plane as the surface of device 100) to generate tactile output. In some embodiments, at least one tactile output generator sensor is located on the back of device 100 , opposite touch screen display 112 located on the front of device 100 .

Device 100 also optionally includes one or more accelerometers 168 . FIG. 1A shows accelerometer 168 coupled to peripherals interface 118 . Alternatively, accelerometer 168 is optionally coupled to input controller 160 within I/O subsystem 106 .加速度計１６８は、任意選択的に、米国特許出願公開第２００５０１９００５９号、「Ａｃｃｅｌｅｒａｔｉｏｎ－ｂａｓｅｄ Ｔｈｅｆｔ Ｄｅｔｅｃｔｉｏｎ Ｓｙｓｔｅｍ ｆｏｒ Ｐｏｒｔａｂｌｅ Ｅｌｅｃｔｒｏｎｉｃ Ｄｅｖｉｃｅｓ」、及び同第２００６００１７６９２号、「Ｍｅｔｈｏｄｓ Ａｎｄ Ａｐｐａｒａｔｕｓｅｓ Ｆｏｒ Ｏｐｅｒａｔｉｎｇ Ａ Ｐｏｒｔａｂｌｅ Ｄｅｖｉｃｅ Ｂａｓｅｄ Ｏｎ Ａｎ Ａｃｃｅｌｅｒｏｍｅｔｅｒ , both of which are incorporated herein by reference in their entireties. In some embodiments, information is displayed on the touch screen display in portrait or landscape orientation based on analysis of data received from one or more accelerometers. Device 100 optionally, in addition to accelerometer(s) 168, has a magnetometer (not shown) and GPS for obtaining information about the position and orientation (e.g., portrait or landscape) of device 100. or GLONASS or other global navigation system) receiver (not shown).

In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or instruction set) 128, touch/motion module (or instruction set) 130, 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 (or instruction set) 136 . Additionally, in some embodiments, memory 102 (FIG. 1A) or memory 370 (FIG. 3) stores device/global internal state 157, as shown in FIGS. 1A and 3 . Device/global internal state 157 includes one or more of the following: an active application state indicating which application, if any, is currently active; which application, view, or other information is displayed on the touch screen display 112; sensor state, including information obtained from the device's various sensors and input control device 116, and location information about the device's position and/or orientation.

operating system 126 (e.g., Darwin®, RTXC®, LINUX®, UNIX®, OS X®, iOS®, WINDOWS®, or Embedded operating systems such as VxWorks®) include various software components and/or drivers for controlling and managing common system tasks (e.g., memory management, storage device control, power management, etc.), It facilitates communication between various hardware and software components.

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 RF circuitry 108 and/or external ports 124 . include. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE®, etc.) connects to other devices directly or indirectly through a network (e.g., Internet, wireless LAN, etc.). adapted to connect to In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector the same as or similar to the 30-pin connector used on the iPod® (trademark of Apple Inc.) device, and/or Or a compatible multi-pin (eg, 30-pin) connector.

Contact/motion module 130 (in conjunction with display controller 156) optionally detects contact with touchscreen 112 and other touch-sensitive devices (eg, touchpads or physical click wheels). The contact/motion module 130 determines whether contact has occurred (e.g., detecting a finger-down event), the strength of the contact (e.g., the force or pressure of the contact, or alternatives to the force or pressure of the contact). determining whether there is movement of the contact and tracking movement across the touch-sensitive surface (e.g., detecting one or more events of dragging a finger); Contains various software components for performing various operations related to detecting contact, such as determining whether contact has stopped (e.g., detecting a finger-up event or interruption of contact) . Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the contact point represented by the set of contact data optionally includes speed (magnitude), velocity (magnitude and direction), and/or acceleration (magnitude and/or or change in direction). These operations are optionally applied to single contacts (eg, single-finger contacts) or multiple simultaneous contacts (eg, “multi-touch”/multiple-finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on the touchpad.

In some embodiments, the contact/motion module 130 is configured to: One or more sets of intensity thresholds are used. In some embodiments, at least a subset of the intensity thresholds are determined according to software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a particular physical actuator, but rather by changing the physical hardware of device 100). may be adjusted without). For example, the mouse "click" threshold of a trackpad or touchscreen display may be set to any of a wide range of predefined thresholds without modifying the hardware of the trackpad or touchscreen display. Additionally, in some implementations, the user of the device is provided with software settings for adjusting one or more of the sets of intensity thresholds (e.g., by adjusting individual intensity thresholds, and/or by adjusting multiple intensity thresholds at once with the system-level click "intensity" parameter).

Contact/motion module 130 optionally detects gesture input by the user. Different gestures on the touch-sensitive surface have different contact patterns (eg, different movement, timing, and/or intensity of detected contact). Thus, gestures are optionally detected by detection of specific contact patterns. For example, detecting a finger tap gesture involves detecting a finger down event (e.g., at an icon location) followed by a finger down event at the same (or substantially the same) location as the finger down event. including detecting a lift-off event. As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger down event, followed by detecting one or more finger dragging events, followed by and detecting finger lift (lift-off) events.

The graphics module 132 can be used on the touch screen 112 or other display, including components for changing the visual effects (e.g., brightness, transparency, saturation, contrast, or other visual characteristics) of displayed graphics. includes various known software components for rendering and displaying graphics in As used herein, the term “graphics” includes, but is not limited to, text, web pages, icons (such as user interface objects including softkeys), digital images, videos, animations, etc. Contains any object that can be displayed against.

In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. Graphics module 132 receives, from an application or the like, one or more codes specifying the graphics to be displayed along with coordinate data and other graphics property data, if desired, and then outputs to display controller 156 . Generate screen image data.

Haptic feedback module 133 is used by tactile output generator(s) 167 to generate tactile outputs at one or more locations on device 100 in response to user interaction with device 100. Contains various software components for generating instructions.

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

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

Application 136 optionally includes the following modules (or instruction sets), or subsets or supersets thereof.
- the contacts module 137 (sometimes called an address book or contact list);
a telephone module 138;
a teleconferencing module 139,
- email client module 140;
an instant messaging (IM) module 141;
● training support module 142,
- a camera module 143 for still and/or video images;
an image management module 144;
● video player module,
● music player module,
the browser module 147,
a calendar module 148;
Of weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5 and other widgets obtained by the user, and user-created widgets 149-6 Widget module 149, optionally including one or more of
- a widget creation module 150 for creating user-created widgets 149-6;
a search module 151,
- a video and music player module 152, which integrates a video player module and a music player module;
● memo module 153,
• a map module 154 and/or • an online video module 155;

Examples of other applications 136 that are optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA enabled applications, encryption, digital Rights management, speech recognition, and speech reproduction are included.

In conjunction with touch screen 112 , display controller 156 , touch/motion module 130 , graphics module 132 , and text input module 134 , contact module 137 (eg, an application of contact module 137 in memory 102 or memory 370 optionally used to manage an address book or contact list (stored in internal state 192), including adding name(s) to the address book; ), associate phone number(s), email address(es), address(es), or other information with names, associate images with names, classify names and providing a phone number or email address to initiate and/or facilitate communication by phone 138, videoconferencing module 139, email 140, or IM 141;

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, touch/motion module 130, graphics module 132, and text input module 134, telephone module 138 optionally includes , enter a series of characters corresponding to a phone number, access one or more phone numbers in the contacts module 137, modify the entered phone number, dial the corresponding phone number, and have a conversation. , and to disconnect or hang up when the conversation is complete. As noted above, wireless communications optionally use any of a number of communication standards, protocols, and techniques.

RF circuit 108, audio circuit 110, speaker 111, microphone 113, touch screen 112, display controller 156, light sensor 164, light sensor controller 158, touch/motion module 130, graphics module 132, text input module 134, contact module 137. , and telephony module 138, the videoconferencing module 139 executes, according to the user's instructions, for starting, conducting, and terminating a videoconference between the user and one or more other participants. Contains possible instructions.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, touch/motion module 130, graphics module 132, and text input module 134, email client module 140 composes emails in response to user instructions. contains executable instructions for transmitting, receiving, and managing In conjunction with image management module 144 , email client module 140 greatly facilitates creating and sending emails with still or video images captured by camera module 143 .

In conjunction with RF circuitry 108, touch screen 112, display controller 156, touch/motion module 130, graphics module 132, and text input module 134, instant messaging module 141 inputs text strings corresponding to instant messages, (e.g., using the Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephone-based instant messaging, or XMPP for Internet-based instant messaging , SIMPLE, or IMPS), receive instant messages, and refer to received instant messages. In some embodiments, instant messages sent and/or received are optionally graphics, photos, audio files, as supported by MMS and/or Enhanced Messaging Service (EMS). , video files, and/or other attachments. As used herein, "instant messaging" refers to telephone-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., using XMPP, SIMPLE, or IMPS). (messages sent as

In conjunction with RF circuitry 108, touch screen 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, training support module 142: Generate workouts (e.g., with time, distance, and/or calorie expenditure goals), communicate with training sensors (sports devices), receive training sensor data, and calibrate sensors used to monitor training , select and play music for training, and display, store, and transmit training data.

In conjunction with touch screen 112, display controller 156, light sensor(s) 164, light sensor controller 158, touch/motion module 130, graphics module 132, and image management module 144, camera module 143 captures still images or It contains executable instructions to capture videos (including video streams) and store them in memory 102 , change characteristics of still images or videos, or delete still images or videos from memory 102 .

In conjunction with touch screen 112, display controller 156, touch/motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 arranges and modifies still and/or video images. Contains executable instructions to (eg, edit) or otherwise manipulate, label, delete, present (eg, in a digital slideshow or album), and store.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, touch/motion module 130, graphics module 132, and text input module 134, browser module 147 can display web pages, portions thereof, and web pages. Contains executable instructions for browsing the Internet following user instructions including retrieving, linking, receiving and displaying linked attachments and other files.

In conjunction with RF circuitry 108, touch screen 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 is able to and executable instructions for creating, displaying, modifying, and storing calendars and data associated with calendars (eg, calendar items, to-do lists, etc.) in accordance with the .

In conjunction with RF circuit 108, touch screen 112, display controller 156, touch/motion module 130, graphics module 132, text input module 134, and browser module 147, widget module 149 is optionally downloaded and used by the user. widget 149-1, stock widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5), or mini-applications created by users (eg , user created widget 149-6). In some embodiments, widgets include Hypertext Markup Language (HTML) files, Cascading Style Sheets (CSS) files, and JavaScript files. In some embodiments, widgets include XML (Extensible Markup Language) files and JavaScript files (eg, Yahoo! widgets).

In conjunction with RF circuitry 108, touch screen 112, display controller 156, touch/motion module 130, graphics module 132, text input module 134, and browser module 147, widget creation module 150 optionally creates widgets. (eg, turn user-specified portions of a web page into widgets).

In conjunction with touch screen 112 , display controller 156 , touch/motion module 130 , graphics module 132 , and text input module 134 , search module 151 follows user instructions and provides one or more search criteria (e.g., one or more user-specified search terms) to search for text, music, sounds, images, videos, and/or other files in memory 102 that match a user-specified search term.

In conjunction with touch screen 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 can display MP3 or AAC files, etc. and video (on touch screen 112 or via external port 124). contains executable instructions for displaying, presenting or otherwise reproducing (on a connected external display). In some embodiments, device 100 optionally includes the functionality of an MP3 player such as an iPod (trademark of Apple Inc.).

In conjunction with touch screen 112, display controller 156, touch/motion module 130, graphics module 132, and text input module 134, notes module 153 is used to create and manage notes, to-do lists, etc., according to user instructions. contains executable instructions for

In conjunction with RF circuitry 108, touch screen 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 optionally: Receive and display maps and data associated with maps (e.g., driving directions, data for stores and other points of interest at or near a particular location, and other location-based data) at the user's direction; used to create, modify, and store

In conjunction with touch screen 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, online video Module 155 indicates that the user is using H.264. 264, etc., to access, view, receive (eg, by streaming and/or downloading), and receive (eg, on a touch screen or externally connected via the external port 124) (on your display), send emails containing links to specific online videos, and otherwise manage them. In some embodiments, instant messaging module 141 is used rather than email client module 140 to send links to specific online videos. Additional description of online video applications can be found in U.S. Provisional Patent Application No. 60/936,562, "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," filed Jun. 20, 2007, and 2007 U.S. patent application Ser. is incorporated herein by reference.

Each of the modules and applications identified above comprise a set of executable instructions for performing one or more of the functions described above, as well as the methods described herein (e.g., the computer-implemented methods described herein). and other information processing methods). These modules (eg, instruction sets) need not be implemented as separate software programs, procedures, or modules, and thus various embodiments optionally include various subsets of these modules. are combined or rearranged in other ways. For example, a video player module is optionally combined with a music player module into a single module (eg, video and music player module 152 of FIG. 1A). In some embodiments, memory 102 optionally stores a subset of the modules and data structures identified above. In addition, memory 102 optionally stores additional modules and data structures not described above.

In some embodiments, device 100 is a device on which operations of a predefined set of functions are performed exclusively through a touchscreen and/or touchpad. By using a touchscreen and/or touchpad as the primary input control device for operation of device 100, the number of physical input control devices (pushbuttons, dials, etc.) on device 100 is optionally reduced. be.

A predefined set of functions that are performed exclusively through the touchscreen and/or touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad navigates device 100 from any user interface displayed on device 100 to a main menu, home menu, or root menu when touched by a user. In such embodiments, the "menu button" is implemented using the touchpad. In some other embodiments, the menu buttons are physical push buttons or other physical input control devices instead of touchpads.

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

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

In some embodiments, application internal state 192 indicates resume information used when application 136-1 resumes execution, information being displayed or prepared for display by application 136-1. one or more of user interface state information, a state queue for allowing the user to return to a previous state or view of the application 136-1, and a redo/undo queue of previous actions taken by the user. including additional information such as

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

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

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

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

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 respective application) in which the touch is detected optionally corresponds to a program level within the application's program hierarchy or view hierarchy. For example, the lowest-level view in which touch is detected is optionally called the hit view, and the set of events recognized as appropriate input is optionally the initial touch that initiates a touch-based gesture. is determined based at least in part on the hit views of the .

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 hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should process the sub-event. In most situations, the hit view is the lowest level view where the first sub-event occurs (eg, the first sub-event in the sequence of sub-events forming the event or potential event). Once a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events associated with the same touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which view(s) in the view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only hit views should receive a particular sequence of sub-events. In another embodiment, the active event recognizer determination module 173 determines that all views containing the physical location of the sub-event are actively participating views, thus all actively participating views are: Determine that a particular sequence of sub-events should be received. In other embodiments, even if a touch sub-event is completely localized to a region associated with a particular view, the view higher up the hierarchy remains the actively involved view.

Event dispatcher module 174 dispatches event information to an event recognizer (eg, event recognizer 180). In embodiments that include active event recognizer determination module 173 , event dispatcher module 174 distributes event information to event recognizers determined by active event recognizer determination module 173 . In some embodiments, the event dispatcher module 174 stores event information obtained by the corresponding event receiver 182 in an event queue.

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

In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each containing instructions for handling touch events that occur within respective views of the application's user interface. including. Each application view 191 of application 136 - 1 includes one or more event recognizers 180 . Typically, each application view 191 includes multiple event recognizers 180 . In other embodiments, one or more of event recognizers 180 are separate modules, such as a user interface kit (not shown) or higher-level objects from which application 136-1 inherits methods and other characteristics. is part of In some embodiments, each event handler 190 processes one or more of event data 179 received from data updater 176 , object updater 177 , GUI updater 178 , and/or event sorter 170 . including. Event handler 190 optionally uses or calls data updater 176 , object updater 177 , or GUI updater 178 to update application internal state 192 . Alternatively, one or more of application views 191 include one or more corresponding event handlers 190 . Also, in some embodiments, one or more of data updater 176 , object updater 177 , and GUI updater 178 are included in each application view 191 .

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

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

The event comparator 184 compares the event information to predefined event or sub-event definitions and determines an event or sub-event or determines or updates the status of an event or sub-event based on the comparison. In some embodiments, event comparator 184 includes event definitions 186 . Event definitions 186 include definitions of events (eg, a predefined series of sub-events), eg, event 1 (187-1), event 2 (187-2), and so on. In some embodiments, sub-events in event 187 include, for example, beginning of touch, end of touch, movement of touch, stop of touch, and multiple touches. In one embodiment, the definition for event 1 (187-1) is a double tap on a displayed object. A double-tap is, for example, the first touch on a displayed object during a given phase (start of touch), the first lift-off during a given phase (end of touch), the Including a second touch on the display object (onset of touch) and a second lift-off during a predetermined phase (end of touch). In another example, the definition of event 2 (187-2) is a drag operation on a displayed object. Drag operations include, for example, touching (or contacting) on a displayed object during predetermined stages, moving the touch across the touch-sensitive display 112, and lifting off the touch (finishing the touch). In some embodiments, the event also includes information about one or more associated event handlers 190 .

In some embodiments, event definitions 187 include event definitions for respective user interface objects. In some embodiments, event comparator 184 performs hit testing to determine user interface objects associated with sub-events. For example, in an application view in which three user interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 determines which of the three user interface objects is displayed. Hit test to determine if it is associated with a touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the results of the hit test to determine which event handler 190 should be activated. For example, the event comparator 184 selects the event handler associated with the object that triggers the sub-event and hit test.

In some embodiments, the definition for each event 187 also includes a delay action that delays the delivery of event information until it is determined if a series of sub-events corresponds to the event recognizer's event type. include.

If the respective event recognizer 180 determines that the sequence of sub-events does not match any of the events in the event definition 186, the respective event recognizer 180 enters an event not possible, event failed, or event terminated state, After that, ignore the next sub-event of the touch-based gesture. In this situation, if there is another event recognizer that remains active for the hit view, that event recognizer will continue to track and process the ongoing touch-based gesture sub-events.

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

In some embodiments, each event recognizer 180 activates the event processor 190 associated with the event when one or more specific sub-events of the event are recognized. In some embodiments, each event recognizer 180 delivers event information associated with the event to the event processor 190 . Activating the event handler 190 is different than sending (and deferring sending) a sub-event to each hit view. In some embodiments, the event recognizer 180 throws a flag associated with the recognized event, and the event handler 190 associated with the flag catches the flag and performs predefined processing. .

In some embodiments, event delivery instructions 188 include sub-event delivery instructions to deliver event information about the sub-event without activating the event handler. Instead, the sub-event delivery instructions deliver event information to the event handlers or actively participating views associated with the series of sub-events. An event handler associated with a sequence of sub-events or actively participating views receives event information and performs predetermined processing.

In some embodiments, data updater 176 creates and updates data used by application 136-1. For example, the data updater 176 updates phone numbers used by the contacts module 137 or stores video files used by the video player module. In some embodiments, object updater 177 creates and updates objects used by application 136-1. For example, the object updater 177 creates new user interface objects or updates the positions of user interface objects. The 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 a touch-sensitive display.

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

The foregoing discussion of event handling of a user's touch on a touch-sensitive display also applies to other forms of user input for operating multifunction device 100 with input devices, all of which are on touch screens. It should be understood that it is not initiated. For example, mouse movement and mouse button presses optionally adapted to pressing or holding a single or multiple keyboards, contact movements such as tapping, dragging, scrolling on a touchpad, pen stylus input, Movements, verbal instructions, detected eye movements, biometric inputs, and/or any combination thereof are optionally utilized as inputs corresponding to sub-events that define the event to be recognized. .

FIG. 2 illustrates portable multifunction device 100 having touch screen 112, according to some embodiments. The touchscreen optionally displays one or more graphics within a user interface (UI) 200 . In this embodiment, as well as those described below, the user may, for example, use one or more fingers 202 (not shown to scale) or one or more styluses 203 (not shown to scale). not drawn to scale) can be used to select one or more of the graphics by making a gesture on the graphic. In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture is one or more taps, one or more swipes (left to right, right to left, up and/or down), and/or Rolling (right-to-left, left-to-right, upwards and/or downwards) of the touching fingers is optionally included. In some implementations or situations, accidental contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon is optional and does not select the corresponding application when the gesture corresponding to selection is a tap.

Device 100 also optionally includes one or more physical buttons, such as “home” or menu button 204 . As mentioned above, menu button 204 is optionally used to navigate to any application 136 in the set of applications that are optionally running on device 100 . Alternatively, in some embodiments, menu buttons are implemented as softkeys in a GUI displayed on touch screen 112 .

In some embodiments, the device 100 includes a touch screen 112, a menu button 204, push buttons 206 for powering the device on/off and locking the device, volume control button(s) 208, subscription It includes a Person Identity Module (SIM) card slot 210, a headset jack 212, and an external port 124 for docking/charging. The push button 206 turns power on and off on the device by depressing the button and holding the button down for a predetermined time interval, depressing the button and releasing the button before the predetermined time interval elapses. is optionally used to lock and/or unlock the device or initiate an unlocking process by releasing the . In an alternative embodiment, device 100 also receives verbal input through microphone 113 to activate or deactivate some functions. Device 100 may also include one or more contact intensity sensors 165 to detect the intensity of contact on touch screen 112 and/or one or more tactile sensors to generate tactile output to the user of device 100 . An output generator 167 is also optionally included.

FIG. 3 is a block diagram of an exemplary multifunction device with a display and touch-sensitive surface, according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, desktop computer, tablet computer, multimedia playback device, navigation device, educational device (such as a children's learning toy), gaming system, or control device (e.g., home controller for commercial use or business use). 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 processors for interconnecting these components. Includes communication bus 320 . Communication bus 320 optionally includes circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device 300 includes input/output (I/O) interface 330 including display 340, which is typically a touch screen display. I/O interface 330 also includes a keyboard and/or mouse (or other pointing device) 350 and touchpad 355 for generating tactile output on device 300 (e.g., as described above with reference to FIG. 1A). tactile output generator 357 (similar to tactile output generator(s) 167), sensor 359 (e.g., light sensor, acceleration sensor, proximity sensor, touch sensitive sensor, and/or as described above with reference to FIG. 1A); optional contact intensity sensor(s) similar to 165). Memory 370 includes high speed random access memory such as DRAM, SRAM, DDR RAM or other random access solid state memory devices, and also one or more magnetic disk storage devices, optical disk storage devices, flash memory devices or other non-volatile memory devices. Optionally includes non-volatile memory such as a non-volatile solid state storage device. Memory 370 optionally includes one or more storage devices located remotely from CPU(s) 310 . In some embodiments, memory 370 stores programs, modules and data structures similar to those stored in memory 102 of portable multifunction device 100 (FIG. 1A), or a subset thereof. do. Additionally, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100 . For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, word processing module 384, website creation module 386, disc authoring module 388 and/or spreadsheet module 390, although portable multiple Memory 102 of functional device 100 (FIG. 1A) optionally does not store these modules.

Each of the above-identified elements of FIG. 3 are optionally stored in one or more of the aforementioned memory devices. Each of the modules identified above corresponds to a set of instructions that perform the functions described above. The modules or programs (e.g., instruction sets) identified above need not be implemented as separate software programs, procedures, or modules; thus, various embodiments optionally include combine or otherwise rearrange various subsets of . In some embodiments, memory 370 optionally stores a subset of the modules and data structures identified above. In addition, memory 370 optionally stores additional modules and data structures not described above.

Attention is now directed to embodiments of user interfaces that optionally execute on portable multifunction device 100, for example.

FIG. 4A shows an exemplary user interface for a menu of applications on portable multifunction device 100, according to some embodiments. A similar user interface is optionally implemented on device 300 . In some embodiments, user interface 400 includes the following elements, or subsets or supersets thereof.
- signal strength indicator(s) 402 for wireless communication(s) such as cellular and Wi-Fi signals;
● Time 404,
- Bluetooth indicator 405,
- battery status indicator 406;
• a tray 408 containing icons for frequently used applications, such as;
o an icon 416 for the phone module 138 labeled "Phone", optionally including an indicator 414 of the number of missed calls or voicemail messages;
o an icon 418 for the email client module 140, labeled "Mail", optionally including an indicator 410 of the number of unread emails;
o icon 420 for browser module 147, labeled "Browser"; and o for video and music player module 152, also referred to as iPod (trademark of Apple Inc.) module 152, labeled "iPod". icon 422, and icons for other applications, such as:
o icon 424 for IM module 141, labeled "message";
o icon 426 for calendar module 148, labeled "Calendar";
o an icon 428 for the image management module 144, labeled "Photos";
o icon 430 for camera module 143, labeled "camera";
o icon 432 for online video module 155, labeled "online video";
o icon 434 for stock price widget 149-2, labeled "stock price";
o icon 436 for map module 154, labeled "Map";
o icon 438 for weather widget 149-1, labeled "Weather";
o icon 440 for alarm clock widget 149-4, labeled "Clock";
o icon 442 for training support module 142, labeled "Training Support";
o Icon 444 for notes module 153, labeled "Notes"; and o Settings application or module, labeled "Settings", that provides access to settings for device 100 and its various applications 136. icon 446 for.

Note that the icon labels shown in FIG. 4A are merely exemplary. For example, icon 422 for video and music player module 152 is labeled "music" or "music player." Other labels are optionally used for various application icons. In some embodiments, the label for each application icon includes the name of the application corresponding to each application icon. In some embodiments, the label of a particular application icon is different than the name of the application corresponding to the particular application icon.

FIG. 4B is an illustration on a device (eg, device 300 of FIG. 3) with a touch-sensitive surface 451 (eg, tablet or touchpad 355 of FIG. 3) separate from display 450 (eg, touchscreen display 112). a typical user interface. Device 300 may also include one or more contact intensity sensors (eg, one or more of sensors 359 ) for detecting the intensity of contact on touch-sensitive surface 451 and/or a tactile sensor for a user of device 300 . Optionally includes one or more tactile output generators 357 for generating output.

Although some of the examples below are described with reference to input on the touch screen display 112 (where the touch sensitive surface and display are combined), in some embodiments the device , detects input on a touch-sensitive surface separate from the display, as shown in FIG. 4B. In some embodiments, this touch-sensitive surface (eg, 451 in FIG. 4B) has a major axis (eg, 452 in FIG. 4B) that corresponds to a major axis (eg, 453 in FIG. 4B) on the display (eg, 450). have According to these embodiments, the device registers contact with touch-sensitive surface 451 (eg, 460 and 462 in FIG. 4B) at corresponding locations on the display (eg, 460 is 468 in FIG. 4B). , and 462 corresponds to 470). Thus, if the touch-sensitive surface is separate from the display, user input (e.g., contacts 460 and 462 and their movement) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B) ) is used by the device to operate the user interface on the multifunction device's display (eg, 450 in FIG. 4B). It should be appreciated that similar methods are optionally used for other user interfaces described herein.

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

FIG. 5A shows an exemplary personal electronic device 500. As shown in FIG. Device 500 includes body 502 . In some embodiments, device 500 can include some or all of the features described with respect to devices 100 and 300 (eg, FIGS. 1A-4B). In some embodiments, device 500 has a touch-sensitive display screen 504, hereinafter touch screen 504. FIG. Alternatively, or in addition to touchscreen 504, device 500 has a display and a touch-sensitive surface. As with device 100 and device 300, in some embodiments, touch screen 504 (or touch-sensitive surface) optionally includes a 1D sensor for detecting the intensity of contact (eg, touch) being applied. have one or more intensity sensors. One or more intensity sensors of touch screen 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 different intensity touches can invoke different user interface operations on device 500 .

Exemplary techniques for detecting and processing touch strength are described, for example, in related application "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application," filed May 8, 2013. International Patent Application No. PCT/US2013/040061 (published as International Publication No. WO 2013/169849) entitled "Device, Method, and Graphical User Interface for Transitioning Between Touch Input to PCT/US2013/069483 (published as International Publication No. WO 2014/105276) entitled "Display Output Relationships", each of which is hereby incorporated by reference in its entirety.

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, can, for example, attach device 500 to hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch bands, chains, pants, belts, shoes, purses, backpacks, etc. allow to install. These attachment mechanisms allow device 500 to be worn by a user.

FIG. 5B shows an exemplary personal electronic device 500. As shown in FIG. In some embodiments, device 500 can include some or all of the components described with respect to FIGS. Device 500 has a bus 512 operably coupling I/O section 514 to one or more computer processors 516 and memory 518 . The I/O section 514 can be connected to a display 504, which can have a touch sensing component 522 and, optionally, an intensity sensor 524 (eg, a contact intensity sensor). Additionally, the I/O section 514 includes a 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. can connect to Device 500 may include input mechanism 506 and/or input mechanism 508 . Input mechanism 506 is optionally, for example, a rotatable input device or a depressible and rotatable input device. Input mechanism 508 is optionally a button in some examples.

Input mechanism 508 is optionally, in some implementations, a microphone. Personal electronic device 500 optionally includes various sensors such as GPS sensor 532, accelerometer 534, orientation sensor 540 (eg, compass), gyroscope 536, motion sensor 538, and/or combinations thereof. , all of which are operably connectable to I/O section 514 .

Memory 518 of personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions, which are executed by one or more computer processors 516. Then, for example, a computer processor may be caused to perform the techniques described below, including processes 700, 900, 1100, and process 1300 (FIGS. 7, 9, 11, and 13). A computer-readable storage medium can be any medium capable of tangibly containing or storing computer-executable instructions for use by or in connection with an instruction-execution system, apparatus, or device. In some examples the storage medium is a temporary computer readable storage medium. In some examples the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media can 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 disks based on CD, DVD or Blu-ray technology, and persistent solid state memories such as flash, solid state drives. Personal electronic device 500 is not limited to the components and configuration of FIG. 5B, but may include other or additional components in multiple configurations.

As used herein, the term “affordance” refers to a user-interactive Refers to a graphical user interface object in the . For example, images (eg, icons), buttons and text (eg, hyperlinks) each optionally constitute affordances.

As used herein, the term "focus selector" refers to an input element that indicates the current portion of the user interface with which the user is interacting. In some implementations that include a cursor or other position marker, an input (eg, press input) is detected on a touch-sensitive surface (eg, touchpad 355 of FIG. 3 or touch-sensitive surface 451 of FIG. 4B) Sometimes, when the cursor is over a particular user interface element (e.g., button, window, slider, or other user interface element), the cursor acts as a "focus selector" and the particular user interface element is detected. adjusted according to the input. Some implementations include a touchscreen display (eg, touch-sensitive display system 112 in FIG. 1A or touchscreen 112 in FIG. 4A) that allows direct interaction with user interface elements on the touchscreen display. In an example, a touch detected on a touchscreen acts as a "focus selector" such that input (e.g., press input from touch) is directed to a specific user interface element (e.g., button, window, slider, or other user interface element), that particular user interface element is adjusted according to the detected input. In some implementations, without corresponding cursor movement or contact movement on the touch screen display (e.g., by using the tab or arrow keys to move focus from one button to another). Focus is moved from one area of the user interface to another area of the user interface, and in those implementations the focus selector moves according to the movement of focus between the different areas of the user interface. Regardless of the specific form taken by the focus selector, it is generally used to communicate the user's intended interaction with the user interface (e.g., the user interface with which the user intends to interact). A user interface element (or a touch on a touch screen display) that is controlled by the user (by presenting the element of the interface to the device). 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., cursor, touch or selection box) over the corresponding button is indicates that the user is activating the corresponding button (rather than other user interface elements shown on the display of the ).

As used herein and in the claims, the term "characteristic strength" of contact refers to a characteristic of contact based on one or more strengths of contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity may be a predefined number of intensity samples, or for a predefined event (e.g., after detecting contact, before detecting lift-off of the contact, before or after detecting the start of movement of the contact, before detecting the end of the contact, before or after detecting an increase in the intensity of contact, and/or before or after detecting a decrease in the intensity of contact) for a predetermined time period (e.g., 0.05, 0.1, optionally based on a set of intensity samples collected at 0.2, 0.5, 1, 2, 5, 10 seconds). The characteristic strength of contact is optionally a maximum strength of contact, a mean value of strength of contact, an average value of strength of contact, an average value of strength of contact, a top 10% value of strength of contact, a contact based on one or more of half the maximum strength of the contact, 90% of the maximum strength of contact, and so on. In some embodiments, the duration of contact is used to determine the characteristic strength (eg, when the characteristic strength is the average strength of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine if the action was performed by the user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, the first action is performed as a result of a contact having a characteristic strength that does not exceed the first threshold, and the contact having a characteristic strength that exceeds the first strength threshold and does not exceed the second strength threshold. A second action is performed as a result, and a third action is performed as a result of a contact having a characteristic strength exceeding a second threshold. In some embodiments, rather than the comparison between the characteristic strength and one or more thresholds being used to determine whether to perform the first action or the second action, It is used to determine whether to perform one or more actions (eg, to perform each action or to forgo each action).

FIG. 5C shows detection of multiple contacts 552A-552E on touch-sensitive display screen 504 by multiple intensity sensors 524A-524D. FIG. 5C additionally includes an intensity diagram showing current intensity measurements of intensity sensors 524A-524D in terms of intensity units. In this example, the intensity measurements of intensity sensors 524A and 524D are each 9 intensity units, and the intensity measurements of intensity sensors 524B and 524C are each 7 intensity units. In some implementations, the total intensity is the sum of intensity measurements of multiple intensity sensors 524A-524D, which in this example is 32 intensity units. In some embodiments, each contact is assigned a respective intensity that is a fraction of the total intensity. FIG. 5D shows the assignment of total strength to contacts 552A-552E based on the distance of contacts 552A-552E from center of force 554. FIG. In this example, contacts 552A, 552B, and 552E are each assigned a contact intensity of 8 intensity units of the total intensity, and contacts 552C and 552D are each assigned a contact intensity of 4 intensity units of the total intensity. is assigned an intensity of More generally, in some implementations, each contact j is assigned a respective intensity Ij, which is a fraction of the total intensity A, according to a predetermined mathematical function Ij=A·(Dj/ΣDi); where Dj is the distance from the center of force to each contact j, and ΣDi is the sum of the distances from the center of force to all respective contacts (eg, from i=1 to the last). The operations described with reference to FIGS. 5C-5D may be performed using an electronic device similar or identical to device 100, 300 or 500. FIG. In some embodiments, the characteristic strength of contact is based on one or more strengths of contact. In some embodiments, an intensity sensor is used to determine a single characteristic strength (eg, a single characteristic strength of a single contact). Note that intensity maps are not part of the displayed user interface, but are included in FIGS. 5C-5D for the benefit of the reader.

In some embodiments, a portion of the gesture is identified for purposes of determining characteristic strength. For example, the touch-sensitive surface optionally receives successive swipe contacts transitioning from a starting position to an ending position with increasing strength of the contact. In this example, the characteristic strength of the contact at the end location is optionally based on only a portion of that swipe contact (eg, only the portion of the swipe contact at the end location) rather than the entire continuous swipe contact. In some embodiments, a smoothing algorithm is optionally applied to the strength of the swipe contact prior to determining the characteristic strength of the contact. For example, the smoothing algorithms optionally include one or more of an unweighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some situations, those smoothing algorithms remove small increases or decreases in the strength of swipe contacts for the purpose of determining characteristic strength.

The intensity of contact on the touch-sensitive surface is optionally scaled to one or more intensity thresholds, such as a touch detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. characterize against. In some embodiments, the light pressure intensity threshold corresponds to the intensity with which the device performs operations commonly associated with clicking a physical mouse button or trackpad. In some embodiments, the deep press intensity threshold corresponds to the intensity at which the device performs operations that differ from those typically associated with clicking a physical mouse button or trackpad. In some embodiments, if touch is detected with a characteristic intensity below a light pressure intensity threshold (e.g., and above a slight touch detection intensity threshold below which touch is no longer detected), the device detects a light pressure. A focus selector is moved according to movement of the contact on the touch-sensitive surface without performing actions associated with the pressure intensity threshold or the deep pressure intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent across different sets of user interface diagrams.

Increasing the characteristic intensity of a contact from an intensity below the light pressure intensity threshold to an intensity between the light pressure intensity threshold and the deep pressure intensity threshold may be referred to as a "light pressure" input. Increasing the characteristic strength of a contact from an intensity below the deep pressure threshold to an intensity above the deep pressure threshold is sometimes referred to as a "deep pressure" input. Increasing the characteristic strength of a touch from an intensity below the touch detection intensity threshold to an intensity between the touch detection intensity threshold and the light pressure intensity threshold may be referred to as detecting contact on the touch surface. A decrease in the characteristic strength of a contact from a strength above the contact detection strength threshold to a strength below the contact detection strength threshold may be referred to as detecting lift-off of the contact from the touch surface. In some embodiments, the contact detection strength threshold is zero. In some embodiments, the contact detection strength threshold is greater than zero.

In some embodiments described herein, one or more operations are performed in response to detecting a gesture comprising a respective press input or on a respective contact (or multiple contacts). and each pressure input is based, at least in part, on detecting an increase in the intensity of the contact (or contacts) above a pressure input intensity threshold. detected. In some embodiments, the respective action is performed in response to detecting an increase in the strength of the respective contact (eg, a "downstroke" of the respective pressure input) above a pressure input strength threshold. In some embodiments, the pressure input includes increasing the strength of each contact above the pressure input strength threshold and subsequently decreasing the strength of the contact below the pressure input strength threshold, wherein each action is Execution is performed in response to detection of a decrease in the strength of the respective touch below the input threshold (eg, an "upstroke" of the respective pressure input).

FIGS. 5E-5H illustrate the intensity of contact 562, ranging from an intensity below the light pressure intensity threshold (eg, “IT _L ”) in FIG. 5E to an intensity above the deep pressure intensity threshold (eg, “IT _D ”) in FIG. 5H. Fig. 4 shows detection of gestures including press inputs corresponding to increasing strength; A gesture made by contact 562 is detected on touch-sensitive surface 560 . At that time, on the displayed user interface 570 including the application icons 572A-572D displayed in the predetermined area 574, a cursor 576 is displayed on the application icon 572B corresponding to the application 2. FIG. In some embodiments, gestures are detected on touch-sensitive display 504 . The intensity sensor detects the intensity of contact on touch-sensitive surface 560 . The device determines that the intensity of contact 562 has peaked above a deep pressure intensity threshold (eg, “IT _D ”). Contact 562 is maintained on touch sensitive surface 560 . In response to detecting the gesture, and in response to contact 562 having an intensity above a deep pressure intensity threshold (eg, "IT _D ") during the gesture, a recently opened for app 2, as shown in FIGS. 5F-5H. display reduced representations 578A-578C (eg, thumbnails) of the document. In some embodiments, the intensity compared to one or more intensity thresholds is the characteristic intensity of the contact. Note that the intensity diagram of contact 562 is not part of the displayed user interface, but is included in FIGS. 5E-5H for the benefit of the reader.

In some embodiments, the display of representations 578A-578C includes animation. For example, representation 578A is initially displayed near application icon 572B, as shown in FIG. 5F. As the animation progresses, representation 578A moves upward and representation 578B appears near application icon 572B, as shown in FIG. 5G. Representation 578A then moves upward, representation 578B moves upward toward representation 578A, and representation 578C is displayed near application icon 572B, as shown in FIG. 5H. Representations 578A-578C form an array above icon 572B. In some embodiments, the animation progresses according to the intensity of contact 562, as shown in FIGS. As it increases toward, representations 578A-578C appear and move upward. In some embodiments, the strength on which the animation progression is based is the characteristic strength of the contact. The operations described with reference to FIGS. 5E-5H may be performed using an electronic device similar or identical to device 100, 300 or 500. FIG.

In some embodiments, the device employs intensity hysteresis to avoid unintended inputs, sometimes referred to as "jitter," wherein the device has a hysteresis intensity that has a predefined relationship to the pressure input intensity threshold. Define or select a threshold (e.g., the hysteresis intensity threshold is X intensity units below the pressure input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable ratio of the pressure input intensity threshold ). Thus, in some embodiments, the pressure input includes a corresponding increase in strength of the contact above the pressure input strength threshold followed by a subsequent decrease in strength of the contact below the hysteresis strength threshold corresponding to the pressure input strength threshold. , a corresponding action is performed in response to detecting a subsequent decrease in the intensity of the corresponding touch below its hysteresis intensity threshold (eg, an “upstroke” of the corresponding pressure input). Similarly, in some embodiments, a pressure input causes the device to increase the intensity of the contact from an intensity below the hysteresis intensity threshold to an intensity above the pressure input intensity threshold, and optionally an intensity below the hysteresis intensity. is detected only if it detects a decrease in the strength of subsequent contact with the is executed according to

For ease of discussion, descriptions of actions performed in response to a pressure input associated with a pressure input strength threshold, or in response to gestures involving that pressure input, are for contact strengths above the pressure input strength threshold. increasing, increasing the intensity of the contact from an intensity below the hysteresis intensity threshold to an intensity above the pressing input intensity threshold, decreasing the intensity of the contact below the pressing input intensity threshold, and/or increasing the hysteresis intensity threshold corresponding to the pressing input intensity threshold. Optionally triggered in response to detecting any decrease in the strength of the contact below. Additionally, in embodiments described as performing an action in response to detecting a decrease in the strength of the contact below the pressure input strength threshold, the action corresponds to and is less than the pressure input strength threshold. is optionally performed in response to detecting a decrease in the strength of the touch below a low hysteresis strength threshold.

As used herein, an "installed application" is one that has been downloaded to an electronic device (eg, device 100, 300, and/or 500) and launched on that device (eg, refers to a software application that is ready In some embodiments, the downloaded application becomes an installed application by means of an installation program that extracts program portions from the downloaded package and integrates the extracted portions with the operating system of the computer system.

As used herein, the term "open application" or "running application" refers to the state information maintained (e.g., as part of device/global internal state 157 and/or application internal state 192). Refers to a software application that is The open or running application is optionally one of the following types of applications.
● the active application currently displayed on the display screen of the device in which the application is being used,
A background application (or background process) that is not currently visible, but one or more processes for that application are being served by one or more processors; , volatile and non-volatile) that can be used to resume execution of that application.

As used herein, the term "closed application" refers to a software application for which state information is not maintained (e.g., state information about the closed application is not stored in the device's memory). Closing an application therefore includes stopping and/or removing the application processes associated with the application, and removing state information associated with the application from the device's memory. Generally, opening a second application during a first application does not close the first application. When the second application is displayed and the first application stops being displayed, the first application becomes the background application.

Attention is now directed to embodiments of user interfaces (“UIs”) and related processes implemented on an electronic device such as portable multifunction device 100 , device 300 or device 500 .
User Interface and Associated Processes Usage Metrics Dashboard User Interface

Users interact with electronic devices in many different ways, including viewing information about the electronic device and/or use of the electronic device. In some embodiments, the electronic device displays a visual indication of one or more metrics associated with activity on the electronic device, thereby allowing the user to view information regarding use of the electronic device. do. Embodiments described below provide methods for an electronic device to present an indication of usage metrics associated with use of the electronic device to perform one or more actions. Reducing the amount of time a user needs to perform an action by enhancing interaction with the device, thus reducing the device's power usage and increasing battery life for battery-powered devices do. It is understood that people use devices. When a person uses a device, that person is optionally called the user of that device.

FIGS. 6A-6UU illustrate exemplary methods for an electronic device to present usage metric indications, according to some embodiments of the present disclosure. The embodiments in these figures are used to illustrate the processes described below, including the processes described with reference to Figures 7A-7S.

FIG. 6A shows an exemplary device 500 having a touch screen 504 as described with reference to FIGS. 5A-5H. Touch screen 504 optionally displays one or more user interfaces including various content. In the example shown in FIG. 6A, touch screen 504 displays a limit setting user interface for viewing information and setting limits for use of electronic device 500 . In FIG. 6A, the limit settings user interface includes an indication 602 of device usage, as well as settings for restricted usage modes (eg, "device idle time" 604a), usage limits for one or more applications or categories of applications. (e.g., "app limits" 604b), settings where the feature is always allowed regardless of any usage restrictions currently in place (e.g., "always allow" 604c), settings for content and privacy settings of electronic device 500 (e.g. , “Content and Privacy” 604d), settings related to requiring a password to change usage settings (e.g., “Require password to change” 604e), which actions are being performed on the electronic device. settings to stop recording usage data (e.g., "stop recording usage data" 604f), settings to delete stored data about the use of the electronic device to perform various actions (e.g., 604g), and settings for signing into cloud-based user accounts (eg, "Sign in to iCloud" 604h). As shown, the device usage indication 602 is the amount of time that the electronic device has been used to access each of several applications or application categories (e.g., the News app, the Games category, and the Mail app). including a visual indication of Indication 602 further includes an indication of how much of the total "screentime" usage limit remains (eg, "3 hours left"). Usage limits, including overall usage limits, are described in more detail below with reference to FIGS. 8A-9K. Electronic device 500 also displays an indication of total device usage (eg, “4 hours of usage”) and a comparison of daily device usage to average daily usage (eg, “30 minutes below average”).

FIG. 6B shows the restriction settings user interface when electronic device 500 signs into a cloud-based user account. The Restrictions Settings user interface provides an indication 606 of the nickname of the electronic device 500 associated with the user account and indications of devices associated with other users who are part of a group or family cloud-based account (e.g., John Jr.'s iPhone 608a and Jane's iPhone 608b). The family's cloud-based account includes multiple individual user accounts (eg, "John Jr.'s iPhone" and "Jane's iPhone") associated with other electronic devices. In some embodiments, a family's cloud-based account includes a "parent" user and a "child" user, with the parent user viewing and/or controlling various statistics and/or settings associated with the child user. be able to. As shown here and described in more detail below with reference to FIGS. 6V-W, a parent device (eg, electronic device 500) presents usage information regarding one or more child devices. be able to. Parent devices can also control usage limits and device idle time settings for child devices, as described below with reference to FIGS. 8A-11I. 6C-6D, the user scrolls through the restrictions settings user interface (e.g., by contact 603) to an indication of multiple other electronic devices associated with the cloud-based user account (e.g., John's iPad 610a). , Apple TV 610b, and John's Apple Watch 610c), "Stop recording usage data" setting 604f, and "Delete usage data" setting 604g. Other devices listed in the “My Devices” list are associated with the same user account associated with electronic device 500 . As described below with reference to FIGS. 6TT-6UU, the electronic device 500 can separately or together display usage metrics associated with one or more of the associated devices. .

FIG. 6E shows a widget user interface including a usage widget 612a, a calendar widget 612b, and a weather widget 612c. Usage widget 612a includes device usage indications 602, including usage indications for various applications and categories (eg, news app, mail app, and games category), and affordances selectable to display further usage information. 614 included.

FIG. 6F shows the user selecting affordance 614 (eg, by contact 603). In response to selecting affordance 614, usage widget 612a expands to display additional information, as shown in FIG. 6G. Expanded usage widget 612a provides an indication 616 of total daily device usage, an indication 618 of how much daily device usage deviates from average daily device usage, and device usage by application or application category over time. and an indication of usage limit settings on the electronic device (eg, news app limit 622a and games category limit 622b). Graph 620 shows device usage over time with color-coded segments indicating which application (e.g., News app or Mail app) or application category (e.g., Games category) was used during that time period. Contains a bar for each hour of the day. As shown in FIG. 6G, the usage limit exceeded indication (eg, news application usage limit 622a) includes an indication of how much the application (eg, news application) has been used beyond the usage limit. Similarly, a usage limit not reached indication (eg, games category 622b) includes a usage difference and usage limit indication for that application category (eg, games category). Figures 6H-6I show a user scrolling through the expanded usage widget to see a representation of daily application usage 624a-624e, an indication 626 of the average number of notifications received each day for the past few days, and how much Frequently, the user shows additional information (eg, by contact 603) including an indication 628 of whether the user has initiated "picking up" of the device over the past day or days. As shown, application usage indications 624a-624e are application icons for those applications presented in different sizes to indicate the relative amount of usage of each application. For example, the news application indication 624a is the largest, indicating that this application was used the most. Similarly, the Mail application indication 624b and the Game A application indication 624c are less than the News application indication 624a, according to the amount of usage of these applications.

FIG. 6J shows usage notification 630 generated by device 500, according to some embodiments of the present disclosure. In some embodiments, usage notifications such as notification 630 are generated by electronic device 500 at regularly scheduled intervals (eg, once per day, once per week, etc.). Usage notifications include an indication of device usage 602, an option to view more information about device usage (eg, in a dashboard user interface) (eg, "View" 632a), and dismiss notification without viewing more information about device usage. option (eg, “Reject” 632b). In FIG. 6K, the user selects "view" 632a (eg, by contact 603) to see more information about device usage. In response, electronic device 500 presents a usage dashboard user interface, as shown in FIG. 6L.

The usage dashboard user interface includes a graph 620 showing device usage by application or application category over time as described above with reference to FIG. an indication 636 of the amount of device usage during a moderated usage mode (eg, “device idle time”), and an indication 622a and 622b of usage limits set for applications and categories. The usage dashboard user interface further includes toggle switches for viewing usage metric indications for a day 638a or a week 638b. As shown in FIG. 6L, the usage dashboard user interface currently displays usage metrics for the current day. Application usage indications 622a and 622b with usage limits optionally view information about the respective application or category and display a settings user interface for updating usage limit settings for that application or category. are visually associated with selectable affordances 640a and 640b. For example, affordance 640a can be selected to edit usage limit settings for a news application. As shown in FIG. 6L, when the usage limit is exceeded (eg, News app usage limit 622a), the corresponding affordance 640a has a different color or pattern indicating that the usage limit has been exceeded. Similarly, in some embodiments, the associated affordance has visual properties when the usage limit is near reaching (eg, within a threshold amount of time or percentage of time). In addition, the bar chart showing the usage limit has differently colored portions corresponding to the amount of time the electronic device was used to access a given application or category within the usage limit (e.g., a news app indicator). the amount of time a given application or category has been used beyond its usage limit (as shown in both the indication 622a for the News app and the indication 622b for the Games category); and the amount of time remaining in the usage limit for the application or category (as shown in the game category indication 622b).

FIGS. 6M-6N illustrate that the user scrolls through the usage dashboard user interface (eg, by contact 603) to reveal indications of additional usage metrics, as shown in FIG. 6O. As shown, the usage dashboard user interface provides usage indications 642 for applications that do not have usage limits set (e.g., email), and information about the corresponding applications to set usage limits for that application. Includes affordance 640c selectable to display a settings user interface for updating.

Figures 6P-6Q illustrate that the user scrolls through the usage dashboard user interface (eg, by contact 603) to reveal indications of additional usage metrics, as shown in Figure 6R. FIG. 6R shows a graph 644 of notifications received during the day, an indication 646 of the number of notifications received during the day, an indication 648 of the time when most notifications were received, and various notifications installed on electronic devices. usage dashboard user interface including an indication 650a-650d of how many notifications have been generated by different applications (e.g., all applications that generated notifications today, or the top set number of applications that generated notifications today) . Graph 644 includes multiple bars that indicate how many notifications the electronic device presented during each hour of the day. The user interface further includes a plurality of affordances 652a-652d visually associated with the indications 650a-650d to display notification settings for the corresponding application for which the notification indication is being displayed. can be selected to For example, affordance 652a can be selected to edit notification settings for the iMessage app. Notification indications 650a-650d include the name of the application (eg, "iMessage app," "email app," "news app," and "water tracker app"), how many notifications by each application during the day. generated, and dots positioned to indicate the relative number of notifications generated by that application with respect to other applications.

Figures 6S-6T illustrate that the user scrolls through the usage dashboard user interface (eg, by contact 603) to reveal indications of additional usage metrics, as shown in Figure 6U.

FIG. 6U shows an indication 654 of device “picks” per day (as described in more detail below), an indication 656 of average time between device pickups per day, and a graph 658 of device pickups per day. , an indication 660 of the number of device pickups during the device downtime (device downtime is described in more detail below with reference to FIGS. 10A-11I), the time of day with the maximum device pickups and the 6 shows a usage dashboard user interface including an indication 662 of the number of pickups within the time interval, and an indication 664a and 664b of the number of times the user picked up the electronic device to interact with each of a plurality of applications.

The average time between device pick-ups in a day indicated by indication 656 is calculated as the average time between the first pick-up of the day and the last pick-up of the day. In some embodiments, this average includes the pickups between the first pickup outside the device downtime and the last pickup outside the device downtime. In some embodiments, the average includes pickups between all pickups for a day, regardless of whether one or more of those pickups occurred during device idle time.

A graph of device pickups during the day 658 includes a bar for each hour of the day showing the number of device pickups within each hour. As shown in FIG. 6U, the graph visually distinguishes pickups that occur during device downtime from pickups that occur outside of device downtime, and further illustrates this distinction with device downtime glyph 698-22.

The application with which the user picks up the electronic device to interact with 664a-b is determined based on the first application the user interacts with when picking up the device. For example, if a user launches a device and immediately closes a first application that was presented to the electronic device at launch, then opens a second application to perform an action in the second application, the second application may: An application in which a user picks up and interacts with an electronic device. As another example, if a notification associated with the first device is presented while the device is in sleep mode, and the user provides input to view the notification and interact with the first application, the first is an application with which a user picks up and interacts with an electronic device.

As used herein, device "pickup" refers to many types of user-focused events such as the user unlocking the electronic device, activating the device, and other actions that initiate operation of the electronic device. encompasses In some embodiments, user input to the electronic device is in an idle state (e.g., no user interaction with the electronic device and/or the display of the electronic device is off, sleep mode, locked state, low power mode, etc.). , a user attention event is detected. In some embodiments, the electronic device enters the idle state in response to a predetermined amount of time having elapsed since the last user input was received at the electronic device. Optionally, the electronic device enters the idle state in response to user input (eg, pressing a power or lock button on the electronic device) corresponding to a request to enter the idle state. In some embodiments, the display does not show images while in the idle state. In some embodiments, a lock screen is displayed on the electronic device while it is idle. The user input corresponding to the user attention event is optionally a button press on the electronic device, a user action to exit an idle state (e.g. picking up the device), an unlock input (e.g. a passcode or provide a biometric) and electronic device functionality (e.g. widget user interface, camera application, dashboard user interface, application user interface associated with the displayed notification indication) one or more of the touch inputs to access the Detecting the biometric optionally includes detecting the user's face with a depth camera or another sensor. In some embodiments, the electronic device uses depth cameras and facial recognition technology to determine when a user looks at the user's electronic device and unlocks the electronic device in response to the user looking at the electronic device. (eg, the electronic device unlocks in response to a determination that the user is eyeing the electronic device). In some embodiments, the electronic device exits the idle state and pays attention in response to a notification (e.g., the display turns on to show the notification without user input requiring the display to turn on). The event causes the device to perform some other action (eg, unlock the device, update the display to show an application or operating system user interface). That is, the indication of notification is optionally not a user attention event even if it causes the device to exit the idle state. In some embodiments, the event of interest metric indicates the number of times a user initiates use of the electronic device (eg, "checks" the user's phone).

FIG. 6V shows the limit settings user interface. As shown, the restriction settings user interface includes an indication 608a (“John Jr.'s iPhone”) of the electronic device associated with the user that is part of the family account with which the electronic device 500 is associated. Indications are according to John Jr. iPhone has requested more time to be added to at least one usage limit controlled by electronic device 500 . In FIG. 6V, the user selects indication 608a (eg, by contact 603).

Depending on the user's selection, as shown in FIG. 6W, the electronic device may be a John Jr. display a usage dashboard user interface associated with the iPhone of The user interface, similar to that described above in FIGS. 6L-6N, is designed by John Jr. Indication of request 666 to remove global usage limit implemented on iPhone of John Jr. Indication of device usage 666; Total Screen Time Usage Limit Indication 680 for iPhone, John Jr.; iPhone longest usage session duration indication 670, John Jr. usage indications 672 during device idle time on the iPhone of John Jr.; and indications 674a-b of usage limits on the iPhone of John Jr. includes an indication 676 of application usage for which the iPhone usage limit has not been set.

Indication 666 is presented in response to electronic device 500 receiving a request from another electronic device (e.g., John Jr.'s iPhone) to increase the amount of usage limit time in effect on the other electronic device. be done. As described above with reference to FIG. 6B, electronic device 500 and John Jr. iPhone, optionally electronic device 500 is the iPhone of John Jr. is associated with a family account that can manage usage settings for the iPhone of the family member. Indication 666 may "reject" the request, "give 1 hour" additional time, or tell John Jr. includes a selectable affordance to "go to settings" to see more options to change the restrictions set on your iPhone. Further details regarding requests from the child device to the parent device to add more time to the usage limit, and usage limits in general, are described below with reference to FIGS. 9A-10AAA.

The usage dashboard user interface further includes a plurality of affordances 678a-c selectable to view information about associated applications or categories of applications and/or to change usage limits associated with applications or categories of applications. . As shown in the user interface, the affordance 678a associated with the Game A app is shaded to indicate that the usage limit for the Game A app has been reached. Similarly, the affordance 678a associated with the social media category is shaded to indicate that the usage limit for the social media category is being reached. Other visual indications are possible in some embodiments.

FIG. 6X shows the limit settings user interface. In FIG. 6Y, the user selects setting 604e (eg, via contact 603) that requires a password (or other authentication such as a passcode or biometric) to change usage restriction settings on device 500. In FIG. Upon selection, the electronic device presents a keypad 682 for accepting user input to set a password. In some embodiments, the electronic device allows the user to select an option to use password or passcode length or biometric input (e.g., facial recognition) for authentication to change usage settings. Present a full keyboard or user interface. The authorization required to change one or more usage restriction settings of electronic device 500 is optionally different than the authorization required to unlock electronic device 500 .

After the user sets the password, the electronic device updates the password toggle switch 604e to indicate that a password is required to change the usage restriction setting, as shown in FIG. 6AA. 6BB, the user selects indication 604b to change the usage limits set on electronic device 500. In FIG. Upon input, the electronic device presents a keypad 682 that requires the password (or other authentication method) described above before allowing the user to change settings, as shown in FIG. 6CC.

FIG. 6DD shows that the user has selected the device use indication 602 (eg, by contact 603). Upon selection, electronic device 500 presents a usage dashboard user interface, as shown in FIG. 6EE. As shown in FIG. 6FF, the user then selects toggle switch 638b (eg, via contact 603) to view usage metrics over a week. In response to the input, the electronic device 500 updates the usage dashboard user interface to display usage metric indications over the past week, as shown in FIG. 6GG.

FIG. 6GG shows a usage dashboard user interface presenting multiple usage metrics over the past week. The usage dashboard user interface provides an indication 684 of average device usage per day over the week, daily usage for each day during the week compared to average usage over a longer period of time (e.g., last month or so far) a graph 688 showing daily usage of one or more applications or categories of applications; an indication 690 of the duration of the longest usage session over the course of a week; Includes an indication 692 of daily device usage and an indication 694a-694b of average usage of one or more applications or categories of applications with usage limits set for each day during the week. Graph 688 includes a bar for each day of the week showing usage of electronic device 500 for each day for a number of color-coded applications or application categories. As shown, graph 688 provides an indication of the overall device usage limit (e.g., graph 688) that optionally differs for a week (e.g., Monday through Friday) and weekends (e.g., Saturday and Sunday). horizontal line extending across). For example, as shown in FIG. 6GG, the overall device usage limit for Monday through Friday is optionally lower than the overall device usage limit for Saturday and Sunday.

Although not shown in the figure, the dashboard user interface optionally displays some metrics in aggregations over a week (e.g., totals, averages, etc.) and other metrics in weekly maximums or It should be understood to include indications of any other metric described herein over a period of one week, displayed as a minimum. For example, returning to FIG. 6R, the number of notifications per day 646 is optionally replaced by the average number of notifications for each day over the course of the week, and the interval 648 with the most notifications received during a given day. is replaced by the interval (eg, a day or an hour of a day) that received the most notifications during the week. As another example, returning to FIG. 6U, the number of device pickups during the daily downtime 660 is optionally replaced with the average number of device pickups during the device downtime per day over a week. , the time of maximum pickup per day 662 is optionally replaced with a different interval during the week that received the most notifications (eg, a day or an hour of the day).

FIG. 6HH shows the user selecting affordance 640b associated with the games category (eg, by contact 603). In response to the input, electronic device 500 presents a category setting user interface, as shown in FIG. 6II. The category settings user interface includes a toggle switch 690 for enforcing or not enforcing usage limits for the category of applications, an indication 692 of usage limits for the category of applications, an option to enforce limits with notification and block settings 694a, notification settings. a toggle switch 696 for presenting a verbal warning associated with the usage limit, and a plurality of indications 698a of usage of each application included in the category of applications that apply the usage limit. including ~d.

A toggle switch 690 allows the user to stop enforcing category usage limits while preserving usage limit parameters such as amount of time, notification style, and applications included. In this way, the user can toggle the toggle switch back on and begin enforcing the usage limit again without having to enter the usage limit parameters again. Other details of notification and block 694a settings and notification 694b settings, and usage limit settings are described below with reference to FIGS. 8A-9K. A toggle switch 696 for presenting a verbal warning associated with the usage limit enables the electronic device 500 to speak a notification associated with the usage limit, such as a notification indicating that the usage limit is near or reached. enable

As shown in FIG. 6II, the user selects affordance 640a associated with the Game A application within the Games category (eg, via contact 603) to present additional information and settings for this particular application. In response, electronic device 500 presents a user interface with information regarding the use of game A and settings for setting usage limits for game A, as shown in FIG. 6JJ.

FIG. 6JJ shows Game A usage indication 698-2, Game A average usage indication 698-4, Game A usage indication 698-6 during device idle time of the day, an indication 698-8 of the number of notifications generated by game A during the day, a setting to update the usage limit for game A 689-10, information about game A 698-12, and Shows a usage graph 698-14 (eg, displayed as multiple bars, each representing usage of Game A within each hour of the day). As shown, the user can create a usage limit for Game A, including setting the amount of time the usage limit is and how the electronic device 500 will behave once the limit is reached. . Usage limits are described in more detail with reference to FIGS. 8A-9K. The user interface further includes a summary of information 698-12 about Game A, such as its application icon, age rating, category, developer, and a link to view Game A in the app store on the electronic device. Although the user interface shown in FIG. 6JJ is accessible from the category settings user interface shown in FIGS. , 640a associated with the News app, 678c associated with the Dictionary app, etc.) displays a usage metrics dashboard user interface (eg, shown in FIGS. 6L-6O, 6W, and 6EE-6HH). ) can be accessed from

FIG. 6KK shows a usage dashboard user interface presenting usage metrics for notifications such as those described with reference to FIG. 6R. FIG. 6LL shows the user selecting affordance 652c (eg, by contact 603) associated with news app notification settings. In response, electronic device 500 presents a notification settings user interface for the News app, as shown in FIG. 6MM. The notification settings user interface provides a toggle switch 698-16 for allowing notifications from the News app, a toggle switch 698-18 for presenting notifications about the News app in silent mode, and an indication of what type of notification the News app has. Contains options 698-20 to change what the app presents. one or more indications of the notification when the notification is received on the electronic device when the notification is "on" (e.g., visual indications such as text or images; audio indications such as sounds or spoken phrases; and/or providing tactile or other tactile feedback) by toggling off the "Allow Notifications" toggle switch 698-16 to allow applications to receive notifications anywhere on the electronic device 500. Do not present. Toggling the "silent notification" toggle switch 698-18 on presents an indication of the notification when the notification is received on the electronic device 500, as exemplified below with reference to FIG. 12I ( Indication of multiple notifications received on an electronic device (e.g., as an electronic device does when notifications are allowed), but unlike the behavior of the device when notifications are not allowed Presents an indication of the notification within the notification history user interface, including the . Modifying the "allowed notifications" setting 698-20 causes the electronic device 500 to present all notifications received by the application, a limited number of notifications, or only very important notifications.

FIG. 6NN shows the usage dashboard user interface described above. FIG. 6OO shows the usage dashboard user interface after the user has used the instant messaging application for 15 minutes. In response to application usage, electronic device 500 updates the user interface to display instant messaging application usage over time in device usage graph 620 by application or application category. An indication 616 of total device usage and an indication 618 of electronic device usage compared to average usage are also updated.

FIG. 6PP shows the usage dashboard user interface after the user has used the instant messaging application for another 15 minutes, bringing the total usage of the instant messaging application to 30 minutes. In response to the additional usage, electronic device 500 associates the instant messaging application and email application with the messaging category (eg, according to a determination that the total usage of applications within the messaging category meets the category usage threshold). Once the Mail app and IM app are combined with the Messaging category, graph 620 is updated to show the use of one of the multiple applications (e.g., Mail app or IM app) within the Messaging category associated with the Messaging category. including different colors or patterns. In some embodiments, applications are bound to a category when the combined usage of those applications meets or exceeds a predetermined category usage threshold.

In FIG. 6QQ, the dashboard user interface is updated again after the user uses electronic device 500 to use the instant messaging application for another 30 minutes, bringing the total application usage to 60 minutes. Upon additional usage, the electronic device 500 segregates the instant messaging application and the email application (eg, according to a determination that instant messaging application usage meets an application usage threshold). That is, the graph 620 is updated to include distinct colors or patterns that separately indicate usage of the IM and Mail apps, as opposed to tying them into messaging categories. In some embodiments, applications are isolated when the usage of individual applications within the combined category meets or exceeds a predetermined application usage threshold.

In some embodiments, device 500 supports a given application within uses for a given application (or category) without including only application uses within uses for the given application (or category). Also includes use of web resources (eg, web pages). For example, FIG. 6RR shows the usage dashboard user interface after the user has accessed the website associated with the instant messaging application for 30 minutes. As shown, by accessing a website associated with the instant messaging application, electronic device 500 in turn indicates that the instant messaging application has been used for a total of 1.5 hours. aggregate towards. This number includes 1 hour of native instant messaging application usage and 30 minutes of web browsing application access to the instant messaging application's associated website. In this way, total usage is optionally tracked beyond just native application usage.

FIG. 6SS shows that the user has selected the "Apple TV" indication 610b (eg, by contact 603) within the restrictions settings user interface. Upon selection, the electronic device presents a usage dashboard user interface including usage metrics associated with Apple TV, as shown in FIG. 6TT. In this way, the user can focus on other uses of their device. The usage dashboard user interface of FIG. 6TT includes an indication 616 of daily device usage, an indication 618 of daily usage compared to average usage, and graphs of device usage for applications and application categories during the day. 620, an indication 634 of the duration of the longest usage session, an indication 636 of device usage during idle time, and an indication 622a-622b of usage of capped applications and categories of applications. In some embodiments, electronic device 500 optionally displays additional usage metrics associated with other electronic devices, such as notifications and device pickups as described herein. The metrics presented within the usage dashboard user interface shown in FIG. 6TT are similar to similar usage metrics described above with reference to FIG. 6L.

FIG. 6UU illustrates a usage dashboard user interface that includes aggregate usage metrics for multiple electronic devices associated with a user account (eg, all of John's devices, including Apple TV and John's iPhone). In this way, the user can view the user's usage across multiple (eg, all) of the user's devices. The usage dashboard user interface of FIG. 6UU includes an indication 616 of the combined usage of multiple electronic devices for a day, an indication 618 of how the usage of the day compares to the average usage, applications and applications throughout the day. A graph 620 of the combined usage of devices in the category, an indication 634 of the duration of the longest usage session across all devices, an indication 636 of total usage of all devices during downtime, and applications with usage limits. and indications 622a-622c of the use of categories of applications. In some embodiments, electronic device 500 optionally displays additional usage metrics associated with multiple electronic devices, such as notifications and device pickups as described herein. The metrics presented within the usage dashboard user interface shown in FIG. 6UU are similar to similar usage metrics described above with reference to FIG. 6L.

7A-7S are flow diagrams illustrating a method 700 of presenting usage metric indications, according to some embodiments of the present disclosure. Method 700 optionally includes device 100, device 300, or device 500 as described above with reference to FIGS. 1A-1B, 2-3, 4A-4B, and 5A-5H. run on electronic devices such as Some acts of method 700 are optionally combined and/or the order of some acts is optionally changed.

As will be described below, the method 700 provides a way of presenting an indication of one or more usage metrics associated with the electronic device 500 . This method reduces the cognitive burden on the user when interacting with the user interface of the device of the present disclosure, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, improving the efficiency of user interaction with the user interface conserves power and increases intervals between battery recharges.

In some embodiments, an electronic device (e.g., electronic device 500) that communicates with a display and one or more input devices (e.g., a mobile device that includes a touch screen, keyboard, mouse, trackpad, and touch screen). A computer, including one or more, or a set-top box that communicates with a television and an input device (e.g., a remote controller), on a display, such as a dashboard user interface of usage metrics shown in FIGS. 6L-6U. (e.g., a metric showing how much of the first usage limit has been used, such as a percentage bar, pie chart, etc.), and a second usage metric (e.g., a second Display 702 a dashboard user interface (eg, a digital health dashboard) that includes a visual indication of how much of the usage limit has been used). The first usage metric optionally includes a first activity of the electronic device (e.g., screen time, time using a particular application or a particular category of applications, receiving notifications, such as FIG. 6L). , events of interest, etc.) is associated 704 . As an example, the first metric is optionally an indication of the amount of "screen time" the device has been used by the user during the current day. In some embodiments, the first usage metric visual indication is the first usage metric for a first predetermined time period (eg, one hour, one day, or one week), such as FIG. 6L. A first quantification (eg, amount of time or number of times) of use of the electronic device to perform the action is included (706). The visual indication of the metric of first use optionally includes a visual diagram such as a graph or chart. In some embodiments, the first usage metric visual indication is a displayed number (eg, “three hours of screen time”) indicating the usage metric. The second usage metric optionally uses a second activity of the electronic device that differs from the first activity (e.g., screen time, a particular application, or a particular category of application, such as FIG. 6L time, receiving notifications, events of interest, etc.) (708). As an example, the second usage metric is optionally an indication of the amount of time a user spends using the electronic device to interact with a particular application. In some embodiments, the visual indication of the second usage metric is the second usage metric for a second predetermined time period (eg, 1 hour, 1 day, or 1 week), such as FIG. 6L. A second quantification of the use of the electronic device to perform the action (eg, amount of time or number of times) is included (710). In some embodiments, the second usage metric is a different activity, a different type of activity, a different quantification of usage, and/or a different duration (in some embodiments , same time period), and in some embodiments is associated with the same time period as the first usage metric. For example, the visual indication of how much time a user has spent using the electronic device to interact with a particular application is optionally broken down by application and/or application category that includes the particular application. Includes a graph showing total screen time for device usage.

In some embodiments, while displaying the visual indication of the first metric of usage and the visual indication of the second metric of usage within the dashboard user interface, the electronic device Through the above input device, a third usage metric different from the first usage metric and the second usage metric, such as FIGS. One usage metric and/or a second usage metric may be associated with different actions, different types of actions, different quantifications of use, and/or different time periods (in some embodiments, the same time period). ) is received ( 712 ) corresponding to a request to display a visual indication of. For example, in response to user input looking at the total screen time over the past week and the time spent using a particular application, the electronic device updates the display to show the total screen time over the past week and the time spent using a particular application. Presents the time spent using the electronic device to interact (eg, thus allowing the user to see metrics over different time periods as opposed to over the past day). As another example, in response to input to see the number of notifications received by the electronic device over a day (e.g., in response to user input of swiping down through a dashboard user interface), the electronic device Update to show a chart showing the number of notifications received on the electronic device during each hour and details on how many notifications were generated by different applications. In some embodiments, in response to receiving the input, the electronic device updates the dashboard user interface to include visual indications of the third usage metric, such as FIGS. 6M-6N. (714) (eg, with or without ceasing to display the visual indication of the first usage metric and the second usage metric). For example, the input displaying the visual indication of the third metric of use optionally did not previously display the visual indication of the third metric of use on the display. Input scrolling through the dashboard user interface, optionally scrolling through the displayed displays. Multiple visual indications of multiple usage metrics can be displayed simultaneously, allowing the user to see additional visual indications of additional usage metrics. can be effectively visually communicated to the user, thereby simplifying the interaction between the user and the device to enhance the device's operability (e.g. by providing more than one way of communicating device usage so that usage metrics can be viewed), as well as allowing users to use their devices more quickly and efficiently , to reduce power usage and improve device battery life.

In some embodiments, the electronic device is associated with a user account (e.g., a user ID for accessing personal data and/or settings on multiple electronic devices), such as FIG. 6D. (716). The dashboard user interface optionally displays a first corresponding usage metric (e.g., includes 718 a visual indication of the first usage metric or the second usage metric) (e.g., the first usage metric associated with the user account for performing the first action); track all use of electronic devices). In some embodiments, the first quantification of use is the use of a plurality of electronic devices, including an electronic device performing a first action during a first predetermined time period, as shown in FIG. 6UU. Aggregate 720 (eg, if the first usage metric is the amount of time spent running a particular application or a particular group of applications, the first quantification of usage may be a predetermined is the total amount of time spent running a particular application or a particular group of applications across all devices associated with a user account during a period of The above-described method of associating usage metrics with multiple electronic devices associated with a user enables the electronic devices to present consistent and accurate usage data to the user across all of the user's devices, thereby enabling the user and Simplify interaction with devices to enhance device usability (e.g. metric user usage data for all devices without the user needing to see usage data for each device individually) ), and also allows users to use the device more quickly and efficiently, thereby reducing power usage and improving the battery life of the device.

In some embodiments, the dashboard user interface displays the second corresponding use of the second electronic device associated with the first operation of the electronic device rather than the first operation of the second electronic device, as shown in FIG. including 722 a visual indication of a metric (e.g., a third usage metric) (e.g., since the electronic device displays usage metrics aggregated across multiple devices, the usage for each device is to display the metrics separately, depending on user input to do so (e.g., user input selecting a particular device from a list of devices associated with the user's account). In some embodiments, the electronic device simultaneously displays visual indications of usage metrics for each of a plurality of electronic devices associated with the user account. The above-described method of associating usage metrics with multiple electronic devices associated with a user enables the electronic devices to present consistent and accurate usage data to the user across all of the user's devices, thereby enabling the user and Simplify interaction with devices to enhance device usability (e.g. metric user usage data for all devices without the user needing to see usage data for each device individually) ), and also allows users to use the device more quickly and efficiently, thereby reducing power usage and improving the battery life of the device.

In some embodiments, while displaying the visual indication of the first metric of usage and the visual indication of the second metric of usage within the dashboard user interface, the electronic device A request to display the first use metric and the second use metric in more detail, such as FIGS. A request to view more information about the first-use metric and/or the second-use metric, such as a selection of the metric and/or the second-use metric (e.g., toggle from "Summary" to "Detailed View") Receive 724 an input corresponding to )). In some embodiments, in response to receiving the input, the electronic device updates the dashboard user interface to provide a second visual indication of the first usage metric, as shown in FIG. 6G. (e.g., a visual indication that includes more information on or about the first usage metric than was included in the first visual indication), and a second visual indication of the second usage metric Display 726 an indication (eg, a visual indication that includes more information at or about the second usage metric than was included in the first visual indication). A second visual indication of the first usage metric and a second visual indication of the second usage metric are shown in FIGS. ), optionally a first corresponding quantification of use of an electronic device performing a first action during each of a plurality of time periods during a first predetermined time period. It includes (728) a visual indication (730). In some embodiments, the second visual indication of the first usage metric is a graph or chart over time (e.g., line graph, bar graph, multiple ) and a second visual indication (732) ( for example, showing the metric in hourly bins over a day). In some embodiments, the second visual indication of the second metric of use is a graph or chart over time (e.g., a line graph, a bar graph, multiple pie charts for each time interval) or included in it. Each indication of use for each of the plurality of time periods optionally includes a first action (e.g., presenting information in a first application or first group of applications) and a second action ( For example, presenting information in a second application or group of second applications). In some embodiments, the detailed view includes a first action (e.g., presenting information in a first application or a first group of applications) and a second action (e.g., a second application or a second presenting information in groups of two applications), including graphs or charts using different colors or other visual indications that communicate quantification of usage by an electronic device running The above-described method of further displaying information about the first usage metric enables the electronic device to display usage summary and usage detail views, thereby providing interaction between the user and the device. simplifies and enhances the usability of the device (e.g., by hiding details when the user does not wish to see them, and by showing details when needed) Reduce power usage and improve device battery life by allowing the device to be used more quickly and efficiently.

In some embodiments, the dashboard user interface is visually associated (eg, displayed next to) the visual indication of the first usage metric, as shown in FIGS. 6HH-6II. , a first affordance (eg, selectable icon) (736) selectable to display a settings user interface for changing one or more settings associated with the first usage metric. (734) (eg, the first usage metric is the amount of time that the electronic device is used to execute a first application or first group of applications, and the configuration user interface options (such as method 900) for setting usage limits for an application or a first group of applications. Additionally or alternatively, the first usage metric is optionally a number of notifications generated by the first application or the first group of applications, and the configuration user interface comprises Contains options for changing notification settings for the first group of applications. In some embodiments, the second-use metric is visually associated (eg, displayed next to) the visual indication of the second-use metric, such as FIGS. 6HH-6II. A second affordance (e.g., selectable icon) (738) selectable to display a settings user interface for changing one or more associated settings (e.g., the second usage metric is the amount of time the electronic device is used to run the second application or the second group of applications, and the setting user interface sets a usage limit for the second application or the second group of applications options (such as method 900) for Additionally or alternatively, the second usage metric is optionally a number of notifications generated by the second application or the second group of applications, and the configuration user interface Contains options for changing notification settings for a second group of applications. In some embodiments, the dashboard user interface includes graphs or charts (e.g., bar graphs, line graphs, pie charts, etc.) showing at least the first usage metric and the second usage metric, and at least the first Includes a list of usage metrics and a second usage metric. The dashboard user interface optionally includes additional usage metrics in graphs or charts and in lists. In some embodiments, the first affordance and the second affordance are displayed next to visual indications of the first usage metric and the second usage metric included in the list, respectively. In some embodiments, the settings user interface includes visual indications of use of the selected application or category over a first period of time (e.g., a day), restricted usage modes (e.g., bedtime or device rest). indication of usage during a period of time, indication of average usage of a particular application, indication of notifications generated by the application, affordances for setting usage limits for a particular application, and overview of store information about the application ( rating, category, developer, link to the application in the app store). Additional or alternative metrics are possible. In some embodiments, when a user selects an affordance associated with a category of applications, corresponding metrics are displayed for each application. In some embodiments, the electronic device displays affordances selectable to display metrics for a single application in response to a user selecting affordances associated with a category of applications. The above-described method of displaying affordances selectable to display a configuration user interface while displaying the first and second metrics of use provides the electronic device with an indication that the user is viewing the metrics of use. provide a way to navigate to settings associated with usage metrics between users, thereby simplifying interaction between users and devices to enhance device usability (e.g. by simplifying the user's workflow for changing settings associated with displayed metrics), as well as by enabling users to use their devices more quickly and efficiently to improve device battery life.

In some embodiments, the first predetermined time period is the current day (740), as shown in FIG. (which is a quantification of the use of electronic devices in Japan). In some embodiments, the current day is defined as starting at 12:00 AM in the current time zone of the electronic device. In some embodiments, the current day is defined as some other 24 hour interval, such as 24 hours before the current time on the electronic device. A third usage metric is optionally associated 742 with the first operation of the electronic device (eg, the third usage metric is associated with the first usage metric and some other associated with the same operation of different electronic devices in the manner of (eg, quantification of use, time intervals, etc.). In some embodiments, the visual indication of the third usage metric is the number of uses of the electronic device for performing the first activity during the week prior to the current day, as shown in FIG. 3 quantification (744) (e.g., electronic device over a week (e.g., past seven days including the current day, one week including the current day starting on a particular day (e.g., Sunday or Monday)) display the usage metric associated with the first operation of ). In some embodiments, the visual indication of the metric of first use is or is included in a graph or chart (eg, line graph, bar graph, bar chart, or pie chart). For example, the first usage metric is optionally the amount of time that the electronic device is used to present information associated with the first application or the first group of applications, the dashboard displays a graph or chart containing device usage for each day broken down into panes representing respective applications or groups of applications. The above-described method of updating the dashboard user interface to display first usage metrics over a week period allows an electronic device to present usage metrics over a longer period of time, thereby allowing users and devices to enhance the usability of the device (e.g. by presenting additional information at the same time) by simplifying interactions between This reduces power usage and improves device battery life.

In some embodiments, the dashboard user interface provides a visual indication of a first corresponding usage metric (e.g., first usage metric) associated with displaying information on the display. (746) (e.g., the first action is display usage or "screen time" (e.g., across all applications), as shown in FIG. 6L. In some embodiments, the first action further encompasses other methods of presenting information, such as playing sounds (e.g., music or other media, spoken sounds such as during a call, etc.) using speakers that communicate with the electronic device) , a first corresponding usage metric, as shown in FIG. A first metric is the total use of the electronic device to display information across all applications on the electronic device (eg, total application show time on the electronic device). In some embodiments, the total usage metric is the amount of time that one or more speakers associated with the electronic device are used to present audio content and other output devices of the electronic device present information. It also includes the time used for Total usage is optionally presented as an amount of usage time over a specified time period (eg, a day, a 24-hour period, a week, or another user-specified time period). In some embodiments, the total usage is optionally presented to the user in text (eg, text indicating the amount of time the device has been used) and/or graphically, such as a graph or chart. The indication optionally indicates the total device usage as a percentage (e.g., 50% of the 4-hour usage limit) or percentage (e.g., 2 hours of the 4-hour usage limit) set by the user of the electronic device. Contains percentage bars represented as . In some embodiments, while presenting a first metric indicative of overall display or device usage, the electronic device displays or presents information in which the electronic device is associated with various applications or groups of applications. One or more usage metrics (eg, including a second usage metric) are further presented that indicate the amount of time used to do so. For example, the visual indication of total device display time optionally includes an indication of how long the device has displayed or presented information associated with each of the multiple applications or groups of applications. The above-described method of presenting a visual indication of the amount of time the device has been used to present information allows the electronic device to visually convey to the user the amount of time the device has been used. , which makes the user-device interface more efficient (e.g., the user does not need to monitor their own device usage, thus reducing input provided by the user to the device (e.g., input to monitor is reduced)), in addition to reducing power usage and improving the battery life of the device by allowing the user to use the device more quickly and efficiently.

In some embodiments, displaying information on a display may involve one or more first applications (e.g., a particular application or group of applications, such as FIG. 6L, some In the embodiment of , the application group may be user-defined or defined by the system or a third party to display information on a display (e.g., present it on a different output device that communicates with the electronic device ( For example, playing sound, media, or speech on a speaker that communicates with the electronic device (750). A first corresponding usage metric is optionally used by the electronic device to display information in one or more first applications during a first predetermined period of time, as shown in FIG. the amount of time played 752 (eg, the first usage metric is the screen time associated with one or more first applications). In some embodiments, usage limits are set 754 for one or more first applications (e.g., prior to accessing one or more second applications), as shown in FIG. 6L. limits the amount of time that one or more first applications can be used to present information in a given period of time (eg, one day). A first corresponding visual indication of the usage metric is optionally a usage limit for the one or more first applications (e.g., the device's usage limit for the one or more applications), as shown in FIG. 6L. maximum amount of time that the device will present information without restricting access), wherein the first usage limit indication is a visual indication of the first corresponding usage metric (eg, the visual indication visually compares the amount of time the device is used to present information compared to the usage limit). In some embodiments the visual indication of the first metric is a graph. For example, the visual indication is optionally a bar chart and the size of the bar chart represents the usage limit. In some embodiments, usage limits are predefined by the user. The dashboard user interface optionally provides an indication when the usage limit is nearly reached (e.g., text or icon indicating that the usage limit is nearly reached) and/or a usage limit is exceeded. Present an indication when the usage limit is exceeded, optionally including an indication that quantifies the extent to which the usage limit is exceeded. For example, when a usage limit is represented by a bar chart, a portion of the bar chart optionally indicates usage exceeding the usage limit. The user optionally sets usage limits for one or more applications, one or more groups of applications, and/or overall usage limits for the device. Thus, in some embodiments, the one or more first applications optionally comprise one application, multiple applications, or all applications accessible on the electronic device. The usage limits described herein are optionally the same or similar to the usage limits described with reference to method 900 . The above-described method of comparing the first metric to the usage limits of the electronic device determines how long the user will use the electronic device to obtain information before one or more usage limits will be enforced. Allows the user to communicate whether they can continue to present, which makes the interface between the user and the device more efficient (e.g., the user does not need to compare the user's device usage with their own usage limit). not available), in addition to reducing power usage and improving the battery life of the device by allowing the user to use the device more quickly and efficiently.

In some embodiments, the dashboard user interface includes one or more secondary applications (e.g., a particular application or group of applications, such as shown in FIG. 6N; in some embodiments, the application group is Displaying information on a display (either defined by the user or defined by the system or a third party) (for example, or presented on a different output device in communication with the electronic device (e.g., on speakers in communication with the electronic device) a visual indication of a second corresponding usage metric (eg, the second usage metric) associated with the playing sound, media, or speech) (758). In some embodiments, as shown in FIG. 6N, usage limits are not set for one or more secondary applications (760), and the visual indication of the second corresponding usage metric is , optionally does not include an indication of the usage limit of one or more second applications (eg, because it does not exist) (762). The visual indication of the second usage metric is optionally the amount of time that the electronic device was used to display information in the one or more second applications without indication of usage limit. indicate. In some embodiments, no usage limits are set for the one or more secondary applications, although usage of some or all of the one or more secondary applications is optionally limited to one Limited by a usage limit that has a scope that is strictly different from all of the one or more secondary applications. For example, the one or more second applications optionally include all of the applications accessible on the electronic device, and the one or more first applications optionally include a particular category of applications ( games). In this example, there is no overall usage limit optionally set on the electronic device (e.g., a usage limit that sets maximum device usage across all applications), but one or more of the second applications The part (eg, one or more first applications) is subject to usage limits (eg, usage limits of one or more first applications). Similarly, the one or more second applications optionally comprise a specific application (eg, a specific game application) and the one or more first applications optionally comprise an application specific application. category (eg, games). In this example, there is no usage limit optionally set for a particular second application, but because the one or more first applications include the second application, the second application Usage is limited by usage limits of one or more first applications. The above-described method of indicating usage limits associated with application usage while displaying application usage metrics provides an indication of how long a user can wait before an electronic device is subject to one or more usage limits being enforced. Allows the application to communicate whether the application can continue to present information, thereby making the interface between the user and the device more efficient (e.g., the user can control the user's application (no need to compare usage limits), in addition to reducing power usage and improving device battery life by allowing users to use the device more quickly and efficiently.

In some embodiments, the usage of the electronic device displaying information in the one or more first applications is a threshold amount (e.g., a percentage amount) of the usage limit of the one or more first applications (e.g., 25%, 10%, 5%, etc.) or within an absolute amount of time (e.g., 30 minutes, 15 minutes, 5 minutes, etc.) (764), the first corresponding A visual indication of the usage metric may be a visual indication that the usage limit of the one or more first applications is nearly reached (e.g., a text or icon indicating that the usage limit is nearly reached). Displaying or applying a visual characteristic to the first visual indication of the usage metric (eg, changing the color or size of the visual indication or part of the visual indication). In some embodiments, each visual indication of one or more usage metrics displays a settings user interface for changing one or more settings associated with the corresponding usage metric. Including selectable affordances, optionally displayed with visual characteristics (e.g., different colors) that indicate usage limits associated with corresponding usage metrics that are within a threshold amount Dashboard user interface optionally, if the usage limit is exceeded, presents an indication that optionally includes an indication that quantifies the extent to which the usage limit is exceeded, for example, the usage limit is represented by a bar chart a portion of the bar chart optionally indicates usage exceeding the usage limit, in the manner described above to indicate when the usage limit is close to being reached while displaying usage metrics. allows an electronic device to communicate how long a user can continue to perform one or more actions before one or more usage restrictions are to be enforced, thereby: Making the interface between the user and the device more efficient (e.g., the user does not have to compare the user's usage against their own usage limit), as well as allowing the user to use the device more quickly and efficiently reduces power usage and improves device battery life by allowing

In some embodiments, the first corresponding visual indication of usage metrics is used for the electronic device to present information using each of the plurality of application groups, as shown in FIG. 6L. 766, and each application group includes one or more applications accessible on the electronic device (e.g., an application group may include a single application (e.g., the email application , social networking applications, gaming applications, Internet browsers, etc.) or a category containing multiple applications (e.g., a social media category, a gaming category, a news category, a user-defined category containing multiple applications selected by the user, etc.) or). The visual indication optionally includes a visual representation of how much total device time was used in each application category. In some embodiments, the total device usage metric is displayed as a graph or chart, where the graph or chart includes segments for each application category (e.g., a pie chart with multiple “slices,” multiple partitions). bar chart with , bar chart with multiple bars). The total usage is optionally compared to a usage limit (e.g., pie chart full pie represents a fixed usage limit, bar chart length represents a fixed usage limit, Such). In some embodiments, the dashboard user interface displays a second time associated with the amount of time that the electronic device is used to present information using the first application group, as shown in FIG. 6L. including 768 a visual indication of a corresponding usage metric (e.g., a second usage metric) of (e.g., in addition to presenting the device usage of the first application group within the total device usage metric , a separate metric is presented that conveys the amount of time the first application group was used). The second corresponding visual indication of the usage metric is optionally separate from the first corresponding visual indication of the usage metric, as shown in FIG. 6L. including (770) a visual indication of the metrics of the first application The use of groups is presented in an additional way). In some embodiments, the visual indication of use of the first application group includes text indicating the amount of time the first application group was used. Optionally, such as a bar with a length indicating use of the first application group, a dot with a position indicating use of the first application group, or another visual representation of use of the first application group. A graphic separate from the visual indication of total device usage is displayed. In some embodiments, the electronic device displays a graph or chart that indicates how long the electronic device has been used to present information using each of multiple applications and/or groups of applications, and multiple Presents a text indication of the amount of time spent using each of the applications and/or groups of applications. The above-described method of presenting device usage for each of a plurality of application groups enables an electronic device to graphically present detailed information regarding device usage to a user, thereby providing interactive communication between the user and the device. It simplifies the action and enhances the usability of the device (e.g., by presenting details about the displayed metrics along with the displayed metrics without further input from the user), as well as allowing the user to use the device more easily. It reduces power usage and improves device battery life by allowing it to be used quickly and efficiently.

In some embodiments, the dashboard user interface is one or more first desktops accessible on the electronic device (e.g., installed or accessed via a network connection), as shown in FIG. 6L. including a visual indication (774) of a first corresponding usage metric (eg, a first usage metric) associated with running the applications (eg, an individual application or category of applications) ( 772). The dashboard user interface optionally includes one or more secondary applications accessible (eg, installed or accessed via a network connection) on the electronic device (eg, shown in FIG. 6L). Individual applications or categories of applications, such as.In some embodiments, categories of applications are defined by users.In some embodiments, categories of applications are defined by app stores, publishers, etc. (776) of a second corresponding usage metric (eg, a second usage metric) associated with operating the Thus, as shown in FIG. 6L, the usage metric associated with the first activity optionally includes the electronic device executing one or more first applications during a first predetermined period of time. The usage metric associated with the second action is the amount of time used to (e.g., display) the electronic device, optionally one or more is the amount of time used to run (eg, display) the second application of The above-described method of presenting usage metrics for running applications and/or groups of applications enables an electronic device to present information about which applications are running on the electronic device, thereby: Simplify interaction between the user and the device to enhance device usability, as well as reduce power usage by allowing the user to use the device more quickly and efficiently. to improve the battery life of your device.

In some embodiments, the one or more first applications are multiple applications belonging to the same category (eg, a user-defined category or a system-defined category of applications), as shown in FIG. 6L. There is (778). In some embodiments, categories are defined by an app store, an application publisher or distributor, or another party other than the user. When a new application is introduced to the electronic device (e.g., downloaded from an app store), usage limits set for the category with which the new application is associated are optionally automatically applied to the new application. be done. The first metric is optionally a quantification of total usage for the group of applications within that category. The one or more second applications are optionally an application (780), as shown in FIG. 6L (eg, the second metric is optionally quantification). In some embodiments, the dashboard user interface displays a mixture of one or more metrics for groups of applications as well as one or more metrics for individual applications. In some embodiments, the user defines which applications should have their own metrics presented in the dashboard user interface and which groups of applications should have group metrics presented in the dashboard user interface. do. In some embodiments, the electronic device determines which applications should have individual application metrics presented in the dashboard user interface and which application groups should have group metrics presented in the dashboard user interface. do. For example, applications with usage above a predetermined application usage threshold will optionally have application metrics presented within the dashboard user interface, and the category(s) of applications with usage above a predetermined category threshold. In embodiments, no individual application with usage above the application usage threshold, and in some embodiments even with one or more individual applications with usage above the application usage limit , will cause the category metrics to be presented within the dashboard user interface. The above-described method of simultaneously presenting metrics for individual applications and application categories within a dashboard user interface presents usage metrics that indicate in a meaningful way how an electronic device is being used ( by displaying metrics with similar granularity), which simplifies interaction between users and devices and enhances device usability (e.g., category metrics and application metrics). (by presenting a mixture of ) at the same time, as well as allowing the user to use the device more quickly and efficiently, thereby reducing power usage and improving the battery life of the device.

In some embodiments, the first usage metric is the usage of the native application and the usage of web resources associated with the native application (e.g., using the web application or viewing a web page, as shown in FIG. 6RR). ) (e.g., when a user uses a browser application to access a website (e.g., a particular social networking website) associated with an application (e.g., a particular social networking application associated with the website) on an electronic device When using a browser application to access a web site, it expresses (782). For example, if the first usage metric is a social media metric, the first metric may be device usage for accessing the social media platform using a web browser on the electronic device and including use of the device to run any social media application. The methods described above for including device usage for accessing web pages using the browsing application of an electronic device as part of the metrics of usage associated with the application or category associated with the web page do not require that the electronic device Enables accurate tracking of device usage associated with applications or categories of usage metrics, thereby simplifying interaction between users and devices to enhance device usability (e.g., by combining web usage with appropriate usage metric(s), as well as enabling users to use devices more quickly and efficiently, thereby reducing power usage and improve battery life.

In some embodiments, as shown in FIG. 6PP, multiple first applications of one or more first applications (eg, multiple user-defined or system-defined applications belonging to the same category) is a predetermined category usage threshold (e.g., a predetermined category usage threshold is an absolute threshold (e.g., a first period of time (e.g., one day, one week, etc.) where the plurality of first applications operate A predetermined amount of time (e.g., 30 minutes, 1 hour, 2 hours, etc.) or number of times (e.g., 5 times, 10 times) used to perform (e.g., present information, generate notifications, etc.) , 50 times), or a percentage threshold of total device usage during the first time period (e.g., 5%, 10%, 25%, etc.) (784). The interface optionally includes combined usage metrics for the plurality of first applications (eg, without including individual usage metrics for any of the plurality of first applications) (eg, multiple when the total usage of the first applications exceeds the category threshold, the total usage of the plurality of first applications as a group is presented in the dashboard user interface as a first metric). In some embodiments, as shown in FIG. 6PP, the total usage of the plurality of first applications of the one or more first applications does not exceed a predetermined category usage threshold (e.g., multiple application total usage is less than the threshold), the dashboard user interface does not include combined usage metrics for the plurality of first applications, and A usage metric for the application (e.g., when the combined usage of the multiple applications does not meet the threshold, the usage of one or more applications within the category optionally includes a separate usage metric (e.g., the first and/or including a second usage metric)). The above-described method of selectively presenting metrics about groups of applications enables an electronic device to present information about the categories of applications most commonly run, thereby increasing interaction between users and devices. to enhance device usability (e.g., by presenting a combined metric for a group of applications when the total usage of the group of applications exceeds a threshold), as well as allowing the user to use the device more quickly and efficient use, thereby reducing power usage and improving device battery life.

In some embodiments, as shown in FIG. 6QQ, one or more first applications (e.g., one or more first applications may be multiple user-defined or system-defined categories belonging to the same category). application usage) exceeds an application usage threshold (e.g., a predetermined application usage threshold is an absolute threshold (e.g., the first application during a first period of time performs an action (e.g., present information, generate notifications, etc.) a predetermined amount of time (e.g., 30 minutes, 1 hour, 2 hours, etc.) or number of times (e.g., 5, 10, 50 times), or a percentage threshold of total device usage during the first time period (e.g., 5%, 10%, 25%, etc.) is exceeded 788, the dashboard user interface , including a usage metric for a single first application (eg, instead of or in addition to a combined usage metric for multiple first applications) (eg, if the usage of the first application exceeds the application threshold usage of the first application is presented in the dashboard user interface as the first metric). In some embodiments, as shown in FIG. 6QQ, the total usage of a single first application of the one or more first applications does not exceed a predetermined application usage threshold (e.g., a single first application usage is below the threshold), the dashboard user interface includes usage metrics for the plurality of first applications (e.g., usage of a single first application exceeds the threshold). When not satisfied, the usage of the multiple first applications as a group is presented in the dashboard user interface as the first metric). The application usage threshold here is optionally the same as or similar to the application usage limit described with reference to method 900 . The above-described method of presenting metrics about applications allows an electronic device to present information about the applications that are most commonly run, thereby simplifying the interaction between the user and the device to facilitate the operation of the device. (e.g. by presenting metrics about applications when a group's application usage exceeds a threshold), as well as enabling users to use their devices more quickly and efficiently , to reduce power usage and improve device battery life.

In some embodiments, the dashboard user interface displays a first corresponding usage metric (e.g., first usage metrics) (e.g., a dashboard user interface includes 792) received on the electronic device during a given amount of time (e.g., hour, day, week, etc.) including the Notifications metric, which shows the number of notifications). One or more notifications are optionally received from different electronic devices via wireless or wired connections. One or more notifications are optionally generated by an application installed on the electronic device. The above-described method of displaying notification metrics within a dashboard user interface enables an electronic device to efficiently and clearly communicate device usage for receiving notifications, thereby reducing user-to-device interaction. enhance the usability of the device (e.g. by automatically collecting notification usage data) by simplifying the interaction of This reduces power usage and improves device battery life.

In some embodiments, the electronic device receiving one or more notifications at the electronic device is triggered by one or more first applications (e.g., system-defined or a user-defined application or group of applications, such as multiple applications within the same category) (e.g., receiving a new message notification from a messaging application) (794 ). In some embodiments, the electronic device presents an indication of each notification received (eg, displays an image, generates vibration or tactile and/or tactile output, plays sound, etc.). The first corresponding visual indication of usage metric optionally includes one or more A displayed number indicating the number of received notifications associated with the first application (e.g., a particular application or group of applications, such as system-defined or user-defined multiple applications within the same category) (796). In some embodiments, the dashboard user interface receives notifications associated with one or more secondary applications of the electronic device (e.g., receiving advisory notifications from an advisory application), as shown in FIG. 6R. includes (798) a visual indication of a second corresponding usage metric (eg, a second usage metric) associated with (798). In some embodiments, the electronic device presents an indication of each notification received (eg, displays an image, generates vibration or tactile and/or tactile output, plays sound, etc.). A second corresponding visual indication of the usage metric, optionally for a first predetermined period of time (eg, a day, a week, a month, etc.), as shown in FIG. A displayed number indicating the number of received notifications associated with one or more second applications of the electronic device is included (798-2). The above-described method of displaying metrics for notifications associated with an application or group of applications enables an electronic device to present information about which applications generate the most notifications, thereby increasing user-device interaction. enhance the usability of the device by simplifying interactions between them (e.g. combining application data with notification metrics so that the user knows which applications are using the device and causing notifications to be presented most often). by presenting it as part of the application), as well as by enabling the user to use the device more quickly and efficiently (e.g., applications that generate more notifications that the user wishes to receive). (by changing your notification settings) to reduce power usage and improve your device's battery life.

In some embodiments, the dashboard user interface is a settings user interface for changing notification settings for one or more first applications (e.g., allow all notifications), as shown in FIGS. options to allow some notifications (e.g., based on priority, time of day, or some other metric), or disallow notifications for applications or groups of applications). It further includes (798-4) an affordance (798-6) of 1. In some embodiments, the first affordance is visually associated with (eg, displayed next to) the first corresponding visual indication of the usage metric, as shown in FIGS. 6LL-6MM. ) (e.g., notification metrics are displayed at the same time as affordances for changing notification settings). and a settings user interface for changing the notification settings of one or more secondary applications (e.g., allow all notifications, allow some notifications (e.g., priority, time of day, or some other second affordance (798-8) that can be selected to display either a metric for the application or an option to disallow notifications for an application or group of applications). The second affordance is optionally visually associated with (eg, displayed next to) a second corresponding visual indication of the usage metric (eg, the notification metric changes notification settings). (displayed at the same time as affordances for In some embodiments, the electronic device includes customizable notification settings for each application or group of applications. The electronic device optionally further includes notification settings that affect all of the applications on the electronic device. The above-described method of displaying affordances selectable to display notification settings while displaying metrics for notifications associated with an application or group of applications is provided by an electronic device associated with metrics currently viewed by a user. This allows you to present options to change settings that have been configured, thereby simplifying the interaction between the user and the device to enhance the device experience (e.g. by looking at notification metrics). by making notification settings accessible while you are away), as well as allowing the user to use the device more quickly and efficiently (e.g. changing notification settings after viewing notification metrics). ) to reduce power usage and improve device battery life.

In some embodiments, the first corresponding visual indication of the usage metric is for a first predetermined time period (eg, one day, one week, one month, etc.), as shown in FIG. includes a chart (e.g., line graph, bar chart, etc.) containing an indication of the number of notifications received during each of a plurality of time intervals (e.g., during each hour, each day, etc.) between 798-10 ). The above-described method of presenting a chart of notifications received over time allows the electronic device to provide an indication of how many notifications have been received over a given period of time and how many notifications have been received within each interval. at the same time, thereby simplifying the interaction between the user and the device and enhancing the usability of the device (e.g. displaying related information together without further user input). ), in addition to reducing power usage and improving the battery life of the device by allowing the user to use the device more quickly and efficiently.

In some embodiments, the dashboard user interface displays a corresponding usage metric (e.g., a first metric or a second usage metric) associated with detecting a user attention event, as shown in FIG. 6U. ) (798-12) (eg, a dashboard user interface includes a metric that indicates the number of times a user initiates interaction with an electronic device). In some embodiments, the electronic device presents a user attention events (eg, “device pickup”) dashboard that shows one or more metrics related to user attention events. The User Featured Events dashboard optionally displays the average time between pickups over a predetermined period of time (e.g., day, week, etc.), total number of pickups over a predetermined period of time, most user featured events, (e.g., hour of day, or hour or day of week), number of pickups during restricted use mode, and other metrics such as including. In some embodiments, user input to the electronic device is in an idle state (e.g., no user interaction with the electronic device and/or the display of the electronic device is off, sleep mode, locked state, low power mode, etc.). , a user attention event is detected. In some embodiments, the electronic device enters the idle state in response to a predetermined amount of time having elapsed since the last user input was received at the electronic device. Optionally, the electronic device enters the idle state in response to user input (eg, pressing a power or lock button on the electronic device) corresponding to a request to enter the idle state. In some embodiments, the display does not show images while in the idle state. In some embodiments, a lock screen is displayed on the electronic device while it is idle. The user input corresponding to the user attention event is optionally a button press on the electronic device, a user action to exit an idle state (e.g. picking up the device), an unlock input (e.g. a passcode or provide a biometric) and electronic device functionality (e.g. widget user interface, camera application, dashboard user interface, application user interface associated with the displayed notification indication) one or more of the touch inputs to access the Detecting the biometric optionally includes detecting the user's face with a depth camera or another sensor. In some embodiments, the electronic device uses depth cameras and facial recognition technology to determine when a user looks at the user's electronic device and unlocks the electronic device in response to the user looking at the electronic device. (eg, the electronic device unlocks in response to a determination that the user is eyeing the electronic device). In some embodiments, the electronic device exits the idle state and pays attention in response to a notification (e.g., the display turns on to show the notification without user input requiring the display to turn on). The event causes the device to perform some other action (eg, unlock the device, update the display to show an application or operating system user interface). That is, the indication of notification is optionally not a user attention event even if it causes the device to exit the idle state. In some embodiments, the event of interest metric indicates the number of times the user initiates use of the electronic device (eg, "checks" the user's phone). The above-described method of displaying metrics associated with user attention events (e.g., device pickup) enables an electronic device to present information about how often a user interacts with the electronic device, thereby: It simplifies the interaction between the user and the device to enhance the usability of the device (e.g., by communicating usage information in a way that is meaningful to the user), and also allows the user to use the device more quickly and By enabling efficient use (e.g., by encouraging users to use their phones less frequently and thus more efficiently), reducing power usage and conserving device battery life improves.

In some embodiments, the first corresponding visual indication of the usage metric is the time between user attention events (e.g., user attention event (e.g., electronic device button pressed), as shown in FIG. 6U. being pressed, a user action to exit an idle state (e.g. picking up the device), an unlock input (e.g. entering a passcode or providing a biometric), an electronic device function (e.g. Widget user interface, camera application, dashboard user interface, visual indication of the average time between touch inputs) to access the user interface of the application associated with the displayed notification indication) (798-14). In some embodiments, the time between user-attention events is calculated as the average time between user-attention events for time periods within a first predetermined time period (e.g., 1 day, 1 week, etc.); This time period includes the earliest user-focused event during the first predetermined time period (e.g., the first event of interest in a day, week, or other predetermined time period) and the last user-focused event during the first predetermined time period. (eg, the last event of interest in a day, week, or other predetermined period of time). The above-described method of displaying a metric indicating the average time between user attention events (e.g., device pickup) enables an electronic device to present information about how often a user interacts with the electronic device; This simplifies the interaction between the user and the device to enhance the usability of the device (e.g., by conveying usage information in a way that is meaningful to the user), and also allows the user to use the device By enabling quicker and more efficient use (e.g., by encouraging users to use their phones less frequently and thus more efficiently), reducing power usage and Improve battery life.

In some embodiments, the first corresponding visual indication of usage metric is the user's attention during a first predetermined period of time (eg, a day, a week, etc.), as shown in FIG. 6U. Event (e.g., button pressed on electronic device, user action to exit idle state (e.g., picking up device), unlock input (e.g., entering passcode, or providing biometric) ), touch input to access electronic device functionality (e.g., displaying a widget user interface, a camera application, a dashboard user interface, an application user interface associated with a displayed notification indication) (798-16). The above-described method of displaying a metric indicating the number of user attention events (e.g., device pickups) enables an electronic device to present information about how often a user interacts with the electronic device, thereby: It simplifies the interaction between the user and the device to enhance the usability of the device (e.g., by communicating usage information in a way that is meaningful to the user), and also allows the user to use the device more quickly and By enabling efficient use (e.g., by encouraging users to use their phones less frequently and thus more efficiently), reducing power usage and conserving device battery life improves.

In some embodiments, the first usage metric visual indication is the time interval (e.g., the hour of the day) having the highest number of detected user attention events, as shown in FIG. 6U. , an hour or a day in a week), and the time interval is one of a plurality of time intervals within a first predetermined time period (e.g., , the hour of the day where the most user attention events were detected compared to all of the hours of the day, or the most user attention events of which were detected compared to all of the hours or days of the week 1 day or 1 hour in a week). The above-described method of displaying a metric indicating time intervals with the most user-attention events (e.g., device pickups) enables an electronic device to present information about when a user most interacts with the electronic device; This simplifies the interaction between the user and the device and enhances the usability of the device (e.g., by conveying usage information in a way that is meaningful to the user), as well as allowing the user to By enabling faster and more efficient use (e.g., by encouraging users to use their phones less frequently and thus more efficiently), reducing power usage and Improve battery life.

In some embodiments, detecting an event of interest (798-20) may be performed as shown in FIG. operating system user interface that appears before the device is unlocked without displaying the user interface of any application), screensavers (e.g. screensavers that appear without displaying the user interface of any application that is accessible to the electronic device); or is off (e.g., does not display an image)), following a determination 798-22 that the detected user input corresponds to a request to exit the idle state of the electronic device. events (e.g., events of interest are device movements that meet one or more activation criteria (e.g., lifting to wake), touch input (e.g., selecting an image displayed on the lock screen), touch input, widget user interface, camera user interface, or swipe input to display another user interface of the operating system or one or more applications), actuation of buttons included in the electronic device (e.g., power button, pressing an unlock button, home button, or another button, or toggling a switch), or biometric input of the user (e.g., fingerprint, image of the user's face, or another biometric input (e.g., device is one of the detections of )) to unlock the ). Detecting the biometric optionally includes detecting the user's face with a depth camera or another sensor. In some embodiments, the electronic device uses depth cameras and facial recognition technology to determine when a user looks at the user's electronic device and unlocks the electronic device in response to the user looking at the electronic device. (eg, the electronic device unlocks in response to a determination that the user is eyeing the electronic device). In some embodiments, as shown in FIG. 6U, the detected user input does not correspond to a request to exit the idle state of the electronic device (eg, the electronic device is not idle or the detected user input is incorrect). (e.g., large human contact, device movement that does not correspond to the user picking up the device, etc.), the electronic device refrains from identifying the user input as an event of interest (798-24). (eg, processing user input as input other than the event of interest, or forgoing processing of erroneous user input). The above-described methods of detecting various user-attention events and recording the detections enable an electronic device to present information about how often a user interacts with the electronic device, thereby allowing the user and device to interact with each other. enhances device usability (e.g., by communicating usage information in a way that is meaningful to the user) by simplifying interactions between use (e.g., by encouraging users to use their phones less frequently and thus more efficiently) to reduce power usage and improve device battery life.

In some embodiments, the first corresponding visual indication of usage metric is the restricted usage mode of the electronic device (e.g., "device idle time" or "bedtime"), as shown in FIG. 6U. (798-26) (e.g., the electronic device displays a metric indicating the number of times the electronic device detected user attention events during the restricted use mode). ). The restricted use modes described herein are optionally the same or similar to the restricted use modes described with reference to method 1100 . The above-described method of displaying a metric indicating the number of events of interest during the limited use mode allows the electronic device to present information regarding how often the user interacts with the electronic device during the limited time period. which simplifies interaction between the user and the device to enhance the device's usability (e.g., by communicating usage information in a way that is meaningful to the user); by enabling users to use their devices more quickly and efficiently (e.g., by encouraging users to use their phones outside of restricted modes and thus more efficiently) to improve device battery life.

In some embodiments, as shown in FIGS. 6K-L, prior to displaying the dashboard user interface, the electronic device displays notifications associated with the dashboard user interface (e.g., daily or weekly “digital Health" notification) is presented 798-28, which includes selectable affordances (eg, soft buttons or other user interface elements) to display a dashboard user interface. In some embodiments, this notification includes a visual indication of device usage over the past day, week, or another period of time. The indication is optionally selectable to display a dashboard user interface. The dashboard user interface is optionally displayed in response to detecting user input selecting affordances (e.g., the electronic device has one or more uses at the start of the week or the start of the day). presents a “digital health” notification containing an overview of the metrics of In some embodiments, a weekly "Digital Health" notification is presented at the start of the week, including an overview of overall device usage for the previous week. The summary optionally includes a visual indication of the amount of time the device has been used to present information using each of multiple applications and/or categories of applications, and overall device usage prior to Include indications relative to week (eg, percent above or below average weekly usage). In some embodiments, a daily "digital health" notification is presented at the start of the day, including an overview of overall device usage for the previous day. The summary optionally includes a visual indication of the amount of time the device has been used to present information using each of multiple applications and/or categories of applications, and overall device usage prior to Includes day-to-day comparison indications (eg, percent above or below average daily usage). Other time intervals are possible (eg, monthly usage, etc.). The above-described method of displaying a dashboard user interface in response to selection of a "digital health" notification allows the electronic device to alert the user to review the metrics of their usage, and to provide more information from notifications containing a summary of the metrics. Allows detailed metrics to be presented, thereby simplifying interaction between the user and the device to enhance device usability (e.g. usage summary as notification and more detailed usage by presenting more details in response to user input to present the Improve battery life.

In some embodiments, prior to displaying the dashboard user interface, the electronic device displays a widget user interface (798-30), as shown in FIGS. 6E-I, wherein the widget user interface includes one or more , each widget containing a secondary user interface of an application accessible on the electronic device (e.g., installed or accessible via a network connection) (e.g., each widget User interface objects (e.g., windows) that contain text and/or images associated with the application (e.g., weather widgets displaying current temperatures, sports widgets displaying scores for live events, headlines for recent events) and/or any user interface object that displays content associated with the application). In some embodiments, the content of widgets corresponding to an application is dynamically updated by the application. The one or more widgets optionally include metric widgets associated with the dashboard user interface (eg, widgets associated with the digital health dashboard and/or digital health settings). In some embodiments, the metric widget provides a corresponding visual indication of usage metrics (eg, when the electronic device uses each of a plurality of applications or groups of applications), as shown in FIGS. 6E-6I. bar chart showing the total time spent presenting information over the past week) (798-32). Other durations and/or operations are possible in some embodiments. In some embodiments, the widget further includes an indication comparing usage over a period of time to previous usage (eg, percent above or below average weekly usage). In some embodiments, as shown in FIGS. 6E-6I, the metric widget is selectable (798-34) to display a dashboard user interface (eg, the widget expands to a second or the electronic device presents a dashboard user interface within the settings application), the dashboard user interface optionally detects user input that selects a metric widget (798-36) (eg, the dashboard user interface is displayed in response to the user selecting or expanding the metric widget). The widget user interfaces described herein are optionally the same or similar to the widget user interfaces described with reference to methods 900, 1100, and 1300. The above-described method of displaying a dashboard user interface in response to selection of a metric widget enables the electronic device to display a usage metric (eg, a first usage metric) within a higher-level user interface (eg, a widget user interface). to provide a way for the user to enter inputs to view more detailed metrics while viewing the Metrics Widget, thereby providing two-way interaction between the user and the device. It simplifies the action and enhances the usability of the device (e.g., by presenting an overview of usage as a widget and more details in response to user input to present more details about usage), as well as the ability of the user to reduces power usage and improves device battery life by allowing the device to be used more quickly and efficiently.

In some embodiments, as shown in FIGS. 6DD-6EE, prior to displaying the dashboard user interface, the electronic device displays the electronic device's usage settings user interface (eg, settings user interface associated with device usage). , or the "Digital Health" settings user interface, which is the settings user interface for the operating system of the electronic device and not for any particular application on the electronic device (798-38). The usage settings user interface optionally includes one or more soft buttons selectable to display a user interface for changing settings associated with device usage. In some embodiments, the settings are one or more time intervals, one or more applications, categories of applications, or Usage limits for overall device usage (e.g., “tolerance”), one or more whitelisted applications (e.g., phone, messaging, maps, etc.) or application functionality (e.g., incoming calls from specific contacts) or receive a call), and/or setting one or more privacy and content settings. In some embodiments, the usage settings user interface includes a visual indication (798-40) of a corresponding usage metric (e.g., if the electronic device is in each of a plurality of applications or groups of applications), as shown in FIG. 6DD. bar chart showing the total amount of time spent presenting information over the past week using Other durations and/or operations are possible in some embodiments. In some embodiments, the widget further includes an indication comparing usage over a period of time to previous usage (eg, percent above or below average weekly usage). The user-configured user interface optionally includes affordances (798-42) selectable to display the dashboard user interface (e.g., causes the electronic device to update the display to present the dashboard user interface when selected). a selectable image or selectable text). In some embodiments, the visual indication of the first usage metric can be selected to display a dashboard user interface, as shown in FIGS. 6DD-6EE. In some embodiments, the dashboard user interface receives user input selecting affordances (e.g., the user touches a location on the touch screen where the visual indication of the fourth usage metric is displayed). (eg, a settings application of the electronic device includes a usage settings user interface for changing one or more usage settings of the electronic device). The usage settings user interface optionally includes a visual indication of a fourth usage metric selectable to display a dashboard user interface. In some embodiments, the fourth usage metric provides information about each of a plurality of applications or categories of applications that the device has used over a predetermined time period (eg, current day, current week, etc.) during that time period. The amount of time used to present. The visual indication is optionally a usage limit or "allowance" set for the electronic device that defines the maximum amount of time that the electronic device can present information without one or more usage restrictions. "Capacity" is further indicated. The above-described method of displaying a dashboard user interface in response to selection of a visual indication within a usage settings user interface, wherein the electronic device concurrently presents usage metrics of the electronic device and one or more usage settings, Allows the user to provide a way to enter inputs that view more detailed metrics while viewing usage settings, thereby simplifying interaction between the user and the device to improve the usability of the device. (e.g., by presenting a summary of usage and more details within the settings user interface in response to user input to present more details about usage), as well as helping the user to use the device more quickly and efficiently. reduce power usage and improve battery life of the device.

In some embodiments, the usage configuration user interface, as shown in FIG. 6B, is configured for one or more requests received from other electronic devices (e.g., over a network connection (e.g., wired or wireless connection)). Contains one or more visual indications (798-44). In some embodiments, the electronic device and the other electronic device change one or more usage restrictions implemented on the other electronic device (e.g., overall remove or increase usage limits (e.g., “tolerances”), remove or increase application or application category-specific usage limits (e.g., “tolerances”) for other electronic devices, or other electronic devices; is associated with a group or family account for requesting permission to exit a restricted operating mode (eg, device idle time or "bedtime" mode). In some embodiments, each visual indication includes a displayed image or displayed text indicating the request. In some embodiments, the textual indication may simply indicate that the request has been received, or provide details about the request (e.g., identification of other devices, specific restrictions associated with the request, user identification information). A visual indication is optionally selectable to display one or more options for approving or denying the request. The above-described method of displaying a visual indication of a request to change one or more usage limits of another device enables an electronic device to simultaneously present the request and usage metrics to provide a user with a usage setting for the other device. , thereby simplifying interaction between users and devices to enhance device usability (e.g., combining electronic devices and other devices within one user interface). (by presenting usage settings for the electronic device), as well as allowing the user to use the device more quickly and efficiently, thereby reducing power usage and improving the battery life of the device.

In some embodiments, the electronic device and one or more other electronic devices are associated 798-46 with a user group account (eg, family sharing group), as shown in FIG. 6B. In some embodiments, electronic devices associated with a user group account can share access to files (e.g., documents, photos, etc.) and applications (e.g., users within a user group account can access applications). If you purchase and download it, other electronic devices can download the application without separately purchasing it). A user group account optionally includes a parent user and a child user, wherein an electronic device associated with the parent user is configured to configure one or more settings (e.g., content, content, privacy, usage, and other settings). The usage settings user interface optionally includes one or more affordances (eg, selectable text or images) associated with one or more other electronic devices, as shown in FIGS. 6V-6W. (798-48), one or more affordances stop updating the dashboard user interface to display visual indications of usage metrics associated with the electronic device (798-50); and one or more visual representations of one or more usage metrics associated with other electronic devices associated with the selected affordance (e.g., one or more usage metrics associated with other electronic devices) Select to display indications (798-52) (e.g., present information on other electronic devices, receive notifications on other electronic devices, detect user attention events on other electronic devices, etc.) possible (eg, by touch input, mouse input, keyboard input, voice input, etc.). In some embodiments, parents view a dashboard user interface for each of their child's devices to monitor child device usage and set one or more usage limits (e.g., usage limits (e.g., "tolerances")). )) or set times for the child device to enter a restricted use mode (eg, device idle time or “bedtime”). The electronic device optionally determines which permissions (e.g. metrics to view and/or set usage limits and limited operating periods) should be given to each user account. In some embodiments, the electronic device displays usage metrics (e.g., total device usage or screen time) associated with each electronic device associated with the user group account in the settings user interface. Optionally, each parent device displays metrics associated with each of its child devices, but the child devices are optionally associated with any other device associated with the user group account. Without displaying metrics, the parent device optionally does not display metrics associated with electronic devices associated with other parent user account(s) associated with the user group account. The above-described method of displaying one or more metrics associated with other devices within a user group account enables an electronic device to provide easy access to usage information regarding multiple devices within a user group. , which simplifies interaction between users and devices to enhance device usability (e.g., a settings user interface that allows users to change one or more usage settings of other devices). ), in addition to reducing power usage and improving the battery life of the device by allowing the user to use the device more quickly and efficiently.

In some embodiments, the usage settings user interface deletes usage data about the electronic device (e.g., when presenting information, receiving notifications, detecting user attention events, etc.), as shown in FIG. 6A. (798-54), or data regarding device usage, such as number of times, and in some embodiments, resetting the usage metric of the electronic device by deleting all usage data (798-54). In some embodiments, the method receives 798-56 user input selecting selectable affordances to delete usage data at one or more input devices (e.g., affordances displayed receiving touches at locations on the touch screen, receiving affordance selections with mouse or keyboard input, etc.), and deleting usage data in response to receiving input (798-58). Including further. The above-described method of presenting an option to delete all usage data allows an electronic device to reset its usage metrics upon user request to do so, thereby allowing a enhances the usability of the device by simplifying the interaction of the It reduces power usage and improves device battery life by allowing it to be used quickly and efficiently.

In some embodiments, the usage settings user interface, as shown in FIG. 6A, uses usage data (e.g., times or times to present information, receive notifications, detect user attention events, etc.) about the electronic device. device usage) (798-60). In some embodiments, when data collection is stopped, usage metrics stop updating but are kept in their current state. In some embodiments, the method receives 798-62 user input selecting a selectable affordance to stop recording usage data with one or more input devices (eg, affordance receiving a touch at a location on a touchscreen where is displayed, receiving affordance selections with mouse or keyboard input, etc.) and recording usage data about the electronic device in response to receiving input (eg, with or without deleting all usage data) (798-64). The above-described method of presenting an option to stop recording usage data allows an electronic device to provide user control over which data is reflected in usage metrics, thereby allowing a enhances the usability of the device by simplifying the interaction of reduce power usage and improve device battery life by allowing

In some embodiments, the electronic device is used to set or change one or more usage settings of the electronic device, to display a dashboard user interface, or to control device usage, as shown in FIGS. 6Y-6CC. require authentication credentials (e.g., a passcode different from the passcode for unlocking the electronic device or the passcode for logging into the user account on the electronic device) to change settings associated with the electronic device (798- 66) (e.g., the electronic device receives, at one or more input devices, user input selecting a selectable affordance to require a passcode (e.g., at the location on the touch screen where the affordance was displayed) receive touch, receive affordance selection with mouse or keyboard input, etc.)). In some embodiments, in response to receiving input, the electronic device presents a user interface for setting a passcode (e.g., the electronic device prompts the user to enter a usage data passcode). and a soft keypad for entering a passcode). While a passcode is being requested (e.g., in response to setting or activating a passcode), the electronic device is optionally associated with device use with one or more input devices. receive user input to select one of the selectable affordances to display a settings user interface for changing the settings (e.g., touch at a location on the touch screen where the affordance was displayed); receiving affordance selections with mouse or keyboard input, etc.). In response to user input, the electronic device optionally presents a prompt to enter a passcode (e.g., displays or speaks a message indicating that a password is required to change settings relating to device usage). ). Optionally, the device displays a soft keypad through which the user can enter the password. Upon determination that the entered passcode matches the passcode (e.g., the user enters the correct passcode), the electronic device optionally has the capability to change one or more of the settings. Present a configuration user interface. Upon determination that the entered passcode does not match the passcode (e.g., the user enters an incorrect passcode), the electronic device optionally has the capability to change one or more of the settings. Forgo presenting a usage settings user interface (eg, without the correct passcode, the electronic device does not allow the user to change settings related to device usage). Optionally, the device presents an indication of the current settings (eg, an indication of one or more usage limits or periods during which the device will operate in restricted usage mode). The above-described method of presenting an option requiring a password to change one or more settings associated with device use prevents an electronic device from unauthorized modification of one or more settings associated with device use. , which simplifies interaction between the user and the device and enhances device usability (e.g. allowing changes to be made on the electronic device in response to the correct passcode). ), as well as reducing power usage and improving the battery life of the device by allowing the user to use the device more quickly and efficiently.

In some embodiments, the usage settings user interface includes settings associated with the content's parental guidance rating (e.g., access to content (e.g., applications, music, videos, etc.) having a particular parental guidance rating). One or more affordances (798-70) that can be selected to change the restrictive settings), and settings associated with data privacy (eg, specified types of data (eg, location , contacts, calendar data, tips, photos, wireless connection, microphone, etc. ). The above-described method of simultaneously displaying parental guidance settings and data privacy settings and usage settings enables electronic devices to present related settings within a shared user interface, thereby reducing communication between users and devices. By simplifying interactions and enhancing device usability (e.g., presenting similar settings together), as well as allowing users to use devices more quickly and efficiently, Reduce power usage and improve device battery life.

It is understood that the particular order described for the operations in FIGS. 7A-7S is exemplary only and is not intended to represent the only order in which the operations may be performed. want to be Those skilled in the art will recognize various methods for reordering the operations described herein. In addition, details of other processes described herein with respect to other methods described herein (eg, methods 900, 1100, 1300, and 1500) are also described above with respect to FIGS. Note that method 700 is also applicable in a similar fashion. For example, the usage metrics dashboard user interface, usage metrics, notification metrics, device pickup metrics, usage limit settings, etc. described above with reference to method 700 may optionally be implemented in addition to those described herein. usage metrics dashboard user interface, usage metrics, notification metrics, device pickup metrics, usage limit settings, as described herein with reference to methods (e.g., methods 900, 1100, 1300, and 1500) of have one or more of the following properties: For the sake of brevity, these details are not repeated here.

Operations in the information processing methods described above may be performed within an information processing device, such as a general-purpose processor (eg, as described in connection with FIGS. 1A-1B, 3, 5A-5H) or an application-specific chip. is optionally performed by activating one or more functional modules of Moreover, the operations described above with reference to FIGS. 7A-7S are optionally performed by the components shown in FIGS. 1A-1B. For example, the displaying operations 702, 798-30, and 798-38 and the receiving operations 714, 724, 798-56, and 798-62 optionally include the event sorter 170, the event recognizer 180, and the It is executed by the event processing unit 190 . Event monitor 171 of event sorter 170 detects contact on touch screen 504, and event dispatcher module 174 delivers event information to application 136-1. Each event recognizer 180 of application 136-1 compares the event information with respective event definitions 186 and determines that a first touch at a first location on the touch screen is a default event, such as selection of an object on the user interface. It determines whether it corresponds to the event or sub-event of . When the corresponding predefined event or sub-event is detected, the event recognizer 180 activates the event processor 190 associated with detection of the event or sub-event. Event handler 190 optionally utilizes or calls data updater 176 or object updater 177 to update application internal state 192 . In some embodiments, the event handler 190 accesses the corresponding GUI updater 178 to update what is displayed by the application. Likewise, it will be apparent to those skilled in the art how other processes may be implemented based on the components shown in FIGS. 1A-1B.
Application and Category Usage Limits

Users interact with electronic devices in many different ways, including using applications accessible on the devices. In some situations, it is difficult for users to monitor and limit usage of specific applications during specific time periods. Embodiments described below provide that the electronic device enforces a usage limit to reach a usage limit when a restriction criterion for a particular application or category of applications is met, such as reaching an application usage limit associated with a particular application. It determines that it has been reached and thereby provides a way to restrict the user's use of the particular application that the user wishes to restrict. Setting usage limits on the electronic device for specific applications or categories of applications allows the electronic device to effectively limit the user's use of certain device operations and allows the user to do so. Provides an easy way to set usage limits, which makes device usage more efficient (e.g., users do not need to monitor their own device usage, and therefore have access to user-provided reduce input to the device (eg, input to otherwise monitor user usage); For example, the understanding that a usage limit has been set allows the user to use the restricted behavior more wisely and efficiently to perform all necessary tasks under the usage limit. If the usage limit has been reached, the device restricts the user from using restricted actions, thereby preventing the user from unknowingly exceeding the usage limit and spending more time on the device than intended. Preventing, as well as allowing users to use the device more quickly and efficiently, reduces power usage and improves the battery life of the device. It is understood that people use devices. When a person uses a device, that person is optionally called the user of that device.

FIGS. 8A-8NNN illustrate exemplary methods by which usage limits are set, configured, or enforced on an electronic device, according to some embodiments of the present disclosure. The embodiments in these figures are used to illustrate the processes described below, including the processes described with reference to Figures 9A-9K.

FIG. 8A shows an exemplary device 500 having a touch screen 504 as described with reference to FIGS. 5A-5H. Touch screen 504 optionally displays one or more user interfaces including various content. In the example shown in FIG. 8A, touch screen 504 indicates that one or more users associated with a limited use mode on device 500 whose limit criteria have not been met (e.g., user-defined usage limits have not been reached). display the home screen 802 at times other than the time windows defined by . In some embodiments, the restriction criteria are met when the usage limit for a given application or category of applications is reached, as described below. 8A, home screen 802 displays icons 424, 426, 428, 432, 434, 436 for launching or otherwise displaying different applications on device 500, as described above with reference to FIG. 4A. , 440, 442, 444, 448, and 450.

8B-8T illustrate exemplary methods of setting and defining usage limits on device 500 according to embodiments of the present disclosure. In FIG. 8B, a touch object (eg, a user's finger, stylus, hovering input object, hovering input device, etc.) selects settings application 446 from home screen 802 (eg, by providing contact 803). It is understood that contact 803 and interaction between contact 803 and the settings application icon are merely exemplary. Although specific GUI objects and text are shown in these figures, it is understood that the illustrated GUIs are not limiting. The disclosed method can be performed by displaying GUI objects and text different from those shown without departing from the scope of this disclosure.

In FIG. 8C, a settings user interface is displayed in response to selection of the settings application and contact 803 selects (eg, by tapping) an affordance associated with digital health settings 804 . Upon selection of Digital Health Affordance 804, a message 806 is displayed on the electronic device asking if the user would like to perform an initial usage limit setup (e.g., usage limit not yet on device 500), as shown in FIG. 8D. not set up). Message 806 includes affordances to perform usage limit setup (eg, 'continue' 808a) and affordances to forgo usage limit setup (eg, 'later' 808b). The user proceeds with usage limit setup at 803 by selecting "Continue" 808a. In some embodiments, the user optionally does not continue with the message 806 (e.g., by returning to the home screen 802 by selecting "Later" 808b) to complete the initial usage limit setup. put off

FIG. 8E shows an exemplary restricted use mode setup user interface optionally displayed by device 500 in response to selecting "Continue" 808a in FIG. 8D. In some embodiments, the restricted usage mode setup user interface of FIG. 8E is displayed while performing the initial usage limit setup. For example, as described in more detail below with reference to FIGS. 10A-10AAA and FIGS. 11A-11I, one or more time windows associated with the restricted use mode are optionally First set up in the setup user interface. After initial setup of the limited use mode is complete, the user proceeds to initial use limit setup by selecting "Yes" 810a (eg, via contact 803). In some examples, the limited use mode is optionally not set up prior to the initial usage limit setup (e.g., by returning to home screen 802 by selecting "No" 810b, any by not associating a time window with the limit usage mode). Details of the restricted use mode are described in greater detail below with reference to FIGS. 10A-10AAA and FIGS. 11A-11I. Any of the limited use mode features described in this disclosure may optionally be implemented in combination with any use limit features described herein without departing from the scope of the present disclosure. understood.

FIG. 8F is an exemplary usage limit setup user interface for setting usage limits for one or more applications or categories, optionally displayed by device 500 in response to selecting "yes" 810a in FIG. 8E. 812 is shown. The exemplary usage limit setup user interface displays multiple selectable application categories (e.g., "All Apps and Categories" 814a, "News" 814b, "Games" 814c, "Mail" 814d, "Social Media" 814e). , "streaming" 814f). In some embodiments, the setup user interface includes selectable applications that allow the user to set usage limits for individual applications. In this manner, a user can select one or more categories of applications, or one or more individual applications, that the user wishes to restrict usage to.

In FIG. 8F, exemplary applications associated with each category of applications are displayed under their respective corresponding categories (e.g., "Social App A", "Social App A", "Social App B", "Social App C"). In some embodiments, the user can set usage limits for all applications and categories on the electronic device by selecting "All apps and categories" 814a (e.g., total "screen time" limit). In some embodiments, the user can set usage limits for the applications and categories of applications that the user selects. The user forgoes the initial usage limit setup by leaving the setup user interface (e.g., by selecting "Abort" 816b, returning to home screen 802, by not selecting any applications or categories). be able to.

Although the usage limit setup user interface is accessed as shown, the usage limit setup user interface is optionally accessible differently than the illustrated embodiment without departing from the scope of the present disclosure. It is understood. Although specific applications and categories are shown in the figure, the specific applications and categories are merely exemplary and different applications or categories are optional on the usage limit setup user interface without departing from the scope of this disclosure. is understood to appear in

Figures 8G-8J illustrate exemplary methods of selecting a category of applications and selecting applications associated with the selected category that the user wishes to restrict use. In FIG. 8G, the user selects (eg, via contact 803) a category of applications (eg, social media category 814e to set usage limits for that category). In some situations, a user selects more than one category of applications to set usage limits for those combined categories or to set usage limits for each of those categories. . In some examples, the user does not select an application category. In some examples, selecting "All apps and categories" optionally selects all applications and categories of applications on the electronic device.

In FIG. 8H, a category usage limit setup user interface 818 is displayed in response to selection of a category of application (eg, social media category). As shown, all applications (eg, social applications AE 820a-820e) associated with the currently selected category are displayed and selected by default. In some embodiments, none of the applications are selected. The user selects applications in the currently selected category to be restricted. As illustrated, selection (eg, by contact 803) of a selected application (eg, social media application B 820b) deselects a previously selected application (eg, social application B 820b using contact 803). by deselecting B 820b). that although checkmarks are used to indicate selection of particular GUI objects, other methods of indication selection (e.g., highlighting, cursors) may be used without departing from the scope of this disclosure; is understood.

In FIG. 8I, social media application B 820b is deselected in response to the selection of previously selected social application B 820b. In some embodiments, access to deselected applications is provided even after the usage limit associated with the category to which the application belongs is reached (e.g., deselected applications are described in more detail below). (because it is a "whitelist" application that Deselecting an application (eg, social media application B 820b) optionally causes it to be unrestricted by the corresponding usage limit (eg, usage limit for the social media category). That is, the whitelisted application (eg, social media application B 820b) is optionally accessible after reaching the usage limit (eg, social media category) associated with the whitelisted application.

In some embodiments, use of a non-whitelisted application counts towards the usage limit associated with that application. For example, social media application A 820a is optionally selected on the usage limit setup user interface 818 of FIG. 8I. Access to social media application A 820a is optionally restricted after the usage limit for the social media category is reached. Prior to reaching the usage limit for the social media category, use of social media application A optionally tallies toward the usage limit for the social media category.

In FIG. 8I, the desired set of applications (eg, social media applications A 820a and C-E 820c-820e) are selected and restricted (eg, selected access to applications of the selected set of applications is restricted after reaching the usage limit associated with the associated category), the user may confirm the set of applications (e.g., at contact 803 " Proceed to the next setup user interface by selecting Done" 822).

In FIG. 8J, usage limit setup user interface 812, optionally displayed by device 500 in response to selecting “Done” 822 in FIG. 8I, is selected to implement with one or more corresponding usage limits. (eg, social media 814e). After the desired settings for the applications to be restricted to the social media category have been selected, the applications displayed under the social media category are updated to the category usage setup, as shown in FIG. 8J. Display some or all of the applications selected on the user interface 818 . In some embodiments, if the name of the selected application exceeds the amount of space under the category, some of the selected applications are displayed, followed by "others." Applications displayed under other categories (eg, unselected categories) are optionally not updated. Once all desired applications and categories have been selected and implemented with one or more corresponding usage limits, the user proceeds to the next user interface (e.g., selecting "Add" using contact 803). by).

Figures 8K-8M illustrate an exemplary method of setting usage limits associated with a category. The user can set different usage limits that will be enforced at different times for applications or categories of applications. For example, as shown in FIG. 8K, category usage limit customization user interface 824 is displayed by device 500 in response to selecting "Add" 816a in FIG. 8K. A notify and block option 828 a and a notify option 828 b are also displayed on the category usage limit customization user interface 824 . The method of implementing usage limits in the "notify" and "notify and block" modes is described in more detail below with reference to FIGS. 8NN-8WW. Although notification option 828b is shown selected, it is understood that the user can select either option for their respective usage limits. A default usage limit (eg, "2 hours") associated with the category usage limit is displayed. In some embodiments, the default usage limit is automatically determined by the electronic device. The user can optionally customize usage limits (eg, usage limits different from the default usage limits) for different days by selecting “Customize Days” 826 on the user interface.

In FIG. 8K, selection of “customize day” by contact 803 is detected and in response device 500 displays a usage limit customization user interface, as shown in FIG. 8L. As shown in FIG. 8L, different usage limits (eg, 1 hour) are defined for different days of the week (eg, Monday 836b, Wednesday 836d, and Thursday 836e). Although different days of a week are shown, it is understood that custom usage limits are optionally defined for any period of time. After the customized usage limits are defined, the user selects "Done" 838 to proceed to the next user interface.

FIG. 8M shows a category usage limit customization user interface 824 that is displayed after customized usage limits have been set up (eg, after selecting “Done” 838 in FIG. 8L). After the customized usage limit is set up, under "Customize Days" 826, the time period for which the customized usage limit will be in effect is displayed. If the user selects "Add" 830, the customized usage limit is added to the social media category usage limit settings. For example, as shown in Figure 8M, a one hour usage limit is enforced on Mondays, Wednesdays, and Thursdays. A default usage limit of 2 hours is enforced on Sunday, Tuesday, Friday and Saturday.

After setting the usage limit in FIG. 8M, the device 500 optionally displays a digital health passcode setup user interface 840 to ensure the usage limit has been set, as shown in FIG. 8N. indicate. In some embodiments, after the initial usage limit settings have been set, the electronic device displays a digital health passcode setup user interface 840 to set the digital health settings (e.g., use Prompt the user to enter the passcode associated with the limit settings). In some embodiments, the passcode is the electronic device general passcode to prevent unauthorized access to digital health settings on device 500 (e.g., by a child who knows the parent's device passcode). (e.g., commonly the passcode to unlock the device). Although the illustration prompts for a four-digit numeric passcode, it is understood that different types of authentication credentials are optionally used to secure Digital Health settings (e.g., an alphanumeric password , biometric authentication, etc.).

After completing the initial usage limit settings, a limit setting user interface 844 is displayed, as shown in FIG. 8O. Limit setting user interface 844 is described in more detail with reference to FIGS. 6A-6UU and FIGS. 7A-7S. Usage of applications within the category associated with the usage limit is optionally indicated on usage bar 848 . Categories that have usage limits associated with them (eg, “Social Media”) are displayed under “App Limits” 846 . For example, in FIG. 8O there is no use of the social media category, so use bar 848 indicates that no applications in the social media category are being used. Selection of "App Limits" 846 optionally causes display of the Application Limits user interface of FIG. 8P, which allows the application usage limit settings to be changed.

FIG. 8P shows an application limits user interface 850. FIG. Usage limits categories added during initial setup (eg, "Social Media" 852a) are displayed on the application limits user interface 850 of FIG. 8P. Customized usage limits and their associated time periods are displayed under "Social Media" 852a. The user interface also includes an app limit toggle switch 856 . As shown, the electronic device enforces the defined usage limits when the button is toggled "on." Conversely, the electronic device does not enforce defined usage limits when the button is toggled "off." In some embodiments, when the electronic device does not enforce the defined usage limits, the defined usage limits are retained and stored, but are not enforced. The defined usage limits will optionally be enforced upon subsequent activation of the application limits (eg, by toggling the app limits toggle switch 856 "on"). In some embodiments, application usage may result in reactivation of application limits (e.g., toggling app limits toggle switch 856 "off" for a period of time and then toggling app limits toggle switch 856 "on"). (eg, the application usage contribution is not reset for subsequent activations of the application limit). In some embodiments, application usage is not tracked and retained during reactivation of the application limit (eg, the application usage contribution is reset for subsequent activations of the application limit). The user can add more application or category usage limits by selecting "Add Limit" 854, as shown in Figure 8P. In some examples, selecting “add limit 854 ” optionally causes the electronic device to display a user interface similar to usage limit setup user interface 812 . For the sake of brevity, it is understood that adding one or more application or category usage limits is similar to that described in FIGS. 8F-8M.

FIG. 8Q shows additional application usage limits (e.g., "Game A" 852c and "Streaming App B" 852g) and category usage limits (e.g., "All" 852b, "Games" 852d, "Streaming" 852e, "Streaming and 852f) shows usage limits user interface 850 after "Social Media" 852f) has been added. "All" 852b is the electronic device's overall usage limit (eg, overall "screen time" limit) associated with all applications and categories on the electronic device. "Streaming and Social Media" 852f is a combined category usage limit. Joint category usage limits enforce the use of applications associated with joint categories. For example, the use of streaming or social media applications is optionally enforced by the combined "streaming and social media" usage limit 852f.

The electronic device optionally enforces concurrent usage limits. For example, the user sets up concurrent usage limits "Social Media" 852a and "Streaming and Social Media" 852f on the electronic device, as shown. In some embodiments, use of the social media application associated with the usage limit (eg, social media application A) contributes to both concurrent usage limits. In some embodiments, more conservative limits for concurrent usage limits are enforced. For example, if 2 hours remain for the social media usage limit and 3 hours remain for the streaming and social media usage limit, use of the social media application is optionally more conservative. Limited by the social media usage limit (ie, after 2 hours of use of the social media application). As another example, if two hours remain on the social media usage limit and one hour remains on the streaming and social media usage limit, use of the social media application optionally includes: Limited by more conservative streaming and social media usage limits (ie, after 1 hour of social media application usage).

FIG. 8R shows a category usage limit setting user interface 858 . The category usage limit setup user interface 858 includes information substantially similar to the information displayed in the category usage limit setup user interface 818 of FIGS. 8H-8I. Applications previously selected during usage limit setup (eg, social media applications A 820a and C-E 820c-820e) are displayed on user interface 858 . In some embodiments, the user redefines the applications to be restricted by selecting or deselecting applications on the category usage limit setting user interface 858 . The user changes the name 860 (e.g., "Social Media") of the category usage limit by selecting "Rename" 862, as shown in FIG. As shown in 8T, this results in a renaming of the social media category limit.

Specifically, in FIG. 8S, in response to changing the category usage limit name 860 (e.g., from "Social Media" to "John's Fun Things"), the updated name is displayed on the user interface 858. be done. After the desired updates to the category usage limit settings have been performed, the user may save the updated settings and select "Done" 822 to display the application limits user interface 850 as shown in FIG. 8T. return. FIG. 8T shows the application limit user interface 850 after the category usage limit setting has been updated. In response to renaming the previous social media category 852a to "John's Fun Things", the application limit user interface 850 displays the updated name of the category 852a (e.g., "John's Fun Things"). .

FIGS. 8U-8EE illustrate exemplary methods of displaying representations of applications subject to various constraints, according to embodiments of the present disclosure.

In FIG. 8U, touch screen 504 displays home screen 802 when restriction criteria are not met on device 500 (eg, the usage limit for any application or category of applications has not been reached). In some embodiments, the limit criterion is met when the usage limit for a given application or category of applications has been reached. In some embodiments, usage restriction criteria are met during one or more time windows associated with the restricted usage mode, as described with reference to method 1100 . 8U, home screen 802 displays application icons 424, 426, 428, 432, 434, 436, 440 for launching or otherwise displaying different applications on device 500, as described above in FIG. 4A. (eg, associated with social media application A), 442 (eg, associated with social media application B), 446, 448, 450, and 452. As shown in FIG. 8U, one or more application icons optionally include notification indicators 864 that notify the user of any unread notifications associated with the application. For example, notification indicator 864 in FIG. 8U indicates that social media application A 440 has three unread messages. In some embodiments, notification indicator 864 is a badge superimposed over (or partially over) the appropriate icon, as shown in FIG. 8U.

8V-8W, a horizontal swipe of contact 803 is detected on touchscreen 504 while home screen 802 is displayed, causing a limit criterion to be not met on device 500 (e.g., usage limit reached). cause device 500 to display search user interface 866 when not in use). Search user interface 866 optionally searches for content accessible from device 500 (e.g., websites, news, email, applications installed on device 500, applications available for download to device 500, Calendar items, etc.) is the operating system user interface of device 500 . A search user interface 866, as shown in FIG. 8W, optionally includes a text field 868 for entering one or more search terms to search for content accessible from device 500, which the operating system of device 500 provides to the user. "App Suggestions" user interface 870a for displaying applications suggested to the device 500 (e.g., suggesting commonly used applications, recently used applications, favorite applications, currently running applications), as well as device 500 Widgets 870b and 870c corresponding to applications installed thereon (e.g., text, image(s), and/or any other content associated and updated by corresponding applications such as social media applications A and B) (including user interface objects or windows). As shown in FIG. 8W, social media applications A and B are included in the “App Suggestions” and their corresponding widgets are displayed on the device 500 if the restriction criteria associated with those applications are not met on the device 500 . 500.

In FIG. 8X, the user has entered the search term “social media” into text field 868 when the restriction criteria are not met on device 500 (eg, the usage limit has not been reached). In response to the search term "social media" entered into text field 868, device 500 displays various search results related to the search term "social media" in search user interface 866, as shown in FIG. 8X. For example, the device 500 provides a link 874a to the social media application "Social App A" installed on the device 500, a link 874b to the social media website "Social App A", which is a website about the "Social App A" app. , and links to two social media applications available for download from the application storage location (e.g., App Store), link 874c to "Social App F" and link 874d to "Social App G" application. indicate.

FIG. 8Y shows home screen 802 displayed on device 500 when the social media category usage limit has been reached. In response to reaching the social media category usage limit, the appearance of the social media application A icon 440 is updated to reflect that access to the application is restricted (e.g., the icon is grayed out). Overlaid on the icon is a restriction badge 876 that optionally replaces the previously displayed notification badge). In some embodiments, the restricted badge 876 is at least partially superimposed on the social media application A icon 440, as shown in FIG. 8Y. In some embodiments, the restricted badge 876 is at least partially overlaid on the text description associated with the icon of the restricted application.

8Y-8Z, a vertical swipe of contact 803 is detected on touch screen 504 while home screen 802 is displayed, which satisfies the restriction criteria on device 500 (e.g., social media category use limit reached), cause device 500 to display notification history user interface 878 of FIG. 8Z. Notification history user interface 878 includes notifications 880a-b associated with notifications of applications on the device. In some embodiments, upon determining that the usage limit has been reached, the appearance of the notification for the application associated with the usage limit is updated (e.g., the notification is grayed out) and the associated application is restricted. In some embodiments, notifications with updated appearances are not selectable. In some embodiments, notifications for applications associated with the usage limit are not displayed (eg, suppressed) on the notification history user interface 878 in response to the determination that the usage limit has been reached. When one or more notifications are suppressed on notification history user interface 878, electronic device 500 optionally displays one or more notifications associated with non-restricted applications instead of notifications associated with restricted applications. Show notifications for For example, in FIG. 8Z, notification 880a associated with social media application A is grayed out (or optionally not displayed) in response to device 500's determination that the social media usage limit category has been reached, but music Notification 800b associated with the application indicates that access to the music application is unrestricted.

Such changes in display of representations associated with restricted applications are also made by device 500 in other user interfaces. For example, in FIGS. 8AA-8BB, a horizontal swipe of contact 803 is detected on touchscreen 504 while home screen 802 is displayed, which satisfies a restriction criterion on device 500 (e.g., social media cause the device 500 to display the search user interface 866 of FIG. 8BB when the category usage limit has been reached. Search user interface 866 is substantially similar to the user interface described in FIGS. 8V-8W.

"App Suggestions" user interface 870a displays applications suggested to the user by the operating system of device 500 (e.g., commonly used applications, recently used applications, favorite applications, currently running applications). do). In some embodiments, when a usage limit (e.g., social media category usage limit) is reached, the appearance of the restricted proposed applications is updated to indicate their restriction status (e.g., icon greyed out, social media application A icon 440 greyed out). In some embodiments, once the usage limit has been reached, the applications associated with the usage limit do not appear on the “App Suggestions” user interface 870a, and in some embodiments, the limit criteria are met. not replaced by representations of other applications.

In some embodiments, when the usage limit (e.g., social media category usage limit) is reached, the appearance of the widget corresponding to the application associated with the usage limit is updated, as shown in FIG. 8BB. , indicating their restricted state (eg, widget greyed out, widget 870b corresponding to social media application A greyed out). In some embodiments, when the usage limit is reached, widgets corresponding to applications associated with the usage limit do not appear on search user interface 866 . When an application icon or widget is suppressed on search user interface 866, electronic device 500 optionally displays one or more other icons associated with non-restricted applications instead of notifications associated with restricted applications. Or display a widget. For example, in FIG. 8BB, widget 870b associated with social media application A is grayed out (or optionally not displayed), but is white in response to device 500's determination that the social media usage limit category has been reached. Widget 870c associated with list social media application B (eg, applications not selected on usage limit setup user interface 818 of FIG. 8I) indicates that access to social media application B is unrestricted.

In FIG. 8CC, the user has entered the search term “social media” into text field 868 when restriction criteria are met on device 500 (eg, social media category usage limit is reached). In response to the search term “social media” entered into text field 868, device 500 displays various search results related to the search term “social media” in search user interface 866. FIG. During this time, access to applications associated with reaching usage limits is restricted. For example, when the social media category usage limit is reached, the device 500 has an updated look to the social media application “Social App A” installed on the device 500 (e.g., social media application A’s icon greyed out), link 874a has an updated appearance to the social media website "Social App A", which is the website for the "Social App A" app (e.g., social media application A icon greyed out). display link 874b. In some embodiments, the appearance of the updated link is that social media application A and the social media website corresponding to social media application A are Indicates that it is restricted. In some embodiments, restricted social media category applications (e.g., non-whitelist social media category applications, social media applications A and C-E) are not displayed in search results once the social media category usage limit has been reached. does not appear in When one or more links are suppressed on search user interface 866, electronic device 500 optionally displays one or more other links associated with non-restricted applications instead of notifications associated with restricted applications. Show link. For example, in FIG. 8CC, link 874b associated with social media application A is grayed out (or optionally not displayed) in response to the device 500's determination that the social media usage limit category has been reached, but the installation Links 874c associated with social media application F and social media application G that are not licensed indicate that installation of these applications is not restricted.

FIG. 8DD shows a web browser user interface 882 on device 500 where the restriction criteria are met (eg, the social media category usage limit has been reached). As shown, a user attempts to access a website corresponding to social media application A (eg, "www.socmeda.com"). In some embodiments, in response to an attempt to access a social media website while reaching the social media category usage limit, as shown in FIG. 8DD, content 882-4 of web browser user interface 882: A message hidden from the user by the device 500 and displayed by the device 500 notifies the user that the social media usage limit has been reached. In some embodiments, once the usage limit has been reached, any aspect of the website corresponding to the application associated with the usage limit (e.g., pages with the same home page URL) is restricted to the user. be.

FIG. 8EE shows another web browser user interface 882 in which a restriction criterion is met (eg, social media category usage limit reached) on device 500 . As shown, a user attempts to access a website corresponding to social media application A (eg, "www.socmeda.com"). In some embodiments, in response to an attempt to access a social media website while the social media category usage limit has been reached, website content 882-4 is displayed by the device 500 to the user's social media usage limit. is superimposed with message 882-6 notifying that it has reached Once the social media category usage limit has been reached, the appearance of user interface objects (eg, social media application icon A, images 1 and 2) on content 882-4, as shown in FIG. , is updated (eg, the user interface object is grayed out) to indicate that access to the website is restricted. In some embodiments, once the usage limit has been reached, any aspect of the website corresponding to the application associated with the usage limit (e.g., pages with the same home page URL) is restricted to the user. be.

8FF-8HH illustrate an exemplary method of installing an application on device 500 in situations where restriction criteria for categories associated with the application are met.

FIG. 8FF shows the home screen 802 when the social media category usage limit has been reached. In response to reaching the social media category usage limit, the appearance of the social media application A icon 440 is updated to reflect that access to the application is restricted (e.g., the icon is grayed out). A restricted badge 876 is superimposed on the icon). As shown, the user selects the App Store icon 448 to go to the App Store.

FIG. 8GG shows the App Store user interface 884 . App Store user interface 884 is displayed in response to selection of App Store icon 448 . As shown, the user selects a link 886 (eg, "Get") associated with social media application F to add (eg, download, install) the application to the electronic device. In some embodiments, based on App Store attributes or application metadata, social media application F is associated with social media category usage limits.

FIG. 8HH shows the home screen 802 when the social media category usage limit has been reached. In response to adding social media application F from the App Store, icon 452 for social media application F is added to home screen 802 . Since it is determined that the social media category usage limit has been reached and social media application F is associated with the social media category usage limit, icon 452 for social media application F reflects that the application is restricted. (eg, icon grayed out, restricted badge 876b overlaid on icon).

FIGS. 8II-8KK are illustrative examples of restricting access to applications according to a determination that an electronic device is in a restricted use mode (eg, described in more detail with reference to FIGS. 10A-10AAA and method 1100). show you how.

FIG. 8II shows the home screen 802 when the usage limit has not yet been reached. In FIG. 8JJ, a message 888 (eg, notification) is presented and overlaid on home screen 802 . Message 888 indicates that the limited use mode (eg, device idle time) will begin in 5 minutes. Message 888 stops displaying if the user selects "Dismiss" on the message. In some embodiments, without the "dismiss" option, the message automatically stops displaying after a certain period of time (eg, 5 seconds, 30 seconds, or 1 minute).

FIG. 8KK shows the home screen 802 when bedtime restrictions (eg, restricted use mode) are in place, but application usage limits have not been reached. For example, FIG. 8KK optionally shows home screen 802 more than five minutes after message 888 was presented. When a bedtime restriction is in effect, the applications selected to be restricted by the bedtime restriction are restricted. In some embodiments, when bedtime restrictions are in force, access to restricted applications is restricted even if usage limits for those applications have not been reached. For example, when bedtime restrictions are optionally in effect, the social media category usage limit has two hours left. Bedtime restrictions optionally override usage limit settings. That is, when bedtime restrictions are in force, social media category applications and any other non-whitelist applications are restricted even when social media category (or other) usage limits have not been reached. The appearance of the restricted application's icon is updated (e.g., icon grayed out, restricted badge 876 superimposed on icon) to indicate that the application is restricted (e.g., Social Media Application A 440, Social Media application B 442, messenger application 424, music application 450).

Figures 8LL-8PP illustrate an exemplary method of presenting an indication that access to an application is restricted and providing access to the application.

FIG. 8LL shows device 500 displaying home screen 802 when the usage limit has not been reached. FIG. 8MM shows the device 500 displaying the home screen 802 when the usage limit (eg, social media category usage limit) is reached, under the "notification" option of usage limit settings. In some embodiments, the "notification" option is set on the category usage limit customization user interface 824, see FIG. 8M. The appearance of the application icon (e.g., Social Media Application A 440) associated with the restriction is updated to indicate that the application is restricted (e.g., icon greyed out, restriction badge 876 superimposed on icon). . As shown, the user attempts to launch social media application A by selecting social media application A icon 440 in FIG. 8MM.

In response to an attempt to launch a restricted application (e.g. access to the application is restricted if the usage limit has been reached), device 500 optionally activates the restricted application as shown in FIG. The notification user interface 890 visually obscures the home screen 802 (eg, blurs, grays out, or visually alters the home screen). Although the limit notification user interface 890 is displayed in response to an action (e.g., launching an application from the home screen) when the home screen is displayed, the notification user interface 890 is displayed when the usage limit has been reached. It is understood that it can be displayed on top of any content currently displayed by the device (eg, the user interface of an application). In some embodiments, device 500 displays explanation 890-1 indicating that the usage limit associated with the selected application has been reached. In some embodiments, description 890-1 includes a visual indication (eg, an empty hourglass) to communicate to the user that the limit has been reached, as shown in FIG. 8NN. Restriction notification user interface 890 also optionally includes a plurality of icons 890-2. Plurality of icons 890-2 includes application icons (eg, social media applications A and C through E) associated with usage limits reached (eg, social media category usage limits). If the usage limit reached was associated with only a single application, user interface 890 will optionally only include an icon for that single application.

The restriction notification user interface 890 of FIG. 8NN includes a “dismiss” affordance 892 . In FIG. 8NN, selection of dismissal affordance 892 is detected (eg, by contact 803 detected on dismissal affordance 892). In response to selecting dismiss affordance 892, device 500 stops displaying dismiss affordance 892 on limit notification user interface 890 and displays extend affordance 894 and ignore affordance 896, as shown in FIG. 8OO. do.

In some embodiments, the user selects an extended affordance 894 to allow the user to Able to access restricted applications beyond application usage limits (so that previously defined usage limits continue to be enforced in future days without changing the actual time set for usage limits) ) (eg, as described below with reference to method 900). In some embodiments, the user can opt out of enforcing the usage limit for that particular day by selecting the ignore affordance 896 (change the actual time set for the usage limit). (for example, as described below with reference to method 900), so that the previously defined usage limits continue to be enforced in future days. In some embodiments, device 500 returns to home screen 802 after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds) or when the user returns to home screen 802 (e.g., any portion of restriction notification user interface 890 (description 890-1, extending affordance 894, and ignoring affordance 896) by selecting the electronic device's home button) and displaying extend affordance 894 and ignoring affordance 896; to stop.

According to the "Notify" option, a parent device (e.g., a device associated with a parent on a family account) or a device not associated with a family account at all (e.g., a standalone device) can optionally notify the user of its Do not require entering any authentication (eg, passcode, biometric authentication) to extend or bypass usage limits on the device. As such, upon selection of extend affordance 894 or ignore affordance 896 of FIG. 8OO, limit notification user interface 890 ceases to display and the selected application's user interface is displayed. The user has unrestricted access to the application associated with the extended usage limit for the amount of time defined by the affordance selection (eg, 15 minutes, rest of the day). When the usage limit is extended or ignored, all other aspects of the application associated with the usage limit (e.g., any of the restricted user interface objects described above) are also extended or ignored. . For example, a user may view or interact with widgets, notifications, and web pages corresponding to applications associated with extended or ignored usage limits. For example, as shown in FIG. 8PP, upon selection of the extended affordance of FIG. 8OO, the restriction notification user interface 890 stops displaying and the social media application A user interface 898 is displayed. After the restricted notification user interface 890 stops displaying, the user has an additional 15 minutes of social media category usage time. In some embodiments, after the restricted notification user interface 890 stops displaying and before accessing the selected application, a graphical user interface (e.g., hourglass 890-1 that flips and starts moving again) is displayed. A reset hourglass, such as an animation, is presented on the display to indicate that its usage limit has been extended. In some embodiments, usage of an application associated with a reached usage limit is tracked beyond the reached limit (eg, by extending, ignoring for the rest of the day). For example, the social media category usage limit is optionally two hours. Upon reaching the social media category usage limit, the user optionally extends social media usage beyond the usage limit. A user's social media usage exceeding the two hour limit is optionally tracked by the device.

FIGS. 8QQ-8UU illustrate an exemplary method of presenting an indication that access to an application is restricted and providing access to that application on a parentally controlled child device using local authentication. indicates

FIG. 8QQ shows parental controlled device 500A displaying home screen 802 when the usage limit has not been reached. FIG. 8RR shows the device 500 displaying the home screen 802 when the usage limit (eg, social media category usage limit) is reached under the “notify and block” option of the usage limit settings. In some embodiments, the "notify and block" option is set on the category usage limit customization user interface 824, see FIG. 8M. The appearance of the application icon (e.g., Social Media Application A 440) associated with the restriction is updated to indicate that the application is restricted (e.g., icon greyed out, restriction badge 876 superimposed on icon). . As shown, the user attempts to launch social media application A by selecting social media application A icon 440 in FIG. 8RR.

In response to an attempt to launch a restricted application (e.g. access to the application is restricted if the usage limit has been reached), device 500A optionally activates the restricted application as shown in FIG. The notification user interface 890 visually obscures the home screen 802 (eg, blurs, grays out, or visually alters the home screen). The restriction notification user interface 890 is substantially similar to the user interface described in FIG. 8NN.

At FIG. 8SS, selection of dismissal affordance 892 is detected (eg, by contact 803 detected on dismissal affordance 892). In response to selection of dismissal affordance 892, device 500A stops displaying dismissal affordance 892 on restriction notification user interface 890 and provides local authentication request affordance 898-2 and remote authentication request affordance 898-2, as shown in FIG. 8TT. Display affordance 898-4.

Under the "notify and block" option, parental controlled child devices (e.g. devices associated with a child on a family account) may be authorized to extend or bypass usage limits on that device (e.g. , local authentication on the device (eg passcode, biometric authentication), remote authentication from a different device (eg parent device)). For example, as shown in FIG. 8TT, the user selects local authentication request affordance 898-2 to local authenticate the desired extension of social media usage limits (eg, authentication on parental controlled child device 500A). request.

As shown in FIG. 8UU, in response to selection of local authentication request affordance 898-2 of FIG. Prompt for input. Although the illustration prompts for a four-digit numeric passcode, it is understood that different types of authentication credentials are optionally used to secure Digital Health settings (e.g., an alphanumeric password , biometric authentication, etc.). In some embodiments, the authenticating passcode for extending or overriding the usage limit is different than the electronic device's passcode to prevent unauthorized extension of the usage limit. For example, the authenticating passcode is optionally a digital health passcode, see FIG. 8N. In some embodiments, upon correctly entered authentication (e.g., correct passcode), the user is granted additional access to selected applications beyond the usage limit (e.g., 15 minutes, 1 day rest). When the usage limit is extended or ignored, all other aspects of the application associated with the usage limit (e.g., any of the restricted user interface objects described above) are also extended or ignored. . For example, a user may view or interact with widgets, notifications, and web pages corresponding to applications associated with extended or ignored usage limits.

After the request to extend usage beyond the usage limit has been authenticated, the electronic device displays the electronic device under the "notify" option after the usage limit has been extended, as described in FIG. 8PP and its corresponding description. works in substantially the same way as

Figures 8VV-8YY illustrate an exemplary method of presenting an indication that access to an application is restricted and providing access to that application based on authentication credentials from a parent device.

In response to an attempt to launch a restricted application (e.g. access to the application is restricted if the usage limit has been reached), as similarly shown in FIGS. 8QQ and 8RR and their corresponding descriptions: Child device 500A optionally visually obscures home screen 802 (e.g., blurs, grays out, or visually (changed automatically). The restriction notification user interface 890 is substantially similar to the user interface described in FIG. 8NN.

In FIG. 8VV, selection of dismissal affordance 892 is detected (eg, by touch 803 detected on dismissal affordance 892). In response to selection of dismissal affordance 892, device 500A stops displaying dismissal affordance 892 on restriction notification user interface 890 and displays local authentication request affordance 898-2 and remote authentication request affordance 898-2, as shown in FIG. 8WW. Display affordance 898-4.

Under the "notify and block" option, child devices (e.g. devices associated with a child on a family account) can be authenticated to extend or bypass usage limits on that device (e.g. local Require the user to enter authentication (eg, passcode, biometric authentication), remote authentication from a different device (eg, parent device). For example, as shown in FIG. 8WW, the user selects remote authentication request affordance 898-4 to request remote authentication (eg, authentication on parent device 500B) of the desired extension of social media usage limits.

For example, as shown in FIG. 8XX, in response to selection of remote authentication request affordance 898-2 on child device 500A of FIG. displayed on device 500B. As shown in FIG. 8BB, in some embodiments, the message 898-6 indicates that the usage limit (eg, social media category) on the child device (eg, John Jr.'s device) has been reached and that the child Notify the parent user that the user has requested additional usage beyond the usage limit. Multiple extension affordances 898-8a through 898-8d provide the parent user with different usage limit extension options (e.g., extend by 15 minutes, extend for the rest of the day, customize extension, request for extension). refuse). The extension option selected applies to child device 500A. For example, as shown in FIG. 8XX, the parent user selects extended affordance 898-8a to give the requesting child user an additional 15 minutes over the usage limit.

In some embodiments, upon selection of one of extended affordances 898-8a through 898-8d, passcode entry user interface 842 prompts the allowing user (eg, parent) to Prompts to enter authentication on a remote authentication device (eg, parent device 500B). Although the illustration prompts for a four-digit numeric passcode, it is understood that different types of authentication credentials are optionally used to secure Digital Health settings (e.g., an alphanumeric password , biometric authentication, etc.). In some embodiments, the passcode that authenticates to extend or override the usage limit is different than the electronic device's passcode to prevent unauthorized extension of the usage limit. For example, the authenticating passcode is optionally a digital health passcode, see FIG. 8N. In some embodiments, upon correctly entered authentication (eg, correct passcode) at parent device 500B, child device 500A is granted additional access to selected applications beyond usage limits. The amount of additional access depends on the extended affordance chosen. In some embodiments, no passcode is required to respond to message 898-6. In some embodiments, after the request is authenticated, child device 500A displays an indication (e.g., notification) of the outcome of the request (e.g., extend by 15 minutes, extend the rest of the day, request denied).

After the request to extend usage beyond the usage limit has been authenticated by a remote authentication device (eg, parent device 500B), the electronic device may have the usage limit extended as shown in FIG. 8PP and its corresponding description. It behaves substantially similar to the electronic device under the "Notifications" option after

FIGS. 8ZZ-8CCC illustrate an exemplary method of presenting an indication that access to an application is restricted and providing access to that application based on input from a parent device.

In response to an attempt to launch a restricted application (e.g. access to the application is restricted if the usage limit has been reached), as similarly described in FIGS. 8QQ and 8RR and their corresponding descriptions: Child device 500A optionally visually obscures home screen 802 (e.g., blurs, grays out, or visually (changed automatically). The restriction notification user interface 890 is substantially similar to the user interface described in FIG. 8NN.

In FIG. 8ZZ, selection of dismissal affordance 892 is detected (eg, by touch 803 detected on dismissal affordance 892). In response to selection of dismissal affordance 892, device 500A stops displaying dismissal affordance 892 on restriction notification user interface 890 and provides local authentication request affordance 898-2 and remote authentication request affordance 898-2, as shown in FIG. 8AAA. Display affordance 898-4.

Under the "notify and block" option, child devices (e.g. devices associated with a child on a family account) can be authenticated to extend or bypass usage limits on that device (e.g. local Require the user to enter authentication (eg, passcode, biometric authentication), remote authentication from a different device (eg, parent device). For example, as shown in FIG. 8AAA, the user selects remote authorization request affordance 898-4 to request remote authorization (eg, authorization on parent device 500B) of the desired extension of social media usage limits.

As shown in FIG. 8BBB, in some embodiments (eg, as opposed to the embodiments of FIGS. 8VV-8YY), depending on the selection of remote authentication request affordance 898-2 on child device 500A, the restriction Notification user interface 890 stops displaying and message user interface 898-10 is displayed. For example, a messaging user interface including the current state of a conversation (e.g., not necessarily related to reaching a usage limit) between the child and the child's parent(s) is displayed (e.g., on device 500B). within a messaging application). The messaging user interface 898-10 of FIG. 8BBB includes a message entry user interface 898-12 and a message send affordance 898-14. Before sending a request for additional application access beyond the usage limit, the child optionally authenticates remotely with the request for additional application access as part of an existing messaging conversation with the child's parent. A message to be sent to a device (eg, parent device 500B) can be entered (eg, using an input device (eg, keyboard)). To send a request for additional access and an accompanying message, the user selects send message affordance 898-14. In some embodiments, a child user can send a request for additional access to the child user's parent without entering a message.

In FIG. 8CCC, in response to selection of message sending affordance 898-14 of FIG. child's request. On the device that received the remote authentication request (eg, parent device 500B), rich message 898-16 is also displayed on messaging user interface 898-10. Rich message 898-16 optionally includes a request for additional access from the child user, an accompanying message, and multiple extended affordances 898-18a through 898-18d.

Multiple extension affordances 898-18a through 898-18d provide the parent user with different usage limit extension options (e.g., extend by 15 minutes, extend for the rest of the day, customize extension, request for extension). refuse). Similar to the selection of extension affordances described in FIGS. 8XX-8CCC, the selected extension option applies to child device 500A.

In some embodiments, in response to selection of one of extended affordances 898-18a-898-18d, the authorizing user (eg, a parent), as similarly described in FIG. For example, you are prompted to enter authentication on parent device 500B). In some embodiments, the passcode that authenticates to extend or override the usage limit is different than the electronic device's passcode to prevent unauthorized extension of the usage limit. In some embodiments, upon correctly entered authentication (eg, correct passcode) at the parent device, the child is granted additional access to selected applications beyond usage limits. The amount of additional access depends on the extended affordance chosen. In some embodiments, no passcode is required to respond to message 898-16.

In some embodiments, after the request is authenticated, child device 500A provides an indication of the result of the request (eg, new message on messaging user interface 898-10, notification outside messaging user interface 898-10). (eg, extend by 15 minutes, extend the rest of the day, request denied).

After the request to extend usage beyond the usage limit is authenticated by a remote authentication device (e.g., parent device 500B), the electronic device may have the usage limit extended as described in FIG. 8PP and its corresponding description. It behaves substantially similar to the electronic device under the "Notifications" option after

FIGS. 8DDD-8GGG illustrate an exemplary method of presenting an indication that access to an application is restricted and providing access to that application based on authentication credentials entered into an electronic device.

FIG. 8DDD shows the device 500 displaying the home screen 802 when the usage limit (eg, social media category usage limit) is reached under the "notify and block" option of the usage limit settings. In some embodiments, the "notify and block" option is set on the category usage limit customization user interface 824, see FIG. 8M. The appearance of the application icon (e.g., Social Media Application A 440) associated with the restriction is updated to indicate that the application is restricted (e.g., icon greyed out, restriction badge 876 superimposed on icon). . As shown, the user attempts to launch social media application A by selecting social media application A icon 440 .

In response to an attempt to launch a restricted application (e.g. access to the application is restricted if the usage limit has been reached), device 500 optionally activates the restricted application as shown in FIG. The notification user interface 890 visually obscures the home screen 802 (eg, blurs, grays out, or visually alters the home screen). The restriction notification user interface 890 is substantially similar to the user interface described in FIG. 8NN.

For example, selection of dismissal affordance 892 is detected (eg, by contact 803 detected on dismissal affordance 892). In response to selection of dismiss affordance 892, device 500 stops displaying dismiss affordance 892 on restriction notification user interface 890 and displays extend affordance 894 and ignore affordance 896, as shown in FIG. 8FFF. do.

Under the "notify and block" option, devices without parental controls (e.g. devices associated with adults (e.g. not children) in a family account or devices not associated with a family account at all (e.g. stand Alone's device)) requires the user to enter authentication (eg, passcode, biometric authentication) on the device in order to extend or bypass the usage limit. For example, as shown in FIG. 8EEE, the user selects extend affordance 894 to request an additional 15 minutes of usage time for the restricted category.

For example, as shown in FIG. 8GGG, in response to selection of extended affordance 894, passcode entry user interface 842 prompts the user to enter authentication. Although the illustration prompts for a four-digit numeric passcode, it is understood that different types of authentication credentials are optionally used to secure Digital Health settings (e.g., an alphanumeric password , biometric authentication, etc.). In some embodiments, the passcode that authenticates to extend or override the usage limit is different than the electronic device's passcode to prevent unauthorized extension of the usage limit. For example, the authenticating passcode is optionally a digital health passcode, see FIG. 8N. In some embodiments, upon correctly entered authentication (e.g., correct passcode), the user is granted additional access to selected applications beyond the usage limit (e.g., 15 minutes, 1 day rest).

After the request to extend usage beyond the usage limit has been authenticated, the electronic device displays the electronic device under the "notify" option after the usage limit has been extended, as described in FIG. 8PP and its corresponding description. works in substantially the same way as

Figures 8HHH-8III illustrate an exemplary method of displaying an indication warning that the usage limit threshold has been reached.

FIG. 8HHH shows a user interface 898 of social media application A displayed by device 500 . In Figure 8HHH, the social media category usage limit has not been reached while the social media application is being displayed. FIG. 8III shows the user interface 898 while social media application A is being displayed and the threshold usage of the social media category has been reached (eg, 1 hour 55 minutes, 90% of the social media category usage limit). show. In response to reaching the threshold amount, a notification 898-20 is presented by the device 500 at the top of the user interface 898 indicating the remaining time (eg, 5 minutes) for the social media category usage limit. In some embodiments, the message automatically stops displaying after a certain period of time (eg, 5 seconds, 30 seconds, or 1 minute).

Figures 8JJJ-8KKK illustrate an exemplary method of changing usage limit settings on a child device.

FIG. 8JJJ shows an application limits user interface 850 for a child device. The user attempts to access usage limit settings for the social media category by selecting the social media category 852a. As shown in FIG. 8KKK, following the selection of the social media category 852a and the determination that the device is a child device, the electronic device requires authentication before being able to change or view the social media category usage limit settings ( For example, by entering a passcode on passcode entry user interface 842, by providing authentication credentials). Although the illustration prompts for a four-digit numeric passcode, it is understood that different types of authentication credentials are optionally used to secure Digital Health settings (e.g., an alphanumeric password , biometric authentication, etc.). In some embodiments, the passcode required to change or view the usage limit setting is different than the passcode of the electronic device to prevent unauthorized access to the usage limit setting. For example, the authenticating passcode is optionally a digital health passcode, see FIG. 8N.

Figures 8LLL-8NNN illustrate an exemplary method of changing usage limit settings for a child device from a parent device.

FIG. 8LLL shows a child device 500A and a parent device 500B. Child device 500A and parent device 500B belong to the same family account. In some embodiments, child and parent device designations are determined during initial family account setup. The child device 500A of FIG. 8LLL displays a home screen 802 when usage limits settings (eg, social media category usage limits) are in effect. Meanwhile, the parent device 500B of FIG. 8LLL displays the application limits user interface 850 of the child device 500A. In some embodiments, the application limits user interface 850 of child device 500A is accessed remotely on parent device 500B from the family account user interface described in this disclosure (e.g., see FIGS. 6A-6UU and method 700). as described in reference). The parent selects the social media category 852a (eg, using contact 805) to view or change the child's device's social media category usage limit settings. It is understood that the application limit user interface shown on parent device 500B in FIG. 8LL is substantially similar to the application limit user interface described in this disclosure (see, eg, FIGS. 6A-6UU and method 700 as described).

FIG. 8MMM shows child device 500A and parent device 500B while the parent user is attempting to change the child's usage limit settings on parent device 500B. In response to selection of the social media category 852a of FIG. 8LLL, the parent device 500B requires authentication (e.g., passcode entry user by providing authentication credentials by entering a passcode on interface 842). Although the illustration prompts for a four-digit numeric passcode, it is understood that different types of authentication credentials are optionally used to secure Digital Health settings (e.g., an alphanumeric password , biometric authentication, etc.). In some embodiments, the passcode required to change or view the usage limit settings is different from the passcode of the parent device to prevent unauthorized access to the usage limit settings. For example, the authenticating passcode is optionally a digital health passcode, see FIG. 8N. In some embodiments, no passcode (eg, alphanumeric password, biometric authentication, etc.) is required to change the usage limit settings of the child device from the parent device. After an attempt to change the child's usage limit settings has been authenticated on the parent device, the parent user can optionally change any usage limit settings associated with the selected category.

For example, FIG. 8NNN shows child device 500A and parent device 500B when the parent changes the child's usage limit setting on parent device 500B. After the parent changes the social media usage settings of the child device 500A (e.g., using the methods described in this disclosure, the social media category usage limit is changed from 2 hours to 1 hour, as shown in FIG. 8NNN). ), the parent device displays the child device's application limits user interface 850 . The modified usage limit setting (eg, 1 hour next to social media 852a) is displayed on the application limits user interface on parent device 500B of FIG. 8NNN. Meanwhile, on child device 500A, after the parent changes the social media usage limit setting of child device 500A, message 898-20 (eg, pop-up notification) is presented over home screen 802 to indicate, for example, FIG. The child's social media usage limit settings (e.g., usage limit time, customized usage limit duration, usage limit added, usage limit removed, usage limit combination) were changed by the child's parent, as shown in 8NNN; indicates In some embodiments, the message automatically stops displaying on the child device after a certain period of time (eg, 5 seconds, 30 seconds, or 1 minute). In some embodiments, depending on the usage setting changes made on parent device 500B, whether those changes are more restrictive or less restrictive for child device 500A (e.g., if a parent changes the child's (whether the social media usage limit has been increased or decreased), notification 898-20 and appropriate details within notification 898-20 are presented on child device 500A.

9A-9K illustrate usage limits (eg, limiting an application or category of applications according to a determination that a usage limit associated with the application or category has been reached), according to some embodiments of the present disclosure. 9 is a flow diagram illustrating a method 900 of setting and enforcing . Method 900 optionally includes device 100, device 300, or device 500 as described above with reference to FIGS. 1A-1B, 2-3, 4A-4B, and 5A-5H. run on electronic devices such as Some acts of method 900 are optionally combined and/or the order of some acts is optionally changed.

As described below, method 900 provides a way to set and enforce usage limits for applications or categories of applications on an electronic device. The method reduces usage of the electronic device when the usage limit is reached without requiring the user to monitor the user's usage. For battery-operated electronic devices, restricting access to applications when one or more usage limits are reached conserves power and increases intervals between battery charges.

In some embodiments, an electronic device that communicates with a display and one or more input devices (e.g., a mobile device that includes a touchscreen such as device 500, one or more of a keyboard, mouse, trackpad, and touchscreen wearable devices such as computers or tablet computers including touch screens, or smart watches that include touch screens, or set-top boxes that communicate with televisions and input devices (e.g., remote controllers) through one or more input devices. A series of one or more inputs that set usage limits associated with a first category of applications accessible on the electronic device, such as 8A-8M (e.g., usage limit setup for the social media category) (e.g., using the device or in a particular way (e.g., certain applications (e.g., certain social media applications, SMS, telephony, certain travel applications, email); certain categories of applications (e.g., , social media, streaming media, gaming, travel, work, communication, payments, news); specific functions of devices (e.g. audio, camera, Bluetooth, Wi-Fi); specific functions of applications (e.g. The maximum amount of time (e.g., 1 hour, 3 hours, 12 hours) that can be spent (e.g., using one or more contacts stored in the configured on the device by the input) is received (902). In some embodiments, the maximum amount of time spans multiple sessions (e.g., periods in which the application is not used by the user (e.g., when the device is off, when the device is dormant, when the device is disconnected from the network). It is aggregated over time periods during which the application is used by users separated by when the user is not using the device to run the application, including when the user is not using the device to run the application. In some embodiments, the usage limits are set in the electronic device's settings user interface (e.g., for setting usage limits and one or more other settings of the electronic device, such as power settings, display settings, email settings, etc.). Settings application). In some embodiments, usage limits are set at different electronic devices that communicate with the electronic device (eg, via wireless connections). For example, a parent device is optionally used to set usage limits for a child's device.

In some embodiments, while the usage limit associated with the first category of applications is being enforced 904 (e.g., the usage limit of the category of applications associated with the usage limit being enforced). When the usage time (e.g. social media category usage time) is being monitored by the electronic device, the electronic device displays social media from the home screen when the social media category usage limit is reached (e.g. social media attempt to launch an application), a request to launch a first application in a first category of applications (e.g., a request from a user of an electronic device to launch an application (e.g., a particular social media application), an electronic request from an application on the device to perform a particular function on the device) is received (906). In some embodiments, an internal timer is associated with each particular category of applications or usage time of each application. In some embodiments, the associated internal timer starts when the application is launched. In some embodiments, the timer is stopped when the application is no longer in use (e.g., application is closed, device is turned off or hibernated, device is disconnected). do.

In some embodiments, while the usage limit associated with the first category of applications is being enforced (904), the usage limit for the first category of applications is reached to meet the limit criteria. (e.g., one or more applications (e.g., social media applications) or one or more actions of the user in the first category, according to a determination that the restriction criteria for the first category of applications have been met, including the requirement that determining that the usage time reaches a set usage limit), the electronic device restricts (908) access to a first application of a first category of applications, such as FIG. Restricting the user's access to the above applications (e.g., specific social media applications) or the first category (e.g., social media applications in general) of operation (e.g., social media application A does not start). In some embodiments, the usage time of the application being requested to launch is compared to a usage limit. In some embodiments, in response to determining that the usage limit for the first category of applications has been reached, the request to launch the application either does not launch the application or displays a dialog indicating that the usage limit has been reached. Display and request further user action to complete the launch of the application. In some embodiments, restricting an application from a user is different than preventing the application from running. For example, despite being restricted from the user, the restricted application or action optionally still runs on the device independent of user input (e.g., performing operating system tasks). in the background for the purpose).

In some embodiments, while the usage limit associated with the first category of applications is being enforced 904, the limit criteria are not met (e.g., the first category of applications (e.g., social media application) has not reached a usage limit (e.g., the user's usage time of one or more applications or one or more operations in the first category has not reached a set usage limit) )), the electronic device provides 910 access to a first application of a first category, such as FIG. A user's access to actions in a category (eg, social media applications in general) is not restricted). In some embodiments, the usage time of the application being requested to launch is compared to a usage limit. In some embodiments, in response to a request to launch an application, the application launches normally. The application usage limits described herein are optionally the same or similar to the application usage limits or thresholds described with reference to methods 700 and 1300 . The above-described method of setting a usage limit for a category of applications as a whole and enforcing that usage limit across individual applications of that category of applications allows the electronic device to efficiently control the user's use of specific device behaviors. and provide an easy way for users to set such usage limits, thereby making device usage more efficient (e.g., users can limit their own device usage to monitoring is not required, thus reducing user-supplied input to the device (eg, input to otherwise monitor user usage). The understanding that usage limits have been set allows users to use restricted operations more wisely and efficiently to perform all necessary tasks under usage limits. If the usage limit has been reached, the device restricts the user from using restricted actions, thereby preventing the user from unknowingly exceeding the usage limit and spending more time on the device than intended. Preventing, as well as allowing users to use the device more quickly and efficiently, reduces power usage and improves the battery life of the device.

In some embodiments, the restriction criteria further include a requirement that the first application does not meet one or more restriction exclusion criteria (912), such as FIG. (eg, social media application B is not selected as enforced by the social media category usage limits). In some embodiments, the use of such applications does not count toward usage limits (e.g., an application belongs to a first category, but use of that application contributes to that category and/or overall device usage). not aggregate towards the usage limit). In some embodiments, the application being requested to launch is compared to a list of applications excluded from usage limits. The restriction exemption criteria described above enable an electronic device to determine whether the use of applications belonging to a category with an associated usage limit is exempt from counting toward that usage limit, which manually determine whether a particular application should be excluded (e.g., a particular social media application is optionally excluded because the user needs that application to communicate with family and friends). In addition, by allowing users to use the device more quickly and efficiently, it reduces power usage and improves the battery life of the device.

In some embodiments, upon determining that the restriction criteria for the first category of applications have not been met, the electronic device displays the first application (eg, icon for the first application), such as FIG. 8U. Display representations (e.g., icons, widgets, windows of the first application in the multitasking view along with other windows of other applications) with a first visual characteristic (e.g., when the usage limit has not been reached). display normal icons for applications installed on the electronic device (e.g., in the home screen of the electronic device), such as in color, without obscuring, etc. (914) (e.g., application icon appearance and notification badges indicate that the application is not restricted). For example, the electronic device displays one or more application windows associated with one or more applications (e.g., within a multitasking graphical user interface view), or the electronic device displays the application windows on the home screen of the electronic device. Displays one or more icons for launching .

In some embodiments, upon determination that the restriction criteria for the first category of applications have been met (e.g., upon determination that the usage limit has been reached and the first application is not on the whitelist), The electronic device displays a first representation of the first application, such as FIGS. 8Y-8EE, with a second visual characteristic that differs from the first visual characteristic (eg, an icon ) 916 (eg, application icons, widgets, notifications, and website appearance indicate that the application is restricted). In some embodiments, when the usage limit is reached, the electronic device changes the appearance of various aspects of applications not included in the application whitelist. For example, icons for applications not included in the whitelist (eg, icons on the home screen of the device, certain social media application icons) are shaded when the application is restricted. As another example, notification badges included on application icons for applications not included in the application whitelist are optionally changed (eg, icons for specific social media applications). As another example, in some embodiments the electronic device has multitasking capabilities. In such embodiments, the electronic device optionally displays a user interface that displays visual representations of more than one application simultaneously (e.g., icons from multiple applications simultaneously, current (e.g., a user interface that displays screenshots of the user interface of the In some embodiments, the representation for restricted applications not in the application whitelist within the multitasking user interface described above is altered by the electronic device (e.g., faded out or shaded, or the application whitelist are otherwise modified to be displayed with different visual characteristics than the representation corresponding to the application contained in). The change in appearance of the application representation described herein is optionally the same or similar to the change in appearance of the application representation described with reference to methods 1100 and 1300 . The above-described method of selectively changing the appearance of applications not on the application whitelist when the usage limit is reached allows the electronic device to determine which applications the user has access to when the usage limit is reached. By providing an indication of whether or not the electronic device has In addition to reducing power consumption and improving device battery life.

In some embodiments, displaying the first representation of the first application with the second visual characteristic includes overlaying the first representation on the first representation, such as overlaying the upper right portion of the application icon. including displaying 918 a limited use badge that includes an indication that access to the application is restricted (e.g., the first application (and optionally other applications whose usage limit has been reached); ) with a visual indication of a lock or some other restriction symbol added to the application icon for ). In some embodiments, the badge overlays a portion of the text associated with the application icon. In some embodiments, the badge overlays at least a portion of the application icon, such as FIG. 8AA (eg, a limited use badge replaces the notification badge for social media application A). The above-described method of selectively changing the appearance of representations of applications not on the application whitelist when the usage limit is reached is such that when the electronic device is at the usage limit, the user does not have access. Displaying a restricted use badge on applications that do not allow users to efficiently and selectively limit the use of specific applications for specific periods of time, thereby allowing users to access such restricted applications in addition to reducing the use of the electronic device during those periods, thereby reducing power consumption and improving battery life of the device.

In some embodiments, displaying the first representation of the first application in the first visual characteristic is an indication of a notification (e.g., unread message, displaying 920 a first representation having a notification badge (e.g., unread messages, an indicator of missed calls, etc.) including the number of missed calls, etc. (e.g., the notification badge for social media application A is the application number of unread messages associated with the ). In some embodiments, displaying the first representation of the first application with the second visual property causes the first representation to have the notification badge replaced by the limited use badge, such as FIG. 8AA. including displaying (eg, blurring the indicator or replacing the indicator with a graphic) 922 (eg, a limited use badge replaces the notification badge for social media application A). In some embodiments, the limited use badge described above replaces the notification badge indication on the application icon for non-whitelisted applications when the usage limit is reached, as described above. In some embodiments, replacing the notification badge indication with the limited use badge described above hides the number of notifications associated with the application so that the number of notifications is no longer displayed on the display. The above-described method of selectively changing the appearance of representations of applications not on the application whitelist when the usage limit is reached is such that when the electronic device reaches the usage limit, notification of the representation of the application is enabled. Replacing the indications with restricted use badges on applications to which the user does not have access allows efficient and selective use of specific applications to be restricted for specific periods of time, thereby By not indicating that such notifications exist, users are discouraged from attempting to access restricted applications that have recent notifications, reducing use of the electronic device during those periods; reduce power consumption and improve device battery life.

In some embodiments, the first application does not meet one or more restriction exemption criteria (e.g., non-whitelisted applications, first application not on whitelist, first application reaches usage limit and while the first application is in use (e.g., the primary user interface of the first application is displayed on the electronic device) , or the user is otherwise interacting with the first application (e.g., via a secondary user interface of the first application), the electronic device may allow use of the first application to Aggregate 924 toward the usage limit associated with the first category (e.g., aggregate the contribution of the usage of the non-whitelisted applications to the usage limit associated with the first category of applications that include the first application). do).

In some embodiments, the first application satisfies one or more restriction exemption criteria (e.g., whitelisted applications, the first application is on the whitelist, after the first application reaches its usage limit and the first application uses 926, the electronic device refrains from counting usage of the first application toward the usage limit associated with the first category of applications (e.g., usage of the first application Excluded from usage limits (e.g., the first application is included in an application whitelist and the electronic device provides access to the first application after reaching the usage limit for the first category of applications). As another example, according to a determination that the use of the first application is for whitelisting purposes (e.g., a phone app or messaging app used to communicate with a parent), its use is , not aggregated toward the usage limit). The above-described method of forgoing aggregating usage of applications that meet one or more restriction criteria (e.g., whitelisted applications, applications that are not restricted after a usage limit is reached) is a method in which an electronic device monitors whitelisted applications. without the need to add additional categories for whitelisted applications, thereby allowing an electronic device to monitor one or more whitelisted applications (e.g., use It enables better management of categories of applications, including applications that are not restricted after reaching a limit), as well as allowing users to use their devices more quickly and efficiently, thus reducing power consumption. Reduce usage and improve device battery life.

While the first application is being used (e.g., the primary user interface of the first application is being displayed on the electronic device, or the user is otherwise interacting with the first application) (e.g., via a secondary user interface of the first application), the electronic device optionally, regardless of whether the first application meets one or more exclusion criteria, Aggregate 928 the usage of the first application toward the usage limit associated with the first category of applications (e.g., without depending on whether the first application is on the whitelist, the first aggregate the usage contribution of one application towards the usage limit associated with the first category of applications). For example, a particular social media application associated with a social media category and a one hour usage limit is optionally a whitelisted application and its usage counts towards that usage limit. Usage of different social media applications, which are optionally not whitelisted, are also optionally aggregated towards the usage limit. The above-described method of aggregating application usage allows electronic devices to monitor usage limits for categories of applications, including whitelisted applications, thereby eliminating the need to add additional categories for whitelisted applications. Additionally, an electronic device may better categorize categories of applications that contain one or more whitelisted applications (e.g., applications that are not restricted after the usage limit is reached) because the usage limit of the category takes into account the use of whitelisted applications. In addition to allowing users to use devices more quickly and efficiently, it reduces power usage and improves device battery life.

In some embodiments, a usage limit is associated with the first category of applications during one or more first implementation periods, such as FIG. 8L (e.g., two hour default social media category usage limit). 930 (eg, the usage limit for the first category of applications during weekdays). In some embodiments, the electronic device, via one or more input devices, can, via one or more input devices, one or more receive 932 a set of one or more second inputs that set a second usage limit associated with the first category of applications for a second period of time (e.g., using the device using the device in a specific way (e.g., using a specific application (e.g., certain social media applications, SMS, phone calls, certain travel applications, email) for a period of time other than the prescribed time); A second maximum amount of time (e.g., 1 hour, 3 hours, 12 hours) is set (e.g., when the first usage limit (e.g., default usage limit) while the second usage limit is in effect on Saturdays and Sundays, while the first usage limit is in effect during non-working hours, the second usage limit is during working/school hours a second usage limit is enforced on a specific day of the week, while a first usage limit is enforced on a non-specific day, which is enforced on a specific day of the week).

In some embodiments, according to a determination that the current time is within one or more first implementation periods (e.g., the current time is within a user-defined implementation period (e.g., a particular day of the week, work/school 8L, the electronic device enforces 934 the first usage limit (e.g., the second usage limit during the user-defined enforcement period), as shown in FIG. (e.g., when an application (e.g., a particular social media application) of a first category of applications (e.g., social media) is accessed, aggregates toward a second usage limit; provide or restrict access to applications of the first category of applications based on usage limits of 2)).

In some embodiments, according to a determination that the current time is within one or more second implementation periods (e.g., the current time is other than a user-defined implementation period (e.g., a default period, a specific period of one week), day, after work/school hours, Saturday to Sunday), the electronic device enforces 936 a second usage limit (e.g., user-defined Enforce a first usage limit (e.g., a default usage limit) outside the enforcement period (e.g., when an application in a first category of applications (e.g., social media) (e.g., a particular social media application) is accessed providing or restricting access to applications of a first category of applications based on the first usage limit, which sometimes aggregates toward the first usage limit)). The above-described method of allowing different usage limits for the first category of applications on different days enables an electronic device to effectively limit a user's usage of certain device operations during defined time periods. to provide an easy way for users to set such usage limits for defined time periods, thereby making electronic device use more efficient (e.g., user use With the understanding that a second usage limit has been established, which is specifically restricted during hours, workdays, and specific days, users are encouraged to use the restricted behavior more wisely and efficiently to achieve specific If the user is able to perform all required tasks under the second usage limit during a period of Restricting the use of swipe actions, thereby allowing the user to unknowingly exceed the usage limit and spend more time on the device than intended during certain periods of time (e.g., school/work hours, workdays) In addition, it reduces power usage and improves the battery life of the device by allowing the user to use the device more quickly and efficiently.

In some embodiments, the electronic device via one or more input devices, such as FIG. 8I (eg, social media application B is not selected to be enforced by the social media category usage limit) , a second application of a first category of applications (e.g., a second particular social media application is associated with a social media category that has an associated usage limit) from the usage limit for the first category of applications. Receive 938 input corresponding to a request to exclude (e.g., a request to exclude the second application, for example, optionally configured on a configuration user interface. As another example, a particular If the application is not included in the usage limit, then the particular application will optionally be excluded from the usage limit).

After receiving input corresponding to a request to exempt the second application from the usage limit and while the limit criteria for the first category of applications are satisfied (940), the electronic device optionally: , FIG. 8AA (e.g., social media application B is not restricted from launching when the social media category usage limit is reached) (942). In some embodiments, in response to receiving the request to launch the second application, the electronic device may display the appearance of the social media application B icon as shown in FIG. provide 944 access to a second application (e.g., regardless of whether the usage limit associated with the social media application has been reached or not, the second specified access to social media applications is not restricted). A first application (e.g., a first specific social media application) and a second application (e.g., a second specific social media application that is different from the first specific social media application) are in the social media category. belong, but the electronic device excludes a second application (e.g., a second particular social media application) from the category (e.g., social media) usage limit while use of the first application is restricted be able to. In some embodiments, the user can define which applications are exempt from such category usage limits. In some embodiments, an application is excluded if the user or electronic device does not define usage limits for that application. The above-described method of excluding applications associated with a category from the category's usage limits is such that the electronic device can be divided into applications whose use is restricted by the usage limit (e.g., the first application) and applications that are not restricted by the usage limit ( a second application), thereby reducing the user's burden of dealing with restrictions on applications that should be exempt from such restrictions (e.g., a second application may have a usage limit). but the second application is optionally excluded from the usage limit by the user because the user does not want that application to be restricted); Reduce power usage and improve device battery life by allowing the device to be used more quickly and efficiently.

In some embodiments, the usage limit is of the first category of applications, such as FIG. 8Q (e.g., the social media category usage limit is associated with the social media category usage limit and the streaming and social media category usage limit). A second category of applications accessible on the electronic device is further associated 946 with a second category of applications accessible on the electronic device, including an application that is different from the application (e.g., a usage limit is associated with more than one category and a A total usage limit is set such that each of the two or more categories has a different group of applications (eg, no two groups have the same list of applications). For example, usage limits are optionally associated with social media and streaming applications. As another example, usage limits are optionally associated with social media and messaging applications. Although specific social media applications are associated with both the social media and messaging categories, the lists of applications within the social media category and messaging are optionally different. The above-described method of associating a first category of applications and a second category of applications with usage limits enables an electronic device to restrict usage of applications of the two categories with joint category usage limits, thereby: To reduce the user's burden of tracking different usage limits for different groups when total usage totals for different groups are desired, as well as allow the user to use the device more quickly and efficiently. This reduces power usage and improves device battery life.

In some embodiments, the first category of applications includes all applications accessible on the electronic device (948) (e.g., usage limits is associated with all applications and categories on the electronic device so that a total usage limit is set for all applications on the electronic device). For example, if a global limit is optionally set, use of the first and second specific social media applications is restricted by the global limit even if the specific application is associated with the social media category. The total usage limit here is the same as or similar to the total showtime usage limit described with reference to method 700 . The above-described method of setting global usage limits for all categories of applications enables an electronic device to limit the use of non-whitelisted applications with global usage limits (e.g., enforce user screen time limits), This reduces the user's burden of defining individual limits for each category when an overall usage limit is desired, as well as allowing the user to use the device more quickly and efficiently. This reduces power usage and improves device battery life.

In some embodiments, the usage limit associated with the first category of applications includes one or more (eg, category name previously defined by user, category name previously defined by device) (950). In some embodiments, the default name of the usage limit is the category of application determined based on the category of applications within that category of applications, such as "news" or "games" or "news and games". The name determined by the device. The electronic device optionally renames the usage limit name to a second usage limit name, such as FIG. Receive 952 a set of one or more second inputs to modify (e.g., the set of one or more second inputs optionally comprises one or more input devices (e.g., electronic devices, received from a remote input device). In some embodiments, in response to a series of one or more second inputs, the electronic device changes the social media category usage limit to "John's Fun", such as in FIGS. ), and the usage limit name is changed 954 to a second usage limit name (eg, the category name is redefined by the user). In some embodiments, a user may enter a new user-defined category name (e.g., via a soft keyboard, voice input, etc.) to enter a category name (e.g., a name previously defined by the user, name previously defined by the device) can be changed. For example, a user may create a category that includes applications from a number of different system-defined categories (e.g., a particular social media application belonging to the social media category and a particular gaming application belonging to the gaming category) to category names (eg, "restricted applications", "social media and games"). In some embodiments, the electronic device automatically changes category names. For example, a category labeled "Social Media" initially optionally includes specific social media applications. Certain gaming applications are optionally added to that category. Upon addition of the gaming application, the category name is optionally changed to "Social Media and Gaming" by the device. The above-described method of renaming a usage limit category enables an electronic device to receive input (e.g., from a user, from a remote input device) and change the usage limit category name in response to the input; This allows usage limits to be set up again when a more appropriate usage limit category name is desired (e.g. a new application is associated with a usage limit, a more appropriate usage limit category name to include newly associated applications, etc.). allows the user to change the usage category name when the name is needed), in addition to reducing power usage by allowing the user to use the device more quickly and efficiently. Improve device battery life.

In some embodiments, the first application is a first category of applications, such as FIG. 8Q (e.g., social media applications are simultaneously associated with social media category usage limits and streaming and social media category usage limits) and a second usage limit (eg, the first application is associated with two concurrent usage limits) (956). For example, the social media category is optionally associated with two usage limits. For example, the electronic device optionally has a two hour overall limit, including the social media category limit, and/or the electronic device optionally has a usage limit for a particular application within the social media category ( for example, 30 minutes or some other amount). The second usage limit is optionally an overall usage limit for the electronic device, a usage limit for a category of applications of the electronic device (different from the first category of applications but including the first application), a The usage limit for the first category is a usage limit for the first application itself, which is separate from the usage limit for the first category. The above-described method of enforcing two or more usage limits simultaneously enables an electronic device to monitor application usage against more than one usage limit, thereby allowing the user to determine which application the user wishes to restrict. To reduce the user's burden of separately associating with each of two or more usage limits and separately monitoring each of the two or more usage limits, in addition to allowing the user to use the device more quickly and efficiently. reduces power usage and improves device battery life by allowing

In some embodiments, the first application is associated with a social media category usage limit and a streaming and social media category usage limit at the same time, such as FIG. implemented), the usage limit for the first category of applications has been reached because the second restriction criterion has been met, or the second usage limit has been reached because the second restriction criterion has been satisfied. (e.g., in some embodiments, the most conservative limit (e.g., the usage limit with the least amount of time remaining) is reached 958). the second restriction criterion is satisfied). In some embodiments, following a determination that the second restriction criterion is met, the electronic device restricts access to the first application (960), such as FIG. 8Q (e.g., the social media application is , social media category usage limits and streaming and social media category usage limits, the most conservative usage limits being enforced).

In some embodiments, following a determination that the second restriction criterion is not met, the electronic device provides 962 access to the first application, such as FIG. 8Q (e.g., the social media application is , the social media category usage limit and the streaming and social media category usage limit simultaneously, and neither usage limit has been reached). For example, a first application is optionally associated with two usage limits. The first application optionally belongs to a social media category that optionally has a first usage limit (eg, one hour or some other amount of time). The electronic device optionally has an overall limit (eg, a second usage limit of two hours or some other amount of time). If one of the usage limits is met (e.g., the most conservative/restrictive usage limit is met), even if the other usage limits are not met, the electronic device optionally performs the first Restrict access to applications. Without any device usage, the social media category usage limit optionally has 1 hour remaining and the overall usage limit optionally has 2 hours remaining. In this example, the social media category usage limit is the lowest remaining usage limit for the social media application. As another example, after any device usage, the overall usage limit optionally has 30 minutes left and the social media category optionally has 1 hour left (e.g. (because social media applications haven't been used this much in the last few years). In this example, the overall usage limit is optionally the lowest remaining usage limit for the social media application. For any category or application associated with more than one usage limit, the more conservative remaining usage limit optionally limits usage of the first application. The above-described method of enforcing the most conservative usage limit of two or more simultaneous usage limits is such that the electronic device monitors usage of an application for two or more usage limits and determines the most conservative remaining usage limit. It is possible to enforce limits, whereby an application that a user wishes to limit is separately associated with each of two or more usage limits, and which of the usage limits is reached faster. It reduces power usage and improves device battery life by reducing the burden on the user to make decisions, as well as allowing the user to use the device more quickly and efficiently.

In some embodiments, while the limit criteria for the first category of applications are met (964), the electronic device may be configured to meet the social media category usage limit, such as in FIGS. trying to see or access application suggestions, widgets, search results, and websites corresponding to social media application A), events corresponding to the activation of auxiliary functions of the first application. (e.g., the occurrence of an event that would trigger the display of a notification about the application, a request to display a widget corresponding to the application, a request to share content with the application via a system that shares the user interface, a Requests to view websites, requests to view previous notification history (including application notifications), requests to display application content in picture-in-picture (PIP) mode, display applications in search results or to display and/or perform media control actions associated with the application) is detected (966). Auxiliary functions of the first application are available for execution without displaying the primary user interface of the first application (e.g., without launching the application within an application window or other primary view of the application). Functionality (e.g. display interactive notifications, perform share sheet actions, display widgets, display notification history, display websites in browser, display application content in PIP mode display search result applications; or display and/or control media control actions).

In some embodiments, in response to detecting an event corresponding to the activation of the auxiliary function of the first application, the electronic device responds to FIGS. Application suggestions, widgets, search results, and websites are not accessible to the user when the social media category usage limit is reached), suppress auxiliary functions (968) (e.g., Notification generation functionality, display of website(s) associated with the application, share sheet action(s), display of application content in PIP mode, and any other functionality associated with the application (operating system features) (e.g. restricting the app from appearing in search results, restricting access to widgets associated with the application, restricting the application from appearing as a suggested application)). In some embodiments, launching applications from the home screen of the electronic device (or other user interface of the electronic device) is also inhibited (eg, restricted). In some embodiments, auxiliary functions are inhibited by preventing the function from executing in response to detecting an event. Auxiliary functions described herein are optionally the same or similar to auxiliary functions described with reference to method 1300 . The above-described methods of throttling functionality across operating system aspects of applications that exceed their usage limits allow the electronic device to effectively reduce the overall usage of the electronic device, thereby reducing power consumption. to improve the battery life of your device.

In some embodiments, the electronic device associates corresponding categories of applications by application source on the electronic device from an application source (e.g., an application store for browsing and/or downloading applications to the electronic device). adding 970 access to a second application (e.g., downloading a new application from an app store (e.g., a second specific social media application); accessing the new application remotely; Install a new application: In some embodiments, the app store, such as Figures 8FF-8GG, may include publisher information about the application or some other determination made by the app store (e.g., a news application may , games are designated as part of the Games category in the app store, etc.). adding social media application F from the Store user interface).

In some embodiments, according to the determination that the corresponding category is the first category (e.g., the category assigned to an application added by an app store is the same as an existing category with usage limits on the electronic device). 8HH (e.g., newly added social media application F is determined to be within the social media category usage limit, and the social media category usage limit has been reached). When access to the newly added social media application F is restricted), control 972 access to the second application according to the restriction criteria for the first category of applications (e.g., the first category If the usage limit for (e.g., social media) has been reached, the electronic device optionally redirects the user to a second application (e.g., a second specific social media application added from the application source). also restrict access to Thus, the electronic device applies the first category restrictions to the later added second application. In some embodiments, determining the category assigned to the application added by the app is based on the app store attributes of the added application (eg, games, social media, news, streaming). In some embodiments, this determination is based on metadata associated with the added application.

In some embodiments, according to the determination that the corresponding category is not the first category (eg, determining that the added application does not belong to the first category (eg, a category different from social media)). , the electronic device forgoes (974) controlling access to the second application according to the restriction criteria for the first category of applications (e.g., the added application (e.g., the second specific social media application) is optionally not associated with a first category usage limit (eg, social media usage limit). In some embodiments, the added application is controlled based on different usage limits for different categories of applications to which the added application belongs. In some embodiments, if an added application does not fall under any usage limits on the electronic device, it is not controlled by any usage limits on the electronic device. determining the category (e.g., social media) of the added application (e.g., a second particular social media application) based on one or more classification criteria (e.g., app store taxonomy, new application metadata); , the above-described method of enforcing a usage limit associated with a determined category (e.g., social media) for a new application (e.g., a second particular social media application), wherein the electronic device provides the user with a new application; This makes it possible to efficiently restrict the user's use of added applications without having to determine the classification of the added application, thereby making device usage more efficient (e.g., when the user manually categorizes the added application users do not have to manually determine the usage limits of added applications, users do not need to monitor their own device usage of added applications, and therefore do not have The device restricts the user from using the added application if the usage limit is reached, which reduces the input provided (e.g., input to otherwise monitor the user's usage). , thereby preventing the user from unknowingly exceeding the usage limit and spending more time on the device than intended), as well as allowing the user to use the device more quickly and efficiently This reduces power usage and improves device battery life.

In some embodiments, one associated with a restricted use mode, such as FIG. 8E (e.g., a device idle time period is set), in which access to one or more applications on the electronic device is restricted. One or more windows of time are defined 976 on the electronic device (e.g., a user of the electronic device may allow the electronic device to exclude applications that, in some embodiments, are included on an application whitelist, Define a time of day (eg, 10:00 pm to 5:00 am) as a bedtime restricted use mode that prevents or attempts to prevent access to all applications on the electronic device. In some embodiments, the user simply defines the above time window and does not specify any particular application for which access will be restricted. In such embodiments, the electronic device optionally defaults to restricting or attempting to restrict the use of all applications except whitelisted applications during the restricted usage mode. In some embodiments, one or more windows of time associated with the restricted use mode are defined (e.g., during the defined period(s), the restricted use mode is according to a determination that a request to launch a first application is received and associated with a restricted use mode; During the window of time (e.g., the electronic device is currently in restricted use mode, the electronic device is currently in bedtime restricted use mode), the electronic device is placed in a state such as FIGS. time setting overrides social media category usage limit setting, device idle time setting limits social media application when social media category usage limit is not reached), the limit criteria for the first category of applications are met restricts access to the first application (978) regardless of whether or not it is enabled (eg, restricted usage mode overrides usage limits). For example, access to the first category of applications is optionally restricted during the restricted usage mode even if usage limits for the first category of applications are not met. The restricted use modes described herein are optionally the same or similar to the restricted use modes described with reference to method 1100 . The methods described above for enforcing a restricted usage mode (e.g., bedtime restricted usage mode) in conjunction with an application usage limit require that the electronic device can be used before the usage limit is reached (e.g., device idle time, specified unlimited Allowing access to one or more applications or categories of applications to be restricted during active hours (e.g., bedtime), thereby allowing users to access despite usage limits that may not have been reached. can better manage device use during restricted activity times (e.g., bedtime), as well as reduce power usage by allowing users to use devices more quickly and efficiently to improve the battery life of your device.

In some embodiments, restricting access to the first application is a "notification" option that provides extend and ignore affordances for proceeding with the restricted application, such as FIGS. 8NN-8OO. lower restriction notification user interface), presenting an indication that access to the first application is restricted (e.g., a visual indication (e.g., an hourglass representing that time has displaying on the display one or more application icons associated with the usage limit); playing a sound on speakers associated with the electronic device; haptic(s) indicating that the application is restricted; ) and/or generating tactile output(s), etc. (eg, notifications) (980). The indication includes selectable affordances to provide access to the first application without requiring authentication credentials (e.g., the user accesses the restricted application when the usage limit is reached). graphical user interface elements or soft buttons). In some embodiments, different applications are associated with different limit options that are enforced when the usage limit is reached. For example, the electronic device optionally allows one or more applications to be associated with a "notification" restriction option. If a user attempts to launch an application associated with a "notification" limit (e.g., by selecting the icon for that application from the home screen of the electronic device when the usage limit is reached and the application is not included in the application whitelist), the electronic device optionally displays a popup indicating that application usage is currently restricted (e.g., due to usage time limit being reached). Show indications. The pop-up notification optionally provides one or more affordances that, when selected, allow the user to proceed to the application without having to enter any authentication credentials (e.g., without having to enter administrator or other credentials). includes a "must go" affordance to open the application in the In some embodiments, app usage exceeding acceptable limits (e.g., even if approved due to extended hours) is optionally indicated within the dashboard user interface described above with reference to method 700 ( 6L-6P, 6EE-6HH, 6OO-6SS, and 6UU). In some embodiments, in response to selecting an affordance for providing access to the first application and prior to providing access to the first application, the visual indication on the display is , updates to a second visual indication to indicate that access is being provided. The “notify” option described herein is optionally the same as or similar to the “notify” option described with reference to method 1100 . The above-described method of notifying the user that the application will be restricted when the usage limit is reached, but giving the user the option to access the application nonetheless when needed, is an electronic device that allows the user to Efficiently restricts the use of certain applications for specified periods of time while still allowing necessary tasks to be performed on the electronic device, thereby allowing the electronic device to operate during those periods. In addition to reducing power consumption and improving device battery life.

In some embodiments, restricting access to the first application may include extending and ignoring affordances for requiring authentication before proceeding with the restricted application, such as FIGS. a restricted notification user interface under a "notify and block" option that provides restricted access to the first application, including selectable affordances to provide access to the first application while requiring authentication credentials; presenting an indication that the display on top, play sound on speakers associated with the electronic device, haptic(s) and/or tactile output(s) indicating that the application is restricted, etc. (e.g. notification) ) (982). In some embodiments, the electronic device allows one or more applications to be associated with the "block and notify" restriction option. If the user attempts to launch an application associated with a "block and notify" limit (e.g., by selecting the icon for that application from the home screen of the electronic device when the usage limit is reached, and (assuming that the application is not included in the application whitelist), the electronic device blocks the application from launching and, optionally, the application usage is currently restricted (e.g., usage limits). display a pop-up indication that the In some embodiments, the pop-up indication requires authentication credentials (e.g., password, passcode, or consent from parent device/account, fingerprint, face (e.g., normal biometric authentication) to access the application. requires attention awareness via a depth camera)). If the Electronic Device is a child device within a family account (e.g., the device of a user designated as a child as opposed to a parent or administrator within the family account), the displayed notification is optionally Includes affordances for requesting permission from adult/parent devices in the family account to access applications when limits are reached. In such cases, selection of the request within the notification will optionally result in the notification being delivered to one or more (or all) parent devices associated with the household account, and if permission is granted. The electronic device (eg, at least one of the parent devices or a child device with a passcode) authorizes access to the application. In some embodiments, in response to selecting an affordance for providing access to the first application and prior to providing access to the first application, the visual indication on the display is , updates to a second visual indication to indicate that access is being provided. The “block and notify” option described herein is optionally the same as or similar to the “block and notify” option described with reference to method 1100 . The above-described method of blocking the launching of an application when the usage limit is reached and notifying the user that the application is restricted would allow the electronic device to effectively limit usage of a particular application for a particular period of time. , thereby reducing the use of the electronic device during those periods, as well as reducing power consumption and improving the battery life of the device.

In some embodiments, the electronic device is not a child device (e.g., not a child device in a family account based on the classification of the user account associated with the electronic device or an option selected on the electronic device (e.g., , is the parent device in the family account))), the selection of affordances may include options such as FIG. 8EEE-FIG. Restrictions notification user interface under the "notify and block" option provided), which causes a request to enter a passcode to access the first application (984). For example, the determination that the electronic device is not a child device is optionally based on a determination that the user account associated with the electronic device (e.g., the user currently signed into the device) is not classified as a child account. In some embodiments, the determination that the electronic device is not a child device is optionally made when the electronic device is set to be a parent device in the device's settings (e.g., during initial setup of the device). established) or not associated with a family account at all. For example, the pop-up notification optionally includes one or more affordances that, when selected, allow the user to proceed to the application only if proper authentication credentials are provided. In some embodiments, affordances are user IDs, passwords, passcodes, fingerprint authentication, and/or face authentication (e.g., attention awareness via depth camera is required for successful biometric authentication) includes one or more of soft buttons or input field(s) for For example, if the device is not a child device within a family account (e.g., is a parent device within a family account) or is not associated with a family account at all, the electronic device is optionally is associated with the user account credentials (e.g., user ID and/or password, passcode) (e.g., the user ID and/or password or passcode associated with the profile with which the device is configured). code). In some embodiments, the credentials (e.g., user ID and/or password, passcode) are different than the credentials for accessing the electronic device (e.g., "unlocking" the device and/or logging into the device). passcode different from the one used to In this way, a user (eg, child) who is not the device owner (eg, parent) will not be able to bypass application restrictions if the user does not enter a secondary passcode.

In some embodiments, following a determination that an electronic device is a child device (e.g., based on classification of a user account associated with the electronic device or options selected on the electronic device), selection of affordances is 8TT-FIG. 8CCC (e.g., local authentication request affordances and remote authentication request affordances are displayed on a restricted notification user interface on a child device, and authentication is requested on different corresponding devices depending on affordance selection). enter a passcode to access the first application (e.g., a parental control passcode that is different from the passcode to unlock the device or access the user account associated with the device operation) and, when selected, initiates a process requesting access to the first application from the parent device (e.g., requesting more time from the parent device in the family account). cause the display to present the second affordance (986). For example, a determination that an electronic device is a child device is optionally based on a determination that a user account associated with the electronic device (eg, a user currently signed into the device) is classified as a child account. In some embodiments, the determination that the electronic device is a child device is optionally made when the electronic device is set to child device in the device settings (e.g., during initial setup of the device). set). In some embodiments, this process will send a message to the parent device requesting access to the first application (e.g., a text message or any other alert on the parent device, the parent (singular) or multiple )) to the email account associated with the )). This process then begins when the parent authorizes the child device to access restricted applications (e.g., the parent decides to allow the child device to access restricted applications when the usage limit is reached). You can choose) or deny access to restricted applications on child devices. In some embodiments, the electronic device presents an affordance to enter a passcode and/or initiate a process of requesting access to the first application. In some embodiments, the passcode is a parental control passcode or use passcode that is different from the passcode for unlocking the electronic device. In this way, the child is optionally unable to circumvent the restricted access mode, but the parent optionally has a passcode that allows the electronic device to access the first application. can be entered. Requesting additional time as described herein is similar to requesting additional time as described with reference to the restricted use mode of method 1100 . The above-described method of notifying the user that the application will be restricted when the usage limit is reached, but allowing the user the option to access the application nonetheless when needed, is provided by the electronic device that: Efficiently restricts the use of specific applications for specific periods of time while allowing the user to perform necessary tasks on the electronic device, thereby reducing the time between those periods. It reduces the use of electronic devices and, in addition, reduces power consumption and improves device battery life.

In some embodiments, according to a determination that a usage limit warning threshold has been reached (e.g., a percentage of the usage limit has been reached) while the usage limit associated with the first category of applications is being enforced. (e.g., 90%, 5 minutes remaining, 45 minutes out of an hour, 5 minutes, 10 minutes, 1 hour, or any period before reaching usage limit) ), the electronic device reaches a usage limit warning threshold, such as FIG. display 988 an indication (e.g., text, image, sound, tactile and/or tactile output, etc.) that a 5 minutes remaining, 45 minutes out of an hour), or a certain amount of time (e.g., 5 minutes, 10 minutes, 1 hour, or any period of time) remains before reaching the usage limit notice). In some embodiments, the threshold time is user defined. In some embodiments, the notification includes text, image(s), and/or sound. In embodiments, the notification includes an indication of haptics and/or tactile output. In some embodiments, the notification includes a button that allows the user to dismiss the notification. In some embodiments, the electronic device stops displaying notifications after a certain amount of time. The above-described method of informing the user that the usage limit is about to be reached (e.g., a certain percentage of the usage limit has been used (e.g., 90%, 5 minutes remaining, 45 minutes out of an hour) is , making the interface between the user and the device more efficient (e.g., without the user having to monitor the time, giving the user the opportunity to finish the task they are currently running on the device, reaching usage limits, etc.) prompting the user to stop using the device in anticipation of the can effectively reduce the overall usage of the electronic device, as well as reduce power consumption and improve the battery life of the device.

In some embodiments, the electronic device displays one or more usage limits associated with usage limits, such as FIG. Receive 990 one or more inputs to change settings (eg, change usage limit start/end time, change whitelist, etc.). In some embodiments, in response to receiving 992 one or more inputs to change one or more usage limit settings, via one or more input devices of the electronic device, one or more and according to a determination that the electronic device is a child device (e.g., a classification of a user account associated with the electronic device or a 8JJJ-8KKK (e.g., changing the usage limit settings on a child device requires a passcode). Require authentication 994 before proceeding (eg, require the user of the electronic device to enter a passcode to change usage limit settings). For example, a determination that an electronic device is a child device is optionally based on a determination that a user account associated with the electronic device (eg, a user currently signed into the device) is classified as a child account. In some embodiments, the determination that the electronic device is a child device is optionally made when the electronic device is set to child device in the device settings (e.g., during initial setup of the device). set). In some embodiments, if the electronic device is a child device within a family account, any of the usage limit settings or preferences or rules described herein may be configured with a password or other authentication on the child device. Changes can be made on the child device only in response to the entry of credentials (e.g., upon determining that one of the settings is about to be changed, the electronic device must be authenticated before the change is allowed). prompts the user to enter a password that must be entered). In some embodiments, the authentication credential is the same as the credential for unlocking the device (e.g., passcode, fingerprint, and/or facial recognition (e.g., normal biometrics) to unlock the device. Attention awareness via depth camera is required for metric authentication)). In some embodiments, the authentication credentials are different than the credentials for unlocking the device (eg, the parent's credentials in the family account). In some embodiments, the parent device can remotely change the above settings in place on the child device (eg, optionally by entering the parent's credentials at the parent device).

In some embodiments, in response to receiving 992 one or more inputs to change one or more usage limit settings, one or more usage limits are set from non-electronic devices via the parent device. Subject to a determination that one or more inputs were received to change a setting (e.g., a usage limit setting change was made on a parent device (e.g., a classification of a user account associated with an electronic device or an electronic device Based on the options selected above, the electronic device is the parent device in the family account)), such as FIG. 8LLL-FIG. , perform 996 one or more usage limit setting changes (eg, perform usage limit setting changes without having to enter additional credentials). For example, the determination that the electronic device is not a child device is optionally based on a determination that the user account associated with the electronic device (e.g., the user currently signed into the device) is not classified as a child account. In some embodiments, the determination that the electronic device is not a child device is optionally made when the electronic device is set to be a parent device in the device's settings (e.g., during initial setup of the device). set). In some embodiments, the electronic device is the parent device. In some embodiments, the electronic device is different than the parent device (eg, the electronic device is a child device). In some embodiments, the parent device remotely modifies usage limit settings on the child device (eg, via the Internet, Bluetooth, or other network or protocol). The manner in which usage limits are set/changed here is the same or similar to the manner in which restricted usage modes are set/changed as described with reference to method 1100 . The above-described method of restricting the ability to change usage limit settings enables an electronic device to efficiently and selectively limit the use of certain applications for specified periods of time, thereby reducing the It reduces the use of electronic devices in between, and also reduces power consumption to improve the battery life of the devices.

In some embodiments, in response to performing one or more usage limit setting changes received from other than the electronic device, the electronic device may be configured to change the usage limit setting for the child device by the parent device, such as FIG. one or more usage limit setting changes (e.g., visual indications (e.g., one or more of text and images); sound indications; , verbal indications, and/or tactile and/or tactile output indications) (e.g., parent device (e.g., user account classification associated with the electronic device or (Based on the option you set, present a notification that the usage limit settings have been changed remotely by the parent device in the family account). For example, the determination that the electronic device is not a child device is optionally based on a determination that the user account associated with the electronic device (e.g., the user currently signed into the device) is not classified as a child account. In some embodiments, the determination that the electronic device is not a child device is optionally made when the electronic device is set to be a parent device in the device's settings (e.g., during initial setup of the device). set). In some embodiments, if a parent device remotely changes the above settings in place on a child device, the child device will receive notification that such remote changes have been made, details of the changes (e.g., parent device changed the usage limit, the parent device changed the time window in which the usage limit is enforced from 10:00 pm to 6:00 am to 9:00 pm to 7:00 am, etc.). The notifications generated on the child device here are the same or similar to the notifications generated on the child device with reference to the restricted use mode described in method 1100 . The above-described method of changing usage limit settings enables an electronic device to efficiently and selectively limit the use of specific applications for specific periods of time, thereby allowing electronic Reduces device usage and, in addition, reduces power consumption and improves device battery life.

In some embodiments, generating one or more inputs for changing one or more usage limit settings received from a parent device other than the electronic device (e.g., on the parent device), such as FIG. a passcode is required on the parent device to change usage limit settings on the child device), the parent device (e.g., user account categories associated with the electronic device or options selected on the electronic device) requires entry of authentication credentials to make usage limit setting changes on the electronic device (998-2) (e.g., the parent device's device (e.g., the parent device in the family account) based on passcode (e.g., optionally different from the authentication credentials for accessing the parent device and/or child device) in response to receiving input to change the usage limit settings from the authenticating adult device). A usage limit passcode or other authentication credential) is optionally required on the parent device to proceed with the usage limit setting change). For example, the determination that the electronic device is not a child device is optionally based on a determination that the user account associated with the electronic device (e.g., the user currently signed into the device) is not classified as a child account. In some embodiments, the determination that the electronic device is not a child device is optionally made when the electronic device is set to be a parent device in the device's settings (e.g., during initial setup of the device). set). The methods described above that require authentication credentials (e.g., passcode, fingerprint, face recognition) to change usage limit settings from the parent device do not allow the electronic device to be usage-limited by the remote device after the authentication credentials are entered. to prevent unauthorized access to a parent's device (e.g. a child has access to an adult's device and uses the adult's device to set usage limits on the child's device). settings), as well as reduce power usage and improve device battery life by allowing users to use the device more quickly and efficiently.

It is understood that the particular order described for the acts in FIGS. 9A-9K is exemplary only and is not intended to represent the only order in which the acts may be performed. want to be Those skilled in the art will recognize various methods for reordering the operations described herein. In addition, details of other processes described herein with respect to other methods described herein (eg, methods 700, 1100, 1300, and 1500) are also described above with respect to FIGS. 9A-9K. Note that method 900 is also applicable in a similar fashion. For example, the usage limits, usage limit settings, etc. on the electronic device described above with reference to method 900 can be set with reference to other methods described herein (e.g., methods 700, 1100, 1300, and 1500). Optionally has one or more of the characteristics described herein, such as usage limits, usage restriction settings, etc., on the electronic device. For the sake of brevity, these details are not repeated here.

Operations in the information processing methods described above may be performed within an information processing device, such as a general-purpose processor (eg, as described above in connection with FIGS. 1A-1B, 3, 5A-5H) or an application-specific chip. is optionally performed by activating one or more functional modules of Further, the operations described above with reference to FIGS. 9A-9K are optionally performed by the components shown in FIGS. 1A-1B. For example, displaying operations 914, 916, 918, 920, 922, 942, and 988 and receiving operations 902, 906, 932, and 990 are optionally performed by event sorter 170, event recognizer 180, and It is executed by the event processing unit 190 . Event monitor 171 of event sorter 170 detects contact on touch screen 504, and event dispatcher module 174 delivers event information to application 136-1. Each event recognizer 180 of application 136-1 compares the event information with respective event definitions 186 and determines that a first touch at a first location on the touch screen is a default event, such as selection of an object on the user interface. It determines whether it corresponds to the event or sub-event of . When the corresponding predefined event or sub-event is detected, the event recognizer 180 activates the event processor 190 associated with detecting the event or sub-event. Event handler 190 optionally utilizes or calls data updater 176 or object updater 177 to update application internal state 192 . In some embodiments, the event handler 190 accesses the corresponding GUI updater 178 to update what is displayed by the application. Likewise, it will be apparent to those skilled in the art how other processes may be implemented based on the components shown in FIGS. 1A-1B.
Limited use mode user interface

Users interact with electronic devices in many different ways and during various times of the day or night. For example, a user can read news updates on a news application installed on an electronic device during the user's morning train commute or in bed at the end of the day. However, in some situations it is difficult for users to monitor and restrict usage of specific applications during specific time periods. Embodiments described below provide a way for an electronic device to efficiently and selectively restrict access to certain applications during certain time periods, thereby allowing users to monitor their own usage. reduce the use of electronic devices during those periods without having to Restricting access to applications during specific periods of time also reduces device power usage and increases battery life in battery-powered devices. It is understood that people use devices. When a person uses a device, that person is optionally called the user of that device.

FIGS. 10A-10AAA illustrate exemplary methods for an electronic device to restrict access to certain applications during certain periods of time, according to some embodiments of the present disclosure. The embodiments in these figures are used to illustrate the processes described below, including the processes described with reference to FIGS. 11A-11I.

FIG. 10A shows an exemplary device 500 having a touch screen 504 as described with reference to FIGS. 5A-5H. Touch screen 504 optionally displays one or more user interfaces including various content. In the example shown in FIG. 10A, the touch screen 504 displays a "restrictions settings" graphical user interface 1002 for defining one or more application restriction settings, such as those described above with reference to FIGS. 6A-6D. . For example, FIG. 10A illustrates a selectable affordance 1004 for defining a "device idle time" (eg, restricted use mode) that the device 500 prevents or attempts to prevent access to certain applications on the device. indicates FIG. 10A shows that selectable device downtime setting affordance 1004 includes information about a limited use mode (eg, that device downtime mode is automatically enabled from 10:00 pm to 6:00 am each day). show. In some embodiments, the device idle time or restricted use mode is a bedtime restricted mode for reducing device usage during a user-defined bedtime period.

Affordances 1004 are selectable to define restricted use mode settings or rules, as described herein. For example, in FIG. 10B, selection of device downtime setting affordance 1004 is detected (eg, by tapping of contact 1003 detected on device downtime setting affordance 1004, as shown in FIG. 10B). In response to selecting the device idle time setting affordance 1004, the device 500 displays a "device idle time" graphical user interface 1010, as shown in FIG. 10C.

FIG. 10C shows an exemplary restricted use mode setting or rule. Device idle time screen 1010, as shown in FIG. end affordance 1013 for defining the end time of the restricted use mode; day affordance 1014 for defining on which day the restricted use mode setting will be implemented; to define if the device 500 will implement a restricted use mode (e.g., under the "notify and block" option or the "notify" option as described with reference to FIGS. 8LL-8GGG) Pause time affordance 1015, verbal affordance 1016 to enable speaking the restricted use mode warning (e.g., with an audible voice that reads the restricted use mode warning or notification aloud), or during the restricted use mode A silent affordance 1017 is included to enable a silent mode (eg, a mode that silences incoming calls and alerts when the device 500 is locked). For example, turning off toggle switch input affordance 1011 optionally disables enforcement of the restricted use mode setting also during the hours and days defined by start affordance 1012, end affordance 1013, and day affordance 1014. will do. In some embodiments, turning toggle switch input affordance 1011 off will preserve the restricted use mode settings or rules defined on device idle time screen 1010, and toggle switch input affordance 1011 is turned on. The setting will be restored when the

In some embodiments, the day affordance 1014 can be selected to display another user interface for defining on which days the restricted use mode setting will be implemented. For example, in FIG. 10D, selection of day affordance 1014 is detected (eg, by tapping contact 1003 detected on day affordance 1014, as shown in FIG. 10D). In response to selection of day affordance 1014, device 500 displays "day" graphical user interface 1020, as shown in FIG. 10E.

FIG. 10E shows an exemplary day graphical user interface 1020 for defining on which days the restricted use mode setting is implemented. Daily graphical user interface 1020 optionally includes a daily affordance 1022 that requires each day of the week to have the same restricted usage start and end times (e.g., device downtime, as shown in FIG. 10C). (as defined by start affordance 1012 and end affordance 1013 in screen 1010). In some embodiments, day graphical user interface 1020 provides affordances 1024a-1024g for defining different start and end times for each day of the week, Monday through Sunday, respectively, as shown in FIG. 10E. include. To define different start and end times for different days of the week by enabling affordance 1022 each day and optionally by disabling affordances 1024a-1024g, as shown in FIG. 10E users are prohibited from using affordances 1024a-1024g to In some embodiments, device 500 visually obscures affordances 1024a-1024g when affordances 1022 are enabled each day (e.g., transforming affordances, by graying out or fading out). In some embodiments, device 500 forgoes displaying affordances 1024a-1024g when affordance 1022 is enabled each day. In some embodiments, by disabling affordance 1022 each day, by enabling affordances 1024a-1024g, as shown in FIG. 10F, different start and/or end times for different days of the week Affordances 1024a-1024g can be used by the user to define the (eg, the user can define start and/or end times for each day). For example, by disabling affordance 1022 every day, the user optionally allows the user to set different restricted use mode start and end times for Friday and Saturday via affordances 1024e and 1024f, as shown in FIG. 10F. can be defined. In some embodiments, enabling the daily affordance 1022 will save different start and end times defined by the affordances 1024a-1024g on the daily graphical user interface 1020, and then the daily affordance 1022 is enabled. These settings will now be restored when disabled.

In some embodiments, as shown in FIG. 10G, the always allow affordance 1006 of the restriction settings user interface 1002 includes a list of applications that do not follow the restricted usage mode rules during restricted usage mode (e.g., an application usage whitelist). ) can be selected to display another user interface for defining the For example, in FIG. 10G, selection of Allow affordance 1006 is always detected (eg, by tapping of contact 1003 always detected on Allow affordance 1006, as shown in FIG. 10G). In response to selecting the Allow Always affordance 1006, the device 500 displays the "Always Allow" graphical user interface 1025, as shown in FIG. 10H.

As shown in FIG. 10H, the device 500 displays a list of applications for which the user does not follow the restricted use mode rules during restricted use mode from the always allowed graphical user interface 1025 (e.g., application whitelist, as shown in FIG. 10H). Allows adding or removing applications from the list 1026). For example, FIG. 10H shows Phone app 1026a, Messaging app 1026b, and FaceTime app 1026c on whitelist 1026. FIG. In some embodiments, always-allow graphical user interface 1025 causes an application corresponding to device 500 to be removed from whitelist 1027 when selected by a user (e.g., subject that particular application to restricted use mode rules). ), including selectable removal affordances 1027 adjacent to specific applications listed on the whitelist 1026 . In some embodiments, certain applications will be permanently on the whitelist 1026 . For example, FIG. 10H shows the phone app 1026a without removal affordances 1027 for removing the phone app 1026a from the whitelist 1026, thus the app 1026a for making or receiving calls on the device 500 is optional. are permanently included on the whitelist 1026. In some embodiments, the always allowed graphical user interface 1025 allows applications on the whitelist 1026 to allow anyone to access contacts stored on the device 500 or with specific contacts stored on the device 500 . Indicates whether restricted use mode rules are not followed during restricted use mode for communication through that particular app. For example, FIG. 10H shows that communication via the Phone app 1026a with anyone is not restricted during the restricted use mode, and the Messages app for all contacts stored on the device 500 during the restricted use mode. 1026b is unrestricted (but optionally restricted to other contacts not stored in Contacts on device 500); Indicates that communication via the FaceTime application 1026c is not restricted. In some embodiments, a user can determine which communications via a whitelisted app during restricted use mode are subject to restricted use mode rules, as described in detail below with reference to FIGS. 10K-10S. It is allowed to change whether or not

In some embodiments, the always allowed graphical user interface 1025 includes a list 1028 of applications (eg, applications 1029a-1029e) that can be added to the whitelist 1026, as shown in FIG. 10H. In some embodiments, applications listed in list 1028 include all applications installed on device 500 . FIG. 10H includes selectable add affordances 1029 adjacent to each of the applications 1029a-1029e that allow the user to add any of the applications 1029a-1029e to the whitelist 1026. FIG. For example, FIG. 10I shows the addition of "app 5" (eg, by tapping contact 1003 detected on additional affordance 1029 adjacent to application 1029e). Upon selection of Add Affordance 1029 adjacent to Application 1029e, App 5 is added to Whitelist 1026, as shown in FIG. 10J.

In some embodiments, one or more of the applications 1026a, 1026b, 1026c, 1026d, and 1029e have separate user interfaces for changing communication limits associated with those applications during the restricted use mode. can be selected to display For example, in FIG. 10K, selection of the phone app 1026a is detected (eg, by tapping contact 1003 detected on the input of application 1026a in whitelist 1026, as shown in FIG. 10K). Upon selection of an entry for application 2016a in whitelist 1026, device 500 optionally displays a "telephone" communication graphical user interface 1030, as shown in FIG. 10L. The telephony graphical user interface 1030 optionally includes two selectable affordances for defining which communications by the telephony app are not subject to restricted use mode rules during restricted use mode. For example, FIG. 10L allows communication (e.g., both incoming and outgoing calls) with anyone via the Phone app in a restricted use mode when selected (e.g., , whether or not the other party's communication information is stored on the device 500) selectable "Anyone" option 1032, when selected, stored on the device 500 via the Phone app in limited use mode A selectable "All Contacts" option 1033 that allows communication with any contacts specified (e.g., both incoming and outgoing calls), and the Phone app in restricted use mode when selected. displays a selectable “designated contacts” option 1034 that allows the user to define which contacts (eg, both incoming and outgoing calls) are allowed to communicate with via .

In some embodiments, the specified contacts option 1034 determines which contacts are allowed to communicate with (e.g., both incoming and outgoing calls) via the Phone app during restricted use mode. You can choose to display information for defining For example, in FIG. 10L, selection of designated contact option 1034 is detected (eg, by tapping detected contact 1003 on designated contact option 1034, as shown in FIG. 10L). Depending on the selection of the designated contacts option 1034, the device 500 will determine which contacts are allowed to communicate via the Phone app while in restricted use mode when selected, as shown in FIG. 10M. , including selectable contacts (eg, contacts 1037a, 1037b, and 1037c) stored on device 500 that define the allowed contacts list 1036. In some embodiments, selecting the designated contact option 1034 also causes the device 500 to add a contact to the list of contacts 1036 that, when selected, allows the user to subsequently select contacts on the device 500. A selectable "add contact" affordance 1038 is displayed that allows the user to enter and store a new contact to be displayed. For example, in FIG. 10M, communication (e.g., both incoming and outgoing calls) is allowed only with contacts A and B, but not with contact C, via the Phone app during restricted use mode. .

In some embodiments, the device 500 displays a contact list for daytime-allowed contacts with which the user is allowed to communicate via certain applications during daytime hours (e.g., other than in restricted use mode). list and a contact list of night allowed contacts who are allowed to communicate via the same application during night hours (e.g. during restricted use mode) (e.g. , as described above with reference to FIG. 10M). For example, FIG. 10N shows detecting selection of phone app 1026a (eg, by tapping contact 1003 detected on input of application 1026a in whitelist 1026, as shown in FIG. 10N). In response to selecting an entry for application 2016a in whitelist 1026, device 500 displays "telephone" communication graphical user interface 1030, as shown in FIG. 10O.

In some embodiments, the “telephony” communication graphical user interface 1030 includes a selectable daytime affordance 1039a and a selectable nighttime affordance 1039b, as shown in FIG. 10O. For example, in FIG. 10P, selection of daytime affordance 1039a is detected (eg, by tapping contact 1003 detected on daytime affordance 1039a, as shown in FIG. 10P). In response to selection of daytime affordance 1039a, device 500 displays "daytime" graphical user interface 1040, as shown in FIG. 10Q. In some embodiments, the daytime graphical user interface 1040 displays any contact via the phone app during daytime hours (eg, other than in restricted use mode), as described above with reference to FIGS. 10L-10M. To define whether communication (e.g., both incoming and outgoing calls) with contacts (e.g., anyone, all contacts, or specified contacts) is allowed to define ). As shown in FIG. 10R, selection of nighttime affordance 1039b is optionally detected (eg, by tapping contact 1003 detected on nighttime affordance 1039b, as shown in FIG. 10R). In response to selection of nighttime affordance 1039b, device 500 displays "nighttime" graphical user interface 1042, as shown in FIG. 10S. In some embodiments, the nighttime graphical user interface 1042 is displayed via the phone app during bedtime hours (eg, during restricted use mode), as described above with reference to FIGS. 10L-10M. To define which contacts (e.g., anyone, all contacts, or specified contacts) or communications (e.g., both incoming and outgoing communications) are allowed (e.g., to define a nightly whitelist). In some embodiments, the daytime and nighttime whitelists are different, as shown in FIGS. 10Q and 10S.

In some embodiments, device 500 is a child device (e.g., the device of a user designated as a child, as opposed to a parent or administrator child device within a family account), as shown in FIG. 10T. . If device 500 is a child device, changing one or more restriction settings on restriction settings graphical user interface 1002 is optionally not allowed and/or optionally entering a passcode. (or other authentication as described in this disclosure is required). In FIG. 10T, passcode affordance 1008 is optionally toggled on permanently for the child device, allowing the user of device 500 to enter a passcode to make any changes on restriction settings graphical user interface 1002 . require you to enter For example, in FIG. 10U, selection of device idle time setting affordance 1004 is detected while passcode affordance 1008 is toggled on (e.g., on device idle time setting affordance 1004 as shown in FIG. 10U by tapping detected contact 1003). In response to selection of device idle time setting affordance 1004, device 500 may prompt the user to enter a passcode before being allowed to make any device idle time setting changes, as shown in FIG. 10V. Display the requesting passcode graphical user interface 1044 . In some embodiments, the passcode graphical user interface 1044 is not displayed by the device 500 until the device restriction settings are changed by the user (e.g., for child devices), as described above with reference to FIGS. The user can view restriction settings, including device idle time and always allow settings without having to enter a passcode). In some embodiments, the passcode requested in FIG. 10V is different than the passcode for logging onto or unlocking device 500 (eg, a passcode specific to the restrictions setting). In some embodiments, a biometric is required instead of a passcode to change restriction settings (eg, as described below in process 1100).

In FIG. 10W, the device 500 allows the user to view usage limits 1048 (eg, usage limits associated with members of a family account and/or device usage limits associated with a family account), and those family limits. (eg, as described above with reference to FIGS. 6C-6D). For example, FIG. 10W shows usage limits 1048 for dad account 1049a, mom account 1049b, and child account 1049c. In some embodiments, family settings graphical user interface 1046 is included within limit settings interface 1002 (eg, as described above with reference to FIGS. 6C-6D).

In some embodiments, each of the dad account 1049a, mom account 1049b, and child account 1049c chooses to display a restriction settings graphical user interface for modifying the restriction settings associated with each of those accounts. It is possible. For example, in FIG. 10X, selection of child account 1049c is detected (eg, by tapping contact 1003 detected on child account 1049c, as shown in FIG. 10X). Upon selection of child account 1049c, device 500 displays child restriction settings graphical user interface 1002 associated with child account 1049c, as shown in FIG. 10Y.

In some embodiments, the parent enters a passcode (or provide other restricted settings authentication such as facial recognition). For example, in FIG. 10Z, the selection of Allow affordance 1006 is always detected (eg, by tapping of contact 1003 always detected on Allow affordance 1006, as shown in FIG. 10Z). In response to selecting Always Allow Affordance 1006, the user enters a passcode before device 500 is allowed to make changes to any restriction settings associated with the child account, as shown in FIG. 10AA. Display the passcode graphical user interface 1044 requesting to do so. In some embodiments, passcode graphical user interface 1044 is not displayed by device 500 until device restriction settings are changed by the user (eg, the parent device's Users can view restriction settings for child devices, including device idle time and always allow settings without having to enter a passcode). In some embodiments, the passcode requested in FIG. 10AA is different than the passcode for logging onto or unlocking the device 500 or child device (eg, a passcode specific to the restrictions setting). In some embodiments, a biometric is optionally entered instead of a passcode to make changes to restriction settings (eg, as described below in process 1100).

FIG. 10BB shows child device 500 displaying home screen 1050 at a time before changes to its restriction settings are changed remotely (eg, by a parent device as described above with reference to FIGS. 10W-10AA). show. FIG. 10CC displays home screen 1050 after the change in the restriction settings has been changed remotely (eg, by the parent device as described above with reference to FIGS. 10A-10S and 10W-10BB). child device 500 is shown. In some embodiments, device 500 generates a notification 1052 to indicate to the child device user that their device sleep time limit has been remotely changed, as shown in FIG. 10CC. For example, the notification 1052 of FIG. 10CC indicates that a new contact has been added to the daytime allowed contacts list on device 500 and that the restricted use mode start time is by the parent associated with the family account (e.g., FIG. 10A-10Q) by Mom).

FIG. 10DD shows device 500 displaying home screen 1050 at a time prior to the start time of the restricted use mode. 10DD, home screen 1050 displays icons 424, 426, 416, 432, 434, 436 for launching or otherwise displaying different applications on device 500, as described above with reference to FIG. 4A. , 440, 442, 454, 446, 450, and 452. Because the device is not in restricted use mode (and because individual or category usage limits have not been set or reached as described with reference to method 900), the user can click icon 424, Any application associated with 426, 416, 432, 434, 436, 440, 442, 454, 446, 450, and 452 can be launched.

In some embodiments, device 500 will display a warning before the device enters restricted use mode. For example, as shown in FIG. 10EE, device 500 displays notification 1054 indicating that device inactivity time (eg, limited use mode) will begin in 30 minutes. In some embodiments, the notification 1054 will include a selectable affordance 1055 that, when selected by the user, dismisses the notification 1054 causing the notification 1054 to disappear. In some embodiments, notification 1054 will automatically disappear (eg, close without user input) after a period of time (eg, 5 seconds, 10 seconds, 20 seconds).

FIG. 10FF shows device 500 displaying home screen 1050 at the start of restricted use mode under the “notification” option of device idle time settings (see, for example, FIGS. 8LL-8PP and 10D described above). as did). In some embodiments, device 500 may be a parent device (eg, a device associated with a parent on a family account) or a standalone device (eg, a device not associated with any family account). can. The device 500 optionally visually obscures the home screen 1050 (e.g., blurs, grays out, or renders the home screen visible) upon initiation of the restricted use mode, as displayed in FIG. 10FF. (changed automatically). In some embodiments, device 500 is displaying a graphical user interface other than home screen 1050 (e.g., applications graphical user interface, notification history graphical user interface, etc.) at the start of restricted use mode, and device 500 , visually obscuring its graphical user interface (eg, blurring, graying out, or visually altering its graphical user interface) at the start of the restricted use mode. In some embodiments, the device 500 displays a description 1056 indicating that the restricted use mode has started, and a dismissal affordance 1057. For example, in FIG. 10FF, selection of overruling affordance 1057 is detected (eg, by tapping touch 1003 detected on overruling affordance 1057, as shown in FIG. 10FF). In response to selection of dismissal affordance 1057, device 500 stops displaying dismissal affordance 1057 and displays extend affordance 1058 and ignore affordance 1059, as shown in FIG. 10GG. In some embodiments, a default or user-defined amount of time (e.g., 5 minutes, 15 minutes, 30 minutes) to extend the start of the limited use mode by selecting affordance 1058 to extend the user Allows the user to delay the start of restricted use mode for a period of time (without changing the actual time set for restricted use mode, until limited use mode is previously defined for future days). continue to be time-triggered) (eg, as described below with reference to method 1100). In some embodiments, the user can forego starting the restricted use mode for that particular day by selecting the ignore affordance 1059 (the actual amount set for the limited use mode). (eg, as described below with reference to method 1100), such that the restricted use mode continues to be triggered at the previously defined time in future days, without changing the time of . In some embodiments, the device 500 displays after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds) or when the user selects any portion of the home screen 1050 (description 1056, extended affordance 1058, and Tapping on (other than Ignore Affordance 1059 ) stops displaying Extend Affordance 1058 and Ignore Affordance 1059 . Under the "Notifications" option, a parent device (e.g. a device associated with a parent on a family account) or a standalone device (e.g. a device not associated with any family account) will notify the user of the Does not require entering any authentication (eg, passcode) to extend or bypass restricted use mode. For example, FIG. 10HH shows parent device 500 displaying home screen 1050 after the user selects either extended affordance 1058 or ignored affordance 1059 under the "notifications" option. Since the device 500 of FIG. 10HH is not in the restricted use mode (eg, because it has been extended), the user can use the icons 424, 426, 416, 432, 434, 436, 440, 442, 452, 446, and any application associated with 450 can be launched. Extending or ignoring the initiation of the restricted use mode optionally launches any application or any application functionality that may otherwise have been restricted (e.g., those access widgets or websites associated with the apps, receive notifications, suggest those apps to the user, etc.).

FIG. 10II shows device 500 displaying home screen 1050 at the start of restricted use mode under the “notify and block” option of device idle time settings (see, eg, FIGS. 8QQ-8GGG and 10D). (as described above). In some embodiments, device 500 may be a parent device (eg, a device associated with a parent on a family account) or a standalone device (eg, a device not associated with any family account). can. Device 500 optionally visually obscures home screen 1050 (e.g., blurs, grays out, or renders the home screen visible) upon initiation of the restricted use mode, as shown in FIG. 10II. (changed automatically). In some embodiments, device 500 is displaying a graphical user interface other than home screen 1050 (e.g., applications graphical user interface, notification history graphical user interface, etc.) at the start of restricted use mode, and device 500 , visually obscuring its graphical user interface (eg, blurring, graying out, or visually altering its graphical user interface) at the start of the restricted use mode. In some embodiments, the device 500 displays a description 1056 indicating that the restricted use mode has started, and a dismissal affordance 1057. For example, in FIG. 10II, selection of overruling affordance 1057 is detected (eg, by tapping contact 1003 detected on overruling affordance 1057, as shown in FIG. 10II). In response to selection of dismissal affordance 1057, device 500 stops displaying dismissal affordance 1057 and displays extend affordance 1058 and ignore affordance 1059, as shown in FIG. 10JJ. In some embodiments, a default or user-defined amount of time (e.g., 5 minutes, 15 minutes, 30 minutes) to extend the start of the limited use mode by selecting affordance 1058 to extend the user Allows the user to delay the start of restricted use mode for a period of time (without changing the actual time set for restricted use mode, until limited use mode is previously defined for future days). continue to be time-triggered) (eg, as described below with reference to method 1100). In some embodiments, the user can forego starting the restricted use mode for that particular day by selecting the ignore affordance 1059 (the actual amount set for the limited use mode). (eg, as described below with reference to method 1100), such that the restricted use mode continues to be triggered at the previously defined time in future days, without changing the time of . In some embodiments, the device 500 displays after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds) or when the user selects any portion of the home screen 1050 (description 1056, extended affordance 1058, and Tapping on (other than Ignore Affordance 1059 ) stops displaying Extend Affordance 1058 and Ignore Affordance 1059 . Under "Notify and Block Options", parent devices (e.g. devices associated with a parent on a family account) or standalone devices (e.g. devices not associated with any family account) can optionally be , requires the user to enter authentication (eg, a passcode) to extend or bypass the restricted use mode on the device. For example, upon selection of either extend affordance 1058 or ignore affordance 1059 of FIG. Display a passcode graphical user interface 1044 requesting the user to enter a passcode before it can be ignored. In some embodiments, the passcode requested in FIG. 10KK is different than the passcode for logging onto or unlocking device 500 (eg, a passcode specific to the restrictions setting). In some embodiments, a biometric is entered instead of a passcode to change the restriction settings (eg, as described below in process 1100).

FIG. 10LL shows the device 500 displaying the home screen 1050 after the user has entered the appropriate passcode within the passcode graphical user interface 1044 of FIG. 10KK under “Notification and Blocking Options”. Since the device 500 of FIG. 10LL is not in restricted use mode (eg, because it has been extended), the user can access the icons 424, 426, 416, 432, 434, 436, 440, 442, 452, 446, and any application associated with 450 can be launched. Extending the initiation of the restricted use mode optionally launches any application or any application functionality that may otherwise have been restricted (e.g., associated with those apps). access widgets or websites provided, receive notifications, suggest those apps to the user, etc.).

FIG. 10MM shows child device 500 displaying home screen 1050 at the start of a restricted use mode with device idle time settings (eg, as described above with reference to FIG. 10D). Child device 500 optionally visually obscures home screen 1050 (e.g., blurs, grays out, or change visually). In some embodiments, the child device 500 is displaying a graphical user interface other than the home screen 1050 (e.g., application graphical user interface, notification history graphical user interface, etc.) at the start of the restricted use mode and the child device 500 visually obscures its graphical user interface (eg, blurs, grays out, or visually alters its graphical user interface) at the start of the restricted use mode. In some embodiments, the device 500 displays a description 1056 indicating that the restricted use mode has started, and a dismissal affordance 1057. For example, in FIG. 10MM, selection of overruling affordance 1057 is detected (eg, by tapping contact 1003 detected on overruling affordance 1057, as shown in FIG. 10MM). In response to selection of overriding affordance 1057, device 500 may stop displaying overriding affordance 1057 to allow more time before a restricted use mode is implemented on device 500, as shown in FIG. Affordances 1060 selectable to request (e.g., extend the start time of the limited use mode) and affordances selectable to request more time on another device (e.g., on the parent device) 1062 (eg, as described above with reference to FIGS. 8TT-8CCC). In some embodiments, by selecting either affordance 1060 or affordance 1062, the limited use mode can be pushed forward into the future day without changing the actual time set for the limited use mode. Parents can delay the start of restricted use mode so that it continues to be triggered at a defined time. For example, in FIG. 10OO, selection of affordance 1062 is detected (eg, by tapping contact 1003 detected on affordance 1062, as shown in FIG. 10OO). Upon selection of affordance 1026, device 500 initiates a process to request more time on another device (eg, as described above with reference to FIGS. 8WW-8CCC). For example, the process for requesting more time on another device optionally sends message 1070 (user-editable) within the messaging user interface to deny the request, as shown in FIG. (e.g., affordance 1068a), extend the start time of the restricted use mode for a predetermined period of time (e.g., affordances 1068b and 1068c), and customize the duration of the extension (e.g., affordance 1068d). Send to device(s) (eg, as described above with reference to FIGS. 8AAA-8CCC). In some embodiments, the process for requesting more time on another device denies the request (e.g., affordance 1068a), restricts use for a predetermined period of time, as shown in FIG. Send message 1066 with affordances to extend the start time of the mode (eg, affordances 1068b and 1068c) and customize the duration of the extension (eg, affordance 1068d).

FIG. 10RR shows device 500 displaying home screen 1050 at a time prior to the start time of the restricted use mode. 10RR, home screen 1050 displays icons 424, 426, 416, 432, 434, 436 for launching or otherwise displaying different applications on device 500, as described above with reference to FIG. 4A. , 440, 442, 454, 446, 450, and 452. Since the device is not in restricted use mode, the user can launch any application associated with icons 424, 426, 416, 432, 434, 436, 440, 442, 454, 446, 450, and 452 without restrictions. can do.

FIG. 10SS shows touch screen 504 displaying home screen 1050 while in restricted use mode. In some embodiments, device 500 prevents or attempts to prevent access to all applications on the device while in restricted use mode, except for applications included on an application use whitelist. In some embodiments, icons corresponding to restricted apps (eg, applications not on the application usage whitelist subject to restrictions during the restricted use mode) are changed during the restricted use mode. For example, icons 424, 432, 436, 442, 454, 450, and 452 correspond to restricted apps and are obscured (e.g., distorted) during the restricted use mode, as shown in FIG. , grayed out, faded out and/or visually modified). In some embodiments, as shown in FIG. 10SS, a placeholder generic indication (eg, lock icon) 1070 is placed over or partially over the icon corresponding to the restricted application. A placeholder generic indication (eg, lock icon) 1070 optionally replaces any unread notification indication corresponding to restricted apps (eg, as shown in FIG. 10SS). In some embodiments, a placeholder generic indicator (e.g., a lock icon) is placed above or adjacent to the text associated with the application icon of the restricted application (e.g., next to the name of the application ).

In some embodiments, icons displayed on home screen 1050 are selectable to launch applications corresponding to those icons (eg, during normal operation other than limited use mode). During restricted use mode, device 500 attempts to prevent access to restricted applications under the "notification" option (eg, as described above with reference to FIGS. 10C and 10FF). For example, under the "notifications" option, a user of device 500 (e.g., parent device or standalone device) can optionally select an icon corresponding to a restricted application while in restricted use mode. . For example, in FIG. 10TT, selection of icon 424 (corresponding to a restricted messaging app) is detected (eg, by tapping contact 1003 detected on icon 424, as shown in FIG. 10TT). In response to selection of icon 424, device 500 optionally visually obscures home screen 1050 (e.g., blurs, grays out, or change visually). In some embodiments, the device 500 displays a description 1056 and a dismiss affordance 1057 indicating that access to the Amessenger app is restricted during the restricted use mode. For example, in FIG. 10UU, selection of overruling affordance 1057 is detected (eg, by a tap of touch 1003 detected on overruling affordance 1057, as shown in FIG. 10UU). In response to selection of dismissal affordance 1057, device 500 stops displaying dismissal affordance 1057 and displays forward affordance 1072, as shown in FIG. 10VV. In some embodiments, the user may access the restricted messaging app during the restricted use mode, as shown in FIG. and later). In some embodiments, the device 500 displays after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds) or any portion of the home screen 1050 (other than the instructions 1056 and affordances 1072 to go) that the user Tapping on stops displaying the forward affordance 1072 .

Device 500 (e.g., parent or standalone device) attempts to prevent access to restricted applications during restricted use mode under the "notify and block" option (e.g., FIGS. 10C and 10II-10). 10LL). In some embodiments, under the "notify and block" option, the user of device 500 can optionally select icons corresponding to restricted applications while in restricted use mode. For example, in FIG. 10XX, selection of icon 424 (corresponding to a restricted messaging app) is detected (eg, by tapping contact 1003 detected on icon 424, as shown in FIG. 10XX). In response to selection of icon 424, device 500 optionally visually obscures home screen 1050 (e.g., blurs, grays out, or visually change) to display a passcode graphical user interface 1044 requesting the user to enter a passcode to access the restricted messaging app during the restricted use mode. In some embodiments, the passcode requested in FIG. 10YY is different than the passcode for logging onto or unlocking device 500 (eg, a passcode specific to the restrictions setting). In some embodiments, a biometric is entered instead of a passcode to change the restriction settings (eg, as described below in process 1100).

In some embodiments, child device 500 attempts to prevent access to restricted applications while in restricted use mode. In some embodiments, the user of child device 500 can select icons corresponding to restricted applications during the restricted use mode. For example, in FIG. 10ZZ, selection of icon 424 (corresponding to a restricted messaging app) is detected (eg, by tapping contact 1003 detected on icon 424, as shown in FIG. 10ZZ). In response to selection of icon 424, child device 500 optionally visually obscures home screen 1050 (e.g., blurs, grays out, or renders the home screen visible), as shown in FIG. 10AAA. select to request access to the Messages app in restricted use mode on the child device 500 (e.g., by requiring the parent to enter a passcode directly on the device 500). possible affordances 1082, and selectable to request access to the Messages app in restricted use mode on another device (e.g., request access granted from the parent device via iMessage or a notification) Display affordances 1084 (eg, as described above with reference to FIGS. 8TT-8CCC and FIGS. 10NN-10QQ).

11A-11I are flow diagrams illustrating a method 1100 of selectively restricting access to applications on an electronic device during restricted use modes, according to some embodiments of the present disclosure. Method 1100 optionally includes device 100, device 300, or device 500 as described above with reference to FIGS. 1A-1B, 2-3, 4A-4B, and 5A-5H. run on electronic devices such as Some acts of method 1100 are optionally combined and/or the order of some acts is optionally changed.

As described below, method 1100 provides a method for selectively restricting access to applications on an electronic device during restricted use modes. This method reduces the use of the electronic device for a specific period of time without requiring the user to monitor the user's use. For battery-operated electronic devices, restricting access to applications during specific periods of time conserves power and increases intervals between battery charging.

In some embodiments, an electronic device that communicates with a display and one or more input devices (e.g., a mobile device that includes a touchscreen, such as device 500 that includes touchscreen 504 , a keyboard, a mouse, a trackpad, and a touchscreen 504 a computer or tablet computer that includes one or more of a touch screen such as; a wearable device such as a smartwatch that includes a touch screen; A mobile phone, tablet computer, etc., such as device 100, device 300, or device 500) is placed into a restricted use mode, such as FIGS. A series of one or more inputs (e.g., from one or more input devices of an electronic device or from a second electronic device different from the electronic device) for defining one or more associated windows of time is received (1102). In some embodiments, the restricted use mode is a bedtime restricted use mode. In some embodiments, the electronic device is a child device and the one or more inputs are received from a parent device associated with and in communication with (eg, wireless communication with) the child device (eg, parent Both device and child device user accounts are associated with family or other group accounts). For example, a user of an electronic device may spend hours of the day (e.g., 10:00 p.m. to 5:00 a.m.) excluding applications whose electronic device, in some embodiments, is included on an application whitelist. Defined as a bedtime restricted usage mode that prevents or attempts to prevent access to all applications on the electronic device. In some embodiments, the user defines the time window above and does not specify any particular application for which access is restricted. In such embodiments, the electronic device optionally defaults to restricting or attempting to restrict the use of all applications except whitelisted applications during restricted use mode.

While the one or more windows of time associated with the restricted use mode are defined (1104), and during the one or more windows of time associated with the restricted use mode, the electronic device: Optionally, input is received 1106 via one or more input devices to start a first of multiple applications installed on the electronic device, such as FIG. 10TT (e.g., one input to open and/or use an application on the electronic device when the above time window is in effect (eg, the application was in use when the restricted use mode was in effect)); In some embodiments, in response to receiving 1108 input to start the first application, the first application adds an application usage whitelist (e.g., restricted access during restricted usage mode). 10TT-10AAA, etc., following a determination that the electronic device is not included in the list of noncompliant applications (e.g., a list of applications that may be fully or partially accessed during the bedtime restricted use mode). , restrict 1110 access to the first application (e.g., prohibit launching the application, restrict the functionality of the application, or indicate bedtime restrictions when the user attempts to launch the application). require further action by the user to launch the application, such as displaying a dialog box requesting further confirmation for the user to proceed to the application). In some embodiments, in response to receiving input to start the first application and following a determination that the first application is included in the application usage whitelist, the electronic device performs provides 1112 access to the first application (eg, launches the application normally as if the restricted use mode is not in effect).

In some embodiments, the one or more time windows associated with the bedtime restricted usage mode are preset by a user of the electronic device or remotely set by a user of a different electronic device in communication with the electronic device. is set by In some embodiments, when the application is launched outside of the bedtime restricted usage mode, the bedtime usage restriction is not enforced (e.g., the application continues to run normally as if the restricted usage mode were not enforced). is activated). In some embodiments, access to the first application is provided with certain restrictions (e.g., the application can be launched but has limited functionality while in Restricted Bedtime Mode). ). For example, the phone application is optionally whitelisted for use to communicate with certain contacts (e.g., relatives), and the phone application is launched with limited communication with other contacts. be done. In some embodiments, the electronic device enters restricted use mode while a restricted application (e.g., an application not on the application usage whitelist) is running, and the restricted application is set to the "notification" restriction option or associated with the "block and notify" restriction option (eg, as described in more detail below). For example, under the "notifications" restriction option, the electronic device displays a pop-up indication above the running application that application usage is currently restricted (e.g., due to bedtime restrictions being enforced). (e.g., obscuring the display of running applications), this indication optionally includes one or more affordances that, when selected, allow the user to continue using the application . Under the "notify and block" restricted option, the electronic device blocks the user from using the application (e.g. blurs the application), and optionally the application usage is currently restricted (e.g. bedtime pop-up indications, including an indication that restrictions are in place) and an indication that an authentication credential (e.g., password, passcode, biometric, or consent from a parent device/account) is required to continue using the application. display on top of running applications (e.g., obscure the display of running applications). Detecting the biometric optionally includes detecting the user's face with a depth camera or another sensor. The restricted use modes described herein are optionally the same or similar to the restricted use modes described with reference to methods 700 , 900 and 1300 . The above-described method of selectively restricting access to applications during a bedtime restricted usage mode enables an electronic device to effectively and selectively restrict use of certain applications during specified periods of time. and thereby reduce use of the electronic device during those periods, as well as reduce power consumption and improve battery life of the device.

In some embodiments, one or more time windows associated with a restricted use mode (e.g., bedtime restricted use mode), such as FIG. one or more windows of time (1114), wherein the one or more windows of time associated with the restricted use mode are different than the first one or more windows of time; is a second one or more time windows on a second day of the week that is different from the day (e.g., different days have different settings (time, usage limits, etc.) for restricted use mode can be done) (1116). For example, the time for bedtime restricted usage mode, in which the electronic device prevents or attempts to prevent access to certain applications on the electronic device, is defined differently for different days of the week (e.g., Monday 10pm to 5am, Saturday 11pm to 6am, weekdays 9pm to 5am, weekends 11pm to 7am). The above-described method of defining different hours of the bedtime restricted usage mode for different days of the week makes the interface between the user and the device more efficient (e.g., the user can specify the hours for the bedtime restricted usage mode). need not be updated daily, thus reducing the input provided to the device by the user (e.g., input to update the time for restricted bedtime usage mode), thereby allowing the electronic device to It allows for an efficient reduction in overall usage, in addition to reducing power consumption and improving the battery life of the device.

In some embodiments, the current time on the electronic device is one or more times associated with the restricted use mode while the one or more windows of time associated with the restricted use mode are defined. 10EE (e.g., 5 minutes, 10 minutes, 1 hour, or any period before the start of the restricted use mode), the electronic device performs the restriction Present 1118 an indication (e.g., text, image, sound, tactile and/or tactile output, etc.) that one or more time windows associated with the restricted use mode is approaching (e.g., limited an indication that the usage mode (eg, bedtime restricted usage mode) is about to be implemented within a threshold amount of time (eg, 5 minutes, 10 minutes, 1 hour, or any period of time). In some embodiments, the threshold time is user defined. In some embodiments, the notification includes text, image(s), and/or sound. In embodiments, the notification includes an indication of haptics and/or tactile output. The above-described method of notifying the user that a restricted use mode is about to be implemented makes the interface between the user and the device more efficient (e.g., the user does not have to monitor the time and can provide the user with an opportunity to finish the task they are currently performing, prompt the user to stop using the device in anticipation of the restricted input to update time for restricted bedtime use mode), which allows the electronic device to effectively reduce overall use of the electronic device, in addition to reducing power consumption. to improve the battery life of your device.

In some embodiments, the indication that one or more time windows associated with the restricted use mode are approaching includes a visual indication (1120), which visual indication is illustrated in FIG. including affordances for delaying initiation of the restricted use mode past one or more windows of time associated with the restricted use mode, such as FIG. can be delayed (e.g., so that the restricted use mode continues to trigger at the previously defined time in future days without changing the actual time set for the restricted use mode). In some embodiments, the affordance includes a predetermined amount of time (e.g., 5 minutes, 15 minutes, 30 minutes) to extend the initiation of the restricted use mode.In some embodiments, the affordance includes: Allows the user to manually change the limited use mode start time (e.g., manually enter a different start time.) In some embodiments, the electronic device enables the user to enter the limited use mode. (e.g., the user can dismiss the restricted use mode for a period of time or for the rest of the day), including the start of the restricted use mode. By delaying the start of the use mode, you can optionally launch any application or any application functionality that might otherwise have been restricted (e.g., any application functionality associated with those apps). accessing widgets or websites, receiving notifications, suggesting those apps to the user, etc.) if the electronic device is a child device in the family account (e.g. device of a user designated as a child as opposed to a parent or administrator of a child), the displayed notification optionally extends the restricted use mode 15 minutes, 30 minutes, 1 hour, etc.) to request permission from the adult/parent device in the family account.In such cases, the selection of requests in the notification Optionally, the notification will be delivered to one or more (or all) parent devices associated with the household account, and permission is granted on at least one of the parent devices. If granted, the electronic device extends the start time of the restricted use mode. In some embodiments, affordances allow users to prevent the electronic device from entering restricted use mode. In some embodiments, app usage exceeding acceptable limits (e.g., even if approved due to extended hours) is optionally indicated within the dashboard user interface described above with reference to method 700 ( 6L-6P, 6EE-6HH, 6OO-6SS, and 6UU). The above-described methods of providing affordances for the user to extend the initiation of the restricted use mode make the interface between the user and the device more efficient (e.g., the user does not need to monitor the time and the current time on the device). provide the user with an opportunity to extend the start time of the restricted use mode in order to finish the task they are performing, and encourage the user to stop using the device in anticipation of the restricted use mode, thus Reducing the input provided to the device by the user (e.g., input to update the time for restricted bedtime usage mode), so that the electronic device effectively reduces overall use of the electronic device. in addition to reducing power consumption and improving device battery life.

In some embodiments, other than one or more windows of time associated with the restricted use mode, one or more application icons associated with applications not included on the application whitelist are is displayed 1122 with a first visual characteristic (e.g., icons for applications that are not on the application whitelist except in restricted use mode are displayed normally, such as in color and not grayed out), and the restricted use During one or more windows of time associated with the mode, one or more application icons associated with applications that are not included on the application whitelist are displayed with a first visual characteristic, such as FIG. 10SS. Displayed 1124 with a different second visual characteristic (eg, icons for applications not on the application usage whitelist during restricted use mode are displayed differently than while not in restricted use mode). For example, for those applications not included on the application whitelist, the icons for those applications are optionally changed to be grayed out in restricted use mode (except in restricted use mode). (compared to the color of ), and/or over the icon for those applications (or partially over any portion thereof) in restricted use mode. In some embodiments, a placeholder generic indicator (eg, lock icon) is placed above or adjacent to the text associated with the application icon. In some embodiments, application icons include one or more visual indications of notifications associated with those applications when the restricted use mode is not in effect (e.g., A badge indicating the number of unread notifications is partially superimposed on the icon). In such embodiments, for those applications not included in the application whitelist, their visual indications are removed, grayed out, number of notifications removed, placeholder generic indicators. (eg, a lock icon) or otherwise changed such that the notification status (eg, number of notifications) of those applications is no longer conveyed by those indications. In some embodiments, all applications not on the application usage whitelist are displayed with a lock icon (in embodiments where the application icon previously included a visual indication of the notification to the application, the lock icons replace notification indications). In some embodiments, icons for applications on the application whitelist are displayed the same (e.g., in color, not grayed out, free accessible, etc.). The above-described method of differently displaying restricted applications during restricted use mode allows a user to determine which applications are restricted, thereby enabling the electronic device to display restricted applications during restricted use mode. By providing an indication of which applications a user has or does not have access to, it is possible to efficiently and selectively limit the use of certain applications for certain periods of time, thereby It reduces the use of the electronic device during those periods, in addition to reducing power consumption and improving the battery life of the device.

In some embodiments, restricting access to the first application causes the electronic device to present an indication that access to the first application is restricted, such as FIG. 10UU. including 1126 (e.g., displaying a visual indication on a display, playing a sound on a speaker associated with the electronic device, haptic(s) and/or tactile output(s) etc., indicating that the application is restricted (e.g. notification)). Optionally, the indication includes selectable affordances (1128) to provide access to the first application without requiring authentication credentials, such as FIGS. graphical user interface elements, links or soft buttons) that allow the user to access restricted applications while in the restricted use mode. In some embodiments, different applications are associated with different restriction options that are implemented during the restricted use mode. For example, the electronic device optionally allows one or more applications to be associated with a "notification" restriction option. If a user attempts to launch an application associated with the "Notifications" restriction (e.g., by selecting the icon for that application from the home screen of the electronic device while in restricted use mode, and the application is list), the electronic device optionally displays a pop-up indication that application usage is currently restricted (e.g., due to bedtime restrictions being enforced). indicate. The pop-up notification optionally provides one or more affordances that, when selected, allow the user to proceed to the application without having to enter any authentication credentials (e.g., without having to enter administrator or other credentials). includes an "Ignore for 1 day" affordance) that opens the application in The method described above notifies the user that the application will be restricted during the restricted use mode, but gives the user the option to access the application nonetheless when needed. effectively restricts the use of specific applications for specific periods of time while allowing the user to perform necessary tasks on the In addition, it reduces power consumption and improves battery life of the device.

In some embodiments, restricting access to the first application includes presenting an indication that the electronic device is restricted access to the first application, such as FIG. 10UU. (1130). Optionally, the indication includes (1132) a selectable affordance to provide access to the first application while requiring authentication credentials, such as FIG. 10VV (e.g., visual indication on a display, play a sound on a speaker associated with the electronic device, generate haptic(s) and/or tactile output, etc., indicate that the application is restricted ( e.g. notifications)). In some embodiments, the electronic device allows one or more applications to be associated with the "notify and block" restriction option. If a user attempts to launch an application associated with a "notify and block" restriction (e.g., by selecting the icon for that application from the home screen of the electronic device while in restricted use mode, and the application application whitelist), the electronic device blocks that application from launching, and optionally, application usage is currently restricted (e.g., bedtime restrictions are display a pop-up indication that In some embodiments, the pop-up indication requests authentication credentials (eg, password, passcode, biometric, or consent from parent device/account) to access the application. Detecting the biometric optionally includes detecting the user's face with a depth camera or another sensor. If the Electronic Device is a child device within a family account (e.g., the device of a user designated as a child as opposed to a parent or administrator within the family account), the displayed notification is optionally restricted Includes affordances for requesting permission from an adult/parent device in the family account to access the application while in attached use mode. In such cases, selection of the request within the notification will optionally result in the notification being delivered to one or more (or all) parent devices associated with the household account, and if permission is granted. The electronic device (eg, at least one of the parent devices or a child device with a passcode) authorizes access to the application. In some embodiments, the parent is required to enter a passcode on the parent device to allow access from the parent device to restricted applications on the child device. The above-described method of blocking the launching of an application while in restricted use mode and informing the user that the application is restricted effectively allows an electronic device to restrict the use of a particular application for a specified period of time. , thereby reducing use of the electronic device during those periods, as well as reducing power consumption and improving the battery life of the device.

In some examples, a determination that the electronic device is not a child device (e.g., not a child device in a family account (e.g., is a parent device in a family account) or not associated with a family account at all) Accordingly, selection of the affordance causes a request to enter a passcode to access the first application (1134), such as FIG. 10YY. In some embodiments, the determination that the electronic device is not a child device is based on a determination that the electronic device is a parent device (e.g., a classification of a user account associated with the electronic device or a option). For example, a determination that an electronic device is a parent device is optionally based on a determination that a user account associated with the electronic device (eg, a user currently signed into the device) is classified as a parent account. In some embodiments, the determination that the electronic device is the parent device is optionally determined when the electronic device is set as the parent device in the device's settings (e.g., during initial setup of the device). set). In some embodiments, the request to enter a passcode will only prompt the user if the appropriate authentication credentials (e.g., password, passcode, biometric, or consent from a parent device/account) are provided when selected. A pop-up notification that optionally includes one or more affordances that allow the to go to the application. Detecting the biometric optionally includes detecting the user's face with a depth camera or another sensor. In some embodiments, affordances include one or more of soft buttons or input field(s) for user IDs, passwords, and/or passcodes. For example, if the device is not a child device within a family account (e.g., is a parent device within a family account) or is not associated with a family account at all, the electronic device is optionally is associated with the user account credentials (e.g., user ID and/or password, passcode) (e.g., the user ID and/or password or passcode associated with the profile with which the device is configured). code). In some embodiments, the credentials (e.g., user ID and/or password, passcode) are different than the credentials for accessing the electronic device (e.g., "unlocking" the device and/or logging into the device). passcode different from the one used to In this way, a user (e.g., child) who is not the device owner (e.g., parent) will not be able to bypass the restricted use mode if the user does not enter a secondary passcode.

In some examples, following a determination that an electronic device is a child device (e.g., based on classification of a user account associated with the electronic device or options selected on the electronic device), selection of affordances is 10MM-FIG. 10QQ, a passcode for accessing the first application (e.g., a parental control pass that is different from the passcode for unlocking the device or accessing a user account associated with device operation). code) and, when selected, initiates a process requiring access to the first application from the parent device (e.g., more from the parent device in the family account). causes the display to present a second affordance (1136), which initiates the process of requesting a time for . For example, a determination that an electronic device is a child device is optionally based on a determination that a user account associated with the electronic device (eg, a user currently signed into the device) is classified as a child account. In some embodiments, the determination that the electronic device is a child device is optionally determined when the electronic device is set as a child device in the settings of the device (e.g., during initial setup of the device). set). In some embodiments, this process will send a message to the parent device requesting access to the first application (e.g., a text message or any other alert on the parent device, the parent (singular) (or multiple) to the email account associated with it). This process then begins when the parent authorizes the child device to access restricted applications (e.g., the parent chooses to allow the child device to access restricted applications while in restricted use mode). or deny access to restricted applications on child devices. In some embodiments, the electronic device presents an affordance to enter a passcode and/or initiate a process of requesting access to the first application. In some embodiments, the passcode is a parental control passcode or use passcode that is different from the passcode for unlocking the electronic device. In this way, the child is optionally unable to circumvent the restricted access mode, but the parent optionally has a passcode that allows the electronic device to access the first application. can be entered. In some embodiments, the parent is required to enter a passcode on the parent device to allow access from the parent device to restricted applications on the child device. The above-described method of notifying the user that the application will be restricted during the restricted use mode, but allowing the user the option to access the application nonetheless when needed is an electronic device that allows the user to access the electronic Effectively restricting the use of specific applications for specific periods of time while still allowing necessary tasks to be performed on the device, thereby preserving the electronic device during those periods. Reduce usage, in addition to reduce power consumption and improve device battery life.

In some embodiments, the electronic device, via one or more input devices, is configured to perform one or more restricted usage modes, such as FIG. Receive 1138 a sequence of one or more inputs for activating or deactivating enforcement of the usage mode restrictions (e.g., during one or more time windows associated with the restricted usage mode). Manually turn on or off enforcement of restricted use mode on the electronic device according to the restricted use mode restrictions). Turn off enforcement of restricted usage mode rules that define usage restrictions between, for example, the hours of 10:00 p.m. and 7:00 a.m. (e.g., one or more time windows associated with restricted usage mode) will override usage restrictions during the hours 10:00 pm to 7:00 am (eg, during vacations). Conversely, turning on enforcement of the same restricted usage mode rules would enable those usage restrictions between the hours of 10:00 PM and 7:00 AM. In some embodiments, enforcement of restricted use mode rules can be toggled on or off during one or more time windows associated with the restricted use mode or otherwise (e.g., The electronic device enters (if toggled on outside of the one or more time windows) or exits (one or more controls if) is toggled off for a window of time). In some embodiments, the electronic device configures the usage restriction settings ( For example, store user-defined start time(s), end time(s), whitelist(s), etc.). For example, when the restricted use mode rule enforcement is turned back on (after being turned off), the electronic device optionally reverts to the same restricted use mode rule set up before the restricted use mode was turned off. Enforce restricted use mode restrictions according to usage mode rules (eg, enforce restricted use mode between 10pm and 7am when restricted use mode is toggled back on). In some embodiments, following a determination that enforcement of one or more restricted use mode restrictions has been turned on, the electronic device implements one or more restricted use mode restrictions, such as FIG. 10C (1140 ) (eg, operating the electronic device outside of the restricted use mode or in the restricted use mode (according to the restricted use mode rules)). For example, while in the restricted use mode, the electronic device may prohibit launching restricted applications, limit the functionality of restricted applications, and indicate bedtime restrictions when the user attempts to launch restricted applications. to require further action by the user to launch the restricted application, such as displaying a dialog box requesting further confirmation from the user to proceed to the application. In some embodiments, access to the first application is provided with certain restrictions (e.g., the application can be launched but has limited functionality while in Restricted Bedtime Mode). ). For example, the phone application is optionally whitelisted for use to communicate with certain contacts (e.g., relatives), and the phone application is launched with limited communication with other contacts. be done.

In some embodiments, following a determination that one or more restricted use mode restriction enforcements have been turned off, the electronic device enforces one or more restricted use mode restrictions, such as FIGS. suspending 1142 (e.g., without depending on whether the current state of the electronic device (e.g., the current time) would otherwise cause the device to operate in a restricted operating the electronic device out of the restricted use mode while enforcing the restricted use mode is turned off). For example, outside of the restricted use mode, the electronic device allows applications to launch normally as if the restricted use mode had not been enforced. In some embodiments, when the application is launched outside of the bedtime restricted usage mode, the bedtime usage restriction is not enforced (e.g., the application continues to run normally as if the restricted usage mode were not enforced). is activated). In some embodiments, the electronic device provides a toggle switch to toggle on or off enforcement of the restricted use mode. Thus, even if the current time is within one or more restricted use time windows, but the restricted use mode is turned off, the restrictions associated with the restricted use mode are not enforced. The above-described method by which a user can manually enforce or not enforce restricted use mode rules enables an electronic device to customize the restricted use mode enforcement as desired by the user, thereby: Selectively reducing use of electronic devices, in addition to reducing power consumption and improving battery life of the devices.

In some embodiments, restricting access to the first application includes presenting 1144 one or more verbal indications that access to the first application is restricted (e.g. , in some embodiments, in addition to the visual notification(s) described above, an audible voice indicates that access to the application is restricted). In some embodiments, the electronic device determines that the restricted use indication is to be spoken (e.g., based on specifications in a user account associated with the electronic device or based on electronic device settings). ) only perform verbal notification. For example, the electronic device optionally provides an option that the user can select or not to provide (or not) the notification audibly in addition to or instead of providing the notification visually. I will provide a. In some embodiments, the electronic device optionally does not perform verbal notification (e.g., that access to the application is restricted) following the determination that the restricted use indication is not to be spoken. display the notification without an audible indication of In some embodiments, the notification optionally includes sound (eg, chimes, alerts, music, etc.) without audio reading the notification. In some embodiments, any of the notifications described herein may be electronic, for example, to facilitate providing such notifications to users (e.g., children) who may not be able to read or see such notifications. It can be audibly generated by the device (eg, read to the user of the electronic device). The above-described method of providing an audible notification while restricting access to an application while in a restricted use mode allows the electronic device to enter the restricted use mode while optionally not displaying additional information. It allows you to effectively limit the use of certain applications for a period of time, thereby reducing power consumption and improving the battery life of your device.

In some embodiments, telephony applications on the electronic device (e.g., applications that enable incoming and outgoing audio and/or video calls on the electronic device) are permanently included in the application usage whitelist (1146) ( For example, access to the Phone app is not restricted during restricted use mode). In some embodiments, the electronic device has telephony functionality (e.g., can make calls, receive calls, etc.) performed using a telephony application installed on the electronic device, such as FIG. ) (eg, in the same way other applications such as messaging applications, email applications, video applications, etc. are installed on electronic devices). In such embodiments, the telephony application is optionally always (eg, permanently) included in the application whitelist so that restricted use mode restrictions are not applied to the telephony application. Accordingly, the user can optionally use the telephony application as normal whether or not the restricted use mode is in effect. In some embodiments, the phone application is permanently included in the application usage whitelist only for certain designated contacts (e.g., the phone application is only allowed to contact certain contacts). freely available), the use of the phone application to communicate with other contacts can be restricted. The above-described method of allowing access to telephony operations while restricting access to other applications while in the restricted use mode prevents the electronic device from using certain communication applications while in the restricted use mode. It allows usage to be efficiently limited, thereby reducing power consumption and improving battery life of the device.

In some embodiments, while the one or more windows of time associated with the restricted use mode are defined and during the one or more windows of time associated with the restricted use mode ( For example, during a restricted use mode (eg, bedtime mode), communication operations using a telephony application (eg, call, text message, email, and/or video conferencing operations) are shown in FIGS. 10J-10M. are permissible 1148 for anyone, such as (e.g., communication behavior is not restricted to any particular contact during restricted use mode), or multiple contacts on the electronic device is permissible only for one or more of the designated contacts in the (restricted to contacts in groups or contacts on a whitelist). In some embodiments, the contacts with which the telephony application can communicate without restriction can be defined on the electronic device. For example, the electronic device optionally allows the phone application to access all contacts (e.g., the "Anyone" setting) or a specified subset of contacts (e.g., "Contacts") without restrictions during the restricted use mode. "Settings") and provide settings for being able to communicate (eg, make calls, receive calls, etc.). In some embodiments, the electronic device can only be used by selected individuals (e.g., contacts on the electronic device, or only certain contacts on the electronic device) without restrictions during the restricted use mode. Provide a user interface with which you can communicate. Communication with other individuals is optionally restricted in the manner described above (e.g., not allowed, not allowed without user ID/password, passcode, biometric, or permission from parent device, etc.) . The above-described method by which a user can selectively restrict access to communication operations to specific contacts while in a restricted use mode is provided when an electronic device is enabled for a specific communication application while in a limited use mode. It allows usage to be efficiently limited, thereby reducing power consumption and improving battery life of the device.

In some embodiments, communication operations include incoming and outgoing calls (eg, outgoing and/or incoming phone calls, emails, text messages, and video conference calls) (1150). During the restricted use mode, the electronic device prevents communication (eg, blocks calls, text messages, video conference requests, etc.) from anyone not designated for communications during the restricted use mode. The above-described method by which a user can selectively restrict access to communication operations to specific contacts while in a restricted use mode is provided when an electronic device is enabled for a specific communication application while in a limited use mode. It allows usage to be efficiently limited, thereby reducing power consumption and improving battery life of the device.

In some embodiments, the electronic device receives contact information (e.g., receive (1152) from another electronic device (eg, from a parent device). In some embodiments, the electronic device allows communication with the first contact (1154) during a restricted usage mode, such as FIG. , to allow communication operations to be performed for a first contact (when communication operations are allowed only with designated contacts on the electronic device during restricted use mode). In some embodiments, the electronic device automatically stores the received contact information for the first contact among multiple contacts stored on the electronic device. Optionally, the electronic device and another electronic device are associated (1156) with the same user group account (eg, "Family" or "Family Shared" account), such as FIG. 10W. In some embodiments, the other electronic device is a parent's device within the family account. In such embodiments, the parent device may share one or more of the parent's contacts (eg, contact information such as name, phone number, email address, etc.) with the child device. For example, a parent device can send and store contact information about contacts on the parent device to the child device by selecting the "share with child device" affordance on the parent device (e.g., the child's contacts without the need to specify information or specify the target device to send contact information to). In some embodiments, parents are required to enter a passcode on the parent device in order to send and save contact information on the child device. The above-described method by which a user can selectively restrict access to communication operations to specific contacts while in a restricted use mode is provided when an electronic device is enabled for a specific communication application while in a limited use mode. It allows usage to be efficiently limited, thereby reducing power consumption and improving battery life of the device.

In some embodiments, one or more designated contacts of a plurality of contacts on an electronic device (e.g., contacts stored on the electronic device, contacts on the electronic device, such as FIG. 10M). Contacts in specified groups, or contacts on a whitelist while restricted use mode is enabled, are customizable 1158 (e.g., contacts can be added to the contact whitelist ( For example, contacts whose communication behavior is not restricted during the restricted use mode can be added to or removed from). In some embodiments, certain contacts not included in or on the contact whitelist are controllable by the electronic device. For example, certain contacts on an electronic device can be designated as "acceptable" or "unrestricted" so that communication with those contacts during restricted use mode is not restricted (e.g., other Communication with contacts or individuals is optionally restricted during restricted use mode). In some embodiments, these "unrestricted" contacts are defined on the electronic device itself (eg, within the settings user interface of the electronic device itself). In some embodiments, these "unrestricted" contacts are defined on another device (e.g., if the current device is a child device within a family account, the parent device within the family account will be the child device ). In some embodiments, the parent is required to enter a passcode on the parent device to define "unrestricted" contacts on the child device from the parent device. The above-described method by which a user can selectively restrict access to communication operations to specific contacts while in a restricted use mode is provided when an electronic device is enabled for a specific communication application while in a limited use mode. It allows usage to be efficiently limited, thereby reducing power consumption and improving battery life of the device.

In some embodiments, an electronic device enabled for communicative operation during one or more time windows associated with a restricted use mode (e.g., during a restricted use mode (e.g., bedtime mode)). One or more designated contacts of the plurality of contacts on the device are enabled for communication operations outside of one or more time windows associated with the restricted use mode, such as FIGS. 10O-10S. different from the second one or more specified contacts (eg, a whitelist of daytime contacts whose communication is not restricted during the restricted use mode) (1160). In some embodiments, the daytime contact whitelist is different than the bedtime contact whitelist (eg, contacts whose communication activity is not restricted during restricted use mode). For example, if the restricted use mode is set to be from 10:00 p.m. to 6:00 a.m., the application and/or contact whitelist between 10:00 p.m. Different applications and/or contacts whitelist between 6:00 am and 10:00 pm (eg, different applications and/or contacts can be restricted differently between the two periods). In some embodiments, a particular contact may be listed on both the daytime contact whitelist and the bedtime contact whitelist (e.g., the contact may optionally be listed on both whitelists). superimposed within). In some embodiments, the daytime contact whitelist is the same as the bedtime contact whitelist. In some embodiments, communication operations with contacts not on the daytime contact whitelist are restricted outside of the restricted use mode. In some embodiments, a parent can set or update the daytime and/or bedtime contact whitelist from the parent device. In some embodiments, a parent is required to enter a passcode on the parent device in order to set or update the daytime and/or bedtime contact whitelist on the child device from the parent device. The above-described method by which a user can selectively restrict access to communication operations to specific contacts during limited use mode and otherwise is provided by an electronic device that allows a user to selectively restrict access to certain contacts while in a limited use mode. It allows the use of communication applications to be efficiently limited, thereby reducing power consumption and improving device battery life.

In some embodiments, the electronic device, via one or more input devices, whitelists a second application of multiple applications installed on the electronic device, such as FIGS. Input to add is received (1162). During the one or more windows of time associated with the restricted use mode are defined, and during the one or more windows of time associated with the restricted use mode, the second application continues to use the application. Following its determination to be included in the whitelist, the electronic device provides 1164 access to a second application, such as FIG. to add). In some embodiments, any application installed on the electronic device can be added to the application whitelist either within the settings user interface of the electronic device itself or via another device (e.g. , if the current device is a child device within the family account, then the parent device within the family account is defined for the child device). In some embodiments, a parent is required to enter a passcode at the parent device in order to set or update the application whitelist on the child device from the parent device. The above-described method by which a user can selectively restrict access to certain applications while in a restricted use mode allows an electronic device to effectively restrict use of certain communication applications while in a restricted use mode. limits, thereby reducing power consumption and improving device battery life.

In some embodiments, the electronic device receives one or more inputs to change one or more restricted use mode settings associated with the restricted use mode (1166), such as FIG. 10F ( (e.g. changing start/end times for restricted use mode, changing whitelists, etc.). one or more restricted use modes via one or more input devices of the electronic device in response to receiving 1168 one or more inputs to change one or more restricted use mode settings; One or more inputs to change settings are received and in accordance with a determination that the electronic device is a child device (e.g., based on the classification of a user account associated with the electronic device or options selected on the electronic device) 10T-10V), the electronic device requires authentication (1170) before performing one or more restricted use mode setting changes, such as FIGS. require the user of the electronic device to enter a passcode). For example, a determination that one or more inputs have been received at the child device to change one or more restricted use mode settings is optionally determined by a user account associated with the electronic device (e.g., based on the determination that the currently signed-in user) is classified as a child account. In some embodiments, the determination that one or more inputs have been received at the child device to change one or more restricted use mode settings optionally indicates that the electronic device has changed the settings for the child in the device's settings. Based on a determination that it is configured as a device (eg, configured during initial setup of the device). In some embodiments, if the electronic device is a child device within a family account, any of the restricted use mode settings or preferences or rules, etc., described herein are password or other (e.g., upon determining that one of the settings is about to be changed, the electronic device may authenticate before the change is allowed). prompts the user to enter a password that must be entered). In some embodiments, the authentication credential is the same as the credential for unlocking the device (eg, passcode for unlocking the device). In some embodiments, the authentication credentials are different than the credentials for unlocking the device (eg, the parent's credentials in the family account). In some embodiments, the parent device can remotely change the above settings in place on the child device (eg, optionally by entering the parent's credentials at the parent device). In some embodiments, parents are required to enter a passcode on the parent device in order to remotely change the above settings on the child device. In response to receiving 1168 one or more inputs for changing one or more restricted use mode settings, one or more inputs for changing one or more restricted use mode settings are provided. In accordance with a determination received from a non-electronic device via the parent device (e.g., a restricted use mode change was made on the parent device), the electronic device performs one or more Perform 1172 a restricted use mode setting change (eg, change the restricted use mode without having to enter additional credentials). For example, a determination that one or more inputs to change one or more restricted use mode settings has been received via a parent device is, optionally, a user account (e.g., , the user currently signed into the device) is classified as a parent account. In some embodiments, the determination that one or more inputs to change one or more restricted use mode settings has been received via the parent device is optionally determined by the other device Based on the determination that it is set as the parent device in the settings (eg, set during initial setup of the device). In some embodiments, the electronic device is the parent device. In some embodiments, the electronic device is different than the parent device (eg, the electronic device is a child device). In some embodiments, the parent device remotely modifies the restricted use mode setting on the child device (eg, over the Internet, Bluetooth, or other network or protocol). In some embodiments, a parent is required to enter a passcode on the parent device in order to remotely change the restricted use mode setting on the child device. The above-described method of restricting the ability to change restricted use mode settings enables an electronic device to efficiently and selectively limit the use of specific applications for specific periods of time, thereby allowing them to In addition to reducing power consumption and improving battery life of the device.

In some embodiments, in response to performing one or more restricted use mode setting changes received from other than the electronic device, the electronic device performs one or more restricted use mode setting changes, such as FIG. Present 1174 an indication (e.g., visual indication (e.g., one or more of text and images), sound indication, verbal indication, and/or tactile and/or tactile output indication) regarding ) (e.g. presenting a notification that the restricted use mode setting has been remotely changed by the parent device). In some embodiments, if a parent device remotely changes the above settings in place on a child device, the child device will receive notification that such remote changes have been made, details of the changes (e.g., parent device has changed the time window in which the restricted use mode is implemented from 10:00 pm to 6:00 am to 9:00 pm to 7:00 am, etc.). The above-described method of changing restricted use mode settings enables an electronic device to efficiently and selectively limit the use of certain applications for specified periods of time, thereby reducing reduce the use of electronic devices, as well as reduce power consumption and improve device battery life.

In some embodiments, other than one or more windows of time associated with the restricted use mode, the electronic device may display one or more representations of applications installed on the electronic device (e.g., , icons, widgets, windows of the first application) in a multitasking view along with other windows of other applications (1176). For example, the electronic device displays one or more application windows associated with one or more applications (e.g., within a multitasking graphical user interface view), or the electronic device displays the application windows on the home screen of the electronic device. Displays one or more icons for launching . The one or more representations include a first representation of the first application in a first visual characteristic (e.g., in color, without obscuring, etc., on the electronic device when not in the restricted use mode). Display normal icons for installed applications (eg, within the home screen of the electronic device)). In some embodiments, during 1178 one or more windows of time associated with the restricted use mode (eg, upon initiation of one or more windows of time associated with the restricted use mode). ), an application usage whitelist (e.g., a list of applications to which the first application does not obey restricted access during restricted use mode (e.g., has full or partial access during restricted use mode). ), the electronic device displays (1180) a first representation of the first application in a second visual characteristic different from the first visual characteristic, such as FIG. 10SS (eg, , the representation of an application that is not on the application whitelist looks different than the representation of an application that is not on the application whitelist). In some embodiments, while in restricted notification mode, the electronic device modifies the appearance of various aspects of applications that are not included in the application whitelist. For example, icons for applications not included in the whitelist (e.g., icons on the home screen of the device) may be shaded during limited use mode and/or , a placeholder generic indicator is displayed over the icon for those applications (or partially over any part of it). In some embodiments, a placeholder generic indicator (eg, lock icon) is placed above or adjacent to the text associated with the application icon. As another example, notification badges included on application icons for applications not included in the application whitelist are optionally changed as described above. As another example, in some embodiments, the electronic device has multitasking capabilities in which the electronic device displays a user interface that optionally displays visual representations of more than one application simultaneously (e.g., icons from multiple applications at the same time, screenshots of the current user interface of multiple applications at the same time, multiple application windows for different applications are presented at the same time, the user interface, etc.). In some embodiments, during the restricted use mode, the representation for applications not in the application whitelist within the multitasking user interface is altered by the electronic device (e.g., faded out or shaded, or otherwise modified to be displayed with different visual characteristics than representations corresponding to applications included in the application whitelist). In some embodiments, during 1178 one or more windows of time associated with the restricted use mode (eg, upon initiation of one or more windows of time associated with the restricted use mode). ), and following a determination that the first application is included in the application usage whitelist, the electronic device displays a first representation of the first application in a first visual characteristic, such as FIG. 10SS (1182 ) (eg, the presentation appearance for applications included on the application whitelist continues to display with the same visual characteristics during the restricted use mode). The above-described method of selectively altering the appearance of representations of applications not on the application whitelist during restricted use mode allows the electronic device to determine which applications the user does or does not have access to while in the restricted use mode. By providing an indication of this, it is possible to efficiently and selectively limit the use of certain applications during certain periods of time, thereby reducing the use of the electronic device during those periods. In addition, it reduces power consumption and improves device battery life.

In some embodiments, displaying the first representation of the first application with the second visual characteristic restricts access to the first application on the first representation, such as FIG. 10SS. displaying 1184 a restricted use badge (e.g., overlaid on those application icons or any portion(s) of those application icons (e.g., the upper right portion of the icon). a badge with a visual indication of a lock or some other restriction added to the application icon such as mating). In some embodiments, a restriction symbol (eg, lock icon) is placed above or adjacent to the text associated with the restricted application icon. In some embodiments, application icons include one or more visual indications of notifications associated with those applications when the restricted use mode is not in effect (e.g., A badge indicating the number of unread notifications is partially superimposed on the icon). In such embodiments, for those applications not included in the application whitelist, their visual indications are removed, grayed out, number of notifications removed, placeholder generic indicators. (eg, a lock icon) or otherwise changed such that the notification status (eg, number of notifications) of those applications is no longer conveyed by those indications. The above-described method of selectively changing the appearance of representations of applications that are not on the application whitelist during restricted use mode allows the electronic device to overwrite restricted applications that the user does not have access to during the restricted use mode. Displaying usage badges allows for efficient and selective restriction of use of particular applications for specific periods of time, thereby attempting to allow users to access such restricted applications. In addition, it reduces the use of the electronic device during those periods, thereby reducing power consumption and improving the battery life of the device.

In some embodiments, displaying the first representation of the first application with the first visual characteristic, such as FIGS. displaying 1186 a first representation having a notification badge (e.g., an indicator of unread messages, missed calls, etc.) including a number of unread messages, missed calls, etc.; Displaying the first representation of the application includes displaying 1188 the first representation with the notification badge replaced by the limited use badge (e.g., blurring the indicator or replacing the indicator with a graphic). ). In some embodiments, the lock badge described above replaces the notification badge indication on the application icon for non-whitelisted applications during the restricted use mode time window(s), as described above. The above-described method of selectively changing the appearance of representations of applications that are not on the application whitelist during restricted use mode is such that the electronic device, while in the restricted use mode, notifies the user of the indication of the representation of the application. by replacing it with a restricted use badge on applications that do not have a By not indicating that the to improve the battery life of your device.

It is understood that the particular order described for the acts in FIGS. 11A-11I is exemplary only and is not intended to represent the only order in which the acts may be performed. want to be Those skilled in the art will recognize various methods for reordering the operations described herein. In addition, details of other processes described herein with respect to other methods described herein (eg, methods 700, 900, 1300, and 1500) are also described above with respect to FIGS. Note that method 1100 is also applicable in a similar fashion. For example, the restricted use modes, use limit settings, etc. described above with reference to method 1100 are described herein with reference to other methods described herein (e.g., methods 700, 900, 1300, and 1500). It optionally has one or more of the characteristics described in the document, such as restricted use mode, use limit setting, etc. For the sake of brevity, these details are not repeated here.

Operation in the information processing methods described above may be performed by an information processing device, such as a general-purpose processor (eg, as described above in connection with FIGS. 1A-1B, 3, and 5A-5H) or an application-specific chip. is optionally performed by activating one or more functional modules within. Moreover, the operations described above with reference to FIGS. 11A-11I are optionally performed by the components shown in FIGS. 1A-1B. For example, displaying operations 1122, 1124, 1176, 1180, 1182, 1184, 1186, and 1188, and receiving operations 1102, 1106, 1138, 1152, 1162, and 1166 are optionally performed by event sorter 170. , the event recognition unit 180 and the event processing unit 190 . Event monitor 171 of event sorter 170 detects contact on touch screen 504, and event dispatcher module 174 delivers event information to application 136-1. Each event recognizer 180 of application 136-1 compares the event information with respective event definitions 186 and determines that a first touch at a first location on the touch screen is a default event, such as selection of an object on the user interface. It determines whether it corresponds to the event or sub-event of . When the corresponding predefined event or sub-event is detected, the event recognizer 180 activates the event processor 190 associated with detecting the event or sub-event. Event handler 190 optionally utilizes or calls data updater 176 or object updater 177 to update application internal state 192 . In some embodiments, the event handler 190 accesses the corresponding GUI updater 178 to update what is displayed by the application. Likewise, it will be apparent to those skilled in the art how other processes may be implemented based on the components shown in FIGS. 1A-1B.
Suppress auxiliary application functionality within the user interface

Users interact with electronic devices in many different ways and during various times of the day or night. For example, a user can read news updates on a news application installed on an electronic device during the user's morning train commute or in bed at the end of the day. However, in some situations it is difficult for users to monitor and restrict usage of specific applications during specific time periods. Embodiments described below enable the electronic device to enable the auxiliary functions of certain applications to one or more Provide a method of throttling once the restriction criteria for those particular applications are met, such as for a period of time. By suppressing the application's auxiliary functions when the restriction criteria are met, the electronic device can effectively reduce the overall usage of the electronic device, thus reducing the device's power usage and reducing the power usage of the battery-powered device. increases battery life with respect to It is understood that people use devices. When a person uses a device, that person is optionally called the user of that device.

FIGS. 12A-12BB are exemplary electronic devices that inhibit certain application ancillary features when an application usage limit or restriction criteria associated with those applications is reached, according to some embodiments of the present disclosure. Show how. The embodiments in these figures are used to illustrate the processes described below, including the processes described with reference to Figures 13A-13H.

FIG. 12A shows an exemplary device 500 having a touch screen 504 as described with reference to FIGS. 5A-5H. Touch screen 504 optionally displays one or more user interfaces including various content. In the example shown in FIG. 12A, the touch screen 504 indicates that the restriction criteria are not met on the device 500 (e.g., the user-defined usage limits have not been reached and one or more display the home screen 1202 during a user-defined time window). In some embodiments, as described above with reference to methods 700 and 900, the limit criterion is met when the usage limit for a given application or category of applications has been reached. In some embodiments, the limit criteria are met during one or more time windows associated with the limited use mode, as described above with reference to method 1100 . 12A, home screen 1202 displays icons 424, 426, 416, 432, 434, 436 for launching or otherwise displaying different applications on device 500, as described above with reference to FIG. 4A. , 440, 442, 444, 448, 450, and 452. As shown in FIG. 12A, one or more application icons optionally include notification indicators 1204 that notify the user of any unread notifications associated with the application. For example, notification indicator 1204 in FIG. 12A indicates that there are three unread messages in Messages app 424 . In some embodiments, the notification indicator 1204 is a badge superimposed over (or partially over) the appropriate icon, as shown in FIG. 12A.

12B-12C, a horizontal swipe of contact 1203 is detected on touch screen 504 while home screen 1202 is displayed, causing device 500 to display a search user interface when the restriction criteria are not met on device 500 . 1207 is displayed. Search user interface 1207 optionally searches for content accessible from device 500 (e.g., websites, news, email, applications installed on device 500, applications available for download to device 500, Calendar items, etc.) is the operating system user interface of device 500 . A search user interface 1207, as shown in FIG. 12C, optionally provides a text field 1204 for entering one or more search terms to search for content accessible from device 500, which the operating system of device 500 provides to the user. "App Suggestions" user interface 1208 for displaying applications suggested to the device 500 (e.g., suggesting commonly used applications, recently used applications, favorite applications, currently running applications), and device 500 including widgets 1210 corresponding to applications installed thereon (e.g., user interface objects or windows containing text, image(s), and/or any other content associated and updated by the corresponding application); . For example, in FIG. 12C, the app suggestions user interface 1208 includes the Photos app 428, the Workout Support app 442, the Messages app 424, and the Social Media A app 452, as well as widgets 1210a and "Contacts" corresponding to the "Social Media App A" application. ' contains a widget 1210b corresponding to the application.

In FIG. 12D, the user has entered the search term “social media” into text field 1204 when the restriction criteria are not met on device 500 . In response to the search term “social media” entered into text field 1204, device 500 displays various search results related to the search term “social media” in search user interface 1207. FIG. For example, the device 500 provides a link 1212a to the social media application "Social Media A" installed on the device 500, a link 1212b to the social media website "Social Media A", which is a website about the "Social Media A" app. , and affordances to two social media applications available for download from the App Store (e.g., application storage location), affordance 1212c for downloading "Social Media B" and downloading the "Social Media C" application. display affordance 1212d for

FIG. 12E shows that a new message is being received at device 500 while device 500 is displaying home screen user interface 1202 when the restriction criteria are not met on device 500 . In some embodiments, the event of receiving a message on device 500 corresponds to activation of a feature that displays a notification about new messages on device 500 . For example, FIG. 12F shows device 500 displaying notification 1214 indicating that a new message has been received for messaging app 424 in response to receiving the message in FIG. 12E. In some embodiments, the event of receiving a new message corresponds to the activation of other auxiliary functions, such as updating the unread message indicator on the application icon. For example, FIG. 12F shows that in response to detecting a new message for Messages app 424, Messages app 424 now has 4 unread messages (including the newly received message). Device 500 is shown updating indicator 1204 on app 424 .

FIG. 12G illustrates that the restriction criteria for Messages app 424 and Social Media A app 452 are met on device 500 when new messages for Messages app 424 and Social Media A app 452 are being received on device 500 (e.g., user A touch screen displaying home screen 1202 when a defined usage limit has been reached and/or the current time is within one or more user-defined time windows associated with a restricted usage mode. 504 is shown. In some embodiments, icons corresponding to restricted apps are changed while the restriction criteria for those apps are met. For example, icons 424 and 452 corresponding to Restricted Messages app 424 and Social Media A app 452 are obscured (e.g., distorted, grayed out) while the restriction criteria for those apps are met. faded out and/or visually altered). FIG. 12G shows that indicator 1204 associated with Messages app 424 is optionally obscured so that the number of unread notifications (eg, the number of unread messages in Messages app 424) is no longer visible. indicates that In some embodiments, indicator 1204 is obscured by replacing the indicator with a placeholder generic indication 1206 (eg, a lock icon), as shown in FIG. 12G. In some embodiments, a placeholder generic indication is placed over all icons associated with all restricted applications (or partially on top of). In some embodiments, a placeholder generic indicator (eg, lock icon) is placed above or adjacent to the text associated with the application icon of the restricted application.

FIG. 12H suppresses notifications for restricted applications by forgoing displaying notifications for two new messages received while the restriction criteria for those applications are met in the Messages and Social Media A apps. device 500 is shown. FIG. 12H further illustrates device 500 forgoing updating indicator 1204 on Messages app 424 to now reflect that there are five unread messages in the Messages app (including newly received messages). show. In some embodiments, the device 500 displays a placeholder generic indication 1206 (e.g., lock icon) as shown in FIG. It will be placed over (or partially over) the icon associated with the application. For example, FIG. 12H shows a lock icon 1206 overlaid on the upper right portion of the Social Media A app 452. FIG. In some embodiments, a placeholder generic indication is placed over all icons associated with all restricted applications (or partially on top of). In some embodiments, a placeholder generic indicator (eg, lock icon) is placed above or adjacent to the text associated with the application icon of the restricted application.

12H-12I, a vertical swipe of contact 1203 is detected on touch screen 504 while home screen 1202 is being displayed (eg, down on home screen 1202 from an area of touch screen 504 that is not displayed). ), this causes the device 500 to display the notification history interface 1220 when the restriction criteria are met on the device 500 . Notification history interface 1220 is optionally a user interface of the operating system of device 500 that displays previously received notifications corresponding to one or more applications stored on device 500 . In some embodiments, device 500 displays suppressed notifications for restricted applications in notification history interface 1220 . In some embodiments, the device 500 visually obscures (e.g., blurs, grays out) the restricted application notifications displayed within the notification history interface 1220, as shown in FIG. 12I. , or visually change it). For example, in FIG. 12I, the device 500 displays the notification 1222 associated with the Messages app 424 and the notification 1224 associated with the Social Media A app 452 received in FIG. 12G but suppressed in FIG. Display in 1220.

In some embodiments, the device 500 removes previously suppressed notifications when the usage limits for the applications associated with those notifications are reset (e.g., after the limit criteria for those applications are no longer met). , for example, after the usage limit for the application is no longer satisfied, or after the device's restricted usage mode ends), display them as if they had just been received. For example, FIG. 12J shows that the restriction criteria for Messages app 424 and Social Media A app 452 are met on device 500 (e.g., a user-defined usage limit has been reached or the current time is associated with restricted usage mode). new messages for the Messages app 424 and the Social Media A app 452 are received and suppressed at the device 500 during one or more user-defined time windows specified by the device 500 and while the restriction criteria have been met. Thereafter, touch screen 504 is shown displaying home screen 1202 (eg, as described above with reference to FIGS. 12G-12H). FIG. 12K illustrates the touchscreen of the device displaying home screen 1202 when the usage limits for Messages app 424 and Social Media A app 452 have been reset (eg, when the limit criteria for those applications are no longer met). 504 is shown. In response to resetting the usage limits for the Messages app 424 and the Social Media A app 452 or ending the restricted usage mode for the device 500, the device 500 optionally updates those applications as new notifications. Display any notifications associated with those applications that were previously suppressed while the restriction criteria for For example, device 500 optionally converts previously suppressed notifications 1222 associated with Messages app 424 and previously suppressed notifications 1224 associated with Social Media A app 452 to "new" Present as notifications (eg, as if they were just received).

In some embodiments, the device 500 suppresses restricted applications in search results, suppresses widgets associated with restricted applications, and suppresses restricted applications from appearing in the application suggestion graphical user interface. , and/or suppress other ancillary functions associated with restricted applications (e.g., applications for which restriction criteria are met), such as suppressing windows corresponding to restricted applications from appearing within a multitasking graphical user interface. . For example, in FIGS. 12L-12M, a horizontal swipe of contact 1203 is detected on touch screen 504 while home screen 1202 is displayed when the restriction criteria for Messages app 424 and Social Media A app 452 are met (eg, , as described above with reference to FIGS. 12G-12H), this causes the device 500 to display the search user interface 1207 with the auxiliary functions associated with the restricted application suppressed. A search user interface 1207 optionally includes a text field 1204 for entering one or more search terms to search for content accessible from the device 500, applications suggested to the user by the operating system of the device 500. and widgets 1210 corresponding to applications installed on device 500 (eg, as described above with reference to FIG. 12C). In some embodiments, device 500 suppresses restricted applications and widgets associated with restricted applications in app suggestion user interface 1208, as shown in FIG. 12M. For example, the device 500 optionally visually obscures the restricted application in the app suggestion user interface 1208 (eg, blurs, grays out, or visually (e.g., visually obscuring Restricted Social Media A App 452) and visually obscuring widgets associated with the restricted application (e.g., Restricted Social Media Visually obscuring widget 1210a associated with A app 452) suppresses application suggestions and widgets associated with restricted apps. In some embodiments, device 500 optionally does not display restricted applications in app suggestion user interface 1208 and does not display widgets associated with restricted applications (e.g., restricted social media social media A app 452 and widget 1210a associated with app 452), instead other unrestricted apps (e.g., applications for which restriction criteria are not met) and/or widgets associated with unrestricted apps. to suppress application suggestions and widgets associated with restricted apps.

In FIG. 12N, the user has entered the search term “social media” into text field 1204 when the restriction criteria for Social Media A app 452 are met on device 500 . In response to the search term “social media” entered into text field 1204, device 500 displays various search results related to the search term “social media” in search user interface 1207. FIG. For example, the device 500 optionally provides a link 1212a to the social media application "Social Media A" 452 installed on the device 500, the social media website "Social Media A" 1212b and links to two social media applications available for download from the App Store (e.g., where the applications are stored), 1212c to "Social Media B" and "Social Media C". Display link 1212d to the application. Because the restriction criteria for Social Media A app 452 are met, links 1212a and 1212b are suppressed (eg, visually altered or obscured), as shown in FIG. 12N. In some embodiments, links 1212a and 1212b are suppressed by not being displayed by device 500, as shown in FIG. 12O. Instead of displaying links 1212a and 1212b, links to other unrestricted apps (eg, applications for which restriction criteria are not met) are optionally displayed.

In some embodiments, device 500 suppresses other ancillary functions associated with restricted applications (eg, applications for which restriction criteria are met), such as suppressing website content associated with restricted applications. . For example, FIG. 12P shows a web browser interface suppressing web content from the website “www.socmeda.com” associated with Restricted Social Media A App 452 by forgoing displaying web content from the website. A device 500 displaying 1230 is shown. In some embodiments, the device 500 suppresses not only the homepage of the website associated with the restricted application, but also any other webpages of the website (eg, pages with the same homepage URL). In some embodiments, the device 500 displays an indication 1232 (e.g., text and/or image). In some embodiments, the device 500 obfuscates (eg, blurs, grays out, or visually alters) the web content 1236 so that the website is restricted, as shown in FIG. 12Q. Suppresses web content from restricted applications by displaying an indication 1232 describing In some embodiments, web browser interface 1230 includes a URL field 1234 for entering the web address (eg, URL) of the website. Device 500 optionally allows the user to enter a website address into URL field 1234 while suppressing a website associated with the restricted application, as shown in FIGS. 12R-12S. and allow the user to navigate to another website.

In some embodiments, device 500 allows users to share content with others via one or more applications installed on the device. FIG. 12T shows device 500 displaying web content within a web browser interface 1230 that optionally includes a sharing affordance 1236 selectable to share the web content. For example, in FIG. 12T, selection of shared affordance 1236 is detected (eg, by a tap of contact 1003 detected on shared affordance 1236, as shown in FIG. 12T). In response to selection of share affordance 1236, device 500 displays share sheet graphical user interface 1240, as shown in FIG. 12U. In some embodiments, share sheet graphical user interface 1240 provides a selectable view of applications installed on device 500 that the user optionally chooses to share web content with, as shown in FIG. 12U. Contains icons. In some embodiments, device 500 suppresses icons of restricted applications within share sheet graphical user interface 1240 . For example, in FIG. 12U, the device 500 visually obscures the restricted messaging app icon 424 and the restricted social media A app icon 452 (e.g., blurs, grays out, or renders the icons visible). ) to suppress the restricted messaging app icon 424 and the restricted social media A app icon 452 in the share sheet graphical user interface 1240 . In some embodiments, device 500 refrains from displaying Restricted Messaging App icon 424 and Restricted Social Media A App icon 452 in Share Sheet graphical user interface 1240 (e.g., Restricted Application ), and instead displaying other unrestricted apps (e.g., applications for which the restriction criteria are not met), the restricted messaging app icon 424 and the restricted social media A app icon 452 suppress

FIG. 12V shows the device 500 displaying content associated with the Video Z-app within a picture-in-picture (PIP) interface 1250 when the restriction criteria for the Video Z-app are not met. In some embodiments, the PIP interface 1250 resides on top of another user interface (e.g., the home screen, the primary user interface of another application, the user interface of another application), as shown in FIG. 12V. Is displayed. In some embodiments, the device 500 suppresses application content from being displayed within the picture-in-picture (PIP) interface 1250 when the restriction criteria for that application are met. For example, FIG. 12W illustrates suppressing the display of content associated with the Video Z app within the PIP interface 1250 when the restriction criteria for the Video Z app are met. In some embodiments, device 500 visually obscures (eg, blurs, grays out, or visually alters) content and/or PIP interface 1250, as shown in FIG. 12W. suppresses displaying content associated with the Video Z app within the PIP interface 1250 . In some embodiments, device 500 suppresses displaying content associated with Video Z App in PIP interface 1250 by forgoing displaying content associated with Video Z App in PIP interface 1250. do. If the PIP interface 1250 is currently displaying content associated with the Video Z App when the restriction criteria are met, the device 500, in some embodiments, stops displaying the content in the PIP interface 1250 ( e.g., closing the PIP window) and/or obscuring the PIP interface 1250 (e.g., graying out or fading out the PIP window) and/or pausing the video playback Suppress displaying the associated content. In some embodiments, device 500 renders content and/or PIP interface 1250 visually invisible, as shown in FIG. 12X (eg, showing device 500 after stopping displaying PIP interface 1250). Clarify and suppress displaying content associated with the Video Z App within the PIP interface 1250 by automatically closing the PIP interface 1250 after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds) do.

In some embodiments, the device 500 controls the media control interface associated with a restricted application (eg, an application for which restriction criteria are met), such as suppressing media control interfaces for controlling media content associated with the restricted application. Suppress other auxiliary functions. For example, in FIGS. 12Y-Z, a vertical swipe of contact 1203 is detected on touch screen 504 while home screen 1202 is displayed (eg, from an area of touch screen 504 that is not displayed to home screen 1202). above), which causes the device 500 to display the media control interface 1260 when the restriction criteria are not met on the device 500 . Media control interface 1260 is optionally a user interface for the operating system of device 500 that controls playback of content from various applications on device 500 . The media control interface 1260, as shown in FIG. 12Z, optionally displays media control buttons 1262 for controlling media content and media content information indicating which media content the media control interface 1260 is currently controlling. 1264 included. For example, FIG. 12Z shows device 500 controlling media playback of the song "Hit Song" by "Popstar" via the Music app. In some embodiments, device 500 suppresses media control interface 1260 for media content associated with restricted applications (eg, applications for which restriction criteria are met). For example, FIG. 12AA displays a media control interface 1260 when the restriction criteria for the Music app, the Messages app 424, and the Social Media A app 452 are met on the device 500 to control media content associated with the Music app. device 500 suppressing its media control interface 1260 . In some embodiments, the device 500 stops playing media content associated with the music app and disables the media content button 1262 (e.g., using the button to limit prevent device 500 from suppressing media control interface 1260 by not allowing the application to control media content associated with it. In some embodiments, the device 500 also visually obscures the media control buttons 1262 (e.g., blurs, grays out, or visually alters the media control buttons), as shown in FIG. 12AA. by). In some embodiments, device 500 automatically resets media control interface 1260 after a period of time (eg, 5 seconds, 10 seconds, 20 seconds), as shown in FIG. 12BB. For example, FIG. 12BB shows device 500 no longer playing media content associated with the Music app (e.g., no longer displaying media content information 1264 associated with the Music app), and media control buttons 1262 no longer being displayed. A device 500 that does not In some embodiments, the device 500 resets the media control interface 1260 after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds) when the restriction criteria are met and/or after the device 500 resets the media control interface 1260. to stop displaying the media control interface 1260 .

FIGS. 13A-13H are flow diagrams illustrating a method 1300 of inhibiting certain application ancillary features upon reaching application usage limits or restriction criteria associated with those applications, according to some embodiments of the present disclosure. be. Method 1300 optionally includes device 100, device 300, or device 500 as described above with reference to FIGS. 1A-1B, 2-3, 4A-4B, and 5A-5H. run on electronic devices such as Some acts of method 1300 are optionally combined and/or the order of some acts is optionally changed.

As will be described below, the method 1300 provides a way to throttle certain application ancillaries when the application usage limit associated with those applications is reached. This method reduces the overall usage of the electronic device by restricting how a user interacts with a particular application. For battery-operated electronic devices, reducing the overall usage of the electronic device saves power and increases the interval between battery charges.

In some embodiments, an electronic device that communicates with a display and one or more input devices (e.g., a mobile device that includes a touchscreen such as device 500 that includes touchscreen 504, a keyboard, a mouse, a trackpad, a touchscreen 504, etc.). A computer or tablet computer that includes one or more of the touch screens of a wearable device such as a smartwatch that includes a touch screen, or a set-top box that communicates with a television and an input device (e.g., a remote controller) is an electronic device enforces restrictions on one or more applications, including the first of multiple applications installed on it (e.g., screen time information, time to use a particular application, notifications received from a particular application) While maintaining information, information about events of interest, and optionally controlling the above quantities that the electronic device allows (e.g., usage limits, bedtime limits, etc.), the first, such as FIG. 12C, events corresponding to the activation of auxiliary functions of the application (e.g., the occurrence of an event that would trigger the display of a notification about the application, the request to display the widget corresponding to the application, the application and content via the system shared user interface) to view the website associated with the application, to view the history of previous notifications (including application notifications), to view application content in picture-in-picture (PIP) mode, in search results a request to display an application, view a multitasking graphical user interface, or display and/or perform media control operations associated with the application) (1302). Auxiliary functions of the first application are available for execution without displaying the primary user interface of the first application (e.g., without launching the application within an application window or other primary view of the application). Functionality (e.g. display interactive notifications, perform share sheet actions, display widgets, display notification history, display websites in browser, display application content in PIP mode displaying applications within search results; displaying application windows within a multitasking graphical user interface; or displaying and/or controlling media control actions). In some embodiments, usage limits for one or more applications are enforced over a period of time (eg, over a 24-hour period, a week, or any other period of time).

In some embodiments, in response to detecting 1304 an event corresponding to activation of an auxiliary function of the first application, a restriction criterion for the first application has been met (e.g., if a user to the application Upon determination that a defined usage "limit" (e.g., usage limit or allowance) has been reached, the electronic device inhibits (1306) an auxiliary function (e.g., notification associated with an application), such as FIG. 12M. Generate function, display website(s) associated with application, share sheet action(s), display window corresponding to application in multitasking graphical user interface, display application content in PIP mode , and any other functionality (including operating system functionality) associated with the application (e.g., restricting the app from appearing in search results, restricting access to widgets associated with the application, Restrict the application from appearing as a suggested application, or restrict the window corresponding to the application from appearing within the multitasking graphical user interface)). In some embodiments, usage limits are set for overall device usage, usage of multiple applications within a given category of applications, or specific applications. In some embodiments, launching applications is also inhibited (eg, restricted). In some embodiments, auxiliary functions are inhibited by preventing the function from executing in response to detecting an event.

In some embodiments, in response to detecting 1304 an event corresponding to activation of an auxiliary function of the first application, and following a determination that the restriction criteria are not met, the electronic device performs the , without displaying the application's primary user interface (1308) (e.g. generating notifications from the application, share sheet actions, displaying websites associated with the application, in PIP mode related to various applications on electronic devices, such as displaying application content, displaying widgets associated with applications, displaying windows corresponding to applications from appearing within a multitasking graphical user interface, etc. enable normal use or execution of the function). The limits and auxiliary features described herein are optionally the same or similar to the restricted usage modes, auxiliary features, and/or application usage limits described with reference to methods 700, 900, and 1100. . The above-described method of throttling application features that exceed their usage limits enables the electronic device to effectively reduce the overall usage of the electronic device, thereby reducing power consumption and extending the battery life of the device. improves.

The auxiliary function optionally activates a notification associated with the first application (e.g., an alert and/or notification generated by the application) upon occurrence of an event corresponding to activation of the notification, such as FIG. 12F. ) (e.g., showing a visual indication on a display, playing a sound on a speaker associated with the electronic device, haptic(s) and/or or generating tactile output(s), etc.) (1310). In some embodiments, notifications include visual indications (eg, windows, pop-up boxes) that include text and/or images. Additionally or alternatively, the notification optionally includes sound and/or tactile and/or tactile output indications. In some embodiments, the electronic device suppresses notifications associated with applications that exceed usage limits. In some embodiments, notifications are suppressed by forgoing the display of user visual indications (eg, text and/or images) or the generation of notifications. In some embodiments, notifications are suppressed by obscuring user visual indications (eg, visually altering visual indications, text, and/or images). In some embodiments, notifications are suppressed by forgoing performing sounds and/or haptic and/or tactile output indications associated with the application. In some embodiments, performing the auxiliary function includes presenting a notification generated by the first application. The above-described method of suppressing notifications associated with applications for which restriction criteria are met allows the electronic device to reduce overall usage of the electronic device (e.g., not performing notification functions and thus allowing users to notify and/or by not prompting you to interact with the electronic device), thereby reducing power consumption and improving battery life of the device.

In some embodiments, detecting an event corresponding to the activation of the auxiliary function of the first application is the occurrence of an event corresponding to the activation of a notification associated with the first application, such as FIG. 12E. 1312 (eg, detecting the occurrence of an event that would trigger presentation of the notification). In some embodiments, suppressing the auxiliary function means forgoing presenting the first type of indication in response to a notification generated by the first application, such as FIGS. 12G-12H. Include 1314 (eg, suppress notifications associated with restricted applications). In some embodiments, notifications are suppressed by forgoing the display of user visual indications (eg, text and/or images) or the generation of notifications. In some embodiments, notifications are suppressed by obscuring user visual indications (eg, visually altering visual indications, text, and/or images). In some embodiments, notifications are suppressed by forgoing performing sounds and/or haptic and/or tactile output indications associated with the application.

In some embodiments, performing the auxiliary function includes presenting 1316 the first type of indication in response to a notification generated by the first application, such as FIG. 12F (e.g. , banners, pop-up notifications, or lockscreen notifications). In some embodiments, performing the auxiliary function includes presenting a notification generated by the first application. The above-described method of suppressing notifications associated with applications for which restriction criteria are met and not suppressing notifications associated with applications for which restriction criteria are not met enables an electronic device to efficiently and selectively use the electronic device. (e.g., by not running notification functions for certain applications and thus not prompting users to interact with notifications and/or electronic devices), thereby reducing power consumption. Improve device battery life.

In some embodiments, upon determining 1318 that the restriction criteria for the first application are met, the electronic device displays a notification history user interface (e.g., a previous notification by one or more applications of the electronic device), such as FIG. 12I. includes 1319 visual indications (eg, images, windows, text, etc.) of the first type of indications within a user interface for displaying visual indications of a plurality of notifications generated in a In some embodiments, the notification history user interface further includes one or more indications of notifications generated by one or more applications other than the first application (1319). In some embodiments, the electronic device displays notification history for multiple applications in the notification history user interface, including visual indications of any suppressed notifications generated by the first application.

In some embodiments, notifications generated by multiple applications, including the first application, are displayed in a dedicated notification history user interface (e.g., window ) (eg, subject to a determination that the restriction criteria for the first application are met). This allows the user to optionally later browse notifications for applications that have been suppressed. In some embodiments, visual indications of notifications from unsuppressed applications are presented only within the notification history user interface. is presented outside the notification history user interface (in addition to being presented within the notification history user interface). The above-described method of displaying suppressed notification(s) associated with applications for which the restriction criteria are met in the notification history does not require the electronic device to push the notification (e.g., upon generation of the notification). (by not alerting the user to notifications with pop-up windows, sounds, and/or indications of tactile and/or tactile output), allowing for efficiently organized and displayed notifications that would otherwise be suppressed. , thereby reducing overall usage of the electronic device (eg, by not prompting the user to notify and/or interact with the electronic device), reducing power consumption and improving battery life of the device.

In some embodiments, suppressing the suppression assist function is forgoing presenting the first type of indication in response to a notification generated by the first application, such as FIGS. 12G-12H. (1320) (e.g., activate new indications (e.g., images, sounds, and tactile and/or tactile outputs) of any notifications associated with the application while already exceeding usage limits for that application. not presented explicitly). In some embodiments, after suppressing the auxiliary functionality of the first application, the electronic device determines (1322) that the restriction criteria for the first application are no longer met, such as FIG. The usage of one application no longer meets the usage limit for the first application, the device is no longer in restricted use (eg, device idle time or bedtime mode), etc.). In some embodiments, in response to determining that the restriction criteria for the first application are no longer met, the electronic device presents an indication regarding notifications generated by the first application, such as FIG. 12K. (1324) (e.g., display notifications in the notification history user interface and/or as "new" notifications actively presented as if they had just been received once the usage limit was reset). In some embodiments, a notification generated by an application during the period of reaching the usage limit for that application is presented to the user that the usage limit for that application has been reset and is therefore no longer exceeded. be. For example, if the usage limit for the associated application is a daily limit, the usage limit optionally resets at midnight the next day. In such a situation, when the usage limit for the application resets at midnight, the electronic device optionally displays the previously suppressed notification, which otherwise would have been previously presented. Display within the user interface (eg, on the wake or lock screen of the device). In some embodiments, notifications will be run all at once (e.g., in one alert, window, or popup box containing all previously suppressed notifications), or separately/ They will be displayed sequentially. The above-described method of presenting notifications associated with an application when the usage limit resets allows the electronic device to effectively present previously suppressed notifications while reducing overall usage of the electronic device. This allows for reduced power consumption and improved device battery life.

The auxiliary function optionally displays a widget user interface that displays one or more secondary user interfaces of one or more applications, including the secondary user interface of the first application, such as FIG. 12C. Include 1326 (eg, a widget corresponding to the application). In some embodiments, widgets include user interface objects (eg, windows) that include text and/or images associated with the application (eg, weather widgets displaying the current temperature, scores for live events). a sports widget that displays recent event headlines, and/or a user interface object that displays content associated with the application). In some embodiments, the content of widgets corresponding to an application is dynamically updated by the application. In some embodiments, the secondary user interface (e.g., widget) is displayed concurrently with additional secondary user interfaces of other applications (different from the primary user interface of those other applications) (e.g., widgets). (eg, the widget is displayed simultaneously with other application's widgets). In some embodiments, the secondary user interface (eg, widget) is displayed within a different widget user interface than the primary user interface of the first application. The event corresponding to activation of the auxiliary function optionally includes (1328) a request to display a widget user interface, such as FIGS. 12B-12C (eg, to display a widget user interface on the electronic device user input). In some embodiments, suppressing the auxiliary function suppresses the secondary user interface of the first application, such as FIG. , not displaying or obscuring) while displaying 1330 the widget user interface (eg, suppressing one or more widgets that exceed usage limits). In some embodiments, the widget suspends display of the widget's user interface objects (e.g., text and/or images) associated with the application that has exceeded its usage limit while displaying other widgets. is suppressed (e.g. the widget is not displayed). In some embodiments, widgets obscure user interface objects (e.g., visually alter user interface objects, text, and/or images) while displaying other widgets. is suppressed by Obfuscating the widget optionally displays an indication of the restriction criteria in place of text and/or images associated with the application (e.g., content of the widget when the restriction criteria are not met). Including. In some embodiments, all widgets are suppressed. In some embodiments, performing the auxiliary function includes displaying a widget user interface that displays one or more widgets of one or more applications, including widgets of the first application. The widget user interface described herein is optionally the same or similar to the widget user interface described with reference to Figure 8W. The above-described method of throttling widgets corresponding to applications that exceed usage limits makes the interface between users and devices more efficient (e.g., users can control their own device usage for applications and widgets associated with applications). , thus reducing the input provided to the device by the user (e.g., the input for monitoring usage is reduced), thereby allowing the electronic device to monitor the overall usage of the electronic device. In addition, it reduces power consumption and improves battery life of the device.

In some embodiments, the assistance function includes presenting within the suggestion user interface a visual indication of one or more applications, including the first application for which the suggestion criteria are met, such as FIG. 12C. (1332) (e.g., displaying application suggestions to the user on the electronic device within the electronic device's system (e.g., operating system) user interface, as opposed to, e.g., the user interface of a particular application on the electronic device) to do). In some embodiments, the applications suggested to the user are commonly used applications, recently used applications, favorite applications, currently running applications, and the like. In some embodiments, the suggested applications are displayed in response to a search action performed on the electronic device. For example, a user optionally enters one or more letters into a search box to initiate a search for items containing the one or more letters. In some embodiments, the search is on all installed applications on the electronic device, applications available for download in app stores, websites, content of applications installed on the electronic device, and the like. performed (e.g., searching the content of messages, emails). The search results then optionally include listings of applications, websites, and/or content that include one or more of the entered characters.

An event corresponding to activation of an auxiliary function optionally invokes a request to present a visual indication of one or more applications whose proposal criteria have been met within a proposal user interface, such as FIGS. 12B-12C. Include 1334 (eg, input from the user to display application suggestions on the electronic device). In some embodiments, suppressing the auxiliary function optionally includes presenting a suggested user interface without presenting a visual indication of the first application, such as FIG. 12M (1336 ) (eg, do not display the application in the proposal user interface). For example, the first application will not be displayed with the commonly used application even if the first application is commonly used. In another example, the first application will not be displayed in the search results even if the search prompting display of the search results includes the first application. In some embodiments, the visual indication of the first application is displayed within the suggestions (or search results) user interface. However, it is obscured to indicate that the restriction criteria for the first application have been met. In some embodiments, the suggested user interface is suppressed (eg, all applications are hidden or obscured). In some embodiments, performing the auxiliary function includes presenting a suggested user interface including visual indications of one or more applications including visual indications of the first application (e.g., display the application within the proposal user interface). The above-described method of suppressing application suggestions that exceed the usage limit enables the electronic device to effectively reduce the overall usage of the electronic device, thereby reducing power consumption and extending the battery life of the device. improves.

The ancillary functions optionally include displaying 1338 web content associated with the first application within a browser user interface, such as FIG. 12S (e.g. display the associated web content or website). In some embodiments, the event corresponding to activation of the auxiliary function includes a request to display 1340 web content associated with the first application within a browser user interface, such as FIG. 12R (e.g., input from a user to display web content or a website associated with the first application within a web browser). In some embodiments, inhibiting auxiliary functionality includes preventing access to web content associated with the first application (1342), such as FIG. 12P (e.g., usage limit reached). opting out of displaying website content associated with applications that are For example, if the usage limit for application A associated with website A is reached, the display of website A (or content from website A) within the browser application will be prevented. If the usage limit has not been reached, display of website A will optionally not be prevented. In some embodiments, the electronic device will throttle not only the application that exceeds the usage limit, but also any websites associated with that application. The electronic device optionally displays a visual indication of the restriction criteria (e.g., a splash screen or other image that obscures the content of the web page) in place of the website content when the restriction criteria are met. ). In some embodiments, performing the auxiliary function includes presenting web content associated with the first application within a browser (eg, displaying a website within the browser). The website associated with the application described herein is optionally the same or similar to the website associated with the application described with reference to method 900 . The above-described method of throttling web content associated with an application that exceeds usage limits makes the interface between the user and the device more efficient (e.g., the user can identify themselves regarding the application and the website associated with the application). of the electronic device, thus reducing the input provided to the device by the user (e.g., the input to monitor usage is reduced), thereby allowing the electronic device to It allows for an efficient reduction in overall usage, in addition to reducing power consumption and improving the battery life of the device.

In some embodiments, preventing access to web content associated with the first application (1344) may include accessing web content associated with the first application from the first website, such as FIG. 12Q. (eg, the website content associated with the over-usage application is loaded (eg, downloaded to local memory) by the electronic device). In some embodiments, preventing access to web content associated with the first application (1344) forgoes displaying web content associated with the first application, such as FIG. 12Q. 1348 (eg, web content is loaded by the electronic device but not displayed). In some embodiments, the electronic device blocks display of the content and/or displays some user interface element (e.g., a pop-up dialog or splash screen) above the content. Additionally or alternatively, the web content is optionally displayed but obscured (eg, distorted, grayed out, faded out, and/or visually altered) . The above-described methods of throttling web content associated with applications for which restriction criteria are met (e.g., usage limits are exceeded or the device is in restricted mode) make the interface between users and devices more efficient. (e.g., users do not need to monitor their own device usage with respect to applications and websites associated with applications, thus reducing input provided by users to devices (e.g., input is reduced)), which allows the electronic device to effectively reduce the overall usage of the electronic device, as well as to allow the electronic device to cache web content for future use. In addition, it improves the battery life of the device by reducing power consumption while increasing execution speed.

In some embodiments, preventing access to web content associated with the first application (1350) is for navigating to another web site within a browser user interface, such as FIG. 12R (e.g., , for navigating to other websites, for navigating within a website) while maintaining the display of one or more user interface elements (e.g., one or more graphical user interface buttons, text entry fields) suspending (1352) displaying web content associated with the first application while the first application is running. In some embodiments, browser navigation controls (e.g., URL fields or buttons on the browser) remain operable while specific web content associated with applications for which restriction criteria are met is restricted. be. In some embodiments, websites that are not associated with any application on the electronic device remain accessible as long as the restriction criteria for one or more applications on the electronic device are met. For example, while access to the website associated with the first application is restricted, the browser's navigation controls are not restricted and the user can optionally navigate to other websites. The above-described method of suppressing web content associated with applications whose restriction criteria are met while still allowing access to other websites makes the user-device interface more efficient (e.g., users can , there is no need to monitor the user's own device usage with respect to the application and the website associated with the application, thus reducing the input provided by the user to the device (e.g., the input to monitor usage is reduced )), which allows the electronic device to efficiently reduce the overall usage of the electronic device, as well as reduce power consumption and improve battery life of the device.

In some embodiments, a request to view second web content from a second website within a browser user interface, such as FIGS. Detect 1354 a corresponding second event (e.g., detect the occurrence of an event that will trigger the display of content from another website, optionally not associated with the first application) ). In some embodiments, the second event is the user entering a URL for another website into the browser's address field.

In some embodiments, detected a second event corresponding to a request to view second web content from a second website within the browser user interface while the restriction criteria for the first application are satisfied Optionally (1356), following the determination that the second website is associated with the first application, the electronic device forgoes (1358) displaying the second web content, such as FIG. 12P. (e.g. access to web content from all websites associated with the application(s) for which restriction criteria are met (e.g. usage limit reached, device in restricted access mode, etc.) restrict access). In some embodiments, the electronic device blocks display of the content and/or displays an image (e.g., pop-up dialog or splash screen) indicating that the content is blocked because the usage limit for Application A has been reached. is displayed above the content. Additionally or alternatively, the web content is optionally displayed obfuscated (eg, distorted, grayed out, and/or visually altered).

In some embodiments, detected a second event corresponding to a request to view second web content from a second website within the browser user interface while the restriction criteria for the first application are satisfied Optionally (1356), upon determining that the second website is associated with the second application and that the restriction criteria for the second application are not met, the electronic device performs a second application, such as FIG. 12S. display 1360 the web content of (e.g., the web content associated with the application for which the restriction criteria are not met (e.g., usage limit reached, device is in restricted usage mode, etc.) ). In some embodiments, only websites associated with applications for which the restriction criteria are met are restricted and the user can navigate to other websites. In some embodiments, websites not associated with any application on the electronic device are also accessible while the restriction criteria for one or more applications on the electronic device are met. The above-described method of suppressing web content associated with applications whose restriction criteria are met while still allowing access to other websites makes the user-device interface more efficient (e.g., users can , there is no need to monitor the user's own device usage with respect to the application and the website associated with the application, thus reducing the input provided by the user to the device (e.g., the input to monitor usage is reduced )), which allows the electronic device to efficiently reduce the overall usage of the electronic device, as well as reduce power consumption and improve battery life of the device.

In some embodiments, the auxiliary function directs the media content to be displayed within the picture-in-picture user interface of the first application partially overlaid on one or more other user interfaces, such as FIG. 12V. including 1362 (e.g., displaying a picture-in-picture (PIP) window over another user interface (e.g., over the home screen, the primary user interface of another application, or the user interface of another application); ). The event corresponding to the activation of the auxiliary function optionally includes (1364) a request to display the media content within the picture-in-picture user interface of the first application, such as FIG. 12V (eg, within a PIP window). such as a request to view content from a first application at In some embodiments, the PIP window is already displaying content from the first application and the request is to continue displaying content (eg, receive content to display). In some embodiments, suppressing the auxiliary function includes suppressing the picture-in-picture user interface of the first application (1366), such as FIG. 12W (eg, forgoing displaying the PIP window). , stop displaying content in the PIP window). For example, if the usage limit for application A has been reached, the user will not be able to circumvent restricted access to application A by attempting to start the application's PIP window (e.g., PIP window will not be displayed). In some embodiments, the PIP window for the application will be currently displayed when the usage limit for the application is met, and the electronic device may stop displaying the PIP window or Obscuring one application's PIP window in another way (eg, graying out or fading out the PIP window) will suppress this functionality. In some embodiments, a PIP window is a window that plays media (eg, movies, TV shows, music, etc.) on an electronic device using a media playback application on the electronic device. If the usage limit has not been reached, display of the PIP window will optionally not be prevented (eg, not suppressed). In some embodiments, performing the auxiliary function includes displaying a PIP window of the first application partially overlaid on one or more other user interfaces. The above-described method of throttling PIP windows associated with applications that exceed their usage limits makes the user-device interface more efficient (e.g., the user can control the application and the PIP windows associated with the application themselves). of the electronic device, thus reducing the input provided to the device by the user (e.g., the input to monitor usage is reduced), thereby allowing the electronic device to It allows for an efficient reduction in overall usage, in addition to reducing power consumption and improving the battery life of the device.

In some embodiments, suppressing 1368 the picture-in-picture user interface of the first application may be performed while displaying the picture-in-picture user interface of the first application, such as FIG. 12W. 1370, the picture-in-picture user interface is disabled for a first period of time (e.g., the usage limit for the application is met while the application is being used in PIP mode). Clarifying 1372 (eg, visually changing and/or blocking the PIP window). In some embodiments, the PIP window will continue to display content from the first application, but the content will be visually altered (e.g., blurred, displayed in grayscale). or displayed with a watermark). In some embodiments, the PIP window will stop displaying content from the first application and instead provide other information (e.g., a visual indication that the usage limit for the particular application has been exceeded). indication) will be displayed. In some embodiments, other information displayed will include affordances (eg, graphical user interface elements or soft buttons) for closing the PIP window.

In some embodiments, suppressing 1368 the picture-in-picture user interface of the first application is performed while displaying the picture-in-picture user interface of the first application, such as FIG. 12X. is satisfied 1370 (e.g., the usage limit for the application is satisfied while the application is being used in PIP mode), the picture-in-picture user interface is displayed after the first period of time. Stop displaying 1374 (eg, the PIP window will automatically close after a certain period of time (eg, 5 seconds, 10 seconds, 20 seconds)). For example, the content of the PIP window will be faded out and the PIP window will automatically close after that period.

In some embodiments, this time period is specified by the user in the settings of the electronic device. In some embodiments, upon determining that the restriction criteria for the first application are met while not displaying the picture-in-picture user interface of the first application, the electronic device, with one or more input devices, Detecting user input corresponding to a request to display the picture-in-picture user interface of the first application (e.g., detecting input to display the PIP user interface of the first application while the restriction criteria are met). ), in response to user input corresponding to a request to display a picture-in-picture user interface of the first application, and while the restriction criteria for the first application are satisfied, the electronic device displays the first application (e.g., the restriction criteria for the first application are met while the PIP window for that application is being displayed), the electronic device displays the window after the window is displayed. to prevent it from starting when In this way, a user of an electronic device cannot circumvent the restrictions for a particular application once the usage limit for that particular application has been exceeded. The above-described method of suppressing PIP windows associated with applications for which restriction criteria are met makes the interface between the user and the device more efficient (e.g., the user can specify the user's own preferences regarding the applications and the PIP windows associated with the applications). There is no need to monitor device usage, thus reducing the input provided to the device by the user (e.g., the input to monitor usage is reduced), thereby allowing the electronic device to operate as a whole electronic device. It allows for efficient reduction of usage, in addition to reducing power consumption and improving battery life of the device.

In some embodiments, the auxiliary function displays multiple affordances (eg, one or more graphical user interface buttons) for controlling playback of media content associated with the first application, such as FIG. 12Z 1376 (eg, media control buttons including one or more of play, pause, rewind, fast forward, skip, etc. buttons). In some embodiments, media control buttons are displayed on the media control user interface. In some embodiments, executing the auxiliary function is displaying one or more graphical user interface buttons (e.g., soft buttons) for controlling playback of media content associated with the first application. (eg, one or more of play, pause, rewind, fast forward, skip, etc. buttons).

The event corresponding to activation of the auxiliary function optionally includes a request to display multiple affordances for controlling playback of media content associated with the first application, such as FIGS. 12Y-Z. (1378) (eg, user input requesting to see media control buttons that control playback of media associated with the first application on the electronic device).

In some embodiments, inhibiting the auxiliary function includes preventing multiple affordances from controlling playback of media content associated with the first application (1380), such as FIG. 12AA. In some embodiments, the media control buttons will be displayed but will be disabled (eg, the buttons will not perform their associated media control functions). For example, a media control interface will be displayed with media control buttons including a play button, but the electronic device will prevent the user from performing a play action when the play button is selected. In some embodiments, the inoperable media control buttons will be obscured (eg, visually altered) within the media control user interface. In some embodiments, a media playback control for controlling playback of a media playback application when restriction criteria for a particular media playback application (e.g., movie playback application, television program playback application, or music playback application) are met. access to is restricted by an electronic device. In some embodiments, these media playback controls are within the application itself or a user interface other than the application itself (e.g., within the user interface of the electronic device's system or operating system that is globally accessible on the electronic device). Is displayed. In some embodiments, the media playback controls are configured such that they are no longer selectable to control playback of any media using the media playback application as long as the usage limit for the application is currently reached. , is blocked. In some embodiments, the media control buttons are prevented from being displayed by the electronic device (e.g., media control (by preventing the user interface from being displayed, or by displaying the media control user interface without media control buttons) will be suppressed. In some embodiments, the suppressed media control user interface is displayed on the electronic device for a period of time (e.g., 5 seconds, 10 seconds, 20 seconds) and automatically closes after that period ( For example, it will stop being displayed). The above-described method of suppressing media control buttons associated with applications for which restriction criteria are met makes the interface between the user and the device more efficient (e.g., the user can control the application and the media control buttons associated with the application). It does not need to monitor its own device usage, thus reducing the input provided by the user to the device (e.g., the input to monitor usage is reduced), thereby allowing the electronic device to become an electronic device In addition to reducing power consumption and improving battery life of the device.

In some embodiments, preventing multiple affordances from controlling playback of media content associated with the first application (1382) during a first period of time, such as in FIG. 12AA (e.g., 5 minutes, 15 minutes, 1 hour, or any user-defined period of time) to put the affordances into an inactive state in which the device ignores user input directed to the affordances (e.g., if a media control button is disabling 1384 each of the media functions associated with each of the media control buttons. For example, a play button will not play content in response to a selection input on the play button when the play button is in a frozen state. In some embodiments, frozen media control buttons will be obscured (eg, visually changed) to indicate to the user that they are frozen. In some embodiments, even if the frozen media control buttons are not operable, they may indicate that the media has recently been played (or the usage limit has been reset, such as displaying the title of the media, the image of the media, etc.). can potentially be controlled by the media control buttons). In some embodiments, this period of time is the amount of time remaining until the restriction criteria for the particular application associated with the media control button is no longer met. In some embodiments, restriction criteria for a particular media playback application while the media control is controlling playback of the media playback application (e.g., while the media playback application is generating media on the electronic device) is satisfied, the media controls are frozen in their current state (e.g., the media's current playback state, the media's identity (e.g., title), etc., at the time the restriction criteria are met). shown), blocked from interaction from the user. In some embodiments, media playback is additionally stopped when the playback controls are frozen. In some embodiments, the media controls are reset to their default state after being frozen for some period of time (e.g., 5 seconds, 10 seconds, 20 seconds) (e.g., when the media is not playing, no media title, etc.).

In some embodiments, preventing multiple affordances from controlling playback of media content associated with the first application (1382) includes multiple affordances after the first time period, such as in FIG. 12BB. Include 1386 affordances from an inactive state to a default state (e.g., media control buttons that do not indicate that any media is playing, and therefore do not control media playback). default state). Thus, in some embodiments in their default state, the media control buttons no longer indicate the current playback state of the media, identification of the media (eg, title), etc. In some embodiments, this period of time is the amount of time remaining before the usage limit for the particular application associated with the media control button is reset. In some embodiments, even if affordances for controlling media content are reset to default states, the electronic device prevents presentation of media associated with any application for which the restriction criteria are met. In some embodiments, the electronic device stops displaying the media control interface after the first period of time instead of defaulting the media control buttons. The above-described method of suppressing media control buttons associated with applications for which restriction criteria are met makes the interface between the user and the device more efficient (e.g., the user can control the application and the media control buttons associated with the application). It does not need to monitor its own device usage, thus reducing the input provided by the user to the device (e.g., the input to monitor usage is reduced), thereby allowing the electronic device to become an electronic device In addition to reducing power consumption and improving battery life of the device.

It is understood that the particular order described for the acts in FIGS. 13A-13H is exemplary only and is not intended to represent the only order in which the acts may be performed. want to be Those skilled in the art will recognize various methods for reordering the operations described herein. In addition, details of other processes described herein with respect to other methods described herein (e.g., methods 700, 900, 1100, and 1500) are also described above with respect to Figures 13A-13H. Note that method 1300 is also applicable in a similar fashion. For example, the usage limits, restricted usage modes, auxiliary functions, usage limit settings, etc. on the electronic device described above with reference to method 1100 may be applied to other methods described herein (eg, methods 700, 900, 1100). , and 1500), optionally having one or more of the characteristics such as usage limits, restricted usage modes, auxiliary functions, usage restriction settings, etc. on the electronic device. For the sake of brevity, these details are not repeated here.

Operations in the information processing methods described above may be performed within an information processing device, such as a general-purpose processor (eg, as described above in connection with FIGS. 1A-1B, 3, 5A-5H) or an application-specific chip. is optionally performed by activating one or more functional modules of Further, the operations described above with reference to FIGS. 13A-13H are optionally performed by the components shown in FIGS. 1A-1B. For example, detecting 1302 , suppressing 1306 , and performing 1308 operations are optionally performed by event sorter 170 , event recognizer 180 , and event processor 190 . Event monitor 171 of event sorter 170 detects contact on touch screen 504, and event dispatcher module 174 delivers event information to application 136-1. Each event recognizer 180 of application 136-1 compares the event information with respective event definitions 186 and determines that a first touch at a first location on the touch screen is a default event, such as selection of an object on the user interface. It determines whether it corresponds to the event or sub-event of . When the corresponding predefined event or sub-event is detected, the event recognizer 180 activates the event processor 190 associated with detecting the event or sub-event. Event handler 190 optionally utilizes or calls data updater 176 or object updater 177 to update application internal state 192 . In some embodiments, the event handler 190 accesses the corresponding GUI updater 178 to update what is displayed by the application. Likewise, it will be apparent to those skilled in the art how other processes may be implemented based on the components shown in FIGS. 1A-1B.
Remote management of restriction settings

Users interact with electronic devices in many different ways, including using applications accessible on the devices. In some situations, administrators (eg, parents) remotely manage restriction settings on restricted devices (eg, their children's electronic devices). The embodiments described below allow the electronic device to allow the user of the restricted device to access one of the restricted devices, either with a passcode restricted device, or with an authorizing device or other remote administrator. To provide a method for requesting permission from an administrator to change the above usage restriction settings. Requiring authorization from administrators on restricted devices to change usage restriction settings facilitates such changes when electronic devices require authorization by another party (e.g., a parent). can provide an efficient way to This simplification improves the usability of the device and makes the interface between the user and the device more efficient (e.g., by allowing the user to interact with the device with less input), thereby allowing the user Reduce power usage and improve battery life in electronic devices by allowing the device to be used more quickly and efficiently. It is understood that people use devices. When a person uses a device, that person is optionally called the user of that device.

14A-14T illustrate exemplary methods for an electronic device to manage restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure. The embodiments in these figures are used to illustrate the processes described below, including the processes described with reference to Figures 15A-15G.

FIG. 14A shows an exemplary device 500 having a touch screen 504 as described with reference to FIGS. 5A-5H. Electronic device 500 shown in FIG. 14A is associated with a restricted account, such as a child account associated with a group of user accounts within a family including one or more child user accounts and one or more parent user accounts. . In some embodiments, an administrator or parent user account modifies one or more restriction settings (eg, one or more restriction settings described above with reference to FIGS. 10A-13H) of the child's electronic device 500. have permission to Touch screen 504 optionally displays one or more user interfaces including various content. In the example shown in FIG. 14A, the touch screen 504 provides an indication that the initial restriction settings for the electronic device have been set (e.g., by a parent device) when the initial restriction settings for the electronic device have not previously been set. 1498-26 is displayed. Indication 1498-26 indicates which limit settings have been set and their details (e.g., "Device idle time from 6am to 10pm Monday through Thursday" and "Usage limits: news apps, games category , and social media categories”). Accordingly, in some embodiments, device 500 displays notification 1498-26 when a parent device first sets usage restriction settings on device 500. FIG.

FIG. 14B illustrates a restriction settings user interface displayed on a child device 500, such as those described with reference to FIGS. 6A-6C, 8O-8Q, and 10A-10AA. The restriction settings user interface changes various restriction settings of the electronic device, as well as an indication 1402 of device usage and an indication 1408 that screen time data is shared with one or more parent devices associated with the child device. multiple affordances 1404a-e (e.g., 'Device Downtime' 1404a, 'App Limits' 1404b, 'Always Allow' 1404c, 'Content & Privacy' 1404d, and 'All website browsing data on parent device Include" 1404e). Device idle time 1404a was described in more detail above with reference to FIGS. 10A-11I. App limits 1404b are described in greater detail above with reference to FIGS. 8A-9K. Always grant 1404c was described in more detail above with reference to FIGS. 6A-13H. Next, Include All Website Browsing Data on Parent Device 1404e optionally allows the parent device to present information regarding which websites the child device 500 accesses with the web browsing application. do. With this feature turned off, the parent device optionally does not present usage information regarding which websites were accessed by child device 500 . However, accessing a website associated with an application installed on child device 500 optionally counts as using the electronic device to access that application (e.g. Time spent accessing the associated website counts toward the usage limit for that application or category of applications and is included in usage data for that application and/or category). Sharing screen time data (eg, as indicated by indication 1402) with a parent or administrator device also provides the ability to set device idle time, always allowed applications and features, sharing and privacy permissions, content Understand that this includes sharing other usage data and restricted permissions, such as purchasing preferences, age-restricted content consumption preferences, and such preferences are also optionally subject to the remote management scheme of this disclosure. want to be

As shown in FIG. 14B, the age of the child whose user account is associated with device 500 is below the threshold age at which sharing screen time data with the child's parents is optional. Accordingly, the electronic device 500 presents an indication 1408 that the screentime data is shared with the child's parent without presenting a setting to no longer share the screentime data with the child's parent.

In FIG. 14C, electronic device 500 detects contact 1403 at affordance 1404a to change one or more device pause time settings. In response to a request to change settings, electronic device 500 presents an authentication user interface, as shown in FIG. 14D. As shown in FIG. 14D, the authentication user interface prompts affordance 1406 for permission to change settings remotely from an administrative account (e.g., from a parent account or parent device) and enters a passcode to change settings. A keypad 1482 is included for In some embodiments, the passcode for changing the restriction settings is stored on the electronic device 500 so that the administrator or parent knows the passcode without the non-administrator or child knowing the passcode. different from the passcode to unlock the .

In FIG. 14E, electronic device 500 detects touch 1403 at affordance 1406 to remotely request parental permission to change restriction settings. In response to a request requesting permission to change the restriction settings, the electronic device 500 sends a signal requesting permission to change the restriction settings to another electronic device (e.g., an administrator user account or a parent user account). electronic device associated with your account).

FIG. 14F shows electronic device 500 associated with a parent's user account. The electronic device 500 presents an indication 1489-20 that the child has requested permission to change the restriction settings on the child's electronic device. As shown in FIG. 14F, in some embodiments the indication 1489-20 includes information regarding which restriction setting the child is attempting to change (eg, device idle time). The parent approves (e.g., by selecting "Allow" within indication 1498-20) or denies (e.g., by selecting "Reject"). If the parent denies the child's request to change the restriction settings, the child device cannot change the restriction settings. If the parent approves the child's request to access the restriction settings on the child's electronic device, the child's electronic device presents a user interface for changing the restriction settings. In some embodiments, once a parent approves a change to a restriction setting, the child device will be activated until one or more restriction settings are changed or until the child exits the settings user interface for more than a predetermined amount of time. During a single session (eg, until the child exits the Restrictions User Interface), access to Restrictions Settings is allowed for a predetermined period of time.

FIG. 14G shows the electronic device 500 associated with the child's user account. Electronic device 500 is associated with a device idle time, such as in response to the parent selecting "Allow" in indication 1498-20 in FIG. 14F or in response to successful entry of a passcode in FIG. 14D. A user interface 1410 is presented for changing one or more settings (1411-1417). As shown in FIG. 14G, electronic device 500 detects contact 1403 and optionally further user input to change the device downtime start time from 10:00 PM to 11:00 PM. As noted above, parental authorization to change one or more restriction settings is optionally valid for a limited amount of time. Accordingly, the electronic device 500 presents an indication 1450 that changes to the device sleep time setting can be made for another three minutes. As noted above, other authentication timeframes and criteria are possible. After the settings have been changed, the limit settings user interface is updated to reflect the changed settings, as shown in FIG. was set to 10:00 pm to 5:00 am Monday through Thursday, it will be set to 11:00 pm to 5:00 am Monday through Thursday).

When the child makes changes to the restriction settings, the parent device optionally presents an indication explaining which changes have been made. FIG. 14I shows electronic device 500 associated with a parent account. As shown in FIG. 14I, the electronic device 500 displays an indication 1498-22 that the child device has changed the device sleep time from 10:00 pm-5:00 am Monday-Thursday to 11:00 pm-5:00 am Monday-Thursday. present. Indication 1498-22 includes affordances for denying or allowing the change. Thus, parent devices can optionally override setting changes made on child devices. If the parent device approves the setting changes made by the child device, the child device will act according to those changes. For example, by approving a device sleep time change from 10:00pm-5:00am to 11:00pm-5:00am, the child device will operate in a restricted use mode starting at 10:00pm. to 11:00 p.m. in normal unrestricted mode.

If the parent rejects the setting changes made by the child device, the child device optionally presents an indication that the setting changes have been rejected. FIG. 14J shows an electronic device 500 associated with a child's user account. The electronic device 500 presents an indication 1498-24 that the change to the restriction setting has been rejected by the parent (eg, "Daddy has rejected the device downtime setting change"). Further, if the parent rejects the setting changes made on the child device, the child device will continue to operate according to the settings before the settings were changed. That is, the child device will continue to optionally transition to a restricted use mode starting at 10:00 PM.

FIG. 14K shows a usage dashboard relating to a child's device usage presented on the electronic device 500 associated with the parent user account. The child device usage dashboard provides an indication 1416 of the child's overall device usage, such as those described with reference to FIGS. 6L-6U, how the child's device usage compares to the average device usage. Graph 1424 showing detailed device usage metrics, Longest sessions on child's device during the day indication 1434, Device usage during device idle time indication 1436, Usage limit exceeded Indications 1422a-b of usage of configured applications and categories of applications, indications 1442 of usage of applications without usage limits, and indications 1442 of usage associated with applications and categories presented within the dashboard user interface. Includes a plurality of affordances 1440a-c for changing restriction settings.

As shown in FIG. 14K, the dashboard user interface includes an indication 1442 of how long the child's electronic device has been used to access the browser application, including which websites were accessed and for how long. It does not contain detailed information. However, the time spent using the browser application to access websites associated with the applications and categories for which usage metrics are presented is optionally (eg, visiting one or more websites associated with the News app optionally count toward the News app usage metrics and usage limits 1422a).

FIG. 14L shows the restrictions settings user interface presented by the electronic device 500 associated with the child user account. As shown in Figure 14L, the setting "Include all website browsing data on parent device" 1404e is activated. When this setting is activated, the administrator or parent's electronic device optionally presents information within the dashboard user interface regarding whether the website is accessed by the child device, as shown in FIG. 14M. do. In FIG. 14M, the dashboard user interface displays an indication 1442a of the amount of total time the child's electronic device has used the browser application, as well as the amount of time the child's electronic device has accessed Website A and Website B, respectively. Includes quantity indications 1442b and 1442c.

FIG. 14N shows a child restrictions settings user interface presented by electronic device 500 associated with a parent user account. The restriction settings user interface includes indications of use of the child device and multiple affordances 1404a for changing restriction settings of the child device, such as those described with reference to FIGS. Including ~f. If the child's age is above a threshold age (e.g., 13 years old), the parent optionally selects affordance 1404f to change the child's electronic device restriction settings on the child's electronic device. have the option to remove and/or change the showtime password required for As shown in FIG. 14O, when the child's age is below the threshold age, the parent device has the ability to change the showtime password by selecting affordance 1404g, but the showtime password cannot be removed.

When a parent changes a child device's restriction settings, the child device optionally presents an indication of which settings have been changed. FIG. 14P shows a restriction setting change indication 1498-28 presented on the electronic device 500 associated with the child user account. Indication 1498-28 contains information about which setting was changed and how it was changed (eg, "Daddy added a one hour usage limit to the browser app").

As described herein, the parent device can optionally access the showtime data of the child device to change one or more restriction settings of the child device. It should be appreciated that sharing showtime data is one example of many types of information and permissions that may be shared on a parent's or administrator's device. Here and throughout this description, sharing showtime data is the ability to view any of the usage metrics (e.g., showtime, notifications, device pickup, etc.) described above with reference to FIGS. Ability to set and update one or more restriction settings (e.g., device idle time and/or usage limits), set one or more content and privacy settings, content purchase settings, age-restricted content consumption settings, etc. It is understood to optionally include one or more of:

Once the child's age exceeds a predetermined threshold (eg, 18 years old), the child device optionally stops sharing screen time data with the child's parent and/or limits usage on the child device. Control of settings can be taken over from the parent device. FIG. 14Q shows an indication 1498-26 presented on child device 500 that the child device can stop sharing showtime data with the child's parent. Indication 1498-26 is optionally displayed when the child's age exceeds a predetermined threshold (eg, 18 years old). Once the child's age exceeds this threshold, the child device's restriction settings user interface is optionally updated to include a setting to stop sharing screen time data with the child's parent. FIG. 14R shows a restriction settings user interface presented on child device 500 when the child's age exceeds a threshold for which sharing screen time data with the child's parents is optional. As shown in FIG. 14R, the settings user interface is updated to include affordance 1404h ("Turn off showtime sharing"). In some embodiments, the settings user interface on child device 500 did not include affordance 1404h when the child's age was below a predetermined threshold (eg, 18 years old). FIG. 14S shows child device 500 detecting contact at affordance 1404h.

In some embodiments, in response to this request to stop sharing screentime data with the child's parent, the child device requests permission to stop sharing screentime data from the parent device. 14D, which optionally includes displaying the authorization user interface shown in FIG. 14D. The parent optionally allows the child device to retrieve the showtime data by providing a passcode or authorization on the child device, or by authenticating the request on the parent device, as described above with reference to FIG. 14F. You can approve requests to stop sharing. Where permission is required to stop sharing screentime data, screentime data is optionally shared with parents until they approve a setting change to stop sharing screentime data. continue to be shared with the device. In some embodiments, parental permission to stop sharing screentime data is not required once the child's age exceeds an age threshold (eg, 18 years old).

As shown in FIG. 14T, when the child device 500 no longer shares usage data with the child's parent, the restriction settings user interface is updated according to the changes. In FIG. 14T, the indication 1408 that showtime data is shared with the child's parent and the affordance 1404h to turn off showtime sharing are no longer presented within the restrictions settings user interface. Optionally, setting 1404e for toggling the inclusion of all website browsing data on the parent device also stops being displayed. In some embodiments, after the child device stops sharing screentime data with the parent device, the user of the child device can view the screen without the need for authentication input (e.g., passcode or authorization from the parent device). , control usage settings on child devices (e.g., device idle time, usage limits, ability to add/remove apps on child devices, change content purchase settings, view age-restricted content, privacy settings, etc.) can be changed to

15A-15G are flow diagrams illustrating a method 1500 of managing restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure. Method 1500 optionally includes device 100, device 300, or device 500 as described above with reference to FIGS. 1A-1B, 1-3, 4A-4B, and 5A-5H. run on electronic devices such as Some acts of method 1500 are optionally combined and/or the order of some acts is optionally changed.

As described below, method 1500 updates one or more restriction settings associated with electronic device 500 (e.g., a restricted device) with the permissions of another electronic device (e.g., an authorizing device) or user account. provide a way. This method reduces the cognitive burden on the user when interacting with the user interface of the device of the present disclosure, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, improving the efficiency of user interaction with the user interface conserves power and increases intervals between battery recharges.

In some embodiments, the first electronic device 500 (e.g., display, touch screen, television) and one or more input devices (e.g., touch screen, touch sensitive surface, remote For example, a smartphone, a smart watch, a tablet computer, a computer, a set-top box, etc.) while a usage restriction setting that restricts the use of the first electronic device is implemented in the first electronic device (1502) (eg , one or more applications, such as those described with reference to methods 700, 900, 1100, and/or 1300, being implemented on a first electronic device, category usage of applications, total device usage, etc. Restrictive use limits, restricted use modes, such as those described with reference to methods 700, 900, 1100, and/or 1300. In some embodiments, the first electronic device includes methods 700, 900, Devices such as those described with reference to 1100 and/or 1300 that use restriction settings allow (e.g. parent accounts or administrators in a set of related accounts including one or more children or restricted accounts) restricted devices (e.g., one or more parent or administrator accounts), such as those described with reference to methods 700, 900, 1100, and/or 1300, controlled by a a child in a set of associated accounts, including a device associated with a restricted account), responds, via one or more input devices, to requests to change usage restriction settings on the first electronic device. A series of one or more inputs (e.g., inputs on a restricted device to change the usage limits in force on the restricted device, restricted usage mode settings, etc. Such usage restriction settings are shown in Fig. 14C, etc. In some embodiments, this input to change usage restriction settings on the restricted device is implemented on the restricted device. (1504) is detected in the usage restriction settings user interface on the restricted device that displays information about the usage restriction settings that are currently running.

In some embodiments, in response to receiving the series of one or more inputs, the series of one or more inputs is different from the first electronic device, such as in FIGS. 14D-14E . From the electronic device (or from an administrator account associated with a second electronic device). In some embodiments, the request for authorization includes multiple accounts with administrator privileges (e.g., multiple ) includes input corresponding to the request requesting permission to change the usage restriction settings (e.g., the user interface displayed by the restricted device 1506 ), the method 700 , 900 , 1100, and/or 1300, or providing a passcode to change settings on a restricted device, or granting permission to change usage restriction settings from an authorizing device. Provide multiple ways to change usage restriction settings on restricted devices, including requesting or requesting permission from an administrator account associated with the device to allow. device detects input requesting permission to change usage restriction settings from the authorizing device), the first electronic device tells the second electronic device, such as FIGS. Send 1508 a request for permission to change usage restriction settings on one electronic device (e.g., a notification or other A request to have a message displayed on the authorizing device, in some embodiments, this notification on the authorizing device identifies the specific usage restriction settings that the restricted device is attempting to change, and/or or information about how the restricted device is attempting to change the usage restriction setting (e.g., the new value of the usage restriction setting detected on the restricted device).In some embodiments, Allow Changes Depending on the input detected on the Allowing Device, the Allowing Device sends a Change Authorization to the Restricted Device, and the Restricted Device modifies the usage restriction settings on the Restricted Device. In some embodiments, the restricted device is not allowed to change the usage restriction setting, and the restricted device is not allowed to change the usage restriction setting, depending on the input detected by the authorizing device denying the Restriction settings change usage restriction settings input for is detected before).

In some embodiments, after sending 1510 a request for authorization to change the usage restriction settings to the second electronic device, as in FIGS. 14D-14F, the authorization response is 2 electronic device (e.g., the user of the authorizing device selects the "Allow" affordance displayed on the notification received at the authorizing device), the first electronic device performs the 14G-14H, etc. (1512), according to a determination that a denying response was received from the second electronic device (e.g., the user of the authorizing device (1514), the first electronic device is denied changing usage restriction settings, such as FIG. 14I. In some embodiments, instead of entering a passcode on the restricted device, the user of the restricted device allows the restricted device to change usage settings even if no response is received from the authorizing device. can be made possible.

The above-described method of controlling from a device that permits changes to usage restriction settings on a restricted device is an efficient way to facilitate such changes when an electronic device requires authentication from another party. provide a method that enhances the usability of the device and makes the interface between the user and the device more efficient (e.g., allowing the user to interact with the device with less input) ), in addition to reducing power usage and improving the battery life of the device by allowing the user to use the device more quickly and efficiently.

In some embodiments, allowing the first electronic device to change the usage restriction setting is a method such as that of FIG. 14G to allow the first electronic device to change the usage restriction setting. enabling 1516 the first electronic device to change the usage restriction settings until detection of a termination condition of the (e.g., the restricted device receives approval from the authorizing device for a predetermined period of time). Restricted devices that are enabled to change usage restriction settings for a period of time after (e.g., 30 seconds, 2 minutes, 5 minutes) will be able to change the settings after which such changes will be made. Allowed to change usage restriction settings until exiting the user interface (and optionally requesting permission again before being allowed to change usage restriction settings after exiting the settings user interface) must be done), the restricted device is allowed to change the usage restriction setting until the restricted device confirms the setting change (e.g., a "Save or "OK" or "Back" affordances), the restricted device will exit the settings user interface for longer than a predetermined amount of time (e.g., 30 seconds, 2 minutes, 5 minutes). allowed to change usage limit settings up to ).

The above-described methods of restricting in various ways the ability of a restricted device to change usage-restricted settings subject to authorization to change usage-restricted settings may prevent the electronic device from allowing such authorization to be unlimited. This improves the usability of the device and streamlines the interface between the user and the device (e.g. changing usage settings on devices with restricted allowed devices). management), as well as reducing power usage and improving device battery life by allowing users to use the device more quickly and efficiently.

In some embodiments, after enabling the first electronic device to change the usage restriction setting, the first electronic device changes the usage restriction setting to change the usage restriction setting, such as in FIG. modify 1518 the operation of the first electronic device according to the change in the (e.g., performed on the restricted device according to the change in usage settings, as described in methods 700, 900, 1100, and/or 1300); change application or application usage limits, change device idle time on restricted devices according to changes in usage settings, etc.).

The above-described method of operating a restricted device according to updated usage restriction settings enables an electronic device to provide an efficient method of implementing such updates, thereby improving the operability of the device. Enhanced to make the user interface with the device more efficient (e.g., by allowing the user to interact with the device with less input), as well as allowing the user to use the device more quickly and efficiently reduce power usage and improve device battery life by allowing

In some embodiments, in response to receiving the sequence of one or more inputs, the sequence of one or more inputs corresponds to at least the entry of authentication credentials, such as on the keypad 1482 shown in FIG. 14D. (eg, a passcode, biometric, or other authentication credential for changing usage restriction settings as described in methods 700, 900, 1100, and/or 1300), the authentication credential is successfully authenticated (e.g., the user of the restricted device enters the correct credentials to change the usage restriction settings), the first electronic device may use the Allowed 1522 to change the restriction settings, according to which the authentication credentials were not successfully authenticated (e.g., the user of the restricted device entered incorrect credentials to change the usage restriction settings). ), the first electronic device forgoes allowing the first electronic device to change the usage restriction setting (1524), such as FIG. 14J. Thus, in some embodiments, the restricted device changes usage restriction settings in response to authentication credentials being entered at the restricted device instead of receiving authentication from the authorizing device. enabled. In some embodiments, once authentication credentials are entered at a restricted device, a request for authorization is not sent to the authorizing device.

The above-described method of providing a passcode or other authentication input on a restricted device to change usage restriction settings is an efficient way for electronic devices to enable such changes (e.g., locally). , which improves the usability of the device and makes the user-device interface more efficient (e.g., by allowing the user to interact with the device with alternative inputs). ), in addition to reducing power usage and improving the battery life of the device by allowing the user to use the device more quickly and efficiently.

In some embodiments, the first electronic device identifies, via one or more input devices, one or more websites viewed on the first electronic device. Input is received 1526 to allow or disallow sharing of website browsing activity with the second electronic device (eg, in a manner similar to dialog 1489-20 described above with reference to FIG. 14F, the permission Allowing or disallowing the device to see the names/identifications of individual websites viewed by the user of the restricted device (allowing or not allowing the restricted device to share individual website browsing (compared to the total website browsing time that the allowed devices can optionally view, regardless of whether or not they are allowed).In some embodiments, the restricted device user has a restricted device account users can only control the sharing of this website browsing data if they are over a certain age (e.g. 10, 13, 18), otherwise they cannot control the sharing of this data Can not). In response to receiving input to allow or disallow sharing of website browsing behavior with the second electronic device, in a manner similar to the allowing or disallowing described above with reference to FIG. 14F ( 1528), in accordance with the determination that the input identifies one or more websites viewed on the first electronic device to allow sharing with the second electronic device, the first electronic device may: , FIG. 14M, and shares 1530 website browsing behavior identifying one or more websites viewed on the first electronic device with the second electronic device (e.g., the device that allows identifying information of individual websites viewed by the user of the viewed device (e.g., web address, title/name, etc.) and/or the time spent viewing those individual websites can be viewed), input 14K, according to the determination that the website browsing behavior identifying one or more websites viewed on the first electronic device is not permitted to be shared with the second electronic device. refrain from sharing 1532 website browsing behavior identifying one or more websites viewed on the first electronic device with the second electronic device (e.g., allowed devices are restricted (e.g., web addresses, titles/names, etc.) and/or time spent viewing those individual websites viewed by the user of the device.

The above-described methods of controlling the sharing of individual website usage information enable electronic devices to provide efficient methods of maintaining privacy on restricted devices while still facilitating the enforcement of usage restrictions. , which improves the usability of the device and makes the interface between the user and the device more efficient (e.g., by allowing the user to interact with the device with less input), as well as allowing the user to Reduce power usage and improve device battery life by allowing the device to be used more quickly and efficiently.

In some embodiments, while a setting disallowing sharing of website browsing behavior identifying one or more websites viewed on the first electronic device with the second electronic device is enabled. In turn, the first electronic device shares 1534 website browsing behavior with the second electronic device that does not identify one or more websites viewed on the first electronic device, such as FIG. 14K ( For example, even if the authorized device cannot see individual website browsing information from a restricted device, the authorized device can still see which websites were viewed, the time of day the website was viewed, the web Limitations such as the duration of individual sessions of viewing the Site and/or the total amount of time spent viewing the Website on a restricted device without being able to see the particular webpage or subdomain viewed; You can see information about overall web usage on your device, instead the amount of time the website was used is aggregated into application usage).

Continuing to share general web usage information with authorized devices The methods described above provide an efficient way of enforcing usage restrictions even when electronic devices do not share individual website usage information with authorized devices. , which improves the usability of the device and makes the interface between the user and the device more efficient (e.g., by allowing the user to interact with the device with less input); , reducing power usage and improving device battery life by allowing users to use devices more quickly and efficiently.

In some embodiments, while a setting disallowing sharing of website browsing behavior identifying one or more websites viewed on the first electronic device with the second electronic device is enabled. , the first electronic device shares 1536 website browsing behavior corresponding to one or more applications or one or more categories of applications with a second electronic device (e.g., second The sharing with the electronic device of the Web for accessing the website associated with the use of the first application and the first application without sharing specific information about the web browsing behavior performed by the web browser. Aggregate statistics about browser usage and aggregate statistics about the use of the second application and the use of web browsers to access websites associated with the second application (e.g., allow restricted devices). Even if you can't see individual website browsing information from the devices you authorize, your authorized devices may still use applications (e.g., ESPN website browsing corresponding to the ESPN app reflected on the authorized device as use of the ESPN app). ) or websites corresponding to the application's category (e.g., social media website browsing corresponding to the social media app category is reflected on devices that allow use within the app's social media category) Further, in some embodiments, usage limits for those applications or categories are still imposed on restricted devices where applicable, methods 700, 900, 1100, and /or website browsing on the restricted device becomes restricted when that browsing is restricted by application/category limits in force on the restricted device, as described in 1300) .

The above-described method of reflecting website usage data corresponding to applications/categories of applications provides an efficient method of enforcing usage restrictions even when electronic devices are not shared with devices that permit individual website usage information. , thereby improving the usability of the device and making the interface between the user and the device more efficient (e.g., by allowing the user to interact with the device with less input) In addition, it reduces power usage and improves the battery life of the device by allowing the user to use the device more quickly and efficiently.

In some embodiments, following a determination that the user associated with the account on the first electronic device is below a predetermined age (eg, 10, 13, 15), the second electronic device , FIG. 14O, etc. (e.g., the second device cannot be removed) ( 1538) (e.g., the authorizing device provides a passcode or other authentication credential or action (such as authorizing the authorizing device) on the restricted device to change usage restriction settings on the restricted device In some embodiments, however, the authorizing device is a passcode or other authentication credentials can be changed). Upon determination that the user associated with the account of the first electronic device is older than a predetermined age (e.g., 10, 13, 15), the second electronic device may use Enabled 1540 to remove the requirement for authentication on the first electronic device to change the restriction settings (e.g., the authorizing device changes the usage restriction settings on the restricted device). can eliminate the requirement to provide a passcode or other authentication credential or action (such as authorizing an authorizing device) on the restricted device in order to do so.In some embodiments, the authorizing device Alternatively, passcodes or other authentication credentials required on the restricted device to change usage restriction settings on the restricted device may still be changed).

The above-described method of providing the controlled ability to remove the passcode requirement from devices restricted to authorized devices allows electronic devices to be used even when individual website usage information is not shared with authorized devices. It is possible to provide an efficient way of enforcing restrictions, thereby improving the usability of the device and making the user-device interface more efficient (e.g., the user interacting with the device with less input). In addition, it reduces power usage and improves the battery life of the device by allowing the user to use the device more quickly and efficiently.

In some embodiments, after removing the requirement for authentication at the first electronic device to change the usage restriction setting, the first electronic device and the second electronic device Usage restriction settings can be changed, including usage restriction settings at the first electronic device, such as the electronic device can change one or more settings as described above with reference to FIG. 14G (1542 ) (e.g., when the passcode is removed, both the authorizing device or administrator account and the restricted device can change the restrictions and limits in place on the restricted device).

The method described above that allows both the restricted device and the authorizing device to change usage restriction settings once the passcode requirement has been removed ensures that the electronic device does not allow use of the authorizing device on the restricted device. It is possible to provide an efficient way to facilitate such changes while maintaining the ability to affect restriction settings, thereby improving the usability of the device and improving the interface between the user and the device. by making it more efficient (e.g., by allowing the user to interact with the device with less input), as well as by allowing the user to use the device more quickly and efficiently Reduce usage and improve device battery life.

In some embodiments, following a determination that the user associated with the first electronic device account is older than a predetermined age (eg, 15, 18), the first electronic device 1544 can stop sharing device usage information with a second electronic device, such as FIG. A device or administrator account can be deactivated, hi some embodiments, a restricted device can leave an authorizing device without relying on any authentication from the authorizing device. , you can turn off or otherwise adjust the usage restriction settings on restricted devices). Upon determination that the user associated with the account of the first electronic device has an age below a predetermined age, the second electronic device may initiate sharing of device usage information with the second electronic device, such as in FIG. 14B. Cannot be deactivated 1546 (eg, the restricted device cannot deactivate the ability of the authorizing device or administrator account to view usage information about the restricted device).

The above-described methods of controlling when restricted devices can stop sharing usage information with permissive devices suggest that electronic devices provide an efficient way to control such functionality. which enhances the usability of the device and makes the interface between the user and the device more efficient (e.g., by allowing the user to interact with the device with less input); Reduce power usage and improve device battery life by allowing users to use devices more quickly and efficiently.

In some embodiments, ceasing to share device usage information with the second electronic device may be performed by disabling device usage information from the second electronic device in a manner similar to that described above with reference to FIG. 14F. Require 1548 approval to stop sharing information with a second electronic device (e.g., a restricted device can be configured without approval from the authorizing device or an administrator account to do so). In some embodiments, if a restricted device attempts to turn off sharing of usage information with an authorized device, the authorized device displays a notification showing the request with the option to "allow" or "deny" the request.If the user of the authorizing device selects "allow", the restricted device can optionally If the user of the permitting device selects "deny", the restricted device can optionally stop sharing usage information with the permitting device. cannot stop sharing with you).

The above-described method of requiring authorization of the authorizing device to stop sharing usage information with the authorizing device provides an efficient way for an electronic device to control such changes by the authorizing device. , which improves the usability of the device and makes the interface between the user and the device more efficient (e.g., by allowing the user to interact with the device with less input); , reduce power usage and improve device battery life by allowing users to use devices more quickly and efficiently.

In some embodiments, stopping sharing device usage information with the second electronic device may be performed by sharing device usage information with the second electronic device from the second electronic device, such as FIG. 14T. does not require approval to stop (1550) (e.g., a restricted device shares usage information with an authorized device without approval from the authorizing device or an administrator account to do so). In some embodiments, notification of this action indicates that the action is being taken by a restricted device without the enabling device's ability to approve or deny the action. , is sent to the authorizing device (in some embodiments, notification of this action is not sent to the authorizing device).

The methods described above that do not require approval of an authorizing device to stop sharing usage information allow an electronic device to provide an efficient way to stop such sharing, thereby allowing the device to Improve usability to make the user interface with the device more efficient (e.g., by allowing the user to interact with the device with less input), as well as allow the user to interact with the device more quickly and efficiently. Reduce power usage and improve battery life of the device by allowing it to be used on a regular basis.

In some embodiments, upon determining that the user associated with the first electronic device account has reached a predetermined age (e.g., based on the user's birthday and the current date/time), the The one electronic device generates (1552) a notification indicating that the first electronic device can stop sharing device usage information with the second electronic device, such as FIG. 14Q (e.g., restricted The device will display a notification when the user of the restricted device reaches the age at which the user can stop sharing usage information with the permissive device, and that the user can now take such action. become known to the user).

The above-described method of generating notifications to users of restricted devices when information sharing with permitted devices can be changed provides an efficient way for electronic devices to facilitate such changes. to improve the usability of the device and make the interface between the user and the device more efficient (e.g., by allowing the user to interact with the device with less input); In addition, it reduces power usage and improves the battery life of the device by allowing the user to use the device more quickly and efficiently.

In some embodiments, following a determination that the user associated with the account of the first electronic device has an age greater than a predetermined age, the device usage information of the second electronic device, such as FIGS. 14R-14S, and is available 1554 on the first electronic device (e.g., an affordance, button, or controller is displayed to change the sharing of usage information with authorized devices). , enabled within the usage restriction settings user interface on the restricted device), according to a determination that the user associated with the account of the first electronic device has an age below a predetermined age, such as in FIG. 14B; Controls to stop sharing device usage information with a second electronic device are not available 1556 on the first electronic device (e.g., to change sharing of usage information with authorized devices). Affordances, buttons, or controllers are not displayed within the usage restriction user interface on restricted devices, or are displayed within the usage restriction user interface on restricted devices but are not enabled (e.g., laid out)).

The methods described above that enable or disable controls for changing information sharing with authorized devices facilitate such changes while complying with restrictions on the ability of the electronic device to make such changes. to provide an efficient way to interact with the device, thereby improving the usability of the device and making the interface between the user and the device more efficient (e.g., allowing the user to interact with the device with less input). ), in addition to reducing power usage and improving the battery life of the device by allowing the user to use the device more quickly and efficiently.

In some embodiments, the user associated with the first electronic device account has an age greater than a predetermined age (1558), such as in FIGS. 14R-14S. A first electronic device, such as FIG. 14S, receives (1560) input via one or more input devices to stop sharing device usage information with a second electronic device, and In response to receiving input to stop sharing with the second electronic device, the first electronic device stops sharing device usage information with the second electronic device ( 1562) (eg, the user of the restricted device selects a button or toggle switch within the usage restriction settings user interface to stop sharing usage information with the allowed device). In some embodiments, after stopping sharing device usage information with the second electronic device, the first electronic device can change usage restriction settings on the first electronic device, and The second electronic device cannot change 1564 the usage restriction settings on the first electronic device in a manner similar to that described above with reference to FIG. When usage information sharing and/or usage limit sharing is disabled, the previously restricted device can change the usage limit settings on the previously restricted device, but the device or administrator Accounts can no longer change such settings on previously restricted devices (in effect, restricted devices are no longer restricted by optionally authorizing devices/administrator accounts) .

The method described above that allows a previously restricted device to change usage restriction settings on that device, but does not allow an authorizing device to do so, allows an electronic device to change usage restriction settings on that device. This allows the device to operate independently of any other device, thereby improving the usability of the device and making the user-device interface more efficient (e.g., allowing the user to interact with the device with less input). ), in addition to reducing power usage and improving the battery life of the device by allowing the user to use the device more quickly and efficiently.

In some embodiments, while the first electronic device, such as FIG. 14G, is enabled to change the usage restriction setting (1566), the first electronic device via one or more input devices , FIG. 14G, receives 1568 a series of one or more inputs for changing one or more usage restriction settings on the first electronic device (e.g., usage restriction settings on the restricted device After receiving approval from the authorizing device to change the one or more usage restrictions on the first electronic device; In response to receiving the series of one or more inputs for changing the settings, the first electronic device responds to changing one or more usage restriction settings on the first electronic device, such as FIG. 14I. Send 1570 information to the second electronic device (e.g., the restricted device receives information regarding changes to usage limit settings that the restricted device attempted to make (e.g., specific usage limit changes, specific information about any changes attempted on the restricted device, such as device sleep time changes, to the authorized device or to an administrator account.In some embodiments, the restricted device uses making the change and, in conjunction with making the change, sending information about the change to the authorizing device, which optionally allows users of the authorizing device to see the changes made on the restricted device; In such embodiments, the notification optionally indicates that the user of the authorizing device can undo, reject, or change the changes made by the restricted device. It does not have a mechanism that can be overridden, rather, in such embodiments, the authorizing device can optionally override any of the changes made by the restricted device. In contrast, in some embodiments, the restricted device does not make any changes to the restricted use settings and provides information about the attempted changes. first sent to the authorized device, and the authorized device optionally sends to the authorized device's user Display a notification of the attempted change so that users can see the proposed change on restricted devices. In such embodiments, the notification optionally provides a mechanism (e.g., selectable affordances)).

The above-described method of transmitting information about usage limit changes to authorizing devices enables an electronic device to efficiently communicate to devices that authorize such changes, thereby improving the operability of the device. make the interface between the user and the device more efficient (e.g., by allowing the device to operate with less input from the user), as well as allow the user to use the device more quickly and efficiently This reduces power usage and improves device battery life.

In some embodiments, following a determination that one or more usage restriction settings on a first electronic device have been remotely changed (e.g., on a second electronic device, or on a first electronic device such as an administrator account). by another electronic device associated with a user enabled to change the usage restriction settings of the first electronic device, such as in FIG. 14P. Display 1572 a notification indicating changes to one or more usage restriction settings (e.g., the restricted device receives information from the permitting device about changes made to the usage restriction settings on the restricted device). Received and in response, the restricted device displays a notification on the restricted device with details of the change (e.g., usage limit change, device downtime, etc.) so that the user of the restricted device can Allows you to see changes made by devices you allow).

The above-described method of displaying on a restricted device a notification having usage restriction changes made by an authorizing device is an efficient way for an electronic device to provide information of such changes to a user of a restricted device. , which improves the usability of the device and makes the interface between the user and the device more efficient (e.g., by allowing the user to interact with the device with less input ), in addition to reducing power usage and improving the battery life of the device by allowing the user to use the device more quickly and efficiently.

In some embodiments, the one or more usage restriction settings at the first electronic device that are being remotely changed are the usage restriction settings previously not implemented at the first electronic device, such as in FIG. 14A. including defining 1574 the initial usage restriction settings on the first electronic device when the device is activated (e.g., the restricted device can be configured from the authorizing device or an administrator account to allow the authorizing device to implement on the restricted device). information about the initial usage restrictions to be received by the authorizing device when they enforce those restrictions, and in response, the restricted device will receive details of those initial restrictions (e.g., usage limits, device downtime, etc.). ) on the restricted device to allow the user of the restricted device to see the usage restrictions currently in place on the restricted device. The notification includes information about any restrictions currently in place on the restricted device (e.g., any usage limits, any characteristics of device idle time, etc.) In some embodiments, the notification includes total Limits (as opposed to limits for individual games), total screen time limits (as opposed to individual screen time limits), device idle time start and stop times (allowed for device idle time) instead includes a summary of the major restrictions currently in place on the restricted device (as opposed to also including device-defined exceptions).

The above-described method of displaying on a restricted device a notification having initial usage restriction settings made by an authorizing device is an efficient way for an electronic device to provide information of such settings to a user of a restricted device. provide a method that enhances the usability of the device and makes the interface between the user and the device more efficient (e.g., allowing the user to interact with the device with less input) ), in addition to reducing power usage and improving the battery life of the device by allowing the user to use the device more quickly and efficiently.

It is understood that the particular order described for the acts in FIGS. 15A-15G is exemplary only and is not intended to represent the only order in which the acts may be performed. want to be Those skilled in the art will recognize various methods for reordering the operations described herein. Additionally, details of other processes described herein with respect to other methods described herein (eg, methods 700, 900, 1100, and 1300) can be found in method 1500 described above with respect to FIGS. 15A-15G. is also applicable in a similar manner. For example, the method of updating restriction settings on one electronic device with the permissions of another electronic device or user account described above with reference to method 1500, usage restriction settings, etc., are optionally other than those described herein. usage metrics dashboard user interface, usage metrics, notification metrics, device pickup metrics, usage limit settings, as described herein with reference to methods (e.g., methods 700, 900, 1100, and 1300) of have one or more of the following properties: For the sake of brevity, these details are not repeated here.

Operations in the information processing methods described above may be performed within an information processing device, such as a general-purpose processor (eg, as described above in connection with FIGS. 1A-1B, 3, 5A-5H) or an application-specific chip. is optionally performed by activating one or more functional modules of Further, the operations described above with reference to FIGS. 15A-15G are optionally performed by the components shown in FIGS. 1A-1B. For example, display operation 1572 and receive operations 1504 , 1526 , 1560 , and 1568 are optionally performed by event sorter 170 , event recognizer 180 , and event processor 190 . Event monitor 171 of event sorter 170 detects contact on touch screen 504, and event dispatcher module 174 delivers event information to application 136-1. Each event recognizer 180 of application 136-1 compares the event information with respective event definitions 186 and determines that a first touch at a first location on the touch screen is a default event, such as selection of an object on the user interface. It determines whether it corresponds to the event or sub-event of . When the corresponding predefined event or sub-event is detected, the event recognizer 180 activates the event processor 190 associated with detecting the event or sub-event. Event handler 190 optionally utilizes or calls data updater 176 or object updater 177 to update application internal state 192 . In some embodiments, the event handler 190 accesses the corresponding GUI updater 178 to update what is displayed by the application. Likewise, it will be apparent to those skilled in the art how other processes may be implemented based on the components shown in FIGS. 1A-1B.

As noted above, one aspect of the present technology is the collection and use of data available from various sources to control and/or present device usage information to users. This disclosure indicates that, in some cases, this collected data is personal information that uniquely identifies a particular person or can be used to contact that person or identify that person's location. It is contemplated that it may contain data. Such personal data may include demographic data, location-based data, phone number, email address, Twitter ID, home address, user's health or fitness level (e.g., vital sign measurements, medication information, (athletic information), date of birth, or any other identifying or personal information.

The present disclosure recognizes that the use of such personal information data in the present technology can be used to the benefit of the user. For example, personal information data can be used to present or control device usage in ways that are meaningful to the user. The use of such personal information data thus allows for more individualized delivery of such services to users. Further, other uses of personal information data that benefit users are also contemplated by this disclosure. For example, health and fitness data may be used to provide insight into a user's overall wellness, or as positive feedback to individuals using technology to pursue wellness goals. may be used.

This disclosure contemplates that entities responsible for the collection, analysis, disclosure, transmission, storage or other use of such personal information data will adhere to robust privacy policies and/or practices. Specifically, such entities will, at all times, implement privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for the confidentiality and confidentiality of personal information data. should be used. Such policies should be easily accessible to users and updated as data collection and/or use changes. Personal information from users should be collected for that entity's lawful and legitimate uses and should not be shared or sold except for those lawful uses. Further, such collection/sharing should only be performed after informing and obtaining consent from the user. In addition, such entities protect and secure access to such Personal Data and ensure that others who have access to that Personal Data comply with their privacy policies and procedures. all necessary measures should be taken to Further, such entities may themselves be evaluated by third parties to certify their adherence to widely accepted privacy policies and practices. In addition, policies and practices should be tailored to the specific types of personal information data collected and/or accessed and to be consistent with applicable laws and standards, including jurisdiction-specific considerations. For example, in the United States, collection or access to certain health data may be governed by federal and/or state laws, such as, for example, the Health Insurance Portability and Accountability Act (HIPAA); may be subject to regulatory and policy ramifications and should be dealt with accordingly. Different privacy practices should therefore be maintained for different types of personal data in each country.

Notwithstanding the foregoing, the present disclosure also contemplates embodiments in which a user selectively prevents use of or access to personal information data. That is, the present disclosure contemplates that hardware and/or software elements may be provided to prevent or block access to such personal information data. For example, when presenting information about device usage, the Technology allows users to choose to “opt-in” or “opt-out” of participation in the collection of personal information data either during registration for the service or at any time thereafter. can be configured to allow In another example, the user may choose not to provide user-based or device-based usage data for determining device usage and/or control of such usage. In addition to providing "opt-in" and "opt-out" options, this disclosure contemplates providing notice regarding access or use of personal information. For example, the user may be notified upon download of an app that will access the user's personal data, and then reminded again just before the personal data is accessed by the app.

Further, it is the intent of this disclosure that personal information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use. Risk can be minimized by limiting data collection and deleting data when it is no longer needed. Additionally, where applicable, data de-identification can also be used to protect user privacy in certain health-related applications. De-identification includes, where appropriate, removing certain identifiers (e.g. date of birth, etc.), controlling the amount or specificity of data stored (e.g. location data rather than address level). city level), controlling how data is stored (e.g., aggregating data across users), and/or in other ways.

Thus, while this disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, this disclosure does not disclose that those various embodiments also It is also contemplated that it can be performed without the need to access such personal information data. That is, the lack of all or part of such personal information data does not render the various embodiments of the present technology inoperable. For example, based on non-personal data or minimal personal information such as content requested by the device associated with the user, other non-personal information available on the device, or publicly available information; By inferring device usage, device usage information can be determined.

The foregoing description, for purposes of explanation, has been described with reference to specific embodiments. However, the illustrative discussion above is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in light of the above teaching. The best description of the principles of the invention and its practical application is thereby provided to enable others skilled in the art to best understand the invention and the various described embodiments in various modifications suitable for the particular uses envisioned. The embodiments have been chosen and described to enable use in the form of.

Claims (20)

a method,
In an electronic device that communicates with a display and one or more input devices,
using the display to display a dashboard user interface including a visual indication of a first metric of use and a visual indication of a second metric of use;
the first usage metric is associated with receiving notifications associated with one or more first applications of the electronic device;
The visual indication of the first usage metric indicates a number of received notifications associated with the one or more first applications of the electronic device during a first predetermined time period. , including the indicated number, and
the second usage metric is associated with receiving notifications associated with one or more second applications of the electronic device;
The visual indication of the second usage metric measures the number of received notifications associated with the one or more second applications of the electronic device during the first predetermined time period. indicate, including the indicated number,
and
via the one or more input devices while displaying the visual indication of the first metric of usage and the visual indication of the second metric of usage on the dashboard user interface. receiving input corresponding to a request to display a visual indication of a third metric of use different from the first metric of use and the second metric of use;
updating the dashboard user interface to include the visual indication of the third usage metric in response to receiving the input;
A method. 2. The method of claim 1, wherein
the electronic device is one of a plurality of electronic devices associated with a user account;
the dashboard user interface includes a visual indication of a first individual usage metric associated with a first operation of the plurality of electronic devices associated with the user account containing the electronic device;
the dashboard user interface includes a visual indication of the first individual usage metric including a first quantification of usage;
the first quantification of use includes an aggregate use of the plurality of electronic devices, including the electronic device, performing the first action during the first predetermined time period;
Method. 3. The method of claim 2, wherein
the dashboard user interface associated with the first operation of the electronic device but not associated with the first operation of a second electronic device included in the plurality of electronic devices; including visual indications of individual usage metrics for
Method. 2. The method of claim 1, further comprising:
via the one or more input devices while displaying the visual indication of the first metric of usage and the visual indication of the second metric of usage on the dashboard user interface. receiving input corresponding to a request to display the first usage metric and the second usage metric in more detail;
the dashboard user to display a second visual indication of the first metric of use and a second visual indication of the second metric of use in response to receiving the input; updating an interface, wherein the second visual indication of the first metric of usage and the second visual indication of the second metric of usage comprise:
a first discrete visual indication of quantification of use of the electronic device performing a first action for each of a plurality of time periods during the first predetermined time period;
a second visual indication of quantification of use of the electronic device performing a second action for each of the plurality of time periods during the first predetermined time period;
including
A method. The method of claim 1, wherein
The dashboard user interface further comprises:
A first affordance visually associated with the visual indication of the first usage metric, the setting for changing one or more settings associated with the first usage metric. a first affordance selectable to display a user interface;
A second affordance visually associated with the visual indication of the second usage metric, the setting for changing one or more settings associated with the second usage metric. a second affordance selectable to display a user interface;
A method, including 2. The method of claim 1, wherein
the dashboard user interface includes a visual indication of a first individual usage metric associated with a first operation of the electronic device during the first predetermined time period;
The first predetermined period is the current day,
the third usage metric is associated with the first operation of the electronic device;
wherein the visual indication of the third usage metric includes a third quantification of usage of the electronic device performing the first action during the week prior to the current day;
Method. 2. The method of claim 1, wherein
the dashboard user interface includes a visual indication of a first individual usage metric associated with displaying information on the display;
the first individual usage metric includes an amount of time that the electronic device was used to display information during the first predetermined time period;
Method. 8. The method of claim 7, wherein
displaying information on the display includes displaying information on the display using one or more first applications;
The first individual usage metric measures the amount of time the electronic device was used to display information using the one or more first applications during the first predetermined time period. including
a usage limit is set for the one or more first applications;
The visual indication of the first individual usage metric further includes an indication of the usage limit of the one or more first applications, wherein the indication of the usage limit comprises the visually associated with the visual indication of a first individual usage metric;
Method. 8. The method of claim 7, wherein
The visual indication of the first individual usage metric includes an indication of an amount of time that the electronic device was used to present information using each of a plurality of application groups, each an application group includes one or more applications accessible on the electronic device;
The dashboard user interface provides a visual indication of a second individual usage metric associated with an amount of time that the electronic device is used to present information using the first application group. including
wherein the visual indication of the second individual usage metric is a visual indication of the second individual usage metric separate from the visual indication of the first individual usage metric; including
Method. 2. The method of claim 1, wherein the dashboard user interface comprises:
a visual indication of a first individual usage metric associated with executing one or more first applications accessible on the electronic device;
a visual indication of a second individual usage metric associated with running one or more second applications accessible on the electronic device;
A method, including 11. The method of claim 10, wherein
the one or more first applications are a plurality of applications belonging to the same category;
the one or more second applications is an application;
Method. 11. The method of claim 10, wherein
According to a determination that the total usage of the plurality of first applications of the one or more first applications exceeds a predetermined category usage threshold, the dashboard user interface displays the combined usage of the plurality of first applications. including usage metrics,
Upon determining that the total usage of the plurality of first applications of the one or more first applications does not exceed the predetermined category usage threshold, the dashboard user interface causes the plurality of first applications to: individual application usage metrics of the plurality of first applications without including a combined usage metric for
Method. 11. The method of claim 10, wherein
In accordance with a determination that a single first application usage of the one or more first applications exceeds a predetermined application usage threshold, the dashboard user interface displays usage for the single first application. contains metrics for
Upon determining that the usage of the single first application of the one or more first applications does not exceed the predetermined application usage threshold, the dashboard user interface controls the one or more first applications. including usage metrics for applications in
Method. 2. The method of claim 1, wherein the dashboard user interface further comprises:
a first affordance selectable to display a settings user interface for changing notification settings of the one or more first applications, wherein the visual indication of the first usage metric comprises: a visually associated first affordance;
a second affordance selectable to display a settings user interface for changing notification settings of the one or more second applications, wherein the visual indication of the second usage metric comprises: a visually associated second affordance;
A method, including 2. The method of claim 1, wherein the dashboard user interface includes a visual indication of a first individual usage metric associated with detecting a user attention event.
Method. 2. The method of claim 1, further comprising:
presenting an indication of a notification associated with the dashboard user interface prior to displaying the dashboard user interface, the notification being a selectable affordance for displaying the dashboard user interface; and wherein the dashboard user interface is displayed in response to detecting user input to select the affordance. 2. The method of claim 1, further comprising:
Displaying a widget user interface prior to displaying the dashboard user interface, the widget user interface including one or more widgets, each widget representing one of the applications accessible on the electronic device. comprising a secondary user interface, wherein the one or more widgets include a metric widget associated with the dashboard user interface;
the metric widget includes visual indications of individual usage metrics;
the metric widget is selectable to display the dashboard user interface;
the dashboard user interface is displayed in response to detecting user input selecting the metric widget;
Method. 2. The method of claim 1, further comprising:
displaying a usage settings user interface for the electronic device prior to displaying the dashboard user interface, the usage settings user interface comprising:
visual indication of individual usage metrics and
an affordance selectable to display the dashboard user interface, the dashboard user interface being displayed in response to receiving user input selecting the affordance;
A method, including an electronic device,
one or more processors;
memory;
one or more programs, said one or more programs stored in said memory and configured to be executed by said one or more processors, said one or more programs comprising:
using a display to present a dashboard user interface including a visual indication of a first usage metric and a visual indication of a second usage metric;
the first usage metric is associated with receiving notifications associated with one or more first applications of the electronic device;
The visual indication of the first usage metric indicates a number of received notifications associated with the one or more first applications of the electronic device during a first predetermined time period. , including the indicated number, and
the second usage metric is associated with receiving notifications associated with one or more second applications of the electronic device;
The visual indication of the second usage metric measures the number of received notifications associated with the one or more second applications of the electronic device during the first predetermined time period. indicate, including the indicated number,
and
via one or more input devices while displaying the visual indication of the first metric of use and the visual indication of the second metric of use on the dashboard user interface. , receiving input corresponding to a request to display a visual indication of a third metric of use different from the first metric of use and the second metric of use;
updating the dashboard user interface to include the visual indication of the third usage metric in response to receiving the input;
An electronic device containing instructions for performing A non-transitory computer-readable recording medium storing one or more programs, the one or more programs comprising instructions, the instructions being executed by one or more processors of an electronic device to to the device,
using a display to present a dashboard user interface including a visual indication of a first usage metric and a visual indication of a second usage metric;
the first usage metric is associated with receiving notifications associated with one or more first applications of the electronic device;
The visual indication of the first usage metric indicates a number of received notifications associated with the one or more first applications of the electronic device during a first predetermined time period. , including the indicated number, and
the second usage metric is associated with receiving notifications associated with one or more second applications of the electronic device;
The visual indication of the second usage metric measures the number of received notifications associated with the one or more second applications of the electronic device during the first predetermined time period. indicate, including the indicated number,
and
via one or more input devices while displaying the visual indication of the first metric of use and the visual indication of the second metric of use on the dashboard user interface. , receiving input corresponding to a request to display a visual indication of a third metric of use different from the first metric of use and the second metric of use;
updating the dashboard user interface to include the visual indication of the third usage metric in response to receiving the input;
A non-transitory computer-readable medium that causes the

Images