JP7556076B2 - User interface for controlling or presenting device usage on an electronic device - Patents.com - Google Patents

Description

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

In recent years, user interaction with electronic devices has increased significantly. These devices can be devices such as computers, tablet computers, televisions, multimedia devices, mobile devices, etc.

In some situations, a user may wish to view information regarding the user's use of such a device and/or wish to control the user's use of such a device. Enhancing these interactions improves the user's experience with the device and reduces user interaction time, which is particularly important when the input device is battery operated.

Some embodiments described in this disclosure are directed to one or more electronic devices that provide an indication of usage metrics for the device, and one or more operations that the electronic devices may optionally perform in connection with the above. Some embodiments described in this disclosure are directed to one or more electronic devices that set, configure, and/or enforce device usage limits, and one or more operations that the electronic devices may optionally perform in connection with the above. Some embodiments described in this disclosure are directed to one or more electronic devices that restrict access to certain applications for a certain period of time, and one or more operations that the electronic devices may optionally perform in connection with the above. Some embodiments described in this disclosure are directed to one or more electronic devices that inhibit auxiliary functions of certain applications when application usage limits or restriction criteria associated with those applications are reached, and one or more operations that the electronic devices may optionally perform in connection with the above. Some embodiments described in this disclosure are directed to one or more electronic devices that manage restriction settings with permission optionally provided by another electronic device, and one or more operations that the electronic devices may optionally perform in connection with the above. A full description of these embodiments is provided in the "Description of the Preferred Embodiments" section, and it should be understood that the above "Summary of the Invention" does not limit the scope of the present 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, in which like reference numerals refer to corresponding parts throughout:

FIG. 1 is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments.

FIG. 2 is a block diagram illustrating example components for event processing according to some embodiments.

FIG. 1 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 in accordance with some embodiments.

1 illustrates an exemplary user interface for a menu of applications on a portable multifunction device according to some embodiments.

1 illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from a display in accordance with some embodiments.

FIG. 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. 1 illustrates example components of a personal electronic device having a touch-sensitive display and intensity sensor in accordance with some embodiments. FIG. 1 illustrates example components of a personal electronic device having a touch-sensitive display and intensity sensor in accordance with some embodiments.

1 illustrates example components and a user interface of a personal electronic device according to some embodiments. 1 illustrates example components and a user interface of a personal electronic device according to some embodiments. 1 illustrates example components and a user interface of a personal electronic device according to some embodiments. 1 illustrates example components and a user interface of a personal electronic device according to some embodiments.

1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure. 1 illustrates an example method for an electronic device to provide an indication of usage metrics, according to some embodiments of the present disclosure.

1 is a flow diagram illustrating a method for presenting an indication of a usage metric according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for presenting an indication of a usage metric according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for presenting an indication of a usage metric according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for presenting an indication of a usage metric according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for presenting an indication of a usage metric according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for presenting an indication of a usage metric according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for presenting an indication of a usage metric according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for presenting an indication of a usage metric according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for presenting an indication of a usage metric according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for presenting an indication of a usage metric according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for presenting an indication of a usage metric according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for presenting an indication of a usage metric according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for presenting an indication of a usage metric according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for presenting an indication of a usage metric according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for presenting an indication of a usage metric according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for presenting an indication of a usage metric according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for presenting an indication of a usage metric according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for presenting an indication of a usage metric according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for presenting an indication of a usage metric according to some embodiments of the present disclosure.

1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure. 1 illustrates an example method by which usage limits may be set, configured, and/or enforced on an electronic device, according to some embodiments of the present disclosure.

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

1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure. 1 illustrates an example method by which an electronic device can restrict access to a particular application for a particular period of time, according to some embodiments of the present disclosure.

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

1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure. 1 illustrates an example method in which an electronic device throttles auxiliary features of certain applications upon reaching application usage limits associated with those applications, consistent with some embodiments of the present disclosure.

4 is a flow diagram illustrating a method for throttling auxiliary features of certain applications upon reaching application usage limits associated with those applications, according to some embodiments of the present disclosure. 4 is a flow diagram illustrating a method for throttling auxiliary features of certain applications upon reaching application usage limits associated with those applications, according to some embodiments of the present disclosure. 4 is a flow diagram illustrating a method for throttling auxiliary features of certain applications upon reaching application usage limits associated with those applications, according to some embodiments of the present disclosure. 4 is a flow diagram illustrating a method for throttling auxiliary features of certain applications upon reaching application usage limits associated with those applications, according to some embodiments of the present disclosure. 4 is a flow diagram illustrating a method for throttling auxiliary features of certain applications upon reaching application usage limits associated with those applications, according to some embodiments of the present disclosure. 4 is a flow diagram illustrating a method for throttling auxiliary features of certain applications upon reaching application usage limits associated with those applications, according to some embodiments of the present disclosure. 4 is a flow diagram illustrating a method for throttling auxiliary features of certain applications upon reaching application usage limits associated with those applications, according to some embodiments of the present disclosure. 4 is a flow diagram illustrating a method for throttling auxiliary features of certain applications upon reaching application usage limits associated with those applications, according to some embodiments of the present disclosure.

1 illustrates an example 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. 1 illustrates an example 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. 1 illustrates an example 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. 1 illustrates an example 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. 1 illustrates an example 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. 1 illustrates an example 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. 1 illustrates an example 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. 1 illustrates an example 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. 1 illustrates an example 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. 1 illustrates an example 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. 1 illustrates an example 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. 1 illustrates an example 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. 1 illustrates an example 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. 1 illustrates an example 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. 1 illustrates an example 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. 1 illustrates an example 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. 1 illustrates an example 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. 1 illustrates an example 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. 1 illustrates an example 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. 1 illustrates an example 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.

1 is a flow diagram illustrating a method for managing restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for managing restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for managing restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for managing restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for managing restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for managing restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure. 1 is a flow diagram illustrating a method for managing restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure.

In the following description, example methods, parameters, and the like are described. However, it should be understood that the purpose of such description is not to limit the scope of the present disclosure, but to provide a description of example embodiments.

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

In the following description, terms such as "first" and "second" are used to describe various elements, but these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first touch can be referred to as a second touch, and similarly, a second touch can be referred to as a first touch, without departing from the scope of the various embodiments described. A first touch and a second touch are both touches, but are not the same touch.

The terms used in the description of the various embodiments described herein are for the purpose of describing particular embodiments only and are 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" are intended to include the plural forms as well, unless the context clearly indicates otherwise. As used herein, the term "and/or" is also understood to refer to and include any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "includes", "including", "comprises" and/or "comprising", as used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

Optionally, the term "if" is interpreted to mean "when," "upon," "in response to determining," or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if (a stated condition or event) is detected" are, optionally, interpreted to mean "upon determining," "in response to determining," "upon detecting (the stated condition or event)," or "in response to detecting (the stated condition or event)," depending on the context.

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

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

The device typically supports a variety of applications, such as one or more of the following: drawing applications, presentation applications, word processing applications, website creation applications, disc authoring applications, spreadsheet applications, gaming applications, telephony applications, video conferencing applications, email applications, instant messaging applications, training support applications, photo management applications, digital camera applications, digital video camera applications, web browsing applications, digital music player applications, and/or digital video player applications.

The various applications executing on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more features of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and/or changed for each application and/or within each application. In this manner, 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 an embodiment of a portable device with a touch-sensitive display. FIG. 1A is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112, according to some embodiments. The touch-sensitive display 112 may be conveniently referred to as a "touch screen" and may also be known or referred to as a "touch-sensitive display system." The device 100 includes memory 102 (optionally including one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripherals interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input/output (I/O) subsystem 106, other input control devices 116, and an external port 124. The device 100 optionally includes one or more light sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating a tactile output on device 100 (e.g., generating a tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

As used herein and in the claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., finger contact) on the touch-sensitive surface, or a surrogate (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a value range that includes at least four different values, and more typically includes hundreds (e.g., at least 256) different values. The intensity of a 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 the force at various points on the touch-sensitive surface. In some implementations, the force measurements from multiple force sensors are combined (e.g., weighted average) to determine an estimate of the force of the contact. Similarly, a pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and/or change in a contact area detected on the touch-sensitive surface, the capacitance and/or change in the capacitance of the touch-sensitive surface proximate the contact, and/or the resistance and/or change in the capacitance of the touch-sensitive surface proximate the contact, are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measure for the force or pressure of the contact is used directly to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measure). In some implementations, the surrogate measure for the force or pressure of the contact is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of contact as an attribute of user input allows a user access to additional device functionality that may not otherwise be accessible by the user on a reduced-size device with limited area for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical/mechanical controls such as knobs or buttons).

As used herein and in the claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, that is to be detected by a user with the user's sense of touch. For example, in a situation where a device or a component of the device is in contact with a touch-sensitive user surface (e.g., the fingers, palm, or other part of the user's hand), the tactile output generated by the physical displacement is interpreted by the user as a tactile sensation corresponding to a perceived change in the physical properties of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "down-click" or "up-click" of a physical actuator button. In some cases, the user feels a tactile sensation such as a "down-click" or "up-click" even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's action. As another example, movement of the touch-sensitive surface is optionally interpreted or sensed by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. Such user interpretation of touch depends on the user's personal sensory perception, but there are many sensory perceptions of touch that are common to a majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "up click," "down click," "roughness"), unless otherwise noted, the generated tactile output corresponds to a physical displacement of the device, or a component of the device, that produces the described sensory perception for a typical (or average) user.

It should be understood that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than those shown, optionally combines two or more components, or optionally has a different configuration or arrangement of components. 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 includes 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.

A peripheral interface 118 can be used to connect input and output peripherals of the device to the CPU 120 and memory 102. The one or more processors 120 operate or execute various software programs and/or instruction sets stored in the memory 102 to perform various functions for the device 100 and to process data. In some embodiments, the peripheral interface 118, the CPU 120, and the memory controller 122 are optionally implemented on a single chip, such as the chip 104. In some other embodiments, they are optionally implemented on separate chips.

The radio frequency (RF) circuitry 108 transmits and receives RF signals, also referred to as electromagnetic signals. The RF circuitry 108 converts electrical signals to electromagnetic signals or electromagnetic signals to electrical signals and communicates with communication networks and other communication devices via electromagnetic signals. The RF circuitry 108 optionally includes well-known circuits for performing their functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, and memory. The RF circuitry 108 optionally communicates with other devices via wireless communication, such as networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet, and/or wireless networks, such as cellular telephone networks, wireless local area networks (LANs) and/or metropolitan area networks (MANs). RF circuitry 108 optionally includes well-known circuitry for detecting a near field communication (NFC) field, such as by near field communication radio. The wireless communication optionally uses any of a number of communication standards, protocols, and technologies, including Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (T ... 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 (XMPP), Session Initiation Protocol for Instant Messaging and Presence Extensions, and/or Session Initiation Protocol for Instant Messaging and Presence Extensions). Examples of suitable communication protocols include, but are not limited to, SIMPLE, 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 communication protocols not yet developed as of the filing date of this document.

The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between the user and the device 100. The audio circuit 110 receives audio data from the peripherals interface 118, converts the audio data into an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal into human audible sound waves. The audio circuit 110 also receives an electrical signal converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signal into audio data and transmits the audio data to the peripherals interface 118 for processing. The audio data is optionally retrieved from and/or transmitted to the memory 102 and/or the RF circuit 108 by the peripherals interface 118. In some embodiments, the audio circuit 110 further comprises a headset jack (e.g., 212 in FIG. 2). The headset jack provides an interface between the audio circuitry 110 and a removable audio input/output peripheral, such as an output-only headphone or a headset that has both an output (e.g., a single-ear or binaural headphone) and an input (e.g., a microphone).

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

Optionally, a quick press of a push button unlocks the touch screen 112 or optionally initiates a process of using gestures on the touch screen to unlock the device, as described in U.S. Patent Application Serial No. 11/322,549, "Unlocking a Device by Performing Gestures on an Unlock Image," U.S. Patent No. 7,657,849, filed December 23, 2005, which is incorporated by reference in its entirety. A longer press of a push button (e.g., 206) optionally powers the device 100 on or off. The functionality of one or more of the buttons is optionally user customizable. The touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

The touch-sensitive display 112 provides an input and output interface between the device and a user. The display controller 156 receives and/or transmits electrical signals to the touch screen 112. The touch screen 112 displays visual output to the user. The 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.

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

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

The touch-sensitive display in some embodiments of touchscreen 112 is optionally similar to the multi-touch sensing touchpad described in the following U.S. Patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and/or 6,677,932 (Westerman), and/or U.S. Patent Application Publication No. 2002/0015024 (A1), each of which is incorporated by reference in its entirety herein. However, touchscreen 112 displays visual output from device 100, whereas touch-sensitive touchpads do 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 No. 11/381,313, filed May 2, 2006, entitled "Multipoint Touch Surface Controller"; (2) U.S. Patent Application No. 10/840,862, filed May 6, 2004, entitled "Multipoint Touchscreen"; (3) U.S. Patent Application No. 10/903,964, filed July 30, 2004, entitled "Gestures For Touch Sensitive Input Devices"; (4) U.S. Patent Application No. 11/048,264, filed January 31, 2005, entitled "Gestures For Touch Sensitive Input Devices"; "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices", (5) U.S. Patent No. 11/038,590, filed January 18, 2005, "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices", (6) U.S. Patent No. 11/228,758, filed September 16, 2005, "Virtual Input Device Placement On A Touch Screen User Interface", (7) U.S. Patent No. 11/228,700, filed September 16, 2005, "Operation Of A Computer With A Touch Screen (8) U.S. Patent No. 11/228,737, filed September 16, 2005, entitled "Activating Virtual Keys Of A Touch-Screen Virtual Keyboard," and (9) U.S. Patent No. 11/367,749, filed March 3, 2006, entitled "Multi-Functional Hand-Held Device." All of these applications are incorporated herein by reference in their entirety.

Touchscreen 112 optionally has a video resolution of greater than 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. A user optionally contacts touchscreen 112 using any suitable object or appendage, such as a stylus, finger, etc. In some embodiments, the user interface is designed to function primarily through finger-based contact and gestures, which may be less precise than stylus-based input due to the large contact area of a finger on the touchscreen. In some embodiments, the device translates coarse finger-based input into precise pointer/cursor position or commands to perform the user's desired action.

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, the touchpad is a touch-sensitive area of the device that, unlike the touchscreen, does not display visual output. The touchpad is optionally a touch-sensitive surface separate from touchscreen 112 or an extension of the touch-sensitive surface formed by the touchscreen.

The device 100 also includes a power system 162 for providing power to the various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power outage detection circuit, a power converter or inverter, a power status indicator (e.g., a light emitting diode (LED)), and any other components associated with the generation, management, and distribution of power within the portable device.

Optionally, device 100 also includes one or more light sensors 164. FIG. 1A shows a light sensor connected to light sensor controller 158 in I/O subsystem 106. Light sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) phototransistor. Light 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), light sensor 164 optionally captures still images or video. In some embodiments, the light sensor is located on the back of device 100, opposite touchscreen display 112 on the front of the device, to enable the touchscreen display as a viewfinder for still image and/or video capture. In some embodiments, the light sensor is optionally located on the front of the device to obtain an image of the user for videoconference at the same time the user sees other videoconference participants on the touchscreen display. In some embodiments, the position of the light sensor 164 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), thereby using a single light sensor 164 in conjunction with a touch screen display for both video conferencing and still and/or video image capture.

Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I/O subsystem 106. Contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor 165 receives contact intensity information (e.g., 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 proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touch screen display 112 located on the front of device 100.

Device 100 also optionally includes one or more proximity sensors 166. FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternatively, proximity sensor 166 is optionally connected to input controller 160 in I/O subsystem 106. The proximity sensor 166 may optionally be a sensor that is adapted to detect a range of motions, such as those described in U.S. patent application Ser. No. 11/241,839, entitled "Proximity Detector In Handheld Device," Ser. No. 11/240,788, entitled "Proximity Detector In Handheld Device," Ser. No. 11/620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output," and Ser. No. 11/586,862, entitled "Automated Response To And Sensing Of User Activity In Portable No. 11/638,251, "Methods And Systems For Automatic Configuration Of Peripherals," which applications are incorporated herein by reference in their entireties. In some embodiments, the proximity sensor turns off and disables the touch screen 112 when the multifunction device is placed near the user's ear (e.g., 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 in I/O subsystem 106. Tactile output generator 167 optionally includes one or more electroacoustic devices, such as speakers or other audio components, and/or electromechanical devices that convert energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile output on the device). Contact intensity sensor 165 receives tactile feedback generation commands 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 disposed on or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112) and optionally generates a tactile output by moving the touch-sensitive surface vertically (e.g., in/out of the surface of device 100) or laterally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is disposed on the back of device 100, opposite touchscreen display 112 disposed 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 in I/O subsystem 106. The accelerometer 168 optionally functions as described in U.S. Patent Application Publication Nos. 20050190059, "Acceleration-based Theft Detection System for Portable Electronic Devices," and 20060017692, "Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer," both of which are incorporated by reference herein in their entireties. In some embodiments, information is displayed on the touchscreen display in portrait or landscape orientation based on analysis of data received from one or more accelerometers. In addition to the accelerometer(s) 168, the device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information regarding the location and orientation (e.g., portrait or landscape) of the device 100.

In some embodiments, the software components stored in memory 102 include an operating system 126, a communications module (or instruction set) 128, a touch/motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a Global Positioning System (GPS) module (or instruction set) 135, and applications (or instruction sets) 136. Additionally, in some embodiments, as shown in FIGS. 1A and 3, memory 102 (FIG. 1A) or memory 370 (FIG. 3) stores device/global internal state 157. Device/global internal state 157 includes one or more of the following: active application state, indicating which applications, if any, are currently active; display state, indicating which applications, views, or other information are occupying various regions of touchscreen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and location information regarding the device's position and/or orientation.

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

The communications module 128 also includes various software components for facilitating communication with other devices via one or more external ports 124 and for processing data received by the RF circuitry 108 and/or the external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) are adapted to couple to other devices directly or indirectly through a network (e.g., Internet, wireless LAN, etc.). In some embodiments, the external ports are multi-pin (e.g., 30-pin) connectors the same as or similar to the 30-pin connector used on iPod (trademark of Apple Inc.) devices and/or compatible multi-pin (e.g., 30-pin) connectors.

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

In some embodiments, the contact/motion module 130 uses a set of one or more intensity thresholds for determining whether an action has been performed by the user (e.g., for determining whether the user has "clicked" on an icon). 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 thresholds of a particular physical actuator and may be adjusted without modifying the physical hardware of the device 100). 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, a user of the device is provided with a software setting to adjust 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 a system-level click "intensity" parameter).

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

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

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

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

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

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

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

In conjunction with the touch screen 112, the display controller 156, the contact/motion module 130, the graphics module 132, and the text input module 134, the contacts module 137 is optionally used to manage an address book or contact list (e.g., stored in the memory 102 or in the application internal state 192 of the contacts module 137 in the memory 370), including adding a name(s) to the address book, deleting a name(s) from the address book, associating a phone number(s), email address(es), address(es), or other information with a name, associating an image with a name, categorizing and sorting names, providing phone numbers or email addresses to initiate and/or facilitate communication by telephone 138, videoconferencing module 139, email 140, or IM 141, and the like.

In conjunction with the RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the telephone module 138 is optionally used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in the contact module 137, modify an entered telephone number, dial a corresponding telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As described above, the wireless communication optionally uses any of a number of communication standards, protocols, and technologies.

In conjunction with the RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, light sensor 164, light sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, the videoconferencing module 139 contains executable instructions for initiating, conducting, and terminating a videoconference between a user and one or more other participants in accordance with the user's instructions.

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

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

In conjunction with the RF circuitry 108, touch screen 112, display controller 156, contact/action module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, the training support module 142 includes executable instructions to generate workouts (e.g., having time, distance, and/or calorie burn goals), communicate with training sensors (sports devices), receive training sensor data, calibrate sensors used to monitor the workouts, select and play music for the workouts, and display, store, and transmit the workout data.

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

In conjunction with the touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 contains executable instructions for arranging, modifying (e.g., editing) or otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slide show or album), and storing still and/or video images.

In conjunction with the RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the browser module 147 contains executable instructions for browsing the Internet at the direction of a user, including retrieving, linking, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

In conjunction with the RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, the calendar module 148 contains executable instructions to create, display, modify, and store calendars and data associated with the calendars (e.g., calendar items, to-do lists, etc.) in accordance with user instructions.

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

In conjunction with the RF circuitry 108, the touch screen 112, the display controller 156, the contact/motion module 130, the graphics module 132, the text input module 134, and the browser module 147, the widget creation module 150 is optionally used by a user to create a widget (e.g., turn a user-specified portion of a web page into a widget).

In cooperation with the touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the search module 151 contains executable instructions for searching the memory 102 for text, music, sound, images, video, and/or other files matching one or more search criteria (e.g., one or more user-specified search terms) in accordance with a user's instructions.

In conjunction with the touch screen 112, the display controller 156, the contact/motion module 130, the graphics module 132, the audio circuitry 110, the speaker 111, the RF circuitry 108, and the browser module 147, the video and music player module 152 includes executable instructions that allow a user to download and play pre-recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, as well as executable instructions for displaying, presenting, or otherwise playing videos (on the touch screen 112 or on an external display connected via the external port 124). In some embodiments, the device 100 optionally includes the functionality of an MP3 player, such as an iPod (a trademark of Apple Inc.).

In conjunction with the touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the notes module 153 contains executable instructions for creating and managing notes, to-do lists, and the like, as directed by the user.

In conjunction with the RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, the map module 154 is optionally used to receive, display, modify, and store maps and data associated with the maps (e.g., driving directions, data for stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.

In conjunction with the touch screen 112, the display controller 156, the contact/motion module 130, the graphics module 132, the audio circuitry 110, the speaker 111, the RF circuitry 108, the text input module 134, the email client module 140, and the browser module 147, the online video module 155 contains instructions that enable the user to access, view, receive (e.g., by streaming and/or downloading), play (e.g., on the touch screen or on an external display connected via the external port 124), and send and otherwise manage emails containing links to particular online videos in one or more file formats, such as H.264. In some embodiments, the instant messaging module 141 is used to send links to particular online videos, rather than the email client module 140. Further description of online video applications can be found in U.S. Provisional Patent Application No. 60/936,562, entitled "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," filed June 20, 2007, and U.S. Patent Application No. 11/968,067, entitled "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," filed December 31, 2007, the contents of which are incorporated herein by reference in their entireties.

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

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

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

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

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

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

Event monitor 171 receives event information from peripherals interface 118. The event information includes information of a sub-event (e.g., 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 a request to peripherals interface 118 at a predetermined interval. In response, peripherals interface 118 sends event information. In other embodiments, peripherals interface 118 sends event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for longer than a predetermined period of time).

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

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

Another aspect of a 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 in which touch-based gestures occur. The application views (of each application) in which the touch is detected optionally correspond to program levels within the programmatic or view hierarchy of the application. For example, the lowest-level view in which the touch is detected is optionally referred to as a hit view, and the set of events that are recognized as suitable inputs are optionally determined based at least in part on the hit view of the initial touch that initiates the touch-based gesture.

Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should process the sub-events. In most situations, the hit view is the lowest level view in which the first sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.

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

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

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

In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each including instructions for handling touch events occurring within a respective view of the application's user interface. 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 the event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher-level object from which application 136-1 inherits methods and other properties. In some embodiments, each event handler 190 includes one or more of data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more corresponding event handlers 190. Also, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in each application view 191.

Each event recognizer 180 receives event information (e.g., event data 179) from the event sorter 170 and identifies an event from the event information. The event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, the event recognizer 180 also includes at least 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 a sub-event, e.g., a touch or a movement of a touch. Depending on the sub-event, the event information also includes additional information, such as the position of the sub-event. When the sub-event involves a movement of a touch, the event information also optionally includes the speed and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from portrait to landscape or vice versa), and the event information includes corresponding information about the current orientation of the device (also called the device's attitude).

The event comparator 184 compares the event information to predefined event or sub-event definitions and determines the event or sub-event, or determines or updates the state of the event or sub-event, based on the comparison. In some embodiments, the event comparator 184 includes an event definition 186. The event definition 186 includes an event definition (e.g., a predefined set of sub-events), such as, for example, event 1 (187-1), event 2 (187-2), etc. In some embodiments, the sub-events in event 187 include, for example, touch start, touch end, touch movement, touch stop, and multiple touches. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap includes, for example, a first touch on a displayed object during a predetermined phase (touch start), a first lift-off during a predetermined phase (touch end), a second touch on a displayed object during a predetermined phase (touch start), and a second lift-off during a predetermined phase (touch end). In another example, a definition of event 2 (187-2) is a drag operation on a displayed object. The drag operation includes, for example, a touch (or contact) on a displayed object for a given stage, a movement of the touch across the touch-sensitive display 112, and a lift-off of the touch (end of the touch). In some embodiments, the event also includes information regarding one or more associated event handlers 190.

In some embodiments, event definition 187 includes a definition of the event for each user interface object. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, in an application view 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 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, event comparator 184 uses the results of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects the event handler associated with the sub-event and the object that triggers the hit test.

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

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 disabled, event failed, or event finished state and thereafter ignores the next sub-event of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

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

In some embodiments, each event recognizer 180 activates an event handler 190 associated with an 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 handler 190. Activating the event handler 190 is distinct from sending (and postponing sending) the sub-events to the respective 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, the event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver the event information to an event handler associated with the set of sub-events or an actively participating view. The event handler associated with the set of sub-events or an actively participating view receives the event information and performs a predetermined process.

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

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

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

FIG. 2 illustrates a portable multifunction device 100 having a touch screen 112, according to some embodiments. The touch screen optionally displays one or more graphics in a user interface (UI) 200. In this embodiment, as well as embodiments described below, a user can select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale) or one or more styluses 203 (not drawn to scale). In some embodiments, selection of the one or more graphics occurs when the user loses contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, upward and/or downward), and/or rolling of a finger in contact with the device 100 (right to left, left to right, upward and/or downward). In some implementations or situations, accidental contact with a graphic does not select the graphic. For example, a swipe gesture sweeping over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

The device 100 also optionally includes one or more physical buttons, such as a "home" or menu button 204. As previously mentioned, the menu button 204 is optionally used for navigation to any application 136 in a set of applications that optionally execute on the device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touch screen 112.

In some embodiments, device 100 includes a touch screen 112, a menu button 204, a push button 206 for turning power on/off and locking the device, a volume control button(s) 208, a subscriber identity module (SIM) card slot 210, a headset jack 212, and an external port 124 for docking/charging. Push button 206 is optionally used to turn power on/off on the device by pressing and holding the button down for a predefined time interval, to lock the device by pressing and releasing the button before the predefined time interval has elapsed, and/or to unlock the device or initiate an unlocking process. In an alternative embodiment, device 100 also receives verbal input through microphone 113 to activate or deactivate some functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on touch screen 112 and/or one or more tactile output generators 167 for generating a tactile output for a user of device 100.

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

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

Attention is now directed to, for example, an embodiment of a user interface that optionally executes on the portable multifunction device 100.

4A shows an exemplary user interface for a menu of applications on portable multifunction device 100, according to some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:
signal strength indicator(s) 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:
○ An icon 416 for the phone module 138, labeled "Phone", optionally including an indicator 414 of the number of missed calls or voicemail messages;
○ An icon 418 for the email client module 140, labeled "Mail", optionally including an indicator 410 of the number of unread emails;
○ An icon 420 for the browser module 147, labeled "Browser", and ○ An icon 422 for the video and music player module 152, also referred to as the iPod (trademark of Apple Inc.) module 152, labeled "iPod", and ● Icons for other applications, such as:
○ An icon 424 for the IM module 141, labeled "Messages";
○ An icon 426 for the calendar module 148, labeled "Calendar";
○ An icon 428 for the image management module 144, labeled "Photos";
○ An icon 430 for the camera module 143, labeled "Camera",
○ An icon 432 for the online video module 155, labeled "Online Video";
○ An icon 434 for stock price widget 149-2, labeled "Stock Price";
○ An icon 436 for the map module 154, labeled "Map";
○ An icon 438 for the weather widget 149-1, labeled "Weather";
○ An icon 440 for the alarm clock widget 149-4, labeled "Clock",
○ An icon 442 for the training support module 142, labeled "Training Support";
o An icon 444 for a notes module 153, labeled "Notes," and o An icon 446 for a settings application or module, labeled "Settings," which provides access to settings related to the device 100 and its various applications 136.

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 the various application icons. In some embodiments, the label for each application icon includes the name of the application that corresponds to the respective application icon. In some embodiments, the label for a particular application icon is different from the name of the application that corresponds to the particular application icon.

4B illustrates an exemplary user interface on a device (e.g., device 300 of FIG. 3) that includes a touch-sensitive surface 451 (e.g., tablet or touchpad 355 of FIG. 3) that is separate from a display 450 (e.g., touchscreen display 112). Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting the intensity of a contact on touch-sensitive surface 451 and/or one or more tactile output generators 357 for generating a tactile output for a user of device 300.

Although some of the following examples are described with reference to input on 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 that is separate from the display, as shown in FIG. 4B. In some embodiments, this touch-sensitive surface (e.g., 451 in FIG. 4B) has a major axis (e.g., 452 in FIG. 4B) that corresponds to a major axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). According to these embodiments, the device detects contact with touch-sensitive surface 451 (e.g., 460 and 462 in FIG. 4B) at locations that correspond to their respective locations on the display (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In this manner, when the touch-sensitive surface is separate from the display, user input (e.g., contacts 460 and 462 and their movement) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B ) is used by the device to operate a user interface on the display (e.g., 450 in FIG. 4B ) of the multifunction device. It should be understood that similar methods are optionally used for the other user interfaces described herein.

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

5A illustrates an exemplary personal electronic device 500. Device 500 includes a body 502. In some embodiments, device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1A-4B). In some embodiments, device 500 has a touch-sensitive display screen 504, hereafter touch screen 504. Instead of, or in addition to, touch screen 504, device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, touch screen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors for detecting the intensity of a contact (e.g., a touch) being applied. The one or more intensity sensors of touch screen 504 (or touch-sensitive surface) can provide output data representative of the intensity of the touch. A user interface of device 500 can respond to a touch based on the intensity of the touch, meaning that touches of different intensities can invoke different user interface actions on device 500.

Exemplary techniques for detecting and processing touch intensity are described, for example, in related applications, International Patent Application No. PCT/US2013/040061, entitled "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application," filed May 8, 2013 (published as WO 2013/169849), and "Device, Method, and Graphical User Interface for Transitioning Between Touch Input to No. PCT/US2013/069483 (published as WO 2014/105276), entitled "Display Output Relationships," each of which is incorporated herein 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, can 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 allow device 500 to be attached to, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch bands, chains, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow device 500 to be worn by a user.

5B illustrates an exemplary personal electronic device 500. In some embodiments, the device 500 can include some or all of the components described with respect to FIGS. 1A, 1B, and 3. The device 500 has a bus 512 operably coupling an I/O unit 514 to one or more computer processors 516 and a memory 518. The I/O unit 514 can be connected to a display 504, which can have a touch-sensing component 522 and, optionally, an intensity sensor 524 (e.g., a contact intensity sensor). Additionally, the I/O unit 514 can connect to 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. The device 500 can include an input mechanism 506 and/or an input mechanism 508. The 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 embodiments.

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

The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by one or more computer processors 516, may cause the computer processors to perform the techniques described below, including processes 700, 900, 1100, and 1300 (FIGS. 7, 9, 11, and 13). A computer-readable storage medium may be any medium that can tangibly contain or store 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 transient computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media may include, but are not limited to, magnetic storage devices, optical storage devices, and/or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CDs, DVDs, or Blu-ray technology, and persistent solid-state memory such as flash, solid-state drives, and the like. The personal electronic device 500 is not limited to the components and configuration of FIG. 5B and may include other or additional components in multiple configurations.

As used herein, the term "affordance" refers to a user-interactive graphical user interface object that is optionally displayed on a display screen of device 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) each, optionally, constitute an affordance.

As used herein, the term "focus selector" refers to an input element that indicates the current portion of a user interface with which a user is interacting. In some implementations involving a cursor or other position marker, when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 of FIG. 3 or touch-sensitive surface 451 of FIG. 4B), when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the cursor acts as a "focus selector" and the particular user interface element is adjusted according to the detected input. In some implementations including a touchscreen display (e.g., touch-sensitive display system 112 in FIG. 1A or touchscreen 112 in FIG. 4A ) that allows direct interaction with user interface elements on the touchscreen display, contact detected on the touchscreen acts as a “focus selector” such that when input (e.g., a touch press input) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, the particular user interface element is adjusted according to the detected input. In some implementations, focus is moved from one region of the user interface to another region of the user interface (e.g., by using tab or arrow keys to move focus from one button to another) without corresponding cursor movement or contact movement on the touchscreen display, and in those implementations the focus selector moves in accordance with the movement of focus between different regions of the user interface. Regardless of the specific form taken by the focus selector, the focus selector is generally a user interface element (or a contact on a touch screen display) that is controlled by a user to communicate the user's intended interaction with the user interface (e.g., by indicating to the device which element of the user interface the user intends to interact with). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touch screen), the position of the focus selector (e.g., a cursor, contact, or selection box) over a corresponding button indicates that the user intends to activate the corresponding button (rather than another user interface element shown on the device's display).

As used herein and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected during a predefined period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) for a predefined event (e.g., after detecting the 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 the contact, and/or before or after detecting a decrease in the intensity of the contact). The characteristic intensity of the contact is optionally based on one or more of the following: a maximum value of the intensity of the contact, a mean value of the intensity of the contact, an average value of the intensity of the contact, the top 10% values of the intensity of the contact, a half value of the maximum value of the intensity of the contact, a 90% value of the maximum value of the intensity of the contact, etc. In some embodiments, the duration of the contact is used to determine the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action is 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, a contact having a characteristic intensity that does not exceed the first threshold results in a first action being performed, a contact having a characteristic intensity that exceeds the first intensity threshold but does not exceed the second intensity threshold results in a second action being performed, and a contact having a characteristic intensity that exceeds the second threshold results in a third action being performed. In some embodiments, the comparison between the characteristic intensity and the one or more thresholds is used to determine whether to perform one or more actions (e.g., to perform each action or to forgo performing each action), rather than to determine whether to perform the first action or the second action.

5C illustrates the detection of multiple contacts 552A-552E on the touch-sensitive display screen 504 by multiple intensity sensors 524A-524D. FIG. 5C additionally includes an intensity diagram illustrating the 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 the 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 portion of the total intensity. FIG. 5D illustrates the assignment of the total intensity to contacts 552A-552E based on the distance of contacts 552A-552E from the center of force 554. In this example, each of contacts 552A, 552B, and 552E is assigned a contact intensity of 8 intensity units of the total intensity, and each of contacts 552C and 552D is assigned a contact intensity of 4 intensity units of the total intensity. More generally, in some implementations, each contact j is assigned a respective intensity Ij that is a portion 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 the respective contact j, and ΣDi is the sum of the distances from the center of force to all respective contacts (e.g., from i=1 to the end). The operations described with reference to Figures 5C-5D can be performed using electronic devices similar or identical to device 100, 300, or 500. In some embodiments, the characteristic intensity of a contact is based on one or more intensities of the contact. In some embodiments, an intensity sensor is used to determine a single characteristic intensity (e.g., a single characteristic intensity of a single contact). Note that the intensity plots are not part of the displayed user interface, but are included in Figures 5C-5D for the reader's convenience.

In some embodiments, a portion of the gesture is identified for purposes of determining the characteristic intensity. For example, the touch-sensitive surface optionally receives successive swipe contacts that transition from a start position to an end position, where the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end position is optionally based on only a portion of the swipe contact (e.g., only the portion of the swipe contact at the end position) rather than the entire successive swipe contact. In some embodiments, a smoothing algorithm is optionally applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of an unweighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, the smoothing algorithms remove small increases or decreases in the intensity of the swipe contact for purposes of determining the characteristic intensity.

The intensity of the contact on the touch-sensitive surface is optionally characterized against one or more intensity thresholds, such as a contact-detection intensity threshold, a light pressure intensity threshold, a deep pressure intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light pressure intensity threshold corresponds to an intensity at which the device performs an operation typically associated with clicking a physical mouse button or trackpad. In some embodiments, the deep pressure intensity threshold corresponds to an intensity at which the device performs an operation different from the operation typically associated with clicking a physical mouse button or trackpad. In some embodiments, if the contact is detected with a characteristic intensity below the light pressure intensity threshold (e.g., and above a slight contact-detection intensity threshold below which the contact is no longer detected), the device moves a focus selector in accordance with the movement of the contact on the touch-sensitive surface without performing an action associated with the light pressure intensity threshold or the deep pressure intensity threshold. Generally, unless otherwise specified, these intensity thresholds are consistent across different sets of user interface diagrams.

An increase in 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 press" input. An increase in the characteristic intensity of a contact from an intensity below the deep pressure intensity threshold to an intensity above the deep pressure intensity threshold may be referred to as a "deep press" input. An increase in the characteristic intensity of a contact from an intensity below the contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light pressure intensity threshold may be referred to as detection of a contact on the touch surface. A decrease in the characteristic intensity of a contact from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold may be referred to as detection of a lift-off of the contact from the touch surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.

In some embodiments described herein, one or more operations are performed in response to detecting a gesture including a respective press input or in response to detecting a respective press input performed with a respective contact (or multiple contacts), where the respective press input is detected based at least in part on detecting an increase in the intensity of the contact (or multiple contacts) above a press input intensity threshold. In some embodiments, the respective action is performed in response to detecting an increase in the intensity of the respective contact (e.g., a "downstroke" of the respective press input) above the press input intensity threshold. In some embodiments, the press input includes an increase in the intensity of the respective contact above the press input intensity threshold and a subsequent decrease in the intensity of the contact below the press input intensity threshold, where the respective action is performed in response to detecting a subsequent decrease in the intensity of the respective contact below the press input intensity threshold (e.g., an "upstroke" of the respective press input).

5E-5H illustrate detection of a gesture including a press input corresponding to an increase in intensity of contact 562 from an intensity below a light pressure intensity threshold (e.g., "IT _L ") in FIG. 5E to an intensity above a deep pressure intensity threshold (e.g., "IT _D ") in FIG. 5H. The gesture made by contact 562 is detected on touch-sensitive surface 560. In doing so, cursor 576 is displayed over application icon 572B corresponding to app2 on displayed user interface 570, which includes application icons 572A-572D displayed in predetermined area 574. In some embodiments, the gesture is detected on touch-sensitive display 504. An intensity sensor detects the intensity of the contact on touch-sensitive surface 560. The device determines that the intensity of contact 562 has peaked above the deep pressure intensity threshold (e.g., "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 (e.g., "IT _D ") during the gesture, display reduced representations 578A-578C (e.g., thumbnails) of recently opened documents for app2, as shown in Figures 5F-5H. In some embodiments, the intensity that is compared to one or more intensity thresholds is a 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 Figures 5E-5H for the reader's benefit.

In some embodiments, the display of representations 578A-578C includes an animation. For example, representation 578A is initially displayed near application icon 572B, as shown in FIG. 5F. As the animation progresses, representation 578A moves up and representation 578B is displayed near application icon 572B, as shown in FIG. 5G. Representation 578A then moves up and representation 578B moves up 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 as a function of the intensity of contact 562, as shown in FIG. 5F-5G, where representations 578A-578C appear and move upward as the intensity of contact 562 increases toward a deep pressure intensity threshold (e.g., "ITD"). In some embodiments, the intensity on which the animation progression is based is a characteristic intensity of the contact. The operations described with reference to Figures 5E-5H can be performed using an electronic device similar to or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoid accidental inputs, sometimes referred to as "jitter," and the device defines or selects a hysteresis intensity threshold that has a predefined relationship to the pressure input intensity 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 percentage of the pressure input intensity threshold). Thus, in some embodiments, the pressure input includes an increase in the intensity of a corresponding contact above the pressure input intensity threshold and a subsequent decrease in the intensity of the contact below a hysteresis intensity threshold that corresponds to the pressure input intensity threshold, and a corresponding action is taken in response to detecting a subsequent decrease in the intensity of the corresponding contact below the hysteresis intensity threshold (e.g., an "upstroke" of the corresponding pressure input). Similarly, in some embodiments, a pressure input is detected only when the device detects an increase in the intensity of the contact from an intensity below the hysteresis intensity threshold to an intensity above the pressure input intensity threshold, and optionally a subsequent decrease in the intensity of the contact to an intensity below the hysteresis intensity, and a corresponding action is performed in response to detection of the pressure input (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact, as the case may be).

For ease of explanation, the description of an action performed in response to a press input associated with a press input intensity threshold or in response to a gesture including the press input is optionally triggered in response to detecting any of an increase in the intensity of the contact above the press input intensity threshold, an increase in the intensity of the contact from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, a decrease in the intensity of the contact below the press input intensity threshold, and/or a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the press input intensity threshold. Additionally, in an embodiment where an action is described as being performed in response to detecting a decrease in the intensity of the contact below a press input intensity threshold, the action is optionally performed in response to detecting a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to and lower than the press input intensity threshold.

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

As used herein, the terms "open application" or "running application" refer to a software application for which state information is maintained (e.g., as part of device/global internal state 157 and/or application internal state 192). An open or running application is, optionally, any one of the following types of applications:
● The active application currently displayed on the display screen of the device on which the application is being used;
- Background applications (or background processes), which are not currently displayed but one or more processes related to the application are being processed by one or more processors; and - Suspended or hibernated applications, which are not running but have state information stored in memory (volatile and non-volatile, respectively) that can be used to resume execution of the application.

As used herein, the term "closed application" refers to a software application for which no state information is maintained (e.g., no state information for the closed application is stored in the device's memory). Thus, closing an application includes stopping and/or removing the application process for that application, as well as removing state information for that application from the device's memory. Generally, opening a second application during a first application does not close the first application. Once the second application is displayed and the first application is no longer displayed, the first application becomes a background application.

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

A user interacts with an electronic device 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 an operation on the electronic device, thereby allowing the user to view information about the use of the electronic device. The embodiments described below provide a method for the electronic device to present an indication of usage metrics associated with use of the electronic device to perform one or more operations. Enhancing interaction with the device reduces the amount of time a user needs to perform an operation, thus reducing the power usage of the device and increasing battery life for battery-powered devices. It is understood that people use devices. When a person uses a device, the person is optionally referred to as a user of the device.

FIGS. 6A-6UU illustrate example ways in which an electronic device may provide an indication of usage metrics in accordance with 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. 7A-7S.

Figure 6A illustrates an exemplary device 500 having a touch screen 504 as described with reference to Figures 5A-5H. The touch screen 504 optionally displays one or more user interfaces including various content. In the example illustrated in Figure 6A, the touch screen 504 displays a limit setting user interface for viewing information about and setting limits on the use of the electronic device 500. In FIG. 6A , the limit settings user interface displays an indication 602 of device usage, as well as a number of settings related to device usage, such as settings for a limited usage mode (e.g., “Device Downtime” 604a), settings for usage limits for one or more applications or categories of applications (e.g., “App Limits” 604b), a setting where functionality is always allowed regardless of any usage restrictions currently in place (e.g., “Always Allowed” 604c), settings for content and privacy settings for the electronic device 500 (e.g., “Content & Privacy” 604d), settings for requiring a password to change usage settings (e.g., “Require Password to Change” 604e), settings for stopping recording which operations are being performed on the electronic device (e.g., “Stop Recording Usage Data” 604f), settings for deleting stored data related to use of the electronic device to perform various operations (e.g., “Delete Usage Data” 604g), and settings for signing into a cloud-based user account (e.g., “Sign in to iCloud” 604h). As shown, the device usage indication 602 includes a visual indication of the amount of time the electronic device has been used to access each of several applications or application categories (e.g., a news app, a games category, and a mail app). The indication 602 further includes an indication of how much of an overall "screentime" usage limit remains (e.g., "3 hours remaining"). Usage limits, including overall usage limits, are described in more detail below with reference to FIGS. 8A-9K. The electronic device 500 also displays an indication of total device usage (e.g., "4 hours of usage") and a comparison of the day's device usage to the average daily usage (e.g., "30 minutes below average").

6B illustrates a limit setting user interface when the electronic device 500 is signed into a cloud-based user account. The limit setting user interface includes an indication 606 of the nickname of the electronic device 500 associated with the user account, and an indication of devices associated with other users that are part of a group or family cloud-based account (e.g., John Jr.'s iPhone 608a and Jane's iPhone 608b). The family cloud-based account includes individual user accounts associated with other electronic devices (e.g., "John Jr.'s iPhone" and "Jane's iPhone"). In some embodiments, the family cloud-based account includes a "parent" user and a "child" user, where the parent user can view and/or control various statistics and/or settings associated with the child user. As shown here, and as described in more detail below with reference to FIGS. 6V-W, a parent device (e.g., such as the electronic device 500) can present usage information regarding one or more child devices. The parent device can further control the child device's usage limits and device downtime settings, as described below with reference to Figures 8A-11I. In Figures 6C-6D, the user scrolls (e.g., by contact 603) through the limit settings user interface to reveal 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), a "Stop recording usage data" setting 604f, and a "Delete usage data" setting 604g. The 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 Figures 6TT-6UU, electronic device 500 can display usage metrics associated with one or more of the associated devices, either separately or together.

6E illustrates a widget user interface that includes a usage widget 612a, a calendar widget 612b, and a weather widget 612c. The usage widget 612a includes device usage indications 602, including indications of usage for various applications and categories (e.g., news app, mail app, and games category), and selectable affordances 614 to display further usage information.

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

6J illustrates a usage notification 630 generated by the device 500 according to some embodiments of the present disclosure. In some embodiments, usage notifications such as notification 630 are generated by the electronic device 500 at regularly scheduled intervals (e.g., once per day, once per week, etc.). The usage notification includes an indication 602 of device usage, an option (e.g., "View" 632a) to view more information about the device usage (e.g., in a dashboard user interface), and an option (e.g., "Dismiss" 632b) to dismiss the notification without viewing more information about the device usage. In FIG. 6K, the user selects "View" 632a (e.g., by contact 603) to view more information about the device usage. In response, the 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. 6G, an indication 634 of the longest usage session on the device during the day, an indication 636 of the amount of device usage during a limited usage mode (e.g., "device downtime") during the day, and indications 622a and 622b of usage of applications and categories with usage limits set. The usage dashboard user interface further includes a toggle switch to view an indication of usage metrics 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. The indications 622a and 622b of usage of applications with usage limits are optionally visually associated with affordances 640a and 640b that are selectable to display a settings user interface to view information about the respective application or category and to update the usage limit settings for that application or category. For example, affordance 640a is selectable to edit the usage limit settings for a news application. As shown in FIG. 6L, when a usage limit is exceeded (e.g., usage limit 622a for the news app), the corresponding affordance 640a has a different color or pattern indicating that the usage limit has been exceeded. Similarly, in some embodiments, when a usage limit is close to being reached (e.g., within a threshold amount of time or percentage of time), the associated affordance has a visual characteristic. In addition, the bar graph indicating the usage limit includes different 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., as shown in both the news app indication 622a and the games category indication 622b), the amount of time the given application or category was used beyond the usage limit (e.g., as shown in the news app indication 622a), and the amount of time remaining in the usage limit for the application or category (e.g., as shown in the games category indication 622b).

6M-6N illustrate that the user may scroll (e.g., by contact 603) through the usage dashboard user interface to reveal indications of additional usage metrics, as shown in FIG. 6O. As shown, the usage dashboard user interface includes an indication 642 of usage for applications that do not have usage limits set (e.g., mail), as well as a selectable affordance 640c to display a settings user interface for viewing information about the corresponding application and updating usage limit settings for that application.

6P-6Q show a user scrolling (e.g., by contact 603) through the usage dashboard user interface to reveal indications of additional usage metrics, as shown in FIG. 6R. FIG. 6R shows a usage dashboard user interface including a graph 644 of notifications received throughout the day, an indication 646 of the number of notifications received during the day, an indication 648 of the time of day when the most notifications were received, and indications 650a-650d of how many notifications were generated by various applications installed on the electronic device (e.g., all applications that generated notifications today or applications that generated a top set number of notifications today). The graph 644 includes a number of bars indicating how many notifications the electronic device presented during each hour of the day. The user interface further includes a number of affordances 652a-652d visually associated with the indications 650a-650d, which are selectable to display notification settings for the corresponding application for which the indication of the notification is being displayed. For example, affordance 652a is selectable to edit notification settings for the iMessage app. Notification indications 650a-650d include the name of the application (e.g., "iMessage App", "Email App", "News App", and "Water Tracker App"), a count of how many notifications were generated by each application during the day, and dots positioned to indicate the relative number of notifications generated by that application compared to other applications.

Figures 6S-6T show that the user may scroll (e.g., by contact 603) through the usage dashboard user interface to reveal indications of additional usage metrics, as shown in Figure 6U.

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

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

The device pickups throughout the day graph 658 includes a bar for each hour of the day showing the number of device pickups during 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 the device downtime glyph 698-22.

The application with which the user interacts upon picking up the electronic device 664a-b is determined based on the first application with which the user interacts upon picking up the device. For example, if the user powers up the device and immediately closes a first application presented on the electronic device at power up, and then opens a second application and performs an operation in the second application, the second application is the application with which the user interacts upon picking up the electronic device. As another example, if a notification associated with the first device is presented while the device is in a sleep mode, and the user provides input to interact with the first application upon viewing the notification, the first application is the application with which the user interacts upon picking up the electronic device.

As used herein, device "pickup" encompasses many types of user attention events, such as a user unlocking an electronic device, waking up the device, and other actions that initiate operation of the electronic device. In some embodiments, a user attention event is detected when a user input causes the electronic device to exit an idle state (e.g., a sleep mode, a locked state, a low power mode, etc., where there is no user interaction with the electronic device and/or the display of the electronic device is off). 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 a user input corresponding to a request to enter the idle state (e.g., pressing a power button or a lock button on the electronic device). In some embodiments, the display does not display an image during the idle state. In some embodiments, a lock screen is displayed on the electronic device during the idle state. The user input corresponding to the user attention event is optionally one or more of a button press on the electronic device, a user action to exit an idle state (e.g., lifting the device), an unlock input (e.g., entering a passcode or providing a biometric), and a touch input to access a function of the electronic device (e.g., displaying a widget user interface, a camera application, a dashboard user interface, a user interface of an application associated with an indication of a displayed notification). Detecting the biometric optionally includes detecting the user's face with a depth camera or another sensor. In some embodiments, the electronic device can use a depth camera and facial recognition technology to determine when a user looks at the user's electronic device and unlock in response to the user looking at the electronic device (e.g., the electronic device unlocks in response to determining that the user is looking at the electronic device). In some embodiments, the electronic device exits the idle state in response to a notification (e.g., the display turns on to display a notification without a user input requesting that the display be turned on), and the attention event causes the device to perform some other action (e.g., unlocking the device, updating the display to display an application or operating system user interface). That is, an indication of a notification is not a user attention event, even if it optionally causes the device to exit an idle state. In some embodiments, the attention event metric indicates the number of times a user begins to use an electronic device (e.g., "checks" the user's phone).

FIG. 6V illustrates a limit setting user interface. As shown, the limit setting user interface includes an indication 608a ("John Jr.'s iPhone") of an electronic device associated with a user that is part of a family account with which the electronic device 500 is associated. The indication further includes an indication that John Jr.'s iPhone has requested to add more time to at least one usage limit controlled by the electronic device 500. In FIG. 6V, the user selects the indication 608a (e.g., by contact 603).

In response to the user's selection, as shown in FIGURE 6W, the electronic device displays a usage dashboard user interface associated with John Jr.'s iPhone. The user interface may display an indication of a request 666 to remove the overall usage limit implemented on John Jr.'s iPhone, an indication of device usage 666, an indication of an overall screen time usage limit 680 for John Jr.'s iPhone, an indication of the duration of the longest usage session 670 for John Jr.'s iPhone, an indication of device downtime usage 672 on John Jr.'s iPhone, indications of usage of applications that have usage limits set on John Jr.'s iPhone 674a-b, and an indication of the usage of applications that have usage limits set on John Jr.'s iPhone, similar to that described above in FIGURES 6L-6N. Includes an indication 676 of the use of applications that do not have usage limits set on the iPhone.

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 time of a usage limit implemented on the other electronic device. As described above with reference to FIG. 6B, electronic device 500 and John Jr.'s iPhone are optionally associated with a family account through which electronic device 500 can manage usage settings of John Jr.'s iPhone. Indication 666 includes selectable affordances to "deny" the request, "give 1 hour" additional time, or "go to settings" to see further options for changing the limits set on John Jr.'s iPhone. Further details regarding requests from a child device to a parent device to add more time to a usage limit, and usage limits in general, are described below with reference to FIGS. 9A-10AAA.

The usage dashboard user interface further includes a number of affordances 678a-c that can be selected to view information about an associated application or category of applications and/or to change usage limits associated with an application or category 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 close to being reached. In some embodiments, other visual indications are possible.

6X shows a restriction setting user interface. In FIG. 6Y, the user selects (e.g., by contact 603) setting 604e that requires a password (or other authentication such as a passcode or biometric) to change the usage restriction settings on device 500. In response to the selection, the electronic device presents a keypad 682 to accept user input to set the password. In some embodiments, the electronic device presents a full keyboard or user interface where the user can select an option to use a password or passcode length or biometric input (e.g., facial recognition) for authentication to change the usage settings. The authentication required to change one or more usage restriction settings of electronic device 500 is optionally different from the authentication 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 limit settings, as shown in FIG. 6AA. In FIG. 6BB, the user selects the indication 604b to change the usage limits set on the electronic device 500. In response to the input, the electronic device presents a keypad 682 requesting the password (or other authentication method) described above before allowing the user to change the settings, as shown in FIG. 6CC.

Figure 6DD shows the user selecting (e.g., by contact 603) an indication of device usage 602. In response to the selection, the electronic device 500 presents a usage dashboard user interface, as shown in Figure 6EE. As shown in Figure 6FF, the user then selects (e.g., by contact 603) a toggle switch 638b to view usage metrics over a week. In response to the input, the electronic device 500 updates the usage dashboard user interface to display an indication of usage metrics over the past week, as shown in Figure 6GG.

6GG illustrates a usage dashboard user interface presenting multiple usage metrics over the past week. The usage dashboard user interface includes an indication 684 of average device usage per day over the week, an indication 686 of the average daily usage for each day during the week compared to the average usage over a longer period (e.g., last month or ever), a graph 688 showing the daily usage of one or more applications or categories of applications, an indication 690 of the duration of the longest usage session during the week, an indication 692 of the average daily device usage during device downtime, and an indication 694a-694b of the average usage of one or more applications or categories of applications with usage limits for each day during the week. The graph 688 includes a bar for each day of the week showing the usage of the electronic device 500 for each day for a number of color-coded applications or application categories. As shown, graph 688 includes an indication (e.g., a horizontal line extending across graph 688) of overall device usage limits that optionally vary during the week (e.g., Monday through Friday) and over the weekend (e.g., Saturday and Sunday). For example, as shown in FIG. 6GG, the overall device usage limits from Monday through Friday are, optionally, lower than the overall device usage limits for Saturday and Sunday.

Although not shown, it should be understood that the dashboard user interface includes an indication of any other metrics described herein over a week, optionally displaying some metrics in an aggregate over a week (e.g., sum, average, etc.) and other metrics as a maximum or minimum over a week. For example, returning to FIG. 6R, the number of notifications per day 646 is optionally replaced with the average number of notifications for each day over a week, and the interval 648 in which the most notifications were received on a given day is replaced with the interval (e.g., a day or an hour of a day) in which the most notifications were received during the week. As another example, returning to FIG. 6U, the number of device pickups during daily downtime 660 is optionally replaced with the average number of device pickups during device downtime per day over a week, and the maximum time of pickup in a day 662 is optionally replaced with a different interval (e.g., a day or an hour of a day) in which the most notifications were received during the week.

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

Toggle switch 690 allows the user to stop enforcing the category usage limit while preserving the parameters of the usage limit, such as the amount of time, notification style, and included applications. In this way, the user can turn the toggle switch back on and begin enforcing the usage limit again without having to enter the parameters of the usage limit again. Notification and block 694a and notification 694b settings, as well as other details of usage limit settings, are described below with reference to Figures 8A-9K. Toggle switch 696 for presenting a verbal alert associated with the usage limit allows electronic device 500 to speak a notification associated with the usage limit, such as a notification indicating that the usage limit is close to being reached or has been reached.

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

FIG. 6JJ shows an indication of usage of game A 698-2, an indication of average usage of game A 698-4, an indication of usage of game A during device downtime for the day 698-6, an indication of the number of notifications generated by game A during the day 698-8, settings for updating usage limits for game A 689-10, information about game A 698-12, and a graph of usage of game A over time for the day 698-14 (e.g., displayed as multiple bars, each representing usage of game A during each hour of the day). As shown, a user can create a usage limit for game A, including setting the amount of time for the usage limit 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 about game A 698-12, such as its application icon, age rating, category, developer, and a link to view game A in the app store on the electronic device. The user interface shown in FIG. 6JJ is accessible from the category settings user interface shown in FIGS. 6HH-6II, while similar user interfaces for individual applications are accessible from the usage metrics dashboard user interface (e.g., as shown in FIGS. 6L-6O, 6W, and 6EE-6HH) when the user selects a settings affordance associated with an individual application (e.g., 640a associated with a news app, 678c associated with a dictionary app, etc.).

Figure 6KK illustrates a usage dashboard user interface presenting usage metrics for notifications such as those described with reference to Figure 6R. Figure 6LL illustrates a user selecting affordance 652c associated with news app notification settings (e.g., via contact 603). In response, electronic device 500 presents a notification settings user interface for the news app, as shown in Figure 6MM. The notification settings user interface includes a toggle switch 698-16 for allowing notifications from the news app, a toggle switch 698-18 for presenting notifications for the news app in silent mode, and an option 698-20 for changing indications of what types of notifications the news app presents. In contrast to presenting one or more indications of a notification (e.g., a visual indication, such as text or an image, an audio indication, such as a sound or spoken phrase, and/or haptic or other tactile feedback, etc.) when a notification is received at the electronic device when notifications are "on," toggling the "Allow notifications" toggle switch 698-16 off causes the application to not present notifications anywhere on the electronic device 500. Toggling the "Silent notifications" toggle switch 698-18 on causes the electronic device 500 to forgo presenting an indication of a notification when a notification is received (e.g., as the electronic device would do if notifications were allowed), but presents an indication of the notification in a notification history user interface that includes an indication of multiple notifications received at the electronic device, unlike the device's behavior when notifications are not allowed, as exemplified below with reference to FIG. 12I. Changing the "Allowed notifications" setting 698-20 causes the electronic device 500 to present all notifications received at the application, a limited number of notifications, or only very important notifications.

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

6PP illustrates the usage dashboard user interface after the user uses 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, the electronic device 500 combines the instant messaging application and the email application into a messaging category (e.g., pursuant to a determination that the total usage of the applications in the messaging category meets a category usage threshold). Once the mail app and the IM app are combined into the messaging category, the graph 620 is updated to include a color or pattern associated with the messaging category that indicates use of one of the applications (e.g., the mail app or the IM app) in the messaging category. In some embodiments, applications are combined into a category when the combined usage of those applications meets or exceeds a predefined category usage threshold.

In FIG. 6QQ, the dashboard user interface is updated again after the user uses the electronic device 500 to use the instant messaging application for another 30 minutes, bringing the total application usage to 60 minutes. In response to the additional usage, the electronic device 500 separates the instant messaging application and the email application (e.g., pursuant to a determination that the use of the instant messaging application meets an application usage threshold). That is, the graph 620 is updated to include distinct colors or patterns that indicate the use of the IM app and the email app separately, as opposed to combining them into a messaging category. In some embodiments, the applications are separated when the use of the individual applications within the combined category meets or exceeds a predefined application usage threshold.

In some embodiments, the device 500 does not only include application usage within usage for a given application (or category), but also includes usage of web resources (e.g., web pages) corresponding to a given application within usage for a given application (or category). For example, FIG. 6RR shows a usage dashboard user interface after a user has accessed a website associated with an instant messaging application for 30 minutes. As shown, by accessing the website associated with the instant messaging application, the electronic device 500 now tallies toward usage of the instant messaging application to indicate that the instant messaging application was used for a total of 1.5 hours. This number includes 1 hour of use of the native instant messaging application and 30 minutes of accessing the associated website of the instant messaging application using a web browsing application. In this way, total usage is optionally tracked beyond just native application usage.

FIG. 6SS shows the user selecting (e.g., by contact 603) the indication 610b of "Apple TV" within the limit setting user interface. In response to the selection, the electronic device presents a usage dashboard user interface including usage metrics associated with Apple TV, as shown in FIG. 6TT. In this manner, the user can focus on other uses of the user's device. The usage dashboard user interface of FIG. 6TT includes an indication 616 of device usage for the day, an indication 618 of how usage for the day compares to average usage, a graph 620 of device usage of applications and application categories throughout the day, an indication 634 of the duration of the longest usage session, an indication 636 of device usage during downtime, and an indication 622a-622b of usage of applications and application categories for which usage limits have been set. In some embodiments, the 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 in the usage dashboard user interface shown in FIG. 6TT are similar to the 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 (e.g., all of John's devices, including Apple TV and John's iPhone). In this manner, a user can view the user's usage across multiple (e.g., all) of the user's devices. The usage dashboard user interface of FIG. 6UU includes an indication 616 of combined usage of multiple electronic devices for a day, an indication 618 of how usage for a day compares to average usage, a graph 620 of combined usage of devices for applications and application categories during the day, an indication 634 of the longest usage session duration across all devices, an indication 636 of total usage of all devices during downtime, and an indication 622a-622c of usage of applications and application categories with usage limits. In some embodiments, the 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 in the usage dashboard user interface shown in FIG. 6UU are similar to the similar usage metrics described above with reference to FIG. 6L.

7A-7S are flow diagrams illustrating a method 700 for providing an indication of a usage metric, according to some embodiments of the present disclosure. The method 700 is optionally performed on an electronic device, such as device 100, device 300, or device 500, as described above with reference to FIGS. 1A-1B, 2-3, 4A-4B, and 5A-5H. Some operations of the method 700 are optionally combined and/or the order of some operations is optionally changed.

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

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

In some embodiments, while displaying the visual indication of the first usage metric and the visual indication of the second usage metric within the dashboard user interface, the electronic device receives input via one or more input devices corresponding to a request to display a visual indication of a third usage metric that is different from the first usage metric and the second usage metric (e.g., the third usage metric is associated with a different action, a different type of action, a different quantification of usage, and/or a different time period (in some embodiments, the same time period) than the first usage metric and/or the second usage metric), such as in FIG. 6M-6N. For example, in response to a user input to view total screen time and time spent using a particular application over the past week, the electronic device updates the display to present total screen time and time spent using the electronic device to interact with the particular application over the past week (e.g., as opposed to over the past day, thus allowing the user to view metrics over different time periods). As another example, in response to an input to view the number of notifications received by the electronic device over the course of a day (e.g., in response to a user input swiping down via the dashboard user interface), the electronic device updates to display a chart showing the number of notifications received on the electronic device during each hour of the day, as well as details regarding how many notifications were generated by different applications. In some embodiments, in response to receiving the input, the electronic device updates (714) the dashboard user interface to include a visual indication of a third usage metric, such as in Figures 6M-6N (e.g., with or without ceasing to display the visual indication of the first usage metric and the visual indication of the second usage metric). For example, the input to display a visual indication of the third usage metric is, optionally, an input to scroll via the dashboard user interface, which optionally causes the visual indication of the third usage metric to scroll to a display not previously displayed on the display. The above-described method of simultaneously displaying multiple visual indications of multiple usage metrics to allow a user to view additional visual indications of additional usage metrics allows an electronic device to efficiently visually communicate different metrics of device usage to a user, thereby simplifying the interaction between the user and the device and enhancing usability of the device (e.g., by providing more than one way to communicate device usage so that the user can view the usage metrics that are most meaningful to the user), as well as reducing power usage and improving battery life of the device by allowing the user to use the device more quickly and efficiently.

In some embodiments, the electronic device is one of a plurality of electronic devices associated with a user account (e.g., a user ID for accessing personal data and/or settings on a plurality of electronic devices) (716), such as in FIG. 6D. The dashboard user interface optionally includes a visual indication of a first corresponding usage metric (e.g., a first usage metric or a second usage metric) associated with a first operation of a plurality of electronic devices, including the electronic devices associated with the user account (718), such as in FIG. 6UU (e.g., the first usage metric tracks all usage of the electronic devices associated with the user account to perform a first operation). In some embodiments, the first quantification of usage includes an aggregation of usage of a plurality of electronic devices, including the electronic devices performing the first operation, during a first predetermined time period, as shown in FIG. 6UU (e.g., if the first usage metric is an amount of time spent operating a particular application or a particular group of applications, the first quantification of usage is a total amount of time spent operating a particular application or a particular group of applications across all devices associated with the user account during a predetermined time period). The above-described method of associating usage metrics with multiple electronic devices associated with a user allows the electronic device to present consistent and accurate usage data to the user across all of the user's devices, thereby simplifying the interaction between the user and the device and enhancing usability of the device (e.g., by presenting the user's usage data as a single set of metrics for all devices without the user having to individually review the usage data for each device), as well as allowing the user to use the device more quickly and efficiently, thereby reducing power usage and improving the device's battery life.

In some embodiments, the dashboard user interface includes a visual indication of a second corresponding usage metric (e.g., a third usage metric) associated with the first operation of the electronic device rather than the first operation of the second electronic device (722), as shown in FIG. 6TT (e.g., the electronic device switches from displaying aggregated usage metrics across multiple devices to displaying usage metrics for each device separately in response to 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 a visual indication of usage metrics for each of multiple electronic devices associated with the user account. The above-described method of associating usage metrics with multiple electronic devices associated with a user allows the electronic device to present consistent and accurate usage data to the user across all of the user's devices, thereby simplifying the interaction between the user and the device and enhancing usability of the device (e.g., by presenting the user's usage data as a single set of metrics for all devices without the user having to individually review the usage data for each device), as well as allowing the user to use the device more quickly and efficiently, thereby reducing power usage and improving battery life of the device.

In some embodiments, while displaying the visual indication of the first usage metric and the visual indication of the second usage metric within the dashboard user interface, the electronic device receives input via one or more input devices corresponding to a request to display the first usage metric and the second usage metric in more detail (e.g., a request to display more information regarding the first usage metric and/or the second usage metric, such as selecting the first usage metric and/or the second usage metric within the dashboard user interface (e.g., toggling from "overview" to "detailed view")) (724), such as in FIG. 6F-6G. In some embodiments, in response to receiving the input, the electronic device updates the dashboard user interface to display a second visual indication of the first usage metric (e.g., a visual indication that includes more information at or about the first usage metric than was included in the first visual indication) and a second visual indication of the second usage metric (e.g., a visual indication that includes more information at or about the second usage metric than was included in the first visual indication) (726), as shown in FIG. The second visual indication of the first usage metric and the second visual indication of the second usage metric optionally include (728) a first corresponding visual indication of a quantification of the use of the electronic device performing the first operation during each of a plurality of time periods during the first predetermined time period (730) as shown in Figures 6DD-6EE (e.g., showing the metric in one-hour bins over a day). In some embodiments, the second visual indication of the first usage metric is or is included in a graph or chart over time (e.g., a line graph, a bar graph, a plurality of pie charts for each time interval) and a second visual indication of a quantification of the use of the electronic device performing the second operation during each of a plurality of time periods during the first predetermined time period (732) (e.g., showing the metric in one-hour bins over a day), as shown in Figure 6G. In some embodiments, the second visual indication of the second usage metric is or is included in a graph or chart over time (e.g., a line graph, a bar graph, a plurality of pie charts for each time interval). The respective indications of usage for each of the multiple time periods optionally include an indication of a first operation (e.g., presenting information on a first application or group of first applications) and a second operation (e.g., presenting information on a second application or group of second applications). In some embodiments, the detailed view includes a graph or chart using different colors or other visual indications to convey a quantification of usage by the electronic device performing the first operation (e.g., presenting information on a first application or group of first applications) and the second operation (e.g., presenting information on a second application or group of second applications). The above-described method of further displaying information regarding the first usage metric allows the electronic device to display a usage summary and a usage detailed view, thereby simplifying the interaction between the user and the device to enhance the usability of the device (e.g., by hiding details when the user does not want to see them and by showing details when needed), 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 dashboard user interface further includes a first affordance (e.g., a selectable icon) (736) visually associated with (e.g., displayed adjacent to) the visual indication of the first usage metric, selectable to display a settings user interface for changing one or more settings associated with the first usage metric (e.g., the first usage metric is an amount of time the electronic device is used to run the first application or first group of applications, and the settings user interface includes an option (such as method 900) for setting a usage limit for the first application or first group of applications). Additionally or alternatively, the first usage metric is optionally a number of notifications generated by the first application or first group of applications, and the settings user interface includes an option for changing notification settings for the first application or first group of applications, as shown in FIGS. In some embodiments, a second affordance (e.g., selectable icon) (738) visually associated with (e.g., displayed adjacent to) the visual indication of the second usage metric, such as in FIGS. 6HH-6II, and selectable to display a settings user interface for changing one or more settings associated with the second usage metric (e.g., the second usage metric is an amount of time the electronic device is used to execute the second application or second group of applications, and the settings user interface includes an option (such as in method 900) for setting a usage limit for the second application or second group of applications). Additionally or alternatively, the second usage metric is optionally a number of notifications generated by the second application or second group of applications, and the settings user interface includes an option for changing notification settings for the second application or 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, as well as a list of at least the first usage metric and the second usage metric. The dashboard user interface optionally includes additional usage metrics in the graphs or charts and in the list. In some embodiments, the first and second affordances are displayed next to visual indications of the first and second usage metrics included in the list, respectively. In some embodiments, the settings user interface includes visual indications of usage of the selected application or category over a first period (e.g., a day), an indication of usage during a limited usage mode (e.g., bedtime or device downtime), an indication of average usage of the particular application, an indication of notifications generated by the application, an affordance for setting usage limits for the particular application, and a summary of store information about the application (e.g., 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 a selectable affordance to display metrics for a single application in response to a user selecting an affordance associated with a category of applications. The above-described method of displaying a selectable affordance to display a settings user interface while displaying the first and second usage metrics allows the electronic device to provide a way for a user to navigate to settings associated with a usage metric while viewing the usage metric, thereby simplifying the interaction between the user and the device to enhance usability of the device (e.g., by simplifying the user's workflow for changing settings associated with the displayed metrics) and additionally allowing the user to use the device more quickly and efficiently, thereby reducing power usage and improving the device's battery life.

In some embodiments, the first predefined period is the current day (740), as shown in FIG. 6FF (e.g., the first usage metric is a quantification of usage of the electronic device to perform a first operation during the current day). 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 prior to the current time on the electronic device. A third usage metric is optionally associated with the first operation of the electronic device (742) (e.g., the third usage metric is associated with the first usage metric and associated with the same operation of the electronic device in some other manner (e.g., usage quantification, time interval, etc.)). In some embodiments, the visual indication of the third usage metric includes a third quantification of use of the electronic device to perform the first operation during the week prior to the current day (744), as shown in FIG. 6GG (e.g., the electronic device displays usage metrics associated with the first operation of the electronic device over a week period (e.g., the past seven days including the current day, a week including the current day starting on a particular day (e.g., a Sunday or Monday)). In some embodiments, the visual indication of the first usage metric is or is included in a graph or chart (e.g., a line graph, a bar graph, a bar chart, or a pie chart). For example, the first usage metric is, optionally, an amount of time the electronic device was used to present information associated with the first application or first group of applications, and the dashboard displays a graph or chart including device usage for each day broken down into sections representing each application or group of applications. The above-described method of updating a dashboard user interface to display first usage metrics over a week allows an electronic device to present usage metrics over a longer period of time, thereby simplifying the interaction between the user and the device and enhancing the usability of the device (e.g., by presenting additional information 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 device's battery life.

In some embodiments, the dashboard user interface includes a visual indication of a first corresponding usage metric (e.g., a 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 ways of presenting information, such as playing sounds (e.g., music or other media, spoken sounds such as during a phone call, etc.) using speakers in communication with the electronic device), and the first corresponding usage metric includes an amount of time the electronic device was used to display information during a first predetermined period (748), as shown in FIG. 6L (e.g., the first metric is a total usage of the electronic device to display information across all applications on the electronic device (e.g., total application screen time on the electronic device)). In some embodiments, the total usage metric further includes a time that one or more speakers associated with the electronic device were used to present audio content, and a time that other output devices of the electronic device were used to present information. The total usage is optionally presented as an amount of usage time over a specified period (e.g., a day, a 24-hour period, a week, or another user-specified period). In some embodiments, the total usage is optionally presented to the user in text (e.g., text indicating the amount of time the device was used) and/or a graphic, such as a graph or chart. The indication optionally includes a percentage value bar representing the total device usage as a percentage (e.g., 50% of a 4-hour usage limit) or a proportion (e.g., 2 hours of a 4-hour usage limit) of a usage limit set by the user of the electronic device. In some embodiments, while presenting a first metric indicative of overall display or device usage, the electronic device further presents one or more usage metrics (e.g., including a second usage metric) indicative of the amount of time the electronic device was used to display or present information associated with various applications or groups of applications. For example, the visual indication of the overall device screen time optionally includes an indication of how much time the device displayed or presented information associated with each of a plurality of applications or groups of applications. The above-described methods of presenting a visual indication of the amount of time the device has been used to present information allow an electronic device to visually communicate to a user the amount of time the device has been used, thereby making 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 usage is reduced)) and, in addition, reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

In some embodiments, displaying information on the display includes displaying information on the display (e.g., or presenting on a different output device in communication with the electronic device (e.g., playing sound, media, or speech on a speaker in communication with the electronic device)) in one or more first applications (e.g., a particular application or group of applications, such as in FIG. 6L, in some embodiments, the application group is user-defined or system- or third-party-defined), as shown in FIG. 6L (750). A first corresponding usage metric optionally includes an amount of time that the electronic device was used to display information in the one or more first applications during a first predetermined period, as shown in FIG. 6L (e.g., the first usage metric is a screen time associated with the one or more first applications). In some embodiments, a usage limit is set for the one or more first applications (754) (e.g., limiting the amount of time that the one or more first applications can be used to present information in a given period (e.g., day) before accessing the one or more second applications). The visual indication of the first corresponding usage metric optionally further includes an indication of a usage limit for one or more first applications (e.g., a maximum amount of time the device will present information without restricting access to the one or more applications of the device), as shown in FIG. 6L, where the indication of the first usage limit is visually associated (746) with the visual indication of the first corresponding usage metric (e.g., the visual indication visually compares the amount of time the device has been 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, where the size of the bar chart represents the usage limit. In some embodiments, the usage limit is predefined by the user. The dashboard user interface optionally presents an indication of when the usage limit is close to being reached (e.g., text or an icon indicating that the usage limit is close to being reached) and/or an indication of when the usage limit is exceeded, optionally including an indication quantifying the extent to which the usage limit is exceeded. For example, when the usage limit is represented by a bar chart, a portion of the bar chart optionally indicates an amount of usage that exceeds the usage limit. A user optionally sets usage limits for one or more applications, one or more groups of applications, and/or an overall usage limit for the device. Thus, in some embodiments, the one or more first applications optionally include one application, multiple applications, or all applications accessible on the electronic device. The usage limits described herein are optionally the same as or similar to the usage limits described with reference to method 900. The above-described method of comparing a first metric to a usage limit of an electronic device allows the electronic device to communicate how long a user can continue to use the electronic device to present information before one or more usage limits will be implemented, thereby making the user-device interface more efficient (e.g., the user does not have to compare the user's device usage to the user's own usage limit), as well as allowing the user to use the device more quickly and efficiently, thereby reducing power usage and improving the device's battery life.

In some embodiments, the dashboard user interface includes a visual indication of a second corresponding usage metric (e.g., a second usage metric) associated with displaying (e.g., or presenting on a different output device in communication with the electronic device (e.g., playing sound, media, or speech on a speaker in communication with the electronic device)) information on a display in one or more second applications (e.g., a particular application or group of applications, as shown in FIG. 6N; in some embodiments, the application group is user-defined or system- or third-party-defined) (758). In some embodiments, as shown in FIG. 6N, a usage limit is not set for one or more second applications (760), and the visual indication of the second corresponding usage metric, optionally, does not include an indication of a usage limit for the one or more second applications (e.g., because it is not present) (762). The visual indication of the second usage metric, optionally, indicates an amount of time that the electronic device was used to display information in the one or more second applications, without an indication of a usage limit. In some embodiments, no usage limit is set for one or more second applications, but the use of some or all of the one or more second applications is optionally restricted by a usage limit having a scope that is not strictly different from all of the one or more second 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 applications that belong to a particular category of applications (e.g., games). In this example, there is optionally no overall usage limit set on the electronic device (e.g., a usage limit that sets a maximum device usage across all applications), but some of the one or more second applications (e.g., one or more first applications) are subject to a usage limit (e.g., a usage limit for one or more first applications). Similarly, the one or more second applications optionally include a particular application (e.g., a particular game application), and the one or more first applications optionally include applications that belong to a particular category of applications (e.g., games). In this example, optionally there is no usage limit set for a particular second application, but because one or more of the first applications include the second application, the use of the second application is limited by the usage limits of the one or more first applications. The above-described method of indicating a usage limit associated with application usage while displaying application usage metrics allows the electronic device to communicate how long a user can continue to use the application to present information before one or more usage limits will be implemented, thereby making the user's interface with the device more efficient (e.g., the user does not have to compare the user's application usage against the user's own usage limits), as well as allowing the user to use the device more quickly and efficiently, thereby reducing power usage and improving the device's battery life.

In some embodiments, pursuant to a determination (764) that an amount of usage of the electronic device displaying information in one or more first applications is within a threshold amount (e.g., a percentage amount (e.g., 25%, 10%, 5%, etc.) or an absolute amount of time (e.g., 30 minutes, 15 minutes, 5 minutes, etc.) of a usage limit of the one or more first applications, the visual indication of the first corresponding usage metric includes a visual indication that the usage limit of the one or more first applications is close to being reached (e.g., displaying text or an icon indicating that the usage limit is close to being reached, or a visual characteristic is applied to the first visual indication of the usage metric (e.g., changing the color or size of the visual indication or a portion of the visual indication)). In some embodiments, each visual indication of the one or more usage metrics includes an affordance that is selectable to display a settings user interface for modifying one or more settings associated with the corresponding usage metric. The dance is optionally displayed with a visual characteristic (e.g., a different color) that indicates a usage limit associated with the corresponding usage metric that is within a threshold amount. The dashboard user interface optionally presents an indication when a usage limit has been exceeded, optionally including an indication quantifying the extent to which the usage limit has been exceeded. For example, when the usage limit is represented by a bar chart, a portion of the bar chart optionally indicates the amount of usage that exceeds the usage limit. The above-described method of indicating when a usage limit is close to being reached while displaying a usage metric allows the electronic device to communicate how long a user can continue to perform one or more operations before one or more usage restrictions will be implemented, thereby making the user's interface with the device more efficient (e.g., the user does not have to compare the user's usage with the user's own usage limit), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

In some embodiments, the visual indication of the first corresponding usage metric includes an indication of the amount of time the electronic device was used to present information using each of a plurality of application groups (766), as shown in FIG. 6L, where each application group includes one or more applications accessible on the electronic device (e.g., an application group is either a single application (e.g., an email application, a social networking application, a gaming application, an Internet browser, etc.) or a category including multiple applications (e.g., a social media category, a gaming category, a news category, a user-defined category including multiple applications selected by the user, etc.)). The visual indication optionally includes a visual representation of how much of the 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 a segment for each application category (e.g., a pie chart with multiple "slices", a bar chart with multiple segments, a bar chart with multiple bars). The total usage is optionally compared to a usage limit (e.g., the entire pie of the pie chart represents a fixed usage limit, the length of the bar chart represents a fixed usage limit, etc.). In some embodiments, the dashboard user interface includes a visual indication of a second corresponding usage metric (e.g., a second usage metric) associated with the amount of time the electronic device was used to present information using the first application group (768), as shown in FIG. 6L (e.g., in addition to presenting the device usage of the first application group within a total device usage metric, a separate metric conveying the amount of time the first application group was used is presented). The visual indication of the second corresponding usage metric optionally includes a visual indication of the second corresponding usage metric separate from the visual indication of the first corresponding usage metric (770), as shown in FIG. 6L (e.g., in addition to being presented as part of the visual indication of overall device usage (e.g., as part of a graph or chart), the usage of the first application group is presented in an additional manner). In some embodiments, the visual indication of the first application group usage includes text indicating the amount of time the first application group was used. Optionally, a graphic is displayed that is separate from the visual indication of total device usage, such as a bar having a length indicating the usage of the first application group, a dot having a position indicating the usage of the first application group, or another visual representation of the usage of the first application group. In some embodiments, the electronic device presents a graph or chart indicating how much time the electronic device was used to present information using each of the multiple applications and/or groups of applications, as well as a textual indication of the amount of time spent using each of the multiple applications and/or groups of applications. The above-described method of presenting device usage for each of the multiple application groups allows the electronic device to graphically present detailed information about device usage to the user, thereby simplifying the interaction between the user and the device to enhance 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 quickly and efficiently, thereby reducing power usage and improving the battery life of the device.

In some embodiments, the dashboard user interface includes a visual indication (774) of a first corresponding usage metric (e.g., a first usage metric) associated with running one or more first applications (e.g., individual applications or categories of applications) accessible on the electronic device (e.g., installed or accessed via a network connection) (772), as shown in FIG. 6L. The dashboard user interface optionally includes a visual indication (776) of a second corresponding usage metric (e.g., a second usage metric) associated with running one or more second applications (e.g., individual applications or categories of applications, as shown in FIG. 6L; in some embodiments, the application categories are defined by a user; in some embodiments, the application categories are defined by an app store, a publisher, etc.) accessible on the electronic device (e.g., installed or accessed via a network connection). Thus, as shown in FIG. 6L, the usage metric associated with the first operation is optionally the amount of time during the first predetermined time period that the electronic device is used to execute (e.g., display) one or more first applications, and the usage metric associated with the second operation is optionally the amount of time during the first predetermined time period that the electronic device is used to run (e.g., display) one or more second applications. The above-described method of presenting usage metrics for executing applications and/or groups of applications allows the electronic device to present information about which applications are executed on the electronic device, thereby simplifying the interaction between the user and the device to enhance usability of the 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 one or more first applications are multiple applications that belong to the same category (e.g., a user-defined category or a system-defined category of applications) (778), as shown in FIG. 6L. In some embodiments, the category is 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), the usage limit set for the category with which the new application is associated is optionally automatically applied to the new application. The first metric is optionally a quantification of total usage for a group of applications in the category. The one or more second applications are optionally an application (780), as shown in FIG. 6L (e.g., the second metric is optionally a quantification of usage for an individual application). In some embodiments, the dashboard user interface displays a mixture of one or more metrics for a group 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. 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. For example, applications with usage above a predefined application usage threshold will optionally have application metrics presented in the dashboard user interface, and categories of applications with usage above a predefined category threshold (in some embodiments, without individual applications 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 have category metrics presented in the dashboard user interface. The above-described method of simultaneously presenting metrics for individual applications and application categories in the dashboard user interface allows the electronic device to present usage metrics that are indicative in a meaningful way of how the electronic device is being used (e.g., by displaying metrics at a similar granularity), thereby simplifying the interaction between the user and the device to enhance usability of the device (e.g., by presenting a mix of category and application metrics simultaneously), as well as allowing the user to use the device more quickly and efficiently, thereby reducing power usage and improving the device's battery life.

In some embodiments, the first usage metric represents usage of the native application and usage of web resources (e.g., using a web application or viewing a web page) associated with the native application (e.g., usage of using a browser application to access a website when a user uses a browser application to access a website (e.g., a particular social networking website) associated with the application (e.g., a particular social networking application associated with the website) on the electronic device, as shown in FIG. 6RR (782). For example, if the first usage metric is a social media metric, the first metric includes device usage to access a social media platform using a web browser on the electronic device and device usage to execute a social media application installed on the electronic device. The above-described method of including device usage to access a web page using an electronic device's browsing application as part of the usage metrics associated with the application or category associated with the web page allows the electronic device to accurately track device usage associated with the application or category of usage metrics, thereby simplifying the interaction between the user and the device to enhance the usability of the device (e.g., by combining web usage with the appropriate usage metric(s)) and additionally allowing the user to use the device more quickly and efficiently, thereby reducing power usage and improving the device's battery life.

In some embodiments, as shown in FIG. 6PP, the aggregate usage of one or more first applications (e.g., multiple applications belonging to the same user-defined or system-defined category) may be greater than or equal to a predefined category usage threshold (e.g., the predefined category usage threshold may be an absolute threshold (e.g., a predefined amount of time (e.g., 30 minutes, 1 hour, 2 hours, etc.) or number of times (e.g., 5 times, 10 times, 50 times, etc.) that the multiple first applications were used to perform an action (e.g., present information, generate a notification, etc.) during a first time period (e.g., 1 day, 1 week, etc.)), or a first In accordance with a determination that the total device usage exceeds a threshold percentage value (e.g., 5%, 10%, 25%, etc.) of the total device usage during the period of time (784), the dashboard user interface optionally includes a combined usage metric for the multiple first applications (e.g., without including individual usage metrics for any of the multiple first applications) (e.g., when the total usage of the multiple first applications exceeds a category threshold, the total usage of the multiple first applications is presented as a group and as a first metric in the dashboard user interface). In some embodiments, as shown in FIG. 6PP, following a determination that the total usage of the first applications of one or more first applications does not exceed a predefined category usage threshold (e.g., the total usage of the applications belonging to the same category is below the threshold) (786), the dashboard user interface includes usage metrics for each of the first applications without including a combined usage metric for the first applications (e.g., when the total usage of the applications does not meet the threshold, the usage of one or more applications in the category is optionally presented as separate usage metrics (e.g., including the first and/or second usage metrics). The above-described method of selectively presenting metrics for a group of applications allows an electronic device to present information regarding the categories of applications that are most commonly executed, thereby simplifying the interaction between the user and the device to enhance the usability of the device (e.g., by presenting combined metrics for the group of applications when the total usage of the group of applications exceeds the threshold), 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, as shown in FIG. 6QQ, following a determination that usage of a single first application of one or more first applications (e.g., the one or more first applications are multiple applications belonging to the same user-defined or system-defined category) exceeds an application usage threshold (e.g., a predetermined application usage threshold is an absolute threshold (e.g., a predetermined amount of time (e.g., 30 minutes, 1 hour, 2 hours, etc.) or number of times (e.g., 5 times, 10 times, 50 times, etc.) that the first application was used to perform an action (e.g., present information, generate a notification, etc.) during the first time period), or a percentage threshold of total device usage during the first time period (e.g., 5%, 10%, 25%, etc.)), the dashboard user interface includes usage metrics for the single first application (e.g., instead of or in addition to combined usage metrics for the multiple first applications) (e.g., when usage of the first application exceeds the application threshold, usage of the first application is presented in the dashboard user interface as a first metric). In some embodiments, as shown in FIG. 6QQ, following a determination that the total usage of a single first application of the one or more first applications does not exceed a predefined application usage threshold (e.g., the usage of the single first application is below the threshold) (790), the dashboard user interface includes usage metrics for the multiple first applications (e.g., when the usage of the single first application does not meet the threshold, the usage of the multiple first applications is presented in the dashboard user interface as a group and as a 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 application-related metrics allows an electronic device to present information about the most commonly executed applications, thereby simplifying the interaction between the user and the device to enhance the usability of the device (e.g., by presenting application-related metrics when the usage of the group of applications exceeds the threshold), as well as allowing the user to use the device more quickly and efficiently, thereby reducing power usage and improving the device's battery life.

In some embodiments, the dashboard user interface includes a visual indication of a first corresponding usage metric (e.g., a first usage metric) associated with receiving one or more notifications at the electronic device (792), as shown in FIG. 6KK (e.g., the dashboard user interface includes a notification metric indicating a number of notifications received at the electronic device for a given amount of time (e.g., an hour, a day, a week, etc.). The one or more notifications are optionally received from different electronic devices via a wireless or wired connection. The one or more notifications are optionally generated by an application installed on the electronic device. The above-described method of displaying notification metrics within the dashboard user interface allows the electronic device to efficiently and clearly communicate device usage for receiving notifications, thereby simplifying the interaction between the user and the device to enhance device usability (e.g., by automatically collecting notification usage data), as well as allowing the user to use the device more quickly and efficiently, thereby reducing power usage and improving device battery life.

In some embodiments, receiving one or more notifications at the electronic device includes receiving notifications (e.g., receiving a new message notification from a messaging application) associated with one or more first applications (e.g., a particular application or group of applications, such as multiple applications in the same system-defined or user-defined category) of the electronic device (794), as shown in FIG. 6R. In some embodiments, the electronic device presents an indication of each received notification (e.g., displaying an image, generating a vibration or haptic and/or tactile output, playing a sound, etc.). The visual indication of the first corresponding usage metric optionally includes a displayed number indicating the number of received notifications (e.g., a particular application or group of applications, such as multiple applications in the same system-defined or user-defined category) associated with one or more first applications of the electronic device during a first predetermined period (e.g., a day, a week, a month, etc.) (796). In some embodiments, the dashboard user interface includes a visual indication of a second corresponding usage metric (e.g., a second usage metric) associated with receiving notifications associated with one or more second applications of the electronic device (e.g., receiving an advisory notification from an advisory application) (798), as shown in FIG. 6R. In some embodiments, the electronic device presents an indication of each received notification (e.g., displaying an image, generating a vibration or haptic and/or tactile output, playing a sound, etc.). The visual indication of the second corresponding usage metric optionally includes a displayed number indicating a number of received notifications associated with one or more second applications of the electronic device during a first predetermined period (e.g., a day, a week, a month, etc.), as shown in FIG. 6R. The above-described method of displaying notification metrics associated with an application or group of applications allows an electronic device to present information regarding which applications generate the most notifications, thereby simplifying the interaction between the user and the device to enhance usability of the device (e.g., by presenting application data as part of the notification metrics so that the user knows which applications use the device to most frequently cause notifications to be presented), 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 (e.g., by changing notification settings for applications that generate more notifications that the user desires to receive).

In some embodiments, the dashboard user interface further includes a first affordance (798-6) selectable to display a settings user interface (e.g., an option to allow all notifications, allow some notifications (e.g., based on priority, time of day, or some other metric), or not allow notifications for the application or group of applications) for changing notification settings for one or more first applications (798-4), as shown in FIGS. 6LL-6MM. In some embodiments, the first affordance is visually associated with (e.g., displayed adjacent to) a visual indication of a first corresponding usage metric (e.g., the notification metric is displayed simultaneously with the affordance for changing notification settings), as shown in FIGS. 6LL-6MM. And a second affordance (798-8) selectable to display a settings user interface (e.g., an option to allow all notifications, allow some notifications (e.g., based on priority, time of day, or some other metric), or not allow notifications for the application or group of applications) for changing notification settings for one or more second applications. The second affordance is optionally visually associated with (e.g., displayed adjacent to) a visual indication of a second corresponding usage metric (e.g., the notification metric is displayed simultaneously with an affordance for changing the notification settings). 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 a selectable affordance to display notification settings while displaying notification metrics associated with an application or group of applications allows the electronic device to present an option for the user to change settings associated with the metric currently being viewed, thereby simplifying the interaction between the user and the device to enhance usability of the device (e.g., by making notification settings accessible while viewing the notification metrics), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently (e.g., by changing notification settings after viewing the notification metrics).

In some embodiments, the visual indication of the first corresponding usage metric includes a chart (e.g., a line graph, a bar chart, etc.) including an indication of the number of notifications received during each of a plurality of time intervals (e.g., during each hour, during each day, etc.) during a first predetermined time period (e.g., a day, a week, a month, etc.), as shown in FIG. 6LL (798-10). The above-described method of presenting a chart of received notifications over time allows the electronic device to simultaneously present an indication of how many notifications were received during a predetermined time period and how many notifications were received within each interval, thereby simplifying the interaction between the user and the device to enhance usability of the device (e.g., by displaying related information together without further user input), as well as allowing the user to use the device more quickly and efficiently, thereby reducing power usage and improving the device's battery life.

In some embodiments, the dashboard user interface includes a visual indication of a corresponding usage metric (e.g., the first metric or the second usage metric) associated with detecting the user attention event, as shown in FIG. 6U (798-12) (e.g., the dashboard user interface includes a metric indicating the number of times a user initiates an interaction with the electronic device). In some embodiments, the electronic device presents a user attention event (e.g., "device pickups") dashboard that shows one or more metrics related to the user attention event. The user attention event dashboard optionally includes metrics such as the average time between pickups over a given time period (e.g., a day, a week, etc.), the total number of pickups over a given time period, the time period (e.g., an hour of a day, or an hour or day of a week) that has the most user attention events, the number of pickups during a limited use mode, and other metrics. In some embodiments, a user attention event is detected when a user input causes the electronic device to exit an idle state (e.g., a sleep mode, a locked state, a low power mode, etc., where there is no user interaction with the electronic device and/or the display of the electronic device is off). In some embodiments, the electronic device enters the idle state in response to a predetermined amount of time having elapsed since a last user input was received at the electronic device. Optionally, the electronic device enters the idle state in response to a user input corresponding to a request to enter the idle state (e.g., pressing a power button or a lock button on the electronic device). In some embodiments, the display does not display an image during the idle state. In some embodiments, a lock screen is displayed on the electronic device during the idle state. The user input corresponding to the user attention event is optionally one or more of a button press on the electronic device, a user action to exit the idle state (e.g., lifting the device), an unlock input (e.g., entering a passcode or providing a biometric), and a touch input to access a function of the electronic device (e.g., displaying a widget user interface, a camera application, a dashboard user interface, a user interface of an application associated with an indication of a displayed notification). Detecting the biometric optionally includes detecting the user's face with a depth camera or another sensor. In some embodiments, the electronic device can use a depth camera and facial recognition technology to determine when a user looks at the user's electronic device and unlock in response to the user looking at the electronic device (e.g., the electronic device unlocks in response to determining that the user is looking at the electronic device). In some embodiments, the electronic device leaves an idle state in response to a notification (e.g., the display turns on and displays a notification without user input requesting that the display be turned on), and the attention event causes the device to perform some other action (e.g., unlocking the device, updating the display to display an application or operating system user interface). That is, an indication of a notification is not a user attention event, even if it optionally causes the device to leave an idle state. In some embodiments, the attention event metric indicates the number of times a user begins to use the electronic device (e.g., "checks" the user's phone). The above-described method of displaying metrics associated with user attention events (e.g., device pickups) allows an electronic device to present information regarding how frequently a user interacts with the electronic device, thereby simplifying the interaction between the user and the device to enhance usability of the device (e.g., by conveying usage information in a manner that is meaningful to the user), as well as reducing power usage and improving battery life of the device by allowing the user to use the device more quickly and efficiently (e.g., by encouraging the user to use their phone less frequently and therefore more efficiently).

In some embodiments, the visual indication of the first corresponding usage metric includes a visual indication of the time between user attention events (e.g., average time between user attention events (e.g., a button press on the electronic device, a user action to exit an idle state (e.g., lifting the device), an unlock input (e.g., entering a passcode or providing a biometric), a touch input to access a function of the electronic device (e.g., a widget user interface, a camera application, a dashboard user interface, displaying a user interface of an application associated with an indication of a displayed notification)) as shown in FIG. 6U (798-14). In some embodiments, the time between user attention events is calculated as the average time between user attention events during a period within a first predetermined period (e.g., a day, a week, etc.), the period starting with the earliest user attention event during the first predetermined period (e.g., the first attention event of the day, week, or other predetermined period) and the last user attention event during the first predetermined period (e.g., the last attention event of the day, week, or other predetermined period). The above-described method of displaying a metric indicative of the average time between user attention events (e.g., device pickup) allows an electronic device to present information regarding how frequently a user interacts with the electronic device, thereby simplifying the interaction between the user and the device to enhance usability of the device (e.g., by conveying usage information in a manner that is meaningful to the user), as well as reducing power usage and improving battery life of the device by allowing the user to use the device more quickly and efficiently (e.g., by encouraging the user to use their phone less frequently and therefore more efficiently).

In some embodiments, the visual indication of the first corresponding usage metric includes a visual indication of the total number of user attention events (e.g., electronic device button presses, user actions to exit an idle state (e.g., picking up the device), unlock inputs (e.g., entering a passcode or providing a biometric), touch inputs to access a feature of the electronic device (e.g., displaying a widget user interface, a camera application, a dashboard user interface, a user interface of an application associated with an indication of a displayed notification)) during a first predetermined period of time (e.g., a day, a week, etc.), as shown in FIG. 6U (798-16). The above-described method of displaying a metric indicative of the number of user attention events (e.g., device pick-ups) allows the electronic device to present information regarding how frequently a user interacts with the electronic device, thereby simplifying the interaction between the user and the device to enhance usability of the device (e.g., by conveying usage information in a manner that is meaningful to the user), as well as reducing power usage and improving battery life of the device by allowing the user to use the device more quickly and efficiently (e.g., by encouraging the user to use the user's phone less frequently and therefore more efficiently).

In some embodiments, the visual indication of the first usage metric includes a visual indication of the time interval (e.g., an hour of a day, an hour of a week, or a day, etc.) having the highest number of detected user attention events, as shown in FIG. 6U (798-18), which is one of a plurality of time intervals within a first predetermined period (e.g., an hour of a day with the most user attention events detected compared to all of the hours of a day, or a day or hour of a week with the most user attention events detected compared to all of the hours or days of a week). The above-described method of displaying a metric indicative of the time interval with the most user attention events (e.g., device pickups) allows the electronic device to present information regarding when the user interacts with the electronic device the most, thereby simplifying the interaction between the user and the device to enhance the usability of the device (e.g., by conveying usage information in a manner that is meaningful to the user), 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 (e.g., by encouraging the user to use the user's phone less frequently and therefore more efficiently).

In some embodiments, detecting the attention event (798-20) includes identifying the user input as an attention event pursuant to a determination that the detected user input corresponds to a request to exit the idle state of the electronic device (798-22) as shown in FIG. 6U (e.g., the display displays a lock screen (e.g., an operating system user interface that is displayed before the device is unlocked without displaying the user interfaces of any applications accessible to the electronic device), a screen saver (e.g., an image that is displayed without displaying the user interfaces of any applications accessible to the electronic device), or is off (e.g., does not display an image) during the idle state). (For example, the attention event is one of a device movement (e.g., lifting to wake), a touch input (e.g., a touch input to select an image displayed on a lock screen, a swipe input to display a widget user interface, a camera user interface, or another user interface of the operating system or one or more applications), an actuation of a button included in the electronic device (e.g., pressing a power button, an unlock button, a home button, or another button, or toggling a switch), or a detection of a user biometric input (e.g., a fingerprint, an image of the user's face, or another biometric input (e.g., to unlock the device)) that meets one or more activation criteria.) Detecting the biometric optionally includes detecting the user's face with a depth camera or another sensor. In some embodiments, the electronic device can use a depth camera and facial recognition technology to determine when a user looks at the user's electronic device and unlock in response to the user looking at the electronic device (e.g., the electronic device unlocks in response to a determination that the user is looking at the electronic device). In some embodiments, as shown in FIG. 6U, pursuant to a determination (798-24) that the detected user input does not correspond to a request to exit an idle state of the electronic device (e.g., the electronic device is not idle or the detected user input is erroneous (e.g., a large human body contact, a device movement that does not correspond to the user lifting the device, etc.)), the electronic device refrains from identifying the user input as an attention event (e.g., treating the user input as an input other than an attention event, or refraining from processing the erroneous user input). The above-described methods of detecting and recording the detection of various user attention events enable the electronic device to present information regarding how frequently a user interacts with the electronic device, thereby simplifying the interaction between the user and the device to enhance the usability of the device (e.g., by conveying usage information in a manner that is meaningful to the user), as well as reducing power usage and improving the device's battery life by enabling the user to use the device more quickly and efficiently (e.g., by encouraging the user to use their phone less frequently and therefore more efficiently).

In some embodiments, the visual indication of the first corresponding usage metric includes a visual indication of the number of detected events of interest during a limited use mode (e.g., "device downtime" or "bedtime") of the electronic device (798-26), as shown in FIG. 6U (e.g., the electronic device displays a metric indicating the number of times the electronic device detected user-attention events during the limited use mode). The limited use mode described herein is optionally the same as or similar to the limited use mode 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 frequently the user interacts with the electronic device during the limited time, thereby simplifying the interaction between the user and the device to enhance usability of the device (e.g., by conveying usage information in a manner that is meaningful to the user), as well as reducing power usage and improving battery life of the device by allowing the user to use the device more quickly and efficiently (e.g., by encouraging the user to use the user's phone outside of the limited mode and therefore more efficiently).

6K-L, prior to displaying the dashboard user interface, the electronic device presents (798-28) an indication of a notification associated with the dashboard user interface (e.g., a daily or weekly “digital health” notification), which includes an affordance (e.g., a soft button or other user interface element) selectable to display the dashboard user interface. In some embodiments, the notification includes a visual indication of device usage over the past day, past week, or another period of time. The indication is optionally selectable to display the dashboard user interface. The dashboard user interface is optionally displayed in response to detecting user input selecting the affordance (e.g., the electronic device presents a “digital health” notification that includes a summary of one or more usage metrics at the start of the week or start of the day). In some embodiments, a weekly “digital health” notification is presented at the start of the week, including a summary of overall device usage for the previous week. The summary optionally includes a visual indication of the amount of time the device was used to present information using each of the multiple applications and/or categories of applications, and an indication comparing overall device usage to the previous week (e.g., percent above or below average weekly usage). In some embodiments, a daily "digital health" notification is presented at the start of the day, including a summary of overall device usage for the previous day. The summary optionally includes a visual indication of the amount of time the device was used to present information using each of the multiple applications and/or categories of applications, and an indication comparing overall device usage to the previous day (e.g., percent above or below average daily usage). Other time intervals are possible (e.g., monthly usage, etc.). The above-described method of displaying a dashboard user interface in response to selection of the "digital health" notification allows the electronic device to prompt the user to review the metrics of the user's usage and present more detailed metrics from the notification including a summary of the metrics, thereby simplifying the interaction between the user and the device to enhance the usability of the device (e.g., by presenting the summary of usage as a notification and more details in response to user input to present more details regarding usage), 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, prior to displaying the dashboard user interface, as shown in FIGS. 6E-I, the electronic device displays a widget user interface (798-30), the widget user interface including one or more widgets, each of which includes 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 includes a user interface object (e.g., a window) including text and/or images associated with the application (e.g., a weather widget that displays the current temperature, a sports widget that displays scores for live events, a news widget that displays recent event headlines, and/or any user interface object that displays content associated with the application)). In some embodiments, the content of the widget corresponding to the application is dynamically updated by the application. The one or more widgets optionally include a metric widget associated with the dashboard user interface (e.g., a widget associated with a digital health dashboard and/or digital health settings). In some embodiments, the metric widget includes a visual indication of a corresponding usage metric (e.g., a bar chart showing the total time the electronic device was used to present information over the past week using each of a plurality of applications or groups of applications) (798-32), as shown in FIGS. 6E-I. In some embodiments, other time periods and/or operations are possible. In some embodiments, the widget further includes an indication comparing usage over a period of time to previous usage (e.g., a percentage value above or below average usage for a week). In some embodiments, as shown in Figures 6E-6I, the metric widget is selectable to display a dashboard user interface (798-34) (e.g., the widget expands to include more metrics, such as a second metric, or the electronic device presents the dashboard user interface in a settings application), which is optionally displayed in response to detecting a user input selecting the metric widget (798-36) (e.g., the dashboard user interface is displayed in response to a user selecting the metric widget or expanding the metric widget). The widget user interfaces described herein are optionally the same as 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 a selection of a metric widget allows the electronic device to present one of the usage metrics (e.g., a first usage metric) in a higher-level user interface (e.g., a widget user interface) and provide a way for the user to input an input to view a more detailed metric while viewing the metric widget, thereby simplifying the interaction between the user and the device to enhance the usability of the device (e.g., by presenting a usage summary as a widget and more details in response to a user input to present more details regarding the usage), 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, as shown in FIGS. 6DD-6EE, prior to displaying the dashboard user interface, the electronic device displays a usage settings user interface for the electronic device (e.g., a settings user interface associated with device usage, or a “digital health” settings user interface that is a settings user interface for the operating system of the electronic device and not a settings user interface 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 include setting one or more time intervals for operating the device in a limited usage mode (e.g., device downtime or bedtime mode), usage limits (e.g., “allowances”) for one or more applications, categories of applications, or overall device usage, one or more whitelisted applications (e.g., phone, messaging, maps, etc.) or application features (e.g., receiving incoming or outgoing calls from specific contacts), and/or 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., a bar chart showing the total time the electronic device was used to present information over the past week using each of a plurality of applications or groups of applications), as shown in FIG. 6DD. In some embodiments, other time periods and/or operations are possible. In some embodiments, the widget further includes an indication comparing usage over a period of time to previous usage (e.g., a percentage value above or below average usage over the week). The user settings user interface optionally includes an affordance (798-42) selectable to display a dashboard user interface (e.g., a selectable image or selectable text that, when selected, causes the electronic device to update the display to present the dashboard user interface). In some embodiments, the visual indication of the first usage metric is selectable to display a dashboard user interface, as shown in FIGS. 6DD-6EE. In some embodiments, the dashboard user interface is displayed in response to receiving user input selecting the affordance (e.g., a user touches a location on a touchscreen where the visual indication of the fourth usage metric is displayed) (e.g., a settings application of the electronic device includes a usage settings user interface for modifying one or more usage settings of the electronic device). The usage settings user interface optionally includes a visual indication of the fourth usage metric selectable to display the dashboard user interface. In some embodiments, the fourth usage metric is an amount of time the device has been used over a given period (e.g., today, this week, etc.) to present information about each of a plurality of applications or categories of applications used during the period. The visual indication optionally further indicates a usage limit or "allowance" configured for the electronic device that defines a maximum amount of time the electronic device can present information without one or more usage restrictions. The above-described method of displaying a dashboard user interface in response to a selection of a visual indication within a usage settings user interface allows an electronic device to simultaneously present metrics of usage of the electronic device and one or more usage settings, and provide a way for a user to input input to view more detailed metrics while viewing the usage settings, thereby simplifying the interaction between the user and the device to enhance usability of the device (e.g., by presenting a summary and more details of usage within the settings user interface in response to a user input to present more details regarding usage), as well as allowing a user to use the device more quickly and efficiently, thereby reducing power usage and improving battery life of the device.

In some embodiments, the usage settings user interface includes one or more visual indications of one or more requests received (e.g., via a network connection (e.g., wired or wireless connection)) from the other electronic device (798-44), as shown in FIG. 6B. In some embodiments, the electronic device and the other electronic device are associated with a group or family account to modify one or more usage restrictions implemented on the other electronic device (e.g., a request to remove or increase an overall usage limit (e.g., "allowance") for the other electronic device, remove or increase an application or application category specific usage limit (e.g., "allowance") for the other electronic device, or allow the other electronic device to exit a restricted mode of operation (e.g., device downtime or "bedtime" mode), as shown in FIG. 6C. In some embodiments, the visual indications each include a displayed image or displayed text indicating the request. In some embodiments, the text indication simply indicates that a request has been received, or includes details regarding the request (e.g., the identity of the other device, the particular restrictions associated with the request, the identity of the user making the request). The visual indication can optionally be selected 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 allows the electronic device to simultaneously present the request and usage metrics to provide a way for the user to change the usage settings of the other device, thereby simplifying the interaction between the user and the device to enhance usability of the device (e.g., by presenting usage settings for the electronic device and the other electronic device in one user interface), as well as allowing the user to use the device more quickly and efficiently, thereby reducing power usage and improving battery life of the device.

In some embodiments, the electronic device and one or more other electronic devices are associated with a user group account (e.g., a family sharing group) as shown in FIG. 6B (798-46). In some embodiments, the electronic devices associated with the user group account can share access to files (e.g., documents, photos, etc.) and applications (e.g., if a user in the user group account purchases and downloads an application, other electronic devices can download the application without separately purchasing it). The user group account optionally includes a parent user and a child user, and the electronic device associated with the parent user can control one or more settings (e.g., content, privacy, usage, and other settings) of one or more devices associated with the child user. The usage settings user interface, as shown in Figures 6V-6W, optionally includes one or more affordances (e.g., selectable text or images) associated with the one or more other electronic devices (798-48), where the one or more affordances are selectable (e.g., via touch input, mouse input, keyboard input, voice input, etc.) to update the dashboard user interface to stop displaying a visual indication of usage metrics associated with the electronic device (798-50) and to display one or more visual indications of one or more usage metrics (e.g., one or more usage metrics associated with the other electronic device) associated with the selected affordance (e.g., present information on the other electronic device, receive notifications on the other electronic device, detect user attention events on the other electronic device, etc.). In some embodiments, a parent can view the dashboard user interface for each of the child's devices to monitor usage of the child's devices and set one or more usage restrictions (e.g., usage limits (e.g., "allowances")) or a time when the child's device will enter a restricted usage mode (e.g., device downtime or "bedtime"). The electronic device optionally determines what permissions (e.g., to view metrics and/or set usage limits and restricted operating periods) to grant to each user account based on the classification of the user account associated with the electronic device (e.g., as parent, child, etc.) or options selected when the device was set up. In some embodiments, the electronic device displays, in a setup user interface, usage metrics (e.g., total device usage or screen time) associated with each electronic device associated with the user group account. Optionally, each parent device displays metrics associated with each of the child devices, but the child devices optionally do not display metrics associated with any other devices associated with the user group account, and 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 in a user group account allows an electronic device to provide easy access to usage information regarding multiple devices in a user group, thereby simplifying the interaction between a user and the device to enhance usability of the device (e.g., by presenting a settings user interface through which a user can change one or more usage settings of the other devices), as well as allowing a user to use the device more quickly and efficiently, thereby reducing power usage and improving battery life of the device.

In some embodiments, the usage settings user interface includes a selectable affordance for deleting usage data about the electronic device (e.g., data about device usage such as time or number of times to present information, receive notifications, detect user attention events, etc., in some embodiments, deleting all usage data, thereby resetting metrics of usage of the electronic device) as shown in FIG. 6A (798-54). In some embodiments, the method further includes receiving user input with one or more input devices selecting the selectable affordance for deleting usage data (798-56) (e.g., receiving a touch at a location on a touchscreen where the affordance is displayed, receiving a selection of the affordance with a mouse or keyboard input, etc.), and deleting the usage data in response to receiving the input (798-58). The above-described method of presenting an option to delete all usage data allows the electronic device to reset usage metrics upon a user request to do so, thereby simplifying the interaction between the user and the device to enhance usability of the device (e.g., by presenting usage metrics showing only data collected after data has been deleted), as well as allowing the user to use the device more quickly and efficiently, thereby reducing power usage and improving the device's battery life.

In some embodiments, the usage settings user interface includes a selectable affordance to stop recording usage data about the electronic device (e.g., data about device usage such as time or number of times to present information, receive notifications, detect user attention events, etc.) (798-60), as shown in FIG. 6A. In some embodiments, when data collection is stopped, the usage metrics stop updating but are retained in their current state. In some embodiments, the method further includes receiving user input with one or more input devices selecting the selectable affordance to stop recording usage data (798-62) (e.g., receiving a touch at a location on a touchscreen where the affordance is displayed, receiving a selection of the affordance with a mouse or keyboard input, etc.), and stopping recording usage data about the electronic device in response to receiving the input (e.g., 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 simplifying the interaction between the user and the device to enhance usability of the device (e.g., by presenting usage metrics that exclude user-defined time periods), as well as allowing the user to use the device more quickly and efficiently, thereby reducing power usage and improving the device's battery life.

In some embodiments, the electronic device requests authentication credentials (798-66) to display a dashboard user interface or to change settings associated with device usage (e.g., a passcode that is different from a passcode for unlocking the electronic device or a passcode for logging into a user account on the electronic device) to set or change one or more usage settings of the electronic device, as shown in Figures 6Y-6CC (e.g., the electronic device receives user input at one or more input devices selecting a selectable affordance to request a passcode (e.g., receiving a touch at a location on a touchscreen where the affordance is displayed, receiving a selection of the affordance with mouse or keyboard input, etc.). In some embodiments, in response to receiving the input, the electronic device presents a user interface for setting a passcode (e.g., the electronic device displays text requesting the user to enter a passcode for usage data and a soft keypad for entering the passcode). While a passcode is required (e.g., in response to setting or activating a passcode), the electronic device optionally receives user input with one or more input devices to select one of the selectable affordances to display a settings user interface for modifying settings associated with device use (e.g., receiving a touch at a location on a touchscreen where the affordance is displayed, receiving a selection of the affordance with a mouse or keyboard input, etc.). In response to the user input, the electronic device optionally presents a prompt to enter a passcode (e.g., displaying or speaking a message indicating that a password is required to modify settings related to device use). Optionally, the device displays a soft keypad on which the user can enter the password. Pursuant to a determination that the entered passcode matches the passcode (e.g., the user enters a correct passcode), the electronic device optionally presents a usage settings user interface with functionality for modifying one or more of the settings. Pursuant to a determination that the entered passcode does not match the passcode (e.g., the user enters an incorrect passcode), the electronic device optionally refrains from presenting a usage settings user interface with functionality for modifying one or more of the settings (e.g., without the correct passcode, the electronic device does not allow the user to modify settings related to device use). Optionally, the device presents an indication of the current settings (e.g., one or more usage limits or an indication of the period during which the device will operate in a restricted use mode). The above-described method of presenting an option to require a password to change one or more settings associated with device use allows the electronic device to prevent unauthorized modification of one or more settings associated with device use, thereby simplifying the interaction between the user and the device to enhance usability of the device (e.g., allowing changes to be made on the electronic device in response to a correct passcode), as well as allowing the user to use the device more quickly and efficiently, thereby reducing power usage and improving battery life of the device.

In some embodiments, the usage settings user interface includes one or more affordances (798-70) selectable to change settings associated with parental guidance ratings of content (e.g., settings limiting access to content (e.g., applications, music, videos, etc.) having a particular parental guidance rating) and one or more affordances (798-72) selectable to change settings associated with data privacy (e.g., settings limiting sharing of specified types of data (e.g., location, contacts, calendar data, tips, photos, wireless connections, microphone, etc.) as shown in FIG. 6A) (798-68). The above-described method of simultaneously displaying parental guidance settings and data privacy settings and usage settings allows an electronic device to present related settings in a sharing user interface, thereby simplifying user-device interaction to enhance device usability (e.g., presenting similar settings together), as well as allowing a user to use the device more quickly and efficiently, thereby reducing power usage and improving device battery life.

It should be understood that the particular order described for the operations in FIGS. 7A-7S is merely illustrative, and the order described is not intended to indicate that the operations are the only order in which they may be performed. Those skilled in the art will recognize various ways to reorder the operations described herein. In addition, it should be noted that other process details described herein with respect to other methods described herein (e.g., methods 900, 1100, 1300, and 1500) are also applicable in a similar manner to method 700 described above with respect to FIGS. 7A-7S. 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 have one or more of the characteristics of the usage metrics dashboard user interface, usage metrics, notification metrics, device pickup metrics, usage limit settings, etc. described herein with reference to other methods described herein (e.g., methods 900, 1100, 1300, and 1500). For the sake of brevity, these details will not be repeated here.

The operations in the information processing method described above are optionally performed by running one or more functional modules in an information processing device, such as a general-purpose processor (e.g., as described in connection with FIGS. 1A-1B, 3, 5A-5H) or an application specific chip. Additionally, the operations described above with reference to FIGS. 7A-7S are optionally performed by the components shown in FIGS. 1A-1B. For example, displaying operations 702, 798-30, and 798-38 and receiving operations 714, 724, 798-56, and 798-62 are optionally performed by event sorter 170, event recognizer 180, and event processor 190. Event monitor 171 of event sorter 170 detects contacts on touch screen 504, and event dispatcher module 174 delivers the event information to application 136-1. Each event recognizer 180 of application 136-1 compares the event information to a respective event definition 186 to determine whether a first contact at a first location on the touch screen corresponds to a predefined event or sub-event, such as a selection of an object on a user interface. When a corresponding predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the 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, event handler 190 accesses a corresponding GUI updater 178 to update what is displayed by the application. Similarly, it will be clear to one skilled in the art how other processes can be implemented based on the components illustrated in FIGS. 1A-1B.
Application and Category Usage Limits

A user interacts with an electronic device in many different ways, including using applications accessible on the device. In some situations, it is difficult for a user to monitor and limit the use of a particular application for a particular period of time. The embodiments described below provide a method for an electronic device to enforce a usage limit to determine that a usage limit has been reached when a limiting criterion for a particular application or category of applications is met, such as reaching an application usage limit associated with the particular application, thereby limiting the user's use of the particular application that the user wishes to limit. Setting a usage limit on an electronic device for a particular application or category of applications allows the electronic device to efficiently limit the user's use of a particular device operation and provides a simple way for the user to set such a usage limit, thereby making device use more efficient (e.g., the user does not need to monitor his or her own device usage, thus reducing input provided by the user to the device (e.g., input to otherwise monitor the user's usage)). For example, with the understanding that a usage limit has been set, the user can use the restricted operation 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 the restricted operations, 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, thereby reducing power usage and improving the device's battery life. It is understood that people use devices. When a person uses a device, that person is optionally referred to as the user of the device.

8A-8NNN illustrate example ways in which usage limits may be set, configured, or implemented on an electronic device in accordance with 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. 9A-9K.

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

8B-8T illustrate an exemplary method for setting and defining usage limits on device 500, according to an embodiment of the present disclosure. In FIG. 8B, a touch object (e.g., a user's finger, stylus, hovering input object, hovering input device, etc.) selects Settings application 446 from home screen 802 (e.g., by providing contact 803). It is understood that contact 803 and the 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 GUI is not limiting. The disclosed methods can be performed by displaying GUI objects and text differently than shown without departing from the scope of the present disclosure.

In FIG. 8C, in response to selection of the settings application, a settings user interface is displayed and contact 803 selects (e.g., by tapping) an affordance associated with digital health settings 804. In response to selection of digital health affordance 804, a message 806 is displayed on the electronic device asking if the user wants to perform an initial usage limit setup (e.g., because usage limits have not yet been set up on device 500), as shown in FIG. 8D. Message 806 includes an affordance to perform usage limit setup (e.g., "Continue" 808a) and an affordance to forgo usage limit setup (e.g., "Later" 808b). The user proceeds with usage limit setup by selecting "Continue" 808a at 803. In some embodiments, the user optionally forgoes the initial usage limit setup by not continuing with message 806 (e.g., by selecting "Later" 808b, returning to home screen 802).

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

FIG. 8F illustrates an exemplary usage limit setup user interface 812 for setting usage limits for one or more applications or categories, optionally displayed by device 500 in response to selection of “Yes” 810a in FIG. 8E. The exemplary usage limit setup user interface includes a number of selectable categories of applications (e.g., “All Apps & Categories” 814a, “News” 814b, “Gaming” 814c, “Mail” 814d, “Social Media” 814e, “Streaming” 814f). In some embodiments, the setup user interface includes selectable applications, thereby allowing a user to set usage limits for individual applications. In this manner, a user may select one or more categories of applications, or one or more individual applications, for which the user wishes to limit usage.

In FIG. 8F, example applications associated with each category of applications are displayed under each corresponding category (e.g., "Social App A," "Social App B," and "Social App C" under the "Social Media" category 814e). 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., an overall "screen time" limit). In some embodiments, the user can set usage limits for applications and categories of applications that the user selects. The user can forgo the initial usage limit setup by leaving the setup user interface (e.g., by selecting "Abort" 816b, by returning to the home screen 802, by not selecting any applications or categories).

Although the usage limit setup user interface is accessed as shown in the figure, it is understood that the usage limit setup user interface can optionally be accessed in a manner different than the illustrated embodiment without departing from the scope of this disclosure. Although specific applications and categories are shown in the figure, it is understood that the specific applications and categories are merely exemplary and that different applications or categories can optionally appear on the usage limit setup user interface without departing from the scope of this disclosure.

8G-8J illustrate an exemplary method of selecting a category of applications and selecting applications associated with the selected category for which the user wishes to limit usage. In FIG. 8G, the user selects (e.g., by contact 803) a category of applications (e.g., social media category 814e to set a usage limit for that category). In some circumstances, the user selects more than one category of applications to set a usage limit for those combined categories or to set a usage limit for each of those categories. In some examples, the user does not select a category of applications. In some examples, the selection of "all apps and categories" optionally selects all applications and categories of applications on the electronic device.

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

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 the deselected application is provided even after a usage limit associated with the category to which the application belongs has been reached (e.g., because the deselected application is a "whitelist" application, described in more detail below). Deselecting an application (e.g., social media application B 820b) optionally causes it to no longer be restricted by a corresponding usage limit (e.g., the usage limit of the social media category). That is, the whitelist application (e.g., social media application B 820b) is optionally accessible after a usage limit associated with the whitelist application (e.g., the social media category) has been reached.

In some embodiments, use of a non-whitelisted application counts toward a 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 social media category usage limit is reached. Use of social media application A prior to the social media category usage limit being reached optionally counts toward the social media category usage limit.

In FIG. 8I, once the desired set of applications (e.g., social media applications A 820a and C-E 820c-820e) have been selected and restricted (e.g., restricting access to the selected set of applications after a usage limit associated with the selected category is reached) for the currently selected category (e.g., social media), the user confirms the set of applications (e.g., by selecting "Done" 822 in contact 803) and proceeds to the next setup user interface.

In FIG. 8J, a usage limit setup user interface 812, optionally displayed by device 500 in response to selection of "Done" 822 in FIG. 8I, displays the applications and/or categories selected to be enforced with one or more corresponding usage limits (e.g., social media 814e). After a desired set of applications to be restricted for the social media category is selected, the applications displayed under the social media category are updated to display some or all of the applications selected on the category usage setup user interface 818, as shown in FIG. 8J. In some embodiments, if the names of the selected applications exceed the amount of space under the category, some of the selected applications are displayed followed by "other". Applications displayed under other categories (e.g., categories not selected) optionally do not update. Once all desired applications and categories have been selected and enforced with one or more corresponding usage limits, the user proceeds to the next user interface (e.g., by selecting "Add" with contact 803).

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

In FIG. 8K, a selection of "Customize Days" via 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 (e.g., 1 hour) are defined for different days of a week (e.g., 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 time period. After the customized usage limits are defined, the user selects "Done" 838 to proceed to the next user interface.

FIG. 8M illustrates a category usage limit customization user interface 824 that is displayed after a customized usage limit has been set up (e.g., after selecting "Done" 838 in FIG. 8L). After a customized usage limit has been set up, under "Customize Days" 826, the time periods for which the customized usage limit will be in effect are displayed. When the user selects "Add" 830, the customized usage limit is added to the social media category usage limit settings. For example, as shown in FIG. 8M, a 1 hour usage limit is in effect on Monday, Wednesday, and Thursday. A default usage limit of 2 hours is in effect on Sunday, Tuesday, Friday, and Saturday.

After setting the usage limits in FIG. 8M, the device 500 optionally displays a digital health passcode setup user interface 840 to ensure that the usage limits have been set, as shown in FIG. 8N. In some embodiments, after the initial usage limit settings are set, the electronic device displays the digital health passcode setup user interface 840 to prompt the user to enter a passcode associated with the digital health settings (e.g., the usage limit settings) on a passcode entry user interface 842. In some embodiments, the passcode is different from the electronic device's general passcode (e.g., a passcode for unlocking the device in general) to prevent unauthorized access to the digital health settings on the device 500 (e.g., by a child who knows the parent's device passcode). Although a four-digit numeric passcode is prompted in the figure, it is understood that different types of authentication credentials are optionally used to secure the 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. The limit setting user interface 844 is described in more detail with reference to FIGS. 6A-6UU and 7A-7S. Use of applications in categories associated with a usage limit is optionally indicated on a usage bar 848. Categories with associated usage limits (e.g., "Social Media") are displayed under "App Limit" 846. For example, in FIG. 8O, there is no use of the social media category, and therefore the usage bar 848 indicates that applications in the social media category are not being used. Selection of "App Limit" 846 optionally causes the display of the application limit user interface of FIG. 8P, in which application usage limit settings can be changed.

FIG. 8P illustrates an application limits user interface 850. Usage limit categories added during initial setup (e.g., “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 limits toggle switch 856. As illustrated, the electronic device enforces the defined usage limits when the button is toggled “on”. Conversely, the electronic device does not enforce the 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 not enforced. The defined usage limits will, optionally, be enforced upon subsequent activation of the application limits (e.g., by toggling the app limits toggle switch 856 “on”). In some embodiments, application usage is tracked and retained (e.g., application usage contribution is not reset for subsequent activation of application limits) during reactivation of application limits (e.g., by toggling app limits toggle switch 856 “off” for a period of time and then toggling app limits toggle switch 856 “on”). In some embodiments, application usage is not tracked or retained (e.g., application usage contribution is reset for subsequent activation of application limits). A user may add additional application or category usage limits by selecting “Add Limit” 854 as shown in FIG. 8P. In some examples, selection of “Add Limit 854” optionally causes the electronic device to display a user interface similar to usage limit setup user interface 812. For simplicity, it is understood that adding one or more application or category usage limits is similar to that described in FIGS. 8F-8M.

8Q illustrates the usage limits user interface 850 after additional application usage limits (e.g., "Games A" 852c and "Streaming App B" 852g) and category usage limits (e.g., "All" 852b, "Games" 852d, "Streaming" 852e, "Streaming and Social Media" 852f) have been added. "All" 852b is an overall usage limit for the electronic device associated with all applications and categories on the electronic device (e.g., an overall "screen time" limit). "Streaming and Social Media" 852f is a joint category usage limit. The joint category usage limit enforces the use of applications associated with the joint category. For example, use of streaming or social media applications is optionally enforced by the "Streaming and Social Media" joint usage limit 852f.

The electronic device optionally enforces concurrent usage limits. For example, a 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 a social media application associated with a usage limit (e.g., social media application A) contributes to both concurrent usage limits. In some embodiments, the more conservative limit of the concurrent usage limits is enforced. For example, if there are two hours remaining against the social media usage limit and three hours remaining against the streaming and social media usage limit, the use of the social media application is optionally limited by the more conservative social media usage limit (i.e., after two hours of use of the social media application). As another example, if there are two hours remaining against the social media usage limit and one hour remaining against the streaming and social media usage limit, the use of the social media application is optionally limited by the more conservative streaming and social media usage limit (i.e., after one hour of use of the social media application).

FIG. 8R illustrates a category usage limit setup 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 (e.g., social media applications A 820a and C-E 820c-820e) are displayed on the user interface 858. In some embodiments, the user redefines the applications to be restricted by selecting or deselecting applications on the category usage limit setup 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. 8R, which optionally results in a renaming of the social media category limit, as shown in FIGS. 8S and 8T.

Specifically, in FIG. 8S, in response to changing the name 860 of the category usage limit (e.g., from "Social Media" to "John's Fun"), the updated name is displayed on the user interface 858. After the desired updates to the category usage limit settings have been made, the user saves the updated settings and returns to the application limits user interface 850, as shown in FIG. 8T, by selecting "Done" 822. FIG. 8T illustrates the application limits user interface 850 after the category usage limit settings have been updated. In response to renaming the previous social media category 852a to "John's Fun", the application limits user interface 850 displays the updated name of category 852a (e.g., "John's Fun").

8U-8EE illustrate example methods for displaying a representation of an application subject to various constraints in accordance with an embodiment of the present disclosure.

In FIG. 8U, touch screen 504 displays home screen 802 when restriction criteria are not met on device 500 (e.g., usage limits for any application or category of application have not been reached). In some embodiments, restriction criteria are met when usage limits for a given application or category of application have been reached. In some embodiments, usage restriction criteria are met during one or more windows of time associated with a limited usage mode, as described with reference to method 1100. In FIG. 8U, home screen 802 includes application icons 424, 426, 428, 432, 434, 436, 440 (e.g., associated with social media application A), 442 (e.g., associated with social media application B), 446, 448, 450, and 452 for launching or otherwise displaying different applications on device 500, as described above in FIG. 4A. As shown in FIG. 8U, one or more of the application icons optionally include a notification indicator 864 that notifies 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 touch screen 504 while home screen 802 is displayed, causing device 500 to display search user interface 866 when restriction criteria are not met (e.g., usage limits have not been reached) on device 500. Search user interface 866 is, optionally, a user interface of the operating system of device 500 in which 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 searched. The 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 the device 500, an "app suggestions" user interface 870a for displaying applications suggested to the user by the operating system of the device 500 (e.g., suggesting commonly used applications, recently used applications, favorite applications, currently running applications), and widgets 870b and 870c (e.g., user interface objects or windows containing text, image(s), and/or any other content associated with and updated by a corresponding application, such as social media applications A and B) corresponding to applications installed on the device 500. As shown in FIG. 8W, social media applications A and B are included in the "app suggestions" and their corresponding widgets are displayed by the device 500 when the restriction criteria associated with those applications are not met on the device 500.

In FIG. 8X, a user enters the search term "social media" into text field 868 when the restriction criteria are not met (e.g., the usage limit has not been reached) on device 500. In response to the search term "social media" being 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, device 500 displays a link 874a to a social media application "Social App A" installed on device 500, a link 874b to a social media website "Social App A" that is a website related to the "Social App A" application, and links to two social media applications available for download from an application repository (e.g., App Store), a link 874c to a "Social App F" application and a link 874d to a "Social App G" application.

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

8Y-8Z, a vertical swipe of contact 803 is detected on touch screen 504 while home screen 802 is displayed, causing device 500 to display notification history user interface 878 of FIG. 8Z when a limiting criterion is met on device 500 (e.g., a social media category usage limit is reached). Notification history user interface 878 includes notifications 880a-b associated with notifications of applications on the device. In some embodiments, in response to a determination that a usage limit has been reached, the appearance of the notification of the application associated with the usage limit is updated (e.g., the notification is grayed out) to indicate that the associated application is limited. In some embodiments, the notification having the updated appearance is not selectable. In some embodiments, in response to a determination that a usage limit has been reached, the notification of the application associated with the usage limit is not displayed (e.g., suppressed) on notification history user interface 878. When one or more notifications are suppressed on notification history user interface 878, electronic device 500 optionally displays one or more other notifications associated with non-restricted applications in place of the notifications associated with the restricted applications. For example, in FIG. 8Z, notification 880a associated with social media application A is grayed out (or optionally not displayed) in response to a determination by device 500 that the social media usage limit category has been reached, while notification 800b associated with a music application indicates that access to the music application is not restricted.

Such changes in the display of the representation associated with the restricted application are also performed by device 500 in other user interfaces. For example, in FIGS. 8AA-BB, a horizontal swipe of contact 803 is detected on touch screen 504 while home screen 802 is displayed, which causes device 500 to display search user interface 866 of FIG. 8BB when a restriction criteria is met on device 500 (e.g., a social media category usage limit is reached). Search user interface 866 is substantially similar to the user interfaces described in FIGS. 8V-W.

The "App Suggestions" user interface 870a displays applications suggested to the user by the operating system of device 500 (e.g., suggests commonly used applications, recently used applications, favorite applications, currently running applications). In some embodiments, when a usage limit (e.g., a social media category usage limit) is reached, the appearance of the suggested applications that are restricted is updated to indicate their restricted status (e.g., the icon is grayed out, icon 440 for social media application A is grayed out). In some embodiments, when a usage limit is reached, the application associated with the usage limit does not appear on the "App Suggestions" user interface 870a, and in some embodiments is replaced by a representation of another application for which the restriction criteria has not been met.

In some embodiments, when a usage limit (e.g., a social media category usage limit) is reached, the appearance of widgets corresponding to applications associated with the usage limit are updated to indicate their restricted status (e.g., the widgets are grayed out, widget 870b corresponding to social media application A is grayed out), as shown in FIG. 8BB. In some embodiments, when a usage limit is reached, widgets corresponding to applications associated with the usage limit do not appear on the search user interface 866. When application icons or widgets are suppressed on the search user interface 866, the electronic device 500 optionally displays one or more other icons or widgets associated with non-restricted applications in place of notifications associated with the restricted applications. For example, in FIG. 8BB, widget 870b associated with social media application A is grayed out (or optionally not displayed) in response to a determination by device 500 that a social media usage limit category has been reached, while widget 870c associated with whitelisted social media application B (e.g., an application not selected on the usage limit setup user interface 818 of FIG. 8I) indicates that access to social media application B is not restricted.

In FIG. 8CC, a user enters the search term “social media” into text field 868 when a restriction criterion is met on device 500 (e.g., a social media category usage limit is reached). In response to the search term “social media” being entered into text field 868, device 500 displays various search results related to the search term “social media” in search user interface 866. During this time, access to the application associated with the usage limit being reached is restricted. For example, when the social media category usage limit is reached, device 500 displays link 874a with an updated appearance (e.g., social media application A’s icon is grayed out) to a social media application “Social App A” installed on device 500, and link 874b with an updated appearance (e.g., social media application A’s icon is grayed out) to a social media website “Social App A” that is a website related to the “Social App A” app. In some embodiments, the updated link appearance indicates that social media application A and the social media website corresponding to social media application A are restricted at the time of the search (e.g., when the social media category usage limit is reached). In some embodiments, when a social media category usage limit has been reached, restricted social media category applications (e.g., non-whitelisted social media category applications, social media applications A and C-E) do not appear in search results. When one or more links are suppressed on the search user interface 866, the electronic device 500 optionally displays one or more other links associated with non-restricted applications in place of notifications associated with the restricted applications. For example, in FIG. 8CC, link 874b associated with social media application A is grayed out (or optionally not displayed) in response to a determination by device 500 that a social media usage limit category has been reached, while links 874c associated with non-installed social media application F and social media application G indicate that installation of these applications is not restricted.

8DD illustrates a web browser user interface 882 in which a restriction criteria is met on device 500 (e.g., a social media category usage limit is reached). As shown, a user attempts to access a website (e.g., "www.socmeda.com") corresponding to social media application A. In some embodiments, in response to an attempt to access the social media website during a time when the social media category usage limit is reached, content 882-4 of web browser user interface 882 is hidden from the user by device 500, as shown in FIG. 8DD, and a message is displayed by device 500 informing 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 having the same home page URL) is restricted to the user.

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

Figures 8FF-8HH show an example method for installing an application on device 500 in a situation where the restriction criteria for a category associated with the application are met.

FIG. 8FF illustrates 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 icon 440 of social media application A 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 proceed to the App Store.

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

FIG. 8HH illustrates 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, an icon 452 for social media application F is added to the home screen 802. Because the social media category usage limit has been reached and it is determined that social media application F is associated with the social media category usage limit, the icon 452 for social media application F reflects that the application is restricted (e.g., the icon is grayed out, a restriction badge 876b is superimposed on the icon).

FIGS. 8II-8KK illustrate an example method for restricting access to an application pursuant to a determination that the electronic device is in a restricted use mode (e.g., as described in more detail with reference to FIGS. 10A-10AAA and method 1100).

Figure 8II shows the home screen 802 when the usage limit has not yet been reached. In Figure 8JJ, a message 888 (e.g., a notification) is presented and overlaid on the home screen 802. The message 888 indicates that a limited usage mode (e.g., device downtime) will begin in 5 minutes. The 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 period of time (e.g., 5 seconds, 30 seconds, or 1 minute).

FIG. 8KK illustrates the home screen 802 when a bedtime restriction (e.g., limited use mode) is in place but the application usage limit has not been reached. For example, FIG. 8KK illustrates the home screen 802 five minutes after message 888 is optionally presented. When a bedtime restriction is in place, applications selected to be restricted by the bedtime restriction are restricted. In some embodiments, when a bedtime restriction is in place, access to restricted applications is restricted even if the usage limit for those applications has not been reached. For example, when a bedtime restriction is optionally in place, a social media category usage limit has two hours remaining. The bedtime restriction optionally takes precedence over the usage limit setting. That is, when a bedtime restriction is in place, social media category applications and any other non-whitelisted applications are restricted even if the social media category (or other) usage limit has not been reached. The appearance of the restricted application's icon is updated (e.g., the icon is grayed out, a restriction badge 876 is superimposed on the 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 show an example method for providing access to an application by presenting an indication that access to the application is restricted.

8LL shows device 500 displaying home screen 802 when a usage limit has not been reached. FIG. 8MM shows device 500 displaying home screen 802 when a usage limit (e.g., social media category usage limit) has been reached under the "Notification" option of the 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 associated with the limit (e.g., social media application A 440) is updated to indicate that the application is restricted (e.g., the icon is grayed out, a restriction badge 876 is superimposed on the icon). As shown, the user attempts to launch social media application A by selecting social media application A's icon 440 in FIG. 8MM.

In response to an attempt to launch a restricted application (e.g., access to the application is restricted because a usage limit has been reached), device 500 optionally visually obscures home screen 802 (e.g., blurs, grays out, or visually alters home screen) with a restriction notification user interface 890, as displayed in FIG. 8NN. Although restriction notification user interface 890 is displayed in response to an action when the home screen is displayed (e.g., launching an application from the home screen), it is understood that notification user interface 890 may be displayed over any content currently displayed by the device when the usage limit is being reached (e.g., the application's user interface). In some embodiments, device 500 displays description 890-1 indicating that a usage limit associated with the selected application has been reached. In some embodiments, description 890-1 includes a visual indication (e.g., 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 number of icons 890-2. The plurality of icons 890-2 includes application icons (e.g., social media applications A and C-E) associated with the usage limit that was reached (e.g., a social media category usage limit). If the usage limit that was reached was associated with only a single application, then user interface 890 will, optionally, only include an icon for that single application.

The restriction notification user interface 890 of FIG. 8NN includes a "reject" affordance 892. In FIG. 8NN, a selection of the reject affordance 892 is detected (e.g., by a contact 803 detected on the reject affordance 892). In response to the selection of the reject affordance 892, the device 500 stops displaying the reject affordance 892 on the restriction notification user interface 890 and displays the extend affordance 894 and the ignore affordance 896, as shown in FIG. 8OO.

In some embodiments, a user may select an extend affordance 894 to allow the user to access a restricted application beyond the application's usage limit for a predefined or user-defined amount of time (e.g., 5 minutes, 15 minutes, 30 minutes) beyond the usage limit (such that a previously defined usage limit continues to be enforced on future days without changing the actual time set for the usage limit) (e.g., as described below with reference to method 900). In some embodiments, a user may select an ignore affordance 896 to allow the user to forgo enforcement of the usage limit for that particular day (such that a previously defined usage limit continues to be enforced on future days without changing the actual time set for the usage limit) (e.g., as described below with reference to method 900). In some embodiments, the device 500 stops displaying the extend affordance 894 and the ignore affordance 896 after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds) or when the user returns to the home screen 802 (e.g., by tapping on any portion of the limit notification user interface 890 (other than the description 890-1, the extend affordance 894, and the ignore affordance 896), by selecting the home button of the electronic device).

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) optionally does not require the user to enter any authentication (e.g., passcode, biometric authentication) to extend or override the usage limit restriction on that device. As such, in response to selection of the extend affordance 894 or the ignore affordance 896 of FIG. 8OO, the limit notification user interface 890 stops displaying and the user interface of the selected application 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 (e.g., 15 minutes, remainder of the day). When a 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, the user can see or interact with widgets, notifications, and web pages corresponding to the application associated with the extended or ignored usage limit. For example, as shown in FIG. 8PP, in response to selection of the extend affordance of FIG. 8OO, the limit notification user interface 890 stops displaying and the social media application A user interface 898 is displayed. After the limit notification user interface 890 stops displaying, the user has an additional 15 minutes of social media category usage time. In some embodiments, after the limit notification user interface 890 stops displaying and before accessing the selected application, a graphical user interface (e.g., a reset hourglass, such as an animation of hourglass 890-1 reversing and starting again) is presented on the display to indicate that the usage limit has been extended. In some embodiments, usage of the application associated with the reached usage limit is tracked beyond the reached limit (e.g., by extending and ignoring for the remainder 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 the social media usage beyond the usage limit. The user's social media usage beyond the two-hour limit is optionally tracked by the device.

Figures 8QQ-8UU show an example method for providing access to an application on a parentally controlled child device using local authentication with an indication that access to the application is restricted.

8QQ illustrates a parentally controlled device 500A displaying a home screen 802 when a usage limit has not been reached. FIG. 8RR illustrates a device 500 displaying a home screen 802 when a usage limit (e.g., a social media category usage limit) has been 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., the icon is grayed out, a restriction badge 876 is superimposed on the icon). As shown, the user attempts to launch social media application A by selecting social media application A's icon 440 in FIG. 8RR.

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

In FIG. 8SS, a selection of the reject affordance 892 is detected (e.g., by contact 803 detected on the reject affordance 892). In response to the selection of the reject affordance 892, the device 500A stops displaying the reject affordance 892 on the restriction notification user interface 890 and displays the local authentication request affordance 898-2 and the remote authentication request affordance 898-4, as shown in FIG. 8TT.

Under the "Notify and Block" option, a parentally controlled child device (e.g., a device associated with a child on a family account) may prompt the user to enter authorization (e.g., local authorization on the device (e.g., passcode, biometric authentication), remote authorization from a different device (e.g., parent device)) to extend or override the usage limit restriction on that device. For example, as shown in FIG. 8TT, the user selects local authentication request affordance 898-2 to request local authorization (e.g., authorization on parentally controlled child device 500A) for the desired extension of the social media usage limit.

As shown in FIG. 8UU, in response to selection of the local authentication request affordance 898-2 of FIG. 8TT, a passcode entry user interface 842 displayed by device 500A prompts an authorizing user (e.g., a parent) to directly enter authentication. Although a four-digit numeric passcode is shown as being prompted, it is understood that different types of authentication credentials are optionally used to secure the digital health settings (e.g., alphanumeric password, biometric authentication, etc.). In some embodiments, the authenticating passcode for extending or overriding the usage limit is different from the passcode of the electronic device 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, in response to a correctly entered authentication (e.g., correct passcode), the user is granted additional access to the selected application beyond the usage limit (e.g., 15 minutes, remaining in the day). When a usage limit is extended or overridden, 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 overridden. For example, a user may be able to see or interact with widgets, notifications, and web pages that correspond to applications associated with extended or ignored usage limits.

After the request to extend usage beyond the usage limit is authorized, the electronic device operates substantially similarly to an electronic device under the "Notify" option after the usage limit has been extended, as described in FIG. 8PP and its corresponding description.

Figures 8VV-8YY show an example method for providing an indication that access to an application is restricted and providing access to the 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 because a usage limit has been reached), as also shown in Figures 8QQ and 8RR and their corresponding descriptions, the child device 500A optionally visually obscures (e.g., blurs, grays out, or visually alters) the home screen 802 with a restriction notification user interface 890, as displayed in Figure 8VV. The restriction notification user interface 890 is substantially similar to the user interface described in Figure 8NN.

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

Under the "Notify and Block" option, the child device (e.g., a device associated with a child on a family account) requests the user to enter authentication (e.g., local authentication on the device (e.g., passcode, biometric authentication), remote authentication from a different device (e.g., parent device)) to extend or override the usage limit restriction on that device. For example, as shown in FIG. 8WW, the user selects remote authentication request affordance 898-4 to request remote authentication (e.g., authentication on parent device 500B) for the desired extension of the social media usage limit.

For example, as shown in FIG. 8XX, in response to selection of remote authentication request affordance 898-2 on child device 500A of FIG. 8WW, message 898-6 including multiple extension affordances 898-8a through 898-8d is displayed on parent device 500B. As shown in FIG. 8BB, in some embodiments, message 898-6 informs the parent user that a usage limit (e.g., social media category) on the child device (e.g., John Jr.'s device) has been reached and that the child user is requesting 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 remainder of the day, customize the extension, deny the request for extension). The selected extension option is applied to child device 500A. For example, as shown in FIG. 8XX, the parent user selects extension affordance 898-8a to grant the requesting child user an additional 15 minutes beyond the usage limit.

In some embodiments, in response to a selection of one of the extension affordances 898-8a-898-8d, as shown in FIG. 8YY, the passcode entry user interface 842 prompts the authorizing user (e.g., parent) to enter an authorization on a remote authentication device (e.g., parent device 500B). Although a four-digit numeric passcode is shown as being prompted, it is understood that different types of authentication credentials are optionally used to secure the digital health settings (e.g., alphanumeric password, biometric authentication, etc.). In some embodiments, the passcode that authorizes to extend or override the usage limit is different from the passcode of the electronic device 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, in response to a correctly entered authorization (e.g., correct passcode) at the parent device 500B, the child device 500A is granted additional access to the selected application beyond the usage limit. The amount of additional access depends on the selected extension affordance. In some embodiments, no passcode is required to respond to message 898-6. In some embodiments, after the request is authenticated, the child device 500A displays an indication (e.g., a notification) of the outcome of the request (e.g., extend by 15 minutes, extend for the remainder 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 operates substantially similarly to an electronic device under the "Notify" option after the usage limit has been extended, as shown in FIG. 8PP and its corresponding description.

Figures 8ZZ-8CCC show an example method for presenting an indication that access to an application is restricted and providing access to the 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 because a usage limit has been reached), as also described in Figures 8QQ and 8RR and their corresponding descriptions, the child device 500A optionally visually obscures (e.g., blurs, grays out, or visually alters) the home screen 802 with a restriction notification user interface 890, as displayed in Figure 8ZZ. The restriction notification user interface 890 is substantially similar to the user interface described in Figure 8NN.

In FIG. 8ZZ, a selection of the reject affordance 892 is detected (e.g., by contact 803 detected on the reject affordance 892). In response to the selection of the reject affordance 892, the device 500A stops displaying the reject affordance 892 on the restriction notification user interface 890 and displays the local authentication request affordance 898-2 and the remote authentication request affordance 898-4, as shown in FIG. 8AAA.

Under the "Notify and Block" option, the child device (e.g., a device associated with a child on a family account) prompts the user to enter authentication (e.g., local authentication on the device (e.g., passcode, biometric authentication), remote authentication from a different device (e.g., parent device)) to extend or override the usage limit restriction on that device. For example, as shown in FIG. 8AAA, the user selects remote authentication request affordance 898-4 to request remote authentication (e.g., authentication on parent device 500B) for the desired extension of the social media usage limit.

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

8CCC, in response to selection of the message send affordance 898-14 of FIG. 8BBB, the messaging user interface 898-10 updates with the child's request for additional access, optionally represented as a rich message 898-16 to the child's parent. On the device that received the remote authentication request (e.g., parent device 500B), the rich message 898-16 is also displayed on the messaging user interface 898-10. The rich message 898-16 optionally includes a request for additional access from the child user, an accompanying message, and multiple extension 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 remainder of the day, customize the extension, deny the request for extension). Similar to the selection of the extension affordances described in Figures 8XX through 8CCC, the selected extension option is applied to the child device 500A.

In some embodiments, in response to selecting one of the extension affordances 898-18a-898-18d, the authorizing user (e.g., parent) is prompted to enter authorization on a remote authentication device (e.g., parent device 500B) as also described in FIG. 8YY. In some embodiments, the passcode for authorizing to extend or override the usage limit is different from the passcode of the electronic device to prevent unauthorized extension of the usage limit. In some embodiments, in response to a properly entered authorization (e.g., correct passcode) at the parent device, the child is granted additional access to the selected application beyond the usage limit. The amount of additional access depends on the selected extension affordance. In some embodiments, a passcode is not required to respond to message 898-16.

In some embodiments, after the request is authenticated, the child device 500A displays an indication of the result of the request (e.g., a new message on the messaging user interface 898-10, a notification outside of the messaging user interface 898-10) (e.g., extend by 15 minutes, extend for the remainder 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 operates substantially similarly to an electronic device under the "Notify" option after the usage limit has been extended, as described in FIG. 8PP and its corresponding description.

Figures 8DDD-8GGG show an example method for presenting an indication that access to an application is restricted and providing access to the application based on authentication credentials entered into the electronic device.

8DDD illustrates device 500 displaying home screen 802 when a usage limit (e.g., 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 associated with the limit (e.g., social media application A 440) is updated to indicate that the application is restricted (e.g., the icon is grayed out, a restriction badge 876 is superimposed on the icon). As shown, the user attempts to launch social media application A by selecting social media application A's icon 440.

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

For example, a selection of the reject affordance 892 is detected (e.g., by a contact 803 detected on the reject affordance 892). In response to the selection of the reject affordance 892, the device 500 stops displaying the reject affordance 892 on the limit notification user interface 890 and displays the extend affordance 894 and the ignore affordance 896, as shown in FIG. 8FFF.

Under the "Notify and Block" option, devices without parental control (e.g., devices associated with an adult (e.g., not a child) in a family account, or devices not associated with a family account at all (e.g., standalone devices)) will require the user to enter authentication (e.g., passcode, biometric authentication) on the device to extend or override the usage limit restriction. For example, as shown in FIG. 8EEE, the user selects the 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 selecting the extend affordance 894, the passcode entry user interface 842 prompts the user to enter authentication. Although a four-digit numeric passcode is shown as being prompted, it is understood that different types of authentication credentials are optionally used to secure the digital health settings (e.g., alphanumeric password, biometric authentication, etc.). In some embodiments, the passcode that authenticates to extend or override the usage limit is different from the passcode of the electronic device 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, in response to a correctly entered authentication (e.g., correct passcode), the user is granted additional access to the selected application beyond the usage limit (e.g., 15 minutes, remaining in the day).

After the request to extend usage beyond the usage limit is authorized, the electronic device operates substantially similarly to an electronic device under the "Notify" option after the usage limit has been extended, as described in FIG. 8PP and its corresponding description.

Figures 8HHH-8III show an example method for displaying an indication to warn that a usage limit threshold has been reached.

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

Figures 8JJJ-8KKK show an example method for changing usage limit settings on a child device.

8JJJ illustrates a child device application limits user interface 850. 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 a determination that the device is a child device, the electronic device requests authentication (e.g., by providing authentication credentials by entering a passcode on the passcode entry user interface 842) before the social media category usage limit settings can be modified or viewed. Although a four-digit numeric passcode is prompted in the figure, it is understood that different types of authentication credentials are optionally used to secure the digital health settings (e.g., alphanumeric password, biometric authentication, etc.). In some embodiments, the passcode required to modify or view the usage limit settings is different from the electronic device passcode to prevent unauthorized access to the usage limit settings. For example, the authenticating passcode is optionally a digital health passcode, see FIG. 8N.

Figures 8LLL to 8NNN show an example method for changing usage limit settings on a child device from a parent device.

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

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 social media category 852a in FIG. 8LLL, parent device 500B requests authentication (e.g., by providing authentication credentials by entering a passcode on passcode entry user interface 842) before being able to change or view the social media category usage limit settings for child device 500A. Although a four-digit numeric passcode is prompted in the figure, it is understood that a different type of authentication credential is optionally used to secure the digital health settings (e.g., alphanumeric password, biometric authentication, etc.). In some embodiments, the passcode required to change or view the usage limit settings is different from the parent device's passcode 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, a passcode (e.g., alphanumeric password, biometric authentication, etc.) is not 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 is 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 as a parent changes the child's usage limit settings on parent device 500B. After the parent changes the social media usage settings of child device 500A (e.g., the social media category usage limit is changed from 2 hours to 1 hour, as shown in FIG. 8NNN, using the methods described in this disclosure), the parent device displays the child device's application limits user interface 850. The changed usage limit settings (e.g., 1 hour next to social media 852a) are 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 settings of child device 500A, a message 898-20 (e.g., a pop-up notification) is presented on top of home screen 802 to indicate, for example, that the child's social media usage limit settings (e.g., usage limit time, customized usage limit period, adding usage limit, removing usage limit, combination of usage limits) have been changed by the child's parent, as shown in FIG. 8NNN. In some embodiments, the message automatically stops displaying on the child device after a certain period of time (e.g., 5 seconds, 30 seconds, or 1 minute). In some embodiments, depending on the usage setting changes implemented on the parent device 500B, whether those changes are more or less restrictive for the child device 500A (e.g., whether the parent has increased or decreased the child's social media usage limit), notification 898-20 and appropriate details within notification 898-20 are presented on the child device 500A.

9A-9K are flow diagrams illustrating a method 900 for setting and implementing a usage limit (e.g., restricting an application or a category of applications pursuant to a determination that a usage limit associated with the application or category has been reached) according to some embodiments of the present disclosure. The method 900 is optionally performed on an electronic device such as device 100, device 300, or device 500 as described above with reference to FIGS. 1A-1B, 2-3, 4A-4B, and 5A-5H. Some operations of the method 900 are optionally combined and/or the order of some operations 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 usage limits are being reached without the user having to monitor the user's usage. For battery-operated electronic devices, limiting access to applications when one or more usage limits are being reached conserves power and increases the time between battery charges.

In some embodiments, an electronic device in communication with a display and one or more input devices (e.g., a mobile device including a touch screen such as device 500, a computer or tablet computer including one or more of a keyboard, a mouse, a trackpad, and a touch screen, a wearable device such as a smart watch including a touch screen, or a set-top box in communication with a television and an input device (e.g., a remote controller)) receives, via the one or more input devices, a series of one or more inputs (e.g., a usage limit setup for a social media category) that set a usage limit associated with a first category of applications accessible on the electronic device, such as in FIGS. 8A-8M (e.g., a usage limit setup for a social media category). For example, a maximum amount of time (e.g., 1 hour, 3 hours, 12 hours) that can be spent using the device or using the device in a particular way (e.g., using a particular application (e.g., a particular social media application, SMS, phone, a particular travel application, email), a particular category of application (e.g., social media, streaming media, games, travel, work, communication, payments, news), a particular feature of the device (e.g., audio, camera, Bluetooth, Wi-Fi), a particular function of an application (e.g., communicating with one or more contacts stored on the electronic device, etc.) is received on the device via one or more inputs to the device (902). In some embodiments, the maximum amount of time is aggregated over multiple sessions (e.g., periods of time in which the application is used by a user separated by periods of time 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 a network, etc., when the user is not using the device to run the application). In some embodiments, the usage limit is set within a settings user interface of the electronic device (e.g., a settings application for setting usage limits and one or more other settings of the electronic device, such as power settings, display settings, email settings, etc.). In some embodiments, the usage limits are set on a different electronic device that communicates with the electronic device (e.g., via a wireless connection). For example, a parent device is optionally used to set usage limits on a child's device.

In some embodiments, while a usage limit associated with a first category of applications is in effect (904) (e.g., when a usage limit is in effect and usage time of a category of applications associated with the usage limit (e.g., social media category usage time) is being monitored by the electronic device), the electronic device receives a request (906) to launch a first application of the first category of applications (e.g., a request from a user of the electronic device to launch an application (e.g., a particular social media application), a request from an application on the electronic device to perform a particular function on the device, etc.), such as in FIG. 8MM (e.g., attempting to launch a social media application from a home screen when a social media category usage limit has been reached). In some embodiments, an internal timer is associated with the usage time of each particular category of applications or each application. In some embodiments, the associated internal timer starts when the application is launched. In some embodiments, the timer stops when the application is no longer being used (e.g., the application is closed, the device is turned off or paused, the device is disconnected).

In some embodiments, while a usage limit associated with a first category of applications is in effect (904), pursuant to a determination that a restriction criterion for the first category of applications has been met (e.g., determining that a user's time of use of one or more applications (e.g., social media applications) or one or more operations of the first category reaches an established usage limit) including a requirement that a usage limit for the first category of applications be reached in order to satisfy the restriction criterion, the electronic device restricts access to the first application of the first category of applications (908) (e.g., restricting the user's access to one or more applications (e.g., a particular social media application) or operations of the first category (e.g., social media applications in general) (e.g., in response to a selection of social media, social media application A does not launch). In some embodiments, the time of use of the application being requested to launch is compared to the usage limit. In some embodiments, in response to determining that a usage limit for the first category of applications has been reached, the request to launch the application is not launched or displays a dialog indicating that a usage limit has been reached, requesting further user action to complete the launch of the application. In some embodiments, restricting an application from a user is distinct from preventing the application from running. For example, although restricted by the user, a restricted application or operation optionally still runs on the device (e.g., in the background to perform operating system tasks) independent of user input.

In some embodiments, while a usage limit associated with a first category of applications is being enforced (904), pursuant to a determination that a restriction criterion has not been met (e.g., a usage limit for the first category of applications (e.g., social media applications) has not been reached (e.g., determining that the user's usage time of one or more applications or one or more operations of the first category has not reached an established usage limit)), the electronic device provides access to the first application of the first category (910), such as in FIG. 8PP (e.g., the user's access to the application (e.g., a particular social media application) or operations of the first category (e.g., social media applications in general) is not restricted). In some embodiments, the usage time of the application being requested to be launched is compared to the usage limit. In some embodiments, in response to a request to launch the application, the application launches as normal. The application usage limits described herein are, optionally, the same as 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 in that category of applications allows an electronic device to efficiently restrict a user's use of certain device operations and provides an easy way for a user to set such usage limits, thereby making device use more efficient (e.g., the user does not need to monitor his or her own device usage, thus reducing user-provided input to the device (e.g., input to otherwise monitor the user's usage)). With the understanding that a usage limit has been set, the user can use the restricted operations 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 the restricted operations, 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, thereby reducing power usage and improving the device's battery life.

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. 8I (e.g., inclusion on a list (e.g., whitelist) of applications available for use even if a usage limit has been used) (e.g., social media application B is not selected to be enforced by a social media category usage limit). In some embodiments, use of such an application does not count toward the usage limit (e.g., the application belongs to the first category, but use of the application does not count toward the usage limit for that category and/or overall device usage). In some embodiments, the application being requested to launch is compared to a list of applications that are excluded from the usage limit. The above-described restriction exclusion criteria allow the electronic device to determine whether use of an application that belongs to a category having an associated usage limit is excluded from counting toward the usage limit, thereby reducing the burden on the user to manually determine whether a particular application should be excluded (e.g., a particular social media application is optionally excluded because the user needs the application to communicate with family and friends), and also allowing the user to use the device more quickly and efficiently, thereby reducing power usage and improving the device's battery life.

In some embodiments, pursuant to a determination that the restriction criteria for the first category of applications are not met, the electronic device displays a representation (e.g., an icon for the first application) (e.g., an icon, widget, window of the first application in a multitasking view along with other windows of other applications) with a first visual characteristic (e.g., displaying a normal icon for applications installed on the electronic device (e.g., in a home screen of the electronic device) in color, unobscured, etc., when the usage limit has not been reached) (914) (e.g., the appearance of the application icon and a notification badge indicate that the application is not restricted). For example, the electronic device displays one or more application windows associated with the one or more applications (e.g., in a multitasking graphical user interface view), or the electronic device displays one or more icons for launching the application on a home screen of the electronic device).

In some embodiments, pursuant to a determination that the restriction criteria for a first category of applications have been met (e.g., pursuant to a determination that a 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 in FIG. 8Y-FIG. 8EE, with a second visual characteristic different from the first visual characteristic (e.g., changes the appearance of the icon of the application that is not on the whitelist) (916) (e.g., the appearance of the application icon, widget, notification, and website indicates that the application is restricted). In some embodiments, when the usage limit is reached, the electronic device changes the appearance of various aspects of the application that is not included in the application whitelist. For example, the icon for the application that is not included in the whitelist (e.g., an icon on the device's home screen, a particular social media application icon) is shaded when the application is restricted. As another example, a notification badge included on the application icon for the application that is not included in the application whitelist is optionally changed (e.g., the icon of the particular social media application). As another example, in some embodiments, the electronic device has multitasking capabilities. In such an embodiment, the electronic device optionally displays a user interface that displays visual representations of more than one application simultaneously (e.g., a user interface that displays icons from multiple applications simultaneously, screenshots of the current user interfaces of multiple applications simultaneously, etc.). In some embodiments, the representations for restricted applications not on the application whitelist in the multitasking user interface described above are modified by the electronic device (e.g., faded out or shaded, or otherwise modified to appear with different visual characteristics than the representations corresponding to applications included in the application whitelist). The changes in appearance of the application representations described herein are optionally the same as or similar to the changes in appearance of the application representations described with reference to methods 1100 and 1300. The above-described method of selectively modifying the appearance of applications not on the application whitelist when a usage limit is reached allows the electronic device to efficiently and selectively restrict the use of certain applications for certain periods of time by providing an indication of which applications the user does or does not have access to when a usage limit is reached, thereby reducing the use of the electronic device during those periods and, in addition, reducing power consumption and improving the device's battery life.

In some embodiments, displaying the first representation of the first application with the second visual characteristic includes displaying a limited use badge over the first representation, such as over a top right portion of the application icon, that includes an indication that access to the first application is restricted (918) (e.g., a badge having a visual indication of a lock or some other restriction symbol added to the application icon for the first application (and optionally other applications that have reached their usage limit)). In some embodiments, the badge is overlaid on a portion of text associated with the application icon. In some embodiments, the badge is overlaid on at least a portion of the application icon, such as in FIG. 8AA (e.g., the limited use badge replaces the notification badge for social media application A). The above-described method of selectively changing the appearance of the presentation of applications that are not on the application whitelist when a usage limit is reached allows an electronic device to efficiently and selectively restrict the use of certain applications for certain time periods by displaying a limited use badge on applications to which the user does not have access when the usage limit is reached, thereby reducing the likelihood that the user will attempt to access such restricted applications, as well as reducing usage of the electronic device during those time periods, thereby reducing power consumption and improving the device's battery life.

In some embodiments, displaying the first representation of the first application with the first visual characteristic includes displaying the first representation with a notification badge (e.g., an indicator of unread messages, a number of missed calls, etc.) including an indication of notifications received at the first application (e.g., unread messages, a number of missed calls, etc.), such as in FIG. 8U (e.g., a notification badge for social media application A indicates a number of unread messages associated with the application) (920). In some embodiments, displaying the first representation of the first application with the second visual characteristic includes displaying the first representation with a notification badge replaced by a limited use badge (e.g., blurring the indicator or replacing the indicator with a graphic), such as in FIG. 8AA (e.g., the limited use badge replaces the notification badge for social media application A). In some embodiments, the limited use badge described above replaces an indication of a notification badge on the application icon for a non-whitelisted application when a usage limit is reached, as described above. In some embodiments, replacing the indication of the notification badge with the limited use badge described above hides the number of notifications associated with the application such that the number of notifications is no longer displayed on the display. The above-described method of selectively changing the appearance of the representation of an application that is not on the application whitelist when a usage limit is reached allows the electronic device to efficiently and selectively restrict the use of certain applications for certain time periods by replacing the indication of notifications on the application representation with a limited use badge on an application to which the user does not have access when a usage limit is reached, thereby deterring the user from attempting to access restricted applications that have recent notifications by not indicating that such notifications exist, reducing the use of the electronic device during those time periods, and additionally reducing power consumption to improve the device's battery life.

In some embodiments, pursuant to a determination that the first application does not meet one or more restriction exclusion criteria (e.g., non-whitelisted application, the first application is not on the whitelist, the first application is configured to be restricted after a usage limit is reached) and while the first application is being used (e.g., a primary user interface of the first application is displayed on the electronic device or a user is otherwise interacting with the first application (e.g., via a secondary user interface of the first application)), the electronic device aggregates (924) the usage of the first application toward a usage limit associated with a first category of applications (e.g., aggregates a contribution of the usage of non-whitelisted applications to a usage limit associated with a first category of applications that includes the first application).

In some embodiments, pursuant to a determination that the first application meets one or more restriction exemption criteria (e.g., a whitelist application, the first application is on the whitelist, the first application is configured to be accessible after a usage limit is reached, use of the application for whitelist purposes (e.g., a calling app or messaging app used to communicate with a parent)) and while the first application is being used, the electronic device forgoes counting the use of the first application toward the usage limit associated with a first category of application (926) (e.g., pursuant to a determination that the use of the first application is exempt from the usage limit (e.g., because the first application is included on an application whitelist and the electronic device provides access to the first application after a usage limit for the first category of application is reached; as another example, the use of the first application is for whitelist purposes (e.g., a calling app or messaging app used to communicate with a parent)) such that its use is not counted toward the usage limit). The above-described method of forgoing aggregation of 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) allows an electronic device to monitor usage limits for a category of applications without monitoring whitelisted applications, thereby allowing the electronic device to better manage a category of applications that includes one or more whitelisted applications (e.g., applications that are not restricted after a usage limit is reached) without having to add an additional category for whitelisted applications, and additionally reduces power usage and improves the device's battery life by allowing a user to use the device more quickly and efficiently.

While the first application is being used (e.g., a primary user interface of the first application is displayed on the electronic device or a user is otherwise interacting with the first application (e.g., via a secondary user interface of the first application)), the electronic device optionally counts (928) the use of the first application toward a usage limit associated with a first category of application, independent of whether the first application satisfies one or more restriction exclusion criteria (e.g., counts a contribution of the use of the first application toward a usage limit associated with a first category of application, independent of whether the first application is on a whitelist). For example, a particular social media application associated with a social media category and a one-hour usage limit is optionally a whitelist application, and its usage is counted toward that usage limit. Use of a different social media application, which is optionally not on the whitelist, is also optionally counted toward the usage limit. The above-described method of aggregating application usage allows the electronic device to monitor usage limits for categories of applications that include whitelisted applications, thereby allowing the electronic device to better manage categories of applications that include one or more whitelisted applications (e.g., applications that are not restricted after a usage limit is reached) because the category usage limits take into account the use of whitelisted applications without having to add additional categories for whitelisted applications, and additionally allows the user to use the device more quickly and efficiently, thereby reducing power usage and improving the device's battery life.

In some embodiments, the usage limit is a first usage limit associated with a first category of applications during one or more first implementation periods (930) (e.g., a usage limit for a first category of applications during weekdays), such as in FIG. 8L (e.g., a default social media category usage limit of two hours). In some embodiments, the electronic device receives (932) a series of one or more second inputs via one or more input devices that set a second usage limit associated with a first category of applications for one or more second implementation periods, such as FIG. 8L (e.g., a social media category usage limit of one hour for Monday, Wednesday, and Thursday) (e.g., a second maximum amount of time (e.g., 1 hour, 3 hours, 12 hours) that can be spent using the device or using the device in a particular manner (e.g., during times other than the default times, using a particular application (e.g., a particular social media application, SMS, phone, a particular travel application, email)) (e.g., the second usage limit is implemented on Saturday and Sunday while the first usage limit (e.g., the default usage limit) is implemented Monday through Friday; the second usage limit is implemented during work/school hours while the first usage limit is implemented outside of work hours; the second usage limit is implemented on particular days of the week while the first usage limit is implemented outside of the specific days).

In some embodiments, pursuant to determining that the current time is within one or more first implementation periods (e.g., determining that the current time is within a user-defined implementation period (e.g., a particular day of the week, work/school hours, Monday through Friday)), the electronic device enforces (934) a first usage limit (e.g., enforces a second usage limit during the user-defined implementation period (e.g., counting toward a second usage limit when applications (e.g., a particular social media application) of a first category of applications (e.g., social media) are accessed, providing or restricting access to applications of the first category of applications based on the second usage limit)), as shown in FIG. 8L.

In some embodiments, pursuant to a determination that the current time is within one or more second implementation periods (e.g., determining that the current time is outside a user-defined implementation period (e.g., a default period, other than a particular day of the week, after work/school hours, Saturday through Sunday)), the electronic device implements a second usage limit (936) (e.g., implementing a first usage limit (e.g., a default usage limit) outside the user-defined implementation period (e.g., counting toward the first usage limit when applications (e.g., particular social media applications) of a first category of applications (e.g., social media) are accessed, providing or restricting access to applications of the first category of applications based on the first usage limit) as shown in FIG. 8L). The above-described method of allowing different usage limits for a first category of applications on different days allows the electronic device to efficiently restrict the user's use of certain device operations for a defined period of time, providing a simple way for the user to set such usage limits for a defined period of time, thereby making use of the electronic device more efficient (e.g., the user's usage is specifically restricted during school/work hours, work days, specific days, and with the understanding that a second usage limit has been set, the user can use the restricted operations more wisely and efficiently to perform all necessary tasks under the second usage limit during the specific period (e.g., school/work hours, work days); if the usage limit is reached, the device restricts the user from using the restricted operations, thereby preventing the user from unknowingly exceeding the usage limit and spending more time on the device than intended during the specific period (e.g., school/work hours, work days)), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

In some embodiments, the electronic device receives input via one or more input devices corresponding to a request to exclude 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 a usage limit for a first category of applications, such as in FIG. 8I (e.g., social media application B is not selected to be enforced by the social media category usage limit) (938) (e.g., the request to exclude the second application is, for example, optionally configured on a settings user interface. As another example, if a particular application is not included in the usage limit, the particular application will, optionally, be excluded from that usage limit).

After receiving the input corresponding to a request to exclude the second application from the usage limit and while the restriction criteria for the first category of applications are met (940), the electronic device optionally receives a request to launch the second application (942), such as in FIG. 8AA (e.g., social media application B is not restricted from launching when the social media category usage limit is reached). In some embodiments, in response to receiving the request to launch the second application, the electronic device provides access to the second application (944), such as in FIG. 8AA (e.g., the appearance of the icon for social media application B does not update when the social media category usage limit is reached) (e.g., access to the second specific social media application is not restricted regardless of whether the usage limit associated with the social media application is reached). Although the first application (e.g., the first specific social media application) and the second application (e.g., a second specific social media application different from the first specific social media application) belong to a social media category, the electronic device may exclude the second application (e.g., the second specific social media application) from the category (e.g., social media) usage limit while the use of the first application is restricted. In some embodiments, a user can define which applications are excluded from such category usage limits. In some embodiments, if a user or electronic device does not define a usage limit for an application, the application is excluded. The above-described method of excluding applications associated with a category from category usage limits allows the electronic device to distinguish between applications whose usage is limited by the usage limit (e.g., a first application) and applications whose usage is not limited by the usage limit (e.g., a second application), thereby reducing the burden on the user to deal with restrictions on applications that should be excluded from such restrictions (e.g., the second application is associated with a category that has a usage limit, but the second application is optionally excluded from the usage limit by the user because the user does not want the application to be limited), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

In some embodiments, the usage limit is further associated (946) with a second category of applications accessible on the electronic device that includes different applications than the applications in the first category of applications, such as in FIG. 8Q (e.g., a social media category usage limit is associated with a social media category usage limit and a streaming and social media category usage limit) (e.g., a usage limit is associated with two or more categories, with a total usage limit for both categories of applications being set, such that each of the two or more categories has a different group of applications (e.g., the two groups do not have the same list of applications)). For example, a usage limit is optionally associated with social media and streaming applications. As another example, a usage limit is optionally associated with social media and messaging applications. While a particular social media application is 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 allows an electronic device to limit usage of the two categories of applications with a joint category usage limit, thereby reducing the user's burden of tracking different usage limits for different groups when a total overall usage for the different groups is desired, and additionally allows the user to use the device more quickly and efficiently, thereby reducing power usage and improving the device's battery life.

In some embodiments, the first category of applications includes all applications accessible on the electronic device (948), such as in FIG. 8Q (e.g., an "all" usage limit) (e.g., a usage limit is associated with all applications and categories on the electronic device, such that a total usage limit is set for all applications on the electronic device). For example, if an overall limit is optionally set, the use of the first and second specific social media applications is limited by the overall limit even though the specific applications are associated with the social media category. The total usage limit here is the same as or similar to the total screen time usage limit described with reference to method 700. The above-described method of setting an overall usage limit for all categories of applications allows the electronic device to limit the use of non-whitelisted applications by the overall usage limit (e.g., implementing a user screen time limit), thereby reducing the burden on the user to define 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, thereby reducing power usage and improving the device's battery life.

In some embodiments, the usage limit associated with a first category of applications has a first usage limit name based on one or more classification criteria (950) (e.g., a category name previously defined by the user, a category name previously defined by the device), such as in FIG. 8Q (e.g., a social media category usage limit has a default name of “social media”). In some embodiments, the default name of the usage limit is a device-determined name of a category of applications determined based on a category of applications within that category of applications, such as “news” or “games” or “news and games”. The electronic device optionally receives a series of one or more second inputs (952) (e.g., the series of one or more second inputs is optionally received from one or more input devices (e.g., the electronic device, a remote input device)) that change the usage limit name to a second usage limit name, such as in FIG. 8R (e.g., a user selects a “rename” affordance to change the social media category usage limit name). In some embodiments, in response to a series of one or more second inputs, the electronic device renames the usage limit to a second usage limit name (954) (e.g., the category name is redefined by the user), such as in FIGS. 8S-8T (e.g., the user renames the social media category usage limit to “John's Fun”). In some embodiments, the user may rename the category name (e.g., a name previously defined by the user, a name previously defined by the device) by inputting a new user-defined category name (e.g., via a soft keyboard, voice input, etc.). For example, the user may create categories that include applications from a number of different system-defined categories (e.g., a specific social media application that belongs to the social media category, and a specific gaming application that belongs to the gaming category), and generate category names of their own (e.g., “Restricted Applications”, “Social Media and Games”). In some embodiments, the electronic device renames the categories automatically. For example, a category named “Social Media” may initially optionally include a specific social media application. A specific gaming application is optionally added to the category. In response to the addition of a gaming application, the category name is optionally changed by the device to “Social Media and Games”. The above-described method of changing the usage limit category name allows the 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, thereby allowing the user to change the usage category name when a more appropriate usage limit category name is desired (e.g., when a new application is associated with the usage limit and a more appropriate name is needed to contain the newly associated application) instead of having to set up the usage limit again, and additionally allows the user to use the device more quickly and efficiently, thereby reducing power usage and improving the device's battery life.

In some embodiments, the first application is simultaneously associated with a usage limit associated with a first category of applications and a second usage limit (956) (e.g., the first application is associated with two simultaneous usage limits), such as in FIG. 8Q (e.g., the social media application is simultaneously associated with a social media category usage limit and a streaming and social media category usage limit). For example, the social media category is optionally associated with two usage limits. For example, the electronic device optionally has an overall limit of two hours, 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 (e.g., 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 on the electronic device (different from the first category of applications but including the first application), a usage limit for the first application itself that is separate from the usage limit for the first category of applications, etc. The above-described method of simultaneously enforcing two or more usage limits allows an electronic device to monitor application usage against two or more usage limits, thereby reducing the burden on the user to separately associate applications that the user wishes to limit with each of the two or more usage limits and to separately monitor each of the two or more usage limits, as well as allowing the user to use the device more quickly and efficiently, thereby reducing power usage and improving the device's battery life.

In some embodiments, the first application is associated with a second restriction criterion (958) that includes a requirement that either a usage limit for the first category of application is reached for the second restriction criterion to be met, or a second usage limit is reached for the second restriction criterion to be met, such as in FIG. 8Q (e.g., a social media application is simultaneously associated with a social media category usage limit and a streaming and social media category usage limit, and the most conservative usage limit is implemented), such as in FIG. 8Q (e.g., a social media application is simultaneously associated with a social media category usage limit and a streaming and social media category usage limit, and the most conservative usage limit is implemented). In some embodiments, pursuant to a determination that the second restriction criterion is met, the electronic device restricts access to the first application (960), such as in FIG. 8Q (e.g., a social media application is simultaneously associated with a social media category usage limit and a streaming and social media category usage limit, and the most conservative usage limit is implemented).

In some embodiments, pursuant to a determination that the second restriction criterion is not met, the electronic device provides access to the first application (962), such as in FIG. 8Q (e.g., a social media application is simultaneously associated with a social media category usage limit and a streaming and social media category usage limit, and neither usage limit has been reached). For example, the 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 (e.g., of one hour or some other amount of time). The electronic device optionally has an overall limit (e.g., a second usage limit of two hours or some other amount of time). If one of the usage limits is met (e.g., if the most conservative/restrictive usage limit is met), the electronic device optionally restricts access to the first application, even if the other usage limits are not met. Without any device usage, the social media category usage limit optionally has one hour remaining, and the overall usage limit optionally has two hours remaining. In this example, the social media category usage limit is the least remaining usage limit for the social media application. As another example, after some device use, the overall usage limit optionally has 30 minutes remaining and the social media category optionally has 1 hour remaining (e.g., because the social media application has not been used thus far during the current implementation period). In this example, the overall usage limit is optionally the least 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 use of the first application. The above-described method of enforcing the most conservative usage limit of two or more simultaneous usage limits allows the electronic device to monitor the use of the application for two or more usage limits and enforce the most conservative remaining usage limit, thereby reducing the user's burden of separately associating applications that the user wishes to limit with each of the two or more usage limits to separately determine which of the usage limits will be reached sooner, as well as allowing the user to use the device more quickly and efficiently, thereby reducing power usage and improving the device's battery life.

In some embodiments, while the restriction criteria for the first category of applications are met (964), the electronic device detects an event corresponding to activation of an auxiliary function of the first application (e.g., the occurrence of an event that will trigger the display of a notification for the application, a request to display a widget corresponding to the application, a request to share content with the application via a user interface sharing system, a request to view a website associated with the application, a request to view a history of previous notifications (including notifications for the application), a request to display application content in picture-in-picture (PIP) mode, a request to display the application in the search results, or a request to display and/or perform a media control operation associated with the application), such as in FIGS. 8Y-8EE (e.g., the user is attempting to view or access application suggestions, widgets, search results, and websites corresponding to social media application A when the social media category usage limit has been reached) (966). An auxiliary function of the first application is a function (e.g., displaying interactive notifications, performing share sheet actions, displaying widgets, displaying notification history, displaying websites in a browser, displaying application content in PIP mode, displaying applications in search results, or displaying and/or controlling media control operations) that is available to be performed without displaying the primary user interface of the first application (e.g., without launching the application into an application window or other primary view of the application).

In some embodiments, in response to detecting an event corresponding to activation of an auxiliary function of the first application, the electronic device inhibits (968) the auxiliary function (e.g., inhibits notification generation functionality associated with the application, display of the website(s) associated with the application, share sheet action(s), display of 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, restricting the application from appearing as a suggested application), such as in FIG. 8Y-FIG. 8EE (e.g., application suggestions, widgets, search results, and websites corresponding to social media application A are not accessible to the user when the social media category usage limit is reached). In some embodiments, launching the application from a home screen of the electronic device (or other user interface of the electronic device) is also inhibited (e.g., limited). In some embodiments, the auxiliary function is inhibited by preventing the function from being executed in response to detecting the event. The auxiliary functions described herein are, optionally, the same as or similar to the auxiliary functions described with reference to method 1300. The above-described method of throttling functionality across different aspects of the operating system of applications that are exceeding usage limits allows an electronic device to effectively reduce overall usage of the electronic device, thereby reducing power consumption and improving the device's battery life.

In some embodiments, the electronic device adds (970) access to a second application on the electronic device from an application source (e.g., an application store for browsing and/or downloading applications to the electronic device) that is associated with a corresponding category of applications by the application source (e.g., downloading a new application (e.g., a second particular social media application) from the app store, remotely accessing the new application, installing the new application on the device. In some embodiments, the app store, such as in Figures 8FF-8GG, associates the application with a particular category of applications (e.g., a user has added a social media application F from an App Store user interface) based on publisher information about the application or some other determination made by the app store (e.g., a news application is designated as part of a news category in the app store, a game is designated as part of a games category in the app store, etc.).

In some embodiments, pursuant to a determination that the corresponding category is the first category (e.g., determining that the category assigned to the application added by the app store is the same as an existing category on the electronic device with a usage limit), the electronic device controls access to the second application (972) according to the restriction criteria for the first category of the application (e.g., if the usage limit for the first category (e.g., social media) is reached, access to the newly added social media application F is restricted), such as in FIG. 8HH (e.g., the electronic device optionally also restricts the user's access to the second application (e.g., the second specific social media application added from the application source)). Thus, the electronic device applies the first category restriction 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 (e.g., games, social media, news, streaming) of the added application. In some embodiments, this determination is based on metadata associated with the added application.

In some embodiments, pursuant to a determination that the corresponding category is not the first category (e.g., determining that the added application does not belong to the first category (e.g., a category different from social media)), the electronic device forgoes controlling access to the second application according to the restriction criteria for the first category of application (974) (e.g., use of the added application (e.g., the second particular social media application) is, optionally, not associated with the first category usage limit (e.g., social media usage limit)). In some embodiments, the added application is controlled based on a different usage limit for another category of application to which the added application belongs. In some embodiments, if the added application does not fall under any usage limit on the electronic device, it is not controlled by any usage limit on the electronic device. The above-described method of determining a category (e.g., social media) of the added application (e.g., the second particular social media application) based on one or more classification criteria (e.g., app store classification, metadata of the new application) and enforcing a usage limit associated with the determined category (e.g., social media) for the new application (e.g., the second particular social media application) allows the electronic device to efficiently limit a user's use of the added application without having the user determine a classification of the new application, thereby making device usage more efficient (e.g., the user does not have to manually determine the category of the added application, the user does not have to manually determine a usage limit for the added application, the user does not have to monitor the user's own device usage of the added application, thus reducing input provided by the user to the device (e.g., input to otherwise monitor user usage); if a usage limit has been reached, the device limits the user from using the added application, thereby preventing the user from unknowingly exceeding the usage limit and spending more time on the device than intended); and, in addition, reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

In some embodiments, one or more time windows associated with a limited use mode during which access to one or more applications on the electronic device is restricted, such as in FIG. 8E (e.g., a device downtime period is set), are defined on the electronic device (976) (e.g., a user of the electronic device defines a time of day (e.g., 10 p.m. to 5 a.m.) as a bedtime limited use mode during which the electronic device prevents or attempts to prevent access to all applications on the electronic device, except for applications included, in some embodiments, on a whitelist of applications). In some embodiments, the user simply defines the time window and does not specify any particular applications to which access is to be restricted. In such embodiments, the electronic device optionally defaults to restricting or attempting to restrict use of all applications except for whitelisted applications during the limited use mode. In some embodiments, pursuant to a determination that a request to launch the first application is received while one or more time windows associated with the limited use mode are defined (e.g., the limited use mode is set to be in effect for the defined time period(s), a bedtime limited use mode is set), and during one or more time windows associated with the limited use mode (e.g., the electronic device is currently in the limited use mode, the electronic device is currently in the bedtime limited use mode), the electronic device restricts (978) access to the first application independent of whether a restriction criterion for the first category of applications is met (e.g., the limited use mode takes precedence over a usage limit), such as in FIG. 8II-8KK (e.g., device downtime setting takes precedence over a social media category usage limit setting, device downtime setting restricts social media applications when a social media category usage limit has not been reached). For example, access to the first category of applications is optionally restricted during the limited use mode even if a usage limit for the first category of applications has not been met. The limited use mode described herein is, optionally, the same as or similar to the limited use mode described with reference to method 1100. The above-described methods of implementing a restricted use mode (e.g., a bedtime restricted use mode) in conjunction with an application usage limit allow an electronic device to restrict access to one or more applications or categories of applications before a usage limit is reached (e.g., during device downtime, a designated period of inactivity (e.g., bedtime)), thereby allowing a user to better manage device usage during periods of restricted activity (e.g., bedtime) even though a usage limit may not have been reached, as well as reducing power usage and improving the device's battery life by allowing a user to use the device more quickly and efficiently.

In some embodiments, restricting access to the first application includes presenting an indication indicating that access to the first application is restricted (e.g., displaying a visual indication on the display (e.g., an hourglass representing that time is up, one or more application icons associated with the usage limit being reached), such as in FIG. 8NN-FIG. 8OO (e.g., a restriction notification user interface under a "Notification" option providing extend and ignore affordances to proceed with the restricted application), playing a sound on a speaker associated with the electronic device, generating haptic(s) and/or tactile output(s) indicating that the application is restricted, etc. (e.g., a notification) (980). The indication includes a selectable affordance to provide access to the first application without requiring authentication credentials (e.g., a graphical user interface element or soft button that allows the user to access the restricted application when the usage limit is being reached). In some embodiments, different applications are associated with different restriction options that are implemented when the usage limit is being reached. For example, the electronic device optionally allows one or more applications to be associated with a "Notification" restriction option. When a user attempts to launch an application associated with a "notification" restriction (e.g., by selecting an icon for that application from the home screen of the electronic device when the usage limit is being reached, and assuming the application is not included in the application whitelist), the electronic device optionally displays a pop-up indication indicating that application usage is currently restricted (e.g., because the usage time limit has been reached). The pop-up notification optionally includes one or more affordances that, when selected, allow the user to proceed to the application without having to enter any authentication credentials (e.g., a "go anyway" affordance that opens the application without having to enter administrator or other credentials). In some embodiments, app usage that exceeds the allowed limit (e.g., even if approved by a time extension) is optionally indicated in a dashboard user interface described above with reference to method 700 (e.g., as shown in Figures 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 before providing access to the first application, the visual indication on the display 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 a user that an application will be restricted when a usage limit is reached, but giving the user the option to access the application nevertheless when needed, allows the electronic device to effectively restrict the use of a particular application for certain periods of time while still allowing the user to perform necessary tasks on the electronic device, thereby reducing use of the electronic device during those periods, and additionally reducing power consumption to improve the device's battery life.

In some embodiments, restricting access to the first application includes presenting an indication that access to the first application is restricted (e.g., displaying a visual indication on the display (e.g., an hourglass representing time running out, one or more application icons associated with a usage limit being reached), playing a sound on a speaker associated with the electronic device, generating haptic(s) and/or tactile output(s), etc. (e.g., a notification), indicating that the application is restricted), including a selectable affordance to provide access to the first application while requiring authentication credentials, such as in FIGs. 8EEE-8GGG (e.g., a restriction notification user interface under a "Notify and Block" option providing defer and ignore affordances to require authentication before proceeding with the restricted application) (982). In some embodiments, the electronic device allows one or more applications to be associated with the "Block and Notify" restriction option. If a user attempts to launch an application associated with a "block and notify" restriction (e.g., by selecting an icon for that application from the home screen of the electronic device when the usage limit is being reached and assuming that the application is not included in the application whitelist), the electronic device blocks the application from being launched and, optionally, displays a pop-up indication indicating that application usage is currently restricted (e.g., because the usage limit is being reached). In some embodiments, the pop-up indication requests authentication credentials (e.g., password, passcode, or consent from a parent device/account, fingerprint authentication, face authentication (e.g., attention awareness via a depth camera is required for successful biometric authentication)) to access the application. If the electronic device is a child device in a family account (e.g., a device of a user designated as a child as opposed to a parent or administrator in a family account), the displayed notification optionally includes an affordance for requesting permission from an adult/parent device in the family account to access the application when the usage limit is being reached. In such a case, selection of the request in the notification optionally results in a notification being delivered to one or more (or all) parent devices associated with the family account, and if permission is granted (e.g., at least one of the parent devices, or at the child device via a passcode), the electronic device allows access to the application. In some embodiments, in response to selecting an affordance for providing access to the first application, and before providing access to the first application, the visual indication on the display 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 launching an application when a usage limit is reached and notifying the user that the application is restricted allows the electronic device to effectively restrict use of the particular application for a particular period of time, thereby reducing use of the electronic device during those periods, as well as reducing power consumption to improve the device's battery life.

In some embodiments, pursuant to a determination that the electronic device is not a child device (e.g., not a child device in a family account (e.g., a parent device in a family account) based on a classification of a user account associated with the electronic device or an option selected on the electronic device), selection of the affordance triggers a request to enter a passcode to access the first application (984), such as in FIG. 8EEE-FIG. 8GGG (e.g., a restricted notification user interface under a “Notify and Block” option providing defer and ignore affordances to require authentication before proceeding with a restricted application). For example, the determination that the electronic device is not a child device is optionally based on a determination that a user account associated with the electronic device (e.g., a user currently signed in to 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 based on a determination that the electronic device is set to a parent device in the device's settings (e.g., set during initial setup of the device) or is 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 appropriate authentication credentials are provided. In some embodiments, the affordances include one or more of soft buttons or input fields for user ID, password, passcode, fingerprint authentication, and/or face authentication (e.g., attention awareness via a depth camera is required for successful biometric authentication). For example, if the device is not a child device in a family account (e.g., is a parent device in a family account) or is not associated with a family account at all, the electronic device optionally requests that the user enter credentials (e.g., user ID and/or password, passcode) for the user account to which the electronic device is associated (e.g., user ID and/or password or passcode associated with the profile to which the device is configured). In some embodiments, the credentials (e.g., user ID and/or password, passcode) are different from the credentials to access the electronic device (e.g., a different passcode than that used to "unlock" the device and/or log in to the device). In this way, a user (e.g., a child) who is not the owner (e.g., parent) of the device will not be able to circumvent application restrictions if the user does not enter a secondary passcode.

In some embodiments, pursuant to a determination that the electronic device is a child device (e.g., based on a classification of a user account associated with the electronic device or an option selected on the electronic device), selection of the affordance causes the display to present a first affordance requesting entry of a passcode (e.g., a parental control passcode that is different from a passcode for unlocking the device or accessing a user account associated with device operation) to access the first application, such as in FIG. 8TT-FIG. 8CCC (e.g., a local authentication request affordance and a remote authentication request affordance are displayed on a restriction notification user interface on the child device, and authentication is requested on a different corresponding device depending on the selection of the affordance), and a second affordance that, when selected, initiates a process to request access to the first application from a parent device (e.g., initiates a process to request more time from a parent device in a family account) (986). For example, the determination that the electronic device is a child device is optionally based on a determination that a user account associated with the electronic device (e.g., a user currently signed in to the device) is classified as a child account. In some embodiments, the determination that the electronic device is a child device is optionally based on a determination that the electronic device is configured as a child device in the device's settings (e.g., configured during initial setup of the device). In some embodiments, this process results in sending 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, an email request to an email account associated with the parent(s)). This process then allows the parent to grant the child device access to the restricted application (e.g., the parent can choose to allow the child device to access the restricted application when a usage limit has been reached) or deny the child device access to the restricted application. In some embodiments, the electronic device presents an affordance for entering a passcode and/or an affordance for initiating a process to request access to the first application. In some embodiments, the passcode is a parental control passcode or a usage 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 can optionally enter a passcode that allows the electronic device to access the first application. The request for additional time described here is similar to the request for additional time described with reference to the limited use mode of method 1100. The above-described method of notifying a user that an application is restricted when a usage limit is reached, but allowing the user the option to access the application nevertheless when needed, allows the electronic device to effectively restrict the use of certain applications for certain periods of time while still allowing the user to perform necessary tasks on the electronic device, thereby reducing the use of the electronic device during those periods, and in addition reducing power consumption to improve the battery life of the device.

In some embodiments, while a usage limit associated with a first category of applications is being enforced, pursuant to a determination that a warning threshold for the usage limit has been reached (e.g., the warning threshold is reached when a certain percentage of the usage limit has been reached (e.g., 90%, 5 minutes remaining, 45 minutes of an hour, 5 minutes, 10 minutes, 1 hour, or any period of time before the usage limit is reached)), the electronic device displays (988) an indication (e.g., text, image, sound, haptic and/or tactile output, etc.) that a warning threshold for the usage limit has been reached (e.g., a notification indicating that the usage limit is about to be reached and that a threshold time (e.g., 90%, 5 minutes remaining, 45 minutes of an hour) has been reached or a certain time (e.g., 5 minutes, 10 minutes, 1 hour, or any period of time) remains until the usage limit is reached), such as in FIG. 8III (e.g., a notification is displayed on the device indicating that the social media category usage limit has 5 minutes remaining). In some embodiments, the threshold time is defined by a user. In some embodiments, the notification includes text, image(s), and/or sound. In some embodiments, the notification includes a tactile and/or tactile output indication. In some embodiments, the notification includes a button that allows the user to dismiss the notification. In some embodiments, the electronic device stops displaying the notification after a certain amount of time. The above-described method of notifying the user that a usage limit is about to be reached (e.g., a certain percentage of the usage limit (e.g., 90%, 5 minutes remaining, 45 minutes of an hour) has been used) makes the user's interface with the device more efficient (e.g., does not require the user to monitor the time, provides the user with an opportunity to finish a task currently being performed on the device, prompts the user to stop using the device in anticipation of reaching the usage limit, thus reducing inputs provided by the user to the device (e.g., inputs to update usage limit settings)), thereby allowing the electronic device to efficiently reduce overall usage of the electronic device, as well as reducing power consumption to improve the device's battery life.

In some embodiments, the electronic device receives one or more inputs (990) to change one or more usage limit settings associated with a usage limit (e.g., changing a usage limit start/end time, changing a whitelist, etc.), such as in FIG. 8JJJ (e.g., a user is attempting to view or change a social media category usage setting). In some embodiments, in response to receiving one or more inputs to change one or more usage limit settings (992), one or more inputs to change one or more usage limit settings are received via one or more input devices of the electronic device, and pursuant to a determination that the electronic device is a child device (e.g., based on a classification of a user account associated with the electronic device or an option selected on the electronic device), the electronic device requests authentication (994) before performing one or more usage limit setting changes (e.g., requesting a user of the electronic device to enter a passcode to make a usage limit setting change), such as in FIG. 8JJJ-FIG. 8KKK (e.g., changing a usage limit setting on a child device requires a passcode). For example, the determination that the electronic device is a child device is optionally based on a determination that a user account associated with the electronic device (e.g., a user currently signed in to the device) is classified as a child account. In some embodiments, the determination that the electronic device is a child device is optionally based on a determination that the electronic device is configured as a child device in the device's settings (e.g., configured during initial setup of the device). In some embodiments, if the electronic device is a child device in a family account, any of the usage limit settings or preferences or rules described herein can be changed on the child device only upon entry of a password or other authentication credential on the child device (e.g., upon determining that one of the settings is about to be changed, the electronic device prompts the user to enter a password that must be authenticated before the change is allowed). In some embodiments, the authentication credential is the same as the credential for unlocking the device (e.g., a passcode, fingerprint authentication, and/or face authentication (e.g., attention awareness via a depth camera is required for successful biometric authentication) to unlock the device). In some embodiments, the authentication credential is different from the credential for unlocking the device (e.g., a parent's credential in a family account). In some embodiments, the parent device can remotely change the above settings implemented on the child device (e.g., optionally, upon entry of a parent's credential on the parent device).

In some embodiments, in response to receiving one or more inputs to change one or more usage limit settings (992), in accordance with a determination that one or more inputs to change one or more usage limit settings were received from other than the electronic device via the parent device (e.g., the usage limit setting change was made on the parent device (e.g., based on the classification of a user account associated with the electronic device or an option selected on the electronic device, it is a parent device in a family account)), the electronic device performs one or more usage limit setting changes (996) (e.g., makes the usage limit setting change without having to enter additional credentials) such as in FIG. 8LLL-FIG. 8NNN (e.g., the parent device is changing the usage limit settings of the child device). For example, the determination that the electronic device is not a child device is optionally based on a determination that a user account associated with the electronic device (e.g., a user currently signed in to 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 based on a determination that the electronic device is set to a parent device in the device's settings (e.g., set during initial setup of the device). In some embodiments, the electronic device is a parent device. In some embodiments, the electronic device is different from the parent device (e.g., the electronic device is a child device). In some embodiments, the parent device remotely modifies the usage limit settings on the child device (e.g., via the Internet, Bluetooth, or other networks or protocols). The manner in which usage limits are set/modified here is the same as or similar to the manner in which a restricted use mode is set/modified as described with reference to method 1100. The above-described method of limiting the ability to change usage limit settings allows the electronic device to efficiently and selectively restrict the use of certain applications for certain time periods, thereby reducing the use of the electronic device during those time periods, as well as reducing power consumption to improve the device's battery life.

In some embodiments, in response to executing one or more usage limit setting changes received from other than the electronic device, the electronic device presents an indication (998) (e.g., a visual indication (e.g., one or more of text and image), a sound indication, a verbal indication, and/or a tactile and/or tactile output indication) regarding the one or more usage limit setting changes (e.g., a notification is displayed on the child device when the usage limit settings of the child device are changed by the parent device), such as FIG. 8NNN (e.g., presenting a notification that the usage limit settings have been remotely changed by the parent device (e.g., is a parent 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). 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 in to 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 based on a determination that the electronic device is set to a parent device in the device's settings (e.g., set during initial setup of the device). In some embodiments, if the parent device remotely modifies the above settings implemented on the child device, the child device displays a notification that such remote modification has been made, details of the modification (e.g., the parent device has modified the usage limit, the parent device has modified the time window during which the usage limit is implemented from 10:00 PM to 6:00 AM to 9:00 PM to 7:00 AM, etc.). The notification generated on the child device here is the same as or similar to the notification generated on the child device with reference to the restricted usage mode described in method 1100. The above-described method of modifying the usage limit settings allows the electronic device to efficiently and selectively restrict the use of certain applications for certain time periods, thereby reducing the use of the electronic device during those time periods, and in addition, reducing power consumption to improve the battery life of the device.

In some embodiments, generating one or more inputs to change one or more usage limit settings received from a parent device other than the electronic device requires input of authentication credentials to make the usage limit setting change on the electronic device at the parent device (e.g., a parent device in a family account based on the classification of a user account associated with the electronic device or an option selected on the electronic device), such as in FIG. 8 MMM (e.g., a passcode is required on the parent device to change the usage limit setting on the child device on the parent device) (998-2) (e.g., in response to receiving an input to change the usage limit setting from the parent device's device (e.g., the authenticating adult's device), a passcode (e.g., a device usage limit passcode or other authentication credential, optionally different from the authentication credentials for accessing the parent device and/or the child device) is optionally required at 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 a user account associated with the electronic device (e.g., a user currently signed in to 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 based on a determination that the electronic device is configured as a parent device in the device's settings (e.g., configured during initial setup of the device). The above-described method of requiring authentication credentials (e.g., passcode, fingerprint authentication, facial authentication) to change usage limit settings from the parent device allows the electronic device to set usage limits by a remote device after the authentication credentials are entered, thereby preventing unauthorized access to the parent's device (e.g., a child may have access to an adult's device and use the adult's device to change usage limit settings on the child's device), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

It should be understood that the particular order described for the operations in Figures 9A-9K is merely exemplary, and that the order described is not intended to indicate that the operations are the only order in which they may be performed. Those skilled in the art will recognize various ways to reorder the operations described herein. In addition, it should be noted that other process details described herein with respect to other methods described herein (e.g., methods 700, 1100, 1300, and 1500) are also applicable in a similar manner to method 900 described above with respect to Figures 9A-9K. For example, the usage limits, usage restriction settings, etc. on the electronic device described above with reference to method 900 optionally have one or more of the characteristics of the usage limits, usage restriction settings, etc. on the electronic device described herein with reference to other methods described herein (e.g., methods 700, 1100, 1300, and 1500). For the sake of brevity, these details will not be repeated here.

The operations in the information processing method described above are optionally performed by running one or more functional modules in an information processing device, such as a general-purpose processor (e.g., as described above in connection with FIGS. 1A-1B, 3, 5A-5H) or an application specific chip. Additionally, 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 event processor 190. Event monitor 171 of event sorter 170 detects contacts on touch screen 504, and event dispatcher module 174 delivers the event information to application 136-1. The event recognizer 180 of each application 136-1 compares the event information to a respective event definition 186 to determine whether the first contact at a first location on the touch screen corresponds to a predefined event or sub-event, such as the selection of an object on a user interface. When a corresponding predefined event or sub-event is detected, the event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. The event handler 190 optionally utilizes or calls a data updater 176 or an object updater 177 to update the application internal state 192. In some embodiments, the event handler 190 accesses a corresponding GUI updater 178 to update what is displayed by the application. Similarly, it will be apparent to one skilled in the art how other processes can be implemented based on the components shown in FIGS. 1A-1B.
Restricted Use Mode User Interface

Users interact with electronic devices in many different ways and during various times during the day or night. For example, a user may 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 a user to monitor and limit the use of certain applications during certain periods of time. The embodiments described below provide a way for an electronic device to efficiently and selectively limit access to certain applications during certain periods of time, thereby reducing the use of the electronic device during those periods without the user having to monitor their own use. Limiting access to applications during certain periods of time also reduces the power usage of the device to increase battery life for battery-powered devices. It is understood that people use devices. When a person uses a device, that person is optionally referred to as the user of the device.

10A-10AAA illustrate example methods by which an electronic device may restrict access to a particular application for a particular period 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 illustrates an exemplary device 500 having a touch screen 504 as described with reference to FIGS. 5A-5H. The touch screen 504 optionally displays one or more user interfaces including various content. In the example illustrated in FIG. 10A, the touch screen 504 displays a “restriction settings” graphical user interface 1002 for defining one or more application restriction settings, as described above with reference to FIGS. 6A-6D. For example, FIG. 10A illustrates a selectable affordance 1004 for defining a “device downtime” (e.g., a limited use mode) in which the device 500 prevents or attempts to prevent access to certain applications on the device. FIG. 10A illustrates that the selectable device downtime setting affordance 1004 includes information regarding the limited use mode (e.g., that the device downtime mode is automatically enabled from 10:00 PM to 6:00 AM every day). In some embodiments, the device downtime or limited use mode is a bedtime limited mode for reducing device usage during a user-defined bedtime period.

Affordance 1004 is selectable to define limited use mode settings or rules, as described herein. For example, in FIG. 10B, selection of device downtime setting affordance 1004 is detected (e.g., by a tap of contact 1003 detected on device downtime setting affordance 1004, as shown in FIG. 10B). In response to selection of device downtime setting affordance 1004, device 500 displays a "device downtime" graphical user interface 1010, as shown in FIG. 10C.

FIG. 10C shows exemplary restricted use mode settings or rules. The device downtime screen 1010, as shown in FIG. 10C, optionally includes a toggle switch input affordance 1011 for enabling or disabling implementation of the limited use mode settings, an affordance 1012 for defining a start time for the limited use mode, an end affordance 1013 for defining an end time for the limited use mode, a day affordance 1014 for defining which day the limited use mode settings will be implemented, a downtime affordance 1015 for defining how the device 500 will implement the limited use mode at the start time (e.g., under the “Notify and Block” option or the “Notification” option as described with reference to FIGS. 8LL-8GGG), a verbal affordance 1016 for enabling speaking the limited use mode warning (e.g., with an audible voice that reads the limited use mode warning or notification aloud), or a silent affordance 1017 for enabling a silent mode during the limited use mode (e.g., a mode that silences incoming calls and alerts when the device 500 is locked). For example, turning off the toggle switch input affordance 1011 will, optionally, disable enforcement of the limited use mode settings within the hours and days defined by the start affordance 1012, the end affordance 1013, and the day affordance 1014. In some embodiments, turning off the toggle switch input affordance 1011 will save the limited use mode settings or rules defined on the device downtime screen 1010, such that the settings will be restored when the toggle switch input affordance 1011 is turned back on.

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

10E illustrates an exemplary day graphical user interface 1020 for defining which days the limited use mode setting is implemented. The day graphical user interface 1020 optionally includes a daily affordance 1022 that requires that every day of the week have the same limited use start and end times (e.g., as defined by the start affordance 1012 and the end affordance 1013 in the device downtime screen 1010, as shown in FIG. 10C). In some embodiments, the day graphical user interface 1020 includes 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. Enabling the daily affordance 1022, as shown in FIG. 10E, optionally disables affordances 1024a-1024g to prohibit the user from using the affordances 1024a-1024g to define different start and end times for different days of the week. In some embodiments, device 500 visually obscures affordances 1024a-1024g (e.g., by distorting, graying out, fading out) when daily affordance 1022 is enabled, as shown in FIG. 10E. In some embodiments, device 500 forgoes displaying affordances 1024a-1024g when daily affordance 1022 is enabled. In some embodiments, disabling daily affordance 1022, and enabling affordances 1024a-1024g, as shown in FIG. 10F, allows affordances 1024a-1024g to be used by a user to define different start and/or end times for different days of the week (e.g., a user can define start and/or end times for each day). For example, disabling daily affordance 1022 optionally allows a user to define different limited use mode start and end times for Friday and Saturday via affordances 1024e and 1024f, as shown in FIG. 10F. In some embodiments, enabling the daily affordance 1022 will save the different start and end times defined by the affordances 1024a-1024g on the day graphical user interface 1020, such that the next time the daily affordance 1022 is disabled, these settings will be restored.

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

As shown in FIG. 10H, the device 500 allows the user to add or remove applications from a list of applications that do not follow the limited use mode rules while in the limited use mode (e.g., application whitelist 1026, as shown in FIG. 10H) from the always allow graphical user interface 1025. For example, FIG. 10H shows a phone app 1026a, a messaging app 1026b, and a FaceTime app 1026c on the whitelist 1026. In some embodiments, the always allow graphical user interface 1025 includes a selectable remove affordance 1027 adjacent to a particular application listed on the whitelist 1026 that, when selected by the user, causes the device 500 to remove the corresponding application from the whitelist 1027 (e.g., subjecting the particular application to the limited use mode rules). In some embodiments, the particular application will be on the whitelist 1026 permanently. 10H shows the phone app 1026a without a removal affordance 1027 for removing the phone app 1026a from the whitelist 1026, such that the app 1026a for making or receiving calls on device 500 is, optionally, permanently included on the whitelist 1026. In some embodiments, the always allow graphical user interface 1025 indicates whether an application on the whitelist 1026 does not follow the limited use mode rules while in the limited use mode for communication with anyone, contacts stored on device 500, or with a particular contact stored on device 500 via that particular app. For example, FIG. 10H shows that communication via the original phone app 1026a to anyone during the limited use mode is not restricted, communication via the message app 1026b to all contacts stored on the device 500 during the limited use mode (but optionally restricted to other contacts not stored in the contacts on the device 500), and communication via the FaceTime app 1026c to certain designated contacts is not restricted. In some embodiments, the user is permitted to change which communications via whitelisted apps during the limited use mode do not follow the limited use mode rules, as described in more detail below with reference to FIGS. 10K-10S.

10H, the always allow graphical user interface 1025 includes a list 1028 of applications (e.g., applications 1029a-1029e) that can be added to the whitelist 1026. In some embodiments, the applications listed in the list 1028 include all applications installed on the device 500. FIG. 10H includes a selectable add affordance 1029 adjacent to each of the applications 1029a-1029e that allows the user to add any of the applications 1029a-1029e to the whitelist 1026. For example, FIG. 10I illustrates the addition of "app5" (e.g., by a tap of the contact 1003 detected on the add affordance 1029 adjacent to application 1029e). In response to the selection of the add affordance 1029 adjacent to application 1029e, app5 is added to the whitelist 1026, as shown in FIG. 10J.

In some embodiments, one or more of the applications 1026a, 1026b, 1026c, 1026d, and 1029e are selectable to display another user interface for modifying communication restrictions associated with those applications during the limited use mode. For example, in FIG. 10K, selection of the phone app 1026a is detected (e.g., by a tap of contact 1003 detected on the input of the application 1026a in the whitelist 1026, as shown in FIG. 10K). In response to selection of the input of the application 2016a in the whitelist 1026, the device 500 optionally displays a "phone" communication graphical user interface 1030, as shown in FIG. 10L. The phone communication graphical user interface 1030 optionally includes two selectable affordances for defining which communications by the phone app do not follow the limited use mode rules during the limited use mode. For example, FIG. 10L displays a selectable "Anyone" option 1032 that, when selected, allows communication (e.g., both incoming and outgoing calls) with anyone via the phone app in the limited use mode (e.g., regardless of whether the other party's communication information is stored on the device 500), a selectable "All Contacts" option 1033 that, when selected, allows communication (e.g., both incoming and outgoing calls) with any contact stored on the device 500 via the phone app in the limited use mode, and a selectable "Designated Contacts" option 1034 that, when selected, allows the user to define which contacts are allowed to communicate (e.g., both incoming and outgoing calls) via the phone app in the limited use mode, as described herein.

In some embodiments, the designated contacts option 1034 is selectable to display information for defining which contacts are permitted to communicate (e.g., both incoming and outgoing communication) via the phone app during the limited use mode. For example, in FIG. 10L, selection of the designated contacts option 1034 is detected (e.g., by a tap of contact 1003 detected on the designated contacts option 1034, as shown in FIG. 10L). In response to selection of the designated contacts option 1034, the device 500 displays an allowed contacts list 1036, including selectable contacts (e.g., contacts 1037a, 1037b, and 1037c) stored on the device 500, which, when selected, defines which contacts are permitted to communicate via the phone app during the limited use mode, as shown in FIG. 10M. In some embodiments, selection of the designated contacts option 1034 also causes the device 500 to display a selectable "add contact" affordance 1038 that, when selected, allows the user to enter and store a new contact that will then be displayed in the allowed contacts list 1036 as a selectable contact on the device 500. For example, in FIG. 10M, communication (e.g., both incoming and outgoing communication) is permitted only with contacts A and B, but not with contact C, via the phone app during limited use mode.

In some embodiments, the device 500 allows the user to define a contact list of daytime allowed contacts that are allowed to communicate via a particular application during daytime hours (e.g., outside of the limited use mode) and a contact list of nighttime allowed contacts that are allowed to communicate via the same application during nighttime hours (e.g., during the limited use mode) (e.g., as described above with reference to FIG. 10M). For example, FIG. 10N illustrates detecting a selection of the phone app 1026a (e.g., by a tap of the contact 1003 detected on the input of the application 1026a in the whitelist 1026, as shown in FIG. 10N). In response to the selection of the input of the application 2016a in the whitelist 1026, the device 500 displays a "phone" communication graphical user interface 1030, as shown in FIG. 10O.

In some embodiments, the "phone" communication graphical user interface 1030 includes a selectable day affordance 1039a and a selectable night affordance 1039b, as shown in FIG. 10O. For example, in FIG. 10P, a selection of the day affordance 1039a is detected (e.g., by a tap of contact 1003 detected on the day affordance 1039a, as shown in FIG. 10P). In response to the selection of the day affordance 1039a, the device 500 displays a "day" graphical user interface 1040, as shown in FIG. 10Q. In some embodiments, the day graphical user interface 1040 functions to define (e.g., to define a daytime whitelist) which contacts (e.g., anyone, all contacts, or specified contacts) are allowed to communicate (e.g., both incoming and outgoing communication) via the phone app during daytime hours (e.g., outside of limited use mode), as described above with reference to FIGS. 10L-10M. As shown in FIG. 10R, a selection of the night affordance 1039b is optionally detected (e.g., by a tap of contact 1003 detected on the night affordance 1039b, as shown in FIG. 10R). In response to the selection of the night affordance 1039b, the device 500 displays a "night" graphical user interface 1042, as shown in FIG. 10S. In some embodiments, the night graphical user interface 1042 functions to define (e.g., to define a night whitelist) which contacts (e.g., anyone, all contacts, or specified contacts) are allowed to communicate (e.g., both incoming and outgoing communication) with or through the phone app during the bedtime period (e.g., during the limited use mode), as described above with reference to FIGS. 10L-10M. 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., a device of a user designated as a child, as opposed to a parent or administrator child device in a family account), as shown in FIG. 10T. When device 500 is a child device, changing one or more restriction settings on restriction settings graphical user interface 1002 is optionally not enabled and/or optionally requires entering a passcode (or other authentication as described in this disclosure). In FIG. 10T, passcode affordance 1008 is optionally toggled on permanently for the child device, requiring a user of device 500 to enter a passcode to make any changes on restriction settings graphical user interface 1002. For example, in FIG. 10U, while passcode affordance 1008 is toggled on, a selection of device downtime settings affordance 1004 is detected (e.g., by a tap of contact 1003 detected on device downtime settings affordance 1004, as shown in FIG. 10U). In response to selection of the device downtime settings affordance 1004, the device 500 displays a passcode graphical user interface 1044 requesting the user to enter a passcode before any device downtime setting changes are permitted to be made, as shown in FIG. 10V. 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, as described above with reference to FIGS. 10C-10S (e.g., the user of the child device can view the restriction settings, including the device downtime and always allowed settings, without having to enter a passcode). In some embodiments, the passcode requested in FIG. 10V is different from the passcode for logging on or unlocking the device 500 (e.g., it is a passcode specific to the restriction settings). In some embodiments, a biometric is requested instead of a passcode to make restriction setting changes (e.g., as described below in process 1100).

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

In some embodiments, each of the daddy account 1049a, mommy account 1049b, and child account 1049c can be selected to display a limit setting graphical user interface for modifying the limit settings associated with each of those accounts. For example, in FIG. 10X, a selection of the child account 1049c is detected (e.g., by a tap of contact 1003 detected on the child account 1049c, as shown in FIG. 10X). In response to the selection of the child account 1049c, the device 500 displays a child limit setting graphical user interface 1002 associated with the child account 1049c, as shown in FIG. 10Y.

In some embodiments, the parent is requested to enter a passcode (or provide other restriction setting authentication, such as facial recognition) in order for the device 500 (e.g., the parent device) to modify the restriction settings associated with the child account 1049c on the child restriction settings graphical user interface 1002. For example, in FIG. 10Z, a selection of the always allow affordance 1006 is detected (e.g., by a tap of contact 1003 detected on the always allow affordance 1006, as shown in FIG. 10Z). In response to the selection of the always allow affordance 1006, the device 500 displays a passcode graphical user interface 1044, as shown in FIG. 10AA, requesting that the user enter a passcode before any restriction setting changes associated with the child account are permitted to be made. In some embodiments, the passcode graphical user interface 1044 is not displayed by the device 500 until the device restriction settings are modified by the user, as described above with reference to FIGS. 10C-10S (e.g., the user of the parent device can view the restriction settings for the child device, including the device downtime and always allow settings, without having to enter a passcode). In some embodiments, the passcode requested in FIG. 10AA is different from the passcode for logging on to or unlocking device 500 or the child device (e.g., a passcode specific to the restriction settings). In some embodiments, a biometric is optionally entered in place of a passcode to effect a change to the restriction settings (e.g., as described below in process 1100).

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

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

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

FIG. 10FF illustrates device 500 displaying home screen 1050 at the onset of the limited use mode under the “Notifications” option of the device downtime settings (e.g., as described above with reference to FIGS. 8LL-8PP and 10D). In some embodiments, device 500 can be 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). Device 500 optionally visually obscures home screen 1050 (e.g., blurs, grays out, or visually alters home screen) at the onset of the limited use mode, as shown in FIG. 10FF. In some embodiments, device 500 is displaying a graphical user interface other than home screen 1050 (e.g., an application graphical user interface, a notification history graphical user interface, etc.) at the onset of the limited use mode, and device 500 visually obscures that graphical user interface (e.g., blurs, grays out, or visually alters that graphical user interface) at the onset of the limited use mode. In some embodiments, device 500 displays a description 1056 indicating that the limited use mode has been initiated, and a dismiss affordance 1057. For example, in FIG. 10FF, a selection of dismiss affordance 1057 is detected (e.g., by a tap of contact 1003 detected on dismiss affordance 1057, as shown in FIG. 10FF). In response to the selection of dismiss affordance 1057, device 500 stops displaying dismiss affordance 1057 and displays extend affordance 1058 and ignore affordance 1059, as shown in FIG. 10GG. In some embodiments, a user selection of extend affordance 1058 allows the user to delay initiation of the limited use mode (such that the limited use mode continues to be triggered at a previously defined time on future days) for a pre-defined or user-defined amount of time (e.g., 5 minutes, 15 minutes, 30 minutes) that extends the initiation of the limited use mode without changing the actual time set for the limited use mode (e.g., as described below with reference to method 1100). In some embodiments, the user may select the ignore affordance 1059, thereby allowing the user to forgo initiation of the limited use mode for that particular day (such that the limited use mode continues to be triggered at the previously defined time on future days without changing the actual time set for the limited use mode) (e.g., as described below with reference to method 1100). In some embodiments, the device 500 stops displaying the extend affordance 1058 and the ignore affordance 1059 after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds) or when the user taps on any portion of the home screen 1050 (other than the description 1056, the extend affordance 1058, and the ignore affordance 1059). Under the "Notify" option, the 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) does not require the user to enter any authentication (e.g., a passcode) to extend or ignore the limited use mode on that device. For example, FIG. 10HH shows parent device 500 displaying home screen 1050 after a user selects either extend affordance 1058 or ignore affordance 1059 under the "Notifications" option. Because device 500 in FIG. 10HH is not in limited use mode (e.g., because it has been extended), the user can launch any applications associated with icons 424, 426, 416, 432, 434, 436, 440, 442, 452, 446, and 450 without restriction. By extending or ignoring entry into limited use mode, the user can, optionally, launch any applications or perform any application functions that may have otherwise been restricted (e.g., accessing widgets or websites associated with those apps, receiving notifications, suggesting those apps to the user, etc.).

FIG. 10II illustrates device 500 displaying home screen 1050 at the onset of the limited use mode under the “Notifications and Blocking” option of device downtime settings (e.g., as described above with reference to FIGS. 8QQ-8GGG and 10D). In some embodiments, device 500 can be 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). Device 500 optionally visually obscures home screen 1050 (e.g., blurs, grays out, or visually alters home screen) at the onset of the limited use mode, as shown in FIG. 10II. In some embodiments, device 500 is displaying a graphical user interface other than home screen 1050 (e.g., an application graphical user interface, a notification history graphical user interface, etc.) at the onset of the limited use mode, and device 500 visually obscures that graphical user interface (e.g., blurs, grays out, or visually alters that graphical user interface) at the onset of the limited use mode. In some embodiments, device 500 displays a description 1056 indicating that the limited use mode has been initiated, and a dismiss affordance 1057. For example, in FIG. 10II, a selection of dismiss affordance 1057 is detected (e.g., by a tap of contact 1003 detected on dismiss affordance 1057, as shown in FIG. 10II). In response to the selection of dismiss affordance 1057, device 500 stops displaying dismiss affordance 1057 and displays extend affordance 1058 and ignore affordance 1059, as shown in FIG. 10JJ. In some embodiments, a user selection of extend affordance 1058 allows the user to delay initiation of the limited use mode (such that the limited use mode continues to be triggered at a previously defined time on future days) for a pre-defined or user-defined amount of time (e.g., 5 minutes, 15 minutes, 30 minutes) that extends the initiation of the limited use mode without changing the actual time set for the limited use mode (e.g., as described below with reference to method 1100). In some embodiments, the user may forego initiation of the limited use mode for that particular day by selecting the ignore affordance 1059 (such that the limited use mode continues to be triggered at the previously defined time on future days without changing the actual time set for the limited use mode) (e.g., as described below with reference to method 1100). In some embodiments, the device 500 stops displaying the extend affordance 1058 and the ignore affordance 1059 after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds) or when the user taps on any part of the home screen 1050 (other than the description 1056, the extend affordance 1058, and the ignore affordance 1059). Under the "Notification and Blocking Options", 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) optionally requires the user to enter authentication (e.g., a passcode) to extend or ignore the limited use mode on that device. For example, in response to selecting either the extend affordance 1058 or the ignore affordance 1059 in FIG. 10JJ under "Notification and Blocking Options," the device 500 displays a passcode graphical user interface 1044, as shown in FIG. 10KK, requesting the user to enter a passcode before the restricted use mode can be extended or ignored. In some embodiments, the passcode requested in FIG. 10KK is different from the passcode to log on or unlock the device 500 (e.g., a passcode specific to the restriction settings). In some embodiments, a biometric is entered instead of a passcode to effect a change to the restriction settings (e.g., as described below in process 1100).

FIG. 10LL shows device 500 displaying home screen 1050 after the user has entered the appropriate passcode in passcode graphical user interface 1044 of FIG. 10KK under "notifications and blocking options." Because device 500 of FIG. 10LL is not in the restricted use mode (e.g., because it has been extended), the user may launch any applications associated with icons 424, 426, 416, 432, 434, 436, 440, 442, 452, 446, and 450 without restriction. Extending the entry into the restricted use mode may, optionally, allow launching any applications or performing any application functions that may have otherwise been restricted (e.g., accessing widgets or websites associated with those apps, receiving notifications, suggesting those apps to the user, etc.).

10MM illustrates a child device 500 displaying a home screen 1050 at the start of a limited use mode of a device downtime setting (e.g., as described above with reference to FIG. 10D). The child device 500 optionally visually obscures the home screen 1050 at the start of the limited use mode (e.g., blurs, grays out, or visually changes the home screen) as shown in FIG. 10MM. In some embodiments, the child device 500 displays a graphical user interface other than the home screen 1050 at the start of the limited use mode (e.g., an application graphical user interface, a notification history graphical user interface, etc.), and the child device 500 visually obscures that graphical user interface at the start of the limited use mode (e.g., blurs, grays out, or visually changes the graphical user interface). In some embodiments, the device 500 displays a description 1056 indicating that the limited use mode has started, and a dismiss affordance 1057. For example, in Figure 10MM, a selection of the reject affordance 1057 is detected (e.g., by a tap of contact 1003 detected on the reject affordance 1057, as shown in Figure 10MM). In response to the selection of the reject affordance 1057, the device 500 stops displaying the reject affordance 1057, as shown in Figure 10NN, and displays an affordance 1060 selectable to request more time before the limited use mode is implemented on the device 500 (e.g., to extend the start time of the limited use mode), and an affordance 1062 selectable to request more time on another device (e.g., on the parent device) (e.g., as described above with reference to Figures 8TT-8CCC). In some embodiments, selecting either affordance 1060 or affordance 1062 allows the parent to delay the start of the limited use mode such that the limited use mode continues to be triggered at a previously defined time on future days, without changing the actual time set for the limited use mode. For example, in Fig. 10OO, a selection of affordance 1062 is detected (e.g., by a tap of contact 1003 detected on affordance 1062, as shown in Fig. 10OO). In response to the selection of affordance 1026, device 500 initiates a process for requesting more time on another device (e.g., as described above with reference to Figs. 8WW-8CCC). For example, the process for requesting more time on another device may, as shown in Fig. 10PP, optionally send a message 1070 (editable by the user) in a messaging user interface to the parent device(s) with affordances for denying the request (e.g., affordance 1068a), extending the start time of the limited use mode for a predetermined period of time (e.g., affordances 1068b and 1068c), and customizing the period of extension (e.g., affordance 1068d) (e.g., as described above with reference to Figs. 8AAA-8CCC). In some embodiments, the process for requesting more time on another device sends a message 1066 with affordances to deny the request (e.g., affordance 1068a), to extend the start time of the limited use mode for a predetermined period of time (e.g., affordances 1068b and 1068c), and to customize the period of extension (e.g., affordance 1068d), as shown in FIG. 10QQ.

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

10SS illustrates touch screen 504 displaying home screen 1050 during the restricted use mode. In some embodiments, device 500 prevents or attempts to prevent access to all applications on the device during the restricted use mode, except for applications included on the application usage whitelist. In some embodiments, icons corresponding to restricted apps (e.g., applications not on the application usage whitelist that are subject to restrictions during the restricted use mode) are altered 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, grayed out, faded out, and/or visually altered) during the restricted use mode, as shown in FIG. 10SS. In some embodiments, a placeholder generic indication (e.g., a lock icon) 1070 is placed over or partially over the icon corresponding to the restricted application, as shown in FIG. 10SS. A placeholder generic indication (e.g., a lock icon) 1070 optionally replaces any unread notification indication corresponding to the restricted app (e.g., as shown in FIG. 10SS). In some embodiments, the placeholder generic indicator (e.g., a lock icon) is placed on 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 the home screen 1050 are selectable (e.g., during normal operation outside the limited use mode) to launch applications corresponding to those icons. During the limited use mode, the device 500 attempts to prevent access to restricted applications under a "Notifications" option (e.g., as described above with reference to Figs. 10C and 10FF). For example, under the "Notifications" option, a user of the device 500 (e.g., a parent device or a standalone device) can optionally select an icon corresponding to a restricted application during the limited use mode. For example, in Fig. 10TT, a selection of the icon 424 (corresponding to a restricted messaging app) is detected (e.g., by a tap of the contact 1003 detected on the icon 424 as shown in Fig. 10TT). In response to the selection of the icon 424, the device 500 optionally visually obscures the home screen 1050 (e.g., blurs, grays out, or visually alters the home screen), as displayed in Fig. 10UU. In some embodiments, device 500 displays a description 1056 indicating that access to the message app is restricted during the limited use mode, and a dismiss affordance 1057. For example, in FIG. 10UU, a selection of dismiss affordance 1057 is detected (e.g., by a tap of contact 1003 detected on dismiss affordance 1057, as shown in FIG. 10UU). In response to the selection of dismiss affordance 1057, device 500 stops displaying dismiss affordance 1057 and displays a proceed affordance 1072, as shown in FIG. 10VV. In some embodiments, a user's selection of proceed affordance 1072 allows the user to access the restricted message app during the limited use mode (e.g., as described below with reference to method 1100), as shown in FIG. 10WW. In some embodiments, the device 500 stops displaying the forward affordance 1072 after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds) or when the user taps anywhere on the home screen 1050 (other than the description 1056 and the forward affordance 1072).

Device 500 (e.g., a parent or standalone device) attempts to prevent access to restricted applications during the restricted use mode under a "notify and block" option (e.g., as described above with reference to FIG. 10C and FIG. 10II-10LL). In some embodiments, under the "notify and block" option, a user of device 500 can optionally select an icon corresponding to a restricted application during the restricted use mode. For example, in FIG. 10XX, selection of icon 424 (corresponding to a restricted message app) is detected (e.g., by a tap of contact 1003 detected on icon 424, as shown in FIG. 10XX). In response to selection of icon 424, device 500, as displayed in FIG. 10YY, optionally visually obscures home screen 1050 (e.g., blurs, grays out, or visually alters the home screen) and displays passcode graphical user interface 1044 requesting the user to enter a passcode to access the restricted message app during the restricted use mode. In some embodiments, the passcode requested in FIG. 10YY is different from the passcode to log on or unlock device 500 (e.g., a passcode specific to the restriction settings). In some embodiments, a biometric is entered instead of a passcode to effect a change to the restriction settings (e.g., as described below in process 1100).

In some embodiments, the child device 500 attempts to prevent access to restricted applications while in the restricted use mode. In some embodiments, a user of the child device 500 may select an icon corresponding to a restricted application while in the restricted use mode. For example, in FIG. 10ZZ, a selection of icon 424 (corresponding to a restricted messaging app) is detected (e.g., by a tap of contact 1003 detected on icon 424, as shown in FIG. 10ZZ). In response to selection of icon 424, the child device 500, as shown in FIG. 10AAA, optionally visually obscures the home screen 1050 (e.g., blurs, grays out, or visually modifies the home screen) and displays a selectable affordance 1082 for requesting access to the Messages app in limited use mode on the child device 500 (e.g., by requesting the parent to enter a passcode directly on the device 500) and a selectable affordance 1084 for requesting access to the Messages app in limited use mode on another device (e.g., requesting that access be granted from the parent device via an iMessage or notification) (e.g., as described above with reference to FIGS. 8TT-8CCC and 10NN-10QQ).

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

As described below, method 1100 provides a way to selectively limit access to applications on an electronic device while in a restricted use mode. This method reduces usage of the electronic device for a specific period of time without the user having to monitor the user's usage. For battery-operated electronic devices, limiting access to applications for a specific period of time conserves power and increases the time between battery charges.

In some embodiments, an electronic device (e.g., a mobile device including a touch screen such as device 500 including touch screen 504, a computer or tablet computer including one or more of a keyboard, a mouse, a trackpad, and a touch screen such as touch screen 504, a wearable device such as a smart watch including a touch screen, or a set-top box in communication with a television and an input device (e.g., a remote controller)) (e.g., a mobile phone such as device 100, device 300, or device 500, a tablet computer, etc.) in communication with a display and one or more input devices receives a series of one or more inputs (e.g., from one or more input devices of the electronic device or from a second electronic device different from the electronic device) to define one or more time windows associated with a limited use mode, such as in Figures 10A-10E, during which access to one or more applications on the electronic device is limited (1102). In some embodiments, the limited use mode is a bedtime limited use mode. In some embodiments, the electronic device is a child device, and one or more inputs are received from a parent device that communicates (e.g., wirelessly communicates) with and is associated with the child device (e.g., user accounts for both the parent device and the child device are associated with a family or other group account). For example, a user of the electronic device defines a time of day (e.g., 10:00 PM to 5:00 AM) as a bedtime restricted use mode during which the electronic device prevents or attempts to prevent access to all applications on the electronic device except for applications that, in some embodiments, are included on a whitelist of applications. In some embodiments, the user defines the window of time and does not specify any particular applications to which access is restricted. In such embodiments, the electronic device optionally defaults to restricting or attempts to restrict use of all applications except for whitelisted applications during the restricted use mode.

While one or more time windows associated with the limited use mode are defined (1104), and during the one or more time windows associated with the limited use mode, the electronic device optionally receives input via one or more input devices (1106) to start a first application of a plurality of applications installed on the electronic device, such as in FIG. 10TT (e.g., input to open and/or use an application on the electronic device when the one or more time windows are implemented (e.g., an application that was being used when the limited use mode was implemented)). In some embodiments, in response to receiving the input to launch the first application (1108), in accordance with a determination that the first application is not included in an application usage whitelist (e.g., a list of applications that are not subject to limited access during the limited use mode (e.g., may be fully or partially accessible during the bedtime limited use mode)), the electronic device restricts access to the first application (1110), such as in FIG. 10TT-FIG. 10AAA (e.g., prohibits launching the application, restricts the functionality of the application, or requires further action by the user to launch the application, such as displaying a dialog box indicating a bedtime restriction when the user attempts to launch the application and requesting further confirmation from the user to proceed with the application). In some embodiments, in response to receiving the input to launch the first application, in accordance with a determination that the first application is included in the application usage whitelist, the electronic device provides access to the first application (1112), such as in FIG. 10I (e.g., launches the application normally as if the limited use mode was not in effect).

In some embodiments, one or more time windows associated with the bedtime restricted use mode are preset by a user of the electronic device or remotely set by a user of a different electronic device that communicates with the electronic device. In some embodiments, when an application is launched outside of the bedtime restricted use mode, no bedtime usage restrictions are enforced (e.g., the application is launched normally as if the restricted use mode was not implemented). In some embodiments, access to the first application is provided with certain restrictions (e.g., the application can be launched but has limited functionality during the bedtime restricted mode). For example, a phone application is optionally on a whitelist for use in communicating with certain contacts (e.g., relatives), and the phone application is launched with limited communication with other contacts. In some embodiments, the electronic device enters the restricted use mode while a restricted application (e.g., an application not on the application usage whitelist) is running, and the restricted application is associated with a "notify" restriction option or a "block and notify" restriction option (e.g., as described in more detail below). For example, under the "notify" restriction option, the electronic device displays (e.g., obscures) a pop-up indication over the running application indicating that application usage is currently restricted (e.g., because a bedtime restriction is in place), which optionally includes one or more affordances that, when selected, allow the user to continue using the application. Under the "notify and block" restriction option, the electronic device displays (e.g., obscures) a pop-up indication over the running application indicating that the user is blocked from using the application (e.g., blurs the application), and optionally includes an indication requesting authentication credentials (e.g., password, passcode, biometric, or consent from a parent device/account) to continue using the application. 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 as 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 use mode allows an electronic device to efficiently and selectively restrict use of specific applications during specific time periods, thereby reducing use of the electronic device during those time periods, as well as reducing power consumption and improving battery life of the device.

In some embodiments, such as FIG. 10F, the one or more time windows associated with a limited use mode (e.g., a bedtime limited use mode) are a first one or more time windows on a first day of a week (1114), and the one or more time windows associated with the limited use mode are a second one or more time windows on a second day of the week that are different from the first one or more time windows (e.g., the different days can have different settings (times, usage limits, etc.) for the limited use mode) (1116). For example, the times for the bedtime limited use mode during which the electronic device prevents or attempts to prevent access to certain applications on the electronic device are defined differently for different days of a week (e.g., 10 p.m. to 5 a.m. on Monday, 11 p.m. to 6 a.m. on Saturday, 9 p.m. to 5 a.m. on weekdays, and 11 p.m. to 7 a.m. on weekends). The above-described method of defining different times for the bedtime restricted use mode for different days of the week makes the user's interface with the device more efficient (e.g., the user does not need to update the time for the bedtime restricted use mode every day, thus reducing the input provided by the user to the device (e.g., input to update the time for the bedtime restricted use mode)), thereby enabling the electronic device to efficiently reduce the overall use of the electronic device, as well as reducing power consumption and improving the battery life of the device.

In some embodiments, while one or more time windows associated with the limited use mode are defined, pursuant to a determination that the current time at the electronic device is a threshold time prior to one or more time windows associated with the limited use mode (e.g., 5 minutes, 10 minutes, 1 hour, or any period of time prior to initiation of the limited use mode), the electronic device presents (1118) an indication (e.g., text, image, sound, haptic and/or tactile output, etc.) that one or more time windows associated with the limited use mode are approaching (e.g., an indication indicating that the limited use mode (e.g., bedtime restricted use mode) is about to be implemented within the threshold time (e.g., 5 minutes, 10 minutes, 1 hour, or any period of time), such as in FIG. 10EE). In some embodiments, the threshold time is defined by a user. In some embodiments, the notification includes text, image(s), and/or sound. In some embodiments, the notification includes a haptic and/or tactile output indication. The above-described method of notifying the user that the restricted use mode will soon be implemented provides a more efficient user-device interface (e.g., it eliminates the need for the user to monitor the time, provides the user with an opportunity to finish tasks currently running on the device, and prompts the user to stop using the device in anticipation of the restricted use mode, thus reducing inputs provided by the user to the device (e.g., inputs to update the time for the bedtime restricted use mode)), thereby allowing the electronic device to efficiently reduce overall usage of the electronic device, as well as reducing power consumption and improving the device's battery life.

In some embodiments, the indication that one or more time windows associated with the limited use mode are approaching includes a visual indication (1120), which includes an affordance for delaying initiation of the limited use mode past one or more time windows associated with the limited use mode, such as in FIGS. 10EE-10QQ (e.g., a user can delay initiation of the limited use mode (e.g., such that the limited use mode continues to be triggered at a previously defined time on future days without changing the actual time set for the limited use mode). In some embodiments, the affordance includes a predefined amount of time (e.g., 5 minutes, 15 minutes, 30 minutes) for extending initiation of the limited use mode. In some embodiments, the affordance allows the user to manually change the start time of the limited use mode (e.g., manually enter a different start time). In some embodiments, the electronic device allows the user to delay initiation of the limited use mode at any time up to and including the start of the limited use mode (e.g., a user can delay initiation of the limited use mode until a later time). The limited use mode may be overruled for a fixed period of time or for the remainder of the day). Delaying the onset of the limited use mode optionally allows launching of any applications or performing any application functions that may otherwise have been restricted (e.g., accessing widgets or websites associated with those apps, receiving notifications, suggesting those apps to the user, etc.). If the electronic device is a child device in a family account (e.g., a device of a user designated as a child as opposed to a parent or administrator in a family account), the displayed notification optionally includes an affordance for requesting permission from an adult/parent device in the family account to extend the limited use mode (e.g., extend the onset of the limited use mode by 15 minutes, 30 minutes, 1 hour, etc.). In such a case, selection of the request in the notification optionally results in a notification being delivered to one or more (or all) parent devices associated with the family account, and if permission is granted by at least one of the parent devices, the electronic device extends the onset time of the limited use mode. In some embodiments, the affordance allows the user to prevent the electronic device from entering the limited use mode. In some embodiments, app usage that exceeds the permitted limit (e.g., even if approved by extending the time) is optionally indicated in the dashboard user interface described above with reference to method 700 (e.g., as shown in FIGS. 6L-6P, 6EE-6HH, 6OO-6SS, and 6UU). The above-described method of providing affordances for the user to extend the start of the limited use mode makes the user's interface with the device more efficient (e.g., providing the user with an opportunity to extend the start time of the limited use mode to finish a task currently running on the device without the user having to monitor the time, prompting the user to stop using the device in anticipation of the limited use mode, thus reducing inputs provided by the user to the device (e.g., inputs to update the time for the bedtime limited use mode)), thereby allowing the electronic device to efficiently reduce the overall use of the electronic device, and in addition, reducing power consumption to improve the battery life of the device.

In some embodiments, outside of one or more time windows associated with the limited use mode, one or more application icons associated with applications not included on the application whitelist are displayed (1122) with a first visual characteristic, such as that of FIG. 10RR (e.g., displaying the icons of applications not on the application whitelist normally, such as in color and not grayed out, outside of the limited use mode), and during one or more time windows associated with the limited use mode, one or more application icons associated with applications not included on the application whitelist are displayed (1124) with a second visual characteristic different from the first visual characteristic, such as that of FIG. 10SS (e.g., displaying the icons of applications not on the application whitelist differently during the limited use mode than during outside of the limited 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 the limited use mode (compared to their color outside of the limited use mode) and/or a placeholder generic indicator is displayed over (or partially over any portion of) the icons for those applications in the limited use mode. In some embodiments, a placeholder generic indicator (e.g., a lock icon) is placed on or adjacent to the text associated with the application icon. In some embodiments, the 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 received for that application is overlaid on a portion of the icon). In such embodiments, for those applications not included in the application whitelist, their visual indications are removed, grayed out, the number of notifications is removed, replaced with a placeholder generic indication (e.g., a lock icon), or otherwise modified such that the notification state (e.g., the 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 notifications for the application, the lock icon replaces the notification indication). In some embodiments, icons for applications on the application whitelist are displayed the same (e.g., in color, not grayed out, freely accessible, etc.) during both the restricted use mode and outside the restricted use mode. The above-described method of differently displaying restricted applications during a restricted use mode allows a user to determine which applications are restricted, thereby enabling the electronic device to efficiently and selectively restrict use of specific applications for specific time periods by providing an indication of which applications the user does or does not have access to during the restricted use mode, thereby reducing use of the electronic device during those time periods and, in addition, reducing power consumption to improve battery life of the device.

In some embodiments, restricting access to the first application includes the electronic device presenting an indication (1126) indicating that access to the first application is restricted, such as in FIG. 10UU (e.g., displaying a visual indication on a display, playing a sound on a speaker associated with the electronic device, generating haptic(s) and/or tactile output(s), etc., indicating that the application is restricted (e.g., a notification)). Optionally, the indication includes an affordance (1128) selectable to provide access to the first application without requiring authentication credentials, such as in FIG. 10UU-FIG. 10VV (e.g., a graphical user interface element, link, or soft button through which the user can access the restricted application during 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. When a user attempts to launch an application associated with a "notification" restriction (e.g., by selecting an icon for that application from the home screen of the electronic device while in the restricted use mode, and assuming that the application is not included in the application whitelist), the electronic device optionally displays a pop-up indication indicating that application usage is currently restricted (e.g., because a bedtime restriction is in place). The pop-up notification optionally includes one or more affordances that, when selected, allow the user to proceed to the application without having to enter any authentication credentials (e.g., an "ignore for one day" affordance that opens the application without having to enter administrator or other credentials). The above-described method of notifying the user that an application is restricted while in the restricted use mode, but giving the user the option to nevertheless access the application when needed, allows the electronic device to effectively restrict the use of a particular application for certain periods of time while still allowing the user to perform necessary tasks on the electronic device, thereby reducing the use of the electronic device during those periods, and in addition reducing power consumption to improve the device's battery life.

In some embodiments, restricting access to the first application includes the electronic device presenting an indication indicating that access to the first application is restricted (1130), such as in FIG. 10UU. Optionally, the indication includes a selectable affordance to provide access to the first application while requiring authentication credentials (1132), such as in FIG. 10VV (e.g., displaying a visual indication on a display, playing a sound on a speaker associated with the electronic device, generating a haptic(s) and/or tactile output, etc., indicating that the application is restricted (e.g., a notification)). In some embodiments, the electronic device allows one or more applications to be associated with a "notify and block" restriction option. If a user attempts to launch an application associated with a "notify and block" restriction (e.g., by selecting an icon for that application from the home screen of the electronic device while in the restricted use mode, and assuming that the application is not included in the application whitelist), the electronic device blocks the application from launching and, optionally, displays a pop-up indication indicating that application usage is currently restricted (e.g., because a bedtime restriction is in place). In some embodiments, the pop-up indication requests authentication credentials (e.g., a password, passcode, biometric, or consent from a 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 in a family account (e.g., a device of a user designated as a child as opposed to a parent or administrator in a family account), the displayed notification optionally includes an affordance for requesting permission from an adult/parent device in the family account to access the application while in the restricted use mode. In such a case, selection of the request in the notification optionally results in a notification being delivered to one or more (or all) parent devices associated with the family account, and if permission is granted (e.g., at least one of the parent devices, or at the child device via a passcode), the electronic device allows access to the application. In some embodiments, the parent is required to enter a passcode at the parent device to allow access to the restricted application on the child device from the parent device. The above-described methods of blocking launching of applications during a restricted use mode and notifying the user that the application is restricted allow the electronic device to effectively restrict use of certain applications for certain periods of time, thereby reducing use of the electronic device during those periods, as well as reducing power consumption to improve the device's battery life.

In some examples, following a determination that the electronic device is not a child device (e.g., not a child device in a family account (e.g., a parent device in a family account) or not associated with a family account at all), selection of the affordance triggers a request to enter a passcode to access the first application, such as in FIG. 10YY (1134). 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., based on a classification of a user account associated with the electronic device or an option selected on the electronic device). For example, the determination that the electronic device is a parent device is optionally based on a determination that a user account associated with the electronic device (e.g., a user currently signed in to the device) is classified as a parent account. In some embodiments, the determination that the electronic device is a parent device is optionally based on a determination that the electronic device is configured as a parent device in the device's settings (e.g., configured during initial setup of the device). In some embodiments, the request to enter a passcode is a pop-up notification that optionally includes one or more affordances that, when selected, allow the user to proceed to the application only if the appropriate authentication credentials (e.g., password, passcode, biometric, or consent from a parent device/account) are provided. Detecting the biometric optionally includes detecting the user's face with a depth camera or another sensor. In some embodiments, the affordances include one or more of soft buttons or input fields (single or multiple) for a user ID, password, and/or passcode. For example, if the device is not a child device in a family account (e.g., is a parent device in a family account) or is not associated with a family account at all, the electronic device optionally requests that the user enter credentials (e.g., user ID and/or password, passcode) for the user account to which the electronic device is associated (e.g., user ID and/or password or passcode associated with the profile to which the device is configured). In some embodiments, the credentials (e.g., user ID and/or password, passcode) are different from the credentials for accessing the electronic device (e.g., a different passcode than that used to "unlock" and/or log into the device). In this way, a user (e.g., a child) who is not the owner (e.g., a parent) of the device will not be able to circumvent the restricted use mode unless the user enters a secondary passcode.

In some examples, pursuant to a determination that the electronic device is a child device (e.g., based on a classification of a user account associated with the electronic device or an option selected on the electronic device), selection of the affordance causes the display to present a first affordance requesting entry of a passcode to access the first application (e.g., a parental control passcode that is different from a passcode to unlock the device or to access a user account associated with device operation), such as in FIG. 10MM-FIG. 10QQ, and a second affordance that, when selected, initiates a process to request access to the first application from the parent device (e.g., initiates a process to request more time from the parent device in a family account) (1136). For example, the determination that the electronic device is a child device is optionally based on a determination that a user account associated with the electronic device (e.g., a user currently signed in to the device) is classified as a child account. In some embodiments, the determination that the electronic device is a child device is optionally based on a determination that the electronic device is configured as a child device in the settings of the device (e.g., configured during initial setup of the device). 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, an email request to an email account associated with the parent(s)). This process then allows the parent to grant the child device access to the restricted application (e.g., the parent can choose to allow the child device to access the restricted application while in the restricted use mode) or deny the child device access to the restricted application. In some embodiments, the electronic device presents an affordance for entering a passcode and/or an affordance for initiating the process of requesting access to the first application. In some embodiments, the passcode is a parental control passcode or a usage 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 can optionally enter a passcode that allows the electronic device to access the first application. In some embodiments, the parent is required to enter a passcode on the parent device to allow access to the restricted application on the child device from the parent device. The above-described method of informing a user that an application is restricted during a limited use mode, but allowing the user the option to nevertheless access the application when necessary, allows the electronic device to effectively restrict the use of certain applications for certain periods of time while still allowing the user to perform necessary tasks on the electronic device, thereby reducing use of the electronic device during those periods, and in addition reducing power consumption to improve the device's battery life.

In some embodiments, the electronic device receives (1138) a series of one or more inputs via one or more input devices to activate or deactivate enforcement of one or more limited use mode restrictions, including one or more time windows associated with the limited use mode, such as in FIG. 10C (e.g., manually turning on or off enforcement of the limited use mode on the electronic device in accordance with the limited use mode restrictions during one or more time windows associated with the limited use mode). For example, turning off enforcement of limited use mode rules that define usage restrictions between the hours of 10 PM and 7 AM (e.g., one or more time windows associated with the limited use mode) disables the usage restrictions between the hours of 10 PM and 7 AM (e.g., during vacation). Conversely, turning on enforcement of the same limited use mode rules enables those usage restrictions between the hours of 10 PM and 7 AM. In some embodiments, enforcement of the restricted use mode rules may be toggled on or off during or outside of one or more time windows associated with the restricted use mode (e.g., controlling whether the electronic device enters (when toggled on outside of one or more time windows) or exits (when toggled off during one or more time windows) the restricted use mode during one or more time windows associated with the restricted use mode). In some embodiments, the electronic device stores the use limit settings (e.g., user-defined start time(s), end time(s), whitelist(s), etc.) when enforcement of the restricted use mode is turned off, such that the use limit settings are maintained the next time the restricted use mode is turned on. For example, when enforcement of the restricted use mode rules is turned back on (after being turned off), the electronic device optionally enforces the restricted use mode restrictions according to the same restricted use mode rules that were set up before the restricted use mode was turned off (e.g., enforcing the restricted use mode between the hours of 10 PM and 7 AM when the restricted use mode is toggled back on). In some embodiments, pursuant to a determination that enforcement of one or more restricted use mode restrictions is turned on, the electronic device implements (1140) one or more restricted use mode restrictions, such as in FIG. 10C (e.g., operates the electronic device outside the restricted use mode or in the restricted use mode (in accordance with the restricted use mode rules)). For example, during the restricted use mode, the electronic device operates to prohibit the restricted application from being launched, to limit the functionality of the restricted application, and to require further action by the user to launch the restricted application, such as displaying a dialog box indicating a bedtime restriction and requesting further confirmation from the user to proceed with the application when the user attempts to launch the restricted application. In some embodiments, access to a first application is provided with certain restrictions (e.g., the application can be launched but is limited in functionality during the bedtime restricted mode). For example, a phone application is optionally on a whitelist for use in communicating with certain contacts (e.g., relatives), and the phone application is launched with restrictions on communicating with other contacts.

In some embodiments, following a determination that enforcement of one or more limited use mode restrictions has been turned off, the electronic device forgoes enforcement of one or more limited use mode restrictions (1142), such as in FIG. 10C and FIG. 10HH (e.g., operates the electronic device outside the limited use mode while enforcement of the limited use mode is turned off, independent of whether the current state of the electronic device (e.g., the current time) would otherwise have caused the device to operate in the limited use mode). For example, outside the limited use mode, the electronic device allows applications to be launched normally as if the limited use mode was not in effect. In some embodiments, when an application is launched outside the bedtime limited use mode, the bedtime use restrictions are not enforced (e.g., the application is launched normally as if the limited use mode was not in effect). In some embodiments, the electronic device provides a toggle switch for toggling enforcement of the limited use mode on or off. Thus, even if the current time is within one or more limited use time windows but the limited use mode is turned off, restrictions associated with the limited use mode are not enforced. The above-described method of allowing a user to manually enforce or not enforce restricted use mode rules allows the electronic device to customize the enforcement of the restricted use mode as desired by the user, thereby selectively reducing usage of the electronic device and, in addition, reducing power consumption to improve the device's battery life.

In some embodiments, restricting access to the first application includes presenting one or more verbal indications that access to the first application is restricted (1144) (e.g., in some embodiments, in addition to the visual notification(s) described above, an audible voice verbal notification indicating that access to the application is restricted). In some embodiments, the electronic device performs the verbal notification only pursuant to a determination that the limited use indication will be spoken (e.g., based on a specification of a user account associated with the electronic device or based on an electronic device setting). 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. In some embodiments, the electronic device optionally does not perform the verbal notification pursuant to a determination that the limited use indication will not be spoken (e.g., displays the notification without an audible voice indicating that access to the application is restricted). In some embodiments, the notification optionally includes a sound (e.g., a chime, an alert, music, etc.) without a voice reading the notification. In some embodiments, any of the notifications described herein may be audibly generated by the electronic device (e.g., read to a user of the electronic device), for example, to facilitate providing such notifications to a user (e.g., a child) who is unable to read or see them. The above-described methods of providing an audible notification while restricting access to an application during a limited use mode allow the electronic device to effectively restrict use of certain applications while in the limited use mode, optionally while not displaying additional information, thereby reducing power consumption and improving battery life of the device.

In some embodiments, a phone application on the electronic device (e.g., an application that enables outgoing and incoming voice and/or video calls on the electronic device) is permanently included in the application usage whitelist (1146) (e.g., access to the phone app is not restricted during the limited use mode). In some embodiments, the electronic device has phone functionality (e.g., can make and receive calls, etc.) performed using a phone application installed on the electronic device, such as in FIG. 10H (e.g., in the same way that other applications, such as messaging applications, email applications, video applications, etc., are installed on the electronic device). In such embodiments, the phone application is optionally always (e.g., permanently) included in the application whitelist, such that the limited use mode restrictions do not apply to the phone application. Thus, the user can, optionally, use the phone application as normal, regardless of whether the limited 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 freely available to contact certain contacts), and 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 during a limited use mode allows an electronic device to effectively restrict use of certain communication applications while in a limited use mode, thereby reducing power consumption and improving battery life of the device.

In some embodiments, while one or more time windows associated with the limited use mode are defined and during one or more time windows associated with the limited use mode (e.g., during the limited use mode (e.g., bedtime mode)), communication operations (e.g., calling, texting, emailing, and/or video conferencing operations) using the phone application are permissible for anyone (1148), such as in FIG. 10J-10M (e.g., communication operations are not restricted to any particular contacts during the limited use mode), or are permissible only for one or more designated contacts of a plurality of contacts on the electronic device (e.g., communication is restricted to contacts stored on the electronic device during the limited use mode, contacts in a designated group of contacts on the electronic device, or contacts on a whitelist). In some embodiments, the contacts with which the phone application can communicate without restriction can be defined on the electronic device. For example, the electronic device optionally provides a setting for allowing the phone application to communicate (e.g., make calls, receive calls, etc.) with all contacts (e.g., “anyone” setting) or a designated subset of contacts (e.g., “contacts” setting) without restriction during the limited use mode. In some embodiments, the electronic device provides a user interface that allows a phone application to communicate with only selected individuals (e.g., contacts on the electronic device, or only specific contacts on the electronic device) without restriction while in the limited use mode. Communications with other individuals are optionally restricted in the manner described above (e.g., not allowed, not allowed without user ID/password, passcode, biometric, or permission from a parent device, etc.). The above-described manner in which a user can selectively limit access to communication operations to specific contacts during the limited use mode allows the electronic device to effectively restrict use of certain communication applications while in the limited use mode, thereby reducing power consumption and improving battery life of the device.

In some embodiments, the communication operations include incoming and outgoing communications (e.g., outgoing and/or incoming phone calls, emails, text messages, and video conference calls) (1150). While in the limited use mode, the electronic device prevents communications from anyone not designated for communication during the limited use mode (e.g., blocks calls, text messages, video conference requests, etc.). The above-described methods by which a user can selectively limit access to communication operations to specific contacts during the limited use mode allow the electronic device to effectively restrict use of certain communication applications while in the limited use mode, thereby reducing power consumption and improving battery life of the device.

In some embodiments, the electronic device receives (1152), such as in FIG. 10CC, contact information (e.g., from another electronic device (e.g., parent device)) for a first contact from another electronic device that communicates (e.g., via a wireless or wired connection) with the electronic device. In some embodiments, the electronic device allows (1154) communication with the first contact during a limited use mode (e.g., to allow communication operations to be performed on the first contact when communication restrictions are set (e.g., when communication operations are permitted only with contacts specified on the electronic device during the limited use mode), such as in FIG. 10M). In some embodiments, the electronic device automatically saves the received contact information for the first contact among a plurality of contacts stored on the electronic device. Optionally, the electronic device and the other electronic device are associated (1156) with the same user group account (e.g., a "family" or "family sharing" account), such as in FIG. 10W. In some embodiments, the other electronic device is a parent device in a family account. In such embodiments, the parent device can share one or more of the parent's contacts (e.g., contact information such as name, phone number, email address, etc.) with the child device. For example, the parent device can send and store contact information for a contact on the parent device to the child device through selection of a "Share with Child Device" affordance on the parent device (e.g., without having to specify the child's contact information or the target device to send the contact information to). In some embodiments, the parent is required to enter a passcode on the parent device to send and store the contact information on the child device. The above-described methods by which a user can selectively restrict access to communication operations to specific contacts during a limited use mode allow the electronic device to effectively restrict use of certain communication applications while in the limited use mode, 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 the electronic device, such as FIG. 10M (e.g., contacts stored on the electronic device, contacts in a designated group of contacts on the electronic device, or contacts on a whitelist while the limited use mode is enabled) are customizable (1158) (e.g., contacts can be added to or removed from a contact whitelist (e.g., contacts whose communication operations are not restricted during the limited use mode)). In some embodiments, certain contacts not included in or on the contact whitelist can be controlled by the electronic device. For example, certain contacts on the electronic device can be designated as “permissible” or “unrestricted” such that communication with those contacts during the limited use mode is not restricted (e.g., communication with other contacts or individuals is optionally restricted during the limited use mode). In some embodiments, these “unrestricted” contacts are defined on the electronic device itself (e.g., in a settings user interface of the electronic device itself). In some embodiments, these “unrestricted” contacts are defined on another device (e.g., defined for the child device on a parent device in a family account if the current device is a child device in a family account). In some embodiments, the parent is required to enter a passcode at the parent device to define "unrestricted" contacts on the child device from the parent device. The above-described methods by which a user can selectively restrict access to communication operations to specific contacts during a restricted use mode allow the electronic device to effectively restrict the use of certain communication applications while in the restricted use mode, thereby reducing power consumption and improving the device's battery life.

In some embodiments, one or more designated contacts of a plurality of contacts on an electronic device that are enabled for communication operations during one or more time windows associated with a limited use mode (e.g., during a limited use mode (e.g., a bedtime mode)) are different from a second one or more designated contacts that are enabled for communication operations outside of one or more time windows associated with a limited use mode, such as in FIGS. 10O-10S (e.g., a daytime contacts whitelist whose communication operations are not restricted during the limited use mode) (1160). In some embodiments, the daytime contacts whitelist is different from a bedtime contacts whitelist (e.g., contacts whose communication operations are not restricted during the limited use mode). For example, if the limited use mode is set to be from 10 p.m. to 6 a.m., an application and/or contacts whitelist between 10 p.m. and 6 a.m. is optionally different from an application and/or contacts whitelist between 6 a.m. and 10 p.m. (e.g., different applications and/or contacts may be restricted in different ways between the two time periods). In some embodiments, certain contacts may be listed on both the daytime contact whitelist and the bedtime contact whitelist (e.g., contacts are optionally overlapped in both whitelists). 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 limited use mode. In some embodiments, a parent may set or update the daytime and/or bedtime contact whitelists from the parent device. In some embodiments, a parent is required to enter a passcode on the parent device to set or update the daytime and/or bedtime contact whitelists on the child device from the parent device. The above-described methods by which a user may selectively restrict access to communication operations to certain contacts during and outside of the limited use mode allow an electronic device to effectively restrict use of certain communication applications while in the limited use mode, thereby reducing power consumption and improving battery life of the device.

In some embodiments, the electronic device receives input via one or more input devices to add a second application of a plurality of applications installed on the electronic device to an application usage whitelist (1162), such as in FIG. 10I-FIG. 10J. Pursuant to a determination that the second application is included in the application usage whitelist while one or more time windows associated with the restricted use mode are defined and during one or more time windows associated with the restricted use mode, the electronic device provides access to the second application (1164), such as in FIG. 10J (e.g., adds the application to a list of applications that are not restricted during the restricted use mode). In some embodiments, any application installed on the electronic device can be added to the application whitelist (e.g., defined for the child device at a parent device in the family account, if the current device is a child device in a family account) either within a settings user interface of the electronic device itself or via another device. In some embodiments, the parent is required to enter a passcode on the parent device to set or update the application whitelist on the child device from the parent device. The above-described method of allowing a user to selectively restrict access to certain applications while in a limited use mode allows an electronic device to effectively restrict use of certain communication applications while in the limited use mode, thereby reducing power consumption and improving battery life of the device.

In some embodiments, the electronic device receives one or more inputs (1166) for modifying one or more restricted use mode settings associated with the restricted use mode, such as in FIG. 10F (e.g., modifying the start/end time of the restricted use mode, modifying a whitelist, etc.). In response to receiving one or more inputs for modifying one or more restricted use mode settings (1168), the electronic device requests authentication (1170) before performing one or more restricted use mode setting changes, such as in FIG. 10T-FIG. 10V (e.g., requesting a user of the electronic device to enter a passcode to make the restricted use mode changes), in response to receiving one or more inputs for modifying one or more restricted use mode settings at the child device, such as in FIG. 10F (e.g., modifying the start/end time of the restricted use mode, modifying a whitelist, etc.). In response to receiving one or more inputs for modifying one or more restricted use mode settings at the child device, such as in FIG. 10F (e.g., modifying a start/end time of the restricted use mode, modifying a whitelist, etc.), the electronic device requests authentication (1170) before performing one or more restricted use mode setting changes, such as in FIG. 10T-FIG. 10V (e.g., requesting a user of the electronic device to enter a passcode to make the restricted use mode changes). For example, the determination that one or more inputs for modifying one or more restricted use mode settings have been received at the child device is optionally based on a determination that a user account associated with the electronic device (e.g., a user currently signed in to the device) is classified as a child account. In some embodiments, the determination that one or more inputs to change one or more restricted use mode settings are received at the child device is optionally based on a determination that the electronic device is configured as a child device in the device's settings (e.g., configured during initial setup of the device). In some embodiments, if the electronic device is a child device in a family account, any of the restricted use mode settings or preferences or rules described herein can be changed at the child device only upon entry of a password or other authentication credential at the child device (e.g., upon determining that one of the settings is about to be changed, the electronic device prompts the user to enter a password that must be authenticated before the change is allowed). In some embodiments, the authentication credential is the same as the credential to unlock the device (e.g., a passcode to unlock the device). In some embodiments, the authentication credential is different from the credential to unlock the device (e.g., a parent's credential in a family account). In some embodiments, the parent device can remotely change the above settings implemented on the child device (e.g., optionally, upon entry of a parent's credential at the parent device). In some embodiments, the parent is required to enter a passcode on the parent device to remotely change the above settings on the child device. In response to receiving one or more inputs for changing one or more restricted use mode settings (1168), according to a determination that one or more inputs for changing one or more restricted use mode settings were received from outside the electronic device via the parent device (e.g., the restricted use mode change was made on the parent device), the electronic device performs one or more restricted use mode setting changes (1172) (e.g., making the restricted use mode change without the need to enter additional credentials), such as in Figures 10X-10CC. For example, the determination that one or more inputs for changing one or more restricted use mode settings were received via the parent device is, optionally, based on a determination that a user account associated with the other device (e.g., a user currently signed in to the device) is classified as a parent account. In some embodiments, the determination that one or more inputs for changing one or more restricted use mode settings were received via the parent device is, optionally, based on a determination that the other device is configured as a parent device in the device's settings (e.g., configured during initial setup of the device). In some embodiments, the electronic device is a parent device. In some embodiments, the electronic device is different from the parent device (e.g., the electronic device is a child device). In some embodiments, the parent device remotely changes the restricted use mode settings on the child device (e.g., via the Internet, Bluetooth, or other networks or protocols). In some embodiments, the parent is required to enter a passcode on the parent device to remotely change the restricted use mode settings on the child device. The above-described methods of limiting the ability to change the restricted use mode settings allow the electronic device to efficiently and selectively restrict the use of certain applications for certain periods of time, thereby reducing the use of the electronic device during those periods, as well as reducing power consumption to improve the device's battery life.

In some embodiments, in response to executing one or more restricted use mode setting changes received from outside the electronic device, the electronic device presents (1174) an indication (e.g., a visual indication (e.g., one or more of text and images), a sound indication, a verbal indication, and/or a tactile and/or tactile output indication) regarding one or more restricted use mode setting changes, such as FIG. 10CC (e.g., presenting a notification that the restricted use mode settings have been remotely changed by the parent device). In some embodiments, when the parent device remotely changes the above settings implemented on the child device, the child device displays a notification that such remote change has been made, details of the change (e.g., the parent device has changed the time window during 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 the restricted use mode settings allows the electronic device to efficiently and selectively restrict the use of certain applications for certain time periods, thereby reducing the use of the electronic device during those time periods, as well as reducing power consumption to improve the battery life of the device.

In some embodiments, outside of the one or more windows of time associated with the limited use mode, the electronic device displays one or more representations of the application installed on the electronic device (e.g., an icon, widget, a window of the first application in a multitasking view with other windows of the other applications) (1176), such as in FIG. 10RR. For example, the electronic device displays one or more application windows associated with the one or more applications (e.g., in a multitasking graphical user interface view), or the electronic device displays one or more icons for launching the application on a home screen of the electronic device. The one or more representations include a first representation of the first application with a first visual characteristic (e.g., in color, without obscuring, etc., displaying a normal icon for the application installed on the electronic device when not in the limited use mode (e.g., in a home screen of the electronic device)). In some embodiments, pursuant to a determination that the first application is not included in an application usage whitelist (e.g., a list of applications that are not subject to limited access during the limited use mode (e.g., may be fully or partially accessed during the limited use mode)) during one or more windows of time associated with the limited use mode (1178) (e.g., in response to a start of one or more windows of time associated with the limited use mode), the electronic device displays (1180) a first representation of the first application with a second visual characteristic that is different from the first visual characteristic (e.g., an appearance of a representation of an application that is not on the application whitelist differs from an appearance of a representation of an application that is not on the application whitelist), such as in FIG. 10SS. In some embodiments, during the limited notification mode, the electronic device changes the appearance of various aspects of applications that are not included in the application whitelist. For example, icons for applications that are not included in the whitelist (e.g., icons on a home screen of the device) are shaded during the limited use mode, as described above, and/or a placeholder generic indicator is displayed over (or partially over any portion of) the icons for those applications in the limited use mode. In some embodiments, a placeholder generic indicator (e.g., a lock icon) is placed on or adjacent to 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 modified as described above. As another example, in some embodiments, the electronic device has multitasking capabilities in which the electronic device optionally displays a user interface displaying visual representations of more than one application simultaneously (e.g., a user interface displaying icons from multiple applications simultaneously, screenshots of current user interfaces of multiple applications simultaneously, multiple application windows for different applications are presented simultaneously, etc.). In some embodiments, during the restricted use mode, representations for applications not included in the application whitelist in said multitasking user interface are modified 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 one or more windows of time associated with the limited use mode (1178) (e.g., in response to the start of one or more windows of time associated with the limited use mode), in accordance with a determination that the first application is included in the application usage whitelist, the electronic device displays a first representation of the first application with a first visual characteristic (1182), such as in FIG. 10SS (e.g., the appearance of the representation for applications included on the application whitelist continues to be displayed with the same visual characteristic during the limited use mode). The above-described method of selectively changing the appearance of the representation of applications not on the application whitelist during the limited use mode allows the electronic device to efficiently and selectively restrict the use of certain applications for certain periods of time by providing an indication of which applications the user does or does not have access to during the limited use mode, thereby reducing use of the electronic device during those periods and, in addition, reducing power consumption to improve the battery life of the device.

In some embodiments, displaying the first representation of the first application with the second visual characteristic includes displaying a limited use badge on the first representation, such as FIG. 10SS, that includes an indication that access to the first application is restricted (1184) (e.g., a badge having a visual indication of a lock or some other restriction symbol added to the application icons, such as superimposed on those application icons or any portion(s) of those application icons (e.g., the upper right portion of the icons)). In some embodiments, the restriction symbol (e.g., a lock icon) is placed on or adjacent to text associated with the restricted application icon. In some embodiments, the application icons include one or more visual indications of notifications associated with those applications when the limited use mode is not in effect (e.g., a badge indicating the number of unread notifications received for that application is superimposed on a portion of the icon). In such an embodiment, for those applications that are not included on the application whitelist, their visual indications are removed, grayed out, the number of notifications is removed, replaced with a placeholder generic indication (e.g., a lock icon), or otherwise altered such that the notification state (e.g., the number of notifications) of those applications is no longer conveyed by their indications. The above-described method of selectively altering the appearance of the representation of applications that are not on the application whitelist during the restricted use mode allows the electronic device to efficiently and selectively restrict the use of certain applications for certain periods of time by displaying limited use badges on applications to which the user does not have access during the restricted use mode, thereby reducing the likelihood that the user will attempt to access such restricted applications, as well as reducing use of the electronic device during those periods, thereby reducing power consumption and improving the device's battery life.

In some embodiments, displaying the first representation of the first application in the first visual characteristic, such as in FIG. 10RR-FIG. 10SS, includes displaying the first representation with a notification badge (e.g., an indicator of unread messages, missed calls, etc.) including an indication of notifications received by the first application (e.g., number of unread messages, missed calls, etc.) (1186), and displaying the first representation of the first application in the second visual characteristic includes displaying the first representation with the notification badge replaced by a limited use badge (1188) (e.g., blurring the indicator or replacing the indicator with a graphic). In some embodiments, the lock badge described above replaces an indication of a notification badge of the application icon for the non-whitelisted application during the limited use mode time window(s), as described above. The above-described method of selectively changing the appearance of the representation of applications not on the application whitelist during the restricted use mode allows the electronic device to efficiently and selectively restrict the use of certain applications for certain time periods by replacing the indication of notifications of the application representations with limited use badges on applications to which the user does not have access during the restricted use mode, thereby deterring the user from attempting to access restricted applications that have recent notifications by not indicating that such notifications exist, reducing use of the electronic device during those time periods, and additionally reducing power consumption to improve the battery life of the device.

It should be understood that the particular order described for the operations in Figures 11A-11I is merely exemplary, and that the order described is not intended to indicate that the operations are the only order in which they may be performed. Those skilled in the art will recognize various ways to reorder the operations described herein. In addition, it should be noted that other process details described herein with respect to other methods described herein (e.g., methods 700, 900, 1300, and 1500) are also applicable in a similar manner to method 1100 described above with respect to Figures 11A-11I. For example, the limited use modes, use limit settings, etc. described above with reference to method 1100 optionally have one or more of the characteristics of the limited use modes, use limit settings, etc. described herein with reference to other methods described herein (e.g., methods 700, 900, 1300, and 1500). For the sake of brevity, these details will not be repeated here.

The operations in the information processing method described above are optionally performed by running one or more functional modules in an information processing device, such as a general-purpose processor (e.g., as described above in connection with FIGS. 1A-1B, 3, and 5A-5H) or an application specific chip. Additionally, 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, event recognizer 180, and event processor 190. Event monitor 171 of event sorter 170 detects contacts on touch screen 504, and event dispatcher module 174 delivers the event information to application 136-1. The event recognizer 180 of each application 136-1 compares the event information to a respective event definition 186 to determine whether the first contact at a first location on the touch screen corresponds to a predefined event or sub-event, such as the selection of an object on a user interface. When a corresponding predefined event or sub-event is detected, the event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. The event handler 190 optionally utilizes or calls a data updater 176 or an object updater 177 to update the application internal state 192. In some embodiments, the event handler 190 accesses a corresponding GUI updater 178 to update what is displayed by the application. Similarly, it will be apparent to one skilled in the art how other processes can 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 during the day or night. For example, a user may 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 a user to monitor and limit the use of specific applications during certain periods of time. The embodiments described below provide a method for an electronic device to throttle auxiliary functions of specific applications when restriction criteria for those specific applications are met, such as when an application usage limit associated with those applications is reached and/or during one or more periods when the electronic device operates in a limited use mode. Throttle auxiliary functions of applications when restriction criteria are met allows the electronic device to effectively reduce overall use of the electronic device, thus reducing the power usage of the device and increasing battery life for battery-powered devices. It is understood that people use devices. When a person uses a device, that person is optionally referred to as a user of the device.

12A-12BB illustrate example methods in which an electronic device may throttle auxiliary features of certain applications upon reaching application usage limits or restriction criteria associated with those applications, consistent with 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. 13A-13H.

FIG. 12A illustrates an exemplary device 500 having a touch screen 504 as described with reference to FIGS. 5A-5H. The touch screen 504 optionally displays one or more user interfaces including various content. In the example illustrated in FIG. 12A, the touch screen 504 displays a home screen 1202 when the restriction criteria are not met on the device 500 (e.g., the user-defined usage limit has not been reached and outside one or more user-defined time windows associated with the limited use mode). In some embodiments, the restriction criteria are met when a usage limit for a given application or category of applications has been reached, as described above with reference to methods 700 and 900. In some embodiments, the restriction criteria are met during one or more time windows associated with the limited use mode, as described above with reference to method 1100. In FIG. 12A, home screen 1202 includes icons 424, 426, 416, 432, 434, 436, 440, 442, 444, 448, 450, and 452 for launching or otherwise displaying different applications on device 500, as described above with reference to FIG. 4A. As shown in FIG. 12A, one or more of the application icons optionally include a notification indicator 1204 that notifies 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, 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 search user interface 1207 when restriction criteria are not met on device 500. Search user interface 1207 is optionally a user interface of the operating system of device 500 in which 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 searched. The search user interface 1207, as shown in FIG. 12C, optionally includes a text field 1204 for entering one or more search terms to search for content accessible from the device 500, an "app suggestions" user interface 1208 for displaying applications suggested to the user by the operating system of the device 500 (e.g., suggesting commonly used applications, recently used applications, favorite applications, currently running applications), and widgets 1210 (e.g., user interface objects or windows containing text, image(s), and/or any other content associated with and updated by the corresponding application) corresponding to applications installed on the device 500. For example, in FIG. 12C, the app suggestions user interface 1208 includes a photo app 428, a training support app 442, a message app 424, and a social media A app 452, as well as a widget 1210a corresponding to the "social media app A" application and a widget 1210b corresponding to the "contacts" application.

In FIG. 12D, the user enters 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" being entered into text field 1204, device 500 displays various search results related to the search term "social media" in search user interface 1207. For example, device 500 displays a link 1212a to a social media application "social media A" installed on device 500, a link 1212b to a social media website "social media A" that is a website for the "social media A" app, and affordances to two social media applications available for download from an App Store (e.g., a repository of applications), an affordance 1212c for downloading a "social media B" application, and an affordance 1212d for downloading a "social media C" application.

12E illustrates a new message being received on the device 500 while the device 500 is displaying the home screen user interface 1202 when the restriction criteria are not met on the device 500. In some embodiments, the event of receiving a message on the device 500 corresponds to the activation of a function that displays a notification on the device 500 for a new message. For example, FIG. 12F illustrates the device 500 displaying a notification 1214 indicating that a new message has been received for the message 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 an unread message indicator on an application icon. For example, FIG. 12F illustrates the device 500 updating the indicator 1204 on the message app 424 in response to detecting a new message for the message app 424 to now reflect that there are four unread messages in the message app 424 (including the newly received message).

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

FIG. 12H shows device 500 suppressing notifications for restricted applications by forgoing displaying notifications for two new messages received in the Messages and Social Media A apps while the restriction criteria for those applications were met. FIG. 12H further shows device 500 forgoing updating indicator 1204 on Messages app 424 to reflect that there are now five unread messages in the Messages app (including the newly received message). In some embodiments, device 500 will place a placeholder generic indication 1206 (e.g., a lock icon) superimposed (or partially superimposed) on the icon associated with the restricted application for which a message was received while the restriction criteria for that application was met, as shown in FIG. 12H. For example, FIG. 12H shows lock icon 1206 superimposed on the top right portion of Social Media A app 452. In some embodiments, the placeholder generic indication is superimposed (or partially superimposed) on all icons associated with all restricted applications, regardless of whether the restricted applications have any unread notifications. In some embodiments, a placeholder generic indicator (e.g., a lock icon) is placed on 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 displayed (e.g., downward from an area of touch screen 504 that is not displayed toward home screen 1202), which causes device 500 to display notification history interface 1220 when a restriction criterion is met on device 500. Notification history interface 1220 is a user interface of the operating system of device 500 that optionally 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, device 500 visually obscures (e.g., blurs, grays out, or visually alters) the notifications for restricted applications displayed in notification history interface 1220, as shown in FIG. 12I. For example, in FIG. 12I, the device 500 displays in the notification history interface 1220 a notification 1222 associated with the message app 424 and a notification 1224 associated with the social media A app 452 that were received in FIG. 12G but suppressed in FIG. 12H.

In some embodiments, the device 500 displays previously suppressed notifications as if they had just been received once the usage limits for the applications associated with those notifications are reset (e.g., after the restriction criteria for those applications are no longer met, e.g., after the usage limits for the applications are no longer met, or after the device's limited use mode is terminated). For example, FIG. 12J shows the touch screen 504 displaying the home screen 1202 when the restriction criteria for the message app 424 and the social media A app 452 are met on the device 500 (e.g., a user-defined usage limit has been reached or the current time is within one or more user-defined time windows associated with the limited use mode) and after new messages for the message app 424 and the social media A app 452 have been received and suppressed at the device 500 while the restriction criteria were met (e.g., as described above with reference to FIGS. 12G-12H). 12K illustrates the touch screen 504 of the device displaying the home screen 1202 when the usage limits for the message app 424 and the social media A app 452 are reset (e.g., at a time when the restriction criteria for those applications are no longer met). In response to the usage limits for the message app 424 and the social media A app 452 being reset or the limited use mode for the device 500 being terminated, the device 500 optionally displays as new notifications any notifications associated with those applications that were previously suppressed while the restriction criteria for those applications were met. For example, the device 500 optionally presents the previously suppressed notification 1222 associated with the message app 424 and the previously suppressed notification 1224 associated with the social media A app 452 as "new" notifications (e.g., as if they had just been received).

In some embodiments, device 500 suppresses other auxiliary features associated with the restricted application (e.g., an application for which the restriction criteria are met), such as suppressing the restricted application in search results, suppressing widgets associated with the restricted application, suppressing the restricted application from appearing in an application suggestion graphical user interface, and/or suppressing a window corresponding to the restricted application from appearing in 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 message app 424 and social media A app 452 are met (e.g., as described above with reference to FIGS. 12G-12H), thereby causing device 500 to display search user interface 1207 with auxiliary features associated with the restricted application suppressed. Search user interface 1207 optionally includes a text field 1204 for entering one or more search terms to search for content accessible from device 500, an "app suggestions" user interface 1208 for displaying applications suggested to the user by the operating system of device 500, and widgets 1210 corresponding to applications installed on device 500 (e.g., as described above with reference to FIG. 12C ). In some embodiments, device 500 suppresses restricted applications and widgets associated with restricted applications in app suggestions user interface 1208, as shown in FIG. 12M . For example, device 500 suppresses application suggestions and widgets associated with the restricted app by optionally visually obscuring (e.g., blurring, graying out, or visually altering) the restricted application in app suggestions user interface 1208 (e.g., visually obscuring restricted social media A app 452) and visually obscuring widgets associated with the restricted application (e.g., visually obscuring widget 1210a associated with restricted social media A app 452), as shown in FIG. 12M. In some embodiments, device 500 suppresses application suggestions and widgets associated with the restricted app by optionally not displaying the restricted application in app suggestions user interface 1208, not displaying widgets associated with the restricted application (e.g., refraining from displaying social media A app 452 and widget 1210a associated with restricted social media A app 452), and instead displaying other non-restricted apps (e.g., applications for which the restriction criteria are not met) and/or widgets associated with the non-restricted apps.

In FIG. 12N, a user enters the search term "social media" into the text field 1204 when the restriction criteria for the social media A app 452 are met on the device 500. In response to the search term "social media" entered into the text field 1204, the device 500 displays various search results related to the search term "social media" in the search user interface 1207. For example, the device 500 optionally displays a link 1212a to the social media application "social media A" 452 installed on the device 500, a link 1212b to a social media website "social media A" that is a website for the "social media A" app, and links to two social media applications available for download from an App Store (e.g., a repository of applications), a link 1212c to a "social media B" application and a link 1212d to a "social media C" application. Because the restriction criteria for the social media A app 452 are met, the links 1212a and 1212b are suppressed (e.g., 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 (e.g., applications for which the restriction criteria are not met) are optionally displayed.

In some embodiments, the device 500 suppresses other auxiliary functions associated with the restricted application (e.g., an application for which the restriction criteria are met), such as suppressing website content associated with the restricted application. For example, FIG. 12P shows the device 500 displaying a web browser interface 1230 suppressing web content from the website “www.socmeda.com” associated with the restricted social media A app 452 by forgoing displaying web content from the website. In some embodiments, the device 500 suppresses not only the home page of the website associated with the restricted application, but also any other web pages of the website (e.g., pages with the same home page URL). In some embodiments, the device 500 displays an indication 1232 (e.g., text and/or an image) explaining that the website is restricted because the restriction criteria for the social media A app 452 are met, as shown in FIG. 12P. In some embodiments, device 500 suppresses web content from the restricted application by obscuring (e.g., blurring, graying out, or visually altering) web content 1236 and displaying an indication 1232 explaining that the website is restricted, as shown in FIG. 12Q. In some embodiments, web browser interface 1230 includes a URL field 1234 for entering a web address (e.g., a URL) of the website. Device 500 optionally allows a user to enter a website address into URL field 1234 while suppressing a website associated with the restricted application, allowing the user to navigate to another website, as shown in FIGS. 12R-12S.

In some embodiments, device 500 allows a user to share content with others via one or more applications installed on the device. FIG. 12T shows device 500 displaying web content in a web browser interface 1230 that optionally includes a share affordance 1236 selectable to share the web content. For example, in FIG. 12T, a selection of share affordance 1236 is detected (e.g., by a tap of contact 1003 detected on share affordance 1236, as shown in FIG. 12T). In response to the selection of share affordance 1236, device 500 displays a share sheet graphical user interface 1240, as shown in FIG. 12U. In some embodiments, share sheet graphical user interface 1240 includes selectable icons of applications installed on device 500 from which a user optionally selects to share web content, as shown in FIG. 12U. In some embodiments, device 500 suppresses icons of restricted applications in share sheet graphical user interface 1240. For example, in FIG. 12U, the device 500 suppresses the restricted message app icon 424 and the restricted social media A app icon 452 in the share sheet graphical user interface 1240 by visually obscuring the restricted message app icon 424 and the restricted social media A app icon 452 (e.g., by blurring, graying out, or visually altering the icons). In some embodiments, the device 500 suppresses the restricted message app icon 424 and the restricted social media A app icon 452 by forgoing displaying the restricted message app icon 424 and the restricted social media A app icon 452 in the share sheet graphical user interface 1240 (e.g., by not displaying the icons of the restricted application) and instead displaying other non-restricted apps (e.g., applications for which the restriction criteria are not met).

FIG. 12V illustrates the device 500 displaying content associated with the Video Z app in 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 is displayed over another user interface (e.g., a home screen, a primary user interface of another application, a user interface of another application), as shown in FIG. 12V. In some embodiments, the device 500 suppresses the display of application content in 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 in the PIP interface 1250 when the restriction criteria for the Video Z app are met. In some embodiments, the device 500 suppresses the display of content associated with the Video Z app in the PIP interface 1250 by visually obscuring (e.g., blurring, graying out, or visually altering) the content and/or the PIP interface 1250, as shown in FIG. 12W. In some embodiments, the device 500 refrains from displaying content associated with the Video Z App in the PIP interface 1250 by withholding the display of content associated with the Video Z App in the PIP interface 1250. If the PIP interface 1250 is currently displaying content associated with the Video Z App when the restriction criteria are met, the device 500 refrains from displaying content associated with the Video Z App in some embodiments by ceasing the display of 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 playback of the video. In some embodiments, the device 500 suppresses displaying content associated with the Video Z app in the PIP interface 1250 by visually obscuring the content and/or the PIP interface 1250 and automatically closing the PIP interface 1250 after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds), as shown in FIG. 12X (e.g., showing the device 500 after it has stopped displaying the PIP interface 1250).

In some embodiments, device 500 suppresses other auxiliary functions associated with restricted applications (e.g., applications for which restriction criteria are met), such as suppressing a media control interface for controlling media content associated with the restricted application. For example, in FIG. 12Y-12Z, a vertical swipe of contact 1203 is detected on touch screen 504 while home screen 1202 is displayed (e.g., from an area of touch screen 504 not displayed, upwards relative to home screen 1202), thereby causing device 500 to display media control interface 1260 when restriction criteria are not met on device 500. Media control interface 1260 is optionally a user interface of the operating system of device 500 that controls playback of content from various applications on device 500. Media control interface 1260 optionally includes media control buttons 1262 for controlling media content, and media content information 1264 indicating which media content media control interface 1260 is currently controlling, as shown in FIG. 12Z. For example, FIG. 12Z illustrates device 500 controlling media playback of the song "Hit Song" by "Pop Star" via a music app. In some embodiments, device 500 suppresses media control interface 1260 for media content associated with restricted applications (e.g., applications for which restriction criteria are met). For example, FIG. 12AA illustrates device 500 displaying media control interface 1260 and suppressing media control interface 1260 for controlling media content associated with the music app when restriction criteria are met for the music app, message app 424, and social media A app 452 on device 500. In some embodiments, device 500 suppresses device 500 from suppressing media control interface 1260 by stopping playback of media content associated with the music app and disabling media content buttons 1262 (e.g., not allowing the buttons to be used to control media content associated with the restricted applications) as shown in FIG. 12AA. In some embodiments, the device 500 also visually obscures the media control buttons 1262 (e.g., by blurring, graying out, or visually altering the media control buttons), as shown in FIG. 12AA. In some embodiments, the device 500 automatically resets the media control interface 1260 after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds), as shown in FIG. 12BB. For example, FIG. 12BB shows a device 500 that is no longer playing media content associated with a music app (e.g., media content information 1264 associated with the music app is no longer displayed) and that no longer disables the media control buttons 1262. In some embodiments, the device 500 stops displaying the media control interface 1260 after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds) when the limiting criteria are met and/or after the device 500 resets the media control interface 1260.

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

As described below, method 1300 provides a way to throttle auxiliary features of certain applications when application usage limits associated with those applications are reached. This method reduces overall usage of the electronic device by restricting how a user interacts with certain applications. For battery-operated electronic devices, reducing overall usage of the electronic device conserves power and increases the time between battery charges.

In some embodiments, an electronic device in communication with a display and one or more input devices (e.g., a mobile device including a touchscreen such as device 500 including touchscreen 504, a computer or tablet computer including one or more of a keyboard, a mouse, a trackpad, a touchscreen such as touchscreen 504, a wearable device such as a smart watch including a touchscreen, or a set-top box in communication with a television and an input device (e.g., a remote controller)) implements restrictions on one or more applications including a first application of a plurality of applications installed on the electronic device (e.g., maintains showtime information, time to use a particular application, information regarding notifications received from a particular application, information regarding featured events, and optionally, maintains a display of the electronic device, the electronic device, the display of ... 12C )。 While controlling the amount of the above that the device allows (e.g., usage limits, bedtime restrictions, etc.), detects an event corresponding to activation of an auxiliary function of the first application (e.g., the occurrence of an event that will trigger the display of a notification for the application, a request to display a widget corresponding to the application, a request to share content with the application via a system sharing user interface, a request to view a website associated with the application, a request to view a history of previous notifications (including notifications for the application), a request to display application content in picture-in-picture (PIP) mode, a request to display the application in search results, a request to view a multitasking graphical user interface, or a request to display and/or perform media control operations associated with the application (1302). The auxiliary function of the first application is a function (e.g., displaying interactive notifications, performing share sheet actions, displaying widgets, displaying notification history, displaying a website in a browser, displaying application content in PIP mode, displaying the application in search results, displaying an application window in a multitasking graphical user interface, or displaying and/or controlling media control operations) available to be performed without displaying the primary user interface of the first application (e.g., without launching the application in an application window or other primary view of the application). In some embodiments, the usage limits for one or more applications are enforced over a period of time (e.g., 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 feature of the first application, following a determination that a restriction criterion for the first application has been met (e.g., a user-defined "limit" (e.g., a usage limit or allowance) for the application has been reached), the electronic device inhibits (1306) the auxiliary features, such as FIG. 12M (e.g., inhibiting notification generation functionality associated with the application, displaying website(s) associated with the application, share sheet action(s), displaying a window corresponding to the application in a multitasking graphical user interface, displaying 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, restricting the application from appearing as a suggested application, or restricting a window corresponding to the application from appearing in a multitasking graphical user interface)). In some embodiments, the usage limit is set for overall device usage, for use of multiple applications within a given category of applications, or for a particular application. In some embodiments, launching the application is also inhibited (e.g., limited). In some embodiments, the auxiliary function is inhibited by preventing the function from being performed in response to detecting the event.

In some embodiments, in response to detecting an event corresponding to activation of an auxiliary function of the first application (1304), following a determination that the restriction criteria are not met, the electronic device executes (1308) the auxiliary function without displaying a primary user interface of the application, such as in FIG. 12C (e.g., allowing normal use or execution of functions associated with various applications on the electronic device, such as generating notifications from the application, share sheet actions, displaying a website associated with the application, displaying application content in PIP mode, displaying widgets associated with the application, displaying a window corresponding to the application from appearing within a multitasking graphical user interface, etc.). The restrictions and auxiliary functions described herein are optionally the same as or similar to the restricted use modes, auxiliary functions, and/or application usage limits described with reference to methods 700, 900, and 1100. The above-described methods of throttling the functionality of an application that is exceeding a usage limit allow the electronic device to effectively reduce overall use of the electronic device, thereby reducing power consumption and improving battery life of the device.

The auxiliary function optionally includes presenting (1310) a first type of indication of a notification (e.g., an alert and/or notification generated by the application) associated with the first application in response to the occurrence of an event corresponding to activation of the notification, such as FIG. 12F (e.g., displaying a visual indication on the display, playing a sound on a speaker associated with the electronic device, generating haptic(s) and/or tactile output(s), etc.). In some embodiments, the notification includes a visual indication (e.g., a window, a pop-up box) including text and/or an image. Additionally or alternatively, the notification optionally includes a sound and/or a haptic and/or tactile output indication. In some embodiments, the electronic device suppresses notifications associated with applications that have exceeded the usage limit. In some embodiments, the notification is suppressed by withholding a user visual indication (e.g., text and/or an image) or by withholding a generation of the notification. In some embodiments, the notification is suppressed by obscuring a user visual indication (e.g., visually altering the visual indication, text, and/or image). In some embodiments, the notification is suppressed by forgoing executing a sound and/or a haptic and/or tactile output indication associated with the application. In some embodiments, executing the auxiliary function includes presenting a notification generated by the first application. The above-described method of suppressing notifications associated with an application for which a restriction criterion is met allows the electronic device to reduce overall usage of the electronic device (e.g., by not executing a notification function and thus not prompting the user to notify and/or interact with the electronic device), thereby reducing power consumption and improving the battery life of the device.

In some embodiments, detecting an event corresponding to activation of an auxiliary function of the first application includes detecting an occurrence of an event corresponding to activation of a notification associated with the first application (1312), such as in FIG. 12E (e.g., detecting the occurrence of an event that will trigger the presentation of a notification). In some embodiments, suppressing the auxiliary function includes forgoing presenting a first type of indication in response to a notification generated by the first application (1314), such as in FIG. 12G-12H (e.g., suppressing a notification associated with a restricted application). In some embodiments, the notification is suppressed by forgoing display of a user visual indication (e.g., text and/or image) or forgoing generation of a notification. In some embodiments, the notification is suppressed by obscuring a user visual indication (e.g., visually altering a visual indication, text, and/or image). In some embodiments, the notification is suppressed by forgoing performing a sound and/or haptic and/or tactile output indication associated with the application.

In some embodiments, performing the auxiliary function includes presenting a first type of indication (1316) in response to the notification generated by the first application, such as FIG. 12F (e.g., displaying a banner, a pop-up notification, or a lock screen notification). In some embodiments, performing the auxiliary function includes presenting the notification generated by the first application. The above-described method of suppressing notifications associated with applications for which the restriction criteria are met and not suppressing notifications associated with applications for which the restriction criteria are not met allows the electronic device to efficiently and selectively reduce usage of the electronic device (e.g., by not performing notification functions for certain applications and thus not prompting the user to notify and/or interact with the electronic device), thereby reducing power consumption and improving battery life of the device.

In some embodiments, pursuant to a determination that the restriction criteria for the first application are met (1318), the electronic device includes (1319) a visual indication (e.g., an image, a window, text, etc.) of the first type of indication in a notification history user interface (e.g., a user interface for displaying visual indications of multiple notifications previously generated by one or more applications of the electronic device), such as in FIG. 12I. In some embodiments, the notification history user interface further includes (1319) one or more indications of notifications generated by one or more applications other than the first application. In some embodiments, the electronic device displays (1319) a notification history for the multiple applications, including a visual indication of any suppressed notifications generated by the first application, in the notification history user interface.

In some embodiments, notifications generated by multiple applications, including the first application, are displayed within a notification history user interface (e.g., a window) dedicated to displaying notifications that had been received by multiple applications on the electronic device (e.g., even pursuant to a determination that the restriction criteria for the first application are met), optionally allowing a user to later browse the notifications of applications that were suppressed. In some embodiments, visual indications of notifications from non-suppressed applications are presented outside of the notification history user interface (in addition to being presented within the notification history user interface) while visual indications of notifications from a suppressed application (e.g., the first application) are presented only within the notification history user interface. The above-described method of displaying suppressed notification(s) associated with an application for which a limiting criterion is met in the notification history allows the electronic device to efficiently organize and display notifications that would otherwise be suppressed without pushing notifications (e.g., by not alerting the user to the notification with a pop-up window, sound, and/or haptic and/or tactile output indication upon generation of the notification), thereby reducing overall usage of the electronic device (e.g., by not prompting the user to interact with the notifications and/or the electronic device) and reducing power consumption to improve the device's battery life.

In some embodiments, suppressing the suppression assistance functionality includes forgoing presenting a first type of indication in response to a notification generated by the first application (1320), such as in FIGS. 12G-12H (e.g., not actively presenting new indications (e.g., images, sounds, and haptic and/or tactile outputs) of any notifications associated with the application while the usage limit for that application has already been exceeded). In some embodiments, after suppressing the assistance functionality for the first application, the electronic device determines (1322), such as in FIG. 12K, that the restriction criteria for the first application are no longer met (e.g., use of the first application no longer meets the usage limit for the first application, the device is no longer in limited use (e.g., device downtime or bedtime mode), etc.). In some embodiments, in response to determining that the limit criteria for the first application are no longer met, the electronic device presents (1324) an indication regarding the notifications generated by the first application, such as FIG. 12K (e.g., displaying the notifications in a notification history user interface and/or as “new” notifications actively presented as if they had just been received once the usage limit has been reset). In some embodiments, notifications generated by the application during the period in which the usage limit for that application is being reached are presented to the user that the usage limit for that application has been reset and is therefore no longer exceeded. For example, if the usage limit for the relevant application is a daily limit, the usage limit optionally resets at midnight of the following day. In such a situation, when the usage limit for the application resets at midnight, the electronic device optionally displays the previously suppressed notifications in a user interface where the notifications would have previously been presented if not suppressed (e.g., on the wake or lock screen of the device). In some embodiments, the notifications will be acted out all at once (e.g., in one alert, window, or popup box including all previously suppressed notifications) or will be displayed separately/sequentially. The above-described method of presenting notifications associated with an application when a usage limit resets allows the electronic device to efficiently present previously suppressed notifications while reducing overall usage of the electronic device, thereby reducing power consumption and improving the device's battery life.

The auxiliary function optionally includes displaying (1326) a widget user interface that displays one or more secondary user interfaces of one or more applications, including a secondary user interface of the first application, such as in FIG. 12C (e.g., a widget corresponding to the application). In some embodiments, the widget includes a user interface object (e.g., a window) that includes text and/or images associated with the application (e.g., a weather widget that displays the current temperature, a sports widget that displays scores for live events, a news 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 the widget corresponding to the application is dynamically updated by the application. In some embodiments, the secondary user interface (e.g., a widget) is displayed simultaneously with additional secondary user interfaces (different from the primary user interfaces of those other applications) (e.g., a widget) of other applications (e.g., a widget is displayed simultaneously with a widget of the other application). In some embodiments, the secondary user interface (e.g., a widget) is displayed within a user interface of a widget that is different from the primary user interface of the first application. The event corresponding to activation of the auxiliary function optionally includes a request to display a widget user interface (1328), such as in Figures 12B-12C (e.g., an input from a user to display a widget user interface on an electronic device). In some embodiments, suppressing the auxiliary function includes displaying a widget user interface (1330), such as in Figure 12M (e.g., suppressing one or more widgets that have exceeded their usage limit), while suppressing a secondary user interface of the first application (e.g., not displaying or obscuring it with a splash screen or a message indicating that the limit criteria are met). In some embodiments, the widget is suppressed by withholding display of user interface objects (e.g., text and/or images) of the widget associated with the application that has exceeded its usage limit while displaying other widgets (e.g., the widget is not displayed). In some embodiments, the widget is suppressed by obscuring user interface objects (e.g., visually altering user interface objects, text, and/or images) while displaying other widgets. Obscuring the widget optionally includes displaying an indication of the restriction criteria in place of text and/or images associated with the application (e.g., the content of the widget when the restriction criteria is not met). In some embodiments, all widgets are suppressed. In some embodiments, executing the auxiliary function includes displaying a widget user interface displaying one or more widgets of one or more applications, including a widget of the first application. The widget user interface described herein is optionally the same as or similar to the widget user interface described with reference to FIG. 8W. The above-described method of suppressing widgets corresponding to applications that are exceeding a usage limit makes the user's interface with the device more efficient (e.g., the user does not need to monitor his or her device usage with respect to applications and widgets associated with the applications, thus reducing input provided by the user to the device (e.g., input for monitoring usage is reduced)), thereby allowing the electronic device to efficiently reduce overall usage of the electronic device, as well as reducing power consumption to improve the battery life of the device.

In some embodiments, the auxiliary function includes presenting (1332) a visual indication of one or more applications, including the first application for which the suggestion criteria are met, in a suggestion user interface, such as FIG. 12C (e.g., displaying application suggestions to a user on the electronic device, e.g., in a system (e.g., operating system) user interface of the electronic device as opposed to a user interface of a particular application on the electronic device). 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 operation performed on the electronic device. For example, a user optionally enters one or more characters in a search box to initiate a search for items that include the one or more characters. In some embodiments, the search is performed on all installed applications on the electronic device, applications available for download in an app store, websites, content of applications installed on the electronic device, and the like (e.g., searching the content of messages, emails). The search results then optionally include a list of applications, websites, and/or content that include the one or more entered characters.

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

The auxiliary function optionally includes displaying web content associated with the first application in a browser user interface (1338), such as in FIG. 12S (e.g., displaying web content or a website associated with the first application in a web browser). In some embodiments, an event corresponding to activation of the auxiliary function includes a request to display web content associated with the first application in a browser user interface (1340), such as in FIG. 12R (e.g., input from a user to display web content or a website associated with the first application in a web browser). In some embodiments, inhibiting the auxiliary function includes preventing access to web content associated with the first application (1342), such as in FIG. 12P (e.g., forgoing displaying website content associated with an application that has reached a usage limit). For example, if a usage limit for application A associated with website A has been reached, display of website A (or content from website A) in 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 inhibit not only the application that has exceeded its usage limit, but also any websites associated with that application. The electronic device optionally presents a visual indication of the restriction criteria (e.g., a splash screen or other image obscuring 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 in the browser (e.g., displaying the website in the browser). The website associated with the application described herein is optionally the same as or similar to the website associated with the application described with reference to method 900. The above-described method of suppressing web content associated with an application that is exceeding a usage limit makes the user's interface with the device more efficient (e.g., the user does not need to monitor his or her device usage with respect to the application and the website associated with the application, thus reducing input provided by the user to the device (e.g., input for monitoring usage is reduced)), thereby allowing the electronic device to efficiently reduce overall usage of the electronic device, as well as reducing power consumption to improve the battery life of the device.

In some embodiments, preventing access to the web content associated with the first application (1344) includes loading (1346) the web content associated with the first application from a first website, such as in FIG. 12Q (e.g., the content of the website associated with the application that is exceeding the usage limit is loaded by the electronic device (e.g., downloaded to local memory)). In some embodiments, preventing access to the web content associated with the first application (1344) includes forgoing (1348) the web content associated with the first application, such as in FIG. 12Q (e.g., the web content is loaded by the electronic device but not displayed). In some embodiments, the electronic device displays some user interface element (e.g., a pop-up dialog or splash screen) over the content that blocks the display of the content and/or indicates that the content is blocked because the usage limit for application A has been reached. Additionally or alternatively, the web content is optionally displayed but obscured (e.g., distorted, grayed out, faded out, and/or visually altered). The above-described method of suppressing web content associated with an application for which restriction criteria are met (e.g., usage limits are exceeded or the device is in a restricted mode) makes the user's interface with the device more efficient (e.g., the user does not need to monitor his or her device usage with respect to the application and the web sites associated with the application, thus reducing the input provided by the user to the device (e.g., input to monitor usage is reduced)), thereby allowing the electronic device to efficiently reduce overall usage of the electronic device, as well as allowing the electronic device to cache the web content for future use, as well as improving execution speed while simultaneously reducing power consumption and improving the device's battery life.

In some embodiments, preventing access to web content associated with the first application (1350) includes forgoing displaying the web content associated with the first application (1352) while maintaining display of one or more user interface elements (e.g., one or more graphical user interface buttons, text input fields) for navigating to another website (e.g., for navigating to other websites, for navigating within a website) in a browser user interface, such as FIG. 12R. In some embodiments, the browser's navigation controls (e.g., a URL field or button on the browser) remain operable while the particular web content associated with the application for which the restriction criteria is met is restricted. In some embodiments, websites not associated with any application on the electronic device remain accessible while 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 optionally the user may navigate to other websites. The above-described method of suppressing web content associated with an application for which restriction criteria are met while allowing access to other websites allows a more efficient user-device interface (e.g., the user does not need to monitor his or her device usage with respect to the application and websites associated with the application, thus reducing input provided by the user to the device (e.g., input for monitoring usage is reduced)), thereby allowing the electronic device to efficiently reduce overall usage of the electronic device, as well as reducing power consumption and improving battery life of the device.

In some embodiments, while the restriction criteria for the first application are met, a second event is detected (1354) corresponding to a request to view second web content from a second website in a browser user interface, such as in Figures 12R-12S (e.g., detecting the occurrence of an event that may trigger the display of content from another website, optionally not associated with the first application). In some embodiments, the second event is a user entering a URL for another website into the browser's address field.

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

In some embodiments, in response to detecting a second event corresponding to a request to view second web content from a second website in the browser user interface while the restriction criteria for the first application are met (1356), in accordance with a determination that the second website is associated with the second application and the restriction criteria for the second application are not met, the electronic device displays the second web content (1360), such as in FIG. 12S (e.g., displays web content associated with an application for which the restriction criteria are not met (e.g., a usage limit has been reached or the device is in a limited use mode, etc.)). In some embodiments, only websites associated with applications for which the restriction criteria are met are restricted, and the user may navigate to other websites. In some embodiments, websites not associated with any applications 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 an application for which restriction criteria are met while allowing access to other websites allows a more efficient user-device interface (e.g., the user does not need to monitor his or her device usage with respect to the application and websites associated with the application, thus reducing input provided by the user to the device (e.g., input for monitoring usage is reduced)), thereby allowing the electronic device to efficiently reduce overall usage of the electronic device, as well as reducing power consumption and improving battery life of the device.

In some embodiments, the auxiliary function includes displaying the media content in a picture-in-picture user interface of the first application that is partially overlaid on one or more other user interfaces (1362), such as in FIG. 12V (e.g., displaying a picture-in-picture (PIP) window on top of another user interface (e.g., a home screen, a primary user interface of another application, or a user interface of another application). The event corresponding to activation of the auxiliary function optionally includes a request to display the media content in a picture-in-picture user interface of the first application (1364), such as in FIG. 12V (e.g., a request to view content from the first application in a PIP window). In some examples, the PIP window is already displaying content from the first application and the request is to continue displaying content (e.g., receiving content for display). In some embodiments, inhibiting the auxiliary function includes inhibiting a picture-in-picture user interface of the first application (1366), such as in FIG. 12W (e.g., forgoing displaying the PIP window, ceasing to display content in the PIP window). For example, if a usage limit for application A has been reached, the user will not be able to circumvent the restricted access to application A by attempting to initiate a PIP window of the application (e.g., the PIP window will not be displayed). In some embodiments, a PIP window for the application will be currently displayed when the usage limit for the application is met, and the electronic device will inhibit this functionality by ceasing to display the PIP window or by otherwise obscuring the PIP window of the first application (e.g., graying out or fading out the PIP window). In some embodiments, the PIP window is a window that plays media (e.g., movies, TV shows, music, etc.) on the 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 (e.g., not inhibited). 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 suppressing PIP windows associated with applications that are exceeding usage limits allows a more efficient user-device interface (e.g., the user does not need to monitor their own device usage with respect to applications and PIP windows associated with the applications, thus reducing input provided by the user to the device (e.g., input for monitoring usage is reduced)), thereby allowing the electronic device to efficiently reduce overall usage of the electronic device, as well as reducing power consumption and improving battery life of the device.

In some embodiments, inhibiting the picture-in-picture user interface of the first application (1368) includes obscuring the picture-in-picture user interface for a first period of time (1372) (e.g., visually modifying and/or blocking the PIP window) pursuant to a determination that a restriction criterion for the first application is met (1370) while displaying the picture-in-picture user interface of the first application, such as in FIG. 12W (e.g., a usage limit for the application is met while the application is being used in PIP mode). In some embodiments, the PIP window will continue to display content from the first application, but the content will be visually modified (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 display other information (e.g., a visual indication that a usage limit for a particular application has been exceeded). In some embodiments, the other information displayed will include an affordance (e.g., a graphical user interface element or a soft button) for closing the PIP window.

In some embodiments, suppressing the picture-in-picture user interface of the first application (1368) includes ceasing to display the picture-in-picture user interface after a first period of time (e.g., the PIP window will be automatically closed after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds)) pursuant to a determination (1370) that a restriction criterion for the first application is met while displaying the picture-in-picture user interface of the first application, such as in FIG. 12X (e.g., a usage limit for the application is met while the application is being used in PIP mode). For example, the content of the PIP window will be faded out and the PIP window will be automatically closed after the period of time.

In some embodiments, this period is specified by a user in the electronic device's settings. In some embodiments, pursuant to a determination that the restriction criteria for the first application are met while not displaying a picture-in-picture user interface for the first application, the electronic device detects, at one or more input devices, a user input corresponding to a request to display a picture-in-picture user interface for the first application (e.g., detects an input to display a PIP user interface for the first application while the restriction criteria are met), and in response to the user input corresponding to the request to display a picture-in-picture user interface for the first application and while the restriction criteria for the first application are met, the electronic device refrains from displaying the picture-in-picture user interface for the first application (e.g., the restriction criteria for the first application are met while a PIP window for that application is displayed), and the electronic device prevents the window from being launched at a later time. In this manner, a user of the electronic device cannot circumvent the restriction 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 the restriction criteria are met allows a more efficient user-device interface (e.g., the user does not need to monitor his or her own device usage with respect to applications and PIP windows associated with the applications, thus reducing the input provided by the user to the device (e.g., input for monitoring usage is reduced)), thereby allowing the electronic device to efficiently reduce overall usage of the electronic device, as well as reducing power consumption and improving battery life of the device.

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

The event corresponding to activation of the auxiliary functionality optionally includes a request to display a plurality of affordances for controlling playback of media content associated with the first application (1378), such as in Figures 12Y-12Z (e.g., a user input requesting to see media control buttons to control playback of media associated with the first application on the electronic device).

In some embodiments, inhibiting the auxiliary functionality includes preventing a plurality of affordances from controlling playback of the media content associated with the first application (1380), such as FIG. 12AA. In some embodiments, the media control buttons will be displayed but inoperable (e.g., 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 (e.g., visually altered) within the media control user interface. In some embodiments, once the restriction criteria for a particular media playback application (e.g., a movie playback application, a television program playback application, or a music playback application) are met, access to the media playback controls for controlling playback of the media playback application is inhibited by the electronic device. In some embodiments, these media playback controls are displayed within the application itself or within a user interface other than the application itself (e.g., within a system or operating system user interface of the electronic device that is globally accessible on the electronic device). In some embodiments, the media playback controls are blocked 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. In some embodiments, the media control buttons will be suppressed by being prevented from being displayed by the electronic device (e.g., by preventing the media control user interface from being displayed or by displaying the media control user interface without the media control buttons) once the restriction criteria for the media playback application (e.g., the first application) have been met. In some embodiments, the suppressed media control user interface will be displayed on the electronic device for a period of time (e.g., 5 seconds, 10 seconds, 20 seconds) and will automatically close (e.g., stop being displayed) after that period of time. The above-described method of suppressing media control buttons associated with applications for which restriction criteria are met provides a more efficient interface between the user and the device (e.g., the user does not need to monitor his or her own device usage with respect to applications and media control buttons associated with the applications, thus reducing input provided by the user to the device (e.g., input for monitoring usage is reduced)), thereby allowing the electronic device to efficiently reduce overall usage of the electronic device, as well as reducing power consumption and improving battery life of the device.

In some embodiments, preventing the plurality of affordances from controlling playback of the media content associated with the first application (1382) includes placing the plurality of affordances in an inactive state (e.g., a state in which the media control buttons are unable to perform each of the media functions associated with each of the media control buttons) in which the device ignores user input directed at the plurality of affordances (1384), such as in FIG. 12AA, for a first period of time (e.g., 5 minutes, 15 minutes, 1 hour, or any user-defined period of time). 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 (e.g., visually altered) to indicate to the user that they are frozen. In some embodiments, even though frozen media control buttons are not operational, they will still indicate that media was recently played (or could potentially be controlled by the media control button if the usage limit was reset), such as by displaying a media title, an image of the media, etc. In some embodiments, the period of time is the time remaining until the limit criteria of the particular application associated with the media control button are no longer met. In some embodiments, if the restriction criteria for a particular media playback application are met while the media controls are controlling playback of the media playback application (e.g., while the media playback application is generating media on the electronic device), the media controls are frozen in their current state (e.g., showing the current playback state of the media, an identification of the media (e.g., title), etc.) and blocked from user interaction at the time the restriction criteria became met. In some embodiments, playback of the media is additionally stopped when the playback controls are placed in the frozen state. In some embodiments, the media controls are reset to their default state (e.g., showing that the media is not being played by the media playback application, not showing the title of the media, etc.) after some period of freezing (e.g., 5 seconds, 10 seconds, 20 seconds).

In some embodiments, preventing the plurality of affordances from controlling playback of media content associated with the first application (1382) includes causing the plurality of affordances to go from an inactive state to a default state (1386) after a first period of time, such as FIG. 12BB (e.g., returning the media control button to a default state in which the media control button does not indicate that any media is being played and thus does not control playback of the media). Thus, in some embodiments in the default state, the media control button no longer indicates the current playback state of the media, the identity of the media (e.g., title), etc. In some embodiments, this period of time is the time remaining until a usage limit for the particular application associated with the media control button is reset. In some embodiments, even though the affordances for controlling media content are reset to the default state, the electronic device prevents the presentation of media associated with any application for which the limit criteria are met. In some embodiments, the electronic device stops displaying the media control interface instead of causing the media control button to go to the default state after the first period of time. The above-described method of suppressing media control buttons associated with applications for which restriction criteria are met provides a more efficient interface between the user and the device (e.g., the user does not need to monitor his or her own device usage with respect to applications and media control buttons associated with the applications, thus reducing input provided by the user to the device (e.g., input for monitoring usage is reduced)), thereby allowing the electronic device to efficiently reduce overall usage of the electronic device, as well as reducing power consumption and improving battery life of the device.

It should be understood that the particular order described for the operations in Figures 13A-13H is merely exemplary, and the order described is not intended to indicate that the operations are the only order in which they may be performed. Those skilled in the art will recognize various ways to reorder the operations described herein. In addition, it should be noted that other process details described herein with respect to other methods described herein (e.g., methods 700, 900, 1100, and 1500) are also applicable in a similar manner to method 1300 described above with respect to Figures 13A-13H. For example, the use limits, limited use modes, auxiliary functions, use limit settings, etc. on the electronic device described above with reference to method 1100 optionally have one or more of the characteristics of the use limits, limited use modes, auxiliary functions, use limit settings, etc. on the electronic device described herein with reference to other methods described herein (e.g., methods 700, 900, 1100, and 1500). For the sake of brevity, these details will not be repeated here.

The operations in the information processing method described above are optionally performed by running one or more functional modules in an information processing device, such as a general-purpose processor (e.g., as described above in connection with FIGS. 1A-1B, 3, 5A-5H) or an application specific chip. Additionally, the operations described above with reference to FIGS. 13A-13H are optionally performed by the components shown in FIGS. 1A-1B. For example, the detect operation 1302, the suppress operation 1306, and the execute operation 1308 are optionally performed by the event sorter 170, the event recognizer 180, and the event processor 190. The event monitor 171 of the event sorter 170 detects a contact on the touch screen 504, and the event dispatcher module 174 delivers the event information to the application 136-1. The event recognizer 180 of each of the applications 136-1 compares the event information to a respective event definition 186 to determine whether a first contact at a first location on the touch screen corresponds to a predefined event or sub-event, such as a selection of an object on a user interface. When a corresponding predefined event or sub-event is detected, the event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. The event handler 190 optionally utilizes or calls a data updater 176 or an object updater 177 to update the application internal state 192. In some embodiments, the event handler 190 accesses a corresponding GUI updater 178 to update what is displayed by the application. Similarly, it will be clear to one skilled in the art how other processes can be implemented based on the components shown in Figures 1A-1B.
Remote management of restriction settings

Users interact with electronic devices in many different ways, including using applications accessible on the device. In some situations, administrators (e.g., parents) remotely manage the restriction settings on restricted devices (e.g., their child's electronic device). The embodiments described below provide a method for an electronic device to allow a user of a restricted device to request permission from an administrator, either on the passcode restricted device or on an authorizing device or other remote administrator, to change one or more usage restriction settings on the restricted device. Requiring authentication from an administrator on the restricted device to change usage restriction settings can provide an efficient way for an electronic device to facilitate such changes when authorization is requested by another party (e.g., a parent). This simplification improves the usability of the device and makes the user-device interface more efficient (e.g., by allowing a user to interact with the device with fewer inputs), thereby allowing the user to use the device more quickly and efficiently, thereby reducing power usage and improving battery life of the electronic device. It is understood that people use devices. When a person uses a device, that person is optionally referred to as the user of the device.

14A-14T illustrate example 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 FIGS. 15A-15G.

FIG. 14A illustrates an exemplary device 500 having a touch screen 504 as described with reference to FIGS. 5A-5H. The electronic device 500 illustrated 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 has permission to change one or more restriction settings of the child's electronic device 500 (e.g., one or more restriction settings described above with reference to FIGS. 10A-13H). The touch screen 504 optionally displays one or more user interfaces including various content. In the example illustrated in FIG. 14A, the touch screen 504 displays an indication 1498-26 that initial restriction settings have been set (e.g., by a parent device) for the electronic device when initial restriction settings for the electronic device were not previously set. The indication 1498-26 includes information about which restriction settings are set and their details (e.g., "Device downtime Monday through Thursday 6:00 AM to 10:00 PM" and "Usage limits: news apps, games categories, and social media categories"). Thus, in some embodiments, the device 500 displays the notification 1498-26 when a parent device first sets usage restriction settings for the device 500.

14B illustrates a limit setting user interface displayed on a child device 500, such as those described with reference to FIGS. 6A-6C, 8O-8Q, and 10A-10AA. The limit setting user interface includes an indication 1402 of device usage and an indication 1408 that screen time data is being shared with one or more parent devices associated with the child device, as well as multiple affordances 1404a-e for modifying various limit settings of the electronic device (e.g., "Device Downtime" 1404a, "App Limits" 1404b, "Always Allowed" 1404c, "Content and Privacy" 1404d, and "Include All Website Browsing Data on Parent Device" 1404e). Device Downtime 1404a has been described in more detail above with reference to FIGS. 10A-11I. App Limits 1404b has been described in more detail above with reference to FIGS. 8A-9K. Always Allowed 1404c has been 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 via a web browsing application. With this function turned off, the parent device optionally does not present usage information regarding which websites have been accessed by the child device 500. However, accessing websites associated with an application installed on the child device 500 is optionally counted as using the electronic device to access that application (e.g., time spent accessing a website associated with an application counts toward a usage limit for that application or category of applications and is included in the usage data for that application and/or category). It should be understood that sharing screen time data (e.g., as indicated by indication 1402) with a parent or administrator device also includes sharing other usage data and restriction permissions, such as the ability to set device downtime, always allowed applications and features, sharing and privacy permissions, content purchase settings, age-restricted content consumption settings, and that such settings are also optionally subject to the remote management scheme of the present disclosure.

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

In FIG. 14C, the electronic device 500 detects contact 1403 at an affordance 1404a for changing one or more device downtime settings. In response to a request to change the settings, the electronic device 500 presents an authentication user interface, as shown in FIG. 14D. As shown in FIG. 14D, the authentication user interface includes an affordance 1406 for requesting permission to change the settings remotely from an administrative account (e.g., from a parent account or parent device), and a keypad 1482 for entering a passcode to change the settings. In some embodiments, the passcode for changing the restriction settings is different from the passcode for unlocking the electronic device 500, such that an administrator or parent can know the passcode without a non-administrator or child knowing the passcode.

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

14F illustrates an 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 about which restriction settings the child is attempting to change (e.g., device downtime). The parent can approve (e.g., by selecting "Allow" in the indication 1498-20) or deny (e.g., by selecting "Deny" in the indication 1498-20) the child's access to the restriction settings on the child's electronic device. If the parent denies the child's request to change the restriction settings, the child's 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 limit setting, the child device is granted access to the limit settings for a predetermined period of time, during a single session (e.g., until the child exits the limit setting user interface), until one or more limit settings are changed or until the child exits the setting user interface for more than a predetermined amount of time.

14G shows an electronic device 500 associated with a child's user account. The electronic device 500 presents a user interface 1410 for modifying one or more settings (1411-1417) associated with device downtime, such as in response to a parent selecting "Allow" in indication 1498-20 in FIG. 14F, or in response to successful entry of a passcode in FIG. 14D. As shown in FIG. 14G, the electronic device 500 detects contact 1403 and optionally further user input to modify the device downtime start time from 10:00 PM to 11:00 PM. As discussed above, parental authorization to modify one or more restriction settings is optionally valid for a limited amount of time. Thus, the electronic device 500 presents an indication 1450 that modification of the device downtime settings may be made for another three minutes. As discussed above, other authorization timeframes and criteria are possible. After the settings are changed, the limit settings user interface is updated to reflect the changed settings, as shown in FIG. 14H (e.g., "Device downtime 1404a" is now set to 11 PM-5 AM Monday-Thursday, when it was set to 10 PM-5 AM Monday-Thursday as shown in FIGS. 14B-14C).

When a child makes a change to the restriction settings, the parent device optionally presents an indication that explains what changes have been made. FIG. 14I shows an electronic device 500 associated with a parent account. As shown in FIG. 14I, the electronic device 500 presents an indication 1498-22 that the child device has changed the device downtime from 10 PM-5 AM Monday-Thursday to 11 PM-5 AM Monday-Thursday. The indication 1498-22 includes an affordance to reject or allow the change. Thus, the parent device can optionally override the setting changes made at the child device. If the parent device accepts the setting changes made by the child device, the child device operates according to those changes. For example, by accepting the change in device downtime from 10 PM-5 AM to 11 PM-5 AM, the child device operates in a normal non-restricted mode until 11 PM as opposed to operating in a restricted use mode starting at 10 PM.

If the parent rejects the setting change made by the child device, the child device optionally presents an indication that the setting change was rejected. FIG. 14J shows an electronic device 500 associated with a child user account. The electronic device 500 presents an indication 1498-24 that the restriction setting change was rejected by the parent (e.g., "Daddy rejected device downtime setting change"). Furthermore, if the parent rejects the setting change made on the child device, the child device continues to operate according to the settings before the settings were changed. That is, the child device will optionally continue to transition into the restricted use mode starting at 10 p.m.

14K illustrates a usage dashboard for a child's device usage presented on an electronic device 500 associated with a parent user account. The child device usage dashboard includes an indication 1416 of the child's overall device usage, an indication 1428 of how the child's device usage compares to the average device usage, a graph 1424 showing detailed device usage metrics, an indication 1434 of the child's longest session on the device during the day, an indication 1436 of device usage during device downtime, indications 1422a-b of usage of applications and application categories with usage limits, an indication 1442 of usage of applications without usage limits, and a number of affordances 1440a-c for changing limit settings associated with applications and categories presented within the dashboard user interface, such as those described with reference to FIGS. 6L-6U.

As shown in FIG. 14K, the dashboard user interface includes an indication 1442 of how much time the child's electronic device was used to access the browser application, but does not include detailed information about which websites were accessed and for how long. However, time spent using the browser application to access websites associated with the application and category for which usage metrics are presented optionally counts as using the electronic device to access the associated application (e.g., accessing one or more websites associated with a news app optionally counts toward the news app usage metrics and usage limits 1422a).

14L shows a limit setting user interface presented by an electronic device 500 associated with a child user account. As shown in FIG. 14L, the setting "Include all website browsing data on parent device" 1404e has been activated. When this setting is activated, the administrator or parent electronic device optionally presents information about which websites the child device accesses in a dashboard user interface, as shown in FIG. 14M. In FIG. 14M, the dashboard user interface includes an indication 1442b and 1442c of the amount of time the child's electronic device accessed website A and website B, respectively, in addition to an indication 1442a of the total amount of time the child's electronic device used a browser application.

14N shows a child restriction setting user interface presented by an electronic device 500 associated with a parent user account. The restriction setting user interface includes an indication of use of the child device, such as those described with reference to FIGS. 8LLL-8NNN and 10Y-10AA, and a number of affordances 1404a-f for changing the restriction settings of the child device. If the child's age is above a threshold age (e.g., age 13), the parent optionally has the option to remove and/or change the screen time password required to change the restriction settings of the child's electronic device at the child's electronic device by selecting affordance 1404f. As shown in FIG. 14O, when the child's age is below the threshold age, the parent device has the ability to change the screen time password by selecting affordance 1404g, but the screen time password cannot be removed.

When a parent changes a restriction setting on a child device, the child device optionally presents an indication of which settings were changed. FIG. 14P shows an indication 1498-28 of a restriction setting change presented on an electronic device 500 associated with a child user account. The indication 1498-28 includes information about which setting was changed and how it was changed (e.g., "Daddy added a 1 hour usage limit to the Browser app").

As described herein, the parent device can optionally access the screen time data of the child device to modify one or more restriction settings of the child device. It should be understood that sharing screen time data is one example of many types of information and permissions that may be shared at the parent or administrator device. Here and throughout this description, sharing screen time data is understood to optionally include one or more of the following: the ability to view any of the usage metrics (e.g., screen time, notifications, device pickups, etc.) discussed above with reference to Figures 6A-6UU, the ability to set and update one or more restriction settings (e.g., device downtime and/or usage limits), the ability to set one or more content and privacy settings, content purchase settings, age-restricted content consumption settings, etc.

When the child's age exceeds a predetermined threshold (e.g., age 18), the child device can optionally stop sharing screen time data with the child's parent and/or take over control of the usage limit settings on the child device from the parent device. FIG. 14Q shows an indication 1498-26 presented on the child device 500 that the child device can stop sharing screen time data with the child's parent. The indication 1498-26 is optionally displayed when the child's age exceeds a predetermined threshold (e.g., age 18). When the child's age exceeds this threshold, the limit settings user interface on the child device is optionally updated to include a setting to stop sharing screen time data with the child's parent. FIG. 14R shows the limit settings user interface presented on the child device 500 when the child's age exceeds a threshold where sharing screen time data with the child's parent is optional. As shown in FIG. 14R, the settings user interface is updated to include affordance 1404h ("Turn off screen time sharing"). In some embodiments, the settings user interface on the child device 500 did not include affordance 1404h when the child's age was below a predetermined threshold (e.g., age 18). FIG. 14S shows the child device 500 detecting contact at affordance 1404h.

In some embodiments, in response to this request to stop sharing the screen time data with the child's parent, the child device requests permission to stop sharing the screen time data from the parent device, which optionally includes displaying an authentication user interface as shown in FIG. 14D. The parent can optionally approve the request for the child device to stop sharing the screen time data by providing a passcode or authentication on the child device or by authenticating the request on the parent device, as described above with reference to FIG. 14F. If permission to stop sharing the screen time data is required, the screen time data optionally continues to be shared with the parent device until the parent approves the setting change to stop sharing the screen time data. In some embodiments, parental permission to stop sharing the screen time data is not required once the child's age exceeds an age threshold (e.g., age 18).

As shown in FIG. 14T, when the child device 500 no longer shares usage data with the child's parent, the limit settings user interface is updated accordingly. In FIG. 14T, the indication 1408 that screen time data is shared with the child's parent and the affordance 1404h for turning off screen time sharing are no longer presented in the limit settings user interface. Optionally, the setting 1404e for toggling the inclusion of all website browsing data on the parent device also ceases to be displayed. In some embodiments, after the child device stops sharing screen time data with the parent device, the user of the child device is free to modify usage restriction settings on the child device (e.g., device downtime, usage limits, ability to add/remove apps on the child device, changing content purchase settings, viewing age-restricted content, privacy settings, etc.) without the need for authentication input (e.g., a passcode or approval from the parent device).

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. The method 1500 is optionally performed on an electronic device, such as device 100, device 300, or device 500, as described above with reference to FIGS. 1A-1B, 1-3, 4A-4B, and 5A-5H. Some operations of the method 1500 are optionally combined and/or the order of some operations is optionally changed.

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

In some embodiments, a first electronic device 500 (e.g., a smartphone, smartwatch, tablet computer, computer, set-top box, etc.) in communication with a display device (e.g., a display, touch screen, television) and one or more input devices (e.g., a touch screen, touch-sensitive surface, remote controller, etc.) is configured to communicate with the first electronic device while a usage restriction setting is implemented on the first electronic device that restricts use of the first electronic device (e.g., a usage limit that limits use of one or more applications, categories of applications, total device use, etc., such as those described with reference to methods 700, 900, 1100, and/or 1300, implemented on the first electronic device; a restricted use mode, such as those described with reference to methods 700, 900, 1100, and/or 1300). In some embodiments, the first electronic device is configured to communicate with the first electronic device while a usage restriction setting is implemented on the first electronic device that restricts use of the first electronic device (e.g., a usage limit that limits use of one or more applications, categories of applications, total device use, etc., such as those described with reference to methods 700, 900, 1100, and/or 1300, implemented on the first electronic device. In some embodiments, the first electronic device is configured to communicate with the first electronic device while a usage restriction setting is implemented on the first electronic device that restricts use of the first electronic device (e.g., a usage limit that limits use of one or more applications, categories of applications, total device use, etc., such as those described with reference to methods 700, 900, 1100, and/or 1300, implemented on the first electronic device). A restricted device (e.g., a device associated with a child or restricted account in a set of related accounts including one or more parent or administrator accounts), such as those described with reference to methods 700, 900, 1100, and/or 1300, controlled by an authorized device (e.g., a device associated with a parent or administrator account in a set of related accounts including one or more parent or administrator accounts), receives a series of one or more inputs (e.g., inputs on the restricted device to change usage limit settings, restricted use mode settings, etc., implemented on the restricted device, such usage limit settings being set or controlled by an authorized device such as FIG. 14C. In some embodiments, the inputs to change the usage limit settings on the restricted device are detected in a usage limit settings user interface on the restricted device that displays information about the usage limit settings implemented on the restricted device) (1504).

In some embodiments, in response to receiving the series of one or more inputs, pursuant to a determination that the series of one or more inputs includes inputs corresponding to a request for permission to change the usage restriction settings from a second electronic device, such as those of FIGS. 14D-14E, that is different from the first electronic device (or from an administrator account associated with the second electronic device; in some embodiments, the request for permission is sent to multiple accounts with administrator privileges (e.g., multiple parents in a family)) (e.g., a user interface displayed by the restricted device provides multiple ways to change the usage restriction settings on the restricted device, including providing a passcode to change the settings on the restricted device, or requesting permission from the authorizing device to change the usage restriction settings, such as those described with reference to methods 700, 900, 1100, and/or 1300, or requesting permission from an administrator account associated with the authorizing device. In some embodiments, the restricted device detects the input requesting permission to change the usage restriction settings from the authorizing device), the first electronic device sends a request for permission to change the usage limit settings on the first electronic device (1508), such as in FIGS. 14D-14F, to the second electronic device (e.g., a request to cause a notification or other message to be displayed on the authorizing device indicating that an attempt to change the usage limit settings on the restricted device has been detected. In some embodiments, this notification on the authorizing device identifies the specific usage limit settings that the restricted device is attempting to change and/or includes information about how the restricted device is attempting to change the usage limit settings (e.g., the new value of the usage limit settings detected on the restricted device). In some embodiments, in response to an input detected on the authorizing device that allows the change, the authorizing device sends a change authorization to the restricted device, and the restricted device is allowed to change the usage limit settings on the restricted device. In some embodiments, in response to an input detected on the authorizing device that denies the change, the restricted device is not allowed to change the usage limit settings, and the usage limit settings remain as they were before the input to change the usage limit settings was detected).

In some embodiments, after sending a request for permission to change the usage restriction settings to the second electronic device (1510), as in FIG. 14D-FIG. 14F, the first electronic device is allowed to change the usage restriction settings (1512), as in FIG. 14G-FIG. 14H, according to a determination that an allow response is received from the second electronic device (e.g., the user of the allowing device selects the "allow" affordance displayed on the notification received on the allowing device), and the first electronic device is denied to change the usage restriction settings (1514), as in FIG. 14I, according to a determination that a deny response is received from the second electronic device (e.g., the user of the allowing device selects the "deny" affordance displayed on the notification received on the allowing device). In some embodiments, the user of the restricted device can allow the restricted device to change the usage settings even if no response is received from the allowing device, instead of entering a passcode on the restricted device.

The above-described method of controlling from an authorized device changes to usage restriction settings on a restricted device allows an electronic device to provide an efficient way to facilitate such changes when requiring authorization from another party, thereby improving usability of the device and making the user's interface with the device more efficient (e.g., by allowing the user to interact with the device with less input), as well as reducing power usage and improving the device's battery life 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 settings includes allowing the first electronic device to change the usage restriction settings (1516) until detection of an exit condition for allowing the first electronic device to change the usage restriction settings, such as FIG. 14G (e.g., the restricted device is allowed to change the usage restriction settings for a predetermined period of time (e.g., 30 seconds, 2 minutes, 5 minutes) after receiving authorization from the authorizing device; the restricted device is allowed to change the usage restriction settings until the restricted device exits the settings user interface where such changes are to be made (and optionally must request authorization again before being allowed to change the usage restriction settings after exiting the settings user interface); the restricted device is allowed to change the usage restriction settings until the restricted device confirms the setting changes (e.g., by selection of a "Save" or "OK" or "Back" affordance in the settings user interface to implement the setting changes); the restricted device is allowed to change the usage restriction settings until the restricted device exits the settings user interface for longer than a predetermined amount of time (e.g., 30 seconds, 2 minutes, 5 minutes)).

The above-described methods of restricting in various ways the ability of a restricted device to change usage restriction settings according to authorization to do so enable an electronic device to manage such authorization in a non-unlimited manner, thereby improving device usability and streamlining the user-device interface (e.g., by allowing an authorizing device to efficiently manage changes to usage settings on a restricted device) as well as reducing power usage and improving device battery life by allowing a user to use the device more quickly and efficiently.

In some embodiments, after allowing the first electronic device to change the usage restriction settings, the first electronic device changes the usage restriction settings (1518), such as in FIG. 14H, to modify the operation of the first electronic device in accordance with the change in usage restriction settings (e.g., modifying applications or application usage limits implemented on the restricted device in accordance with the change in usage settings, modifying device downtime on the restricted device in accordance with the change in usage settings, etc., as described in methods 700, 900, 1100, and/or 1300).

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

In some embodiments, in response to receiving a series of one or more inputs, in accordance with a determination that the series of one or more inputs includes at least an input corresponding to an authentication credential, such as an input at keypad 1482 shown in FIG. 14D (1520) (e.g., a passcode, biometric, or other authentication credential for changing the usage restriction setting as described in methods 700, 900, 1100, and/or 1300), the first electronic device is enabled to change the usage restriction setting, such as in FIGS. 14G-14H (1522), in accordance with the authentication credential being successfully authenticated (e.g., a user of the restricted device enters a correct credential for changing the usage restriction setting), and in accordance with the authentication credential not being successfully authenticated (e.g., a user of the restricted device enters an incorrect credential for changing the usage restriction setting), the first electronic device refrains from enabling the first electronic device to change the usage restriction setting (1524), such as in FIG. 14J. Thus, in some embodiments, the restricted device is enabled to change usage restriction settings in response to entering authentication credentials at the restricted device instead of receiving authorization from the authorizing device. In some embodiments, when authentication credentials are entered at the 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 allows an electronic device to provide an efficient way of enabling such changes (e.g., locally), thereby improving usability of the device and providing a more efficient user-device interface (e.g., by allowing a user to interact with the device with alternative inputs), as well as allowing a user to use the device more quickly and efficiently, thereby reducing power usage and improving the device's battery life.

In some embodiments, the first electronic device receives input via one or more input devices to allow or not allow sharing with the second electronic device of website browsing activity on the first electronic device identifying one or more websites viewed on the first electronic device (1526) (e.g., allowing or not allowing the authorizing device to see the names/identification of individual websites viewed by the user of the restricted device (compared to total website browsing time, which the authorizing device can optionally see, regardless of whether the restricted device allows or does not allow sharing of individual website browsing shares), in a manner similar to dialog 1489-20 described above with reference to FIG. 14F). In some embodiments, the user of the restricted device can only control sharing of this website browsing data if the user of the restricted device's account is over a certain age (e.g., 10 years old, 13 years old, 18 years old), and cannot control sharing of this data otherwise). In response to receiving an input to allow or not allow sharing of website browsing activity with the second electronic device (1528), in a manner similar to allowing or not allowing described above with reference to FIG. 14F, in accordance with a determination that the input allows sharing of website browsing activity identifying one or more websites viewed on the first electronic device with the second electronic device, the first electronic device may share (1530) with the second electronic device the website browsing activity identifying one or more websites viewed on the first electronic device (e.g., an allowing device may share identifying information (e.g., web address, title/name) of each website viewed by the user of the restricted device, such as in FIG. 14M. In accordance with a determination that the input does not permit sharing with the second electronic device of website browsing behavior identifying one or more websites viewed on the first electronic device (e.g., the permitting device cannot see the identification (e.g., web address, title/name, etc.) of individual websites viewed by the user of the restricted device and/or the time spent viewing those individual websites), the first electronic device refrains from sharing with the second electronic device (1532) website browsing behavior identifying one or more websites viewed on the first electronic device (e.g., the permitting device cannot see the identification (e.g., web address, title/name, etc.) of individual websites viewed by the user of the restricted device and/or the time spent viewing those individual websites).

The above-described methods of controlling the sharing of individual website usage information allow electronic devices to provide an efficient way of maintaining privacy on restricted devices while still facilitating enforcement of usage restrictions, thereby improving device usability and making the user's interface with the device more efficient (e.g., by allowing the user to interact with the device with less input), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

In some embodiments, while the setting that does not allow sharing of website browsing activity identifying one or more websites viewed on the first electronic device with the second electronic device is enabled, the first electronic device shares website browsing activity that does not identify one or more websites viewed on the first electronic device with the second electronic device (1534), such as in FIG. 14K (e.g., even though the authorizing device cannot see individual website browsing information from the restricted device, the authorizing device can see information about general web usage on the restricted device, such as which websites were viewed, the time periods when the websites were viewed, the duration of individual sessions of website browsing, and/or the total amount of time spent viewing websites on the restricted device without being able to see the specific web pages or subdomains viewed, and instead the amount of time the websites were used is aggregated to application usage).

The above-described method of continuing to share general web usage information with authorized devices allows an electronic device to provide an efficient way of enforcing usage restrictions even when individual website usage information is not shared with authorized devices, thereby improving device usability and providing a more efficient user-device interface (e.g., by allowing a user to interact with the device with less input), as well as reducing power usage and improving device battery life by allowing a user to use the device more quickly and efficiently.

In some embodiments, while a setting is enabled that does not allow sharing of website browsing activity identifying one or more websites viewed on the first electronic device with the second electronic device, the first electronic device shares website browsing activity corresponding to one or more applications or one or more categories of applications with the second electronic device (1536), such as in FIG. 14K (e.g., sharing with the second electronic device includes aggregating statistics regarding use of the first application and use of the web browser to access websites associated with the first application, and aggregating statistics regarding use of the second application and use of the web browser to access websites associated with the second application, without sharing specific information regarding the web browsing activity performed in the web browser) (e.g., individual websites from devices with restricted allowed devices). Even without being able to see the browsing information, the authorizing device may still be able to see information regarding web usage related to websites corresponding to an application (e.g., ESPN website browsing corresponding to the ESPN app is reflected on the authorizing device as use of the ESPN app) or a category of applications (e.g., social media website browsing corresponding to a category of social media apps is reflected on the authorizing device as use within the social media category of apps). Additionally, in some embodiments, usage limits for those applications or categories may still be imposed on the restricted device, if applicable, such that website browsing on the restricted device is restricted when that browsing is restricted by application/category limits in place on the restricted device, as described in methods 700, 900, 1100, and/or 1300).

The above-described method of reflecting website usage data corresponding to applications/application categories allows electronic devices to provide an efficient method of enforcing usage restrictions even when individual website usage information is not shared with authorizing devices, thereby improving device usability and making the user's interface with the device more efficient (e.g., by allowing the user to interact with the device with less input), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

In some embodiments, pursuant to a determination that the user associated with the account of the first electronic device has an age lower than a predetermined age (e.g., 10, 13, 15), the second electronic device is prevented from removing (e.g., the second device cannot remove) the requirement for authentication on the first electronic device to change the usage restriction settings, such as in FIG. 14O (e.g., the authorizing device cannot remove the requirement to provide a passcode or other authentication credential or action (such as authorization of the authorizing device) on the restricted device to change the usage restriction settings on the restricted device. In some embodiments, however, the authorizing device can change the passcode or other authentication credential required on the restricted device to change the usage restriction settings on the restricted device). Pursuant to a determination that the user associated with the account of the first electronic device has an age greater than a predetermined age (e.g., 10, 13, 15), the second electronic device is enabled to remove the requirement for authentication at the first electronic device to change the usage restriction settings (1540), such as in FIG. 14N (e.g., the authorizing device may remove the requirement to provide a passcode or other authentication credential or action (such as authorization of the authorizing device) at the restricted device to change the usage restriction settings on the restricted device. In some embodiments, the authorizing device may instead still change the passcode or other authentication credential required at the restricted device to change the usage restriction settings on the restricted device).

The above-described method of providing an authorized device with a controlled ability to remove passcode requirements from restricted devices allows an electronic device to provide an efficient method of enforcing usage restrictions even when individual website usage information is not shared with the authorized device, thereby improving device usability and making the user's interface with the device more efficient (e.g., by allowing the user to interact with the device with less input), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

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

The above-described method of allowing both the restricted device and the authorizing device to change usage restriction settings once the passcode requirement is removed allows the electronic device to provide an efficient way to facilitate such changes while maintaining the authorizing device's ability to affect usage restriction settings on the restricted device, thereby improving device usability and making the user's interface with the device more efficient (e.g., by allowing the user to interact with the device with less input), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

In some embodiments, following a determination that a user associated with the account of the first electronic device has an age greater than a predetermined age (e.g., 15 years old, 18 years old), the first electronic device may stop sharing device usage information with the second electronic device (1544), such as in FIG. 14R-14T (e.g., the restricted device may disable the ability of the authorizing device or administrator account to view usage information regarding the restricted device. In some embodiments, the restricted device may disassociate from the authorizing device and turn off or otherwise adjust usage restriction settings on the restricted device without relying on any authentication from the authorizing device). Following a determination that a user associated with the account of the first electronic device has an age less than a predetermined age, the second electronic device may not stop sharing device usage information with the second electronic device (1546), such as in FIG. 14B (e.g., the restricted device may not disable the ability of the authorizing device or administrator account to view usage information regarding the restricted device).

The above-described methods of controlling when a restricted device may stop sharing usage information with an authorizing device may provide an efficient way for an electronic device to control such functionality, thereby improving the usability of the device and providing a more efficient interface between the user and the device (e.g., by allowing the user to interact with the device with less input), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

In some embodiments, stopping sharing of device usage information with the second electronic device requires approval from the second electronic device to stop sharing device usage information with the second electronic device (1548) in a manner similar to that described above with reference to FIG. 14F (e.g., the restricted device cannot stop sharing usage information with the authorizing device without approval to do so from the authorizing device or an administrator account. In some embodiments, when the restricted device attempts to turn off sharing of usage information with the authorizing device, the authorizing device displays a notification indicating the request with options to "Allow" or "Deny" the request. If the user of the authorizing device selects "Allow," the restricted device can optionally stop sharing usage information with the authorizing device. If the user of the authorizing device selects "Deny," the restricted device can optionally not stop sharing usage information with the authorizing device).

The above-described method of requiring approval of an authorizing device to stop sharing usage information with the authorizing device allows the electronic device to provide an efficient method of control over such changes by the authorizing device, thereby improving the usability of the device and making the user's interface with the device more efficient (e.g., by allowing the user to interact with the device with less input), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

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

The above-described method of not requiring authorization from an authorizing device to stop sharing usage information allows an electronic device to provide an efficient way to stop such sharing, thereby improving device usability and making the user's interface with the device more efficient (e.g., by allowing the user to interact with the device with less input), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

In some embodiments, in response to a determination that a user associated with the account of the first electronic device has reached a predetermined age (e.g., based on the user's birth date and the current date/time), the first electronic device generates (1552) a notification, such as in FIG. 14Q, indicating that the first electronic device may stop sharing device usage information with the second electronic device (e.g., the restricted device may display a notification once the user of the restricted device has reached an age at which the user may stop sharing usage information with permitted devices so that the user knows that they may now take such action).

The above-described method of generating a notification to a user of a restricted device when information sharing with permitted devices can be changed allows an electronic device to provide an efficient way to facilitate such changes, thereby improving usability of the device and making the user's interface with the device more efficient (e.g., by allowing the user to interact with the device with less input), as well as reducing power usage and improving the device's battery life 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, a control for stopping sharing of device usage information with the second electronic device, such as in FIG. 14R-FIG. 14S, is available on the first electronic device (1554) (e.g., an affordance, button, or controller for changing the allowed device sharing of usage information is displayed and enabled in the usage restriction settings user interface on the restricted device), and following a determination that the user associated with the account of the first electronic device has an age less than a predetermined age, a control for stopping sharing of device usage information with the second electronic device, such as in FIG. 14B, is not available on the first electronic device (1556) (e.g., an affordance, button, or controller for changing the allowed device sharing of usage information is not displayed in the usage restriction settings user interface on the restricted device, or is displayed but not enabled (e.g., grayed out) in the usage restriction settings user interface on the restricted device).

The above-described methods of making available or not making available controls to change the sharing of information with permitted devices allow electronic devices to provide an efficient way to facilitate such changes while conforming to limitations on the ability to make such changes, thereby improving usability of the device and making the user's interface with the device more efficient (e.g., by allowing the user to interact with the device with less input), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

In some embodiments, a user associated with an account for the first electronic device has an age greater than a predetermined age (1558), such as in FIG. 14R-FIG. 14S. The first electronic device, such as in FIG. 14S, receives an input via one or more input devices to stop sharing device usage information with the second electronic device (1560), and in response to receiving the input to stop sharing device usage information with the second electronic device, the first electronic device stops sharing device usage information with the second electronic device (1562), such as in FIG. 14T (e.g., a user of the restricted device selects a button or toggle switch in a usage restriction settings user interface to stop sharing usage information with allowing devices). In some embodiments, after ceasing to share device usage information with the second electronic device, the first electronic device may change usage restriction settings on the first electronic device, and the second electronic device may not change usage restriction settings on the first electronic device (1564) in a manner similar to that described above with reference to FIG. 14G (e.g., once usage information sharing and/or usage restriction sharing with an authorizing device or administrator account is disabled, the previously restricted device may change usage restriction settings on the previously restricted device, but the authorizing device or administrator account may no longer change such settings on the previously restricted device. In effect, the restricted device is, optionally, no longer restricted by the authorizing device/administrator account).

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

In some embodiments, while a first electronic device, such as in FIG. 14G, is being enabled to change usage limit settings (1566), the first electronic device receives, via one or more input devices, a series of one or more inputs for changing one or more usage limit settings on the first electronic device (1568), such as in FIG. 14G (e.g., after receiving approval from an authorizing device to change usage limit settings on the restricted device, a user of the restricted device provides inputs to the restricted device for changing usage limit settings, such as changing one or more usage limits implemented on the restricted device, changing device downtime settings implemented on the restricted device), and in response to receiving the series of one or more inputs for changing one or more usage limit settings on the first electronic device, the first electronic device transmits information regarding the changes to one or more usage limit settings on the first electronic device (1570), such as in FIG. 14I (e.g., the restricted device transmits information regarding the changes to usage limit settings that the restricted device attempted to make (e.g., a particular usage limit change, a particular device downtime change, etc.,). In some embodiments, the restricted device makes changes to the limited use settings and, in conjunction with making the changes, sends information about the changes to the authorizing device, which optionally displays a notification of the changes so that the user of the authorizing device can view the changes made on the restricted device. In such embodiments, the notification optionally does not have a mechanism by which the user of the authorizing device can undo, reject, or override the changes made by the restricted device. Rather, in such embodiments, the authorizing device must optionally manually make changes to the usage restriction settings of the restricted device to override any of the changes made by the restricted device. In contrast, in some embodiments, the restricted device does not make changes to the limited use settings and first sends information about the attempted changes to the authorizing device, which optionally displays a notification of the attempted changes so that the user of the authorizing device can view the proposed changes on the restricted device. In such an embodiment, the notification optionally includes a mechanism (e.g., a selectable affordance) that allows the user of the allowing device to cancel/reject/override or accept the change attempted by the restricted device).

The above-described method of transmitting information regarding usage restriction changes to authorizing devices allows an electronic device to efficiently communicate such changes to authorizing devices, thereby improving the usability of the device and making the user's interface with the device more efficient (e.g., by allowing the device to operate with less input from the user), as well as allowing the user to use the device more quickly and efficiently, thereby reducing power usage and improving the device's battery life.

In some embodiments, pursuant to a determination that one or more usage limit settings on the first electronic device have been remotely changed (e.g., by the second electronic device or another electronic device associated with a user enabled to change the usage limit settings of the first electronic device, such as an administrator account), the first electronic device displays a notification (1572), such as in FIG. 14P, indicating the change of one or more usage limit settings on the first electronic device by the second electronic device (e.g., the restricted device receives information from the authorizing device regarding changes made by the authorizing device to the usage limit settings on the restricted device, and in response, the restricted device displays a notification on the restricted device with details of the changes (e.g., changed usage limit, device downtime, etc.) such that the user of the restricted device can view the changes made by the authorizing device).

The above-described method of displaying a notification on a restricted device with usage restriction changes made by an allowing device allows an electronic device to provide an efficient way for the electronic device to provide information of such changes to a user of the restricted device, thereby improving usability of the device and making the user-device interface more efficient (e.g., by allowing the user to interact with the device with less input), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

In some embodiments, the one or more usage limit settings on the first electronic device being remotely modified include a definition of an initial usage limit setting on the first electronic device when no usage limit settings were previously implemented on the first electronic device (1574), such as in FIG. 14A (e.g., the restricted device receives from the authorizing device or an administrator account information regarding the initial usage restrictions that the authorizing device will implement on the restricted device when the authorizing device implements those restrictions, and in response, the restricted device displays a notification on the restricted device with details of those initial restrictions (e.g., usage limits, device downtime, etc.), and updates the restricted device's settings (1574) ... updates the restricted device's settings (1574) (e.g., the restricted device receives from the authorizing device or an administrator account information regarding the initial usage restrictions that the authorizing device will implement on the restricted device when the authorizing device implements those restrictions, and in response, updates the restricted device's settings (1574) (e.g., the restricted device receives from the authorizing device or an administrator account information regarding the initial usage restrictions that the authorizing device will implement on the restricted Allows the user to view usage restrictions currently in place on the restricted device. In some embodiments, the notification includes information about all of the restrictions currently in place on the restricted device (e.g., any usage limits, any characteristics of device downtime, etc.). In some embodiments, the notification instead includes a summary of the major restrictions currently in place on the restricted device, such as total limits on games (as opposed to limits on individual games), total screen time limits (as opposed to individual limits on screen time), start and stop times for device downtime (as opposed to including any device-defined exceptions allowed for device downtime).

The above-described method of displaying a notification on a restricted device with the initial usage restriction settings made by the allowing device allows an electronic device to provide an efficient way for the electronic device to provide information of such settings to a user of the restricted device, thereby improving usability of the device and making the user-device interface more efficient (e.g., by allowing the user to interact with the device with less input), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

It should be understood that the particular order described for the operations in Figures 15A-15G is merely exemplary, and the order described is not intended to indicate that the operations are the only order in which they may be performed. Those skilled in the art will recognize various ways to reorder the operations described herein. In addition, it should be noted that other process details described herein with respect to other methods described herein (e.g., methods 700, 900, 1100, and 1300) are applicable in a similar manner to method 1500 described above with respect to Figures 15A-15G. For example, the method of updating limit settings on one electronic device with the permission of another electronic device or user account described above with reference to method 1500, usage limit settings, etc., optionally has one or more of the characteristics of a dashboard user interface of usage metrics, usage metrics, notification metrics, device pickup metrics, usage limit settings, etc. described herein with reference to other methods described herein (e.g., methods 700, 900, 1100, and 1300). For the sake of brevity, these details will not be repeated here.

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

As discussed 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 a user. The present disclosure contemplates that, in some cases, this collected data may include personal information data that uniquely identifies a particular person or that can be used to contact or locate that person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, Twitter IDs, home addresses, data or records regarding the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), birth date, or any other identifying or personal information.

This disclosure recognizes that the use of such personal information data may be used in the present technology to benefit the user. For example, the personal information data may be used to present or control device usage in a manner that is meaningful to the user. Thus, use of such personal information data may enable more personalized delivery of such services to the user. Additionally, other uses of personal information data to benefit the user are also contemplated by this disclosure. For example, health and fitness data may be used to provide insight into the user's overall wellness, or may be used as proactive feedback to individuals using technology to pursue wellness goals.

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 should implement and always use privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for keeping personal information data confidential and secure. 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 the entity's lawful and legitimate use and should not be shared or sold except for those lawful uses. Furthermore, such collection/sharing should only be carried out after the user has been informed and consented to. In addition, such entities should take all necessary measures to protect and secure access to such personal information data and ensure that others having access to that personal information data comply with their privacy policies and procedures. Furthermore, such entities may subject themselves to third-party assessments to attest to 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 should conform to applicable laws and standards, including jurisdiction-specific considerations. For example, in the United States, the collection or access of certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA), while health data in other countries may be subject to other regulations and policies and should be addressed accordingly. Thus, different privacy practices should 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 blocks 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, in the case of presenting information regarding device usage, the present technology may be configured to allow a user to select to "opt-in" or "opt-out" of participating in the collection of personal information data during registration for the service or at any time thereafter. In another example, a user may choose not to provide user-based or device-based usage data for purposes of determining device usage and/or control of such use. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notifications regarding access or use of personal information. For example, a user may be notified upon download of an app that will access the user's personal information data, and then again immediately prior to the personal information data being 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 collection of data and deleting data when it is no longer needed. In addition, where applicable, data de-identification can be used to protect user privacy, even in certain health-related applications. De-identification can be facilitated by removing certain identifiers (e.g., date of birth, etc.) where appropriate, controlling the amount or specificity of data stored (e.g., collecting location data at a city level rather than an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods.

Thus, while this disclosure broadly encompasses the use of personal information data to implement one or more of the various disclosed embodiments, this disclosure also contemplates that the various embodiments may also be implemented without requiring access to such personal information data. That is, the various embodiments of the technology are not rendered inoperable by the absence of all or a portion of such personal information data. For example, device usage information may be determined by inferring device usage based on non-personal information data such as content requested by a device associated with a user or minimal personal information, other non-personal information available for the device, or publicly available information.

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

Claims (17)

1. A method comprising:
1. An electronic device in communication with a display and one or more input devices, comprising:
detecting an event corresponding to activation of an auxiliary function of a first application during enforcement of a restriction on one or more applications, including a first application of a plurality of applications installed on the electronic device, due to one or more usage limits being satisfied that define an amount of time the one or more applications may be accessed, the auxiliary function of the first application being a function available for execution without displaying a primary user interface of the first application;
in response to detecting the event corresponding to activation of the auxiliary function of the first application,
inhibiting the auxiliary functionality in accordance with a determination that a usage limit for the first application has been met;
executing the auxiliary function without displaying the primary user interface of the first application in accordance with a determination that the usage limit for the first application has not been met;
A method comprising: 2. The method of claim 1 ,
the auxiliary function including presenting an indication of a first type of notification in response to an occurrence of an event corresponding to activation of a notification associated with the first application.
method. 3. The method of claim 2,
suppressing the auxiliary functionality includes refraining from presenting the first type of indication in response to the notification associated with the first application;
performing the auxiliary function includes presenting an indication of the first type in response to the notification associated with the first application.
method. 4. The method of claim 3, further comprising, in accordance with the determination that the usage limit for the first application has been met,
including a visual indication of the first type of indication within a notification history user interface, the notification history user interface further including one or more indications of notifications generated by one or more applications other than the first application. 3. The method of claim 2, wherein suppressing the auxiliary functionality includes forgoing presenting the first type of indication in response to the notification generated by the first application, the method further comprising:
After suppressing the auxiliary function of the first application,
determining that the usage limit for the first application is no longer satisfied;
presenting the indication regarding the notification generated by the first application in response to determining that the usage limit for the first application is no longer satisfied; and
A method comprising: 2. The method of claim 1 ,
the auxiliary functionality includes displaying a widget user interface that displays one or more secondary user interfaces of one or more applications, including a secondary user interface of the first application;
the event corresponding to activation of the auxiliary function includes a request to display the widget user interface;
suppressing the auxiliary functionality includes displaying the widget user interface while suppressing the secondary user interface of the first application.
method. 2. The method of claim 1 ,
the auxiliary functionality includes presenting, within a suggestion user interface, a visual indication of one or more applications, including the first application, for which suggestion criteria are met;
the event corresponding to activation of the auxiliary feature includes a request to present, within the suggestions user interface, a visual indication of the one or more applications for which the suggestion criteria are met;
and suppressing the auxiliary functionality includes presenting the suggestion user interface without presenting a visual indication of the first application.
method. 2. The method of claim 1 ,
The auxiliary functionality includes displaying web content associated with the first application within a browser user interface;
the event corresponding to activation of the auxiliary function includes a request to display, within the browser user interface, web content associated with the first application;
and inhibiting the auxiliary functionality includes preventing access to the web content associated with the first application.
method. 10. The method of claim 8, wherein preventing access to the web content associated with the first application comprises:
loading the web content associated with the first application from a first website;
forgoing displaying the web content associated with the first application; and
A method comprising: 10. The method of claim 8, wherein preventing access to the web content associated with the first application comprises:
forgoing displaying the web content associated with the first application while maintaining display of one or more user interface elements for navigating to another website within the browser user interface. 9. The method of claim 8, further comprising:
detecting a second event corresponding to a request to view second web content from a second website within the browser user interface while the usage limit for the first application is being satisfied; and
in response to detecting the second event corresponding to a request to view the second web content from the second website within the browser user interface while the usage limit for the first application is being satisfied,
refraining from displaying the second web content in accordance with a determination that the second web site is associated with the first application;
displaying the second web content in accordance with a determination that the second website is associated with a second application and a restriction criterion for the second application is not met; and
A method comprising: 2. The method of claim 1 ,
The auxiliary functionality includes displaying media content within a picture-in-picture user interface of the first application, the picture-in-picture user interface partially overlaid on one or more other user interfaces;
the event corresponding to activation of the auxiliary function includes a request to display the media content within the picture-in-picture user interface of the first application;
and suppressing the auxiliary functionality includes suppressing the picture-in-picture user interface of the first application.
method. 13. The method of claim 12, wherein suppressing the picture-in-picture user interface of the first application comprises:
responsive to a determination that the usage limit for the first application is satisfied while displaying the picture-in-picture user interface of the first application,
obscuring the picture-in-picture user interface for a first period of time;
ceasing to display the picture-in-picture user interface after the first period of time; and
A method comprising: 2. The method of claim 1 ,
the auxiliary functionality includes displaying a plurality of affordances for controlling playback of media content associated with the first application;
the event corresponding to activation of the auxiliary functionality includes a request to display the plurality of affordances for controlling playback of the media content associated with the first application;
and inhibiting the auxiliary functionality includes preventing the plurality of affordances from controlling playback of the media content associated with the first application.
method. 15. The method of claim 14, wherein preventing the plurality of affordances from controlling the playback of the media content associated with the first application comprises:
placing the plurality of affordances in an inactive state during a first time period in which the electronic device ignores user input directed at the plurality of affordances;
after the first period of time, placing the plurality of affordances in a default state different from the inactive state;
A method comprising: 1. An electronic device comprising:
one or more processors;
Memory,
and one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing any of the methods according to claims 1 to 15.
Electronic devices. A non-transitory computer-readable recording medium having stored thereon one or more programs, the one or more programs comprising instructions that, when executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, cause the computer system to perform any of the methods of claims 1 to 15.
A non-transitory computer-readable recording medium.

Images