CN110471582B

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

Info

Publication number: CN110471582B
Application number: CN201811616437.2A
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: 2021-10-29
Anticipated expiration: 2038-12-20
Also published as: JP7236480B2; JP6844904B2; CN114047856A; JP2021099826A; CN110471582A; CN116546134A; CN114047856B; JP2019197527A; CN116546134B; CN110471581A; JP2023088907A; JP7556076B2

Abstract

The invention is directed to 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 limits access to certain applications during certain time periods. In some embodiments, the electronic device suppresses auxiliary functions of certain applications when application usage limits or restrictions associated with those applications are reached. In some embodiments, the electronic device manages the restriction settings with permissions optionally provided by another electronic device.

Description

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

The application is a divisional application of Chinese patent application 201811591484.6 entitled "user interface for controlling or presenting device usage on an electronic device" filed on 2018, 12 and 20.

Technical Field

This document relates generally to electronic devices that control or present information about the use of the devices, and user interaction with such devices.

Background

In recent years, user interaction with electronic devices has increased dramatically. These devices may be devices such as computers, tablets, televisions, multimedia devices, mobile devices, and the like.

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

Disclosure of Invention

Some embodiments described in this disclosure relate to one or more electronic devices presenting indications of device usage metrics, and one or more operations optionally performed by the electronic devices in connection with the foregoing. 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 that the electronic devices optionally perform in connection with the above. Some embodiments described in this disclosure relate to one or more electronic devices that limit access to particular applications during particular time periods, and one or more operations optionally performed by the electronic devices in connection with the above. Some embodiments described in this disclosure relate to one or more electronic devices that suppress ancillary functions of particular applications when application usage limits or restrictions associated with those applications are reached, and one or more operations that the electronic device optionally performs in connection with the above. Some embodiments described in this disclosure relate to one or more electronic devices that manage restriction settings with permissions optionally provided by another electronic device, and one or more operations optionally performed by the electronic device in connection with the above. A full description of the embodiments is provided in the accompanying drawings and detailed description, it being understood that the summary provided above does not limit the scope of the disclosure in any way.

Drawings

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

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.

Figure 4A illustrates an exemplary user interface of an application menu on a portable multifunction device according to 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 with 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 UU illustrate example ways in which an electronic device presents usage metric indications, according to some embodiments of the present disclosure.

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

Fig. 8A-8 NNN illustrate exemplary ways to set, configure, and/or implement usage limits on an electronic device according to some embodiments of the present disclosure.

Fig. 9A-9K are flow diagrams illustrating a method of setting, configuring and/or implementing usage 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.

11A-11I are flow diagrams 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 BB illustrate exemplary ways in which an electronic device suppresses ancillary functions of particular applications when application usage limits associated with those applications are reached, according to some embodiments of the present disclosure.

13A-13H are flow diagrams illustrating a method of suppressing ancillary 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 exemplary ways in which an electronic device manages restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure.

Fig. 15A-15G are flow diagrams illustrating a method of managing restriction 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. It should be recognized, however, 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 that use such devices and/or wish to control their use of such devices. Moreover, 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. 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 various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.

The terminology used in the description of the various described 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 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 to be interpreted to mean "when", "at. Similarly, the phrase "if determined … …" or "if [ stated condition or event ] is detected" is optionally to be construed to mean "upon determination … …" or "in response to determination … …" or "upon detection of [ stated condition or event ] or" in response to detection of [ 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 device is a portable communication device, such as a mobile phone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, those from Apple Inc

Device and iPod

An apparatus, and

an apparatus. Other portable electronic devices are optionally used, such as laptops or tablets with touch-sensitive surfaces (e.g., touch screen displays and/or touch pads). It should also be understood that in some embodiments, the device is not a portable communication device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or touchpad).

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: a mapping application, a rendering application, a word processing application, a website creation application, a disc editing application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an email application, an instant messaging application, a fitness support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.

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

Attention is now directed to embodiments of portable devices having touch sensitive displays. 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 called a "touch-sensitive display system". Device 100 includes memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, an input/output (I/O) subsystem 106, other input control devices 116, and an external port 124. The device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 for detecting the intensity of contacts on device 100 (e.g., a touch-sensitive surface, such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating 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 panel 355 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.

As used in this specification and claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (surrogate) for the force or pressure of a contact on the touch-sensitive surface. 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., a weighted average) to determine the 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 detected on the touch-sensitive surface and/or changes thereof, the capacitance of the touch-sensitive surface in the vicinity of the contact and/or changes thereof and/or the resistance of the touch-sensitive surface in the vicinity of the contact and/or changes thereof are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measurement of contact force or pressure is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measurement). In some implementations, the surrogate measurement of contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold 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 a property of the user input, allowing the user to access additional device functionality that is otherwise inaccessible to the user on smaller-sized devices with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or physical/mechanical controls, such as knobs or buttons).

As used in this specification and 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 center of mass of the device that is to be detected by a user with the user's sense of touch. For example, where a device or component of a device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other portion of a 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 the touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "down click" or "up click" of a physical actuation button. In some cases, the user will feel a tactile sensation, such as a "press click" or "release click," 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 moving. As another example, even when there is no change in the smoothness of the touch sensitive surface, the movement of the touch sensitive surface is optionally interpreted or sensed by the user as "roughness" of the touch sensitive surface. While such interpretation of touch by a user will be limited by the user's individualized sensory perception, many sensory perceptions of touch 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 otherwise stated, the generated haptic output corresponds to a physical displacement of the device or a component thereof that would generate the sensory perception of a typical (or ordinary) user.

It should be understood that device 100 is merely one example of a portable multifunction device, and that 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 these 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.

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

Peripheral interface 118 may be used to couple the 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 to process data. In some embodiments, peripherals 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.

RF (radio frequency) circuitry 108 receives and transmits RF signals, also referred to as electromagnetic signals. The RF circuitry 108 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 so forth. RF circuitry 108 optionally communicates 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 via wireless communication. RF circuitry 108 optionally includes well-known circuitry for detecting Near Field Communication (NFC) fields, such as by short-range communication radios. The wireless communication optionally uses any of a number of communication standards, protocols, and techniques, 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, data-only (EV-DO), HSPA +, Dual-cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), wideband code division multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth Low Power consumption (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), Voice over Internet protocol (VoIP), Wi-MAX, email protocols (e.g., Internet Message Access Protocol (IMAP), and/or Post Office Protocol (POP)) Instant messaging (e.g., extensible messaging and presence protocol (XMPP), session initiation protocol for instant messaging and presence with extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol including communication protocols not yet developed at the time of filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. The audio circuitry 110 receives audio data from the peripheral interface 118, converts the audio data to electrical signals, and transmits the electrical signals to the speaker 111. The speaker 111 converts the electrical signals into sound waves audible to a human. The audio circuit 110 also receives electrical signals converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signals to audio data and transmits the audio data to the peripheral interface 118 for processing. Audio data is optionally retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by 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 circuitry 110 and a removable audio input/output peripheral such as an output-only headset or a headset having both an output (e.g., a monaural headset or a binaural headset) and an input (e.g., a microphone).

The I/O subsystem 106 couples input/output peripheral devices on the device 100, such as a touch screen 112 and other input control devices 116, to a 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/transmit electrical signals from/to other input control devices 116. Other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, and the like. In some alternative embodiments, input controller 160 is optionally coupled to (or not coupled to) any of: 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 the 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 a gesture on an Unlock Image," filed on 23.12.2005, which is hereby incorporated by reference in its entirety. A long press of a button (e.g., 206) optionally turns the device 100 on or off. The functionality of one or more buttons is optionally customizable by the user. The touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

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. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output optionally corresponds to a user interface object.

Touch screen 112 has a touch-sensitive surface, sensor, or group of sensors that accept input from a user based on tactile sensation 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 breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user interface objects (e.g., one or more soft keys, icons, web pages, or images) displayed on touch screen 112. In an exemplary embodiment, the point of contact between touch screen 112 and the user corresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen 112 and display controller 156 optionally detect contact and any movement or breaking 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, projected mutual capacitance sensing technology is used, such as that available from Apple Inc. (Cupertino, California)

And iPod

The technique used in (1).

The touch sensitive display in some embodiments of touch screen 112 is optionally similar to a multi-touch sensitive trackpad 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, whereas touch-sensitive touchpads do not provide visual output.

In some embodiments, the touch sensitive display of touch screen 112 is as described in the following patent applications: (1) U.S. patent application 11/381,313 entitled "Multi Touch Surface Controller" filed on 2.5.2006; (2) U.S. patent application No.10/840,862 entitled "Multipoint touch screen" filed on 6.5.2004; (3) U.S. patent application No.10/903,964 entitled "Gestures For Touch Sensitive Input Devices" (Gestures For Touch Sensitive Input Devices) filed on 30.7.2004; (4) U.S. patent application No.11/048,264 entitled "Gestures For Touch Sensitive Input Devices" filed on 31/1/2005; (5) U.S. patent application No.11/038,590 entitled "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices" (Pattern-Based Graphical User interface For Touch Sensitive Input Devices) filed on 18.1.2005; (6) U.S. patent application No.11/228,758 entitled "Virtual Input Device On A Touch Screen User Interface" (Virtual Input Device placed On a Touch Screen User Interface) filed On 16.9.2005; (7) U.S. patent application No.11/228,700 entitled "Operation Of A Computer With A Touch Screen Interface" (Operation Of a Computer With a Touch Screen Interface), filed on 16.9.2005; (8) U.S. patent application No.11/228,737 entitled "Activating Virtual Keys Of A Touch-Screen Virtual Keys" (Activating Virtual Keys Of a Touch Screen Virtual Keyboard) filed on 16.9.2005; and (9) U.S. patent application No.11/367,749 entitled "Multi-Functional Hand-Held Device" filed 3.3.2006. All of these applications are incorporated herein by reference in their entirety.

The touch screen 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user optionally makes contact with touch screen 112 using any suitable object or appendage, such as a stylus, finger, or the like. 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 larger contact area of the finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the action desired by the user.

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

The device 100 also includes a power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, Alternating Current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a Light Emitting Diode (LED)), and any other components associated with the generation, management, and distribution of power in a portable device.

The device 100 optionally further includes 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 from the environment projected through one or more lenses and converts the light into data representing an image. In conjunction with imaging module 143 (also called a camera module), optical sensor 164 optionally captures still images or video. In some embodiments, an optical sensor is located on the back of device 100, opposite touch screen display 112 on the front of the device, so that the touch screen display can be used as a viewfinder for still and/or video image acquisition. In some embodiments, an optical sensor is located on the front of the device so that images of the user are optionally acquired for the video conference while the user views other video conference participants 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 a lens and sensor 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 capture.

Device 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. Contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors for measuring the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor 165 receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some implementations, at least one contact intensity sensor is collocated with or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touch screen display 112, which is located on the front of 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 "Proximaty Detector In Handheld Device"; no.11/240,788 entitled "Proximity Detector In Handheld Device" (Proximity Detector In Handheld Device); no.11/620,702, entitled "Using Ambient Light Sensor To Automation 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" (Automated Response And Sensing Of User Activity In Portable Devices); and U.S. patent application No.11/638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals" (Methods And Systems For Automatic Configuration Of Peripherals), which is hereby incorporated by reference in its entirety. In some embodiments, the proximity sensor turns off and disables the touch screen 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

Device 100 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. Tactile output generator 167 optionally includes one or more electro-acoustic devices, such as speakers or other audio components; and/or an electromechanical device that converts energy into linear motion, such as a motor, solenoid, electroactive aggregator, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts an electrical signal into a tactile output on the device). Contact intensity sensor 165 receives haptic feedback generation instructions from haptic feedback module 133 and generates haptic output on device 100 that can be felt by a user of 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., into/out of the surface of device 100) or laterally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touch screen display 112, which is located on the front of device 100.

Device 100 optionally also 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 "Accelation-Based Detection System For Portable Electronic Devices" And U.S. patent publication 20060017692 entitled "Methods And apparatus For Operating A Portable Device Based On An Accelerometer", both of which are incorporated herein by reference in their entirety. In some embodiments, information is displayed in a portrait view or a landscape view on the touch screen display based on analysis of data received from one or more accelerometers. Device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) in addition to accelerometer 168 for obtaining information about the position and orientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or set of instructions) 128, a contact/motion module (or set of instructions) 130, a graphics module (or set of instructions) 132, a text input module (or set of instructions) 134, a Global Positioning System (GPS) module (or set of instructions) 135, and an application program (or set of instructions) 136. Further, in some embodiments, memory 102 (fig. 1A) or 370 (fig. 3) stores device/global internal state 157, as shown in fig. 1A and 3. Device/global internal state 157 includes one or more of: an active application state indicating which applications (if any) are currently active; 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 an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.

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. The external port 124 (e.g., Universal Serial Bus (USB), firewire, etc.) is adapted to couple directly to other devices or indirectly via a network (e.g., the internet, wireless LAN, etc.). In some embodiments, the external port is an external port

(trademark of Apple inc.) a multi-pin (e.g., 30-pin) connector that is the same as or similar to and/or compatible with the 30-pin connector used on the device.

Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch sensitive devices (e.g., a touchpad or a physical click wheel). The contact/motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether contact has occurred (e.g., detecting a finger-down event), determining contact intensity (e.g., force or pressure of contact, or a substitute for force or pressure of contact), determining whether there is movement of contact and tracking movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining whether contact has ceased (e.g., detecting a finger-up event or a contact-breaking). The contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact optionally includes determining velocity (magnitude), velocity (magnitude and direction), and/or 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 multiple point simultaneous contacts (e.g., "multi-touch"/multiple finger contacts). In some embodiments, the contact/motion module 130 and the display controller 156 detect contact on the touch panel.

In some embodiments, the contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by the user (e.g., determine whether the user has "clicked" on an icon). In some embodiments, at least a subset of the intensity thresholds are determined as a function of software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and may be adjusted without changing the physical hardware of device 100). For example, the mouse "click" threshold of the trackpad or touchscreen can be set to any one of a wide range of predefined thresholds without changing the trackpad or touchscreen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more intensity thresholds of 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 motions, timings, and/or intensities of detected contacts). Thus, the gesture is optionally detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event, and then detecting a finger-up (lift-off) event at the same location (or substantially the same location) as the finger-down event (e.g., at the location of the 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 subsequently 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 display, 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, videos, animations 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 specifying a graphic 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 in generating haptic outputs 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 such as contacts 137, email 140, IM 141, browser 147, and any other application that requires 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 desktop widgets, local yellow pages desktop widgets, and map/navigation desktop widgets).

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

● contact module 137 (sometimes referred to as a contact list or contact list);

● a telephone module 138;

● video conferencing module 139;

● e-mail client module 140;

● Instant Messaging (IM) module 141;

● fitness support module 142;

● 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;

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

● for forming a user-created desktop applet 149-6;

● search module 151;

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

● notepad module 153;

● map module 154; and/or

● 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, rendering 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 contact lists or contact lists (e.g., stored in memory 102 or in application internal state 192 of contacts module 137 in memory 370), including: adding one or more names to the address book; delete names from the address book; associating a telephone number, email address, physical address, or other information with a name; associating the image with a 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; and so on.

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, phone module 138 is optionally used to enter a sequence of characters corresponding to a phone number, access one or more phone numbers in contacts module 137, modify an entered phone number, dial a corresponding phone number, conduct a conversation, and disconnect or hang up when the conversation is complete. As noted above, the 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, video conference module 139 includes executable instructions to initiate, conduct, and terminate video conferences between the 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 to create, send, receive, and manage 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 an email with a still image or a video image 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 messaging module 141 includes executable instructions for: inputting a sequence of characters corresponding to an instant message, modifying previously input characters, transmitting a corresponding instant message (e.g., using a Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocol for a phone-based instant message or using XMPP, SIMPLE, or IMPS for an internet-based instant message), receiving an instant message, and viewing the received instant message. In some embodiments, the transmitted and/or received instant messages optionally include graphics, photos, audio files, video files, and/or MMS and/or other attachments supported in an 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., having time, distance, and/or calorie burning goals); communicating with fitness sensors (sports equipment); receiving fitness sensor data; calibrating a sensor for monitoring fitness; selecting and playing music for fitness; and displaying, storing and transmitting 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 video (including video streams) and storing them in the memory 102, modifying features of the still images or video, or deleting the still images or video 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, labeling, 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 to browse the internet (including searching for, linking to, receiving and displaying web pages or portions thereof, and 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 to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do, etc.) according to user instructions.

In conjunction with the RF circuitry 108, the touch screen 112, the display system controller 156, the contact/motion module 130, the graphics module 132, the text input module 134, and the browser module 147, the desktop applet module 149 is a mini-application (e.g., a weather desktop applet 149-1, a stock market desktop applet 149-2, a calculator desktop applet 149-3, an alarm clock desktop applet 149-4, and a dictionary desktop applet 149-5) or a mini-application created by a user (e.g., a user created desktop applet 149-6) that is optionally downloaded and used by the 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! desktop applet).

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, the desktop applet creator module 150 is optionally used by a user to create a desktop applet (e.g., to turn a user-specified portion of a web page into a 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 memory 102 for text, music, sound, images, video, and/or other files that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speakers 111, RF circuitry 108, and browser module 147, 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, rendering, or otherwise playing back video (e.g., on touch screen 112 or on an external display connected via 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, backlogs, 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 used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data related to stores 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 circuitry 110, speaker 111, RF circuitry 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), playback (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 link to the particular online video is sent using instant messaging module 141 instead of email client module 140. Additional descriptions of Online video applications may be found in U.S. provisional patent application 60/936,562 entitled "Portable Multi function Device, Method, and Graphical User Interface for Playing Online video," filed on year 2007, 20.6.2007 and U.S. patent application 11/968,067 entitled "Portable Multi function Device, Method, and Graphical User Interface for Playing Online video," filed on year 2007, 31.12.12, 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 as 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., the 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 on which the operation of a predefined set of functions is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or trackpad 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.

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

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 classifier 170 (e.g., in operating system 126) and corresponding application 136-1 (e.g., any of the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives the event information and determines application 136-1 and application view 191 of 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, application 136-1 includes an application internal state 192 that indicates a current application view that is displayed on 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 embodiments, the application internal state 192 includes additional information, such as one or more of: resume information to be used when the application 136-1 resumes execution, user interface state information indicating that information is being displayed or is ready for display by the application 136-1, a state queue for enabling a 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 a sub-event (e.g., a user touch on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or sensors such as proximity sensor 166, accelerometer 168, and/or microphone 113 (through audio circuitry 110). Information received by peripheral interface 118 from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

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

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

When touch-sensitive display 112 displays more than one view, hit view determination module 172 provides a software process for determining where within one or more views a sub-event has occurred. The view consists 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 programmatic level within a programmatic or view hierarchy of applications. For example, the lowest level view in which a touch is detected is optionally referred to as a hit view, and the set of events identified as correct inputs is optionally determined based at least in part on the hit view of the initial touch that initiated the touch-based gesture.

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

The active 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 recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of the sub-event are actively participating views, and thus determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if the touch sub-event is completely confined to the area associated with a particular view, the higher views in the hierarchy will remain actively participating views.

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

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

In some embodiments, the 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 application's user interface. 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 that inherits methods and other properties from it. In some embodiments, the respective event handlers 190 comprise one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177 or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Additionally, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.

The corresponding event recognizer 180 receives event information (e.g., event data 179) from the event classifier 170 and recognizes events from the event information. The event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, event recognizer 180 also includes metadata 183 and at least a subset of event delivery 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 a sub-event such as a touch or touch movement. According to the sub-event, the event information further includes additional information, such as the location of the sub-event. When the sub-event relates to motion of a touch, the event information optionally also includes the velocity and direction of the sub-event. In some embodiments, the event comprises rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information comprises corresponding information about the current orientation of the device (also referred to as the device pose).

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

In some embodiments, event definition 187 includes definitions of events for respective user interface objects. In some embodiments, 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 the event handler associated with the sub-event and the object that triggered the hit test.

In some embodiments, 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 the event type of the event identifier.

When the respective event recognizer 180 determines that the sequence of sub-events does not match any event in the event definition 186, the respective event recognizer 180 enters an event not possible, event failed, or event ended state, after which subsequent sub-events of the touch-based gesture are ignored. In this case, 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 attributes, tags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, metadata 183 includes configurable attributes, flags, and/or lists that indicate how or how event recognizers interact with each other. In some embodiments, metadata 183 includes configurable attributes, flags, and/or lists that indicate whether a sub-event is delivered to a different level in the view or programmatic hierarchy.

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

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

In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, the data updater 176 updates a phone number used in the contacts 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, object updater 177 creates a new user interface object or updates the location of a user interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends the display information to graphics module 132 for display on the touch-sensitive display.

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

It should be understood that the above discussion of event processing with respect to user touches on a touch sensitive display also applies to other forms of user input utilizing an input device to operate 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 movements on the touchpad, such as tapping, dragging, scrolling, etc.; inputting by a stylus; 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 the User Interface (UI) 200. In this embodiment, as well as other embodiments described below, a user can select one or more of these graphics by making gestures on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics will occur when the 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 a rolling of a finger (right to left, left to right, up, and/or down) that has made contact with device 100. In some implementations, or in some cases, inadvertent contact with a graphic does not select the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that swipes over the application icon optionally does not select the corresponding application.

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

In some embodiments, device 100 includes touch screen 112, menu buttons 204, push buttons 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 docking/charging external port 124. Pressing the button 206 optionally serves to turn the device on/off by pressing the button and holding the button in a 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 unlocking the device or initiating an unlocking process. In an alternative embodiment, device 100 also accepts voice input through microphone 113 for activating or deactivating certain functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of contacts on touch screen 112, and/or one or more tactile output generators 167 for generating tactile outputs for a user of 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, desktop, tablet, multimedia player device, navigation device, educational device (such as a child learning toy), gaming system, or control device (e.g., a home controller or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects and controls communication between system components. Device 300 includes an input/output (I/O) interface 330 with a display 340, typically a touch screen display. I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and touchpad 355, tactile output generator 357 (e.g., similar to tactile output generator 167 described above with reference to fig. 1A) for generating tactile outputs on device 300, sensors 359 (e.g., optical sensors, acceleration sensors, proximity sensors, touch-sensitive sensors, and/or contact intensity sensors (similar to contact intensity sensors 165 described above with reference to fig. 1A)). Memory 370 includes high speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU 310. In some embodiments, memory 370 stores programs, modules, and data structures similar to or a subset of the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (fig. 1A). Further, 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 modules corresponds to a set of instructions for performing a function described above. The modules or programs (e.g., sets of instructions) described above 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 portable multifunction device 100 according to 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 indicators 406;

● have a tray 408 of icons for common applications, such as:

an icon 416 of the phone module 138 labeled "phone", 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 labeled "mail", the icon 418 optionally including an indicator 410 of the number of unread emails;

icon 420 of the browser module 147, labeled "browser"; and

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

● icons for other applications, such as:

icon 424 of IM module 141 labeled "message";

icon 426 of calendar module 148 labeled "calendar";

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

icon 430 of camera module 143 labeled "camera";

icon 432 for online video module 155 labeled "online video";

an icon 434 of the O stock desktop applet 149-2 labeled "stock market";

Icon 436 of map module 154 labeled "map";

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

icon 440 of alarm clock desktop applet 149-4 labeled "clock";

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

icon 444 of O notepad module 153 labeled "notepad"; and

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

It should be noted that the icon labels shown in fig. 4A are merely exemplary. For example, icon 422 of video and music player module 152 is labeled "music" or "music player". Other tabs are optionally used for the 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., touchscreen display 112). Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting the intensity of contacts on touch-sensitive surface 451, and/or one or more tactile output generators 357 for generating tactile outputs for a user of device 300.

Although some of the examples below will be given with reference to input on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, as shown in fig. 4B. In some implementations, the touch-sensitive surface (e.g., 451 in fig. 4B) has a primary axis (e.g., 452 in fig. 4B) that corresponds to a primary axis (e.g., 453 in fig. 4B) on the display (e.g., 450). In accordance with these embodiments, the device detects contacts (e.g., 460 and 462 in fig. 4B) with the touch-sensitive surface 451 at locations that correspond to respective locations on the display (e.g., in fig. 4B, 460 corresponds to 468 and 462 corresponds to 470). As such, 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 their movements) 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 understood that similar methods are optionally used for the other user interfaces described herein.

Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contact, single-finger tap gesture, finger swipe gesture), it should be understood that in some embodiments one or more of these finger inputs are replaced by inputs from another input device (e.g., mouse-based inputs or stylus inputs). For example, the swipe gesture is optionally replaced by 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 detecting a contact, followed by ceasing to detect a contact) while the cursor is over the location of the flick gesture. Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or mouse 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 embodiments, the device 500 has a touch-sensitive display screen 504, hereinafter referred to as a touch screen 504. Instead of or in addition to the touch screen 504, the device 500 has a display and a touch-sensitive surface. As with devices 100 and 300, in some embodiments, touch screen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors for detecting the intensity of an applied contact (e.g., touch). One or more intensity sensors of the touch screen 504 (or touch-sensitive surface) may provide output data representing the intensity of a touch. The user interface of device 500 may respond to the touch based on the intensity of the touch, meaning that different intensities of the touch may invoke different user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity are found, for example, in the following related patent applications: international patent Application Ser. No. PCT/US2013/040061, entitled "Device, Method, and Graphical User Interface for Displaying User Interface Objects reforming to an Application", filed on 8.5.2013, published as WIPO patent publication No. WO/2013/169849; and International patent application Ser. No. PCT/US2013/069483 entitled "Device, Method, and Graphical User Interface for transiting Between Touch Input to Display Output Relationships", filed on 11/2013, 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, 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, belt, shoe, purse, backpack, and 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 portion 514 with one or more computer processors 516 and a memory 518. The I/O portion 514 may be connected to the display 504, which may have a touch sensitive member 522 and optionally an intensity sensor 524 (e.g., a contact intensity sensor). Further, I/O portion 514 may interface with communication unit 530 for receiving application programs and operating system data using Wi-Fi, Bluetooth, Near Field Communication (NFC), cellular, and/or other wireless communication techniques. 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., a compass), a gyroscope 536, a motion sensor 538, and/or combinations thereof, all of which may be operatively connected to I/O portion 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 the

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, or 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 memory such as flash memory, solid state drives, and the like. 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, images (e.g., icons), buttons, and text (e.g., hyperlinks) optionally each constitute an affordance.

As used herein, the term "focus selector" refers to an input element that is used to indicate the current portion of the user interface with which the user is interacting. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in fig. 3 or touch-sensitive surface 451 in fig. 4B) while the cursor is over 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 that include 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, a contact detected on the touch screen serves as a "focus selector" such that when an input (e.g., a press input by the contact) is detected at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touch screen display, 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 corresponding movement of a cursor or movement of a contact on the touch screen display (e.g., by moving the focus from one button to another using tab or arrow keys); in these implementations, the focus selector moves according to movement of the focus between different regions of the user interface. Regardless of the particular form taken by the focus selector, the focus selector is typically a user interface element (or contact on a touch screen display) that is controlled by the user to deliver the user's intended interaction with 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 touchscreen), the location 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 (as opposed to other user interface elements shown on the device display).

As used in the specification and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples acquired during a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after detecting contact, before detecting contact liftoff, before or after detecting contact start movement, before or after detecting contact end, before or after detecting an increase in intensity of contact, and/or before or after detecting a decrease in intensity of contact). The characteristic intensity of the contact is optionally based on one or more of: a maximum value of the intensity of the contact, a mean value of the intensity of the contact, an average value of the intensity of the contact, a value at the top 10% of the intensity of the contact, a half-maximum value of the intensity of the contact, a 90% maximum value of the intensity of the contact, and the like. 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, a contact whose characteristic intensity does not exceed the first threshold results in a first operation, a contact whose characteristic intensity exceeds the first intensity threshold but does not exceed the second intensity threshold results in a second operation, and a contact whose characteristic intensity exceeds the second threshold results in a third operation. In some embodiments, a comparison between the feature strengths and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the respective operation or to forgo performing the respective operation) rather than to determine whether to perform the first operation or the second operation.

FIG. 5C illustrates the detection of multiple contacts 552A-552E on the touch-sensitive display screen 504 using multiple intensity sensors 524A-524D. FIG. 5C also includes an intensity map that shows 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 a sum of 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 respective intensity, i.e., a fraction of the cumulative intensity. FIG. 5D illustrates assigning cumulative intensities to the contacts 552A-552E based on their distances from the center of the force 554. In this example, each of

contacts

552A, 552B, and 552E is assigned a strength of 8 strength units of contact of cumulative strength, and each of contacts 552C and 552D is assigned a strength of 4 strength units of contact of cumulative strength. More generally, in some implementations, each contact j is assigned a respective intensity Ij, which is a portion of the cumulative intensity a, according to a predefined mathematical function Ij ═ a · (Dj/Σ Di), where Dj is the distance of the respective contact j from the force center, and Σ Di is the sum of the distances of all 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 assist the reader.

In some implementations, a portion of the gesture is recognized for determining the feature intensity. For example, the touch-sensitive surface optionally receives a continuous swipe contact that transitions from a starting location and reaches an ending location where the contact intensity increases. In this example, the characteristic intensity of the contact at the end location 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 location). 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: a non-weighted 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 dips in the intensity of the swipe contact for the purpose of determining the feature intensity.

Contact intensity 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 light press intensity threshold corresponds to an intensity that: at which intensity the device will perform the operations typically associated with clicking a button of a physical mouse or touchpad. In some embodiments, the deep press intensity threshold corresponds to an intensity that: at which intensity the device will perform a different operation than that typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, when a contact is detected whose characteristic intensity is 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 in accordance with movement of the contact on the touch-sensitive surface without performing operations associated with a light press intensity threshold or a deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface drawings.

Increasing the 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. Increasing the 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. Increasing 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 characteristic intensity of the contact from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting lift-off of the contact from the touch surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.

In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting a respective press input performed with a respective contact (or contacts), wherein the 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 embodiments, the respective operation is performed in response to detecting an increase in intensity of the respective contact above a press input intensity threshold (e.g., a "down stroke" 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 a subsequent decrease in intensity of the respective contact below the press input threshold (e.g., an "up stroke" of the respective press input).

5E-5H illustrate detection of a gesture that includes an intensity of contact 562 from below the light press intensity threshold in FIG. 5E (e.g., "IT" pressure threshold_L") ofThe intensity increases above the deep press intensity threshold in FIG. 5H (e.g., "IT_D") intensity corresponds to a press input. On the displayed user interface 570 including the application icons 572A-572D displayed in the predefined area 574, a gesture performed with the contact 562 is detected on the touch-sensitive surface 560 while the cursor 576 is displayed over the application icon 572B corresponding to application 2. In some implementations, the gesture is detected on the touch-sensitive display 504. The intensity sensor detects the intensity of the contact on the touch-sensitive surface 560. The device determines that the intensity of contact 562 is at a deep press intensity threshold (e.g., "IT_D") above peak. A contact 562 is maintained on the touch-sensitive surface 560. In response to detecting the gesture, and in accordance with the intensity rising to the deep press intensity threshold during the gesture (e.g., "IT)_D") above, displays reduced-scale representations 578A-578C (e.g., thumbnails) of the document recently opened 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 assist the reader.

In some embodiments, the display of representations 578A-578C includes animation. For example, the representation 578A is initially displayed in proximity to the application icon 572B, as shown in fig. 5F. As the animation progresses, the representation 578A moves upward and a representation 578B is displayed adjacent to 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 contact 562, as shown in fig. 5F-5G, where representations 578A-578C appear and move upward as the intensity of contact 562 increases toward a deep press intensity threshold (e.g., "ITD"). In some embodiments, the intensity at which the animation progresses is a 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 embodiments, the device employs intensity hysteresis to avoid accidental input sometimes referred to as "jitter," where the device defines or selects a hysteresis intensity threshold having a predefined relationship to the press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press input intensity threshold). Thus, 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 a hysteresis intensity threshold corresponding to the press input intensity threshold, and the respective operation is performed in response to detecting a subsequent decrease in intensity of the respective contact 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 the press input (e.g., depending on the circumstances, the increase in contact intensity or the decrease in contact intensity).

For ease of explanation, optionally, a description of an operation performed in response to a press input associated with a press input intensity threshold or in response to a gesture that includes a press input is triggered in response to detection of any of the following: the contact intensity increases above the press input intensity threshold, the contact intensity increases from an intensity below the hysteresis intensity threshold to an intensity above the press input intensity threshold, the contact intensity decreases below the press input intensity threshold, and/or the contact intensity decreases below the hysteresis intensity threshold corresponding to the press input intensity threshold. Additionally, in examples in which operations are described as being performed in response to detecting that the intensity of the contact decreases below the press input intensity threshold, the operations are optionally performed in response to detecting that the intensity of the contact decreases 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 to an electronic device (e.g., device 100, 300, and/or 500) and is ready to be launched (e.g., become open) on the device. In some embodiments, the downloaded application is changed to an installed application with 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 that has maintained 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;

● background applications (or background processes) that are not currently shown but for which one or more processes are being processed by one or more processors; and

● are not running but have paused or hibernated applications that are stored in memory (volatile and non-volatile, respectively) and that can be used to resume execution of the applications.

As used herein, the term "closed application" refers to a software application that does not have retained 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 the application's application process and removing the application's state information from the device's memory. Generally, while in a first application, opening a second application does not close the first application. The first application becomes the 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

User interface for use measurement control panel

Users interact with electronic devices in a number of different ways, including viewing information about the electronic devices and/or the use of the electronic devices. In some embodiments, the electronic device displays a visual indication of one or more metrics associated with an 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 a usage metric associated with performing one or more operations using the electronic device. Enhancing interaction with the device reduces the amount of time required for a user to perform an operation, thereby reducing the power usage of the device and extending the battery life of the battery-powered device. It should be understood that one uses the device. When a person uses a device, the person is optionally referred to as the user of the device.

Fig. 6A-6 UU illustrate example ways in which an electronic device presents usage metric indications, according to some embodiments of the present disclosure. The embodiments in these figures are used to illustrate the processes described below, including the processes described with reference to fig. 7A-7S.

Fig. 6A illustrates an exemplary device 500 having a touch screen 504, such as described with reference to fig. 5A-5H. The 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 restriction setting user interface for viewing information about use of the electronic device 500 and setting a limit of use of the electronic device 500. In fig. 6A, a restriction setting user interface displays an indication 602 of device usage and a plurality of settings related to device usage, such as settings for a restricted usage mode (e.g., "device downtime" 604a), settings for usage limits for one or more applications or application categories (e.g., "application limits" 604b), settings for which functions are always allowed regardless of any currently enforced usage restrictions (e.g., "always allowed" 604c), content and privacy settings for electronic device 500 (e.g., "content and privacy" 604d), settings for which changes to usage settings require a password (e.g., "make changes require a password" 604e), settings for which operations are being performed at the electronic device are stopped (e.g., "stop recording usage data" 604f), settings for which stored data related to performing various operations using the electronic device are deleted (e.g., "delete usage data" 604g), and settings to log into the cloud-based user account (e.g., "log into iCloud" 604 h). As shown, the indication 602 of device usage includes a visual indication of the amount of time the electronic device has been used to access each of several applications or categories of applications (e.g., news applications, game categories, and mail applications). Indication 602 also includes an indication of how much remaining is left (e.g., "3 hours left") for the total "screen time" usage limit. The usage limits, including the overall usage limit, are described in more detail below with reference to fig. 8A through 9K. The electronic device 500 also displays an indication of overall device usage (e.g., "use 4 hours"), and a comparison of the current day's device usage to the average daily usage (e.g., "30 minutes below average").

Fig. 6B illustrates a restriction settings user interface when the electronic device 500 logs into a cloud-based user account. The restriction settings user interface includes an indication 606 of a nickname for the electronic device 500 associated with the user account and indications of devices associated with other users that are part of the group or family cloud-based account (e.g., an iPhone 608a by John jr. and an iPhone 608b by Jane). The family cloud-based account includes a plurality of individual user accounts (e.g., "John jr's iPhone" and "Jane's iPhone") associated with other electronic devices. In some embodiments, the family cloud-based accounts include "parent" users and "child" users, and enable the parent user to view and/or control various statistics and/or settings associated with the child devices. As shown here and described in more detail below with reference to fig. 6V-6W, a parent device (e.g., such as electronic device 500) can present usage information about one or more child devices. The parent device can also control the usage limit and device down time settings of the child device 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 (e.g., John's iPad 610a, Apple TV 610b, and John's Apple Watch 610C) associated with the cloud-based user account, a "stop recording usage data" setting 604f, and a "delete usage data" setting 604 g. 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. 6TT through 6UU, the electronic device 500 may be capable of displaying usage metrics associated with one or more associated devices, either individually or together.

Fig. 6E shows a desktop applet user interface that includes a use desktop applet 612a, a calendar desktop applet 612b, and a weather desktop applet 612 c. The usage desktop applet 612a includes an indication 602 of device usage, including indications 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 the affordance 614, the desktop applet 612a is deployed to display additional information, as shown in FIG. 6G. The expanded usage desktop applet 612a includes an indication 616 of the total device usage for the current day, an indication of how much the device usage for the current day deviates from the average device usage 618, a graphical representation 620 of the device usage over time indicating an application or application category, and indications of usage limits set on the electronic device (e.g., news application limit 622a and game category limit 622 b). Graph 620 includes a bar for each hour of the day indicating device usage during that hour, with a color coded portion to indicate which application (e.g., news application or mail application) or application category (e.g., game category) is used during each hour. As shown in fig. 6G, the indication of the usage limit that has been exceeded (e.g., news application usage limit 622a) includes an indication of how much the application program (e.g., news application) has been used beyond the usage limit. Likewise, the indication of a usage limit (e.g., game category 622b) that has not been reached includes an indication of a difference in usage of the application category (e.g., game category) from the usage limit. Fig. 6H-6I show the user scrolling (e.g., with contact 603) the expanded usage desktop applet to present additional information, including representations 624a-624e of the application usage for the current day, an indication 626 of the average number of notifications received per day over the past few days, and an indication 628 of the frequency with which the user has initiated a "pick up" of the device over the past one or more days. As shown, the indications of the application icons 624a-624e are application icons for those applications that are presented in different sizes indicating relative usage amounts of the respective applications. For example, news application indication 624a is maximum, indicating that the application has been used the most. Also, mail application designation 624b and game a application designation 624c are smaller than news application designation 624a, depending on the amount of usage of these applications.

Fig. 6J illustrates a usage notification 630 generated by the device 500 according to some examples of the present disclosure. In some embodiments, usage notifications such as notification 630 are generated by electronic device 500 at regularly scheduled intervals (e.g., once per day, once per week, etc.). The usage notification includes an indication 602 of device usage, an option (e.g., "view" 632a) to view more information about device usage (e.g., in a dashboard user interface), 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 device usage. In response, the electronic device 500 presents a usage panel user interface, as shown in FIG. 6L.

The usage control panel user interface includes a graphical representation 620 of device usage over time for an application or application category, described above with reference to FIG. 6G, an indication 634 of the longest usage session on the device during the current day, an indication 636 of the amount of device usage during a limited usage mode (e.g., "device downtime") during the current day, and

indications

622a and 622b of the usage of the application and category for which usage limits are set. The usage control panel user interface also includes toggle keys for viewing indications of usage metrics for a day 638a or a week 638 b. As shown in fig. 6L, the usage measurements for the current day are currently displayed using the dashboard user interface.

Indications

622a and 622b of usage of applications having usage limits are optionally visually associated with

affordances

640a and 640b, which affordances 640a and 640b may select to display a settings user interface for viewing information about a respective application or category, and updating usage limit settings for that application or category. For example, affordance 640a may be selected to edit a usage limit setting for a news application. As shown in fig. 6L, when the usage limit has been exceeded (e.g., news application usage limit 622a), the corresponding affordance 640a has another color or pattern indicating that the usage limit has been exceeded. Also, in some embodiments, when the usage limit is nearly reached (e.g., within a threshold amount or percentage of time), the associated affordance has a visual characteristic. Additionally, the histogram indicating usage limits includes different colored portions corresponding to the amount of time within the usage limits the electronic device was used to access a given application or category (e.g., as shown in both news application indication 622a and game category indication 622 b), the amount of time the given application or category was used beyond the usage limits (e.g., as shown in news application indication 622a), and the amount of time remaining in the usage limits of the application or category (e.g., as shown in game category indication 622 b).

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

Fig. 6P-6Q illustrate a user scrolling (e.g., with contact 603) the usage control panel user interface to reveal additional usage metric indications, as shown in fig. 6R. FIG. 6R shows a usage 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 hour at which the most notifications were received, and indications 650a-650d of how many notifications were generated by a plurality of applications installed on the electronic device (e.g., all applications generating notifications on the day, or a set number of applications generating notifications on top of the day). The illustration 644 includes a plurality of bars that indicate how many notifications 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 the indication for which the notification is displayed. For example, the affordance 652a may be selected 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 how many notifications the respective application generated throughout the day, and points located to indicate the relative number of notifications the application generated relative to other applications.

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

Fig. 6U shows a usage control panel user interface including an indication 654 of the "pick up" of the device for the day (described in more detail below), an indication 656 of the average time between picking up devices for the day, an illustration 658 of the picking up devices for the entire day, an indication 660 of the number of times the device was picked up during the device downtime (the device downtime is described in more detail below with reference to fig. 10A-11I), an indication 662 of the hour in which the device was picked up the most and the number of times in the time interval, and

indications

664a and 664b of the number of times the user interacted with each of the plurality of applications when picking up the electronic device.

The average time between picks up a device for the day indicated by indication 656 is calculated as the average time between the first pick up and the last pick up for the day. In some embodiments, the average value comprises picks between a first pick outside of the plant downtime and a last pick outside of the plant downtime. In some embodiments, the average includes picks between all picks on the day, regardless of whether one or more of those picks occurred during the equipment down time.

The graphic 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 in each hour. As shown in FIG. 6U, the illustration visually distinguishes picks that occur during equipment downtime from picks that occur outside of equipment downtime, and also indicates this distinction with equipment downtime flags 698-22.

The applications 664a-b with which the user picks up the electronic device to interact are determined based on the first application the user interacted with when picking up the device. For example, if a user wakes up a device, immediately closes a first application presented at the electronic device upon waking, and then opens a second application to perform operations with the second application, the second application is the application that the user picks up the electronic device to interact with. 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 the application that the user picks up the electronic device to interact with.

As used herein, "picking up" a device encompasses multiple types of user attention events, such as a user unlocking the electronic device, waking the device, and other operations that initiate operation of the electronic device. In some embodiments, a user attention event is detected when a user input causes the electronic device to exit an idle state (e.g., a sleep mode, a locked state, a low power mode, etc., during which the user does not interact with the electronic device and/or a 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 corresponding to the request to enter the idle state (e.g., pressing a power or lock button of the electronic device). 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: a button of the electronic device is pressed, a user action to terminate an idle state (e.g., raise the device), an unlock input (e.g., enter a password or provide a biometric feature), and a touch input to access a function of the electronic device (e.g., a desktop applet user interface, a camera application, a dashboard user interface, a user interface that displays an application associated with a displayed notification indication). Detecting the biometric feature optionally includes detecting a face of the user with a depth camera or another sensor. In some implementations, the electronic device can use depth cameras and facial recognition techniques to determine when the user is looking at their electronic device and unlock in response to the user looking at the electronic device (e.g., the electronic device unlocks in response to determining that the user is focusing on the electronic device). In some embodiments, the electronic device exits the idle state in response to the notification (e.g., the display is open to display the notification without user input requesting the display to be 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 a user attention event, even though it causes the device to exit the idle state. In some embodiments, the event of interest metric indicates the number of times the user initiated use of the electronic device (e.g., "check" his phone).

FIG. 6V illustrates a restriction settings user interface. As shown, the restriction settings user interface includes an indication 608a of the electronic device associated with the user as part of the home account associated with the electronic device 500 ("iPhone" by John jr.). The indication also includes an indication that an iPhone for John jr requests more time to be added 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 the user's selection, the electronic device displays a usage 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 the overall usage limit implemented on the iPhone of John jr, an indication 680 of the overall screen time usage limit of the iPhone of John jr, an indication 670 of the duration of the longest usage session of the iPhone of John jr, an indication 672 of the amount of usage during device downtime on the iPhone of John jr, indications 674a-b of usage of applications with usage limits on the iPhone of John jr, and an indication 676 of usage of applications without usage limits on the iPhone of John jr, similar to that described above 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., an iPhone of John jr.) to increase an amount of time to use the usage limit implemented on the other electronic device. As described above with reference to fig. 6B, electronic device 500 and John jr. Indication 666 includes selectable affordances for "deny" the request, "give 1 hour" additional time, or "go to setup" to see more options for modifying the restrictions on John jr's iPhone. Requesting more time to add usage limits from the child device to the parent device, and more details regarding usage limits in general, are described below with reference to fig. 9A-10 AAA.

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

FIG. 6X illustrates a restriction settings user interface. In fig. 6Y, the user selects setting 604e (e.g., with contact 603) requiring a password (or other authentication such as a password or biometric feature) for changing the usage restriction settings on device 500. In response to the selection, the electronic device presents a keypad 682 for receiving user input to set the password. In some embodiments, the electronic device presents a full keyboard or 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 use settings. The authentication required to make changes to one or more usage restriction settings of the electronic device 500 is optionally different than 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 for making a change to the use restriction setting, as shown in fig. 6 AA. In fig. 6BB, the user selects the indication 604b to make a change to the usage limit on the electronic device 500. In response to the input, the electronic device presents the keypad 682 to request the password (or other authentication method) described above, as shown in fig. 6CC, before allowing the user to change the settings.

Fig. 6DD shows an indication 602 of user selection (e.g., with contact 603) of device usage. In response to the selection, the electronic device 500 presents a usage panel user interface, as shown in FIG. 6 EE. As shown in fig. 6FF, the user then selects toggle 638b (e.g., with contact 603) to view the usage measurements over the course of the week. In response to the input, the electronic device 500 updates the usage control panel user interface to display an indication of the usage metric over the course of the past week, as shown in FIG. 6 GG.

FIG. 6GG shows a usage control panel user interface that presents a plurality of usage metrics over the course of a past week. The usage dashboard user interface includes an indication 684 of average device usage per day during the week, an indication 686 of how average daily usage is compared to average usage over a longer period of time (e.g., last month or all), a graphical representation 688 showing daily usage of one or more applications or application classes, 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 indications 694a-694b of average usage per day during the week for one or more applications or application classes for which usage limits are set. The illustration 688 includes bars for a plurality of color-coded applications and application categories indicating the day of the week the usage of the electronic device 500 is daily. As shown, diagram 688 includes an indication of an overall device usage limit (e.g., a horizontal line running across diagram 688), which optionally is different on weekdays (e.g., monday through friday) and weekends (e.g., saturday and sunday). For example, as shown in FIG. 6GG, the overall equipment usage limits for Monday through Friday are optionally lower than the overall equipment usage limits for Saturday and Sunday.

Although not shown in the figures, it should be understood that the control panel user interface optionally includes an indication of any other metric described herein over the course of the week, with some metrics being displayed aggregated over the week (e.g., as a total, average, etc.) and other metrics being displayed as a maximum or minimum for the week. For example, returning to fig. 6R, the number of notifications 646 for a day is optionally replaced by the average number of notifications per day for the week, while the interval 648 during which the most notifications are received for a day is replaced by the interval during which the most notifications are received for the week (e.g., a day or an hour of a day). As another example, returning to fig. 6U, the number of times 660 a device was picked up during the down time of the day is optionally replaced by the average number of times a device was picked up during the down time of the device for each day during the week, and the hour with the most picks 662 for the day is optionally replaced by another interval (e.g., a certain day or a certain hour of a day) during which most notifications were received during the period.

FIG. 6HH illustrates a 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 II. The category-setting user interface includes a toggle key 690 for implementing or not implementing usage limits for application categories, an indication 692 of usage limits for application categories, an option 694a for setting implementation limits with notifications and blocks, an option 694b for setting implementation limits with notifications, a toggle key 696 for presenting verbal alerts associated with the usage limits, and a plurality of indications 698a-d of usage of each application included in the application category to which the usage limits apply.

Toggle 690 enables a user to stop enforcing category usage limits while saving parameters of the usage limits, such as amount of time, notification style, and included applications. In this way, the user can reopen the toggle to begin enforcing the usage limits without having to reenter the parameters of the usage limits. Further details of the notification and

block settings

694a and 694b, and usage limit settings, are described below with reference to fig. 8A-9K. Toggle 696 for presenting verbal alerts associated with usage limits enables electronic device 500 to speak a notification associated with the usage limits, such as a notification indicating that the usage limits are approaching being reached or have been reached.

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

FIG. 6JJ shows an indication 698-2 of the amount of usage of Game A, an indication 698-4 of the average usage of Game A, an indication 698-6 of the usage of Game A during equipment downtime for the current day, an indication 698-8 of the number of notifications that Game A generated during the current day, a setting 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 for the current day (e.g., shown as a plurality of bars, where each bar represents usage of Game A in each hour of the current day). As shown, the user is able to 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 usage 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. 6JJ is accessible from the category settings user interface shown in fig. 6HH through 6II, similar user interfaces for the various applications are accessible from the usage metrics dashboard user interface (e.g., as shown in fig. 6L through 6O, 6W, and 6EE through 6 HH) when the user selects the setting affordance associated with the individual application (e.g., 640a associated with the news application, 678c associated with the dictionary application, etc.).

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

Fig. 6NN illustrates the usage control panel user interface described above. Fig. 6OO shows the usage control panel user interface 15 minutes after the user uses the instant messaging application. In response to the application usage, the electronic device 500 updates the user interface to display the usage of the instant messaging application in a graphical representation 620 of device usage of the application or application category over time. An indication 616 of the overall device usage and an indication 618 of the usage of the electronic device compared to the average usage are also updated.

Fig. 6PP shows the usage control panel user interface after the user has used the instant messaging application for another 15 minutes, thereby bringing the total usage of the instant messaging application to 30 minutes. In response to the additional use, 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 use of the applications in the message category satisfies a category use threshold). Once the mail application and the IM application are combined into the message category, the illustration 620 is updated to include a color or pattern associated with the message category that indicates use of one of the plurality of application programs (e.g., the mail application or the IM application) in the message category. In some embodiments, applications are combined into categories when the combined usage of those applications meets or exceeds a predetermined category usage threshold.

In fig. 6QQ, the instant messaging application is updated again after the user uses the electronic device 500 for another 30 minutes, thereby making the overall use of the application 60 minutes. In response to the additional use, the electronic device 500 separates the instant messaging application and the email application (e.g., based on a determination that the use of the instant messaging application satisfies an application use threshold). That is, rather than combining them into message categories, the illustration 620 is updated to include separate colors or patterns that indicate the use of the IM application and the mail application, respectively. In some embodiments, applications are separated when the usage of individual applications in a combined category meets or exceeds a predetermined application usage threshold.

In some embodiments, device 500 includes not only application usage within the usage of a given application (or category), but also usage of a network resource (e.g., a web page) corresponding to the given application within the usage of the given application (or category). For example, fig. 6RR shows the usage control panel user interface after the user has visited a website associated with the instant messaging application for thirty minutes. As shown, accessing the website associated with the instant messaging application accounts for 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 using the native instant messaging application and 30 minutes of accessing the instant messaging application's associated website with the web browsing application. In this way, overall usage is optionally tracked in addition to simple native application usage.

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

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

Fig. 7A-7S are flow diagrams illustrating a method 700 of presenting an indication of a usage metric, according to some embodiments of the present disclosure. The method 700 is optionally performed on an electronic device, such as the device 100, the device 300, or the device 500 described above with reference to fig. 1A-1B, fig. 2-3, fig. 4A-4B, and fig. 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-powered electronic devices, improving the efficiency with which a user interacts with the user interface conserves power and increases the time between battery charges.

In some embodiments, a control panel user interface (e.g., a digital health control panel) is displayed (702) with 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 trackpad, and a touch screen, or a set-top box in communication with the television and an input device (e.g., a remote control), the dashboard user interface includes a visual indication of a first usage metric (e.g., a metric indicating how much of the first usage limit has been used, such as a percentage bar, a pie chart, etc.) and a visual indication of a second usage metric (e.g., a metric indicating how much of the second usage limit has been used), such as the usage metric dashboard user interfaces shown in fig. 6L-6U. The first usage metric is optionally associated with a first operation of the electronic device (e.g., screen time, time to use a particular application or a particular category of applications, receive a notification, follow 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 the day during which the user has used the device. In some embodiments, the visual indication of the first usage metric includes (706) a first usage quantification (e.g., an amount of time or number of times) of performing a first operation using the electronic device 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 graphic or chart. In some embodiments, the visual indication of the first usage metric is a displayed number indicating the usage metric (e.g., "3 hours of screen time"). The second usage metric is optionally associated with a second operation of the electronic device (708) different from the first operation (e.g., screen time, time to use a particular application or a particular application category, receive a notification, follow up event, etc.), such as in fig. 6L. For example, the second usage metric is optionally an indication of an amount of time that a user has spent using the electronic device to interact with a particular application. In some embodiments, the visual indication of the second usage metric includes (710) a second usage quantification (e.g., an amount of time or number of times) using the electronic device to perform a second operation 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 quantifications of usage, 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 has been spent by a user 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 applications and/or categories of applications (including the particular application).

In some embodiments, while displaying the visual indication of the first usage metric and the visual indication of the second usage metric in the dashboard user interface, the electronic device receives (712), via the one or more input devices, input corresponding to a request to display a visual indication of a third usage metric that is different from the first and second usage metrics (e.g., the third usage metric is associated with the first and/or second usage metrics and a different operation, a different operation type, a different usage quantification, and/or a different time period (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 a particular application, the electronic device updates the display to present the total screen time in the past week (e.g., rather than in the past day, allowing the user to view measurements over different time periods) and the time spent using the electronic device to interact with the particular application. As another example, in response to an input to view the number of notifications received by the electronic device over the course of a day (e.g., in response to a user input swiping down through the dashboard user interface), the electronic device updates to display a chart showing the number of notifications received at the electronic device within each hour of the day and details about how many of those notifications were generated by different applications. In some embodiments, in response to receiving the input, the electronic device updates (714) the dashboard user interface to include a visual indication of the third usage metric (e.g., with or without stopping display of 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 metric is optionally an input scrolling through the dashboard user interface, which optionally causes the visual indication of the third usage metric 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 interaction between the user and the device and enhances operability of the device (e.g., by providing more than one way to communicate device usage such that the user can view the usage metrics most meaningful to him), 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 (716) is one of a plurality of electronic devices associated with a user account (e.g., a user ID for accessing personal data and/or settings at the plurality of electronic devices), such as in fig. 6D. The control panel user interface (718) optionally includes a visual indication of a first respective usage metric (e.g., a first usage metric or a second usage metric) associated with a first operation of the plurality of electronic devices (including the electronic device) associated with the user account (e.g., the first usage metric tracks usage of all electronic devices associated with the user account for performing the first operation), such as in the UU of fig. 6. In some embodiments, the first usage quantification includes (720) a usage aggregation of performing a first operation using the plurality of electronic devices, including the electronic device, during a first predetermined time period (e.g., if the first usage metric is an amount of time spent running a particular application or a particular group of applications, the first usage quantification 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 time period), as shown in fig. 6 UU. The above-described manner of associating usage metrics with multiple electronic devices associated with a user allows the electronic devices to present accurate usage data to the user that is consistent across all of the user's devices, which simplifies interaction 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 of the devices without the user having to individually check 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 the first operation of the electronic device but not associated with the first operation of the second electronic device (e.g., the electronic device switches from displaying aggregated usage metrics across multiple devices to displaying a usage metric 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 TT. In some implementations, the electronic device simultaneously displays a visual indication of the usage metrics 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 accurate usage data to the user that is consistent across all of the user's devices, which simplifies interaction 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 of the devices without the user having to individually check 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 the visual indication of the first usage metric and the visual indication of the second usage metric are displayed in the dashboard user interface, the electronic device receives (724), via the one or more input devices, an input corresponding to a request to display the first usage metric and the second usage metric in more detail (e.g., a request to display more information about the first usage metric and/or the second usage metric (e.g., switch from an "overview" to a "detailed view"), such as selecting the first usage metric and/or the second usage metric in the dashboard 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 metric (e.g., a visual indication that includes more information than or about the first usage metric than included in the first visual indication) and a second visual indication of the second usage metric (e.g., a visual indication that includes more information than or about the second usage metric than included in the first visual indication), as shown in fig. 6G. The second visual indication of the first usage metric and the second visual indication of the second usage metric optionally include (728) a first respective visual indication of usage quantification (730) of performing the first operation using the electronic device for each of the plurality of time periods during the first predetermined time period, as shown in fig. 6 DD-6 EE (e.g., showing metrics in a one-hour day pane). In some embodiments, the second visual indication of the first usage metric is or is included in a graphical or chart (e.g., a line graph, a bar graph, a plurality of pie charts for each time interval, etc.) over time, and the second visual indication (732) of usage quantification of the second operation is performed using the electronic device for each of the plurality of time periods over a first predetermined period of time (e.g., showing the metrics in a one hour pane of the day), as shown in fig. 6G. In some embodiments, the second visual indication of the second usage metric is or is included in a graph or chart (e.g., a line graph, a bar graph, a plurality of pie charts for each time interval, etc.) over time. 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 first application suite) and a second operation (e.g., presenting information in a second application or second application suite). In some embodiments, the detailed view includes a diagram or chart that uses different colors or other visual indications to convey a quantification of use of performing a first operation (e.g., presenting information in a first application or first application suite) and a second operation (e.g., presenting information in a second application or second application suite) using the electronic device. The above-described manner of displaying more information about the first usage measure allows the electronic device to display an overview of usage and a detailed view of usage, which simplifies the interaction between the user and the device and enhances the operability of the device (e.g., by hiding details when the user does not want to see and by displaying details when needed), which in turn reduces power usage and improves the 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., selectable icon) visually associated with (e.g., displayed next to) the visual indication of the first usage metric, the first affordance being 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 an option for setting a usage limit for the first application or first set of applications (such as in method 900)), as shown in fig. 6HH through 6 II. 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 to alter the notification settings of the first application or the first set of applications. In some embodiments, a second affordance (e.g., a selectable icon) is visually associated with (e.g., displayed next to) a visual indication of a second usage metric, the second affordance is selectable to display (738) a setting user interface for altering one or more settings associated with the second usage metric (e.g., the second usage metric is an amount of time the electronic device has been used to run a second application or set of applications, and the setting user interface includes an option for setting a usage limit for the second application or set of applications (such as in method 900)), such as in fig. 6 HH-6 II. Additionally or alternatively, the second usage measure is optionally a number of notifications generated by the second application or the second group of applications, and the settings user interface includes an option to alter the notification settings of the second application or the second group of applications. In some embodiments, the control panel user interface includes a graph or chart (e.g., bar chart, line chart, pie chart, etc.) indicating at least the first and second usage metrics and a list of at least the first and second usage metrics. The control panel user interface optionally includes additional usage measurements in the diagrams or charts and in the lists. In some embodiments, the first affordance and the second affordance are displayed next to a visual indication of the first usage metric and the second usage metric, respectively, included in the list. In some embodiments, setting the user interface includes a visual indication of usage of the selected application or category throughout a first time period (e.g., the day), an indication of usage during a limited usage mode (e.g., bedtime or device downtime), an indication of average usage of a particular application, an indication of notifications generated by an application, an affordance for setting usage limits for a particular application, and a summary of store information about an application (e.g., rating, category, developer, link of an application in an application store). Additional or alternative measures are possible. In some embodiments, when a user selects an affordance associated with a category of applications, a respective metric is displayed for each application. In some embodiments, the electronic device displays affordances that are selectable to display metrics for individual applications in response to a user selecting an affordance associated with a category of applications. Displaying the affordances of the selectable setting user interface while displaying the first and second usage metrics allows the electronic device to provide a way for a user to navigate to the settings associated with the usage metrics while viewing the usage metrics, which simplifies user interaction with the device and enhances operability of the device (e.g., by simplifying the workflow of the user to change settings associated with the displayed metrics), 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 first predetermined time period is (740) the current day (e.g., the first usage metric is a usage quantification of a first operation performed using the electronic device during the current day), as shown in fig. 6 FF. In some embodiments, the day is defined to start at 12:00am 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 (742) with a first operation of the electronic device (e.g., the third usage metric is associated with the same operation of the electronic device associated with the first usage metric and is different in some other respect (e.g., usage quantification, time interval, etc.). in some embodiments, the visual indication of the third usage metric includes (744) a third usage quantification using the electronic device to perform the first operation during a week prior to the current day (e.g., the electronic device displays the usage metric associated with the first operation of the electronic device in a week (e.g., the past seven days including the current day, the week beginning on a particular day (e.g., a sunday or monday)), as shown in fig. 6 GG. in some embodiments, the visual indication of the first usage metric is a graphic or chart (e.g., line graph, bar graph, pie graph) or included therein. For example, the first usage measure is optionally an amount of time that the electronic device has been used to present information associated with a first application or group of first applications, and the control panel displays a graphical representation or chart including device usage for each day divided into sections representing each application or group of applications used. The above-described manner of updating the dashboard user interface to display the first usage metric for a week allows the electronic device to present usage metrics over a longer period of time, which simplifies the interaction between the user and the device and enhances the operability of the device (e.g., by presenting additional information simultaneously), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, the dashboard user interface includes (746) a visual indication of a first respective usage metric (e.g., a first usage metric) associated with displaying information on the display (e.g., the first operation is displaying usage or "screen time" (e.g., on all applications), as shown in fig. 6L. in some embodiments, the first operation also includes other ways of presenting information, such as playing sound (e.g., music or other media, spoken sound, such as during a phone call, etc.) with a speaker in communication with the electronic device, and the first respective usage metric includes (748) an amount of time that the electronic device has been used to display information during a first predetermined period of time (e.g., the first metric is a total usage of the electronic device on all applications on the electronic device for displaying information (e.g., total application screen time on the electronic device)), as shown in fig. 6L. In some embodiments, the overall usage metric further includes a time at which one or more speakers associated with the electronic device are used to present the audio content, and a time at which other output devices of the electronic device are used to present the information. The overall usage is optionally presented as an amount of time used over a specified period of time (e.g., a day, a twenty-four hour period, a week, or another period of time specified by the user). In some embodiments, the overall usage is optionally presented to the user in text (e.g., text indicating the amount of time the device has been used) and/or in a graphic such as a diagram or chart. The indication optionally includes a percentage bar that expresses overall device usage as a percentage (e.g., 50% of the four hour usage limit) or fraction (e.g., two hours of the four hour usage limit) of the usage limit set by the electronic device user. In some embodiments, in presenting a 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 that 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 displays or presents information associated with each of the plurality or group of applications. 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 their own device usage, thus reducing user input provided to the device (e.g., 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 use the device more quickly and efficiently.

In some embodiments, displaying information on the display includes (750) displaying the information on the display (e.g., or presented 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)) with one or more first applications (e.g., a particular application or group of applications, such as in FIG. 6L. in some embodiments, the group of applications is user-defined or defined by the system or a third party), as shown in FIG. 6L. The first respective usage metric optionally includes (752) an amount of time that the electronic device has been used to display information with the one or more first applications during the first predetermined time period (e.g., the first usage metric is a screen time associated with the one or more first applications), as shown in fig. 6L. In some embodiments, a usage limit (e.g., the amount of time the one or more first applications can be used to present information for a given period of time (e.g., a day) before access to the one or more second applications is restricted) is set (754) for the one or more first applications, as shown in fig. 6L. The visual indication of the first respective usage metric optionally further includes (746) an indication of a usage limit of the one or more first applications (e.g., a maximum amount of time that 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 metric (e.g., the visual indication visually compares the amount of time that 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 chart, and the size of the bar chart represents the usage limit. In some embodiments, the usage limit is predefined by the user. The control panel user interface optionally presents an indication of when the usage limit is nearing being reached (e.g., text or an icon indicating that the usage limit is nearing 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 the usage limits of one or more applications, groups of one or more applications, and/or the overall usage limit of the device. Thus, in some embodiments, the one or more first applications optionally include an application, a plurality of applications, or all applications accessible on the electronic device. The usage limits described herein are optionally the same as or similar to the usage limits described with reference to method 900. The above-described 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 one or more usage limits are enforced, which makes the user-device interface more efficient (e.g., the user does not have to compare their device usage to the usage limit by himself), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, the control panel user interface includes (758) a visual indication of a second corresponding usage metric (e.g., a second usage metric) associated with displaying information on a display (e.g., or presented 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)) with one or more second applications (e.g., a particular application or group of applications, as shown in FIG. 6N. In some embodiments, no usage limit is set for the one or more second applications (760), and the visual indication of the second respective usage metric optionally does not include (762) an indication of the usage limit of the one or more second applications (e.g., because there is no), as shown in fig. 6N. The visual indication of the second usage metric 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, although no usage limit is set for the one or more second applications, the usage of some or all of the one or more second applications is optionally limited by a usage 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 category (e.g., games). Although in this example, optionally no overall usage limit is set at the electronic device (e.g., a usage limit that sets the maximum amount of device usage across all applications), 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). Also, the one or more second applications optionally include specific applications (e.g., specific gaming applications), while the one or more first applications optionally include applications belonging to a specific application category (e.g., games). Although in this example, optionally no usage limit is set for a particular second application, usage of the second application is limited by the usage limits of the one or more first applications, as the one or more first applications comprise the second application. The above-described manner of indicating usage limits associated with application usage when displaying application usage metrics allows the electronic device to communicate how much time the user can continue to present information with the application before one or more usage limits are executed, which makes the user-device interface more efficient (e.g., the user does not have to compare their application usage to the usage limits themselves), which in turn reduces power usage and improves the 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 (764) that the amount of usage of the electronic device to display information with the one or more first applications is within a threshold amount of a usage limit of the one or more first applications (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.)), 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., displaying a text or icon indicating that the usage limit is approaching to be reached, or a visual characteristic is applied to the visual indication of the first usage metric (e.g., a visual indication or a change in color or size of a portion of the visual indication)), as shown in fig. 6W. In some embodiments, the visual indication of each of the one or more usage measurements includes an affordance selectable to display a settings user interface for altering one or more settings associated with the respective usage measurement. The affordance is optionally displayed with a visual characteristic (e.g., another color) indicating that the usage limit associated with the respective usage metric 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 close to being reached when the usage metrics are 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 usage to the usage limit by himself), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

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., an application group is a single application (e.g., an email application, a social network application, a game application, an internet browser, etc.)) or a category that includes a plurality of applications (e.g., a social media category, a game 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 measure is displayed as a graph or chart, the graph or chart includes a section for each application category (e.g., a pie chart with multiple "sections," a bar chart with multiple sections, a bar chart with multiple bars, etc.). The overall usage is optionally compared to usage limits (e.g., the entire pie of the pie chart represents a fixed usage limit, the length of the bar chart represents a fixed usage limit, etc.). In some embodiments, the control panel user interface includes (768) a visual indication of a second respective usage metric (e.g., a second usage metric) that the electronic device has been used to present information with the first application program group (e.g., a separate metric is presented that conveys an amount of time the first application program group was used in addition to presenting device usage of the first application program group within the overall device usage metric), as shown in fig. 6L. The visual indication of the second respective usage metric optionally includes (770) a visual indication of the second respective usage metric separate from the visual indication of the first respective usage metric (e.g., usage of the first application suite is presented in an additional manner than is presented as part of the visual indication of overall device usage (e.g., as part of a diagram or chart), as shown in fig. 6L. In some embodiments, the visual indication of the use of the first set of applications includes text indicating an amount of time the first set of applications was used. Optionally, a graphic separate from the visual indication of overall device usage is displayed, such as a bar of length indicating usage of the first application program group, a point of position indicating usage of the first application program group, or another visual representation of usage of the first application program group. In some embodiments, the electronic device presents a graph or chart showing how much time the electronic device has been used to present information with each of a plurality of applications and/or groups of applications, and a textual indication of the amount of time spent with each of the plurality of applications and/or groups of applications. The above-described manner of presenting device usage for each of a plurality of application suites allows the electronic device to present detailed information about device usage to a user in a graphical manner that simplifies interaction between the user and the device and enhances operability of the device (e.g., by presenting details about displayed metrics along with displayed metrics without further 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, 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 categories of applications) 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 control panel user interface optionally includes a visual indication (776) of a second corresponding usage metric (e.g., a second usage metric) associated with one or more second applications (e.g., individual applications or categories of applications, as shown in FIG. 6L. in some embodiments, the categories of applications are defined by a user. in some embodiments, the categories of applications are defined by an application store, a publisher, etc.) running on the electronic device that are accessible (e.g., installed on the electronic device or accessed via a network connection). Thus, the usage metric associated with the first operation is optionally an amount of time that the electronic device was used to run (e.g., display) one or more first applications during the first predetermined period of time, and the usage metric associated with the second operation is optionally an amount of time that the electronic device was used to run (e.g., display) 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 the interaction between the user and the device and enhances the operability of the device, which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, the one or more first applications are (778) multiple applications that belong to the same category (e.g., a user-defined category or a system-defined application category), as shown in fig. 6L. In some embodiments, the categories are defined by an application store, an application publisher or distributor, or another party other than the user. When a new application is introduced to the electronic device (e.g., downloaded from an application store), the usage limits set for the category associated with the new application are optionally automatically applied to the new application. The first metric is optionally a quantification of the overall usage of the set 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 usage of the individual applications), as shown in fig. 6L. In some embodiments, the dashboard user interface displays a mix of one or more metrics for a group of applications simultaneously 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, applications using a threshold above the predetermined application usage will optionally have application metrics presented in the dashboard user interface, while application categories using a threshold above the predetermined category (in some embodiments, no individual applications using a threshold above the application usage, and in some embodiments, even one or more individual applications using a threshold above the application usage) will have category metrics presented in the dashboard user interface. The above-described manner of simultaneously presenting metrics of individual applications and application categories in a dashboard user interface allows an electronic device to present usage metrics showing how the electronic device is being used in a meaningful manner (e.g., by displaying metrics with similar granularity), which simplifies interaction between the user and the device and enhances operability of the device (e.g., by simultaneously 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 use the device more quickly and efficiently.

In some embodiments, the first usage metric represents (782) usage of the native application and usage of a network resource associated with the native application (e.g., using a web application or viewing a web page) (e.g., when a user accesses a website (e.g., a particular social networking website) associated with an application of the electronic device (e.g., a particular social networking application associated with the website) using a browser application, usage of the website using the browser application, as shown in FIG. 6 RR) The above-described approach of a portion of usage metrics allows an electronic device to accurately track device usage associated with each application or class of usage metrics, which simplifies user-device interaction and enhances device operability (e.g., by combining network usage with appropriate usage metrics), which in turn reduces power usage and improves battery life of the device by enabling a user to use the device more quickly and efficiently.

In some embodiments, the control panel user interface optionally includes a combined usage metric for a plurality of first applications (e.g., a plurality of applications belonging to the same user-defined or system-defined category) of the one or more first applications in accordance with a determination (784) that the total usage of the plurality of first applications exceeds a predetermined category usage threshold (e.g., the predetermined category usage threshold is an absolute threshold (e.g., the predetermined category usage threshold is a predetermined amount of time (e.g., half an hour, two hours, etc.) or number of times (e.g., 5, 10, 50, etc.) that the plurality of first applications have been used to perform an operation (e.g., present information, generate a notification, etc.) during a first time period (e.g., a day, a week, etc.)) or a percentage threshold (e.g., 5%, 10%, 25%, etc. of total device usage during the first time period, not including individual usage metrics for any of the plurality of first applications) (e.g., when overall usage of the plurality of first applications exceeds a category threshold, the overall 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 PP. In some embodiments, in accordance with a determination (786) that the overall usage of the plurality of first applications of the one or more first applications does not exceed the predetermined category usage threshold (e.g., the overall usage of the plurality of applications belonging to the same category is less than the threshold), the dashboard user interface includes a usage metric for the respective applications of the plurality of first applications and does not include a combined usage metric for the plurality of first applications (e.g., the usage of one or more applications of the category is optionally presented as a separate usage metric (e.g., includes the first and/or second usage metrics) when the overall usage of the plurality of applications does not satisfy the threshold), as shown in fig. 6 PP. The above-described manner of selectively presenting metrics for a suite of applications allows the electronic device to present information regarding the categories of applications that are most frequently running, which simplifies interaction between the user and the device and enhances operability of the device (e.g., by presenting a combined metric for a suite of applications when overall usage of the suite of applications exceeds a threshold), 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, upon determining (788) that usage of a single first application in the one or more first applications (e.g., the one or more first applications are a plurality of applications belonging to the same category defined by the user or system) exceeds an application usage threshold (e.g., the predetermined application usage threshold is an absolute threshold (e.g., the predetermined application usage threshold is a predetermined amount of time (e.g., half an hour, one hour, two hours, etc.) or number of times (e.g., 5, 10, 50, etc.) that the first application has been used to perform an operation (e.g., present information, generate a notification, etc.) during a first time period) or a percentage threshold (e.g., 5%, 10%, 25%, etc. of overall device usage during the first time period), the control panel user interface includes a usage metric for the single first application (e.g., instead of or in addition to the combined usage measure of the plurality of first applications) (e.g., when the usage of the first application exceeds an application threshold, the usage of the first application is presented in the dashboard user interface as a first measure), as shown in fig. 6 QQ. In some embodiments, in accordance with a determination (790) that the overall usage of the single first application of the one or more first applications does not exceed the predetermined application usage threshold (e.g., the usage of the single first application is less than the threshold), the dashboard user interface includes a usage measure for the plurality of first applications (e.g., the usage of the plurality of first applications as a group is presented in the dashboard user interface as a first measure when the usage of the single first application does not satisfy the threshold), as shown in fig. 6 QQ. The application usage threshold described herein is optionally the same as or similar to the application usage limit described with reference to method 900. The above-described manner of presenting metrics for applications allows the electronic device to present information about the most frequently running applications, which simplifies interaction between the user and the device and enhances operability of the device (e.g., by presenting metrics for applications when usage of a group application exceeds a threshold), 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 includes (792) a visual indication of a first respective usage metric (e.g., a first usage metric) 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 KK. The one or more notifications are optionally received from another electronic device by way 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 control panel user interface allows the electronic device to communicate device usage for receiving notifications in an efficient and clear manner, which simplifies interaction 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 the one or more notifications at the electronic device includes (794) receiving a notification (e.g., receiving a new message notification from a messaging application) associated with one or more first applications (e.g., a particular application or group of applications, such as multiple applications in the same category as defined by the system or defined by the user) 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 vibratory or tactile and/or haptic output, plays a sound, etc.). The visual indication of the first respective usage metric optionally includes (796) a displayed number indicating a number of notifications (e.g., a particular application or group of applications, such as a plurality of applications in the same category as system-defined or user-defined) associated with the one or more first applications of the electronic device received during a first predetermined time period (e.g., a day, a week, a month, etc.). In some embodiments, the dashboard user interface includes (798) a visual indication of a second respective usage metric (e.g., a second usage metric) associated with receiving notifications associated with one or more second applications of the electronic device (e.g., receiving reminder notifications from a reminder application), 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 vibratory or tactile and/or haptic output, plays a sound, etc.). The visual indication of the second respective usage metric optionally includes (798-2) a displayed number indicating a number of notifications associated with the one or more second applications of the electronic device received during a first predetermined time period (e.g., a day, a week, a month, etc.), as shown in fig. 6R. The above-described manner of displaying notification metrics associated with an application or group of applications allows the electronic device to present information about which applications generated the most notifications, which simplifies user-device interaction and enhances device operability (e.g., by presenting application data as part of the notification metrics so that the user knows which applications caused the device to be most frequently used to present notifications), 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 changing the notification settings of applications that generate more notifications than the user intended 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., an option to allow all notifications for an application or group of applications, allow some notifications (e.g., based on priority, time of day, or some other metric), or disallow notifications), as shown in fig. 6 LL-6 MM. In some embodiments, the first affordance is visually associated with (e.g., displayed next to): a visual indication of the first respective usage metric (e.g., the notification metric is displayed simultaneously with the affordance for changing the notification settings), and a second affordance of a settings user interface selectable to display (798-8) for changing the notification settings of the one or more second applications (e.g., an option to allow all notifications, allow some notifications (e.g., based on priority, time of day, or some other metric), or disallow notifications for an application or group of applications), as shown in fig. 6 LL-6 MM. The second affordance is optionally visually associated with (e.g., displayed next to) a visual indication of a second respective usage metric (e.g., the notification metric is displayed simultaneously with the affordance for altering the notification setting). In some embodiments, the electronic device includes custom notification settings that are customizable for each application or for groups of applications. The electronic device optionally also includes notification settings that affect all applications on the electronic device. The above-described manner of displaying affordances 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 changing settings associated with a metric that a user is currently viewing, which simplifies interaction between the user and the device and enhances operability of the device (e.g., by enabling notification settings to be accessed when viewing the 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 changing notification settings after viewing the notification metrics).

In some embodiments, the visual indication of the first respective usage metric includes (798-10) a chart (e.g., a line chart, a bar chart, 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 time period (e.g., a day, a week, a month, etc.), as shown in fig. 6 LL. The above-described manner of presenting a graph 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 interaction between the user and the device and enhances operability of the device (e.g., by displaying related 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 a respective usage metric (e.g., a first metric or a second usage metric) associated with detecting a user attention event (e.g., the dashboard user interface includes a metric indicating a number of times a user initiates interaction with the electronic device), as shown in fig. 6U. In some embodiments, the electronic device presents a user attention event (e.g., "pick up device") dashboard indicating one or more metrics related to the user attention event. The user attention event dashboard optionally includes metrics such as average time between picks over a predetermined period of time (e.g., a day, a week, etc.), total number of picks over the predetermined period of time, a time range with the most user attention events over the predetermined period of time (e.g., an hour of a day or an hour or a day of a week), number of picks during a limited use mode (e.g., bedtime), and other metrics. In some embodiments, a user attention event is detected when a user input causes the electronic device to exit an idle state (e.g., a sleep mode, a locked state, a low power mode, etc., during which the user does not interact with the electronic device and/or a 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 corresponding to the request to enter the idle state (e.g., pressing a power or lock button of the electronic device). 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: a button of the electronic device is pressed, a user action to terminate an idle state (e.g., raise the device), an unlock input (e.g., enter a password or provide a biometric feature), and a touch input to access a function of the electronic device (e.g., a desktop applet user interface, a camera application, a dashboard user interface, a user interface that displays an application associated with a displayed notification indication). Detecting the biometric feature optionally includes detecting a face of the user with a depth camera or another sensor. In some implementations, the electronic device can utilize depth cameras and facial recognition techniques to determine when the user is looking at their electronic device and unlock in response to the user looking at the electronic device (e.g., the electronic device unlocks in response to determining that the user is focusing on the electronic device). In some embodiments, the electronic device exits the idle state in response to the notification (e.g., the display is open to display the notification without user input requesting the display to be 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 a user attention event, even though it causes the device to exit the idle state. In some embodiments, the event of interest metric indicates the number of times the user initiated use of the electronic device (e.g., "check" his phone). The above-described manner of displaying metrics associated with user attention events (e.g., picking up a device) allows an electronic device to present information about the frequency with which a user interacts with the electronic device, which simplifies interaction between the user and the device and enhances operability of the device (e.g., by communicating 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-14) a visual indication of a time between user attention events (e.g., an average time between user attention events (e.g., a button of the electronic device is pressed, a user action to terminate an idle state (e.g., raising the device), an unlock input (e.g., entering a password or providing a biometric feature), a touch input to access 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 the earliest user attention event during the first predetermined time period (e.g., the first attention event for the day, week, or other predetermined time period) and the last user attention event during the first predetermined time period (e.g., the last attention event for the day, week, or other predetermined time period). The above-described manner of displaying a measure indicative of the average time between user attention events (e.g., picking up a device) allows the electronic device to present information about the frequency with which a user interacts with the electronic device, which simplifies interaction between the user and the device and enhances operability of the device (e.g., by communicating 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-16) a visual indication of a total number of user attention events (e.g., a button of the electronic device is pressed, a user action to terminate an idle state (e.g., raising the device), an unlock input (e.g., entering a password or providing a biometric feature), a touch input to access 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) during a first predetermined time period (e.g., a day, a week, etc.), as shown in fig. 6U. The above-described manner of displaying a metric indicative of a number of user attention events (e.g., picking up a device) allows the electronic device to present information about the frequency with which a user interacts with the electronic device, which simplifies interaction between the user and the device and enhances operability of the device (e.g., by communicating 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 usage metric includes (798-18) a visual indication of a time interval (e.g., an hour of day, an hour of week, a day, etc.) during which the most number of user attention events were detected, the time interval being one of a plurality of time intervals over the first predetermined time period (e.g., the hour of day during which the most user attention events were detected, compared to all hours of the day, or the day or hour of week during which the most user attention events were detected, compared to all hours or days of the week), as shown in fig. 6U. The above-described manner of displaying a metric indicative of the time interval with the most user-focused 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 the interaction between the user and the device and enhances the operability of the device (e.g., by communicating usage information in a manner that is meaningful to the user), which in turn reduces power usage and improves the 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, detecting (798-20) the 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 accessible to the electronic device), a screen saver (e.g., an image displayed without displaying a user interface of any application accessible to the electronic device), or closed (e.g., without displaying an image)), the user input is identified as an event of interest (e.g., the event of interest is one of a device motion that satisfies one or more wake conditions (e.g., is raised to wake up), a touch input (e.g., a touch input that selects an image displayed on the lock screen), a touch input, A swipe input to display a desktop applet user interface, a camera user interface, or another user interface of an operating system or one or more applications), an actuation of a button included in an electronic device (e.g., pressing a power button, an unlock button, a home button, or another button or toggle switch), or a detection of a user biometric input (e.g., a fingerprint, a user facial image, or another biometric input (e.g., to unlock the device)). Detecting the biometric feature optionally includes detecting a face of the user with a depth camera or another sensor. In some implementations, the electronic device can utilize depth cameras and facial recognition techniques to determine when the user is looking at their electronic device and unlock in response to the user looking at the electronic device (e.g., the electronic device unlocks in response to determining that the user is 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 an idle state of the electronic device (e.g., the electronic device is not in an idle state, or the detected user input is erroneous (e.g., large body contact, device motion not corresponding to the user raising the device, etc.)), the electronic device forgoes identifying the user input as an event of interest (e.g., processes the user input as an input other than an event of interest or discards processing erroneous user input), as shown in fig. 6U. The above-described manner of detecting and recording the detection of various user attention events allows the electronic device to present information about the frequency with which a user interacts with the electronic device, which simplifies interaction between the user and the device and enhances operability of the device (e.g., by communicating 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., the electronic device displays a metric indicating a number of times the electronic device detected user events of interest during the limited-use mode), as shown in fig. 6U. The limited-use mode described herein is optionally the same as or similar to the limited-use mode described with reference to method 1100. The above-described manner of displaying a metric indicative of the number of events of interest during the limited use mode allows the electronic device to present information regarding the frequency with which a user interacts with the electronic device during a limited time, which simplifies interaction between the user and the device and enhances operability of the device (e.g., by communicating 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 be outside of the limited mode, thereby using their phone more efficiently).

In some embodiments, prior to displaying (798-28) the dashboard user interface, the electronic device presents an indication of a notification (e.g., a daily or weekly "digital health" notification) associated with the dashboard user interface, the notification including an affordance (e.g., a soft button or other user interface element) that is 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, the 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 a user input selecting the affordance (e.g., the electronic device presents a "digital health" notification at the beginning of the week or the beginning of the day, including a summary of one or more usage metrics). In some embodiments, a weekly "digital health" notification is presented at the beginning of the week, including a summary of the overall device usage of the last week. This summary optionally includes a visual indication of the amount of time the device was used to present information with each of the plurality of applications and/or application categories, and an indication that compares the overall device usage to the previous weeks (e.g., a percentage of average weekly usage above or below). In some embodiments, the daily "digital health" notification is presented at the beginning of the day, including a summary of the overall device usage of the previous day. This summary optionally includes a visual indication of the amount of time the device was used to present information with each of the plurality of applications and/or application categories, and an indication that compares the overall device usage to the previous days (e.g., a percentage of average daily usage above or below). Other time intervals are also possible (e.g., monthly use, etc.). The manner in which the control panel user interface is displayed in response to selection of a "digital health" notification described above allows the electronic device to remind the user to review its usage metrics and present more detailed metrics from the notification including a summary of the metrics, which simplifies the interaction between the user and the device and enhances the 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 the usage), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, prior to displaying the control panel user interface, the electronic device displays (798-30) a desktop applet user interface that includes an auxiliary user interface of an application that is accessible on the electronic device (e.g., installed on the electronic device or accessible via a network connection), as shown in fig. 6E-6I (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 that displays a current temperature, a sports desktop applet that displays a live event score, a news desktop applet that displays a title of a recent event, and/or any user interface object that displays content associated with the application), the content of the desktop applet corresponding to the application is dynamically updated by the application. The one or more desktop applets optionally include a metrics desktop applet associated with the dashboard user interface (e.g., a desktop applet associated with a digital health dashboard and/or digital health settings). In some embodiments, the measure desktop applet includes (798-32) visual indications of the respective usage measures (e.g., bar charts indicating the total time the electronic device was used to present information with each of a plurality of applications or groups of applications over the past week), as shown in fig. 6E-6I. 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 a week) to compare usage over the time period to previous usage. In some embodiments, the measure desktop applet can select (798-34) to display the dashboard user interface (e.g., the desktop applet expands to include more measures, such as a second measure or the electronic device presenting the dashboard user interface within the setup application), and the dashboard user interface is optionally displayed (798-36) in response to detecting a user input selecting the measure desktop applet (e.g., the dashboard user interface is displayed in response to a user selecting the measure desktop applet or expanding the measure desktop applet), as shown in fig. 6E-6I. The desktop applet user interface described herein is optionally the same as or similar to the desktop applet user interface described with reference to

methods

900, 1100, and 1300. The manner in which the dashboard user interface is displayed in response to selection of the metric desktop applet described above allows the electronic device to present one of the usage metrics (e.g., the first usage metric) in a top-level user interface (e.g., the desktop applet user interface) and provide a way for the user to enter input for viewing more detailed metrics while viewing the metric desktop applet, which simplifies interaction between the user and the device and enhances operability of the device (e.g., by presenting the usage summary as a desktop applet 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 use the device more quickly and efficiently.

In some embodiments, prior to displaying the dashboard user interface, the electronic device displays (798-38) a usage settings user interface for the electronic device (e.g., a settings user interface associated with device usage or a "digital health" settings user interface that is a settings user interface for an operating system of the electronic device, and does not display settings user interfaces for any particular application on the electronic device), as shown in fig. 6DD through 6 EE. 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 setting one or more time intervals, one or more applications, application categories, or usage limits for overall device usage (e.g., "quotas"), one or more whitelisting applications (e.g., phone, messaging, maps, etc.) or application functions (e.g., calling or receiving calls from particular contacts), and/or one or more privacy and content settings for operating the device in a limited usage mode (e.g., device downtime or bedtime mode). In some embodiments, the usage settings user interface includes visual indications (798-40) of 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 groups of applications over a past week), as shown in FIG. 6 DD. 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 a week) to compare usage over the time period to previous usage. The user setup user interface optionally includes an affordance (e.g., selectable image or selectable text that, when selected, causes the electronic device to update the display to present the dashboard user interface) that is selectable to display (798-42) the dashboard user interface. In some embodiments, the visual indication of the first usage metric may be selectable to display a dashboard user interface), as shown in fig. 6 DD-6 EE. 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 touchscreen at which the visual indication of the fourth usage metric is displayed) the 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 selectable to display a fourth usage metric for the dashboard user interface. In some embodiments, the fourth usage metric 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 current day, the current 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 that the electronic device can present information without one or more usage restrictions. The manner in which the dashboard user interface is displayed in response to selection of a visual indication in the usage settings user interface described above allows the electronic device to simultaneously present usage metrics and one or more usage settings of the electronic device and provide a way for the user to enter input for viewing more detailed metrics when viewing the usage settings, which simplifies interaction between the user and the device and enhances operability of the device (e.g., by presenting a usage summary in the settings user interface 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 use the device more quickly and efficiently.

In some embodiments, the usage settings user interface includes (798-44) one or more visual indications of one or more requests to modify one or more usage limits valid at the other electronic device received from the other electronic device (e.g., via a network connection (e.g., a wired or wireless connection), as shown in FIG. 6B. in some embodiments, the electronic device and the other electronic device are associated with a group or home account) (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 limited mode of operation (e.g., device downtime or "bedtime" mode)), as shown in fig. 6C. In some embodiments, the visual indications each include a displayed image or displayed text indicating the request. In some embodiments, the textual indication merely indicates that the request has been received or includes details about the request (e.g., the identity of the other device, the particular restrictions associated with the request, the identity of the user making the request, etc.). The visual indication is optionally selectable to display one or more options for approving or denying the request. The manner in which the visual indication of a request to modify one or more usage restrictions of other devices is displayed described above allows the electronic device to simultaneously present the request and the usage metrics and provide a way for the user to alter the usage settings of the other devices, which simplifies device-to-device interaction and enhances device operability (e.g., by presenting the usage settings of the electronic device and the 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 use the device more quickly and efficiently.

In some embodiments, the electronic device and the 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, electronic devices associated with a 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 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., by 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 of usage metrics (e.g., presenting information at the other electronic devices, receiving notifications at the other electronic devices, detecting user attention events at the other electronic devices) associated with the other electronic devices associated with the selected affordances, as shown in fig. 6V to 6W. In some embodiments, a parent can view the control panel user interface of each device of a child to monitor usage of the child device and set one or more usage limits (e.g., "quota")) 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 operating periods) to give to each user account based on a classification of the user account associated with the electronic device (e.g., as a parent, child, etc.) or an option selected when setting up the device. In some embodiments, the electronic device displays the usage metrics (e.g., overall device usage or screen time) associated with each electronic device associated with the user group account in a settings user interface. Optionally, each parent device displays a metric associated with each child device, but the child device optionally does not display a metric associated with any other device associated with the user group account, and the parent device optionally does not display a metric associated with an electronic device associated with other parent user accounts associated with the user group account. The manner in which one or more metrics associated with other devices in a user group account are displayed described above allows the electronic device to provide convenient access to usage information for multiple devices in a user group, which simplifies user-device interaction and enhances device operability (e.g., by presenting a settings user interface in which a user can modify one or more usage settings for 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 that is selectable to delete usage data of the electronic device (e.g., data related to device usage, such as the time or number of times information is presented, notifications is received, events of interest to the user are detected, etc. in some embodiments, deleting all of the usage data causes the usage metrics of the electronic device to be 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 selecting an affordance selectable to delete the usage data (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.), and deleting (798-58) the usage data in response to receiving the input. The manner in which the option for deleting all usage data is presented described above allows the electronic device to reset the usage metrics in response to a user request therefor, which simplifies user-device interaction and enhances device operability (e.g., presenting usage metrics that indicate only 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 use the device more quickly and efficiently.

In some embodiments, the usage settings user interface includes (798-60) an affordance that is selectable to stop recording usage data of the electronic device (e.g., data related to device usage, such as the time or number of times information is presented, notifications is received, events of interest to the user are detected, etc.), as shown in FIG. 6A. In some embodiments, the usage metrics stop updating when data collection is stopped, but remain in its 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 a 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 for the electronic device (with or without deleting all of the usage data). The manner in which the option for ceasing to record usage data described above is presented allows the electronic device to give the user control over what data is reflected in the usage measurements, which simplifies the interaction between the user and the device and enhances the operability of the device (e.g., presenting the usage measurements excluding user-defined time periods), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, the electronic device requires (798-66) authentication credentials for displaying a dashboard 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 CC (e.g., the electronic device receives user input at the one or more input devices selecting an affordance selectable to require a password (e.g., receives a touch at a location on a touch screen that displays the affordance, 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 a use data password and a soft keyboard for entering the password). When a password is required (e.g., in response to 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 settings user interface for altering settings associated with device use (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 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 settings related to device use 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 enters the correct password), the electronic device optionally presents a usage 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 usage settings user interface that can alter one or more of these settings (e.g., without the correct password, the electronic device does not allow the user to alter settings related to device usage). Optionally, the device presents an indication of the current settings (e.g., an indication of one or more usage limits or periods of time the device is operating in a limited use mode) without the ability to make changes. The manner in which the above-described option of presenting a password to make changes to one or more settings associated with device usage allows the electronic device to prevent unauthorized changes to the one or more settings associated with device usage, which simplifies interaction 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 a 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 usage 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 to restrict access to content (e.g., applications, music, videos, 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 to restrict sharing of a specified type of data, as shown in fig. 6A (e.g., location, contact, calendar data, reminder, photo, wireless connection, microphone, etc.)). The above-described manner of simultaneously displaying usage settings with parental guidance settings and data privacy settings allows the electronic device to present the relevant settings in a shared user interface, which simplifies interaction between the user and the device and enhances operability of the device (e.g., presents similar settings together), 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. 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. One of ordinary skill in the art will recognize a variety of ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein in connection with other methods described herein (e.g.,

methods

900, 1100, 1300, and 1500) also apply in a similar manner to method 700 described above in connection with fig. 7A-7S. For example, the usage metrics panel user interface, the usage metrics, the notification metrics, the device pick-up metrics, the usage restriction settings, and the like described above with reference to method 700 optionally have one or more of the features of the usage metrics panel user interface, the usage metrics, the notification metrics, the device pick-up metrics, the usage restriction settings, and the like 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 conjunction with fig. 1A-1B, fig. 3, fig. 5A-5H) or an application-specific chip. Further, the operations described above with reference to fig. 7A-7S are optionally performed by the components depicted in fig. 1A-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 recognizer 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 calls data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update the content displayed by the application. Similarly, one of ordinary skill in the art will clearly know how other processes may be implemented based on the components depicted in fig. 1A-1B.

Application and class usage limits

Users interact with electronic devices in a number of different ways, including utilizing applications accessible on the devices. In some cases, it is difficult for a user to monitor and limit the use of a particular application during certain time periods. The embodiments described below provide a way for an electronic device to enforce usage limits and determine that the usage limits are reached when limitations of particular applications or classes of applications are met (such as when application usage limits associated with those applications are reached), thereby limiting the user's use of particular applications that the user wishes to limit. Setting usage limits for a particular application or class of applications on an electronic device allows the electronic device to effectively limit the use of particular device operations by a user, and provides a simple way for a user to set such usage limits, which makes the use of the device more efficient (e.g., the user does not have to monitor their own device usage, thereby reducing user-provided input to the device (e.g., input for otherwise monitoring the user's usage)). For example, it is understood that the usage limit is set, the user can more judiciously and effectively use limited operations to perform all necessary tasks at the usage limit. If the usage limit is reached, the device limits the user to use 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 the battery life of the device by enabling the user to use the device more quickly and efficiently. It should be understood that one uses the device. When a person uses a device, the person is optionally referred to as the user of the device.

Fig. 8A-8 NNN illustrate exemplary ways to set, configure, or implement usage 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 illustrates an exemplary device 500 having a touch screen 504, described with reference to fig. 5A-5H. The 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 restriction condition is 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 restricted use mode). In some embodiments, the restriction condition is satisfied when a usage limit is reached for a given application or class of applications, as described below. In fig. 8A, the home screen 802 includes

icons

424, 426, 428, 432, 434, 436, 440, 442, 444, 448, and 450 for launching or otherwise displaying different applications on the device 500, as described above with reference to fig. 4A.

Fig. 8B-8T illustrate an exemplary method of setting and defining usage limits on a device 500 according to an example of the present disclosure. In fig. 8B, a touch object (e.g., a user's finger, stylus, hover input object, hover input device, etc.) (e.g., by providing contact 803) selects a settings application 446 from the home screen 802. It should be understood that contact 803 and the interaction between contact 803 and setting an 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 shown, 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 tapping) the affordance associated with the digital health setting 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 the user wishes to perform an initial usage limit setting (e.g., because the usage limit has not yet been set on the device 500). Message 806 includes an affordance for performing the usage limit setting (e.g., "continue" 808a) and an affordance for abandoning the usage limit setting (e.g., "do not now" 808 b). The user continues to use the limit settings by selecting "continue" 808a with contact 803. In some embodiments, the user optionally gives up the initial usage limit setting by not continuing with message 806 (e.g., by selecting "not now" 808b, by returning to home screen 802).

Fig. 8E illustrates an exemplary limited use mode settings user interface, optionally displayed by device 500 in response to selection of "continue" 808a in fig. 8D. In some embodiments, the limited use mode settings user interface is displayed in fig. 8E when the initial usage limit settings are performed. For example, one or more time windows associated with the limited use mode are optionally initially set in a limited use mode settings user interface, as described in more detail below in conjunction with fig. 10A-10 AAA and fig. 11A-11I. After the initial setting of the limited use mode is complete, 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 the initial use limit setting (e.g., by selecting "no" 810b, by returning to the home screen 802, by not associating any time windows with the limited use mode). Details of the limited use mode are described in more detail below with reference to fig. 10A-10 AAA and fig. 11A-11I. It is to be understood that any feature of the limited mode of use described in this disclosure is optionally 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 usage limit setting user interface 812 for setting usage limits for one or more applications or categories, optionally displayed by device 500 in response to selection of "YES" 810a in FIG. 8E. The exemplary usage limit settings 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 settings user interface includes selectable applications, allowing a user to set usage limits for individual applications. In this way, the user can select one or more application categories or one or more individual applications that the user wishes to restrict use.

In FIG. 8F, 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 is able to set usage limits for the applications and application categories selected by the user. The user can forgo the initial usage 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 application or category).

While the usage limit setting user interface is illustrated as being accessed, it should be understood that the usage limit setting user interface is optionally accessible 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 exemplary only, and that different applications or categories optionally appear on the usage limit setting user interface without departing from the scope of the present disclosure.

Fig. 8G through 8J illustrate exemplary methods of selecting a category of applications and selecting applications associated with the selected category for which the user wishes to restrict use. In fig. 8G, the user selects an application category (e.g., social media category 814e to set a usage limit for that category) (e.g., with contact 803). In some cases, the user selects more than one application category to set usage limits for those combined categories, or for each of those categories. In some examples, the user does not select the 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., a social media category), a category usage limit settings user interface 818 is displayed. As shown, all applications (e.g., social applications A-E820 a-820E) associated with the currently selected category are displayed and selected by default. In some embodiments, none of these applications is selected; the user selects the application of the currently selected category to be restricted. As shown, selecting a selected application (e.g., social media application B820B) (e.g., with contact 803) deselects the previously selected application (e.g., deselects social application B820B with contact 803). While a checkmark is used to indicate selection of a particular GUI object, it should be understood that other methods of indicating selection (e.g., highlighting, cursor) may be used without departing from the scope of this disclosure.

In FIG. 8I, social media application B820B is deselected in response to selecting previously selected social application B820B. In some embodiments, access to the deselected application is provided even after the usage limit associated with the category to which the application belongs has been reached (e.g., since the deselected application is a "white list" application, as described in more detail below). Deselecting an application (e.g., social media application B820B) optionally makes it unrestricted by a respective usage limit (e.g., social media category usage limit). That is, the whitelisting application (e.g., social media application B820B) is optionally accessible after a usage limit (e.g., a social media category) associated with the whitelisting application is reached.

In some embodiments, usage of a non-white listed application accounts for a usage limit associated with the application. For example, in FIG. 8I, social media application A820 a is optionally selected on usage limit settings user interface 818. Access to social media application a 820a is optionally restricted after the social media category usage limit has been reached. Usage of social media application A 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) for a currently selected category (e.g., social media) are selected to be restricted (e.g., access to applications in the selected set of applications is restricted after a usage 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, usage limit settings user interface 812, optionally displayed by device 500 in response to selection of "done" 822 in FIG. 8I, displays applications and/or categories (e.g., social media 814e) that have been selected to be implemented by one or more respective usage 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 name of the selected application exceeds the amount of space under the category, some of the selected application is displayed and followed by "more". Applications displayed under other categories (e.g., non-selected categories) are optionally not updated. Once all desired applications and categories have been selected for enforcement by one or more respective usage limits, the user proceeds to the next user interface (e.g., by selecting "Add" with contact 803).

Fig. 8K through 8M illustrate an exemplary method of setting usage limits associated with a category. The user can set different usage limits for the application or application class to be enforced 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 customization user interface 824. A notification and block option 828a and a notification option 828b are also displayed on the category usage limit customization user interface 824. The methods of implementing usage limits in the "notify" and "notify and block" modes are described in more detail below with reference to fig. 8NN through 8 WW. While the notification option 828b is selected in the illustration, it should be understood that the user can select either option for each usage limit. A default usage limit (e.g., "2 hours") associated with the category usage limit is displayed. In some embodiments, the default usage limit is automatically determined by the electronic device. The user is optionally able to self-define usage limits for different days (e.g., different usage limits than default usage limits) by selecting "custom day" 826 on the user interface.

In FIG. 8K, the selection of "custom day" by contact 803 is detected and, in response, device 500 displays a usage limit customization user interface, as shown in FIG. 8L. As shown in fig. 8L, different usage limits (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 usage limit is defined, the user selects "done" 838 to proceed to the next user interface.

FIG. 8M shows the category usage limit custom user interface 824 displayed after the custom usage limit has been set (e.g., after selecting "done" 838 in FIG. 8L). After the custom usage limit is set, the time period for which the custom usage limit is enforced is displayed under "custom day" 826. When the user selects "add" 830, the custom usage limit is added to the social media category usage limit setting. For example, as shown in FIG. 8M, one hour usage limits are implemented on Monday, Wednesday, and Thursday. The default usage limits of two hours are implemented on sunday, tuesday, friday and saturday.

After the usage limits are set in fig. 8M, device 500 optionally displays a digital health password setting user interface 840, as shown in fig. 8N, for protecting the set usage limits. In some embodiments, after the initial usage limit setting has been set, the electronic device displays the digital health password settings user interface 840 and prompts the user to enter a password associated with the digital health setting (e.g., usage limit setting) on the 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 the digital health settings on the device 500 (e.g., a child who knows the parent device password). While a four digit password is prompted in the illustration, it should be understood that different types of authentication credentials are optionally used to secure the digital health setting (e.g., alphanumeric password, biometric authentication, etc.).

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

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

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

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

Fig. 8R shows a category usage limit settings user interface 858. The category usage limit settings user interface 858 includes substantially similar information to that shown on the category usage limit settings user interface 818 in fig. 8H-8I. Previously selected applications (e.g., social media applications A820 a and C-E820C-820E) during use limit setting are displayed on the user interface 858. In some embodiments, the user redefines the applications to be restricted by selecting or deselecting applications on the category usage limit 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 usage limit for the category (e.g., renaming from "social media" to "John' S enjoyment), the updated name is displayed on the user interface 858. After the desired update to the category usage limit settings is performed, the user saves the updated settings by selecting "done" 822 and returns to the application limits user interface 850, as shown in FIG. 8T. FIG. 8T shows the application limits user interface 850 after the category usage limits settings have been updated. In response to renaming the previous social media category 852a as "John's fun," the application limits user interface 850 displays the updated name of the category 852a (e.g., "John's fun").

Fig. 8U through 8EE illustrate exemplary methods 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 restriction condition is not satisfied on the device 500 (e.g., no usage limit for any application or application category is reached). In some embodiments, the restriction condition is satisfied when a usage 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, the 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 embodiments, the notification indicator 864 is a label superimposed over (or partially over) an 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 results in device 500 displaying search user interface 866 when the restriction condition is not satisfied on device 500 (e.g., no usage 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, emails, 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 displaying applications suggested by the operating system of the device 500 for the user (e.g., suggesting commonly used applications, recently used applications, favorite applications, currently running applications), and desktop widgets 870B and 870c corresponding to applications installed on the device 500 (e.g., user interface objects or windows including text, images, and/or any other content associated with and updated by respective applications, such as social media applications a and B), as shown in fig. 8W. As shown in fig. 8W, social media applications a and B are included in the "application suggestions" 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 the text field 868 when the restriction condition is not met (e.g., no usage limit is reached) on the device 500. In response to the search term "social media" having been entered into the text field 868, the device 500 displays various search results related to the search term "social media" in the search user interface 866, as shown in FIG. 8X. For example, device 500 displays a link 874a of the social media application "social app a" installed on device 500, a link 874b of the social media website "social app a" as a website related to the "social app a" application, and links of 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 shows 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 by a restriction indicator 876 that replaces the previously displayed notification indicator). In some embodiments, as shown in fig. 8Y, a restriction label 876 at least partially overlays the social media application a icon 440. In some embodiments, the restriction indicator 876 at least partially overlays the textual description associated with the restricted 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 a restriction condition is satisfied on device 500 (e.g., a social media category usage limit is reached). The notification history user interface 878 includes notifications 880a-b associated with notifications for applications on the device. In some embodiments, in response to determining that the usage limit is reached, the appearance of the notification for 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 for applications associated with the usage limit are not displayed (e.g., suppressed) on the notification history user interface 878. When one or more notifications are suppressed on the notification history user interface 878, the electronic device 500 optionally displays one or more other notifications related to the non-restricted 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 a music application indicates that access to the music application is not limited.

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 BB, a horizontal swipe of contact 803 is detected on touch screen 504 while home screen 802 is displayed, which causes device 500 to display search user interface 866 in fig. 8BB when a restriction condition is satisfied on device 500 (e.g., a social media category usage limit is reached). Search user interface 866 is substantially similar to the user interfaces described in fig. 8V-8W.

The "application suggestion" user interface 870a displays applications that the operating system of the device 500 suggests for the user (e.g., suggests 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 limited suggested application is updated to indicate its limited state (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 constraints have 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 state (e.g., desktop applet grayed out, desktop applet 870b corresponding to social media application a grayed out), as shown in fig. 8 BB. In some embodiments, 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 desktop applet is suppressed on the search user interface 866, the electronic device 500 optionally displays one or more other icons or desktop applets associated with the non-restricted application in place of the notification associated with the restricted application. For example, in fig. 8BB, in response to device 500 determining that the social media usage limit category has been reached, desktop applet 870B associated with social media application a is grayed out (or optionally not displayed), while desktop applet 870c associated with whitelisted social media application B (e.g., the application not selected on usage limit settings user interface 818 in fig. 8I) indicates that access to social media application B is not limited.

In FIG. 8CC, the user has entered the search term "social media" into the text field 868 when the restriction condition is met on the device 500 (e.g., the social media category usage limit is reached). In response to the search term "social media" having been entered into the text field 868, the device 500 displays various search results related to the search term "social media" in the search user interface 866. During this time, access to the application associated with the usage limit being reached is restricted. For example, when the social media category usage limit is reached, device 500 displays a link 874a with the updated appearance of the social media application "social application a" (e.g., the social media application a icon grayed out) installed on device 500, and a link 874b with the updated appearance of the social media website "social application a" (e.g., the social media application a icon grayed out) as 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 restricted from searching (e.g., when a social media category usage limit is reached). In some embodiments, restricted social media category applications (e.g., non-white list social media category applications, social media applications A and C-E) do not appear in the search results when the social media category usage limit is reached. When one or more links are suppressed on the search user interface 866, the electronic device 500 optionally displays the one or more links related to the non-restricted application in place of the notification associated with the restricted application. For example, in FIG. 8CC, 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 link 874c associated with uninstalled social media application F and social media application G indicates that installation of these applications is not limited.

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

FIG. 8EE illustrates another web browser user interface 882 during which constraints are satisfied (e.g., a social media category usage limit is reached) on the device 500. As shown, the user is attempting 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 time that the social media category usage limit was reached, the content 882-4 of the website is overlaid 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., the user interface objects are grayed out) to indicate that access to the website is limited, as shown in FIG. 8 EE. 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 having the same home page URL) is restricted to the user.

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

Fig. 8FF shows the home screen 802 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, and a restriction indicator 876 overlays the icon). As shown, the user selects the application store icon 448 to proceed to the application store.

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

Fig. 8HH 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 social media application F is determined to be associated with the social media category usage limit, social media application F icon 452 reflects that the application is restricted (e.g., the icon grays out, restriction marker 876b overlays the icon).

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

Figure 8II shows the home screen 802 when the usage limit has not been reached. In fig. 8JJ, a message 888 (e.g., a notification) is presented and overlays the home screen 802. Message 888 indicates that the limited use mode (e.g., device down time) will begin after 5 minutes. If the user selects "dismiss" on the message, the message 888 stops displaying. In some embodiments, the message automatically stops being displayed after a period of time (e.g., 5 seconds, 30 seconds, or 1 minute) in the absence of the "dismiss" option.

Figure 8KK shows the home screen 802 when the bedtime limit (e.g., limited use mode) is active but no application use limit has been reached. For example, fig. 8KK optionally shows a home screen 802 that exceeds 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 usage limits 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 usage limit setting. That is, the social media category application and any other non-whitelisting 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 restricted application's icon (e.g., icon grayed out, restriction label 876 covering icon) is updated to indicate that the application is restricted (e.g., social media application a 440, social media application B442, Messenger application 424, music application 450).

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

Fig. 8LL illustrates the device 500 displaying a home screen 802 when no usage limit is reached. Fig. 8MM shows device 500 displaying 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 "notify" option is set on the category usage limits customization user interface 824, see FIG. 8M. The appearance of the application icon associated with the restriction (e.g., social media application a 440) 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 MM.

In response to attempting to launch a restricted application (e.g., access to the application is restricted when the usage limit is reached), the device 500 optionally notifies the user interface 890 with the restrictions displayed in fig. 8NN to visually obscure the home screen 802 (e.g., blur, graying, or visually change the home screen). Although the restriction notification user interface 890 is displayed in response to an action while the home screen is displayed (e.g., launching an application from the home screen), it should be appreciated that the notification user interface 890 may be displayed by the device on any then-displayed content (e.g., a user interface of an application) when the usage limit is reached. In some embodiments, device 500 displays interpretation 890-1 indicating that the usage 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 communicate to the user that the limit has been reached, as shown in fig. 8 NN. Restriction 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 usage limit reached is associated with only a single application, user interface 890 optionally would include only icons for that single application.

Restriction notification user interface 890 in FIG. 8NN includes a "remove" affordance 892. Selection of the cancellation affordance 892 is detected in fig. 8NN (e.g., through a contact 803 detected on the cancellation affordance 892). In response to selecting dismiss affordance 892, device 500 ceases to display dismiss affordance 892 on restriction notification user interface 890 and displays extension affordance 894 and ignore affordance 896, as shown in FIG. 8 OO.

In some embodiments, user selection of the delay presentation affordance 894 allows the user to access the restricted application beyond the usage limit of the application (without altering the actual time setting of the usage limit so that the previously defined usage 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 usage limit (e.g., as described below with reference to method 900). In some embodiments, user selection of ignore affordance 896 allows the user to forgo implementing the usage limit for that particular day (without altering the actual time setting of the usage limit so that the previously defined usage limit will continue to execute in the future) (e.g., as described below with reference to method 900). In some embodiments, the device 500 stops displaying the deferred affordance 894 and the ignore affordance 896 after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds) or when the user returns to the home screen 802 (e.g., by tapping any portion of the notification user interface 890 (other than the interpretation 890-1, the extended affordance 894, and the ignore affordance 896), by selecting a main button of the electronic device).

According to the "notify" option, the parent device (e.g., a device associated with a parent on the home account) or a device not associated with the home account at all (e.g., a stand-alone device) optionally does not require the user to enter any authentication (e.g., password, biometric authentication) to extend or ignore the usage limit on the device. Thus, in response to selection of either the deferred affordance 894 or the ignored affordance 896 in the OO of FIG. 8, the restricted notification user interface 890 ceases to be displayed and the user interface of the selected application is displayed; the user has unrestricted access to the application associated with the extended usage limit for a defined amount of time (e.g., 15 minutes, time remaining for the day) in the affordance selection. When the usage limit is extended or ignored, all other aspects of the application associated with the usage limit (e.g., any of the restricted user interface objects previously described) are also extended or ignored. For example, the user may view or interact with the desktop gadgets, notifications, and web pages corresponding to the applications associated with the extended or ignored usage limits. For example, as shown in FIG. 8PP, in response to selection of the deferred presentation representable in FIG. 8OO, the restriction 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 stopped displaying, the user has an additional 15 minutes of social media category usage time. In some embodiments, after the restriction notification user interface 890 ceases to display and prior to accessing the selected application, a graphical user interface object is presented on the display (e.g., resetting an hourglass, such as the hourglass 890-1 being flipped and starting an animation that is rerun) to indicate that the usage limit is extended. In some embodiments, usage of applications associated with the reached usage limit is tracked beyond the reached limit (e.g., by extension, by ignoring for the remaining time 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 a user beyond the two hour limit is optionally tracked by the device.

Fig. 8QQ through 8UU illustrate an exemplary method of presenting an indication that access to an application is restricted and utilizing local authentication to provide access to an application on a parental controlled child device.

Fig. 8QQ shows that the parental controlled child device 500A displays the main screen 802 when no usage limit is reached. Fig. 8RR 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, a "notify and block" option is set on the category usage limits customization user interface 824, see fig. 8M. The appearance of the application icon associated with the restriction (e.g., social media application a 440) 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 RR.

In response to attempting to launch a restricted application (e.g., access to the application is restricted when the usage limit is reached), device 500A optionally notifies user interface 890 with the restriction to visually obscure home screen 802 (e.g., blur, graying out, or visually change the home screen), as shown in fig. 8 SS. The restriction notification user interface 890 is substantially similar to the user interface described in FIG. 8 NN.

Selection of the elimination affordance 892 is detected in fig. 8SS (e.g., through a contact 803 detected on the elimination affordance 892). In response to selecting dismiss affordance 892, device 500A ceases to display dismiss affordance 892 on restriction notification user interface 890 and displays local authentication request affordance 898-2 and remote authentication request affordance 898-4, as shown in FIG. 8 TT.

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

As shown in fig. 8UU, in response to selection of the local authentication request affordance 898-2 in fig. 8TT, a password entry user interface 842 displayed by device 500A prompts an authorized user (e.g., a parent) to personally enter authentication. While a four digit password is prompted in the illustration, it should be understood that different types of authentication credentials are optionally used to secure the digital health setting (e.g., alphanumeric password, biometric authentication, etc.). In some embodiments, the authentication password used to extend or ignore the usage limit is different from a 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 as described with reference to fig. 8N. In some embodiments, in response to a properly entered authentication (e.g., a proper password), the user is granted additional access beyond the usage limit (e.g., 15 minutes, time remaining in the day) to the selected application. When the usage limit is extended or ignored, all other aspects of the application associated with the usage limit (e.g., any of the restricted user interface objects previously described) are also extended or ignored. For example, the user may view or interact with the desktop gadgets, notifications, and web pages corresponding to the applications associated with the extended or ignored usage limits.

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

Fig. 8 VV-8 YY illustrate exemplary methods 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., access to the application is restricted when the usage limit is reached), as similarly reflected in fig. 8QQ and 8RR and their respective descriptions, the child device 500A optionally notifies the user interface 890 with the restriction to visually obscure the home screen 802 (e.g., obscure, gray, or visually change the home screen), as shown in fig. 8 VV. The restriction notification user interface 890 is substantially similar to the user interface described in FIG. 8 NN.

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

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

For example, as shown in FIG. 8XX, in response to the selection of the remote authentication request affordance 898-2 on the child device 500A in FIG. 8WW, a message 898-6 including a plurality of extension affordances 898-8a through 898-8d is displayed on the parent device 500B. As shown in fig. 8BB, in some embodiments, a message 898-6 informs the parent user that a usage limit (e.g., social media category) on a child device (e.g., John jr's device) is reached and that the child user is requesting additional usage beyond the usage limit. The plurality of extension presentations 898-8a through 898-8d may indicate that the parent user is given different usage limit extension options (e.g., extend 15 minutes, extend for time remaining for the day, custom extend, deny extension request); the selected extension option is applied to the child device 500A. For example, as shown in FIG. 8XX, the parent user selects the extension show affordance 898-8a to give the requesting child user an additional 15 minutes beyond the usage limit.

In some embodiments, in response to selecting one of the delay show affordances 898-8 a-898-8 d, the password entry user interface 842 prompts the authorizing user (e.g., parent) to enter authentication on a remote authentication device (e.g., parent device 500B), as shown in fig. 8 YY. While a four digit password is prompted in the illustration, it should be understood that different types of authentication credentials are optionally used to secure the digital health setting (e.g., alphanumeric password, biometric authentication, etc.). In some embodiments, the authentication password used to extend or ignore the usage limit is different from a 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 as described with reference to fig. 8N. In some embodiments, in response to the authentication being correctly entered at the parent device 500B (e.g., the correct password), the child device 500A is granted additional access to the selected application beyond the usage limit; the amount of additional access depends on the selected latency presentation. 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 result of the request (e.g., 15 minutes extended, time remaining on the day extended, request denied).

After the request to extend usage beyond the usage 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 usage limit is extended under the "notify" option, as reflected in fig. 8PP and its corresponding description.

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

In response to attempting to launch a restricted application (e.g., access to the application is restricted when the usage limit is reached), as similarly described in fig. 8QQ and 8RR and their respective descriptions, the child device 500A optionally notifies the user interface 890 with the restriction to visually obscure the home screen 802 (e.g., blur, graying out, or visually change the home screen), as shown in fig. 8 ZZ. The restriction notification user interface 890 is substantially similar to the user interface described in FIG. 8 NN.

Selection of the elimination affordance 892 is detected in fig. 8ZZ (e.g., by a contact 803 detected on the elimination affordance 892). In response to selecting cancel affordance 892, device 500A ceases to display cancel affordance 892 on restriction notification user interface 890 and displays local authentication request affordance 898-2 and 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 the user to enter authentication (e.g., local authentication on the device (e.g., password, biometric authentication), remote authentication from another device (e.g., a parent device)) to extend or ignore the usage limit on the device. For example, as shown in FIG. 8AAA, the user selects the remote authentication request affordance 898-4 to request remote authentication for a desired extension of social media usage limits (e.g., authentication on parent device 500B).

As shown in fig. 8BBB, in some embodiments (e.g., unlike the embodiments of fig. 8 VV-8 YY), in response to selection of the remote authentication request affordance 898-2 on the child device 500A, the restriction notification user interface 890 ceases to be displayed and the message user interface 898-10 is displayed. For example, a messaging user interface is displayed (e.g., in a messaging application on device 500B) that includes the current status of a conversation between a child and a parent of the child (e.g., not necessarily related to the usage limit being reached). The messaging user interface 898-10 in FIG. 8BBB includes a message entry user interface 898-12 and a messaging affordance 898-14. Prior to sending a request for additional application access beyond the usage limit, the child can optionally enter a message (e.g., using an input device (e.g., keyboard)) 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 parent of the child. To send the request for additional access and accompanying messages, the user selects the messaging affordance 898-14. In some embodiments, a child user can send a request for additional access to their parent without entering a message.

In FIG. 8CCC, in response to selection of the messaging affordance 898-14 in FIG. 8BBB, the messaging user interface 898-10 is updated with a child's request for additional access, optionally represented as a rich message 898-16 to the child's parent. On the device that received the remote authentication request (e.g., parent device 500B), rich messages 898-16 are also displayed on messaging user interface 898-10. The rich messages 898-16 optionally include a request for additional access from a child user, an accompanying message, and a plurality of delay show affordances 898-18a through 898-18 d.

The plurality of extension presentations 898-18a through 898-18d may indicate that the parent user is given different usage limit extension options (e.g., extend 15 minutes, extend for time remaining for the day, custom extend, deny extension request); the selected extension option is applied to the child device 500A, similar to the selection of the extension affordance described in fig. 8 XX-8 CCC.

In some embodiments, in response to selecting one of the delay show affordances 898-18 a-898-8 d, the authorizing user (e.g., parent) is prompted on a remote authentication device (e.g., parent device 500B) to enter authentication, as similarly described in fig. 8 YY. In some embodiments, the authentication password used to extend or ignore the usage limit is different from a password of the electronic device used to prevent unauthorized extension of the usage limit. In some embodiments, in response to authentication entered correctly at the parent device (e.g., correct password), the child is granted additional access to the selected application beyond the usage limit; the amount of additional access depends on the selected latency presentation. 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 (e.g., a new message on the messaging user interface 898-10, a notification outside of the messaging user interface 898-10) of the result of the request (e.g., 15 minutes extended, time remaining on the day extended, request denied).

After the request to extend usage beyond the usage 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 usage limit is extended under the "notify" option, as described in fig. 8PP and its corresponding description.

Fig. 8DDD through 8GGG illustrate exemplary methods of presenting an indication that access to an application is restricted and providing access to the application based on authentication credentials input to an electronic device.

Fig. 8DDD shows device 500 displaying home screen 802 when a usage limit (e.g., social media category usage limit) is reached under the "notify and block" option of the usage limit setting. In some embodiments, a "notify and block" option is set on the category usage limits customization user interface 824, see fig. 8M. The appearance of the application icon associated with the restriction (e.g., social media application a 440) 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., access to the application is restricted when the usage limit is reached), device 500 optionally notifies user interface 890 with the restriction to visually mask home screen 802 (e.g., blur, graying, or visually changing the home screen), as shown in fig. 8 EEE. The restriction notification user interface 890 is substantially similar to the user interface described in FIG. 8 NN.

For example, selection of the elimination affordance 892 is detected (e.g., through a contact 803 detected on the elimination affordance 892). In response to selecting dismiss affordance 892, device 500 ceases to display dismiss affordance 892 on restriction notification user interface 890 and displays extension affordance 894 and ignore affordance 896, as shown in FIG. 8 FFF.

Under the notify and block option, devices without parental control, such as devices associated with an adult member (e.g., a non-child) in a family account, or devices not associated with a family account at all (e.g., a standalone device), require the user to enter authentication (e.g., password, biometric authentication) on the device to extend or ignore the usage limit. For example, as shown in FIG. 8EEE, the user selects the delay show affordance 894 to request an additional 15 minutes of usage time for the restricted category.

For example, as shown in fig. 8GGG, password input user interface 842 prompts the user to enter authentication in response to selection of extension affordance 894. While a four digit password is prompted in the illustration, it should be understood that different types of authentication credentials are optionally used to secure the digital health setting (e.g., alphanumeric password, biometric authentication, etc.). In some embodiments, the authentication password used to extend or ignore the usage limit is different from a 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 as described with reference to fig. 8N. In some embodiments, in response to a properly entered authentication (e.g., a proper password), the user is granted additional access beyond the usage limit (e.g., 15 minutes, time remaining in the day) to the selected application.

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

Fig. 8 HHH-8 III illustrate an exemplary method of displaying an indication that a warning threshold has been reached with respect to a usage limit.

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

Fig. 8JJJ through 8KKK illustrate an exemplary method of altering usage limit settings on a child device.

FIG. 8JJJ illustrates a child device's application limits user interface 850. The user attempts to access the usage limit settings for the social media category by selecting the social media category 852 a. As shown in fig. 8KKK, upon selection of the social media category 852a and determination that the device is a child device, the electronic device requires authentication (e.g., by entering a password on password entry user interface 842, by providing authentication credentials) before the social media category usage limit setting can be altered or viewed. While a four digit password is prompted in the illustration, it should be understood that different types of authentication credentials are optionally used to secure the digital health setting (e.g., alphanumeric password, 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 as described with reference to fig. 8N.

Fig. 8LLL through 8NNN illustrate an exemplary method of altering child device usage limit settings from a parent device.

Fig. 8LLL shows a child device 500A and a parent device 500B. The child device 500A and the parent device 500B belong to the same family account. In some embodiments, the names of the child and parent devices are determined during initial home account setup. The child device 500A in figure 8LLL displays the home screen 802 when the usage limit setting (e.g., social media category usage limit) is active. Meanwhile, the parent device 500B in the LLL of FIG. 8 displays the application limits user interface 850 of the child device 500A. In some embodiments, the application limit user interface 850 of the child device 500A is remotely accessed 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 UU and method 700). The parent selects the social media category 852a (e.g., by utilizing contacts 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. 8LL is substantially similar to the application limit user interface described in the present disclosure (e.g., as described with reference to fig. 6A-6 UU and method 700).

Fig. 8MMM illustrates the child device 500A and the parent device 500B when the parent user is attempting to modify the child usage limit setting on the parent device 500B. In response to the selection of the social media category 852a in the LLL 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 setting of the child device 500A can be altered or viewed. While a four digit password is prompted in the illustration, it should be understood that different types of authentication credentials are optionally used to secure the digital health setting (e.g., alphanumeric password, biometric authentication, etc.). In some embodiments, the password required to alter or view the usage limit setting is different from the password of the parent device used to prevent unauthorized access to the usage limit setting. For example, the authentication password is optionally a digital health password as described with reference to fig. 8N. In some embodiments, no password (e.g., alphanumeric password, biometric authentication, etc.) is required to change the usage limit settings of the child device from the parent device. After an attempt to modify a child usage limit setting is authenticated on the parent device, the parent user is optionally able to modify any usage limit settings associated with the selected category.

For example, fig. 8NNN shows the child device 500A and the parent device 500B when the parent modifies the child usage limit setting on the parent device 500B. After the parent modifies the social media usage 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 NNN), the parent device displays the application limit user interface 850 of the child device. In fig. 8NNN, the modified usage limit setting (e.g., one hour next to the social media 852 a) is displayed on the application limit user interface on the parent device 500B. Meanwhile, on the child device 500A, after the parent modifies the social media usage limit setting of the child device 500A, a message 898-20 (e.g., a pop-up notification) is presented on top of the primary screen 802, e.g., as shown in fig. 8NNN, to indicate that the child's social media usage limit setting (e.g., usage limit time, custom usage limit time period, addition of usage limit, removal of usage limit, combination of usage limits) has been modified by its parent. In some embodiments, the message automatically ceases to be 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 the notifications 898-20 and the notifications 898-20 are presented on the child device 500A in response to usage setting changes implemented on the parent device 500B, regardless of whether those changes are more or less restrictive to the 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 flow diagrams illustrating a method 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, 2-3, 4A-4B, and 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 an application or class of applications on an electronic device. The method reduces the usage of the electronic device when the usage limit is reached without requiring the user to monitor his own usage. For battery-driven electronic devices, limiting 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, a mouse, a trackpad, and a 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)) in communication with a display and one or more input devices receives (902), via the one or more input devices, a sequence of one or more inputs that set usage limits associated with a first application category accessible on the electronic device (e.g., a sequence of one or more inputs that can use the device or use the device in a particular manner (e.g., use a particular application (e.g., a particular social media application, SMS, phone, a particular travel application, email), a particular application category (e.g., social media, streaming media, games, travel, work, communication, payment, news), a maximum amount of time (e.g., one hour, three hours, twelve hours) spent by a particular function of the device (e.g., audio, camera, bluetooth, Wi-Fi), a particular function of the application (e.g., communicating with one or more contacts stored on the electronic device, etc.), such as in fig. 8A-8M (e.g., usage limit settings for a social media category). In some embodiments, the maximum amount of time accumulates over multiple sessions (e.g., periods of time that the application is used by the user are not used by the user (e.g., when the user is not using the device to run the application, including when the device is turned off, when the device is hibernating, when the device is disconnected from the network, etc.)). In some embodiments, the usage limits are set in a settings user interface of the electronic device (e.g., a settings application for setting the usage limits of the electronic device and one or more other settings, such as power settings, display settings, email settings, etc.). In some embodiments, the usage limit is set at another electronic device in communication with the electronic device (e.g., through a wireless connection). For example, a parent device is optionally used to set usage limits for a child's device.

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

In some embodiments, in accordance with a determination that a restriction condition for the first application category has been met when the usage limit associated with the first application category is valid (904), wherein the restriction condition includes requiring that the usage limit for the first application category has been reached in order for the restriction condition to be met (e.g., determining that the usage time of one or more applications (e.g., social media applications) or one or more operations of the first category of the user reaches a set usage limit), the electronic device restricts (908) access to the first application of the first application category (e.g., restricts user access to the one or more applications (e.g., particular social media applications) or operations of the first category (e.g., generally, social media applications), as in 8NN in the figure (e.g., in response to selecting social media, social media application a does not launch). In some embodiments, the usage time of the application requesting startup is compared to a usage limit. In some embodiments, in response to determining that the usage limit of the first application category has been reached, the request to launch the application is not launched or a dialog is displayed indicating that the usage limit has been reached and requiring further user action to complete the launch of the application. In some embodiments, restricting the application from the user is different than preventing the application from running. For example, a restricted application or operation, although restricted from the user, optionally still runs on the device (e.g., in the background where operating system tasks are performed) independent of user input.

In some embodiments, when the usage limit associated with the first application category is valid (904), in accordance with a determination that the limitation has not been met (e.g., the usage limit of the first application category (e.g., social media application) has not been reached (e.g., a determination that the usage time of the one or more applications or the one or more operations of the first category of the user has not reached the set usage limit)), the electronic device provides (910) access to the first application of the first application category, such as in FIG. 8PP (e.g., the user's access to the application (e.g., a particular social media application) or the first category of operations (e.g., generally, social media applications) is not limited). In response to a request to start an application, the application starts normally. The application usage limits described herein are optionally the same as or similar to the application usage limits or thresholds described with reference to

methods

700 and 1300. The above-described method of setting usage limits for an application category as a whole and enforcing the usage limits on individual applications of the application category allows an electronic device to effectively limit the use of a particular device operation by a user, and provides a simple way for a user to set such usage limits, which makes the use of the device more efficient (e.g., the user does not have to monitor his own device usage, thereby reducing the input provided to the device by the user (e.g., input for otherwise monitoring the user's usage), it is understood that the usage limits are set, the user can more judiciously and effectively use the limited operations to perform all necessary tasks at the usage limits; if the usage limits are reached, the device limits the user's use of the limited operations, thereby preventing the user from inadvertently exceeding the usage limits and spending more time on the device than expected), this in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, the restriction condition further includes requiring the first application not to satisfy one or more restriction exception conditions (912) (e.g., included on a list of applications (e.g., a whitelist) 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 usage of such applications does not count into usage limits (e.g., the application belongs to a first category, but the usage of the application is not counted against the usage limit for that category and/or overall device usage, in some embodiments, the restricted exception condition described above allows the electronic device to determine whether use of an application that belongs to a category having an associated usage limit is exempt from being included in the usage limit, this reduces the burden on the user to manually determine whether a particular application should be exempted (e.g., a particular social media application is optionally exempted, because the user needs the application to communicate with family and friends), 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 restriction condition for the first application category has 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 in a multitasking view along with other windows of other applications) (e.g., an icon of the first application) with a first visual characteristic (e.g., displays a normal icon of an application installed on the electronic device when a usage limit has not been reached (e.g., in a home screen of the electronic device), such as in terms of color, unmasked, etc.)), such as fig. 8U (e.g., the appearance of the application icon and the notification tab indicates that the application is not restricted). For example, the electronic device displays one or more application windows associated with one or more applications (e.g., in a multitasking 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 a restriction condition for the first application category has been met (e.g., in accordance with a determination that the usage limit has been 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 an appearance of an icon of the 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 EE, (e.g., the appearance of the application icon, the desktop applet, the notification, and the website indicates that the application is restricted). In some embodiments, when the usage limit is reached, the electronic device modifies the appearance of aspects of the application that are not included in the application whitelist. For example, icons of applications that are not included in the whitelist (e.g., icons on the home screen of the device, particular social media application icons) are shaded when the applications are restricted. As another example, notification identifiers included on application icons for applications not included in the application whitelist are optionally modified (e.g., a particular social media application icon). As another example, in some embodiments, the electronic device has multitasking 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 screenshots of current user interfaces of multiple applications, etc.). In some embodiments, representations of restricted applications in the above multitasking user interface that are not in the application white list are modified by the electronic device (e.g., faded or shaded, or otherwise modified to be displayed with different visual characteristics than representations corresponding to applications included in the application white list). The change in appearance of the application representation described herein is optionally the same as or similar to the change in appearance of the application representation described with reference to

methods

1100 and 1300. The manner described above of selectively changing the appearance of applications that are not on the application white list when the usage limit is reached allows the electronic device to effectively and selectively restrict usage of particular applications during certain time periods by providing an indication of what applications the user has or does not have access rights to when the usage limit is reached, which reduces usage of the electronic device during those time periods, 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 indicator on the first representation, the limited use indicator including an indication that access to the first application is limited (918) (e.g., an indicator with a visual indication of a lock or some other limitation symbol added to an application icon of the first application (and optionally also other applications that have reached their limits of use), such as covering a top right portion of the application icon; in some embodiments, the indicator covers at least a portion of text associated with the application icon; in some embodiments, the indicator covers at least a portion of the application icon), such as in FIG. 8AA (e.g., the limited use indicator replaces the notification indicator of social media application A). The manner described above of selectively changing the appearance of representations of applications that are not on the application whitelist when the usage limit is reached allows the electronic device to effectively and selectively restrict the use of particular applications during certain time periods by displaying restricted use identifiers on applications that the user does not have access to when the usage limit is reached, 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 time periods, thereby reducing power consumption and improving the battery life of the device.

In some embodiments, displaying the first representation of the first application with the first visual characteristic 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., the notification indicator of social media application a indicates the number of unread messages associated with the application). In some embodiments, displaying the first representation of the first application with the second visual characteristic includes displaying a first representation (922) (e.g., a vague indicator or a graphical replacement indicator) that the notification indicator has been replaced with a limited-use indicator, such as in fig. 8AA (e.g., the limited-use indicator replaces the notification indicator of social media application a). In some embodiments, the limited-use indicator described above replaces an indication of a notification indicator of an application icon of a non-white list application when the usage limit is reached. In some embodiments, replacing the indication of the notification indicator with the limited-use indicator described above hides the number of notifications associated with the application such that the number of notifications are no longer displayed on the display. The manner described above of selectively changing the appearance of representations of applications that are not on the application whitelist when the usage limit is reached allows the electronic device to effectively and selectively restrict usage of particular applications during certain time periods by replacing the notification indication of the application representation with a restricted usage identifier on applications that the user does not have access to when the usage limit is reached, which prevents the user from attempting to access restricted applications with such notifications by not indicating the presence of recent notifications, which reduces usage of the electronic device during those time periods, which in turn reduces power consumption and improves battery life of the device.

In some embodiments, in accordance with a determination that the first application does not satisfy the one or more restrictive exceptions (e.g., a non-whitelisted application, the first application is not on a whitelist, the first application is configured to be restricted after the usage limit is reached) and 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 credits (924) usage of the first application to the usage limit associated with the first application category (e.g., credits a contribution to usage of the non-whitelisted application to the usage limit associated with the first application category that includes the first application).

In some embodiments, in accordance with a determination that the first application satisfies the one or more restrictive exception conditions (e.g., a whitelist application, the first application being on a whitelist, the first application being configured to be accessible after the usage limit is reached, use of the application for whitelist purposes (e.g., a phone application and a messaging application for parental communication)) and while the first application is being used, the electronic device relinquishes (926) use of the first application to the usage limit associated with the first application category (e.g., in accordance with a determination that use of the first application is excluded from the usage limit (e.g., because the first application is included in the application whitelist, and e.g., the electronic device provides access to the first application after the usage limit of the first application category is reached; as well as, because the first application's use is for whitelisting purposes (e.g., a phone application or messaging application for communicating with a parent)), and its use is not counted to the usage limit. The method of forgoing usage of applications that satisfy the one or more restrictions (e.g., whitelisting applications, applications that are not restricted after the usage limit has been reached) described above allows the electronic device to monitor the usage limit for application categories without monitoring the whitelisting applications, which allows the electronic device to better manage application categories that include one or more whitelisting applications (e.g., applications that are not restricted after the usage limit has been reached) without having to add additional categories for the whitelisting 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.

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 optionally credits (928) usage of the first application to the usage limit associated with the first application category regardless of whether the first application satisfies the one or more restrictive exception conditions (e.g., credits a contribution to usage of the first application to the usage limit associated with the first application category 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 white list application, and its usage is counted into the usage limit. Usage of another social media application that is optionally not whitelisted is also optionally included as a usage limit. The method of crediting use of applications described above allows an electronic device to monitor usage limits for application categories that include whitelisted applications, which allows the electronic device to better manage application categories that include one or more whitelisted applications (e.g., applications that are not restricted after the usage limits have been reached) because the usage limits for the categories take into account use of the whitelisted applications without having to add additional categories for the 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 over one or more first implementation time periods (e.g., a usage limit for the first application category on a weekday), such as in fig. 8L (e.g., a default two hour social media category usage limit). In some embodiments, the electronic device receives (932), via the one or more input devices, a sequence of one or more second inputs that set a second usage limit associated with the first application category in one or more second enforcement time periods (e.g., use the device or use the device in a particular manner (e.g., use a particular application (e.g., a particular social media application, SMS, phone, particular travel application, email) during times other than a default time) (e.g., the second usage limit is valid on saturday and sunday while the first usage limit (e.g., default usage limit) is valid on monday through friday; the second usage limit is valid during work/lesson hours while the first usage limit is valid outside work hours; the second usage limit is valid on a particular day of the week, while the first usage limit is valid outside of that particular day) a second maximum amount of time (e.g., one hour, three hours, twelve hours) that may be spent, such as in fig. 8L (e.g., one hour social media category usage limits on monday, wednesday, and thursday).

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, work/class time, monday through friday)), the electronic device implements (934) a first usage limit (e.g., a second usage limit is entered when an application (e.g., a particular social media application) of a first application category (e.g., social media) is accessed, provides or limits access to applications of the first application category based on the second usage limit), as shown in fig. 8L.

In some embodiments, in accordance with a determination that the current time is within the one or more second implementation periods (e.g., a determination that the current time is outside of a user-defined implementation period (e.g., a default period, outside of a particular day of the week, after work/school hours, saturday to sunday)), the electronic device implements (936) a second usage limit, as shown in fig. 8L (e.g., a first usage limit is entered when an application of a first application category (e.g., social media applications) is accessed, access to applications of the first application category is provided or limited based on the first usage limit) (e.g., a default usage limit)). The above-described method of allowing different usage limits for different days for a first application class allows an electronic device to effectively limit a user's use of a particular device operation during a defined time period and provides an easy way for the user to set such usage limits during the defined time period, which makes the use of the electronic device more efficient (e.g., the user's use is restricted exclusively during class/work hours, workdays, particular days; it is understood that the second usage limit is set, the user can more judiciously and effectively use the limited operation to perform all necessary tasks at the second usage limit during a second particular time period (e.g., class/work hours, workdays); if the usage limit is reached, the device restricts the user's use of the restricted operation, thereby preventing the user from performing the particular time period (e.g., class/work hours, weekdays) inadvertently exceeding usage limits and spending more time on the device than expected), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

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 category (e.g., a second particular social media application is associated with a social media category having an associated usage limit) from the usage limit of the first application category (e.g., the request to exclude the second application is optionally set on the settings user interface.

After receiving input corresponding to a request to exclude the second application from the usage limit, and when the restriction condition for the first application category is satisfied (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 launching when the social media category 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 a second particular social media application is not restricted regardless of whether 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 the social media category usage limit is reached). While the first application (e.g., a first particular social media application) and the second application (e.g., a second particular social media application that is different from the first particular social media application) belong to a category of social media, the electronic device is able to exclude the second application (e.g., the second particular social media application) from the category (e.g., social media) usage limits while the first application is restricted from use. In some embodiments, the user can define which applications are excluded from such category usage limits. In some embodiments, an application is excluded if the user or the electronic device does not define the usage limit of the application. The above-described method of excluding applications associated with a category from usage limits for a category allows an electronic device to distinguish between using applications that are limited by usage limits (e.g., a first application) and using applications that are not limited by usage limits (e.g., a second application), which reduces the burden on a user to address limitations on applications that should be excluded from such limitations (e.g., while the second application is associated with a category having usage limits, the second application is optionally excluded from usage limits by the user because the user does not want the application to be limited), 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 is also associated with a second category of applications accessible on the electronic device, the second category of applications including different applications (946) than the applications of the first category of applications (e.g., the usage limit is associated with two or more categories such that an overall usage limit for both categories of applications is set and each of the two or more categories has a different group of applications (e.g., no two groups have the same list of applications)), such as in fig. 8Q (e.g., social media category usage is first associated with social media category usage limit and streaming and social media category usage limits). For example, usage limits are optionally associated with social media and streaming applications. As another example, usage limits are optionally associated with social media and messaging applications. While a particular social media application is associated with both social media and messaging categories, the application lists in the social media categories and messaging are optionally different. The above-described method of associating a first application category and a second application category to usage limits allows the electronic device to limit the usage of the two categories of applications by associating the category usage limits, which reduces the burden on the user to track the different usage limits of the different groups, which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently if overall usage of the different groups in total is desired.

In some embodiments, the first application category includes all applications accessible on the electronic device (948) (e.g., the usage limit is associated with all applications and categories on the electronic device such that the total usage limit for all applications on the electronic device is set), such as in 8Q (e.g., "all" usage limits). For example, if the overall limit is optionally set, then the use of first and second particular social media applications is limited by the overall limit even if the particular applications are associated with a social media category. The total usage limit here is the same as or similar to the total screen time usage limit described with reference to method 700. The above-described method of setting the overall usage limit for all application categories allows the electronic device to limit all non-whitelisted application usage (e.g., implement user screen time limits) by the overall usage limit, which reduces the burden on the user to define separate limits for each category when the overall usage limit is desired, which in turn reduces power usage and improves the 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 based on one or more classification criteria (e.g., a user previously defined category name, a device previously defined category name), such as in fig. 8Q (e.g., a social media category usage limit has a default name "social media"). In some embodiments, the default name of the usage limit is a device-determined name of an application category determined based on the category of applications in the application category, such as "news" or "games" or "news and games"). The electronic device optionally receives (952) a sequence of one or more second inputs (e.g., the sequence of one or more second inputs optionally received from the one or more input devices (e.g., electronic device, remote input device)) that rename the usage limit name to a second usage limit name, such as in fig. 8R (e.g., the user selects a "rename" affordance to rename the social media category usage limit name). In some embodiments, in response to the sequence of one or more second inputs, the electronic device names (954) the usage limit names to second usage limit names (e.g., the category names are redefined by the user), such as in fig. 8S-8T (e.g., the user renames the social media category usage limit to "John' S fun"). In some embodiments, the user can rename a category name (e.g., a user previously defined name, a device previously defined name) by entering the user-defined new 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-defined different categories (e.g., a particular social media application belonging to a social media category and a particular game application belonging to a game category) and create their own category name (e.g., "restricted applications," "social media, and games"). In some embodiments, the electronic device automatically renames the category name. For example, a category named "social media" optionally initially 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 games". The above-described method of renaming usage limit class names allows an electronic device to receive input (e.g., from a user, from a remote input device) and rename usage limit class names in response thereto, which allows a user to rename usage class names when a more appropriate usage limit class name is desired (e.g., when a new application is associated to a 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 956 with both a usage limit associated with the first application category and a second usage limit (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 a social media category usage limit and a streaming and social media category usage limit). 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 a social media category limit, and/or the electronic device optionally has a usage limit of a particular application within the social media category (e.g., half an hour or some other amount). 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 forth. The above-described method of implementing two or more usage limits simultaneously allows the electronic device to monitor the usage of applications relative to the two or more usage limits, which reduces the burden on the user to associate applications that the user wishes to limit to each of the two or more usage limits separately and to monitor each of the two or more usage limits separately, 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 first application is associated with a second constraint, the second constraint comprising a requirement that: for the second limitation to be met, the usage limit of the first application category has been reached, or for the second limitation to be met, the second usage limit has been reached (958) (e.g., in some embodiments, the second limitation is met when the most conservative limit (e.g., the usage limit with the least time remaining) is reached), such as in fig. 8Q (e.g., a social media application is associated with both social media category usage limits and streaming and social media category usage limits, and a more conservative usage limit is implemented). In some embodiments, in accordance with a determination that the second limitation has been met, the electronic device limits (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 a more conservative usage limit is enforced).

In some embodiments, in accordance with a determination that the second limitation 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 neither usage limit has been reached). For example, the first application is optionally associated with two usage limits. The first application optionally belongs to a social media category, 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 residual, and the overall usage limit optionally has a 2 hour residual. In this example, the social media category usage limit is the minimum remaining usage limit for the social media application. As another example, after a certain device usage, the overall usage limit optionally has a 30 minute remaining, and the social media category optionally has a 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 a minimum remaining usage limit for the social media application. For any class or application associated with more than one usage limit, a more conservative remaining usage limit optionally limits the usage of the first application. The above-described method of enforcing the most conservative usage limit of two or more simultaneous usage limits allows the electronic device to monitor the usage of applications relative to the two or more usage limits and enforce the most conservative remaining usage limits, which reduces the burden on the user to associate the applications that the user wishes to limit to each of the two or more usage limits separately and to determine which of the usage limits was reached earlier separately, which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, upon satisfaction of the restriction condition for the first application category (964), the electronic device detects (966) an event corresponding to activation of a secondary function of the first application (e.g., occurrence of an event that would trigger display of a notification for 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 for the application), a request to display application content in a picture-in-picture (PIP) mode, a request to display the application in search results, or a request to display and/or perform a media control operation associated with the application), wherein the secondary function of the first application is available for execution without displaying a primary user interface of the first application (e.g., not launching the application in the application window or other main view of the application), such as in fig. 8Y-8 EE (e.g., the user is attempting to view or access application suggestions, desktop applets, search results, and websites corresponding to social media application a when the social media category usage limit has been reached).

In some embodiments, in response to detecting an event corresponding to activation of the secondary function of the first application, the electronic device suppresses (968) the secondary function (e.g., suppresses a notification generation function associated with the application, a display of a website associated with the application, a shared table action, a display of application content in PIP mode, and any other functions associated with the application (including operating system functions) (e.g., restricts applications from appearing in search results, displays access to a desktop applet associated with the application, restricts applications from appearing as suggested applications) such as in fig. 8Y-8 EE (e.g., application suggestions corresponding to social media application a, desktop applets, search results, and websites from being accessible to the user when a social media category usage limit has been reached). Launching of the application is also suppressed (e.g., limited), where such launching is from a home screen of the electronic device (or other user interface of the electronic device). In some embodiments, the secondary function is inhibited by preventing the function from being executed in response to detecting the event. The ancillary functions described herein are optionally the same as or similar to the ancillary functions described with reference to method 1300). The manner in which the functionality is inhibited on different aspects of the operating system of an application for which the usage limit has been exceeded described above allows the electronic device to effectively reduce the overall utilization of the electronic device, which reduces power consumption and improves the 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) that associates the second application with a corresponding application category (e.g., downloading a new application (e.g., a second particular social media application) from the application store, remotely accessing the new application, installing the new application on the device. in some embodiments, the application store associates the application with a particular application category based on publisher information about the application or some other determination made by the application store (e.g., the news application is designated as part of a news category in the application store, the game is designated as part of a game category in the application store, etc.)) such as in fig. 8FF through 8GG (e.g., the user is adding a social media application F from an app store user interface).

In some embodiments, in accordance with a determination that the respective category is a first category (e.g., a determination that the category assigned to the added application by the app store is the same as an existing category on the electronic device having a usage limit), the electronic device controls (972) access to the second application in accordance with the restrictions 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 the application source), such as in FIG. 8HH (e.g., the newly added social media application F is determined to be within the social media category usage limit; access to the newly added social media application F is restricted when the social media category usage limit has been reached). Thus, the electronic device applies the first class restriction to the subsequently added second application. In some embodiments, the determination of the category assigned to the added application by the application is based on application store attributes of the added application (e.g., games, social media, news, streaming.

In some embodiments, in accordance with a determination that the respective category is not a first category (e.g., a determination that the added application does not belong to the first category (e.g., a category other than social media)), the electronic device relinquishes (974) access to the second application in accordance with a restriction of the first application category (e.g., use of the added application (e.g., a second particular social media application) is optionally not associated with a first category usage limit (e.g., a social media usage limit). Application store classification, metadata of the new application) and enforcing a usage limit for the new application (e.g., the second particular social media application) associated with the determined category (e.g., social media) allows the electronic device to effectively limit the user's usage of the added application without the user determining the category of the new application, which makes the use of the device more efficient (e.g., the user does not have to manually determine the category of the added application; the user does not have to manually determine the usage limits of the added application; the user does not have to monitor their own device usage of the added application, thereby reducing user-provided input to the device (e.g., input for otherwise monitoring the user's usage); if the usage limit is reached, the device restricts the user from using 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 the 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 a limited usage mode during which access to one or more applications on the electronic device is limited are defined on the electronic device (976) (e.g., a user of the electronic device defines hours of the day (e.g., 10pm to 5am) as a bedtime limited usage mode during which the electronic device prevents or attempts to prevent access to all applications on the electronic device, except for applications on a whitelist of included applications in some embodiments), such as in fig. 8E (e.g., a device downtime period is set). In some embodiments, the user defines only the upper time window, not specifying any particular application to which access is to be restricted — in such embodiments, the electronic device optionally defaults to restricting or attempting to restrict use of all applications other than the whitelist application during the restricted use mode. In some embodiments, in accordance with a determination that the request to launch the 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 take effect during a defined period of time, the bedtime limited-use mode is set), and 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, the electronic device is currently in the bedtime limited-use mode), the electronic device limits (978) access to the first application regardless of whether a limitation condition for the first application category has been satisfied (e.g., the limited-use mode overrides the use limit), such as in fig. 8 II-8 KK (e.g., the device down time setting overrides the social media category use limit setting, device downtime set limits social media applications when social media category usage limits have not been reached). Access to the first application class is optionally restricted during the restricted use mode even if, for example, a usage limit of the first application class has not been met. The limited-use mode described herein is optionally the same as or similar to the limited-use mode described with reference to method 1100. The manner in which the limited usage mode (e.g., bedtime limited usage mode) is implemented in conjunction with the application usage limit described above allows the electronic device to limit access to one or more applications or classes of applications before the usage limit has been reached (e.g., during device downtime, a specified inactivity time (e.g., bedtime)), which allows the user to better manage device usage during limited activity times (e.g., bedtime), although the usage limit may not have been reached, 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, restricting access to the first application includes presenting an indication indicating that access to the first application is restricted (e.g., displaying a visual indication on a display (e.g., an hourglass indicating time out, one or more application icons associated with a time limit reached), playing a 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)), where the indication includes an affordance (980) (e.g., a graphical user interface element or soft button that allows user access to the restricted application when the usage limit is reached) that is selectable to provide access to the first application without authentication credentials, such as in fig. 8 NN-8 OO (e.g., a restriction under the "notify" option notifies the user interface to provide an extension for continuing the restricted application and an ignore affordance for continuing with the restricted application), such as in fig. 8 NN-8 OO (e.g., a restriction under the "notify" option ). 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" restriction option. If the user attempts to launch an application associated with a "notification" limitation (e.g., by selecting an icon for the application from a 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 was reached). The pop-up notification optionally includes one or more affordances that, when selected, allow the user to proceed to the application without entering any authorization credentials (e.g., open the application without entering an "always on" affordance for an administrator or other credential; in some embodiments, application usage beyond an allowed 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 EE-6 HH, 6 OO-6 SS, and 6 UU) The items are the same or similar. The manner described above of notifying the user that an application is restricted when a usage limit is reached, but giving the user the option of accessing the application when needed, allows the electronic device to effectively limit the use of certain applications during certain time periods while allowing the user to perform the necessary tasks on the electronic device, which reduces the use of the electronic device during those time periods, 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 an indication indicating that access to the first application is restricted, wherein the indication comprises an affordance (982) selectable to provide access to the first application while requiring authentication credentials (e.g., to display a visual indication on a display (e.g., an hourglass indicating time out, one or more application icons associated with usage limits reached), to play a sound with a speaker associated with the electronic device, to generate a haptic and/or tactile output, etc., indicating that the application is restricted (e.g., a notification)), such as in fig. 8 EEE-8 GGG (e.g., a restriction notification user interface under the "notify and block" option provides an extension 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" restriction option. If the user attempts to launch an application associated with the "block and notify" restriction (e.g., by selecting an icon for the application from a 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 launch and optionally displays a pop-up indication indicating that application usage is currently restricted (e.g., because the usage limit was 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., requiring awareness of attention via the depth camera for successful biometric authentication)) 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, selecting the request in the notification optionally results in the notification being delivered to one or more (or all) parent devices associated with the family account, and the electronic device allows access to the application when permission is granted (e.g., at least one of the parent devices or a password at a 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 or similar to the "block and notify" option described with reference to method 1100. The manner described above of blocking application startup when usage limits are reached and informing the user that the application is restricted allows the electronic device to effectively limit the use of certain applications during certain time periods, which reduces the use of the electronic device during those time periods, 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 a first application (984), such as in fig. 8EEE through 8GGG (e.g., a restriction notification user interface under a "notify and block" option provides an extension and ignore affordance for requesting authentication before proceeding with the restricted application) The parent device (e.g., set at the time of initial setup of the device) or not associated with the home account at all. 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. In some embodiments, the affordance includes one or more of soft buttons or input fields for user id, password, fingerprint authentication, and/or facial authentication (e.g., requiring awareness of attention via the depth camera for successful biometric authentication). For example, if the device is not a child device in the home account (e.g., is a parent device in the home account) or is not associated with the home account at all, the electronic device optionally requests the user to enter credentials (e.g., a user id and/or password, password) for a user account associated with the electronic device (e.g., a user id and/or password associated with a profile to configure the device). In some embodiments, the credentials (e.g., user id and/or password, password) are different from the credentials used to access the electronic device (e.g., a password different from a password used to "unlock" the device and/or log in to the device). As such, a user (e.g., a child) that is not the device owner (e.g., parent) would not be able to bypass the application restriction if the auxiliary password were not 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 to 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 the parent device in a home account), such as in fig. 8 TT-8 CC (e.g., a local authentication request affordance and a remote authentication request affordance are displayed on a restriction notification user interface on the child device; in response to selection of the affordance, requesting authentication on a different corresponding device). 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 the time the device is initially set up). 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 requesting access to the first application). The process would then 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 to access the restricted application when the usage limit is reached) or deny access to the restricted application from the child device. 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 a first application. In some implementations, the password is a parental control password or a use password that is different from the password used to unlock the electronic device. In this way, 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 manner described above of notifying the user of the option that the application is restricted when the usage limit is reached, but that enables the user to access the application when needed, allows the electronic device to effectively limit the use of certain applications during certain time periods while allowing the user to perform the necessary tasks on the electronic device, which reduces the use of the electronic device during those time periods, which in turn reduces power consumption and improves the battery life of the device.

In some embodiments, upon determining that the usage limit associated with the first application category is valid, in accordance with determining that the warning threshold for the usage limit has been reached (e.g., the warning threshold was reached when a portion of the usage limit has been reached (e.g., 90%, 5 minutes remaining, 45 minutes of 1 hour; 5 minutes, 10 minutes, 1 hour before the usage limit was reached; or any time period), the electronic device displays (988) an indication (e.g., a text, an image, a sound, a haptic and/or tactile output, etc.) that the warning threshold for the usage limit has been reached (e.g., indicating that the usage limit is about to be reached and that a threshold time (e.g., 90%, 5 minutes remaining, 45 minutes of 1 hour) has been reached or that a particular time (e.g., 5 minutes, 10 minutes, 1 hour) remains before the usage limit is reached, Or any period of time), such as in fig. 8II (e.g., a notification is displayed on the device indicating that the social media category usage limit has a 5 minute remaining). In some examples, the threshold time is defined by a user. In some embodiments, the notification includes text, an image, and/or a sound. In an embodiment, the notification comprises a haptic and/or tactile output indication. In some embodiments, the notification includes a button that allows the user to dismiss the notification. In some embodiments, the electronic device stops displaying the notification after a certain amount of time. The manner in which the user is notified that the usage limit is about to be reached (e.g., a particular fraction of the usage limit (e.g., 90%, 5 minutes remaining, 45 minutes of 1 hour) has been used) described above makes the user-device interface more efficient (e.g., the user does not have to monitor time, provide the user with an opportunity to complete a task currently being performed on the device, and prompt the user to stop using the device in anticipation of the usage limit being reached, thereby reducing user-provided inputs to the device (e.g., inputs for updating the usage limit settings)), 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, the electronic device receives one or more inputs for altering one or more usage limit settings associated with the usage limit (990) (e.g., alteration of start/end times of the usage limit, alteration of a whitelist, etc.), such as in fig. 8JJJ (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 (992) to alter the one or more usage limit settings, in accordance with a determination that the one or more inputs to alter the one or more usage limit settings are received via the one or more input devices of the electronic device and 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), the electronic device requires (994) authorization (e.g., requires a user of the electronic device to enter a password in order to alter the usage limit settings) prior to performing the one or more usage limit setting alterations, such as in fig. 8jj through 8KKK (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 the time the device is initially set up). In some embodiments, if the electronic device is a child device in a home account, any usage 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 credentials 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 credential is the same as the credential used to unlock the device (e.g., a password, fingerprint authentication, and/or facial authentication used to unlock the device (e.g., for successful biometric authentication, awareness of attention via the depth camera is required)). In some embodiments, the authentication credential is different from the credential used to unlock the device (e.g., the credential of the parent in the family account). In some embodiments, the parent device is able to modify the above settings that are valid on the child device remotely (e.g., optionally by entering parent credentials at the parent device).

In some embodiments, in response to receiving the one or more inputs (992) to alter the one or more usage limit settings, in accordance with a determination that the one or more inputs to alter the one or more usage limit settings are received from outside of the electronic device via the parent device (e.g., that the alteration to the usage limit settings was 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 setting alterations (e.g., makes the alteration to the usage limit settings without requiring entry of additional credentials), such as in fig. 8 LLL-8 NNN (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 categorized 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 the time the device is initially set up). 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 usage limit setting on the child device remotely (e.g., over the internet, bluetooth, or other network or protocol). The manner in which the usage limits are set/modified here is the same as or similar to the manner in which the limited-use mode is set/modified as described with reference to method 1100. The manner in which the ability to alter the usage limit settings is limited described above allows the electronic device to effectively and selectively limit the use of certain applications during certain time periods, which reduces the use of the electronic device during those time periods, 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 an image), an audible indication, a verbal indication, and/or a tactile and/or haptic output indication) regarding the one or more usage limit setting changes (e.g., presents a notification (e.g., is a parent device in a family account, an option selected on the electronic device based on a categorization of a user account associated with the electronic device, or otherwise) that the usage limit setting was changed remotely by a parent device), such as in fig. 8NNN (e.g., displays a notification on a child device when its usage limit setting was 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 categorized 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 the time the device is initially set up). In some embodiments, if the parent device remotely modifies the above settings that are valid on the child device, the child device displays a notification of the occurrence of such remote modifications, details of the modifications (e.g., the parent device has changed the usage limit, the parent device has changed the time window during which the usage limit was valid from 10pm to 6am to 9pm to 7am, etc.). The notifications generated on the child device here are the same or similar to the notifications generated on the child device with reference to the limited use mode described in method 1100. The manner in which the usage limit settings are altered described above allows the electronic device to effectively and selectively limit the use of certain applications during certain time periods, which reduces the use of the electronic device during those time periods, 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 other than the electronic device to alter the one or more usage limit settings requires input of authentication credentials (998-2) for causing the usage limit setting alteration on the electronic device at a parent device (e.g., a parent device that is 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) (e.g., in response to receiving input of an altered usage limit setting from a device of the parent device (e.g., a device of an authorized adult), a password (e.g., a device usage limit password or other authentication credentials, optionally different from the authentication credentials used to access the parent and/or child device) is optionally required at the parent device for continuing the usage limit setting alteration), such as in fig. 8MMM (e.g., a password is required 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 categorized 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 the time the device is initially set up). The above-described methods requiring authentication credentials (e.g., password, fingerprint authentication, facial authentication) to change usage limit settings from a parent device allow an electronic device to set usage limits with 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 change the child device usage limit settings), which reduces power usage and improves the 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. One of ordinary skill in the art will recognize a variety of ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein in connection with other methods described herein (e.g.,

methods

700, 1100, 1300, and 1500) also apply in a similar manner to method 900 described above in connection with fig. 9A-9K. For example, the usage limits, usage limit settings, etc. on the electronic device described above with reference to method 900 optionally have one or more of the features of the usage limits, usage 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 conjunction with fig. 1A-1B, fig. 3, fig. 5A-5H) or an application-specific chip. Further, the operations described above with reference to fig. 9A-9K are optionally performed by the components depicted in fig. 1A-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 recognizer 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 calls data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update the content displayed by the application. Similarly, one of ordinary skill in the art will clearly know how other processes may be implemented based on the components depicted in fig. 1A-1B.

User interface with limited usage mode

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 the 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 time periods. The embodiments described below provide a way for an electronic device to effectively and selectively restrict access to certain applications during certain time periods, which reduces the use of the electronic device during those time periods without requiring the user to monitor its own usage. Limiting access to applications during certain time periods further reduces the power usage of the device and increases the battery life of the battery-powered device. It should be understood that one uses the device. When a person uses a device, the person is optionally referred to as the 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 illustrates an exemplary device 500 having a touch screen 504, such as described with reference to fig. 5A-5H. The touch screen 504 optionally displays one or more user interfaces including various content. In the example shown in fig. 10A, the touch screen 504 displays a "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 prevents or attempts to prevent access to certain applications on the device. FIG. 10A shows that the selectable device downtime setting affordance 1004 includes information about limited usage modes (e.g., the device downtime mode is automatically enabled from 10pm to 6am per day). In some embodiments, the device down time or limited use mode is a bedtime limited mode for reducing device use during user-defined bedtime hours.

The affordance 1004 is selectable to define a limited-use mode setting or rule, as will now be described. For example, in FIG. 10B, selection of the device downtime setting affordance 1004 is detected (e.g., through a tap of the contact 1003 detected on the device downtime setting affordance 1004, as shown in FIG. 10B). In response to selection of the equipment down time setting affordance 1004, the equipment 500 displays an "equipment down time" graphical user interface 1010 as shown in FIG. 10C.

Fig. 10C illustrates an exemplary limited use mode setting or rule. Device downtime screen 1010 optionally includes a switch input affordance 1011 to enable or disable implementation of limited use mode settings, a start affordance 1012 to define a start time of limited use mode, an end affordance 1013 to define an end time of limited use mode, a day affordance 1014 to define on what day the limited use mode settings are implemented, a downtime affordance 1015 to define how the limited use mode will be implemented by device 500 at the start time (e.g., under a "notify and block" or "notify" option, as described with reference to figures 8 LL-8 GGG), a talk-out affordance 1016 to enable a limited use mode alert to be spoken (e.g., read out a limited use mode alert or notification by audible voice loud), or a do-not disturb mode during the limited use mode (e.g., a pattern that silences calls and alerts that arrive while device 500 is locked) is 1017, as shown in fig. 10C. For example, closing the toggle input affordance 1011 will optionally disable implementation of the limited-use mode setting even within the times and days defined by the start affordance 1012, the end affordance 1013, and the day affordance 1014. In some embodiments, closing the toggle input affordance 1011 will save the limited use mode settings or rules defined on the device downtime screen 1010 so that these settings will be restored when the toggle input affordance 1011 is reopened.

In some embodiments, the day affordance 1014 may select to display another user interface that defines 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., through a tap 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 day the limited use mode setting is implemented. The day graphical user interface 1020 optionally includes a daily affordance 1022 for requiring each day of the week to have the same limited-use start and end times (e.g., as defined by the start affordance 1012 and the end affordance 1013 in the device downtime screen 1010, as shown in fig. 10C). In some embodiments, the day graphical user interface 1020 includes affordances 1024 a-1024 g for defining different start and end times for each day of the week (monday-sunday), respectively, as shown in fig. 10E. Enabling the daily affordance 1022 optionally inhibits the user from using the affordances 1024 a-1024 g to define different start and end times for different days of the week by disabling the affordances 1024 a-1024 g, as shown in fig. 10E. In some embodiments, device 500 visually hides affordances 1024 a-1024 g (e.g., by twisting, graying out, fading out the affordances) when daily affordance 1022 is enabled, as shown in fig. 10E. In some embodiments, device 500 relinquishes display of affordances 1024 a-1024 g when daily affordance 1022 is enabled. In some embodiments, disabling daily affordance 1022 enables a user to define different start and/or end times for different days of the week using affordances 1024 a-1024 g (e.g., allowing a 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 affordance 1022 optionally allows a user to define different limited-use mode start and end times for friday and saturday via affordances 1024e and 1024F, as shown in fig. 10F. In some embodiments, enabling the daily affordance 1022 will save on the day graphical user interface 1020 to illustrate the different start and end times defined by the affordances 1024 a-1024 g, 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 limited usage setting user interface 1002 may select to display another user interface that defines a list of applications that are not subject to the limited usage mode rules during the limited usage mode (e.g., an application usage white list). For example, in FIG. 10G, selection of the always allowed affordance 1006 is detected (e.g., through a tap of the contact 1003 detected on the always allowed affordance 1006, as shown in FIG. 10G). In response to selection of always allowed affordance 1006, device 500 displays an "always allowed" graphical user interface 1025, as shown in FIG. 10H.

As shown in fig. 10H, device 500 enables a user to add or remove applications from a list of applications that are always allowed to graphical user interface 1025 to be unconstrained during a limited use mode (e.g., application use whitelist 1026, shown in fig. 10H) by the limited use mode rules. For example, fig. 10H shows a phone application 1026a, a messaging application 1026b, and a FaceTime application 1026c on a whitelist 1026. In some embodiments, graphical user interface 1025 is always allowed to include a selectable removal affordance 1027 adjacent to certain applications listed on whitelist 1026 that, when selected by a user, causes device 500 to remove the corresponding application from whitelist 1027 (e.g., subject the particular application to the restricted usage pattern rules). In some embodiments, certain applications will be permanently on whitelist 1026. For example, FIG. 10H shows a phone application 1026a that does not have a remove affordance 1027 for removing it from the whitelist 1026-thus, the phone application 1026a for making or receiving calls on the device 500 is optionally permanently included on the whitelist 1026. In some embodiments, the graphical user interface 1025 is always allowed to indicate that the application on the whitelist 1026 is not constrained by the limited use mode rules during the limited use mode for communication with anyone, contacts saved to the device 500, or specific contacts saved on the device 500 through that particular application. For example, fig. 10H shows that communication with anyone through the phone application 1026a is unrestricted during the limited use mode, that communication through the messaging application 1026b is unrestricted for all contacts stored on the device 500 (but optionally restricted for others than the contacts stored on the device 500) during the limited use mode, and that communication through the FaceTime application 1026c is unrestricted for certain designated contacts. In some embodiments, allowing the user to alter which communications applied through the whitelist 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 illustrates a selectable add affordance 1029 adjacent to each of applications 1029 a-1029 e that enables a user to add any of applications 1029 a-1029 e to whitelist 1026. For example, fig. 10I illustrates adding "application 5" (e.g., by a tap of a contact 1003 detected on an add affordance 1029 adjacent to an application 1029 e). In response to selection of add affordance 1029 adjacent to application 1029e, application 5 is added to whitelist 1026, as shown in FIG. 10J.

In some embodiments, one or more of the

applications

1026a, 1026b, 1026c, 1026d, and 1029e may be selectable to display another user interface for altering the communication restrictions associated with those applications during the limited-use mode. For example, in FIG. 10K, selection of the phone application 1026a is detected (e.g., by a tap of the contact 1003 detected on an entry of the application 1026a in the whitelist 1026, as shown in FIG. 10K). In response to selection of an entry for the application 2016a in the whitelist 1026, the device 500 optionally displays a "phone" communication graphical user interface 1030, as shown in FIG. 10L. The telephonic communications graphical user interface 1030 optionally includes two selectable affordances for defining what communications utilizing the telephonic application are not constrained by the limited use mode rules during the limited use mode. For example, fig. 10L shows a selectable "anyone" option 1032 that, when selected, allows communication (e.g., both incoming and outgoing communications) with anyone (e.g., whether or not another party's communication information is stored on device 500) through the phone application during the limited use mode; a selectable "all contacts" option 1033 that, when selected, allows communication (e.g., both incoming and outgoing communications) with any contacts stored on device 500 through the phone application during the limited use mode; and a selectable "specify contacts" option 1034 that, when selected, allows the user to define what contacts to allow communications (e.g., incoming and outgoing communications) with through the phone application during the limited use mode, as will now be described.

In some embodiments, the designate contacts option 1034 may be selectable to display information defining what contacts are allowed to communicate with (e.g., both incoming and outgoing communications) through the phone application during the limited use mode. For example, in fig. 10L, selection of the designated contact option 1034 is detected (e.g., by a tap of the contact 1003 detected on the designated contact option 1034, as shown in fig. 10L). In response to selection of the designated contact option 1034, device 500 displays an allowed contact list 1036 that includes selectable contacts (e.g.,

contacts

1037a, 1037b, and 1037c) stored on device 500 that, when selected, define what contacts to allow communication with through the phone application during the limited-use mode, as shown in fig. 10M. In some embodiments, selection of the designated contacts option 1034 also causes the device 500 to display a selectable "add contacts" affordance 1038 that, when selected, allows the user to enter and store new contacts on the device 500, which will then be displayed as selectable contacts in the allowed contacts list 1036. For example, in fig. 10M, only communications with contacts a and B are allowed through the phone application during the limited use mode, but not with contact C (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 allowed to communicate with via a particular application during daytime hours (e.g., outside of the limited-use mode) and a nighttime allowed contact list of contacts allowed to communicate with via that same application during nighttime hours (e.g., during the limited-use mode) (e.g., as described above with reference to fig. 10M). For example, FIG. 10N illustrates detection of a selection of the phone application 1026a (e.g., by a tap of the contact 1003 detected on an entry of the application 1026a in the whitelist 1026, as shown in FIG. 10N). In response to selection of an entry for the application 2016a in the whitelist 1026, the device 500 displays a "phone" communication graphical user interface 1030, as shown in FIG. 10O.

In some embodiments, the "phone" communication graphical user interface 1030 includes a selectable 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., through a tap of the contact 1003 detected on the daytime affordance 1039a, as shown in FIG. 10P). In response to selection of the daytime affordance 1039a, device 500 displays a "daytime" graphical user interface 1040, as shown in fig. 10Q. In some embodiments, the daytime graphical user interface 1040 operates as described above with reference to fig. 10L-10M to define with a phone application during daytime hours (e.g., outside of a limited-use mode) with what contacts (e.g., anyone, all contacts, or a designated contact) communications (e.g., both incoming and outgoing communications) are allowed (e.g., to define a daytime white list). As shown in fig. 10R, selection of the night affordance 1039b is optionally detected (e.g., by a tap of the contact 1003 detected on the night affordance 1039b, as shown in fig. 10R). In response to selection of the night affordance 1039b, the device 500 displays a "night" graphical user interface 1042, as shown in fig. 10S. In some embodiments, the night graphical user interface 1042 operates as described above with reference to fig. 10L-10M to define with which contacts (e.g., any person, all contacts, or designated contacts) communications (e.g., both incoming and outgoing communications) are allowed through the phone application during the night hours (e.g., during the limited use mode) (e.g., defining a night white list). In some embodiments, the daytime and nighttime whitelists are different, as shown in fig. 10Q and 10S.

In some embodiments, the device 500 is a child device (e.g., a device designated as a user of the child, rather than a parent or administrator in a family account), as shown in fig. 10T. If the device 500 is a child device, altering one or more restriction settings on the restriction 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 restriction settings graphical user interface 1002. For example, in FIG. 10U, selection of the device downtime setting affordance 1004 is detected when the password affordance 1008 is toggled on (e.g., through a tap of a contact 1003 detected on the device downtime setting affordance 1004, as shown in FIG. 10U). In response to selection of device downtime set affordance 1004, device 500 displays password graphical user interface 1044, asking the user to enter a password before being allowed to make changes to any device downtime set, as shown in FIG. 10V. In some embodiments, password graphical user interface 1044 is not displayed by device 500 (e.g., a user of a child device is able to view the restriction settings, including device downtime and always allowed settings, without having to enter a password) until the device restriction settings are altered by the user as described above with reference to fig. 10C-10S. 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 restrictions set). In some embodiments, to make changes to the restriction 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 "family" graphical user interface 1046 in which the user is able to view family usage limits 1048 (e.g., usage limits associated with members of the family account and/or usage limits of devices associated with the family account) and make changes to those family limits (e.g., as described above with reference to fig. 6C-6D). For example, fig. 10W shows usage limits 1048 for parent account 1049a, mother account 1049b, and child account 1049 c. In some embodiments, the home settings graphical user interface 1046 is included within the restriction settings interface 1002 (e.g., as described above with reference to fig. 6C-6D).

In some embodiments, each of parent account 1049a, mother account 1049b, and child account 1049c may be selectable to display a restriction settings graphical user interface to make changes to the restriction settings associated with each of those accounts. For example, in fig. 10X, selection of child account 1049c is detected (e.g., by a tap of contact 1003 detected on child account 1049c, as shown in fig. 10X). In response to the selection of child account 1049c, device 500 displays a child restrictions settings graphical user interface 1002 associated with child account 1049c, as shown in FIG. 10Y.

In some embodiments, in order for the device 500 (e.g., a parent device) to make changes to the restriction settings associated with the child account 1049c on the child restriction settings graphical user interface 1002, the parent is required to enter a password (or provide other restriction settings authentication, such as facial recognition). For example, in FIG. 10Z, selection of the always allowed affordance 1006 is detected (e.g., through a tap of the contact 1003 detected on the always allowed affordance 1006, as shown in FIG. 10Z). In response to selection of always allowed affordance 1006, device 500 displays password graphical user interface 1044, asking the user to enter a password before being allowed to change any of the restriction settings associated with the child account, as shown in FIG. 10 AA. In some embodiments, password graphical user interface 1044 is not displayed by device 500 before the device limit settings are altered by the user, as described above with reference to fig. 10C-10S (e.g., the user of the parent device is able to view the limit settings of the 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 the child device (e.g., is a password unique to the restriction settings). In some embodiments, to make changes to the restriction settings, a biometric feature is optionally entered instead of a password (e.g., as described below in process 1100).

Fig. 10BB shows the child device 500 displaying the home screen 1050 at a time before the change to its restriction settings is remotely changed (e.g., by a parent device, as described above with reference to fig. 10W-10 AA). Fig. 10CC shows the child device 500 displaying the main screen 1050 at a time after the change to the restriction setting is remotely changed (e.g., by a parent device, as described above with reference to fig. 10A-10S and 10W-10 BB). In some embodiments, the device 500 generates a notification 1052 to indicate to the user of the child device that their device down time limit has been remotely changed, as shown in fig. 10 CC. For example, notification 1052 in fig. 10CC shows that a new contact is added to the daytime allowed contact list of device 500, and the start time of the limited use mode is changed by the parent associated with the family account (e.g., by mother, as described above with reference to fig. 10A-10Q).

Fig. 10DD shows the device 500 displaying the home screen 1050 at a time prior to the start time of the limited use mode. In fig. 10DD, the home screen 1050 includes

icons

424, 426, 416, 432, 434, 436, 440, 442, 454, 446, 450, and 452 for launching or otherwise displaying different applications on the device 500, as described above with reference to fig. 4A. Because the device is not in 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, device 500 will display an alert before the device enters the limited use mode. For example, as shown in FIG. 10EE, 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 embodiments, the notification 1054 will automatically disappear (e.g., turn off without user input) after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds).

Fig. 10FF illustrates the device 500 displaying the home screen 1050 at the beginning of the limited use mode under the "notify" option of the device downtime setting (e.g., as described above with reference to fig. 8 LL-8 PP and 10D). In some embodiments, the device 500 may be a parent device (e.g., a device associated with a parent on a family account) or a stand-alone device (e.g., a device not associated with any family account). The device 500 optionally visually hides 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 FF. 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.) other than the home screen 1050 at the beginning of the limited-use mode, and the device 500 visually hides (e.g., blurs, 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 a dismissal affordance 1057. For example, in FIG. 10FF, selection of the removal affordance 1057 is detected (e.g., by a tap of the contact 1003 detected on the removal affordance 1057, as shown in FIG. 10 FF). In response to selecting the dismiss affordance 1057, the device 500 ceases to display the dismiss affordance 1057, displays the display affordance 1058, and ignores the affordance 1059, as shown in FIG. 10 GG. In some embodiments, user selection of the delay show affordance 1058 allows the user to delay the start of the limited-use mode (without changing the actual time setting of the limited-use mode so that the limited-use mode will continue to be triggered at a previously defined time in the future) a predefined or user-defined amount of time (e.g., 5 minutes, 15 minutes, 30 minutes) to extend the start of the limited-use mode (e.g., as described below with reference to method 1100). In some embodiments, the user selecting ignore affordance 1059 allows the user to abort the start of the limited-use mode for that particular day (without changing the actual time setting of the limited-use mode so that the limited-use mode will continue to be triggered at the previously defined time in the future) (e.g., as described below with reference to method 1100). In some embodiments, the device 500 stops displaying the delayed 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 main screen 1050 (except for the interpretation 1056, the delayed affordance 1058, and the ignore affordance 1059). Under the "notification option," the parent device (e.g., the device associated with the parent on the family account) or a stand-alone device (e.g., the device not associated with any family account) does not require the user to enter any authentication (e.g., a password) to extend or ignore the restricted usage pattern on the device. For example, fig. 10HH shows the parent device 500 displaying the home screen 1050 after the user selects either the extension affordance 1058 or the ignore affordance 1059 under "notification option". Because the device 500 in fig. 10HH 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. Extending or ignoring the initiation of the limited use mode optionally enables any application to be launched or any application functionality to be performed, which may otherwise have been limited (e.g., accessing a desktop applet or website associated with those applications, receiving a notification, recommending those applications to a user, etc.).

Fig. 10II shows 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 setting (e.g., as described above with reference to fig. 8 QQ-8 GGG and 10D). In some embodiments, the device 500 may be a parent device (e.g., a device associated with a parent on a family account) or a stand-alone device (e.g., a device not associated with any family account). The device 500 optionally visually hides 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 II. 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.) other than the home screen 1050 at the beginning of the limited-use mode, and the device 500 visually hides (e.g., blurs, 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 a dismissal affordance 1057. For example, in FIG. 10II, selection of the remove affordance 1057 is detected (e.g., by a tap of the contact 1003 detected on the remove affordance 1057, as shown in FIG. 10 II). In response to selecting the dismiss affordance 1057, device 500 stops displaying dismiss affordance 1057 and displays deferred affordance 1058 and ignore affordance 1059, as shown in FIG. 10 JJ. In some embodiments, user selection of the delay show affordance 1058 allows the user to delay the start of the limited-use mode (without changing the actual time setting of the limited-use mode so that the limited-use mode will continue to be triggered at a previously defined time in the future) a predefined or user-defined amount of time (e.g., 5 minutes, 15 minutes, 30 minutes) to extend the start of the limited-use mode (e.g., as described below with reference to method 1100). In some embodiments, the user selecting ignore affordance 1059 allows the user to abort the start of the limited-use mode for that particular day (without changing the actual time setting of the limited-use mode so that the limited-use mode will continue to be triggered at the previously defined time in the future) (e.g., as described below with reference to method 1100). In some embodiments, the device 500 stops displaying the delayed 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 main screen 1050 (except for the interpretation 1056, the delayed 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 family account) or a stand-alone device (e.g., a device not associated with any family account) optionally requires the user to enter authentication (e.g., a password) to extend or ignore the restricted usage pattern on the device. For example, in response to a selection of the deferred presentation affordance 1058 or the ignore affordance 1059 in FIG. 10JJ under "notify and block options," device 500 displays a password graphical user interface 1044 asking the user to enter a password before the limited-use mode can be extended or ignored, as shown in FIG. 10 KK. In some embodiments, the password required at fig. 10KK 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 restrictions set). In some embodiments, to make changes to the restriction settings, a biometric feature is entered instead of a password (e.g., as described below in process 1100).

Fig. 10LL illustrates device 500 displaying home screen 1050 after the user enters the correct password in password graphical user interface 1044 of fig. 10KK under "notify and block option". Because device 500 in fig. 10LL 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 initiation 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. 10MM shows that the child device 500 displays the main 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 hides the primary screen 1050 (e.g., blurs, grays out, or visually changes the primary screen) at the beginning of the limited use mode, as shown in fig. 10 MM. 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.) other than the home screen 1050 at the beginning of the limited use mode, and the child device 500 visually hides (e.g., blurs, 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 a dismissal affordance 1057. For example, in FIG. 10MM, selection of the dismissal affordance 1057 is detected (e.g., by a tap of the contact 1003 detected on the dismissal affordance 1057, as shown in FIG. 10 MM). In response to selecting the dismissal affordance 1057, the device 500 stops displaying the dismissal affordance 1057 and displays a selectable affordance 1060 for requesting more time on the device 500 (e.g., extending a 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), as illustrated in fig. 10NN (e.g., as described above with reference to fig. 8 TT-8 CCC). In some embodiments, selecting either affordance 1060 or affordance 1062 allows a parent to delay the start of the limited-use mode without changing the actual time setting of the limited-use mode so that the limited-use mode will continue to be triggered at a previously defined time in the future. For example, in FIG. 10OO, selection of an affordance 1062 is detected (e.g., by a tap of a contact 1003 detected on the affordance 1062, as shown in FIG. 10 OO). 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. 8 WW-8 CCC). For example, the 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 (e.g., affordance 1068a) for rejecting the request, affordances (e.g.,

affordances

1068b and 1068c) for extending the start time of the limited-use mode for a predetermined period of time, and affordances (e.g., affordance 1068d) for custom extending the period of time (e.g., as described above with reference to fig. 8 AAA-8 CCC), as shown in fig. 10 PP. In some embodiments, the process for requesting more time on another device sends a notification 1066 with an affordance (e.g., affordance 1068a) for rejecting the request, an affordance (e.g.,

affordances

1068b and 1068c) for extending the start time of the limited-use mode for a predetermined period of time, and an affordance (e.g., affordance 1068d) for customizing the extended period of time, as shown in fig. 10 QQ.

Fig. 10RR shows the device 500 displaying the main screen 1050 at a time before the start time of the limited use mode. In fig. 10RR, the home screen 1050 includes

icons

424, 426, 416, 432, 434, 436, 440, 442, 454, 446, 450, and 452 for launching or otherwise displaying different applications on the device 500, as described above with reference to fig. 4A. Because the device is not in a limited use mode, the user is able to launch any application associated with

icons

Fig. 10SS shows the touch screen 504 displaying the main screen 1050 during the limited use mode. In some embodiments, device 500 prevents or attempts to prevent access to all applications on the device during the limited use mode except for applications included on the application usage white list. In some embodiments, icons corresponding to restricted applications (e.g., applications that are restricted during the restricted use mode that are not on the application use white list) are changed during the restricted use mode. For example,

icons

424, 432, 436, 442, 454, 450, and 452 correspond to restricted applications and are hidden (e.g., distorted, grayed out, faded out, and/or visually changed) during the restricted usage mode, as shown in fig. 10 SS. In some embodiments, a placeholder generic indication (e.g., a lock icon) 1070 is placed on or partially on the icon corresponding to the restricted application, as shown in fig. 10 SS. A placeholder generic indication (e.g., a lock icon) 1070 optionally replaces any unread notification indication corresponding to the restricted application (e.g., as shown in fig. 10 SS). In some embodiments, a placeholder generic indicator (e.g., a lock icon) is placed on or near text associated with an application icon for a restricted application (e.g., next to the name of the application).

In some embodiments, the icons displayed on the home screen 1050 may 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, 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 FF). For example, under the "notify" option, a user of device 500 (e.g., a parent device or stand-alone device) is optionally able to select an icon corresponding to a restricted application during the restricted use mode. For example, in fig. 10TT, selection of an icon 424 (corresponding to the restricted message application) is detected (e.g., by a tap of a contact 1003 detected on the icon 424, as shown in fig. 10 TT). In response to selecting the icon 424, the device 500 optionally visually hides the home screen 1050 (e.g., blurs, grays, or visually changes the home screen) as shown in fig. 10 UU. In some embodiments, the device 500 displays an interpretation 1056 indicating that access to the messaging application is restricted during the restricted use mode and a dismissal affordance 1057. For example, in fig. 10UU, selection of the remove affordance 1057 is detected (e.g., by a tap of the contact 1003 detected on the remove affordance 1057, as shown in fig. 10 UU). In response to selecting the remove affordance 1057, the device 500 stops displaying the remove affordance 1057 and displays the render affordance 1072, as shown in fig. 10 VV. In some embodiments, selection of the affordance 1072 by the user allows the user to access a limited messaging application (e.g., as described below with reference to method 1100) during a limited use mode, as illustrated by the WW of fig. 10. In some embodiments, the device 500 stops displaying the presentation affordance 1072 after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds) or when the user taps any portion of the main screen 1050 (in addition to the interpretation 1056 and the presentation 1072).

The device 500 (e.g., a parent or stand-alone device) attempts to prevent 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 II-10 LL). 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 the restricted use mode. For example, in FIG. 10XX, selection of the icon 424 (corresponding to the restricted message application) is detected (e.g., by a tap of the contact 1003 detected on the icon 424, as shown in FIG. 10 XX). In response to selecting icon 424, device 500 optionally visually hides home screen 1050 (e.g., blurs, grays, or visually changes the home screen) and displays password graphical user interface 1044, requiring the user to enter a password to access the limited message application during the limited use mode, as shown in fig. 10 YY. In some embodiments, the password required at YY of fig. 10 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 restrictions set). In some embodiments, to make changes to the restriction 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 prevent access to restricted applications during the restricted use mode. In some embodiments, a user of the child device 500 is able to select an icon corresponding to a restricted application during a restricted use mode. For example, in fig. 10ZZ, selection of icon 424 (corresponding to a restricted messaging application) is detected (e.g., by a tap of contact 1003 detected on icon 424, as shown in fig. 10 ZZ). In response to selecting the icon 424, the child device 500 optionally visually hides (e.g., blurs, grays out, or visually changes) the home screen 1050 and displays selectable affordances 1082 for requesting access to the message application during the limited-use mode on the child device 500 (e.g., by requiring the parent to enter a password directly on the device 500) and selectable affordances 1084 (e.g., as described above with reference to fig. 8 TT-8 CCC and 10 NN-10 QQ) 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), as shown in fig. 10 AAA.

11A-11I are flow diagrams illustrating a method 100 of selectively restricting access to applications on an electronic device during a limited use mode according to some embodiments of the present disclosure. Method 1100 is optionally performed on an electronic device (such as device 100, device 300, or device 500) as described above in connection with fig. 1A-1B, 2-3, 4A-4B, and 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 restrict access to applications on an electronic device during a limited use mode. The method reduces the usage of the electronic device during a particular time period without requiring the user to monitor their own usage. For battery-driven electronic devices, limiting access to applications during a particular time period conserves power and increases the time between battery charges.

In some embodiments, an electronic device (e.g., a mobile phone, a 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 a tablet including one or more of a keyboard, a mouse, a touchpad, and a touch screen, such as touch screen 504, a wearable device, such as a smart watch including a touch screen, or a set-top box in communication with a television and an input device (e.g., a remote 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 restricted usage modes 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 family or other group account). For example, a user of the electronic device defines a bedtime limited use mode as a few hours of the day (e.g., 10pm to 5am) during which the electronic device prevents or attempts to prevent access to all applications on the electronic device, except for applications included on the application white list in some embodiments. In some embodiments, the user defines the time window and does not specify any particular application to which access is to be restricted. In such embodiments, the electronic device optionally defaults to limiting or attempting to limit the use of all applications except the whitelist application during the limited use mode.

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 to initiate a first application of the plurality of applications installed on the electronic device (e.g., input to open and/or use the application on the electronic device or input to continue using 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 TT. In some embodiments, in response to receiving the input to launch the first application (1108), in accordance with a determination that the first application is not included in an application usage whitelist (e.g., a list of applications that are not restricted from restricted access during the restricted usage mode (e.g., can be fully or partially accessed during the bedtime restricted usage mode)), the electronic device restricts (1110) access to the first application (e.g., prohibits application launch, restricts functionality of the application, or requires further action by the 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-10 AAA. In some embodiments, in response to receiving the input to launch the first application (1112), in accordance with a determination that the first application is included in the application usage whitelist, the electronic device provides access to the first application (e.g., launches the application normally as if the limited-use mode is not active), 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 remotely set by a user of another electronic device in communication with the electronic device. In some embodiments, when the application is launched outside of the bedtime limited use mode, no bedtime use limitation occurs (e.g., the application launches normally as if the limited use mode was not active). In some embodiments, 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 phone application is optionally on a white list for communicating with a particular contact (e.g., a relative), and the phone application is launched, restricting communications with other contacts. In some embodiments, the electronic device enters the limited-use mode while a limited application (e.g., an application that is not on the application-use white list) is running, and the limited application is associated with a "notify" or "block and notify" limitation option (e.g., as described in more detail below). For example, under the "notify" restriction option, the electronic device displays a pop-up indication (e.g., masking the display of the running application) on the running application indicating that application usage is currently restricted (e.g., due to bedtime restrictions being in effect), 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" restriction 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 restricted (e.g., due to bedtime restrictions being valid), and that the indication requires authentication credentials (e.g., a password, biometric feature, or consent from the parent device/account) to continue using the application. Detecting the biometric feature optionally includes detecting a face of the user with a depth camera or another sensor. The limited-use mode described herein is optionally the same as or similar to the limited-use mode described with reference to

methods

700, 900, and 1300. The above-described manner of selectively restricting access to applications during a bedtime limited use mode allows the electronic device to effectively and selectively restrict use of certain applications during certain time periods, which reduces use of the electronic device during those time periods, which in turn reduces power consumption and improves battery life of the device.

In some embodiments, the one or more time windows associated with a limited-use mode (e.g., a bedtime limited-use mode) are a first one or more time windows (1114) on a first day of the week, and the one or more time windows associated with a limited-use mode are a second one or more time windows (e.g., different days can have different settings (times, usage limits, etc.) for the limited-use mode that are different from the first one or more time windows) on a second day of the week that is different from the first day of the week (e.g., different days can have different settings (times, usage limits, etc.) for the limited-use mode, such as in fig. 10F. for example, the times of the bedtime limited-use mode during which the electronic device prevents or attempts to prevent access to certain applications on the electronic device are defined differently for different days of the week (e.g., 10pm to 5am on monday, 11pm to 6am on saturday, weekdays from 9pm to 5am, weekends from 11pm to 7 am). The manner in which the different times of the bedtime limited use mode are defined for different days of the week described above makes the user-device interface more efficient (e.g., the user does not have to update the time of the bedtime limited use mode on a daily basis, thus reducing user input provided to the device (e.g., input for updating the time of the bedtime limited use mode)), 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, in accordance with a determination that the current time on the electronic device is a threshold time before the one or more time windows associated with the limited-use mode (e.g., 5 minutes, 10 minutes, 1 hour, or any period of time before the limited-use mode begins) when 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., the bedtime limited-use mode) will take effect within the threshold time (e.g., 5 minutes, 10 minutes, 1 hour, or any period of time)), such as in fig. 10 EE. In some examples, the threshold time is defined by a user. In some embodiments, the notification includes text, an image, and/or a sound. In an embodiment, the notification comprises a haptic and/or tactile output indication. The manner in which the user is notified that the limited-use mode will soon take effect described above makes the user-device interface more efficient (e.g., the user does not have to monitor time, provide the user with an opportunity to complete a task currently being performed on the device, and prompt the user to discontinue use of 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 usage of the electronic device, which in turn reduces power consumption and improves the battery life of the device.

In some embodiments, the indication of the approach of the one or more time windows associated with the limited-use mode comprises a visual indication (1120), and the visual indication comprises 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 the start 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 FIGS. 10EE through 10QQ, hi some embodiments, the affordance comprises a predefined amount of time (e.g., 5 minutes, 15 minutes, 30 minutes) for extending the start of the limited-use mode. Manually entering another start time). In some embodiments, the electronic device allows the user to delay the start of the limited use mode any time until and including the start of the limited use mode (e.g., allowing the user to eliminate the limited use mode for a period of time or for the remainder of the day). Delaying the start of the limited-use mode optionally enables any application to be launched or any application function to be executed 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.). 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 the adult/parent device in the home account for extending the limited-use mode (e.g., extending the beginning of the limited-use mode by 15 minutes, 30 minutes, 1 hour, etc.). In this case, selecting the request in the notification optionally results in the notification being delivered to one or more (or all) parent devices associated with the family 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 a user to prevent the electronic device from entering a limited-use mode. In some embodiments, application usage beyond the allowed limit (e.g., even if approved due to time stretching) is optionally indicated in the dashboard user interface described above with reference to method 700 (e.g., as shown in fig. 6L-6P, 6 EE-6 HH, 6 OO-6 SS, and 6 UU). The manner in which the affordances for the user to extend the start of the limited-use mode described above makes the user-device interface more efficient (e.g., the user does not have to monitor time, provide the user with an opportunity to extend the start time of the limited-use mode to complete a task currently being performed on the device, and prompt 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 usage of the electronic device, which in turn reduces power consumption and improves battery life of the device.

In some embodiments, one or more application icons associated with applications not included on the application white list are displayed 1122 with a first visual characteristic outside of the one or more time windows associated with the limited use mode (e.g., icons of applications not included on the application white list are normally displayed outside of the limited use mode, such as in terms of color, not grayed out, etc.), such as in FIG. 10RR, and the one or more application icons associated with applications not included on the application white list are displayed 1124 with a second visual characteristic different from the first visual characteristic during the one or more time windows associated with the limited use mode (e.g., icons of applications not included on the application white list are displayed differently during the limited use mode than when outside of the limited use mode), such as in fig. 10 SS. For example, for those applications not included on the application whitelist, the icons of those applications are optionally changed to be grayed out (compared to a color outside of the limited use mode) in the limited use mode and/or a placeholder generic indicator is displayed on the icons of those applications (or partially on any portion of the icons of those applications) in the limited use mode. In some embodiments, a placeholder generic indicator (e.g., a lock icon) is placed on or near the 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 label covering a portion of the icon indicating the number of unread notifications received 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, replaced with placeholder generic indications (e.g., lock icons), or otherwise changed such that the notification status (e.g., 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 white list are displayed with a lock icon (in embodiments where the application icon in the past included a visual indication of the application's notification, the lock icon replaces the notification indication). In some embodiments, the icons of the applications on the application whitelist are displayed the same both during and outside of the limited use mode (e.g., in terms of color, not grayed out, freely accessible, etc.). The manner in which the applications that are restricted during the limited use mode are variously displayed described above allows a user to determine which applications are restricted, which allows the electronic device to effectively and selectively restrict use of particular applications during certain time periods by providing an indication of what applications the user has or does not have access rights to during the limited use mode, which reduces use of the electronic device during those time periods, which in turn reduces power consumption and improves 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 a 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 UU. 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. 10UU through fig. 10 VV. In some embodiments, different applications are associated with different restriction options that are active during the restricted use mode. For example, the electronic device optionally allows one or more applications to be associated with a "notification" restriction option. If the user attempts to launch an application associated with a "notification" restriction (e.g., by selecting an icon for the application from a home screen of the electronic device during the limited 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 active). The pop-up notification optionally includes one or more affordances that, when selected, allow the user to proceed to the application without entering any authorization credentials (e.g., an "ignore for the day" affordance that opens the application without entering an administrator or other credential). The manner described above of notifying the user that the application is restricted during the limited use mode, but giving the user the option of accessing the application when needed, allows the electronic device to effectively limit the use of certain applications during certain time periods while allowing the user to perform the necessary tasks on the electronic device, which reduces the use of the electronic device during those time periods, 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 UU. Optionally, the indication includes (1132) an affordance selectable to provide access to the first application when authentication credentials are required (e.g., display a visual indication on a display, play a sound with a speaker associated with the electronic device, generate a haptic and/or tactile output, etc., indicating that the application is restricted (e.g., a notification)), such as in fig. 10 VV. In some embodiments, the electronic device allows one or more applications to be associated with a notify and block restriction option. If the user attempts to launch an application associated with the "notify and block" restriction (e.g., by selecting an icon for the application from a home screen of the electronic device during the limited 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 active). In some embodiments, the pop-up indication requires authentication credentials (e.g., password, biometric feature, or consent from the parent device/account) to access the application. Detecting the biometric feature 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, selecting the request in the notification optionally results in the notification being delivered to one or more (or all) parent devices associated with the family account, and the electronic device allows access to the application when permission is granted (e.g., at least one of the parent devices or a password at a child device). In some embodiments, a parent is required to enter a password at the parent device to allow access to restricted applications on the child device from the parent device. The manner in which the application is blocked from starting during the limited use mode and the user is notified that the application is limited as described above allows the electronic device to effectively limit the use of certain applications during certain time periods, which reduces the use of the electronic device during those time periods, 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 family account (e.g., is a parent device in a family account), or is not associated with a family account at all), selecting the affordance causes (1134) a request to enter a password to access the first application, such as in YY of fig. 10. 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 a 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 the parent device in a setting of the device (e.g., set at the time the device is initially set). In some embodiments, the request to enter a password is a pop-up notification, optionally including one or more affordances that, when selected, only allow the user to continue to the application if the correct authentication credentials (e.g., password, biometric feature, or consent from the parent device/account) are provided. Detecting the biometric feature 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 the home account (e.g., is a parent device in the home account) or is not associated with the home account at all, the electronic device optionally requests the user to enter credentials (e.g., a user id and/or password, password) for a user account associated with the electronic device (e.g., a user id and/or password associated with a profile to configure the device). In some embodiments, the credentials (e.g., user id and/or password, password) are different from the credentials used to access the electronic device (e.g., a password different from a password used to "unlock" the device and/or log in to the device). As such, a user (e.g., a child) that is not the owner (e.g., parent) of the device will not be able to bypass the limited use mode if the auxiliary password is not 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 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 the parent device in a home account), such as in fig. 10 MM-10 QQ. 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 the time the device is initially set up). 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 would then 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 access to the restricted application from the child device. 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 a first application. In some implementations, the password is a parental control password or a use password that is different from the password used to unlock the electronic device. In this way, 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, a parent is required to enter a password at the parent device to allow access to restricted applications on the child device from the parent device. The manner in which the user is notified of the options that the application is restricted during the limited use mode, but that the user is able to access the application when needed, described above, allows the electronic device to effectively limit the use of certain applications during certain time periods while allowing the user to perform the necessary tasks on the electronic device, which reduces the use of the electronic device during those time periods, 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 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 turning on or off 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, the implementation of a restricted usage pattern rule that closes usage restrictions defined during the hours of 10pm to 7am (e.g., one or more time windows associated with the restricted usage pattern) disables those usage restrictions during the hours of 10pm to 7am (e.g., during vacation). Conversely, an implementation that turns on the same restricted usage pattern rules enables those usage restrictions during the hours of 10pm to 7 am. In some embodiments, the enforcement of the limited-use mode rules may be switched on or off during or outside of the one or more time windows associated with the limited-use mode (e.g., to control 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 limited-use mode during the one or more time windows associated with the limited-use mode). In some embodiments, the electronic device stores the usage restriction settings (e.g., user-defined start time, end time, white list, etc.) when the implementation of the limited-use mode is turned off, such that the usage restriction settings are maintained for the next time the limited-use mode is turned on. For example, when enforcement of the limited-use mode rules is turned back on (after having been turned off), the electronic device optionally enforces limited-use mode restrictions according to the same limited-use mode rules that have been set before the limited-use mode was turned off (e.g., when the limited-use mode is turned back on, the limited-use mode is enforced during the several hours of 10pm to 7 am). In some embodiments, in accordance with a determination that the enforcement of the one or more limited use mode restrictions has been opened, the electronic device enforces (1140) the one or more limited use mode restrictions (e.g., operating the electronic device outside of or in a limited use mode (in accordance with limited use mode rules)), such as in fig. 10C. For example, during the limited use mode, the electronic device operates to disable 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 proceed to the application when the user attempts to launch the limited application. In some embodiments, access is provided to the first application under certain restrictions (e.g., the application may be launched during a bedtime limited mode, but with limited functionality). For example, the phone application is optionally on a white list for communicating with a particular contact (e.g., a relative), and the phone application is launched, restricting communications with other contacts.

In some embodiments, in accordance with a determination that the enforcement of the one or more limited use mode restrictions has been turned off, the electronic device forgoes (1142) enforcement of the one or more limited use mode restrictions (e.g., operates the electronic device outside of the limited use mode whenever the enforcement of the limited use mode has been turned off, regardless of whether a current state (e.g., a current time) of the electronic device would otherwise have caused the device to operate in the limited use mode), such as in fig. 10C and 10 HH. For example, outside of the limited-use mode, the electronic device allows normal launching of applications as if the limited-use mode was not active. In some embodiments, when the application is launched outside of the bedtime limited use mode, no bedtime use limitation occurs (e.g., the application launches normally as if the limited use mode was not active). 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 limited-use mode is turned off while the current time is within the one or more limited-use time windows, the restrictions associated with the limited-use mode are not enforced. The manner described above that allows a user to manually enforce or not enforce the restricted usage pattern rules allows the electronic device to customize the enforcement of the restricted usage patterns as desired by the user, which selectively reduces usage of the electronic device, which in turn reduces power consumption and improves battery life of the device.

In some embodiments, restricting access to the first application includes presenting (1144) one or more verbal indications that access to the first application is restricted (e.g., an audible voice indicates a verbal notification that access to the application is restricted, in some embodiments in addition to the visual notification described above). In some embodiments, the electronic device performs the verbal notification only in accordance with the determination that the limited-use indication is to be spoken (e.g., based on a designation of a user account associated with the electronic device or based on electronic device settings). For example, the electronic device optionally provides an option that the user can select or not select for audibly providing (or not providing) the notification in addition to or instead of visually providing. In some embodiments, the electronic device optionally does not perform the verbal notification (e.g., displays the notification without audible voice indication that access to the application is limited) in accordance with a determination that the limited-use indication will not be spoken. In some embodiments, the notification optionally includes a sound (e.g., a ringtone, an alert, music, etc.) without a voice-read notification. In some embodiments, any of the notifications described herein can be audibly generated by the electronic device (e.g., read to a user of the electronic device), for example, to facilitate providing such notifications to a user (e.g., a child) who is unable to read or see. The manner in which audible notifications are provided when access to applications is restricted during the limited use mode described above allows the electronic device to effectively limit the use of certain applications while in the limited use mode, while optionally not displaying additional information, which reduces power consumption and improves the 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 an application usage white list (e.g., access to the telephony application is not restricted during the restricted use mode). In some embodiments, the electronic device has telephony functionality (e.g., is capable of making phone calls, receiving phone calls, etc.) implemented with a phone application installed on the electronic device (e.g., in the same manner that other applications such as a messaging application, an email application, a video application, etc. are installed on the electronic device), such as in fig. 10H. In such embodiments, the phone application is optionally always (e.g., permanently) included in the white list of applications, such that limited use mode restrictions do not apply to the phone application. Thus, the user is optionally able to use the phone application normally, whether or not the limited use mode is active. In some embodiments, the phone application is permanently included in the application usage white list only for certain designated contacts (e.g., the phone application is free to contact only certain contacts), and communication with other contacts using the phone application can be limited. The manner in which access to the phone application is allowed while restricting access to other applications during the restricted use mode described above allows the electronic device to effectively restrict the use of certain communication applications while in the restricted use mode, which reduces power consumption and improves the battery life of the device.

In some embodiments, communication operations (e.g., phone call, text message, email, and/or video conference operations) using the phone application are permissible to anyone (e.g., communication operations are not restricted to any particular contact during the limited use mode) or are permissible only to one or more designated contacts of the plurality of contacts on the electronic device (e.g., communication is restricted to contacts stored on the electronic device, contacts in a designated group of contacts on the electronic device, or contacts on a whitelist during the limited use mode) while 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 (e.g., during the limited use mode), such as in fig. 10J-10M. In some embodiments, the contacts with which the phone application can communicate without limitation can be defined at the electronic device. For example, the electronic device optionally provides settings (e.g., "anyone" settings) for allowing the phone application to communicate without limitation with all contacts (e.g., "anyone" settings) or a specified subset of contacts (e.g., place a call thereto, receive a call therefrom, etc.) during the limited-use mode-in some embodiments, the electronic device provides a user interface that only allows the phone application to communicate without limitation with selected individuals (e.g., only contacts on the electronic device, or certain contacts on the electronic device) during the limited-use mode. Communication with other individuals is optionally restricted in the manner previously described (e.g., not allowed without user id/password, biometric feature, or permission from a parent device, etc.). The manner described above that allows a user to selectively limit access to communication operations with certain contacts during a limited use mode allows the electronic device to effectively limit the use of certain communication applications while in the limited use mode, which reduces power consumption and improves the battery life of the device.

In some embodiments, the communication operations include (1150) incoming and outgoing communications (e.g., outgoing and/or incoming phone 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 anyone not designated for communicating during the limited use mode. The manner described above that allows a user to selectively limit access to communication operations with certain contacts during a limited use mode allows the electronic device to effectively limit the use of certain communication applications while in the limited use mode, which reduces power consumption and improves the 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 CC. 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 the communication limit is set to the 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 "family" or "family share" account) (1156), such as in fig. 10W. In some embodiments, the other electronic device is a device of a parent in the family account. In such embodiments, the parent device can 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 via a selection of the "share with child device" affordance on the parent device (e.g., without specifying the child's contact information or specifying the target device to which the contact information is to be sent). In some embodiments, the parent is required to enter a password at the parent device to transmit and store the contact information on the child device. The manner described above that allows a user to selectively limit access to communication operations with certain contacts during a limited use mode allows the electronic device to effectively limit the use of certain communication applications while in the limited use mode, which reduces power consumption and improves the battery life of the device.

In some embodiments, the contacts of 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 allowed during the limited use mode) are customized (1158) (e.g., contacts can be added to or deleted from a contacts whitelist (e.g., contacts whose communication operations are not restricted during the limited use mode)), such as in fig. 10M. In some embodiments, the particular contacts that are included or not included on the contacts 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 communications with those contacts are unrestricted during the limited use mode (e.g., communications with other contacts or individuals are optionally restricted during the limited use mode). In some embodiments, these "unrestricted" contacts are defined at the electronic device itself (e.g., within a settings user interface of the electronic device itself). In some embodiments, these "unrestricted" contacts are restricted at another device (e.g., at a parent device in the family account of a child device 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 an "unrestricted" contact on the child device from the parent device. The manner described above that allows a user to selectively limit access to communication operations with certain contacts during a limited use mode allows the electronic device to effectively limit the use of certain communication applications while in the limited use mode, which reduces power consumption and improves the battery life of the device.

In some embodiments, the one or more designated contacts of the plurality of contacts with which communication operations are permitted on the electronic device during the one or more time windows associated with the limited-use mode (e.g., during a limited-use mode (e.g., a bedtime mode)) are different from (1160) 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., an daytime contact white list during which communication is not restricted), such as in fig. 10O-10S. In some embodiments, the daytime contact whitelist is different from the nighttime contact whitelist (e.g., contacts whose communication operations are not restricted during the limited use mode). For example, if the limited use mode is set 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 restricted 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., the contacts optionally overlap in both whitelists). In some embodiments, the daytime contact white list is the same as the nighttime contact white list. In some embodiments, communication operations with contacts that are not on the daytime contact white list are restricted outside of the restricted use mode. In some embodiments, the parent can set or update a daytime and/or nighttime contact white list from the parent device. In some embodiments, a parent is required to enter a password at the parent device to set or update a daytime and/or nighttime contact white list on a child device from the parent device. The manner described above that allows a user to selectively restrict access to communication operations with certain contacts during and outside of the limited use mode allows the electronic device to effectively restrict the use of certain communication applications while in the limited use mode, which reduces power consumption and improves the battery life of the device.

In some embodiments, the electronic device receives (1162), via the one or more input devices, input to add 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 usage whitelist when and during the one or more time windows associated with the limited usage mode are defined, the electronic device provides (1164) access to the second application (e.g., adds the application to a list of applications that are not restricted during the limited usage mode), such as in fig. 10J. In some embodiments, any application installed on the electronic device can be added to the application white list, 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, a parent is required to enter a password at the parent device to set or update an application whitelist on a child device from the parent-parent device. The manner described above in which the user is allowed to selectively restrict access to certain applications during the limited use mode allows the electronic device to effectively restrict the use of certain communication applications while in the limited use mode, which reduces power consumption and improves the battery life of the device.

In some embodiments, the electronic device receives (1166) one or more inputs (e.g., changes to start/end times of limited use modes, changes to whitelists, etc.) for changing one or more limited use mode settings associated with a limited use mode, such as in fig. 10F. In response to receiving the one or more inputs for altering the one or more limited-use mode settings (1168), in accordance with a determination that the one or more inputs for altering 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 alter the limited-use mode) prior to performing the one or more limited-use mode setting alterations, such as in fig. 10T-10V. For example, determining that the one or more inputs for altering the one or more limited use mode settings are received at the 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 for altering the one or more limited use mode settings are received at a child device is optionally based on determining that the electronic device is set to the child device in the settings of the device (e.g., set at the time the device was initially set). In some embodiments, if the electronic device is a child device in a home account, any of the 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 permitted). In some embodiments, the authentication credential is the same as the credential used to unlock the device (e.g., the password used to unlock the device). In some embodiments, the authentication credential is different from the credential used to unlock the device (e.g., the credential of the parent in the family account). In some embodiments, the parent device is able to modify the above settings that are valid on the child device remotely (e.g., optionally by entering parent 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 for altering the one or more limited use mode settings (1168), in accordance with a determination that the one or more inputs for altering the one or more limited use mode settings are received via the parent device from outside of the electronic device (e.g., the alteration to limited use mode is made on the parent device), the electronic device performs (1172) the one or more limited use mode setting alterations (e.g., the alteration to limited use mode is made without requiring input of additional credentials), such as in fig. 10X-10 CC. 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 to the parent device in a setting of the device (e.g., set at the time the device is initially set). 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 changes to the limited-use mode settings on the child device remotely (e.g., over the internet, bluetooth, or other network or protocol). In some embodiments, a parent is required to enter a password at a parent device to remotely change the limited use mode setting on a child device. The manner in which the ability to alter the limited use mode settings described above is limited allows the electronic device to effectively and selectively limit the use of certain applications during certain time periods, which reduces the use of the electronic device during those time periods, 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 an 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 changes (e.g., presents a notification that the limited use mode settings were remotely changed by the parent device), such as in fig. 10 CC. 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 of the occurrence of such remote modifications, details of the modifications (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 in which the limited use mode settings are altered described above allows the electronic device to effectively and selectively limit the use of certain applications during certain time periods, which reduces the use of the electronic device during those time periods, which in turn reduces power consumption and improves the battery life of the device.

In some embodiments, the electronic device displays (1176), outside the one or more time windows associated with the limited-use mode, one or more representations of applications installed on the electronic device (e.g., an icon, a desktop applet, a window of the first application in a multitasking view along with other windows of other applications), such as in fig. 10 RR. For example, the electronic device displays one or more application windows associated with one or more applications (e.g., in a multitasking 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, 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 not included in an application usage whitelist (e.g., a list of applications that are not subject to limited access restrictions during the limited use mode (e.g., can be fully or partially accessed during the limited use mode)), the electronic device displays (1180) a first representation (e.g., an instance) having the first application with a second visual characteristic different from the first visual characteristic (1180) E.g., the appearance of a representation of an application that is not on the application white list is different from the appearance of a representation of an application that is not on the application white list), such as in 10SS in the figure. In some embodiments, during the limited notification mode, the electronic device modifies the appearance of aspects of the application that are not included in the application whitelist. For example, icons of applications not included in the white list (e.g., icons on the home screen of the device) are shaded during the limited use mode, and/or a placeholder generic indicator is displayed over icons of those applications (or partially over any portion of icons of those applications) in the limited use mode, as previously described. In some embodiments, a placeholder generic indicator (e.g., a lock icon) is placed on or near the text associated with the application icon. As another example, notification identifiers included on application icons for applications not included in the application white list are optionally modified, as described above. As another example, in some embodiments, the electronic device has multitasking capabilities, where the electronic device optionally displays a user interface that simultaneously displays visual representations of more than one application (e.g., simultaneously displays icons from multiple applications, a user interface that simultaneously displays screenshots of the current user interface of multiple applications, multiple application windows of different applications are presented simultaneously, etc.). In some embodiments, during the limited use mode, 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 representations corresponding to applications included in the application whitelist) by the electronic device. In some embodiments, in accordance with a determination that the first application is included in the application usage whitelist during the one or more time windows associated with the limited usage mode (1178) (e.g., in response to a start of the one or more time windows associated with the limited usage mode), the electronic device displays (1182) a first representation of the first application with a first visual characteristic (e.g., an appearance of the representation of the application included in the application whitelist continues to be displayed with the same visual characteristic during the limited usage mode), such as in fig. 10 SS. The above-described manner of selectively changing the appearance of representations of applications that are 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 time periods by providing an indication of what applications the user has or does not have access rights to during the limited use mode, which reduces the use of the electronic device during those time periods, 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 (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 with a visual indication of a lock or some other limitation symbol added to the application icons, 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 SS. In some embodiments, a restriction symbol (e.g., a lock icon) is placed on or near the text associated with the restricted 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 label covering a portion of the icon indicating the number of unread notifications received 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, replaced with placeholder generic indications (e.g., lock icons), or otherwise changed such that the notification status (e.g., number of notifications) of those applications is no longer conveyed by those indications. The manner described above of selectively changing the appearance of representations of applications that are not on the application white list during the limited use mode allows the electronic device to effectively and selectively limit the use of particular applications during certain time periods by displaying limited use identifiers on applications that the user does not have access rights to during the limited use mode, which reduces the likelihood that the user will attempt to access such limited applications, which in turn reduces the use of the electronic device during those time periods, thereby reducing power consumption and improving the battery life of the device.

In some embodiments, displaying the first representation of the first application with the first visual characteristic includes displaying (1186) the first representation with a notification indicator (e.g., an indicator of an unread message, a missed call, etc.) that includes 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 in which the notification indicator has been replaced with a restricted-use indicator (e.g., obscuring the indicator or replacing the indicator with a graphic), such as in fig. 10 RR-10 SS. In some embodiments, the lock identifier described above replaces the indication of the notification identifier of the application icon for the non-white list application during the limited use mode time window, as previously described. The manner described above of selectively changing the appearance of representations of applications that are not on the application white list during the limited use mode allows the electronic device to effectively and selectively limit the use of particular applications during certain time periods by replacing the notification indications of the application representations with limited use identifiers on applications that the user does not have access rights during the limited use mode, which prevents the user from attempting to access the limited applications with such notifications by not indicating the presence of recent notifications, which reduces the use of the electronic device during those time periods, 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. 11A-11I are described is merely exemplary and is not intended to suggest that the order described is the only order in which the operations may be performed. One of ordinary skill in the art will recognize a variety of ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein in connection with other methods described herein (e.g.,

methods

700, 900, 1300, and 1500) also apply in a similar manner to method 1100 described above in connection with fig. 11A-11I. For example, the limited-use mode, usage limit settings, etc., described above with reference to method 1100, optionally have one or more of the features of the limited-use mode, usage limit settings, etc., described herein with reference to other methods described herein (e.g.,

methods

700, 900, 1300, and 1500). For the sake of brevity, these details 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 conjunction with fig. 1A-1B, 3, and 5A-5H) or an application-specific chip. Further, the operations described above with reference to fig. 11A-11I are optionally performed by the components depicted in fig. 1A-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 recognizer 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 calls data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update the content displayed by the application. Similarly, one of ordinary skill in the art will clearly know how other processes may be implemented based on the components depicted in fig. 1A-1B.

Suppression of secondary application functionality 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 the 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 time periods. The embodiments described below provide a way for an electronic device to suppress ancillary functionality for particular applications when their limitations are met, such as when application usage limits associated with those applications are reached and/or during one or more periods of time during which 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 usage of the electronic device, thereby reducing the power usage of the device and increasing the battery life of the battery-powered device. It should be understood that one uses the device. When a person uses a device, the person is optionally referred to as the user of the device.

Fig. 12A-12 BB illustrate exemplary ways in which an electronic device suppresses ancillary functions of particular applications when application usage limits or restrictions 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 illustrates an exemplary device 500 having a touch screen 504, described with reference to fig. 5A-5H. The 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 restriction condition is not met on the device 500 (e.g., the user-defined usage limit has not been reached and is outside of one or more user-defined time windows associated with the restricted use mode). In some embodiments, the limit condition is satisfied when a usage 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 restriction condition is satisfied during one or more time windows associated with the restricted usage mode, as described above with respect to method 1100. In fig. 12A, the 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 the device 500, as described above with reference to fig. 4A. As shown in fig. 12A, the 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, the notification indicator 1204 is a label superimposed over (or partially superimposed over) an 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 restriction condition is not satisfied on device 500. Search user interface 1207 is optionally a user interface for the operating system of device 500 to search for content accessible from device 500 (e.g., websites, news, emails, 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 displaying applications suggested by the operating system of the device 500 for the user (e.g., suggesting commonly used applications, recently used applications, favorite applications, currently running applications), and a desktop applet 1210 corresponding to the application installed on the device 500 (e.g., a user interface object or window including text, images, and/or any other content associated with and updated by the corresponding application), as shown in fig. 12C. For example, in fig. 12C, the application suggestion user interface 1208 includes a photos application 428, a fitness support application 442, a messaging application 424, and a social media a application 452, and the desktop applet 1210a corresponds to a "social media application a" application and the desktop applet 1210b corresponds to a "contacts" application.

In FIG. 12D, the user has entered the search term "social media" into the text field 1204 when the restriction is not satisfied on the device 500. In response to the search term "social media" having been entered into the text field 1204, the device 500 displays various search results related to the search term "social media" in the search user interface 1207. For example, device 500 displays a link 1212a of the social media application "social media a" installed on device 500, a link 1212b of the social media website "social media a" as 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 device 500 while device 500 is displaying home screen user interface 1202 when the restriction condition is not satisfied on device 500. In some embodiments, the event of receiving a message at device 500 corresponds to activating a function for displaying a notification related to the new message on device 500. For example, fig. 12F shows device 500 displaying notification 1214 in response to receiving the message in fig. 12E, indicating that the new message was received 424 in connection with the messaging application. In some embodiments, the event of receiving a new message corresponds to the initiation of other auxiliary functions, such as updating an unread message indicator on an application icon. For example, fig. 12F shows device 500 updating indicator 1204 on messaging application 424 to reflect that there are now four unread messages (including the newly received message) in messaging application 424 in response to detecting a new message for messaging application 424.

Fig. 12G shows the touchscreen 504 displaying the home screen 1202 when a restriction condition is satisfied 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-use mode) while 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 satisfied for those applications. For example,

icons

424 and 452 corresponding to restricted messaging application 424 and social media A application 452 are masked (e.g., distorted, grayed out, faded out, and/or visually changed) when the restriction conditions are satisfied for those applications. Fig. 12G illustrates that indicator 1204 associated with messaging application 424 is optionally masked such that the number of unread notifications (e.g., the number of unread messages in messaging application 424) is no longer visible. In some embodiments, the indicator 1204 is masked by replacing it with a placeholder generic indication 1206 (e.g., a lock icon), as shown in fig. 12G. In some embodiments, the placeholder 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 embodiments, a placeholder generic indicator (e.g., a lock icon) is placed on or near text associated with an application icon for a restricted application.

FIG. 12H illustrates that device 500 suppresses notifications for restricted applications by forgoing displaying notifications for two new messages received in a message and a social media A application when the restriction conditions are satisfied for those applications. Fig. 12H also shows that device 500 forgoes updating indicator 1204 on messaging application 424 to reflect that there are now five unread messages (including the newly received message) in the messaging application. In some embodiments, the device 500 overlays a place placeholder generic indication 1206 (e.g., a lock icon) on (or partially on) an icon associated with the restricted application when the restriction condition is satisfied for the application that received the message for the application, as shown in fig. 12H. For example, FIG. 12H shows that the lock icon 1206 overlays the upper right portion of the social media A application 452. In some embodiments, the placeholder 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 embodiments, a placeholder generic indicator (e.g., a lock icon) is placed on or near text associated with an application icon for a 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 that is not being displayed down to home screen 1202), which causes device 500 to display notification history interface 1220 when the restriction conditions are satisfied on device 500. Notification history interface 1220 is optionally a user interface of the operating system of device 500 that displays previously received notifications stored on device 500 that correspond to one or more applications. In some embodiments, device 500 displays the suppressed notifications for the restricted application in notification history interface 1220. In some embodiments, device 500 visually masks notifications (e.g., blurs, grays, or visually changes the notifications) for restricted applications displayed in notification history interface 1220, as shown in fig. 12I. For example, in FIG. 12I, device 500 displays notification 1222 associated with messaging application 424 and notification 1224 associated with social media A application 452 in notification history interface 1220, which were received at FIG. 12G but suppressed in FIG. 12H.

In some embodiments, device 500 displays the previously suppressed notifications when the usage limits of the applications associated with those notifications are reset (e.g., after the restriction conditions are no longer satisfied for those applications; e.g., after the usage limits of the applications are no longer satisfied, or after the limited-use mode of the device ends), as if they were just received. For example, fig. 12J shows the touchscreen 504 displaying the home screen 1202 when the restriction conditions are satisfied 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 restricted 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 restriction conditions are satisfied (e.g., as described above with reference to fig. 12G-12H). Fig. 12K shows the device touchscreen 504 displaying the 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 satisfied for those applications). In response to the usage limits being reset for the messaging application 424 and the social media A application 452 or the limited use 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 satisfied as new notifications. For example, device 500 optionally presents previously suppressed notification 1222 associated with messaging application 424, and previously suppressed notification 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., the application for which the restriction condition is satisfied), such as suppressing the restricted application in 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 the home screen 1202 is displayed when the restriction conditions are satisfied for the messaging application 424 and the 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 ancillary 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 displaying applications suggested for the user by the operating system of the device 500, and a desktop applet 1210 corresponding to the applications 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, device 500 suppresses application suggestions and desktop widgets associated with the restricted application by optionally visually obscuring (e.g., blurring, graying out, or visually changing) the restricted application in application suggestion user interface 1208 (e.g., visually obscuring restricted social media a application 452) and visually obscuring desktop widgets associated with the restricted application (e.g., visually obscuring desktop widgets associated with restricted social media a application 452), as shown in fig. 12M. In some embodiments, the device 500 suppresses application suggestions and desktop widgets associated with the restricted application by optionally not displaying the restricted application in the application suggestion user interface 1208 and not displaying the desktop widget associated with the restricted application (e.g., forgoing displaying the social media a application 452 and the desktop widget 1210a associated with the restricted social media a application 452), but displaying other unrestricted applications (e.g., applications for which the restriction conditions are not satisfied) and/or desktop widgets associated with the unrestricted application.

In FIG. 12N, the user has entered the search term "social media" into the text field 1204 when the restriction is satisfied on the device 500 for the social media A application 452. In response to the search term "social media" having been entered into the text field 1204, the device 500 displays various search results related to the search term "social media" in the search user interface 1207. For example, device 500 optionally displays a link 1212a of the social media application "social media a" 452 installed on device 500, a link 1212b of the social media website "social media a" as a website related to the "social media a" application, and links of 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. Since the constraint is satisfied for the social media A application 452, the

links

1212a and 1212b are suppressed (e.g., visually changed or masked) 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 non-restricted applications (e.g., applications for which the restrictions are not met) are optionally displayed.

In some embodiments, the device 500 suppresses other auxiliary functions associated with the restricted application (e.g., the application for which the restriction condition is satisfied), such as suppressing website content associated with the restricted application. For example, FIG. 12P illustrates the device 500 displaying a web browser interface 1230 that suppresses web content from a website "www.socmeda.com" associated with the restricted social media A application 452 by forgoing displaying web content from the website. In some embodiments, 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, the 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 the 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., blurring, graying out, or visually changing) the web content 1236 and displaying an indication 1232 that the interpreting website is restricted, as shown in fig. 12Q. In some embodiments, the web browser interface 1230 includes a URL field 1234 for entering a network address (e.g., URL) of a website. Device 500 optionally allows the user to enter a website address in URL field 1234 when suppressing a website associated with the restricted application and to navigate to another website, as shown in fig. 12R-12S.

In some embodiments, device 500 allows a user to share content with other application or applications installed on the device. Fig. 12T illustrates device 500 displaying network content in a web browser interface 1230, which web browser interface 1230 optionally includes a selectable sharing affordance 1236 for sharing network content. For example, in FIG. 12T, selection of the sharing affordance 1236 is detected (e.g., through a tap of the contact 1003 detected on the sharing affordance 1236, as shown in FIG. 12T). In response to selection of sharing affordance 1236, device 500 displays sharing table graphical user interface 1240, as shown in FIG. 12U. In some embodiments, the shared table graphical user interface 1240 includes selectable icons for applications installed on the device 500 that the user optionally selects to share network content, as shown in fig. 12U. In some embodiments, device 500 suppresses icons of restricted applications in shared table graphical user interface 1240. For example, in fig. 12U, device 500 suppresses restricted message application icon 424 and restricted social media a application icon 452 in shared form graphical user interface 1240 by visually obscuring restricted message application icon 424 and restricted social media a application icon 452 (e.g., by blurring, graying out, or visually changing icons). In some embodiments, device 500 suppresses restricted messaging application icon 424 and restricted social media a application icon 452 by forgoing displaying restricted messaging application icon 424 and restricted social media a application icon 452 in shared form graphical user interface 1240 (e.g., by not displaying an icon of a restricted application), but displaying other unrestricted applications (e.g., applications for which the restriction conditions are not met).

Fig. 12V illustrates device 500 displaying content associated with a video Z application in a picture-in-picture (PIP) interface 1250 when the constraints of the video Z application are not satisfied. In some embodiments, PIP interface 1250 is displayed on another user interface (e.g., on a home screen, a main user interface of another application, a user interface of other applications), as shown in fig. 12V. In some embodiments, device 500 suppresses application content from being displayed in a picture-in-picture (PIP) interface 1250 when the application's constraints are satisfied. For example, fig. 12W illustrates that content associated with the video Z application is suppressed from being displayed in the PIP interface 1250 when the restriction condition of the video Z application is satisfied. In some embodiments, device 500 suppresses the display of content associated with the video Z application in PIP interface 1250 by visually masking (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 the video Z application in PIP interface 1250 by forgoing the display of content associated with the video Z application in PIP interface 1250. If the PIP interface 1250 is currently displaying content associated with the video Z application when the restriction condition is satisfied, the device 500 in some embodiments suppresses displaying content associated with the video Z application by stopping display of the content in the PIP interface 1250 (e.g., closing the PIP window) and/or masking the PIP interface 1250 (e.g., graying out or fading out the PIP window) and/or pausing playback of the video. In some embodiments, the device 500 refrains from displaying content associated with the video Z application in the PIP interface 1250 by visually masking the content and/or the PIP interface 1250 and automatically closing the PIP interface 1250 after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds), as shown in fig. 12X (e.g., displaying the device 500 after ceasing to display the PIP interface 1250).

In some embodiments, the device 500 suppresses other auxiliary functions associated with the restricted application (e.g., the 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., up to home screen 1202 from an area of touch screen 504 that is not being displayed), which causes device 500 to display media control interface 1260 when the restriction condition is not satisfied 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 illustrates device 500 controlling media playback of the Song "Hit Song" of "Pop Star" through a music application. In some embodiments, the device 500 suppresses the media control interface 1260 for media content associated with restricted applications (e.g., applications for which the restriction condition is satisfied). For example, FIG. 12AA illustrates the device 500 displaying a media control interface 1260 when the constraints are satisfied on the device 500 for the music application, the messaging application 424, and the social media A application 452, and suppressing the media control interface 1260 for controlling media content associated with the music application. In some embodiments, device 500 suppresses media control interface 1260 by stopping playback of media content associated with the music application and disabling media control button 1262 (e.g., not allowing the button to be used to control media content associated with the restricted application), as shown in fig. 12 AA. In some implementations, device 500 also visually hides 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 embodiments, the device 500 automatically resets the media control interface 1260 after a period of time (e.g., 5 seconds, 10 seconds, 20 seconds), as shown in fig. 12 BB. For example, fig. 12BB 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 that 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 (e.g., 5 seconds, 10 seconds, 20 seconds) after the constraint is met and/or for a period of time after the device 500 resets the media control interface 1260.

Fig. 13A-13H are flow diagrams illustrating a method 1300 of suppressing auxiliary functionality of particular applications when application usage limits or restrictions associated with those applications are reached, according to some embodiments of the present disclosure. Method 1300 is optionally performed on an electronic device (such as device 100, device 300, or device 500) as described above in connection with fig. 1A-1B, 2-3, 4A-4B, and 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 accessibility functionality for particular applications when application usage limits associated with those applications are reached. The method reduces overall usage of the electronic device by limiting the way a user interacts with a particular application. For battery-powered electronic devices, reducing the overall usage of the electronic device conserves 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, a mouse, a touchpad, 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)) in communication with a display and one or more input devices implements restrictions (e.g., maintaining screen time information, time of use of a particular application, information about notifications received from a particular application, information about events of interest, and optionally controls the amount of each of the above allowed by the electronic device (e.g., usage limits, bedtime limits, etc.)) corresponding to activation of a secondary function of a first application (e.g., an occurrence of an event that would trigger a notification of a display application, a request to display a desktop applet corresponding to an application, a request to share content with an application via a system sharing user interface, a request to view a website associated with an application, a request to view a history of previous notifications (including notifications of an application), a request to display application content in a picture-in-picture (PIP) mode, a request to display an 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), wherein the secondary function of the first application is a primary user interface available to be executed without the first application being displayed (e.g., not launching the application in an application window or other main view of the application), such as in fig. 12C (e.g., displaying interactive notifications, performing shared form actions, displaying desktop applets, displaying notification history, displaying websites in a browser, displaying application content in a PIP mode, displaying applications in search results, displaying application windows in a multitasking graphical user interface, or displaying and/or controlling media control operations). 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 the event (1304) corresponding to activation of the secondary function of the first application, in accordance with a determination that a restriction condition of the first application has been satisfied (e.g., a user-defined "limit" of application usage (e.g., a usage limit or quota) has been reached), the electronic device suppresses (1306) the secondary function (e.g., suppresses a notification generation function associated with the application, a display of a website associated with the application, a shared table 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 functions associated with the application (including operating system functions) (e.g., restricting application from appearing in search results, restricting access to a desktop applet associated with the application, restricting application from appearing as a suggested application, Or restricting the window corresponding to the application from appearing in the 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 category, or for a particular application. In some embodiments, the launching of the application is also inhibited (e.g., restricted). In some embodiments, the secondary function is inhibited by preventing the function from being executed in response to detecting the event.

In some embodiments, in response to detecting the event (1304) corresponding to activation of the secondary function of the first application, in accordance with a determination that the restriction condition has not been met, the electronic device executes (1308) the secondary function without displaying a main user interface of the application (e.g., allowing normal use or execution of functions related to various applications on the electronic device, such as generating notifications from the application, sharing table actions, displaying websites associated with the application, displaying application content in a PIP mode, displaying desktop widgets associated with the application, displaying windows corresponding to the application appear in a multitasking graphical user interface, etc.), such as in fig. 12C. The limits 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 manner described above of suppressing the functionality of an application for which 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 accessibility functionality optionally includes presenting a first type of indication of a notification associated with the first application (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.) in response to an occurrence of an event corresponding to activation of the notification (e.g., an application-generated alert and/or notification) (1310), such as in fig. 12F. In some embodiments, the notification includes a visual indication (e.g., a window, a pop-up box), including text and/or an image. Additionally or alternatively, the notification optionally includes an audible and/or tactile and/or haptic output indication. In some embodiments, the electronic device suppresses notifications associated with applications for which usage limits have been exceeded. In some embodiments, notifications are suppressed by forgoing display of a user visual indication (e.g., text and/or images) or forgoing generation of the notification. In some embodiments, notifications are suppressed by masking user visual indications (e.g., visually changing visual indications, text, and/or images). 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 secondary function includes presenting a notification generated by the first application. The manner in which notifications associated with applications for which the constraints are satisfied are suppressed described above allows the electronic device to effectively reduce overall usage of the electronic device (e.g., by not performing the notification function, and thus 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, detecting an event corresponding to activation of an auxiliary function of the first application includes detecting occurrence of an event corresponding to activation of a notification associated with the first application (1312) (e.g., detecting occurrence of an event that would trigger presentation of the notification), such as in fig. 12E. In some embodiments, suppressing the accessibility functionality includes forgoing presentation of the first type of indication (1314) (e.g., suppressing notifications associated with restricted applications) in response to the notification generated by the first application, such as in fig. 12G-12H. In some embodiments, notifications are suppressed by forgoing display of a user visual indication (e.g., text and/or images) or forgoing generation of the notification. In some embodiments, notifications are suppressed by masking user visual indications (e.g., visually changing visual indications, text, and/or images). 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 secondary function includes presenting an indication of a first type (1316) (e.g., displaying a banner, pop-up notification, or lock screen notification) in response to the notification generated by the first application, such as in fig. 12F. In some embodiments, performing the secondary function includes presenting a notification generated by the first application. The manner described above of suppressing notifications associated with applications for which the restriction condition is satisfied, and not suppressing notifications associated with applications for which the restriction condition is not satisfied, allows the electronic device to effectively and selectively reduce usage of the electronic device (e.g., by not performing the notification function of certain applications and thus not prompting a 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, in accordance with a determination (1318) that the restriction condition of the first application is satisfied, the electronic device includes (1319) a visual indication (e.g., an image, a window, text, etc.) of the first type of indication in a notification history user interface (e.g., a user interface for displaying visual indications of 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 for the plurality of applications in a 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., a window) dedicated to displaying notifications that have been received on the electronic device via the plurality of applications (e.g., even if the constraints of the first application are satisfied in accordance with the determination). This optionally allows the user to later view notifications for the suppressed application. In some embodiments, a visual indication of notifications from an unsuppressed application is also presented outside of (in addition to) the notification history user interface, while a visual indication of notifications from a suppressed application (e.g., a first application) is presented only in the notification history user interface. The manner in which suppressed notifications associated with applications for which the constraints are satisfied are displayed in the notification history described above allows the electronic device to efficiently organize and display otherwise suppressed notifications without pushing the notifications (e.g., by not alerting the user to the notifications with pop-up windows, sounds, and/or tactile and/or haptic output indications when they are generated), which reduces overall usage 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 accessibility functionality includes forgoing presentation of a first type of indication (1320) in response to the notification generated by the first application (e.g., not actively presenting new indications (e.g., images, sounds, and haptic and/or tactile outputs) of any notifications associated with the application when usage limits of the application have been exceeded, such as in fig. 12G-12H in some embodiments, after suppressing the accessibility functionality of the first application, the electronic device determines (1322) that the restrictions of the first application are no longer satisfied (e.g., that usage of the first application no longer satisfies the usage limits of the first application, that the device is no longer in limited use (e.g., device downtime or bedtime mode), etc.), such as in fig. 12K in some embodiments, in response to determining that the restrictions of the first application are no longer satisfied, 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 it was just received when the usage restrictions were reset), such as in fig. 12K. In some embodiments, notifications generated by an application during a time period in which the usage limit of the application has been reached are presented to a user when the usage limit of the application is reset and thus no longer exceeded. For example, if the usage limit of the relevant application is a daily limit, the usage limit is optionally reset at midnight the following day. In such cases, when the usage limit of the application is reset at midnight, the electronic device optionally displays previously suppressed notifications in the user interface indicating that these notifications would have been previously presented if not suppressed (e.g., on a wake-up or lock-up screen of the device). In some embodiments, these notifications will be performed all at once (e.g., in an alert, window, or pop-up containing all previously suppressed notifications), or will be displayed separately/sequentially. The manner in which notifications associated with applications are presented at usage limit resets described above allows the electronic device to effectively present previously suppressed notifications while reducing overall usage of the electronic device, which reduces power consumption and improves battery life of the device.

The accessibility functionality optionally includes displaying a desktop applet user interface that exposes one or more accessibility user interfaces of one or more applications, including an accessibility user interface (1326) of a first application (e.g., corresponding to the desktop applet of the application), such as in fig. 12C. In some embodiments, the desktop widget includes a user interface object (e.g., a window) including text and/or images associated with the application (e.g., a weather desktop widget displaying a current temperature, a sports desktop widget displaying a live-live score, a news desktop widget displaying a title of a recent event, 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, secondary user interfaces (e.g., desktop applets) are displayed simultaneously with additional secondary user interfaces (e.g., desktop applets) of other applications that are different from the primary user interfaces of those applications (e.g., desktop applets are displayed simultaneously with desktop applets of other applications). In some embodiments, a secondary user interface (e.g., a desktop applet) is displayed in a user interface of the desktop applet that is different from a primary user interface of the first application. The event corresponding to activation of the auxiliary function optionally includes a request to display a desktop applet user interface (1328) (e.g., an input from a user to display the desktop applet user interface on the electronic device), such as in fig. 12B-12C. In some embodiments, suppressing the secondary function includes displaying the desktop applet user interface while suppressing (e.g., not displaying or masking with a message or splash screen indicating that the restriction condition is satisfied) the secondary user interface (1330) of the first application (e.g., suppressing the one or more desktop applets whose usage limit is exceeded), such as in fig. 12M. In some embodiments, a desktop applet is suppressed by forgoing display (e.g., the desktop applet is not displayed) of user interface objects (e.g., text and/or images) of the desktop applet associated with the application for which the usage limit was exceeded while displaying other desktop applets. In some embodiments, a desktop applet is suppressed by hiding user interface objects (e.g., visually changing user interface objects, text, and/or images) while displaying other desktop applets. The hidden desktop applet optionally includes an indication of a display restriction condition in place of text and/or images associated with the application (e.g., the contents of the desktop applet when the restriction condition is not satisfied). In some embodiments, all desktop applets are suppressed. In some embodiments, performing the secondary function includes displaying a desktop applet user interface that exposes one or more desktop applets 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 as or similar to the desktop applet user interface described with reference to fig. 8W. The manner in which the desktop applet corresponding to the application for which the usage limit has been exceeded is suppressed described above 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 user input to the device (e.g., input to monitor 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, the accessibility functionality includes presenting a visual indication (1332) of one or more applications (including the first application) for which the suggestion conditions have been met in a suggestion user interface (e.g., displaying application suggestions to the user on the electronic device in a system (e.g., operating system) user interface (other than a user interface of a particular application on the electronic device), such as in FIG. 12. in some embodiments, the applications suggested for the user are commonly used applications, recently used applications, favorite applications, applications currently running, etc. The search is conducted for all installed applications on the electronic device, applications available in the application store for download, websites, content of applications installed on the electronic device (e.g., content of search messages, emails), and so forth. The search results would then optionally include a list of applications, websites, and/or content, including the one or more entered characters.

The event corresponding to activation of the accessibility functionality optionally includes a request (1334) to present a visual indication of the one or more applications for which the suggestion condition has been met in a suggestion user interface (e.g., an input from a user to display application suggestions on the electronic device), such as in fig. 12B-12C. In some embodiments, suppressing the accessibility assistance function optionally includes presenting a suggestion user interface without presenting a visual indication (1336) of the first application (e.g., without displaying the application in the suggestion interface), such as in fig. 12M. For example, the first application will not be displayed with commonly used applications, even when the first application is commonly used. In another example, the first application will not be displayed in the search results even if the search prompting display of the search results encompasses the first application. In some embodiments, 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 suggestion user interface is suppressed (e.g., all applications are not displayed or hidden). In some embodiments, performing the secondary function includes presenting a suggestion user interface including visual indications of the one or more applications, including a visual indication of the first application (e.g., displaying the application in the suggestion interface). The proposed way of suppressing applications for which the usage limit has been exceeded described above 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 accessibility functionality 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 embodiments, the event corresponding to activation of the accessibility functionality includes a request (1340) to display web content associated with the first application in a browser user interface (e.g., input from a user to display web content or a website associated with the first application in a web browser), such as in fig. 12R. In some embodiments, suppressing the accessibility functionality includes preventing access to web content associated with the first application (1342) (e.g., forgoing display of web content associated with the application whose 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 prevented. In some embodiments, the electronic device will suppress not only the application for which the usage limit has been exceeded, but also any websites associated with the application. The electronic device optionally presents a visual indication of the restriction condition (e.g., a splash screen or other image that obscures the web page content) in place of the web site content when the restriction condition is satisfied. In some embodiments, performing the secondary function includes presenting web content associated with the first application in a browser (e.g., displaying a website in the browser). The website associated with the application described herein is optionally the same as or similar to the website associated with the application described with reference to method 900. The manner in which the web content associated application whose usage limit has been exceeded described above is suppressed makes the user-device interface more efficient (e.g., the user does not have to monitor its own device usage for the application and the website associated with the application, thus reducing the user's input to the device (e.g., input to monitor 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, preventing access to web content associated with the first application includes (1344) loading web content associated with the first application from a first website (1346) (e.g., the 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, preventing access to web content associated with the first application includes (1344) forgoing display of web content associated with the first application (1348) (e.g., the web content is loaded but not displayed by the electronic device), such as in fig. 12Q. In some embodiments, 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 network content is optionally displayed, but in a masked manner (e.g., distorted, grayed out, faded out, and/or visually altered). The manner in which the application associated with the web content for which the constraints are met (e.g., the usage limit has been exceeded or the device is in a limited mode) described above is suppressed makes the user-device interface more efficient (e.g., the user does not have to monitor its own device usage for the application and the website associated with the application, thus reducing user input to the device (e.g., input to monitor usage is reduced)), which allows the electronic device to effectively reduce 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 battery life of the device, while improving execution speed.

In some embodiments, preventing access to the web content associated with the first application includes (1350) forgoing displaying 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 the other website, for navigating within the website), such as in fig. 12R. In some embodiments, the navigation controls of the browser (e.g., URL fields or buttons on the browser) remain operable, while the particular web content associated with the application for which the restrictions are satisfied is restricted. In some embodiments, websites that are not associated with any application on the electronic device remain accessible when the constraints of one or more applications on the electronic device are met. For example, while access to a website associated with the first application is restricted, the navigation controls of the browser are not restricted, optionally allowing the user to navigate to other websites. The manner in which the above-described web content associated application is suppressed from being satisfied, while allowing access to other websites makes the user-device interface more efficient (e.g., the user does not have to monitor their own device usage for the application and websites associated with the application, thus reducing user input provided to the device (e.g., input used to monitor 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 constraint of the first application is satisfied, 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., detecting an occurrence of an event that would trigger display of content from another website that is 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 (1356) 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, in accordance with a determination that the second website is associated with the first application, the electronic device forgoes (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 satisfied (e.g., the usage limit has been reached, the device is in a restricted access mode, etc.), such as in fig. 12P. In some embodiments, 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 network content is optionally masked and displayed (e.g., warped, grayed out, and/or visually altered).

In some embodiments, in response to detecting a second event (1356) 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, 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 that displays the restriction condition that is not satisfied (e.g., the usage limit has been reached or the device is in a limited access mode, etc.), such as in fig. 12S. In some embodiments, only websites associated with applications for which the restriction condition is satisfied are restricted and the user is allowed to navigate to other websites. In some embodiments, websites that are not associated with any application on the electronic device are also accessible when the constraints of one or more applications on the electronic device are met. The manner in which the above-described restricting of web content-associated applications for which the condition is satisfied while allowing access to other websites makes the user-device interface more efficient (e.g., the user does not have to monitor their own device usage for the application and websites associated with the application, thus reducing user input provided to the device (e.g., input used to monitor 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 implementations, the secondary 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., displays a picture-in-picture (PIP) window on another user interface (e.g., on a home screen, a main user interface of another application, or a user interface of another application), such as in fig. 12V. The event corresponding to activation of the secondary function optionally includes a request to display media content in a picture-in-picture user interface of the first application (1364) (e.g., a request to view 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 embodiments, suppressing the secondary function includes suppressing a picture-in-picture user interface (1366) of the first application (e.g., forgoing displaying the PIP window, ceasing to display content in the PIP window), such as in fig. 12W. For example, if the usage limit of application a has been reached, the user will not be able to bypass the limited access to 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 usage limit of the application is met, and the electronic device will suppress this function by ceasing to display 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 embodiments, the PIP window is a window that utilizes a media playback application on the electronic device to playback media (e.g., movies, television programs, music, etc.) on the electronic device. If the usage limit has not been reached, display of the PIP window optionally will not be prevented (e.g., will not be suppressed). In some embodiments, performing the secondary function includes displaying a PIP window of the first application partially overlapping one or more other user interfaces. The manner in which the PIP window associated application whose usage limit has been exceeded described above 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 PIP window associated with the application, thus reducing the user's input to the device (e.g., input to monitor 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, a picture-in-picture user interface that suppresses a first application includes (1368): in accordance with a determination that a restriction condition of the first application is satisfied (1370) when the picture-in-picture user interface of the first application is displayed (e.g., a usage limit of the application is satisfied when the application is being used in PIP mode), the picture-in-picture user interface is masked (1372) for a first period of time (e.g., the PIP window is visually altered and/or blocked), such as in fig. 12W. In some embodiments, the PIP window will continue to display content from the first application, but the content will be visually altered (e.g., blurred, displayed in grayscale, or displayed with watermarks). In some embodiments, the PIP window will stop displaying content from the first application and will instead display other information (e.g., a visual indication that the usage limit for the 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, a picture-in-picture user interface that suppresses a first application includes (1368): in accordance with a determination that a restriction condition of the first application is satisfied (1370) when the picture-in-picture user interface of the first application is displayed (e.g., a usage limit of the application is satisfied when the application is being used in PIP mode), the display of the picture-in-picture user interface is stopped 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 the restriction condition for the first application is satisfied when the picture-in-picture user interface for the first application is not displayed, the electronic device detects, with the one or more input devices, user input corresponding to a request to display the picture-in-picture user interface for the first application (e.g., detects input for displaying a PIP user interface for the first application when the restriction condition is satisfied), and in response to a user input corresponding to a request to display a picture-in-picture user interface of the first application, and upon satisfaction of the constraints of the first application, the electronic device forgoes display of the picture-in-picture user interface of the first application (e.g., the constraints of the first application are satisfied when a PIP window of the application is not being displayed), and the electronic device prevents the window from launching at a later time. Thus, once the usage limit of a particular application has been exceeded, the user of the electronic device cannot circumvent the restrictions on that particular application. The manner in which the PIP window associated application for which the constraint is satisfied is suppressed as described above 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 user's input to the device (e.g., input to monitor 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 displaying a plurality of affordances (e.g., one or more graphical user interface buttons) (1376) (e.g., media control buttons including play, pause, rewind, forward, skip, etc. buttons) for controlling playback of media content associated with the first application, such as in fig. 12Z. In some embodiments, the media control buttons are displayed on the 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 (e.g., one or more of play, pause, rewind, forward, skip, etc.) of media content associated with the first application.

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

In some embodiments, 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 button will be displayed, but will not be operable (e.g., the button will not perform the media control function 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 implementations, the inoperable media control button will be masked (e.g., visually changed) in the media control user interface. In some embodiments, when a restriction condition of a particular media playback application (e.g., a movie playback application, a television program playback application, or a music playback application) is satisfied, 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 the application's own user interface or are limited outside of the application itself (e.g., in a system or operating system user interface of the electronic device that is globally accessible on the electronic device). In some embodiments, the media playback controls are blocked such that they are no longer selectable to control playback of any media utilizing the media playback application as long as the usage limit of the application is currently reached. In some embodiments, the media control button will be suppressed by preventing display by the electronic device (e.g., by preventing the media control user interface from being displayed or displaying the media control user interface without the media control button) when the restriction condition of the media playback application (e.g., the first application) is satisfied. 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 from displaying) after the period of time. The manner in which the media control buttons associated with the applications for which the constraints are satisfied are suppressed described above makes the user-device interface more efficient (e.g., the user does not have to monitor their own device usage for the applications and the media control buttons associated with the applications, thus reducing user input to the device (e.g., input to monitor 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, preventing the plurality of affordances from controlling playback of media content associated with the first application includes (1382) entering the plurality of affordances into an inactive state in which the device ignores user input for the plurality of affordances (e.g., into a state in which 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 the content in response to a selection input on the play button. In some embodiments, the frozen media control button will be masked (e.g., visually changed) to indicate to the user that it is frozen. In some embodiments, even if the media control buttons in the frozen state are inoperable, they will indicate that the media was recently played back (or potentially controllable 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 remaining until the constraints of the particular application associated with the media control button are no longer satisfied. In some embodiments, if the restriction condition of a particular media playback application is satisfied while the media control is controlling playback of that media playback application (e.g., while the media playback application is playing media on the electronic device), the media control is frozen in its current state (e.g., indicating the current playback state of the media, the identity (e.g., title) of the media, etc.) and is blocked from user interaction at the time the restriction condition becomes satisfied. In some embodiments, when the playback control is placed in the frozen state, playback of the media is also stopped. In some embodiments, the media control is reset to its default state for a certain period of time (e.g., 5 seconds, 10 seconds, 20 seconds) after being frozen (e.g., indicating no media is being played by the media playback application, indicating no media title, etc.).

In some embodiments, 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 entered into a default state (1386) from an inactive state (e.g., returning the media control button to the default state where 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 BB. Thus, in some embodiments, in the default state, the media control button no longer indicates the current playback state of the media, the identity (e.g., title) of the media, and so forth. In some embodiments, the period of time is the time remaining before the usage limit of the particular application associated with the media control button is reset. In some embodiments, the electronic device prevents presentation of media associated with any application for which the restriction condition is satisfied despite the affordance for controlling the media content being reset to the default state. In some implementations, the electronic device stops displaying the media control interface after the first period of time, rather than entering the media control button into the default state. The manner in which the application associated with the media control button whose constraint is satisfied is suppressed as described above makes the user-device interface more efficient (e.g., the user does not have to monitor their own device usage for the application and the media control button associated with the application, thus reducing user input to the device (e.g., input to monitor 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.

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 order described is the only order in which the operations may be performed. One of ordinary skill in the art will recognize a variety of ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein in connection with other methods described herein (e.g.,

methods

700, 900, 1100, and 1500) also apply in a similar manner to method 1300 described above in connection with fig. 13A-13H. For example, the usage limits, restricted usage modes, auxiliary functions, usage restriction settings, etc. on the electronic device described above with reference to method 1100 optionally have one or more of the features of the usage limits, restricted usage modes, auxiliary functions, usage restriction settings, etc. on the electronic device described herein with reference to other methods described herein (e.g.,

methods

700, 900, 1100, and 1500). For the sake of brevity, these details 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 conjunction with fig. 1A-1B, fig. 3, fig. 5A-5H) or an application-specific chip. Further, the operations described above with reference to fig. 13A-13H are optionally performed by the components depicted in fig. 1A-1B. For example, detect operation 1302, suppress operation 1306, and execute 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 recognizer 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 calls data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update the content displayed by the application. Similarly, one of ordinary skill in the art will clearly know how other processes may be implemented based on the components depicted in fig. 1A-1B.

Remote management of restriction settings

Users interact with electronic devices in a number of different ways, including utilizing applications accessible on the devices. In some cases, an administrator (e.g., a parent) remotely manages the restriction settings at a restricted device (e.g., an 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 permission to change one or more usage limit settings of a limited device, either with a password 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 an electronic device to provide an efficient way to facilitate such changes when another party (e.g., a parent) requires authentication. This facilitation 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 the battery life of the device by enabling the user to use the device more quickly and efficiently. It should be understood that one uses the device. When a person uses a device, the person is optionally referred to as the user of the device.

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

Fig. 14A illustrates 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 in a household, including one or more child user accounts and one or more parent user accounts. In some embodiments, an administrator or parent user account has permission to change one or more restriction settings of the child electronic device 500 (e.g., one or more restriction settings described above with reference to fig. 10A-13H). The 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 indications 1498-26 that the initial restriction settings have been set (e.g., by the parent device) for the electronic device when not previously set. Indications 1498-26 include information about which restriction settings have been set and their detailed information (e.g., "device downtime on Monday through Thursday 6am-10 pm" and "usage limit: news applications, game categories, and social media categories"). 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 restriction 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 restriction settings user interface includes an indication of device usage 1402 and an indication 1408 that screen time data is being shared with one or more parent devices associated with the child device, and a plurality of affordances 1404a-e for modifying various restriction settings of the electronic device (e.g., "device downtime" 1404a, "application limits" 1404b, "always allowed" 1404c, "content and privacy" 1404d, and "include 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. The application limit 1404b is described in more detail above with reference to fig. 8A-9K. 1404c are 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 in a web browsing application. When this feature is turned off, the parent device optionally does not present usage information about which websites are accessed by the child device 500. However, accessing a website associated with an application installed on the child device 500 is optionally calculated as accessing the application using the electronic device (e.g., the time taken to access the website associated with the application accounts for the usage limit of the application or class of applications and is included in the usage data for the application and/or class). It should be understood 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 restriction permissions, such as the ability to set device downtime, applications and functions that are always allowed, sharing and privacy permissions, content purchase settings, age-restricted content consumption settings, and the like, 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 device 500 is below a threshold age at which it is optional to share screen time data with the parent of the child. Thus, the electronic device 500 presents an indication 1408 regarding the sharing of the screen time data with the parent of the child, without presenting settings for no longer sharing the screen time data with the parent of the child.

In FIG. 14C, electronic device 500 detects contact 1403 at affordance 1404a for altering one or more device downtime settings. In response to the request to change the settings, the electronic device 500 presents an 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 an administrative 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 restriction settings is different from the password used to unlock the electronic device 500 so that an administrator or parent may know the password, but not the administrator or child.

In fig. 14E, the electronic device 500 detects a contact 1403 at the affordance 1406 for remotely requesting parental permission to change the restriction setting. In response to the request for permission to change the restriction 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 permission to change the restriction setting.

Fig. 14F illustrates the electronic device 500 associated with a user account for a parent. The electronic device 500 presents an indication 1489-20 that the child requests permission to change the restriction settings at the electronic device of the child. As shown in fig. 14F, in some embodiments, the indications 1489-20 include information about which limit settings (e.g., equipment down time) the child is attempting to change. The parent can grant (e.g., "allow" by selecting indication 1498-20) or deny (e.g., "deny" by selecting indication 1498-20) the child access to the restriction settings at the child's electronic device. If the parent denies the child's request to change the restriction settings, the child device cannot change the restriction settings. If the parent approves the child's request to access the restriction settings at the child's electronic device, the child's electronic device presents a user interface for changing the restriction settings. In some embodiments, when a parent approves a change to a restriction setting, a child device is granted access to the restriction setting for a predetermined period of time, for a single session (e.g., until the child exits the restriction setting user interface), until one or more restriction setting changes, or until the child leaves the setting user interface for more than a predetermined amount of time.

FIG. 14G illustrates the electronic device 500 associated with a child user account. The electronic device 500 presents a user interface 1410 for altering one or more settings associated with device downtime (1411-1417), such as in response to a 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 a contact 1403 and optionally detects a further user input to change the device down time start time from 10pm to 11 pm. As described above, parental authorization for altering one or more restriction settings is optionally valid for a limited amount of time. Accordingly, the electronic device 500 presents an indication 1450 that a change to the device downtime settings may be made for three minutes as well. As described above, other authorization time frames and criteria are possible. After the settings are changed, the restriction settings user interface is updated to reflect the changed settings, as shown in FIG. 14H (e.g., "plant downtime 1404 a" is set to 11pm to 5am for Monday through Thursday, which is preceded by being set to 10pm to 5am for Monday through Thursday, as shown in FIGS. 14B through 14C).

When a child makes changes to the restriction settings, the parent device optionally presents an indication describing which changes were made. Fig. 14I illustrates the electronic device 500 associated with a parent account. As shown in FIG. 14I, the electronic device 500 presents instructions 1498-22 regarding the child device changing the device downtime from 10pm to 5am on Monday to Thursday to 11pm to 5am on Monday to Thursday. The indications 1498-22 include affordances for rejecting or allowing changes. Thus, the parent device is optionally able to overwrite the setting changes made at the child device. If the parent device approves changes to the settings made by the child device, the child device operates according to those changes. For example, by modifying the approved device downtime from 10pm to 5am to 11pm to 5am, the child device operates in a normal unrestricted mode up to 11pm, rather than beginning to operate in a restricted use mode from 10 pm.

If the parent rejects a setting change made by the child device, the child device optionally presents an indication that the setting change was rejected. FIG. 14J illustrates the electronic device 500 associated with a child user account. The electronic device 500 presents an indication 1498-24 that the change to the restriction setting was rejected by the parent (e.g., "the parent rejects the device downtime setting change"). Further, when the parent rejects the setting change made at the child device, the child device continues to operate according to the setting before the change. That is, the child device optionally will continue to transition from 10pm into the limited use mode.

Fig. 14K illustrates a usage panel for device usage by a child presented at the electronic device 500 associated with a parent user account. The child device usage control panel includes an indication 1416 of the overall usage of the child's devices, an indication 1428 of how the child's device usage compares to the average usage of the devices, 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, indications 1422a-b of the usage limits set applications and application categories, an indication 1442 of the usage limits unset applications, and a plurality of affordances 1440a-c for altering the limit settings associated with the applications and categories presented in the control panel 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 taken to access the website associated with the application and category for which the usage measurements are presented using the browser application is optionally counted as the application associated with the access using the electronic device (e.g., accessing one or more websites associated with a news application is optionally counted in the news application usage measurements and usage limits 1422 a).

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

FIG. 14N illustrates a child restriction settings user interface presented by the electronic device 500 in association with a parent user account. The restriction setting user interface includes an indication of the use of the child device and a plurality of affordances 1404a-f for altering the restriction setting of the child device, such as described with reference to fig. 8 LLL-8 NNN and 10Y-10 AA. If the child's age is greater than a threshold age (e.g., 13 years old), the parent optionally has the option of removing and/or altering the screen time password required to alter the restriction settings for the child electronic device at the child electronic device by selecting the 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 affordance 1404g, but the screen time password cannot be removed.

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

As described herein, the parent device is optionally able to access screen time data for the child device and make changes to one or more restriction settings of the child device. It should be understood that shared screen time data is one example of the various 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 UU (e.g., screen time, notifications, pick-up of a device, etc.), the ability to set and update one or more restriction settings (e.g., device downtime and/or usage limits), the ability to set one or more content and privacy settings, content purchase settings, age restriction content consumption settings, etc.

Once the child's age exceeds a predetermined threshold (e.g., 18 years old), the child device optionally can cease 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. FIG. 14Q illustrates indications 1498-26 presented at the child device 500 that the child device is able to stop sharing screen time data with the parent of the child. When the age of the child exceeds a predetermined threshold (e.g., 18 years old), an indication 1498-26 is optionally displayed. When the child's age exceeds this threshold, the child's device's restriction settings user interface is optionally updated to include settings for ceasing to share screen time data with the child's parents. Fig. 14R illustrates a restriction settings 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 an affordance 1404h ("close 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 that the child device 500 detects contact at the affordance 1404 h.

In some embodiments, in response to this request to stop sharing screen time data with the parent of the child, the child device requests permission from the parent device to stop sharing screen time data, optionally including displaying an authentication user interface shown in fig. 14D. The parent optionally can approve the request for the child device to stop 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 stop sharing the screen time data is required, the screen time data optionally continues to be shared with the parent device until the parent approves the setting change to stop sharing the screen time data. In some embodiments, no parental permission to stop sharing screen time data is required when the child's age exceeds an age threshold (e.g., 18 years old).

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

Fig. 15A-15G are flow diagrams illustrating a method 1500 of managing restriction settings with permissions optionally provided by another electronic device, according to some embodiments of the present disclosure. Method 1500 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, 1-3, 4A-4B, and 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 way for updating one or more restriction settings associated with the electronic device 500 (e.g., a restricted device) with permission 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-powered electronic devices, improving the efficiency with which a user interacts with the user interface conserves power and increases the time between battery charges.

In some embodiments, a first electronic device 500 (e.g., a smartphone, a smartwatch, a tablet, a computer, a set-top box, etc.) in communication with a display device (e.g., a display, a touchscreen, a television) and one or more input devices (e.g., a touchscreen, a touch-sensitive surface, a remote control, etc.) when a usage restriction setting that restricts use of the first electronic device is active at the first electronic device (1502) (e.g., a usage limit that restricts use of one or more applications, application categories, overall device usage, etc., such as described with reference to

methods

700, 900, 1100, and/or 1300, a restricted usage mode that is active on the first electronic device, such as described with reference to

methods

700, 900, 1100, and/or 1300, etc.) A device), such as described with reference to

methods

700, 900, 1100, and/or 1300, whose usage restriction settings are controlled by an authorizing device (e.g., a device associated with a parent account or an administrator account in a set of related accounts including one or more child or restricted accounts), such as described with reference to

methods

700, 900, 1100, and/or 1300)), receive (1504), via the one or more input devices, a sequence of one or more inputs corresponding to a request to change usage restriction settings at the first electronic device (e.g., an input at the restricted device to change usage limits valid on the restricted device, restricted usage mode settings, etc., where such usage restriction settings have been set by or controlled by the authorizing device, such as in fig. 14C. In some embodiments, this input to alter the usage restriction setting on the restricted device is detected at a usage restriction setting user interface displayed on the restricted device that displays information about the usage restriction setting that is valid on the restricted 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 corresponding to a request for permission to a second electronic device, such as in FIGS. 14D-14E (or a request to an administrator account associated with the second electronic device). In some embodiments, a request for permission is sent to multiple accounts (e.g., multiple parents in a household) having administrator privileges, different from the first electronic device, for altering the usage restriction settings (1506) (e.g., a user interface displayed by the restricted device provides various ways of altering the usage restriction settings at the restricted device, including providing a password for altering the settings at the restricted device, such as described with reference to

methods

700, 900, 1100, and/or 1300, or requesting permission to an authorizing device to alter the usage restriction settings, or request permission from an administrator account associated with the authorizing device. In some embodiments, the limited device detects input to the authorization device of permission to change the usage restriction setting), the first electronic device transmits (1508) a request to the second electronic device for permission to change the usage restriction setting at the first electronic device, such as in fig. 14D-14F, (e.g., causing a notification or other message to be displayed at the authorization device indicating that a request to attempt to change the usage restriction setting on the limited device has been detected). In some embodiments, this notification on the authorizing device identifies the particular usage restriction setting that the restricted device is attempting to change and/or includes information about how the restricted device is attempting to change the usage restriction setting (e.g., a new value of the usage restriction setting detected at the restricted device). In some embodiments, in response to detecting input to the change authorization at the authorizing device, the authorizing 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 detecting an input at the authorizing device denying 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 input for changing the usage restriction setting).

In some embodiments, after transmitting (1510) a request for permission to change the usage restriction settings to the second electronic device, as in fig. 14D-14F, in accordance with a determination to receive an authorization response from the second electronic device (e.g., the user of the authorization device selects an "allow" 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 to receive a denial response from the second electronic device (e.g., the user of the authorization device selects a "deny" affordance displayed on the notification received at the authorization device), the first electronic device is denied (1514) to alter the usage restriction settings, such as in fig. 14I. In some embodiments, the user of the restricted device can instead enter a password at the restricted device to allow the restricted device to change the usage settings even if no response is received from the authorized device.

The manner in which changes in usage restriction settings on a restricted device are controlled from an authorizing device described above allows the electronic device to provide an efficient way of facilitating such changes when such changes require 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 the battery life of the device by enabling the user to use the device more quickly and efficiently.

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 before detecting a termination condition that allows the first electronic device to change the usage restriction setting (1516), such as in fig. 14G (e.g., the restricted device is allowed to change the usage restriction setting in a predetermined period of time (e.g., 30 seconds, 2 minutes, 5 minutes) after receiving approval from the authorizing device, the restricted device is allowed to change the restricted usage setting before the restricted device leaves the settings user interface in which such change is to be made (and optionally must again request permission before being allowed to change the usage restriction setting after leaving the settings user interface), the restricted device is allowed to change the restricted usage setting before the restricted device confirms the settings change (e.g., by performing a selection of a "save" or a "good" or a "return" affordance of the settings change in the settings user interface), the limited device is allowed to change the limited-use setting before the limited device leaves the setting user interface for more than a predetermined amount of time (e.g., 30 seconds, 2 minutes, 5 minutes).

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

In some embodiments, after allowing the first electronic device to change the usage restriction setting, the first electronic device changes the usage restriction setting and changes operation of the first electronic device in accordance with the change in the usage restriction setting (1518), such as in fig. 14H (e.g., changes an application or application usage limit that is valid on the restricted device in accordance with the change in the usage setting, changes device downtime on the restricted device in accordance with the change in the usage setting, etc., such as described in

methods

700, 900, 1100, and/or 1300).

The manner in which limited devices are operated 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 the user to interact with the device with fewer inputs), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

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 keypad 1482 shown in fig. 14D (e.g., a password, biometric feature, or other authorization credential to alter a usage restriction setting, as described in

methods

700, 900, 1100, and/or 1300), in accordance with the authorization credential being successfully authenticated (e.g., a user of a restricted device enters a correct credential to alter the usage restriction setting), the first electronic device is allowed (1522) to alter the usage restriction setting, such as in fig. 14G-14H; and upon the authorization credential not being successfully authenticated (e.g., the user of the restricted device entering an incorrect credential to change the usage restriction settings), the first electronic device relinquishes (1524) allowing the first electronic device to change the usage restriction settings, such as in fig. 14J. Thus, in some embodiments, the restricted device is allowed to alter the usage restriction settings in response to authorization credentials being input at the restricted device (rather than receiving authorization from the authorizing device). In some embodiments, the request for permission is not transmitted to the authorizing device when the authorization credential is input at the restricted device.

The manner in which the password or other authorization input for altering the usage restriction settings at the restricted device described above allows the electronic device to provide an efficient manner (e.g., locally) to allow 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 the 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 that identifies one or more websites viewed on the first electronic device with the second electronic device (e.g., allowing or disallowing the authorized device to view names/identities of various websites viewed by a user of the restricted device (optionally, the authorized device is able to view total website viewing time as compared to total website viewing time, regardless of whether the restricted device allows or disallows sharing of individual website viewing shares), in a manner similar to the dialogs 1489-20 described above with reference to FIG. 14F) 18 years old) to control the sharing of this website view data, otherwise this data sharing cannot be controlled). In response to receiving input (1528) to allow or disallow sharing of website viewing activities with the second electronic device, in accordance with a determination that the input allows 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, such as in fig. 14M (e.g., the authorization device is able to view information (e.g., network address, title/name, etc.) of the various websites viewed by the user of the restricted device and/or the time it takes to view those various websites), in a manner similar to the allowing or disallowing described above with reference to fig. 14F); and in accordance with a determination that the input does not allow website viewing activity identifying the one or more websites viewed on the first electronic device to be shared with the second electronic device, the first electronic device relinquishes (1532) website viewing activity identifying the one or more websites viewed on the first electronic device to be shared with the second electronic device, such as in fig. 14K (e.g., the information (e.g., network address, title/name, etc.) of the various websites viewed by the user of the restricted device and/or the time it takes to view those various websites cannot be viewed by the authorized device).

The manner in which sharing of individualized website usage information is controlled described above allows the electronic device to provide an efficient way of maintaining privacy at a restricted device while still facilitating implementation of usage restrictions, which enhances operability of the device and makes the user-device interface more efficient (e.g., by allowing the user to interact with the device with fewer inputs), 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, upon setting up the website viewing activity enabled to disallow sharing with the second electronic device of the website viewing activity that identifies the one or more websites that have been viewed on the first electronic device, the first electronic device shares (1534) with the second electronic device website viewing activity 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 authorization device is unable to view individual website viewing information from the restricted device, the authorization device is able to view information about general network usage on the restricted device, such as the total amount of time spent on viewing websites on the restricted device, but is unable to view which websites are viewed, what periods of the day the websites are viewed, the duration of individual sessions in which websites are viewed, and/or the specific web pages or sub-domains that are viewed, and conversely, the amount of time the web site is used is aggregated with the application usage).

The manner in which generic network usage information continues to be shared with the authorization device described above allows the electronic device to provide an efficient way of enforcing usage restrictions even when individualized website usage information is not shared with the authorization 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 fewer inputs), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, upon setting up the website viewing activity enabled to disallow sharing with the second electronic device of the website viewing activity identifying the one or more websites already viewed on the first electronic device, the first electronic device shares (1536) with the second electronic device website viewing activity corresponding to the one or more applications or the one or more application categories, such as in fig. 14K (e.g., shares with the second electronic device aggregated statistics regarding usage of the first application and accessing of the website associated with the first application using the web browser and aggregated statistics regarding usage of the second application and accessing of the website associated with the second application using the web browser, 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 capable of viewing information regarding website network usage corresponding to an application (e.g., an ESPN website corresponding to an ESPN application views reflected on the authorizing device as usage of the ESPN application) or application category (e.g., a social media website corresponding to a social media application category views reflected on the authorizing device as usage of the application of the social media category). Further, in some embodiments, usage limits for those applications or categories are still imposed on the restricted device when applicable, such that website viewing on the restricted device is restricted when the viewing is restricted by the application/category limits that are valid on the restricted device, as described in

methods

700, 900, 1100, and/or 1300).

The manner in which website usage data corresponding to applications/application categories is reflected described above allows the electronic device to provide an efficient way of enforcing usage restrictions even when individualized 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 fewer inputs), which in turn reduces power usage and improves the 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 less than a predetermined age (e.g., 10, 13, 15 years), the second electronic device is prevented from removing (e.g., the second electronic device is not able to remove) a requirement that the altered usage restriction setting require authorization at the first electronic device (1538), such as in fig. 14O (e.g., the authorization device is not able to remove a requirement that the altered usage restriction setting on the restricted device require a password or other authorization credential or action to be provided at the restricted device (as approved by the authorization device). 10, 13, 15), the second electronic device is allowed to remove the requirement that the altered usage restriction settings require authorization at the first electronic device, such as in fig. 14N (e.g., the authorization device can remove the requirement that the altered usage restriction settings on the restricted device require a password or other authorization credential or action to be provided at the restricted device (as approved by the authorization device). In some embodiments, the authorization device is alternatively still able to alter the password or other authorization credential required at the restricted device to alter the usage restriction settings at the restricted device).

The manner in which the above-described controlled capability is provided for an authorization device for removing password requirements from a restricted device allows the electronic device to provide an efficient way of enforcing usage restrictions even when individualized website usage information is not shared with the authorization 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 fewer inputs), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, after the requirement that authorization be required at the first electronic device to change the usage restriction setting has been removed, the first electronic device and the second electronic device can change the usage restriction setting at the first electronic device, including the usage restriction setting (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, the authorization device or both the administrator account and the restricted device can change the limits and limits valid on the restricted device).

The manner described above that allows both the limited device and the authorized device to make changes to the usage 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 usage restriction settings on the limited 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 fewer inputs), which in turn reduces power usage and improves the 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 can cease sharing device usage information with the second electronic device (1544), such as in fig. 14R-14T (e.g., the limited device can cease the ability of the authorization device or the administrator account to view usage information regarding the limited device; in some embodiments, the limited device can be disassociated from the authorization device and the usage limit settings at the limited device can be closed or otherwise adjusted independently of any authorization from the authorization 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 the predetermined age, the second electronic device cannot cease sharing device usage information with the second electronic device (1546), such as in fig. 14B (e.g., the limited device cannot stop the ability of the authorized device or the administrator account to view usage information about the limited device).

The manner described above of controlling when a restricted device can cease sharing usage information with an authorized device allows the 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 the user to interact with the device with fewer inputs), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

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 restricted device cannot cease sharing usage information with the authorized device without approval from the authorized device or an administrator account.

The manner described above in which authorization device approval is required for cessation of usage information sharing with an authorization device allows the electronic device to provide an efficient way for the authorization device to control such changes, 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 the battery life of the device by enabling the user to use the device more quickly and efficiently.

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 limited device can cease sharing usage information with the authorized device without approval from the authorized device or an administrator account.

The manner described above in which authorized device approval is not required for decommissioning information sharing allows the electronic device 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 the 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 can cease sharing device usage information with the second electronic device, such as in fig. 14Q (e.g., the limited device displays the notification when the user of the limited device reaches an age at which the user can cease sharing usage information with the authorized device so that the user knows that they can now take such action).

The manner in which notifications are generated for a user of a restricted device when the user is able to alter the sharing of information with authorized devices described above allows the electronic device to provide an efficient way of facilitating 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 the 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, the control for ceasing to share device usage information with the second electronic device is available on the first electronic device (1554), such as in fig. 14R-14S (e.g., the affordance, button, or control for altering sharing of usage information with the authorized device is displayed and enabled in the usage-restriction-setting user interface on the 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 the predetermined age, the control for ceasing to share device usage information with the second electronic device is not available on the first electronic device (1556), such as in fig. 14B (e.g., the affordance, button, or control for altering sharing of usage information with the authorized device is not displayed in the usage-restriction-setting user interface on the restricted device, or displayed in a usage restriction settings user interface on a restricted device but not enabled (e.g., grayed out)).

The manner in which the controls for changing information sharing with an authorized device described above are made available or unavailable allows the electronic device to provide an efficient manner of facilitating such changes while complying with the limitations on the ability to make such changes, 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 the battery life of the device by enabling the user to use the device more quickly and efficiently.

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; receiving (1560), by the first electronic device, an input to cease 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 the 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., the user of the restricted device selects a button or toggle key in the usage restriction settings user interface to cease sharing usage information with the authorized device). In some embodiments, after ceasing to share the device usage information with the second electronic device, the first electronic device is able to change the usage restriction settings on the first electronic device, and the second electronic device is unable to change the usage restriction settings on the first electronic device in a manner similar to that described above with reference to FIG. 14G (1564) (e.g., once the usage information sharing and/or usage restriction sharing with the authorizing device or administrator account has been disabled, the previously restricted device is able to modify the usage restriction settings on the previously restricted device, but the authorizing device or administrator account is no longer able to modify such settings on the previously restricted device.

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

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) via the one or more input devices a sequence of one or more inputs for changing the one or more usage restriction settings on the first electronic device (e.g., after receiving approval from the authorizing device to change the usage restriction settings on the restricted device, the 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 a device downtime setting valid on the restricted device, etc.)); and 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 to the second electronic device regarding the alteration of the one or more usage restriction settings on the first electronic device, such as in fig. 14I (e.g., the restricted device transmits information to the authorization device or an administrator account regarding all changes attempted by the restricted device to the usage restriction settings (e.g., information regarding all changes attempted at the restricted device, such as a particular usage limit change, a particular device downtime change, etc.). in some embodiments, the restricted device makes the alteration of the restricted usage settings and transmits information regarding the alteration to the authorization device in conjunction with making the alteration, the authorization device optionally displays a notification of the alteration, enabling a user of the authorized device to see the changes made on the restricted device; in such embodiments, the notification optionally does not have a mechanism by which the user of the device is authorized to be able to cancel, reject or invalidate the change made by the restricted device. Rather, 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 use settings, and information regarding the attempted changes is first transmitted to the authorizing device, which optionally displays a notification of the attempted changes so that the user of the authorizing device can see the changes intended to be made on the restricted device; in such embodiments, the notification optionally has a mechanism (e.g., a selectable affordance) that authorizes the user of the device to be able to cancel/reject/invalidate or approve the change that the restricted device is attempting to make).

The manner in which information regarding usage restriction changes is transmitted to an authorized device described above allows the electronic device to efficiently communicate such changes to the authorized 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 the 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 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 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 change of the one or more usage restriction settings at the first electronic device by the second electronic device, such as in fig. 14P (e.g., the limited device receives information from the authorizing device regarding updates to the usage restriction settings on the limited device that the authorizing device has made, and in response, the limited device displays a notification with details of the change (e.g., changes to usage limits, device downtime, etc.) on the limited device so that the user of the limited device can see the change made by the authorizing device).

The manner of displaying a notification at a restricted device with usage restriction changes by an authorized device described above allows the electronic device to provide an efficient way to provide such changed information to a user of the restricted device, which enhances 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, the one or more usage restriction settings at the first electronic device being remotely altered includes defining initial usage restriction settings at the first electronic device when no previous usage restriction settings were valid at the first electronic device (1574), such as in fig. 14A (e.g., the restricted device receives information from the authorization device or an administrator account regarding those restrictions that the authorization device was validated on the restricted device when the authorization device validated the initial usage restrictions, and in response, the restricted device displays a notification on the restricted device with details of those initial restrictions (e.g., usage limits, device downtime, etc.) so that a user of the restricted device can see the usage restrictions that are now valid on the restricted device. Each usage limit, each characteristic of equipment down time, etc.). In some embodiments, the notification instead includes a summary of the key restrictions that are now in effect on the restricted device, such as the total limit of the game (rather than the limits of the individual games), the total limit of the screen time (rather than the individual limits of the screen time), the start and stop times of the device downtime (rather than also including exceptions to the device downtime definition by the authorized device), and so forth).

The manner of displaying a notification at a limited device with initial usage limit settings by an authorized device described above allows the electronic device to provide an efficient way to provide information of such settings to a user of the limited device, which enhances operability of the device and makes the user-device interface more efficient (e.g., by allowing the user to interact with the device with fewer inputs), 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 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 order described is the only order in which the operations may be performed. One of ordinary skill in the art will recognize a variety of ways to reorder the operations described herein. Additionally, it should be noted that 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 method of updating a restriction setting at one electronic device with permission of another electronic device or user account described above with reference to method 1500, usage restriction setting, etc., optionally has one or more of the characteristics of the usage metric dashboard user interface, usage metric, notification metric, pick-up device metric, usage restriction setting, 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 conjunction with fig. 1A-1B, fig. 3, fig. 5A-5H) or an application-specific chip. Further, the operations described above with reference to fig. 15A-15G are optionally performed by the components depicted in fig. 1A-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 recognizer 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 calls data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update the content displayed by the application. Similarly, one of ordinary skill in the art will clearly know 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 a variety of sources to control and/or present device usage information to a user. The present disclosure contemplates that, in some instances, 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, phone numbers, email addresses, twitter IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying or personal information.

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

The present disclosure contemplates that entities responsible for collecting, analyzing, publishing, transmitting, storing, or otherwise using such personal information data will comply with established privacy policies and/or privacy practices. In particular, such entities should enforce and adhere to the use of privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as data collection and/or usage changes. Personal information from the user should be collected for legitimate and legitimate uses by the entity and not shared or sold outside of these legitimate uses. Furthermore, such acquisition/sharing should be done after receiving the user's informed consent. Furthermore, such entities should consider taking any necessary steps to defend and secure access to such personal information data and to ensure that others who have access to the personal information data comply with 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 the particular type of personal information data collected and/or accessed, and to 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 laws, such as the health insurance transfer and accountability act (HIPAA); while other countries may have health data subject to other regulations and policies and should be treated accordingly. Therefore, different privacy practices should be maintained for different personal data types in each country.

Regardless 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 technology may be configured to allow a user to opt-in to "join" or "opt-out of" participating in the collection of personal information data during the registration 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 "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 their personal information data is to 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, the risk can be minimized by limiting data collection and deleting data. In addition, and when applicable, including in certain health-related applications, data de-identification may be used to protect the privacy of the user. De-identification may be facilitated by removing particular identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at a city level rather than 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 various embodiments may be implemented without the need to access 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 an absolute minimum amount of personal information (such as content requested by a device associated with the user, other non-personal information available to the device, or publicly available information).

The foregoing description, for purpose 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 applications, to thereby enable others skilled in the art to best utilize the invention and various embodiments described, 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:

receiving, via the one or more input devices, a sequence of one or more inputs that set usage limits associated with a first application category accessible on the electronic device;

while the usage limit associated with the first application class is valid:

receiving a request to launch a first application of the first application category;

in accordance with a determination that a first constraint for the first application category has been satisfied, restricting access to the first application of the first application category, wherein the first constraint comprises requiring that the usage limit for the first application category has been reached for the first constraint to be satisfied:

in accordance with a determination that the first application does not satisfy one or more restrictive exception conditions, restricting access to the first application; and

in accordance with a determination that the first application satisfies the one or more restricted exception conditions, providing access to the first application;

in accordance with a determination that the first constraint has not been met, providing access to the first application; and

When the first application is used, counting usage of the first application toward a usage limit associated with the first application category independent of whether the first application satisfies the one or more restricted exception conditions.

2. The method of claim 1, further comprising:

in accordance with a determination that the constraint for the first application category has not been met, displaying a first representation of the first application with a first visual characteristic; and

in accordance with a determination that the constraint for the first application category has been met, displaying the first representation of the first application with a second visual characteristic different from the first visual characteristic.

3. The method of claim 2, wherein displaying the first representation of the first application with the second visual characteristic comprises displaying a restricted-use indicator on the first representation, the restricted-use indicator comprising an indication that access to the first application is restricted.

4. The method of claim 3, wherein:

displaying the first representation of the first application with the first visual characteristic comprises displaying the first representation with a notification indicator comprising an indication of a notification received at the first application; and

Displaying the first representation of the first application with the second visual characteristic includes displaying the first representation that the notification indicator has been replaced by the limited-use indicator.

5. The method of claim 1, wherein the usage limit is a first usage limit associated with the first application class for one or more first enforcement time periods, and further comprising:

receiving, via the one or more input devices, a sequence of one or more second inputs that set a second usage limit associated with the first application class for one or more second enforcement time periods;

in accordance with a determination that the current time is within the one or more first implementation time periods, implementing the first usage limit; and

in accordance with a determination that the current time is within the one or more second implementation time periods, implementing the second usage limit.

6. The method of claim 1, further comprising:

receiving, via the one or more input devices, input corresponding to a request to exclude a second application of the first application category from the usage limits for the first application category; and

After receiving the input corresponding to the request for excluding the second application from the usage limit and when the restriction condition for the first application category is satisfied:

receiving a request to launch the second application; and

providing access to the second application in response to receiving the request to launch the second application.

7. The method of claim 1, wherein the usage limit is further associated with a second category of applications accessible on the electronic device, the second category of applications including applications that are different from applications of the first category of applications.

8. The method of claim 1, wherein the first application category includes all applications accessible on the electronic device.

9. The method of claim 1, wherein the usage limit associated with the first application class has a first usage limit name based on one or more classification criteria, and further comprising:

receiving a sequence of one or more second inputs weighing and naming the usage limit names as second usage limit names; and

Renaming the usage limit name to the second usage limit name in response to the sequence of one or more second inputs.

10. The method of claim 1, further comprising:

when the constraint for the first application class is satisfied:

detecting an event corresponding to activation of an auxiliary function of the first application, wherein the auxiliary function of the first application is a function available 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 secondary function of the first application, suppressing the secondary function.

11. The method of claim 1, further comprising:

adding access to a second application on the electronic device from an application source, wherein the application source associates the second application with a respective application category;

in accordance with a determination that the respective application category is the first application category, controlling access to the second application in accordance with the restriction condition for the first application category; and

in accordance with a determination that the respective application category is not the first application category, forgoing controlling access to the second application in accordance with the restriction condition for the first application category.

12. The method of claim 1, wherein one or more time windows associated with a restricted usage mode during which access to one or more applications on the electronic device is restricted are defined on the electronic device, the method further comprising:

in accordance with a determination that the request to launch the first application is received while 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, restricting access to the first application regardless of whether a restriction condition for the first application category has been satisfied.

13. The method of claim 1, wherein restricting access to the first application comprises:

presenting an indication indicating that access to the first application is restricted, wherein the indication comprises an affordance selectable to provide access to the first application without requiring authentication credentials.

14. The method of claim 1, wherein restricting access to the first application comprises:

Presenting an indication indicating that access to the first application is restricted, wherein the indication comprises an affordance selectable to provide access to the first application while requiring authentication credentials.

15. The method of claim 14, wherein:

in accordance with a determination that the electronic device is not a child device, selection of the affordance causes a request to be entered for a password for accessing the first application; and

in accordance with a determination that the electronic device is a child device, selection of the affordance causes the display to present a first affordance that requires entry of a password to access the first application and, when selected, initiates a process that requests access to the first application from a parent device.

16. The method of claim 1, further comprising:

displaying an indication that the usage limit of the usage threshold has been reached in accordance with the determination that the usage limit of the alert threshold has been reached when the usage limit associated with the first application class is valid.

17. The method of claim 1, further comprising:

receiving one or more inputs for altering one or more usage limit settings associated with the usage limits; and

In response to receiving the one or more inputs for altering the one or more usage limit settings:

in accordance with a determination that the one or more inputs to alter the one or more usage limit settings are received via the one or more input devices of the electronic device and that the electronic device is a child device, requiring authorization prior to performing the alteration of the one or more usage limit settings; and

in accordance with a determination that the one or more inputs to alter the one or more usage limit settings are received via a parent device from outside the electronic device, performing an alteration of the one or more usage limit settings.

18. The method of claim 17, further comprising:

presenting an indication of the change to the one or more usage limit settings in response to performing the change to the one or more usage limit settings received from outside the electronic device.

19. The method of claim 17, wherein:

generating one or more inputs received from a parent device other than the electronic device to alter one or more usage limit settings requires an authentication certificate to be input at the parent device to make the alteration to the usage limit settings on the electronic device.

20. The method of claim 1, wherein the first application is simultaneously associated with:

a usage limit associated with the first application class, an

A second use limit.

21. The method of claim 20, wherein the first application is associated with a second constraint, the second constraint comprising a requirement that: in order to satisfy the second limitation condition having reached the usage limit of the first application or in order to satisfy the second limitation condition having reached the second usage limit, the method further comprises:

in accordance with a determination that the second limiting condition is satisfied, limiting access to the first application; and

in accordance with a determination that the second constraint is not satisfied, providing access to the first application.

22. 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 including instructions for:

receiving, via one or more input devices, a sequence of one or more inputs that set usage limits associated with a first category of applications accessible on the electronic device;

While the usage limit associated with the first application class is valid:

23. The electronic device of claim 22, wherein the one or more programs further include instructions for:

24. The electronic device of claim 23, wherein displaying the first representation of the first application with the second visual characteristic comprises displaying a restricted-use indicator on the first representation, the restricted-use indicator comprising an indication that access to the first application is restricted.

25. The electronic device of claim 24, wherein:

26. The electronic device of claim 22, wherein the usage limit is a first usage limit associated with the first application class for one or more first enforcement time periods, and the one or more programs further include instructions to:

27. The electronic device of claim 22, wherein the one or more programs further include instructions for:

receiving a request to launch the second application; and

28. The electronic device of claim 22, wherein the usage limit is further associated with a second category of applications accessible on the electronic device, the second category of applications including applications that are different from applications of the first category of applications.

29. The electronic device of claim 22, wherein the first application category includes all applications accessible on the electronic device.

30. The electronic device of claim 22, wherein the usage limit associated with the first application class has a first usage limit name based on one or more classification criteria, and the one or more programs further include instructions for:

31. The electronic device of claim 22, wherein the first application is simultaneously associated with:

a usage limit associated with the first application class, an

A second use limit.

32. The electronic device of claim 31, wherein the first application is associated with a second restriction, the second restriction comprising a requirement that: in order to satisfy the second limitation condition having reached the usage limit of the first application or in order to satisfy the second limitation condition having reached the second usage limit, the one or more programs further include instructions for:

33. The electronic device of claim 22, wherein the one or more programs further include instructions for:

When the constraint for the first application class is satisfied:

34. The electronic device of claim 22, wherein the one or more programs further include instructions for:

35. The electronic device of claim 22, wherein one or more time windows associated with a limited use mode during which access to one or more applications on the electronic device is limited are defined on the electronic device, the one or more programs further comprising instructions for:

36. The electronic device of claim 22, wherein restricting access to the first application comprises:

37. The electronic device of claim 22, wherein restricting access to the first application comprises:

38. The electronic device of claim 37, wherein:

in accordance with a determination that the electronic device is a child device, selection of the affordance causes a display to present a first affordance that requires entry of a password to access the first application and, when selected, initiates a process that requests access to the first application from a parent device.

39. The electronic device of claim 22, further comprising:

40. The electronic device of claim 22, wherein the one or more programs further include instructions for:

41. The electronic device of claim 40, wherein the one or more programs further include instructions for:

42. The electronic device of claim 40, wherein:

43. 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 an electronic device, cause the electronic device to perform operations comprising:

while the usage limit associated with the first application class is valid:

44. The non-transitory computer readable storage medium of claim 43, wherein the one or more programs further cause the electronic device to:

45. The non-transitory computer-readable storage medium of claim 44, wherein displaying the first representation of the first application with the second visual characteristic includes displaying a restricted-use indicator on the first representation, the restricted-use indicator including an indication that access to the first application is restricted.

46. The non-transitory computer-readable storage medium of claim 45, wherein:

47. The non-transitory computer readable storage medium of claim 43, wherein the usage limit is a first usage limit associated with the first application category over one or more first enforcement time periods, and the one or more programs further cause the electronic device to:

48. The non-transitory computer readable storage medium of claim 43, wherein the one or more programs further cause the electronic device to:

receiving a request to launch the second application; and

49. The non-transitory computer-readable storage medium of claim 43, wherein the usage limit is further associated with a second category of applications accessible on the electronic device, the second category of applications including applications that are different from applications of the first category of applications.

50. The non-transitory computer-readable storage medium of claim 43, wherein the first application category includes all applications accessible on the electronic device.

51. The non-transitory computer readable storage medium of claim 43, wherein the usage limit associated with the first application category has a first usage limit name based on one or more classification criteria, and the one or more programs further cause the electronic device to:

52. The non-transitory computer-readable storage medium of claim 43, wherein the first application is simultaneously associated with:

a usage limit associated with the first application class, an

A second use limit.

53. The non-transitory computer-readable storage medium of claim 52, wherein the first application is associated with a second constraint, the second constraint comprising a requirement that: in order to satisfy the second limitation condition having reached the usage limit of the first application program or in order to satisfy the second limitation condition having reached the second usage limit, the one or more programs further cause the electronic device to:

54. The non-transitory computer readable storage medium of claim 43, wherein the one or more programs further cause the electronic device to:

when the constraint for the first application class is satisfied:

55. The non-transitory computer readable storage medium of claim 43, wherein the one or more programs further cause the electronic device to:

56. The non-transitory computer readable storage medium of claim 43, wherein one or more time windows associated with a restricted usage mode during which access to one or more applications on the electronic device is restricted are defined on the electronic device, wherein the one or more programs further cause the electronic device to:

57. The non-transitory computer-readable storage medium of claim 43, wherein restricting access to the first application comprises:

58. The non-transitory computer-readable storage medium of claim 43, wherein restricting access to the first application comprises:

59. The non-transitory computer-readable storage medium of claim 58, wherein:

60. The non-transitory computer-readable storage medium of claim 43, further comprising:

61. The non-transitory computer readable storage medium of claim 43, wherein the one or more programs further cause the electronic device to:

62. The non-transitory computer readable storage medium of claim 61, wherein the one or more programs further cause the electronic device to:

63. The non-transitory computer-readable storage medium of claim 61, wherein: