CN116546134A

CN116546134A - User interface for controlling or presenting device usage on an electronic device

Info

Publication number: CN116546134A
Application number: CN202310102093.8A
Authority: CN
Inventors: E·C·克兰菲尔; C·P·福斯; D·C·格拉哈姆; G·铃木
Original assignee: Apple Inc
Current assignee: Apple Inc
Priority date: 2018-05-08
Filing date: 2018-12-20
Publication date: 2023-08-04
Also published as: JP6844904B2; CN114047856B; JP2019197527A; JP7236480B2; CN110471582A; CN110471582B; JP2023088907A; JP2021099826A; CN114047856A; CN110471581A

Abstract

The invention provides a user interface for controlling or presenting device usage on an electronic device. "in some embodiments, the electronic device presents a device usage metric indication. In some embodiments, the electronic device sets, configures, and/or enforces device usage limits. In some embodiments, the electronic device restricts access to certain applications during certain time periods. In some embodiments, the electronic device suppresses auxiliary functions of certain applications when application use limits or constraints associated with those applications are reached. In some embodiments, the electronic device manages the limit settings with permissions optionally provided by another electronic device.

Description

User interface for controlling or presenting device usage on an electronic device

The present application is a divisional application of chinese patent application 201811591484.6 with the title of "user interface for controlling or presenting device usage on an electronic device" having a filing date of 2018, 12, 20.

Technical Field

This document relates generally to electronic devices that control or present information regarding device usage, and user interactions with such devices.

Background

In recent years, user interaction with electronic devices has been significantly enhanced. These devices may be devices such as computers, tablets, televisions, multimedia devices, mobile devices, etc.

In some cases, a user may wish to view information about and/or control his use of such devices. Enhancing these interactions may improve the user's experience of using the device and reduce user interaction time, which is particularly important where the input device is battery powered.

Disclosure of Invention

Some embodiments described in this disclosure relate to one or more electronic devices presenting an indication of a device usage measure, and one or more operations related to the foregoing that the electronic device optionally performs. Some embodiments described in this disclosure relate to one or more electronic devices that set, configure, and/or implement device usage limits, and one or more operations related to the foregoing that the electronic devices optionally perform. Some embodiments described in this disclosure relate to one or more electronic devices that limit access to a particular application during a particular period of time, and one or more operations related to the foregoing that the electronic device optionally performs. Some embodiments described in this disclosure relate to one or more electronic devices that inhibit auxiliary functions of particular applications when application usage limits or constraints associated with those applications are reached, and one or more operations related to the above that the electronic devices optionally perform. Some embodiments described in this disclosure relate to one or more electronic devices managing restriction settings with permissions optionally provided by another electronic device, and one or more operations related to the foregoing optionally performed by the electronic device. A full description of the embodiments is provided in the accompanying drawings and detailed description, and it is to be understood that the summary of the invention provided above is not in any way limiting the scope of the disclosure.

Drawings

For a better understanding of the various described embodiments, reference should be made to the following detailed description taken in conjunction with the accompanying drawings in which like reference numerals designate corresponding parts throughout the figures thereof.

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

FIG. 1B is a block diagram illustrating exemplary components for event processing according to some embodiments.

Fig. 2 illustrates a portable multifunction device with a touch screen in accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.

FIG. 4A illustrates an exemplary user interface for an application menu on a portable multifunction device in accordance with some embodiments.

Fig. 4B illustrates an exemplary user interface of a multifunction device with a touch-sensitive surface separate from a display in accordance with some embodiments.

Fig. 5A illustrates a personal electronic device according to some embodiments.

Fig. 5B is a block diagram illustrating a personal electronic device, according to some embodiments.

Fig. 5C-5D illustrate exemplary components of a personal electronic device having a touch sensitive display and an intensity sensor, according to some embodiments.

Fig. 5E-5H illustrate exemplary components and user interfaces of a personal electronic device according to some embodiments.

Fig. 6A-6 AU illustrate an exemplary manner in which an electronic device presents usage metric indications in accordance with some embodiments of the present disclosure.

Fig. 7A-7S are flowcharts illustrating a method of presenting usage metric indications, according to some embodiments of the present disclosure.

Fig. 8A-8 AAN illustrate an exemplary manner of setting, configuring, and/or enforcing usage limits on electronic devices according to some embodiments of the present disclosure.

Fig. 9A-9K are flowcharts illustrating a method of setting, configuring, and/or implementing use limits according to some embodiments of the present disclosure.

Fig. 10A-10 AAA illustrate an exemplary manner in which an electronic device limits access to a particular application during a particular time period according to some embodiments of the present disclosure.

Fig. 11A-11I are flowcharts illustrating a method of restricting access to a particular application during a particular time period according to some embodiments of the present disclosure.

Fig. 12A-12 AB illustrate an exemplary manner in which an electronic device suppresses auxiliary functions of particular applications when application usage limits associated with those applications are reached, according to some embodiments of the present disclosure.

Fig. 13A-13H are flowcharts illustrating a method of suppressing auxiliary functions of particular applications when application usage limits associated with those applications are reached, according to some embodiments of the present disclosure.

Fig. 14A-14T illustrate an exemplary manner in which an electronic device manages limit settings with permissions optionally provided by another electronic device, according to some embodiments of the disclosure.

Fig. 15A-15G are flowcharts illustrating a method of managing limit settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure.

Detailed Description

The following description sets forth exemplary methods, parameters, and the like. However, it should be recognized that such description is not intended as a limitation on the scope of the present disclosure, but is instead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methods and interfaces for presenting information about and/or controlling device usage. Such techniques may reduce the cognitive burden on users using such devices and/or desiring to control their use of such devices. Further, such techniques may reduce processor power and battery power that would otherwise be wasted on redundant user inputs.

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

The terminology used in the description of the various illustrated embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments 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. It will also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "comprises," "comprising," "includes," and/or "including," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

Depending on the context, the term "if" is optionally interpreted to mean "when..once..once.," in response to determining "or" in response to detecting ". Similarly, the phrase "if determined … …" or "if detected [ stated condition or event ]" is optionally interpreted to mean "upon determining … …" or "in response to determining … …" or "upon detecting [ stated condition or event ]" or "in response to detecting [ stated condition or event ]" depending on the context.

Embodiments of electronic devices, user interfaces for such devices, and related processes for using such devices are described herein. In some embodiments, the apparatus is a device further comprisingPortable communication devices such as mobile phones with other functions such as PDA and/or music player functions. Exemplary embodiments of the portable multifunction device include, but are not limited to, those from Apple inc (Cupertino, california)Device, iPod->Device, and->An apparatus. Other portable electronic devices, such as a laptop or tablet computer having a touch-sensitive surface (e.g., a touch screen display and/or a touchpad), are optionally used. It should also be appreciated that in some embodiments, the device is not a portable communication device, but rather a desktop computer having a touch-sensitive surface (e.g., a touch screen display and/or a touch pad).

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

The device typically supports various applications such as one or more of the following: drawing applications, presentation applications, word processing applications, website creation applications, disk editing applications, spreadsheet applications, gaming applications, telephony applications, video conferencing applications, email applications, instant messaging applications, fitness 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 generic physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and/or changed for different applications and/or within the respective applications. In this way, the common physical architecture of the devices (such as the touch-sensitive surface) optionally supports various applications with a user interface that is intuitive and transparent to the user.

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

As used in this specification and the claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of the contact on the touch-sensitive surface (e.g., finger contact), or to an alternative to the force or pressure of the contact on the touch-sensitive surface (surrogate). The intensity of the contact has a range of values that includes at least four different values and more typically includes hundreds of different values (e.g., at least 256). The intensity of the contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure forces at different points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted average) to determine an estimated contact force. Similarly, the pressure-sensitive tip of the stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area and/or its variation detected on the touch-sensitive surface, the capacitance of the touch-sensitive surface in the vicinity of the contact and/or its variation and/or the resistance of the touch-sensitive surface in the vicinity of the contact and/or its variation are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, surrogate measurements of contact force or pressure are directly used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to surrogate measurements). In some implementations, surrogate measurements of contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). The intensity of the contact is used as an attribute of the user input, allowing the user to access additional device functions that are not otherwise accessible to the user on a smaller sized device of limited real estate for displaying affordances and/or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical/mechanical control, such as a knob or button).

As used in this specification and in the claims, the term "haptic 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 a centroid of the device, to be detected by a user with a user's feel. For example, in the case where the device or component of the device is in contact with a touch-sensitive surface of the user (e.g., a finger, palm, or other portion of the user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a haptic sensation corresponding to a perceived change in a physical characteristic of the device or component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or touch pad) is optionally interpreted by a user as a "press click" or "click-down" of a physically actuated button. In some cases, the user will feel a tactile sensation, such as "press click" or "click down", even when the physical actuation button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement is not moved. As another example, movement of the touch-sensitive surface may optionally be interpreted or sensed by a user as "roughness" of the touch-sensitive surface, even when the smoothness of the touch-sensitive surface is unchanged. While such interpretation of touches by a user will be limited by the user's individualized sensory perception, many sensory perceptions of touches are common to most users. Thus, when a haptic output is described as corresponding to a particular sensory perception of a user (e.g., "click down," "click up," "roughness"), unless stated otherwise, the haptic output generated corresponds to a physical displacement of the device or component thereof that would generate that sensory perception of a typical (or ordinary) user.

It should be understood that the device 100 is merely one example of a portable multifunction device, and that the device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the 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 and/or application specific integrated circuits.

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

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

The RF (radio frequency) circuit 108 receives and transmits RF signals, also referred to as electromagnetic signals. The RF circuitry 108 converts/converts electrical signals to/from electromagnetic signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 optionally includes well known circuitry for performing these functions including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a codec chipset, a Subscriber Identity Module (SIM) card, memory, and the like. RF circuitry 108 optionally communicates via wireless communication with networks such as the internet (also known as the World Wide Web (WWW)), intranets, and/or wireless networks such as cellular telephone networks, wireless Local Area Networks (LANs), and/or Metropolitan Area Networks (MANs), and other devices. The RF circuitry 108 optionally includes well-known circuitry for detecting Near Field Communication (NFC) fields, such as by short range communication radios. Wireless communications optionally use any of a variety of communication standards, protocols, and technologies including, but not limited to, global system for mobile communications (GSM), enhanced Data GSM Environment (EDGE), high Speed Downlink Packet Access (HSDPA), high Speed Uplink Packet Access (HSUPA), evolution, pure data (EV-DO), HSPA, hspa+, dual cell HSPA (DC-HSPDA), long Term Evolution (LTE), near Field Communications (NFC), wideband code division multiple access (W-CDMA), code Division Multiple Access (CDMA), time Division Multiple Access (TDMA), 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.11 ac), voice over internet protocol (VoIP), wi-MAX, email protocols (e.g., internet Message Access Protocol (IMAP) and/or Post Office Protocol (POP)), messages (e.g., extensible message handling and presence protocol (XMPP), protocols for instant messaging and presence using extended session initiation protocol (sime), messages and presence (IMPS), instant messaging and/or SMS (SMS) protocols, or any other suitable communications protocol not yet developed herein.

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

I/O subsystem 106 couples input/output peripheral devices on device 100, such as touch screen 112 and other input control devices 116, to peripheral interface 118. The I/O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, an intensity sensor controller 159, a haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive electrical signals from/send electrical signals to the other input control devices 116. Other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click-type dials, and the like. In some alternative implementations, the input controller 160 is optionally coupled to (or not coupled to) any of the following: a keyboard, an infrared port, a USB port, and a pointing device such as a mouse. The one or more buttons (e.g., 208 in fig. 2) optionally include an up/down button for volume control of speaker 111 and/or microphone 113. The one or more buttons optionally include a push button (e.g., 206 in fig. 2).

The quick press of the push button optionally disengages the lock of the touch screen 112 or optionally begins the process of unlocking the device using a gesture on the touch screen, as described in U.S. patent application 11/322,549 (i.e., U.S. patent No.7,657,849), entitled "Unlocking a Device by Performing Gestures on an Unlock Image" (unlocking the device by performing a gesture on an unlock image) filed on day 12, 23 of 2005, which is hereby incorporated by reference in its entirety. Long presses of a button (e.g., 206) optionally cause the device 100 to power on or off. The function of the one or more buttons is optionally customizable by the user. Touch screen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

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

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

Touch screen 112 optionally uses an LCD (liquid crystalDisplay) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, but other display technologies are used in other embodiments. Touch screen 112 and display controller 156 optionally detect contact and any movement or interruption thereof using any of a variety of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In one exemplary embodiment, a projected mutual capacitance sensing technique is used, such as that described in the text from Apple inc (Cupertino, california) And iPod->Techniques used in the above.

The touch sensitive display in some implementations of touch screen 112 is optionally similar to the multi-touch sensitive touch pad 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 et al) and/or U.S. patent publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, while touch sensitive touchpads do not provide visual output.

In some implementations, the touch sensitive display of touch screen 112 is as described in the following patent applications: (1) U.S. patent application Ser. No. 11/381,313 entitled "Multipoint Touch Surface Controller" (Multi-touch surface controller) filed on 5/2/2006; (2) U.S. patent application Ser. No.10/840,862 entitled "Multipoint Touchscreen" (Multi-touch Screen) filed 5/6/2004; (3) U.S. patent application Ser. No.10/903,964, entitled "Gestures For Touch Sensitive Input Devices" (gesture for touch sensitive input device) filed on 7/30 th 2004; (4) U.S. patent application Ser. No.11/048,264, filed on 1/31/2005, entitled "Gestures For Touch Sensitive Input Devices" (gesture for touch sensitive input device); (5) U.S. patent application Ser. No.11/038,590, filed 1/18 2005, entitled "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices" (Pattern-based graphical user interface for touch-sensitive input devices); (6) U.S. patent application Ser. No.11/228,758, filed 9/16/2005, entitled "Virtual Input Device Placement On A Touch Screen User Interface" (virtual input device placed on touch screen user interface); (7) U.S. patent application Ser. No.11/228,700, filed 9/16/2005, entitled "Operation Of A Computer With A Touch Screen Interface" (operation of a computer with touch screen interface); (8) U.S. patent application Ser. No.11/228,737, filed on 9/16/2005, entitled "Activating Virtual Keys Of A Touch-Screen Virtual Keyboard" (activating virtual keys of a touch screen virtual keyboard); and (9) U.S. patent application Ser. No.11/367,749 entitled "Multi-Functional Hand-Held Device" filed 3/2006. All of these applications are incorporated by reference herein in their entirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some implementations, the touch screen has a video resolution of about 160 dpi. The user optionally uses any suitable object or appendage, such as a stylus, finger, or the like, to make contact with touch screen 112. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which may not be as accurate as stylus-based input due to the large contact area of the finger on the touch screen. In some embodiments, the device translates the finger-based coarse input into a precise pointer/cursor position or command for performing the action desired by the user.

In some embodiments, the device 100 optionally includes a touch pad (not shown) for activating or deactivating specific functions in addition to the touch screen. In some embodiments, the touch pad is a touch sensitive area of the device that, unlike a touch screen, does not display visual output. The touch pad is optionally a touch sensitive surface separate from the touch screen 112 or an extension of the touch sensitive surface formed by the touch screen.

The apparatus 100 also includes a power system 162 for powering 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 failure detection circuit, a power converter or inverter, a power status indicator (e.g., light Emitting Diode (LED)), and any other components associated with the generation, management, and distribution of power in the portable device.

The apparatus 100 optionally further comprises one or more optical sensors 164. FIG. 1A shows an optical sensor coupled to an optical sensor controller 158 in the I/O subsystem 106. The optical sensor 164 optionally includes a Charge Coupled Device (CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The optical sensor 164 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with imaging module 143 (also called a camera module), optical sensor 164 optionally captures still images or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite the touch screen display 112 on the front of the device, so that the touch screen display can be used as a viewfinder for still image and/or video image acquisition. In some embodiments, the optical sensor is located on the front of the device such that the user optionally acquires an image of the other video conference participants for video conferencing while the user views the user on the touch screen display. In some implementations, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lenses and sensors in the device housing) such that a single optical sensor 164 is used with the touch screen display for both video conferencing and still image and/or video image acquisition.

The apparatus 100 optionally further comprises one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to an intensity sensor controller 159 in the I/O subsystem 106. The contact strength 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 strength sensors (e.g., sensors for measuring force (or pressure) of a contact on a touch-sensitive surface). The contact strength sensor 165 receives contact strength information (e.g., pressure information or a surrogate for pressure information) from the environment. In some implementations, at least one contact intensity sensor is juxtaposed or adjacent 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 rear of the device 100, opposite the touch screen display 112 located on the front of the device 100.

The device 100 optionally further includes one or more proximity sensors 166. Fig. 1A shows a proximity sensor 166 coupled to the peripheral interface 118. Alternatively, the proximity sensor 166 is optionally coupled to the input controller 160 in the I/O subsystem 106. The proximity sensor 166 optionally performs as described in the following U.S. patent applications: 11/241,839, entitled "Proximity Detector In Handheld Device"; no.11/240,788, entitled "Proximity Detector In Handheld Device" (proximity detector in a handheld device); no.11/620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output" (enhanced proximity sensor output using ambient light sensor); no.11/586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices" (automatic response and sensing of user activity in portable devices); and No.11/638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals" (method and system for automatic configuration of peripheral devices), which are hereby incorporated by reference in their entirety. In some embodiments, the proximity sensor is turned off and the touch screen 112 is disabled when the multifunction device is placed near the user's ear (e.g., when the user is making a telephone call).

The device 100 optionally further comprises one or more tactile output generators 167. FIG. 1A shows a haptic output generator coupled to a haptic feedback controller 161 in the I/O subsystem 106. The 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 a device). The contact intensity sensor 165 receives haptic feedback generation instructions from the haptic feedback module 133 and generates a haptic output on the device 100 that can be perceived by a user of the device 100. In some embodiments, at least one tactile output generator is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112), and optionally generates tactile output by moving the touch-sensitive surface vertically (e.g., inward/outward of the surface of device 100) or laterally (e.g., backward and forward in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the rear of the device 100, opposite the touch screen display 112 located on the front of the device 100.

The device 100 optionally further includes one or more accelerometers 168. Fig. 1A shows accelerometer 168 coupled to peripheral interface 118. Alternatively, accelerometer 168 is optionally coupled to input controller 160 in I/O subsystem 106. Accelerometer 168 optionally performs as described in the following U.S. patent publications: U.S. patent publication 20050190059, entitled "acception-based Theft Detection System for Portable Electronic Devices," and U.S. patent publication 20060017692, entitled "Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer," both of which are incorporated herein by reference in their entirety. In some implementations, information is displayed in a portrait view or a landscape view on a touch screen display based on analysis of data received from one or more accelerometers. The device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) in addition to the accelerometer 168 for obtaining information about the position and orientation (e.g., longitudinal or lateral) of the device 100.

In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact/motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a Global Positioning System (GPS) module (or instruction set) 135, and an application program (or instruction set) 136. Furthermore, in some embodiments, memory 102 (fig. 1A) or 370 (fig. 3) stores device/global internal state 157, as shown in fig. 1A and 3. The device/global internal state 157 includes one or more of the following: an active application state indicating which applications (if any) are currently active; a display state indicating what applications, views, or other information occupy various areas of the touch screen display 112; sensor status, including information obtained from the various sensors of the device and the input control device 116; and location information regarding the location and/or pose of the device.

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

The communication module 128 facilitates communication with other devices through one or more external ports 124 and also includes various software components for processing data received by the RF circuitry 108 and/or the external ports 124. External port 124 (e.g., universal Serial Bus (USB), firewire, etc.) is adapted to be coupled directly to other devices or indirectly via a network (e.g., the internet, wireless LAN, etc.). In some embodiments, the external port is in communication withThe 30-pin connector used on the (Apple inc. Trademark) device is the same or similar and/or compatible with a multi-pin (e.g., 30-pin) connector.

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

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

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

Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other displays, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual characteristics) of the displayed graphics. As used herein, the term "graphic" includes any object that may be displayed to a user, including without limitation text, web pages, icons (such as user interface objects including soft keys), digital images, video, animation, and the like.

In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. The graphic module 132 receives one or more codes for designating graphics to be displayed from an application program or the like, and also receives coordinate data and other graphic attribute data together if necessary, and then generates screen image data to output to the display controller 156.

Haptic feedback module 133 includes various software components for generating instructions for use by haptic output generator 167 to generate haptic output at one or more locations on device 100 in response to user interaction with device 100.

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

The GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to the phone 138 for use in location-based dialing, to the camera 143 as picture/video metadata, and to applications that provide location-based services, such as weather desktops, local page desktops, and map/navigation desktops).

The application 136 optionally includes the following modules (or sets of instructions) or a subset or superset thereof:

contact module 137 (sometimes referred to as an address book or contact list);

a telephone module 138;

video conferencing module 139;

email client module 140;

an Instant Messaging (IM) module 141;

a fitness support module 142;

a camera module 143 for still and/or video images;

an image management module 144;

a video player module;

a music player module;

browser module 147;

Calendar module 148;

a desktop applet module 149, optionally including one or more of: weather desktop applet 149-1, stock market desktop applet 149-2, calculator desktop applet 149-3, alarm desktop applet 149-4, dictionary desktop applet 149-5, and other desktop applets obtained by the user, and user created desktop applet 149-6;

a desktop applet creator module 150 for forming a user-created desktop applet 149-6;

search module 151;

a video and music player module 152 that incorporates the video player module and the music player module;

notepad module 153;

map module 154; and/or

An online video module 155.

Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 is optionally used to manage an address book or contact list (e.g., in application internal state 192 of contacts module 137 stored in memory 102 or memory 370), including: adding one or more names to the address book; deleting names from the address book; associating a telephone number, email address, physical address, or other information with the name; associating the image with the name; classifying and classifying names; providing a telephone number or email address to initiate and/or facilitate communication through telephone 138, video conferencing module 139, email 140, or IM 141; etc.

In conjunction with 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, telephone module 138 is optionally used to input a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contact module 137, modify the entered telephone number, dial the corresponding telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephony module 138, videoconferencing module 139 includes executable instructions to initiate, conduct, and terminate a videoconference between a user and one or more other participants according to user instructions.

In conjunction with 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 includes executable instructions for creating, sending, receiving, and managing emails in response to user instructions. In conjunction with the image management module 144, the email client module 140 makes it very easy to create and send emails with still or video images captured by the camera module 143.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, instant message module 141 includes executable instructions for: inputting a character sequence corresponding to an instant message, modifying previously inputted characters, transmitting a corresponding instant message (e.g., using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for phone-based instant messages or using XMPP, SIMPLE, or IMPS for internet-based instant messages), receiving an instant message, and viewing the received instant message. In some embodiments, the transmitted and/or received instant message optionally includes graphics, photographs, audio files, video files, and/or other attachments supported in an MMS and/or Enhanced Messaging Service (EMS). As used herein, "instant message" refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, workout support module 142 includes executable instructions to create a workout (e.g., with time, distance, and/or calorie burn targets); communicate with a fitness sensor (exercise device); receiving fitness sensor data; calibrating a sensor for monitoring fitness; selecting and playing music for exercise; and displaying, storing and transmitting the fitness data.

In conjunction with touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions for: capturing still images or videos (including video streams) and storing them in the memory 102, modifying features of still images or videos, or deleting still images or videos from the memory 102.

In conjunction with 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 includes executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, tagging, deleting, presenting (e.g., in a digital slide or album), and storing still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions for browsing the internet (including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages) according to user instructions.

In conjunction with 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, calendar module 148 includes executable instructions for creating, displaying, modifying, and storing calendars and data associated with calendars (e.g., calendar entries, to-do items, etc.) according to user instructions.

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, desktop applet module 149 is a mini-application (e.g., weather desktop applet 149-1, stock market desktop applet 149-2, calculator desktop applet 149-3, alarm clock desktop applet 149-4, and dictionary desktop applet 149-5) or a mini-application created by a user (e.g., user created desktop applet 149-6) that is optionally downloaded and used by a user. In some embodiments, the desktop applet includes an HTML (hypertext markup language) file, a CSS (cascading style sheet) file, and a JavaScript file. In some embodiments, the desktop applet includes an XML (extensible markup language) file and a JavaScript file (e.g., yahoo.

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

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

In conjunction with the touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, and browser module 147, the video and music player module 152 includes executable instructions that allow a user to download and playback recorded music and other sound files stored in one or more file formats (such as MP3 or AAC files), as well as executable instructions for displaying, presenting, or otherwise playing back video (e.g., on 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 (trademark of Apple inc.).

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notepad module 153 includes executable instructions to create and manage notepads, backlog, and the like, according to user instructions.

In conjunction with 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, map module 154 is optionally configured to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data related to shops and other points of interest at or near a particular location, and other location-based data) according to user instructions.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, email client module 140, and browser module 147, online video module 155 includes instructions for: allowing a user to access, browse, receive (e.g., by streaming and/or downloading), play back (e.g., on a touch screen or on an external display connected via external port 124), send an email with a link to a particular online video, and otherwise manage online video 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 instead of the email client module 140. Other descriptions of online video applications may be found in U.S. provisional patent application 60/936,562, entitled "Portable Multifunction Device, method, and Graphical User Interface for Playing Online Videos," filed on even date 20 at 6, 2007, and U.S. patent application 11/968,067, entitled "Portable Multifunction Device, method, and Graphical User Interface for Playing Online Videos," filed on even date 31 at 12, 2007, the contents of both of which are hereby incorporated by reference in their entirety.

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

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

A predefined set of functions performed solely by the touch screen and/or the touch pad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates the device 100 from any user interface displayed on the device 100 to a main menu, home menu, or root menu. In such implementations, a touch pad is used to implement a "menu button". In some other embodiments, the menu buttons are physical push buttons or other physical input control devices, rather than touch pads.

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

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

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

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

In some embodiments, event monitor 171 sends requests to peripheral interface 118 at predetermined intervals. In response, the peripheral interface 118 transmits event information. In other embodiments, the peripheral interface 118 transmits event information only if there is a significant event (e.g., an input above a predetermined noise threshold is received and/or an input exceeding a predetermined duration is received).

In some implementations, the event classifier 170 also includes a hit view determination module 172 and/or an active event identifier determination module 173.

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

Another aspect of the user interface associated with an application is a set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the respective application) in which the touch is detected optionally corresponds to a level of programming within the application's programming or view hierarchy. For example, the lowest horizontal view in which a touch is detected is optionally referred to as a hit view, and the set of events identified as being correctly entered is optionally determined based at least in part on the hit view of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related to sub-events of the 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 sub-events. In most cases, the hit view is the lowest level view in which the initiating sub-event (e.g., the first sub-event in a sequence of sub-events that form an event or potential event) occurs. Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as a hit view.

The activity event recognizer determination module 173 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some implementations, the active event identifier determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, the activity event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively engaged views, and thus determines that all actively engaged views should receive a particular sequence of sub-events. In other embodiments, even if the touch sub-event is completely localized to an area associated with one particular view, the higher view in the hierarchy will remain the actively engaged view.

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

In some embodiments, the operating system 126 includes an event classifier 170. Alternatively, the application 136-1 includes an event classifier 170. In yet another embodiment, the event classifier 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 a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for processing touch events that occur within a respective view of the user interface of the application. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, the respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of the event recognizers 180 are part of a separate module that is a higher level object, such as a user interface toolkit (not shown) or application 136-1, from which to inherit methods and other properties. In some implementations, the respective event handlers 190 include one or more of the following: 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 invokes data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of application views 191 include one or more corresponding event handlers 190. Additionally, in some implementations, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in a respective application view 191.

The corresponding event identifier 180 receives event information (e.g., event data 179) from the event classifier 170 and identifies events from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 further includes at least a subset of metadata 183 and event transfer instructions 188 (which optionally include sub-event delivery instructions).

The event receiver 182 receives event information from the event sorter 170. The event information includes information about sub-events such as touches or touch movements. The event information also includes additional information, such as the location of the sub-event, according to the sub-event. When a sub-event relates to movement of a touch, the event information optionally also includes the rate and direction of the sub-event. In some embodiments, the event includes rotation of the device from one orientation to another orientation (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about a current orientation of the device (also referred to as a device pose).

The event comparator 184 compares the event information with predefined event or sub-event definitions and determines an event or sub-event or determines or updates the state of the event or sub-event based on the comparison. In some embodiments, event comparator 184 includes event definition 186. Event definition 186 includes definitions of events (e.g., a predefined sequence of sub-events), such as event 1 (187-1), event 2 (187-2), and other events. In some implementations, sub-events in the event (187) include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, the definition of event 1 (187-1) is a double click on the displayed object. For example, the double click includes a first touch (touch start) for a predetermined period of time on the displayed object, a first lift-off (touch end) for a predetermined period of time, a second touch (touch start) for a predetermined period of time on the displayed object, and a second lift-off (touch end) for a predetermined period of time. In another example, the definition of event 2 (187-2) is a drag on the displayed object. For example, dragging includes touching (or contacting) on the displayed object for a predetermined period of time, movement of the touch on the touch-sensitive display 112, and lift-off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

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

In some implementations, the definition of the respective event (187) further includes a delay action that delays delivery of the event information until it has been determined that the sequence of sub-events does or does not correspond to an event type of the event recognizer.

When 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 impossible, event failed, or event end state after which subsequent sub-events of the touch-based gesture are ignored. In this case, the 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, the respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to the actively engaged event recognizer. In some embodiments, metadata 183 includes configurable attributes, flags, and/or lists that indicate how event recognizers interact or are able to interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to different levels in a view or programmatic hierarchy.

In some embodiments, when one or more particular sub-events of an event are identified, the corresponding event recognizer 180 activates an event handler 190 associated with the event. In some implementations, the respective event identifier 180 delivers event information associated with the event to the event handler 190. The activate event handler 190 is different from sending (and deferring) sub-events to the corresponding hit view. In some embodiments, event recognizer 180 throws a marker associated with the recognized event, and event handler 190 associated with the marker obtains the marker and performs a predefined process.

In some implementations, the event delivery instructions 188 include sub-event delivery instructions that deliver event information about the sub-event without activating the event handler. Instead, the sub-event delivery instructions deliver the event information to an event handler associated with the sub-event sequence or to an actively engaged view. Event handlers associated with the sequence of sub-events or with the actively engaged views receive the event information and perform a predetermined process.

In some embodiments, the data updater 176 creates and updates data used in the application 136-1. For example, the data updater 176 updates a telephone number used in the contact module 137 or stores a video file used in the video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, the object updater 177 creates a new user interface object or updates the location of the user interface object. GUI updater 178 updates the GUI. For example, the GUI updater 178 prepares the display information and sends the display information to the graphics module 132 for display on a touch-sensitive display.

In some embodiments, event handler 190 includes or has access to data updater 176, object updater 177, and 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 appreciated that the above discussion regarding event handling of user touches on a touch sensitive display also applies to other forms of user inputs that utilize an input device to operate the multifunction device 100, not all of which are initiated on a touch screen. For example, mouse movements and mouse button presses optionally in conjunction with single or multiple keyboard presses or holds; contact movement on the touch pad, such as flicking, dragging, scrolling, etc.; stylus input; movement of the device; verbal instructions; detected eye movement; inputting biological characteristics; and/or any combination thereof is optionally used as input corresponding to sub-events defining the event to be identified.

Fig. 2 illustrates a portable multifunction device 100 with a touch screen 112 in accordance with some embodiments. The touch screen optionally displays one or more graphics within a User Interface (UI) 200. In this and other embodiments described below, a user can select one or more of these graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figures) or one or more styluses 203 (not drawn to scale in the figures). In some embodiments, selection of one or more graphics will occur when a user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, up and/or down), and/or scrolling of a finger that has been in contact with the device 100 (right to left, left to right, up and/or down). In some implementations or in some cases, inadvertent contact with the graphic does not select the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that swipes over an application icon optionally does not select the corresponding application.

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

In some embodiments, the device 100 includes a touch screen 112, menu buttons 204, a press button 206 for powering the device on/off and for locking the device, one or more volume adjustment buttons 208, a Subscriber Identity Module (SIM) card slot 210, a headset jack 212, and a docking/charging external port 124. Pressing button 206 is optionally used to turn on/off the device by pressing the button and holding the button in the pressed state for a predefined time interval; locking the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or unlock the device or initiate an unlocking process. In an alternative embodiment, the device 100 also accepts voice input through the microphone 113 for activating or deactivating certain functions. The device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of contacts on the touch screen 112, and/or one or more haptic output generators 167 for generating haptic outputs for a user of the device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. The device 300 need not be portable. In some embodiments, the device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child learning toy), a gaming system, or a control device (e.g., a home controller or an industrial controller). The device 300 generally includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. Communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects and controls communications between system components. The device 300 includes an input/output (I/O) interface 330 with a display 340, typically a touch screen display. The I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 (e.g., similar to the tactile output generator 167 described above with reference to fig. 1A), sensors 359 (e.g., optical sensors, acceleration sensors, proximity sensors, touch sensitive sensors, and/or contact intensity sensors (similar to the contact intensity sensor 165 described above with reference to fig. 1A)) for generating tactile outputs on the device 300. 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 310. In some embodiments, memory 370 stores programs, modules, and data structures, or a subset thereof, similar to those stored in memory 102 of portable multifunction device 100 (fig. 1A). Furthermore, 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 editing 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 above elements in fig. 3 is optionally stored in one or more of the previously mentioned memory devices. Each of the above-described modules corresponds to a set of instructions for performing the above-described functions. The above-described modules or programs (e.g., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the modules and data structures described above. Further, memory 370 optionally stores additional modules and data structures not described above.

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

Fig. 4A illustrates an exemplary user interface of an application menu on the portable multifunction device 100 in accordance with some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, the user interface 400 includes the following elements, or a subset or superset thereof:

one or more signal strength indicators 402 for one or more wireless communications, such as cellular signals and Wi-Fi signals;

Time 404;

bluetooth indicator 405;

battery status indicator 406;

tray 408 with icons of common applications such as:

an icon 416 labeled "phone" of phone module 138, the icon 416 optionally including an indicator 414 of the number of missed calls or voice messages;

an icon 418 of the email client module 140 marked "mail", the icon 418 optionally including an indicator 410 of the number of unread emails;

icon 420 of browser module 147 marked "browser"; and

icon 422 labeled "iPod" of video and music player module 152 (also referred to as iPod (trademark of Apple inc. Module 152); and

icons of other applications, such as:

icon 424 marked "message" for IM module 141;

icon 426 of calendar module 148 marked "calendar";

icon 428 marked "photo" of image management module 144;

icon 430 marked "camera" for camera module 143;

icon 432 of online video module 155 marked "online video";

icon 434 labeled "stock market" for stock market desktop applet 149-2;

Icon 436 marked "map" of map module 154;

icon 438 marked "weather" for weather desktop applet 149-1;

icon 440 marked "clock" for alarm desktop applet 149-4;

icon 442 labeled "fitness support" for fitness support module 142;

icon 444 labeled "notepad" for notepad module 153; and

the "set" icon 446 of a set application or module provides access to settings of the device 100 and its various applications 136.

It should be noted that the iconic labels shown in fig. 4A are merely exemplary. For example, the icon 422 of the video and music player module 152 is labeled "music" or "music player". Other labels are optionally used for various application icons. In some embodiments, the label of the respective application icon includes a name of the application corresponding to the respective application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.

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

While some of the examples below will be given with reference to inputs on touch screen display 112 (where the touch sensitive surface and the display are combined), in some embodiments the device detects inputs on a touch sensitive surface separate from the display, as shown in fig. 4B. In some implementations, the touch-sensitive surface (e.g., 451 in fig. 4B) has a primary axis (e.g., 452 in fig. 4B) that corresponds to the primary axis (e.g., 453 in fig. 4B) on the display (e.g., 450). According to these embodiments, the device detects contact (e.g., 460 and 462 in fig. 4B) with the touch-sensitive surface 451 at a location corresponding to a respective location on the display (e.g., 460 corresponds to 468 and 462 corresponds to 470 in fig. 4B). Thus, when the touch-sensitive surface (e.g., 451 in FIG. 4B) is separated from the display (450 in FIG. 4B) of the multifunction device, user inputs (e.g., contacts 460 and 462 and movement thereof) detected by the device on the touch-sensitive surface are used by the device to manipulate the user interface on the display. It should be appreciated that similar approaches are optionally used for other user interfaces described herein.

Additionally, while the following examples are primarily given with reference to finger inputs (e.g., finger contacts, single-finger flick gestures, finger swipe gestures), it should be understood that in some embodiments one or more of these finger inputs are replaced by 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., rather than a contact), followed by movement of the cursor along the path of the swipe (e.g., rather than movement of the contact). As another example, a flick gesture is optionally replaced by a mouse click (e.g., instead of detection of contact, followed by ceasing to detect contact) when the cursor is over the position of the flick gesture. Similarly, when multiple user inputs are detected simultaneously, it should be appreciated that multiple computer mice are optionally used simultaneously, or that the mice and finger contacts are optionally used simultaneously.

Fig. 5A illustrates an exemplary personal electronic device 500. The device 500 includes a body 502. In some embodiments, device 500 may include some or all of the features described with respect to devices 100 and 300 (e.g., fig. 1A-4B). In some implementations, the device 500 has a touch sensitive display 504, hereinafter referred to as a touch screen 504. In addition to or in lieu of touch screen 504, device 500 has a display and a touch-sensitive surface. As with devices 100 and 300, in some implementations, touch screen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors for detecting the intensity of an applied contact (e.g., touch). One or more intensity sensors of the touch screen 504 (or touch sensitive surface) may provide output data representative of the intensity of the touch. The user interface of the device 500 may respond to touches based on the intensity of the touches, meaning that touches of different intensities may invoke different user interface operations on the device 500.

Exemplary techniques for detecting and processing touch intensity are found, for example, in the following related patent applications: international patent application serial number PCT/US2013/040061, filed 5/8 a 2013, entitled "Device, method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application", issued as WIPO patent publication No. WO/2013/169849; and international patent application serial number PCT/US2013/069483, filed 11/2013, entitled "Device, method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships", published as WIPO patent publication No. WO/2014/105276, each of which is hereby incorporated by reference in its entirety.

In some embodiments, the device 500 has one or more input mechanisms 506 and 508. The input mechanisms 506 and 508 (if included) may be in physical form. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, the device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, may allow for attachment of the device 500 with, for example, a hat, glasses, earrings, necklace, shirt, jacket, bracelet, watchband, bracelet, pants, leash, shoe, purse, backpack, or the like. These attachment mechanisms allow the user to wear the device 500.

Fig. 5B illustrates an exemplary personal electronic device 500. In some embodiments, the apparatus 500 may include some or all of the components described with reference to fig. 1A, 1B, and 3. The device 500 has a bus 512 that operatively couples an I/O section 514 with one or more computer processors 516 and memory 518. The I/O portion 514 may be connected to a display 504, which may have a touch sensitive component 522 and optionally an intensity sensor 524 (e.g., a contact intensity sensor). In addition, the I/O portion 514 may be connected 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 may include input mechanisms 506 and/or 508. For example, the input mechanism 506 is optionally a rotatable input device or a depressible input device and a rotatable input device. In some examples, the input mechanism 508 is optionally a button.

In some examples, the input mechanism 508 is optionally a microphone. Personal electronic device 500 optionally includes various sensors, such as a GPS sensor 532, an accelerometer 534, an orientation sensor 540 (e.g., compass), a gyroscope 536, a motion sensor 538, and/or combinations thereof, all of which are operatively connected to 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 the one or more computer processors 516, may, for example, cause the computer processors to perform the techniques described below, including processes 700, 900, 1100, and 1300 (fig. 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, and device. In some examples, the storage medium is a transitory computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. The non-transitory computer readable storage medium may include, but is not limited to, magnetic storage devices, optical storage devices, and/or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or blu-ray technology, and persistent solid state memories such as flash memory, solid state drives, etc. The personal electronic device 500 is not limited to the components and configuration of fig. 5B, but may include other components or additional components in a variety of 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 (fig. 1A, 3, and 5A-5B). For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) optionally each constitute an affordance.

As used herein, the term "focus selector" refers to an input element for indicating the current portion of a user interface with which a user is interacting. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when the cursor detects an input (e.g., presses an input) on a touch-sensitive surface (e.g., touch pad 355 in fig. 3 or touch-sensitive surface 451 in fig. 4B) above a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations including a touch screen display (e.g., touch sensitive display system 112 in fig. 1A or touch screen 112 in fig. 4A) that enables direct interaction with user interface elements on the touch screen display, the contact detected on the touch screen acts as a "focus selector" such that when an input (e.g., a press input by a contact) is detected on the touch screen display at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations, the focus is moved from one area of the user interface to another area of the user interface without a corresponding movement of the cursor or movement of contact on the touch screen display (e.g., by moving the focus from one button to another using a tab key or arrow key); in these implementations, the focus selector moves in accordance with movement of the focus between different areas of the user interface. Regardless of the particular form that the focus selector takes, the focus selector is typically controlled by the user in order to deliver a user interface element (or contact on the touch screen display) that is interactive with the user of the user interface (e.g., by indicating to the device the element with which the user of the user interface desires to interact). For example, upon detection of a press input on a touch-sensitive surface (e.g., a touchpad or touch screen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a respective button will indicate that the user desires to activate the respective button (rather than other user interface elements shown on the device display).

As used in the specification and claims, the term "characteristic intensity" of a contact refers to the characteristic of a 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 acquired during a predetermined period of time (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after detection of contact, before or after detection of lift-off of contact, before or after detection of start of movement of contact, before or after detection of end of contact, and/or before or after detection of decrease in intensity of contact). The characteristic intensity of the contact is optionally based on one or more of: maximum value of intensity of contact, average value of intensity of contact, value at first 10% of intensity of contact, half maximum value of intensity of contact, 90% maximum value of intensity of contact, etc. In some embodiments, the duration of the contact is used in determining 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 the user has performed an operation. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, contact of the feature strength that does not exceed the first threshold results in a first operation, contact of the feature strength that exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and contact of the feature strength that exceeds the second threshold results in a third operation. In some implementations, a comparison between the feature strength and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform or forgo performing the respective operations) rather than for determining whether to perform the first or second operations.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E on the touch-sensitive display screen 504 using a plurality of intensity sensors 524A-524D. FIG. 5C also includes an intensity graph showing the current intensity measurements of the intensity sensors 524A-524D relative to 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 cumulative intensity is the sum of the intensity measurements of the plurality of intensity sensors 524A-524D, which in this example is 32 intensity units. In some embodiments, each contact is assigned a corresponding intensity, i.e., a portion of the cumulative intensity. FIG. 5D illustrates the assignment of cumulative intensities to contacts 552A-552E based on their distance from the center of force 554. In this example, each of the contacts 552A, 552B, and 552E is assigned an intensity of the contact of 8 intensity units of cumulative intensity, and each of the contacts 552C and 552D is assigned an intensity of the contact of 4 intensity units of cumulative intensity. More generally, in some implementations, each contact j is assigned a respective intensity Ij according to a predefined mathematical function ij=a· (Dj/Σdi), which is a fraction of the cumulative intensity a, where Dj is the distance of the respective contact j from the force center, and Σdi is the sum of the distances of all the respective contacts (e.g., i=1 to last) from the force center. The operations described with reference to fig. 5C-5D may be performed using an electronic device similar or identical to device 100, 300, or 500. In some embodiments, the characteristic intensity of the contact is based on one or more intensities of the contact. In some embodiments, an intensity sensor is used to determine a single characteristic intensity (e.g., a single characteristic intensity of a single contact). It should be noted that the intensity map is not part of the displayed user interface, but is included in fig. 5C-5D to aid the reader.

In some implementations, a portion of the gesture is identified for determining a feature strength. For example, the touch-sensitive surface optionally receives a continuous swipe contact that transitions from a starting position and to an ending position where the contact intensity increases. In this example, the characteristic intensity of the contact at the end position is optionally based on only a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., only the portion of the swipe contact at the end position). 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 the following: an unweighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow spikes or depressions in the intensity of the swipe contact for the purpose of determining the characteristic intensity.

The intensity of the contact on the touch-sensitive surface is optionally characterized relative to one or more intensity thresholds, such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the tap strength threshold corresponds to a strength of: at this intensity the device will perform the operations normally associated with clicking a button of a physical mouse or touch pad. In some embodiments, the deep compression intensity threshold corresponds to an intensity of: at this intensity the device will perform an operation that is different from the operation normally associated with clicking a physical mouse or a button of a touch pad. In some implementations, when a contact is detected with a characteristic intensity below a light press intensity threshold (e.g., and above a nominal contact detection intensity threshold, a contact below the nominal contact detection intensity threshold is no longer detected), the device will move the focus selector according to movement of the contact over the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent across different sets of user interface drawings.

The increase in contact characteristic intensity from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a "light press" input. The increase in contact characteristic intensity from an intensity below the deep-press intensity threshold to an intensity above the deep-press intensity threshold is sometimes referred to as a "deep-press" input. The increase in the contact characteristic intensity from an intensity below the contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting a contact on the touch surface. The decrease in the contact characteristic intensity from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting a lift-off of 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 implementations described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting a respective press input performed with a respective contact (or contacts), wherein a respective press input is detected based at least in part on detecting an increase in intensity of the contact (or contacts) above a press input intensity threshold. In some implementations, the respective operation is performed in response to detecting that the intensity of the respective contact increases above a press input intensity threshold (e.g., a "downstroke" of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above a press input intensity threshold and a subsequent decrease in intensity of the contact below the press input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press input threshold (e.g., an "upstroke" of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a change in intensity from contact 562 below the tap intensity threshold in FIG. 5E (e.g., "IT _L ") increases in intensity above the deep compression intensity threshold in fig. 5H (e.g.," IT) _D ") intensity corresponds to the press input. On the displayed user interface 570 including application icons 572A-572D displayed in predefined area 574, a gesture performed with contact 562 is detected on touch-sensitive surface 560 while cursor 576 is displayed over application icon 572B corresponding to application 2. In some implementations, a gesture is detected on the touch-sensitive display 504. The intensity sensor detects the intensity of the contact on the touch-sensitive surface 560. The device determines contact 56The intensity of 2 is below the deep compression intensity threshold (e.g., "IT _D ") reaches a peak above. Contact 562 is maintained on touch-sensitive surface 560. In response to detecting the gesture, and in accordance with the intensity rising to a deep press intensity threshold (e.g., "IT" during the gesture _D ") the above contact 562 displays reduced-scale representations 578A-578C (e.g., thumbnails) of the recently opened document for application 2, as shown in fig. 5F-5H. In some embodiments, the intensity is a characteristic intensity of the contact compared to one or more intensity thresholds. It should be noted that the intensity map for contact 562 is not part of the displayed user interface, but is included in fig. 5E-5H to aid the reader.

In some embodiments, the display of representations 578A-578C includes animation. For example, representation 578A is initially displayed adjacent to application icon 572B, as shown in FIG. 5F. As the animation proceeds, the representation 578A moves upward and the representation 578B is displayed near the application icon 572B, as shown in fig. 5G. Representation 578A then moves upward, 578B moves upward toward representation 578A, and representation 578C is displayed adjacent to application icon 572B, as shown in fig. 5H. Representations 578A-578C form an array over icon 572B. In some embodiments, the animation progresses according to the intensity of the contact 562, as shown in fig. 5F-5G, where representations 578A-578C appear and move upward as the intensity of the contact 562 increases toward a deep press intensity threshold (e.g., "ITD"). In some embodiments, the intensity upon which the animation progresses is based is the characteristic intensity of the contact. The operations described with reference to fig. 5E-5H may be performed using an electronic device similar or identical to device 100, 300, or 500.

In some implementations, the device employs intensity hysteresis to avoid accidental inputs, sometimes referred to as "jitter," in which the device defines or selects a hysteresis intensity threshold that has a predefined relationship to the compression input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the compression input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the compression input intensity threshold). Thus, in some embodiments, the press input includes an increase in the intensity of the respective contact above a press input intensity threshold and a subsequent decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the press input intensity threshold, and the respective operation is performed in response to detecting that the intensity of the respective contact subsequently decreases below the hysteresis intensity threshold (e.g., an "upstroke" of the respective press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in contact intensity from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press input intensity threshold and optionally a subsequent decrease in contact intensity to an intensity at or below the hysteresis intensity, and a corresponding operation is performed in response to detecting a press input (e.g., an increase in contact intensity or a decrease in contact intensity depending on the circumstances).

For ease of explanation, optionally, a description of operations performed in response to a press input associated with a press input intensity threshold or in response to a gesture comprising a press input is triggered in response to detecting any of the following: the contact strength increases above the compression input strength threshold, the contact strength increases from an intensity below the hysteresis strength threshold to an intensity above the compression input strength threshold, the contact strength decreases below the compression input strength threshold, and/or the contact strength decreases below the hysteresis strength threshold corresponding to the compression input strength threshold. In addition, in examples where the operation is described as being performed in response to the intensity of the detected contact decreasing below a press input intensity threshold, the operation is optionally performed in response to the intensity of the detected contact decreasing below a hysteresis intensity threshold that corresponds to and is less than the press input intensity threshold.

As used herein, an "installed application" refers to a software application that has been downloaded onto an electronic device (e.g., device 100, 300, and/or 500) and is ready to be started (e.g., turned on) on the device. In some embodiments, the downloaded application becomes an installed application using an installer, the installed application extracts program portions from the downloaded software package and integrates the extracted portions with the operating system of the computer system.

As used herein, the term "open application" or "executing application" refers to a software application having retention state information (e.g., as part of device/global internal state 157 and/or application internal state 192). The open or executing application is optionally any of the following types of applications:

an active application currently displayed on the display screen of the device that is using the application;

a background application (or background process) that is not currently shown but for which one or more processes are being processed by one or more processors; and

a suspended or dormant application that is not running but has state information stored in memory (volatile and nonvolatile, respectively) and available to resume execution of the application.

As used herein, the term "closed application" refers to a software application that does not have maintained state information (e.g., the state information of the closed application is not stored in the memory of the device). Thus, closing an application includes stopping and/or removing application processes of the application and removing state information of the application from memory of the device. Generally, when in a first application, opening a second application does not close the first application. The first application becomes a background application when the second application is displayed and the first application stops being displayed.

Attention is now directed to embodiments of a user interface ("UI") and associated processes implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.

User interface and associated process

Using a measurement control panel user interface

The user interacts with the electronic device in a number of different ways, including viewing information about the electronic device and/or the use of the electronic device. In some embodiments, the electronic device displays a visual indication of one or more metrics associated with operation at the electronic device, thereby allowing a user to view information about the use of the electronic device. The embodiments described below provide a way for an electronic device to present an indication of usage metrics associated with performing one or more operations using the electronic device. Enhancing interaction with the device reduces the amount of time required for the user to perform an operation, thereby reducing the power consumption of the device and extending the battery life of the battery-powered device. It will be appreciated that people use the device. When a person uses a device, the person is optionally referred to as a user of the device.

Fig. 6A-6 AU illustrate an exemplary manner in which an electronic device presents usage metric indications 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 fig. 7A-7S.

Fig. 6A shows an exemplary device 500 having a touch screen 504, such as described with reference to fig. 5A-5H. Touch screen 504 optionally displays one or more user interfaces including various content. In the example shown in fig. 6A, the touch screen 504 displays a limit setting user interface for viewing information about the use of the electronic device 500 and setting limits of the use of the electronic device 500. In fig. 6A, the limit settings user interface displays an indication 602 of device usage and a plurality of settings related to device usage, such as a setting of a limited usage mode (e.g., "device downtime" 604 a), a setting of a usage limit for one or more applications or application categories (e.g., "application limit" 604 b), a setting of which functions are always allowed regardless of any usage limit currently implemented (e.g., "always allowed" 604 c), a setting of content and privacy of the electronic device 500 (e.g., "content and privacy" 604 d), a setting of changing the usage settings requiring a password (e.g., "make change requiring password" 604 e), a setting of stopping recording which operations are being performed at the electronic device (e.g., "stop recording usage data" 604 f), a setting of deleting stored data related to performing various operations using the electronic device (e.g., "delete usage data" 604 g), and a setting of logging into a cloud-based user account (e.g., "log into the iCloud"604 h). As shown, the indication 602 of device usage includes a visual indication of the amount of time that the electronic device has been used to access each of several applications or application categories (e.g., news applications, game categories, and mail applications). The indication 602 also includes an indication of how much remains (e.g., "3 hours remain") about the total "screen time" usage limit. The usage limits, including the overall usage limits, are described in more detail below with reference to fig. 8A-9K. The electronic device 500 also displays an indication of overall device usage (e.g., "4 hours of use"), and a comparison of the device usage to average daily usage on the same day (e.g., "30 minutes below average level").

Fig. 6B illustrates a limit setting user interface when the electronic device 500 is logged into a cloud-based user account. The limit settings 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 the group or family cloud-based account (e.g., iPhone 608a and iPhone 608b of John jr.). The family cloud-based account includes a plurality of individual user accounts (e.g., "iPhone of John jr. And" iPhone of Jane ") associated with other electronic devices. In some embodiments, the family cloud-based account includes a "parent" user and a "child" user, and enables the parent user to view and/or control various statistics and/or settings associated with the child device. As shown herein and described in more detail below with reference to fig. 6V-6W, a parent device (e.g., such as electronic device 500) is capable of presenting usage information regarding one or more child devices. The parent device is also able to control the usage limits of the child device and the device downtime settings, as described below with reference to fig. 8A-11I. In fig. 6C-6D, the user scrolls (e.g., with contact 603) the limit settings user interface to reveal indications of a plurality of other electronic devices associated with the cloud-based user account (e.g., john's iPad610a, 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 fig. 6 AT-6 AU, the electronic device 500 is capable of displaying usage metrics associated with one or more associated devices, either alone or together.

FIG. 6E shows a desktop applet user interface that includes the use of a desktop applet 612a, a calendar desktop applet 612b, and a weather desktop applet 612 c. The usage applet 612a includes an indication 602 of device usage, including an indication of usage of various applications and categories (e.g., news applications, mail applications, and game categories) and an affordance 614 that is selectable to display more usage information.

Fig. 6F shows a user selecting an affordance 614 (e.g., with contact 603). In response to selecting affordance 614, a desktop applet 612a is used to expand to display additional information, as shown in FIG. 6G. The expanded use desktop applet 612a includes an indication 616 of the total device usage of the day, an indication of how much the device usage of the day deviates from the balance average device usage 618, a graphic 620 indicating the device usage of an application or application class over time, and an indication of the usage limits set on the electronic device (e.g., news application limits 622a and game class limits 622 b). The graphic 620 includes bars each hour of the day indicating device usage during that hour with a color coded portion for indicating which application (e.g., news application or mail application) or application category (e.g., game category) is used each hour. As shown in fig. 6G, the indication of the usage limit that has been exceeded (e.g., news application usage limit 622 a) includes an indication of how much of the application (e.g., news application) has been used beyond the usage limit. Also, the indication of the usage limit (e.g., game category 622 b) that has not been reached includes an indication of a difference between the usage of the application category (e.g., game category) and the usage limit. Fig. 6H-6I illustrate the use of a desktop applet rolled out by a user (e.g., with contact 603) to reveal additional information, including representations 624a-624e of application usage for the day, an indication 626 of the average number of notifications received for each of the last days, and an indication 628 of how often the user initiated "pick up" the device over the last day or days. As shown, the indications for the applications 624a-624e are application icons for those applications that are presented in different sizes indicating the relative usage of the respective applications. For example, news application indication 624a is the largest, indicating that the application has been used the most. Also, depending on the amount of usage of these applications, mail application indication 624b and game a application indication 624c are smaller than news application indication 624 a.

Fig. 6J illustrates a usage notification 630 generated by the device 500 according to some examples of the present disclosure. In some embodiments, a use notification, such as notification 630, is generated by electronic device 500 at regularly scheduled intervals (e.g., once daily, once weekly, etc.). The usage notification includes an indication 602 of device usage, an option to view more information about device usage (e.g., in a dashboard user interface) (e.g., "view" 632 a), and an option to dismiss the notification without viewing more information about device usage (e.g., "dismiss" 632 b). In fig. 6K, the user selects "view" 632a (e.g., with contact 603) to view more information about the use of the device. In response, the electronic device 500 presents a use dashboard user interface, as shown in fig. 6L.

The usage control panel user interface includes the illustration 620 described above with reference to fig. 6G indicating device usage of an application or class of applications over time, the indication 634 of the longest usage session on the device during the day, the indication 636 of the amount of device usage during the limited use mode (e.g., "device downtime") during the day, and the indications 622a and 622b of usage of the application and class for which the usage limit is set. The usage dashboard user interface also includes a toggle key for viewing an indication of usage metrics for either the day 638a or the week 638 b. As shown in fig. 6L, the usage metrics for the current day are currently displayed using the dashboard user interface. Indications 622a and 622b of the use of an application having a use limit are optionally visually associated with affordances 640a and 640b, the affordances 640a and 640b being selectable to display a settings user interface for viewing information about the respective application or category and updating the use limit settings for the application or category. For example, affordance 640a may be selected to edit the usage limit settings of a news application. When the usage limit has been exceeded (e.g., news application usage limit 622 a), as shown in fig. 6L, the corresponding affordance 640a has another color or pattern that indicates that the usage limit has been exceeded. Also, in some embodiments, when the usage limit approach is reached (e.g., within a threshold amount or percentage of time), the associated affordance has visual characteristics. In addition, the bar graph indicating the usage limit includes different colored portions corresponding to the amount of time that the electronic device is used to access a given application or category within the usage limit (e.g., as shown in both the news application indication 622a and the game category indication 622 b), the amount of time that the given application or category is used beyond the usage limit (e.g., as shown in the news application indication 622 a), and the amount of time remaining in the usage limit of the application or category (e.g., as shown in the game category 622b indication).

Fig. 6M-6N illustrate a user scrolling (e.g., with contact 603) through the usage control panel user interface to reveal additional usage metric indications, as shown in fig. 6O. As shown, the usage control panel user interface includes an indication 642 of the amount of usage of an application (e.g., mail) for which a usage limit has not been set, and an affordance 640c of the setup user interface that is selectable to display information about the corresponding application and update the usage limit settings for the application.

Fig. 6P-6Q illustrate a user scrolling through the usage control panel user interface (e.g., with contact 603) to reveal additional usage metric indications, as shown in fig. 6R. FIG. 6R shows an indication 650a-650d of how many notifications were generated using the dashboard user interface, including a graphical representation 644 of notifications received throughout the day, an indication 646 of the number of notifications received during the day, an indication 648 of the hours that received the most notifications, and a plurality of applications installed on the electronic device (e.g., all applications generating notifications for the day, or a set number of applications generating notifications for the top of the day). The illustration 644 includes a plurality of bars indicating how much notification the electronic device presents during each hour of the day. The user interface also includes a plurality of affordances 652a-652d visually associated with the indications 650a-650d that represent notification settings of respective applications that are selectable to display indications for which notifications are displayed. For example, the affordance 652a can select to edit notification settings of an iMessage application. The indications 650a-650d of notifications include the names of the applications (e.g., "iMessage application," "email application," "news application," and "Water tracker application"), the number of notifications that the respective application generated throughout the day, and the points positioned to indicate the relative number of notifications that the application generated with respect to other applications.

Fig. 6S-6T illustrate a user scrolling (e.g., with contact 603) through the usage control panel user interface to reveal additional usage metric indications, as shown in fig. 6U.

Fig. 6U shows the use of the dashboard user interface, including an indication 654 of the "pick up" device for the day (described in more detail below), an indication 656 of the average time between picking up devices for the day, a graphical representation 658 of the pick up devices for the entire day, an indication 660 of the number of times the device was picked up during the device downtime (described in more detail below with reference to fig. 10A-11I), an indication 662 of the number of hours the device was picked up the most during the day and the number of times it was picked up during the time interval, and an indication 664a and 664b of the number of times the user has picked up the electronic device to interact with each of the plurality of applications.

The average time between picking up the device the day, indicated by indication 656, is calculated as the average time between the first pick up the day and the last pick up the day. In some embodiments, the average includes a pick-up between a first pick-up outside of the equipment downtime and a last pick-up outside of the equipment downtime. In some embodiments, the average includes picks between all picks of the day, whether or not one or more of those picks occur during equipment downtime.

The illustration 658 of picking up the device throughout the day includes bars for each hour of the day indicating the number of times the device was picked up per hour. As shown in fig. 6U, the illustration visually distinguishes a pick-up that occurs during the equipment downtime from a pick-up that occurs outside of the equipment downtime, and also indicates this distinction with the equipment downtime markers 698-22.

The applications 664a-b with which the user picks up the electronic device to interact are determined based on the first application with which the user interacted when picking up the device. For example, if a user wakes up the device, immediately after waking up, the first application presented at the electronic device is closed, and then the second application is opened to perform operations with the second application, the second application is an application with which the user picks up the electronic device to interact. As another example, if the device presents a notification associated with the first device while in the sleep mode and the user provides input to view the notification and interact with the first application, the first application is an application with which the user picks up the electronic device to interact.

As used herein, a "pick up" device encompasses multiple types of user attention events, such as a user unlocking an electronic device, waking up the device, and other operations that initiate operations of the electronic device. In some embodiments, the user attention event is detected when the user input causes the electronic device to exit an idle state (e.g., sleep mode, locked state, low power mode, etc., during which the user does not interact with the electronic device and/or the display of the electronic device is turned 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 (e.g., pressing a power or lock button of the electronic device) corresponding to a request to enter the idle state. In some implementations, the display does not display images during the idle state. In some embodiments, the 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: buttons of the electronic device are pressed, user actions for terminating an idle state (e.g., raising the device), unlocking inputs (e.g., entering a password or providing biometric features), and touch inputs for accessing functions of the electronic device (e.g., a desktop applet user interface, a camera application, a dashboard user interface, a user interface displaying an application associated with a displayed notification indication). Detecting biometric features optionally includes detecting a face of the user with a depth camera or another sensor. In some implementations, the electronic device can use depth camera and facial recognition techniques to determine when a user is looking at their electronic device and unlock in response to the user looking at the electronic device (e.g., the electronic device unlock in response to determining that the user is focusing on the electronic device). In some embodiments, the electronic device exits the idle state in response to the notification (e.g., the display opens to display the notification without user input requesting the display to open), and the event of interest causes the device to perform some other action (e.g., unlock the device, update the display to display a user interface of an application or operating system). That is, the indication of the notification is optionally not an event of interest to the user, even though it causes the device to exit the idle state. In some implementations, the event metrics of interest indicate the number of times a user initiates use of the electronic device (e.g., "check" his phone).

Fig. 6V shows a limit setting user interface. As shown, the limit settings user interface includes an indication 608a of an electronic device associated with a user that is part of a home account associated with the electronic device 500 ("iPhone of John jr). The indication also includes an indication that the iPhone request for John jr is added more time to at least one usage restriction controlled by the electronic device 500. In fig. 6V, the user selects indication 608a (e.g., with contact 603).

In response to a user selection, the electronic device displays a usage control panel user interface associated with the iPhone of John jr, as shown in fig. 6W. The user interface includes an indication 666 of a request to remove an overall use limit implemented on an iPhone of John jr, an indication 680 of an overall screen time use limit of an iPhone of John jr, an indication 670 of a duration of a longest use session of an iPhone of John jr, an indication 672 of an amount of use during device downtime on an iPhone of John jr, an indication 674a-b of use of an application with a use limit on an iPhone of John jr, and an indication 676 of use of an application without a use limit on an iPhone of John jr, similar to that described previously in fig. 6L-6N.

The indication 666 is presented in response to the electronic device 500 receiving a request from the other electronic device (e.g., john jr. IPhone) to increase the amount of time of the use 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 home account that enables electronic device 500 to manage the usage settings of John jr's iPhone. Indication 666 includes a selectable affordance for "reject" request, "give 1 hour" additional time, or "go to setup" to see more options for modifying the restrictions on the iPhone of John jr. Requesting the addition of more time to the usage limit from the child device to the parent device, and more details about the usage limit in general, are described below with reference to fig. 9A-10 AAA.

The usage control panel user interface also includes a plurality of affordances 678a-c, the affordances 678a-c being selectable to view information about an associated application or class of applications and/or to alter usage limits associated with the application or class of applications. As shown in the user interface, the affordance 678a associated with the game a application is shaded to indicate that the use limit of the game a application has been reached. Likewise, affordances 678a associated with social media categories are shaded to indicate that the usage limit proximity of the social media categories is reached. In some embodiments, other visual indications are possible.

Fig. 6X shows a limit setting user interface. In fig. 6Y, the user selects setting 604e (e.g., with contact 603) to require a password (or other authentication such as a password or biometric feature) to change the usage restriction setting on device 500. In response to the selection, the electronic device presents a keypad 682 for receiving user input to set a password. In some embodiments, the electronic device presents a full keyboard or a user interface that allows the user to select a password or password length, or an option for using biometric input (e.g., facial recognition) for authentication to make changes to the usage settings. The authentication required to make changes to one or more usage restriction settings of the electronic device 500 is optionally different from the authentication required to unlock the electronic device 500.

After the user sets the password, the electronic device updates the password switch key 604e to indicate that the password is required in order to make a change to the use restriction setting, as shown in fig. 6 AA. In fig. 6AB, the user selects the indication 604b to alter the usage limit on the electronic device 500. In response to the input, the electronic device presents a keypad 682 to require the above-described password (or other authentication method) before allowing the user to change the settings, as shown in fig. 6 AC.

Fig. 6AD shows an indication 602 of the user's selection of device usage (e.g., with contact 603). In response to the selection, the electronic device 500 presents a usage control panel user interface, as shown in fig. 6 AE. As shown in fig. 6AF, the user then selects the switch key 638b (e.g., with contact 603) to view the usage measure over the course of a week. In response to the input, the electronic device 500 updates the usage control panel user interface to display an indication of the usage metrics over the course of the past week, as shown in FIG. 6 AG.

FIG. 6AG illustrates a usage control panel user interface presenting a plurality of usage metrics over the course of the past week. The usage control panel user interface includes an indication 684 of average device usage per day during the week, an indication 686 of how average daily usage per day during the week compares to average usage over a longer period of time (e.g., the last month or all times), a graphical representation 688 showing daily usage of one or more applications or application categories, an indication 690 of the duration of the longest usage session during the week, an indication 692 of average daily device usage during device downtime, and an indication 694a-694b of average usage per day for one or more applications or application categories for which usage limits are set during the week. Illustration 688 includes bars each day of the week indicating usage of electronic device 500 each day for a plurality of color coded applications and application categories. As shown, the illustration 688 includes an indication of overall device usage limits (e.g., a horizontal line running across the illustration 688) that are optionally different on weekdays (e.g., monday through friday) and weekends (e.g., friday and sunday). For example, as shown in fig. 6AG, the overall device usage limits for monday through friday are optionally lower than the overall device usage limits for wednesday and sunday.

Although not shown in the figures, it should be understood that the dashboard user interface optionally includes indications of any other metrics described herein over the course of the week, with some metrics displayed in aggregate (e.g., as a total, average, etc.) over the week and other metrics displayed as maxima or minima over the week. For example, returning to FIG. 6R, the number of notifications per day 646 is optionally replaced with the average number of notifications per day of the week, while the interval 648 that receives the most notifications within a day is replaced with the interval that receives the most notifications within the week (e.g., a day or an hour of the day). As another example, returning to fig. 6U, the number of times the day 660 the device was picked up during the downtime is optionally replaced by the average number of times the device was picked up during the downtime for each day during the week, while the hour with the most picks 662 on the day is optionally replaced by another interval (e.g., a day or an hour of a day) of the most notifications received during the period.

FIG. 6AH shows the user selecting (e.g., with contact 603) an affordance 640b associated with a game category. In response to the input, the electronic device 500 presents a category setting user interface, as shown in fig. 6 AI. The category setting user interface includes a toggle key 690 for enforcing or not enforcing a usage limit for the application category, an indication 692 of the usage limit for the application category, an option 694a for setting the enforcement limit with notifications and blocking, an option 694b for setting the enforcement limit with notifications, a toggle key 696 for presenting verbal alerts associated with the usage limit, and a plurality of indications 698a-d of usage of each application included in the application category to which the usage limit applies.

The switch key 690 enables the user to stop enforcing category usage limits while preserving parameters of the usage limits, such as amount of time, notification style, and applications included. In this way, the user can re-open the switch key to begin enforcing the usage limit without having to re-enter parameters of the usage limit. Further details of notification and blocking settings 694a and 694b, and use limit settings are described below with reference to fig. 8A-9K. A toggle button 696 for presenting verbal alerts associated with a usage limit enables the electronic device 500 to speak notifications associated with the usage limit, such as a notification indicating that the usage limit is approaching or has been reached.

As shown in FIG. 6AI, the user selects (e.g., with contact 603) an affordance 640a associated with the game A application in the game category to present additional information and settings for that particular application. In response, the electronic device 500 presents a user interface with information about the use of game a and settings for setting the use limit for game a, as shown in fig. 6 AJ.

FIG. 6AJ shows an indication 698-2 of usage of game A, an indication 698-4 of average usage of game A, an indication 698-6 of usage of game A during device downtime of the day, an indication 698-8 of the number of notifications generated by game A during the day, settings 698-10 for updating usage limits for game A, information 698-12 about game A, and a graphical representation 698-14 of usage of game A over time of the day (e.g., displayed as a plurality of bars, each bar representing usage of game A during each hour of the day). As shown, the user can create a usage limit for game a, including the amount of time that the usage limit is set and how the electronic device 500 will behave when the limit is reached (e.g., "notify and block" or "notify"). The use limit is described in more detail with reference to fig. 8A to 9K. The user interface also includes an overview 698-12 of information about game A, such as its application icons, age ratings, categories, developers, and links to view game A in an application store on the electronic device. While the user interface shown in fig. 6AJ is accessible from the category settings user interface shown in fig. 6AH through 6AI, similar user interfaces for each application are accessible from the usage metric control panel user interface (e.g., as shown in fig. 6L through 6O, 6W, and 6AE through 6 AH) when the user selects the settings affordance associated with an individual application (e.g., 640a associated with a news application, 678c associated with a dictionary application, etc.).

FIG. 6AK illustrates a usage control panel user interface presenting usage metrics related to notifications, such as described with reference to FIG. 6R. In fig. 6AL, the user selects (e.g., with contact 603) an affordance 652c associated with the news application notification setting. In response, the electronic device 500 presents a notification settings user interface of the news application, as shown in fig. 6 AM. The notification settings user interface includes toggle keys 698-16 for allowing notifications from news applications, toggle keys 698-18 for presenting notifications to news applications in silence mode, and options 698-20 for altering the indication of which notification the news application presents. Switching "allow notification" switch keys 698-16 off causes the application to not present the notification anywhere on electronic device 500, rather, when the notification is "on," one or more indications of the notification are presented when the notification is received at the electronic device (e.g., visual indications such as text or images, audio indications such as audible or spoken words, and/or haptic or other tactile feedback, etc.). Toggling "silent notification" toggle 698-18 on causes electronic device 500 to forgo presenting an indication of the notification when the notification is received (e.g., because the electronic device does so when the notification is allowed), but unlike the behavior of the device when the notification is not allowed, presenting an indication of the notification in a notification history user interface, including an indication of a plurality of notifications received at the electronic device, as described below with reference to FIG. 12I. Altering the "notification enabled" settings 698-20 causes the electronic device 500 to present all notifications, a limited number of notifications, or only high-importance notifications received at the application.

Fig. 6AN illustrates the use of the dashboard user interface described previously. FIG. 6AO shows the usage control panel user interface 15 minutes after the user has used the instant messaging application. In response to the application usage, the electronic device 500 updates the user interface to display the use of the instant messaging application in a graphical representation 620 of device usage over time of the application or application class. An indication 616 of overall device usage and an indication 618 of usage of the electronic device as compared to average usage are also updated.

Fig. 6AP shows the usage control panel user interface after the user has used the instant messaging application for another 15 minutes, thereby allowing the total usage of the instant messaging application to reach 30 minutes. In response to the additional usage, the electronic device 500 combines the instant messaging application and the email application into a message category (e.g., in accordance with a determination that the overall usage of the applications in the message category meets a category usage threshold). Once the mail application and the IM application are combined into the message category, the graphic 620 is updated to include a color or pattern associated with the message category that indicates the use of one of the plurality of applications (e.g., the mail application or the IM application) in the message category. In some embodiments, applications are combined into a category when the combined use of those applications meets or exceeds a predetermined category use threshold.

In fig. 6AQ, the user is again updated after using the electronic device 500 to use the instant messaging application for another 30 minutes, thereby allowing the overall use of the application to reach 60 minutes. In response to the additional usage, the electronic device 500 separates the instant messaging application from the email application (e.g., in accordance with a determination that the usage of the instant messaging application meets an application usage threshold). That is, instead of combining the IM application and the mail application into a message category, the illustration 620 is updated to include separate colors or patterns that indicate their use, respectively. In some embodiments, applications are separated when the use of individual applications in a portfolio category meets or exceeds a predetermined application use threshold.

In some embodiments, the device 500 includes not only application usage within the usage of a given application (or class), but also the usage of network resources (e.g., web pages) corresponding to the given application within the usage of the given application (or class). For example, FIG. 6AR illustrates the usage control panel user interface after the user has accessed the website associated with the instant messaging application for thirty minutes. As shown, accessing a website associated with an instant messaging application counts the use of the instant messaging application because the electronic device 500 now indicates that the instant messaging application has been used for a total of 1.5 hours. This number includes one hour of use of the native instant messaging application and 30 minutes of use of the web browsing application to access the relevant networking station of the instant messaging application. Thus, overall usage is optionally tracked in addition to simple native application usage.

Fig. 6AS shows an indication 610b of the user's selection of "Apple TV" in the limit settings user interface (e.g., with contact 603). In response to the selection, the electronic device presents a usage control panel user interface including usage metrics associated with Apple TV, as shown in fig. 6 AT. In this way, the user can concentrate on the use of another device among the devices of the user. The usage control panel user interface in FIG. 6AT includes an indication 616 of the device usage of the day, an indication 618 of how the device usage is compared to average usage, a graphical representation 620 of the use of applications and application categories for the device throughout the day, an indication 634 of the duration of the longest usage session, an indication 636 of the device usage during downtime, and an indication 622a-622b of the use of applications and application categories for which the usage limit is set. In some embodiments, the electronic device 500 optionally displays additional usage metrics associated with the other electronic device, such as the notification and pick-up device described herein. The metrics presented in the usage control panel user interface shown in fig. 6AT are similar to the similar usage metrics described above with reference to fig. 6L.

Fig. 6AU illustrates a usage control panel user interface including aggregated usage metrics for multiple electronic devices associated with a user account (e.g., all devices for John, including Apple TV and iPhone for John). In this way, the user is able to view their use on multiple (e.g., all) of their devices. The usage control panel user interface in fig. 6AU includes an indication 616 of the combined usage of the plurality of electronic devices for the day, an indication 618 of how the usage of the day is compared to average usage, a graphical representation 620 of the combined usage of the applications and application categories for the device throughout the day, an indication 634 of the duration of the longest usage session on all devices, and an indication 636 of the overall usage of all devices during downtime, and an indication 622a-622c of the usage of the applications and application categories for which the usage limit is set. In some embodiments, the electronic device 500 optionally displays additional usage metrics associated with the plurality of electronic devices, such as the notification and pickup devices described herein. The metrics presented in the usage control panel user interface shown in fig. 6AU are similar to the similar usage metrics described above with reference to fig. 6L.

Fig. 7A-7S are flowcharts illustrating a method 700 of presenting an indication of a usage metric according to some embodiments of the present disclosure. Method 700 is optionally performed on an electronic device (such as device 100, device 300, or device 500 described above with reference to fig. 1A-1B, 2-3, 4A-4B, and 5A-5H). Some operations in method 700 are optionally combined and/or the order of some operations is optionally changed.

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

In some embodiments, a control panel user interface (e.g., a digital health control panel) including a visual indication of a first usage metric (e.g., a metric indicating how much a first usage limit has been used up, such as a percentage bar, pie chart, etc.) and a visual indication of a second usage metric (e.g., a metric indicating how much a second usage limit has been used up), such as the usage metric control panel user interface shown in fig. 6L-6U, is displayed (702) at a display at an electronic device (e.g., electronic device 500) in communication with the 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 touch pad, and a touch screen, or a set top box in communication with a television and an input device (e.g., a remote control). The first usage metric is optionally associated with a first operation of the electronic device (e.g., screen time, time of use of a particular application or particular application class, receipt of a notification, attention to an event, etc.) (704), such as in fig. 6L. For example, the first metric is optionally an indication of the amount of "screen time" during which the user has used the device during the day. In some implementations, the visual indication of the first usage measure includes (706) a first usage quantization (e.g., an amount of time or number of times) that the electronic device is used to perform the first operation during a first predetermined period of time (e.g., an hour, a day, or a week), such as in fig. 6L. The visual indication of the first usage metric optionally includes a visual illustration, such as a graph or chart. In some implementations, the visual indication of the first usage measure is a number (e.g., "3 hours of screen time") that is displayed indicating the usage measure. The second usage metric is optionally associated with a second operation of the electronic device (708) that is different from the first operation (e.g., screen time, time of use of a particular application or particular application class, receipt of a notification, attention to an event, etc.), such as in fig. 6L. For example, the second usage measure is optionally an indication of the amount of time that has been spent by the user interacting with the particular application using the electronic device. In some implementations, the visual indication of the second usage measure includes (710) a second usage quantification (e.g., an amount of time or number of times) of performing the second operation using the electronic device during a second predetermined period of time (e.g., an hour, a day, or a week), such as in fig. 6L. In some embodiments, the second usage metric and the first usage metric are associated with different operations, different operation types, different usage quantifies, and/or different time periods (in some embodiments, the same time period), and in some embodiments, the same time period. For example, the visual indication of how much time a user has spent interacting with a particular application using the electronic device optionally includes a graphical representation showing the total screen time used by the device divided by the application and/or application class (including the particular application).

In some embodiments, upon displaying the visual indication of the first usage metric and the visual indication of the second usage metric in the control panel user interface, the electronic device receives (712), via the one or more input devices, an input 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 the first usage metric and/or the second usage metric and different operations, different types of operations, different quantification of usage, and/or different time periods (in some embodiments, the same time period), such as in fig. 6M-6N. For example, in response to user input for viewing the total screen time in the past week and the time spent using the particular application, the electronic device updates the display to present the total screen time in the past week (e.g., rather than during the past day, allowing the user to view the metrics over different time periods) and the time spent using the electronic device to interact with the particular application. As another example, in response to input for viewing the number of notifications received by the electronic device during the course of a day (e.g., in response to user input swiped down through the dashboard user interface), the electronic device updates to display a chart showing the number of notifications received at the electronic device and details about how many of those notifications were generated by different applications within each hour of the day. In some embodiments, in response to receiving the input, the electronic device updates (714) the dashboard user interface to include a visual indication of the third usage metric (e.g., with or without stopping displaying the visual indication of the first usage metric and the visual indication of the second usage metric), such as in fig. 6M-6N. For example, the input for displaying the visual indication of the third usage measure is optionally an input scrolling through a dashboard user interface, which optionally causes the visual indication of the third usage measure to scroll into the display, where it was not previously displayed on the display. The above-described manner of simultaneously displaying multiple visual indications of multiple usage metrics, and allowing a user to view additional visual indications of additional usage metrics, allows the electronic device to effectively visually communicate different metrics of device usage to the user, which simplifies interactions between the user and the device and enhances operability of the device (e.g., by providing more than one way to communicate device usage so that the user can view the metrics of usage that are most meaningful to it), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and effectively use the device.

In some embodiments, the electronic device (716) is one of the plurality of electronic devices associated with a user account (e.g., a user ID for accessing personal data and/or settings at the plurality of electronic devices), such as in fig. 6D. The dashboard user interface (718) optionally includes visual indications (e.g., a first usage measure tracking usage of all electronic devices associated with the user account for performing a first operation) of a first respective usage measure (e.g., a first usage measure or a second usage measure) associated with a first operation of the plurality of electronic devices associated with the user account, such as in fig. 6 AU. In some embodiments, the first usage quantization includes (720) a usage aggregation of performing the first operation using the plurality of electronic devices (including the electronic device) during a first predetermined period of time (e.g., if the first usage measure is an amount of time spent running a particular application or a particular group of applications, the first usage quantization is a total amount of time spent running the particular application or the particular group of applications on all devices associated with the user account during the predetermined period of time), as shown in fig. 6 AU. The above-described manner of associating usage metrics with multiple electronic devices associated with a user allows the electronic devices to present consistent accurate usage data to the user across all devices of the user, which simplifies interactions between the user and the devices and enhances operability of the devices (e.g., by presenting the user's usage data as a single set of metrics for all devices without the user having to individually examine the usage data for each device), which in turn reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.

In some embodiments, the dashboard user interface includes (722) a visual indication of a second respective usage metric (e.g., a third usage metric) associated with a first operation of the electronic device but not with a first operation of a second electronic device (e.g., the electronic device switches from displaying aggregated usage metrics on the plurality of devices to displaying usage metrics separately for each device in response to user input to do so (e.g., user input selecting a particular device from a list of devices associated with a user account), as shown in fig. 6 AT. In some implementations, the electronic device simultaneously displays a visual indication of the usage metric for each of a plurality of electronic devices associated with the user account. The above-described manner of associating usage metrics with multiple electronic devices associated with a user allows the electronic devices to present consistent accurate usage data to the user across all devices of the user, which simplifies interactions between the user and the devices and enhances operability of the devices (e.g., by presenting the user's usage data as a single set of metrics for all devices without the user having to individually examine the usage data for each device), which in turn reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.

In some embodiments, when a visual indication of the first usage measure and a visual indication of the second usage measure are displayed in the control panel user interface, the electronic device receives (724), via the one or more input devices, input corresponding to a request to display the first usage measure and the second usage measure in more detail (e.g., a request to display more information about the first usage measure and/or the second usage measure (e.g., switch from "overview" to "detailed view"), such as selecting the first usage measure and/or the second usage measure in the control panel user interface, such as in fig. 6F-6G. In some embodiments, in response to receiving the input, the electronic device updates (726) the dashboard user interface to display a second visual indication of the first usage measure (e.g., a visual indication that includes more information than or about the first usage measure than included in the first visual indication) and a second visual indication of the second usage measure (e.g., a visual indication that includes more information than or about the second usage measure than included in the first visual indication), as shown in fig. 6G. The second visual indication of the first usage measure and the second visual indication of the second usage measure optionally include (728) a first respective visual indication of usage quantization of performing the first operation during the first predetermined time period using the electronic device for each of the plurality of time periods, as shown in fig. 6 AD-6 AE (e.g., showing the measure in a one-hour-of-day pane). In some embodiments, the second visual indication of the first usage measure is or is included in a graphical or graphical representation over time (e.g., a line graph, a bar graph, a plurality of pie charts for each time interval, etc.), and the second visual indication (732) of usage quantification of the second operation performed using the electronic device for each of the plurality of time periods over a first predetermined time period (e.g., showing the measure in an hour pane throughout the day), as shown in fig. 6G. In some embodiments, the second visual indication of the second usage measure is or is included in a graphical or chart over time (e.g., a line graph, a bar graph, a plurality of pie charts for each time interval, etc.). Each indication of use for each of the plurality of time periods optionally includes an indication of a first operation (e.g., presenting information in a first application or a first set of applications) and a second operation (e.g., presenting information in a second application or a second set of applications). In some embodiments, the detailed view includes a graphical or chart using different colors or other visual indications to convey usage quantification of performing a first operation (e.g., presenting information in a first application or a first application group) and a second operation (e.g., presenting information in a second application or a second application group) using the electronic device. The above-described manner of displaying more information about the first usage metric allows the electronic device to display an overview of the usage and a detailed view of the usage, which simplifies interactions between the user and the device and enhances operability of the device (e.g., by hiding details when the user does not want to see and by displaying the details when needed), which in turn reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, the dashboard user interface further includes (734) a first affordance (e.g., a selectable icon) visually associated with (e.g., displayed alongside) a visual indication of a first usage metric, the first affordance selectable to display (736) a settings user interface for altering one or more settings associated with the first usage metric (e.g., the first usage metric is an amount of time the electronic device has been used to run the first application or first set of applications, and the settings user interface includes options for setting a usage limit for the first application or first set of applications (such as in method 900)), as shown in fig. 6 AH-6 AI. Additionally or alternatively, the first usage measure is optionally a number of notifications generated by the first application or the first set of applications, and the settings user interface includes an option for altering notification settings of the first application or the first set of applications. In some embodiments, the second affordance (e.g., a selectable icon) is visually associated with (e.g., displayed alongside) a visual indication of the second usage measure, the second affordance being selectable to display (738) a settings user interface for altering one or more settings associated with the second usage measure (e.g., the second usage measure is an amount of time the electronic device has been used to run the second application or the second set of applications, and the settings user interface includes options for setting usage limits for the second application or the second set of applications (such as in method 900)), such as in fig. 6 AH-6 AI. Additionally or alternatively, the second usage measure is optionally a number of notifications generated by the second application or the second set of applications, and the settings user interface includes an option for altering notification settings of the second application or the second set of applications. In some embodiments, the dashboard user interface includes a graphic or chart (e.g., bar chart, line graph, pie chart, etc.) indicating at least a first usage metric and a second usage metric, and 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 illustration or diagram and in the list. In some embodiments, the first affordance and the second affordance are displayed alongside visual indications of the first usage measure and the second usage measure, respectively, included in the list. In some embodiments, the setup user interface includes a visual indication of the use of the selected application or category throughout a first period of time (e.g., the day), an indication of use during a limited use mode (e.g., bedtime or device downtime), an indication of average use of a particular application, an indication of notifications generated by the application, an affordance for setting up limits of use for the particular application, and an overview of store information about the application (e.g., ratings, categories, developers, links of the application in the application store). Additional or alternative metrics are possible. In some embodiments, when a user selects an affordance associated with an application category, a respective metric is displayed for each application. In some embodiments, the electronic device display is selectable to display affordances of metrics for individual applications in response to a user selecting an affordance associated with an application category. The above-described manner of displaying affordances selectable to display a settings user interface when displaying first and second usage metrics allows an electronic device to provide a way for a user to navigate to settings associated with usage metrics when viewing the usage metrics, which simplifies interactions between the user and the device and enhances operability of the device (e.g., by simplifying a workflow by which the user changes settings associated with the displayed metrics), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the first predetermined time period is (740) the day (e.g., the first usage measure is a usage quantification of the first operation performed using the electronic device during the day), as shown in fig. 6 AF. In some embodiments, the day is defined to begin when 12:00am is in the current time zone of the electronic device. In some embodiments, the day is defined as some other 24 hour interval, such as 24 hours prior to the current time at the electronic device. The third usage metric is optionally associated with a first operation of the electronic device (742) (e.g., the third usage metric is associated with the same operation of the electronic device as the first usage metric and is in some other aspect different (e.g., usage quantization, time interval, etc.). In some embodiments, the visual indication of the third usage metric includes (744) a third usage quantization of the electronic device performing the first operation during a previous week using the electronic device (e.g., the electronic device displays a usage metric associated with the first operation in a week (e.g., the last seven days including the day, the week including the day, beginning on a particular day (e.g., sunday, monday)), as shown in fig. 6 AG. In some embodiments, the visual indication of the first usage metric is a graphic or chart (e.g., usage quantization, pie chart) or is included therein. For example, the first usage metric is optionally a time period the electronic device has been used to present information associated with the first application program or a set of first applications, and the user interface is displayed on a display of the control panel by way of the user interface is allowed to be presented with the user interface of the device for a further time period of time of day (e.g., the user interface of day) the user interface of the user interface is allowed to be presented), this in turn reduces power usage and improves battery life of the device by enabling a user to more quickly and efficiently use the device.

In some embodiments, the dashboard user interface includes (746) a visual indication of a first respective usage measure associated with displaying information on the display (e.g., the first usage measure is a total usage of the electronic device for displaying information (e.g., a total application screen time on the electronic device) for a first predetermined period of time (e.g., the first usage measure), as shown in fig. 6L. Text indicating the amount of time the device has been used) and/or presented to the user in a graphic, such as a graphic or chart. The indication optionally includes a percentage bar that expresses overall device usage as a percentage (e.g., 50% of a four hour usage limit) or fraction (e.g., two hours of a four hour usage limit) of the usage limit set by the user of the electronic device. In some embodiments, in presenting the first metric indicative of overall display or device usage, the electronic device also presents one or more usage metrics (e.g., including a second usage metric) indicative of an amount of time the electronic device has been 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 has displayed or presented information associated with each of the plurality of applications or application groups. The above-described manner of presenting a visual indication of the amount of time that a device has been used to present information allows an electronic device to visually communicate to a user the amount of time that the device has been used, which makes the user-device interface more efficient (e.g., the user does not have to monitor his own device usage, thus reducing the input provided by the user to the device (e.g., the input used to monitor usage is reduced)), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, displaying (750) information on the display includes displaying (e.g., or presenting (e.g., playing sound, media, or voice with a speaker in communication with the electronic device)) information on the display with one or more first applications (e.g., a particular application or set of applications, such as in fig. 6L. In some embodiments, the set of applications is user-defined or defined by a system or a third party), as shown in fig. 6L. The first respective usage measure optionally includes (752) an amount of time the electronic device has been used to display information with the one or more first applications during the first predetermined period of time (e.g., the first usage measure is a screen time associated with the one or more first applications), as shown in fig. 6L. In some embodiments, a usage limit is set (754) for the one or more first applications (e.g., an amount of time the one or more first applications can be used to present information in a given period of time (e.g., a day) before access to the one or more second applications is restricted), as shown in fig. 6L. The visual indication of the first respective usage measure optionally further includes (746) an indication of a usage limit of the 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), an indication of a first usage limit visually associated with the visual indication of the first respective usage measure (e.g., the visual indication visually compares the amount of time the device has been used to present information to the usage limit), as shown in fig. 6L. In some embodiments, the visual indication of the first metric is a graphical representation. For example, the visual indication is optionally a bar graph, and the size of the bar graph 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 approaching being reached (e.g., text or icons indicating that the usage limit is approaching being reached) and/or an indication of when the 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 graph, a portion of the bar graph optionally indicates an amount of usage that exceeds the usage limit. The user optionally sets a use limit for one or more applications, one or more application groups, and/or an overall use limit for the device. Thus, in some embodiments, the one or more first applications optionally include one application, a plurality of applications, or all applications accessible on the electronic device. The use limits described herein are optionally the same or similar to the use limits described with reference to method 900. The above-described manner of comparing the first metric to the usage limit of the electronic device allows the electronic device to communicate how much time the user can continue to present information with the electronic device before the one or more usage limits are enforced, which makes the user-device interface more efficient (e.g., the user does not have to compare his device usage to the usage limit himself), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the dashboard user interface includes (758) a visual indication of a second respective usage metric (e.g., a second usage metric) associated with displaying information (e.g., or rendering with another output device in communication with the electronic device (e.g., playing sound, media, or voice with a speaker in communication with the electronic device)) on a display with one or more second applications (e.g., a particular application or group of applications, as shown in FIG. 6N. In some embodiments, the group of applications is user-defined or defined by a system or a third party). In some embodiments, the usage limit is not set (760) for the one or more second applications, and the visual indication of the second corresponding usage measure optionally does not include (762) an indication of the usage limit for the one or more second applications (e.g., because there is no), as shown in fig. 6N. The visual indication of the second usage measure optionally indicates an amount of time the electronic device has been used to display information with the one or more second applications without an indication of a usage limit. In some embodiments, while no use limit is set for the one or more second applications, use of some or all of the one or more second applications is optionally limited by a use limit that is different in scope from all of the one or more second applications. For example, the one or more second applications optionally include all applications accessible at the electronic device, while the one or more first applications optionally include applications belonging to a particular application class (e.g., games). Although in this example, the overall usage limit (e.g., the maximum amount of usage limit for device usage across all applications) is optionally not set at the electronic device, some of the one or more second applications (e.g., the one or more first applications) are limited by the usage limit (e.g., the usage limit of the one or more first applications). Likewise, the one or more second applications optionally include a particular application (e.g., a particular gaming application), while the one or more first applications optionally include applications belonging to a particular application class (e.g., gaming). Although in this example, the use limit is optionally not set for a particular second application, the use of the second application is limited by the use limit of the one or more first applications, as the one or more first applications include the second application. The above-described manner of indicating the use limit associated with application use when displaying the application use metrics allows the electronic device to communicate how much time the user can continue to present information with the application before one or more use limits are enforced, which makes the user-device interface more efficient (e.g., the user does not have to compare his application use to the use limit by himself), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, in accordance with a determination (764) that the usage of information by the one or more first applications using the electronic device 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 the usage limit of the one or more first applications, the visual indication of the first respective usage metric includes a visual indication that the usage limit of the one or more first applications is approaching to be reached (e.g., a display indicates that the usage limit is approaching text or an icon to be reached, or a visual indication that a visual characteristic is applied to the first usage metric (e.g., a visual indication or a color or a change in a portion of the visual indication)), as shown in fig. 6W. In some implementations, the visual indication of each of the one or more usage metrics includes an affordance selectable to display a settings user interface for altering one or more settings associated with the respective usage metric. The affordance is optionally displayed with a visual characteristic (e.g., another color) that indicates that the use limit associated with the respective use measure is within a threshold amount. The control panel user interface optionally presents an indication of when the 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 graph, a portion of the bar graph optionally indicates an amount of usage that exceeds the usage limit. The above-described manner of indicating when the usage limit is approaching to be reached when the usage metric is displayed allows the electronic device to communicate how much time the user can continue to perform one or more operations before one or more usage limits are performed, which makes the user-device interface more efficient (e.g., the user does not have to compare his or her usage to the usage limit), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the visual indication of the first respective usage metric includes (766) an indication of an amount of time that the electronic device has been used to present information with each of a plurality of application groups, each application group including one or more applications that are accessible on the electronic device (e.g., the application group is a single application (e.g., an email application, a social networking application, a gaming application, an internet browser, etc.)) or a category that includes a plurality of applications (e.g., a social media category, a gaming category, a news category, a user-defined category that includes a plurality of user-selected applications, etc.), as shown in fig. 6L. The visual indication optionally includes a visual representation of how much of the overall device time is used for each application category. In some embodiments, when the overall device usage metrics are displayed as a graph or chart, the graph or chart includes a section for each application category (e.g., pie chart with multiple "subdivisions," bar chart with multiple sections, bar chart with multiple bars, etc.). The overall usage is optionally compared to a usage limit (e.g., the entire pie of pie chart represents a fixed usage limit, the length of bar chart represents a fixed usage limit, etc.). In some embodiments, the dashboard user interface includes (768) a visual indication of a second corresponding usage metric (e.g., a second usage metric) that the electronic device has been used to render information with the first application group (e.g., a separate metric that conveys an amount of time the first application group was used is rendered in addition to device usage that renders the first application group within the overall device usage metric), as shown in fig. 6L. The visual indication of the second respective usage measure optionally includes (770) a visual indication of the second respective usage measure separate from the visual indication of the first respective usage measure (e.g., the use of the first application group is presented in an additional manner, except that it is presented as part of the visual indication of overall device usage (e.g., as part of a diagram or graph)), as shown in fig. 6L. In some implementations, the visual indication of the use of the first application group includes text indicating an amount of time the first application group was used. Optionally, a graphic separate from the visual indication of overall device usage is displayed, such as a bar of length indicating the use of the first application group, a point of location indicating the use of the first application group, or another visual representation of the use of the first application group. In some embodiments, the electronic device presentation shows a graphical or chart showing how much time the electronic device has been used to present information with each of a plurality of applications and/or application groups, and a textual indication of the amount of time spent with each of the plurality of applications and/or application groups. The above-described manner of presenting device usage for each of the plurality of application groups allows the electronic device to graphically present detailed information about device usage to the user, which simplifies interactions between the user and the device and enhances operability of the device (e.g., by presenting details about the displayed metrics with no further input from the user), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the dashboard user interface includes (772) a visual indication (774) of a first respective usage metric (e.g., a first usage metric) associated with one or more first applications (e.g., individual applications or application categories) running on the electronic device that are accessible (e.g., installed on the electronic device or accessed via a network connection), as shown in fig. 6L. The dashboard user interface optionally includes visual indications (776) of second respective usage metrics (e.g., second usage metrics) associated with one or more second applications (e.g., individual applications or application categories, as shown in fig. 6L) that are accessible on the electronic device (e.g., installed on the electronic device or accessed via a network connection). Thus, the usage measure associated with the first operation is optionally an amount of time the electronic device is used to run (e.g., display) the one or more first applications during the first predetermined period of time, and the usage measure associated with the second operation is optionally an amount of time the electronic device is used to run (e.g., display) the one or more second applications during the first predetermined period of time, as shown in fig. 6L. The above-described manner of presenting usage metrics for running applications and/or groups of applications allows the electronic device to present information about which applications are running on the electronic device, which simplifies interactions between the user and the device and enhances operability of the device, which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the one or more first applications are (778) multiple applications belonging to the same category (e.g., user-defined category or system-defined application category), as shown in fig. 6L. In some embodiments, the categories are defined by the application store, the 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 application store), the use limit set for the category associated with the new application is optionally automatically applied to the new application. The first metric is optionally a quantification of the overall usage of the group of applications in the category. The one or more second applications are optionally (780) one application (e.g., the second metric is optionally a quantification of the use of the individual applications), as shown in fig. 6L. In some embodiments, the dashboard user interface displays one or more metrics for a group of applications while mixing with one or more metrics for an individual application. In some embodiments, the user defines which applications should have their own metrics presented in the dashboard user interface and which application groups 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, an application that uses a threshold above a predetermined application usage threshold will optionally have an application metric presented in the dashboard user interface, while an application class that uses a threshold above a predetermined class threshold (in some embodiments, no individual application above the application usage threshold is used, and in some embodiments, even one or more individual applications that use a threshold above the application usage limit) will have a class metric presented in the dashboard user interface. The above-described manner of concurrently presenting metrics for individual applications and application categories in a dashboard user interface allows the electronic device to present usage metrics that show how the electronic device is being used in a meaningful way (e.g., by displaying metrics with similar granularity), which simplifies interactions between the user and the device and enhances operability of the device (e.g., by concurrently presenting a mix of category metrics and application metrics), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the first usage metric represents (782) usage of the native application and usage of network resources associated with the native application (e.g., usage of the web application or viewing web pages) (e.g., when a user accesses a web site (e.g., a particular social networking web site) associated with an application of the electronic device (e.g., a particular social networking application associated with the web site) using the browser application, as shown in FIG. 6 AR. For example, if the first usage metric is a social media metric, the first metric includes device usage on the electronic device that utilizes the web browser to access the social media platform and device usage that runs the social media application installed on the electronic device. Device usage that utilizes the browsing application of the electronic device to access web pages includes as part of the usage metric associated with the application or class associated with the web page that allows the electronic device to accurately track simplified device usage associated with each usage metric, as shown in FIG. 6 AR. For example, if the first usage metric is a social media metric, the device usage of the device is a social media platform and device is a device that is installed on the electronic device that is a device that is installed on the electronic device.

In some embodiments, in accordance with a determination (784) that the aggregate use of the plurality of first applications (e.g., a plurality of applications belonging to the same user-defined or system-defined class) exceeds a predetermined class use threshold (e.g., the predetermined class use threshold is an absolute threshold (e.g., the plurality of first applications have been used to perform an operation (e.g., render information, generate notifications, etc.) during a first period of time (e.g., a day, a week, etc.) for a predetermined amount of time (e.g., half hour, etc.) or a number of times (e.g., 5, 10, 50, etc.) or a percentage threshold (e.g., 5%, 10%, 25% of the aggregate device use during a first period of time) that the control panel user interface optionally includes a combined use metric (e.g., does not include individual application metrics for any of the plurality of first applications) (e.g., the plurality of first applications are not included as a predetermined class use metric in the first control panel (e.g., the same class use threshold is not included) during the first period of time), the plurality of first applications are determined as a plurality of applications belonging to the same class use threshold in the first user-defined class (e.g., the same class use threshold) in accordance with the plurality of applications 786), the dashboard user interface includes usage metrics for respective ones of the plurality of first applications, but does not include combined usage metrics for the plurality of first applications (e.g., when the overall usage of the plurality of 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 first and/or second usage metrics)), as shown in fig. 6 AP. The above-described manner of selectively presenting the metrics of the application program groups allows the electronic device to present information about the class of most commonly running application programs, which simplifies interactions between the user and the device and enhances operability of the device (e.g., by presenting the combined metrics of the application program groups when the overall use of the application program groups exceeds a threshold), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, in accordance with a determination (788) that the use of a single first application of the one or more first applications (e.g., the one or more first applications are multiple applications belonging to a same class of user-defined or system-defined) exceeds an application use threshold (e.g., the predetermined application use threshold is an absolute threshold (e.g., the first application has been used to perform an operation (e.g., render information, generate notifications, etc.) during a first period of time) for a predetermined amount of time (e.g., half-hour, two hours, etc.) or number of times (e.g., 5, 10, 50, etc.) or a percentage threshold (e.g., 5%, 10%, 25% of total device use during a first period of time), the control panel user interface includes a measure of use of the single first application (e.g., as an alternative or addition to a combined use measure of the multiple first applications) (e.g., when the use of the first application exceeds the application threshold, the first application is used in a first application, such as a single application, in a first control panel, e.g., the control panel, etc.), the control panel user interface includes determining that the use of the single first application (e.g., the single application) exceeds the first application user-use threshold (e.g., the user interface) by the single application user interface (e.g., the control panel) by the single application user interface) based on the predetermined measure (e.g., the user-defined by the single application user-application user interface or the control panel) or the user interface (e.g., the control panel application user-threshold), when the usage of the single first application does not meet the threshold, the usage of the plurality of first applications as a group is presented in the dashboard user interface as a first metric), as shown in fig. 6 AQ. The application use threshold described herein is optionally the same or similar to the application use limit described with reference to method 900. The above-described manner of presenting the metrics of the applications allows the electronic device to present information about the most commonly running applications, which simplifies interactions between the user and the device and enhances operability of the device (e.g., by presenting the metrics of the applications when usage of the group application exceeds a threshold), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the dashboard user interface includes (792) a visual indication of a first respective usage measure (e.g., a first usage measure) associated with receiving one or more notifications at the electronic device (e.g., the dashboard user interface includes a notification metric indicating a number of notifications received at the electronic device during a given amount of time (e.g., an hour, a day, a week, etc.), as shown in fig. 6 AK. The one or more notifications are optionally received from another electronic device by means of a wireless or wired connection. The one or more notifications are optionally generated by an application installed on the electronic device. The above-described manner of displaying notification metrics in the dashboard user interface allows the electronic device to communicate device usage for receiving notifications in an efficient and clear manner, which simplifies interactions between the user and the device and enhances operability of the device (e.g., by automatically collecting notification usage data), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the electronic device receiving (794) at the electronic device one or more notifications includes receiving notifications (e.g., receiving new message notifications 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 category as system-defined or user-defined) of the electronic device, as shown in fig. 6R. In some embodiments, the electronic device presents an indication of each received notification (e.g., displays an image, generates a vibration or haptic and/or tactile output, plays a sound, etc.). The visual indication of the first respective usage measure optionally includes (796) a number displayed indicating a number of notifications (e.g., particular applications or groups of applications, such as multiple applications in the same category as system-defined or user-defined) received during a first predetermined period of time (e.g., one day, one week, one month, etc.) associated with the one or more first applications of the electronic device. In some embodiments, the dashboard user interface includes (798) a visual indication of a second respective usage measure (e.g., a second usage measure) associated with receiving notifications associated with one or more second applications of the electronic device (e.g., receiving alert notifications from alert applications), as shown in fig. 6R. In some embodiments, the electronic device presents an indication of each received notification (e.g., displays an image, generates a vibration or haptic and/or tactile output, plays a sound, etc.). The visual indication of the second corresponding usage metric optionally includes (798-2) a number displayed indicating a number of notifications associated with the one or more second applications of the electronic device received during the first predetermined period of time (e.g., day, week, month, etc.), as shown in fig. 6R. The above-described manner of displaying notification metrics associated with an application or group of applications allows an electronic device to present information about which applications generated the most notifications, which simplifies interactions between a user and the device and enhances operability of the device (e.g., by presenting application data as part of the notification metrics so that the user knows which applications make the device most frequently used to present notifications), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device (e.g., by altering notification settings of applications that generate more notifications than the user wants to receive).

In some embodiments, the dashboard user interface further includes (798-4) a first affordance selectable to display (798-6) a settings user interface for altering notification settings of the one or more first applications (e.g., options to allow all notifications, allow some notifications (e.g., based on priority, time of day, or some other measure), or not allow notifications for an application or group of applications), as shown in fig. 6 AL-6 AM. In some embodiments, the first affordance is visually associated with (e.g., displayed alongside) the following: a visual indication of the first respective usage measure (e.g., the notification measure is displayed concurrently with the affordance for altering the notification settings), and optionally a second affordance of a settings user interface for altering the notification settings of the one or more second applications (e.g., options for allowing all notifications, some notifications (e.g., based on priority, time of day, or some other measure), or no notifications for an application or group of applications), as shown in fig. 6 AL-6 AM. The second affordance is optionally visually associated with (e.g., displayed alongside) a visual indication of the second corresponding usage measure (e.g., the notification measure is displayed concurrently with the affordance for altering the notification setting). In some embodiments, the electronic device includes notification settings that are customizable for each application or for groups of applications. The electronic device optionally further comprises notification settings that affect all applications on the electronic device. The above-described manner of displaying an affordance selectable to display notification settings when displaying notification metrics associated with an application or group of applications allows an electronic device to present options for altering settings associated with metrics currently being viewed by a user, which simplifies interactions between the user and the device and enhances operability of the device (e.g., by making notification settings accessible when viewing notification metrics), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device (e.g., by altering notification settings after viewing notification metrics).

In some embodiments, the visual indication of the first respective usage metric includes (798-10) a graph (e.g., line graph, bar graph, etc.) that includes an indication of a 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 period of time (e.g., one day, one week, one month, etc.), as shown in fig. 6 AL. The above-described manner of presenting a chart of notifications received over time allows the electronic device to simultaneously present an indication of how many notifications have been received during a predetermined period of time and how many notifications have been received in each interval, which simplifies interactions between the user and the device and enhances operability of the device (e.g., by displaying relevant information together without further user input), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the dashboard user interface includes (798-12) a visual indication of the respective usage metrics (e.g., first metrics or second usage metrics) associated with detecting the user attention event (e.g., the dashboard user interface includes metrics indicating the number of times the user initiated interactions with the electronic device), as shown in fig. 6U. In some implementations, the electronic device presents a user attention event (e.g., "pick up device") control panel that indicates one or more metrics related to the user attention event. The user attention event control panel optionally includes metrics such as the average time between picks over a predetermined period of time (e.g., a day, a week, etc.), the total number of picks over the predetermined period of time, the time range with the most user attention events within the predetermined period of time (e.g., an hour of a day or an hour of a week or a day), the number of picks during a limited use mode (e.g., bedtime), and other metrics. In some embodiments, the user attention event is detected when the user input causes the electronic device to exit an idle state (e.g., sleep mode, locked state, low power mode, etc., during which the user does not interact with the electronic device and/or the display of the electronic device is turned 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 (e.g., pressing a power or lock button of the electronic device) corresponding to a request to enter the idle state. In some implementations, the display does not display images during the idle state. In some embodiments, the 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: buttons of the electronic device are pressed, user actions for terminating an idle state (e.g., raising the device), unlocking inputs (e.g., entering a password or providing biometric features), and touch inputs for accessing functions of the electronic device (e.g., a desktop applet user interface, a camera application, a dashboard user interface, a user interface displaying an application associated with a displayed notification indication). Detecting biometric features optionally includes detecting a face of the user with a depth camera or another sensor. In some embodiments, the electronic device can utilize depth cameras and facial recognition techniques to determine when a user is looking at their electronic device and unlock in response to the user looking at the electronic device (e.g., the electronic device unlock in response to determining that the user is focusing on the electronic device). In some embodiments, the electronic device exits the idle state in response to the notification (e.g., the display opens to display the notification without user input requesting the display to open), and the event of interest causes the device to perform some other action (e.g., unlock the device, update the display to display a user interface of an application or operating system). That is, the indication of the notification is optionally not an event of interest to the user, even though it causes the device to exit the idle state. In some implementations, the event metrics of interest indicate the number of times a user initiates use of the electronic device (e.g., "check" his phone). The above-described manner of displaying metrics associated with a user's attention event (e.g., picking up the device) allows the electronic device to present information about the frequency with which the user interacts with the electronic device, which simplifies interactions between the user and the device and enhances operability of the device (e.g., by conveying usage information in a manner that is meaningful to the user), which in turn reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently (e.g., by encouraging the user to use their phone less frequently).

In some embodiments, the visual indication of the first respective usage metric includes (798-14) a visual indication of a time between user interest events (e.g., an average time between user interest events (e.g., a button of an electronic device is pressed, a user action for terminating an idle state (e.g., raising the device), an unlock input (e.g., entering a password or providing a biometric feature), a touch input for accessing a function of the electronic device (e.g., a desktop applet user interface, a camera application, a dashboard user interface, a user interface displaying an application associated with a displayed notification indication)), as shown in fig. 6U. In some embodiments, the time between user attention events is calculated as an average time between user attention events during a time period within a first predetermined time period (e.g., a day, a week, etc.), beginning with an earliest user attention event during the first predetermined time period (e.g., a first attention event of the day, week, or other predetermined time period) and a last user attention event during the first predetermined time period (e.g., a last attention event of the day, week, or other predetermined time period). The above-described manner of displaying a measure indicative of the average time between events of interest to the user (e.g., picking up the device) allows the electronic device to present information about the frequency with which the user interacts with the electronic device, which simplifies interactions between the user and the device and enhances operability of the device (e.g., by conveying usage information in a manner that is meaningful to the user), which in turn reduces power usage and improves battery life of the device (e.g., by encouraging the user to use their phone less frequently).

In some embodiments, the visual indication of the first respective usage metric includes (798-16) a visual indication of a total number of user attention events (e.g., buttons of the electronic device are pressed, user actions for terminating an idle state (e.g., raising the device), unlocking inputs (e.g., entering a password or providing a biometric feature), functions for accessing the electronic device (e.g., a desktop applet user interface, a camera application, a control panel user interface, a user interface displaying an application associated with the displayed notification indication) during a first predetermined period of time (e.g., a day, a week, etc.), as shown in fig. 6U. The above-described manner of displaying a metric indicative of the number of events of interest to the user (e.g., picking up the device) allows the electronic device to present information regarding the frequency with which the user interacts with the electronic device, which simplifies interactions between the user and the device and enhances operability of the device (e.g., by conveying usage information in a manner that is meaningful to the user), which in turn reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently (e.g., by encouraging the user to use their phone less frequently).

In some embodiments, the visual indication of the first usage metric includes a visual indication of a time interval (e.g., one hour of a day, one hour of a week, or one day, etc.) at which the maximum number of user attention events are detected (798-18), which is one of a plurality of time intervals over a first predetermined period of time (e.g., the hour at which the maximum user attention events are detected during a day, as compared to all hours of the day or hours at which the maximum user attention events are detected during a week), as shown in fig. 6U. The above-described manner of displaying a metric indicative of a time interval with most user attention events (e.g., picking up the device) allows the electronic device to present information about when the user most interacted with the electronic device, which simplifies interactions between the user and the device and enhances operability of the device (e.g., by conveying usage information in a manner that is meaningful to the user), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device (e.g., by encouraging the user to use their phone less frequently and thus more efficiently).

In some embodiments, detecting (798-20) an event of interest includes: in accordance with a determination (798-22) that the detected user input corresponds to a request to exit an idle state of the electronic device, as shown in FIG. 6U (e.g., the display displays a lock screen during the idle state (e.g., a user interface of an operating system displayed before the device is unlocked without displaying a user interface of any application that is accessible to the electronic device), a screensaver (e.g., an image displayed without displaying a user interface of any application that is accessible to the electronic device), or a shutdown (e.g., no image displayed), the user input is identified as an event of interest (e.g., the event of interest is one of a device motion (e.g., elevation to wake up), a touch input (e.g., a touch input that selects an image displayed on the lock screen, a swipe input for displaying a desktop applet user interface, a camera user interface, or another user interface of an operating system or one or more applications), actuation of a button included in the electronic device (e.g., a press power button, unlock button, home button, or another toggle button, or a detection of a biometric input (e.g., a biometric input, a facial recognition scheme is implemented, a user input is optionally implemented, a facial recognition scheme is implemented, or a facial recognition scheme is used), the electronic device can utilize depth cameras and facial recognition techniques to determine when a user is looking at their electronic device and unlock in response to the user looking at the electronic device (e.g., the electronic device unlock in response to determining that the user is focusing on the electronic device). In some embodiments, in accordance with a determination (798-24) that the detected user input does not correspond to a request to exit the idle state of the electronic device (e.g., the electronic device is not in the idle state, or the detected user input is erroneous (e.g., large body contact, device motion that does not correspond to a user-raised device, etc.)), the electronic device foregoes identifying the user input as an event of interest (e.g., processes the user input as an input that is not an event of interest or forego processing the erroneous user input), as shown in fig. 6U. The above-described manner of detecting and recording the detection of various user-focused events allows the electronic device to present information regarding the frequency with which the user interacts with the electronic device, which simplifies the interaction between the user and the device and enhances the operability of the device (e.g., by conveying usage information in a manner that is meaningful to the user), which in turn reduces power usage and improves battery life of the device 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 thus more efficiently).

In some embodiments, the visual indication of the first respective usage metric includes (798-26) a visual indication of a number of events of interest detected during a limited use mode of the electronic device (e.g., "device downtime" or "bedtime") (e.g., the electronic device displays a metric indicating a number of times the electronic device detected a user event of interest during the limited use mode), as shown in fig. 6U. The limited use modes described herein are optionally the same or similar to the limited use modes described with reference to method 1100. The above-described manner of displaying a measure indicative of the number of events of interest during the limited use mode allows the electronic device to present information about the frequency with which the user interacts with the electronic device during the limited time, which simplifies interactions between the user and the device and enhances operability of the device (e.g., by conveying usage information in a manner that is meaningful to the user), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device (e.g., by encouraging the user to be outside of the limited mode, thereby more efficiently use their phone).

In some embodiments, prior to displaying (798-28) the dashboard user interface, the electronic device presents an indication of a notification associated with the dashboard user interface (e.g., a daily or weekly "digital health" notification) that includes an affordance (e.g., a soft button or other user interface element) selectable to display the dashboard user interface, as shown in fig. 6K-6L. 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 a 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, including an overview of one or more usage metrics, at the beginning of the week or the beginning of the day). In some embodiments, weekly "digital health" notifications are presented at the beginning of the week, including an overview of the overall device usage in the last week. The summary optionally includes a visual indication of the amount of time the device is used to present information with each of the plurality of applications and/or application categories, as well as an indication of the overall device usage compared to the previous weeks (e.g., a percentage of average weekly usage is exceeded or undershot). In some embodiments, the daily "digital health" notification is presented at the beginning of the day, including an overview of the overall device usage of the previous day. The summary optionally includes a visual indication of the amount of time the device is used to present information with each of the plurality of applications and/or application categories, as well as an indication of the overall device usage compared to the previous days (e.g., a percentage of average daily usage is exceeded or undershot). Other time intervals are also possible (e.g., monthly usage, etc.). The manner of displaying the dashboard user interface in response to selecting the "digital health" notification described above allows the electronic device to alert the user to check his usage metrics and present more detailed metrics from notifications that include a metric summary, which simplifies interactions between the user and the device and enhances operability of the device (e.g., by presenting the usage summary as a notification and presenting more details in response to user input for presenting more details about usage), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the electronic device displays (798-30) a desktop applet user interface prior to displaying the dashboard user interface, the desktop applet user interface including an auxiliary user interface on the electronic device that is accessible to (e.g., installed on the electronic device or accessible via a network connection) the application (e.g., each desktop applet includes a user interface object (e.g., a window) that includes text and/or images associated with the application (e.g., a weather desktop applet displaying current temperature, a sports desktop applet displaying live scores of a scene, a news desktop applet displaying titles of recent events, and/or any user interface object displaying content associated with the application) in some embodiments, the content of the desktop applet corresponding to the application is dynamically updated by the application in some embodiments, the one or more desktop applets optionally including metrics desktop applets associated with the user interface (e.g., desktop applets associated with digital health control boards and/or digital health settings) in some embodiments including metrics (798-32) in some embodiments, such as shown in one or more of the group of the electronic control boards may be displayed in one or more than one week, the other embodiments, the user interface may be a graphical user interface may be displayed in one or more than one week, the desktop applet also includes an indication (e.g., a percentage of average usage above or below one week) that compares the usage over the period of time to the previous usage. In some embodiments, the metrics desktop applet may be selected (798-34) to display a dashboard user interface (e.g., the desktop applet is expanded to include more metrics, such as a second metric or the electronic device rendering the dashboard user interface within the setup application), and the dashboard user interface is optionally displayed (798-36) in response to detecting user input selecting the metrics desktop applet (e.g., the dashboard user interface is displayed in response to a user selecting the metrics desktop applet or expanding the metrics desktop applet), as shown in fig. 6E-6I. The desktop applet user interfaces described herein are optionally the same or similar to the desktop applet user interfaces described with reference to methods 900, 1100, and 1300. The manner of displaying the dashboard user interface in response to selecting the metrics desktop applet described above allows the electronic device to present one of the metrics of use (e.g., the first metric of use) in the top-level user interface (e.g., the desktop applet user interface) and provides a way for a user to enter input for viewing more detailed metrics when viewing the metrics desktop applet, which simplifies interactions between the user and the device and enhances operability of the device (e.g., by presenting a summary of use as the desktop applet and presenting more details in response to user input for presenting more details about use), which in turn reduces power use and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the electronic device displays (798-38) a usage settings user interface of 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 of the operating system of the electronic device, and does not display settings user interfaces of any particular application on the electronic device) prior to displaying the dashboard user interface, as shown in fig. 6 AD-6 AE. The usage settings user interface optionally includes one or more soft buttons that are selectable to display a user interface for altering settings associated with device usage. In some embodiments, the settings include one or more time intervals to set the device in a limited use mode (e.g., device downtime or bedtime mode), one or more applications, application categories, or usage limits (e.g., "limits") for overall device usage, one or more whitelisted applications (e.g., phone, messaging, map, etc.), or application functions (e.g., calling or receiving calls from particular contacts), and/or one or more privacy and content settings. In some implementations, the usage settings user interface includes visual indications (798-40) of the respective usage metrics (e.g., bar charts indicating the total time the electronic device was used to present information with each of a plurality of applications or application groups in the past week), as shown in fig. 6 AD. In some embodiments, other time periods and/or operations are possible. In some embodiments, the desktop applet also includes an indication (e.g., a percentage of average usage above or below one week) that compares usage over the period of time to previous usage. The user settings user interface optionally includes an affordance (e.g., a selectable image or selectable text) that is selectable to display (798-42) the dashboard user interface, which 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 may be selectable to display a control panel user interface), as shown in fig. 6 AD-6 AE. In some embodiments, the dashboard user interface is displayed in response to receiving a user input selection (e.g., a user touching a location on the touch screen where a visual indication of a fourth usage measure is displayed) affordance (e.g., a settings application of the electronic device includes a usage settings user interface for altering one or more usage settings of the electronic device). The usage settings user interface optionally includes a visual indication of a fourth usage metric selectable to display the dashboard user interface. In some implementations, the fourth measure of usage is an amount of time that the device is used to present information for each of a plurality of applications or application categories used during a predetermined period of time (e.g., the day, the week, etc.). The visual indication optionally also indicates a usage limit or "quota" set for the electronic device that defines a maximum amount of time the electronic device can present information without one or more usage restrictions. The manner of displaying the dashboard user interface in response to the visual indication in the select use settings user interface described above allows the electronic device to simultaneously present the use metrics and one or more use settings of the electronic device and provides a way for a user to enter input for viewing more detailed metrics when viewing the use settings, which simplifies interactions between the user and the device and enhances operability of the device (e.g., by presenting a summary of use in the settings user interface and presenting more details in response to user input for presenting more details regarding use), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the usage settings user interface includes (798-44) one or more visual indications of one or more requests received from other electronic devices (e.g., via a network connection (e.g., a wired or wireless connection), as shown in fig. 6B. In some embodiments, an electronic device and the other electronic device are associated with a group or home account) for modifying one or more usage restrictions that are valid at the other electronic device (e.g., a request to remove or increase an overall usage limit (e.g., "quota") for the other electronic device, remove or increase an application-or application-class-specific usage limit (e.g., "quota") for the other electronic device, or authorize the other electronic device to exit a restricted mode of operation (e.g., a 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 a request. In some embodiments, the text indication merely indicates that the request has been received or includes details regarding the request (e.g., the identity of the other device, specific restrictions associated with the request, the identity of the user making the request, etc.). The visual indication is optionally selectable to display one or more options for approving or rejecting the request. The manner of displaying the visual indication of the request to modify one or more usage restrictions of the other device described above allows the electronic device to simultaneously present the request and the usage measure and provide a way for the user to alter the usage settings of the other device, which simplifies device-to-device interactions and enhances device operability (e.g., by presenting the usage settings of the electronic device and other electronic devices in one user interface), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use 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 share group) (798-46), as shown in FIG. 6B. 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 an application to download the application, the other electronic devices can download the application without requiring a separate purchase). The user group account optionally includes a parent user and a child user, and allows an electronic device associated with the parent user to control one or more settings (e.g., content, privacy, usage, and other settings) of the one or more devices associated with the child user. The usage settings user interface optionally includes (798-48) one or more affordances (e.g., selectable text or images) associated with the one or more other electronic devices that are selectable (e.g., via touch input, mouse input, keyboard input, voice input, etc.) to update the dashboard user interface to cease displaying (798-50) visual indications of usage metrics associated with the electronic devices and to display (798-52) one or more visual indications (e.g., one or more usage metrics associated with the other electronic devices associated with the selected affordances) of the other electronic devices, information is presented at the other electronic devices, notifications are received at the other electronic devices, user attention events are detected at the other electronic devices, as shown in fig. 6V-6W. In some embodiments, a parent can view a dashboard user interface for each device of a child to monitor the use of the child device and set one or more use limits (e.g., "limits")) or times when the child device enters a limited use mode (e.g., device downtime or "bedtime"). The electronic device optionally determines which permissions (e.g., for viewing metrics and/or setting usage limits and limited periods of operation) to give each user account based on a classification of the user accounts associated with the electronic device (e.g., as parents, children, etc.) or options selected when setting the device. In some embodiments, the electronic device displays in the setup user interface a usage metric (e.g., overall device usage or screen time) associated with each electronic device associated with the user group account. Optionally, each parent device displays the metrics associated with each child device, but the child devices optionally do not display the metrics associated with any other devices associated with the user group account, and the parent devices optionally do not display the metrics associated with the electronic devices associated with other parent user accounts associated with the user group account. The manner of displaying one or more metrics associated with other devices in a user group account described above allows an electronic device to provide convenient access to usage information for multiple devices in a user group, which simplifies interactions between a user and the device and enhances operability of the device (e.g., by presenting a settings user interface in which a user can modify one or more usage settings of the other devices), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the usage settings user interface includes (798-54) an affordance selectable to delete usage data of the electronic device (e.g., data related to device usage, such as time or number of times information is presented, notifications are received, events of interest to the user are detected, etc., in some embodiments, deleting all of the usage data results in the usage metric of the electronic device being reset), as shown in FIG. 6A. In some embodiments, the method further includes receiving (798-56) user input at the one or more input devices that selects an affordance selectable to delete the affordance of the usage data (e.g., receiving a touch at a location on the touch screen where the affordance is displayed, receiving a selection of the affordance with a mouse or keyboard input, etc.), and in response to receiving the input, deleting (798-58) the usage data. The manner of presenting the options for deleting all usage data described above allows the electronic device to reset the usage metrics in response to user requests for this, which simplifies interactions between the user and the device and enhances operability of the device (e.g., presenting only the usage metrics indicating the data collected after the data was deleted), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the usage settings user interface includes (798-60) an affordance selectable to cease recording usage data of the electronic device (e.g., data related to device usage, such as presentation information, receipt of notifications, detection of times or times of user attention events, etc.), as shown in FIG. 6A. In some embodiments, when data collection is stopped, the usage metrics stop updating, but remain in their current state. In some embodiments, the method further includes receiving (798-62) user input at the one or more input devices selecting an affordance selectable to cease recording usage data (e.g., receiving a touch at a location on the touch screen where the affordance is displayed, receiving a selection of the affordance with a mouse or keyboard input, etc.), and in response to receiving the input, ceasing (798-64) recording usage data (delete or not delete all usage data) for the electronic device. The manner of presenting the options for stopping recording of usage data described above allows the electronic device to give the user control over what data is reflected in the usage metrics, which simplifies interactions between the user and the device and enhances operability of the device (e.g., presenting the usage metrics excluding user-defined periods of time), which in turn reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, the electronic device needs (798-66) authentication credentials for displaying a control panel user interface or modifying settings associated with device usage (e.g., a password different from a password used to unlock the electronic device or a password used to log into a user account at the electronic device) to set or alter one or more usage settings of the electronic device, as shown in fig. 6Y-6 AC (e.g., the electronic device receives user input at the one or more input devices selecting an affordance that can require a password (e.g., receives a touch at a location on a touch screen where the affordance is displayed, receives a selection of the affordance with a mouse or keyboard input, etc.)). In some embodiments, in response to receiving the input, the electronic device presents a user interface for setting the password (e.g., the electronic device displays text requesting the user to enter the use data password and a soft keyboard for entering the password). When a password is required (e.g., in response to a setting or activating the password), the electronic device optionally receives user input at the one or more input devices for selecting one of the affordances selectable to display a setting user interface for altering settings associated with device use (e.g., receiving a touch at a location on a touch screen 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 for entering a password (e.g., displays or speaks a message indicating that changing a setting related to device usage requires a password). Optionally, the device displays a soft keyboard that the user can use to enter a password. In accordance with a determination that the entered password matches the password (e.g., the user entered the correct password), the electronic device optionally presents a use settings user interface capable of altering one or more of these settings. In accordance with a determination that the entered password does not match the password (e.g., the user entered an incorrect password), the electronic device optionally foregoes presenting a use settings user interface that enables one or more of these settings to be altered (e.g., without the correct password, the electronic device does not allow the user to alter settings related to device use). Optionally, the device presents an indication of the current setting (e.g., an indication of one or more usage limits or a period of time the device is operating in a limited usage mode) without the ability to make changes. The manner in which the above-described options for presenting the one or more settings that require a password to change the one or more settings associated with device usage allow the electronic device to block unauthorized changes to the one or more settings associated with device usage, which simplifies interactions between the user and the device and enhances operability of the device (e.g., allows changes to be made at the electronic device in response to the correct password), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the use settings user interface includes (798-68) one or more affordances selectable (798-70) to modify settings associated with a parental guidance rating for content (e.g., settings that restrict access to content (e.g., applications, music, video, etc.) having a specified parental guidance rating), and one or more affordances selectable (798-72) to modify settings associated with data privacy (e.g., settings that restrict sharing of specified types of data, as shown in fig. 6A (e.g., location, contacts, calendar data, reminders, photographs, wireless connections, microphones, etc.)). The manner of concurrently displaying usage settings with parental guidance settings and data privacy settings described above allows the electronic device to present relevant settings in a shared user interface, which simplifies interactions between the user and the device and enhances operability of the device (e.g., presenting similar settings together), which in turn reduces power usage and increases battery life of the device by enabling the user to more quickly and efficiently use the device.

It should be understood that the particular order in which the operations in fig. 7A-7S are described is merely exemplary and is not intended to suggest that the described order is the only order in which the operations may be performed. Those of ordinary skill in the art will recognize a variety of ways to reorder the operations described herein. In addition, it should be noted that the details of other processes described herein in connection with other methods described herein (e.g., methods 900, 1100, 1300, and 1500) are equally applicable in a similar manner to method 700 described above in connection with fig. 7A-7S. For example, the usage metric control panel user interface, usage metrics, notification metrics, device pickup metrics, usage limit settings, etc. described above with reference to method 700 optionally have one or more of the features of the usage metric control panel user interface, usage metrics, notification metrics, device pickup metrics, usage limit settings, etc. described herein with reference to other methods (e.g., methods 900, 1100, 1300, and 1500) described herein. For the sake of brevity, these details are not repeated here.

The operations in the above-described information processing method are optionally implemented by running one or more functional modules in an information processing apparatus such as a general purpose processor (e.g., as described in connection with fig. 1A-1B, 3, 5A-5H) or an application specific chip. Furthermore, the operations described above with reference to fig. 7A to 7S are optionally implemented by the components depicted in fig. 1A to 1B. For example, display operations 702, 798-30, and 798-38 and receive operations 714, 724, 798-56, and 798-62 are optionally implemented by event sorter 170, event recognizer 180, and event handler 190. The event monitor 171 in the event sorter 170 detects a contact on the touch screen 504 and the event dispatcher module 174 communicates the event information to the application 136-1. The respective event identifier 180 of the application 136-1 compares the event information to the respective event definition 186 and determines whether the first contact at the first location on the touch screen corresponds to a predefined event or sub-event, such as a selection of an object on the user interface. When a respective 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. Event handler 190 optionally utilizes or invokes data updater 176 or object updater 177 to update the 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 apparent to one of ordinary skill in the art how other processes may be implemented based on the components depicted in fig. 1A-1B.

Application and class use limits

Users interact with electronic devices in a number of different ways, including using applications accessible on the device. In some cases, it is difficult for a user to monitor and limit the use of a particular application during certain periods of time. The embodiments described below provide a way for an electronic device to enforce usage limits and determine that the usage limits are reached when the limitations of a particular application or class of applications are met, such as when application usage limits associated with those applications are reached, thereby limiting the user's use of the particular application that the user wishes to limit. Setting a usage limit for a particular application or class of applications on an electronic device allows the electronic device to effectively limit the user's usage of the particular device's operations, and provides a simple way for the user to set such usage limits, which makes the device's usage more efficient (e.g., the user does not have to monitor his own device usage, thereby reducing the user's provided input to the device (e.g., input used to otherwise monitor the user's usage)). For example, it is understood that the use limit is set, and the user can more intelligently and effectively use limited operations to perform all necessary tasks under the use limit. If the usage limit is reached, the device limits the user's usage to limited operations, thereby preventing the user from inadvertently exceeding the usage limit and spending more time on the device than expected, which in turn reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. It will be appreciated that people use the device. When a person uses a device, the person is optionally referred to as a user of the device.

Fig. 8A-8 AAN illustrate an exemplary manner of setting, configuring, or implementing use limits on an electronic device according to some embodiments of the present disclosure. The embodiments in these figures are used to illustrate the processes described below, including the processes described with reference to fig. 9A-9K.

Fig. 8A shows an exemplary device 500 having a touch screen 504, described with reference to fig. 5A-5H. Touch screen 504 optionally displays one or more user interfaces including various content. In the example shown in fig. 8A, the touch screen 504 displays the home screen 802 when the constraints are not met on the device 500 (e.g., the user-defined usage limit has not been reached, outside of one or more user-defined time windows associated with the limited usage mode). In some embodiments, the constraints are met when a use limit is reached for a given application or class of applications, as described below. In fig. 8A, 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 device 500, as described above with reference to fig. 4A.

Fig. 8B-8T illustrate an exemplary method of setting and defining usage limits on a device 500 according to examples of the present disclosure. In fig. 8B, a touch object (e.g., a user's finger, stylus, hover input object, hover input device, etc.) selects a setup application 446 from home screen 802 (e.g., by providing contact 803). It should be appreciated that contacts 803 and interactions between contacts 803 and the set application icon are merely exemplary. While specific GUI objects and text are shown in the figures, it should be understood that the GUI shown is not limiting; the disclosed methods may be performed by displaying GUI objects and text that are different from those illustrated without departing from the scope of the present disclosure.

In fig. 8C, in response to selecting the settings application, a settings user interface is displayed and contact 803 selects (e.g., via a tap) an affordance associated with digital health settings 804. In response to selection of the digital health affordance 804, as shown in FIG. 8D, a message 806 is displayed on the electronic device asking the user if he wishes to perform initial use limit settings (e.g., because use limits have not been set on the device 500). Message 806 includes an affordance for performing the use limit setting (e.g., "continue" 808 a) and an affordance for relinquishing the use limit setting (e.g., "now not" 808 b). The user continues to use the limit setting by selecting "continue" 808a with contact 803. In some embodiments, the user optionally relinquishes the initial use limit setting by not continuing with message 806 (e.g., by selecting "now not" 808b, by returning to home screen 802).

Fig. 8E illustrates an exemplary limited use mode setting user interface, optionally displayed by the device 500 in response to selection of "continue" 808a in fig. 8D. In some embodiments, the limited use mode setting user interface is displayed in fig. 8E when initial use limit settings are performed. For example, one or more time windows associated with the limited use mode are optionally initially set in the limited use mode settings user interface, as described in more detail below in connection with fig. 10A-10 AAA and 11A-11I. After the initial setting of the limited use mode is completed, the user proceeds to the initial use limit setting by selecting "yes" 810a (e.g., with contact 803). In some examples, the limited use mode is optionally not set prior to initial use limit setting (e.g., by selecting "no" 810b, by returning to the home screen 802, by not associating any time window with the limited use mode). Details of the restricted use mode are described in more detail below with reference to fig. 10A-10 AAA and fig. 11A-11I. It should be understood that any feature of the limited use modes described in this disclosure may optionally be implemented in combination with any of the use limit features described herein without departing from the scope of this disclosure.

FIG. 8F illustrates an exemplary use limit setting user interface 812 for setting one or more application or category use limits, which is optionally displayed by the device 500 in response to selection of "Yes" 810a in FIG. 8E. The exemplary use limit setting user interface includes a plurality of selectable application categories (e.g., "all applications and categories" 814a, "news" 814b, "games" 814c, "mail" 814d, "social media" 814e, "streaming" 814 f). In some embodiments, the setup user interface includes selectable applications, allowing a user to set up usage limits for individual applications. In this way, the user can select one or more application categories or one or more individual applications that he wishes to limit use.

In FIG. 8F, the exemplary applications associated with each application category are displayed under each respective category (e.g., "social application A", "social application B", "social application C" under "social media" category 814 e). In some embodiments, the user can set a usage limit (e.g., a total "screen time" limit) for all applications and categories on the electronic device by selecting "all applications and categories" 814 a. In some embodiments, the user can set a usage limit for the application and application class selected by the user. The user can relinquish the initial use limit setting by leaving the settings user interface (e.g., by selecting "cancel" 816b, by returning to the home screen 802, by not selecting any applications or categories).

While the use limit setting user interface is illustrated as being accessed, it should be appreciated that the use limit setting user interface may optionally be accessed in a different manner than the illustrated embodiment without departing from the scope of the present disclosure. Although specific applications and categories are shown in the drawings, it should be understood that the specific applications and categories are merely exemplary and that different applications or categories optionally appear on the use limit setting user interface without departing from the scope of the present disclosure.

Fig. 8G-8J illustrate exemplary methods of selecting an application category and selecting an application associated with the selected category for which the user wishes to limit use. In fig. 8G, the user selects an application category (e.g., social media category 814 e) to set a usage limit for the category (e.g., using contact 803). In some cases, the user selects more than one application category 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 an application category. In some examples, selecting "all applications and categories" optionally selects all applications and application categories on the electronic device.

In fig. 8H, in response to selecting an application category (e.g., social media category), a category usage limit setting user interface 818 is displayed. As shown, all applications associated with the currently selected category (e.g., social applications A-E820 a-820E) are displayed and selected by default. In some embodiments, none of these applications is selected; the user selects the currently selected category of applications that will be limited. As shown, selecting a selected application (e.g., social media application B820B) is deselected (e.g., by using contact 803) from a previously selected application (e.g., social application B820B is deselected by using contact 803). While check marks are used to indicate selection of a particular GUI object, it should be understood that other methods of indicating selection (e.g., highlighting, cursors) may be used without departing from the scope of the present disclosure.

In FIG. 8I, social media application B820B is deselected in response to selecting previously selected social application B820B. In some implementations, access to the deselected application is provided even after the use limit associated with the category to which the application belongs has been reached (e.g., because the deselected application is a "whitelisted" application, which will be described in more detail below). The deselection application (e.g., social media application B820B) optionally leaves it unrestricted by the corresponding usage limits (e.g., social media category usage limits). That is, the whitelist application (e.g., social media application B820B) is optionally accessible after a usage limit (e.g., social media category) associated with the whitelist application is reached.

In some embodiments, the use of a non-whitelisted application is credited with the use limit associated with the application. For example, in FIG. 8I, social media application A820 a is optionally selected on the use limit setting user interface 818. Access to the social media application a 820a is optionally limited after the social media category usage limit has been reached. The social media application a's usage optionally counts into the social media category usage limit before the social media category usage limit is reached.

In FIG. 8I, once a desired set of applications (e.g., social media applications A820 a and C-E820C-820E) of a currently selected category (e.g., social media) is selected to be restricted (e.g., access to applications in the selected set of applications is restricted after the use limit associated with the selected category has been reached), the user confirms the set of applications (e.g., by selecting "done" 822 with contact 803) and proceeds to the next setup user interface.

In fig. 8J, a use limit setting user interface 812, optionally displayed by the device 500 in response to selection of "done" 822 in fig. 8I, displays applications and/or categories (e.g., social media 814 e) that have been selected to be implemented by one or more respective use limits. After the 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 selected applications on the category usage settings 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 and are followed by "still more". Applications displayed under other categories (e.g., unselected categories) are optionally not updated. Once all of the desired applications and categories have been selected as being enforced by one or more respective usage limits, the user proceeds to the next user interface (e.g., by selecting "add" using contact 803).

Fig. 8K-8M illustrate an exemplary method of setting a usage limit associated with a category. The user can set different usage limits for applications or application categories to be implemented at different times. For example, as shown in FIG. 8K, in response to selection of "Add" 816a in FIG. 8K, device 500 displays a category usage limit custom user interface 824. Notification and blocking options 828a and notification options 828b are also displayed on the category usage limit custom user interface 824. Methods of implementing the use limits in the "notify" and "notify and block" modes are described in more detail below with reference to fig. 8 AN-8 AW. While notification option 828b is selected in the illustration, it should be appreciated that the user is able to select any option for each use limit. A default usage limit (e.g., "2 hours") associated with the category usage limit is displayed. In some embodiments, the default use limit is automatically determined by the electronic device. The user is optionally able to customize the use limits for different days (e.g., different use limits than the default use limit) by selecting "custom day" 826 on the user interface.

In FIG. 8K, selection of "custom day" via contact 803 is detected and in response, device 500 displays a use limit custom 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 the week (e.g., monday 836b, wednesday 836d, and thursday 836 e). Although different days of the week are illustrated, it should be understood that custom usage limits are optionally defined for any time period. After the custom use limit is defined, the user selects "done" 838 to proceed to the next user interface.

FIG. 8M illustrates the category usage limit customization user interface 824 displayed after the customization usage limit has been set (e.g., after the "done" 838 is selected in FIG. 8L). After the custom use limit is set, the period of time during which the custom use limit is implemented is displayed under "custom day" 826. Upon the user selecting "Add" 830, the custom usage limit is added to the social media category usage limit setting. For example, as shown in fig. 8M, the use limit of one hour is implemented on monday, wednesday, and thursday. Default use limits for two hours are implemented on sunday, tuesday, friday and Saturday.

After setting the use limit in fig. 8M, the device 500 optionally displays a digital health password setup user interface 840, as shown in fig. 8N, for protecting the set use limit. In some embodiments, after the initial use limit setting has been set, the electronic device displays a digital health password setting user interface 840 and prompts the user to enter a password associated with the digital health setting (e.g., use limit setting) on a password entry user interface 842. In some embodiments, the password is different from a general password of the electronic device (e.g., a password used to unlock the device in general) in order to prevent unauthorized access to digital health settings on the device 500 (e.g., by a child who knows the parent device password). While a four-digit digital password is prompted in the illustration, it should be appreciated that different types of authentication credentials are optionally used to secure digital health settings (e.g., alphanumeric passwords, biometric authentication, etc.).

After the initial use limit setting is completed, the limit setting user interface 844 is limited, as shown in FIG. 8O. The limit setting user interface 844 is described in more detail with reference to fig. 6A to 6AU and fig. 7A to 7S. The use of applications in the category associated with the use limit is optionally indicated on a use bar 848. Categories (e.g., "social media") with associated usage limits are displayed below "application limits" 846. For example, in FIG. 8O, no social media categories are used, and thus, use bar 848 indicates that no social media category applications are used. Selection of the "application limits" 846 optionally results in the display of an application limits user interface in FIG. 8P, wherein the application use limit settings can be altered.

Fig. 8P shows an application limit user interface 850. In FIG. 8P, the usage limit categories (e.g., "social media" 852 a) added during initial setup are displayed on the application limit user interface 850. Custom usage limits and their associated time periods are displayed under "social media" 852 a. The user interface also includes an application limit switch key 856. As shown, if the button is toggled "on", the electronic device implements the defined usage limit. Conversely, if the button is toggled "off", the electronic device does not implement the defined usage limit. In some embodiments, when the electronic device does not implement the defined usage limit, the defined usage limit is maintained and saved but not implemented. The defined usage limit will optionally be implemented in a subsequent activation of the application limit (e.g., by toggling the application limit toggle key 856 "on"). In some embodiments, application usage is tracked and preserved during reactivation of the application limit (e.g., by toggling the application limit toggle 856 "off" for a period of time and then toggling the application limit toggle 856 "on") (e.g., the application usage contribution is not reset for subsequent activations of the application limit). In some embodiments, application usage is not tracked and not preserved during reactivation of the application limit (e.g., application usage contribution is reset for subsequent activations of the application limit). The user can add more application or category usage limits by selecting "add limit" 854, as shown in FIG. 8P. In some examples, selection of "add limit 854" optionally causes the electronic device to display a user interface similar to the use limit setting user interface 812. For simplicity, it should be appreciated that adding one or more application or category usage limits is similar to that described in fig. 8F-8M.

FIG. 8Q illustrates the usage limit user interface 850 after additional application usage limits (e.g., "Game A"852c and "streaming application B"852 g) and category usage limits (e.g., "all" 852B, "Game" 852d, "streaming" 852e, "streaming and social media" 852 f) are added. "all" 852b is the overall usage limit (e.g., the total "screen time" limit) of the electronic device associated with all applications and categories on the electronic device. "streaming and social media" 852f is a syndication category usage limit. The federation class usage limit enforces the use of applications associated with the federation class. For example, the use of streaming or social media applications is optionally implemented by a "streaming and social media" joint use limit 852 f.

The electronic device optionally implements concurrent use limits. For example, the user sets concurrent use limits "social media" 852a and "streaming and social media" 852f on the electronic device, as shown. In some embodiments, the use of the social media application associated with the use limit (e.g., social media application a) contributes to both the parallel use limits. In some embodiments, more conservative limits of concurrent use limits are implemented. For example, if there are two hours remaining for the social media usage limit and three hours remaining for the streaming and social media usage limits, the use of the social media application is optionally limited by the more conservative social media usage limit (i.e., two hours after the social media application is used). As another example, if there are two hours remaining for the social media usage limit and one hour remaining for 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., one hour after the social media application is used).

Fig. 8R shows a category usage limit setting user interface 858. The category usage limit setting user interface 858 includes substantially similar information as that shown on the category usage limit setting user interface 818 in fig. 8H-8I. Previously selected applications (e.g., social media applications A820 a and C-E820C-820E) are displayed on the user interface 858 during use limit settings. In some embodiments, the user redefines applications to be restricted by selecting or deselecting applications on the category use limit settings user interface 858. The user renames the name 860 of the category usage limit (e.g., "social media") by selecting "rename" 862, as shown in fig. 8R, which optionally results in renaming of the social media category limit, as shown in fig. 8S and 8T.

In particular, in FIG. 8S, in response to renaming the name 860 of the category usage limit (e.g., renaming "John' S interest" from "social media"), the updated name is displayed on the user interface 858. After the desired update of the category usage limit settings is performed, the user saves the updated settings by selecting "done" 822 and returns to the application limit user interface 850, as shown in FIG. 8T. FIG. 8T illustrates the application limit 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 interest," the application limit user interface 850 displays an updated name for the category 852a (e.g., "John's interest").

Fig. 8U-8 AE illustrate an exemplary method of displaying representations of applications according to various restrictions according to examples of the present disclosure.

In fig. 8U, the touch screen 504 displays the home screen 802 when the constraints are not met on the device 500 (e.g., no application or application class usage limit is reached). In some embodiments, the limit condition is satisfied when a use limit is reached for a given application or class of applications. In some embodiments, the usage restriction condition is satisfied during one or more time windows associated with the restricted 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 with reference to fig. 4A. As shown in fig. 8U, one or more application icons optionally include a notification indicator 864 that notifies the user of any unread notifications associated with the application. For example, the notification indicator 864 in FIG. 8U indicates that there are three unread messages in the social media application A440. In some implementations, the notification indicator 864 is an indicator that is overlaid (or partially overlaid) on top of the appropriate icon, as shown in fig. 8U.

In fig. 8V-8W, 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 when the constraints are not met on device 500 (e.g., no use limit is reached). Search user interface 866 is optionally a user interface of the operating system of device 500 to search for content accessible from device 500 (e.g., websites, news, email, applications installed on device 500, applications available for download to device 500, calendar entries, etc.). The search user interface 866 optionally includes a text field 868 for entering one or more search terms for searching for content accessible from the device 500, an "application suggestion" user interface 870a for applications suggested to the user by the operating system of the display device 500 (e.g., applications that are commonly used, applications that are recently used, applications that are favorite, applications that are currently running), and a desktop applet 870B and 870c (e.g., a user interface object or window that includes text, images, and/or any other content associated with and updated by a respective application (such as social media applications a and B)) corresponding to the application installed on the device 500, as shown in fig. 8W. As shown in FIG. 8W, social media applications A and B are included in the "application suggestion" and their corresponding desktop applets are displayed by device 500 when the constraints associated with those applications are not met on device 500.

In fig. 8X, the user has entered the search term "social media" into text field 868 when the constraints are not met on device 500 (e.g., no usage limit is reached). In response to the search term "social media" having been 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 link 874a for social media application "social application A" installed on device 500, link 874b for social media website "social application A" which is a website related to "social application A" applications, and links for two social media applications available for download from an application repository (e.g., an application store): link 874c of the "social application F" application and link 874d of the "social application G" application.

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

In fig. 8Y-8Z, a vertical swipe of contact 803 is detected on touch screen 504 while home screen 802 is displayed, which causes device 500 to display notification history user interface 878 in fig. 8Z when the constraints are met on device 500 (e.g., social media category usage limits are reached). Notification history user interface 878 includes notifications 880a-b associated with notifications of applications on the device. In some implementations, in response to determining that the usage limit is reached, the appearance of the notification of the application associated with the usage limit is updated (e.g., the notification grays out) to indicate that the associated application is restricted. In some embodiments, the notification after the appearance update is not selectable. In some embodiments, in response to determining that the usage limit is reached, notifications of applications associated with the usage limit are 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 related to the unrestricted application in place of the notifications associated with the restricted application. For example, in fig. 8Z, in response to device 500 determining that the social media usage limit category has been reached, notification 880a associated with social media application a is grayed out (or optionally not displayed) while notification 800b associated with the music application indicates that access to the music application is not restricted.

The device 500 also makes such modifications to the display of representations associated with restricted applications in other user interfaces. For example, in fig. 8 AA-8 AB, 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 in fig. 8AB when the constraints are met on device 500 (e.g., social media category usage limits are reached). Search user interface 866 is substantially similar to the user interfaces described in fig. 8V-8W.

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

In some embodiments, when a usage limit (e.g., social media category usage limit) is reached, the appearance of the desktop applet corresponding to the application associated with the usage limit is updated to indicate its limited status (e.g., the desktop applet is grayed out, the desktop applet 870b corresponding to social media application a is grayed out), as shown in fig. 8 AB. In some implementations, when the usage limit is reached, the desktop applet corresponding to the application associated with the usage limit does not appear on the search user interface 866. When an application icon or applet is suppressed on the search user interface 866, the electronic device 500 optionally displays one or more other icons or applets associated with the unrestricted application in place of notifications associated with the restricted application. For example, in FIG. 8AB, in response to device 500 determining that the social media usage limit category has been reached, the desktop applet 870B associated with social media application A is grayed out (or optionally not displayed), while the desktop applet 870c associated with white list social media application B (e.g., the unselected application on the usage limit setting user interface 818 in FIG. 8I) indicates that access to social media application B is unrestricted.

In FIG. 8AC, the user has entered the search term "social media" into text field 868 when the constraints are met on device 500 (e.g., social media category usage limit is reached). In response to the search term "social media" having been 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 reached usage limit is restricted. For example, when the social media category usage limit is reached, the device 500 displays a link 874a that is updated in appearance (e.g., social media application A icon grayed out) for the social media application "social application A" installed on the device 500, and a link 874b that is updated in appearance (e.g., social media application A icon grayed out) for the social media website "social application A" that is a website related to the "social application A" application. 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 limited in searching (e.g., when social media category usage limits are reached). In some embodiments, when the social media category usage limit is reached, the restricted social media category applications (e.g., non-whitelisted social media category applications, social media applications A and C-E) do not appear in the search results. When one or more links are suppressed on search user interface 866, electronic device 500 optionally displays one or more links related to the unrestricted application in place of notifications associated with the restricted application. For example, in FIG. 8AC, in response to device 500 determining that the social media usage limit category has been reached, link 874b associated with social media application A is grayed out (or optionally not displayed), while links 874c associated with uninstalled social media application F and social media application G indicate that installation of these applications is unrestricted.

Fig. 8AD illustrates a web browser user interface 882 during the time that the constraints are met on device 500 (e.g., social media category usage limits are reached). As shown, the user attempts to access a website (e.g., "www.socmeda.com") corresponding to social media application a. In some embodiments, in response to attempting to access a social media website during the time the social media category usage limit is reached, the content 882-4 of the web browser user interface 882 is hidden from view by the device 500 and a message informing the user that the social media usage limit has been reached is displayed by the device 500, as shown in FIG. 8 AD. In some embodiments, when the usage limit is reached, any aspect of the website corresponding to the application associated with the usage limit (e.g., pages with the same home URL) is restricted to the user.

Fig. 8AE illustrates another web browser user interface 882 during the time that the constraints are met on device 500 (e.g., social media category usage limits are reached). As shown, the user attempts to access a website (e.g., "www.socmeda.com") corresponding to social media application a. In some embodiments, in response to attempting to access the social media website during the period when the social media category usage limit is reached, the content 882-4 of the website is covered by the device 500 with a message informing the user that the social media usage limit has been reached. When the social media category usage limit is reached, the appearance of the user interface objects (e.g., social media application icon a, images 1 and 2) on content 882-4 are optionally updated (e.g., user interface objects grayed out) to indicate that access to the website is restricted, as shown in fig. 8 AE. In some embodiments, when the usage limit is reached, any aspect of the website corresponding to the application associated with the usage limit (e.g., pages with the same home URL) is restricted to the user.

Fig. 8AF to 8AH illustrate an exemplary method of installing an application on the device 500 in the case where the restriction condition of the category associated with the application is satisfied.

FIG. 8AF illustrates home screen 802 when social media category usage limits are reached. In response to the social media category usage limit being reached, the appearance of the social media application A icon 440 is updated to reflect that access to the application is restricted (e.g., the icon is grayed out, and the restriction indicator 876 overlays the icon). As shown, the user selects the app store icon 448 to advance to the app store.

Fig. 8AG shows an application 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 the social media application F to add (e.g., download, install) the application to the electronic device. In some embodiments, social media application F is associated with a social media category usage limit based on application store attributes or application metadata.

Fig. 8AH shows the home screen 802 when the social media category usage limit is reached. In response to adding social media application F from the application store, social media application F icon 452 is added to home screen 802. Since the social media category usage limit is reached and the social media application F is determined to be associated with the social media category usage limit, the social media application F icon 452 reflects that the application is restricted (e.g., the icon is grayed out, the restriction identifier 876b overlays the icon).

Fig. 8 AI-8 AK illustrate an exemplary method of restricting access to an application in accordance with a determination that an electronic device is in a limited use mode (e.g., as described in more detail with reference to fig. 10A-10 AAA and method 1100).

Fig. 8AI shows the home screen 802 when no usage limit has been reached. In fig. 8AJ, a message 888 (e.g., notification) is presented and overlays the home screen 802. Message 888 indicates that the limited use mode (e.g., device downtime) will begin after 5 minutes. If the user selects "eliminate" on the message, message 888 stops displaying. In some embodiments, the message automatically stops displaying after a period of time (e.g., 5 seconds, 30 seconds, or 1 minute) without the "dismissal" option.

Fig. 8AK shows the home screen 802 when the bedtime limit (e.g., limited use mode) is valid, but no application use limit has been reached yet. For example, fig. 8AK optionally shows the home screen 802 more than 5 minutes after the message 888 is presented. When the bedtime limit is valid, the application selected to be limited by the bedtime limit is limited. In some embodiments, when the bedtime limit is in effect, access to restricted applications is restricted even if the limits of use of those applications are not reached. For example, when the bedtime limit is optionally valid, the social media category usage limit optionally has 2 hours remaining. The bedtime limit optionally overrides the use limit setting. That is, social media category applications and any other non-whitelist applications are limited when the bedtime limit is valid, even if the social media category (or other) usage limit is not reached. The appearance of the icon of the restricted application (e.g., the icon grays out, the restriction identifier 876 overlays the icon) is updated to indicate that the application is restricted (e.g., social media application A440, social media application B442, messenger application 424, music application 450).

Fig. 8 AL-8 AP illustrate an exemplary method of presenting an indication that access to an application is restricted and providing access to the application.

Fig. 8AL shows the device 500 displaying the home screen 802 when no usage limit is reached. Fig. 8AM shows the device 500 displaying a home screen 802 when a usage limit (e.g., social media category usage limit) is reached under the "notify" option of the usage limit setting. In some embodiments, the "notification" option is set on the category usage limit custom user interface 824, see FIG. 8M. The appearance of the application icon associated with the restriction (e.g., social media application A440) is updated to indicate that the application is restricted (e.g., the icon is grayed out, and the restriction identifier 876 overlays the icon). As shown, the user attempts to launch social media application A by selecting social media application A icon 440 in FIG. 8 AM.

In response to attempting to launch a restricted application (e.g., when the usage limit is reached, access to the application is restricted), the device 500 optionally visually masks the home screen 802 (e.g., blurs, grays out, or visually changes the home screen) with the restrictions displayed in fig. 8 AN. While the limit 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 should be understood that the notification user interface 890 may be displayed by the device on any content (e.g., the user interface of an application) that is displayed at the time the usage limit is reached. In some embodiments, the device 500 displays an explanation 890-1 indicating that the use limit associated with the selected application has been reached. In some embodiments, interpretation 890-1 includes a visual indication (e.g., AN empty hourglass) to convey to the user that the limit has been reached, as shown in fig. 8 AN. The limit notification user interface 890 also optionally includes a plurality of icons 890-2. The plurality of icons 890-2 includes application icons (e.g., social media applications A and C-E) associated with reached usage limits (e.g., social media category usage limits). If the reached use limit is associated with only a single application, the user interface 890 optionally would include only an icon for that single application.

The limit notification user interface 890 in fig. 8AN includes a "dismissal" affordance 892. Selection of the dismissal affordance 892 is detected in fig. 8AN (e.g., via contact 803 detected on dismissal affordance 892). In response to selecting the dismissal affordance 892, the device 500 stops displaying the dismissal affordance 892 on the limit notification user interface 890 and displays the delay affordance 894 and ignore affordance 896, as shown in FIG. 8 AO.

In some embodiments, user selection of the extended presentation capability representation 894 allows the user to access the restricted application beyond the use limit of the application (without altering the actual time setting of the use limit such that the previously defined use limit will continue to execute in the future) for a predetermined or user-defined amount of time (e.g., 5 minutes, 15 minutes, 30 minutes) beyond the use limit (e.g., as described below with reference to method 900). In some embodiments, the user selection of the negligence enabled representation 896 allows the user to forgo enforcing the use limit for that particular day (without altering the actual time setting of the use limit such that the previously defined use limit will continue to be executed in the future) (e.g., as described below with reference to method 900). In some embodiments, the device 500 stops displaying the extended affordance 894 and the ignored 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 any portion of the limit notification user interface 890 (other than interpreting 890-1, extending the affordance 894, and ignoring the affordance 896) by selecting a home button of the electronic device).

According to the "notify" option, a parent device (e.g., a device associated with a parent on a home account) or a device not associated with a home account at all (e.g., a standalone device) optionally does not require the user to enter any authentication (e.g., password, biometric authentication) to extend or ignore the limit of use limit on the device. Thus, in response to selection of the delay presentation capability representation 894 or the ignore presentation capability representation 896 in FIG. 8AO, 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 use limit for the amount of time (e.g., 15 minutes, the remaining time of the day) for which the affordance is selected. When the usage limit is extended or ignored, all other aspects of the application associated with the usage limit (e.g., any of the limited user interface objects previously described) are also extended or ignored. For example, a user may view or interact with a desktop applet, notification, and web page corresponding to an application associated with an extended or ignored use limit. For example, as shown in FIG. 8AP, in response to selection of the delay presentation capability representation in FIG. 8AO, the limit notification user interface 890 ceases to be displayed 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 object (e.g., an animation that resets an hourglass, such as hourglass 890-1, is flipped and begins to re-run) is presented on the display to indicate that the use limit is extended. In some implementations, the usage of the application associated with the reached usage limit is tracked beyond the reached limit (e.g., by extending, by ignoring for the remainder of the day). For example, the social media category usage limit is optionally two hours. When the social media category usage limit is reached, the user optionally extends social media usage beyond the usage limit. Social media usage by users beyond the two hour limit is optionally tracked by the device.

Fig. 8 AQ-8 AU illustrate exemplary methods of presenting an indication that access to an application is limited and utilizing local authentication to provide access to an application on a parental-controlled child device.

Fig. 8AQ shows that the parent-controlled child device 500A displays a home screen 802 when no usage limit is reached. Fig. 8AR shows the device 500 displaying the home screen 802 when the usage limit (e.g., social media category usage limit) is reached under the "notify and block" option of the usage limit setting. In some embodiments, the "notify and block" option is set on the category usage limit custom user interface 824, see FIG. 8M. The appearance of the application icon associated with the restriction (e.g., social media application A440) is updated to indicate that the application is restricted (e.g., the icon is grayed out, and the restriction identifier 876 overlays the icon). As shown, the user attempts to launch social media application A by selecting social media application A icon 440 in FIG. 8 AR.

In response to attempting to launch a restricted application (e.g., when the usage limit is reached, access to the application is restricted), the device 500A optionally visually masks the home screen 802 (e.g., blurs, grays, or visually changes the home screen) with a restriction notification user interface 890, AS shown in fig. 8 AS. The limit notification user interface 890 is substantially similar to the user interface described in fig. 8 AN.

Selection of the dismissal affordance 892 is detected in fig. 8AS (e.g., via contact 803 detected on dismissal affordance 892). In response to selecting the dismissal affordance 892, the device 500A stops displaying the dismissal affordance 892 on the limit 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. 8 AT.

Under the "notify and block" option, a parental-controlled child device (e.g., a device associated with a child on a home account) requires a user to enter authentication (e.g., local authentication (e.g., password, biometric authentication) on the device, remote authentication from another device (e.g., a parent device) to extend or ignore the limit of use on the device). For example, as shown in FIG. 8AT, the user selects the local authentication request affordance 898-2 to request local authentication (e.g., authentication on the parental-controlled child device 500A) for a desired extension of social media usage limits.

As shown in fig. 8AU, in response to selection of the local authentication request affordance 898-2 in fig. 8AT, the password input user interface 842 displayed by the device 500A prompts the authorized user (e.g., parent) to personally enter authentication. While a four-digit digital password is prompted in the illustration, it should be appreciated that different types of authentication credentials are optionally used to secure digital health settings (e.g., alphanumeric passwords, biometric authentication, etc.). In some embodiments, the authentication password used to extend or ignore the usage limit is different from the password of the electronic device used to prevent unauthorized extension of the usage limit. For example, the authentication password is optionally a digital health password with reference to fig. 8N. In some embodiments, in response to a correctly entered authentication (e.g., a correct password), the user is granted additional access to the selected application beyond the use limit (e.g., 15 minutes, the remaining time of the day). When the usage limit is extended or ignored, all other aspects of the application associated with the usage limit (e.g., any of the limited user interface objects previously described) are also extended or ignored. For example, a user may view or interact with a desktop applet, notification, and web page corresponding to an application associated with an extended or ignored use limit.

After the request for extended use beyond the use limit is authenticated, the electronic device operates in a substantially similar manner as the electronic device after the use limit is extended under the "notify" option, as described in fig. 8AP and its corresponding description.

Fig. 8AV to 8AY illustrate an exemplary method of presenting 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 attempting to launch a restricted application (e.g., when the limit of use is reached, access to the application is restricted), as similarly reflected in fig. 8AQ and 8AR and their corresponding descriptions, the child device 500A optionally visually masks the home screen 802 (e.g., blurs, grays, or visually changes the home screen) with a restriction notification user interface 890, as shown in fig. 8 AV. The limit notification user interface 890 is substantially similar to the user interface described in fig. 8 AN.

Selection of the dismissal affordance 892 is detected in FIG. 8AV (e.g., via contact 803 detected on dismissal affordance 892). In response to selecting the eliminate affordance 892, the device 500A stops displaying the eliminate affordance 892 on the limit 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. 8 AW.

Under the "notify and block" option, a child device (e.g., a device associated with a child on a home account) requires a user to enter authentication (e.g., local authentication (e.g., password, biometric authentication) on the device, remote authentication from another device (e.g., a parent device) to extend or ignore the limit of use on the device. For example, as shown in FIG. 8AW, the user selects remote authentication request affordance 898-4 to request remote authentication (e.g., authentication on parent device 500B) for a desired extension of social media usage limits.

For example, as shown in FIG. 8AX, a message 898-6 including a plurality of extended presentation capability representations 898-8a through 898-8d is displayed on the parent device 500B in response to the selection of the remote authentication request capability representation 898-2 on the child device 500A in FIG. 8 AW. As shown in fig. 8AB, 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. Device) is reached and that the child user is requesting additional usage beyond the usage limit. The plurality of extension representations 898-8a through 898-8d give the parent user different usage limit extension options (e.g., extend for 15 minutes, extend for the remainder of the day, custom extend, refuse extend request); the selected extension option is applied to the child device 500A. For example, as shown in FIG. 8AX, the parent user selects the extended presentation energy representation 898-8a to give the requesting child user an additional 15 minutes beyond the use limit.

In some embodiments, in response to selecting one of the delay presentation energy representations 898-8a through 898-8d, the password entry user interface 842 prompts the user (e.g., parent) for authorization to enter authentication on a remote authentication device (e.g., parent device 500B), as shown in fig. 8 AY. While a four-digit digital password is prompted in the illustration, it should be appreciated that different types of authentication credentials are optionally used to secure digital health settings (e.g., alphanumeric passwords, biometric authentication, etc.). In some embodiments, the authentication password used to extend or ignore the usage limit is different from the password of the electronic device used to prevent unauthorized extension of the usage limit. For example, the authentication password is optionally a digital health password with reference to fig. 8N. In some embodiments, the child device 500A is granted additional access to the selected application beyond the use limit in response to authentication (e.g., a proper password) entered properly at the parent device 500B; the amount of additional access depends on the selected extended affordance. In some embodiments, no password 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., notification) of the outcome of the request (e.g., 15 minutes extended, the remaining time of day extended, request denied).

After the request for extended use beyond the use limit is authenticated by the remote authentication device (e.g., parent device 500B), the electronic device operates in a substantially similar manner as the electronic device after the use limit is extended under the "notify" option, as reflected in fig. 8AP and its corresponding description.

Fig. 8AZ to 8AAC illustrate exemplary methods of presenting an indication that access to an application is limited and providing access to the application based on input from a parent device.

In response to attempting to launch a restricted application (e.g., when the limit of use is reached, access to the application is restricted), as similarly described in fig. 8AQ and 8AR and their corresponding descriptions, the child device 500A optionally visually masks the home screen 802 (e.g., blurs, grays, or visually changes the home screen) with a restriction notification user interface 890, as shown in fig. 8 AZ. The limit notification user interface 890 is substantially similar to the user interface described in fig. 8 AN.

Selection of the dismissal affordance 892 is detected in fig. 8AZ (e.g., via contact 803 detected on dismissal affordance 892). In response to selecting the eliminate affordance 892, the device 500A stops displaying the eliminate affordance 892 on the limit 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. 8 AAA.

Under the "notify and block" option, a child device (e.g., a device associated with a child on a home account) requires a user to enter authentication (e.g., local authentication (e.g., password, biometric authentication) on the device, remote authentication from another device (e.g., a parent device) to extend or ignore the limit of use on the 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 a desired extension of social media usage limits.

As shown in fig. 8AAB, in some embodiments (e.g., unlike the embodiments of fig. 8 AV-8 AY), in response to selection of the remote authentication request affordance 898-2 on child device 500A, the limit notification user interface 890 stops displaying and the message user interface 898-10 is displayed. For example, a message user interface including the current state of the conversation between the child and the parent of the child (e.g., not necessarily related to the usage limit being reached) is displayed (e.g., in a messaging application on device 500B). The messaging user interface 898-10 in the AAB of FIG. 8 includes a message input user interface 898-12 and a messaging affordance 898-14. Before sending the request for additional application access beyond the usage limit, the child is optionally able to enter (e.g., with an input device (e.g., keyboard)) a message to be sent to a remote authentication device (e.g., parent device 500B) along with the request for additional application access as part of an existing message session with the child's parent. To send a request for additional access and an accompanying message, the user selects message sending affordances 898-14. In some embodiments, a child user can send a request for additional access to their parent without entering a message.

In FIG. 8AAC, in response to the selection of the message sending affordance 898-14 in FIG. 8AAB, the messaging user interface 898-10 is updated with a child's request for additional access, optionally represented as a child parent's rich message 898-16. On the device receiving 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 a plurality of delay presentable representations 898-18a through 898-18d.

The plurality of extension representations 898-18a through 898-18d give the parent user different usage limit extension options (e.g., extend for 15 minutes, extend for the remainder of the day, custom extend, refuse extend request); the selected extension option is applied to the child device 500A similar to the selection of the extension affordance described in fig. 8AX through 8 AAC.

In some embodiments, in response to selecting one of the delay presentation representations 898-18a through 898-8d, the user (e.g., parent) performing the authorization is prompted to enter authentication on a remote authentication device (e.g., parent device 500B), as similarly described in fig. 8 AY. In some embodiments, the authentication password used to extend or ignore the usage limit is different from the password of the electronic device used to prevent unauthorized extension of the usage limit. In some embodiments, in response to authentication (e.g., a correct password) entered correctly at the parent device, the child is granted additional access to the selected application beyond the use limit; the amount of additional access depends on the selected extended affordance. In some embodiments, no password is required to respond to messages 898-16.

In some embodiments, after the request is authenticated, the child device 500A displays an indication of the outcome of the request (e.g., 15 minutes extended, the remaining time of day extended, the request is denied) (e.g., a new message on the messaging user interface 898-10, a notification outside of the messaging user interface 898-10).

After the request for extended use beyond the use limit is authenticated by the remote authentication device (e.g., the parent device 500B), the electronic device operates in a substantially similar manner as the electronic device after the use limit is extended under the "notify" option, as described in fig. 8AP and its corresponding description.

Fig. 8 AAD-8 AAG illustrate an exemplary method of presenting an indication that access to an application is restricted and providing access to the application based on authentication credentials entered into an electronic device.

Fig. 8AAD illustrates the device 500 displaying a 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 setting. In some embodiments, the "notify and block" option is set on the category usage limit custom user interface 824, see FIG. 8M. The appearance of the application icon associated with the restriction (e.g., social media application A440) is updated to indicate that the application is restricted (e.g., the icon is grayed out, and the restriction identifier 876 overlays the icon). As shown, the user attempts to launch social media application A by selecting social media application A icon 440.

In response to attempting to launch a restricted application (e.g., when the usage limit is reached, access to the application is restricted), the device 500 optionally visually masks the home screen 802 (e.g., blurs, grays out, or visually changes the home screen) with a restriction notification user interface 890, as shown in fig. 8 AAE. The limit notification user interface 890 is substantially similar to the user interface described in fig. 8 AN.

For example, selection of the dismissal affordance 892 is detected (e.g., via contact 803 detected on the dismissal affordance 892). In response to selecting the dismissal affordance 892, the device 500 stops displaying the dismissal affordance 892 on the limit notification user interface 890 and displays the delay affordance 894 and ignore affordance 896, as shown in fig. 8 AAF.

Under the "notify and block" option, devices without parental control (e.g., devices associated with adult members (e.g., non-children) in a home account, or devices not associated with a home account at all (e.g., stand-alone devices)) require the user to enter an authentication (e.g., password, biometric authentication) on the device to extend or ignore the use limit. For example, as shown in FIG. 8AAE, the user selects the delay presentation energy representation 894 to request an additional 15 minutes use time for the restricted category.

For example, as shown in fig. 8AAG, in response to selection of the extended affordance 894, the password input user interface 842 prompts the user to enter authentication. While a four-digit digital password is prompted in the illustration, it should be appreciated that different types of authentication credentials are optionally used to secure digital health settings (e.g., alphanumeric passwords, biometric authentication, etc.). In some embodiments, the authentication password used to extend or ignore the usage limit is different from the password of the electronic device used to prevent unauthorized extension of the usage limit. For example, the authentication password is optionally a digital health password with reference to fig. 8N. In some embodiments, in response to a correctly entered authentication (e.g., a correct password), the user is granted additional access to the selected application beyond the use limit (e.g., 15 minutes, the remaining time of the day).

Fig. 8 AAH-8 AAI illustrate an exemplary method of displaying an indication that a warning threshold regarding a use limit has been reached.

Fig. 8AAH illustrates a user interface 898 of social media application a displayed by device 500. In FIG. 8AAH, the social media category usage limit has not been reached while the social media application is being displayed. FIG. 8AAI illustrates the user interface 898 when the social media application A is being displayed and a threshold amount of social media category usage (e.g., 1 hour and 55 minutes, 90% of the social media category usage limit) has been reached. In response to the threshold amount being reached, device 500 presents a notification 898-20 on user interface 898 to indicate a remaining time (e.g., 5 minutes) of 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).

Fig. 8AAJ to 8AAK illustrate an exemplary method of altering the use limit setting on a child device.

Fig. 8AAJ shows an application limit user interface 850 for child devices. The user attempts to access the usage limit settings for the social media category by selecting social media category 852 a. As shown in fig. 8AAK, upon selection of the social media category 852a and determining that the device is a child device, the electronic device requires authentication (e.g., by entering a password on the password entry user interface 842, by providing authentication credentials) before the social media category usage limit settings can be altered or viewed. While a four-digit digital password is prompted in the illustration, it should be appreciated that different types of authentication credentials are optionally used to secure digital health settings (e.g., alphanumeric passwords, biometric authentication, etc.). In some embodiments, the password required to alter or view the usage limit setting is different from the password of the electronic device used to prevent unauthorized access to the usage limit setting. For example, the authentication password is optionally a digital health password with reference to fig. 8N.

Fig. 8AAL to 8AAN illustrate an exemplary method of changing child device usage limit settings from a parent device.

Fig. 8AAL shows child device 500A and parent device 500B. The child device 500A and the parent device 500B belong to the same home account. In some embodiments, the names of child devices and parent devices are determined during initial home account setup. Child device 500A in the AAL of fig. 8 displays home screen 802 when the use limit setting (e.g., social media category use limit) is active. Meanwhile, the parent device 500B in the AAL of fig. 8 displays the application limit user interface 850 of the child device 500A. In some embodiments, the application limit user interface 850 of the child device 500A is accessed remotely on the parent device 500B from the home account user interface described in the present disclosure (e.g., as described with reference to fig. 6A-6 AU and method 700). The parent selects social media category 852a (e.g., by utilizing contact 805) to view or alter the social media category usage limit settings of the child device. It should be appreciated that the application limit user interface shown on the parent device 500B in fig. 8AL is substantially similar to the application limit user interface described in the present disclosure (e.g., as described with reference to fig. 6A-6 AU and method 700).

Fig. 8AAM shows child device 500A and parent device 500B when a parent user is attempting to modify child use limit settings on parent device 500B. In response to selection of the social media category 852a in the AAL of fig. 8, the parent device 500B requires authentication (e.g., by entering a password on the password entry user interface 842, by providing authentication credentials) before the social media category usage limit settings of the child device 500A can be altered or viewed. While a four-digit digital password is prompted in the illustration, it should be appreciated that different types of authentication credentials are optionally used to secure digital health settings (e.g., alphanumeric passwords, biometric authentication, etc.). In some embodiments, the password required to alter or view the usage limit setting is different from the password used by the parent device to prevent unauthorized access to the usage limit setting. For example, the authentication password is optionally a digital health password with reference to fig. 8N. In some embodiments, changing the usage limit settings of the child device from the parent device does not require a password (e.g., alphanumeric password, biometric authentication, etc.). After modifying the child use limit settings in an attempt to be authenticated on the parent device, the parent user is optionally able to modify any use limit settings associated with the selected category.

For example, fig. 8AAN shows child device 500A and parent device 500B when a parent modifies child use limit settings on parent device 500B. After the parent modifies the social media use settings of the child device 500A (e.g., the social media category usage limit has been modified from two hours to one hour using the methods described in this disclosure, as shown in fig. 8 AAN), the parent device displays the application limit user interface 850 of the child device. In fig. 8AAN, the modified use limit settings (e.g., one hour next to social media 852 a) are displayed on an application limit user interface on the parent device 500B. Meanwhile, on the child device 500A, after the parent modifies the social media usage limit settings of the child device 500A, messages 898-20 (e.g., pop-up notifications) are presented over the home screen 802, as shown, for example, in FIG. 8AAN, to indicate that the child's social media usage limit settings (e.g., usage limit time, custom usage limit time period, addition of usage limits, removal of usage limits, combination of usage limits) have been modified by their parent. In some embodiments, the message automatically stops being displayed on the child device after a period of time (e.g., 5 seconds, 30 seconds, or 1 minute). In some embodiments, appropriate details in notifications 898-20 and notifications 898-20 are presented on child device 500A in response to usage setting changes implemented on parent device 500B, regardless of whether those changes are more or less restrictive to child device 500A (e.g., regardless of whether the parent has increased or decreased the child's social media usage limit).

Fig. 9A-9K are flowcharts illustrating methods 900 of setting and implementing usage limits (e.g., limiting an application or class of applications based on determining that a usage limit associated with the application or class is reached) according to some embodiments of the present disclosure. Method 900 is optionally performed on an electronic device (such as device 100, device 300, or device 500) as described above in connection with fig. 1A-1B, fig. 2-3, fig. 4A-4B, and fig. 5A-5H. Some operations in method 900 are optionally combined and/or the order of some operations is optionally changed.

As described below, the method 900 provides a way to set and enforce usage limits for applications or application categories on electronic devices. The method reduces the use of the electronic device when the use limit is reached without requiring the user to monitor his own use. For battery-operated electronic devices, restricting access to applications when one or more usage limits are reached saves 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, a computer or tablet including one or more of a keyboard, mouse, touch pad, and touch screen), a wearable device such as a smartwatch including a touch screen, or a set-top box in communication with a television and an input device (e.g., a remote control), receives (902) via the one or more input devices a sequence of one or more inputs setting a usage limit associated with a first application category accessible on the electronic device (e.g., a user may use the device or use the device in a particular manner (e.g., using a particular application (e.g., a particular social media application, SMS, telephone, a particular travel application, email), a particular application category (e.g., social media, streaming media, games, travel, work, communications, payment, news), a particular function of the device (e.g., audio, camera, bluetooth-Fi), a particular function of the application (e.g., one or more stored on the electronic device, etc.), and is set up to a minimum amount of time (e.g., one or more than one or more of a) by a user may be set up to a minimum, such as one or more of M, 8, a user may be set up to a minimum amount of time (e.g., M) of one or more of the device). In some embodiments, the maximum amount of time is accumulated over multiple sessions (e.g., periods of time in which the application is used by the user are separated by periods of time in which the application is not used by the user (e.g., when the user is not using the device to run the application, including when the device is off, when the device is dormant, when the device is disconnected from the network, etc.). In some embodiments, the usage limit is set in a settings user interface of the electronic device (e.g., a settings application for setting the usage limit of the electronic device and one or more other settings such as power settings, display settings, email settings, etc.). In some embodiments, the use limit is set at another electronic device in communication with the electronic device (e.g., via a wireless connection). For example, a parent device is optionally used to set the limits of use of the child's device.

In some embodiments, when the usage limit associated with the first application class is valid (904) (e.g., when the usage limit is valid, the usage time of the application class associated with the usage limit (e.g., social media class usage time) is monitored by the electronic device), the electronic device receives (906) a request to launch the first application of the first application class (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 fig. 8AM (e.g., an attempt to launch a social media application from a home screen when the social media class usage limit has been reached). In some embodiments, an internal timer is associated with each particular application class or usage time of each application. In some embodiments, the associated internal timer is started once the application is started. In some embodiments, the timer is stopped when the application is no longer in use (e.g., the application is turned off, the device is turned off or dormant, the device is disconnected, etc.).

In some embodiments, when the usage limit associated with the first application class is valid (904), in accordance with a determination that the restriction condition of the first application class has been met, wherein the restriction condition includes a requirement that the usage limit of the first application class has been reached (e.g., a determination that a usage time of one or more applications (e.g., social media applications) of the user or one or more operations of the first class has reached a set usage limit) in order for the restriction condition to be met, the electronic device restricts (908) access to the first application of the first application class (e.g., restricts access to the one or more applications (e.g., particular social media applications) by the user or operations of the first class (e.g., generally, in some embodiments, in response to determining that the usage limit of the first application class has been reached, the request to launch the application does not launch the application, or a dialog indicating that the usage limit has been reached is displayed and further user action is required to complete launch of the application. In the background of executing operating system tasks).

In some embodiments, the electronic device provides (910) access to the first application of the first application class, such as in FIG. 8AP (e.g., user access to the application (e.g., a particular social media application) or operation of the first class (e.g., generally) is not limited in that a limit of use (e.g., a social media application) of the first application class has not been met (e.g., a determination is made that a time of use of one or more applications or one or more operations of the first class has not met a set limit of use) is not yet met), in accordance with a determination that a limit of use of the first application class (e.g., a social media application) has not yet been met (e.g., in some embodiments, a time of use of the application requesting launch is compared to a limit of use, in some embodiments, in response to a request for launching the application, the application use limit of the application described herein is optionally the same as or a threshold value as the threshold of the application of the reference method 700 and the application or the application described 1300, such that the user is not provided as a limit of use of the device, such as an input to a user-specific device, such that the user is not provided with a simple way to set up the user-of the device (e.g., such a user-class is allowed to use of the user-specific application) and such as a user-class is set as a user-specific user-class is provided to a limit of the device, input to otherwise monitor use by the user); understanding that the use limit is set, the user can more intelligently and effectively use limited operations to perform all necessary tasks under the use limit; if the usage limit is reached, the device limits the user's usage to limited operations, thereby preventing the user from inadvertently exceeding the usage limit and spending more time on the device than expected, which in turn reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, the restrictions also include requiring that the first application not meet one or more restriction exception conditions (912) (e.g., including on a list of applications (e.g., a white list) that are available for use even if the usage restriction is exhausted), such as in fig. 8I (e.g., social media application B is not selected to be implemented by the social media category usage limit). In some embodiments, the application that is requested to be launched is compared to a list of applications that are free of usage limits.

In some embodiments, in accordance with a determination that the constraints of the first application class have not been met, the electronic device displays (914) a representation of the first application (e.g., an icon, a desktop applet, a window of the first application along with other windows of other applications in a multitasking view) (e.g., an icon of the first application) (e.g., a normal icon of an application installed on the electronic device when the usage limit has not been reached (e.g., in a home screen of the electronic device), such as in color, unmasked, etc.), such as in fig. 8U (e.g., the appearance of the application icon and notification indicator indicates that the application is not limited). For example, the electronic device displays one or more application windows associated with one or more applications (e.g., in a multi-tasking graphical user interface view), or the electronic device displays one or more icons for launching applications on a home screen of the electronic device.

In some embodiments, in accordance with a determination that the constraint of the first application class has been met (e.g., in accordance with a determination that the usage limit is reached and the first application is not on the whitelist), the electronic device displays (916) a first representation of the first application (e.g., changes the appearance of an icon of an application that is not on the whitelist) with a second visual characteristic that is different from the first visual characteristic, such as fig. 8Y-8 AE, (e.g., the application icon, the desktop applet, the notification, and the appearance of the website indicate that the application is limited). In some embodiments, the electronic device modifies the appearance of aspects of the application that are not included in the application whitelist when the usage limit is reached. For example, icons of applications that are not included in the whitelist (e.g., icons on the device's home screen, specific social media application icons) are shaded when the application is restricted. As another example, notification identifiers included on application icons of applications not included in the application whitelist are optionally modified (e.g., particular social media application icons). As another example, in some embodiments, an electronic device has multi-tasking capabilities. In such embodiments, the electronic device optionally displays a user interface that simultaneously displays visual representations of more than one application (e.g., a user interface that simultaneously displays icons from multiple applications, simultaneously displays a screen shot of a current user interface of multiple applications, etc.). In some embodiments, the representations of restricted applications in the above multitasking user interface that are not in the application whitelist are modified (e.g., faded or shaded, or otherwise modified to be displayed with different visual characteristics than the representations corresponding to the applications included in the application whitelist) by the electronic device. The appearance changes of the application representations described herein are optionally the same as or similar to the appearance changes of the application representations described with reference to methods 1100 and 1300. The above-described manner of selectively changing the appearance of applications that are not on the application whitelist when the usage limit is reached allows the electronic device to effectively and selectively limit the use of particular applications during certain periods of time by providing an indication of what applications the user has or does not have access to when the usage limit is reached, which reduces the use of the electronic device during those periods of time, which in turn reduces power consumption and improves 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 identifier on the first representation, the limited use identifier including an indication (918) that access to the first application is limited (e.g., a identifier having a visual indication of a lock or some other limited symbol added to the application icon of the first application (and optionally also other applications that have reached their use limit), such as covering an upper right portion of the application icon, in some embodiments, the identifier covers a portion of text associated with the application icon, in some embodiments, the identifier covers at least a portion of the application icon), such as in FIG. 8AA (e.g., the limited use identifier replaces the notification identifier of social media application A). The above-described manner of selectively changing the appearance of representations of applications not on the application whitelist when the usage limit is reached allows the electronic device to effectively and selectively limit the use of particular applications during certain periods of time by displaying limited use identifiers on applications that do not have access rights when the usage limit is reached, which reduces the likelihood that users will attempt to access such limited applications, which in turn reduces the use of the electronic device during those periods of time, thereby reducing power consumption and improving the battery life of the device.

In some embodiments, displaying the first representation of the first application with the first visual characteristic includes displaying the first representation with a notification indicator (e.g., an indicator of an unread message, missed call, etc.) that includes an indication (920) of a notification received at the first application (e.g., an indicator of an unread message, missed call, etc.), such as fig. 8U (e.g., a notification indicator of social media application a indicates a number of unread messages associated with the application). In some implementations, displaying the first representation of the first application with the second visual characteristic includes displaying a first representation (922) that the notification identifier has been replaced with a limited use identifier (e.g., a obscured indicator or a graphical replacement indicator), such as in fig. 8AA (e.g., a limited use identifier replaces the notification identifier of social media application a). In some implementations, the limited use identifier described above replaces the indication of the notification identifier of the application icon of the non-whitelisted application when the use limit is reached. In some embodiments, replacing the indication of the notification identifier with the limited use identifier described above conceals the number of notifications associated with the application such that the number of notifications is no longer displayed on the display. The above-described manner of selectively changing the appearance of representations of applications not on the application whitelist when the usage limit is reached allows the electronic device to effectively and selectively limit the use of a particular application during certain periods of time by replacing notification indications of the application representations with limited use identifiers on applications that do not have access rights when the usage limit is reached, which in turn reduces power consumption and improves battery life of the device by preventing users from attempting to access limited applications having such notifications by not indicating the presence of a recent notification.

In some embodiments, in accordance with a determination that the first application does not satisfy the one or more constraint exception conditions (e.g., the non-whitelisted application, the first application is not on the whitelist, the first application is configured to be constrained after the usage limit is reached) and while the first application is being used (e.g., a main user interface of the first application is being displayed on the electronic device, or a user is otherwise interacting with the first application (e.g., via an auxiliary user interface of the first application)), the electronic device counts (924) the usage of the first application to a usage limit associated with the first application class (e.g., counts contributions of the usage of the non-whitelisted application to a usage limit associated with the first application class including the first application).

In some embodiments, in accordance with a determination that the first application meets the one or more limited exception conditions (e.g., a whitelist application, the first application being on the whitelist, the first application being configured to be accessible after a usage limit is reached, the application's use for whitelist purposes (e.g., a telephone application and messaging application for parental communications)) and while the first application is being used, the electronic device relinquishes (926) the first application's use to a usage limit associated with the first application class (e.g., in accordance with a determination that the first application's use is excluded from the usage limit (e.g., because the first application is included in the application whitelist, and the electronic device provides access to the first application after the usage limit of the first application class is reached; e.g., because the first application's use is for whitelist purposes (e.g., a telephone application or messaging application for parental communications)), and its use is not being used by the first application, the electronic device relinquished (e.g., a method of allowing the one or more applications to be better-limited to be whitelisted after the application's use limit is determined to be met (e.g., the electronic device is not being whitelisted), unrestricted applications after the usage limit has been reached) without having to add additional categories for the whitelist application, which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

While the first application is being used (e.g., a primary user interface of the first application is being 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 into a use limit associated with the first application class, regardless of whether the first application satisfies the one or more constraint exception conditions (e.g., counts a contribution of the use of the first application into a use limit associated with the first application class, regardless of whether the first application is on a whitelist). For example, the particular social media application associated with the social media category and the 1 hour usage limit is optionally a whitelist application, and its usage is credited to the usage limit. The use of another social media application that is optionally not whitelisted is also optionally counted into a use limit. The method of accounting for use of an application described above allows an electronic device to monitor usage limits of application categories including whitelisted applications, which allows the electronic device to better manage application categories including one or more whitelisted applications (e.g., applications that are not limited after the usage limits have been reached), because the usage limits of the categories take into account the use of whitelisted applications without having to add additional categories for whitelisted applications, which in turn reduces power usage and improves battery life of the device by enabling a user to more quickly and efficiently use the device.

In some embodiments, the usage limit is a first usage limit (930) associated with the first application category for one or more first implementation periods (e.g., a usage limit of the first application category on a weekday), 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) via the one or more input devices a sequence of one or more second inputs (e.g., using the device or using the device in a particular manner (e.g., using a particular application (e.g., a particular social media application, SMS, phone, particular travel application, email) that sets a second usage limit associated with the first application category in one or more second implementation time periods (e.g., the second usage limit is active on Saturday and Saturday, while the first usage limit (e.g., the default usage limit) is active on Saturday to Saturday; the second usage limit is active on work/in class time, while the first usage limit is active outside of work time; the second usage limit is active on a particular day of the week, while the first usage limit is active outside of the particular day) may be set in a second maximum amount of time (e.g., spending one hour, three hours, twelve hours) that is active outside of the particular day, such as in one Saturday, for example, one day, and four categories of media such as those set on Saturday (e.g., saturday).

In some embodiments, in accordance with a determination that the current time is within the one or more first implementation time periods (e.g., a determination that the current time is during a user-defined implementation time period (e.g., a particular day of the week, a work/lesson time, monday through friday)), the electronic device implements (934) a first usage limit (e.g., implements (e.g., counts into a second usage limit when an application of a first application class (e.g., social media) is accessed (e.g., a particular social media application), based on which access to the application of the first application class is provided or restricted), as shown in fig. 8L.

In some embodiments, in accordance with determining that the current time is within the one or more second implementation time periods (e.g., determining that the current time is outside of a user-defined implementation time period (e.g., a default time period, outside of a particular day of the week, after a work/class time, saturday to Saturday)), the electronic device implements (936) the second usage limit, as shown in FIG. 8L (e.g., the first usage limit is accounted for when an application (e.g., a particular social media application) of the first application class (e.g., social media) is accessed, the access to the application of the first application class is provided or restricted based on the first usage limit) (e.g., the default usage limit)). The above-described method of allowing different use limits of a first application class on different days allows the electronic device to effectively limit the user's use of a particular device operation during a defined period of time and provides a simple way for the user to set such use limits during the defined period of time, which makes the use of the electronic device more efficient (e.g., the user's use is limited exclusively during lessons/work hours, work days, particular days; understanding that the second use limit is set, the user can more intelligently use limited operations to perform all necessary tasks during the second particular period of time (e.g., lessons/work hours, work days) at the second use limit, and if the use limit is reached, the device limits the user's use of limited operations, thereby preventing the user from inadvertently exceeding the use limit during the particular period of time (e.g., lessons/work hours, work days) and spending more time on the device than expected), which in turn enables the user to use more quickly and effectively to reduce the device's battery life.

In some embodiments, the electronic device receives (938), via the one or more input devices, input corresponding to a request to exclude a second application of the first application class (e.g., a second particular social media application is associated with a social media class having an associated usage limit) from the usage limit of the first application class (e.g., the request to exclude the second application is optionally set on a set user interface).

After receiving input corresponding to a request to exclude the second application from the usage limit, and when the constraints of the first application class are met (940), the electronic device optionally receives (942) a request to launch the second application, such as in fig. 8AA (e.g., social media application B is not restricted from being launched when the social media class usage limit has been reached). In some embodiments, in response to receiving the request to launch the second application, the electronic device provides (944) access to the second application (e.g., access to the second particular social media application is not restricted whether or not a usage limit associated with the social media application is reached), such as in fig. 8AA (e.g., the appearance of the social media application B icon is not updated when a social media category usage limit is reached). While a first application (e.g., a first particular social media application) and a second application (e.g., a second particular social media application that is different from the first particular social media application) belong to a social media category, the electronic device is able to exclude the second application (e.g., the second particular social media application) from category (e.g., social media) usage limits, while usage of the first application is limited. In some embodiments, the user can define which applications are excluded from such class usage limits. In some embodiments, an application is excluded if the user or electronic device does not define the limits of use of the application. The above-described method of excluding applications associated with a category from the use limits of the category allows an electronic device to distinguish between applications whose use is limited by the use limits (e.g., a first application) and applications whose use is not limited by the use limits (e.g., a second application), which reduces the burden on the user in coping with the limitations on applications that should be excluded from such limitations (e.g., while the second application is associated with a category having a use limit, the second application is optionally excluded from the use limits by the user because the user does not want the application to be limited), which in turn reduces power use and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the usage limit is also associated with a second application class accessible on the electronic device, the second class of application class including applications (946) that are different from the applications of the first application class (e.g., the usage limit is associated with two or more classes such that the overall usage limit for both application classes is set and each of the two or more classes has a different set of applications (e.g., no two sets have the same application list), such as in fig. 8Q (e.g., social media class usage is associated with social media class usage limit and streaming and social media class usage limit first). For example, the usage limit is optionally associated with social media and streaming applications. As another example, the usage limit is optionally associated with social media and messaging applications. While a particular social media application is associated with both social media and messaging categories, the list of applications in the social media category and messaging are optionally different. The above-described method of associating the first application class and the second application class to the use limit allows the electronic device to limit the use of the two classes of applications with joint class use limits, which reduces the burden on the user to track different use limits for different groups, which in turn reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently if total overall use of the different groups is desired.

In some embodiments, the first application class includes all applications (948) that are accessible on the electronic device (e.g., the use limit is associated with all applications and classes on the electronic device such that the total use limit for all applications on the electronic device is set), such as in 8Q (e.g., the "all" use limit). For example, if the total limit is optionally set, the use of the first and second particular social media applications is limited by the total limit, even if the particular applications are associated with social media categories. The total usage limit herein 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 the overall use limits for all application categories allows the electronic device to limit all non-whitelisted application uses (e.g., enforcing user screen time limits) at the overall use limits, which reduces the burden on the user to define individual limits for each category when the overall use limits are desired, which in turn reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, the usage limit associated with the first application category has a first usage limit name (e.g., user previously defined category name, device previously defined category name) based on one or more classification criteria, such as in fig. 8Q (e.g., social media category usage limit has a default name of "social media"). In some embodiments, the default name of the usage limit is a name determined by the device of the application class determined based on the class of applications in the application class, such as "news" or "games" or "news and games". The electronic device optionally receives (952) a sequence of one or more second inputs renaming the usage limit name to a second usage limit name (e.g., the sequence of one or more second inputs is optionally received from the one or more input devices (e.g., electronic device, remote input device)), such as in fig. 8R (e.g., user selects a "rename" affordance to rename social media category usage limit names). In some embodiments, in response to the sequence of one or more second inputs, the electronic device renames 954 the usage limit name to a second usage limit name (e.g., the category name is redefined by the user), such as in fig. 8S-8T (e.g., the user renames the social media category usage limit to "John' S enjoyment"). In some embodiments, the user is able to rename a category name (e.g., a user previously defined name, a device previously defined name) by entering a new user-defined category name (e.g., via a soft keyboard, voice input, etc.). For example, a user can create a category that includes applications from multiple system definitions of different categories (e.g., a particular social media application belonging to a social media category and a particular gaming application belonging to a gaming category), and create their own category names (e.g., "restricted application," "social media, and gaming"). In some embodiments, the electronic device automatically renames the category name. For example, a category named "social media" initially optionally includes a particular social media application. A particular game application is optionally added to the category. In response to adding the game application, the category name is optionally changed by the device to "social media and game". The above-described method of renaming a usage limit class name allows an electronic device to receive input (e.g., from a user, from a remote input device) and rename the usage limit class name in response to the input, which allows the user to rename the usage limit class name when a more appropriate usage limit class name is desired (e.g., when a new application is associated to the usage limit, a more appropriate name is needed to include the newly associated application) without having to set the usage limit again, which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the first application is associated with both the usage limit associated with the first application category and the second usage limit (956) (e.g., the first application is associated with two concurrent usage limits), such as in fig. 8Q (e.g., the social media application is associated with both the social media category usage limit and the streaming and social media category usage limits). For example, a social media category is optionally associated with two usage limits. For example, the electronic device optionally has an overall limit of 2 hours including social media category limits, and/or the electronic device optionally has a usage limit (e.g., half an hour or some other amount) for a particular application within the social media category. The second usage limit is optionally an overall usage limit of the electronic device, a usage limit of an application class of the electronic device (different from, but including, the first application class), a usage limit of the first application itself, separate from the usage limit of the first application class, and so on. The above-described method of implementing two or more usage limits simultaneously allows the electronic device to monitor usage of the application relative to two or more usage limits, which reduces the burden on a user to respectively associate applications that the user wishes to limit to each of the two or more usage limits and to respectively monitor each of the two or more usage limits, which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some implementations, the first application is associated with a second constraint, the second constraint comprising a requirement: for the second constraint to be met, the usage limit of the first application class has been met, or for the second constraint to be met, the second usage limit has been met (958) (e.g., in some embodiments, the second constraint is met when the most conservative limit (e.g., the usage limit with the least time remaining) is met), such as in fig. 8Q (e.g., the social media application is associated with both the social media class usage limit and the streaming and social media class usage limits, and the more conservative usage limit is implemented). In some embodiments, in accordance with a determination that the second constraint has been met, the electronic device restricts (960) access to the first application, such as in fig. 8Q (e.g., the social media application is associated with both social media category usage limits and streaming and social media category usage limits, and more conservative usage limits are implemented).

In some embodiments, in accordance with a determination that the second constraint has not been met, the electronic device provides (962) access to the first application, such as in fig. 8Q (e.g., the social media application is associated with both social media category usage limits and streaming and social media category usage limits, and either usage limit has not been met). For example, the first application is optionally associated with two usage limits. The first application optionally belongs to a social media category, optionally having a first usage limit (e.g., 1 hour or some other amount of time); and the electronic device optionally has an overall limit (e.g., 2 hours or some other amount of time, a second usage limit). If one of these 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 a 1 hour remaining, and the overall usage limit optionally has a 2 hour remaining. In this example, the social media category usage limit is the minimum remaining usage limit of the social media application. As another example, after a certain device usage, the overall usage limit optionally has 30 minutes remaining, and the social media category optionally has 1 hour remaining (e.g., because no social media application has been used so far during the current implementation period). In this example, the overall usage limit is optionally the least remaining usage limit of the social media application. The more conservative remaining usage limits optionally limit the use of the first application for any class or application associated with more than one usage limit. The above-described method of enforcing the most conservative use limits of two or more simultaneous use limits allows an electronic device to monitor the use of an application relative to two or more use limits and enforcing the most conservative remaining use limits, which reduces the burden on a user to respectively associate an application that the user wishes to limit to each of the two or more use limits and to respectively determine which of these use limits was reached earlier, which in turn reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, when a constraint of a first application class is satisfied (964), the electronic device detects (966) an event corresponding to activation of an auxiliary function of the first application (e.g., an event that triggers display of a notification of the application, a request to display a desktop applet 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 prior notification history (including a notification of the application), a request to display application content in a picture-in-picture (PIP) mode, a request to display the application in a search result, or a request to display and/or perform a media control operation associated with the application), wherein the auxiliary function of the first application is a function (e.g., display of an interactive notification, execution of a shared form notification, a display applet, a display in a browser, a display of a notification of a prior notification history (including a notification of the application), a request to display of the application in a search result, a request to display of the application in a social control window or other main view of the application) that is available for execution without displaying a main user interface of the first application (e.g., without launching an application), a history (e.g., display of an interactive notification, execution of a shared form notification, display of a desktop applet, a display of a web site, a display history, a display of the application in a search window or other main view of the application), a search result, a display of the application in a social control window, a search result, a control window, a display of the application in a social graph 8, a user control window, or a user control of the application is attempted to be displayed in a social graph 8, or a user control of the application is displayed in a social graph 8, and/user control of the application is running the user control of the application is displayed in the user interface, and/social device control operation of the user control of the application is running of the application, user interface control of the application, user interface system control of the user interface system application, user interface system control operation, search results and websites).

In some embodiments, in response to detecting an event corresponding to activation of an auxiliary function of a first application, the electronic device suppresses (968) the auxiliary function (e.g., suppresses the notification generation function associated with the application, the display of the website associated with the application, the shared form action, the display of application content in PIP mode, and any other functions associated with the application (including operating system functions) (e.g., limiting the application to appear in search results, displaying access to the desktop applet associated with the application, limiting the application to appear as a suggested application) such as in fig. 8Y-8 AE (e.g., application suggestions corresponding to social media application a, desktop applet, search results, and website are not accessible to the user when social media category usage limits have been reached). The above-described manner of suppressing functionality on different aspects of the operating system of an application whose usage limits have been exceeded allows the electronic device to effectively reduce overall utilization of the electronic device, which reduces power consumption and improves battery life of the device.

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), wherein the application source associates (e.g., downloads new applications (e.g., second particular social media application) from the application store, remotely accesses new applications, installs new applications on the device, in some embodiments, the application store associates (e.g., news applications are specified in the application store as part of a news category, games are specified in the application store as part of a game category, etc.) the application with particular application categories, such as in fig. 8 AF-8 AG (e.g., the user is adding social media application F from the application store user interface).

In some embodiments, in accordance with a determination that the corresponding category is a first category (e.g., a determination that the category assigned to the added application by the application store is the same as an existing category having a usage limit on the electronic device), the electronic device controls (972) access to a second application in accordance with a restriction condition of the first application category (e.g., if the usage limit of the first category (e.g., social media) is reached, the electronic device optionally also restricts user access to the second application (e.g., a second particular social media application added from an application source), such as in FIG. 8AH (e.g., newly added social media application F is determined to be in the social media category usage limit; when the social media category usage limit has been reached, access to newly added social media application F is restricted). Thus, the electronic device applies the first class restriction to the subsequently added second application. In some embodiments, determining the category assigned to the added application by the application is based on an application store attribute (e.g., game, social media, news, streaming) of the added application.

In some embodiments, the electronic device relinquishes (974) control of access to the second application based on the constraints of the first application class (e.g., the use of the added application (e.g., the second particular social media application) is optionally not associated with a first class use limit (e.g., social media use limit). In some embodiments, the added application is controlled based on another use limit of another application class to which the added application falls, in some embodiments, if the added application does not fall within any use limit on the electronic device, then it is not controlled by any use limit on the electronic device, the social media of the added application (e.g., the second particular social media application) is determined based on one or more classification criteria (e.g., application store classification, metadata of the new application) and the social media of the new application (e.g., the new application) is not effectively associated with the social media of the social device based on the social media of any use limit of the electronic device, the user does not have to manually determine the category of the added application; the user does not have to manually determine the usage limits of the added application; the user does not have to monitor the use of his own device of the added application, thereby reducing the input the user provides to the device (e.g., input for otherwise monitoring the use of the user); if the usage limit is reached, the device limits the user's use of the added application, thereby preventing the user from inadvertently exceeding the usage limit and spending more time on the device than expected, which in turn reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, one or more time windows associated with the restricted usage mode during which access to one or more applications on the electronic device is restricted are defined (976) on the electronic device (e.g., a user of the electronic device defines hours of a day (e.g., 10pm to 5 am) as a bedtime restricted usage mode during which the electronic device blocks or attempts to block access to all applications on the electronic device, in some embodiments except applications on the included application whitelist), such as in fig. 8E (e.g., device downtime period is set). In some embodiments, the user defines only the above time window without specifying any particular application for 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 the whitelisted application during the restricted use mode. In some embodiments, in accordance with a determination that a request to launch a first application is received when the 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 during a defined period of time) and the electronic device restricts (978) access to the first application during the one or more time windows associated with the limited use mode (e.g., the electronic device is currently in the limited use mode) regardless of whether a restriction condition of the first application class has been met (e.g., the limited use mode is prioritized over a use limit), such as in fig. 8 AI-8 AK (e.g., the device downtime setting is prioritized over the social media class use limit setting, the device downtime setting restricts the social media application when the social media class use limit has not been reached). Even if, for example, the usage limit of the first application class has not been met, access to the first application class is optionally restricted during the restricted usage mode. The limited use modes described herein are optionally the same or similar to the limited use modes described with reference to method 1100. The manner described above in connection with implementing a limited use mode (e.g., a bedtime limited use mode) in conjunction with an application use limit allows an electronic device to limit access to one or more applications or application categories before the use limit has been reached (e.g., during device downtime, specified inactivity time (e.g., bedtime)), which allows a user to better manage device use during the limited activity time (e.g., bedtime), although the use limit may not yet be reached, which in turn reduces power use and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, restricting access to the first application includes presenting AN indication that indicates that access to the first application is restricted (e.g., displaying a visual indication (e.g., AN hourglass representing time spent, one or more application icons associated with the time limit being reached), playing a sound with a speaker associated with the electronic device, generating a tactile and/or haptic output, etc., indicating that the application is restricted (e.g., a notification)), wherein the indication includes AN affordance (980) selectable to provide access to the first application without authentication credentials (e.g., a graphical user interface element or soft button that allows a user to access the restricted application when the use limit is reached), such as in fig. 8 AN-8 AO (e.g., restriction under the "notification" option notifies the user interface to provide AN extended and ignored affordance for continuing the restricted application). In some embodiments, different applications are associated with different restriction options that are valid when the usage limit is reached. For example, the electronic device optionally allows one or more applications to be associated with a "notification" limit option. If the user attempts to launch an application associated with a "notification" limit (e.g., by selecting an icon for the application from the home screen of the electronic device when the usage limit is 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 limited (e.g., because the usage time limit is reached). In some embodiments, application usage beyond the allowable limits (e.g., even if approved due to time extension) is optionally indicated in the dashboard user interface described above with reference to method 700 (e.g., AS shown in fig. 6L-6P, 6 AE-6 AH, 6 AO-6 AS, and 6 AU). In some embodiments, in response to selecting an affordance for providing access to a first application, and in response to a visual indication on the display being updated to a second visual indication to display that access is being provided prior to providing access to the first application, the "notify" option described herein is optionally the same AS or similar to the "notify" option described with reference to method 1100. The user notification application is limited in use by the battery, while the user is restricted in use by the user, the user is also allowed to perform a reduced in the electronic device while allowing the user to perform tasks while at the same time, in some embodiments, in response to selecting an affordance for providing access to the first application.

In some embodiments, restricting access to the first application includes presenting an indication that indicates that access to the first application is restricted, wherein the indication includes an affordance (982) selectable to provide access to the first application while requiring authentication credentials (e.g., displaying a visual indication (e.g., an hourglass indicating time is spent, one or more application icons associated with the reached use limit), playing a sound with a speaker associated with the electronic device, generating haptic and/or tactile output, etc., indicating that the application is restricted (e.g., a notification)), such as in fig. 8 AAE-8 AAG (e.g., a restriction notification user interface under the "notify and block" option provides an extended and ignore affordance for requesting authentication before continuing with the restricted application). In some embodiments, the electronic device allows one or more applications to be associated with a "block and notify" limit option. If the user attempts to launch an application associated with a "block and notify" limit (e.g., by selecting an icon for the application from the home screen of the electronic device when the usage limit is reached, and assuming 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 limited (e.g., because the usage limit is reached). In some implementations, the pop-up indication requires authentication credentials (e.g., a password, or consent from a parent device/account, fingerprint authentication, facial authentication (e.g., for successful biometric authentication, attention awareness via a depth camera)) to access the application. If the electronic device is a child device in the home account (e.g., a device designated as a user of the child, rather than a parent or administrator in the home account), the displayed notification optionally includes an affordance for requesting permission from an adult/parent device in the home account for accessing the application when the usage limit is reached. In this case, the request in the selection notification optionally causes the notification to be delivered to one or more (or all) parent devices associated with the home account, and the electronic device allows access to the application when permission is granted (e.g., at least one of the parent devices or with a password at the child device). In some embodiments, in response to selecting the affordance for providing access to the first application, and prior to providing access to the first application, the visual indication on the display is updated to a second visual indication to show 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 manner of blocking application launch and informing the user that the application is restricted when the usage limit is reached allows the electronic device to effectively limit the use of certain applications during certain periods of time, which reduces the use of the electronic device during those periods of time, which in turn reduces power consumption and improves the battery life of the device.

In some embodiments, in accordance with a determination that the electronic device is not a child device (e.g., is not a child device in a home account (e.g., is a parent device in a home 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 results in a request to enter a password to access the first application (984), such as in fig. 8 AAE-8 AAG (e.g., a restricted notification user interface under a "notify and block" option provides an extended and ignore affordance for requesting authentication before continuing the restricted application)), for example, determining 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 logged into the device) is not categorized as a child account, for example, the pop-up notification optionally includes one or more affordances that, when selected, only allow the user to proceed to the application when the correct authentication credentials are provided. Is a parent device in the home account) or not associated with the home account at all, the electronic device optionally requests the user to enter credentials (e.g., user id and/or password, password) of the user account associated with the electronic device (e.g., user id and/or password associated with a profile used to configure the device). In some implementations, credentials (e.g., user id and/or password, password) are different from credentials used to access the electronic device (e.g., a password different from a password used to "unlock" the device and/or login to the device). In this way, a user (e.g., child) that is not the device owner (e.g., parent) will not be able to bypass the application restrictions if no auxiliary password is entered.

In some embodiments, in accordance with a determination that the electronic device is a child device (e.g., based on a categorization 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 requiring entry of a password (e.g., a parental control password different from a password used to unlock the device or access a user account associated with device operation) to access the first application, and a second affordance (986) that, when selected, initiates a process for requesting access to the first application from a parent device (e.g., initiates a process for requesting more time from a parent device in a home account) such as in fig. 8 AT-8 AC (e.g., a local authentication request affordance and a remote authentication request affordance are displayed on a restricted notification user interface on the child device; requesting authentication on different corresponding devices in response to selection of the affordance). For example, determining that the electronic device is a child device is optionally based on determining that a user account associated with the electronic device (e.g., a user currently logged into the device) is categorized as a child account. In some embodiments, determining that the electronic device is a child device is optionally based on determining that the electronic device is set as a child device in a setting of the device (e.g., set at initial setting of the device). In some embodiments, the process will send a message to the parent device (e.g., a text message or any other alert on the parent device, an email request to an email account associated with the parent) requesting access to the first application. The process will then either allow the parent to grant access to the restricted application to the child device (e.g., the parent can choose to allow the child device access to the restricted application when the usage limit is reached) or deny the child device access to the restricted application. In some embodiments, the electronic device presents an affordance for entering a password and/or an affordance for initiating a process for requesting access to the first application. In some implementations, the password is a different parental control password or use password than the password used to unlock the electronic device. As such, the child optionally cannot bypass the restricted access mode, but the parent optionally can enter a password to allow the electronic device to access the first application. The request for additional time described herein is similar to the request for additional time described with reference to the limited use mode in method 1100. The above-described manner of informing the user that the application is restricted when the usage limit is reached, but that the user is enabled to access the options of the application when needed, allows the electronic device to effectively restrict the use of certain applications during certain periods of time, while allowing the user to perform necessary tasks on the electronic device, which reduces the use of the electronic device during those periods of time, which in turn reduces power consumption and improves the battery life of the device.

In some embodiments, upon determining that a warning threshold for the usage limit has been reached (e.g., the warning threshold has been reached (e.g., 45 minutes in the usage limit of 90%,5 minutes remaining, 1 hour; 5 minutes, 10 minutes, 1 hour, or any period of time before the usage limit has been reached) when the usage limit associated with the first application class is valid), the electronic device displays (988) an indication (e.g., text, image, sound, tactile and/or haptic output, etc.) that the warning threshold for the usage limit has been reached (e.g., an indication that the usage limit is about to be reached and a threshold time (e.g., 90%, 45 minutes in the 5 minutes remaining, 1 hour) has been reached or remains a particular time (e.g., 5 minutes, 10 minutes, 1 hour, or any period of time) before the usage limit has been reached) (such as in FIG. 8AI (e.g., a notification is displayed on the device, indicating that the usage limit has 5 minutes remained) in some examples, the threshold time is defined by the user in some examples, including in some embodiments, the sound, tactile output is stopped in some of the social notification device (e.g., the indication of the amount of time is about to be reached) and the threshold time (e.g., 45 minutes in the 5 minutes remaining in the 5 minutes, 1 hour) is reached) before the usage limit is reached 45 minutes in 1 hour) has been used) in a manner that makes the user-device interface more efficient (e.g., the user does not have to monitor time, provides the user with an opportunity to complete tasks currently being performed on the device, and prompts the user to stop using the device if the projected use limit is reached, thereby reducing user-provided input to the device (e.g., input to update the use limit setting)), which allows the electronic device to effectively reduce overall use of the electronic device, which in turn reduces power consumption and improves battery life of the device.

In some embodiments, the electronic device receives one or more inputs (990) for altering one or more usage limit settings associated with the usage limit (e.g., a change to a start/end time of the usage limit, a change to a whitelist, etc.), such as in fig. 8AAJ (e.g., the user is attempting to view or modify social media category usage settings). In some embodiments, in response to receiving the one or more inputs to change the one or more usage limit settings (992), in accordance with a determination that the one or more inputs to change the one or more usage limit settings are received via the one or more input devices of the electronic device and the electronic device is a child device (e.g., based on a categorization of a user account associated with the electronic device or an option selected on the electronic device), the electronic device requires (994) authorization (e.g., requires a user of the electronic device to enter a password in order to change the usage limit settings) prior to performing the one or more usage limit settings changes, such as in fig. 8 AAJ-8 AAK (e.g., modifying the usage limit settings on the child device requires a password). For example, determining that the electronic device is a child device is optionally based on determining that a user account associated with the electronic device (e.g., a user currently logged into the device) is categorized as a child account. In some embodiments, determining that the electronic device is a child device is optionally based on determining that the electronic device is set as a child device in a setting of the device (e.g., set at initial setting of the device). In some embodiments, if the electronic device is a child device in a home account, any use limit settings or preferences or rules, etc., described herein can only be modified at the child device in response to entering a password or other authentication credential at the child device (e.g., upon determining that one of these settings is being modified, the electronic device prompts the user to enter a password that must be authenticated before modification is allowed). In some implementations, the authentication credentials are the same as credentials used to unlock the device (e.g., password, fingerprint authentication, and/or facial authentication (e.g., for successful biometric authentication, attention awareness via a depth camera is required)) for unlocking the device. In some implementations, the authentication credentials are different from credentials used to unlock the device (e.g., credentials of a parent in a home account). In some embodiments, the parent device is able to modify the above settings valid on the child device remotely (e.g., optionally, by entering parental credentials at the parent device).

In some embodiments, in response to receiving the one or more inputs to change the one or more usage limit settings (992), in accordance with a determination that the one or more inputs to change the one or more usage limit settings are received from outside the electronic device via the parent device (e.g., the change to the usage limit settings is made on the parent device (e.g., is a parent device in a home account, based on a categorization of a user account associated with the electronic device, or an option selected on the electronic device)), the electronic device performs (996) the one or more usage limit settings changes (e.g., makes a change to the usage limit settings without requiring input of additional credentials), such as in fig. 8 AAL-8 AAN (e.g., the parent device is modifying the usage limit settings of a child device). For example, determining that the electronic device is not a child device is optionally based on determining that a user account associated with the electronic device (e.g., a user currently logged into the device) is not classified as a child account. In some embodiments, determining that the electronic device is not a child device is optionally based on determining that the electronic device is set as a parent device in a setting of the device (e.g., set at initial setting 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 makes the change to the use limit settings on the child device remotely (e.g., over the internet, bluetooth, or other network or protocol). The manner in which the usage limit is set/changed is the same or similar to the manner in which the limited usage mode is set/changed as described with reference to method 1100. The above-described manner of limiting the ability to alter the use limit settings allows the electronic device to effectively and selectively limit the use of certain applications during certain periods of time, which reduces the use of the electronic device during those periods of time, which in turn reduces power consumption and improves the battery life of the device.

In some embodiments, in response to performing the one or more usage limit setting changes received from outside the electronic device, the electronic device presents (998) an indication (e.g., a visual indication (e.g., one or more of text and images), an audible indication, a verbal indication, and/or a tactile and/or haptic output indication) of the one or more usage limit setting changes (e.g., presents a notification (e.g., a parent device in a home account, a classification based on a user account associated with the electronic device or an option selected on the electronic device) that the usage limit setting is changed remotely by the parent device), such as in fig. 8AAN (e.g., a notification is displayed on a child device when its usage limit setting is modified by the parent device). For example, determining that the electronic device is not a child device is optionally based on determining that a user account associated with the electronic device (e.g., a user currently logged into the device) is not classified as a child account. In some embodiments, determining that the electronic device is not a child device is optionally based on determining that the electronic device is set as a parent device in a setting of the device (e.g., set at initial setting of the device). In some embodiments, if the parent device remotely modifies the above settings that are active on the child device, the child device displays a notification that such remote modification occurred, details of the modification (e.g., the parent device has changed the usage limit, the parent device has changed the time window during which the usage limit was active from 10pm to 6am to 9pm to 7am, etc.). The notifications generated on the child device herein are the same as or similar to the notifications generated on the child device with reference to the limited use mode described in method 1100. The manner of altering the use limit settings described above allows the electronic device to effectively and selectively limit the use of certain applications during certain periods of time, which reduces the use of the electronic device during those periods of time, which in turn reduces power consumption and improves the battery life of the device.

In some embodiments, generating the one or more inputs received from a parent device external to the electronic device for altering the one or more usage limit settings requires that authentication credentials (998-2) for making a usage limit setting alteration on the electronic device be entered at the parent device (e.g., based on a categorization of a user account associated with the electronic device or an option selected on the electronic device) (e.g., in response to receiving input from a device of the parent device (e.g., a device of an authorized adult) to alter the usage limit settings, a password (e.g., a device usage limit password or other authentication credentials, optionally different from authentication credentials for accessing the parent and/or child device) be optionally required at the parent device for continuing the usage limit setting alteration), such as in fig. 8AAM (e.g., requiring a password on the parent device to modify the usage limit settings of the child device on the parent device). For example, determining that the electronic device is not a child device is optionally based on determining that a user account associated with the electronic device (e.g., a user currently logged into the device) is not classified as a child account. In some embodiments, determining that the electronic device is not a child device is optionally based on determining that the electronic device is set as a parent device in a setting of the device (e.g., set at initial setting of the device). The above-described methods of requiring authentication credentials (e.g., password, fingerprint authentication, facial authentication) to alter the usage limit settings from a parent device allow the electronic device to set the usage limit through a remote device after the authentication credentials are entered, which prevents 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 alter the child device usage limit settings), which reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

It should be understood that the particular order in which the operations in fig. 9A-9K are described is merely exemplary and is not intended to suggest that the described order is the only order in which the operations may be performed. Those of ordinary skill in the art will recognize a variety of ways to reorder the operations described herein. In addition, it should be noted that the details of other processes described herein in connection with other methods described herein (e.g., methods 700, 1100, 1300, and 1500) are equally applicable in a similar manner to method 900 described above in connection with fig. 9A-9K. For example, the use limits, use limit settings, etc. on the electronic device described above with reference to method 900 optionally have one or more of the features of the use limits, use limit 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 are not repeated here.

The operations in the above-described information processing method are optionally implemented by running one or more functional modules in an information processing apparatus such as a general purpose processor (e.g., as described in connection with fig. 1A-1B, 3, 5A-5H) or an application specific chip. Furthermore, the operations described above with reference to fig. 9A to 9K are optionally implemented by the components depicted in fig. 1A to 1B. For example, display operations 914, 916, 918, 920, 922, 942, and 988 and receive operations 902, 906, 932, and 990 are optionally implemented by event sorter 170, event recognizer 180, and event handler 190. The event monitor 171 in the event sorter 170 detects a contact on the touch screen 504 and the event dispatcher module 174 communicates the event information to the application 136-1. The respective event identifier 180 of the application 136-1 compares the event information to the respective event definition 186 and determines whether the first contact at the first location on the touch screen corresponds to a predefined event or sub-event, such as a selection of an object on the user interface. When a respective 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. Event handler 190 optionally utilizes or invokes data updater 176 or object updater 177 to update the 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 apparent to one of ordinary skill in the art how other processes may be implemented based on the components depicted in fig. 1A-1B.

Limited use mode user interface

Users interact with electronic devices in a number of different ways and during different times of day or night. For example, a user may read the latest news on a news application installed on an electronic device in bed during their morning train commute or at the end of the day. However, in some cases, it is difficult for a user to monitor and limit the use of a particular application during certain periods of time. The embodiments described below provide a way for an electronic device to effectively and selectively limit access to certain applications during certain periods of time that reduces the use of the electronic device during those periods of time without requiring the user to monitor its own use. Limiting access to applications during certain periods of time further reduces the power usage of the device and increases the battery life of the battery-operated device. It will be appreciated that people use the device. When a person uses a device, the person is optionally referred to as a user of the device.

Fig. 10A-10 AAA illustrate an exemplary manner in which an electronic device limits access to a particular application during a particular time period 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 fig. 11A-11I.

Fig. 10A shows an exemplary device 500 having a touch screen 504, such as described with reference to fig. 5A-5H. Touch screen 504 optionally displays one or more user interfaces including various content. In the example shown in fig. 10A, touch screen 504 displays a "limit settings" graphical user interface 1002 for defining one or more application limit settings, as described above with reference to fig. 6A-6D. For example, FIG. 10A illustrates an optional affordance 1004 for defining a "device downtime" (e.g., a limited use mode) during which the device 500 blocks or attempts to block access to certain applications on the device. FIG. 10A illustrates that the selectable device downtime setting affordance 1004 includes information regarding a limited use mode (e.g., the device downtime mode is automatically enabled from 10pm to 6am each day). In some embodiments, the device downtime or limited use mode is a bedtime limited mode for reducing device use during a user-defined bedtime hour.

The affordance 1004 may be selectable to define limited use mode settings or rules, as will now be described. For example, in fig. 10B, selection of the device downtime affordance 1004 is detected (e.g., by tapping of the contact 1003 detected on the device downtime affordance 1004, as shown in fig. 10B). In response to selection of the equipment downtime affordance 1004, the equipment 500 displays an "equipment downtime" graphical user interface 1010, as shown in FIG. 10C.

Fig. 10C illustrates exemplary limited use mode settings or rules. The device downtime screen 1010 optionally includes a switch input affordance 1011 for enabling or disabling implementation of the limited use mode setting, a start affordance 1012 for defining a start time of the limited use mode, an end affordance 1013 for defining an end time of the limited use mode, a day affordance 1014 for defining on what day the limited use mode setting is implemented, a downtime affordance 1015 for defining how the device 500 will implement the limited use mode at the start time (e.g., under a "notify and block" option or a "notify" option, as described with reference to fig. 8 AL-8 AAG), a say affordance 1016 for enabling the limited use mode alert to be spoken (e.g., by audible speech read out of the limited use mode alert or notification), or a do-not-disturb affordance 1017 for enabling the do-not-disturb mode during the limited use mode (e.g., a mode that silences calls and alerts that arrive when the device 500 is locked), as shown in fig. 10C. For example, turning off the switch input affordance 1011 will optionally disable implementation of the limited use mode setting even for the time and day defined by the start affordance 1012, end affordance 1013, and day affordance 1014. In some embodiments, closing the switch input affordance 1011 will save the limited use mode settings or rules defined on the device downtime screen 1010 such that these settings will be restored when the switch input affordance 1011 is re-opened.

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

FIG. 10E illustrates an exemplary day graphical user interface 1020 for defining on what days a limited use mode setting is implemented. The day graphical user interface 1020 optionally includes a daily affordance 1022 (e.g., as defined by a start affordance 1012 and an end affordance 1013 in the device downtime screen 1010, as shown in fig. 10C) for requiring each day of the week to have the same limited use start and end times. In some embodiments, day graphical user interface 1020 includes affordances 1024 a-1024 g for defining different start and end times, respectively, for each day of the week (monday-sunday), as shown in fig. 10E. Enabling daily affordances 1022 optionally inhibits the user from using affordances 1024 a-1024 g to define different start and end times for different days of the week by disabling affordances 1024 a-1024 g, as shown in fig. 10E. In some embodiments, when daily affordances 1022 are enabled, device 500 visually masks affordances 1024 a-1024 g (e.g., by twisting, graying out, fading out these affordances), as shown in fig. 10E. In some embodiments, device 500 discards displaying affordances 1024 a-1024 g when daily affordance 1022 is enabled. In some embodiments, disabling daily affordances 1022 enables a user to define different start and/or end times for different days of the week (e.g., allows the user to define start and/or end times on a daily basis) by enabling affordances 1024 a-1024 g, as shown in fig. 10F. For example, disabling daily affordances 1022 optionally allows the 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, the daily affordance 1022 will be saved on the daily graphical user interface 1020 to affordances 1024 a-1024 g defining different start and end times such that these settings will be restored the next time the daily affordance 1022 is disabled.

In some embodiments, as shown in fig. 10G, the always-allowed affordance 1006 of the limit settings user interface 1002 is selectable to display another user interface for defining a list of applications (e.g., application use whitelist) that are not constrained by the limited use mode rules during the limited use mode. For example, in fig. 10G, a selection of the always-on affordance 1006 is detected (e.g., by tapping of the contact 1003 detected on the always-on affordance 1006, as shown in fig. 10G). In response to selection of the always enabled affordance 1006, the device 500 displays an "always enabled" graphical user interface 1025, as shown in FIG. 10H.

As shown in fig. 10H, the device 500 enables a user to add or remove applications from a list of applications (e.g., application use whitelist 1026, shown in fig. 10H) that are not constrained by the limited use mode rules during the limited use mode, always allow the graphical user interface 1025. For example, FIG. 10H shows a telephony application 1026a, a messaging application 1026b, and a faceTime application 1026c on a whitelist 1026. In some embodiments, graphical user interface 1025 is always permitted to include a selectable removal affordance 1027 adjacent to certain applications listed on whitelist 1026, which when selected by a user, causes device 500 to remove the corresponding application from whitelist 1027 (e.g., subject that particular application to a restricted use mode rule). In some embodiments, certain applications will be permanently on the whitelist 1026. For example, fig. 10H shows a telephony application 1026a that does not have a removal affordance 1027 for removing it from the whitelist 1026—thus, the telephony application 1026a for making or receiving calls on the device 500 is optionally permanently included on the whitelist 1026. In some embodiments, graphical user interface 1025 is always enabled to indicate that an application on whitelist 1026 is not constrained by the restricted use mode rules for communicating with anyone, contacts saved to device 500, or specific contacts saved on device 500 through that particular application during the restricted use mode. For example, fig. 10H shows that communication with anyone through the telephony application 1026a is unrestricted during the limited use mode, communication through the messaging application 1026b is unrestricted during the limited use mode for all contacts stored on the device 500 (but optionally, restricted for others who are not contacts stored on the device 500), and communication through the FaceTime application 1026c is unrestricted for certain designated contacts. In some embodiments, the user is allowed to alter which communications through the whitelist application are not constrained by the limited use mode rules during the limited use mode, as detailed below with reference to fig. 10K-10S.

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

In some implementations, one or more of applications 1026a, 1026b, 1026c, 1026d, and 1029e can be selected 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 a telephony application 1026a is detected (e.g., by a tap of contact 1003 detected on an entry of application 1026a in a whitelist 1026, as shown in fig. 10K). In response to selection of an entry for application 2016a in whitelist 1026, device 500 optionally displays a "phone" communication graphical user interface 1030, as shown in FIG. 10L. The telephony communication graphical user interface 1030 optionally includes two selectable affordances for defining what communications utilizing the telephony application are not constrained by the limited use mode rules during the limited use mode. For example, fig. 10L shows a selectable "anybody" option 1032 that, when selected, allows communication (e.g., both incoming and outgoing communication) with anybody (e.g., whether or not the other party's communication information is stored on device 500) through a telephony application during a limited use mode; a selectable "all contacts" option 1033 that, when selected, allows communication (e.g., both incoming and outgoing communication) with any contacts saved on the device 500 through the phone application during the limited use mode; and a selectable "designate contacts" option 1034 that, when selected, allows the user to define what contacts' communication (e.g., incoming and outgoing communication) is permitted with through the phone application during the limited use mode, as will now be described.

In some implementations, the designated contact option 1034 is selectable to display information defining what contacts' communications (e.g., both incoming and outgoing communications) are allowed through the phone application during the limited use mode. For example, in fig. 10L, selection of the specified contact option 1034 is detected (e.g., by a tap of the contact 1003 detected on the specified contact option 1034, as shown in fig. 10L). In response to selection of the designated contact option 1034, the device 500 displays a permitted contact list 1036 including selectable contacts stored on the device 500 (e.g., contacts 1037a, 1037b, and 1037 c) that, when selected, define what contacts are permitted to communicate with through the phone application during the limited use mode, as shown in fig. 10M. In some embodiments, selection of the designated contact 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 on the device 500 that would then be displayed as a selectable contact in the allowed contact list 1036. For example, in fig. 10M, only communication with contacts a and B is allowed through the phone application during the limited use mode, but communication with contact C is not allowed (e.g., both incoming and outgoing communications).

In some embodiments, the device 500 allows the user to define a daytime allowed contact list of contacts that are allowed to communicate with it through a particular application during daytime hours (e.g., outside of a limited use mode) and a nighttime allowed contact list of contacts that are allowed to communicate with it through that same application during nighttime hours (e.g., during a limited use mode) (e.g., as described above with reference to fig. 10M). For example, FIG. 10N illustrates the detection of a selection of a telephony application 1026a (e.g., by a tap of contact 1003 detected on an entry of application 1026a in a whitelist 1026, as shown in FIG. 10N). In response to selection of an entry for application 2016a in whitelist 1026, 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 daytime affordance 1039a and a selectable nighttime affordance 1039b, as shown in fig. 10O. For example, in fig. 10P, selection of the daytime affordance 1039a is detected (e.g., by tapping of the contact 1003 detected on the daytime affordance 1039a, as shown in fig. 10P). In response to selection of the daytime affordance 1039a, the device 500 displays a "daytime" graphical user interface 1040, as shown in fig. 10Q. In some embodiments, the daytime graphical user interface 1040 works as described above with reference to fig. 10L-10M to define what contacts (e.g., anyone, all contacts, or designated contacts) are allowed to communicate (e.g., both incoming and outgoing communications) through the phone application during the daytime hours (e.g., outside of the limited use mode) (e.g., to define a daytime whitelist). As shown in fig. 10R, selection of the night affordance 1039b is optionally detected (e.g., by tapping of the contact 1003 detected on the night affordance 1039b, as shown in fig. 10R). In response to selection of the night time affordance 1039b, the device 500 displays a "night time" graphical user interface 1042, as shown in FIG. 10S. In some embodiments, the night time graphical user interface 1042 works as described above with reference to fig. 10L-10M to define what contacts (e.g., anyone, all contacts, or designated contacts) are allowed to communicate (e.g., both incoming and outgoing communications) through the phone application during the night hours (e.g., during the limited use mode) (e.g., define a night white list). In some embodiments, the daytime and nighttime whitelists are different, as shown in fig. 10Q and 10S.

In some embodiments, device 500 is a child device (e.g., a device designated as a user of a child, rather than a parent or administrator in a home account), as shown in fig. 10T. If the device 500 is a child device, altering one or more limit settings on the limit settings graphical user interface 1002 is optionally not allowed and/or optionally requires entry of a password (or requires other authentication, as described in this disclosure). In fig. 10T, the password affordance 1008 is optionally permanently switched on for the child device, requiring the user of the device 500 to enter a password to make any changes on the limit settings graphical user interface 1002. For example, in fig. 10U, selection of the device downtime affordance 1004 is detected when the password affordance 1008 is switched on (e.g., by tapping of the contact 1003 detected on the device downtime affordance 1004, as shown in fig. 10U). In response to selection of the device downtime setting affordance 1004, the device 500 displays a password graphical user interface 1044, requiring the user to enter a password before being allowed to make changes to any device downtime setting, as shown in FIG. 10V. In some embodiments, password graphical user interface 1044 is not displayed by device 500 until the device limit settings are changed by the user as described above with reference to fig. 10C-10S (e.g., a user of a child device can view the limit settings, including device downtime and always allow settings, without having to enter a password). In some embodiments, the password required at fig. 10V is different from the password used to log into the device 500 or unlock the device 500 (e.g., is a password unique to the limit setting). In some implementations, to make the change to the limit settings, a biometric feature is required instead of a password (e.g., as described below in process 1100).

In fig. 10W, device 500 is displaying a "home" graphical user interface 1046 in which a user is able to view home usage limits 1048 (e.g., usage limits associated with members of a home account and/or usage limits of devices associated with a home account) and make changes to those home limits (e.g., as described above with reference to fig. 6C-6D). For example, FIG. 10W shows the limits of use 1048 of the parent account 1049a, the mother account 1049b, and the child account 1049 c. In some embodiments, the home settings graphical user interface 1046 is contained within the limit settings interface 1002 (e.g., as described above with reference to fig. 6C-6D).

In some implementations, each of the parent account 1049a, the mother account 1049b, and the child account 1049c can be selected to display a limit setting graphical user interface to make changes to the limit settings associated with each of those accounts. For example, in fig. 10X, selection of the child account 1049c is detected (e.g., by tapping of the contact 1003 detected on the child account 1049c, as shown in fig. 10X). In response to 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, to make a change to the limit settings associated with the child account 1049c on the child limit settings graphical user interface 1002 by the device 500 (e.g., a parent device), the parent is required to enter a password (or provide other limit settings authentication, such as facial recognition). For example, in fig. 10Z, a selection of the always-on affordance 1006 is detected (e.g., by tapping of the contact 1003 detected on the always-on affordance 1006, as shown in fig. 10Z). In response to selection of the always enabled affordance 1006, the device 500 displays a password graphical user interface 1044 asking the user to enter a password before being allowed to make changes to any limit settings associated with the child account, as shown in FIG. 10 AA. In some embodiments, the password graphical user interface 1044 is not displayed by the device 500 until the device limit settings are changed by the user, as described above with reference to fig. 10C-10S (e.g., a user of a parent device can view limit settings of a child device, including device downtime and always allowed settings, without having to enter a password). In some embodiments, the password required at fig. 10AA is different from the password used to log into or unlock the device 500 or child device (e.g., is a password unique to the limit setting). In some implementations, to make the change to the limit settings, a biometric feature is optionally entered instead of a password (e.g., as described below in process 1100).

Fig. 10AB illustrates the time display home screen 1050 before the child device 500 has changed its limit settings remotely (e.g., by a parent device, as described above with reference to fig. 10W-10 AA). Fig. 10AC shows the time display main screen 1050 after the child device 500 has changed the change to the limit setting remotely (e.g., by the parent device, as described above with reference to fig. 10A-10S and 10W-10 AB). In some embodiments, the device 500 generates a notification 1052 to indicate to the user of the child device that its device downtime limit has been remotely altered, as shown in fig. 10 AC. For example, notification 1052 in the AC of fig. 10 shows that new contacts are added to the daytime permitted contact list of device 500, and the start time of the restricted use mode is altered by the parent (e.g., by the mother, as described above with reference to fig. 10A-10Q) associated with the home account.

Fig. 10AD shows the device 500 displaying the main screen 1050 at a time before the start time of the limited use mode. In fig. 10AD, 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 a limited use mode (and because no individual or category use limit is set or reached, as described with reference to method 900), the user is able to launch any application associated with icons 424, 426, 416, 432, 434, 436, 440, 442, 454, 446, 450, and 452 without limitation.

In some embodiments, the device 500 will display an alert before the device enters the limited use mode. For example, as shown in fig. 10AE, the device 500 is displaying a notification 1054 indicating that device downtime (e.g., limited use mode) will begin after 30 minutes. In some embodiments, the notification 1054 will include a selectable affordance 1055 for dismissing the notification 1054, which when selected by the user, causes the notification 1054 to disappear. In some implementations, the notification 1054 will automatically disappear (e.g., shut down without user input) after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds).

Fig. 10AF illustrates that the device 500 displays the home screen 1050 at the beginning of the limited use mode under the "notify" option of the device downtime settings (e.g., as described above with reference to fig. 8 AL-8 AP and fig. 10D). In some embodiments, device 500 may be a parent device (e.g., a device associated with a parent on a home account) or a stand-alone device (e.g., a device not associated with any home account). The device 500 optionally visually masks the home screen 1050 (e.g., blurs, grays out, or visually changes the home screen) at the beginning of the limited use mode, as shown in fig. 10 AF. In some embodiments, the device 500 is displaying a graphical user interface (e.g., an application graphical user interface, a notification history graphical user interface, etc.) that is not the home screen 1050 at the beginning of the limited use mode, and the device 500 visually masks the graphical user interface (e.g., obscures, grays, or visually changes the graphical user interface) at the beginning of the limited use mode. In some embodiments, the device 500 displays an interpretation 1056 indicating that the limited use mode has begun and an undo affordance 1057. For example, in FIG. 10AF, selection of the dismissal affordance 1057 is detected (e.g., by tapping of the contact 1003 detected on the dismissal affordance 1057, as shown in FIG. 10 AF). In response to selecting the dismissal affordance 1057, the apparatus 500 ceases to display the dismissal affordance 1057, displays the delay affordance 1058, and ignores the affordance 1059, as shown in FIG. 10 AG. In some implementations, user selection of the delay-enabled representation 1058 allows the user to delay the start of the limited-use mode (without altering the actual time setting of the limited-use mode such that the limited-use mode will continue to be triggered at a previously defined time in the future) by a predefined or user-defined amount of time (e.g., 5 minutes, 15 minutes, 30 minutes) for extending the start of the limited-use mode (e.g., as described below with reference to method 1100). In some embodiments, the user selection of the inattention enabled representation 1059 allows the user to relinquish the beginning of the limited use mode for that particular day (without altering the actual time setting of the limited use mode such that the limited use mode will continue to be triggered in the future at a previously defined time) (e.g., as described below with reference to method 1100). In some embodiments, the device 500 stops displaying the extension 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 any portion of the home screen 1050 (except for the explanation 1056, the extension affordance 1058, and the ignore affordance 1059). Under the "notification option," a parent device (e.g., a device associated with a parent on a home account) or a standalone device (e.g., a device not associated with any home account) does not require the user to enter any authentication (e.g., a password) to extend or ignore the limited use mode on the device. For example, fig. 10AH shows the parent device 500 displaying the home screen 1050 under the "notify option" after the user selects the extended affordance 1058 or ignores the affordance 1059. Because the device 500 in fig. 10AH is not in the limited use mode (e.g., because it has been extended), the user is able to launch any application associated with icons 424, 426, 416, 432, 434, 436, 440, 442, 452, 446, and 450 without limitation. Extending or ignoring the beginning of the limited use mode optionally enables any application to be launched or any application function to be performed that may otherwise have been restricted (e.g., accessing a desktop applet or website associated with those applications, receiving a notification, recommending those applications to a user, etc.).

Fig. 10AI illustrates the device 500 displaying the home screen 1050 at the beginning of the limited use mode under the "notify and block" option of the device downtime settings (e.g., as described above with reference to fig. 8 AQ-8 AAG and fig. 10D). In some embodiments, device 500 may be a parent device (e.g., a device associated with a parent on a home account) or a stand-alone device (e.g., a device not associated with any home account). The device 500 optionally visually masks the home screen 1050 (e.g., blurs, grays out, or visually changes the home screen) at the beginning of the limited use mode, as shown in fig. 10 AI. In some embodiments, the device 500 is displaying a graphical user interface (e.g., an application graphical user interface, a notification history graphical user interface, etc.) that is not the home screen 1050 at the beginning of the limited use mode, and the device 500 visually masks the graphical user interface (e.g., obscures, grays, or visually changes the graphical user interface) at the beginning of the limited use mode. In some embodiments, the device 500 displays an interpretation 1056 indicating that the limited use mode has begun and an undo affordance 1057. For example, in fig. 10AI, selection of the dismissal affordance 1057 is detected (e.g., by tapping of the contact 1003 detected on the dismissal affordance 1057, as shown in fig. 10 AI). In response to selecting the dismissal affordance 1057, the apparatus 500 stops displaying the dismissal affordance 1057 and displays the delay affordance 1058 and the ignore affordance 1059, as shown in fig. 10 AJ. In some implementations, user selection of the delay-enabled representation 1058 allows the user to delay the start of the limited-use mode (without altering the actual time setting of the limited-use mode such that the limited-use mode will continue to be triggered at a previously defined time in the future) by a predefined or user-defined amount of time (e.g., 5 minutes, 15 minutes, 30 minutes) for extending the start of the limited-use mode (e.g., as described below with reference to method 1100). In some embodiments, the user selection of the inattention enabled representation 1059 allows the user to relinquish the beginning of the limited use mode for that particular day (without altering the actual time setting of the limited use mode such that the limited use mode will continue to be triggered in the future at a previously defined time) (e.g., as described below with reference to method 1100). In some embodiments, the device 500 stops displaying the extension 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 any portion of the home screen 1050 (except for the explanation 1056, the extension affordance 1058, and the ignore affordance 1059). Under the "notify and block option," a parent device (e.g., a device associated with a parent on a home account) or a standalone device (e.g., a device not associated with any home account) optionally requires the user to enter an authentication (e.g., a password) to extend or ignore the limited use mode on the device. For example, in response to selection of the delay presentation enable representation 1058 or the ignore presentation enable representation 1059 in FIG. 10AJ under the "Notification and block option," the device 500 displays a password graphical user interface 1044 that requires the user to enter a password before the limited use mode can be extended or ignored, as shown in FIG. 10 AK. In some embodiments, the password required at fig. 10AK is different from the password used to log into the device 500 or unlock the device 500 (e.g., is a password unique to the limit setting). In some implementations, to make the change to the limit settings, a biometric feature is entered instead of a password (e.g., as described below in process 1100).

Fig. 10AL shows the device 500 displaying the home screen 1050 after the user has entered the correct password in the password graphical user interface 1044 of fig. 10AK under the "notify and block option". Because the device 500 in fig. 10AL is not in a limited use mode (e.g., because it has been extended), the user is able to launch any application associated with icons 424, 426, 416, 432, 434, 436, 440, 442, 452, 446, and 450 without limitation. The beginning of the extended limited use mode optionally enables any application to be launched or any application function to be performed that may otherwise have been limited (e.g., accessing a desktop applet or website associated with those applications, receiving notifications, recommending those applications to the user, etc.).

Fig. 10AM illustrates the child device 500 displaying the home screen 1050 at the beginning of the limited use mode of the device downtime setting (e.g., as described above with reference to fig. 10D). The child device 500 optionally visually masks the home screen 1050 (e.g., blurs, grays, or visually changes the home screen) at the beginning of the limited use mode, as shown in fig. 10 AM. In some embodiments, the child device 500 is displaying a graphical user interface (e.g., an application graphical user interface, a notification history graphical user interface, etc.) that is not the home screen 1050 at the beginning of the limited use mode, and the child device 500 visually masks the graphical user interface (e.g., obscures, grays, or visually changes the graphical user interface) at the beginning of the limited use mode. In some embodiments, the device 500 displays an interpretation 1056 indicating that the limited use mode has begun and an undo affordance 1057. For example, in fig. 10AM, selection of the dismissal affordance 1057 is detected (e.g., by tapping of the contact 1003 detected on the dismissal affordance 1057, as shown in fig. 10 AM). In response to selecting the dismissal affordance 1057, the device 500 ceases to display the dismissal affordance 1057 and displays a selectable affordance 1060 for requesting more time on the device 500 (e.g., extending the start time of the limited use mode) before the limited use mode is implemented and a selectable affordance 1062 for requesting more time on another device (e.g., on a parent device) (e.g., as described above with reference to fig. 8 AT-8 AAC), as shown in fig. 10 AN. In some embodiments, selecting either affordance 1060 or affordance 1062 allows the parent to delay the start of the limited use mode without altering the actual time setting of the limited use mode so that the limited use mode will continue to be triggered in the future at a previously defined time. For example, in FIG. 10AO, selection of affordance 1062 is detected (e.g., by tapping of contact 1003 detected on affordance 1062, as shown in FIG. 10 AO). In response to selecting the affordance 1026, the device 500 initiates a process for requesting more time on another device (e.g., as described above with reference to fig. 8AW through 8 AAC). For example, a process for requesting more time on another device optionally sends a message 1070 (user editable) to the parent device in a messaging user interface having an affordance for rejecting the request (e.g., affordance 1068 a), affordances for extending the start time of the limited use mode for a predetermined period of time (e.g., affordances 1068b and 1068 c), and affordances for customizing the extended period of time (e.g., affordance 1068 d) (e.g., as described above with reference to fig. 8 AAA-8 AAC), as shown in fig. 10 AP. In some embodiments, a process for requesting more time on another device sends a notification 1066 with an affordance for rejecting the request (e.g., affordance 1068 a), affordances for extending the start time of the limited use mode for a predetermined period of time (e.g., affordances 1068b and 1068 c), and affordances for customizing the extended period of time (e.g., affordance 1068 d), as shown in fig. 10 AQ.

Fig. 10AR shows the device 500 displaying the main screen 1050 at a time before the start time of the limited use mode. In fig. 10AR, 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 a limited use mode, the user is able to launch any application associated with icons 424, 426, 416, 432, 434, 436, 440, 442, 454, 446, 450, and 452 without limitation.

Fig. 10AS shows that touch screen 504 displays home screen 1050 during a limited use mode. In some embodiments, the device 500 blocks or attempts to block access to all applications on the device during the limited use mode, except for applications included on the application use whitelist. In some implementations, icons corresponding to restricted applications (e.g., applications that are restricted from using whitelists on applications during the restricted use mode) are changed during the restricted use mode. For example, icons 424, 432, 436, 442, 454, 450, and 452 correspond to limited applications and are hidden (e.g., distorted, grayed out, faded out, and/or visually altered) during a limited use mode, AS shown in fig. 10 AS. In some embodiments, the placeholder generic indication (e.g., lock icon) 1070 is placed over an icon corresponding to the restricted application or partially over an icon corresponding to the restricted application, AS shown in fig. 10 AS. The occupancy generic indication (e.g., lock icon) 1070 optionally replaces any unread notification indication corresponding to the restricted application (e.g., AS shown in fig. 10 AS). In some implementations, the placeholder generic indicator (e.g., lock icon) is placed on or near text associated with the application icon of the restricted application (e.g., beside the name of the application).

In some implementations, icons displayed on the home screen 1050 can be selected to launch applications corresponding to those icons (e.g., during normal operation outside of the limited use mode). During the limited use mode, the device 500 attempts to block access to the limited application under the "notify" option (e.g., as described above with reference to fig. 10C and 10 AF). For example, under the "notify" option, a user of device 500 (e.g., a parent device or a standalone device) is optionally able to select an icon corresponding to a restricted application during a restricted use mode. For example, in fig. 10AT, selection of icon 424 (corresponding to the restricted message application) is detected (e.g., by a tap of contact 1003 detected on icon 424, as shown in fig. 10 AT). In response to selecting icon 424, device 500 optionally visually masks home screen 1050 (e.g., blurs, grays, or visually changes the home screen), as shown in fig. 10 AU. In some embodiments, the device 500 displays an interpretation 1056 indicating that access to the message application is restricted during the restricted use mode and a dismissed affordance 1057. For example, in fig. 10AU, selection of the dismissal affordance 1057 is detected (e.g., by tapping of the contact 1003 detected on the dismissal affordance 1057, as shown in fig. 10 AU). In response to selecting the dismissal affordance 1057, the apparatus 500 ceases to display the dismissal affordance 1057 and displays the make affordance 1072, as shown in fig. 10 AV. In some embodiments, user selection of the affordance 1072 allows the user to access a limited-use message application (e.g., as described below with reference to method 1100) during a limited-use mode, as shown in fig. 10 AW. In some embodiments, the device 500 stops displaying the affordance 1072 after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds) or when the user taps any portion of the home screen 1050 (in addition to interpreting 1056 and affordance 1072).

The device 500 (e.g., a parent or standalone device) attempts to block access to the restricted application during the restricted use mode under the "notify and block" option (e.g., as described above with reference to fig. 10C and 10 AI-10 AL). In some embodiments, under the "notify and block" option, the user of device 500 is optionally able to select an icon corresponding to a restricted application during a restricted use mode. For example, in fig. 10AX, selection of icon 424 (corresponding to the restricted message application) is detected (e.g., by a tap of contact 1003 detected on icon 424, as shown in fig. 10 AX). In response to selecting icon 424, device 500 optionally visually masks home screen 1050 (e.g., blurs, grays, or visually changes the home screen) and displays password graphical user interface 1044, asking the user to enter a password to access the limited-message application during the limited-use mode, as shown in fig. 10 AY. In some embodiments, the password required at fig. 10AY is different from the password used to log into the device 500 or unlock the device 500 (e.g., is a password unique to the limit setting). In some implementations, to make the change to the limit settings, a biometric feature is entered instead of a password (e.g., as described below in process 1100).

In some embodiments, the child device 500 attempts to block access to the restricted application during the restricted use mode. In some embodiments, the user of child device 500 is able to select an icon corresponding to a restricted application during a restricted use mode. For example, in fig. 10AZ, selection of icon 424 (corresponding to the restricted message application) is detected (e.g., by tapping of contact 1003 detected on icon 424, as shown in fig. 10 AZ). In response to selecting icon 424, child device 500 optionally visually masks home screen 1050 (e.g., blurs, grays, or visually changes the home screen) and displays a selectable affordance 1082 for requesting access to the message application during the limited use mode on child device 500 (e.g., by requiring the parent to directly enter a password on device 500) and a selectable affordance 1084 for requesting access to the message application during the limited use mode on another device (e.g., requiring access to be granted from the parent device via AN iMessage or notification) (e.g., as described above with reference to fig. 8 AT-8 AAC and fig. 10 AN-10 AQ), as shown in fig. 10 AAA.

Fig. 11A-11I are flowcharts illustrating a method 100 of selectively restricting access to an application 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 in connection with fig. 1A-1B, fig. 2-3, fig. 4A-4B, and fig. 5A-5H. Some operations in method 1100 are optionally combined, and/or the order of some operations is optionally changed.

As described below, the method 1100 provides a way to selectively limit access to applications on an electronic device during a limited use mode. The method reduces the use of the electronic device during a particular period of time without requiring the user to monitor his own use. For battery-operated electronic devices, limiting access to applications during certain periods of time saves power and increases the time between battery charges.

In some embodiments, an electronic device (e.g., a mobile phone, tablet, etc., such as device 100, device 300, or device 500) in communication with a display and one or more input devices (e.g., a mobile device including a touch screen, such as device 500 including touch screen 504, a computer or tablet, including one or more of a keyboard, a mouse, a touch pad, and a touch screen, such as touch screen 504, a wearable device, such as a smartwatch including a touch screen, or a set-top box in communication with a television and an input device (e.g., a remote control) receives (1102) a sequence of one or more inputs (e.g., from the one or more input devices of the electronic device or from a second electronic device or different from the electronic device) for defining one or more time windows associated with a restricted use mode during which access to one or more applications on the electronic device is restricted, such as in fig. 10A-10E. In some embodiments, the limited use mode is a bedtime limited use mode. In some embodiments, the electronic device is a child device, and the one or more inputs are received from a parent device in communication (e.g., wireless communication) with the child device and associated with the child device (e.g., user accounts of both the parent device and the child device are associated with a household or other group account). For example, a user of the electronic device defines a few hours of the day (e.g., 10pm to 5 am) as a bedtime limited use mode during which the electronic device blocks or attempts to block access to all applications on the electronic device, in some embodiments except applications included on the application whitelist. In some embodiments, the user defines the above-described time window and does not specify any particular application for which access is to be restricted. In such embodiments, the electronic device optionally defaults to limiting or attempts to limit the use of all applications during the limited use mode except for the whitelisted application.

When the one or more time windows associated with the limited use mode are defined and during the one or more time windows associated with the limited use mode (1104), the electronic device optionally receives (1106), via the one or more input devices, input for launching a first application of a plurality of applications installed on the electronic device (e.g., input for opening and/or using the application on the electronic device or input for continuing to use the application on the electronic device while the one or more time windows are in effect (e.g., the application is being used while the limited use mode is in effect)), such as in fig. 10 AT. In some embodiments, in response to receiving input (1108) to launch the first application, in accordance with a determination that the first application is not included in an application use whitelist (e.g., a list of applications that are not subject to restricted access during a restricted use mode (e.g., can be fully or partially accessed during a bedtime restricted use mode)), the electronic device restricts (1110) access to the first application (e.g., inhibits application launch, restricts functionality of the application, or requires further action by a user to launch the application, such as displaying a dialog box indicating the bedtime restriction and requiring confirmation from the user to continue the application when the user attempts to launch the application), such as in fig. 10 AT-10 AAA. In some embodiments, in response to receiving input to launch the first application (1112), in accordance with a determination that the first application is included in the application use whitelist, the electronic device provides access to the first application (e.g., normally launches the application as if the limited use mode were not valid), such as in fig. 10I.

In some embodiments, the one or more time windows associated with the bedtime limited use mode are preset by a user of the electronic device or are set remotely by a user of another electronic device in communication with the electronic device. In some embodiments, no bedtime usage restriction occurs when the application is started outside of the bedtime limited use mode (e.g., the application is started normally as if the limited use mode were not valid). In some implementations, access is provided to the first application under certain restrictions (e.g., the application may be launched but have limited functionality during the bedtime limited mode). For example, the telephony application is optionally on a whitelist for communicating with a particular contact (e.g., a relative), and the telephony application is launched, restricting communications with other contacts. In some embodiments, the electronic device enters the restricted use mode while a restricted application (e.g., an application that is not on the application use 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" limit option, the electronic device displays a pop-up indication (e.g., a display that masks the running application) on the running application that indicates that application usage is currently limited (e.g., due to the bedtime limit being valid), and the indication optionally includes one or more affordances that, when selected, allow the user to continue using the application. Under the "notify and block" limit option, the electronic device blocks the user from using the application (e.g., obfuscates the application), and optionally displays a pop-up notification on the running application (e.g., masks the display of the running application), including an indication that application usage is currently limited (e.g., due to the bedtime limit being valid), and that the indication requires authentication credentials (e.g., passwords, biometric features, or consent from a parent device/account) to continue using the application. Detecting biometric features optionally includes detecting a face of the user with a depth camera or another sensor. The limited use modes described herein are optionally the same or similar to the limited use modes described with reference to methods 700, 900, and 1300. The above-described manner of selectively restricting access to applications during bedtime limited use modes allows the electronic device to effectively and selectively restrict use of certain applications during certain periods of time, which reduces use of the electronic device during those periods of time, which in turn reduces power consumption and improves battery life of the device.

In some embodiments, the one or more time windows associated with the restricted use mode (e.g., the bedtime restricted use mode) (1116) is a first one or more time windows of a first day of the week, and the one or more time windows associated with the restricted use mode is a second one or more time windows of a second day of the week different from the first one or more time windows (e.g., different days can have different settings (time, use limits, etc.) of the restricted use mode (1116), such as in fig. 10F. For example, the time of the restricted use mode of the bedtime during which the electronic device blocks or attempts to block access to certain applications on the electronic device is defined differently for different days of the week (e.g., 10pm to 5am for monday, 11pm to 6am for monday, 9pm to 5am for weekend, 11pm to 7am for example)), the different days of the bedtime of the week is defined as a different time of the bedtime of the day on a day of the day, such as to allow for a more efficient update of the user mode of the user device (e.g., reduced overall user-interface of the user-interface, thus reducing the user's consumption of the restricted use time of the user's device).

In some embodiments, in accordance with a determination that the current time on the electronic device is a threshold time (e.g., 5 minutes, 10 minutes, 1 hour, or any time period before the start of the limited use mode) before the one or more time windows associated with the limited use mode are defined, the electronic device presents (1118) an indication (e.g., text, image, sound, haptic and/or tactile output, etc.) that the one or more time windows associated with the limited use mode are approaching (e.g., a notification indicating that the limited use mode (e.g., bedtime limited use mode) will be effective within the threshold time (e.g., 5 minutes, 10 minutes, 1 hour, or any time period), such as in fig. 10 AE. In some examples, the threshold time is defined by a user. In some embodiments, the notification includes text, images, and/or sound. In an embodiment, the notification includes a haptic and/or tactile output indication. The above-described manner of informing the user that the limited use mode will take effect soon makes the user-device interface more efficient (e.g., the user does not have to monitor time, providing the user with an opportunity to complete tasks currently being performed on the device, and prompting the user to stop using the device in anticipation of the limited use mode, thereby reducing user-provided input to the device (e.g., input to update the bedtime limited use mode)), which allows the electronic device to effectively reduce overall use of the electronic device, which in turn reduces power consumption and improves battery life of the device.

In some embodiments, the indication of the one or more time window approximations associated with the limited use mode includes a visual indication (1120), and the visual indication includes an affordance for delaying initiation of the limited use mode beyond the one or more time windows associated with the limited use mode (e.g., allowing a user to delay initiation of the limited use mode (without altering an actual time setting of the limited use mode such that the limited use mode will continue to be triggered at a previously defined time in the future), such as in fig. 10 AE-10 AQ, 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, the affordance allows the user to manually alter the start time of the limited use mode (e.g., manually enter another start time.) in some embodiments, the electronic device allows the user to delay the start of the limited use mode any time up to and including the start of the limited use mode (e.g., allow the user to eliminate the limited use mode for a period of time or for the remainder of the day.) the delay of the start of the limited use mode optionally enables any application to be launched or any application function to be performed that may have otherwise been limited (e.g., access to a desktop applet or website associated with those applications, receive notifications, recommend those applications to the user, etc.), if the electronic device is a child device in a home account (e.g., a device designated as a user of a child, rather than a parent or administrator in the home account), the displayed notification optionally includes an affordance for requesting permission from the adult/parent device in the home account for an extended limited use mode (e.g., 15 minutes, 30 minutes, 1 hour, etc., extending the beginning of the limited use mode). In this case, selecting a request in the notification optionally causes the notification to be delivered to one or more (or all) of the parent devices associated with the home account, and the electronic device extends the start time of the limited use mode when permission is granted by at least one of the parent devices. In some embodiments, the affordance allows the user to block the electronic device from entering the limited-use mode. In some embodiments, application usage beyond the allowable limit (e.g., even if approved due to time extension) is optionally indicated in the dashboard user interface described above with reference to method 700 (e.g., AS shown in fig. 6L-6P, 6 AE-6 AH, 6 AO-6 AS, and 6 AU). The manner of providing an affordance for a user to extend the beginning of a limited use mode described above makes the user-device interface more efficient (e.g., the user does not have to monitor time, provides the user with an opportunity to extend the beginning time of the limited use mode to complete tasks currently being performed on the device, and prompts the user to stop using the device in anticipation of the limited use mode, thereby reducing user-provided input to the device (e.g., input to update the bedtime limited use mode)), which allows the electronic device to effectively reduce overall use of the electronic device, which in turn reduces power consumption and improves battery life of the device.

In some embodiments, outside of the 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 (e.g., icons of applications not on the application whitelist are normally displayed outside of the limited use mode, such AS in color, not grayed out, etc.), such AS in fig. 10AR, and during the one or more time windows associated with the limited use mode, the 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 (e.g., icons of applications not on the application whitelist are displayed during the limited use mode in a different manner than when outside of the limited use mode, such AS in fig. 10 AS). For example, for those applications that are not included on the application whitelist, the icons of those applications are optionally changed to be grayed out in the limited use mode (as compared to colors outside of the limited use mode) and/or the placeholder generic indicators are displayed on the icons of those applications in the limited use mode (or partially on any portion of the icons of those applications). In some implementations, the placeholder generic indicator (e.g., lock icon) is placed on or near text associated with the application icon. In some embodiments, when the limited use mode is not active, the application icons include one or more visual indications of notifications associated with those applications (e.g., a designator indicating a portion of the overlay icon that received a number of unread notifications in the application). In such embodiments, for those applications that are not included in the application whitelist, those visual indications are removed, grayed out, have the number of notifications removed therefrom, are replaced with a placeholder generic indication (e.g., a lock icon), or are otherwise changed such that the notification status (e.g., the number of notifications) of those applications is no longer conveyed by those indications. In some embodiments, all applications that are not on the application usage whitelist are displayed with a lock icon (in embodiments where the application icon in the past included a visual indication of the notification of the application, the lock icon replaces the notification indication). In some embodiments, the icons of the applications on the application whitelist are displayed identically (e.g., in color, no graying, free access, etc.) both during the limited use mode and outside the limited use mode. The above-described manner of differently displaying applications that are restricted during the restricted use mode allows a user to determine which applications are restricted, which allows the electronic device to effectively and selectively restrict the use of a particular application during certain periods of time by providing an indication of what applications the user has or does not have access to during the restricted use mode, which reduces the use of the electronic device during those periods of time, which in turn reduces power consumption and improves the battery life of the device.

In some embodiments, restricting access to the first application includes the electronic device presenting (1126) an indication that access to the first application is restricted (e.g., displaying a visual indication on a display, playing sound with a speaker associated with the electronic device, generating a haptic and/or tactile output, etc., indicating that the application is restricted (e.g., a notification)), such as in fig. 10 AU. Optionally, the indication includes (1128) an affordance (e.g., a graphical user interface element, link, or soft button that allows a user to access the restricted application during the restricted use mode) selectable to provide access to the first application without requiring authentication credentials, such as in fig. 10 AU-10 AV. In some implementations, different applications are associated with different restriction options that are valid during the restricted use mode. For example, the electronic device optionally allows one or more applications to be associated with a "notification" limit option. If the user attempts to launch an application associated with a "notification" restriction (e.g., by selecting an icon for the application from the home screen of the electronic device during a restricted use mode, and assuming the application is not included in the application whitelist), the electronic device optionally displays a pop-up indication indicating that application use is currently restricted (e.g., because the bedtime restriction is in effect). The pop-up notification optionally includes one or more affordances that, when selected, allow the user to continue to the application without entering any authorized credentials (e.g., open the application without entering an "ignore for the day" affordance of an administrator or other credential). The above-described manner of informing the user that the application is restricted during the restricted use mode, but gives the user the option to access the application when needed, allows the electronic device to effectively restrict the use of certain applications during certain periods of time, while allowing the user to perform the necessary tasks on the electronic device, which reduces the use of the electronic device during those periods of time, which in turn reduces power consumption and improves the battery life of the device.

In some embodiments, restricting access to the first application includes the electronic device presenting (1130) an indication that access to the first application is restricted, such as in fig. 10 AU. Optionally, the indication includes (1132) an affordance selectable to provide access to the first application when authentication credentials are required (e.g., displaying a visual indication on a display, playing sound with a speaker associated with the electronic device, generating a haptic and/or tactile output, etc., indicating that the application is restricted (e.g., notified)), such as in fig. 10 AV. In some embodiments, the electronic device allows one or more applications to be associated with a "notify and block" limit option. If the user attempts to launch an application associated with a "notify and block" restriction (e.g., by selecting an icon for the application from the home screen of the electronic device during a restricted use mode, and assuming the application is not included in the application whitelist), the electronic device blocks the application launch and optionally displays a pop-up indication indicating that application use is currently restricted (e.g., because the bedtime restriction is in effect). In some embodiments, the pop-up indication requires authentication credentials (e.g., a password, a biometric feature, or consent from a parent device/account) to access the application. Detecting biometric features optionally includes detecting a face of the user with a depth camera or another sensor. If the electronic device is a child device in the home account (e.g., a device designated as a user of the child, rather than a parent or administrator in the home account), the displayed notification optionally includes an affordance for requesting permission from an adult/parent device in the home account for accessing the application during the limited use mode. In this case, the request in the selection notification optionally causes the notification to be delivered to one or more (or all) parent devices associated with the home account, and the electronic device allows access to the application when permission is granted (e.g., at least one of the parent devices or with a password at the child device). In some embodiments, the parent is required to enter a password at the parent device to allow access to the restricted application on the child device from the parent device. The above-described manner of blocking application launch and informing the user that the application is restricted during the restricted use mode allows the electronic device to effectively limit the use of certain applications during certain periods of time, which reduces the use of the electronic device during those periods of time, which in turn reduces power consumption and improves the battery life of the device.

In some examples, in accordance with a determination that the electronic device is not a child device (e.g., is not a child device in a home account (e.g., is a parent device in a home account), or is not associated with a home account at all), selection of the affordance results in (1134) a request to enter a password to access the first application, such as in fig. 10 AY. In some embodiments, determining that the electronic device is not a child device is based on determining that the electronic device is a parent device (e.g., based on categorization of a user account associated with the electronic device or an option selected on the electronic device). For example, determining that the electronic device is a parent device is optionally based on determining that a user account associated with the electronic device (e.g., a user currently logged into the device) is categorized as a parent account. In some embodiments, determining that the electronic device is a parent device is optionally based on determining that the electronic device is set as a parent device in a setting of the device (e.g., set at initial setting of the device). In some embodiments, the request for entry of the password is a pop-up notification, optionally including one or more affordances that, when selected, only allow the user to proceed to the application if the correct authentication credentials (e.g., password, biometric feature, or consent from a parent device/account) are provided. Detecting biometric features optionally includes detecting a face of the user with a depth camera or another sensor. In some embodiments, the affordance includes one or more of a soft button or an input field for a user id, password, and/or password. For example, if the device is not a child device in a home account (e.g., is a parent device in a home account) or is not associated with a home account at all, the electronic device optionally requests the user to enter credentials (e.g., user id and/or password, password) of a user account associated with the electronic device (e.g., user id and/or password associated with a profile used to configure the device). In some implementations, credentials (e.g., user id and/or password, password) are different from credentials used to access the electronic device (e.g., a password different from a password used to "unlock" the device and/or login to the device). In this way, a user (e.g., child) that is not the device owner (e.g., parent) will not be able to bypass the limited use mode if no auxiliary password is entered.

In some examples, in accordance with a determination that the electronic device is a child device (e.g., based on a categorization of a user account associated with the electronic device or an option selected on the electronic device), selection of the affordance causes (1136) the display to present a first affordance requiring entry of a password (e.g., a parental control password different from a password used to unlock the device or to access a user account associated with device operation) to access the first application, and a second affordance initiating a process when selected for requesting access to the first application from a parent device (e.g., initiating a process for requesting more time from a parent device in a home account), such as in fig. 10 AM-10 AQ. For example, determining that the electronic device is a child device is optionally based on determining that a user account associated with the electronic device (e.g., a user currently logged into the device) is categorized as a child account. In some embodiments, determining that the electronic device is a child device is optionally based on determining that the electronic device is set as a child device in a setting of the device (e.g., set at initial setting of the device). In some embodiments, the process will send a message (e.g., a text message or any other alert on the parent device, an email request to an email account associated with the parent) to the parent device to request access to the first application. The process will then either allow the parent to grant access to the restricted application to the child device (e.g., the parent can choose to allow the child device access to the restricted application during 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 password and/or an affordance for initiating a process for requesting access to the first application. In some implementations, the password is a different parental control password or use password than the password used to unlock the electronic device. As such, the child optionally cannot bypass the restricted access mode, but the parent optionally can enter a password to allow the electronic device to access the first application. In some embodiments, the parent is required to enter a password at the parent device to allow access to the restricted application on the child device from the parent device. The above-described manner of informing the user that the application is restricted during the restricted use mode, but that the user is enabled to access the options of the application when needed, allows the electronic device to effectively restrict the use of certain applications during certain periods of time, while allowing the user to perform the necessary tasks on the electronic device, which reduces the use of the electronic device during those periods of time, which in turn reduces power consumption and improves the battery life of the device.

In some embodiments, the electronic device receives (1138), via the one or more input devices, a sequence of one or more inputs for activating or deactivating the implementation of one or more limited-use mode restrictions, including the one or more time windows associated with the limited-use mode (e.g., manually opening or closing the implementation of the limited-use mode on the electronic device according to the limited-use mode restrictions during the one or more time windows associated with the limited-use mode), such as in fig. 10C. For example, implementation of a restricted use mode rule that closes use limits defined during several hours (e.g., one or more time windows associated with the restricted use mode) from 10pm to 7am disables those use limits during several hours (e.g., during a holiday) from 10pm to 7 am. In contrast, opening the same restricted use mode rule enforcement enables those use restrictions during several hours, 10pm to 7 am. In some implementations, enforcement of the restricted use mode rule may be switched on or off during or outside of the one or more time windows associated with the restricted use mode (e.g., controlling whether the electronic device will enter (if switched on outside of the one or more time windows) or exit (if switched off during the one or more time windows) the restricted use mode during the one or more time windows associated with the restricted use mode). In some embodiments, the electronic device stores the usage restriction settings (e.g., user-defined start time, end time, whitelist, etc.) when the implementation of the limited use mode is turned off, such that the usage restriction settings are maintained for the limited use mode to be turned on at a time. For example, when the enforcement of the limited-use mode rules is turned back on (after having been turned off), the electronic device optionally enforces the limited-use mode restriction according to the same limited-use mode rules that have been set before the limited-use mode was turned off (e.g., enforces the limited-use mode during several hours of 10pm to 7am when the limited-use mode is turned back on). In some embodiments, in accordance with a determination that the enforcement of the one or more limited-use mode restrictions has been turned on, the electronic device enforces (1140) the one or more limited-use mode restrictions (e.g., operates the electronic device outside of or in the limited-use mode (according to limited-use mode rules)), such as in fig. 10C. For example, during a limited use mode, the electronic device operates to prohibit the limited application from launching, limit the functionality of the limited application, and require further action by the user to launch the limited application, such as displaying a dialog box indicating a bedtime limit and requiring further confirmation from the user to continue to the application when the user attempts to launch the limited application. In some implementations, access is provided to the first application under certain restrictions (e.g., the application may be launched during bedtime limited mode, but with limited functionality). For example, the telephony application is optionally on a whitelist for communicating with a particular contact (e.g., a relative), and the telephony application is launched, restricting communications with other contacts.

In some embodiments, in accordance with a determination that the implementation of the one or more limited-use mode restrictions has been turned off, the electronic device relinquishes (1142) the implementation of the one or more limited-use mode restrictions (e.g., operates the electronic device outside of the limited-use mode whenever the implementation of the limited-use mode has been turned off, regardless of whether the current state (e.g., current time) of the electronic device would have otherwise caused the device to operate in the limited-use mode), such as in fig. 10C and 10 AH. For example, outside of the limited use mode, the electronic device allows normal launching of the application as if the limited use mode were not valid. In some embodiments, no bedtime usage restriction occurs when the application is started outside of the bedtime limited use mode (e.g., the application is started normally as if the limited use mode were not valid). In some embodiments, the electronic device provides a toggle key for toggling the implementation of the limited use mode on or off. Thus, even if the current time is within the one or more limited use time windows, the limited use mode is turned off, and the limitations associated with the limited use mode are not enforced. The manner described above that allows a user to manually implement or not implement the limited use mode rules allows the electronic device to customize the implementation of the limited use mode as desired by the user, which selectively reduces the use of the electronic device, which in turn reduces power consumption and improves the battery life of the device.

In some embodiments, restricting access to the first application includes presenting (1144) one or more verbal instructions (e.g., audible voice instructions, in some embodiments in addition to the visual notification described above) that access to the first application is restricted. In some embodiments, the electronic device performs the verbal notification (e.g., based on a designation of a user account associated with the electronic device or based on an electronic device setting) only in accordance with determining that the limited use indication is to be spoken. For example, the electronic device optionally provides an option that the user can select or not select for audibly providing (or not providing) notifications as a supplement or alternative to being visually provided. In some embodiments, the electronic device optionally does not speak without performing a verbal notification in accordance with a determination that the limited use indication is not to be spoken (e.g., displays a notification without an audible voice indication that access to the application is limited). In some embodiments, the notification optionally includes sound (e.g., ring tone, alert, music, etc.) without a voice reading notification. In some embodiments, any of the notifications described herein can be audibly generated by (e.g., read to) the electronic device(s) to, for example, facilitate providing such notifications to users (e.g., children) who cannot read or see. The manner of providing audible notifications when access to applications is restricted during a limited use mode described above allows the electronic device to effectively limit the use of certain applications when in a limited use mode, while optionally not displaying additional information, which reduces power consumption and improves battery life of the device.

In some embodiments, a telephony application on the electronic device (e.g., an application that allows outgoing and incoming voice and/or video calls on the electronic device) is permanently included (1146) in the application usage whitelist (e.g., access to telephony applications is not restricted during the restricted usage mode). In some embodiments, the electronic device has a telephony function (e.g., capable of making a telephone call, receiving a telephone call, etc.) implemented with a telephony application installed on the electronic device (e.g., in the same manner as other applications such as messaging applications, email applications, video applications, etc. are installed on the electronic device), such as in fig. 10H. In such implementations, the telephony application is optionally always (e.g., permanently) included in the application's whitelist, such that the limited use mode restriction does not apply to the telephony application. Thus, the user is optionally able to use the telephony application normally, whether or not the limited use mode is active. In some embodiments, the telephony application is permanently included in the application usage whitelist for only certain designated contacts (e.g., the telephony application is free to only contact certain contacts), and use of the telephony application to communicate with other contacts can be limited. The manner described above in which access to telephony applications is allowed when access to other applications is restricted during the limited use mode allows the electronic device to effectively limit the use of certain communication applications when in the limited use mode, which reduces power consumption and improves battery life of the device.

In some embodiments, communication operations (e.g., phone calls, text messages, email, and/or video conferencing operations) using a phone application are permissible to anyone (e.g., communication operations are not restricted to any particular contact during limited use mode) or permissible only for one or more designated contacts of a plurality of contacts on an electronic device (e.g., communication is restricted to contacts saved on an electronic device, contacts in a designated group of contacts on an electronic device, or contacts on the white) during limited use mode (e.g., during limited use mode) while the one or more time windows associated with limited use mode are defined and in some embodiments, such as in fig. 10J-10M. In some embodiments, contacts with which a telephony application can communicate without limitation can be defined at an electronic device. For example, the electronic device optionally provides a user interface for allowing the telephony application to communicate with all contacts (e.g., any person's settings) or specified subsets of contacts (e.g., make calls to them, receive calls from them, etc.) without limitation during the limited use mode, and in some embodiments, the electronic device provides a user interface that allows only the telephony application to communicate with selected individuals (e.g., only contacts on the electronic device, or some contacts on the electronic device) without limitation during the limited use mode. Communication with other individuals is optionally restricted in the manner described previously (e.g., disallowed without user id/password, biometric feature or permission from the parent device, etc.). The manner described above in which a user is allowed to selectively limit access to communication operations with certain contacts during a limited use mode allows the electronic device to effectively limit use of certain communication applications while in the limited use mode, which reduces power consumption and improves battery life of the device.

In some implementations, the communication operations include (1150) incoming and outgoing communications (e.g., outgoing and/or incoming telephone calls, emails, text messages, and video conference calls). During the limited use mode, the electronic device blocks communications (e.g., blocks phone calls, text messages, video conference requests, etc.) from any person not designated for communications during the limited use mode. The manner described above in which a user is allowed to selectively limit access to communication operations with certain contacts during a limited use mode allows the electronic device to effectively limit use of certain communication applications while in the limited use mode, which reduces power consumption and improves battery life of the device.

In some embodiments, the electronic device receives (1152) contact information for the first contact (e.g., from another electronic device (e.g., a parent device)) from another electronic device in communication with the electronic device (e.g., via a wireless or wired connection), such as in fig. 10 AC. In some embodiments, the electronic device allows (1154) communication with the first contact during the limited use mode (e.g., allows performance of a communication operation with the first contact when a communication limit is set to a contact setting (e.g., when only communication operations with contacts specified on the electronic device are allowed during the limited use mode), such as in fig. 10M. In some embodiments, the electronic device automatically saves the received contact information for a first contact of the plurality of contacts saved on the electronic device. Optionally, the electronic device and the other electronic device are associated with the same user group account (e.g., a "home" or "home shared" account) (1156), such as in fig. 10W. In some embodiments, the other electronic device is a device of a parent in a home account. In such embodiments, the parent device is able to share one or more contacts (e.g., contact information such as name, phone number, email address, etc.) of the parent with the child device. For example, the parent device can transmit and save contact information for contacts on the parent device to the child's device (e.g., without specifying the child's contact information or specifying a target device to which the contact information is to be sent) by selection of the "share with child device" affordance on the parent device. In some embodiments, the parent is required to enter a password at the parent device to transmit and save the contact information on the child device. The manner described above in which a user is allowed to selectively limit access to communication operations with certain contacts during a limited use mode allows the electronic device to effectively limit use of certain communication applications while in the limited use mode, which reduces power consumption and improves battery life of the device.

In some embodiments, the one or more designated contacts of the plurality of contacts on the electronic device (e.g., contacts saved on the electronic device, contacts in a designated group of contacts on the electronic device, or contacts on a whitelist that is allowed during the limited use mode)) are customized (1158) (e.g., contacts can be added to or deleted from a whitelist of contacts (e.g., contacts for which communication operations are not limited during the limited use mode)), such as in fig. 10M. In some embodiments, specific contacts that are included or not included on the contact whitelist can be controlled by the electronic device. For example, certain contacts of the electronic device can be designated as "allowed" or "unrestricted" such that communication with those contacts is unrestricted during the restricted use mode (e.g., communication with other contacts or individuals is optionally restricted during the restricted use mode). In some embodiments, these "unrestricted" contacts are defined at the electronic device itself (e.g., within a setup user interface of the electronic device itself). In some embodiments, these "unrestricted" contacts are defined at another device (e.g., at a parent device in a family account of child devices if the current device is a child device in the family account). In some embodiments, a parent is required to enter a password at the parent device to define "unrestricted" contacts on the child device from the parent device. The manner described above in which a user is allowed to selectively limit access to communication operations with certain contacts during a limited use mode allows the electronic device to effectively limit use of certain communication applications while in the limited use mode, which reduces power consumption and improves battery life of the device.

In some embodiments, the one or more designated contacts of the plurality of contacts on the electronic device with which communication operations are permitted during the one or more time windows associated with the limited use mode (e.g., during the limited use mode (e.g., the bedtime mode) are different (1160) from a second one or more designated contacts with which communication operations are permitted outside of the one or more time windows associated with the limited use mode (e.g., a daytime contact whitelist with which communication is not limited during the limited use mode), such as in fig. 10O-10S. In some embodiments, the daytime contact whitelist is different from the nighttime contact whitelist (e.g., contacts for which communication operations are not restricted during the restricted use mode). For example, if the limited use mode is set to from 10pm to 6am, the 10pm to 6am application and/or contact whitelist is optionally different from the 6am to 10pm application and/or contact whitelist (e.g., different applications and/or contacts can be limited in different ways during the two time periods). In some embodiments, a particular contact can be listed in both a daytime contact whitelist and a nighttime contact whitelist (e.g., contacts optionally overlap in the two whitelists). In some embodiments, the daytime contact whitelist is the same as the nighttime contact whitelist. In some embodiments, communication operations with contacts that are not on the daytime contact whitelist are restricted outside of the restricted use mode. In some embodiments, a parent can set or update a daytime and/or nighttime contact whitelist from a parent device. In some embodiments, the parent is required to enter a password at the parent device to set or update the daytime and/or nighttime contact whitelist on the child device from the parent device. The manner described above in which a user is allowed to selectively limit access to communication operations with certain contacts during and beyond a limited use mode allows the electronic device to effectively limit use of certain communication applications while in the limited use mode, which reduces power consumption and improves battery life of the device.

In some embodiments, the electronic device receives (1162), via the one or more input devices, an input for adding a second application of the plurality of applications installed on the electronic device to an application usage whitelist, such as in fig. 10I-10J. In accordance with a determination that the second application is included in the application use whitelist when the one or more time windows associated with the limited use mode are defined and during the one or more time windows associated with the limited use mode, the electronic device provides (1164) access to the second application (e.g., adds the application to a list of applications that are not limited during the limited use mode), such as in fig. 10J. In some embodiments, any application installed on the electronic device can be added to the application whitelist, whether in the settings user interface of the electronic device itself or via another device (e.g., if the current device is a child device in a home account, defined for the child device at a parent device in the home account). In some embodiments, the parent is required to enter a password at the parent device to set or update the application whitelist on the child device from the parent device. The manner described above in which a user is allowed to selectively restrict access to certain applications during a limited use mode allows the electronic device to effectively restrict use of certain communication applications while in a limited use mode, which reduces power consumption and improves battery life of the device.

In some embodiments, the electronic device receives (1166) one or more inputs (e.g., a change to a start/end time of a limited use mode, a change to a whitelist, etc.) for changing one or more limited use mode settings associated with the limited use mode, such as in fig. 10F. In response to receiving the one or more inputs to change the one or more limited-use mode settings (1168), in accordance with a determination that the one or more inputs to change the one or more limited-use mode settings are received via the one or more input devices of the electronic device and the electronic device is a child device (e.g., based on a categorization of a user account associated with the electronic device or an option selected on the electronic device), the electronic device requires (1170) authorization (e.g., requires a user of the electronic device to enter a password in order to change the limited-use mode) prior to performing the one or more limited-use mode setting changes, such as in fig. 10T-10V. For example, determining that the one or more inputs to alter the one or more limited use mode settings are received at a child device is optionally based on determining that a user account associated with the electronic device (e.g., a user currently logged into the device) is categorized as a child account. In some embodiments, determining that the one or more inputs to alter the one or more limited use mode settings is received at the child device is optionally based on determining that the electronic device is set as the child device in a setting of the device (e.g., set upon initial setting of the device). In some embodiments, if the electronic device is a child device in a home account, any limited use mode settings or preferences or rules, etc., described herein can only be modified at the child device in response to entering a password or other authentication credential at the child device (e.g., upon determining that one of these settings is being modified, the electronic device prompts the user to enter a password that must be authenticated before modification is allowed). In some implementations, the authentication credentials are the same as credentials used to unlock the device (e.g., a password used to unlock the device). In some implementations, the authentication credentials are different from credentials used to unlock the device (e.g., credentials of a parent in a home account). In some embodiments, the parent device is able to modify the above settings valid on the child device remotely (e.g., optionally, by entering parental credentials at the parent device). In some embodiments, the parent is required to enter a password at the parent device to remotely modify the above settings on the child device. In response to receiving the one or more inputs to change the one or more limited-use mode settings (1168), in accordance with a determination that the one or more inputs to change the one or more limited-use mode settings are received from outside the electronic device via the parent device (e.g., the change to the limited-use mode is made on the parent device), the electronic device performs (1172) the one or more limited-use mode setting changes (e.g., changes to the limited-use mode without requiring input of additional credentials), such as in fig. 10X-10 AC. For example, determining that the one or more inputs to alter the one or more limited use mode settings are received via a parent device is optionally based on determining that a user account associated with the other device (e.g., a user currently logged into the device) is categorized as a parent account. In some embodiments, determining that the one or more inputs to alter the one or more limited use mode settings are received via a parent device is optionally based on determining that the other device is set as a parent device in a setting of the device (e.g., set upon initial setting 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 makes the change to the limited use mode setting on the child device remotely (e.g., over the internet, bluetooth, or other network or protocol). In some embodiments, the parent is required to enter a password at the parent device to remotely alter the limited use mode setting on the child device. The above-described manner of limiting the ability to alter the limited use mode settings allows the electronic device to effectively and selectively limit the use of certain applications during certain periods of time, which reduces the use of the electronic device during those periods of time, which in turn reduces power consumption and improves the battery life of the device.

In some embodiments, in response to executing the one or more limited-use mode settings 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 image), an audible indication, a verbal indication, and/or a tactile and/or haptic output indication) of the one or more limited-use mode settings modification (e.g., presents a notification that the limited-use mode settings were modified remotely by the parent device), such as in fig. 10 AC. In some embodiments, if the parent device does remotely modify the above settings that are valid on the child device, the child device displays a notification that such remote modification occurred, details of the modification (e.g., the parent device has changed the time window during which the limited use mode was valid from 10pm to 6am to 9pm to 7am, etc.). The manner of altering the limited use mode settings described above allows the electronic device to effectively and selectively limit the use of certain applications during certain periods of time, which reduces the use of the electronic device during those periods of time, which in turn reduces power consumption and improves the battery life of the device.

In some embodiments, outside the one or more time windows associated with the limited use mode, the electronic device displays (1176) one or more representations of applications installed on the electronic device (e.g., icons, desktop applets, windows of a first application in a multitasking view along with other windows of other applications), such as in fig. 10 AR. For example, the electronic device displays one or more application windows associated with one or more applications (e.g., in a multi-tasking graphical user interface view), or the electronic device displays one or more icons for launching applications on a home screen of the electronic device. In some embodiments, the electronic device displays (1180) a first representation of the first application (e.g., a representation of an application that is not on the application white list (e.g., in response to a beginning of the one or more time windows associated with the restricted use mode), in response to determining that the first application is not included in the application use white list (e.g., a list of applications that are not subject to restricted access constraints (e.g., can be fully or partially accessed during the restricted use mode) for the application installed on the electronic device, such AS in terms of color, etc.), the electronic device has a first representation of the first application (e.g., a different appearance of the representation of the application that is not on the application white list than the appearance of the application that is not on the application white list) (e.g., in response to a beginning of the one or more time windows associated with the restricted use mode), a shadow is included in the electronic device in the restricted use mode (e.g., a list of applications that is not subject to restricted access constraints (e.g., can be fully or partially accessed during the restricted use mode), the electronic device is included in the restricted use white list (e.g., a shadow is included in the application) in the application display device during the restricted use mode, and/or the placeholder generic indicators are displayed over the icons of those applications (or partially over any portion of the icons of those applications) in the limited use mode, as described above. In some implementations, the placeholder generic indicator (e.g., lock icon) is placed on or near text associated with the application icon. As another example, notification identifiers included on application icons of applications not included in the application whitelist are optionally modified, as described previously. As another example, in some embodiments, the electronic device has a multi-tasking capability, wherein the electronic device optionally displays a user interface that simultaneously displays visual representations of more than one application (e.g., a user interface that simultaneously displays icons from multiple applications, simultaneously displays screen shots of a current user interface of multiple applications, multiple application windows of different applications are presented simultaneously, etc.). In some embodiments, during the limited use mode, the representations of applications in the above multitasking user interface that are not in the application whitelist are modified (e.g., faded or shaded, or otherwise modified to be displayed with different visual characteristics than the representations corresponding to applications included in the application whitelist) by the electronic device. In some embodiments, during the one or more time windows associated with the limited use mode (1178) (e.g., in response to a start of the one or more time windows associated with the limited use mode), in accordance with a determination that the first application is included in the application use whitelist, the electronic device displays (1182) a first representation of the first application with a first visual characteristic (e.g., an appearance of a representation of the application included in the application whitelist continues to be displayed with the same visual characteristic during the limited use mode), such AS in fig. 10 AS. The manner in which the appearance of the representation of applications not on the application whitelist is selectively changed during the limited use mode described above allows the electronic device to effectively and selectively limit the use of particular applications during certain periods of time by providing an indication of what applications the user has or does not have access to during the limited use mode, which reduces the use of the electronic device during those periods of time, which in turn reduces power consumption and improves battery life of the device.

In some embodiments, displaying the first representation of the first application with the second visual characteristic includes (1184) displaying a limited-use indicator on the first representation, the limited-use indicator including an indication that access to the first application is limited (e.g., an indicator added to the visual indication of the application icon with a lock or some other limiting symbol, such AS covering those application icons or any portion of those application icons (e.g., the upper right portion of the icon)), such AS in fig. 10 AS. In some implementations, a limit symbol (e.g., a lock icon) is placed on or near text associated with the limited application icon. In some embodiments, when the limited use mode is not active, the application icons include one or more visual indications of notifications associated with those applications (e.g., a designator indicating a portion of the overlay icon that received a number of unread notifications in the application). In such embodiments, for those applications that are not included in the application whitelist, those visual indications are removed, grayed out, have the number of notifications removed therefrom, are replaced with a placeholder generic indication (e.g., a lock icon), or are otherwise changed such that the notification status (e.g., the number of notifications) of those applications is no longer conveyed by those indications. The manner described above of selectively changing the appearance of an application that is not on the application whitelist during the restricted use mode allows the electronic device to effectively and selectively limit the use of particular applications during certain periods of time by displaying a restricted use identifier on applications that the user does not have access to during the restricted use mode, which reduces the likelihood that the user will attempt to access such restricted applications, which in turn reduces the use of the electronic device during those periods of time, thereby reducing power consumption and improving the battery life of the device.

In some embodiments, displaying the first representation of the first application with the first visual characteristic includes displaying (1186) the first representation with a notification indicator (e.g., an indicator of an unread message, missed call, etc.), the notification indicator including an indication of a notification received at the first application (e.g., a number of unread messages, missed calls, etc.), and displaying the first representation of the first application with the second visual characteristic includes displaying (1188) the first representation with the notification indicator having been replaced with a limited use indicator (e.g., obscuring the indicator or replacing the indicator with a graphic), such AS in fig. 10 AR-10 AS. In some embodiments, the lock identifier described above replaces the indication of the notification identifier of the application icon of the non-whitelisted application during the limited use mode time window, as previously described. The above-described manner of selectively changing the appearance of representations of applications not on the application whitelist during the limited use mode allows the electronic device to effectively and selectively limit the use of particular applications during certain periods of time by replacing notification indications of the application representations with limited use identifiers on applications that the user does not have access to during the limited use mode, which in turn reduces power consumption and improves battery life of the device by preventing the user from attempting to access limited applications having such notifications by not indicating the presence of a recent notification.

It should be understood that the particular order in which the operations in fig. 11A-11I are described is merely exemplary and is not intended to suggest that the described order is the only order in which the operations may be performed. Those of ordinary skill in the art will recognize a variety of ways to reorder the operations described herein. In addition, it should be noted that the details of other processes described herein in connection with other methods described herein (e.g., methods 700, 900, 1300, and 1500) are equally applicable in a similar manner to method 1100 described above in connection with fig. 11A-11I. For example, the limited use mode, use restriction settings, etc. described above with reference to method 1100 optionally have one or more of the features of the limited use mode, use restriction 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 are not repeated here.

The operations in the above-described information processing method are optionally implemented by running one or more functional modules in an information processing apparatus such as a general-purpose processor (e.g., as described in connection with fig. 1A-1B, 3, and 5A-5H) or an application-specific chip. Furthermore, the operations described above with reference to fig. 11A to 11I are optionally implemented by the components depicted in fig. 1A to 1B. For example, display operations 1122, 1124, 1176, 1180, 1182, 1184, 1186 and 1188 and receive operations 1102, 1106, 1138, 1152, 1162 and 1166 are optionally implemented by event sorter 170, event recognizer 180 and event handler 190. The event monitor 171 in the event sorter 170 detects a contact on the touch screen 504 and the event dispatcher module 174 communicates the event information to the application 136-1. The respective event identifier 180 of the application 136-1 compares the event information to the respective event definition 186 and determines whether the first contact at the first location on the touch screen corresponds to a predefined event or sub-event, such as a selection of an object on the user interface. When a respective 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. Event handler 190 optionally utilizes or invokes data updater 176 or object updater 177 to update the 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 apparent to one of ordinary skill in the art how other processes may be implemented based on the components depicted in fig. 1A-1B.

Suppressing auxiliary application functions in a user interface

Users interact with electronic devices in a number of different ways and during different times of day or night. For example, a user may read the latest news on a news application installed on an electronic device in bed during their morning train commute or at the end of the day. However, in some cases, 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 inhibit auxiliary functions of particular applications when the limitations of those particular applications are met, such as when application usage limits associated with those applications are reached and/or during one or more periods of time when the electronic device is operating in a limited use mode. Suppressing the auxiliary functions of the application when the constraints are met allows the electronic device to effectively reduce the overall use of the electronic device, thereby reducing the power use of the device and increasing the battery life of the battery-operated device. It will be appreciated that people use the device. When a person uses a device, the person is optionally referred to as a user of the device.

Fig. 12A-12 AB illustrate an exemplary manner in which an electronic device suppresses auxiliary functions of particular applications when application use limits or constraints associated with those applications are reached, 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 fig. 13A-13H.

Fig. 12A shows an exemplary device 500 having a touch screen 504, described with reference to fig. 5A-5H. Touch screen 504 optionally displays one or more user interfaces including various content. In the example shown in fig. 12A, the touch screen 504 displays the home screen 1202 when the constraints are not met on the device 500 (e.g., the user-defined usage limit has not been reached and outside of one or more user-defined time windows associated with the limited usage mode). In some embodiments, the limit condition is satisfied when the use limit is reached for a given application or class of applications, as described above with reference to methods 700 and 900. In some embodiments, the constraints 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 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 message application 424. In some embodiments, notification indicator 1204 is an indicator that overlays (or partially overlays) the appropriate icon, as shown in fig. 12A.

In fig. 12B-12C, a horizontal swipe of contact 1203 is detected on touch screen 504 while home screen 1202 is displayed, which causes device 500 to display search user interface 1207 when the constraints are not met on device 500. Search user interface 1207 is optionally a user interface of the operating system of device 500 to search for content accessible from device 500 (e.g., websites, news, email, applications installed on device 500, applications available for download to device 500, calendar entries, etc.). The search user interface 1207 optionally includes a text field 1204 for entering one or more search terms for searching for content accessible from the device 500, an "application suggestion" user interface 1208 for applications suggested to the user by the operating system of the display device 500 (e.g., applications that are commonly used, applications that are recently used, applications that are favorite, applications that are currently running), and a desktop applet 1210 (e.g., a user interface object or window that includes text, images, and/or any other content associated with and updated by the corresponding application) corresponding to the application installed on the device 500, as shown in fig. 12C. For example, in FIG. 12C, the application suggestion user interface 1208 includes a photo application 428, a workout support application 442, a messaging application 424, and a social media A application 452, and the applet 1210a corresponds to a "social media application A" application, and the applet 1210b corresponds to a "contacts" application.

In fig. 12D, the user has entered the search term "social media" into text field 1204 when the constraints are not met on device 500. In response to the search term "social media" having been 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 for a social media application "social media A" installed on device 500, a link 1212b for a social media website "social media A" that is a website related to the "social media A" application, and affordances of two social media applications available for download from an application store (e.g., an application repository): an affordance 1212C for downloading a "social media B" application and an affordance 1212d for downloading a "social media C" application.

Fig. 12E shows a new message received at the device 500 when the device 500 is displaying the home screen user interface 1202 when the constraints are not met on the device 500. In some embodiments, the event of receiving a message at the device 500 corresponds to activating a function for displaying a notification related to a new message on the device 500. For example, fig. 12F shows device 500 displaying a notification 1214 in response to receiving the message in fig. 12E indicating that the new message was received in connection with 424 the message application. In some embodiments, the event of receiving a new message corresponds to initiating other auxiliary functions, such as updating an unread message indicator on an application icon. For example, fig. 12F shows device 500 updating an indicator 1204 on message application 424 to reflect that there are now four unread messages (including a newly received message) in message application 424 in response to detecting a new message for message application 424.

FIG. 12G illustrates that the touch screen 504 displays a home screen 1202 when a constraint is met on the device 500 for the message application 424 and the social media A application 452 (e.g., the user-defined usage limit has been reached and/or the current time is during one or more user-defined time windows associated with the limited usage mode) when a new message related to the message application 424 and the social media A application 452 is being received at the device 500. In some embodiments, icons corresponding to restricted applications are changed when the restriction conditions are met for those applications. For example, icons 424 and 452 corresponding to restricted messaging application 424 and social media a application 452 are hidden (e.g., distorted, grayed out, faded out, and/or visually changed) when the restriction conditions are met for those applications. Fig. 12G illustrates that the indicator 1204 associated with the message application 424 is optionally obscured such that the number of unread notifications (e.g., the number of unread messages in the message application 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 implementations, the placeholder generic indication is overlaid (or partially overlaid) on all icons associated with all restricted applications, whether or not the restricted applications have any unread notifications. In some implementations, the placeholder generic indicator (e.g., lock icon) is placed on or near text associated with the application icon of the restricted application.

FIG. 12H illustrates device 500 suppressing notifications for restricted applications by discarding notifications that display two new messages received in the message and social media A application when the restriction conditions are met for those applications. Fig. 12H also shows that the device 500 discards updating the indicator 1204 on the message application 424 to reflect that there are now five unread messages (including the newly received message) in the message application. In some embodiments, the device 500 superimposes a place-and-hold generic indication 1206 (e.g., a lock icon) on (or partially superimposed on) an icon associated with a restricted application when the restriction condition is satisfied for that application that received a message for that application, as shown in fig. 12H. For example, FIG. 12H shows lock icon 1206 overlaying an upper right portion of social media A application 452. In some implementations, the placeholder generic indication is overlaid (or partially overlaid) on all icons associated with all restricted applications, whether or not the restricted applications have any unread notifications. In some implementations, the placeholder generic indicator (e.g., lock icon) is placed on or near text associated with the application icon of the restricted application.

In fig. 12H-12I, 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 being displayed down to home screen 1202), which causes device 500 to display notification history interface 1220 when a limit condition is met on device 500. Notification history interface 1220 is optionally a user interface of the operating system of device 500 that displays previously received notifications corresponding to one or more applications stored on device 500. In some embodiments, the device 500 displays the suppressed notification of the restricted application in the notification history interface 1220. In some embodiments, the device 500 visually masks notifications of restricted applications displayed in the notification history interface 1220 (e.g., obscures, grays, or visually changes the notifications), as shown in fig. 12I. For example, in FIG. 12I, device 500 displays in notification history interface 1220 a notification 1222 associated with message application 424 and a notification 1224 associated with social media A application 452, which were received at FIG. 12G but suppressed in FIG. 12H.

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

In some embodiments, the device 500 suppresses other auxiliary functions associated with the restricted application (e.g., an application for which the restriction condition is satisfied), such as suppressing the restricted application in the search results, suppressing a desktop applet associated with the restricted application, suppressing the restricted application from appearing in the application suggestion graphical user interface, and/or suppressing a window corresponding to the restricted application from appearing in the multitasking graphical user interface. For example, in fig. 12L-12M, a horizontal swipe of contact 1203 is detected on touch screen 504 while home screen 1202 is displayed when the constraints are met for message application 424 and social media a application 452 (e.g., as described above in connection with fig. 12G-12H), which causes device 500 to display search user interface 1207 with suppressed auxiliary functionality associated with the restricted application. The search user interface 1207 optionally includes a text field 1204 for entering one or more search terms for searching for content accessible from the device 500, an "application suggestion" user interface 1208 for applications suggested by the operating system of the display device 500 for the user, and a desktop applet 1210 corresponding to the application installed on the device 500 (e.g., as described above with reference to fig. 12C). In some embodiments, the device 500 suppresses the restricted application and the desktop applet associated with the restricted application in the application suggestion user interface 1208, as shown in fig. 12M. For example, the device 500 suppresses application suggestions and the desktop applet associated with the restricted application by optionally visually masking the restricted application (e.g., blurring, graying out, or visually changing the restricted application) in the application suggestion user interface 1208 (e.g., visually masking the restricted social media a application 452) and visually masking the desktop applet associated with the restricted application (e.g., visually masking the desktop applet associated with the restricted social media a application 452), as shown in fig. 12M. In some embodiments, the device 500 suppresses application suggestions and desktop applets associated with restricted applications by optionally not displaying restricted applications in the application suggestion user interface 1208 and not displaying the desktop applets associated with restricted applications (e.g., forgoing displaying the social media a application 452 and the desktop applet 1210a associated with the restricted social media a application 452), but displaying other unrestricted applications (e.g., applications for which the restrictions are not met) and/or the desktop applets associated with unrestricted applications.

In FIG. 12N, the user has entered the search term "social media" into text field 1204 when the constraints are met on device 500 for social media A application 452. In response to the search term "social media" having been 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 optionally displays a link 1212a for social media application "social media A"452 installed on device 500, a link 1212b for social media website "social media A" that is a website related to the "social media A" application, and links for two social media applications available for download from an application store (e.g., an application repository): link 1212C of the "social media B" application and link 1212d of the "social media C" application. Because the constraints are met for social media A application 452, links 1212a and 1212b are suppressed (e.g., visually altered or hidden) 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. Rather than displaying links 1212a and 1212b, links to other unrestricted applications (e.g., applications where the restrictions are not satisfied) 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 condition is satisfied), such as suppressing website content associated with the restricted application. For example, FIG. 12P shows device 500 displaying web browser interface 1230 suppressing web content from web site "www.socmeda.com" associated with restricted social media A application 452 by forgoing displaying web content from the web site. 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 having the same home page URL). In some embodiments, device 500 displays an indication 1232 (e.g., text and/or image) explaining that the website is restricted because the restriction condition is satisfied for social media a application 452, as shown in fig. 12P. In some embodiments, the device 500 suppresses web content from the restricted application by masking (e.g., obscuring, graying out, or visually changing) the web content 1236 and displaying an indication 1232 that the interpreted web site is restricted, as shown in fig. 12Q. In some embodiments, web browser interface 1230 includes a URL field 1234 for entering the web address (e.g., URL) of the web site. The device 500 optionally allows the user to enter a website address in the URL field 1234 while suppressing websites associated with restricted applications and allows the user to navigate to another website, as shown in fig. 12R-12S.

In some embodiments, the device 500 allows a user to share content with other one or more applications installed on the device. Fig. 12T shows device 500 displaying web content in web browser interface 1230, web browser interface 1230 optionally including a selectable sharing affordance 1236 for sharing web content. For example, in fig. 12T, selection of the shared affordance 1236 is detected (e.g., by tapping of the contact 1003 detected on the shared affordance 1236, as shown in fig. 12T). In response to selection of the share affordance 1236, the device 500 displays a share form graphical user interface 1240, as shown in FIG. 12U. In some embodiments, the sharing form graphical user interface 1240 includes selectable icons of applications installed on the device 500, which the user optionally selects to share web content, as shown in fig. 12U. In some embodiments, the device 500 suppresses icons of restricted applications in the shared form graphical user interface 1240. For example, in fig. 12U, the device 500 suppresses the limited message application icon 424 and the limited social media a application icon 452 in the shared form graphical user interface 1240 by visually obscuring the limited message application icon 424 and the limited social media a application icon 452 (e.g., by blurring, graying out, or visually changing the icons). In some embodiments, the device 500 suppresses the restricted message application icon 424 and the restricted social media a application icon 452 by discarding the restricted message application icon 424 and the restricted social media a application icon 452 from being displayed in the shared form graphical user interface 1240 (e.g., by not displaying icons of restricted applications), but displaying other unrestricted applications (e.g., applications for which the restriction condition is not satisfied).

Fig. 12V illustrates device 500 displaying content associated with a video Z application in picture-in-picture (PIP) interface 1250 when the limitations of the video Z application are not met. In some embodiments, PIP interface 1250 is displayed on another user interface (e.g., on a home screen, a home user interface of another application, a user interface of another application), as shown in fig. 12V. In some embodiments, device 500 suppresses application content from being displayed in picture-in-picture (PIP) interface 1250 when the application's constraints are met. For example, fig. 12W illustrates that content associated with a video Z application is suppressed from being displayed in PIP interface 1250 when the limitations of the video Z application are met. In some embodiments, device 500 suppresses the display of content associated with the video Z application in PIP interface 1250 by visually obscuring (e.g., blurring, graying out, or visually changing) the content and/or PIP interface 1250, as shown in fig. 12W. In some embodiments, device 500 suppresses the display of content associated with video Z application in PIP interface 1250 by relinquishing the display of content associated with video Z application in PIP interface 1250. If PIP interface 1250 is currently displaying content associated with video Z application when the constraints are met, device 500 suppresses the display of content associated with video Z application in some embodiments by stopping the display of the content in PIP interface 1250 (e.g., closing the PIP window) and/or masking PIP interface 1250 (e.g., graying out or fading out the PIP window) and/or pausing the playback of the video. In some embodiments, device 500 suppresses the display of content associated with video Z application in PIP interface 1250 by visually obscuring content and/or PIP interface 1250 and automatically closing PIP interface 1250 after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds), as shown in fig. 12X (e.g., device 500 after stopping the display of PIP interface 1250).

In some embodiments, the device 500 suppresses other auxiliary functions associated with the restricted application (e.g., an application for which the restriction condition is satisfied), 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 being displayed up to home screen 1202), which causes device 500 to display media control interface 1260 when the constraints 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 what media content media control interface 1260 is currently controlling, as shown in fig. 12Z. For example, fig. 12Z shows device 500 controlling media playback of a Song "Hit Song" of "Pop Star" by a music application. In some implementations, the device 500 suppresses the media control interface 1260 for media content associated with a restricted application (e.g., an application for which the restriction condition is satisfied). For example, fig. 12AA shows device 500 displaying media control interface 1260 when the constraints are met on device 500 for music application, message application 424, and social media a application 452, and suppressing media control interface 1260 for controlling media content associated with the music application. In some implementations, the device 500 suppresses the media control interface 1260 by stopping playback of media content associated with the music application and disabling the media control button 1262 (e.g., not allowing the button to be used to control media content associated with a restricted application), as shown in fig. 12 AA. In some implementations, the device 500 also visually conceals the media control button 1262 (e.g., by blurring, graying out, or visually changing the media control button), as shown in fig. 12 AA. In some implementations, 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. 12 AB. For example, fig. 12AB shows that device 500 is no longer playing media content associated with the music application (e.g., media content information 1264 associated with the music application is no longer displayed), and device 500 is no longer disabling media control button 1262. In some embodiments, the device 500 stops the display of the media control interface 1260 for a period of time after the constraints are met (e.g., 5 seconds, 10 seconds, 20 seconds) and/or for a period of time after the device 500 resets the media control interface 1260.

Fig. 13A-13H are flowcharts illustrating methods 1300 of suppressing auxiliary functions of particular applications when application usage limits or constraints associated with those applications are reached, according to some embodiments of the present disclosure. The method 1300 is optionally performed on an electronic device (such as device 100, device 300, or device 500), as described above in connection with fig. 1A-1B, fig. 2-3, fig. 4A-4B, and fig. 5A-5H. Some operations in method 1300 are optionally combined and/or the order of some operations is optionally changed.

As described below, method 1300 provides a way to suppress auxiliary functions for particular applications when application usage limits associated with those applications are reached. The method reduces the overall use of the electronic device by limiting the way a user interacts with a particular application. For battery-operated electronic devices, reducing the overall use of the electronic device saves power and increases the time interval 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, including one or more of a keyboard, mouse, touch pad, touch screen, such as touch screen 504), a wearable device, such as a smartwatch including a touch screen, or a set-top box in communication with a television and an input device (e.g., a remote control) in implementing restrictions (e.g., holding screen time information, time to use a particular application, information about notifications received from a particular application, information about events of interest) on one or more applications (including a first application of a plurality of applications installed on the electronic device), and optionally controlling the amount of the above allowed by the electronic device (e.g., usage limits, bedtime limits, etc.)) detecting (1302) an event corresponding to activation of an auxiliary function of the first application (e.g., an event that would trigger display of a notification of the application, a request to display a desktop applet 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 of the application), a request to display application content in a 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 a media control operation associated with an application program), where the auxiliary function of the first application program is a function (e.g., displaying an interactive notification, performing a shared form action, displaying a desktop applet, displaying a notification history, displaying a website in a browser, displaying application content in a PIP mode, displaying an application program in a search result, displaying an application program window in a multitasking graphical user interface, or displaying and/or controlling a media control operation) that is available to be performed without displaying the primary user interface of the first application program (e.g., without launching an application program in an application program window or other front view of the application program), such as in fig. 12C. In some embodiments, the usage limits of the one or more applications are enforced over a period of time (e.g., over a twenty-four hour period, a week, or any other period of time).

In some embodiments, in response to detecting an event corresponding to activation of an auxiliary function of the first application (1304), in accordance with a determination that a constraint of the first application has been met (e.g., a user-defined application usage "limit" (e.g., a usage limit or quota) has been reached), the electronic device suppresses (1306) the auxiliary function (e.g., suppresses a notification generation function associated with the application, a display of a website associated with the application, a shared form action, a display of a window corresponding to the application in a multitasking graphical user interface, a display of application content in a PIP mode, and any other function associated with the application (including operating system functions) (e.g., limiting application presence in search results, limiting access to a desktop applet associated with the application, limiting application presence as a suggested application, or limiting presence of a window corresponding to the application in a multitasking graphical user interface)), such as in fig. 12M. In some embodiments, the usage limit is set for overall device usage, usage of multiple applications in a given application class, or for a particular application. In some embodiments, the launching of the application 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.

In some embodiments, in response to detecting an event corresponding to activation of an auxiliary function of a first application (1304), in accordance with a determination that a constraint has not been met, the electronic device performs (1308) the auxiliary function without displaying a primary user interface of the application (e.g., allowing normal use or execution of various application-related functions on the electronic device, such as generating notifications from the application, sharing form actions, displaying websites associated with the application, displaying application content in PIP mode, displaying a desktop applet associated with the application, displaying windows corresponding to the application appear in a multitasking graphical user interface, etc.), such as in fig. 12C. The limitations and auxiliary functions described herein are optionally the same as or similar to the limited use modes, auxiliary functions and/or application use limits described with reference to methods 700, 900 and 1100. The above-described manner of suppressing the functionality of an application whose usage limit has been exceeded allows the electronic device to effectively reduce the overall usage of the electronic device, which reduces power consumption and improves the battery life of the device.

The auxiliary function optionally includes presenting an indication of a first type of notification (e.g., displaying a visual indication on a display, playing a sound with a speaker associated with the electronic device, generating a haptic and/or tactile output, etc.) of the notification (e.g., an alert and/or notification generated by the application, etc.) in response to occurrence of an event corresponding to activation of the notification (e.g., the notification) (1310), such as in fig. 12F. In some embodiments, the notification includes a visual indication (e.g., window, pop-up box) including text and/or images. Additionally or alternatively, the notification optionally includes an audible and/or tactile and/or haptic output indication. In some embodiments, the electronic device suppresses notifications associated with applications for which the usage limit has been exceeded. In some embodiments, notifications are suppressed by discarding the display of a user visual indication (e.g., text and/or image) or discarding the generation of the notification. In some embodiments, notifications are suppressed by masking the user's visual indication (e.g., visually altering the visual indication, text, and/or image). In some embodiments, notifications are suppressed by forgoing execution of audible and/or tactile and/or haptic output indications associated with the application. In some embodiments, performing the auxiliary function includes presenting a notification generated by the first application. The manner in which notifications associated with applications for which the constraints are met are suppressed described above allows the electronic device to effectively reduce overall use of the electronic device (e.g., by not performing notification functions and thus not prompting a user to interact with the notification and/or the electronic device), which reduces power consumption and improves battery life of the device.

In some implementations, 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) (e.g., detecting an occurrence of an event that would trigger presentation of the notification), such as in fig. 12E. In some implementations, suppressing the auxiliary function includes discarding presentation of the first type of indication (1314) in response to the notification generated by the first application (e.g., suppressing the notification associated with the restricted application), such as in fig. 12G-12H. In some embodiments, notifications are suppressed by discarding the display of a user visual indication (e.g., text and/or image) or discarding the generation of the notification. In some embodiments, notifications are suppressed by masking the user's visual indication (e.g., visually altering the visual indication, text, and/or image). In some embodiments, notifications are suppressed by forgoing execution of audible and/or tactile and/or haptic output indications associated with the application.

In some embodiments, performing the auxiliary function includes presenting an indication of a first type (1316) (e.g., displaying a banner, a pop-up notification, or a lock screen notification) in response to the notification generated by the first application, such as in fig. 12F. In some embodiments, performing the auxiliary function includes presenting a notification generated by the first application. The above-described manner of suppressing notifications associated with applications for which the constraints are met, and not suppressing notifications associated with applications for which the constraints are not met, allows the electronic device to effectively and selectively reduce use of the electronic device (e.g., by not executing notification functions of certain applications, and thus not prompting a user to interact with the notification and/or the electronic device), which reduces power consumption and improves battery life of the device.

In some embodiments, in accordance with a determination that the constraints of the first application are met (1318), the electronic device includes (1319) a visual indication (e.g., image, window, text, etc.) of the indication of the first type in a notification history user interface (e.g., a user interface for displaying visual indications of a plurality of 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 one or more indications of notifications generated by one or more applications other than the first application (1319). In some embodiments, the electronic device displays a notification history of the plurality of applications in the notification history user interface, including a visual indication of any suppressed notifications generated by the first application.

In some embodiments, notifications generated by the plurality of applications (including the first application) are displayed in a notification history user interface (e.g., window) dedicated to displaying notifications that have been received via the plurality of applications on the electronic device (e.g., even if a constraint condition of the first application is satisfied in accordance with a determination). This optionally allows the user to later browse notifications of the suppressed application. In some embodiments, visual indications of notifications from non-suppressed applications are also presented outside of (in addition to being presented in) the notification history user interface, while visual indications of notifications from suppressed applications (e.g., first application) are presented only in the notification history user interface. The manner described above of displaying the suppressed notifications associated with applications for which the constraints are met in the notification history allows the electronic device to efficiently organize and display notifications that are otherwise suppressed without pushing the notifications (e.g., by not alerting the user of the notifications in a pop-up window, sound, and/or tactile and/or haptic output indication when the notifications are generated), which reduces overall use of the electronic device (e.g., by not prompting the user to interact with the notifications and/or the electronic device), which reduces power consumption and improves battery life of the device.

In some embodiments, suppressing the auxiliary function includes discarding the indication (1320) of the first type in response to the notification generated by the first application (e.g., not actively presenting a new indication (e.g., image, sound, and tactile and/or haptic output) of any notification associated with the application when the usage limit of the application has been exceeded, such as in fig. 12G-12H. In some embodiments, after suppressing the auxiliary function of the first application, the electronic device determines (1322) that the restriction condition of the first application is no longer met (e.g., the usage of the first application no longer meets the usage limit of the first application, the device is no longer in limited use (e.g., device downtime or bedtime mode), etc.), such as in fig. 12K, in response to determining that the limitations of the first application are no longer met, the electronic device presents (1324) an indication of the notification generated by the first application (e.g., displays the notification in a notification history user interface and/or is actively presented as a "new" notification as if it had just been received when the usage limit was reset), such as in fig. 12K. The electronic device optionally displays previously suppressed notifications in a user interface, indicating that these notifications would have been previously presented (e.g., on a wake or lock screen of the device) if not suppressed. In some embodiments, these notifications will be performed all at once (e.g., in an alert, window, or pop-up box containing all previously suppressed notifications), or will be displayed separately/sequentially. The manner of presenting notifications associated with applications at the time of a use limit reset described above allows an electronic device to effectively present notifications that were previously suppressed while reducing the overall use of the electronic device, which reduces power consumption and improves the battery life of the device.

The auxiliary functions optionally include displaying a desktop applet user interface that exposes one or more auxiliary user interfaces of one or more applications, including an auxiliary user interface (1326) of a first application (e.g., a desktop applet corresponding to the application), such as in fig. 12C. In some embodiments, the desktop applet includes user interface objects (e.g., windows) including text and/or images associated with the application (e.g., a weather desktop applet that displays the current temperature, a sports desktop applet that displays the live score, a news desktop applet that displays the title of the most recent event, and/or any user interface object that displays content associated with the application). In some embodiments, the content of the desktop applet corresponding to the application is dynamically updated by the application. In some embodiments, the auxiliary user interface (e.g., a desktop applet) is displayed simultaneously with additional auxiliary user interfaces (e.g., desktop applets) of other applications that are different from the main user interface of those applications (e.g., desktop applets are displayed simultaneously with the desktop applets of other applications). In some embodiments, the auxiliary user interface (e.g., a desktop applet) is displayed in a user interface of the desktop applet that is different from the main user interface of the first application. The event corresponding to activation of the auxiliary function optionally includes a request (1328) to display a desktop applet user interface (e.g., input from a user for displaying the desktop applet user interface on the electronic device), such as in fig. 12B-12C. In some embodiments, suppressing the auxiliary function includes displaying a desktop applet user interface while suppressing (e.g., not displaying or obscured with a message or a splash screen indicating that the limit condition is met) the auxiliary user interface (1330) of the first application (e.g., suppressing the one or more desktop applets whose limit of use is exceeded), such as in fig. 12M. In some embodiments, the desktop applet is suppressed by discarding the display of user interface objects (e.g., text and/or images) of the desktop applet (e.g., the desktop applet is not displayed) associated with the application whose usage limit is exceeded. In some embodiments, the desktop applet is suppressed by hiding the user interface object (e.g., visually changing the user interface object, text, and/or image) while displaying other desktop applets. The hidden desktop applet optionally includes displaying an indication of the constraint in place of text and/or images associated with the application (e.g., the content of the desktop applet when the constraint is not satisfied). In some embodiments, all desktop applets are suppressed. In some embodiments, performing the auxiliary function includes displaying a desktop applet user interface that exposes one or more desktops of the one or more applications (including the desktop applet of the first application). The desktop applet user interface described herein is optionally the same or similar to the desktop applet user interface described with reference to fig. 8W. The above-described manner of suppressing the desktop applet corresponding to the application whose usage limit has been exceeded makes the user-device interface more efficient (e.g., the user does not have to monitor his own device usage for the application and the desktop applet associated with the application, thus reducing the user's input provided to the device (e.g., the input for monitoring usage is reduced)), which allows the electronic device to effectively reduce the overall usage of the electronic device, which in turn reduces power consumption and improves the battery life of the device.

In some embodiments, the auxiliary function includes presenting a visual indication (1332) of one or more applications (including the first application) for which the suggested conditions have been met in the suggested user interface (e.g., displaying application suggestions to the user on the electronic device in a system (e.g., operating system) user interface of the electronic device (rather than a user interface of a particular application on the electronic device), such as in FIG. 12.

The event corresponding to activation of the auxiliary function optionally includes a request (1334) to present a visual indication of the one or more applications in the suggestion user interface that the suggestion condition has been met (e.g., input from a user for displaying application suggestions on the electronic device), such as in fig. 12B-12C. In some embodiments, suppressing the auxiliary function optionally includes presenting a suggested user interface without presenting a visual indication of the first application (1336) (e.g., without displaying the application in the suggested interface), such as in fig. 12M. For example, the first application will not be displayed with the commonly used application, even when the first application is commonly used. In another example, the first application will not be displayed in the search results even though the search prompting display of the search results encompasses the first application. In some implementations, a visual indication of the first application is displayed in a suggestion (or search result) user interface; however, it is masked to indicate that the constraints of the first application have been met. In some embodiments, the suggested user interface is suppressed (e.g., all applications are not displayed or hidden). In some embodiments, performing the auxiliary function includes presenting a suggested user interface including visual indications of the one or more applications, including visual indications of the first application (e.g., displaying the application in the suggested interface). The above-described suggested manner of suppressing applications where the usage limit has been exceeded allows the electronic device to effectively reduce the overall usage of the electronic device, which reduces power consumption and improves the battery life of the device.

The auxiliary function optionally includes displaying web content associated with the first application in a browser user interface (1338) (e.g., displaying web content or a website associated with the first application in a web browser), such as in fig. 12S. In some implementations, the event corresponding to activation of the auxiliary function includes a request (1340) for displaying web content associated with the first application in the browser user interface (e.g., input from a user for displaying web content or a website associated with the first application in the web browser), such as in fig. 12R. In some implementations, the suppression assist function includes blocking access to web content associated with the first application (1342) (e.g., forgoing displaying web site content associated with applications for which the usage limit has been reached), such as in fig. 12P. For example, if the usage limit of application A associated with website A has been reached, the display of website A (or content from website A) in the browser application will be prevented. If the usage limit has not been reached, the display of website A will optionally not be blocked. In some embodiments, the electronic device will suppress not only applications whose usage limit has been exceeded, but also any websites associated with the application. The electronic device optionally presents a visual indication of the constraint (e.g., a screen or other image that masks the web page content) in place of the web site content when the constraint is met. In some implementations, performing the auxiliary function includes presenting web content associated with the first application in the browser (e.g., displaying a website in the browser). The web sites associated with applications described herein are optionally the same or similar to the web sites associated with applications described with reference to method 900. The manner in which the above-described web content-associated applications whose usage limits have been exceeded is suppressed makes the user-device interface more efficient (e.g., the user does not have to monitor his own device usage for the application and the website associated with the application, thus reducing the input the user provides to the device (e.g., the input for monitoring usage is reduced)), which allows the electronic device to effectively reduce the overall usage of the electronic device, which in turn reduces power consumption and improves the battery life of the device.

In some embodiments, blocking access to the web content associated with the first application includes (1344) loading the web content associated with the first application from the first website (1346) (e.g., content of the website associated with the application whose usage limit has been exceeded is loaded by the electronic device (e.g., downloaded to local memory)), such as in fig. 12Q. In some embodiments, blocking access to the web content associated with the first application includes (1344) forgoing displaying the web content (1348) associated with the first application (e.g., the web content is loaded but not displayed by the electronic device), such as in fig. 12Q. In some implementations, the electronic device displays some user interface element (e.g., a pop-up dialog box or a splash screen) on the content that blocks the display of the content and/or indicates that the content is blocked because the usage limit of application a has been reached. Additionally or alternatively, the web content is optionally displayed, but in a hidden manner (e.g., distorted, grayed out, faded out, and/or visually altered). The above-described manner of suppressing the application associated with web content for which the constraints are met (e.g., the usage limit has been exceeded or the device is in a restricted mode) makes the user-device interface more efficient (e.g., the user does not have to monitor his own device usage for the application and the website associated with the application, thus reducing the user's provided input to the device (e.g., the input for monitoring usage is reduced)), which allows the electronic device to effectively reduce the overall usage of the electronic device, which in turn allows the electronic device to cache web content for future use, which in turn reduces power consumption and improves the device's battery life, while improving execution speed.

In some implementations, blocking access to the web content associated with the first application includes (1350) relinquishing display of the web content associated with the first application while maintaining display of one or more user interface elements (e.g., one or more graphical user interface buttons, text input fields) in the browser user interface for navigating to another website (1352) (e.g., for navigating to other websites, for navigating within a website), such as in fig. 12R. In some implementations, the browser's navigation control (e.g., a URL field or button on the browser) remains operable while the particular web content associated with the application for which the constraints are met is limited. In some embodiments, websites not associated with any applications on the electronic device remain accessible when the constraints of one or more applications on the electronic device are met. For example, when access to a website associated with a first application is restricted, the navigation control of the browser is not restricted, optionally allowing the user to navigate to other websites. The above-described manner in which the suppression constraints are met for web content-associated applications while allowing access to other websites makes the user-device interface more efficient (e.g., the user does not have to monitor his own device usage for the application and the website associated with the application, thus reducing user-provided input to the device (e.g., the input for monitoring usage is reduced)), which allows the electronic device to effectively reduce overall usage of the electronic device, which in turn reduces power consumption and improves battery life of the device.

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

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 when the restriction condition of the first application is met (1356), in accordance with a determination that the second website is associated with the first application, the electronic device relinquishes (1358) displaying the second web content (e.g., restricts access to web content from all websites associated with the application for which the restriction condition is met (e.g., the usage limit has been reached, the device is in a restricted access mode, etc.), such as in fig. 12P. In some implementations, the electronic device displays an image (e.g., a pop-up dialog box or a splash screen) on the content that blocks the display of the content and/or indicates that the content is blocked because the usage limit of application a has been reached. Additionally or alternatively, the web content is optionally obscured and displayed (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 when the restriction condition of the first application is satisfied (1356), in accordance with a determination that the second website is associated with the second application and the restriction condition of the second application is not satisfied, the electronic device displays (1360) the second web content (e.g., web content associated with an application for which the display restriction condition is not satisfied (e.g., the usage limit has been reached or the device is in a restricted access mode, etc.), such as in fig. 12S. In some embodiments, only websites associated with applications where the constraints are met are restricted and the user is allowed to navigate to other websites. In some embodiments, websites not associated with any applications on the electronic device are also accessible when the constraints of one or more applications on the electronic device are met. The above-described manner in which the suppression constraints are met for web content-associated applications while allowing access to other websites makes the user-device interface more efficient (e.g., the user does not have to monitor his own device usage for the application and websites associated with the application, thus reducing the input provided by the user to the device (e.g., the input for monitoring usage is reduced)), which allows the electronic device to effectively reduce the overall use of the electronic device, which in turn reduces power consumption and improves the battery life of the device.

In some implementations, the auxiliary function includes displaying media content in a picture-in-picture user interface of the first application that partially overlaps one or more other user interfaces (1362) (e.g., displaying a picture-in-picture (PIP) window on another user interface (e.g., on a main screen, a main user interface of another application, or a user interface of another application), such as in fig. 12V). Events corresponding to activation of the auxiliary function optionally include a request for displaying media content in a picture-in-picture user interface of the first application (1364) (e.g., a request for viewing content from the first application in a PIP window, etc.), such as in fig. 12V. In some examples, the PIP window is already displaying content from the first application and the request is to continue displaying the content (e.g., receive content for display). In some implementations, suppressing the auxiliary function includes suppressing a picture-in-picture user interface (1366) of the first application (e.g., forgoing displaying the PIP window, stopping displaying content in the PIP window), such as in fig. 12W. For example, if the use limit of application a has been reached, the user will not be able to bypass the limited access of application a by attempting to launch the PIP window of the application (e.g., the PIP window will not be displayed). In some embodiments, the PIP window of the application will be currently displayed when the application's use limit is met, and the electronic device will suppress this function by stopping displaying the PIP window or otherwise hiding the PIP window of the first application (e.g., graying out or fading out the PIP window). In some implementations, the PIP window is a window that plays back media (e.g., movies, television programs, music, etc.) on an electronic device using a media playback application on the electronic device. If the usage limit has not been reached, the display of the PIP window optionally will not be blocked (e.g., will not be suppressed). In some embodiments, performing the auxiliary function includes displaying the PIP window of the first application partially overlapping one or more other user interfaces. The above-described manner of suppressing the PIP window associated with an application whose usage limit has been exceeded makes the user-device interface more efficient (e.g., the user does not have to monitor his own device usage for the application and the PIP window associated with the application, thus reducing the input the user provides to the device (e.g., the input for monitoring usage is reduced)), which allows the electronic device to effectively reduce the overall usage of the electronic device, which in turn reduces power consumption and improves the battery life of the device.

In some implementations, the suppression of the picture-in-picture user interface of the first application includes (1368): in accordance with a determination that the constraints of the first application are met (1370) when the PIP user interface of the first application is displayed (e.g., the use limits of the application are met when the application is being used in PIP mode), the PIP user interface is hidden (1372) for a first period of time (e.g., the PIP window is visually changed and/or blocked), such as in fig. 12W. In some implementations, the PIP window will continue to display content from the first application but the content will be visually altered (e.g., obscured, displayed in grayscale, or watermarked). In some implementations, the PIP window will cease displaying content from the first application and instead will display other information (e.g., a visual indication that the 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 soft button) for closing the PIP window.

In some implementations, the suppression of the picture-in-picture user interface of the first application includes (1368): in accordance with a determination that the constraints of the first application are met (1370) when the PIP user interface of the first application is displayed (e.g., the use limits of the application are met when the application is being used in PIP mode), the PIP user interface is stopped from being displayed after a first period of time (1374) (e.g., the PIP window will automatically close after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds)), such as in fig. 12X. For example, the content of the PIP window will fade out and the PIP window will automatically close after that period of time.

In some embodiments, the time period is specified by a user in a setting of the electronic device. In some embodiments, in accordance with a determination that a constraint of the first application is satisfied when the picture-in-picture user interface of the first application is not displayed, the electronic device detects, with the one or more input devices, a user input corresponding to a request to display the picture-in-picture user interface of the first application (e.g., detects an input for displaying the PIP user interface of the first application when the constraint is satisfied), and in response to the user input corresponding to the request to display the picture-in-picture user interface of the first application, the electronic device relinquishes displaying the picture-in-picture user interface of the first application when the constraint of the first application is satisfied (e.g., the constraint of the first application is satisfied when the PIP window of the first application is not being displayed), and the electronic device prevents the window from launching at a later time. Thus, once the limit of use of a particular application has been exceeded, the user of the electronic device cannot bypass the restrictions on that particular application. The manner in which the above-described suppression constraints are met for the PIP window associated with the application makes the user-device interface more efficient (e.g., the user does not have to monitor his own device usage for the application and the PIP window associated with the application, thus reducing the input the user provides to the device (e.g., the input for monitoring usage is reduced)), which allows the electronic device to effectively reduce the overall use of the electronic device, which in turn reduces power consumption and improves the battery life of the device.

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

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

In some implementations, suppressing the auxiliary function includes preventing the plurality of affordances from controlling playback of media content associated with the first application (1380), such as in fig. 12 AA. In some implementations, the media control buttons will be displayed, but will be inoperable (e.g., the buttons will not perform the media control functions associated therewith). For example, the 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 operation when the play button is selected. In some embodiments, the inoperable media control buttons will be hidden (e.g., visually altered) in the media control user interface. In some embodiments, when a constraint of a particular media playback application (e.g., a movie playback application, a television program playback application, or a music playback application) is met, access to a media playback control for controlling playback of the media playback application is suppressed by the electronic device. In some embodiments, these media playback controls are displayed in or otherwise limited to the application's own user interface (e.g., in a system or operating system user interface of an electronic device that is globally accessible on the electronic device). In some embodiments, the media playback controls are blocked such that as long as the application's usage limit is currently reached, they are no longer selectable to control playback of any media utilizing the media playback application. In some embodiments, the media control button is to be suppressed by preventing display by the electronic device (e.g., by preventing the media control user interface from being displayed or displaying a media control user interface without the media control button) when a constraint of a media playback application (e.g., a first application) is 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 automatically turned off (e.g., stopped displaying) after the period of time. The above-described manner of suppressing the media control buttons associated with applications for which the constraints are met makes the user-device interface more efficient (e.g., the user does not have to monitor his own device usage for the applications and the media control buttons associated with the applications, thus reducing the input provided by the user to the device (e.g., the input for monitoring usage is reduced)), which allows the electronic device to effectively reduce the overall usage of the electronic device, which in turn reduces power consumption and improves the battery life of the device.

In some implementations, preventing the plurality of affordances from controlling playback of media content associated with the first application includes (1382) entering an inactive state in which the device ignores user input for the plurality of affordances (e.g., entering 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) for a first period of time (1384) (e.g., for five minutes, fifteen minutes, one hour, or any user-defined period of time), such as in fig. 12 AA. For example, when the play button is in a frozen state, the play button will not play content in response to a selection input on the play button. In some embodiments, the frozen media control buttons will be hidden (e.g., visually altered) to indicate to the user that they are frozen. In some embodiments, even though the media control buttons in the frozen state are inoperable, they will indicate that the media was recently being played back (or potentially may be controlled by the media control buttons if the usage limit is reset), such as by displaying the title of the media, an image of the media, and so forth. In some embodiments, the period of time is the time that remains until the constraints of the particular application associated with the media control button are no longer met. In some embodiments, if a constraint of a particular media playback application is met while the media control is controlling playback of the media playback application (e.g., while the media playback application is playing media on an electronic device), the media control is frozen in its current state (e.g., indicating the current playback state of the media, the identity of the media (e.g., title), etc.), and is blocked from interaction from the user at the time the constraint becomes met. In some embodiments, when the playback control is placed in a frozen state, playback of the media is also stopped. In some embodiments, the media control is reset to its default state (e.g., indicating that no media is being played by the media playback application, indicating that no media title is present, etc.) for a certain period of time (e.g., 5 seconds, 10 seconds, 20 seconds) after being frozen.

In some implementations, preventing the plurality of affordances from controlling playback of media content associated with the first application includes (1382): after a first period of time, the plurality of affordances are brought from an inactive state to a default state (1386) (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 back, and thus does not control playback of the media), such as in fig. 12 AB. Thus, in some implementations, in the default state, the media control buttons no longer indicate the current playback state of the media, the identity (e.g., title) of the media, and so on. In some embodiments, this period of time is the time that remains before the usage limit of the particular application associated with the media control button is reset. In some implementations, the electronic device prevents presentation of media associated with any application for which the constraints are met, although the affordance for controlling the media content is reset to a default state. In some embodiments, the electronic device stops displaying the media control interface after the first period of time rather than entering the media control button into a default state. The manner in which the media control buttons are associated with applications in which the above-described suppression constraints are met makes the user-device interface more efficient (e.g., the user does not have to monitor his own device usage for applications and media control buttons associated with applications, thus reducing the input provided by the user to the device (e.g., the input for monitoring usage is reduced)), which allows the electronic device to effectively reduce the overall use of the electronic device, which in turn reduces power consumption and improves the battery life of the device.

It should be understood that the particular order in which the operations in fig. 13A-13H are described is merely exemplary and is not intended to suggest that the described order is the only order in which the operations may be performed. Those of ordinary skill in the art will recognize a variety of ways to reorder the operations described herein. In addition, it should be noted that the details of other processes described herein in connection with other methods described herein (e.g., methods 700, 900, 1100, and 1500) are equally applicable in a similar manner to method 1300 described above in connection with fig. 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 features of use limits, limited use modes, auxiliary functions, use limit settings, etc. on the electronic device described herein with reference to other methods (e.g., methods 700, 900, 1100, and 1500) described herein. For the sake of brevity, these details are not repeated here.

The operations in the above-described information processing method are optionally implemented by running one or more functional modules in an information processing apparatus such as a general purpose processor (e.g., as described in connection with fig. 1A-1B, 3, 5A-5H) or an application specific chip. Furthermore, the operations described above with reference to fig. 13A to 13H are optionally implemented by the components depicted in fig. 1A to 1B. For example, detection operation 1302, suppression operation 1306, and execution operation 1308 are optionally implemented by event sorter 170, event recognizer 180, and event handler 190. The event monitor 171 in the event sorter 170 detects a contact on the touch screen 504 and the event dispatcher module 174 communicates the event information to the application 136-1. The respective event identifier 180 of the application 136-1 compares the event information to the respective event definition 186 and determines whether the first contact at the first location on the touch screen corresponds to a predefined event or sub-event, such as a selection of an object on the user interface. When a respective 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. Event handler 190 optionally utilizes or invokes data updater 176 or object updater 177 to update the 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 apparent to one of ordinary skill in the art how other processes may be implemented based on the components depicted in fig. 1A-1B.

Remote management of limit settings

Users interact with electronic devices in a number of different ways, including using applications accessible on the device. In some cases, an administrator (e.g., a parent) remotely manages the limit settings at the limited device (e.g., the electronic device of its child). The embodiments described below provide a way for an electronic device to enable a limited device user to request administrator permissions to change one or more usage restriction settings of the limited device, either cryptographically at the limited device or at an authorizing device or other remote administrator. Requesting administrator authentication for changing usage restriction settings at a restricted device allows the electronic device to provide an efficient way to facilitate such changes when authentication is required by another party (e.g., a parent). This promotion enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing the user to interact with the device with less input), which reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device. It will be appreciated that people use the device. When a person uses a device, the person is optionally referred to as a user of the device.

Fig. 14A-14T illustrate an exemplary manner in which an electronic device manages limit settings with permissions optionally provided by another electronic device, according to some embodiments of the disclosure. The embodiments in these figures are used to illustrate the processes described below, including the processes described with reference to fig. 15A-15G.

Fig. 14A shows an exemplary device 500 having a touch screen 504, described with reference to fig. 5A-5H. The electronic device 500 shown in fig. 14A is associated with a restricted account, such as a child account associated with a set of user accounts (including one or more child user accounts and one or more parent user accounts) in a household. In some embodiments, the administrator or parent user account has permission to alter one or more limit settings of the child electronic device 500 (e.g., one or more limit settings described above with reference to fig. 10A-13H). Touch screen 504 optionally displays one or more user interfaces including various content. In the example shown in fig. 14A, the touch screen 504 displays an indication 1498-26 that the initial limit setting has been set for the electronic device (e.g., by the parent device) when not previously set. The indication 1498-26 includes information about which limit settings have been set and its details (e.g., "Monday to Thursday 6am-10pm device downtime" and "usage limits: news application, game category, and social media category"). Thus, in some embodiments, the device 500 displays the notifications 1498-26 when the parent device first sets the usage restriction settings for the device 500.

Fig. 14B illustrates a limit setting user interface displayed on the child device 500, such as described with reference to fig. 6A-6C, 8O-8Q, and 10A-10 AA. The limit settings 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 a plurality of affordances 1404a-e for modifying various limit settings of the electronic device (e.g., "device downtime" 1404a, "application limits" 1404b, "always allowed" 1404c, "content and privacy" 1404d, and "including complete website view data on parent device" 1404 e). The plant downtime 1404a is described in more detail above with reference to fig. 10A-11I. Application limit 1404b is described in more detail above with reference to fig. 8A-9K. 1404c is always allowed to be described in more detail above with reference to fig. 6A-13H. Opening the complete website view data 1404e included on the parent device optionally allows the parent device to present information about which websites the child device 500 accesses with the web browsing application. When this feature is turned off, the parent device optionally does not present usage information regarding which websites were accessed by the child device 500. However, accessing the website associated with the application installed on the child device 500 is optionally counted as accessing the application using the electronic device (e.g., the time taken to access the website associated with the application counts up the usage limits of the application or application class and is included in the usage data for the application and/or class). It should be appreciated that sharing screen time data with a parent or administrator device (e.g., as indicated by indication 1402) also includes sharing other usage data and limiting permissions, such as the ability to set device downtime, applications and functions that are always allowed, sharing and privacy permissions, content purchase settings, age-limited content consumption settings, etc., and such settings are optionally also subject to the remote management scheme of the present disclosure.

As shown in fig. 14B, the age of the child whose user account is associated with the device 500 is below a threshold age at which sharing screen time data with the parent of the child is optional. Thus, the electronic device 500 presents the indication 1408 that the screen time data is shared with the parent of the child, and does not present the settings for no longer sharing the screen time data with the parent of the child.

In fig. 14C, the electronic device 500 detects a contact 1403 at an affordance 1404a for altering one or more device downtime settings. In response to a request to change the setting, the electronic device 500 presents the authorization user interface shown in fig. 14D. As shown in fig. 14D, the authorization user interface includes an affordance 1406 for remotely requesting permission to change settings from a management account (e.g., from a parent account or parent device), and a keypad 1482 for entering a password for changing settings. In some embodiments, the password used to change the limit setting is different than the password used to unlock the electronic device 500 such that the password may be known to an administrator or parent, rather than the administrator or child not.

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

Fig. 14F shows an electronic device 500 associated with a user account of a parent. The electronic device 500 presents an indication 1489-20 regarding the child requesting permission to alter the limit settings at the child's electronic device. As shown in fig. 14F, in some embodiments, the indication 1489-20 includes information regarding which limit settings (e.g., equipment downtime) the child is attempting to change. A parent can approve (e.g., by selecting "allow" in indications 1498-20) or deny access to the child to the restriction settings at the child's electronic device (e.g., by selecting "deny" in indications 1498-20). If the parent refuses the child's request to change the limit setting, the child device cannot change the limit setting. If the parent approves the child's request for access to the limit settings at the child's electronic device, the child's electronic device presents a user interface for altering the limit settings. In some embodiments, when a parent approves a change to a limit setting, the child device is granted access to the limit setting for a predetermined period of time, for a single session (e.g., until the child exits the limit setting user interface), until one or more limit settings change, or until the child exits the limit setting user interface for more than a predetermined amount of time.

Fig. 14G shows an electronic device 500 associated with a child user account. The electronic device 500 presents a user interface 1410 for altering one or more settings (1411-1417) associated with the device downtime, such as in response to a "permit" in the parental selection indication 1498-20 in fig. 14F, or in response to a successful entry of a password in fig. 14D. As shown in fig. 14G, the electronic device 500 detects the contact 1403 and optionally further user input to change the device downtime start time from 10pm to 11 pm. As described above, parental authorization to alter one or more limit settings is optionally valid for a limited amount of time. Thus, the electronic device 500 presents an indication 1450 that a change to the device downtime settings may also be made for three minutes. As described above, other authorization time frames 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 set to 11pm to 5am for Monday to Tuesday, which was previously set to 10pm to 5am for Monday to Tuesday, as shown in FIGS. 14B to 14C).

When a child makes changes to the limit settings, the parent device optionally presents an indication describing which changes were 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 regarding the child device to change the device downtime from 10pm to 5am on Monday to 11pm to 5am on Monday to Tuesday. The indication 1498-22 includes an affordance for rejecting or allowing the change. Thus, the parent device is optionally able to override the setting changes made at the child device. If the parent device approves the child device's changes to the settings, the child device operates in accordance with those changes. For example, by approving a change in device downtime from 10pm to 5am to 11pm to 5am, the child device operates in a normal unrestricted mode up to 11pm, rather than starting from 10pm to operate in a restricted use mode.

If the parent rejects the setting change 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 change to the limit setting was denied by the parent (e.g., "father denied device downtime setting change"). Further, when the parent refuses the setting change made at the child device, the child device continues to operate according to the setting prior to the change. That is, the child device will optionally continue to transition from 10pm into the limited use mode.

Fig. 14K illustrates a usage control panel of device usage for a child presented at an electronic device 500 associated with a parent user account. The child device usage control board includes an indication 1416 of the overall usage of the child's device, an indication 1428 of how the usage of the child's device compares to the average usage of the device, a graph 1424 showing detailed device usage metrics, an indication 1434 of the longest session on the child's device for the day, an indication 1436 of device usage during device downtime, an indication 1422a-b of the use of applications and application categories for which the usage limit is set, an indication 1442 of the use of applications for which the usage limit is not set, and a plurality of affordances 1440a-c for altering the limit settings associated with the applications and categories presented in the control board user interface, such as described with reference to fig. 6L-6U.

As shown in fig. 14K, the dashboard user interface includes an indication 1442 of how long the child's electronic device was used to access the browser application, but does not include detailed information about which websites were accessed and how long they were accessed. However, the time it takes to access the web sites associated with the applications and categories for which the usage metrics are presented using the browser application is optionally counted as accessing the associated application using the electronic device (e.g., accessing one or more web sites associated with the news application is optionally counted as news application usage metrics and usage limits 1422 a).

FIG. 14L illustrates a limit setting user interface presented by the electronic device 500 associated with a child user account. As shown in fig. 14L, the setting "including complete website view data on parent device" 1404e is activated. When the settings are activated, the administrator or parent electronic device optionally presents information in the dashboard user interface as to which websites the child device accesses, as shown in FIG. 14M. In fig. 14M, the dashboard user interface includes, in addition to an indication 1442a of the total amount of time the child electronic device uses the browser application, indications 1442B and 1442c of the amount of time the child electronic device accesses website a and website B, respectively.

Fig. 14N shows a child limit setting user interface presented by the electronic device 500 associated with a parent user account. The limit setting user interface includes an indication of the use of the child device and a plurality of affordances 1404a-f for altering the limit settings of the child device, such as described with reference to fig. 8 AAL-8 AAN and 10Y-10 AA. If the child's age is greater than a threshold age (e.g., 13 years), the parent optionally has the option of removing and/or changing the screen time password required to make a change to the limit settings of the child electronic device at the child electronic device by selecting affordance 1404 f. As shown in fig. 14O, when the child's age is less than the threshold age, the parent device has the ability to change the screen time password by selecting the affordance 1404g, but the screen time password cannot be removed.

When a parent changes the limit settings of the child device, the child device optionally presents an indication of which settings have been changed. FIG. 14P shows an indication 1498-28 of a limit setting change presented at the electronic device 500 associated with a child user account. The indication 1498-28 includes information about which settings have been changed and how they have been changed (e.g., "dad has added one hour's usage limit to the browser application").

As described herein, the parent device is optionally able to access the child device's screen time data and make changes to one or more limit settings of the child device. It should be appreciated that sharing screen time data is one example of the types of information and permissions that are shared with a parent or administrator device. Here and throughout the specification, shared screen time data is understood to optionally include one or more of the following: the ability to view any of the usage metrics described above with reference to fig. 6A-6 AU (e.g., screen time, notification, pick up of device, etc.), the ability to set and update one or more limit settings (e.g., device downtime and/or usage limits), the ability to set one or more content and privacy settings, content purchase settings, age-limited content consumption settings, etc.

Once the child's age exceeds a predetermined threshold (e.g., 18 years), the child device is optionally able to stop sharing screen time data with the child's parent and/or take over control of the usage restriction settings on the child device from the parent device. FIG. 14Q shows an indication 1498-26 presented at the child device 500 that the child device is able to stop sharing screen time data with a parent of the child. Indications 1498-26 are optionally displayed when the age of the child exceeds a predetermined threshold (e.g., 18 years). When the child's age exceeds this threshold, the limit setting user interface of the child device is optionally updated to include settings for stopping sharing of screen time data with the child's parent. FIG. 14R illustrates a limit setting user interface presented at the child device 500 when the child's age exceeds a threshold at which sharing screen time data with the child's parent is optional. As shown in fig. 14R, the settings user interface is updated to include the affordance 1404h ("off-screen time sharing"). In some embodiments, the settings user interface on the child device 500 does not include the affordance 1404h when the child's age is less than a predetermined threshold (e.g., 18 years old). Fig. 14S shows the child device 500 detecting contact at the affordance 1404h.

In some embodiments, in response to this request to stop sharing screen time data with parents of the child, the child device requests permission from the parent device to stop sharing screen time data, optionally including displaying the authentication user interface shown in fig. 14D. The parent optionally can approve the request for the child device to cease sharing screen time data by providing a password or authentication at the child device, or by authenticating the request at the parent device, as described above with reference to fig. 14F. If permission to cease sharing of 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 for ceasing to share the screen time data. In some embodiments, parental permission to stop sharing screen time data is not required when the child's age exceeds an age threshold (e.g., 18 years).

As shown in fig. 14T, when the child device 500 no longer shares usage data with the parent of the child, the limit setting user interface is updated according to the change. In fig. 14T, the indication 1408 of the screen time data sharing with the parent of the child and the affordance 1404h for closing the screen time sharing are no longer presented in the limit-setting user interface. Optionally, the setting 1404e for switching to including complete website viewing data on the parent device also stops displaying. In some embodiments, after the child device stops sharing screen time data with the parent device, the user of the child device may freely alter the usage restriction settings on the child device (e.g., device downtime, usage limits, the ability to add/remove applications on the child device, alter content purchase settings, view age-restricted content, privacy settings, etc.) without requiring authorized input (e.g., a password or approval from the parent device).

Fig. 15A-15G are flowcharts illustrating a method 1500 of managing limit 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 in connection with fig. 1A-1B, fig. 1-3, fig. 4A-4B, and fig. 5A-5H. Some operations in method 1500 are optionally combined and/or the order of some operations is optionally changed.

As described below, the method 1500 provides a means for updating one or more limit settings associated with the electronic device 500 (e.g., a limited device) with permissions of another electronic device (e.g., an authorized device) or a user account. The method reduces the cognitive burden on the user when interacting with the device user interface of the present disclosure, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, improving the efficiency of user interaction with the user interface saves power and increases the time between battery charges.

In some embodiments, a first electronic device 500 (e.g., a smart phone, a smart watch, a tablet, a computer, a set top box, etc.) in communication with a display device (e.g., a display, a touch screen, a television, etc.) and one or more input devices (e.g., a touch-sensitive surface, a remote control, etc.) is limited in use when a limit setting limiting use of the first electronic device is active at the first electronic device (1502) (e.g., limiting use of one or more application programs, application program categories, overall device use, etc.), such as described with reference to methods 700, 900, 1100, and/or 1300, limited use modes available on the first electronic device, such as described with reference to methods 700, 900, 1100, and/or 1300, etc.), in some embodiments, the first electronic device is a limited device (e.g., a child or limited device associated with a set of related accounts including one or more parent or administrator accounts), such as described with reference methods 700, 900, 1100, and/or 1300, set up with reference to one or more parent or administrator accounts, such as described with reference to one or more of the set of limited accounts, limited use modes available on the first electronic device (e.g., one or more of limited user accounts) such as described with reference to one or more of the set of limited user accounts, limited use modes, such as described with reference to one or more limited user accounts, one or more limited use modes available electronic devices (e.g., one or more of limited use modes) such as described with reference to control devices 700, 900, 1100, and/or 1300, etc.) in some embodiments, wherein such usage restriction settings have been set by or controlled by an authorizing device, such as in fig. 14C. In some embodiments, this input to alter the usage restriction settings on the restricted device is detected at a usage restriction settings user interface displayed on the restricted device that displays information about the usage restriction settings valid on the restricted device.

In response to receiving the sequence of one or more inputs, in some embodiments, the sequence of one or more inputs includes an input corresponding to a request to request permission from a second electronic device, such as in fig. 14D-14E (or to an administrator account associated with the second electronic device), in response to receiving the sequence of one or more inputs, the request for permission is sent to a plurality of accounts (e.g., parents in a household) having administrator privileges, in some embodiments, unlike a first electronic device, for altering a usage restriction setting (1506) (e.g., a manner in which a user interface displayed by the restricted device provides a plurality of usage restriction settings at the restricted device, including providing a password at the restricted device for altering the settings, such as described with reference to methods 700, 900, 1100, and/or 1300, or requesting permission from an authorizing device for altering the usage restriction settings, or requesting permission from an administrator account associated with the second electronic device), the restricted device detecting that the request was entered into the authorized device for the usage restriction settings, the first electronic device, in some embodiments, the restricted device detecting that the first electronic device is notified of the restricted device (e.g., at the restricted device) has attempted to alter the usage restriction settings, such as in response to the first electronic device (e.g., 14), this notification on the authorizing device identifies the particular usage restriction setting that the limited device is attempting to change and/or includes information about how the limited device is attempting to change the usage restriction setting (e.g., a new value of the usage restriction setting detected at the limited device). In some embodiments, in response to an input to the change authorization detected at the authorization device, the authorization device transmits the change authorization to the restricted device, and the restricted device is allowed to change the usage restriction settings on the restricted device. In some embodiments, in response to an input detected at the authorizing device rejecting the change, the restricted device is not allowed to change the usage restriction setting on the restricted device and the usage restriction setting remains as it was before the detection of the change to the usage restriction setting).

In some embodiments, after transmitting (1510) a request to the second electronic device for permission to change the usage restriction settings, as in fig. 14D-14F, in accordance with a determination that an authorization response is received from the second electronic device (e.g., a user of the authorization device selects an "allowed" affordance displayed on a notification received at the authorization device), the first electronic device is allowed (1512) to change the usage restriction settings, such as in fig. 14G-14H; and in accordance with a determination that a rejection response is received from the second electronic device (e.g., a user of the authorizing device selects a "reject" affordance displayed on a notification received at the authorizing device), the first electronic device is rejected (1514) to alter the usage restriction settings, such as in fig. 14I. In some embodiments, the user of the limited device can instead enter a password at the limited device to allow the limited device to alter the usage settings even if no response is received from the authorizing device.

The manner in which the above-described modification of the usage restriction settings on the restricted device is controlled from the authorizing device allows the electronic device to provide an efficient way of facilitating such modification when it requires authorization from another party, which enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing the user to interact with the device with less input), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, allowing the first electronic device to change the usage restriction setting includes allowing the first electronic device to change the usage restriction setting (1516) before detecting a termination condition allowing the first electronic device to change the usage restriction setting, such as in fig. 14G (e.g., the restricted device is allowed to change the usage restriction setting after receiving approval from the authorizing device for a predetermined period of time (e.g., 30 seconds, 2 minutes, 5 minutes), the restricted device is allowed to change the restricted usage setting before the restricted device leaves the setting user interface in which such change is to take place (and optionally has to request permission again after leaving the setting user interface), the restricted device is allowed to change the restricted usage setting before the restricted device confirms the setting change (e.g., by performing a "save" or "good" or "return" selection of setting changes in the setting user interface that enables the setting), the restricted device is allowed to change the restricted usage setting before the restricted device leaves the setting user interface for more than a predetermined amount of time (e.g., 30 seconds, 2 minutes, 5 minutes).

The above-described ability to variously limit the alteration of the usage restriction settings by the restricted device in accordance with the approval allows the electronic device to manage such approval so that it is not unrestricted, which enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing the authorized device to effectively manage the alteration of the usage settings on the restricted device), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and effectively use the device.

In some embodiments, after allowing the first electronic device to change the usage restriction settings, the first electronic device changes the usage restriction settings and changes operation of the first electronic device according to the change in the usage restriction settings (1518), such as in fig. 14H (e.g., changes an application or application usage limit valid on the restricted device according to the change in the usage settings, changes device downtime on the restricted device according to the change in the usage settings, etc., such as described in methods 700, 900, 1100, and/or 1300).

The manner of operating a limited device according to updated usage limit settings described above allows the electronic device to provide an efficient way of implementing such updates, which enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing a user to interact with the device with less input), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, in response to receiving the sequence of one or more inputs, in accordance with a determination that the sequence of one or more inputs includes an input (1520) corresponding to an input of an authorization credential, such as at least at a keypad 1482 shown in fig. 14D (e.g., a password, biometric feature, or other authorization credential for altering a usage restriction setting, as described in methods 700, 900, 1100, and/or 1300), upon which the authorization credential is successfully authenticated (e.g., a user of the restricted device enters a correct credential for altering the usage restriction setting), the first electronic device is permitted (1522) to alter the usage restriction setting, such as in fig. 14G-14H; and based on the authorization credential not being successfully authenticated (e.g., the user of the restricted device entered an incorrect credential for altering the usage restriction setting), the first electronic device relinquishes (1524) the first electronic device permission to alter the usage restriction setting, such as in fig. 14J. Thus, in some embodiments, the restricted device is allowed to change the usage restriction settings in response to the authorization credential being entered at the restricted device (rather than receiving authorization from the authorizing device). In some embodiments, when an authorization credential is entered at the restricted device, no request for permission is transmitted to the authorizing device.

The manner described above of providing a password or other authorized input at the restricted device for altering the use restriction settings allows the electronic device to provide an efficient way (e.g., locally) of allowing such updates, which enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing the user to interact with the device with alternative inputs), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the first electronic device receives (1526), via the one or more input devices, input for allowing or disallowing sharing of website viewing activity on the first electronic device identifying one or more websites that have been viewed on the first electronic device with the second electronic device (e.g., allowing or disallowing the authorizing device to view the names/identities of the various websites that the user of the restricted device has viewed (compared to the total website viewing time, the authorizing device optionally being able to view the total website viewing time, regardless of whether the restricted device allows or disallows sharing of individual website viewing sharing), in a manner similar to the dialogues 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 viewing data if the user of the account of the restricted device is greater than a predetermined age (e.g., 10 years, 13 years, 18 years), otherwise cannot control this sharing of data). In response to receiving an input (1528) to allow or disallow sharing of website viewing activity with the second electronic device, in a manner similar to the allowing or disallowing described above with reference to fig. 14F, in accordance with a determination that the input allows sharing of website viewing activity with the second electronic device that identifies the one or more websites that have been viewed on the first electronic device, the first electronic device shares website viewing activity with the second electronic device that identifies the one or more websites that have been viewed on the first electronic device, such as in fig. 14M (e.g., information (e.g., network address, title/name, etc.) of individual websites that the user of the limited device is able to view and/or time spent viewing those individual websites); and in accordance with a determination that the input does not allow sharing of website viewing activities with the second electronic device that identify the one or more websites that have been viewed on the first electronic device, the first electronic device relinquishes (1532) the website viewing activities with the second electronic device that identify the one or more websites that have been viewed on the first electronic device, such as in fig. 14K (e.g., information (e.g., network address, title/name, etc.) of each website that the user of the restricted device cannot view and/or time it takes to view that each website).

The manner of controlling sharing of personalized website usage information described above allows an electronic device to provide an efficient way of maintaining privacy at a restricted device while still facilitating enforcing usage restrictions, which enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing a user to interact with the device with less input), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, when the setting is enabled to disallow sharing of website viewing activity with the second electronic device that identifies the one or more websites that have been viewed on the first electronic device, the first electronic device shares (1534) website viewing activity with the second electronic device that does not identify the one or more websites that have been viewed on the first electronic device, such as in fig. 14K (e.g., while the authorizing device cannot view individual website viewing information from the limited device, the authorizing device can view information about general network usage on the limited device, such as the total amount of time spent on the limited device viewing websites, and cannot view which websites are viewed, what time periods of day the websites are viewed, the duration of each session of viewing the website, and/or the particular web page or subdomain being viewed, and conversely, the amount of time the website is used is aggregated with application usage).

The manner described above of continuing to share general network usage information with an authorized device allows the electronic device to provide an efficient way of enforcing usage restrictions even when personalized website usage information is not shared with the authorized device, which enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing the user to interact with the device with less input), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, when the setting is enabled to disallow website viewing activity with the second electronic device that identifies the one or more websites that have been viewed on the first electronic device, the first electronic device shares (1536) website viewing activity with the second electronic device that corresponds to one or more applications or one or more application categories, such as in FIG. 14K (e.g., sharing aggregate statistics with the second electronic device regarding the use of the first application and access to websites associated with the first application using a web browser and aggregate statistics regarding the use of the second application and access to websites associated with the second application, without sharing specific information regarding the web browsing activity performed at the web browser) (e.g., even if the authorizing device is unable to view individual website viewing information from the restricted device, the authorizing device is able to view information regarding the website viewing activity corresponding to the application (e.g., ESPN viewing as an ESPN application is reflected on the authorizing device) or the application category (e.g., application is restricted to the application category as a restricted user of the application) when the application is restricted from being applied to the restricted user categories such as in the method of the restricted user categories, such that the social media viewing device is restricted in view category 700, 1100 and/or 1300).

The manner in which website usage data corresponding to the application/application categories is reflected described above allows the electronic device to provide an efficient way of enforcing usage restrictions even when personalized website usage information is not shared with authorized devices, which enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing the user to interact with the device with less input), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, in accordance with a determination that the age of the user associated with the account of the first electronic device is less than a predetermined age (e.g., 10 years old, 13 years old, 15 years old), the second electronic device is prevented from removing (e.g., the second electronic device cannot remove) the requirement that the authorization be required at the first electronic device for altering the use restriction setting (1538), such as in fig. 14O (e.g., the authorization device cannot remove the requirement that the password or other authorization credential or action (such as authorization device approval) be required at the restricted device for altering the use restriction setting).

The manner described above of providing the authorizing device with a controlled capability for removing password requirements from the restricted device allows the electronic device to provide an efficient way of enforcing usage restrictions even when personalized website usage information is not shared with the authorizing device, which enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing the user to interact with the device with less input), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, after the requirement for changing the usage restriction settings to require authorization at the first electronic device has been removed, the first electronic device and the second electronic device can change the usage restriction settings at the first electronic device, including the usage restriction settings (1542), such as allowing the first electronic device to change one or more settings, as described above with reference to fig. 14G (e.g., once the password is removed, both the authorization device or the administrator account and the restricted device can change the restrictions and limits valid on the restricted device).

The above-described manner of allowing both the restricted device and the authorized device to make changes to the use restriction settings when the password requirements are removed allows the electronic device to provide an efficient way of facilitating such changes while maintaining the ability of the authorized device to affect the use restriction settings on the restricted device, which enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing the user to interact with the device with less input), which in turn reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, in accordance with a determination that the age of the user associated with the account of the first electronic device is greater than a predetermined age (e.g., 15 years, 18 years), the first electronic device is able to cease sharing device usage information with the second electronic device (1544), such as in fig. 14R-14T (e.g., the restricted device is able to cease the ability of the authorizing device or the administrator account to view usage information about the restricted device).

The manner of controlling when a limited device can cease sharing usage information with an authorized device described above allows an electronic device to provide an efficient way of controlling such capabilities, which enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing a user to interact with the device with less input), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, ceasing to share device usage information with the second electronic device requires approval from the second electronic device to cease 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 limited device cannot cease sharing usage information with the authorized device without approval from the authorized device or an administrator account).

The above-described manner of requiring approval of the authorizing device for the cessation of usage information sharing with the authorizing device allows the electronic device to provide an efficient way of authorizing device control of such changes, which enhances device operability and makes the user-device interface more efficient (e.g., by allowing a user to interact with the device with less input), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, ceasing to share device usage information with the second electronic device does not require approval from the second electronic device to cease sharing device usage information with the second electronic device (1550), such as in FIG. 14T (e.g., the restricted device is able to cease sharing usage information with the authorized device without approval from the authorized device or an administrator account).

The above-described manner of not requiring authorized device approval for decommissioning information sharing allows electronic devices to provide an efficient way of decommissioning such sharing, which enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing the user to interact with the device with less input), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, in response to determining that the user associated with the account of the first electronic device has reached a predetermined age (e.g., based on the user's birthday and current date/time), the first electronic device generates (1552) a notification indicating that the first electronic device is able to cease sharing device usage information with the second electronic device, such as in fig. 14Q (e.g., the restricted device displays a notification when the user of the restricted device reaches an age at which the user is able to cease sharing usage information with the authorized device, such that the user knows that they are now able to take such action).

The manner in which notifications are generated for a user of a limited device when the user is able to alter the information sharing with an authorized device described above allows the electronic device to provide an efficient way to facilitate such alterations, which enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing the user to interact with the device with less input), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, in accordance with a determination that the age of the user associated with the account of the first electronic device is greater than a predetermined age, a control for ceasing sharing of device usage information with the second electronic device is available for use on the first electronic device (1554), such as in fig. 14R-14S (e.g., an affordance for altering usage information sharing with an authorizing device, a button or control is displayed and enabled in a usage restriction settings user interface on a restricted device), and in accordance with a determination that the age of the user associated with the account of the first electronic device is less than a predetermined age, a control for ceasing sharing of device usage information with the second electronic device is not available for use on the first electronic device (1556), such as in fig. 14B (e.g., an affordance for altering usage information sharing with an authorizing device, a button or control is not displayed in a usage restriction settings user interface on a restricted device, or is displayed but not enabled in a usage restriction settings user interface on a restricted device).

The above-described manner of using controls for altering information sharing with an authorized device to be available or unavailable allows an electronic device to provide an efficient way of facilitating such alterations while meeting constraints on the ability to make such alterations, which enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing a user to interact with the device with less input), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the age of the user associated with the account of the first electronic device is greater than a predetermined age (1558), such as in fig. 14R-14S; the first electronic device receives (1560) input for stopping sharing device usage information with the second electronic device, such as in fig. 14S, via the one or more input devices; and in response to receiving input to cease sharing device usage information with the second electronic device, the first electronic device ceases (1562) sharing device usage information with the second electronic device, such as in fig. 14T (e.g., a button or a toggle key in a user-selected usage restriction settings user interface of the restricted device for ceasing sharing of usage information with the authorized device). In some embodiments, after ceasing to share device usage information with the second electronic device, the first electronic device can change the usage restriction settings on the first electronic device and the second electronic device cannot change the usage restriction settings on the first electronic device (1564) in a similar manner as described above with reference to FIG. 14G (e.g., once usage information sharing and/or usage restriction sharing with an authorized device or administrator account has been disabled, the previously restricted device can change the usage restriction settings on the previously restricted device, but the authorized device or administrator account can no longer change such settings on the previously restricted device).

The above-described manner of allowing a previously restricted device to make changes to the usage restriction settings on the device, but not allowing the authorizing device to do so, allows the electronic device to operate independent of the authorizing device in terms of usage restrictions, which enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing the user to interact with the device with less input), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, when the first electronic device is allowed to change the usage restriction settings (1566), such as in fig. 14G, the first electronic device receives (1568) a sequence of one or more inputs for changing one or more usage restriction settings on the first electronic device via the one or more input devices (e.g., after receiving approval from the authorizing device to change the usage restriction settings on the restricted device, a user of the restricted device provides an input to the restricted device for changing the usage restriction settings (such as changing one or more usage limits valid on the restricted device, changing device downtime settings valid on the restricted device, etc.); in response to receiving the sequence of one or more inputs for altering the one or more usage restriction settings on the first electronic device, the first electronic device transmits (1570) information regarding the alteration of the one or more usage restriction settings on the first electronic device to the second electronic device, such as in fig. 14I (e.g., the restricted device transmits information regarding the alteration of the usage restriction settings that the restricted device has attempted to make to an authorizing device or an administrator account (e.g., information regarding all alterations attempted at the restricted device, such as a particular usage limit alteration, a particular device downtime alteration, etc.). In some embodiments, the restricted device makes an alteration to the restricted usage setting and in connection with making the alteration transmits information regarding the alteration to the authorizing device, the authorizing device optionally displaying a notification of the alteration so that a user of the authorizing device can see the alteration made on the restricted device; in contrast, in such embodiments, the authorizing device optionally must manually make changes to the usage restriction settings of the restricted device to reverse any changes made by the restricted device, in contrast, in some embodiments, the restricted device does not make changes to the restricted usage settings and first transmits information regarding the attempted changes to the authorizing device, the authorizing device optionally displays a notification of the attempted changes so that the user of the authorizing device can see the changes intended on the restricted device, the notification optionally has a mechanism (e.g., an optional affordance) by which the user of the authorized device can cancel/reject/invalidate or approve the attempted change of the restricted device.

The manner in which information regarding usage restriction changes is transmitted to the authorizing device described above allows the electronic device to efficiently communicate such changes to the authorizing device, which enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing the device to operate with less input from the user), which in turn reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, in accordance with a determination that one or more usage restriction settings at the first electronic device have been remotely changed (e.g., by the second electronic device or another electronic device associated with a user that is allowed to change the usage restriction settings of the first electronic device, such as an administrator account), the first electronic device displays a notification (1572) indicating the second electronic device's change to the one or more usage restriction settings at the first electronic device, such as in fig. 14P (e.g., the limited device receives information from the authorizing device regarding the authorizing device's update to the usage restriction settings on the limited device, and in response, the limited device displays a notification on the limited device with details of the change (e.g., change to the usage limit, device downtime, etc.) so that the user of the limited device can see the change made by the authorizing device).

The manner of displaying notifications with usage restriction changes made by an authorized device at a restricted device described above allows an electronic device to provide an efficient way to provide such changed information to a user of the restricted device, which enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing the user to interact with the device with less input), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

In some embodiments, the one or more usage restriction settings at the first electronic device are remotely altered including defining initial usage restriction settings at the first electronic device when no usage restriction settings were previously active at the first electronic device (1574), such as in FIG. 14A (e.g., the restricted device receives information from an authorized device or an administrator account regarding those restrictions that are active on the restricted device when the authorized device validates the initial usage restriction, and in response, the restricted device displays on the restricted device notifications with details of those initial restrictions (e.g., usage limits, device downtime, etc.) such that a user of the restricted device can see the usage restrictions now active at the restricted device in some embodiments, the notifications include information regarding all restrictions now active on the restricted device (e.g., each usage limit, each characteristic of device downtime, etc.), in some embodiments, the notifications instead include an overview of critical gaming limits now active on the restricted device, such as a total limit of gaming (but not all screen limits) and the total limits of all devices (but not all limits) and no device downtime, etc.).

The manner of displaying the notification with the initial use restriction settings made by the authorizing device at the restricted device described above allows the electronic device to provide an efficient way to provide information of such settings to the user of the restricted device, which enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing the user to interact with the device with less input), which in turn reduces power usage and improves battery life of the device by enabling the user to more quickly and efficiently use the device.

It should be understood that the particular order in which the operations in fig. 15A-15G are described is merely exemplary and is not intended to suggest that the described order is the only order in which the operations may be performed. Those of ordinary skill in the art will recognize a variety of ways to reorder the operations described herein. In addition, it should be noted that the details of other processes described herein with respect to other methods described herein (e.g., methods 700, 900, 1100, and 1300) also apply in a similar manner to method 1500 described above with reference to fig. 15A-15G. For example, the methods of updating limit settings at one electronic device with permissions of another electronic device or user account described above with reference to method 1500, use limit settings, etc., optionally have one or more of the characteristics of using the metric control panel user interface, use metrics, notification metrics, picking up device metrics, use 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 are not repeated here.

The operations in the above-described information processing method are optionally implemented by running one or more functional modules in an information processing apparatus such as a general purpose processor (e.g., as described in connection with fig. 1A-1B, 3, 5A-5H) or an application specific chip. Furthermore, the operations described above with reference to fig. 15A to 15G are optionally implemented by the components depicted in fig. 1A to 1B. For example, display operation 1572 and receive operations 1504, 1526, 1560, and 1568 are optionally implemented by event sorter 170, event recognizer 180, and event handler 190. The event monitor 171 in the event sorter 170 detects a contact on the touch screen 504 and the event dispatcher module 174 communicates the event information to the application 136-1. The respective event identifier 180 of the application 136-1 compares the event information to the respective event definition 186 and determines whether the first contact at the first location on the touch screen corresponds to a predefined event or sub-event, such as a selection of an object on the user interface. When a respective 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. Event handler 190 optionally utilizes or invokes data updater 176 or object updater 177 to update the 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 apparent to one of ordinary skill in the art how other processes may be implemented based on the components depicted in fig. 1A-1B.

As described above, one aspect of the disclosed technology is to collect and use data from various sources to control and/or present device usage information to a user. The present disclosure contemplates that in some examples, such collected data may include personal information data that uniquely identifies or may be used to contact or locate a particular person. Such personal information data may include demographic data, location-based data, telephone numbers, email addresses, twitter IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital signs measurements, medication information, exercise information), birth dates, or any other identification or personal information.

The present disclosure recognizes that the use of such personal information data in the present technology may be used to benefit users. For example, personal information data may be used to present or control device usage in a manner that is meaningful to the user. Thus, the use of such personal information data enables users to more personally provide such services. In addition, the present disclosure contemplates other uses for personal information data that are beneficial to the user. For example, health and fitness data may be used to provide insight into the overall health of a user, or may be used as positive feedback to individuals using technology to pursue health goals.

The present disclosure contemplates that entities responsible for gathering, analyzing, disclosing, transmitting, storing or otherwise using such personal information data will comply with established privacy policies and/or privacy practices. In particular, such entities should exercise and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as the collection and/or use of data changes. Personal information from users should be collected for legal and reasonable use by entities and not shared or sold outside of these legal uses. In addition, such collection/sharing should be performed after informed consent is received from the user. In addition, such entities should consider taking any necessary steps to defend and secure access to such personal information data and to ensure that other persons having access to personal information data adhere to their privacy policies and procedures. In addition, such entities may subject themselves to third party evaluations to prove compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted to collect and/or access particular types of personal information data and to suit applicable laws and standards including specific considerations of jurisdiction. For example, in the united states, the collection or acquisition of certain health data may be governed by federal and/or state law, such as the health insurance transfer and liability act (HIPAA); while health data in other countries may be subject to other regulations and policies and should be processed accordingly. Thus, different privacy practices should be maintained for different personal data types in each country.

In spite of the foregoing, the present disclosure also contemplates embodiments in which a user selectively prevents use or access to personal information data. That is, the present disclosure contemplates that hardware elements and/or software elements may be provided to prevent or block access to such personal information data. For example, in terms of presenting information about device usage, the disclosed techniques may be configured to allow a user to choose to "join" or "exit" to participate in the collection of personal information data during registration with a service or at any time thereafter. As another example, a user may choose not to provide user-based or device-based usage data for determining device usage and/or controlling such usage. In addition to providing the "opt-in" and "opt-out" options, the present disclosure contemplates providing notifications related to accessing or using personal information. For example, the user may be notified that his personal information data will be accessed when the application is downloaded, and then be reminded again just before the personal information data is accessed by the application.

Further, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of inadvertent or unauthorized access or use. Once the data is no longer needed, risk can be minimized by limiting data collection and deleting the data. In addition, and when applicable, included in certain health-related applications, the data de-identification may be used to protect the privacy of the user. De-identification may be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at a city level instead of at an address level), controlling how data is stored (e.g., aggregating data on a user), and/or other methods, as appropriate.

Thus, while the present disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that the various embodiments may be implemented without accessing such personal information data. That is, various embodiments of the present technology do not fail to function properly due to the lack 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 or absolute minimum metrics of personal information (such as content requested by a device associated with a user, other non-personal information available to the device, or publicly available information).

The foregoing description, for purposes of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application to thereby enable others skilled in the art to best utilize the invention and various described embodiments with various modifications as are suited to the particular use contemplated.

Claims

1. A method, comprising:

at an electronic device in communication with a display and one or more input devices:

detecting an event corresponding to activation of an auxiliary function of a first application including a plurality of applications installed on the electronic device while enforcing restrictions on the one or more applications as to how many times and/or when one or more usage limits of access are satisfied by the one or more applications, wherein the auxiliary function of the first application is a function adapted to be executed without displaying a main user interface of the first application; and

in response to detecting the event corresponding to activation of the auxiliary function of the first application:

in accordance with a determination that the first application's constraints have been met, suppressing

Preparing the auxiliary function; and

in accordance with a determination that the constraint is not satisfied, the application is not displayed

The auxiliary function is executed in the case of the user main interface.

2. The method according to claim 1, wherein:

the auxiliary function includes presenting an indication of a first type of notification associated with the first application in response to occurrence of an event corresponding to activation of the notification.

3. The method according to claim 2, wherein:

suppressing the auxiliary function includes discarding presentation of the first type of indication in response to the notification associated with the first application; and

performing the auxiliary function includes presenting the first type of indication in response to the notification associated with the first application.

4. A method according to claim 3, further comprising, in accordance with a determination that the constraint of the first application is satisfied:

the visual indication of the first type of indication is included in a notification history user interface that also includes one or more indications of notifications generated by one or more applications other than the first application.

5. The method of claim 2, wherein suppressing the auxiliary function comprises discarding an indication of the first type presented in response to the notification generated by the first application, and further comprising:

after suppressing the auxiliary function of the first application:

determining that the constraint of the first application is no longer satisfied; and

in response to determining that the constraint of the first application is no longer met, the indication of the notification generated by the first application is presented.

6. The method according to claim 1, wherein:

the auxiliary function includes displaying a desktop applet user interface that exposes one or more auxiliary user interfaces of one or more applications, the one or more auxiliary user interfaces including an auxiliary user interface of the first application;

the event corresponding to activation of the auxiliary function includes a request to display the desktop applet user interface; and

suppressing the auxiliary function includes displaying the desktop applet user interface while suppressing the auxiliary user interface of the first application.

7. The method according to claim 1, wherein:

the auxiliary function includes presenting in a suggestion user interface a visual indication of one or more applications including the first application that a suggestion condition has been met;

the event corresponding to activation of the auxiliary function includes a request to present a visual indication in the suggested user interface that the suggested condition has been met for the one or more applications; and

suppressing the auxiliary function includes presenting the suggested user interface without presenting a visual indication of the first application.

8. The method according to claim 1, wherein:

the auxiliary function includes displaying web content associated with the first application in a browser user interface;

the event corresponding to activation of the auxiliary function includes a request to display web content associated with the first application in the browser user interface; and

suppressing the auxiliary function includes blocking access to the web content associated with the first application.

9. The method of claim 8, wherein blocking access to the web content associated with the first application comprises:

loading the web content associated with the first application from a first website, and

the web content associated with the first application is forgone display.

10. The method of claim 8, wherein blocking access to the web content associated with the first application comprises:

the web content associated with the first application is relinquished from display while maintaining display of one or more user interface elements in the browser user interface for navigating to another website.

11. The method of claim 8, further comprising:

detecting a second event corresponding to a request to view second web content from a second website in the browser user interface when the constraint condition of the first application is satisfied;

in response to detecting the second event corresponding to a request to view the second web content from the second website in the browser user interface when the constraint of the first application is satisfied:

in accordance with a determination that the second website is associated with the first application, forgoing displaying the second web content; and

in accordance with a determination that the second web site is associated with a second application and that a constraint of the second application is not satisfied, the second web content is displayed.

12. The method according to claim 1, wherein:

the auxiliary function includes displaying media content in a picture-in-picture user interface of the first application, the picture-in-picture user interface partially overlapping one or more other user interfaces;

the event corresponding to activation of the auxiliary function includes a request to display the media content in the picture-in-picture user interface of the first application; and

Suppressing the auxiliary function includes suppressing the picture-in-picture user interface of the first application.

13. The method of claim 12, wherein suppressing the picture-in-picture user interface of the first application comprises:

in accordance with a determination that the constraint of the first application is satisfied when the picture-in-picture user interface of the first application is displayed:

masking the picture-in-picture user interface for a first period of time, and

and stopping displaying the picture-in-picture user interface after the first period of time.

14. The method according to claim 1, wherein:

the auxiliary function 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 function includes a request to display the plurality of affordances for controlling playback of the media content associated with the first application; and

suppressing the auxiliary function includes preventing the plurality of affordances from controlling playback of the media content associated with the first application.

15. The method of claim 14, wherein preventing the plurality of affordances from controlling playback of the media content associated with the first application comprises:

Causing the plurality of affordances to enter an inactive state in which the device ignores user input for the plurality of affordances for a first period of time; and

after the first period of time, the plurality of affordances is caused to enter a default state that is different from the inactive state.

16. An electronic device, comprising:

one or more processors;

a memory; and

one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for performing the method of any of claims 1-15.

17. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which 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 the method of any of claims 1-15.