User interface for logging user activities

Abstract

The invention relates to a user interface for logging user activities. The present disclosure generally relates to logging user activity during a subset of loop time periods. In some embodiments, based on the received physiological data, the computer system enables logging of one or more user activities to be performed during a subset of the cycle periods. In some embodiments, based on execution of the one or more user activities during the subset of the loop periods, the computer system enables logging of the one or more user activities to be performed during the subset of the loop periods for a predetermined period of time.

Description

[0001] This application is a divisional application of the Chinese invention patent application with the filing date of August 31, 2021, the national application number 202180053264.1, and the invention name “User interface for logging user activities”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This patent application claims priority to U.S. Provisional Application Serial No. 63 / 072,889, entitled “USER INTERFACES FOR LOGGING USER ACTIVITIES,” filed on August 31, 2020, and U.S. Non-Provisional Application Serial No. 16 / 953,781, entitled “USER INTERFACES FOR LOGGING USER ACTIVITIES,” filed on November 20, 2020. The contents of these patent applications are hereby incorporated by reference herein in their entirety for all purposes. Technical Field

[0004] The present disclosure relates generally to computer user interfaces and, more particularly, to techniques for logging user activity during subsets of recurring time periods. Background Art

[0005] The computer system may include an application for logging user activity during a subset of the recurring time periods. Such systems may receive user input using a user interface including one or more graphical elements suitable for use with logging user activity during a subset of the recurring time periods. Summary of the invention

[0006] However, some techniques for logging user activities during a subset of recurring time periods using an electronic device are often cumbersome and inefficient. For example, some prior art techniques use complex and time-consuming user interfaces that may include multiple keystrokes or keystrokes. Prior art techniques require more time than necessary, which results in wasted user time and device energy. This latter consideration is particularly important in battery-powered devices.

[0007] Therefore, the present technology provides a faster, more efficient method and interface for electronic devices to log user activities during a subset of recurring time periods. Such methods and interfaces optionally supplement or replace other methods for logging user activities during a subset of recurring time periods. Such methods and interfaces reduce the cognitive burden imposed on users and produce a more efficient human-computer interface. For battery-powered computing devices, such methods and interfaces save power and increase the time interval between battery charges.

[0008] According to some embodiments, a method performed at a computer system in communication with a display generation component and one or more input devices is described. The method includes: displaying, via the display generation component, a task selection user interface having a set of one or more selectable task user interface objects, the set of one or more selectable task user interface objects including a first selectable task user interface object corresponding to a first type of user activity to be performed during the first subset of the recurring time periods based on determining that physiological data of a first subset of the recurring time periods meets a first set of criteria; and the set of one or more selectable task user interface objects including a second selectable task user interface object corresponding to a second type of user activity to be performed during the second subset of the recurring time periods based on determining that physiological data of a second subset of the recurring time periods different from the first subset of the recurring time periods meets the first set of criteria; receiving, via the one or more input devices, a first set of one or more inputs while displaying the task selection user interface; and in response to receiving the first set of one or more inputs: enabling logging of the first type of user activity during the first subset of the recurring time periods based on determining that the first set of one or more inputs includes input selecting the first selectable task user interface object; and enabling logging of the second type of user activity during the second subset of the recurring time periods based on determining that the first set of one or more inputs includes input selecting the second selectable task user interface object.

[0009] According to some embodiments, a non-transitory computer-readable storage medium is described that stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices. The one or more programs include instructions for: displaying, via the display generation component, a task selection user interface having a set of one or more selectable task user interface objects, the set of one or more selectable task user interface objects including a first selectable task user interface object corresponding to a first type of user activity to be performed during the first subset of recurring time periods based on determining that physiological data for a first subset of recurring time periods meets a first set of criteria; and the set of one or more selectable task user interface objects including a second selectable task user interface object corresponding to a second type of user activity to be performed during the second subset of recurring time periods based on determining that physiological data for a second subset of the recurring time periods different from the first subset of recurring time periods meets the first set of criteria; receiving, via the one or more input devices, a first set of one or more inputs while displaying the task selection user interface; and in response to receiving the first set of one or more inputs: enabling logging of the first type of user activity during the first subset of the recurring time periods based on determining that the first set of one or more inputs includes input selecting the first selectable task user interface object; and enabling logging of the second type of user activity during the second subset of the recurring time periods based on determining that the first set of one or more inputs includes input selecting the second selectable task user interface object.

[0010] According to some embodiments, a transient computer-readable storage medium is described that stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices. The one or more programs include instructions for: displaying, via the display generation component, a task selection user interface having a set of one or more selectable task user interface objects, the set of one or more selectable task user interface objects including a first selectable task user interface object corresponding to a first type of user activity to be performed during the first subset of recurring time periods based on determining that physiological data for a first subset of recurring time periods meets a first set of criteria; and the set of one or more selectable task user interface objects including a second selectable task user interface object corresponding to a second type of user activity to be performed during the second subset of recurring time periods based on determining that physiological data for a second subset of the recurring time periods different from the first subset of recurring time periods meets the first set of criteria; receiving, via the one or more input devices, a first set of one or more inputs while displaying the task selection user interface; and in response to receiving the first set of one or more inputs: enabling logging of the first type of user activity during the first subset of the recurring time periods based on determining that the first set of one or more inputs includes input selecting the first selectable task user interface object; and enabling logging of the second type of user activity during the second subset of the recurring time periods based on determining that the first set of one or more inputs includes input selecting the second selectable task user interface object.

[0011] According to some embodiments, a computer system is described. The computer system includes: a display generation component; one or more input devices; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for: displaying, via the display generation component, a task selection user interface having a set of one or more selectable task user interface objects, the set of one or more selectable task user interface objects including a first selectable task user interface object corresponding to a first type of user activity to be performed during the first subset of recurring time periods based on determining that physiological data for a first subset of recurring time periods meets a first set of criteria; and the set of one or more selectable task user interface objects including a second selectable task user interface object corresponding to a second type of user activity to be performed during the second subset of recurring time periods based on determining that physiological data for a second subset of the recurring time periods different from the first subset of recurring time periods meets the first set of criteria; receiving, via the one or more input devices, a first set of one or more inputs while displaying the task selection user interface; and in response to receiving the first set of one or more inputs: enabling logging of the first type of user activity during the first subset of the recurring time periods based on determining that the first set of one or more inputs includes input selecting the first selectable task user interface object; and enabling logging of the second type of user activity during the second subset of the recurring time periods based on determining that the first set of one or more inputs includes input selecting the second selectable task user interface object.

[0012] According to some embodiments, a computer system is described that includes a display generation component and one or more input devices. The computer system also includes: means for displaying, via the display generation component, a task selection user interface having a set of one or more selectable task user interface objects, the set of one or more selectable task user interface objects including a first selectable task user interface object corresponding to a first type of user activity to be performed during the first subset of the recurring time periods based on determining that the physiological data of a first subset of the recurring time periods meets a first set of criteria; and the set of one or more selectable task user interface objects including a second selectable task user interface object corresponding to a second type of user activity to be performed during the second subset of the recurring time periods based on determining that the physiological data of a second subset of the recurring time periods different from the first subset of the recurring time periods meets the first set of criteria; means for receiving, via the one or more input devices, a first set of one or more inputs while displaying the task selection user interface; and means for performing the following operations in response to receiving the first set of one or more inputs: enabling logging of the first type of user activity during the first subset of the recurring time periods based on determining that the first set of one or more inputs includes input selecting the first selectable task user interface object; and enabling logging of the second type of user activity during the second subset of the recurring time periods based on determining that the first set of one or more inputs includes input selecting the second selectable task user interface object.

[0013] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices. The one or more programs include instructions for: displaying, via the display generation component, a task selection user interface having a set of one or more selectable task user interface objects, the set of one or more selectable task user interface objects including a first selectable task user interface object corresponding to a first type of user activity to be performed during the first subset of recurring time periods based on determining that physiological data for a first subset of recurring time periods meets a first set of criteria; and the set of one or more selectable task user interface objects including a second selectable task user interface object corresponding to a second type of user activity to be performed during the second subset of recurring time periods based on determining that physiological data for a second subset of the recurring time periods different from the first subset of recurring time periods meets the first set of criteria; receiving, via the one or more input devices, a first set of one or more inputs while displaying the task selection user interface; and in response to receiving the first set of one or more inputs: enabling logging of the first type of user activity during the first subset of the recurring time periods based on determining that the first set of one or more inputs includes input selecting the first selectable task user interface object; and enabling logging of the second type of user activity during the second subset of the recurring time periods based on determining that the first set of one or more inputs includes input selecting the second selectable task user interface object.

[0014] According to some embodiments, a method performed at a computer system in communication with a display generation component and one or more input devices is described. The method includes: displaying a target creation user interface having a set of one or more selectable target creation user interface objects via the display generation component, wherein based on determining that a first type of user activity performed within a first subset of a recurring time period satisfies a first set of criteria, the set of one or more selectable target creation user interface objects includes a first selectable target creation user interface object corresponding to the first type of user activity to be performed during the first subset of the recurring time period; and based on determining that a second type of user activity performed within a second subset of the recurring time period that is different from the first subset of the recurring time period satisfies the first set of criteria, the set of one or more selectable target creation user interface objects includes a first selectable target creation user interface object corresponding to the first type of user activity to be performed during the first subset of the recurring time period. creating a second selectable target user interface object for the second type of user activity performed during the second subset of the recurring time period; receiving a first set of one or more inputs while displaying the target creation user interface; and in response to receiving the first set of one or more inputs: based on determining that the first set of one or more inputs includes input for selecting the first selectable target user interface object, enabling logging of the first type of user activity during the first subset of the recurring time period for a predetermined duration; and based on determining that the first set of one or more inputs includes input for selecting the second selectable target user interface object, enabling logging of the second type of user activity during the second subset of the recurring time period for the predetermined duration.

[0015] According to some embodiments, a non-transitory computer-readable storage medium is described, which stores one or more programs configured to be executed by one or more processors of a computer system that communicates with a display generation component and one or more input devices. The one or more programs include instructions for performing the following operations: displaying a target creation user interface having a set of one or more selectable target creation user interface objects via the display generation component, based on determining that a first type of user activity performed within a first subset of a recurring time period meets a first set of criteria, the set of one or more selectable target creation user interface objects includes a first selectable target creation user interface object corresponding to the first type of user activity to be performed during the first subset of the recurring time period; and based on determining that a second type of user activity performed within a second subset of the recurring time period different from the first subset of the recurring time period meets the first set of criteria, the set of one or more selectable target creation user interface objects includes a first selectable target creation user interface object corresponding to the first type of user activity to be performed during the first subset of the recurring time period. creating a second selectable target user interface object for the second type of user activity performed during the second subset of the recurring time periods; receiving a first set of one or more inputs while displaying the target creation user interface; and in response to receiving the first set of one or more inputs: enabling logging of the first type of user activity during the first subset of the recurring time periods for a predetermined duration based on determining that the first set of one or more inputs includes input for selecting the first selectable target user interface object; and enabling logging of the second type of user activity during the second subset of the recurring time periods for the predetermined duration based on determining that the first set of one or more inputs includes input for selecting the second selectable target user interface object.

[0016] According to some embodiments, a transient computer-readable storage medium is described that stores one or more programs configured to be executed by one or more processors of a computer system that communicates with a display generation component and one or more input devices. The one or more programs include instructions for performing the following operations: displaying a target creation user interface having a set of one or more selectable target creation user interface objects via the display generation component, based on determining that a first type of user activity performed within a first subset of a recurring time period meets a first set of criteria, the set of one or more selectable target creation user interface objects includes a first selectable target creation user interface object corresponding to the first type of user activity to be performed during the first subset of the recurring time period; and based on determining that a second type of user activity performed within a second subset of the recurring time period different from the first subset of the recurring time period meets the first set of criteria, the set of one or more selectable target creation user interface objects includes a first selectable target creation user interface object corresponding to the first type of user activity to be performed during the first subset of the recurring time period. creating a second selectable target user interface object for the second type of user activity performed during the second subset of the recurring time periods; receiving a first set of one or more inputs while displaying the target creation user interface; and in response to receiving the first set of one or more inputs: enabling logging of the first type of user activity during the first subset of the recurring time periods for a predetermined duration based on determining that the first set of one or more inputs includes input for selecting the first selectable target user interface object; and enabling logging of the second type of user activity during the second subset of the recurring time periods for the predetermined duration based on determining that the first set of one or more inputs includes input for selecting the second selectable target user interface object.

[0017] According to some embodiments, a computer system is described. The computer system includes: a display generation component; one or more input devices; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for performing the following operations: displaying a target creation user interface having a set of one or more selectable target creation user interface objects via the display generation component, based on determining that a first type of user activity performed within a first subset of a recurring time period meets a first set of criteria, the set of one or more selectable target creation user interface objects includes a first selectable target creation user interface object corresponding to the first type of user activity to be performed during the first subset of the recurring time period; and based on determining that a second type of user activity performed within a second subset of the recurring time period different from the first subset of the recurring time period meets the first set of criteria, the set of one or more selectable target creation user interface objects includes a first selectable target creation user interface object corresponding to the first type of user activity to be performed during the first subset of the recurring time period. creating a second selectable target user interface object for the second type of user activity performed during the second subset of the recurring time periods; receiving a first set of one or more inputs while displaying the target creation user interface; and in response to receiving the first set of one or more inputs: enabling logging of the first type of user activity during the first subset of the recurring time periods for a predetermined duration based on determining that the first set of one or more inputs includes input for selecting the first selectable target user interface object; and enabling logging of the second type of user activity during the second subset of the recurring time periods for the predetermined duration based on determining that the first set of one or more inputs includes input for selecting the second selectable target user interface object.

[0018] According to some embodiments, a computer system including a display generation component and one or more input devices is described. The computer system also includes: a device for displaying a target creation user interface having a set of one or more selectable target creation user interface objects via the display generation component, wherein based on determining that a first type of user activity performed within a first subset of a recurring time period satisfies a first set of criteria, the set of one or more selectable target creation user interface objects includes a first selectable target creation user interface object corresponding to the first type of user activity to be performed during the first subset of the recurring time period; and based on determining that a second type of user activity performed within a second subset of the recurring time period that is different from the first subset of the recurring time period satisfies the first set of criteria, the set of one or more selectable target creation user interface objects includes a first selectable target creation user interface object corresponding to the second type of user activity to be performed during the second subset of the recurring time period. A second selectable target creation user interface object for performing the second type of user activity; a device for receiving a first set of one or more inputs when displaying the target creation user interface; and a device for performing the following operations in response to receiving the first set of one or more inputs: based on determining that the first set of one or more inputs includes an input for selecting the first selectable target user interface object, enabling logging of the first type of user activity during the first subset of the recurring time period for a predetermined duration; and based on determining that the first set of one or more inputs includes an input for selecting the second selectable target creation user interface object, enabling logging of the second type of user activity during the second subset of the recurring time period for the predetermined duration.

[0019] According to some embodiments, a computer program product is described. The computer program product includes: one or more programs configured to be executed by one or more processors of a computer system that communicates with a display generation component and one or more input devices. The one or more programs include instructions for performing the following operations: displaying a target creation user interface having a set of one or more selectable target creation user interface objects via the display generation component, based on determining that a first type of user activity performed within a first subset of a recurring time period meets a first set of criteria, the set of one or more selectable target creation user interface objects includes a first selectable target creation user interface object corresponding to the first type of user activity to be performed during the first subset of the recurring time period; and based on determining that a second type of user activity performed within a second subset of the recurring time period different from the first subset of the recurring time period meets the first set of criteria, the set of one or more selectable target creation user interface objects includes a first selectable target creation user interface object corresponding to the first type of user activity to be performed during the first subset of the recurring time period. creating a second selectable target user interface object for the second type of user activity performed during the second subset of the recurring time periods; receiving a first set of one or more inputs while displaying the target creation user interface; and in response to receiving the first set of one or more inputs: enabling logging of the first type of user activity during the first subset of the recurring time periods for a predetermined duration based on determining that the first set of one or more inputs includes input for selecting the first selectable target user interface object; and enabling logging of the second type of user activity during the second subset of the recurring time periods for the predetermined duration based on determining that the first set of one or more inputs includes input for selecting the second selectable target user interface object.

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

[0021] Thus, a faster, more efficient method and interface is provided for devices to log user activity during a subset of recurring time periods, thereby improving the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may supplement or replace other methods for logging user activity during a subset of recurring time periods. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] 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, wherein like reference numerals designate corresponding parts throughout the several views.

[0023] Figure 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display according to some embodiments.

[0024] Figure 1B is a block diagram illustrating example components for event processing according to some embodiments.

[0025] Figure 2 A portable multifunction device with a touch screen according to some embodiments is shown.

[0026] Figure 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments.

[0027] Figure 4A An exemplary user interface for a menu of applications on a portable multifunction device is shown according to some embodiments.

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

[0029] Figure 5A A personal electronic device according to some embodiments is shown.

[0030] Figure 5B is a block diagram illustrating a personal electronic device according to some embodiments.

[0031] Figures 6A to 6AL An exemplary user interface for logging user activity during a subset of recurring time periods is shown according to some embodiments.

[0032] Figure 7 is a flowchart illustrating a method for logging user activity during a subset of recurring time periods according to some embodiments.

[0033] FIG. 8A to FIG. 8B is a flowchart illustrating a method for logging user activity during a subset of recurring time periods according to some embodiments. DETAILED DESCRIPTION

[0034] The following description sets forth exemplary methods, parameters, etc. However, it should be appreciated that such description is not intended to limit the scope of the present disclosure, but is provided as a description of exemplary embodiments.

[0035] There is a need for electronic devices that provide an effective method and interface for logging user activities during a subset of recurring time periods. In addition, the electronic device should provide a display of the logged user activities during the subset of recurring time periods along with other user data so that the user can determine the effect of performing the user activities. Such techniques can reduce the cognitive burden on users who log user activities during the subset of recurring time periods, thereby improving productivity. In addition, such techniques can reduce processor power and battery power that would otherwise be wasted on redundant user input.

[0036] under Figure 1A to Figure 1B , Figure 2 , Figure 3 , FIG. 4A to FIG. 4B and FIG. 5A to FIG. 5B A description of an exemplary device for performing techniques for management event notifications is provided. Figures 6A to 6AL An exemplary user interface for logging user activity during a subset of recurring time periods is shown. Figure 7 is a flowchart illustrating a method of logging user activity during a subset of recurring time periods according to some embodiments. FIG. 8A to FIG. 8B is a flowchart illustrating a method of logging user activity during a subset of recurring time periods according to some embodiments. Figures 6A to 6AL The user interface in the Figure 7 and FIG. 8A to FIG. 8B The process is described below in the process.

[0037] In addition, in the method described herein where one or more steps depend on one or more conditions being met, it should be understood that the method can be repeated in multiple repetitions so that in the process of repetition, all conditions for determining the steps in the method have been met in different repetitions of the method. For example, if the method needs to perform the first step (if the condition is met), and perform the second step (if the condition is not met), then the ordinary technician will know that the steps stated are repeated until both the condition is met and the condition is not met (in no particular order). Therefore, the method described as having one or more steps depending on one or more conditions being met can be rewritten as a method of repeating until each condition described in the method is met. However, this does not require the system or computer-readable medium to declare that the system or computer-readable medium contains instructions for performing a contingent operation based on the satisfaction of the corresponding one or more conditions, and is therefore able to determine whether the possible situation has been met without explicitly repeating the steps of the method until all conditions for determining the steps in the method have been met. It will also be understood by ordinary technicians in the art that, similar to the method with the contingent step, the system or computer-readable storage medium can repeat the steps of the method as many times as needed to ensure that all the contingent steps have been performed.

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

[0039] The terms used in the description of various described embodiments herein are only for the purpose of describing specific embodiments, and are not intended to be limited. As used in the description of various described embodiments and in the appended claims, the singular forms "one" and "the" are intended to also include plural forms, unless the context clearly indicates otherwise. It will also be understood that the term "and / or" used herein refers to and encompasses any and all possible combinations of one or more items in the associated listed items. It will also be understood that the term "includes", "including", "comprises" and / or "comprising" when used in this specification specifies the presence of stated features, integers, steps, operations, elements and / or parts, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts and / or their grouping.

[0040] The term "if" is optionally interpreted to mean "when," "upon," or "in response to determining," or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined that ..." or "if [a stated condition or event] is detected" are optionally interpreted to mean "upon determining that ..." or "in response to determining that ..." or "upon detecting [a stated condition or event]," or "in response to detecting [a stated condition or event]," depending on the context.

[0041] Embodiments of electronic devices, user interfaces for such devices, and associated 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 includes other functions, such as a PDA and / or a music player function. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple iPod from Apple Inc. (Cupertino, California). Devices, iPod Equipment, and Device. Optionally use other portable electronic devices, such as laptops or tablet computers 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 a desktop computer with a touch-sensitive surface (e.g., touch screen displays and / or touch pads). In some embodiments, the electronic device is a computer system that communicates with the display generation component (e.g., via wireless communication, via wired communication). The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separated from the computer system. As used herein, "display" content includes transmitting data (e.g., image data or video data) to an integrated or external display generation component via a wired or wireless connection to visually generate content to display content (e.g., video data rendered or decoded by display controller 156).

[0042] 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.

[0043] The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk editing application, a spreadsheet application, a gaming application, a telephony 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.

[0044] Various applications executed 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 adjusted and / or varied within the respective applications. In this way, the common physical architecture of the device (such as a touch-sensitive surface) optionally supports a variety of applications with a user interface that is intuitive and clear to the user.

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

[0046] 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 surrogate (surrogate) of the force or pressure of a contact on the touch-sensitive surface. The intensity of a 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 a 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 the force at different points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted average) to determine an estimated contact force. Similarly, the pressure-sensitive tip of a 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 its change, the capacitance of the touch-sensitive surface near the contact and / or its change, and / or the resistance of the touch-sensitive surface near the contact and / or its change are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some embodiments, the substitute measurement of the contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of the contact as an attribute of the user input allows the user to access additional device functions that would otherwise be inaccessible to the user on a smaller device with limited real estate, which is used to display an enable indication (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls, such as knobs or buttons).

[0047] As used in this specification and claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, which will be detected by a user using the user's sense of touch. For example, in the case where a device or a component of the device is in contact with a user's touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical characteristic of the device or component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "press click" or "release click" to 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 does not move. As another example, even when there is no change in the smoothness of the touch-sensitive surface, movement of the touch-sensitive surface may optionally be interpreted or sensed by the user as "roughness" of the touch-sensitive surface. Although such a user's interpretation of touch will be limited by the user's individualized sensory perceptions, many sensory perceptions of touch are common to most users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "press click," "release click," "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or a component thereof that would generate that sensory perception for a typical (or average) user.

[0048] 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 the components. Figure 1A The various components shown in the EMBODIMENTS 2000 are implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application specific integrated circuits.

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

[0050] The peripheral device interface 118 can be used to couple the input peripheral devices and output peripheral devices of the device to the CPU 120 and the memory 102. The one or more processors 120 run or execute various software programs (such as computer programs (e.g., including instructions)) and / or instruction sets stored in the memory 102 to perform various functions of the device 100 and process data. In some embodiments, the peripheral device interface 118, the CPU 120, and the memory controller 122 are optionally implemented on a single chip such as the chip 104. In some other embodiments, they are optionally implemented on separate chips.

[0051] RF (radio frequency) circuit 108 receives and sends RF signals, also referred to as electromagnetic signals. RF circuit 108 converts electrical signals into / converts electromagnetic signals into electrical signals, and communicates with communication networks and other communication devices via electromagnetic signals. RF circuit 108 optionally includes well-known circuits for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codec chipsets, user identity modules (SIM) cards, memories, and the like. RF circuit 108 optionally communicates with networks and other devices via wireless communications, such as the Internet (also referred to as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs)). RF circuit 108 optionally includes well-known circuits for detecting near field communications (NFC) fields, such as through short-range communications radio components. Wireless communication optionally uses any of a variety of communication standards, protocols and technologies, including, but not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, 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, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11d), IEEE 802.11e, IEEE 802.11f, IEEE 802.11g, IEEE 802.11g). 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 Utilizing Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol including communication protocols that have not been developed as of the filing date of this document.

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

[0053] The I / O subsystem 106 couples input / output peripherals on the device 100, such as a touch screen 112 and other input control devices 116, to a peripheral device interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, a depth camera controller 169, an intensity sensor controller 159, a tactile feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive / send electrical signals from other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, etc. In some embodiments, the input controller 160 is optionally coupled to any of the following (or none of the following): a keyboard, an infrared port, a USB port, and a pointing device such as a mouse. One or more buttons (e.g., Figure 2 208) optionally includes an increase / decrease button for volume control of the speaker 111 and / or the microphone 113. The one or more buttons optionally include a push button (e.g., Figure 2206 in). In some embodiments, the electronic device is a computer system that communicates with one or more input devices (e.g., via wireless communication, via wired communication). In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a touchpad as part of a touch-sensitive display). In some embodiments, the one or more input devices include one or more camera sensors (e.g., one or more optical sensors 164 and / or one or more depth camera sensors 175), such as for tracking a user's gestures (e.g., hand gestures) as input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system.

[0054] A 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 gestures on the touch screen, as described in U.S. Patent Application 11 / 322,549, filed on December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image" (i.e., U.S. Patent No. 7,657,849), which is hereby incorporated by reference in its entirety. A long press of the push button (e.g., 206) optionally turns the device 100 on or off. The functions of one or more buttons are optionally user-customizable. The touch screen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

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

[0056] The touch screen 112 has a touch-sensitive surface, sensor, or sensor group that accepts input from a user based on tactile and / or haptic contact. The touch screen 112 and display controller 156 (together with any associated modules and / or instruction sets in memory 102) detect contact on the touch screen 112 (and any movement or interruption of the contact) and convert the detected contact into interaction with a user interface object (e.g., one or more soft keys, icons, web pages, or images) displayed on the touch screen 112. In an exemplary embodiment, the point of contact between the touch screen 112 and the user corresponds to a finger of the user.

[0057] The 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. The touch screen 112 and display controller 156 optionally use 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 the touch screen 112 to detect contact and any movement or interruption thereof. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as in the Apple ® from Apple Inc. (Cupertino, California). and iPod The technology used in.

[0058] The touch-sensitive display in some embodiments of the touch screen 112 is optionally similar to the multi-touch-sensitive touch pad described in the following U.S. Patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman et al.), and / or U.S. Patent Publication 2002 / 0015024A1, each of which is hereby incorporated by reference in its entirety. However, the touch screen 112 displays visual output from the device 100, while the touch-sensitive touch pad does not provide visual output.

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

[0060] The touch screen 112 optionally has a video resolution of more than 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user optionally uses any suitable object or attachment such as a stylus, a finger, etc. to contact the touch screen 112. In some embodiments, the user interface is designed to work primarily through 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 converts rough finger-based input into precise pointer / cursor positions or commands for performing the actions desired by the user.

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

[0062] The device 100 also includes a power system 162 for powering the various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, a power fault 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.

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

[0064] Device 100 optionally also includes one or more depth camera sensors 175 . Figure 1A A depth camera sensor coupled to a depth camera controller 169 in the I / O subsystem 106 is shown. The depth camera sensor 175 receives data from the environment to create a three-dimensional model of an object (e.g., a face) within the scene from a viewpoint (e.g., a depth camera sensor). In some embodiments, in conjunction with the imaging module 143 (also referred to as a camera module), the depth camera sensor 175 is optionally used to determine a depth map of different portions of an image captured by the imaging module 143. In some embodiments, the depth camera sensor is located at the front of the device 100, so that an image of the user with depth information is optionally obtained for video conferencing while the user is viewing other video conference participants on the touch screen display, and a selfie with depth map data is captured. In some embodiments, the depth camera sensor 175 is located at the rear of the device, or at both the rear and front of the device 100. In some embodiments, the position of the depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and sensor in the device housing) so that the depth camera sensor 175 is used with the touch screen display for both video conferencing and still image and / or video image acquisition.

[0065] Device 100 optionally also includes one or more contact intensity sensors 165 . Figure 1AA contact force sensor is shown coupled to a force sensor controller 159 in the I / O subsystem 106. Contact force 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 force sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). Contact force sensor 165 receives contact force information (e.g., pressure information or a surrogate for pressure information) from the environment. In some embodiments, at least one contact force sensor is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact force sensor is located on the back of device 100, opposite to touch screen display 112 located on the front of device 100.

[0066] Device 100 optionally also includes one or more proximity sensors 166 . Figure 1A A proximity sensor 166 is shown coupled to the peripherals 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 is optionally implemented as described in the following U.S. patent applications: No. 11 / 241,839, entitled "Proximity Detector In Handheld Device"; No. 11 / 240,788, entitled "Proximity Detector In Handheld Device"; No. 11 / 620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output"; No. 11 / 586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and No. 11 / 638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals", which are hereby incorporated by reference in their entirety. In some embodiments, when the multifunction device is placed near the user's ear (e.g., when the user is on a phone call), the proximity sensor turns off and disables the touch screen 112.

[0067] Device 100 optionally also includes one or more tactile output generators 167 . Figure 1AA tactile output generator is shown coupled to a tactile feedback controller 161 in the I / O subsystem 106. The tactile output generator 167 optionally includes one or more electroacoustic devices such as a speaker or other audio component; and / or an electromechanical device for converting energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component for converting an electrical signal into a tactile output on the device). The contact force sensor 165 receives tactile feedback generation instructions from the tactile feedback module 133 and generates a tactile output on the device 100 that can be felt by a user of the device 100. In some embodiments, at least one tactile output generator is arranged in parallel or adjacent to a touch-sensitive surface (e.g., a touch-sensitive display system 112) and optionally generates a tactile output by moving the touch-sensitive surface vertically (e.g., inward / outward of the surface of the device 100) or laterally (e.g., backward and forward in the same plane as the surface of the device 100). In some embodiments, at least one tactile output generator sensor is located on the back of the device 100, opposite the touch screen display 112 located on the front of the device 100.

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

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

[0070] The 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 facilitating communication between various hardware components and software components.

[0071] 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 circuit 108 and / or the external port 124. The external port 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) is suitable for coupling directly to other devices, or indirectly through a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is connected to (trademark of Apple Inc.) devices.

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

[0073] 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 a user (e.g., to determine whether a user has "clicked" an icon). In some embodiments, at least a subset of the intensity thresholds are determined based on software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of specific physical actuators and can be adjusted without changing the physical hardware of the device 100). For example, without changing the touchpad or touchscreen display hardware, the mouse "click" threshold of a touchpad or touchscreen can be set to any one of a large range of predefined thresholds. In addition, in some specific implementations, a software setting is provided to the user of the device for adjusting one or more intensity thresholds in a set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by utilizing a system-level click on an "intensity" parameter to adjust multiple intensity thresholds at once).

[0074] 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 the detected contacts). Therefore, gestures are optionally detected by detecting specific contact patterns. For example, detecting a finger tap gesture includes detecting a finger press event, and then detecting a finger lift (lift-off) event at the same location (or substantially the same location) as the finger press event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and then detecting a finger lift (lift-off) event.

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

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

[0077] Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator 167 to produce tactile output at one or more locations on device 100 in response to user interaction with device 100 .

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

[0079] 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 a weather widget, a local yellow pages widget, and a map / navigation widget).

[0080] The application 136 optionally includes the following modules (or instruction sets) or a subset or superset thereof:

[0081] ● Contacts module 137 (sometimes called address book or contact list);

[0082] ● Telephone module 138;

[0083] ● Video conferencing module 139;

[0084] ● Email client module 140;

[0085] ●Instant messaging (IM) module 141;

[0086] ●Fitness support module 142;

[0087] ● Camera module 143 for still images and / or video images;

[0088] ● Image management module 144;

[0089] ●Video player module;

[0090] ●Music player module;

[0091] ●Browser module 147;

[0092] ● Calendar module 148;

[0093] A widget module 149, which optionally includes one or more of the following: a weather widget 149-1, a stock market widget 149-2, a calculator widget 149-3, an alarm widget 149-4, a dictionary widget 149-5, and other widgets acquired by the user, and a user-created widget 149-6;

[0094] A widget creator module 150 for forming a user-created widget 149-6;

[0095] ●Search module 151;

[0096] ● Video and music player module 152, which merges the video player module and the music player module;

[0097] ●Note module 153;

[0098] ● Map module 154; and / or

[0099] ●Online video module 155.

[0100] Examples of other applications 136 that are 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.

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

[0102] 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 contact 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 described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

[0103] In combination with the RF circuit 108, the audio circuit 110, the speaker 111, the microphone 113, the touch screen 112, the display controller 156, the optical sensor 164, the optical sensor controller 158, the contact / motion module 130, the graphics module 132, the text input module 134, the contact module 137 and the telephone module 138, the video conferencing module 139 includes executable instructions for initiating, conducting and terminating a video conference between a user and one or more other participants in accordance with user instructions.

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

[0105] In conjunction with RF circuit 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 the following operations: inputting a character sequence corresponding to an instant message, modifying previously input characters, transmitting a corresponding instant message (e.g., using a short message service (SMS) or multimedia message service (MMS) protocol for phone-based instant messaging or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, the transmitted and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments supported in MMS and / or enhanced messaging services (EMS). As used herein, "instant messaging" refers to both phone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0106] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154 and the music player module, the fitness support module 142 includes executable instructions for creating a fitness (e.g., with time, distance and / or calorie burn goals); communicating with fitness sensors (sports equipment); receiving fitness sensor data; calibrating sensors for monitoring fitness; selecting and playing music for fitness; and displaying, storing and transmitting fitness data.

[0107] In conjunction with the 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, the camera module 143 includes executable instructions for the following operations: capturing still images or videos (including video streams) and storing them in the memory 102, modifying the characteristics of the still images or videos, or deleting the still images or videos from the memory 102.

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

[0109] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132 and the text input module 134, the browser module 147 includes executable instructions for browsing the Internet in accordance with user instructions, including searching, linking to, receiving and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0110] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132, the text input module 134, the email client module 140 and the browser module 147, the calendar module 148 includes executable instructions for creating, displaying, modifying and storing calendars and data associated with the calendar (e.g., calendar entries, to-do items, etc.) in accordance with user instructions.

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

[0112] In combination with the RF circuit 108, touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134 and browser module 147, the widget creator module 150 is optionally used by a user to create widgets (e.g., converting a user-specified portion of a web page into a widget).

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

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

[0115] In conjunction with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the note module 153 includes executable instructions for creating and managing notes, to-do lists, etc. according to user instructions.

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

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

[0118] Each of the modules and applications described above corresponds to an executable instruction set for performing one or more of the functions described above and the methods described in this patent application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) do not have to be implemented as independent software programs (such as computer programs (e.g., including instructions)), processes, or modules, so various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. For example, a video player module is optionally combined with a music player module into a single module (e.g., Figure 1A In some embodiments, the memory 102 optionally stores a subset of the above modules and data structures. In addition, the memory 102 optionally stores additional modules and data structures not described above.

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

[0120] A predefined set of functions that are performed exclusively through the touch screen and / or touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 to a main menu, a home menu, or a root menu from any user interface displayed on the device 100. In such embodiments, a "menu button" is implemented using the touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a touchpad.

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

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

[0123] In some embodiments, the application internal state 192 includes additional information, such as one or more of the following: resumption information to be used when the application 136-1 resumes execution, user interface state information indicating that information is being displayed or is ready to be displayed 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.

[0124] Event monitor 171 receives event information from peripherals interface 118. Event information includes information about sub-events (e.g., user touches 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, one or more accelerometers 168, and / or microphone 113 (through audio circuit 110). The information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

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

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

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

[0128] Another aspect of the user interface associated with an application is a set of views, sometimes also referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of the respective application) in which a touch is detected optionally correspond to a programmatic level within the programmatic or view hierarchy of the application. 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 that are recognized as correct input is optionally determined at least in part based on the hit view of the initial touch that started the touch-based gesture.

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

[0130] 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 embodiments, 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 therefore determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely confined to an area associated with one particular view, higher views in the hierarchy will still remain as actively participating views.

[0131] Event distributor module 174 distributes event information to event recognizers (e.g., event recognizers 180). In embodiments including active event recognizer determination module 173, event distributor module 174 delivers the event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event distributor module 174 stores the event information in an event queue, which is retrieved by corresponding event receivers 182.

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

[0133] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events occurring within a corresponding view of the user interface of the application. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, the corresponding application view 191 includes multiple event recognizers 180. In other embodiments, one or more event recognizers in event recognizers 180 are part of an independent module, which is a higher-level object such as a user interface toolkit or application 136-1 from which methods and other properties are inherited. In some embodiments, the corresponding event handler 190 includes one or more of the following: data updater 176, object updater 177, GUI updater 178, and / or event data 179 received from event classifier 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 in application view 191 include one or more corresponding event handlers 190. In addition, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in the corresponding application view 191.

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

[0135] Event receiver 182 receives event information from event classifier 170. Event information includes information about sub-events such as touch or touch movement. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves the movement of the touch, the event information optionally also includes the speed and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another orientation (for example, from a longitudinal orientation to a transverse orientation, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device posture).

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

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

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

[0139] When a corresponding event recognizer 180 determines that a sequence of sub-events does not match any event in event definition 186, the corresponding event recognizer 180 enters an event impossible, event failed, or event ended state, after which subsequent sub-events 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.

[0140] In some embodiments, the corresponding event recognizers 180 include metadata 183 with configurable properties, flags, 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 properties, flags, and / or lists that indicate how event recognizers interact or can interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate whether sub-events are delivered to different levels in a view or programmatic hierarchy.

[0141] In some embodiments, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates an event handler 190 associated with the event. In some embodiments, the corresponding event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is different from sending (and deferred sending) the sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a tag associated with the identified event, and the event handler 190 associated with the tag obtains the tag and performs a predefined process.

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

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

[0144] 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 the corresponding application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

[0145] It should be understood that the above discussion of event processing for user touches on a touch-sensitive display also applies to other forms of user input that utilize input devices to operate the multifunction device 100, and not all user input is initiated on the touch screen. For example, mouse movement and mouse button presses, optionally in conjunction with single or multiple keyboard presses or hold; contact movement on a touch pad, such as tapping, dragging, scrolling, etc.; stylus input; movement of the device; verbal commands; detected eye movement; biometric input; and / or any combination thereof are optionally used as input corresponding to sub-events that define the event to be distinguished.

[0146] Figure 2A portable multifunction device 100 with a touch screen 112 according to some embodiments is shown. The touch screen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment and other embodiments described below, a user can select one or more of these graphics by, for example, making gestures on the graphics using one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, when the user interrupts contact with one or more graphics, selection of one or more graphics will occur. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down) and / or rolling of fingers that have been in contact with the device 100 (from right to left, from left to right, up and / or down). In some specific implementations or in some cases, inadvertent contact with a graphic will not select the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application.

[0147] The 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 button is implemented as a soft key in a GUI displayed on the touch screen 112.

[0148] In some embodiments, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for turning the device on / off and for locking the device, one or more volume adjustment buttons 208, a user identity module (SIM) card slot 210, an earphone jack 212, and a docking / charging external port 124. The push button 206 is optionally used to turn the device on / off by pressing the button and keeping the button in a pressed state for a predefined time interval; lock the device by pressing the button and releasing the button before the predefined time interval passes; and / or unlock the device or initiate an unlocking process. In an alternative embodiment, the device 100 also accepts voice input for activating or deactivating certain functions through a microphone 113. The device 100 also optionally includes one or more contact strength sensors 165 for detecting the strength of contact on the touch screen 112, and / or one or more tactile output generators 167 for generating tactile output for a user of the device 100.

[0149] Figure 3300 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments. The device 300 does not have to be portable. In some embodiments, the device 300 is a laptop, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a game system, or a control device (e.g., a home controller or an industrial controller). The device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, a memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuits (sometimes referred to as a chipset) that interconnect system components and control communications between system components. The device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touch screen display. The I / O interface 330 also optionally includes a keyboard and / or a mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 for generating tactile output on the device 300 (e.g., similar to the above reference Figure 1A The tactile output generator 167 described above), sensor 359 (e.g., optical sensor, acceleration sensor, proximity sensor, touch sensor and / or contact intensity sensor (similar to the above reference Figure 1A The memory 370 may include a high-speed random access memory, such as DRAM, SRAM, DDRRAM, or other random access solid-state memory devices; and may optionally include a 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. The memory 370 may optionally include one or more storage devices located away from the CPU 310. In some embodiments, the memory 370 stores data related to the portable multifunction device 100 ( Figure 1A ) or a subset thereof. In addition, 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 a drawing module 380, a presentation module 382, ​​a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while portable multifunction device 100 ( Figure 1A )'s memory 102 optionally does not store these modules.

[0150] Figure 3Each element in the above-mentioned elements in is optionally stored in one or more memory devices of the previously mentioned memory device. Each module in the above-mentioned modules corresponds to an instruction set for performing the above-mentioned functions. The above-mentioned modules or programs (e.g., instruction sets) do not have to be implemented with separate software programs (such as computer programs (e.g., including instructions)), processes or modules, and therefore the 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 above-mentioned modules and data structures. In addition, memory 370 optionally stores additional modules and data structures not described above.

[0151] Attention is now turned to an embodiment of a user interface that is optionally implemented on, for example, portable multifunction device 100.

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

[0153] ● Signal strength indicators 402 for wireless communications such as cellular signals and Wi-Fi signals;

[0154] ●Time 404;

[0155] ●Bluetooth indicator 405;

[0156] ●Battery status indicator 406;

[0157] A tray 408 with icons for commonly used applications, such as:

[0158] o 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 voicemails;

[0159] o 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;

[0160] o an icon 420 labeled "Browser" of the browser module 147; and

[0161] o an icon 422 labeled “iPod” of a video and music player module 152 (also referred to as an iPod (trademark of Apple Inc.) module 152); and

[0162] ● Icons for other applications, such as:

[0163] o Icon 424 labeled “Messages” of IM module 141;

[0164] o Icon 426 labeled “Calendar” of calendar module 148;

[0165] o Icon 428 labeled “Photos” of the image management module 144;

[0166] o Icon 430 labeled “Camera” of camera module 143;

[0167] o Icon 432 labeled “Online Video” of the online video module 155;

[0168] o Icon 434 labeled “Stock Market” of the stock market widget 149 - 2 ;

[0169] o an icon 436 labeled “MAP” of the map module 154;

[0170] o Icon 438 labeled “Weather” of the weather widget 149 - 1 ;

[0171] o Icon 440 labeled “Clock” of the alarm clock widget 149 - 4 ;

[0172] o an icon 442 labeled “Fitness Support” of the fitness support module 142;

[0173] o an icon 444 labeled "Notes" of the notes module 153; and

[0174] o An icon 446 of a settings application or module labeled “Settings” that provides access to settings for the device 100 and its various applications 136 .

[0175] It should be noted that Figure 4A The icon labels shown in are exemplary only. For example, icon 422 of video and music player module 152 is labeled "Music" or "Music Player". Other labels are optionally used for various application icons. In some embodiments, the label of a corresponding application icon includes the name of the application corresponding to the corresponding 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.

[0176] Figure 4B A touch-sensitive surface 451 (eg, touch screen display 112) is shown having a touch-sensitive surface 451 (eg, Figure 3 tablet computer or touch pad 355) device (e.g., Figure 3Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting intensity of contacts on touch-sensitive surface 451 and / or one or more tactile output generators 357 for generating tactile output for a user of device 300.

[0177] Although some of the examples below are given with reference to input on a touch screen display 112 (where a touch-sensitive surface and a display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, such as Figure 4B In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a main axis (e.g., Figure 4B 453) corresponding to the principal axis (for example, Figure 4B According to these embodiments, the device detects a position corresponding to a corresponding position on the display (e.g., Figure 4B 460 corresponds to 468 and 462 corresponds to 470) in contact with touch-sensitive surface 451 (e.g., Figure 4B Thus, when the touch-sensitive surface (e.g., Figure 4B 451) and a display of a multi-function device (e.g., Figure 4B When the user input detected by the device on the touch-sensitive surface (e.g., contacts 460 and 462 and their movement) is separated, the device is used to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

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

[0179] Figure 5AAn exemplary personal electronic device 500 is shown. Device 500 includes a body 502. In some embodiments, device 500 may include a body 502 relative to devices 100 and 300 (e.g., Figures 1A to 4B ) some or all of the features described in the foregoing. In some embodiments, device 500 has a touch-sensitive display screen 504, referred to hereinafter as touch screen 504. As an alternative or in addition to touch screen 504, 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 strength sensors for detecting the intensity of contact (e.g., touch) applied. One or more strength sensors of touch screen 504 (or touch-sensitive surface) can provide output data representing the intensity of touch. The user interface of device 500 can respond to touch based on the intensity of the touch, which means that touches of different intensities can invoke different user interface operations on device 500.

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

[0181] In some embodiments, the device 500 has one or more input mechanisms 506 and 508. The input mechanisms 506 and 508 (if included) can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, the device 500 has one or more attachment mechanisms. Such attachment mechanisms (if included) can allow the device 500 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watchbands, bracelets, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow the user to wear the device 500.

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

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

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

[0185] As used herein, the term "indicative representation" refers to an optional feature of the apparatus 100, 300, and / or 500 ( Figure 1A , Figure 3 and FIG. 5A to FIG. 5B ) is a user-interactive graphical user interface object displayed on a display screen of a computer. For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) optionally each constitute an affordance.

[0186] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface that a user is interacting with. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), a focus selector is displayed on a touch-sensitive surface (e.g., Figure 3 Touchpad 355 or Figure 4B In the event that an input (e.g., a press input) is detected on the touch-sensitive surface 451 in the display, the particular user interface element is adjusted according to the detected input. In the case that a touch-screen display (e.g., Figure 1A A touch-sensitive display system 112 or Figure 4AIn some implementations of the touch screen 112 in FIG. 1 , a contact detected on the touch screen acts as a “focus selector” such that when an input (e.g., a press input by the contact) is detected at the 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 moves from one area of ​​the user interface to another area of ​​the user interface without corresponding movement of a cursor or movement of the contact on the touch screen display (e.g., by using a tab key or arrow keys to move the focus from one button to another); in these implementations, the focus selector moves in accordance with the movement of the focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user interface element (or contact on the 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 of the user interface with which the user desires to interact). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a corresponding button will indicate that the user intends to activate the corresponding button (rather than other user interface elements shown on the device display).

[0187] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of a contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected 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 contact is detected, before contact is detected to be lifted off, before or after contact starts to move, before contact ends, before or after contact intensity is detected to increase, and / or before or after contact intensity is detected to decrease). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum value of the intensity of the contact, the mean value of the intensity of the contact, the average value of the intensity of the contact, the value at the top 10% of the intensity of the contact, the half-maximum value of the intensity of the contact, the 90% maximum value of the intensity of the contact, etc. In some embodiments, the duration of the contact is used when determining the characteristic intensity (e.g., when the characteristic intensity is the average value of the intensity of the contact over time). In some embodiments, the feature strength is compared to a set of one or more strength thresholds to determine whether the user has performed an operation. For example, the set of one or more strength thresholds optionally includes a first strength threshold and a second strength threshold. In this example, a contact whose feature strength does not exceed the first threshold results in a first operation, a contact whose feature strength exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and a contact whose feature strength exceeds the second threshold results in a third operation. In some embodiments, a comparison between the feature strength and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the corresponding operation or to abandon the corresponding operation) rather than to determine whether to perform the first operation or the second operation.

[0188] In some embodiments, a portion of a gesture is identified for determining characteristic strength. For example, the touch-sensitive surface optionally receives a continuous swipe contact that transitions from a starting position and reaches an end position, where the contact strength increases. In this example, the characteristic strength of the contact at the end position is optionally based only on a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., only the portion of the swipe contact at the end position). In some embodiments, a smoothing algorithm is optionally applied to the strength of the swipe contact before determining the characteristic strength of the contact. For example, a smoothing algorithm optionally includes one or more of the following: an unweighted sliding 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 peaks or depressions in the strength of the swipe contact to achieve the purpose of determining the characteristic strength.

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

[0190] An increase in contact feature intensity from an intensity below a light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a "light press" input. An increase in contact feature intensity from an intensity below a deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press" input. An increase in contact feature intensity from an intensity below a contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting contact on the touch surface. A decrease in contact feature intensity from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting contact lifted 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.

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

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

[0193] 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 including a press input is triggered in response to detecting any of the following: contact intensity increasing to above the press input intensity threshold, contact intensity increasing from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, contact intensity decreasing to below the press input intensity threshold, and / or contact intensity decreasing to below a hysteresis intensity threshold corresponding to the press input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting that the intensity of the contact decreases below the press input intensity threshold, the operation is 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.

[0194] Attention is now turned 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.

[0195] Figures 6A to 6AL An exemplary user interface for logging user activity during a subset of recurring time periods according to some embodiments is shown. The user interface in these figures is used to illustrate a user interface including Figure 7 and FIG. 8A to FIG. 8B The process is described below in the process.

[0196] Fig. 6AAn electronic device 600 (e.g., a smart phone) is shown displaying an introductory user interface 606 on a touch screen display 602. In some embodiments, the device 600 includes one or more features of the devices 100, 300, and / or 500. The current date is August 1, as indicated by the text above the device 600 (which is provided to improve understanding and is not part of the displayed interface), and the current time is 08:00, as shown by the time indication 604. The introductory user interface 606 introduces the glucose monitoring feature and includes a continue enable indication 606a. In some embodiments, the introductory user interface 606 includes multiple separate content screens that describe the blood glucose monitoring feature in more detail during the introduction. In some embodiments, the device 600 receives one or more inputs to initiate and complete the introduction of the blood glucose monitoring feature. In this example, device 600 detects a tap input 608 corresponding to a selection of continue affordance 606a, and in response to receiving tap input 608, device 600 begins a baseline phase (e.g., an introduction phase, an initial phase, and / or a sensor phase) and displays an hourly log user interface 610, as shown. Figure 6B shown.

[0197] Figure 6B A device 600 is depicted displaying an hourly log user interface 610 on a touch screen display 602. The hourly log user interface 610 includes a graph area 612 that includes a day of the week indicator 612a (e.g., "S" for Sunday, "M" for Monday, etc.) and a chart area 612b that currently reads "No chart data available." In some embodiments, once sufficient data has been received, the day of the week indicator 612a may be selected, causing the device 600 to display chart data for the selected day. In some embodiments, the chart data becomes available after the device 600 has received a predetermined amount of data (e.g., blood glucose data). In some embodiments, the blood glucose data is provided by a continuous blood glucose monitor that is worn by a user of the device 600 and communicates with the device 600.

[0198] Hourly log user interface 610 also includes log area 614. Log area 614 includes meal log record affordance 614a, activity log record affordance 614b, and mood log record affordance 614c. Hourly log user interface 610 also includes hour tab affordance 616a and setting tab affordance 616b. In some embodiments, selection of setting tab affordance 616b causes device 600 to display setting user interface. In some embodiments, setting user interface includes multiple options, some of which may be reviewing collected data, adjusting time frame, viewing strategy, customizing measurement units.

[0199] like Figure 6C As shown in the time indication 604, 4 hours have passed (relative to Figure 6B ) and the current time is now 12:00. Device 600 has received blood glucose data to be displayed on the touch screen display 602 in the hourly log user interface 610. The day of the week indicator 612a corresponding to Saturday, August 1 (e.g., "S") now includes a small chart icon indicating that data has been collected for that day. Chart area 612b now includes hours along the x-axis and blood glucose amounts along the y-axis. Chart line 612c (e.g., corresponding to blood glucose measurement results) shows blood glucose measurement results in a specific time period. Chart line 612c stops at 12:00, indicating that data has been collected before 12:00. Chart line 612c shows standard blood glucose measurement results and elevated blood glucose measurement results. As shown, elevated measurement results (e.g., measurement results exceeding a predetermined threshold value (e.g., >130mg / dL; >180mg / dL)) are visually distinguished from standard measurement results (e.g., with different line widths, with different colors). In some embodiments, the chart line 612c does not visually distinguish the elevated measurement from the standard measurement. The device 600 receives a tap input 617 corresponding to the selection of the meal log record affordance 614a. In response to detecting the tap input 617 at the meal log record affordance 614a, the device 600 initiates the creation of a log entry for a meal (e.g., consuming food or drinking a beverage (e.g., breakfast, lunch, dinner, snacks)). In some embodiments, the selection of the activity log record affordance 614b initiates the creation of a log entry for a physical activity (e.g., exercise, meditation). In some embodiments, the selection of the emotion log record affordance 614c initiates the creation of a log entry for an emotion (e.g., happiness, sadness, listlessness, excitement).

[0200] exist Fig.6D, the device 600 displays a log entry creation user interface 618 on the touch screen display 602. The log entry creation user interface 618 includes a time selection affordance 618a. In some embodiments, the selection of the time selection affordance 618a allows customization of the time corresponding to the log entry. In this example, the time selection affordance 618a shows (e.g., defaults to) the current time 12:00. The log entry creation user interface 618 also includes a search bar 618b, which can be selected to initiate a search for a specific food. In some embodiments, when the log records an activity or emotion, the search bar 618b can be used to find a specific exercise or emotion. The log entry creation user interface 618 also includes a camera affordance 618c and a save affordance 618d. In some embodiments, the selection of the camera affordance 618c turns on the camera of the device 600 and allows the user to capture photos of their meals. In such embodiments, the device 600 generates log entries (e.g., using image recognition software) based on photos of meals.

[0201] The log entry creation user interface 618 includes an item selection area 620. In this example, the item selection area 620 displays common foods that the user can select for logging. In some embodiments, when logging activities, the item selection area 620 includes selectable affordances corresponding to various activities (e.g., walking, biking, meditation). In some embodiments, when logging emotions, the item selection area 620 includes selectable affordances corresponding to various emotions / emotions (e.g., feelings (e.g., anxiety, excitement, fatigue)). The device 600 receives tap inputs 622a and 622b corresponding to selections of the bread affordance 620a and the salad affordance 620b, respectively. In some embodiments, when creating a log entry, only one of the selectable affordances within the item selection area 620 may be selected. In some embodiments, when creating a log entry, one or more of the selectable affordances within the item selection area 620 may be selected. As Fig. 6E As shown, in response to detecting tap inputs 622a and 622b, device 600 displays a log entry creation user interface 618 in which bread indicator 620a and salad indicator 620b are visually distinct from other food indicators (e.g., bold), thereby indicating that these two foods have been selected for logging.

[0202] exist Fig. 6E In the example of FIG. 6 , device 600 receives a tap input 624 corresponding to a selection of save affordance 618 d. In response to detecting tap input 624, device 600 generates a log entry 614 d displayed in log area field 614 of hourly log user interface 610, such as Fig. 6F shown.

[0203] exist Fig. 6F , hourly log user interface 610 now includes the display of log entry 614d. Log entry 614d includes the food consumed (e.g., bread and salad) and the time indication (e.g., 12:00) corresponding to the time when the food is consumed. Log entry 614d is displayed below "afternoon", and "afternoon" indicates the general time period for eating. In this example, every day is divided into four cyclic time periods (e.g., quadrants), which include morning (04:00 to 10:00), afternoon (10:00 to 16:00), evening (16:00 to 22:00) and night (22:00 to 04:00). In some embodiments, quadrants span different time ranges. In some embodiments, quadrants are not equal time periods (e.g., two 5-hour time periods and two 7-hour time periods; longer time periods are used for night quadrants) within a 24-hour period. In some embodiments, a subset of cyclic time periods is different from a quadrant (e.g., a day is divided into six or eight parts, or a week is divided into separate days). In some embodiments, a full day is a cyclic time period that is not further divided. In some embodiments, the cyclic time period is selected (e.g., customized) by the user. Log entry 614d also includes optional details of the specified food type (e.g., "sour yeast roll" is a "bread"). In this example, "sour yeast roll" is specified below "bread", and "add details..." is displayed below "salad" as a prompt for adding details (e.g., notes, specifying the type of salad). In some embodiments, selecting "add details..." causes device 600 to display a text input field and keyboard. In some embodiments, after entering additional details, device 600 stops displaying "add details..." and displays the entered text. Log entry 614d optionally includes selectable affordance 614d1 (e.g., an icon with three dots) to view details and edit (e.g., add or remove food types) or delete log entries. In some embodiments, in response to selecting enable indication 614d1 or log entry 614d, device 600 displays a log details user interface including specific details about the log entry (e.g., a glucose graph, date, time, and options to edit, copy, or delete the log entry).

[0204] In addition to generating the log entry 614d, the device 600 also displays a meal glyph 612d along the chart line 612c. The meal glyph 612d is displayed along the chart area 612b at a time corresponding to the time of the meal (e.g., 12:00). In some embodiments, if the log entry is an activity or emotion log entry, the corresponding activity or emotion glyph will be displayed along the chart line 612c. In some embodiments, the meal glyph, activity glyph, and emotion glyph are selectable user interface objects that, when selected, cause the device 600 to display a log detail user interface corresponding to the log entry.

[0205] Now turn to Figure 6G , the current date is August 10, as indicated above the device 600. The device 600 displays an hourly log user interface 610 on the touch screen display 602. The hourly log user interface 610 includes a chart area 612b having a chart line 612e and an activity icon 614e displayed in a log area field 614. The activity icon 612e corresponds to a log entry 614e (e.g., walking). In some embodiments, the device 600 may receive a swipe input corresponding to the chart area 612b to scroll (e.g., horizontally) and view previously collected data. In some embodiments, the previously collected data in the chart area 612b includes a meal icon at the time of each log entry corresponding to breakfast (e.g., toast) and lunch (e.g., pasta) along the chart line 612c, as shown in the log area 614.

[0206] Ten days after its introduction, on August 11, Figure 6H As shown, the device 600 displays an action notification 626 on top of the hourly log user interface 610. The action notification 626 indicates that the baseline phase is now complete and the next phase of the glucose monitoring feature (e.g., the action phase) is available. In some embodiments, the action notification 626 is displayed after a minimum amount of time has passed since the baseline phase began (e.g., starting data collection). In some embodiments, the action notification 626 is displayed after the device 600 has received enough physiological data (e.g., blood glucose measurement results). In some embodiments, the action notification 626 is displayed after the device 600 has received enough elevated blood glucose measurement results. In some embodiments, the action phase is unavailable (e.g., locked) until a standard such as the described standard has been met. The action notification 626 includes a continue enable representation 626a (e.g., "select an action item"). The device 600 detects a tap input 628 corresponding to the selection of the continue enable representation 626a, and in response to the tap input 628, the device 600 initiates the action phase establishment.

[0207] like Fig.6IAs shown, in response to detecting a tap input 628, the device 600 initiates the action phase establishment by displaying a baseline summary user interface 630 on the touch screen display 602. The baseline summary user interface 630 includes an informative enabling representation 630a and a continuing enabling representation 630b that details how to present the physiological data (e.g., blood glucose data) received by the device 600. The informative enabling representation 630a includes an elevated value (e.g., one to ten) corresponding to the elevated level (e.g., no elevation, slightly elevated, some elevation, elevated, very elevated) of the received blood glucose measurement result. In some embodiments, the elevated value is presented instead of the concentration value (e.g., mg / dL). In some embodiments, the elevated value is based on the blood glucose measurement results (derived from these blood glucose measurement results) within a time period (e.g., from 10:00 to 16:00; one day; seven days from 09:00 to 12:00 every day).

[0208] Fig.6I The baseline summary user interface 630 also includes a morning baseline affordance 632. The morning baseline affordance 632 shows a morning baseline graph 632a and a morning elevation value 632b, which is a visual representation of elevation data received by the device 600 during the morning quadrant (e.g., a time period in the morning (e.g., from 04:00 to 10:00)) during a baseline phase (e.g., an introduction phase, an initial phase, a sensor phase). In some embodiments, the morning baseline graph 632a depicts an instance (e.g., a single morning (e.g., the morning of August 8)) of physiological data with the highest elevation received by the device 600 during the morning quadrant of the baseline phase. In some embodiments, the morning baseline graph 632a is based on all physiological data (derived from the physiological data) received by the device 600 during the morning quadrant of the baseline phase (e.g., for 10 days; for one week) (e.g., displayed as an average). In some embodiments, the baseline summary user interface 630 presents a subset of recurring time periods (e.g., a day; a week) that differs from quadrants (e.g., a day divided into sixths or eighths, or a week divided into individual days).

[0209] like Fig.6I As shown, device 600 detects a swipe input 638 on touch screen display 602 corresponding to a request to scroll baseline summary user interface 630. In response to receiving swipe input 638, device 600 displays a second portion of baseline summary user interface 630, such as Figure 6J As shown. Figure 6J, baseline summary user interface 630 includes a portion of a morning baseline affordance 632 and an optional view all morning data affordance 632c. In some embodiments, selection of the view all morning data affordance 632c causes device 600 to display a user interface having one or more graphs including a morning baseline graph 632a corresponding to physiological data (e.g., blood glucose measurements) received by device 600 during a morning quadrant of a baseline phase (e.g., a time period in the morning (e.g., from 04:00 to 10:00)). In some embodiments, in response to selection of the view all morning data affordance 632c, device 600 displays a graph corresponding to an instance of receiving elevated physiological data (e.g., measurements above a threshold).

[0210] exist Figure 6J , the baseline summary user interface 630 includes an evening baseline indication 634. The evening baseline indication 634 is similar to the morning baseline indication 632, however, the evening baseline indication 634 corresponds to physiological data (e.g., blood glucose measurements) received by the device 600 during the evening quadrant of the baseline phase (e.g., during a time period during the evening (e.g., from 16:00 to 22:00)). The evening baseline indication 634 includes an evening baseline graph 634a, which shows blood glucose measurements received by the device 600 along the x-axis during the time period during the evening (e.g., from 16:00 to 22:00) and along the y-axis. The portion of the evening baseline graph 634a containing elevated measurements is visually different (e.g., has a thicker line width) than non-elevated measurements. The evening baseline indication 634 includes an evening elevated value 632b. Baseline summary user interface 630 includes a selectable view all evening data affordance 634c that is similar to selectable view all morning data affordance 632c.

[0211] The baseline summary user interface 630 also includes a portion of a nighttime baseline affordance 636 similar to the morning baseline affordance 632 and the evening baseline affordance 634. The nighttime baseline affordance 636 corresponds to physiological data (e.g., blood glucose measurements) received by the device 600 during the nighttime quadrant of the baseline phase (e.g., the nighttime time period (e.g., from 22:00 to 04:00)). In some embodiments, after receiving the scroll input, the device 600 displays the baseline summary user interface 630, which shows the entire nighttime baseline affordance 636 and an optional view all nighttime data affordance similar to the optional view all morning data affordance 632c and the optional view all evening data affordance 634c.

[0212] In the described example, the device 600 displays affordances corresponding to physiological data received during the morning quadrant, evening quadrant, and night quadrant during a baseline phase (e.g., an initial time period (e.g., ten days, a week)), and does not display affordances corresponding to physiological data received during the afternoon quadrant (e.g., an afternoon time period (e.g., from 10:00 to 16:00)). In some embodiments, the device 600 determines one or more portions of the day with the highest elevated blood glucose measurement results (e.g., during the baseline phase) based on the received physiological data and displays the baseline affordances accordingly. In some embodiments, the portion of the day with the highest elevated blood glucose measurement results and therefore displayed by the device 600 contains the highest measurement results (e.g., the three highest measurement results between the four quadrants of the day). In some embodiments, the portion of the day displayed by the device 600 has the highest elevated value. In some embodiments, the portion of the day displayed by the device 600 spends more time in an elevated measurement state. Therefore, in some embodiments, the device 600 displays a combination of the morning quadrant, the afternoon quadrant, the evening quadrant, and the night quadrant. In some embodiments, device 600 displays an indicator corresponding to each quadrant (e.g., morning, afternoon, evening, night).

[0213] like Figure 6J As shown, device 600 receives a tap input 640 corresponding to a selection of the continue affordance 630b. In response to detecting the tap input 640, device 600 displays a task selection user interface 642 on touch screen display 602, such as Figure 6K As shown. Task selection user interface 642 currently includes a portion of morning task affordance 644, evening task affordance 646, and nighttime task affordance 648. Each task affordance (e.g., 644, 646, 648) includes a plurality of selectable tasks (e.g., three) to be selected to be performed during a specified portion of the day (e.g., morning, evening). The selectable tasks are to perform physical activity (e.g., "try an activity before and after breakfast") or to eat or give up eating a type of food (e.g., "eat carbohydrates during dinner"; "avoid snacks before and after dinner") during a specified portion of the day. In some embodiments, the tasks presented that affect the elevated blood glucose measurement results are the same for each user (e.g., standard tasks). In some embodiments, the execution of these tasks has a positive effect on the blood glucose measurement results (e.g., reducing the increase in blood glucose measurement results). Device 600 receives a swipe input 650 corresponding to a request to scroll task selection user interface 642.

[0214] In response to detecting the swipe input 650, the device 600 displays another portion of the task selection user interface 642, such as Figure 6LAs shown. The task selection user interface 642 shows a portion of the morning task enable representation 644 together with the evening task enable representation 646 and the night task enable representation 648. The evening task enable representation 646 includes three selectable tasks 646a-646c to be performed to affect the blood glucose measurements received by the device 600 during the evening. The night task enable representation 648 includes three selectable tasks 648a-648c to be performed to affect the blood glucose measurements received by the device 600 during the night. Selectable task 646a (which reads "Try an activity during dinner") is a task to be performed during the evening quadrant (e.g., a time period during the evening (e.g., from 16:00 to 22:00)) to affect the blood glucose measurements received by the device 600 during the same time period. Optional task 648b, which reads "Try smaller portions of high-reacting foods at dinner," is a task to be performed at dinner (typically in the evening quadrant) to affect blood glucose measurements received by device 600 during the night quadrant (e.g., the time period of the night (e.g., from 22:00 to 04:00)). In some embodiments, the task is to be performed within a specified portion of the day. In some embodiments, the task may be performed around the specified portion of the day. In some embodiments, the task is to be logged within a specified portion of the day.

[0215] exist Figure 6L , device 600 detects tap input 652a corresponding to selection of selectable task 648a and tap input 652b corresponding to selection of selectable task 646a. Figure 6M As shown, in response to receiving tap inputs 652a and 652b, the device 600 displays selectable tasks 646a and selectable tasks 648a on the touch screen display 602 with check marks as confirmation indications that each task has been selected. When selecting a task, the device 600 displays selectable affordances "Learn More" and "Examples" below the selected tasks 646a and 648a. In some embodiments, the selection of the "Learn More" affordance causes the device 600 to display additional information about the selected task. In some embodiments, the selection of the "Examples" affordance causes the device 600 to display one or more examples corresponding to the selected task (e.g., take a walk after dinner; ride a bike before dinner walk; choose a low-carb dessert before going to bed; give up dessert). When selecting tasks 646a and 648a, the device 600 displays a continue affordance 642a (which reads "Select 2 action items"). The device 600 detects a tap input 654 corresponding to a selection of the continue enable indication 642a, which completes the action phase establishment.

[0216] In response to receiving the tap input 654 to complete the action phase establishment, the device 600 displays a progress user interface 656, such as Figure 6N The device 600 also displays a progress tab indicator 616c for navigating to a progress user interface 656. The progress user interface 656 includes a counter 656a having a real-time count of the number of completed tasks (e.g., "Completed Action Items") (currently shown as "0") and the number of days remaining (currently shown as "7"). The action phase for the glucose monitoring feature is a predetermined time period (e.g., 7 days, 10 days), as indicated by the number of days remaining.

[0217] Figure 6N The progress user interface 656 also includes an evening region 658 and a portion of a nighttime region 660. Each region contains descriptive text for when to perform the selected task. The evening region 658 shows the selected task 646a, "Try an activity before or after dinner," along with instructions for tracking and selectable affordances "Learn more" and "Examples." The nighttime region 660 contains elements similar to those of the evening region 658. In some embodiments, the device 600 detects a swipe input to scroll the displayed progress user interface 656 and displays the entire evening region 658. The device 600 detects a tap input 662 corresponding to a selection of the hour tab affordance 616a and, in response, navigates to the corresponding Figure 6G and Fig.6O The hourly log user interface shown is similar to hourly log user interface 610 .

[0218] exist Fig.6O , several days have passed and the current date is August 14, as indicated by the device 600 above. In some embodiments, the device 600 displays an hourly log user interface 610, wherein the chart area 612b includes the current time (e.g., 20:00) along the x-axis. In some embodiments, the device 600 detects a swipe input to scroll the chart area 612b to display the blood glucose data collected at an earlier time. In this example, the device 600 displays an hourly log user interface 610, wherein the chart area 612b shows a chart line 612c from about 09:30 to 16:00. The meal icon 612f corresponds to the "bagel" log entry 614f. The device 600 detects a tap input 664 corresponding to the selection of the activity log record affordance 614b.

[0219] In response to receiving a tap input 664 at the activity logging enable indication 614b, the device 600 initiates logging of the activity, such as Figure 6P As shown in the log entry creation user interface 618 in FIG. Fig.6DAs discussed, log entry creation user interface 618 includes selectable affordances corresponding to various activities (e.g., relaxing, walking, running). Device 600 detects tap input 666a at walking affordance 620c and then detects tap input 666b at next affordance 618e. In response to receiving tap inputs 666a and 666b, device 600 displays task confirmation user interface 668, as shown in FIG. Figure 6Q shown.

[0220] Figure 6Q The device 600 is shown displaying a task confirmation user interface 668 on a touch screen display 602. FIG. 6I to FIG. 6N As shown, when creating a log entry after selecting a task to be performed during the action phase, a task confirmation user interface 668 is presented. The task confirmation user interface 668 includes a task 646a (which reads "Try an activity during dinner") and a task 648a (which reads "Avoid high-carbohydrate food or drinks before going to bed"), both of which are in reference to FIG. 6I to FIG. 6N The task selection period described is selected. In some embodiments, multiple (e.g., three or more) tasks are presented in the task confirmation user interface 668. In some embodiments, the task confirmation user interface 668 presents the task corresponding to the time specified on the log entry creation user interface 618 (e.g., when the time specified on the log entry creation user interface 618 is between 16:00 and 22:00, the task 626a is presented), and the task not corresponding to the specified time is not presented. In some embodiments, when the time specified on the log entry creation user interface 618 does not correspond to the part used to perform the selected task in a day, the device 600 abandons displaying the task confirmation user interface 618 (e.g., for the log entry not between 16:00 and 22:00 or between 22:00 and 04:00, the task confirmation user interface 618 is not displayed). In some embodiments, the device 600 displays the task confirmation user interface 618 regardless of the time specified on the log entry creation user interface 618, and the task may be marked as completed outside the portion of the day designated for performing the task (e.g., creating a log entry at 20:00 and selecting task 648a to be performed between 22:00 and 04:00). In some embodiments, in response to detecting input selecting a task to be marked as completed outside the portion of the day designated for performing the task, the device 600 displays an information message that the effect of performing the selected task outside the portion of the day designated for performing the task is uncertain on the collected physiological data (e.g., "The effect of your 20:00 log entry "Avoid high-carbohydrate foods or beverages before bedtime" is uncertain on your nighttime blood glucose measurement results").

[0221] exist Figure 6Q In the example detailed in , device 600 detects a tap input 670a corresponding to a selection of task 646a. In some embodiments, in response to the selection of task 646a, task 646a is shown with a check mark indication. Device 600 also detects a tap input 670b corresponding to a selection of save affordance 668a. In response to receiving tap input 670b, device 600 saves the activity log entry and displays hourly log user interface 610.

[0222] like Figure 6R As shown, the device 600 displays an hourly log user interface 610 with an updated chart area 612b on the touch screen display 602. The updated chart area 612b shows a time period ranging from 15:30 to 22:00 with a chart line 612c and an activity icon 612g. The activity icon 612g corresponds to the "Walking" log entry 614g. The "Walking" log entry 614g includes an indication that task 646a is satisfied by walking at 20:00. In contrast, the "Bagel" log entry 614f does not satisfy the task selected by the user and therefore does not include an indication similar to the indication of the "Walking" log entry 614g. The device 600 receives a tap input 672 corresponding to a selection of the progress tab enable indication 616c, and in response, displays the progress user interface 656, as shown. Figure 6S shown.

[0223] like Figure 6S As shown, the device 600 displays the reference Figure 6N The described progress user interface is similar to progress user interface 656. Although Figure 6N The progress user interface 656 is shown on the first day of the action phase (e.g., August 11, after completing the action phase setup), but Figure 6S A progress user interface 656 is shown during an action phase (eg, August 14). A counter 656a is updated to indicate that five action items (eg, tasks) have been completed and there are three days left in the action phase to perform the tasks displayed on the progress user interface 656.

[0224] exist Figure 6S, the evening region 658 includes the selected task 646a together with a "walking" log entry 614g and a "biking" log entry 614h corresponding to the log entry for the task 646a that satisfies "try an activity before or after dinner". Log entries 614g and 614h include elevation values ​​indicating the effect of performing an activity (e.g., walking, biking) on ​​blood glucose measurements received by the device 600 during the evening period (e.g., from 16:00 to 22:00) of the day when the activity was performed (e.g., walking on August 14, biking on August 13). Both walking and biking result in a decrease in the evening elevation score for their respective days (e.g., to "3", to "2") compared to the typical evening elevation score "7" received by the device 600 during the baseline phase. The device 600 receives a swipe input 674 corresponding to a request to scroll the progress user interface 656 to view more of the night region 660.

[0225] like Figure 6T As shown, in response to the swipe input 674, the device 600 displays a more progress user interface 656, which now shows the portion of the night region 658 including the "ride" log entry 614h and the entire night region 660. The night region 660 includes the reference Figure 6N Information similar to the information described includes task 648a, and also includes log entries corresponding to performing task 648a (e.g., "sugar-free cheesecake," "low-carb oatmeal cookies," "dinner with water").

[0226] The device 600 receives a tap input 676 corresponding to a selection of the “ride” log entry 614h. Figure 6U As shown, in response to detecting the tap input 676, the device 600 displays a logbook details user interface 678 on the touch screen display 602. The logbook details user interface 678 includes details about the "ride" logbook entry 614h, including the date and time the activity was performed (e.g., 18:30 on August 13) and the elevation values ​​of the blood glucose measurements received by the device 600 during the evening period of August 13 (e.g., from 16:00 to 22:00). The logbook details user interface 678 also includes the selected task 646a and a typical evening elevation score of "7".

[0227] exist Figure 6U , the log details user interface 678 shows a comparison area 678a. The comparison area 678a includes a chart having an evening baseline curve graph 634a overlaid on (e.g., superimposed on, displayed simultaneously with) the riding curve graph 678b. As previously described with reference to Figure 6JAs described, the evening baseline graph 634a is a graphical representation of blood glucose measurements received by the device 600 during the evening period (e.g., from 16:00 to 22:00) during the baseline phase. The riding graph 678b is a graphical representation of blood glucose data received by the device 600 during the evening period on August 13, and includes an activity icon at 18:30 showing when task 646a was performed. Both the evening baseline graph 634a and the riding graph 678b include portions that are visually different (e.g., thicker line width) from the rest of the graph. The visually different portions of each graph represent blood glucose measurements that are above a predetermined threshold and are considered elevated measurements.

[0228] Log details user interface 678 includes a selectable exit affordance 678c. Device 600 detects a tap input 680 corresponding to a selection of exit affordance 678c, and in response, device 600 stops displaying log details user interface 678 and displays progress user interface 656, as shown in FIG. Figure 6V shown.

[0229] exist Figure 6V , device 600 returns to displaying progress user interface 656. Progress user interface includes selectable plus-sign affordance 660a within nighttime region 660. Device 600 detects tap input 682 corresponding to selection of plus-sign affordance 660a and, in response, initiates a process for selecting a new task to be performed during the nighttime time period.

[0230] like Figure 6W As shown, in response to receiving the tap input 682, the device 600 displays a task adding user interface 684. The task adding user interface 684 includes selectable tasks 648b and 648c to be performed to affect the blood glucose measurement results received by the device 600 at night. Tasks 648b and 648c are tasks that were not selected during the action phase establishment, and reference FIG. 6I to FIG. 6N Detailed description further. In some embodiments, the plus sign indicator 660a is not displayed in the nighttime region 660, and thus the task adding user interface 684 is not available until the current task (e.g., "Avoid high-carbohydrate food or beverages before going to bed") has been completed (e.g., performed, logged) multiple times (e.g., three times). The device 600 detects a tap input 686a corresponding to a selection of the task 648c (which reads "Eat a high-fiber snack before going to bed"). In some embodiments, in response to receiving the tap input 686a, the device 600 displays the task 648c with an indication that it has been selected (e.g., with a check mark).

[0231] like Figure 6XAs shown, after receiving tap input 686a, device 600 detects tap input 686b corresponding to the selection of saving affordance 684a. In response to receiving tap input 686b, device 600 displays progress user interface 656 with newly selected task 648c listed in nighttime region 660. Within nighttime region 660, task 648a shows three log entries corresponding to performing "avoid high-carbohydrate food or beverage before going to bed", and task 648c indicates that the log entry corresponding to performing "eat high-fiber snacks before going to bed" has not been completed. In some embodiments, after adding a new task, task 648c is displayed as a selectable option on task confirmation user interface 668 while creating a new log entry.

[0232] Now turn to Figure 6Y , the date is currently August 18, seven days after starting the action phase, and the current time is 09:00. The device 600 displays a pull-out notification 688 above the hourly log user interface 610. In some embodiments, the pull-out notification 688 is displayed above the progress user interface. The pull-out notification 688 indicates that the action phase is now complete and the next phase of the glucose monitoring feature (e.g., the target phase) is available. The device 600 detects a tap input 690 within the pull-out notification 688 corresponding to a selection of the continue enable indication 688a (e.g., "Add target"). In response to receiving the tap input 690, the device 600 initiates the creation of a Figure 6Z in the target.

[0233] like Figure 6Z As shown, the device 600 displays a goal selection user interface 692 on the touch screen display 602. The goal selection user interface 692 includes selectable tasks 646a, 648a, and 648c, which are performed and tracked during the action phase. In some embodiments, if the task is completed multiple times (e.g., three times) during the action phase, the task is displayed on the goal selection user interface 692. The device 600 detects a tap input 694a corresponding to a selection of task 646a "Try an activity before or after dinner." In some embodiments, in response to receiving the tap input 694a, the device 600 displays task 646a with an indication that it is selected (e.g., with a check mark). After selecting task 694a, the device 600 receives a tap input 694b corresponding to a selection of the continue enable indication 692a. In response to detecting the tap input 694b, the device 600 displays a goal customization user interface 696, as shown in FIG. Figure 6AA shown.

[0234] exist Figure 6AA, device 600 displays a target customization user interface 696. Target customization user interface 696 includes task 646a together with selectable text fields 696a and 696b and day field 696c for customizing a target based on task 646a. Text field 696a corresponds to specifying an activity to be performed (e.g., walking, yoga, running), and text field 696b corresponds to specifying the duration of the activity to be performed (e.g., 20 minutes, 60 minutes). Device 600 detects tap inputs 698a and 698b corresponding to the selection of text fields 696a and 696b. In some embodiments, in response to receiving tap inputs 698a and 698b at text fields 696a and 696b for customizing a target, device 600 displays a keyboard for inputting custom text. Device 600 also detects tap inputs 698c corresponding to the selection of day field 696c. In some embodiments, in response to receiving a tap input 698c at the day field 696c, the device 600 displays a list from one to seven for selecting how many times per week to perform the goal. In some embodiments, the goal customization user interface 696 includes a customization field for specifying when to perform the customized goal based on task 646a during a recurring subset of the recurring time period (e.g., after eating dinner, before eating dinner, while eating).

[0235] exist Figure 6AB , device 600 displays a goal customization user interface 696 having text fields 696a and 696b complete with "Do 20 minutes of yoga" and a day field 696c set to "5" times per week. Device 600 receives a tap input 6100 corresponding to a selection of the continue affordance 696d. In response to detecting the tap input 6100, device 600 saves the customized goal 6102, as shown in FIG. Figure 6AC shown.

[0236] exist Figure 6AC , device 600 continues to display goal customization user interface 696 with customized goal 6102 based on task 646a. Goal customization user interface 696 now includes additional selectable affordances for “edit” and “delete” customized goal 6102. Goal customization user interface 696 also includes selectable add affordance 696e. In some embodiments, selecting add affordance 696e causes device 600 to display a menu associated with Figure 6Z Device 600 receives tap input 6104 corresponding to a selection of save affordance 696f. In response to detecting tap input 6104, device 600 displays progress user interface 656, such as Figure 6AD shown.

[0237] exist Figure 6AD , the device 600 displays a progress user interface 656 on the touch screen display 602 that is updated when in the goal stage. The progress user interface 656 includes selectable week enable indications 656b and 656c. The week enable indication 656c corresponding to the current week of "August 18 to August 24" is visually highlighted (e.g., in bold) to indicate that the week enable indication is currently selected. Below the week enable indication 656c, the device 600 displays "0%" to indicate that the goal has not yet been completed. In some embodiments, in response to selection of the week enable indication 656b for the week of "August 11 to August 17" corresponding to the action stage, the device 600 displays the week enable indication 656b as visually highlighted (e.g., in bold) and includes an evening area 658 and a nighttime area 600 in the progress user interface 656, as shown in reference to FIG. Figure 6S to Figure 6V As described.

[0238] In this example, Figure 6AD , when the weekly enable representation 656c is selected, the progress user interface 656 includes the customized goal 6102 and the selected task 646a. The customized goal 6102 includes progress indicators 6102a-6012e. Progress indicator 6102a is a plus sign that can be selected to confirm the completion instance of the customized goal. Progress indicator 6102e has "Goal" written below it to indicate that at the fifth completion instance of the customized goal, the goal has been met for the week.

[0239] Now turn to Figure 6AE , the date is currently August 19, and the time is 20:00. Device 600 displays a progress user interface 656 with a customized goal 6102 and log entries 614i and 614j. In some embodiments, log entries 614i and 614j are created via selecting activity logging affordance 614b on hourly log user interface 610, similar to reference 614. Fig.6O As described. The "walking" log entry 614j satisfies the task 646a "try an activity before and after dinner", however, it is not performing the activity of the customized goal 6102. In contrast, the "yoga" log entry 614i satisfies the task 646a and is performing the activity of the customized goal 6102. In some embodiments, the device 600 only displays the log entries that meet the customized goal (e.g., displaying the "yoga" log entry 614i but not the "walking" log entry 614j). In some embodiments, the device 600 displays all log entries that satisfy the task 646a "try an activity before and after dinner" performed during the week of August 18 to August 24. The device 600 detects a tap input 6106 corresponding to the selection of the progress indicator 6102a.

[0240] like Figure 6AF As shown, in response to receiving tap input 6106, device 600 updates progress indicator 6102a to show a check mark and updates progress indicator 6102b to a selectable plus sign. Below the weekly indicator 656c, device 600 updates from "0%" to "20%", indicating that the customized goal 6102 has been completed once in five times.

[0241] At the end of the week, on August 24, if Figure 6AG As shown, device 600 displays goal review user interface 6108. Goal review user interface 6108 includes customized goal 6102, where progress indicators 6102a-6102d are filled with check marks and progress indicator 6102e is empty to indicate that customized goal 6102 was completed four out of five times between August 18 and August 24. Device 600 detects tap input 6110 corresponding to selection of continue enable indication 6108a. In response to receiving tap input 6110, device 600 displays rating user interface 6112, as shown in FIG. Figure 6AH shown.

[0242] exist Figure 6AH , device 600 displays a rating user interface 6112 including a rating area 6114. Rating area 6114 includes a rating scale from "0 bad" to "10 good" and a sliding enable representation 6114a positioned at "5" to start. In some embodiments, sliding enable representation 6114a is initially positioned at "0 bad". Device 600 detects a swipe input 6116 corresponding to selection and movement of sliding enable representation 6114a.

[0243] like Figure 6AI As shown, in response to receiving swipe input 6116, device 600 moves slide affordance 6114a to the left and updates “your answer” to “7.” Device 600 receives tap input 6118 corresponding to selection of continue affordance 6112a and, in response, proceeds to target customization user interface 696.

[0244] exist Figure 6AJ In the example of FIG. 6 , target customization user interface 696 includes a prompt to modify the customized target 6102 based on task 646a using selectable edit affordance 696g or selectable delete affordance 696h. In some embodiments, selecting edit affordance 696g causes device 600 to display Figure 6AB Target customized user interface 696. In some embodiments, when the device 600 is displaying Figure 6ABWhen the goal customization user interface 696 is used to edit the customized goal, the device 600 receives a tap input to change (e.g., modify, edit, update) the customized goal to be performed during a subsequent time period (e.g., next week, August 25 to August 31). In some embodiments, in response to the selection of the delete enable indication 696h, the device 600 stops displaying (e.g., deletes, removes) the customized goal 6102. The goal customization user interface 696 also includes a prompt to add a new goal using an optional add enable indication 696e. In some embodiments, selecting the add enable indication 696e causes the device 600 to display the corresponding Figure 6Z The target selection user interface shown is similar to the target selection user interface 692 with selectable tasks 648a and 648b. In some embodiments, the selection of task 648a or 648b initiates the reference Figures 6AA to 6AD In some embodiments, selecting the save enable indication 696f causes the device 600 to display a progress user interface 656, similar to the reference 696f. Figures 6AC to 6AD The process described.

[0245] like Figure 6AI As shown, the device 600 receives a score of "7" for the customized goal 6102 performed from August 18 to August 24. In some embodiments, if the score is a high range score (e.g., 7 or higher), the device 600 displays a goal customization user interface 696, such as in Figure 6J In some embodiments, if the score of the customized goal is a medium range score (e.g., from four to six), the device 600 displays a feedback user interface 6120, such as Figure 6AK shown. Figure 6AK The feedback user interface 6120 includes a questionnaire for evaluating the success factors for completing the customized goal. In some embodiments, if the score of the customized goal is a low range score (e.g., three or lower), the device 600 displays an obstacle user interface 6122, such as Figure 6AL shown. Figure 6AL The obstacle user interface 6122 includes a questionnaire related to determining obstacles (e.g., obstacles) for completing the customized goal. In some embodiments, the device 600 also displays examples of (e.g., time management, ways to maintain motivation) for improving the success and scoring of the customized goal. In some embodiments, the device 600 also displays suggestions (e.g., tips) for improving the success and scoring of the customized goal.

[0246] Figure 7Flowchart showing a method for recording user activities using an electronic device log during a subset of a recurring time period according to some embodiments. Method 700 is performed at a computer system (e.g., 100, 300, 500, 600), which communicates with a display generation component (e.g., 602) (e.g., a display controller, a touch-sensitive display system; and / or a display (e.g., integrated or connected)) and one or more input devices (e.g., 112, 160, 602) (e.g., a gyroscope, an accelerometer, a microphone, and / or a touch-sensitive surface). Some operations in method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0247] In some embodiments, the electronic device (e.g., 600) includes a computer system. The computer system optionally communicates (e.g., wired communication, wireless communication) with a display generation component (e.g., 602) and one or more input devices (e.g., 112, 160, 602). The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separated from the computer system. One or more input devices are configured to receive input, such as a touch-sensitive surface that receives user input. In some embodiments, one or more input devices are integrated with the computer system. In some embodiments, one or more input devices are separated from the computer system. Therefore, the computer system can send data (e.g., image data or video data) to an integrated or external display generation component via a wired or wireless connection to generate content in a visual manner (e.g., using a display device), and can receive input from one or more input devices via a wired or wireless connection.

[0248] As described below, method 700 provides an intuitive way to log user activities during a subset of recurring time periods. The method reduces the cognitive burden on the user of logging user activities during a subset of recurring time periods, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to log user activities faster and more efficiently during a subset of recurring time periods saves power and increases the time interval between battery charges.

[0249] The computer system displays (706) via a display generation component (e.g., 602) a task selection user interface (e.g., 642) having a set of one or more selectable task user interface objects (e.g., 644, 646, 648). The set of one or more selectable task user interface objects includes, based on determining (708) a first subset of recurring time periods (e.g., the time of day at which the device 600 receives data to display the line graph 634a) (e.g., a specific time quadrant of each day (e.g., 6 hours of the day, morning, afternoon, evening, night); a day of the week (e.g., Monday, Tuesday) physiological data (e.g., 634a) (e.g., data regarding blood glucose levels (e.g., quantification of elevated blood glucose levels over a duration); baseline blood glucose measurements) satisfying a first set of criteria (e.g., as shown by the elevated value scales of 630a, 634b). In some embodiments, the first set of criteria includes criteria that are satisfied when the physiological data exceeds a threshold value (e.g., the blood glucose level exceeds the threshold value blood glucose level)), corresponding to the first subset of recurring time periods (e.g., within the first subset of recurring time periods). Figure 6N In some embodiments, based on determining that the physiological data for the first subset of recurring time periods does not satisfy the first set of criteria, the one or more selectable task user interface objects do not include the first selectable task user interface object. Based on determining (710) that the physiological data for a second subset of recurring time periods (e.g., the times of day during which the device 600 receives data to display the line graph within 636) that is different from the first subset of recurring time periods (e.g., the times of day during which the device 600 receives data to display the line graph within 636) satisfies the first set of criteria (e.g., the increasing values ​​within 636 as shown by the increasing value scale of 630a), the set of one or more selectable task user interface objects includes a first set of selectable task user interface objects corresponding to the physiological data for the second subset of recurring time periods (e.g., the times of day during which the device 600 receives data to display the line graph within 636), which corresponds to the time periods to be displayed during the first subset of recurring time periods. Figure 6N In some embodiments, based on determining that the physiological data for the second subset of the recurring time periods satisfies the first set of criteria, the one or more selectable task user interface objects do not include the first selectable task user interface object.

[0250] While displaying the task selection user interface (eg, 642), the computer system receives (712) a first set of one or more inputs (eg, 652a, 652b, 654) (eg, tap inputs) via one or more input devices (eg, 112, 160).

[0251] In response to receiving (714) the first set of one or more inputs and based on determining that the first set of one or more inputs includes an input (e.g., 652a) selecting a first selectable task user interface object (e.g., 646a), the computer system performs a task selection operation during a first subset of the cycle time periods (e.g., during Figure 6N In some embodiments, the computer system enables (716) logging (e.g., via recording; tracking; logging of a first type of user activity (e.g., 646a) during a period (e.g., specified in 646 and 660 of the recurring time periods) (e.g., during future occurrences of a first subset of recurring time periods). In response to receiving (714) the first set of one or more inputs and based on determining that the first set of one or more inputs includes an input (e.g., 652b) selecting a second selectable task user interface object (e.g., 648a), the computer system enables (718) logging of a second type of user activity (e.g., 648a) during a second subset of recurring time periods (e.g., as specified in 660). In some embodiments, logging of the first type of user activity during the first subset of recurring time periods is not enabled. Displaying a first selectable task user interface object corresponding to the first user activity or a second selectable task user interface object corresponding to the second user activity based on whether the physiological data for the different subsets of recurring time periods meets a set of criteria provides feedback to the user regarding the physiological data for the different subsets of recurring time periods. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0252] Prior to displaying the task selection user interface (e.g., 642), the computer system receives (702) (e.g., via one or more physiological sensors in communication with the computer system (e.g., integrated into the computer system; in communication with the computer system); data transmission from another computer system) a first predetermined time period (e.g., as described in reference to FIG. 6A to FIG. 6GA first set of physiological data (e.g., as represented by 612c) from August 1 to August 10 (e.g., 10 days, 14 days, 30 days) is described, wherein the physiological data of a first subset of recurring time periods (e.g., the recurring time period is the period from 12PM to 6PM of each day of the predetermined time period) is based on (e.g., derived from, extrapolated from, extracted from) a subset (e.g., 632a, 634a) of the first set of physiological data (e.g., as represented by 612c from August 1 to August 10) of the predetermined time period. In some embodiments, the physiological data is blood glucose data for the period from 12PM to 6PM of the 10-day data collection period.

[0253] After receiving the first set of physiological data for the first predetermined time period (e.g., in response to completing the receipt of the first set of physiological data for the predetermined time period (e.g., at the end of the predetermined time period)), the computer system displays (704) a data summary user interface (e.g., 630) that includes a first representation (e.g., 632a, 632a) (e.g., graphical user interface object; representation in a graph; numerical value) of physiological data in the first set of physiological data for the first predetermined time period that exceeds a first threshold value (e.g., below the values ​​of 632a and 634b). In some embodiments, the first representation of the physiological data includes an indication of a subset of recurring time periods (e.g., a 6-hour quadrant of a day) during which the physiological data was obtained. In some embodiments, the data summary user interface includes a second representation of physiological data in the first set of physiological data for the predetermined time period that exceeds the threshold value. In some embodiments, the second representation of the physiological data corresponds to data from a different subset of recurring time periods (e.g., from a different quadrant of a day) than the data corresponding to the first representation of the physiological data. Displaying the first representation of the physiological data that exceeds the threshold value provides additional feedback to the user as a subset of the received data. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0254] Wherein before receiving the first set of physiological data for the first predetermined time period (e.g., before receiving the entire first set of physiological data), the task selection user interface (e.g., 642) is not available for display (e.g., locked; not available for display upon user request), and in response to receiving the first set of physiological data for the first predetermined time period (e.g., receiving the entire first set of physiological data), the computer system provides the task selection user interface (e.g., 642) for display (e.g., by displaying notification 626) (e.g., making the task selection user interface available for display (e.g., from a previously unavailable state)). In some embodiments, in response to receiving the first set of physiological data for the predetermined time period, at least a first interface of a set of user interfaces including the task selection user interface is displayed. In response to receiving the data, the task selection user interface is provided for displaying access to interfaces that operate based on whether the data is available. Performing optimization operations when a set of conditions have been met and no further user input is required enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0255] In some embodiments, the first type of user activity to be performed during the first subset of the recurring time periods is performing a physical activity (e.g., 614g, 614h) (e.g., exercising) or consuming food or drinking a beverage (e.g., Figure 6T in the log entries listed below 648a) (e.g., eating).

[0256] After enabling logging of the first type of user activity during the first subset of the recurring time periods and after enabling logging of the second type of user activity during the second subset of the recurring time periods, the computer system displays a progress user interface (e.g., 656) (e.g., an interface including representations of completed user activities that have been enabled for logging), based on determining that the user activity has been completed during the first subset of the recurring time periods (e.g., during Figure 6SA first instance of a first type of user activity (e.g., 646a) (e.g., physical activity (e.g., exercising); consuming food or drinking beverages (e.g., eating carbohydrates last)) is logged (e.g., "walking" in 614g, "riding" in 614h) during a time period specified in 658 of ) (e.g., the recurring time period is the period from 12PM to 6PM each day), the progress user interface including displaying a representation (e.g., 614g, 614h) (e.g., a user interface object (e.g., a selectable interface object (e.g., an enable representation)) corresponding to the first instance of the first type of user activity within a first portion (e.g., 658) (e.g., the first third) of the progress user interface (e.g., a user interface containing all completed action items), wherein the first portion of the progress user interface corresponds to a first subset of the recurring time period (e.g., a portion dedicated to logged events from 12PM to 6PM each day).

[0257] After enabling logging of the first type of user activity during the first subset of the recurring time periods and after enabling logging of the second type of user activity during the second subset of the recurring time periods, the computer system displays a progress user interface (e.g., 656) (e.g., an interface including representations of completed user activities that have been enabled for logging), based on determining that the user activity has been completed during the second subset of the recurring time periods (e.g., during Figure 6T The first instance (e.g., 648a) of a second type of user activity (e.g., physical activity (e.g., exercise); consuming food or drinking beverages (e.g., last eating carbohydrates)) is logged during the time period specified in 660 of FIG. 1 (e.g., the recurring time period is the period from 12PM to 6PM every day) (e.g., the recurring time period is the period from 12PM to 6PM every day). Figure 6T ), the progress user interface including displaying a representation (e.g., first one-third) corresponding to the first instance of the second type of user activity within a second portion (e.g., 660) (e.g., first third) of the progress user interface (e.g., a user interface including all completed action items). Figure 6T) (e.g., a log entry below 648a in the progress user interface) (e.g., a user interface object (e.g., a selectable interface object (e.g., an enable representation)), wherein a second portion of the progress user interface corresponds to a second subset of the recurring time periods (e.g., a portion dedicated to logged events from 12PM to 6PM for each day). In some embodiments, the representation of the completed user activity includes an increased score. In some embodiments, each portion of the progress user interface includes an increased score for the baseline measurement. In some embodiments, a representation of a second instance of the first type of user activity is being displayed within the first portion of the progress user interface. A user interface displaying representations of completed instances of user activity organized by a subset of recurring time periods provides the user with improved feedback about what logged activities the computer system has received during a particular subset of recurring time periods. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0258] After enabling logging of a first type of user activity during a first subset of recurring time periods, the computer system displays a first representation (e.g., 614h) (e.g., a user interface object (e.g., a selectable interface object (e.g., an affordance)) of a logged instance of the first type of user activity (e.g., 646a) (e.g., “riding” at 18:30).

[0259] The computer system receives a first input (eg, 676 ) (eg, a tap) corresponding to a representation of a logged instance of a first type of user activity.

[0260] In response to receiving the first user input, the computer system displays a comparison user interface (e.g., 678) that includes a first representation (e.g., a graphical user interface object; a representation in a graph; a numerical value) of physiological data (e.g., 634a) that exceeds a first threshold value in a first set of physiological data for a first predetermined time period.

[0261] In response to receiving the first user input, the computer system displays a comparison user interface (e.g., 678) that includes a second representation (e.g., a graphical user interface object; a representation in a graph) of physiological data corresponding to a logged instance of a first type of user activity (e.g., 678b) in a second set of physiological data (e.g., data collected during an action phase; data different from the first set of physiological data) (e.g., the physiological data was collected during a time period during which the logged instance of the first type of activity was performed).

[0262] In response to receiving the first user input, the computer system displays a comparison user interface (e.g., 678) that includes a first type of user activity (e.g., along the Figure 6U A second representation (e.g., similar or identical to the first representation graphic) of the logged instance of the activity glyph 678b of FIG. 678b) is provided. A user interface that displays the first representation and the second representation of the physiological data having the same subset of recurring time periods provides feedback to the user regarding the status of the data for the same subset of time periods received by the computer system. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0263] After the number of times that the first type of user activity has been logged exceeds the second threshold value (e.g., Figure 6V After the user selects the three logged entries listed below 648a in (e.g., performing the activity three or more times), the computer system displays a first selectable user interface object (e.g., 660a) (e.g., a plus button for adding a new user activity).

[0264] The computer system receives a second set of one or more inputs (e.g., 682, 686a, 686b) (e.g., tap inputs) via one or more input devices (e.g., 112, 160), wherein the second set of one or more inputs includes an input (e.g., 682) corresponding to a first selectable user interface object (e.g., a tap on a plus button). In some embodiments, the second set of one or more inputs includes one or more inputs identifying a type of user activity to be performed during the first subset of the recurring time periods.

[0265] In response to receiving the second set of one or more inputs, the computer system enables a first subset of the recurring time periods (e.g., Figure 6XIn some embodiments, the user activity of the third type (e.g., 648c) during the time period specified in 660 of the cycle time is recorded. In some embodiments, the action phase is initiated using two action items to be performed in different subsets of the cycle time period, and then the third action item is added to a subset in the subset, so that two or more action items can be performed in a subset of the cycle time period. In some embodiments, the third action item is added to the third subset of the cycle time period (e.g., the cycle time period is the period from 6PM to 12AM every day). In some embodiments, user activity (e.g., action item) is the same (e.g., not personalized) for all users. After satisfying the condition, display selectable user interface objects provide feedback that can perform additional operations to the user. Providing improved visual feedback to the user has just enhanced the operability of the device, and made the user-device interface more efficient (e.g., by helping the user to provide appropriate input and reduce user errors when operating the device / interacting with the device), which in turn reduces power use and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0266] After enabling logging of the first type of user activity during the first subset of recurring time periods, the computer system receives a third set of one or more inputs (e.g., 664, 666a, 666b, 670a, 670b), wherein the third set of one or more inputs includes initiating a log entry (e.g., in response to Fig.6O In some embodiments, the third set of one or more inputs includes one or more inputs that select or identify additional details of the log entry (e.g., the type of activity performed, the time the activity was performed; the current emotion).

[0267] After receiving input initiating a log entry, the computer system displays a selectable confirmation user interface object for a first type of user activity (e.g., Figure 6Q 646a, 648a shown on 668).

[0268] After receiving input that initiates a log entry and in response to receiving a third group of one or more inputs, based on determining that the third group of one or more inputs includes a selection of a selectable confirmation user interface object for the first type of user activity (e.g., 670a), the computer system log records an instance of the first type of user activity (e.g., 614g).

[0269] After receiving the input initiating the log entry and in response to receiving the third set of one or more inputs, based on determining that the third set of one or more inputs does not include a selection of a selectable confirmation user interface object for the first type of user activity, the computer system log records an event that is not an instance of the first type of user activity (e.g., similar to Figure 6R In some embodiments, logging an instance of a first type of user activity includes: displaying a selectable user interface object with an indication that the first type of user activity has been completed. In some embodiments, logging an event includes: displaying a selectable user interface object that does not include an indication that the first type of user activity has been completed. In some embodiments, the selectable user interface objects corresponding to the instance and the event are editable. In some embodiments, the selectable user interface object corresponding to the event is displayed only in the hour tab and not on the progress tab. In some embodiments, the selectable user interface object corresponding to the instance of the first type of user activity is displayed on both the hour tab and the progress tab. In some embodiments, initiating a log entry includes recording the time of day. In some embodiments, if the first type of user activity is performed during a time that is not a specified subset of the recurring time period, the log record includes an instance of the first type of user activity with an indication that the effect of performing the first type of user activity is uncertain (e.g., the action affects the glucose measurement result of the specified subset of the recurring time).

[0270] In some embodiments, enabling logging of the first type of user activity during the first subset of recurring time periods includes enabling logging of the first type of user activity during the first subset of recurring time periods for a second predetermined time period (e.g., as described in reference to Figures 6H to 6X Described as represented by the "remaining days" from August 11 to August 18 in 656a) (e.g., 7 days, 14 days). In some embodiments, after the second predetermined time period, at least one function for logging the first type of activity becomes disabled.

[0271] After the second predetermined time period ends, the computer system provides a goal creation user interface (e.g., 692) for display (e.g., making the goal creation user interface available for display (e.g., from a previously unavailable state)), wherein the goal creation user interface is unavailable for display until the second predetermined time period is completed. In some embodiments, the goal creation user interface is an interface corresponding to method 800. Providing the goal creation user interface for display after the predetermined time period ends allows access to the interface at a time point relevant to the functionality of the interface. Performing optimization operations when a set of conditions have been met and no further user input is required enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0272] It should be noted that the process described above with respect to method 700 (eg Figure 7 ) also apply in a similar manner to the methods described below. For example, method 800 optionally includes one or more features of the various methods described above with reference to method 700. For example, the target creation user interface of method 800 displays a set of one or more selectable target creation user interface objects, wherein the set of one or more selectable target creation user interface objects is based on logging the type of user activity during the first subset of the recurring time periods as in method 700. For the sake of brevity, these details are not repeated below.

[0273] FIG. 8A to FIG. 8B Flowchart showing a method for recording user activities using an electronic device log during a subset of a recurring time period according to some embodiments. Method 800 is performed at a computer system (e.g., 100, 300, 500, 600) (e.g., a smart phone, a smart watch), which communicates with a display generation component (e.g., 602) (e.g., a display controller, a touch-sensitive display system; and / or a display (integrated or connected)) and one or more input devices (e.g., 160) (e.g., a gyroscope, an accelerometer, a microphone, and / or a touch-sensitive surface). Some operations in method 800 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0274] As described below, method 800 provides an intuitive way to log user activities during a subset of recurring time periods. The method reduces the cognitive burden on the user of logging user activities during a subset of recurring time periods, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to log user activities faster and more efficiently during a subset of recurring time periods saves power and increases the time interval between battery charges.

[0275] The computer system displays (802) via a display generation component (e.g., 602) a target creation user interface (e.g., 692, 696) having a set of one or more selectable target creation user interface objects (e.g., 648a, 646a, 648c). Based on determining (804) that a first subset of the recurring time periods (e.g., Figure 6S A first type of user activity (e.g., an activity described with respect to 646a) (e.g., physical activity (e.g., exercising); eating or drinking certain foods) performed within a time period specified in 658 of ) (e.g., a specific time quadrant of each day (e.g., 6 hours of the day, morning, afternoon, evening, night); a day of the week (e.g., Monday, Tuesday)) satisfies a first set of criteria (e.g., within Figure 6Z In some embodiments, the first set of criteria includes criteria that are satisfied when the first type of user activity is performed more than a threshold number of times. In some embodiments, the first set of criteria includes criteria that are satisfied when it is determined that the first type of user activity has a positive effect on the physiological data. In some embodiments, based on determining that the first type of user activity performed within the first subset of the recurring time periods does not satisfy the first set of criteria, the one or more selectable target creation user interface objects do not include the first selectable target creation user interface object. In some embodiments, the first type of user activity performed within the first subset of the recurring time periods is logged according to the method of 700. In some embodiments, the first set of criteria includes criteria that are satisfied when the first type of user activity has been available for a predetermined time period (e.g., one week, the duration of an action phase). In some embodiments, the target creation user interface becomes available after the predetermined time period ends. Based on determining (806) that a second subset of the recurring time periods is different from the first subset of the recurring time periods (e.g., within Figure 6T A second type of user activity (e.g., the activity described with respect to 648a) performed within the time period specified in 660 of FIG. 6 satisfies the first set of criteria (e.g., within Figure 6Z), the group of one or more selectable user interface objects includes a second selectable target creation user interface object (e.g., 648a) corresponding to a second type of user activity to be performed during a second subset of the recurring time periods (e.g., a type of activity different from the first type of user activity).

[0276] While displaying the target creation user interface (eg, 692), the computer system receives (818) a first set of one or more inputs (eg, 694a, 694b, 698a, 698b, 698c) (eg, taps).

[0277] In response to receiving (820) a first set of one or more inputs and based on determining that the first set of one or more inputs includes input (e.g., 646a) selecting a first selectable target to create a user interface object (e.g., 646a), the computer system enables (822) logging (e.g., via recording of user input; tracking; logging) of a first type of user activity during a first subset of recurring time periods (e.g., during future occurrences of the first subset of recurring time periods) for a predetermined duration (e.g., 656c) (e.g., one week, 10 days).

[0278] In response to receiving (820) the first set of one or more inputs and based on determining that the first set of one or more inputs includes input selecting a second selectable target to create a user interface object (e.g., Figure 6Z In some embodiments, upon a tap at 648a in the display, the computer system enables (824) logging of a second type of user activity during a second subset of the recurring time periods for a predetermined duration (e.g., 656c). In some embodiments, logging of a first type of user activity during a first subset of the recurring time periods is not enabled. Displaying a first selectable target creation user interface object or a second selectable target creation user interface object based on whether the first type of activity or the second type of activity was performed provides feedback to the user about what type of activity was previously performed. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0279] In some embodiments, the goal creation user interface (e.g., 696) includes (808) (e.g., simultaneously, non-simultaneously) a set (810) of one or more selectable user interface objects (e.g., 696a) (e.g., text fields; selectable predefined options) that, when selected, configure (e.g., identify; specify; set) a subtype of the first type of user activity (e.g., 646a) (e.g., "yoga," as in Figure 6AB In some embodiments, the goal creation user interface (e.g., 696) includes (808) (e.g., simultaneously, non-simultaneously) a set (812) of one or more selectable user interface objects (e.g., 698b) (e.g., text fields; selectable predefined options) that, when selected, configure (e.g., identify; specify; set) a first subset of the recurring time periods (e.g., between Figure 6S In some embodiments, the goal creation user interface (e.g., 696) includes (808) (e.g., simultaneously, non-simultaneously) a set (814) of one or more selectable user interface objects (e.g., 696b) (e.g., text fields; selectable predefined options) that, when selected, indicate a duration for which the first type of user activity is to be performed (e.g., as in the example of the time period specified in 658 of ). Figure 6AB The first type of user activity is configured (e.g., identified; detailed instructions; set up) by displaying a selectable user interface object for the configuration target (e.g., 20 minutes discussed above) (e.g., 30 minutes; 60 minutes). Displaying a selectable user interface object for the configuration target provides the user with additional control options for customizing the first type of user activity. Providing additional control options enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0280] In some embodiments, the goal creation user interface includes (808) a set (816) of one or more selectable user interface objects (e.g., 696c) (e.g., text fields; selectable predefined options) that, when selected, configure (e.g., identify; specify; set) a target number of times (e.g., logged as being performed) a first type of user activity is to be performed during a first subset of recurring time periods within a predetermined duration (e.g., Figure 6ABDisplaying selectable user interface objects that configure targets provides the user with more control over the device. Providing additional control over the device enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0281] In some embodiments, the first set of criteria is met when a given type of user activity has been performed (e.g., performed and logged) at least once during a previously predetermined time period (e.g., 614g, 614h, log entries listed in 660) (e.g., action phase). In some embodiments, the first set of criteria is met when the physiological data indicates that the given type of user activity has a desired (e.g., positive) effect on a physiological parameter (e.g., blood glucose level). In some embodiments, for each given type of activity that meets the first set of criteria, the goal creation user interface (e.g., 692) includes a selectable goal creation user interface object for the given type of activity that meets the first set of criteria (e.g., as in Figure 6Z 646a, 648a, 648c discussed above). In some embodiments, the goal creation user interface provides goal creation user interface objects for all activity types performed during the action phase. Displaying selectable goal creation user interface objects for a given type of activity that meets the first set of criteria provides the user with additional feedback as to the particular activity performed. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0282] After enabling logging of the first type of user activity (e.g., 6102) during the first subset of recurring time periods for a predetermined duration, the computer system displays a target number of times (e.g., as in FIG. 1 ) to perform the first type of user activity (e.g., 6102) during the first subset of recurring time periods for the predetermined duration. Figure 6ABIn some embodiments, the representation includes an indication of the number of times that the first type of user activity has been completed during a predetermined time period. In some embodiments, the representation is seven empty circles, each representing a day, which are filled when the first type of user activity is completed. Displaying an indication of progress toward a target number of times to perform the first type of user activity during a first subset of the recurring time periods within a predetermined duration (e.g., a progress indicator) provides feedback to the user about what is needed to meet the goal. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0283] After enabling logging of the first type of user activity (e.g., 6102) during the first subset of cycle times for a predetermined duration and after the predetermined duration ends (e.g., at Figure 6AG 24, 2009), the computer system receives feedback corresponding to a first type of user activity (e.g., along Figure 6AH to Figure 6AI A second set of one or more user inputs (e.g., 6110, 6116, 6118) is provided with a rating scale (e.g., 6114a) at the first type of user activity (e.g., feedback indicating a user's emotion and / or an evaluation of performance of the first type of user activity over a predetermined duration).

[0284] After receiving the first set of one or more user inputs (e.g., after selection of 696g), and, in some embodiments, based on determining that feedback about the first type of user activity satisfies the first set of feedback criteria (e.g., the feedback is of the first type (e.g., negative feedback), the computer system displays a set of one or more selectable user interface objects (e.g., similar to Figure 6AB696a, 696b, and 696c at (e.g., text fields; selectable predefined options), the set of one or more selectable user interface objects, when selected, modify one or more characteristics of the first type of user activity (e.g., a target number of times to perform the activity; a duration within which the activity is to be performed) (e.g., modify to log during a second, upcoming predetermined time period). Displaying a set of one or more selectable user interface objects to modify one or more characteristics of the first type of user activity provides the user with more control over the device. Providing additional controls over the device enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0285] After enabling logging of the first type of user activity during the first subset of cycle times for a predetermined duration and ending at the predetermined duration (e.g., at Figure 6AG 24, 2009), the computer system receives a second set of one or more user inputs (e.g., 6110, 6116, 6118) corresponding to feedback about the first type of user activity (e.g., feedback indicating the user's emotion and / or an evaluation of the performance of the first type of user activity over a predetermined duration).

[0286] After receiving the second set of one or more user inputs (e.g., after selection of 696e), and, in some embodiments, based on determining that the feedback about the first type of user activity satisfies the first set of feedback criteria (e.g., the feedback is of the first type (e.g., negative feedback), the computer system displays a set of one or more selectable user interface objects (e.g., similar to Figure 6Z648a and 648b) (e.g., text fields; selectable predefined options), the set of one or more selectable user interface objects, when selected, enable logging of a third type of user activity, different from the first type of user activity, during a first subset of recurring time periods for a second predetermined duration (e.g., a subsequent period of 7 days) after the first predetermined time period. In some embodiments, different questions are displayed based on the selection of the ranked affordance (e.g., What went well? What could be done better?). In some embodiments, for selecting a low ranked affordance (e.g., 4 or lower), tips for overcoming obstacles are provided. In some embodiments, 6 tips are displayed for each action item category. In some embodiments, for selecting a high ranked affordance (e.g., 7 or higher), tips are not displayed and the option to modify the goal is advanced. Displaying a set of one or more selectable user interface objects to enable logging of the third type of user activity provides the user with more control over the device. Providing additional controls for the device without cluttering the UI with additional displayed controls enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0287] After enabling logging of the first type of user activity during the first subset of loop times for a predetermined duration, the computer system displays a progress user interface (e.g., 656) (e.g., an interface including a representation of completed user activity that has been enabled for logging), wherein the progress user interface includes a first selectable user interface object (e.g., 656b) corresponding to a previously predetermined time period (e.g., an action phase) that, when selected, displays a first selectable user interface object (e.g., 656c) corresponding to a previously predetermined time period (e.g., an action phase) during the previously predetermined time period (e.g., 614g, 614h, Figure 6S to Figure 6V660 of the computer system); a second selectable user interface object (e.g., 656c) corresponding to a predetermined duration, which, when selected, displays a representation of the logged instances (e.g., 614i, 614j) of the first type of user activity (e.g., the first type of user activity performed during the first subset of the recurring time periods) within the predetermined time period. Displaying a user interface with a selectable user interface object to view the logged activities within the predetermined time period provides the user with improved feedback about what logged activities the computer system has received. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0288] For the purpose of explanation, the preceding description is described by reference to specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or limit the invention to the disclosed precise form. According to the above teachings, many modifications and variations are possible. These embodiments are selected and described in order to best explain the principles of these technologies and their practical applications. Others skilled in the art can thus best utilize these technologies and various embodiments with various modifications suitable for the intended specific use.

[0289] Although the disclosure and examples have been fully described with reference to the accompanying drawings, it should be noted that various changes and modifications will become apparent to those skilled in the art. It should be understood that such changes and modifications are considered to be included within the scope of the disclosure and examples defined by the claims.

[0290] As described above, one aspect of the present technology is to collect and use data from various sources to improve the delivery to users of logged user activities during subsets of recurring time periods or any other content they may be interested in. The present disclosure contemplates that in some instances, these collected data may include personal information data that uniquely identifies or can be used to contact or locate a specific 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.

[0291] The present disclosure recognizes that the use of such personal information data in the present technology can be used to benefit users. For example, personal information data can be used to deliver targeted content based on user activities logged during a subset of recurring time periods that are of greater interest to the user. Therefore, the use of such personal information data enables the user to exercise planned control over the content delivered. In addition, the present disclosure also contemplates other uses of personal information data that benefit users. For example, health and fitness data can be used to provide insights into the user's overall health, or can be used as positive feedback to individuals using technology to pursue health goals.

[0292] This disclosure envisions that entities responsible for collecting, analyzing, disclosing, transmitting, storing or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as the collection and / or use of data changes. Personal information from users should be collected for legitimate and reasonable purposes of the entity and not shared or sold outside of these legitimate uses. In addition, such collection / sharing should be performed after receiving informed consent from the user. In addition, such entities should consider taking any necessary steps to safeguard and protect access to such personal information data and ensure that others who have access to personal information data comply with their privacy policies and processes. In addition, such entities may subject themselves to third-party assessments to demonstrate their compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted to specific types 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 access of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA), while health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained in each country for different types of personal data.

[0293] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of 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, with respect to logging user activities during a subset of a recurring time period, the technology of the present invention may be configured to allow a user to choose to "opt in" or "opt out" to participate in the collection of personal information data at any time during or after registration for a service. In another example, a user may choose not to provide data for logging user activities during a subset of a recurring time period. In yet another example, a user may choose to limit the length of time that data is retained or to prohibit the development of a baseline profile entirely. In addition to providing "opt-in" and "opt-out" options, the present disclosure also contemplates providing notifications related to access or use of personal information. For example, a user may be notified that their personal information data will be accessed when downloading an application, and then the user may be reminded again just before the personal information data is accessed by the application.

[0294] In addition, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use. Risks can be minimized by limiting data collection and deleting data once it is no longer needed. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. De-identification can be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than at the address level), controlling how data is stored (e.g., aggregating data between users), and / or other methods when appropriate.

[0295] 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 also be implemented without access to such personal information data. That is, various embodiments of the present technology will not fail to function properly due to the lack of all or a portion of such personal information data. For example, content may be selected and delivered to a user by inferring preferences 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 a content delivery service, or publicly available information.

Claims

1. A computer system configured to communicate with a display generation component, the computer system comprising: one or more processors; and A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: receiving a first set of physiological data for a first predetermined time period, wherein a first subset of the first set of physiological data for the first predetermined time period corresponds to physiological data for a first subset of recurring time periods; as well as After receiving the first set of physiological data for the first predetermined time period: displaying a data summary user interface via the display generation component; displaying in the data summary user interface a first representation of physiological data exceeding a first threshold value in the first set of physiological data for the first predetermined time period based on determining that the physiological data for the first subset of the recurring time period meets a first set of criteria; as well as Based on determining that the physiological data of the first subset of the recurring time periods do not satisfy the first set of criteria, the first representation of physiological data exceeding the first threshold value in the first set of physiological data for the first predetermined time period is abandoned for display in the data summary user interface.

2. The computer system of claim 1 , wherein a second subset of the first set of physiological data for the first predetermined time period that is different from the first subset of the first set of physiological data for the first predetermined time period corresponds to physiological data for a second subset of the recurring time periods, the one or more programs further comprising instructions for: After receiving the first set of physiological data for the first predetermined time period: Based on determining that the physiological data of the second subset of the recurring time periods meets the first set of criteria, a second representation of physiological data exceeding the first threshold value in the first set of physiological data for the first predetermined time period is displayed in the data summary user interface. 3 . The computer system of claim 1 , wherein the first subset of the recurring time periods corresponds to a first quadrant of each day of the first predetermined time period.

4. The computer system according to claim 1, wherein: The first representation of the physiological data includes an indication of the first subset of the recurring time periods during which the physiological data was obtained.

5. The computer system of claim 1, wherein the first set of criteria includes criteria that are satisfied when the physiological data exceeds the first threshold value. The computer system according to claim 1 , wherein the physiological data is data corresponding to blood sugar level.

7. The computer system of claim 1, wherein the first representation comprises a visual representation of elevated data received during the first subset of the recurring time periods.

8. The computer system of claim 1, wherein the one or more programs further comprise instructions for: After receiving the first set of physiological data for the first predetermined time period, a task selection user interface having a set of one or more selectable task user interface objects is displayed via the display generation component.

9. The computer system of claim 8, wherein the one or more programs further comprise instructions for: After receiving the first set of physiological data for the first predetermined time period and in accordance with determining that the physiological data for the first subset of the recurring time periods does not satisfy the first set of criteria: Displaying, on the task-selection user interface, a first selectable task user interface object corresponding to a first type of user activity to be performed during the first subset of the recurring time periods is foregone.

10. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component, the one or more programs comprising instructions for: receiving a first set of physiological data for a first predetermined time period, wherein a first subset of the first set of physiological data for the first predetermined time period corresponds to physiological data for a first subset of recurring time periods; as well as After receiving the first set of physiological data for the first predetermined time period: displaying a data summary user interface via the display generation component; displaying in the data summary user interface a first representation of physiological data in the first set of physiological data for the first predetermined time period that exceeds a first threshold value based on determining that the physiological data for the first subset of the recurring time period meets a first set of criteria; as well as Based on determining that the physiological data of the first subset of the recurring time periods do not satisfy the first set of criteria, the first representation of physiological data exceeding the first threshold value in the first set of physiological data for the first predetermined time period is abandoned for display in the data summary user interface.

11. The non-transitory computer-readable storage medium of claim 10, wherein a second subset of the first set of physiological data for the first predetermined time period that is different from the first subset of the first set of physiological data for the first predetermined time period corresponds to physiological data for a second subset of the recurring time periods, the one or more programs further comprising instructions for: After receiving the first set of physiological data for the first predetermined time period: Based on determining that the physiological data of the second subset of the recurring time periods meets the first set of criteria, a second representation of physiological data exceeding the first threshold value in the first set of physiological data for the first predetermined time period is displayed in the data summary user interface. 12 . The non-transitory computer readable storage medium of claim 10 , wherein the first subset of the recurring time periods corresponds to a first quadrant of each day of the first predetermined time period.

13. The non-transitory computer-readable storage medium of claim 10, wherein: The first representation of the physiological data includes an indication of the first subset of the recurring time periods during which the physiological data was obtained.

14. The non-transitory computer-readable storage medium of claim 10, wherein the first set of criteria includes criteria that are satisfied when the physiological data exceeds the first threshold value.

15. The non-transitory computer-readable storage medium of claim 10, wherein the physiological data is data corresponding to a blood glucose level.

16. The non-transitory computer-readable storage medium of claim 10, wherein the first representation comprises a visual representation of elevation data received during the first subset of the recurring time periods.

17. The non-transitory computer readable storage medium of claim 10, wherein the one or more programs further comprise instructions for: After receiving the first set of physiological data for the first predetermined time period, a task selection user interface having a set of one or more selectable task user interface objects is displayed via the display generation component.

18. The non-transitory computer readable storage medium of claim 17, wherein the one or more programs further comprise instructions for: After receiving the first set of physiological data for the first predetermined time period and in accordance with determining that the physiological data for the first subset of the recurring time periods does not satisfy the first set of criteria: Displaying, on the task-selection user interface, a first selectable task user interface object corresponding to a first type of user activity to be performed during the first subset of the recurring time periods is foregone.

19. A method comprising: At a computer system in communication with a display generating component: receiving a first set of physiological data for a first predetermined time period, wherein a first subset of the first set of physiological data for the first predetermined time period corresponds to physiological data for a first subset of recurring time periods; as well as After receiving the first set of physiological data for the first predetermined time period: displaying a data summary user interface via the display generation component; displaying in the data summary user interface a first representation of physiological data in the first set of physiological data for the first predetermined time period that exceeds a first threshold value based on determining that the physiological data for the first subset of the recurring time period meets a first set of criteria; as well as Based on determining that the physiological data of the first subset of the recurring time periods do not satisfy the first set of criteria, displaying the first representation of physiological data exceeding a first threshold value in the first set of physiological data for the first predetermined time period in the data summary user interface is abandoned.

20. The method of claim 19, wherein a second subset of the first set of physiological data for the first predetermined time period that is different from the first subset of the first set of physiological data for the first predetermined time period corresponds to physiological data for a second subset of the recurring time periods, the method further comprising: After receiving the first set of physiological data for the first predetermined time period: Based on determining that the physiological data of the second subset of the recurring time periods meets the first set of criteria, a second representation of physiological data exceeding the first threshold value in the first set of physiological data for the first predetermined time period is displayed in the data summary user interface.

21. The method of claim 19, wherein the first subset of the recurring time periods corresponds to a first quadrant of each day of the first predetermined time period.

22. The method according to claim 19, wherein: The first representation of the physiological data includes an indication of the first subset of the recurring time periods during which the physiological data was obtained.

23. The method of claim 19, wherein the first set of criteria includes criteria that are satisfied when the physiological data exceeds the first threshold value.

24. The method of claim 19, wherein the physiological data is data corresponding to blood glucose level.

25. The method of claim 19, wherein the first representation comprises a visual representation of elevation data received during the first subset of the recurring time periods.

26. The method of claim 19, further comprising: After receiving the first set of physiological data for the first predetermined time period, a task selection user interface having a set of one or more selectable task user interface objects is displayed via the display generation component.

27. The method according to claim 26, further comprising: After receiving the first set of physiological data for the first predetermined time period and in accordance with determining that the physiological data for the first subset of the recurring time periods does not satisfy the first set of criteria: Displaying, on the task-selection user interface, a first selectable task user interface object corresponding to a first type of user activity to be performed during the first subset of the recurring time periods is foregone.

Images