User interface for organizing user activity

Abstract

The present disclosure generally relates to organizing user activity. In some embodiments, based on the accessed data, the computer system displays a user interface in which representations of the data corresponding to the user activity are arranged in different regions based on effects of the user activity on the body parameters.

Description

Cross-reference to related applications

[0001] This application claims priority to U.S. Patent Application No. 18 / 912,506, filed October 10, 2024, entitled "USER INTERFACES FOR ORGANIZING USER ACTIVITIES," and U.S. Provisional Patent Application No. 63 / 543,923, filed October 12, 2023, also entitled "USER INTERFACES FOR ORGANIZING USER ACTIVITIES." The entire contents of each of these patent applications are incorporated herein by reference. Technical Field

[0002] This disclosure relates generally to computer user interfaces, and more specifically to techniques for organizing user activities. Background Technology

[0003] Computer systems may include applications for organizing user activities. Such systems may use user interfaces to receive user input, and these user interfaces may include one or more graphical elements suitable for use in organizing user activities. Summary of the Invention

[0004] However, some technologies used to organize user activities using electronic devices are often cumbersome and inefficient. For example, some existing technologies use complex and time-consuming user interfaces that may include multiple buttons or keystrokes. These existing technologies require more time than necessary, resulting in wasted user time and device energy. This latter consideration is particularly important in battery-powered devices.

[0005] Therefore, this technology provides electronic devices with faster and more efficient methods and interfaces for organizing user activities. Such methods and interfaces can optionally complement or replace other methods for organizing user activities. These methods and interfaces reduce the cognitive burden on users and result in more efficient human-machine interfaces. For battery-powered computing devices, such methods and interfaces save power and increase the time interval between battery charging sessions.

[0006] According to some implementation schemes, a method is described that is performed at a computer system communicating with a display generation component and one or more input devices. The method includes: displaying a task selection user interface via a display generation component, 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 cyclic time period, based on a determination that physiological data from a first subset of the cyclic time period meets a first set of criteria; and a second selectable task user interface object corresponding to a second type of user activity to be performed during the second subset of the cyclic time period, based on a determination that physiological data from a second subset of the cyclic time period, different from the first subset of the cyclic time period, meets the first set of criteria; receiving a first set of one or more inputs via one or more input devices 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 cyclic time period based on a determination that the first set of one or more inputs includes an 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 cyclic time period based on a determination that the first set of one or more inputs includes an input selecting the second selectable task user interface object.

[0007] 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 display generation components and one or more input devices. The one or more programs include instructions for: displaying a task selection user interface via the display generation component 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 cyclic time period, based on a determination that physiological data of a first subset of the cyclic time period meets a first set of criteria; and a second selectable task user interface object corresponding to a second type of user activity to be performed during the second subset of the cyclic time period, based on a determination that physiological data of a second subset of the cyclic time period, different from the first subset of the cyclic time period, meets the first set of criteria; receiving a first set of one or more inputs via one or more input devices when 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 cyclic time period based on a determination that the first set of one or more inputs includes an 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 cyclic time period based on a determination that the first set of one or more inputs includes an input selecting the second selectable task user interface object.

[0008] 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 generation component and one or more input devices. The one or more programs include instructions for: displaying a task selection user interface via the display generation component 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 cyclic time period, based on a determination that physiological data of a first subset of the cyclic time period meets a first set of criteria; and a second selectable task user interface object corresponding to a second type of user activity to be performed during the second subset of the cyclic time period, based on a determination that physiological data of a second subset of the cyclic time period, different from the first subset of the cyclic time period, meets the first set of criteria; receiving a first set of one or more inputs via one or more input devices when 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 cyclic time period based on a determination that the first set of one or more inputs includes an 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 cyclic time period based on a determination that the first set of one or more inputs includes an input selecting the second selectable task user interface object.

[0009] 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 a task selection user interface via the display generation component 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 cyclic time period, based on a determination that physiological data of a first subset of the cyclic time period meets a first set of criteria; and a second selectable task user interface object corresponding to a second type of user activity to be performed during the second subset of the cyclic time period, based on a determination that physiological data of a second subset of the cyclic time period, different from the first subset of the cyclic time period, meets the first set of criteria; receiving a first set of one or more inputs via one or more input devices when 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 cyclic time period based on a determination that the first set of one or more inputs includes an 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 cyclic time period based on a determination that the first set of one or more inputs includes an input selecting the second selectable task user interface object.

[0010] According to some implementation schemes, a computer system including a display generation component and one or more input devices is described. The computer system further includes: components for displaying a task selection user interface having a set of one or more selectable task user interface objects via the display generation component, 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 cyclic time period, based on a determination that physiological data of a first subset of the cyclic time period meets a first set of criteria; and a second selectable task user interface object corresponding to a second type of user activity to be performed during the second subset of the cyclic time period, based on a determination that physiological data of a second subset of the cyclic time period, different from the first subset of the cyclic time period, meets the first set of criteria; components for receiving a first set of one or more inputs via one or more input devices when displaying the task selection user interface; and components 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 cyclic time period based on a determination that the first set of one or more inputs includes an 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 cyclic time period based on a determination that the first set of one or more inputs includes an input selecting the second selectable task user interface object.

[0011] According to some implementation schemes, a method is described that is performed at a computer system communicating with a display generation component and one or more input devices. 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, the set of one or more selectable target creation user interface objects including: a first selectable target creation user interface object corresponding to a first type of user activity to be performed during the first subset of the cyclic time period based on a determination that a first type of user activity performed within a first subset of the cyclic time period meets a first set of criteria; and a second selectable target creation user interface object corresponding to a second type of user activity to be performed during the second subset of the cyclic time period based on a determination that a second type of user activity performed within a second subset of the cyclic time period different from the first subset of the cyclic time period meets the first set of criteria; receiving a first set of one or more inputs when 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 for a predetermined duration during the first subset of the cyclic time period based on a determination that the first set of one or more inputs includes an input selecting the first selectable target user interface object; and enabling logging of the second type of user activity for the predetermined duration during the second subset of the cyclic time period based on a determination that the first set of one or more inputs includes an input selecting the second selectable target creation user interface object.

[0012] 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 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 target creation user interface having a set of one or more selectable target creation user interface objects, the set of one or more selectable target creation user interface objects including: a first selectable target creation user interface object corresponding to a first type of user activity to be executed during the first subset of the cyclic time period, based on a determination that a first type of user activity executed within a first subset of the cyclic time period meets a first set of criteria; and a second type of user activity executed within a second subset of the cyclic time period, different from the first subset of the cyclic time period, corresponding to a first selectable target creation user interface object to be executed during the second subset of the cyclic time period. The system executes a second selectable target creation user interface object for the second type of user activity; when displaying the target creation user interface, it receives a first set of one or more inputs; and in response to receiving the first set of one or more inputs: based on a determination that the first set of one or more inputs includes an input to select the first selectable target user interface object, it enables logging of the first type of user activity for a predetermined duration during the first subset of the cyclic time period; and based on a determination that the first set of one or more inputs includes an input to select the second selectable target creation user interface object, it enables logging of the second type of user activity for the predetermined duration during the second subset of the cyclic time period.

[0013] According to some embodiments, a transient computer-readable storage medium is described, the transient 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 and one or more input devices. The one or more programs include instructions for: displaying via the display generation component a target creation user interface having a set of one or more selectable target creation user interface objects, the set of one or more selectable target creation user interface objects including: a first selectable target creation user interface object corresponding to a first type of user activity to be executed during the first subset of the cyclic time period, based on a determination that a first type of user activity executed within a first subset of the cyclic time period meets a first set of criteria; and a second type of user activity executed within a second subset of the cyclic time period, different from the first subset of the cyclic time period, corresponding to a first selectable target creation user interface object to be executed during the second subset of the cyclic time period. The system executes a second selectable target creation user interface object for the second type of user activity; when displaying the target creation user interface, it receives a first set of one or more inputs; and in response to receiving the first set of one or more inputs: based on a determination that the first set of one or more inputs includes an input to select the first selectable target user interface object, it enables logging of the first type of user activity for a predetermined duration during the first subset of the cyclic time period; and based on a determination that the first set of one or more inputs includes an input to select the second selectable target creation user interface object, it enables logging of the second type of user activity for the predetermined duration during the second subset of the cyclic time period.

[0014] 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 target creation user interface having a set of one or more selectable target creation user interface objects, the set of one or more selectable target creation user interface objects including: a first selectable target creation user interface object corresponding to a first type of user activity to be executed during the first subset of the cyclic time period, based on a determination that a first type of user activity executed within a first subset of the cyclic time period meets a first set of criteria; and a second type of user activity executed within a second subset of the cyclic time period, different from the first subset of the cyclic time period, corresponding to a first selectable target creation user interface object to be executed during the second subset of the cyclic time period. The system executes a second selectable target creation user interface object for the second type of user activity; when displaying the target creation user interface, it receives a first set of one or more inputs; and in response to receiving the first set of one or more inputs: based on a determination that the first set of one or more inputs includes an input to select the first selectable target user interface object, it enables logging of the first type of user activity for a predetermined duration during the first subset of the cyclic time period; and based on a determination that the first set of one or more inputs includes an input to select the second selectable target creation user interface object, it enables logging of the second type of user activity for the predetermined duration during the second subset of the cyclic time period.

[0015] According to some embodiments, a computer system including a display generation component and one or more input devices is described. The computer system further includes: a component for displaying via the display generation component a target creation user interface having a set of one or more selectable target creation user interface objects, the set of one or more selectable target creation user interface objects including: a first selectable target creation user interface object corresponding to a first type of user activity to be executed during the first subset of the cyclic time period, based on a determination that a first type of user activity executed within a first subset of the cyclic time period meets a first set of criteria; and a second type of user activity corresponding to a second type of user activity to be executed during the second subset of the cyclic time period, based on a determination that a second type of user activity executed within a second subset of the cyclic time period, different from the first subset of the cyclic time period, meets the first set of criteria. The user activity includes a second selectable target creation user interface object; a component for receiving a first set of one or more inputs when displaying the target creation user interface; and a component 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 for a predetermined duration during a first subset of the cyclic time period based on a determination that the first set of one or more inputs includes an input to select the first selectable target user interface object; and enabling logging of the second type of user activity for the predetermined duration during a second subset of the cyclic time period based on a determination that the first set of one or more inputs includes an input to select the second selectable target creation user interface object.

[0016] According to some embodiments, a method is described that is executed at a computer system communicating with a display generation component and one or more input devices. The method includes: accessing data corresponding to a first set of occurring user activities, the data including: first data including an indication of the influence of a first subset of user activities on a first physiological parameter; and second data including an indication of the influence of a second subset of user activities on the first physiological parameter; receiving a request to display a first user interface via one or more input devices; and, in response to receiving the request to display the first user interface, displaying the first user interface via the display generation component, including: displaying a first graphical representation of the first data corresponding to the first subset of user activities, wherein: based on the determination of a first set of influence level criteria satisfying the indication of the influence of the first subset of user activities on the first physiological parameter, in a first area of ​​the first user interface... The system displays a first graphical representation; and displays a second graphical representation in a second region of the first user interface, different from the first region, based on the determination that the indication of the influence of a first subset of user activities on a first physiological parameter meets a second set of influence level criteria different from the first set of influence criteria; and displays a second graphical representation corresponding to the second subset of user activities, wherein: the second graphical representation is displayed in the first region of the first user interface based on the determination that the indication of the influence of a second subset of user activities on a first physiological parameter meets a first set of influence level criteria; and the second graphical representation is displayed in the second region of the first user interface based on the determination that the indication of the influence of a second subset of user activities on a first physiological parameter meets a second set of influence level criteria.

[0017] 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 in communication with a display generation component and one or more input devices. The one or more programs include instructions for: accessing data corresponding to a first set of occurrences of user activity, the data including: first data including an indication of the influence of a first subset of user activity on a first physiological parameter; and second data including an indication of the influence of a second subset of user activity on the first physiological parameter; receiving a request to display a first user interface via one or more input devices; and, in response to receiving the request to display the first user interface, displaying the first user interface via the display generation component, including: displaying a first graphical representation of the first data corresponding to the first subset of user activity, wherein: based on the determination of a first set of influence level criteria satisfying the indication of the influence of the first subset of user activity on the first physiological parameter, the first user interface... A first graphical representation is displayed in a first area of ​​the interface; and a second graphical representation is displayed in a second area of ​​the first user interface, different from the first area, based on the determination that the indication of the influence of a first subset of user activities on a first physiological parameter meets a second set of influence level criteria different from the first set of influence criteria; and a second graphical representation corresponding to a second subset of user activities is displayed, wherein: a second graphical representation is displayed in the first area of ​​the first user interface based on the determination that the indication of the influence of a second subset of user activities on a first physiological parameter meets a first set of influence level criteria; and a second graphical representation is displayed in the second area of ​​the first user interface based on the determination that the indication of the influence of a second subset of user activities on a first physiological parameter meets a second set of influence level criteria.

[0018] According to some embodiments, a transient computer-readable storage medium is described, the transient 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 and one or more input devices. The one or more programs include instructions for: accessing data corresponding to a first set of occurrences of user activity, the data including: first data including an indication of the influence of a first subset of user activity on a first physiological parameter; and second data including an indication of the influence of a second subset of user activity on the first physiological parameter; receiving a request to display a first user interface via one or more input devices; and, in response to receiving the request to display the first user interface, displaying the first user interface via the display generation component, including: displaying a first graphical representation of the first data corresponding to the first subset of user activity, wherein: based on the determination of a first set of influence level criteria satisfying the indication of the influence of the first subset of user activity on the first physiological parameter, the first user interface... A first graphical representation is displayed in a first area of ​​the interface; and a second graphical representation is displayed in a second area of ​​the first user interface, different from the first area, based on the determination that the indication of the influence of a first subset of user activities on a first physiological parameter meets a second set of influence level criteria different from the first set of influence criteria; and a second graphical representation corresponding to a second subset of user activities is displayed, wherein: a second graphical representation is displayed in the first area of ​​the first user interface based on the determination that the indication of the influence of a second subset of user activities on a first physiological parameter meets a first set of influence level criteria; and a second graphical representation is displayed in the second area of ​​the first user interface based on the determination that the indication of the influence of a second subset of user activities on a first physiological parameter meets a second set of influence level criteria.

[0019] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: 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: accessing data corresponding to a first set of occurrences of user activity, the data including: first data including an indication of the influence of a first subset of user activity on a first physiological parameter; and second data including an indication of the influence of a second subset of user activity on the first physiological parameter; receiving a request to display a first user interface via one or more input devices; and, in response to receiving the request to display the first user interface, displaying the first user interface via the display generation component, including: displaying a first graphical representation of the first data corresponding to the first subset of user activity, wherein: based on the determination of a first set of influence level criteria satisfying the indication of the influence of the first subset of user activity on the first physiological parameter, the first user interface... A first graphical representation is displayed in a first area of ​​the interface; and a second graphical representation is displayed in a second area of ​​the first user interface, different from the first area, based on the determination that the indication of the influence of a first subset of user activities on a first physiological parameter meets a second set of influence level criteria different from the first set of influence criteria; and a second graphical representation corresponding to a second subset of user activities is displayed, wherein: a second graphical representation is displayed in the first area of ​​the first user interface based on the determination that the indication of the influence of a second subset of user activities on a first physiological parameter meets a first set of influence level criteria; and a second graphical representation is displayed in the second area of ​​the first user interface based on the determination that the indication of the influence of a second subset of user activities on a first physiological parameter meets a second set of influence level criteria.

[0020] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: components for accessing data corresponding to a first set of occurrences of user activity, the data including: first data including an indication of the influence of a first subset of user activity on a first physiological parameter; and second data including an indication of the influence of a second subset of user activity on the first physiological parameter; components for receiving a request to display a first user interface via one or more input devices; and components for displaying the first user interface via the display generation component in response to receiving the request to display the first user interface, including: components for displaying a first graphical representation of the first data corresponding to the first subset of user activity, wherein: based on the determination of a first set of influence level criteria satisfying the indication of the influence of the first subset of user activity on the first physiological parameter, in the first... A first graphical representation is displayed in a first area of ​​the user interface; and the first graphical representation is displayed in a second area of ​​the first user interface, different from the first area, based on the determination that the indication of the influence of a first subset of user activities on a first physiological parameter meets a second set of influence level criteria different from the first set of influence criteria; and a component for displaying a second graphical representation of second data corresponding to a second subset of user activities, wherein: the second graphical representation is displayed in the first area of ​​the first user interface based on the determination that the indication of the influence of a second subset of user activities on a first physiological parameter meets a first set of influence level criteria; and the second graphical representation is displayed in the second area of ​​the first user interface based on the determination that the indication of the influence of a second subset of user activities on a first physiological parameter meets a second set of influence level criteria.

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

[0022] Therefore, faster and more efficient methods and interfaces are provided for organizing user activities, thereby improving the effectiveness, efficiency, and user satisfaction of such devices. These methods and interfaces can complement or replace other methods used for organizing user activities. Attached Figure Description

[0023] To better understand the various described embodiments, reference should be made to the following detailed description in conjunction with the accompanying drawings, wherein the same reference numerals in all the drawings indicate corresponding parts.

[0024] Figure 1A This is a block diagram illustrating a portable multi-functional device with a touch-sensitive display according to some implementation schemes.

[0025] Figure 1B This is a block diagram illustrating exemplary components for event handling according to some implementation schemes.

[0026] Figure 2 Examples of portable multi-functional devices with touchscreens according to some implementation schemes are shown.

[0027] Figure 3A This is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface according to some implementation schemes.

[0028] Figures 3B to 3G This example demonstrates how to perform an operation using an Application Programming Interface (API).

[0029] Figure 4A An exemplary user interface for a menu applied to a portable multi-functional device, according to some implementation schemes, is illustrated.

[0030] Figure 4B An exemplary user interface for a multifunctional device having a touch-sensitive surface separate from the display is illustrated according to some embodiments.

[0031] Figure 5A Examples of personal electronic devices according to some implementation schemes are shown.

[0032] Figure 5B This is a block diagram illustrating a personal electronic device according to some implementation schemes.

[0033] Figures 6A to 6AM Exemplary user interfaces for logging and / or organizing user activity, according to some implementation schemes, are illustrated.

[0034] Figure 7 This is a flowchart illustrating a method for logging user activity during a subset of a cyclic time period, according to some implementation schemes.

[0035] Figures 8A to 8B This is a flowchart illustrating a method for logging user activity during a subset of a cyclic time period, according to some implementation schemes.

[0036] Figure 9 This is a flowchart illustrating a method for organizing user activities according to some implementation schemes. Detailed Implementation

[0037] The following description illustrates exemplary methods, parameters, etc. However, it should be understood that such description is not intended to limit the scope of this disclosure, but is provided as a description of exemplary embodiments.

[0038] Electronic devices are needed that provide efficient methods and interfaces for organizing user activities. Furthermore, these devices should display logged user activities during a subset of a cyclical time period, along with other user data, so that users can determine the effectiveness of their actions. Such technologies reduce the cognitive burden on users logging user activities during a subset of a cyclical time period, thereby improving productivity. Additionally, these technologies reduce processor and battery power wasted otherwise on redundant user input.

[0039] under Figures 1A to 1B , Figure 2 , Figures 3A to 3G , Figures 4A to 4B and Figures 5A to 5B A description of an exemplary device for performing management event notifications is provided. Figures 6A to 6AM An exemplary user interface is illustrated (e.g., during a subset of a cyclical time period) for logging and / or organizing user activity. Figure 7 This is a flowchart illustrating a method for logging user activity during a subset of a cyclic time period, according to some implementation schemes. Figures 8A to 8B This is a flowchart illustrating a method for logging user activity during a subset of a cyclic time period, according to some implementation schemes. Figure 9 This is a flowchart illustrating a method for organizing user activities according to some implementation schemes. Figures 6A to 6AM The user interface in the document is used to illustrate the processes described below, including Figure 7 , Figures 8A to 8B and Figure 9 The process in.

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

[0041] The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and / or” as used herein refers to and covers any and all possible combinations of one or more of the associated listed items. It will also be understood that the terms “comprising” and / or “including” as used in this specification specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0042] Depending on the context, the term "if" may optionally be interpreted as meaning "when," "in," or "in response to determination" or "in response to detection." Similarly, depending on the context, the phrases "if it is determined..." or "if [the stated condition or event] is detected" may optionally be interpreted as meaning "in response to determination..." or "in response to detection of [the stated condition or event]."

[0043] This document describes implementations of electronic devices, user interfaces for such devices, and associated processes for using such devices. In some implementations, the device is a portable communication device, such as a mobile phone, that also includes other functionalities such as PDA and / or music player functionality. Exemplary implementations of portable multi-functional devices include, but are not limited to, the iPhone from Apple Inc. of Cupertino, California. ® Devices, iPod Touch ® Devices and iPads ®Device. Alternatively, other portable electronic devices may be used, such as laptop computers or tablet computers with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads). In some embodiments, the electronic device is a computer system that communicates with a display generating component (e.g., via wireless or wired communication). The display generating component is configured to provide visual output, such as display via a CRT display, via an LED display, or via image projection. In some embodiments, the display generating component is integrated with the computer system. In some embodiments, the display generating component is separate from the computer system. As used herein, “display” content includes displaying content (e.g., video data rendered or decoded by display controller 156) by sending data (e.g., image data or video data) to an integrated or external display generating component via a wired or wireless connection to visually generate content.

[0044] 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 may optionally include one or more other physical user interface devices, such as a physical keyboard, mouse, and / or joystick.

[0045] The device typically supports a variety of applications, such as one or more of the following: drawing applications, presentation applications, word processing applications, website creation applications, disk editing applications, spreadsheet applications, game applications, telephone applications, video conferencing applications, email applications, instant messaging applications, fitness support applications, photo management applications, digital camera applications, digital video camera applications, web browsing applications, digital music player applications, and / or digital video player applications.

[0046] Various applications running on this device may 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 the corresponding information displayed on the device may optionally be adjusted and / or varied for different applications, and / or within the respective applications. In this way, the shared physical architecture of the device (such as the touch-sensitive surface) may optionally support a variety of applications using a user interface that is intuitive and clear to the user.

[0047] Now let’s turn our attention to implementation schemes for portable devices with touch-sensitive displays. Figure 1AThis is a block diagram illustrating a portable multi-functional device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display 112 is sometimes referred to as a “touchscreen” for convenience, and is sometimes referred to as or called a “touch-sensitive display system.” 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 interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact strength sensors 165 for detecting the intensity of contact on device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of device 100). Device 100 may optionally include one or more haptic output generators 167 for generating haptic outputs on device 100 (e.g., generating haptic outputs on a haptic surface such as the haptic display system 112 of device 100 or the touchpad 355 of device 300). These components may optionally communicate via one or more communication buses or signal lines 103.

[0048] As used in this specification and claims, the term "intensity" of contact on a tactile surface refers to the force or pressure (force per unit area) of a contact (e.g., finger contact) on a tactile surface, or to a substitute (alternative) for the force or pressure of a contact on a tactile surface. The intensity of contact has a range of values ​​that includes at least four different values ​​and more typically hundreds of different values ​​(e.g., at least 256). The intensity of contact may optionally be 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 tactile surface may optionally be used to measure the force at different points on the tactile surface. In some embodiments, force measurements from multiple force sensors are combined (e.g., weighted average) to determine the estimated contact force. Similarly, the pressure-sensitive tip of a stylus may optionally be used to determine the pressure of the stylus on the tactile surface. Alternatively, the size and / or change of the contact area detected on the touch-sensitive surface, the capacitance and / or change of the touch-sensitive surface adjacent to the contact, and / or the resistance and / or change of the touch-sensitive surface adjacent to the contact may be used as substitutes 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 an 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 an 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 user input allows users to access additional device functions that would otherwise be inaccessible to the user on a smaller device with limited physical space, which is used (e.g., on a touch-sensitive display) to display an indication and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls, such as knobs or buttons).

[0049] As used in this specification and claims, the term "tactile output" refers to a physical displacement of the 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., the housing), or a displacement of a component relative to the center of mass of the device, detected by the user using the user's tactile sense. For example, when the device or a component of the device comes into contact with a 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 the physical characteristics of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or touchpad) may optionally be interpreted by the user as a "press-click" or "release-click" on a physically actuated button. In some cases, the user will feel a tactile sensation, such as a "press-click" or "release-click," even when a physically actuated button associated with the touch-sensitive surface, which has been physically pressed (e.g., displaced) by the user's movement, does not move. As another example, even when the smoothness of the tactile surface remains unchanged, the movement of the tactile surface can optionally be interpreted or sensed by the user as the "roughness" of the tactile surface. While such interpretations of touch by users will be limited by the individualized sensory perceptions of the user, many sensory perceptions of touch are common to most users. Therefore, when a tactile output is described as corresponding to a specific sensory perception of the user (e.g., "release click", "press click", "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or its components that will generate the sensory perception described by a typical (or common) user.

[0050] It should be understood that device 100 is merely an example of a portable multifunctional device, and device 100 may optionally have more or fewer components than those shown, may optionally combine two or more components, or may optionally have different configurations or arrangements of these components. Figure 1A The various components shown are implemented in hardware, software, or a combination of both, including one or more signal processing and / or application-specific integrated circuits.

[0051] Memory 102 may optionally include high-speed random access memory, and may also optionally include 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 may optionally control access to memory 102 by other components of device 100.

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

[0053] RF (Radio Frequency) circuit 108 receives and transmits RF signals, also known as electromagnetic signals. RF circuit 108 converts electrical signals into electromagnetic signals / 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 circuitry 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, subscriber identity module (SIM) cards, memory, etc. RF circuit 108 optionally communicates wirelessly with networks (such as the Internet (also known as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs))) and other devices. RF circuit 108 optionally includes well-known circuitry for detecting near-field communication (NFC) fields, such as via short-range communication radio components. Wireless communication may optionally use any of a variety of communication standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High-Speed ​​Downlink Packet Access (HSDPA), High-Speed ​​Uplink Packet Access (HSUPA), Evolution, Pure Data (EV-DO), HSPA, HSPA+, Dual-Unit 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), and Wi-Fi (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (e.g., Internet Messaging Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence with Extended Utility (SIMPLE), Instant Messaging and Presence Service (IMPS)) and / or Short Message Service (SMS), or any other suitable communication protocol that has not been developed as of the date of this document submission.

[0054] Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between the user and device 100. Audio circuitry 110 receives audio data from peripheral interface 118, converts the audio data into electrical signals, and sends the electrical signals to speaker 111. Speaker 111 converts the electrical signals into sound waves that are audible to humans. Audio circuitry 110 also receives electrical signals converted from sound waves by microphone 113. Audio circuitry 110 converts the electrical signals into audio data and sends the audio data to peripheral interface 118 for processing. Audio data may optionally be retrieved by peripheral interface 118 from and / or sent to memory 102 and / or RF circuitry 108. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., ...). Figure 2 (212 in the text). The headset jack provides an interface between the audio circuitry 110 and a removable audio input / output peripheral device, such as an output-only headset or a headset with both outputs (e.g., a single-ear or dual-ear headset) and inputs (e.g., a microphone).

[0055] I / O subsystem 106 couples input / output peripherals (such as touchscreen 112 and other input control devices 116) on device 100 to peripheral interface 118. I / O subsystem 106 optionally includes display controller 156, optical sensor controller 158, depth camera controller 169, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive electrical signals from / transmit electrical signals to the other input control device 116. Other input control devices 116 optionally include physical buttons (e.g., push-buttons, rocker buttons, etc.), dial pads, slide switches, joysticks, click dials, etc. In some embodiments, input controller 160 may optionally be coupled to (or not coupled to) any of the following: keyboard, infrared port, USB port, and pointing device such as mouse. One or more buttons (e.g., ... Figure 2 Optionally, 208 may include increase / decrease buttons for volume control of speaker 111 and / or microphone 113. These one or more buttons may optionally include a push-button (e.g., Figure 2(Ref. 206 in the original text). 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 user 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.

[0056] A rapid press of the push button may optionally disengage the touchscreen 112 from its lock or optionally initiate a process of unlocking the device using gestures on the touchscreen, as described in U.S. Patent Application 11 / 322,549 (i.e., U.S. Patent No. 7,657,849), filed December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image," the entire contents of which are incorporated herein by reference. A long press of the push button (e.g., 206) may optionally power on or off the device 100. The function of one or more of these buttons may optionally be user-customizable. The touchscreen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

[0057] The touch-sensitive display 112 provides input and output interfaces between the device and the user. The display controller 156 receives electrical signals from and / or transmits electrical signals to the touchscreen 112. The touchscreen 112 displays visual output to the user. Visual output may optionally include graphics, text, icons, video, and any combination thereof (collectively, "graphics"). In some embodiments, some or all of the visual output may optionally correspond to user interface objects.

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

[0059] Touchscreen 112 may optionally employ LCD (Liquid Crystal Display) technology, LPD (Light Emitting Polymer Display) technology, or LED (Light Emitting Diode) technology, but other display technologies may be used in other embodiments. Touchscreen 112 and display controller 156 may optionally use any of a variety of touch sensing technologies now known or to be developed hereafter, along with other proximity sensor arrays or other elements for determining one or more points of contact with touchscreen 112, to detect contact and any movement or interruption thereto. These various touch sensing technologies include, but are not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies. In an exemplary embodiment, projected mutual capacitance sensing technology, such as that used in the iPhone from Apple Inc. (Cupertino, California), is used. ® and iPod Touch ® The technology used.

[0060] In some embodiments of the touchscreen 112, the touch-sensitive display may optionally resemble a multi-touch-sensitive touchpad described in the following U.S. patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman et al.) and / or U.S. Patent Publication 2002 / 0015024A1, each of which is incorporated herein by reference in its entirety. However, the touchscreen 112 displays visual output from the device 100, while the touch-sensitive touchpad does not provide visual output.

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

[0062] The touchscreen 112 optionally has a video resolution exceeding 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. Users may optionally use any suitable object or accessory, such as a stylus, finger, etc., to interact with the touchscreen 112. In some embodiments, the user interface is designed to operate primarily through finger-based touch and gestures, which may be less precise than stylus-based input due to the larger contact area of ​​a finger on the touchscreen. In some embodiments, the device translates coarse finger-based input into precise pointer / cursor positioning or commands for performing the user-desired actions.

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

[0064] The device 100 also includes a power system 162 for supplying power to various components. The power system 162 may optionally include 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., light-emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power in the portable device.

[0065] The device 100 may optionally also include one or more optical sensors 164. Figure 1AAn optical sensor 164 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 an imaging module 143 (also referred to as a camera module), the optical sensor 164 optionally captures still images or video. In some embodiments, the optical sensor is located on the rear of the device 100, facing away from a touchscreen display 112 on the front of the device, allowing the touchscreen display to be used as a viewfinder for still image and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device, allowing images of the user to be optionally acquired for video conferencing while the user views other video conferencing participants on the touchscreen display. In some embodiments, the positioning of the optical sensor 164 can be changed by the user (e.g., by rotating the lenses and sensors within the device housing), allowing a single optical sensor 164 to be used in conjunction with the touchscreen display for both video conferencing and still image and / or video image acquisition.

[0066] The device 100 may optionally also include one or more depth camera sensors 175. Figure 1A A depth camera sensor is shown coupled to a depth camera controller 169 in I / O subsystem 106. Depth camera sensor 175 receives data from the environment to create a 3D model of an object (e.g., a face) within the scene from a viewpoint (e.g., the depth camera sensor). In some embodiments, in conjunction with imaging module 143 (also referred to as a camera module), depth camera sensor 175 may optionally be used to determine depth maps of different portions of an image captured by imaging module 143. In some embodiments, the depth camera sensor is located at the front of device 100, such that user images with depth information can be optionally acquired for video conferencing while a user views other video conferencing participants on a touchscreen display, and selfies with depth map data can be captured. In some embodiments, depth camera sensor 175 is located at the rear of the device, or both the rear and front of device 100. In some embodiments, the positioning of depth camera sensor 175 can be changed by the user (e.g., by rotating a lens and sensor within the device housing), such that depth camera sensor 175 is used in conjunction with a touchscreen display for both video conferencing and still image and / or video image acquisition.

[0067] The device 100 may optionally also include one or more contact strength sensors 165. Figure 1AA contact strength sensor is shown coupled to a strength sensor controller 159 in I / O subsystem 106. The contact strength sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electro-force sensors, piezoelectric sensors, optical force sensors, capacitive touch-sensitive surfaces, or other strength sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). The contact strength sensor 165 receives contact strength information (e.g., pressure information or a substitute for pressure information) from the environment. In some embodiments, at least one contact strength sensor is arranged juxtaposed with or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact strength sensor is located on the rear of device 100, opposite to the touchscreen display 112 located on the front of device 100.

[0068] The device 100 may optionally also include one or more proximity sensors 166. Figure 1A A proximity sensor 166 coupled to a peripheral device interface 118 is shown. Alternatively, the proximity sensor 166 may be coupled to an input controller 160 in an I / O subsystem 106. The proximity sensor 166 may be configured as described in the following U.S. patent applications: 11 / 241,839, entitled "Proximity Detector In Handheld Device"; 11 / 240,788, entitled "Proximity Detector In Handheld Device"; 11 / 620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output"; 11 / 586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and 11 / 638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals", the entire contents of which are incorporated herein by reference. In some implementations, when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call), the proximity sensor is turned off and the touchscreen 112 is disabled.

[0069] The device 100 may optionally also include one or more haptic output generators 167. Figure 1AA haptic output generator coupled to a haptic feedback controller 161 in I / O subsystem 106 is shown. The haptic output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components; and / or electromechanical devices for converting energy into linear motion such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other haptic output generating components (e.g., components for converting electrical signals into haptic outputs on the device). A contact intensity sensor 165 receives haptic feedback generation instructions from a haptic feedback module 133 and generates a haptic output on device 100 that can be felt by a user of device 100. In some embodiments, at least one haptic output generator is juxtaposed or adjacent to a haptic surface (e.g., haptic display system 112) and optionally generates the haptic output by moving the haptic surface vertically (e.g., in / outward from the surface of device 100) or laterally (e.g., backward and forward in the same plane as the surface of device 100). In some embodiments, at least one haptic output generator sensor is located on the rear of the device 100, opposite to the touch screen display 112 located on the front of the device 100.

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

[0071] 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. Furthermore, in some embodiments, memory 102 ( Figure 1A ) or 370 ( Figure 3A Storage device / global internal state 157, such as Figure 1A and Figure 3A As shown in the figure. 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, indicating what applications, views or other information occupy various areas of the touch screen display 112; sensor state, including information obtained from various sensors and input control devices 116 of the device; and position information relating to the device's position and / or orientation.

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

[0073] The communication module 128 facilitates communication with other devices via one or more external ports 124 and includes various software components for processing data received by the RF circuitry 108 and / or the external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) are adapted to be directly coupled to other devices or indirectly coupled via a network (e.g., the Internet, Wireless LAN, etc.). In some embodiments, the external port is for use with an iPod. ® (Trademark of Apple Inc.) The same or similar and / or compatible multi-pin (e.g., 30-pin) connectors used in Apple Inc. devices.

[0074] The contact / motion module 130 optionally detects contact with the touchscreen 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). The contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether a contact has occurred (e.g., detecting a finger press event), determining the contact intensity (e.g., the force or pressure of the contact, or an alternative to force or pressure), determining whether there is movement of the contact and tracking 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 a contact break). 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 which is represented by a series of contact data. These operations can optionally be applied to single-point contact (e.g., single-finger contact) or multi-point simultaneous contact (e.g., "multi-touch" / multiple-finger contact). In some implementations, the contact / motion module 130 and the display controller 156 detect contact on the touchpad.

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

[0076] The touch / motion module 130 optionally detects gesture input performed by the user. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different movements, timings, and / or intensities of the detected contact). Therefore, gestures can be detected optionally by detecting specific contact patterns. For example, detecting a finger tap gesture includes: detecting a finger press event, and then detecting a finger lift-off (lift-away) event at the same (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 a touch-sensitive surface includes: detecting a finger press event, then detecting one or more finger drag events, and subsequently detecting a finger lift-off (lift-away) event.

[0077] The graphics module 132 includes various known software components for rendering and displaying graphics on the touchscreen 112 or other displays, including components for altering the visual impact of the displayed graphics (e.g., brightness, transparency, saturation, contrast, or other visual properties). 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.

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

[0079] The haptic feedback module 133 includes various software components for generating instructions which are used by the haptic output generator 167 to generate haptic output at one or more locations on the device 100 in response to user interaction with the device 100.

[0080] Optionally, the text input module 134, a component of the graphics module 132, provides a soft keyboard for entering text in various applications, such as the contact module 137, email client module 140, IM module 141, browser module 147, and any other application that requires text input.

[0081] GPS module 135 determines the location of the device and provides that information for use in various applications (e.g., to telephone module 138 for use in location-based dialing; to camera module 143 as image / video metadata; and to applications that provide location-based services, such as weather widgets, local yellow pages widgets, and map / navigation widgets).

[0082] Application 136 may optionally include the following modules (or instruction sets) or subsets or supersets thereof: • Contacts module 137 (sometimes called address book or contact list); • Telephone module 138; • Video conferencing module 139; • Email client module 140; • Instant Messaging (IM) module 141; • Fitness support module 142; • Camera module 143 for still images and / or video images; • Image management module 144; • Video player module; • Music player module; • Browser module 147; • Calendar module 148; • Widget module 149, which may optionally include one or more of the following: weather widget 149-1, stock market widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5 and other widgets acquired by the user, and user-created widget 149-6; • Widget creator module 150 for creating user-created widgets 149-6; • Search module 151; • Video and music player module 152, which combines a video player module and a music player module; • Memo module 153; • Map module 154; and / or • Online video module 155.

[0083] Examples of other applications 136 that may be 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, speech recognition, and speech duplication.

[0084] In conjunction with the touchscreen 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., in application internal state 192 of the contact module 137 stored in memory 102 or memory 370), including: adding one or more names to the address book; deleting names from the address book; associating 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 the telephone module 138, video conferencing module 139, email client module 140, or IM module 141; and so on.

[0085] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, telephone module 138 is optionally used to input character sequences corresponding to telephone numbers, access one or more telephone numbers in contact module 137, modify input telephone numbers, dial corresponding telephone numbers, initiate conversations, and disconnect or hang up when a conversation is completed. As noted above, wireless communication may optionally use any of a variety of communication standards, protocols, and technologies.

[0086] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contact module 137, and telephone module 138, video conferencing module 139 includes executable instructions to initiate, conduct, and terminate video conferences between the user and one or more other participants based on user instructions.

[0087] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / 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 commands. Combined with image management module 144, email client module 140 makes it very easy to create and send emails containing still images or video images captured by camera module 143.

[0088] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for: entering a character sequence corresponding to an instant message, modifying previously entered characters, sending a corresponding instant message (e.g., using Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocols for telephone-based instant messaging or using XMPP, SIMPLE, or IMPS for internet-based instant messaging), receiving an instant message, and viewing received instant messages. In some embodiments, the sent and / or received instant messages may optionally include graphics, photographs, audio files, video files, and / or other attachments supported in MMS and / or Enhanced Messaging Services (EMS). As used herein, "instant message" means both telephone-based messages (e.g., messages delivered using SMS or MMS) and internet-based messages (e.g., messages delivered using XMPP, SIMPLE, or IMPS).

[0089] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, fitness support module 142 includes executable instructions for: creating fitness activities (e.g., with time, distance, and / or calorie burning goals); communicating with fitness sensors (exercise equipment); receiving fitness sensor data; calibrating sensors used to monitor fitness; selecting and playing music for fitness activities; and displaying, storing, and transmitting fitness data.

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

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

[0092] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions for browsing the Internet according to user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as links to attachments and other files on web pages.

[0093] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and associated data (e.g., calendar entries, to-dos, etc.) according to user instructions.

[0094] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, widget module 149 may be a micro-application (e.g., weather widget 149-1, stock market widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or a user-created micro-application (e.g., user-created widget 149-6). In some embodiments, the widget includes HTML (Hypertext Markup Language) files, CSS (Cascading Style Sheets) files, and JavaScript files. In some embodiments, the widget includes XML (Extensible Markup Language) files and JavaScript files (e.g., Yahoo! widgets).

[0095] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, widget creator module 150 can optionally be used by the user to create widgets (e.g., turning a user-specified section of a webpage into a widget).

[0096] In conjunction with the touchscreen 112, display controller 156, touch / 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) according to user instructions.

[0097] Incorporating touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions allowing users to download and play back recorded music and other sound files stored in one or more file formats such as MP3 or AAC files, as well as executable instructions for displaying, presenting, or otherwise playing back video (e.g., on touchscreen 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 (a trademark of Apple Inc.).

[0098] Combining the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the memo module 153 includes executable instructions for creating and managing memos, to-do items, etc., according to user instructions.

[0099] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 may optionally be used to receive, display, modify, and store maps and map-related data (e.g., driving directions, data related to shops and other points of interest at or near a specific location, and other location-based data) according to user instructions.

[0100] Incorporating touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, the online video module 155 includes instructions for allowing users to access, browse, receive (e.g., via streaming and / or downloading), play back (e.g., on the touchscreen or on an external display connected via external port 124), send emails with links to specific online videos, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, an instant messaging module 141 is used instead of the email client module 140 to send links to specific online videos. Additional descriptions of the online video application can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed 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 December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are incorporated herein by reference in their entirety.

[0101] Each of the modules and applications described above corresponds to an executable set of instructions for performing one or more functions described above and the methods described in this patent application (e.g., computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) need not be implemented as separate software programs, processes, or modules; therefore, various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. For example, a video player module may optionally be combined with a music player module into a single module (e.g., Figure 1A (e.g., video and music player module 152). In some embodiments, memory 102 may optionally store a subset of the aforementioned modules and data structures. Additionally, memory 102 may optionally store additional modules and data structures not described above.

[0102] In some implementations, device 100 is a device on which the operation of a predefined set of functions is performed solely via a touchscreen and / or touchpad. By using a touchscreen and / or touchpad as the primary input control device for operating device 100, the number of physical input control devices (such as push-buttons and dial pads) on device 100 can be optionally reduced.

[0103] A predefined set of functions, uniquely performed via a touchscreen and / or touchpad, may optionally include navigation between user interfaces. In some implementations, the touchpad, when touched by a user, navigates device 100 from any user interface displayed on device 100 to the main menu, main desktop menu, or root menu. In such implementations, a "menu button" is implemented using the touchpad. In some other implementations, the menu button is a physical push-button or other physical input control device, rather than a touchpad.

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

[0105] Event classifier 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which the event information should be delivered. Event classifier 170 includes event monitor 171 and event dispatcher 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 running. 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 should be delivered.

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

[0107] Event monitor 171 receives event information from peripheral device interface 118. The event information includes information about sub-events, such as user touches on touch-sensitive display 112 as part of a multi-touch gesture. Peripheral device 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 (via audio circuitry 110). The information received by peripheral device interface 118 from I / O subsystem 106 includes information from touch-sensitive display 112 or touch-sensitive surfaces.

[0108] In some implementations, the event monitor 171 sends requests to the peripheral device interface 118 at predetermined intervals. In response, the peripheral device interface 118 sends event information. In other implementations, the peripheral device interface 118 sends event information only when a significant event occurs (e.g., receiving input above a predetermined noise threshold and / or receiving input for a predetermined duration).

[0109] In some implementations, the event classifier 170 also includes a hit view determination module 172 and / or an activity event recognizer determination module 173.

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

[0111] Another aspect of the user interface associated with an application is a set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the corresponding application) in which a touch is detected optionally corresponds to a procedural level within the application's procedural or view hierarchy. For example, the lowest-level view in which a touch is detected may optionally be called the hit view, and the set of events identified as correct input is optionally determined, at least in part, based on the hit view of the initial touch that initiates the touch-based gesture.

[0112] The hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchical structure, the hit view determination module 172 identifies the hit view as the lowest-level view in the hierarchical structure from which 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 forming an event or potential event) occurs. Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source to which it was identified as the hit view.

[0113] The activity event recognizer determination module 173 determines which views(s) within the view hierarchy should receive a specific sub-event sequence. In some embodiments, the activity event recognizer determination module 173 determines that only the hit view should receive the specific sub-event sequence. In other embodiments, the activity event recognizer determination module 173 determines that all views including the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive the specific sub-event sequence. In other embodiments, even if the touch sub-event is entirely confined to the area associated with a particular view, higher views in the hierarchy will still remain actively participating views.

[0114] Event assigner module 174 assigns event information to event identifiers (e.g., event identifier 180). In embodiments that include active event identifier determination module 173, event assigner module 174 delivers event information to the event identifier determined by active event identifier determination module 173. In some embodiments, event assigner module 174 stores event information in an event queue, which is retrieved by the corresponding event receiver 182.

[0115] In some implementations, operating system 126 includes event classifier 170. Alternatively, application 136-1 includes event classifier 170. In yet another implementation, event classifier 170 is a separate module or part of another module (such as contact / motion module 130) stored in memory 102.

[0116] In some implementations, application 136-1 includes a plurality of 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 application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a corresponding application view 191 includes a plurality of event recognizers 180. In other implementations, one or more of the event recognizers 180 are part of a separate module, such as a user interface toolkit or a higher-level object from which application 136-1 inherits methods and other properties. In some implementations, a corresponding event handler 190 includes one or more of the following: a data updater 176, an object updater 177, a GUI updater 178, and / or event data 179 received from an event classifier 170. Event handlers 190 may optionally utilize or invoke the data updater 176, the object updater 177, or the GUI updater 178 to update the application's internal state 192. Alternatively, one or more application views in application view 191 include one or more corresponding event handlers 190. Additionally, 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.

[0117] 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 at least one subset of metadata 183 and event delivery instructions 188 (which may optionally include sub-event delivery instructions).

[0118] Event receiver 182 receives event information from event classifier 170. The 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 touch movement, the event information may optionally also include the speed and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another (e.g., from a portrait orientation to a lateral orientation, or vice versa), and the event information includes corresponding information about the device's current orientation (also referred to as device orientation).

[0119] Event comparator 184 compares event information with predefined event or sub-event definitions and determines the event or sub-event based on the comparison, or determines or updates the state of the event or sub-event. In some embodiments, event comparator 184 includes event definition 186. Event definition 186 contains definitions of events (e.g., predefined sequences 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, event 1 (187-1) is defined as a double-click on a displayed object. For example, a double-click includes a first touch (touch start) of a predetermined duration on the displayed object, a first lift-off of a predetermined duration (touch end), a second touch (touch start) of a predetermined duration on the displayed object, and a second lift-off of a predetermined duration (touch end). In another example, event 2 (187-2) is defined as a drag on a displayed object. For example, dragging includes a touch (or contact) of a predetermined duration on the displayed object, movement of the touch on the touch-sensitive display 112, and lifting the touch (end of touch). In some embodiments, the event also includes information for one or more associated event handlers 190.

[0120] In some implementations, event definition 187 includes definitions of events for corresponding user interface objects. In some implementations, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, in an application view 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 the event handler associated with the sub-event and the object that triggered the hit test.

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

[0122] When the corresponding event recognizer 180 determines that the sub-event sequence 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 based on touch gestures are ignored. In this case, other event recognizers (if any) that remain active in the hit view continue to track and process the ongoing sub-events based on touch gestures.

[0123] In some embodiments, the corresponding event recognizer 180 includes metadata 183 having configurable attributes, flags, and / or lists instructing how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, the metadata 183 includes configurable attributes, flags, and / or lists instructing how or how event recognizers can interact with each other. In some embodiments, the metadata 183 includes configurable attributes, flags, and / or lists instructing whether sub-events are delivered to different levels in a view or programmatic hierarchy.

[0124] In some implementations, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates the event handler 190 associated with the event. In some implementations, 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 delivering (and deferred delivering) the sub-events to the corresponding hit view. In some implementations, the event recognizer 180 throws a flag associated with the identified event, and the event handler 190 associated with the flag acquires the flag and performs a predefined process.

[0125] In some implementations, event delivery instruction 188 includes 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 the sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or the actively participating view receives the event information and performs a predetermined process.

[0126] In some implementations, 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 implementations, 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 positioning of user interface objects. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and transmits that display information to graphics module 132 for display on a touch-sensitive display.

[0127] In some implementations, event handler 190 includes, or has access to, a data updater 176, an object updater 177, and a GUI updater 178. In some implementations, 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 implementations, they are included in two or more software modules.

[0128] It should be understood that the above discussion regarding event handling for user touch 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 touchscreen. For example, mouse movement and mouse button presses optionally in conjunction with single or multiple keyboard presses or holds; touch movements on the touchpad, such as taps, drags, scrolls, etc.; stylus input; device movement; verbal commands; detected eye movements; biometric input; and / or any combination thereof may optionally be used as input corresponding to sub-events that define the event to be identified.

[0129] Figure 2A portable multifunction device 100 with a touchscreen 112 is illustrated according to some embodiments. The touchscreen 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 graphics by gesturing over the graphics, for example, 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, selection of one or more graphics occurs when the user breaks contact with one or more graphics. 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 scrolling (from right to left, from left to right, up and / or down) of a finger already in contact with the device 100. In some specific embodiments or in some cases, unintentional contact with a graphic does not select the graphic. For example, a swipe gesture over an application icon may optionally not select the corresponding application when the gesture corresponding to selection is a tap.

[0130] Device 100 may optionally also include one or more physical buttons, such as a "main desktop" or menu button 204. As previously described, menu button 204 may optionally be used to navigate to any application 136 of a set of applications optionally executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touchscreen 112.

[0131] In some embodiments, device 100 includes a touchscreen 112, a menu button 204, a push-button 206 for powering on / off and locking the device, one or more volume control buttons 208, a SIM card slot 210, a headphone jack 212, and a docking / charging external port 124. The push-button 206 is optionally used to: power on / off the device by pressing the button and holding it in the pressed state for a predefined time interval; lock the device by pressing the button and releasing it before the predefined time interval has elapsed; and / or unlock the device or initiate an unlocking process. In another embodiment, device 100 also accepts voice input via microphone 113 for activating or deactivating certain functions. Device 100 may also optionally include one or more contact strength sensors 165 for detecting the intensity of contact on the touchscreen 112, and / or one or more haptic output generators 167 for generating haptic output for the user of device 100.

[0132] Figure 3AThis is a block diagram of an exemplary multi-functional device with a display and a touch-sensitive surface according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a children's learning toy), gaming system, or control device (e.g., a home controller or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects system components and controls communication between system components. Device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touchscreen display. The I / O interface 330 may also optionally include a keyboard and / or mouse (or other pointing device) 350 and a touchpad 355, and a haptic output generator 357 for generating haptic output on device 300 (e.g., similar to the reference above). Figure 1A The described tactile output generator 167), sensor 359 (e.g., optical sensor, accelerometer, proximity sensor, touch sensor and / or contact intensity sensor (similar to the one described above)) Figure 1A The described contact strength sensor 165). Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices; and optionally includes non-volatile memory, such as one or more disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU 310. In some embodiments, memory 370 stores information related to portable multifunction device 100. Figure 1A The memory 370 stores programs, modules, and data structures similar to those in the memory 102 of the portable multifunction device 100, or subsets thereof. Additionally, the memory 370 may optionally store additional programs, modules, and data structures not present in the memory 102 of the portable multifunction device 100. For example, the memory 370 of the device 300 may optionally store a drawing module 380, a rendering module 382, ​​a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while the portable multifunction device 100 ( Figure 1A The memory 102 may optionally not store these modules.

[0133] Figure 3AEach of the elements described above may optionally be stored in one or more memory devices of the previously mentioned memory devices. Each of the modules described above corresponds to a set of instructions for performing the functions described above. The modules or programs (e.g., instruction sets) described above need not be implemented as separate software programs, processes, or modules, and therefore various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 may optionally store a subset of the modules and data structures described above. In addition, memory 370 may optionally store additional modules and data structures not described above.

[0134] Specific embodiments within the scope of this disclosure may be implemented, in whole or in part, using a tangible computer-readable storage medium (or a plurality of tangible computer-readable storage media of one or more types) that encodes one or more computer-readable instructions. It should be understood that computer-readable instructions may be organized in any format, including applications, widgets, processes, software, and / or components.

[0135] Specific embodiments within the scope of this disclosure include computer-readable storage media that encode instructions organized as an application (e.g., application 3160) that, when executed by one or more processing units, control the execution of an electronic device (e.g., device 3150). Figure 3B Methods Figure 3C The methods and / or one or more other processes and / or methods described herein.

[0136] It should be recognized that the application of 3160 ( Figure 3D The application 3160 (as shown in the diagram) can be any suitable type of application, including one or more of the following: browser applications, applications used as execution environments for plugins, widgets, or other applications, fitness applications, health applications, digital payment applications, media applications, social networking applications, messaging applications, and / or map applications. In some embodiments, application 3160 is an application pre-installed on device 3150 at the time of purchase (e.g., a first-party application). In some embodiments, application 3160 is an application provided to device 3150 via operating system update files (e.g., a first-party or second-party application). In some embodiments, application 3160 is an application provided via an app store. In some embodiments, the app store can be an app store pre-installed on device 3150 at the time of purchase (e.g., a first-party app store). In some embodiments, the app store is a third-party app store (e.g., an app store provided by another app store, downloaded via a network, and / or read from a storage device).

[0137] refer to Figure 3B and Figure 3DApplication 3160 acquires information (e.g., 3010). In some embodiments, at 3010, information is acquired from at least one hardware component of device 3150. In some embodiments, at 3010, information is acquired from at least one software module of device 3150. In some embodiments, at 3010, information is acquired from at least one hardware component external to device 3150 (e.g., peripheral devices, accessory devices, and / or servers). In some embodiments, the information acquired at 3010 includes location information, time information, notification information, user information, environmental information, electronic device status information, weather information, media information, historical information, event information, hardware information, and / or motion information. In some embodiments, in response to acquiring information at 3010 and / or after this step, application 3160 provides the information to the system (e.g., 3020).

[0138] In some implementations, the system (e.g., Figure 3E The 3110 shown is the operating system hosted on the device 3150. In some implementations, the system (e.g., Figure 3E 3110 shown in the figure is an external device (e.g., a server, peripheral device, accessory and / or personal computing device) that includes an operating system.

[0139] refer to Figure 3C and Figure 3G Application 3160 acquires information (e.g., 3030). In some embodiments, the information acquired at 3030 includes location information, time information, notification information, user information, environmental information, electronic device status information, weather information, media information, historical information, event information, hardware information, and / or motion information. In response to acquiring information at 3030 and / or after this step, application 3160 performs an operation on the information (e.g., 3040). In some embodiments, the operation performed at 3040 includes: providing notifications based on the information, sending messages based on the information, displaying information, controlling the user interface of a fitness application based on the information, controlling the user interface of a health application based on the information, controlling focus mode based on the information, setting reminders based on the information, adding calendar entries based on the information, and / or calling the API of system 3110 based on the information.

[0140] In some implementations, execution is performed in response to a trigger. Figure 3B Methods and / or Figure 3C The method involves one or more steps. In some implementations, triggering includes the detection of an event, a notification received from system 3110, user input, and / or a response to a call to an API provided by system 3110.

[0141] In some implementations, when the instructions of application 3160 are executed, control device 3150 executes them by calling an application programming interface (API) (e.g., API 3190) provided by system 3110. Figure 3B Methods and / or Figure 3C The method. In some implementations, application 3160 executes without calling API 3190. Figure 3B Methods and / or Figure 3C At least a part of the method.

[0142] In some implementation schemes, Figure 3B Methods and / or Figure 3C One or more steps of the method involve calling the API (e.g., API 3190) using one or more parameters defined by the API. In some implementations, one or more parameters include constants, keys, data structures, objects, object classes, variables, data types, pointers, arrays, lists, or pointers to functions or methods and / or references to data or other items to be passed via the API in another way.

[0143] refer to Figure 3D Example 3150 is shown. In some embodiments, device 3150 is a personal computing device, smartphone, smartwatch, fitness tracker, head-mounted display (HMD) device, media device, public utility, speaker, television, and / or tablet computer. Figure 3D As illustrated, device 3150 includes application 3160 and operating system (e.g., Figure 3E System 3110 is shown in the diagram. Application 3160 includes application implementation module 3170 and API call module 3180. System 3110 includes API 3190 and implementation module 3100. It should be understood that device 3150, application 3160 and / or system 3110 may include... Figure 3D and Figure 3E The examples illustrate more, fewer, and / or different components.

[0144] In some implementations, application implementation module 3170 includes a set of one or more instructions corresponding to one or more operations performed by application 3160. For example, when application 3160 is a messaging application, application implementation module 3170 may include operations for receiving and sending messages. In some implementations, application implementation module 3170 communicates with API calling module 3180 via API 3190 (in... Figure 3E (As shown in the figure) communicates with system 3110.

[0145] In some implementations, API 3190 is a software module (e.g., a set of computer-readable instructions) that provides an interface allowing different modules (e.g., API calling module 3180) to access and / or use one or more functions, methods, procedures, data structures, classes, and / or other services provided by implementation module 3100 of system 3110. For example, API calling module 3180 can access features of implementation module 3100 through one or more API calls or enablements (e.g., embodied by function or method calls) exposed by API 3190 (e.g., software and / or hardware modules capable of receiving, responding to, and / or transmitting API calls), and can pass data and / or control information via API calls or enablements using one or more parameters. In some implementations, API 3190 allows application 3160 to use services provided by a software development kit (SDK) library. In some implementations, application 3160 combines calls to functions or methods provided by the SDK library and API 3190, or uses data types or objects defined in the SDK library and provided by API 3190. In some implementations, API calling module 3180 makes API calls via API 3190 to access and use features of implementation module 3100 specified by API 3190. In such implementations, implementation module 3100 may return a value to API calling module 3180 via API 3190 in response to an API call. This value may report to application 3160 the capabilities or status of hardware components of device 3150, including those capabilities or statuses related to aspects such as input capabilities and status, output capabilities and status, processing capabilities, power status, storage capacity and status, and / or communication capabilities. In some implementations, API 3190 is implemented in part by firmware, microcode, or other low-level logic executed in part on the hardware components.

[0146] In some implementations, API 3190 allows the developer of API calling module 3180 (which may be a third-party developer) to utilize features provided by implementation module 3100. In such implementations, one or more API calling modules (e.g., including API calling module 3180) may exist that communicate with implementation module 3100. In some implementations, API 3190 allows multiple API calling modules written in different programming languages ​​to communicate with implementation module 3100 (e.g., API 3190 may include features for translating calls and returns between implementation module 3100 and API calling module 3180), and API 3190 is implemented in a specific programming language. In some implementations, API calling module 3180 calls APIs from different providers, such as a set of APIs from an OS provider, another set of APIs from a plugin provider, and / or another set of APIs from another provider (e.g., a software library provider) or the creator of another set of APIs.

[0147] Examples of API 3190 may include one or more of the following: pairing API (e.g., for establishing a secure connection, such as with an accessory), device detection API (e.g., for locating nearby devices, such as media devices and / or smartphones), payment API, UIKit API (e.g., for generating user interfaces), location detection API, locator API, map API, health sensor API, sensor API, messaging API, push notification API, streaming API, collaboration API, video conferencing API, app store API, advertising service API, web browser API (e.g., WebKit API), transportation API, networking API, WiFi API, Bluetooth API, NFC API, UWB API, fitness API, smart home API, contact transfer API, photo API, camera API, and / or image processing API. In some implementations, a sensor API is an API for accessing data associated with sensors of device 3150. For example, a sensor API may provide access to raw sensor data. Alternatively, a sensor API may provide data derived (and / or generated) from raw sensor data. In some implementations, sensor data includes temperature data, image data, video data, audio data, heart rate data, IMU (Inertial Measurement Unit) data, lidar data, location data, GPS data, and / or camera data. In some implementations, sensors include one or more of accelerometers, temperature sensors, infrared sensors, optical sensors, heart rate sensors, barometers, gyroscopes, proximity sensors, and / or biometric sensors.

[0148] In some embodiments, implementation module 3100 is a system (e.g., an operating system and / or server system) software module (e.g., a set of computer-readable instructions) configured to perform operations in response to receiving an API call via API 3190. In some embodiments, implementation module 3100 is configured to provide an API response (via API 3190) as a result of processing the API call. For example, implementation module 3100 and API call module 3180 can each be any of an operating system, library, device driver, API, application, or other module. It should be understood that implementation module 3100 and API call module 3180 can be the same or different types of modules. In some embodiments, implementation module 3100 is at least partially embodied in firmware, microcode, or hardware logic.

[0149] In some implementations, implementation module 3100 returns a value via API 3190 in response to an API call from API call module 3180. While API 3190 defines the syntax and results of the API call (e.g., how to enable the API call and what the API call does), API 3190 may not reveal how implementation module 3100 performs the functionality specified by the API call. Various API calls are passed via one or more application programming interfaces between API call module 3180 and implementation module 3100. Passing API calls may include issuing, initiating, enabling, calling, receiving, returning, and / or responding to function calls or messages. In other words, passing can describe the actions of API call module 3180 or implementation module 3100. In some implementations, function calls or other enablements of API 3190 transmit and / or receive one or more parameters via parameter lists or other structures.

[0150] In some implementations, implementation module 3100 provides more than one API, each API providing a different view or aspect of the functionality implemented by implementation module 3100. For example, one API of implementation module 3100 may provide a first set of functions and be exposed to third-party developers, while another API of implementation module 3100 may be hidden (e.g., not exposed) and provide a subset of the first set of functions, and also provide another set of functions, such as test or debug functions not in the first set of functions. In some implementations, implementation module 3100 calls one or more other components via lower-level APIs, thus acting as both an API calling module and an implementation module. It should be recognized that implementation module 3100 may include additional functions, methods, classes, data structures, and / or other features not specified through API 3190 and not available to API calling module 3180. It should also be recognized that API calling module 3180 may be on the same system as implementation module 3100, or may be remotely located and accessed via a network using API 3190. In some implementations, implementation module 3100, API 3190, and / or API calling module 3180 are stored in a machine-readable medium, which includes any means for storing information in a machine-readable (e.g., computer or other data processing system) form. For example, a machine-readable medium may include a magnetic disk, optical disk, random access memory, read-only memory, and / or flash memory devices.

[0151] An Application Programming Interface (API) is an interface between a first software process and a second software process, specifying the format for communication between the two processes. Limited APIs (e.g., private or partner APIs) are APIs accessible to a limited set of software processes (e.g., only software processes within the operating system or only software processes authorized to access the limited API). Public APIs are accessible to a broader set of software processes. Some APIs enable a software process to communicate or set the state of one or more input devices (e.g., one or more touch sensors, proximity sensors, vision sensors, motion / or orientation sensors, pressure sensors, intensity sensors, sound sensors, wireless proximity sensors, biometric sensors, buttons, switches, rotatable elements, and / or external controllers). Some APIs enable a software process to communicate and / or set the state of one or more output generation components (e.g., one or more audio output generation components, one or more display generation components, and / or one or more haptic output generation components). Some APIs enable specific capabilities (e.g., scrolling, handwriting, text input, image editing, and / or image creation) to be accessed, executed, and / or used by a software process (e.g., generating output for use by the software process based on input from the software process). Some APIs enable content from software processes to be inserted into templates and displayed in user interfaces with layouts and / or behaviors specified by the templates.

[0152] Many software platforms include a set of frameworks that provide core objects and behaviors that software developers need to build software applications that can be used on the platform. Software developers use these objects to display content on a screen, interact with that content, and manage interactions with the software platform. The basic behavior of a software application depends on this framework, and this framework provides software developers with numerous ways to customize the application's behavior to match the specific needs of the application. Many of these core objects and behaviors are accessed via APIs. APIs typically specify the format for communication between software processes, including specifying and grouping available variables, functions, and protocols. API calls (sometimes called API requests) are typically passed from a sending software process to a receiving software process as a way to achieve one or more of the following: the sending software process requests information from the receiving software process (e.g., for the sending software process to take an action); the sending software process provides information to the receiving software process (e.g., for the receiving software process to take an action); the sending software process requests an action from the receiving software process; or the sending software process provides information to the receiving software process about the action taken by the sending software process. In some cases, interaction with a device (e.g., using a user interface) will involve passing and / or receiving one or more API calls (e.g., multiple API calls) between multiple different software processes (e.g., different parts of an operating system, applications and operating systems, or different applications) via one or more APIs (e.g., via multiple different APIs). For example, when input is detected, direct sensor data is frequently processed into one or more input events, which are provided (e.g., via an API) to a receiving software process, which makes some determinations based on the input events and then (e.g., via an API) transmits information to the software process to perform an operation (e.g., change the device state and / or the user interface) based on the determinations. While the determinations and the operations performed in response can be made by the same software process, alternatively, the determinations can be made in a first software process and relayed (e.g., via an API) to a second software process different from the first software process, allowing the operation to be performed by the second software process. Alternatively, the second software process can relay instructions (e.g., via an API) to a third software process different from the first and / or second software processes to perform the operation. It should be understood that some or all user interactions with a computer system may involve one or more API calls within the steps of interacting with the computer system (e.g., between different software components of the computer system or between software components of the computer system and software components of one or more remote computer systems).It should be understood that some or all user interactions with a computer system may involve one or more API calls between steps of interaction with the computer system (e.g., between different software components of the computer system or between software components of the computer system and software components of one or more remote computer systems).

[0153] In some implementations, the application can be any suitable type of application, including one or more of the following: browser applications, applications used as execution environments for plugins, widgets or other applications, fitness applications, health applications, digital payment applications, media applications, social networking applications, messaging applications and / or map applications.

[0154] In some embodiments, the application is an application pre-installed on the first computer system at the time of purchase (e.g., a first-party application). In some embodiments, the application is an application provided to the first computer system via operating system update files (e.g., a first-party application). In some embodiments, the application is an application provided via an app store. In some embodiments, the app store is pre-installed on the first computer system at the time of purchase (e.g., a first-party app store) and allows the download of one or more applications. In some embodiments, the app store is a third-party app store (e.g., an app store provided by another device, downloaded via a network, and / or read from a storage device). In some embodiments, the application is a third-party application (e.g., an application provided by an app store, downloaded via a network, and / or read from a storage device). In some embodiments, the application controls the first computer system to execute methods 700, 800, and 900 by calling an application programming interface (API) provided by a system process using one or more parameters. Figure 7 , Figure 8A , Figure 8B and Figure 9 ).

[0155] In some implementations, exemplary APIs provided by system processes include one or more of the following: pairing API (e.g., for establishing a secure connection, such as with an accessory), device detection API (e.g., for locating nearby devices, such as media devices and / or smartphones), payment API, UIKit API (e.g., for generating user interfaces), location detection API, locator API, map API, health sensor API, sensor API, messaging API, push notification API, streaming API, collaboration API, video conferencing API, app store API, advertising service API, web browser API (e.g., WebKit API), transportation API, networking API, WiFi API, Bluetooth API, NFC API, UWB API, fitness API, smart home API, contact transfer API, photo API, camera API, and / or image processing API.

[0156] In some embodiments, at least one API is a software module (e.g., a set of computer-readable instructions) that provides an interface allowing different modules (e.g., an API calling module) to access and use one or more functions, methods, procedures, data structures, classes, and / or other services provided by an implementation module of a system process. The API may define one or more parameters passed between the API calling module and the implementation module. In some embodiments, API 3190 defines a first API call that can be provided by API calling module 3180. An implementation module is a system software module (e.g., a set of computer-readable instructions) configured to perform operations in response to receiving an API call via the API. In some embodiments, the implementation module is configured to provide an API response (via the API) as a result of processing the API call. In some embodiments, the implementation module is included in a device (e.g., 3150) running an application. In some embodiments, the implementation module is included in a separate electronic device.

[0157] Now let’s turn our attention to the implementation of the user interface, which may be optionally implemented on, for example, a portable multifunction device 100.

[0158] Figure 4A An exemplary user interface for an application menu on a portable multifunction device 100 according to some embodiments is illustrated. A similar user interface may optionally be implemented on device 300. In some embodiments, user interface 400 includes the following elements or a subset or superset thereof: • Signal strength indicator 402 for wireless communications such as cellular signals and Wi-Fi signals; • Time 404; • Bluetooth indicator 405; • Battery status indicator 406; • Tray 408 features icons for frequently used applications, such as: o The telephone module 138 has an icon 416 labeled "telephone", which optionally includes an indicator 414 for the number of missed calls or voicemail messages; o An icon 418 labeled "Mail" in the email client module 140, which optionally includes an indicator 410 for the number of unread emails; o The browser module 147 has an icon 420 labeled "Browser"; and o The video and music player module 152 (also known as the iPod (Apple Inc. trademark) module 152) with an icon 422 labeled "iPod"; and • Icons of other applications, such as: o IM module 141's icon 424 labeled "Message"; o Calendar module 148 has an icon 426 labeled "Calendar"; o Image management module 144 icon 428 labeled "Photo"; o The icon 430 of the camera module 143 is labeled "camera"; o The icon 432 of the online video module 155 is labeled "Online Video"; o The icon 434 labeled "Stock Market" in the Stock Market widget 149-2; o Map module 154's icon 436 labeled "map"; o Weather widget 149-1 with icon 438 labeled "Weather"; o Alarm clock widget 149-4 with icon 440 labeled "Clock"; o The icon 442 of the fitness support module 142 is labeled "fitness support"; o The icon 444 labeled "Memo" in the Memo module 153; and o The icon 446, labeled "Settings," is used to set up an application or module that provides access to the settings of the device 100 and its various applications 136.

[0159] It should be pointed out that, Figure 4AThe illustrated icon labels are merely exemplary. For example, icon 422 of video and music player module 152 is labeled "Music" or "Music Player". Other labels may be used for various application icons. In some embodiments, the label of a particular application icon includes the name of the application corresponding to that particular application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to that particular application icon.

[0160] Figure 4B An example is illustrated having a touch-sensitive surface 451 (e.g., separate from the display 450 (e.g., touchscreen display 112)). Figure 3A Devices such as tablets or touchpads (e.g., 355) Figure 3A An exemplary user interface on the device 300. The device 300 may also optionally include one or more contact intensity sensors (e.g., one or more sensors in sensor 359) for detecting the intensity of contact on the touch-sensitive surface 451 and / or one or more haptic output generators 357 for generating haptic output for the user of the device 300.

[0161] While some examples of input on a touchscreen display 112 (which combines a touch-sensitive surface and a display) are given below, in some implementations the device detects input on a touch-sensitive surface separate from the display, such as... Figure 4B As shown in the diagram. In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a spindle (e.g., on the display (e.g., 450) corresponding to the main axis on the display (e.g., Figure 4B The main shaft of 453 in the middle (e.g., Figure 4B (452 in the example). According to these embodiments, the device detects the position corresponding to a specific location on the display (e.g., in...). Figure 4B In the diagram, 460 corresponds to 468 and 462 corresponds to 470) is in contact with the touch-sensitive surface 451 (e.g., Figure 4B (460 and 462 in the text). Thus, when the touch-sensitive surface (e.g., ...) Figure 4B 451 in the middle) and the display of a multi-functional device (e.g., Figure 4B When the touch-sensitive surface (450) is separated, user input detected by the device on the touch-sensitive surface (e.g., touches 460 and 462 and their movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods can be optionally used for other user interfaces described herein.

[0162] Additionally, while the examples below are primarily given with reference to finger input (e.g., finger touch, single-finger tap, finger swipe), it should be understood that in some implementations, one or more of these finger inputs may be replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture may optionally be replaced by a mouse click (e.g., instead of a touch), followed by movement of the cursor along the swipe path (e.g., instead of movement of the touch). As another example, a tap gesture may optionally be replaced by a mouse click when the cursor is over the location of the tap gesture (e.g., instead of detection of touch, followed by cessation of touch detection). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice may optionally be used simultaneously, or mouse and finger touch may optionally be used simultaneously.

[0163] Figure 5A An exemplary personal electronic device 500 is illustrated. Device 500 includes a body 502. In some embodiments, device 500 may include components relative to device 100 and device 300 (e.g., Figures 1A to 4B The device 500 may include some or all of the features described herein. In some embodiments, the device 500 has a touch-sensitive display 504, referred to below as a touchscreen 504. Alternatively, or in addition to the touchscreen 504, the device 500 may also have a display and a touch-sensitive surface. Similar to the cases of devices 100 and 300, in some embodiments, the touchscreen 504 (or touch-sensitive surface) may optionally include one or more intensity sensors for detecting the intensity of an applied contact (e.g., a touch). The one or more intensity sensors of the touchscreen 504 (or touch-sensitive surface) may provide output data representing the intensity of the touch. The user interface of the device 500 may respond to touches based on the intensity of the touch, meaning that touches of different intensities may invoke different user interface operations on the device 500.

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

[0165] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push-buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, allow device 500 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watch straps, bangles, trousers, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow a user to wear device 500.

[0166] Figure 5B An exemplary personal electronic device 500 is depicted. In some embodiments, device 500 may include information about... Figure 1A , Figure 1B and Figure 3ASome or all of the components described. Device 500 has a bus 512 that operatively couples I / O portion 514 to one or more computer processors 516 and memory 518. I / O portion 514 may be connected to display 504, which may have touch-sensitive component 522 and optionally have intensity sensor 524 (e.g., contact intensity sensor). Furthermore, I / O portion 514 may be connected to 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 may optionally be a rotatable input device or a pressable and rotatable input device. In some examples, input mechanism 508 may optionally be a button.

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

[0168] 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 to 900. Figure 7 , Figures 8A to 8B and Figure 9 A computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some examples, the storage medium is a transient computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media can include, but are not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical discs based on CD, DVD, or Blu-ray technology, and persistent solid-state storage such as flash memory, solid-state drives, etc. Personal electronic devices are not limited to... Figure 5B It can be the components and configurations, or it can include other components or additional components in a variety of configurations.

[0169] As used herein, the term "power indication" refers to the ability to indicate power in devices 100, 300, and / or 500 (…). Figure 1A , Figure 3A and Figures 5A to 5BA user-interactive graphical user interface object displayed on a screen. For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) may each constitute a functional representation.

[0170] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface with which a user is interacting. In some specific 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), the cursor is positioned on a touch-sensitive surface (e.g., a...). Figure 3A The touchpad 355 or Figure 4B When an input (e.g., a press input) is detected on the touch-sensitive surface 451 of the display, the specific user interface element is adjusted according to the detected input. This applies to touchscreen displays (e.g., those capable of direct interaction with user interface elements on a touchscreen display) that enable direct interaction with user interface elements on the touchscreen display. Figure 1A The touch-sensitive display system 112 or Figure 4A In some embodiments of the touchscreen 112, a touch detected on the touchscreen acts as a "focus selector," such that when input (e.g., a press input by touch) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, that particular user interface element is adjusted according to the detected input. In some embodiments, focus moves from one area of ​​the user interface to another without corresponding movement of the cursor or movement of a touch on the touchscreen display (e.g., moving focus from one button to another using tab keys or arrow keys); in these embodiments, the focus selector moves according to the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user-controlled user interface element (or a touch on the touchscreen display) that delivers the user's expected interaction with the user interface (e.g., by indicating to the device the element of the user interface that the user expects to interact with). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of the focus selector (e.g., a cursor, touch, or selection box) above the corresponding button will indicate to the user that they expect to activate the corresponding button (rather than other user interface elements shown on the device's display).

[0171] 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 may optionally be based on a predefined number of intensity samples or a set of intensity samples collected over 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 lift off, before or after contact begins to move, before contact ends, before or after contact intensity increases and / or before or after contact intensity decreases). The characteristic intensity of a contact may optionally be based on one or more of the following: the maximum value of the contact intensity, the mean value of the contact intensity, the average value of the contact intensity, the value at the top 10% of the contact intensity, the half maximum value of the contact intensity, or the 90% maximum value of the contact intensity, 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 contact intensity over time). In some implementations, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether a user has performed an action. For example, the set of one or more intensity thresholds may optionally include a first intensity threshold and a second intensity threshold. In this example, contact with a characteristic intensity not exceeding the first threshold results in a first action, contact with a characteristic intensity exceeding the first intensity threshold but not exceeding the second intensity threshold results in a second action, and contact with a characteristic intensity exceeding the second threshold results in a third action. In some implementations, a comparison between the characteristic intensity and one or more thresholds is used to determine whether one or more actions should be performed (e.g., whether to perform the corresponding action or abandon performing the corresponding action) rather than to determine whether to perform the first action or the second action.

[0172] In some implementations, a portion of the gesture is identified for determining the characteristic intensity. For example, a touch-sensitive surface may optionally receive a series of swipe contacts that transition from a starting position to an ending position, where the contact intensity increases. In this example, the characteristic intensity of the contact at the ending position may optionally be based only on a portion of the series of swipe contacts, rather than the entire swipe contact (e.g., only the portion of the swipe contact at the ending position). In some implementations, a smoothing algorithm may optionally be applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm may optionally include one or more of the following: unweighted moving average smoothing algorithm, triangular smoothing algorithm, median filter smoothing algorithm, and / or exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow spikes or dips in the intensity of the swipe contact to achieve the purpose of determining the characteristic intensity.

[0173] Optionally, the contact intensity on a touch-sensitive surface can be 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 on a physical mouse or touchpad. 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 on a physical mouse or touchpad. In some embodiments, when a contact with a characteristic intensity lower than the light press intensity threshold (e.g., and higher than the nominal contact detection intensity threshold, where contacts lower than the nominal contact detection intensity threshold are no longer detected) is detected, the device will move the focus selector based on the movement of the contact on the touch-sensitive surface without performing the operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent across different groups of user interface figures.

[0174] An increase in contact intensity from 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 intensity from 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 intensity from 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 a contact on the touch surface. A decrease in contact intensity from above a contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting a contact being lifted off 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.

[0175] In some embodiments described herein, one or more operations are performed in response to detecting a gesture including 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 intensity of the contact (or multiple contacts) increases to above a press input intensity threshold. In some embodiments, the corresponding operation is performed in response to detecting that the intensity of the corresponding contact increases to above a press input intensity threshold (e.g., a "downward stroke" of the corresponding press input). In some embodiments, the press input includes the intensity of the corresponding contact increasing to above a press input intensity threshold and the intensity of the contact subsequently decreasing to below the press input intensity threshold, and the corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases to below the press input threshold (e.g., an "upward stroke" of the corresponding press input).

[0176] In some implementations, the device employs intensity hysteresis to avoid unintended inputs sometimes referred to as "jitter," wherein the device defines or selects a hysteresis intensity threshold that has a predefined relationship with 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 percentage of the press input intensity threshold). Therefore, in some implementations, a press input includes an increase in the intensity of the corresponding contact above the press input intensity threshold and a subsequent decrease in the intensity of that contact below the hysteresis intensity threshold corresponding to the press input intensity threshold, and an operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases below the hysteresis intensity threshold (e.g., the "upstroke" of the corresponding press input). Similarly, in some implementations, a press input is detected only when the device detects that the intensity of the contact increases from an intensity equal to or below a hysteresis intensity threshold to an intensity equal to or above a press input intensity threshold and optionally the intensity of the contact subsequently decreases to an intensity equal to or below the hysteresis intensity, and an appropriate operation is performed in response to the detection of a press input (e.g., depending on the environment, the intensity of the contact increases or decreases).

[0177] For ease of explanation, optionally, the description of an operation triggered in response to a press input associated with a press input strength threshold or in response to a gesture including a press input may be provided in response to detecting any of the following conditions: the contact strength increases to above the press input strength threshold, the contact strength increases from below a hysteresis strength threshold to above the press input strength threshold, the contact strength decreases to below the press input strength threshold, and / or the contact strength decreases to below the hysteresis strength threshold corresponding to the press input strength threshold. Additionally, in the example where the operation is described as being performed in response to detecting a decrease in contact strength below the press input strength threshold, the operation may optionally be performed in response to detecting a decrease in contact strength below a hysteresis strength threshold corresponding to and less than the press input strength threshold.

[0178] Now let’s turn our attention to the implementation of user interfaces (“UIs”) on electronic devices, such as portable multifunction devices 100, 300 or 500, and the associated processes.

[0179] Figures 6A to 6AM Exemplary user interfaces for logging and / or organizing user activity (e.g., during a subset of a cyclic time period) are illustrated according to some implementation schemes. The user interfaces in these figures are used to illustrate the processes described below, including... Figure 7 , Figures 8A to 8B and Figure 9 The process in.

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

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

[0182] The hourly log user interface 610 also includes a log area 614. Log area 614 includes a meal log recording indicator 614a, an activity log recording indicator 614b, and a mood log recording indicator 614c. The hourly log user interface 610 also includes an hour tab indicator 616a and a settings tab indicator 616b. In some embodiments, selecting the settings tab indicator 616b causes device 600 to display a settings user interface. In some embodiments, the settings user interface includes multiple options, some of which may include reviewing collected data, adjusting time frames, viewing strategies, and customizing measurement units.

[0183] like Figure 6C As indicated by time indicator 604, 4 hours have passed (relative to...). Figure 6B The current time is 12:00. Device 600 has received blood glucose data to be displayed on touchscreen display 602 within 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 the hour along the x-axis and the blood glucose level along the y-axis. Chart line 612c (e.g., corresponding to blood glucose measurements) shows blood glucose measurements over a specific time period. Chart line 612c stops at 12:00, indicating that data was collected before 12:00. Chart line 612c shows standard blood glucose measurements and elevated blood glucose measurements. As shown, elevated measurements (e.g., measurements exceeding predetermined thresholds (e.g., >130 mg / dL; >180 mg / dL)) are visually distinguished from standard measurements (e.g., with different line widths, with different colors). In some embodiments, chart line 612c does not visually distinguish elevated measurements from standard measurements. Device 600 receives a tap input 617 corresponding to a selection of a meal log recording enablement representation 614a. In response to detecting the tap input 617 at the meal log recording enablement representation 614a, device 600 initiates the creation of a log entry for meals (e.g., eating food or drinking beverages (e.g., breakfast, lunch, dinner, snack)). In some embodiments, a selection of an activity log recording enablement representation 614b initiates the creation of a log entry for physical activity (e.g., exercise, meditation). In some embodiments, a selection of an emotion log recording enablement representation 614c initiates the creation of a log entry for emotions (e.g., happiness, sadness, listlessness, excitement).

[0184] exist Figure 6DIn this embodiment, device 600 displays a log entry creation user interface 618 on a touchscreen display 602. The log entry creation user interface 618 includes a time selection indicator 618a. In some embodiments, selection of the time selection indicator 618a allows customization of the time corresponding to the log entry. In this example, the time selection indicator 618a displays (e.g., by default) 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, the search bar 618b can be used to find specific exercises or emotions when logging activities or moods. The log entry creation user interface 618 also includes a camera indicator 618c and a save indicator 618d. In some embodiments, selection of the camera indicator 618c opens the camera of device 600 and allows the user to capture photos of themselves eating. In such embodiments, device 600 generates log entries based on the photos of the meal (e.g., using image recognition software).

[0185] 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 log entry. In some embodiments, when logging activities, the item selection area 620 includes selectable energy representations corresponding to various activities (e.g., walking, cycling, meditation). In some embodiments, when logging emotions, the item selection area 620 includes selectable energy representations corresponding to various emotions / feelings (e.g., sensations (e.g., anxiety, excitement, fatigue)). The device 600 receives tap inputs 622a and 622b corresponding to selections of bread energy representation 620a and salad energy representation 620b, respectively. In some embodiments, when creating a log entry, only one selectable energy representation within the item selection area 620 can be selected. In some embodiments, when creating a log entry, one or more selectable energy representations within the item selection area 620 can be selected. Figure 6E As shown, in response to the detection of tap inputs 622a and 622b, device 600 displays a log entry creation user interface 618, wherein bread energy indicators 620a and salad energy indicators 620b are visually distinct from other food energy indicators (e.g., in bold), thereby indicating that these two foods have been selected for logging.

[0186] exist Figure 6E In this process, device 600 receives a tap input 624 corresponding to a selection of the saved power indicator 618d. In response to detecting the tap input 624, device 600 generates a log entry 614d displayed in the log area 614 of the hourly log user interface 610, such as... Figure 6F As shown.

[0187] exist Figure 6F In this implementation, the 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 a time indication corresponding to the time the food was consumed (e.g., 12:00). Log entry 614d is displayed below “Afternoon,” which indicates the general time period for eating. In this example, the day is divided into four cyclical 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 implementations, quadrants span different time ranges. In some implementations, quadrants are not equal time periods within a 24-hour period (e.g., two 5-hour periods and two 7-hour periods; a longer period is used for the night quadrant). In some implementations, subsets of the cyclical time periods differ from the quadrants (e.g., a day is divided into six or eight parts, or a week is divided into separate days). In some implementations, a full day is a cyclical time period without further subdivision. In some implementations, the cyclical time period is selected by the user (e.g., customized). Log entry 614d also includes optional details specifying the food type (e.g., "sour yeast roll" is a type of "bread"). In this example, "sour yeast roll" is specified under "bread," and an option to "add details..." is displayed under "salad" as a prompt to add details (e.g., notes, specifying the type of salad). In some implementations, selecting "add details..." causes device 600 to display a text input field and keyboard. In some implementations, after additional details are entered, device 600 stops displaying "add details..." and displays the entered text. Log entry 614d optionally includes a selectable display representation 614d1 (e.g., an icon with three dots) to view details and edit (e.g., add or remove food type) or delete the log entry. In some implementations, in response to selecting an indicator 614d1 or a log entry 614d, device 600 displays a log details user interface containing specific details about the log entry (e.g., glucose curve, date, time, and options to edit, copy, or delete the log entry).

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

[0189] Turn now Figure 6G The current date is August 10th, as indicated above device 600. Device 600 displays an hourly log user interface 610 on a touchscreen display 602. The hourly log user interface 610 includes a chart area 612b with chart lines 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, device 600 may receive a swipe input corresponding to chart area 612b to scroll (e.g., horizontal scrolling) and view previously collected data. In some embodiments, the previously collected data within chart area 612b includes meal icons along chart line 612c at the time corresponding to each log entry for breakfast (e.g., toast) and lunch (e.g., pasta), as shown in log area 614.

[0190] Ten days after its introduction, on August 11th, as Figure 6H As shown, device 600 displays an action notification 626 on the hourly log user interface 610. Action notification 626 indicates that the baseline phase is now complete and the next phase of glucose monitoring features (e.g., the action phase) is available. In some embodiments, action notification 626 is displayed after a minimum amount of time has elapsed since the start of the baseline phase (e.g., the start of data collection). In some embodiments, action notification 626 is displayed after device 600 has received sufficient physiological data (e.g., blood glucose measurements). In some embodiments, action notification 626 is displayed after device 600 has received sufficient elevated blood glucose measurements. In some embodiments, the action phase is unavailable (e.g., locked) until criteria such as those described have been met. Action notification 626 includes a continue enable indication 626a (e.g., "Select Action Item"). Device 600 detects a tap input 628 corresponding to a selection of the continue enable indication 626a, and in response to tap input 628, device 600 initiates action phase establishment.

[0191] like Figure 6IAs shown, in response to the detection of a tap input 628, device 600 initiates an action phase establishment by displaying a baseline summary user interface 630 on a touchscreen display 602. The baseline summary user interface 630 includes an informative energy display 630a detailing how physiological data (e.g., blood glucose data) received by device 600 is presented, as well as a continuing energy display 630b. The informative energy display 630a includes an elevation value (e.g., one to ten) corresponding to the elevation level of the received blood glucose measurement (e.g., no elevation, slightly elevated, some elevation, elevated, very elevated). In some embodiments, the elevation value is presented instead of a concentration value (e.g., mg / dL). In some embodiments, the elevation value is based on blood glucose measurements (derived from these blood glucose measurements) over a time period (e.g., from 10:00 to 16:00; one day; seven days a day from 09:00 to 12:00).

[0192] Figure 6I The baseline summary user interface 630 also includes a morning baseline energy display 632. The morning baseline energy display 632 shows a morning baseline graph 632a and morning elevation values ​​632b, which is a visual representation of elevation data received by device 600 during the morning quadrant (e.g., a morning time period (e.g., from 04:00 to 10:00)) during a baseline phase (e.g., introduction phase, initial phase, sensor phase). In some embodiments, the morning baseline graph 632a depicts an instance of physiological data with the highest elevation received by device 600 during the morning quadrant of the baseline phase (e.g., a single morning (e.g., the morning of August 8th)). In some embodiments, the morning baseline graph 632a is based on all physiological data (derived from physiological data) received by device 600 during the morning quadrant of the baseline phase (e.g., displayed as averages) during a baseline phase (e.g., lasting 10 days; lasting one week). In some implementations, the baseline summary user interface 630 presents subsets of cyclical time periods (e.g., a day; a week) that are different from the quadrants (e.g., a day is divided into six or eight parts, or a week is divided into individual days).

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

[0194] exist Figure 6J In the baseline summary user interface 630, an evening baseline energy display 634 is included. The evening baseline energy display 634 is similar to the morning baseline energy display 632; however, the evening baseline energy display 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., a time period during the evening (e.g., from 16:00 to 22:00)). The evening baseline energy display 634 includes an evening baseline graph 634a, which shows the blood glucose measurements received by the device 600 along the x-axis during the evening period (e.g., from 16:00 to 22:00) and along the y-axis. The portions of the evening baseline graph 634a containing elevated measurements are visually distinct from (e.g., having thicker line widths) non-elevated measurements. The evening baseline energy display 634 includes evening elevation values ​​632b. The baseline summary user interface 630 includes an energy display 634c that allows users to selectively view all nighttime data, similar to an energy display 632c that allows users to selectively view all morning data.

[0195] The baseline summary user interface 630 also includes a portion of a nighttime baseline energy display 636, similar to the morning baseline energy display 632 and the evening baseline energy display 634. The nighttime baseline energy display 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., a nighttime period, e.g., from 22:00 to 04:00)). In some embodiments, after receiving scrolling input, the device 600 displays the baseline summary user interface 630, which shows the entire nighttime baseline energy display 636, as well as an optional nighttime energy display similar to the optional viewing of all morning data energy display 632c and the optional viewing of all evening data energy display 634c.

[0196] In the described example, device 600 displays an energy representation corresponding to physiological data received during the morning, evening, and nighttime quadrants within a baseline phase (e.g., an initial time period (e.g., ten days, one week)), and does not display an energy representation 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, device 600 determines one or more portions of the day with the highest elevated blood glucose measurements (e.g., during the baseline phase) based on the received physiological data and displays a baseline energy representation accordingly. In some embodiments, the portion of the day with the highest elevated blood glucose measurements, and therefore displayed by device 600, includes the highest measurements (e.g., three highest measurements between the four quadrants of the day). In some embodiments, the portion of the day displayed by device 600 has the highest elevated value. In some embodiments, the portion of the day displayed by device 600 spends more time in the elevated measurement state. Therefore, in some embodiments, device 600 displays a combination of the morning, afternoon, evening, and nighttime quadrants. In some implementations, device 600 displays an energy indication corresponding to each quadrant (e.g., morning, afternoon, evening, night).

[0197] like Figure 6J As shown, device 600 receives a tap input 640 corresponding to a selection of the continue enable display 630b. In response to detecting the tap input 640, device 600 displays a task selection user interface 642 on the touchscreen display 602, as shown. Figure 6K As shown. The task selection user interface 642 currently includes a portion of a morning task indicator 644, an evening task indicator 646, and a nighttime task indicator 648. Each task indicator (e.g., 644, 646, 648) includes multiple selectable tasks (e.g., three) to be selected to perform during a specified portion of the day (e.g., morning, evening). Selectable tasks are performing physical activity (e.g., “try an activity before or after breakfast”) or eating or forgoing a type of food during the specified portion of the day (e.g., “eat carbohydrates during dinner”; “avoid snacks before or after dinner”). In some embodiments, the tasks presented that affect elevated blood glucose measurements are the same for each user (e.g., standard tasks). In some embodiments, the performance of these tasks has a positive effect on blood glucose measurements (e.g., reducing the elevation of blood glucose measurements). Device 600 receives a swipe input 650 corresponding to a request to scroll the task selection user interface 642.

[0198] In response to the detection of a swipe input 650, device 600 displays another part 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 indicator 644 along with the evening task indicator 646 and the night task indicator 648. The evening task indicator 646 includes three selectable tasks 646a to 646c to be performed to affect blood glucose measurements received by the device 600 during the evening. The night task indicator 648 includes three selectable tasks 648a to 648c to be performed to affect blood glucose measurements received by the device 600 during the night. Selectable task 646a (which is described as "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 blood glucose measurements received by the device 600 during the same time period. Optional task 648b (described as “Try smaller portions of high-reactive foods at dinner”) is a task to be performed at dinner (typically within the nighttime quadrant) to influence blood glucose measurements received by device 600 during the nighttime quadrant period (e.g., a nighttime time period (e.g., from 10:00 PM to 4:00 AM)). In some embodiments, the task is to be performed within a designated portion of the day. In some embodiments, the task may be performed near a designated portion of the day. In some embodiments, the task is to be logged within a designated portion of the day.

[0199] exist Figure 6L In this context, device 600 detects tap input 652a corresponding to the selection of selectable task 648a and tap input 652b corresponding to the selection of selectable task 646a. For example... Figure 6M As shown, in response to receiving tap inputs 652a and 652b, device 600 displays selectable tasks 646a and 648a on touchscreen display 602, each with a checkmark indicating that a task has been selected. When a task is selected, device 600 displays selectable enablement options “Learn More” and “Example” below the selected tasks 646a and 648a. In some embodiments, selecting the “Learn More” enablement option causes device 600 to display additional information about the selected task. In some embodiments, selecting the “Example” enablement option causes device 600 to display one or more examples corresponding to the selected task (e.g., taking a walk after dinner; cycling before dinner; choosing a low-carb dessert before bed; forgoing dessert). When tasks 646a and 648a are selected, device 600 displays a continue enablement option 642a (which reads “Select 2 action items”). Device 600 detects a tap input 654 corresponding to the selection of the continue enablement option 642a, which completes the action phase establishment.

[0200] In response to a tap input 654 established during the completion of the action phase, device 600 displays a progress user interface 656, such as... Figure 6NAs shown. Device 600 also displays a progress tab indicator 616c for navigating to the progress user interface 656. The progress user interface 656 includes a counter 656a that has 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.

[0201] Figure 6N The progress user interface 656 also includes a portion of a night area 658 and a night area 660. Each area contains descriptive text indicating when to perform the selected task. The night area 658 displays the selected task 646a “Try an activity before or after dinner” along with instructions for tracking and optional indicator “Learn More” and “Examples”. The night area 660 contains elements similar to those in the night area 658. In some embodiments, the device 600 detects a swipe input that scrolls the displayed progress user interface 656 and displays the entire night area 658. The device 600 detects a tap input 662 corresponding to a selection of the hour tab indicator 616a and, in response, navigates to the corresponding... Figure 6G and Figure 6O The hourly log user interface shown is similar to the hourly log user interface 610.

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

[0203] In response to receiving a tap input 664 at the activity log recording enable display 614b, device 600 initiates activity logging, such as Figure 6P The log entry creation user interface 618 is shown in the reference. Figure 6DThe log entry creation user interface 618 discussed includes selectable power indicators corresponding to various activities (e.g., relaxation, walking, running). Device 600 detects a tap input 666a at the walking power indicator 620c, and then detects a tap input 666b at the next power indicator 618e. In response to receiving tap inputs 666a and 666b, device 600 displays a task confirmation user interface 668, such as... Figure 6Q As shown.

[0204] Figure 6Q A device 600 is shown that displays a task confirmation user interface 668 on a touchscreen display 602. For example... Figures 6I to 6N As shown, when a log entry is created after a task has been selected to be performed during the action phase, a task confirmation user interface 668 is presented. Task confirmation user interface 668 includes task 646a (which reads "Try an activity during dinner") and task 648a (which reads "Avoid high-carbohydrate foods or drinks before bedtime"), both of which are referenced in... Figures 6I to 6N The task selection period is as described. 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 tasks corresponding to the time specified on the log entry creation user interface 618 (e.g., task 626a is presented when the time specified on the log entry creation user interface 618 is between 16:00 and 22:00), and does not present tasks that do not correspond to the specified time. In some embodiments, when the time specified on the log entry creation user interface 618 does not correspond to the portion of the day used to perform the selected task, the device 600 does not display the task confirmation user interface 618 (e.g., the task confirmation user interface 618 is not displayed for log entries that are not between 16:00 and 22:00 or between 22:00 and 04:00). In some embodiments, device 600 displays a 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 to be completed outside the portion of the day designated for its execution (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 to be completed outside the portion of the day designated for its execution, device 600 displays an information message stating that the effect of performing the selected task outside the portion of the day designated for its execution is indeterminate for the collected physiological data (e.g., "The effect of the entry you logged at 20:00, 'Avoid high-carbohydrate foods or drinks before bed,' is indeterminate for your nighttime blood glucose measurement").

[0205] exist Figure 6Q In the example detailed below, device 600 detects a tap input 670a corresponding to the selection of task 646a. In some embodiments, task 646a is indicated with a checkmark in response to the selection of task 646a. Device 600 also detects a tap input 670b corresponding to the selection of save enable display 668a. In response to receiving tap input 670b, device 600 saves the activity log entry and displays the hourly log user interface 610.

[0206] like Figure 6R As shown, device 600 displays an hourly log user interface 610 with an updated chart area 612b on a touchscreen display 602. The updated chart area 612b shows a time period from 15:30 to 22:00 using chart lines 612c and activity icons 612g. Activity icon 612g corresponds to a “Walking” log entry 614g. The “Walking” log entry 614g includes an indication that task 646a was fulfilled by walking at 20:00. Conversely, the “Baglet” log entry 614f does not fulfill the user-selected task and therefore does not include an indication similar to that of the “Walking” log entry 614g. Device 600 receives a tap input 672 corresponding to a selection of a progress tab enable display 616c and, in response, displays a progress user interface 656, as shown. Figure 6S As shown.

[0207] like Figure 6S As shown, device 600 displays and references information on touchscreen display 602. 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 the action phase setup is complete), but... Figure 6S The progress user interface 656 is shown during the action phase (e.g., August 14). The counter 656a is updated to indicate that five action items (e.g., tasks) have been completed and there are three days left in the action phase to perform the tasks shown on the progress user interface 656.

[0208] exist Figure 6SIn the evening zone 658, the selected task 646a is accompanied by a “walking” log entry 614g and a “cycling” log entry 614h corresponding to the task 646a that satisfies the requirement of “trying an activity before or after dinner.” Log entries 614g and 614h include elevation values ​​indicating the impact of the performed activity (e.g., walking, cycling) on ​​blood glucose measurements received by device 600 during an evening period (e.g., from 16:00 to 22:00) of the day in which the activity was performed (e.g., walking on August 14th, cycling on August 13th). Compared to a typical evening elevation score of “7” received by device 600 during the baseline phase, both walking and cycling resulted in a reduction in the evening elevation score for their respective days (e.g., a reduction to “3”, a reduction to “2”). Device 600 receives a swipe input 674 corresponding to a scrolling progress user interface 656 to view more of the evening zone 660.

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

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

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

[0212] The log details user interface 678 includes an selectable exit power indicator 678c. Device 600 detects a tap input 680 corresponding to a selection of the exit power indicator 678c, and in response, device 600 stops displaying the log details user interface 678 and displays the progress user interface 656, such as... Figure 6V As shown.

[0213] exist Figure 6V In the middle, device 600 returns to the progress user interface 656. The progress user interface includes a selectable plus sign power indicator 660a within the night area 660. Device 600 detects a tap input 682 corresponding to the selection of the plus sign power indicator 660a, and in response, initiates a process for selecting a new task to be performed during the night time period.

[0214] like Figure 6W As shown, in response to receiving a tap input 682, device 600 displays a task addition user interface 684. The task addition user interface 684 includes selectable tasks 648b and 648c to be executed to affect the blood glucose measurement received by device 600 overnight. Tasks 648b and 648c are tasks that were not selected during the action phase setup, see reference... Figures 6I to 6N Further detailed description. In some embodiments, the plus sign indicator 660a is not displayed in the night zone 660, and therefore the task addition user interface 684 is unavailable until the current task (e.g., "Avoid high-carbohydrate foods or drinks before bed") has been completed (e.g., executed, logged) multiple times (e.g., three times). Device 600 detects a tap input 686a corresponding to the selection of task 648c (which reads "Eat high-fiber snacks before bed"). In some embodiments, in response to receiving tap input 686a, device 600 displays task 648c with an indication that it has been selected (e.g., with a checkmark).

[0215] like Figure 6XAs shown, after receiving tap input 686a, device 600 detects tap input 686b corresponding to the selection of the save enable display 684a. In response to receiving tap input 686b, device 600 displays a progress user interface 656 with the new selection listed in the night zone 660. Within the night zone 660, task 648a shows three log entries corresponding to the execution of "avoid high-carbohydrate foods or drinks before bedtime," and task 648c indicates that the log entry corresponding to the execution of "eat high-fiber snacks before bedtime" is not yet complete. In some embodiments, after adding a new task, task 648c is displayed as a selectable option on the task confirmation user interface 668 while creating a new log entry.

[0216] Turn now Figure 6Y The current date is August 18th, seven days after the start of the action phase, and the current time is 09:00. Device 600 displays an elicited notification 688 on the hourly log user interface 610. In some implementations, the elicited notification 688 is displayed on the progress user interface. The elicited 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. Device 600 detects a tap input 690 within the elicited notification 688 corresponding to a selection of a continued enablement indication 688a (e.g., "Add Target"). In response to receiving the tap input 690, device 600 initiates creation. Figure 6Z The goal in the process.

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

[0218] exist Figure 6AAIn this embodiment, device 600 displays a target customization user interface 696. The target customization user interface 696 includes a task 646a along with selectable text fields 696a and 696b for customizing a target based on task 646a, and a day field 696c. 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 (e.g., 20 minutes, 60 minutes). Device 600 detects tap inputs 698a and 698b corresponding to selections 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 the target, device 600 displays a keyboard for entering customized text. Device 600 also detects tap inputs 698c corresponding to selections of the day field 696c. In some implementations, in response to receiving a tap input 698c at the day field 696c, device 600 displays a list from one to seven for selecting how many times per week to perform the goal. In some implementations, the goal customization user interface 696 includes a customization field for specifying when to perform the customized goal based on task 646a (e.g., after dinner, before dinner, or simultaneously with dinner) during a cyclical subset of the cyclical time period.

[0219] exist Figure 6AB In the process, device 600 displays a target-customized user interface 696, which has text fields 696a and 696b displaying "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 a continue enablement indication 696d. In response to detecting the tap input 6100, device 600 saves the customized target 6102, as shown. Figure 6AC As shown.

[0220] exist Figure 6AC In this context, device 600 continues to display a target customization user interface 696 with a customized target 6102 based on task 646a. The target customization user interface 696 now includes "edit" and "delete" additional selectable power representations for the customized target 6102. The target customization user interface 696 also includes an option to add a power representation 696e. In some embodiments, selecting to add a power representation 696e causes device 600 to display a power representation 696e that is consistent with the target 6102. Figure 6Z The target selection user interface shown is similar to target selection user interface 692. Device 600 receives a tap input 6104 corresponding to the selection of the save power indicator 696f. In response to detecting the tap input 6104, device 600 displays progress user interface 656, as shown. Figure 6AD As shown.

[0221] exist Figure 6AD In this embodiment, device 600 displays a progress user interface 656 updated on a touchscreen display 602 when the target stage is being reached. The progress user interface 656 includes selectable weekly energy indicators 656b and 656c. The weekly energy indicator 656c corresponding to the current week "August 18 to August 24" is visually highlighted (e.g., in bold) to indicate that the weekly energy indicator is currently selected. Below the weekly energy indicator 656c, device 600 displays "0%" to indicate that the target has not yet been achieved. In some embodiments, in response to the selection of the weekly energy indicator 656b corresponding to the week "August 11 to August 17" of the action stage, device 600 displays the weekly energy indicator 656b as visually highlighted (e.g., in bold), and the progress user interface 656 includes a night area 658 and a night area 600, as referenced. Figures 6S to 6V As described.

[0222] In this example, Figure 6AD In the context of the process, when the week indicator 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 to 6012e. Progress indicator 6102a is a plus sign, which can be selected to confirm a completed instance of the customized goal. Progress indicator 6102e is labeled "Goal" below it, indicating that the goal has been met for the week at the fifth completed instance of the customized goal.

[0223] Turn now Figure 6AE The current date is August 19th, and the time is 20:00. Device 600 displays a progress user interface 656 with the customized target 6102 and log entries 614i and 614j. In some implementations, log entries 614i and 614j are created via selecting an active logging enablement representation 614b on the hourly log user interface 610, similar to the reference... Figure 6O As described. The “Walking” log entry 614j satisfies task 646a “try an activity before or after dinner,” however, it is not performing the activity for customized goal 6102. In contrast, the “Yoga” log entry 614i satisfies task 646a and is performing the activity for customized goal 6102. In some embodiments, device 600 displays only log entries that satisfy the customized goal (e.g., displays “Yoga” log entry 614i but not “Walking” log entry 614j). In some embodiments, device 600 displays all log entries that satisfy task 646a “try an activity before or after dinner” performed during the week of August 18 to August 24. Device 600 detects a tap input 6106 corresponding to a selection of progress indicator 6102a.

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

[0225] At the end of the week, on August 24, as Figure 6AG As shown, device 600 displays a target review user interface 6108. The target review user interface 6108 includes a customized target 6102, where progress indicators 6102a to 6102d are filled with checkmarks and progress indicator 6102e is empty, indicating that the customized target 6102 was completed four out of five times between August 18th and August 24th. Device 600 detects a tap input 6110 corresponding to a selection of the continue enable indicator 6108a. In response to receiving the tap input 6110, device 600 displays a rating user interface 6112, as shown... Figure 6AH As shown.

[0226] exist Figure 6AH In this embodiment, device 600 displays a rating user interface 6112 including a rating area 6114. The rating area 6114 includes a rating scale from "0 Bad" to "10 Good" and a sliding indicator 6114a positioned at "5". In some embodiments, the sliding indicator 6114a is initially positioned at "0 Bad". Device 600 detects a swipe input 6116 corresponding to selection and movement of the sliding indicator 6114a.

[0227] like Figure 6AI As shown, in response to receiving a swipe input 6116, device 600 moves the sliding power indicator 6114a to the left and updates "Your answer" to "7". Device 600 receives a tap input 6118 corresponding to a selection of the continue power indicator 6112a, and in response, proceeds to the target customized user interface 696.

[0228] exist Figure 6AJ In this context, the target customization user interface 696 includes prompts to modify the customized target 6102 based on task 646a using either an editable display representation 696g or an optional deletion display representation 696h. In some implementations, selecting to edit the display representation 696g causes device 600 to display... Figure 6AB The target is a customized user interface 696. In some implementations, when device 600 is displaying... Figure 6ABWhen the target customization user interface 696 is used to edit a customized target, device 600 receives tap input to change (e.g., modify, edit, update) the customized target to be performed during a subsequent time period (e.g., the following week, August 25 to August 31). In some embodiments, in response to the selection to delete the indicator 696h, device 600 stops displaying (e.g., delete, remove) the customized target 6102. The target customization user interface 696 also includes a prompt to add a new target using the optional addition indicator 696e. In some embodiments, selecting to add an indicator 696e causes device 600 to display the target with... Figure 6Z The target selection user interface shown is similar to a target selection user interface 692 with selectable tasks 648a and 648b. In some embodiments, the selection of task 648a or 648b is initiated and referenced. Figures 6AA to 6AD The described process is similar to the goal creation. In some implementations, selecting to save the power indicator 696f causes the device 600 to display a progress user interface 656, similar to the reference. Figures 6AC to 6AD The process described.

[0229] like Figure 6AI As shown, device 600 receives a score of "7" for a customized target 6102 performed from August 18 to August 24. In some embodiments, if the score is a high-range score (e.g., 7 or higher), device 600 displays a target customization user interface 696, such as in Figure 6J In some implementations, if the rating of the customized target is a medium range (e.g., from four to six), device 600 displays a feedback user interface 6120, such as... Figure 6AK As shown. Figure 6AK The feedback user interface 6120 includes a questionnaire for assessing success factors for achieving the customized goal. In some implementations, if the rating 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 As shown. Figure 6AL The obstacle user interface 6122 includes a questionnaire involving the identification of obstacles (e.g., hindrances) to achieving the customized goal. In some embodiments, device 600 also displays examples of ways to improve success and rating of the customized goal (e.g., time management, ways of maintaining motivation). In some embodiments, device 600 also displays suggestions (e.g., tips) for improving success and rating of the customized goal.

[0230] exist Figure 6AMIn this embodiment, device 600 displays a toolbox user interface 6200. The toolbox user interface 6200 provides information about various user activities (also referred to herein as "actions" or "strategies") that the user can perform to potentially influence the user's bodily parameters, such as blood glucose levels and / or events of elevated blood glucose. In some embodiments, the activities shown in the toolbox user interface 6200 are referenced... Figures 6A to 6AL Examples of activities discussed, such as references Figure 6S The discussion focuses on the "cycling" activity. The Toolbox User Interface 6200 organizes information about user activities based on the level of impact on the user's physical parameters (e.g., events causing elevated blood sugar), as discussed in more detail below.

[0231] exist Figure 6AM In the toolbox user interface 6200, there is an initial display portion 6200a and an additional portion 6200b accessible via scrolling (e.g., in response to a swipe gesture) of the toolbox user interface 6200. At the top of the initial display portion 6200a, the toolbox user interface 6200 includes power indicators 6202a, 6202b, and 6202c, which correspond to the identification baseline phase (also referred to herein as the “baseline phase”), the exploration strategy phase (also referred to herein as the “action phase”), and the construction routine phase (also referred to herein as the “target phase”), respectively. These phases are part of an overall multi-stage process (also referred to herein as the “glucose monitoring feature”) for monitoring and / or influencing the user’s blood glucose levels, as described above. The user can select (e.g., via touch or air gesture) power indicators 6202a, 6202b, or 6202c to navigate to the interface corresponding to the respective phase. Figure 6AM In the device 600 toolbox user interface 6200, the current focus is on the exploration strategy phase, as indicated by the bold text of the power indicator 6202b, the angle brackets below the power indicator, and the indicator 6204b. Indicator 6204a indicates that the exploration strategy phase is currently in progress within a multi-phase process.

[0232] exist Figure 6AMIn the toolbox user interface 6200, a representation of user activities organized based on the level of impact on the user's physical parameters (e.g., blood glucose levels and / or elevated glucose events) is displayed (e.g., representations 6206a, 6206b, 6208a, and 6210a). In some embodiments, data corresponding to a specific user activity (e.g., a specific instance of the execution of the user activity) includes data indicating the impact of the execution of the user activity on physical parameters (e.g., blood glucose levels). For example, referring to representation 6206a corresponding to the "go cycling" activity, this representation includes impact indicators 6206a4 and 6306a5. Impact indicator 6206a4 indicates (e.g., via a numerical value and a down arrow) that the occurrence of the first log entry of the "go cycling" activity resulted in a reduction of 5 elevated glucose events in the corresponding afternoon (as described in more detail above) compared to the baseline / benchmark number of elevated glucose events detected during the afternoon session of the baseline / benchmark phase (e.g., a reduction from 7 events to 2 events or from 5 events to zero events). In some implementations, the occurrence of an activity having a first type of effect (e.g., a reduction in elevated glucose events) is displayed with a first visual characteristic or outline, such as being colored green (e.g., as indicated by the pattern of effect indicator 6206a4). Similarly, effect indicator 6306a5 indicates that a second occurrence of the "going cycling" activity compared to baseline / benchmark resulted in a reduction of two elevated glucose events in the corresponding afternoon. Figure 6AM In the toolbox user interface 6200, a representation 6206a for the "Go Cycling" activity is displayed in area 6206 corresponding to the activity already identified as "most influential" (e.g., an activity that meets the first set of influence level criteria). Representation 6206a also includes an indicator 6206a2 indicating the difficulty level of the activity. In some embodiments, the indicated difficulty is determined by the computer system. In some embodiments, the difficulty is determined by the user and / or logged. In some embodiments, the difficulty level is useful to the user when setting the goal for the activity to be performed. Representation 6206a also includes an indicator 6206a6 indicating the maximum single decrease in glucose events that the "Go Cycling" activity has among all currently logged activities (e.g., a decrease of 5 is the maximum single decrease seen in the toolbox user interface 6200). In some embodiments, a representation (e.g., representation 6206a) can be selected (e.g., via air gestures or touch gestures) to display additional information about the logged events for the corresponding activity. For example, the choice of representation 6206a allows information to be displayed detailing the precise number of elevation events that occur each time during the "go cycling" activity (e.g., not just in...). Figure 6AM The incremental information seen in the data includes information about the date and / or time of each activity and / or information about the corresponding time period (e.g., the afternoon).

[0233] exist Figure 6AM In the representation 6206b corresponding to the “Walking” activity, it has also been identified as being in the “Most Influential” category (e.g., because it also meets the first set of influence level criteria) and is therefore also displayed in area 6206 of the toolbox user interface 6200. Representation 6206b includes four influence indicators, including indicator 6206b1 depicting an equal sign. Indicator 6206b1 indicates that the occurrence of one of the four log entries of the “Walking” activity resulted in no change in the number of elevated glucose events in the corresponding morning time period relative to the baseline / benchmark number of elevated glucose events observed in the morning time period during the baseline / benchmark phase. It should be noted that despite this result, the “Walking” activity was determined to be the “Most Influential” activity based on the total influence data of all occurrences of the activity. Representation 6206b also includes indicator 6206b2, which indicates that the “Walking” activity has the most log entries (e.g., a reduction of 3 occurrences) among all currently logged activities that have the effect of reducing elevated glucose events.

[0234] exist Figure 6AM In this context, the toolbox user interface 6200 also includes a region 6208 corresponding to activities that have been identified as having a smaller impact (e.g., a smaller impact compared to those in region 6206). Figure 6AM In this context, region 6208 includes designation 6208a, which corresponds to the food-related activity – “reduced portion size”. Although this activity resulted in one fewer elevated glucose event compared to baseline / benchmark, computer system 600 displays designation 6208a in region 6208 instead of region 6206 because it determines that the level of effect does not meet the “most influential” criterion.

[0235] exist Figure 6AM In the toolbox user interface 6200, there is also a region 6210 corresponding to activities that have been deemed not to meet the "most influential" or "less influential" categories. Figure 6AM In this context, region 6210 includes indication 6210a, which corresponds to the food-related activity – “eating carbohydrates last.” Indication 6210a indicates that two occurrences of the activity are logged, including the first occurrence corresponding to the evening time period, where an increase in elevated glucose events (e.g., relative to baseline) is observed, as indicated by influence indicator 6210a1 (e.g., 2 with an upward arrow). In some embodiments, the occurrence of activities with a second type of influence (e.g., an increase in elevated glucose events) is displayed with a second visual characteristic or outline, such as being colored orange (e.g., as indicated by the pattern of influence indicator 6210a1, which is different from the pattern of influence indicator 6206a4).

[0236] exist Figure 6AM The toolbox user interface 6200 also includes an indicator 6212, which can be selected to cause the computer system 600 to display additional activities / strategies (e.g., strategies without any log entries or strategies that meet different impact criteria). The toolbox user interface 6200 also includes an indicator 6214 for accessing information that may be related to events affecting blood glucose levels and / or events such as certain foods or activities. The toolbox user interface 6200 also includes indicators 6216a, 6216b, 6216c, and 61216d, which respectively correspond to accessing the home page of an application including the toolbox user interface 6200 (e.g., an hourly log user interface 610), accessing the toolbox user interface 6200, accessing details of body parameter sensors (e.g., a continuous glucose sensor), and accessing a settings user interface (e.g., similar to indicator 616b).

[0237] In some implementations, when additional activities are logged, if the additional impact data leads to a reclassification of the activities, the representation of the activities (e.g., representations 6206a, 6206b, 6208a, and / or 6010a) is updated to include additional impact indicators and / or moved to a different area of ​​the toolbox user interface 6200.

[0238] Figure 7 This is a flowchart illustrating a method for logging user activity using an electronic device during a subset of a cyclic time period, according to some embodiments. Method 700 is performed at a computer system (e.g., 100, 300, 500, 600) that communicates with display generation components (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 may be optionally combined, some operations may be optionally changed in order, and some operations may be optionally omitted.

[0239] 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 generating component (e.g., 602) and one or more input devices (e.g., 112, 160, 602). The display generating component is configured to provide visual output, such as display via a CRT monitor, via an LED monitor, or via image projection. In some embodiments, the display generating component is integrated with the computer system. In some embodiments, the display generating component is separate 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 separate from the computer system. Therefore, the computer system can transmit data (e.g., image data or video data) to the integrated or external display generating component via a wired or wireless connection to visually generate content (e.g., using a display device), and can receive input from one or more input devices via a wired or wireless connection.

[0240] As described below, method 700 provides an intuitive way to log user activity during a subset of a cyclic time period. This method reduces the cognitive burden on the user regarding logging user activity during a subset of a cyclic time period, thereby creating a more efficient human-computer interface. For battery-powered computing devices, it enables users to log user activity faster and more efficiently during a subset of a cyclic time period, saving power and increasing the time interval between battery charging.

[0241] The computer system displays (706) 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) via a display generation component (e.g., 602). This set of one or more selectable task user interface objects includes the determination (708) of physiological data (e.g., 634a) of a day (e.g., when device 600 receives data to display time of day in line graph 634a) based on a first subset of cyclic time periods (e.g., specific time quadrants of a day (e.g., 6 hours, morning, afternoon, evening, night); or physiological data (e.g., 634a) of a day in a week (e.g., Monday, Tuesday) (e.g., data on blood glucose levels (e.g., quantification of elevated blood glucose levels over a period of time); baseline blood glucose measurements) satisfying a first set of criteria (e.g., as shown by the elevation scales of 630a, 634b). In some embodiments, the first set of criteria includes criteria that must be met when physiological data exceeds a threshold (e.g., blood glucose levels exceed a threshold blood glucose level) and criteria corresponding to the first subset of cyclic time periods (e.g., in...). Figure 6NThe first selectable task user interface object (e.g., 646a to 646c) is a first type of user activity (e.g., 646a (“try an activity”), 646b (“eat carbohydrates”), 646c (“avoid snacks”)) performed during the time period specified in 658. In some embodiments, one or more selectable task user interface objects do not include the first selectable task user interface object based on the determination that physiological data from a first subset of the cyclic time period does not meet a first set of criteria. This set of one or more selectable task user interface objects includes: a determination (710) that physiological data (e.g., a line graph displayed in 636) from a second subset of the cyclic time period (e.g., the time of day when device 600 receives data to display a line graph within 636) meets the first set of criteria (e.g., the elevation value within 636 as indicated by the elevation value scale of 630a), corresponding to the time to be performed in the second subset of the cyclic time period (e.g., in the first subset of the cyclic time period). Figure 6N A second selectable task user interface object (e.g., 648a to 648c) for a second type of user activity (e.g., 648a (“Avoid high-carbohydrate foods”), 648b (“Try smaller portions”), 648c (“Eat high-fiber snacks”)) performed during a time period specified in 660 (e.g., a different type of activity from the first type of user activity). In some embodiments, one or more selectable task user interface objects do not include the first selectable task user interface object, based on the determination that physiological data from a second subset of the cyclic time period meets the first set of criteria.

[0242] When the task selection user interface is displayed (e.g., 642), the computer system receives (712) a first set of one or more inputs (e.g., 652a, 652b, 654) via one or more input devices (e.g., 112, 160) (e.g., tap input).

[0243] In response to receiving (714) a first set of one or more inputs and based on the determination of the first set of one or more inputs including an input (e.g., 652a) selecting a first selectable task user interface object (e.g., 646a), the computer system, in a first subset of the cyclic time period (e.g., in Figure 6NDuring the time periods specified in 646 and 660 (e.g., during future occurrences of a first subset of the cyclic time period), logging (716) of the first type of user activity (e.g., 646a) is enabled (e.g., recording via user input; tracking; logging). In response to receiving (714) one or more first sets of inputs and 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 the second type of user activity (e.g., 648a) during the second subset of the cyclic time period (e.g., as specified in 660). In some embodiments, logging of the first type of user activity during the first subset of the cyclic time period is not enabled. Based on whether the physiological data of different subsets of the cyclic time period meet a set of criteria, the system displays feedback to the user on the physiological data of different subsets of the cyclic time period to either the first selectable task user interface object corresponding to the first user activity or the second selectable task user interface object corresponding to the second user activity. Providing users with improved visual feedback enhances device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0244] Before displaying the task selection user interface (e.g., 642), the computer system receives (702) (e.g., via one or more physiological sensors communicating with the computer system (e.g., integrated into the computer system; communicating with the computer system); data transmission from another computer system) a first predetermined time period (e.g., as referenced) Figures 6A to 6G The first set of physiological data (e.g., represented by 612c) described for the period from August 1st to August 10th (e.g., 10 days, 14 days, 30 days) includes physiological data for a first subset of the cyclical time periods (e.g., the cyclical time periods are the time periods from 12 PM to 6 PM each day of a predetermined time period) based on a subset (e.g., 632a, 634a) of the first set of physiological data for the predetermined time periods (e.g., represented by 612c from August 1st to August 10th) (e.g., derived from, extrapolated from, extracted from the subset). In some embodiments, the physiological data are blood glucose data for the time period from 12 PM to 6 PM during a 10-day data collection period.

[0245] After receiving a first set of physiological data for a first predetermined time period (e.g., in response to the completion of receiving 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 summarization user interface (e.g., 630), which includes a first representation (e.g., 632a, 632a) of physiological data in the first set of physiological data for the first predetermined time period that exceeds a first threshold (e.g., values ​​below 632a and 634b) (e.g., a graphical user interface object; a representation in a graph; a numerical value). In some embodiments, the first representation of physiological data includes an indication of a subset of the cyclic time periods during which physiological data is acquired (e.g., a 6-hour quadrant of a day). In some embodiments, the data summarization 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. In some embodiments, the second representation of physiological data corresponds to data from a different subset of the cyclic time periods (e.g., from different quadrants of a day) that is different from the data corresponding to the first representation of physiological data. Displaying the first representation of physiological data exceeding the threshold provides the user with additional feedback as a subset of the received data. Providing users with improved visual feedback enhances device operability and makes the user device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0246] Prior to receiving a first set of physiological data for a first predetermined time period (e.g., before receiving all of the first set of physiological data), the task selection user interface (e.g., 642) is unavailable for display (e.g., locked; unavailable for display upon user request). In response to receiving the first set of physiological data for the first predetermined time period (e.g., receiving all of the 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 a predetermined time period, at least a first interface from a set of user interfaces including the task selection user interface is displayed. The task selection user interface is provided in response to the receipt of data to display an interface that controls access to the interface 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 device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0247] In some implementations, the first type of user activity to be performed during a first subset of the cycle time period is performing physical activity (e.g., 614g, 614h) (e.g., exercise) or eating food or drinking beverages (e.g., in...). Figure 6T (e.g., eating).

[0248] After logging of the first type of user activity is enabled during a first subset of the cyclic time period and after logging of the second type of user activity is enabled during a second subset of the cyclic time period, the computer system displays a progress user interface (e.g., 656) (e.g., an interface including a representation of the user activity that has been enabled for logging completion), based on the first subset of the cyclic time period (e.g., during...). Figure 6SThe process logs the identification of the first instance (e.g., “walking” in 614g, “cycling” in 614h) of a first type of user activity (e.g., 646a) (e.g., physical activity (e.g., exercise); eating food or drinking beverages (e.g., eating carbohydrates last)) during a time period specified in 658 (e.g., a cyclical time period is a period from 12 PM to 6 PM every day). The progress user interface includes displaying a representation (e.g., 614g, 614h) corresponding to the first instance of the first type of user activity within a first part (e.g., 658) (e.g., the first third) of the progress user interface (e.g., a user interface containing all completed action items) of the first instance (e.g., 614g, 614h) (e.g., a user interface object (e.g., a selectable interface object (e.g., a power display)), wherein the first part of the progress user interface corresponds to a first subset of the cyclical time period (e.g., a portion dedicated to the logged events from 12 PM to 6 PM every day).

[0249] After logging of the first type of user activity is enabled during a first subset of the cyclic time period and after logging of the second type of user activity is enabled during a second subset of the cyclic time period, the computer system displays a progress user interface (e.g., 656) (e.g., an interface including a representation of user activity that has been enabled for logging completion), based on the second subset of the cyclic time period (e.g., in...). Figure 6T During the time period specified in 660 (e.g., a cyclical time period is the period from 12 PM to 6 PM every day), log the first instance of the second type of user activity (e.g., 648a) (e.g., physical activity (e.g., exercise); eating food or drinking beverages (e.g., eating carbohydrates last)). Figure 6T The determination of "sugar-free cheesecake"), the progress user interface includes, within the second part (e.g., 660) (e.g., the first third) of the progress user interface (e.g., a user interface containing all completed action items), a representation of the first instance corresponding to the second type of user activity (e.g., ...) is displayed (e.g., ...) Figure 6TThe second part of the progress user interface corresponds to a second subset of the cyclic time period (e.g., a portion dedicated to logged events from 12 PM to 6 PM each day), as described in 648a below (e.g., a user interface object, such as a selectable interface object, such as a power indicator). In some embodiments, the representation of completed user activity includes an elevation score. In some embodiments, each part of the progress user interface includes a baseline measurement elevation score. In some embodiments, a representation of a second instance of a first type of user activity is displayed within a first part of the progress user interface. The user interface displaying a representation of completed instances of user activity organized by subsets of cyclic time periods provides the user with improved feedback on what logged activities the computer system has received during a specific subset of the cyclic time period. Providing the user with improved visual feedback enhances device operability 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 consumption and extends device battery life by enabling the user to use the device more quickly and efficiently.

[0250] After enabling logging of the first type of user activity during a first subset of the cyclic time period, the computer system displays a first representation (e.g., 614h) of the logged instance of the first type of user activity (e.g., “riding” at 18:30) (e.g., user interface object (e.g., selectable interface object (e.g., power display))).

[0251] The computer system receives a first input (e.g., 676) (e.g., a tap) representing a logged instance of a first type of user activity.

[0252] In response to receiving 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 exceed a first threshold in a first set of physiological data for a first predetermined time period.

[0253] In response to receiving 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 (e.g., physiological data collected during the action phase; data different from the first set of physiological data) corresponding to a logged instance of a first type of user activity (e.g., 678b).

[0254] In response to receiving first user input, the computer system displays a comparison user interface (e.g., 678), which includes a first type of user activity (e.g., along...). Figure 6U The second representation (e.g., similar or identical to the first representation graphic) of the logged instance of the activity icon (678b). The user interface displaying the first and second representations of physiological data with the same subset of cyclic time periods provides the user with feedback on the status of the data received by the computer system for the same time subset. 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 consumption and extends the device's battery life by enabling the user to use the device more quickly and efficiently.

[0255] The number of times that the first type of user activity has been logged more than the second threshold (e.g., Figure 6V After the three log entries listed below 648a (e.g., the activity is executed three or more times), the computer system displays a first selectable user interface object (e.g., 660a) (e.g., a plus button for adding new user activities).

[0256] 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 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 the type of user activity to be performed during a first subset of a cyclic time period.

[0257] In response to receiving a second set of one or more inputs, the computer system enables the first subset of the time interval during the loop (e.g., in...). Figure 6XLogs are kept of third-type user activities (e.g., 648c) during a specified time period (as specified in 660). In some implementations, an action phase is initiated using two action items to be performed in different subsets of the cyclic time period, and then a third action item is added to a subset of the subsets, allowing two or more action items to be performed within a subset of the cyclic time period. In some implementations, a third action item is added to a third subset of the cyclic time period (e.g., the cyclic time period is from 6 PM to 12 AM daily). In some implementations, user activities (e.g., action items) are the same for all users (e.g., not personalized). After a condition is met, a selectable user interface object is displayed to provide feedback to the user that additional actions can be performed. Providing improved visual feedback to the user enhances device operability 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 consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0258] After enabling logging of the first type of user activity during a first subset of the cyclic time period, the computer system receives one or more third sets of 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...). Figure 6O The third set of inputs (e.g., 664 at 614b) (e.g., entries corresponding to the performance of user activities (e.g., physical activities (e.g., exercise); eating food or drinking beverages); entries corresponding to the user's current mood or emotion). In some implementations, 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 when the activity was performed; the current mood).

[0259] After receiving input to initiate a log entry, the computer system displays an optional confirmation user interface object for the first type of user activity (e.g., such as...). Figure 6Q (646a, 648a shown on 668).

[0260] After receiving input to initiate a log entry and in response to receiving a third set of one or more inputs, the computer system log records an instance of the first type of user activity (e.g., 614g), based on the determination of a selection of an optional confirmation user interface object for the first type of user activity (e.g., 670a).

[0261] After receiving input to initiate a log entry and in response to receiving a third set of one or more inputs, if the third set of one or more inputs does not include a determination of the selection of an optional confirmation user interface object for the first type of user activity, the computer system logs events that are not instances of the first type of user activity (e.g., similar to...). Figure 6R (The "bagel" log entry). In some embodiments, logging instances of the 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 events 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 instances and events are editable. In some embodiments, the selectable user interface objects corresponding to events are displayed only in the hour tab and not on the progress tab. In some embodiments, the selectable user interface objects corresponding to instances of the first type of user activity are displayed on both the hour tab and the progress tab. In some embodiments, initiating a log entry includes logging the time of day. In some embodiments, if the first type of user activity is performed during a specified subset of time periods that are not within a cyclic time period, the log entry includes instances of the first type of user activity indicating that the effect of performing the first type of user activity is indeterminate (e.g., the action affects a specified subset of glucose measurements within a cyclic time period).

[0262] In some implementations, enabling logging of the first type of user activity during a first subset of the cyclic time period includes: enabling logging of the first type of user activity during the first subset of the cyclic time period for a second predetermined time period (e.g., as referenced). Figures 6H to 6X The number of days described is represented by "remaining days" from August 11 to August 18 in 656a (e.g., 7 days, 14 days). In some implementations, after a second predetermined time period, at least one function for logging the first type of activity becomes disabled.

[0263] After the end of the second predetermined time period, the computer system provides a target creation user interface (e.g., 692) for display (e.g., making the target creation user interface available for display (e.g., from a previously unavailable state)), wherein the target creation user interface was not available for display before the end of the second predetermined time period. In some embodiments, the target creation user interface is the interface corresponding to method 800. Providing the target creation user interface for display after the end of the predetermined time period allows access to the interface at a time point relevant to its functionality. Performing optimization operations when a set of conditions have been met without further user input 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 consumption and extends the device's battery life by enabling the user to use the device more quickly and efficiently.

[0264] It should be noted that the above text regarding method 700 (for example, Figure 7 The details of the process described herein also apply in a similar manner to the methods described below. For example, method 800 may optionally include 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 of this type of user activity during a first subset of the cyclic time period as in method 700. For the sake of brevity, these details will not be repeated below.

[0265] Figures 8A to 8B This is a flowchart illustrating a method for logging user activity using an electronic device during a subset of a cyclic time period, according to some embodiments. Method 800 is performed at a computer system (e.g., 100, 300, 500, 600) (e.g., a smartphone, a smartwatch), 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 may be optionally combined, some operations may be optionally changed in order, and some operations may be optionally omitted.

[0266] As described below, method 800 provides an intuitive way to log user activity during a subset of a cyclic time period. This method reduces the cognitive burden on the user regarding logging user activity during a subset of a cyclic time period, thereby creating a more efficient human-computer interface. For battery-powered computing devices, it enables users to log user activity faster and more efficiently during a subset of a cyclic time period, saving power and increasing the time interval between battery charging.

[0267] The computer system displays (802) a target-created user interface (e.g., 692, 696) via a display generation component (e.g., 602) having a set of one or more selectable target-created user interface objects (e.g., 648a, 646a, 648c). Based on a first subset within a cyclic time period (e.g., in...), Figure 6S The first type of user activity (e.g., the activities described in 646a) performed within the time period specified in 658 (e.g., a specific time quadrant of a day (e.g., 6 hours of the day, morning, afternoon, evening, night); a day of the week (e.g., Monday, Tuesday)) meets the first set of criteria (e.g., in Figure 6Z The determination of the criteria discussed in the context (804) means that the set of one or more selectable user interface objects includes a first selectable target creation user interface object (e.g., 646a) corresponding to a first type of user activity to be performed during a first subset of the cyclic time period. In some embodiments, the first set of criteria includes criteria that are met 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 met when it is determined that the first type of user activity has a positive effect on physiological data. In some embodiments, one or more selectable target creation user interface objects do not include a first selectable target creation user interface object based on the determination that the first type of user activity performed within the first subset of the cyclic time period does not meet the first set of criteria. In some embodiments, the first type of user activity performed within the first subset of the cyclic time period is logged according to the method of 700. In some embodiments, the first set of criteria includes criteria that are met when the first type of user activity has been available for a predetermined time period (e.g., a 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 a second subset of the cyclic time period that is different from the first subset of the cyclic time period (e.g., in... Figure 6T The second type of user activity (e.g., the activity described in 648a) performed within the time period specified in 660 meets the first set of criteria (e.g., in Figure 6ZThe determination of the criteria discussed in the context (806) includes one or more selectable user interface objects in the group, which include a second selectable target creation user interface object (e.g., 648a) corresponding to a second type of user activity (e.g., an activity type different from the first type of user activity) to be performed during a second subset of the cyclic time period.

[0268] When the user interface is created for the display target (e.g., 692), the computer system receives (818) a first set of one or more inputs (e.g., 694a, 694b, 698a, 698b, 698c) (e.g., a tap).

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

[0270] In response to receiving (820) a first set of one or more inputs and creating a user interface object based on the first set of one or more inputs, including selecting a second selectable target (e.g., in...), Figure 6Z Upon determination of the tap at 648a, the computer system enables (824) logging of the second type of user activity for a predetermined duration (e.g., 656c) during a second subset of the cyclic time period. In some embodiments, logging of the first type of user activity is not enabled during the first subset of the cyclic time period. Feedback is provided to the user about what type of activity was previously performed by 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. Providing improved visual feedback to the user enhances device operability 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 consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0271] In some implementations, the target of creating a user interface (e.g., 696) includes (808) (e.g., simultaneously, not simultaneously) a set (810) of one or more selectable user interface objects (e.g., 696a) (e.g., text fields; selectable predefined options), which, when selected, is configured (e.g., identifier; description; settings) a subtype of a first type of user activity (e.g., 646a) (e.g., "yoga", as in...). Figure 6AB (Discussed in the context of the location). In some implementations, the objective of creating a user interface (e.g., 696) includes (808) (e.g., simultaneously, not simultaneously) a set (812) of one or more selectable user interface objects (e.g., 698b) (e.g., text fields; selectable predefined options), which, when selected, configure (e.g., identifier; description; settings) a first subset of a cyclic time period (e.g., in...). Figure 6S The time period within which the first type of user activity is to be performed (e.g., "before and after dinner" in 646a) is specified in 658 (e.g., before dinner; after dinner; at the beginning or end of the first subset of the cyclic time period). In some embodiments, the target user interface (e.g., 696) includes (808) (e.g., simultaneously, not simultaneously) a set (814) of one or more selectable user interface objects (e.g., 696b) (e.g., text fields; selectable predefined options), which, when selected, is configured (e.g., identifier; description; setting) for the duration within which the first type of user activity is to be performed (e.g., as in...). Figure 6AB (e.g., 30 minutes; 60 minutes). The selectable user interface object displaying 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 consumption and extends the device's battery life by enabling the user to use the device more quickly and efficiently.

[0272] In some implementations, the target 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), which, when selected, are configured (e.g., identifier; description; settings) to perform (e.g., log for execution) a target number of times a first type of user activity is to be performed during a first subset of a predetermined duration of a cyclic time period. Figure 6AB(The "5 times" discussed here) (e.g., the target). Displaying selectable user interface objects for configuring targets provides users with more control over the device. Providing additional control over the device enhances its operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends the device's battery life by enabling users to use the device more quickly and efficiently.

[0273] In some implementations, the first set of criteria is met when a given type of user activity has been performed (e.g., executed and logged) at least once during a previously predetermined time period (e.g., 614g, 614h, log entries listed within 660) (e.g., an action phase). In some implementations, the first set of criteria is met when physiological data indicates that a given type of user activity has a target (e.g., positive) effect on a physiological parameter (e.g., blood glucose level). In some implementations, for each given type of activity that meets the first set of criteria, the target creation user interface (e.g., 692) includes selectable target creation user interface objects (e.g., as shown in...) for the given type of activity that meets the first set of criteria. Figure 6Z (Referring to 646a, 648a, and 648c). In some implementations, the target creation user interface provides target creation user interface objects for all types of activities performed during the action phase. Selectable target creation user interface objects are displayed for a given type of activity that meets the first set of criteria, providing the user with additional feedback as to the specific activity being performed. Providing the user with improved visual feedback 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 consumption and extends the device's battery life by enabling the user to use the device more quickly and efficiently.

[0274] After enabling logging of the first type of user activity (e.g., 6102) during a predetermined duration in the first subset of the cycle time, the computer system displays the target number of times the first type of user activity (e.g., 6102) is to be performed during the first subset of the cycle time within the predetermined duration (e.g., as in...). Figure 6ABThe representation of “5 times” (e.g., minimum number of times) discussed herein (e.g., 6102a to 6102e) (e.g., indication; graphical user interface object). In some embodiments, the representation includes an indication of the number of times a 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. An indication (e.g., a progress indicator) showing progress toward a target number of times the first type of user activity is to be performed during a first subset of the cyclical time period within a predetermined duration provides the user with feedback on what is needed to meet the target. 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 consumption and extends the device's battery life by enabling the user to use the device more quickly and efficiently.

[0275] After enabling logging of the first type of user activity (e.g., 6102) for a predetermined duration during the first subset of the cycle time and after the predetermined duration ends (e.g., at... Figure 6AG On August 24th, the computer system received feedback corresponding to the first type of user activity (e.g., along with...). Figures 6AH to 6AI The second set of one or more user inputs (e.g., 6110, 6116, 6118) of the rating scale 6114a (e.g., feedback indicating the user’s emotions and / or the evaluation of the performance of the first type of user activity during a predetermined duration).

[0276] After receiving a first set of one or more user inputs (e.g., after selecting 696g), and, in some embodiments, based on the determination that feedback on a first type of user activity meets a 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 6ABThe set of one or more selectable user interface objects (e.g., text fields; selectable predefined options) modifies one or more characteristics of a first type of user activity when selected (e.g., the target number of times the activity is to be performed; the duration of the activity within which it is to be performed) (e.g., modifying logging to occur during a second, upcoming, predetermined time period). Displaying one or more selectable user interface objects to modify one or more characteristics of a first type of user activity provides the user with more control over the device. Providing additional control over the device enhances its operability 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 consumption and extends the device's battery life by enabling the user to use the device more quickly and efficiently.

[0277] After enabling logging of the first type of user activity during the first subset of the cycle time for a predetermined duration and after the predetermined duration ends (e.g., at...), Figure 6AG After August 24, the computer system receives a second set of one or more user inputs (e.g., 6110, 6116, 6118) corresponding to feedback on the first type of user activity (e.g., feedback indicating the user's emotions and / or evaluation of the performance of the first type of user activity during a predetermined duration).

[0278] After receiving a second set of one or more user inputs (e.g., after selecting 696e), and, in some embodiments, based on the determination that feedback on a first type of user activity meets a 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 6ZThe set of one or more selectable user interface objects (e.g., text fields; selectable predefined options) enables logging of a third type of user activity, different from the first type, for a second predetermined duration (e.g., a subsequent period of 7 days) during a first subset of the cyclical time period, after a first predetermined time period. In some embodiments, different questions are displayed based on the selection of the sorting energy representation (e.g., what is going well? What could be done better?). In some embodiments, tips for overcoming obstacles are provided for selecting a low sorting energy representation (e.g., 4 or lower). In some embodiments, six tips are displayed for each action item category. In some embodiments, no tips are displayed for selecting a high sorting energy representation (e.g., 7 or higher), and the option to modify the goal is advanced. Displaying one or more selectable user interface objects to enable logging of the third type of user activity gives the user more control over the device. Providing additional control over the device without cluttering the UI with additional displayed controls enhances device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0279] After logging of a first type of user activity for a predetermined duration is enabled during a first subset of the cycle time, the computer system displays a progress user interface (e.g., 656) (e.g., an interface including a representation of user activity that has been enabled for the completion of 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), which, when selected, is displayed during the previously predetermined time period (e.g., 614g, 614h). Figures 6S to 6VThe system includes: a representation of logged instances of a first type of user activity (e.g., a first type of user activity performed during a first subset of a cyclic time period) within the log entries listed in 660; and a second selectable user interface object (e.g., 656c) corresponding to a predetermined duration, which, when selected, displays a representation of logged instances (e.g., 614i, 614j) of the first type of user activity (e.g., a first type of user activity performed during a first subset of a cyclic time period). Displaying a user interface with selectable user interface objects to view logged activities within a predetermined time period provides the user with improved feedback on what logged activities the computer system has received. Providing the user with improved visual feedback enhances device operability 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 consumption and extends device battery life by enabling the user to use the device more quickly and efficiently.

[0280] Figure 9 This is a flowchart illustrating a method for organizing user activities using an electronic device according to some embodiments. Method 900 is performed at a computer system (e.g., 100, 300, 500, 600) that communicates with display generating components (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 900 may be optionally combined, some operations may be optionally changed in order, and some operations may be optionally omitted.

[0281] 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 generating component (e.g., 602) and one or more input devices (e.g., 112, 160, 602). The display generating component is configured to provide visual output, such as display via a CRT monitor, via an LED monitor, or via image projection. In some embodiments, the display generating component is integrated with the computer system. In some embodiments, the display generating component is separate 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 separate from the computer system. Therefore, the computer system can transmit data (e.g., image data or video data) to the integrated or external display generating component via a wired or wireless connection to visually generate content (e.g., using a display device), and can receive input from one or more input devices via a wired or wireless connection.

[0282] As described below, Method 900 provides an intuitive way to organize user activities. This method reduces the cognitive burden on users organizing their activities, thereby creating a more efficient human-computer interface. For battery-powered computing devices, it enables users to log user activities more quickly and efficiently during subsets of cyclic time periods, saving power and increasing the time interval between battery charging cycles.

[0283] The computer system accesses (902) data corresponding to the first set of occurrences of user activities (e.g., physical activities (e.g., exercise); eating or drinking certain foods) (e.g., multiple instances corresponding to a single type of activity or multiple instances corresponding to different types of occurrences (e.g., two instances of walking after dinner and three instances of eating low-sugar foods)) (e.g., locally stored data stored on a storage device of the computer system and / or remotely stored data stored on an external computer system) (in some embodiments, the data is user log data, data collected by one or more sensors, and / or data collected by the computer system); this data includes: first data (904) (e.g., corresponding to data representing 6206a), which includes data on user activities (e.g., the "going cycling" activity of 6206a). An indication of the effect of a first subset (e.g., type of user activity) on a first physiological parameter (e.g., 6206a4) (in some embodiments, the first data is a subset of the accessed data corresponding to the first user activity type (e.g., all data, for all instances, for the post-dinner walking activity type)) (in some embodiments, the indication of the effect includes a separate indication of the effect on each instance of the first user activity type) (e.g., in some embodiments, the first data includes data for 3 instances of the post-dinner walking activity type, with discrete indications of the effect on each of the 3 instances); and second data (906) (e.g., data corresponding to 6210a), which includes an indication of the effect of a second subset of user activities on the first physiological parameter (e.g., 6210a1). In some embodiments, the first subset of user activities is a first type of activity performed during a first time period, and the second subset of user activities is the same first type of activity performed during a second time period different from the first time period (e.g., the first subset is post-dinner walking activity, and the second subset is post-lunch walking activity).

[0284] The computer system receives (908) a request via one or more input devices to display a first user interface (e.g., 6200) (e.g., a summary user interface, an overview user interview including data from multiple stages of the process, and / or a data room user interface).

[0285] In response to receiving a request to display a first user interface, the computer system displays (910) the first user interface (e.g., 6200) via a display generation component.

[0286] The display of the first user interface includes a computer system display (912) of a first graphical representation (e.g., 6206a) of first data corresponding to a first subset of user activity (in some embodiments, the first graphical representation corresponds to multiple occurrences of the first subset of user activity (in some embodiments, all occurrences) (e.g., the first representation represents three occurrences of the walking activity type after dinner)), wherein: the first graphical representation is displayed in a first region (e.g., 6206) of the first user interface according to the determination (914) that the indication of the influence of the first subset of user activity on the first physiological parameter meets a first set of influence level criteria; and the first graphical representation is displayed in a second region (e.g., 6210) of the first user interface, different from the first region, according to the determination (916) that the indication of the influence of the first subset of user activity on the first physiological parameter meets a second set of influence level criteria different from the first set of influence criteria (in some embodiments, the second set of influence level criteria is met when the first set of influence level criteria is not met, and / or vice versa).

[0287] The first user interface includes a computer system display (918) of a second graphical representation (e.g., 6210a) of second data corresponding to a second subset of user activities, wherein: the second graphical representation is displayed in a first area of ​​the first user interface according to (920) the determination that the indication of the influence of the second subset of user activities on the first physiological parameter meets a first set of influence level criteria; and the second graphical representation is displayed in a second area of ​​the first user interface according to (922) the determination that the indication of the influence of the second subset of user activities on the first physiological parameter meets a second set of influence level criteria. The display of representations of user activities in different areas of the first user interface based on whether the indication of the influence of the activity on the first physiological parameter meets each set of criteria provides feedback to the user regarding the status of the data and the nature of the data (e.g., physiological data) accessed by the computer system. This also automatically organizes the user interface when conditions are met, without requiring further user input. Providing improved feedback and performing operations automatically enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when interacting with the operating system), which in turn reduces power consumption and extends the system's battery life by enabling the user to use the system more quickly and efficiently.

[0288] In some implementations, the first physiological parameter is (e.g., the blood glucose level of a user of a computer system); and the indication of the effect of a first subset of user activities on the first physiological parameter (e.g., 6206a4) is an indication of the effect of a first subset of user activities on glucose levels (e.g., abnormal glucose events, such as elevated (e.g., events with glucose levels above the normal and / or recommended range (e.g., above 125 mg / dL) and / or decreased (e.g., events with glucose levels below 70 mg / dL)) (e.g., the effect of a single instance of walking activity after dinner on blood glucose levels and / or the effect of whether an abnormal glucose event occurs relative to baseline and / or target).

[0289] In some implementations, the first subset of user activities is performing physical activities (e.g., exercising) (e.g., 6206a) or eating food or drinking beverages (e.g., 6210a) (e.g., eating).

[0290] In some implementations, the first data includes data corresponding to multiple indications of the impact of a first subset of user activities on a first physiological parameter (e.g., 6206a4 and 6206a5) (e.g., data including multiple occurrences / instances corresponding to the first subset of user activities) (e.g., the first data includes data corresponding to three instances of the walking activity type after dinner). Accessing the data including multiple indications of the impact of the first subset of user activities on the first physiological parameter provides the user with improved feedback regarding the impact of the first subset of user activities on the physiological parameter.

[0291] In some embodiments, the first graphical representation includes an indication of the effect of a first subset of user activities on a first physiological parameter (e.g., 6206a4) (e.g., graphical and / or textual indications) (in some embodiments, the indication is a quantitative and / or qualitative representation of the effect (in some embodiments, the indication represents a change from a baseline level (e.g., a baseline level of a physiological parameter (e.g., blood glucose)) and / or a baseline level of an event associated with the physiological parameter (e.g., an elevated blood glucose event)). In some embodiments, the first graphical representation includes multiple indications of the effects corresponding to multiple occurrences of the first subset of user activities (e.g., the first graphical representation includes three indications of the effects corresponding to three separate occurrences of the first subset of activities (e.g., three instances of a walking activity type after dinner)). Including an indication of the effect of a first subset of user activities on the first physiological parameter in the first graphical representation provides the user with improved visual feedback regarding the effect of the corresponding first subset of user activities.

[0292] In some embodiments, the first set of influence level criteria includes criteria (e.g., as described relative to region 6206) that are met when an indication of the influence of a first subset of user activities on a first physiological parameter indicates that the first subset of user activities provides an influence on the first physiological parameter exceeding a first threshold (e.g., the highest single measurement level of influence and / or the highest frequency of influence). In some embodiments, the first threshold is a relative threshold determined based on a complete set of accessed data (e.g., the highest single measurement level of influence and / or the highest frequency of influence within the accessed data). In some embodiments, the first threshold is a predetermined threshold established independently of the accessed data. In some embodiments, the accessed data includes multiple distinct subsets of user activities, where each subset is a different type of user activity (e.g., walking, jogging, running, swimming, strolling, eating a certain food, or avoiding eating a certain food after dinner), and the first set of influence level criteria corresponds to a certain percentile or group of the accessed data (e.g., corresponding to 1 / 3 of the data that has the highest and / or most frequent influence on the first physiological parameter). Arranging representations of user activities in different areas of the first user interface based on whether corresponding subsets of user activities provide an influence exceeding the threshold provides feedback to the user regarding improvements in the most influential subset of activities. This also automatically organizes the user interface based on the level of influence.

[0293] In some implementations, the second set of influence level criteria includes criteria that are met when an indication of the influence of a first subset of user activity on a first physiological parameter indicates that the first subset of user activity provides an influence on the first physiological parameter below a second threshold (e.g., as described relative to region 6208). In some implementations, the second threshold is a relative threshold determined based on a complete set of accessed data. In some implementations, the second threshold is a predetermined threshold established independently of the accessed data. In some implementations, the second threshold is equal to the first threshold. In some implementations, the second set of influence level criteria includes criteria that are met when an indication of the influence of a first subset of user activity on a first physiological parameter indicates that the first subset of user activity provides an influence on the first physiological parameter below a second threshold but above a third threshold (e.g., within the middle range of influence levels). Arranging representations of user activities in different areas of the first user interface based on whether corresponding subsets of user activities provide an influence below a threshold provides the user with improved feedback on the influence level of certain subsets of activities. Doing so also automatically organizes the user interface based on influence levels.

[0294] In some embodiments, displaying the first graphical representation includes: displaying the first graphical representation in a third region (e.g., 6210) of the first user interface, different from the first and second regions, based on the determination that the indication of the influence of a first subset of user activities on a first physiological parameter meets a third set of influence level criteria. In some embodiments, the third set of influence level criteria includes criteria that are met when the indication of the influence of the first subset of user activities on the first physiological parameter is a negative influence and / or an influence of a corresponding type (e.g., an increase corresponding to elevated blood glucose). Displaying the second graphical representation includes: displaying the second graphical representation in a third region of the first user interface, different from the first and second regions, based on the determination that the indication of the influence of a second subset of user activities on the first physiological parameter meets a third set of influence level criteria. Displaying representations of user activities in different regions of the first user interface based on whether the indication of the influence of activities on the first physiological parameter meets a third set of criteria provides the user with feedback on the status of the data and the nature of the data (e.g., physiological data) accessed by the computer system. Doing so also automatically organizes the user interface when conditions are met without requiring further user input. In some embodiments, displaying the first graphical representation includes: based on the determination of the highest level of influence on the first physiological parameter within a first group of occurrences of user activity corresponding to the indication of the influence of a first subset of user activity on the first physiological parameter, displaying a first graphical representation with an indicator of a first type (e.g., 6206a6) (e.g., a graphical badge and / or text indicating that the first subset of user activity has the highest level of influence). In some embodiments, the highest level of influence corresponds to the maximum reduction in the number of occurrences of elevated blood glucose (e.g., the number of occurrences relative to baseline values, reference values, and / or user-defined values) within a predetermined time period (e.g., evening or morning). Displaying the first graphical representation with the first type of indicator when certain conditions are met provides improved visual feedback on the relationship between the first subset of user activity and the overall first group of occurrences of user activity, and also automatically performs the function without requiring further user input.

[0295] In some embodiments, displaying the first graphical representation includes: based on the determination of the most frequent level of influence on the first physiological parameter within a first set of occurrences of user activity corresponding to the indication of the influence of a first subset of user activity on the first physiological parameter, displaying a first graphical representation with a second type of indicator (e.g., 6206b2) (e.g., a graphical badge and / or text indicating that the first subset of user activity has the highest level of influence) (in some embodiments, an indicator different from the first type of indicator). In some embodiments, the most frequent level of influence corresponds to the highest reduction in the number of occurrences of elevated blood glucose (e.g., the number of occurrences relative to baseline, reference, and / or user-defined values) within a predetermined time period (e.g., evening or morning). Displaying the first graphical representation with the second type of indicator when certain conditions are met provides improved visual feedback on the relationship between the first subset of user activity and the overall first set of occurrences of user activity, and also automatically performs the function without requiring further user input.

[0296] In some embodiments, the first graphical representation includes an indication of the difficulty level of a first subset of user activities (e.g., 6206a2) (e.g., graphical or textual indication) (in some embodiments, the difficulty level is a predetermined difficulty level assigned to the first subset of activities (e.g., assigned to activity type)) (in some embodiments, the difficulty level is a difficulty level selected / evaluated by the user). Displaying a first graphical representation with an indication of the difficulty level provides improved visual feedback on the difficulty of performing the first subset of user activities.

[0297] In some embodiments, the first user interface further includes: a first selectable graphical user interface object (e.g., 6202a) that, when selected, causes the computer system to display a second user interface corresponding to a first stage (e.g., an initial stage and / or a start stage) in an ordered sequence of stages of a multi-stage event (in some embodiments, corresponding to a stage for collecting initial baseline data of a first physiological parameter); and a second selectable graphical user interface object (e.g., 6202c) that, when selected, causes the computer system to display a third user interface corresponding to a second stage (e.g., an end stage) in an ordered sequence of stages of a multi-stage event (in some embodiments, corresponding to a stage for selecting and / or performing user activities after collecting baseline data), wherein the second stage follows the first stage.

[0298] In some implementations, the computer system receives first user input corresponding to a first graphical representation (e.g., input corresponding to the representation 6206a) via one or more input devices (e.g., touch or air gestures, mouse input, and / or keyboard input); and in response to the first user input, the computer system displays additional information not included in the first graphical representation, corresponding to a first subset of user activity (additional information about the execution of user activity and / or the effect of user activity on a first physiological parameter). Displaying additional information corresponding to the first subset of user activity in response to input provides additional information and feedback when requested, without cluttering the first user interface when additional information is not required.

[0299] In some implementations, the first representation corresponds to multiple occurrences of a first subset of user activities (e.g., according to representation 6206a) (e.g., three instances of a walk after dinner); and the additional information includes additional information for each of the multiple occurrences of the first subset of user activities. Displaying additional information corresponding to the multiple occurrences of the first subset of user activities in response to input provides additional information and feedback when requested, without cluttering the first user interface when the additional information is not required.

[0300] It should be noted that the above is relative to method 900 (e.g., Figure 9 The details of the process described also apply in a similar manner to the methods described above. For example, method 900 may optionally include one or more features of the various methods described above with reference to methods 700 and 800. For example, the toolbox user interface of method 900 may display activities logged using method 800. For the sake of brevity, these details will not be repeated below.

[0301] For purposes of explanation, the foregoing description has been given by reference to specific embodiments. However, the illustrative discussion above is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible based on the teachings above. These embodiments were chosen and described in order to best explain the principles of these techniques and their practical application. Others skilled in the art will thus be able to best utilize these techniques and the various embodiments with various modifications suitable for the particular intended use.

[0302] While this 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 this disclosure and examples as defined by the claims.

[0303] As described above, one aspect of the present invention involves collecting and using data from various sources to improve the delivery of user activity or any other content that may be of interest to users during a subset of a cyclical time period. This disclosure contemplates that, in some instances, such collected data may include personal information data that uniquely identifies or can be used to contact or locate specific individuals. This personal information data may include demographic data, location-based data, telephone numbers, email addresses, Twitter IDs, home addresses, data or records relating to a 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.

[0304] This disclosure recognizes that the use of such personal information data in the techniques of this invention can benefit users. For example, personal information data can be used to deliver targeted content based on user activity logged during a subset of cyclical time periods of greater interest to the user. Therefore, the use of such personal information data enables users to have planned control over the delivered content. Furthermore, this disclosure envisions other uses for personal information data that benefit users. For example, health and fitness data can be used to provide insights into a user's overall health status or can be used as positive feedback for individuals using the technology to pursue health goals.

[0305] This disclosure anticipates that entities responsible for the collection, analysis, disclosure, transmission, storage, or other use of such personal information data will comply with robust privacy policies and / or privacy measures. Specifically, such entities should implement and adhere to privacy policies and measures that are recognized as meeting or exceeding industry or governmental 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 entity purposes and should not be shared or sold outside of these legitimate purposes. Furthermore, such collection / sharing should be conducted only after receiving informed consent from users. Additionally, such entities should consider taking any necessary steps to protect and safeguard the right to access such personal information data and ensure that other entities with access to personal information data comply with the privacy policies and procedures of other entities. Furthermore, such entities may subject themselves to third-party assessments to demonstrate their compliance with widely accepted privacy policies and measures. Moreover, policies and measures should be adapted to the specific types of personal information data collected and / or accessed, and to applicable laws and standards, including considerations of specific jurisdictions. For example, in the United States, the collection or acquisition of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); while in other countries, health data may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be advocated for different types of personal data in each country.

[0306] Regardless of the foregoing, this disclosure also contemplates implementation schemes for users to selectively block the use or access to personal information data. That is, this disclosure contemplates providing hardware and / or software components to prevent or block access to such personal information data. For example, in relation to organizing user activity, the inventive technology can be configured to allow users to opt-in or opt-out at any time during or after service registration to participate in the collection of personal information data. In another example, users may choose not to provide data for organizing user activity. In yet another example, users may choose to limit the length of time data is retained or completely prohibit the development of baseline profiles. In addition to providing opt-in and opt-out options, this disclosure also contemplates providing notifications related to access to or use of personal information. For example, users may be notified when downloading an application that their personal information data will be accessed, and then reminded again just before the application accesses the personal information data.

[0307] Furthermore, the intent of this disclosure is that personal information data should be managed and processed in a manner that minimizes the risk of unintentional or unauthorized access or use. Once data is no longer needed, this risk can be minimized by restricting data collection and deleting data. Additionally, and where applicable, including in certain health-related applications, data deidentification can be used to protect user privacy. Deidentification can be facilitated, where appropriate, 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 the address level), controlling how data is stored (e.g., aggregating data among users), and / or other methods.

[0308] Therefore, while this disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, it also contemplates that various embodiments can be implemented without access to such personal information data. That is, various embodiments of this technology will not become inoperable due to the absence of all or part of such personal information data. For example, preferences can be inferred based on non-personal information data or a minimal amount of personal information such as content requested by a device associated with a user, other non-personal information available to the content delivery service, or publicly available information, thereby selecting content and delivering it to the user. Claims (as amended under Article 19 of the Treaty) 1. A method, the method comprising: At the computer system that communicates with the display generation components and one or more input devices: Access the first set of data that occurred, corresponding to an instance of log recordings related to user activity, the data including: First data, comprising an indication of the impact of a first subset of user activity on a first physiological parameter; and The second data includes an indication of the impact of a second subset of user activities on the first physiological parameter; Receive a request to display a first user interface via the one or more input devices; and In response to receiving the request to display the first user interface, displaying the first user interface via the display generation component includes: A first graphical representation of the first data corresponding to the first subset of user activity is displayed, wherein: Based on the indication that the influence of the first subset of user activities on the first physiological parameter meets a first set of influence level criteria, the first graphical representation is displayed in a first area of ​​the first user interface; and Based on the indication that the first subset of user activity's influence on the first physiological parameter meets a second set of influence level criteria different from the first set of influence criteria, the first graphical representation is displayed in a second region of the first user interface, different from the first region; and A second graphical representation of the second data corresponding to the second subset of user activity is displayed, wherein: Based on the indication that the influence of the second subset of user activities on the first physiological parameter meets the first set of influence level criteria, the second graphical representation is displayed in the first area of ​​the first user interface; and The second graphical representation is displayed in a second area of ​​the first user interface based on the indication that the influence of the second subset of user activities on the first physiological parameter meets the second set of influence level criteria. 2. The method according to claim 1, wherein: The first physiological parameter is blood glucose level; and The indication of the effect of the first subset of user activity on the first physiological parameter is an indication of the effect of the first subset of user activity on glucose levels. 3. The method according to any one of claims 1 to 2, wherein the first subset of user activities is performing physical activities or consuming food or drinking beverages. 4. The method according to any one of claims 1 to 3, wherein: The first data includes multiple indications corresponding to the effect of the first subset of user activities on the first physiological parameter. 5. The method according to any one of claims 1 to 4, wherein: The first graphical representation includes an indication of the effect of a first subset of user activities on the first physiological parameter. 6. The method according to any one of claims 1 to 5, wherein the first set of influence level criteria includes criteria satisfied when the indication of the influence of the first subset of user activities on the first physiological parameter indicates that the first subset of user activities has an influence on the first physiological parameter exceeding a first threshold. 7. The method according to any one of claims 1 to 6, wherein the second set of influence level criteria includes criteria satisfied when the indication of the influence of the first subset of user activities on the first physiological parameter indicates that the first subset of user activities has an influence on the first physiological parameter below a second threshold. 8. The method according to any one of claims 1 to 7, wherein: The first graphic representation includes: Based on the indication that the first subset of user activity's influence on the first physiological parameter meets a third set of influence level criteria, the first graphical representation is displayed in a third region of the first user interface, distinct from the first and second regions; and The second graphic representation includes: The second graphical representation is displayed in a third region of the first user interface, which is different from the first and second regions, based on the indication that the second subset of user activity has an impact on the first physiological parameter and meets the third set of impact level criteria. 9. The method according to any one of claims 1 to 8, wherein: The first graphic representation includes: The first graphical representation with a first type of indicator is displayed based on the indication that determines the influence of the first subset of user activities on the first physiological parameter, which corresponds to the highest level of influence on the first physiological parameter within the first group of occurrences of user activities. 10. The method according to any one of claims 1 to 9, wherein: The first graphic representation includes: The first graphical representation with a second type of indicator is displayed based on the indication that determines the influence of the first subset of user activities on the first physiological parameter, which corresponds to the most frequent level of influence on the first physiological parameter within the first group of occurrences of user activities. 11. The method according to any one of claims 1 to 10, wherein the first graphical representation includes an indication of the difficulty level of the first subset of user activities. 12. The method according to any one of claims 1 to 11, wherein the first user interface further comprises: A first selectable graphical user interface object, when selected, causes the computer system to display a second user interface corresponding to a first stage in an ordered sequence of stages of a multi-stage event; and A second selectable graphical user interface object, when selected, causes the computer system to display a third user interface corresponding to a second stage in the ordered sequence of stages of the multi-stage event, wherein the second stage follows the first stage. 13. The method according to any one of claims 1 to 12, further comprising: Receive first user input corresponding to the first graphical representation via the one or more input devices; and In response to the first user input, additional information that was not included in the first graphical representation and corresponds to the first subset of user activity is displayed. 14. The method of claim 13, wherein: The first graph represents multiple occurrences corresponding to the first subset of user activities; and The additional information includes additional information for each of the multiple occurrences of the first subset of user activities. 15. 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 and one or more input devices, the one or more programs including instructions fo...

Claims

1. A method, the method comprising: At the computer system that communicates with the display generation components and one or more input devices: Access the first set of data that occurred corresponding to the user activity, said data including: First data, comprising an indication of the impact of a first subset of user activity on a first physiological parameter; and The second data includes an indication of the impact of a second subset of user activities on the first physiological parameter; Receive a request to display a first user interface via the one or more input devices; and In response to receiving the request to display the first user interface, displaying the first user interface via the display generation component includes: A first graphical representation of the first data corresponding to the first subset of user activity is displayed, wherein: Based on the indication that the influence of the first subset of user activities on the first physiological parameter meets a first set of influence level criteria, the first graphical representation is displayed in a first area of ​​the first user interface; and Based on the indication that the first subset of user activity's influence on the first physiological parameter meets a second set of influence level criteria different from the first set of influence criteria, the first graphical representation is displayed in a second region of the first user interface, different from the first region; and A second graphical representation of the second data corresponding to the second subset of user activity is displayed, wherein: Based on the indication that the influence of the second subset of user activities on the first physiological parameter meets the first set of influence level criteria, the second graphical representation is displayed in the first area of ​​the first user interface; and The second graphical representation is displayed in a second area of ​​the first user interface based on the indication that the second subset of user activities affects the first physiological parameter and that the second set of influence level criteria is satisfied.

2. The method according to claim 1, wherein: The first physiological parameter is blood glucose level; and The indication of the effect of the first subset of user activity on the first physiological parameter is an indication of the effect of the first subset of user activity on glucose levels.

3. The method according to any one of claims 1 to 2, wherein the first subset of user activities is performing physical activities or consuming food or drinking beverages.

4. The method according to any one of claims 1 to 3, wherein: The first data includes multiple indications corresponding to the effect of the first subset of user activities on the first physiological parameter.

5. The method according to any one of claims 1 to 4, wherein: The first graphical representation includes an indication of the effect of a first subset of user activities on the first physiological parameter.

6. The method according to any one of claims 1 to 5, wherein the first set of influence level criteria includes criteria satisfied when the indication of the influence of the first subset of user activities on the first physiological parameter indicates that the first subset of user activities has an influence on the first physiological parameter exceeding a first threshold.

7. The method according to any one of claims 1 to 6, wherein the second set of influence level criteria includes criteria satisfied when the indication of the influence of the first subset of user activities on the first physiological parameter indicates that the first subset of user activities has an influence on the first physiological parameter below a second threshold.

8. The method according to any one of claims 1 to 7, wherein: The first graphic representation includes: Based on the indication that the first subset of user activity's influence on the first physiological parameter meets a third set of influence level criteria, the first graphical representation is displayed in a third region of the first user interface, distinct from the first and second regions; and The second graphic representation includes: The second graphical representation is displayed in a third region of the first user interface, which is different from the first and second regions, based on the indication that the second subset of user activity has an impact on the first physiological parameter and meets the third set of impact level criteria.

9. The method according to any one of claims 1 to 8, wherein: The first graphic representation includes: The first graphical representation with a first type of indicator is displayed based on the indication that determines the influence of the first subset of user activities on the first physiological parameter, which corresponds to the highest level of influence on the first physiological parameter within the first group of occurrences of user activities.

10. The method according to any one of claims 1 to 9, wherein: The first graphic representation includes: The first graphical representation with a second type of indicator is displayed based on the indication that determines the influence of the first subset of user activities on the first physiological parameter, which corresponds to the most frequent level of influence on the first physiological parameter within the first group of occurrences of user activities.

11. The method according to any one of claims 1 to 10, wherein the first graphical representation includes an indication of the difficulty level of the first subset of user activities.

12. The method according to any one of claims 1 to 11, wherein the first user interface further comprises: A first selectable graphical user interface object, when selected, causes the computer system to display a second user interface corresponding to a first stage in an ordered sequence of stages of a multi-stage event. and A second selectable graphical user interface object, when selected, causes the computer system to display a third user interface corresponding to a second stage in the ordered sequence of stages of the multi-stage event, wherein the second stage follows the first stage.

13. The method according to any one of claims 1 to 12, further comprising: Receive first user input corresponding to the first graphical representation via the one or more input devices; as well as In response to the first user input, additional information that was not included in the first graphical representation and corresponds to the first subset of user activity is displayed.

14. The method of claim 13, wherein: The first graph represents multiple occurrences corresponding to the first subset of user activities; and The additional information includes additional information for each of the multiple occurrences of the first subset of user activities.

15. 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 and one or more input devices, the one or more programs including instructions for performing the method according to any one of claims 1 to 14.

16. A computer system configured to communicate with a display generation component and one or more input devices, 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 method according to any one of claims 1 to 14.

17. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: Components for performing the method according to any one of claims 1 to 14.

18. A computer program product comprising 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 comprising instructions for performing the method according to any one of claims 1 to 14.

19. 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 and one or more input devices, the one or more programs comprising instructions for: Access the first set of data that occurred corresponding to the user activity, said data including: The first data includes an indication of the impact of a first subset of user activities on a first physiological parameter; and The second data includes an indication of the impact of a second subset of user activities on the first physiological parameter; Receive a request to display a first user interface via the one or more input devices; as well as In response to receiving the request to display the first user interface, displaying the first user interface via the display generation component includes: A first graphical representation of the first data corresponding to the first subset of user activity is displayed, wherein: Based on the indication that the influence of the first subset of user activities on the first physiological parameter meets a first set of influence level criteria, the first graphical representation is displayed in a first area of ​​the first user interface; and Based on the indication that the first subset of user activity's influence on the first physiological parameter meets a second set of influence level criteria different from the first set of influence criteria, the first graphical representation is displayed in a second region of the first user interface, different from the first region; and A second graphical representation of the second data corresponding to the second subset of user activity is displayed, wherein: Based on the indication that the influence of the second subset of user activities on the first physiological parameter meets the first set of influence level criteria, the second graphical representation is displayed in the first area of ​​the first user interface; and The second graphical representation is displayed in a second area of ​​the first user interface based on the indication that the second subset of user activities affects the first physiological parameter and that the second set of influence level criteria is satisfied.

20. A computer system configured to communicate with a display generation component and one or more input devices, 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: Access the first set of data that occurred corresponding to the user activity, said data including: First data, comprising an indication of the impact of a first subset of user activity on a first physiological parameter; and The second data includes an indication of the impact of a second subset of user activities on the first physiological parameter; Receive a request to display a first user interface via the one or more input devices; and In response to receiving the request to display the first user interface, displaying the first user interface via the display generation component includes: A first graphical representation of the first data corresponding to the first subset of user activity is displayed, wherein: Based on the indication that the influence of the first subset of user activities on the first physiological parameter meets a first set of influence level criteria, the first graphical representation is displayed in a first area of ​​the first user interface; and Based on the indication that the first subset of user activity's influence on the first physiological parameter meets a second set of influence level criteria different from the first set of influence criteria, the first graphical representation is displayed in a second region of the first user interface, different from the first region; and A second graphical representation of the second data corresponding to the second subset of user activity is displayed, wherein: Based on the indication that the influence of the second subset of user activities on the first physiological parameter meets the first set of influence level criteria, the second graphical representation is displayed in the first area of ​​the first user interface; and The second graphical representation is displayed in a second area of ​​the first user interface based on the indication that the second subset of user activities affects the first physiological parameter and that the second set of influence level criteria is satisfied.

21. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: A component for accessing data corresponding to a first set of occurrences in user activity, the data including: First data, comprising an indication of the impact of a first subset of user activity on a first physiological parameter; and The second data includes an indication of the impact of a second subset of user activities on the first physiological parameter; A component for receiving a request to display a first user interface via the one or more input devices; and A component for displaying the first user interface via the display generation component in response to receiving a request to display the first user interface includes: A component for displaying a first graphical representation of the first data corresponding to the first subset of user activity, wherein: Based on the indication that the influence of the first subset of user activities on the first physiological parameter meets a first set of influence level criteria, the first graphical representation is displayed in a first area of ​​the first user interface; and Based on the indication that the first subset of user activity's influence on the first physiological parameter meets a second set of influence level criteria different from the first set of influence criteria, the first graphical representation is displayed in a second region of the first user interface, different from the first region; and A component for displaying a second graphical representation of the second data corresponding to the second subset of user activity, wherein: Based on the indication that the influence of the second subset of user activities on the first physiological parameter meets the first set of influence level criteria, the second graphical representation is displayed in the first area of ​​the first user interface; and The second graphical representation is displayed in a second area of ​​the first user interface based on the indication that the second subset of user activities affects the first physiological parameter and that the second set of influence level criteria is satisfied.

22. A computer program product comprising 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 comprising instructions for: Access the first set of data that occurred corresponding to the user activity, said data including: The first data includes an indication of the impact of a first subset of user activities on a first physiological parameter; and The second data includes an indication of the impact of a second subset of user activities on the first physiological parameter; Receive a request to display a first user interface via the one or more input devices; as well as In response to receiving the request to display the first user interface, displaying the first user interface via the display generation component includes: A first graphical representation of the first data corresponding to the first subset of user activity is displayed, wherein: Based on the indication that the influence of the first subset of user activities on the first physiological parameter meets a first set of influence level criteria, the first graphical representation is displayed in a first area of ​​the first user interface; and Based on the indication that the first subset of user activity's influence on the first physiological parameter meets a second set of influence level criteria different from the first set of influence criteria, the first graphical representation is displayed in a second region of the first user interface, different from the first region; and A second graphical representation of the second data corresponding to the second subset of user activity is displayed, wherein: Based on the indication that the influence of the second subset of user activities on the first physiological parameter meets the first set of influence level criteria, the second graphical representation is displayed in the first area of ​​the first user interface; and The second graphical representation is displayed in a second area of ​​the first user interface based on the indication that the second subset of user activities affects the first physiological parameter and that the second set of influence level criteria is satisfied.

Images