User interface for health application

Abstract

To provide a user interface for a health application where exemplary user interfaces are explained for managing the health and safety features on an electrotonic device.SOLUTION: An exemplary user interface is explained for managing the setup of a health function on an electronic device. The exemplary user interface is explained for managing background health measurements on an electronic device in several embodiments. The exemplary user interface is explained for managing biometric measurements used by the electronic device in several embodiments. The exemplary user interface is explained for providing the result of health information captured on the electronic device in several embodiments. The exemplary user interface is explained for managing the background health measurements on the electronic device in several embodiments.SELECTED DRAWING: Figure 6A

Description

[Technical Field]

[0001] The present disclosure relates generally to computer user interfaces, and more particularly to techniques for managing and / or presenting health data. [Background technology]

[0002] Using health applications on electronic devices to measure and manage health information is a convenient and effective way to provide and maintain awareness of one's health. Electronic devices allow users to quickly and easily capture, manage, and monitor health information. Summary of the Invention

[0003] Some techniques for managing health data using electronic devices are generally cumbersome and inefficient. For example, some techniques use complex and time-consuming user interfaces that may involve multiple key presses or strokes. Such techniques take more time than necessary and waste the user's time and the device's energy. The latter problem is particularly acute in battery-operated devices.

[0004] Thus, the present technology provides electronic devices with faster, more efficient methods and interfaces for managing and / or presenting health data. Such methods and interfaces optionally complement or replace other methods for managing and / or presenting health data. Such methods and interfaces reduce the cognitive burden on users and create a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges. Such methods and interfaces also allow users to quickly and easily capture health information, thereby motivating users to frequently monitor their health. Such methods and interfaces also allow users to conveniently view and manage recorded health information, thereby increasing users' awareness of their current health status.

[0005] According to some embodiments, a method is described that is executed on a computer system in communication with a display generation component and one or more input devices. The method includes displaying, via the display generation component, a user interface that includes a plurality of user interface objects corresponding to health-related features, the plurality of user interface objects including a first user interface object corresponding to a first health-related feature, the first user interface object including: an indication that the first health-related feature is active in accordance with a determination that the first health-related feature is currently active; an indication that the first health-related feature is available for activation in accordance with a determination that the first health-related feature is currently inactive and available for activation via a set of one or more inputs received at the computer system; and an indication that the first health-related feature is not available for activation in accordance with a determination that the first health-related feature is currently inactive and not available for activation.

[0006] According to some embodiments, 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 is described. The one or more programs include instructions for displaying, via the display generation component, a user interface including a plurality of user interface objects corresponding to health-related features, the plurality of user interface objects including a first user interface object corresponding to a first health-related feature, the first user interface object including: an indication that the first health-related feature is active in accordance with a determination that the first health-related feature is currently active; an indication that the first health-related feature is available for activation in accordance with a determination that the first health-related feature is currently inactive and available for activation via a set of one or more inputs received at the computer system; and an indication that the first health-related feature is not available for activation in accordance with a determination that the first health-related feature is currently inactive and not available for activation.

[0007] According to some embodiments, a 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 is described. The one or more programs include instructions for displaying, via the display generation component, a user interface including a plurality of user interface objects corresponding to health-related features, the plurality of user interface objects including a first user interface object corresponding to a first health-related feature, the first user interface object including: an indication that the first health-related feature is active in accordance with a determination that the first health-related feature is currently active; an indication that the first health-related feature is available for activation in accordance with a determination that the first health-related feature is currently inactive and available for activation via a set of one or more inputs received at the computer system; and an indication that the first health-related feature is not available for activation in accordance with a determination that the first health-related feature is currently inactive and not available for activation.

[0008] According to some embodiments, a computer system is described that includes a display generation component, one or more input devices, one or more processors, and a memory that stores 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 user interface including a plurality of user interface objects corresponding to health-related features, the plurality of user interface objects including a first user interface object corresponding to a first health-related feature, the first user interface object including: an indication that the first health-related feature is active in accordance with a determination that the first health-related feature is currently active; an indication that the first health-related feature is available for activation in accordance with a determination that the first health-related feature is currently inactive and available for activation via a set of one or more inputs received at the computer system; and an indication that the first health-related feature is not available for activation in accordance with a determination that the first health-related feature is currently inactive and not available for activation.

[0009] According to some embodiments, a computer system is described that includes a display generation component, one or more input devices, and means for displaying, via the display generation component, a user interface including a plurality of user interface objects corresponding to health-related features, the plurality of user interface objects including a first user interface object corresponding to a first health-related feature, the first user interface object including: an indication that the first health-related feature is active in accordance with a determination that the first health-related feature is currently active; an indication that the first health-related feature is available for activation in accordance with a determination that the first health-related feature is currently inactive and available for activation via a set of one or more inputs received at the computer system; and an indication that the first health-related feature is not available for activation in accordance with a determination that the first health-related feature is currently inactive and not available for activation.

[0010] According to some embodiments, a method is described that is executed on a computer system in communication with a display generation component and one or more input devices. The method includes displaying, via the display generation component, a set of one or more user interfaces corresponding to a first health-related feature, where the first health-related feature is currently inactive, and pursuant to a determination that a set of activation permission criteria is met, the set of one or more user interfaces corresponding to the first health-related feature, including location-based criteria that are met when a current location of the computer system satisfies the set of location-based criteria, displaying a first activation user interface of the set of one or more activation user interfaces, the first activation user interface set including a first selectable user interface object that activates the first health-related feature when selected via input received via the one or more input devices, and pursuant to a determination that the set of activation permission criteria is not met, displaying a notification interface that includes first information corresponding to the first health-related feature and that does not include a selectable user interface object that activates the first health-related feature when selected via input received via the one or more input devices.

[0011] According to some embodiments, 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 is described, the one or more programs including instructions for displaying, via the display generation component, a set of one or more user interfaces corresponding to a first health-related function, where the first health-related function is currently inactive, displaying the set of one or more user interfaces corresponding to the first health-related function includes: pursuant to a determination that a set of activation permission criteria are met, the set including location-based criteria that are met when a current location of the computer system satisfies the set of location-based criteria, displaying a first activation user interface of the set of one or more activation user interfaces, the first activation user interface set including a first selectable user interface object that, when selected via input received via the one or more input devices, activates the first health-related function; and pursuant to a determination that the set of activation permission criteria are not met, displaying a notification interface that includes first information corresponding to the first health-related function and that does not include a selectable user interface object that, when selected via input received via the one or more input devices, activates the first health-related function.

[0012] According to some embodiments, a 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 is described, the one or more programs including instructions for displaying, via the display generation component, a set of one or more user interfaces corresponding to a first health-related function, where the first health-related function is currently inactive, displaying the set of one or more user interfaces corresponding to the first health-related function includes: pursuant to a determination that a set of activation permission criteria are met, the set including location-based criteria that are met when a current location of the computer system satisfies the set of location-based criteria, displaying a first activation user interface of the set of one or more activation user interfaces, the first activation user interface set including a first selectable user interface object that, when selected via input received via the one or more input devices, activates the first health-related function; and pursuant to a determination that the set of activation permission criteria are not met, displaying a notification interface that includes first information corresponding to the first health-related function and that does not include a selectable user interface object that, when selected via input received via the one or more input devices, activates the first health-related function.

[0013] According to some embodiments, a computer system is described that 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 set of one or more user interfaces corresponding to a first health-related function, where the first health-related function is currently inactive, and displaying the set of one or more user interfaces corresponding to the first health-related function includes: pursuant to a determination that a set of activation permission criteria are met, the set of activation permission criteria including location-based criteria that are met when a current location of the computer system satisfies the set of location-based criteria, displaying a first activation user interface of the set of one or more activation user interfaces, the first activation user interface set including a first selectable user interface object that activates the first health-related function when selected via input received via the one or more input devices; and pursuant to a determination that the set of activation permission criteria are not met, displaying a notification interface that includes first information corresponding to the first health-related function and that does not include a selectable user interface object that activates the first health-related function when selected via input received via the one or more input devices.

[0014] According to some embodiments, a computer system is described that includes a display generation component, one or more input devices, and means for displaying, via the display generation component, a set of one or more user interfaces corresponding to a first health-related feature, wherein the first health-related feature is currently inactive, and displaying the set of one or more user interfaces corresponding to the first health-related feature includes: pursuant to a determination that a set of activation permission criteria are met, the set including location-based criteria that are met when a current location of the computer system satisfies the set of location-based criteria, displaying a first activation user interface of the set of one or more activation user interfaces, the first set of activation user interfaces including a first selectable user interface object that, when selected via input received via the one or more input devices, activates the first health-related feature; and pursuant to a determination that the set of activation permission criteria are not met, displaying a notification interface that includes first information corresponding to the first health-related feature and that does not include a selectable user interface object that, when selected via input received via the one or more input devices, activates the first health-related feature.

[0015] According to some embodiments, a method is described that is executed on a computer system in communication with a display generation component and one or more input devices. The method includes displaying, via the display generation component, a first configuration user interface of a set of one or more configuration user interfaces for a first health-related tracking function currently configured to track a first set of health-related data while the computer system is in a first mode and a second mode different from the first mode, the first configuration user interface including a first selectable user interface object, and receiving a set of one or more inputs, the set of one or more inputs including inputs corresponding to the first selectable user interface object, and configuring the first health-related tracking function to not track the first set of health-related data while the computer system is in the first mode while tracking the first set of health-related data while the computer system is in the second mode, in response to the set of one or more inputs.

[0016] According to some embodiments, 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 is described, the one or more programs including: displaying, via the display generation component, a first configuration user interface of a set of one or more configuration user interfaces for a first health-related tracking function currently configured to track a first set of health-related data while the computer system is in a first mode and a second mode different from the first mode, the first configuration user interface including a first selectable user interface object; and receiving a set of one or more inputs, the set of one or more inputs including inputs corresponding to the first selectable user interface object; and configuring, in response to the set of one or more inputs, the first health-related tracking function to not track the first set of health-related data while the computer system is in the first mode while tracking the first set of health-related data while the computer system is in the second mode.

[0017] According to some embodiments, a 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 is described, the one or more programs including: displaying, via the display generation component, a first configuration user interface of a set of one or more configuration user interfaces for a first health-related tracking function currently configured to track a first set of health-related data while the computer system is in a first mode and a second mode different from the first mode, the first configuration user interface including a first selectable user interface object; and receiving a set of one or more inputs, the set of one or more inputs including inputs corresponding to the first selectable user interface object; and configuring, in response to the set of one or more inputs, the first health-related tracking function to not track the first set of health-related data while the computer system is in the first mode while tracking the first set of health-related data while the computer system is in the second mode.

[0018] According to some embodiments, a computer system is described that includes a display generation component, one or more input devices, one or more processors, and a memory that stores one or more programs configured to be executed by the one or more processors. The one or more programs include: displaying, via the display generation component, a first configuration user interface of a set of one or more configuration user interfaces for a first health-related tracking function currently configured to track a first set of health-related data while the computer system is in a first mode and a second mode different from the first mode, the first configuration user interface including a first selectable user interface object; and receiving a set of one or more inputs, the set of one or more inputs including inputs corresponding to the first selectable user interface object; and configuring, in response to the set of one or more inputs, the first health-related tracking function to not track the first set of health-related data while the computer system is in the first mode while tracking the first set of health-related data while the computer system is in the second mode.

[0019] According to some embodiments, a computer system is described that includes: a display generation component; one or more input devices; means for displaying, via the display generation component, a first configuration user interface of a set of one or more configuration user interfaces for a first health-related tracking function, the first configuration user interface including a first selectable user interface object, the first health-related tracking function currently configured to track a first set of health-related data while the computer system is in a first mode and a second mode different from the first mode, and for receiving one or more set of inputs, the one or more set of inputs including inputs corresponding to the first selectable user interface object; and means for configuring the first health-related tracking function to not track the first set of health-related data while the computer system is in the second mode, in response to the one or more set of inputs.

[0020] According to some embodiments, a method is described that is executed on a display generation component, a set of one or more biometric sensors, and a computer system in communication with the set of one or more sensors. The method includes initiating a biometric analysis process that includes detecting first biometric data via the one or more biometric sensors, detecting the first set of sensor data via the set of one or more sensors during the biometric analysis process, and stopping the biometric analysis process in response to detecting the first set of sensor data following a determination that the first set of sensor data meets a stopping criterion for the first set.

[0021] According to some embodiments, 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, a set of one or more biometric sensors, and the set of one or more sensors is described, wherein the one or more programs include initiating a biometric analysis process including detecting first biometric data via the one or more biometric sensors, detecting the first set of sensor data via the set of one or more sensors during the biometric analysis process, and stopping the biometric analysis process in response to detecting the first set of sensor data and pursuant to a determination that the first set of sensor data satisfies a stopping criterion for the first set.

[0022] According to some embodiments, a 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, a set of one or more biometric sensors, and the set of one or more sensors is described, wherein the one or more programs include initiating a biometric analysis process including detecting first biometric data via the one or more biometric sensors, detecting the first set of sensor data via the set of one or more sensors during the biometric analysis process, and stopping the biometric analysis process in response to detecting the first set of sensor data and pursuant to a determination that the first set of sensor data satisfies a stopping criterion for the first set.

[0023] According to some embodiments, a computer system is described that includes a display generation component, a set of one or more biometric sensors, a set of one or more sensors, 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 initiating a biometric analysis process that includes detecting first biometric data via the one or more biometric sensors, detecting the first set of sensor data via the set of one or more sensors during the biometric analysis process, and stopping the biometric analysis process in response to detecting the first set of sensor data and pursuant to a determination that the first set of sensor data satisfies a stopping criterion for the first set.

[0024] According to some embodiments, a computer system is described that includes a display generation component, a set of one or more biometric sensors, means for initiating a biometric analysis process that includes detecting first biometric data via the set of one or more sensors, and means for detecting the first set of sensor data via the set of one or more sensors during the biometric analysis process, and means for stopping the biometric analysis process in response to detecting the first set of sensor data and pursuant to a determination that the first set of sensor data satisfies a stopping criterion for the first set.

[0025] According to some embodiments, a method is described that is executed on a computer system in communication with a display generation component and one or more input devices. The method includes displaying, via the display generation component, a summary user interface for a first health-related tracking feature, the summary user interface including a collection of one or more user interface objects corresponding to tracking data collected by the first health-related tracking feature, the collection of one or more user interface objects including a first user interface object corresponding to first data collected via the first health-related tracking feature, and displaying the summary user interface includes, pursuant to determining that the first data was collected under one or more conditions of a first type, displaying the first user interface object with an indication that at least a portion of the tracking data collected by the first health-related tracking feature was collected under one or more conditions of the first type.

[0026] According to some embodiments, 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 is described. The one or more programs include instructions for displaying, via the display generation component, a summary user interface of a first health-related tracking feature, the summary user interface including a collection of one or more user interface objects corresponding to tracking data collected by the first health-related tracking feature, the collection of one or more user interface objects including a first user interface object corresponding to first data collected via the first health-related tracking feature. Displaying the summary user interface includes, pursuant to a determination that the first data was collected under one or more conditions of a first type, displaying the first user interface object with an indication that at least a portion of the tracking data collected by the first health-related tracking feature was collected under one or more conditions of the first type.

[0027] According to some embodiments, a 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 is described. The one or more programs include instructions for displaying, via the display generation component, a summary user interface of a first health-related tracking feature, the summary user interface including a collection of one or more user interface objects corresponding to tracking data collected by the first health-related tracking feature, the collection of one or more user interface objects including a first user interface object corresponding to first data collected via the first health-related tracking feature. Displaying the summary user interface includes, pursuant to a determination that the first data was collected under one or more conditions of a first type, displaying the first user interface object with an indication that at least a portion of the tracking data collected by the first health-related tracking feature was collected under one or more conditions of the first type.

[0028] According to some embodiments, a computer system is described that includes a display generation component, one or more input devices, one or more processors, and a memory that stores 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 summary user interface of a first health-related tracking feature, the summary user interface including a collection of one or more user interface objects corresponding to tracking data collected by the first health-related tracking feature, the collection of one or more user interface objects including a first user interface object corresponding to first data collected via the first health-related tracking feature. Displaying the summary user interface includes, pursuant to a determination that the first data was collected under one or more conditions of a first type, displaying the first user interface object with an indication that at least a portion of the tracking data collected by the first health-related tracking feature was collected under one or more conditions of the first type.

[0029] According to some embodiments, a computer system is described that includes a display generation component, one or more input devices, and means for displaying, via the display generation component, a summary user interface of a first health-related tracking feature, the summary user interface including a collection of one or more user interface objects corresponding to tracking data collected by the first health-related tracking feature, the collection of one or more user interface objects including a first user interface object corresponding to first data collected via the first health-related tracking feature, and displaying the summary user interface includes, pursuant to determining that the first data was collected under one or more conditions of a first type, displaying the first user interface object with an indication that at least a portion of the tracking data collected by the first health-related tracking feature was collected under one or more conditions of the first type.

[0030] According to some embodiments, a method is described that is executed in a computer system in communication with a set of one or more biometric sensors, the method including detecting that a first set of health metrics are met, measuring values ​​of biometric parameters via the set of one or more biometric sensors in response to detecting that the set of health metrics are met in accordance with a determination that the computer system is in a first mode, and discontinuing measuring the biometric parameters in accordance with a determination that the computer system is in a second mode different from the first mode.

[0031] According to some embodiments, 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 set of one or more biometric sensors is described, wherein the one or more programs include instructions to detect that a first set of health metrics are met, measure values ​​of biometric parameters via the set of one or more biometric sensors in response to detecting that the set of health metrics are met in accordance with a determination that the computer system is in a first mode, and discontinue measuring the biometric parameters in accordance with a determination that the computer system is in a second mode different from the first mode.

[0032] According to some embodiments, a 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 set of one or more biometric sensors is described, wherein the one or more programs include instructions to detect that a first set of health metrics are met, measure values ​​of biometric parameters via the set of one or more biometric sensors in response to detecting that the set of health metrics are met in accordance with a determination that the computer system is in a first mode, and discontinue measuring the biometric parameters in accordance with a determination that the computer system is in a second mode different from the first mode.

[0033] According to some embodiments, a computer system is described that includes a set of one or more biometric sensors, one or more processors, and a memory that stores one or more programs configured to be executed by the one or more processors, the one or more programs including instructions to detect that a first set of health metrics is met, measure values ​​of biometric parameters via the set of one or more biometric sensors in response to detecting that the set of health metrics is met in accordance with a determination that the computer system is in a first mode, and discontinue measuring the biometric parameters in accordance with a determination that the computer system is in a second mode different from the first mode.

[0034] According to some embodiments, a computer system is described that includes a set of one or more biometric sensors, means for detecting that a first set of health metrics is met, and means for, in response to detecting that the set of health metrics is met, measuring values ​​of biometric parameters via the set of one or more biometric sensors in accordance with a determination that the computer system is in a first mode, and ceasing measuring the biometric parameters in accordance with a determination that the computer system is in a second mode different from the first mode.

[0035] Executable instructions to perform these functions are optionally contained in a non-transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors. Executable instructions to perform these functions are optionally contained in a transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors.

[0036] Thus, devices are provided with faster, more efficient methods and interfaces for managing and / or presenting health data, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may optionally complement or replace other methods for managing and / or presenting health data. [Brief explanation of the drawings]

[0037] For a better understanding of the various embodiments described above, please refer to the following description of the embodiments in conjunction with the following drawings, in which like reference numerals refer to corresponding parts throughout the drawings, in which:

[0038] [Figure 1A] FIG. 1 is a block diagram illustrating a portable multifunction device having a touch-sensitive display in accordance with some embodiments.

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

[0040] [Figure 2] 1 illustrates a portable multifunction device with a touch screen according to some embodiments.

[0041] [Figure 3] FIG. 1 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface in accordance with some embodiments.

[0042] [Figure 4A] 1A-1C illustrate exemplary user interfaces for a menu of applications on a portable multifunction device in accordance with some embodiments.

[0043] [Figure 4B]1 illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display, according to some embodiments.

[0044] [Figure 5A] 1 illustrates a personal electronic device according to some embodiments.

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

[0046] [Figure 6A] 1 illustrates an example user interface for managing health and safety features on an electronic device according to some embodiments. [Figure 6B] 1 illustrates an example user interface for managing health and safety features on an electronic device according to some embodiments. [Figure 6C] 1 illustrates an example user interface for managing health and safety features on an electronic device according to some embodiments. [Figure 6D] 1 illustrates an example user interface for managing health and safety features on an electronic device according to some embodiments. [Figure 6E] 1 illustrates an example user interface for managing health and safety features on an electronic device according to some embodiments. [Figure 6F] 1 illustrates an example user interface for managing health and safety features on an electronic device according to some embodiments. [Figure 6G] 1 illustrates an example user interface for managing health and safety features on an electronic device according to some embodiments. [Figure 6H] 1 illustrates an example user interface for managing health and safety features on an electronic device according to some embodiments. [Figure 6I]1 illustrates an example user interface for managing health and safety features on an electronic device according to some embodiments. [Figure 6J] 1 illustrates an example user interface for managing health and safety features on an electronic device according to some embodiments. [Figure 6K] 1 illustrates an example user interface for managing health and safety features on an electronic device according to some embodiments. [Figure 6L] 1 illustrates an example user interface for managing health and safety features on an electronic device according to some embodiments. [Figure 6M] 1 illustrates an example user interface for managing health and safety features on an electronic device according to some embodiments. [Figure 6N] 1 illustrates an example user interface for managing health and safety features on an electronic device according to some embodiments. [Figure 6O] 1 illustrates an example user interface for managing health and safety features on an electronic device according to some embodiments.

[0047] [Figure 7A] FIG. 1 is a flow diagram illustrating a method for managing health and safety features on an electronic device according to some embodiments. [Figure 7B] FIG. 1 is a flow diagram illustrating a method for managing health and safety features on an electronic device according to some embodiments. [Figure 7C] FIG. 1 is a flow diagram illustrating a method for managing health and safety features on an electronic device according to some embodiments.

[0048] [Figure 8A] 1 illustrates an exemplary user interface for managing the setup of wellness features on an electronic device according to some embodiments. [Figure 8B]1 illustrates an exemplary user interface for managing the setup of wellness features on an electronic device according to some embodiments. [Figure 8C] 1 illustrates an exemplary user interface for managing the setup of wellness features on an electronic device according to some embodiments. [Figure 8D] 1 illustrates an exemplary user interface for managing the setup of wellness features on an electronic device according to some embodiments. [Figure 8E] 1 illustrates an exemplary user interface for managing the setup of wellness features on an electronic device according to some embodiments. [Figure 8F] 1 illustrates an exemplary user interface for managing the setup of wellness features on an electronic device according to some embodiments. [Figure 8G] 1 illustrates an exemplary user interface for managing the setup of wellness features on an electronic device according to some embodiments. [Figure 8H] 1 illustrates an exemplary user interface for managing the setup of wellness features on an electronic device according to some embodiments. [Figure 8I] 1 illustrates an exemplary user interface for managing the setup of wellness features on an electronic device according to some embodiments. [Figure 8J] 1 illustrates an exemplary user interface for managing the setup of wellness features on an electronic device according to some embodiments. [Figure 8K] 1 illustrates an exemplary user interface for managing the setup of wellness features on an electronic device according to some embodiments. [Figure 8L] 1 illustrates an exemplary user interface for managing the setup of wellness features on an electronic device according to some embodiments. [Figure 8M] 1 illustrates an exemplary user interface for managing the setup of wellness features on an electronic device according to some embodiments. [Figure 8N]1 illustrates an exemplary user interface for managing the setup of wellness features on an electronic device according to some embodiments. [Figure 8O] 1 illustrates an exemplary user interface for managing the setup of wellness features on an electronic device according to some embodiments. [Figure 8P] 1 illustrates an exemplary user interface for managing the setup of wellness features on an electronic device according to some embodiments. [Figure 8Q] 1 illustrates an exemplary user interface for managing the setup of wellness features on an electronic device according to some embodiments. [Figure 8R] 1 illustrates an exemplary user interface for managing the setup of wellness features on an electronic device according to some embodiments. [Figure 8S] 1 illustrates an exemplary user interface for managing the setup of wellness features on an electronic device according to some embodiments.

[0049] [Figure 9A] FIG. 1 is a flow diagram illustrating a method for managing the setup of wellness features on an electronic device according to some embodiments. [Figure 9B] FIG. 1 is a flow diagram illustrating a method for managing the setup of wellness features on an electronic device according to some embodiments. [Figure 9C] FIG. 1 is a flow diagram illustrating a method for managing the setup of wellness features on an electronic device according to some embodiments.

[0050] [Figure 10A] 1 illustrates an example user interface for managing background health measurements on an electronic device according to some embodiments. [Figure 10B] 1 illustrates an example user interface for managing background health measurements on an electronic device according to some embodiments. [Figure 10C]1 illustrates an example user interface for managing background health measurements on an electronic device according to some embodiments. [Figure 10D] 1 illustrates an example user interface for managing background health measurements on an electronic device according to some embodiments. [Figure 10E] 1 illustrates an example user interface for managing background health measurements on an electronic device according to some embodiments. [Figure 10F] 1 illustrates an example user interface for managing background health measurements on an electronic device according to some embodiments. [Figure 10G] 1 illustrates an example user interface for managing background health measurements on an electronic device according to some embodiments. [Figure 10H] 1 illustrates an example user interface for managing background health measurements on an electronic device according to some embodiments. [Figure 10I] 1 illustrates an example user interface for managing background health measurements on an electronic device according to some embodiments. [Figure 10J] 1 illustrates an example user interface for managing background health measurements on an electronic device according to some embodiments. [Figure 10K] 1 illustrates an example user interface for managing background health measurements on an electronic device according to some embodiments. [Figure 10L] 1 illustrates an example user interface for managing background health measurements on an electronic device according to some embodiments. [Figure 10M] 1 illustrates an example user interface for managing background health measurements on an electronic device according to some embodiments. [Figure 10N] 1 illustrates an example user interface for managing background health measurements on an electronic device according to some embodiments. [Figure 10O] 1 illustrates an example user interface for managing background health measurements on an electronic device according to some embodiments. [Figure 10P] 1 illustrates an example user interface for managing background health measurements on an electronic device according to some embodiments. [Figure 10Q] 1 illustrates an example user interface for managing background health measurements on an electronic device according to some embodiments. [Figure 10R] 1 illustrates an example user interface for managing background health measurements on an electronic device according to some embodiments. [Figure 10S] 1 illustrates an example user interface for managing background health measurements on an electronic device according to some embodiments. [Figure 10T] 1 illustrates an example user interface for managing background health measurements on an electronic device according to some embodiments. [Figure 10U] 1 illustrates an example user interface for managing background health measurements on an electronic device according to some embodiments. [Figure 10V] 1 illustrates an example user interface for managing background health measurements on an electronic device according to some embodiments.

[0051] [Figure 11A] FIG. 1 is a flow diagram illustrating a method for managing background health measurements on an electronic device according to some embodiments. [Figure 11B] FIG. 1 is a flow diagram illustrating a method for managing background health measurements on an electronic device according to some embodiments.

[0052] [Figure 12A]1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12B] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12C] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12D] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12E] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12F] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12G] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12H] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12I] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12J] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12K] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12L]1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12M] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12N] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12Q] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12R] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12S] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12T] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12U] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12V] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12W] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12X] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12Y]1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12Z] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12AA] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12AB] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12AC] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12AD] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12AE] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12AF] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 12AG] 1 illustrates an exemplary user interface for managing biometric measurements taken using an electronic device according to some embodiments.

[0053] [Figure 12O] 10A-10C are flow diagrams illustrating methods for managing prompts and measurements based on location and movement data, respectively. [Figure 12P] 10A-10C are flow diagrams illustrating methods for managing prompts and measurements based on location and movement data, respectively.

[0054] [Figure 13A] FIG. 1 is a flow diagram illustrating a method for managing biometric measurements taken using an electronic device according to some embodiments. [Figure 13B] FIG. 1 is a flow diagram illustrating a method for managing biometric measurements taken using an electronic device according to some embodiments.

[0055] [Figure 14A] 1 illustrates an exemplary user interface for providing results of health information captured on an electronic device according to some embodiments. [Figure 14B] 1 illustrates an exemplary user interface for providing results of health information captured on an electronic device according to some embodiments. [Figure 14C] 1 illustrates an exemplary user interface for providing results of health information captured on an electronic device according to some embodiments. [Figure 14D] 1 illustrates an exemplary user interface for providing results of health information captured on an electronic device according to some embodiments. [Figure 14E] 1 illustrates an exemplary user interface for providing results of health information captured on an electronic device according to some embodiments. [Figure 14F] 1 illustrates an exemplary user interface for providing results of health information captured on an electronic device according to some embodiments. [Figure 14F1] 1 illustrates an exemplary user interface for providing results of health information captured on an electronic device according to some embodiments. [Figure 14F2] 1 illustrates an exemplary user interface for providing results of health information captured on an electronic device according to some embodiments. [Figure 14G] 1 illustrates an exemplary user interface for providing results of health information captured on an electronic device according to some embodiments. [Figure 14H] 1 illustrates an exemplary user interface for providing results of health information captured on an electronic device according to some embodiments. [Figure 14I] 1 illustrates an exemplary user interface for providing results of health information captured on an electronic device according to some embodiments.

[0056] [Figure 15A] FIG. 1 is a flow diagram illustrating a method for providing results of health information captured on an electronic device, according to some embodiments. [Figure 15B] FIG. 1 is a flow diagram illustrating a method for providing results of health information captured on an electronic device, according to some embodiments.

[0057] [Figure 16A] 1 illustrates an exemplary user interface for managing background health measurements on an electronic device, according to some embodiments. [Figure 16B] 1 illustrates an exemplary user interface for managing background health measurements on an electronic device, according to some embodiments. [Figure 16C] 1 illustrates an exemplary user interface for managing background health measurements on an electronic device, according to some embodiments.

[0058] [Figure 17A] FIG. 1 is a flow diagram illustrating a method for managing background health measurements on an electronic device according to some embodiments. [Figure 17B] 1 is a flow diagram illustrating a method for managing background health measurements on an electronic device according to some embodiments.

[0059] The following description describes example methods, parameters, etc. However, it should be recognized that such description is not intended as a limitation on the scope of the present disclosure, but is instead provided as a description of example embodiments.

[0060] There is a need for electronic devices that provide efficient methods and interfaces for managing and / or presenting health data. For example, there is a need for electronic devices that quickly and easily measure health information to allow users to conveniently monitor their health. As another example, there is a need for electronic devices that allow users to conveniently and efficiently manage and monitor acquired health information so that users can easily understand the results and respond appropriately. As another example, there is a need for electronic devices that allow users to conveniently display and manage various health and safety functions so that users can use the electronic device to assess their health in an efficient and effective manner. Such techniques can reduce the cognitive burden on users accessing health data on electronic devices, thereby increasing productivity. Furthermore, such techniques can reduce processor and battery power that would otherwise be wasted on redundant user input.

[0061] 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description of an example device for performing techniques for managing and / or presenting health data. FIGS. 6A-6O illustrate example user interfaces for managing health and safety features on an electronic device, according to some embodiments. FIGS. 7A-7C are flow diagrams illustrating methods for managing health and safety features on an electronic device, according to some embodiments. The user interfaces in FIGS. 6A-6O are used to illustrate processes described below, including the processes in FIGS. 7A-7C. FIGS. 8A-8S illustrate example user interfaces for managing the setup of health features on an electronic device, according to some embodiments. FIGS. 9A-9C are flow diagrams illustrating methods for managing the setup of health features on an electronic device, according to some embodiments. The user interfaces in FIGS. 8A-8S are used to illustrate processes described below, including the processes in FIGS. 9A-9C. FIGS. 10A-10V illustrate example user interfaces for managing background health measurements on an electronic device, according to some embodiments. FIGS. 11A-11B are flow diagrams illustrating methods for managing background health measurements on an electronic device according to some embodiments. The user interfaces of FIGS. 10A-10V are used to illustrate processes described below, including the processes of FIGS. 11A-11B. FIGS. 12A-12N and 12Q-12AG show exemplary user interfaces for managing biometric measurements taken using an electronic device according to some embodiments. FIGS. 12O and 12P are flow diagrams illustrating methods for managing prompts and measurements based on location and movement data, respectively. FIGS. 13A-13B are flow diagrams illustrating methods for managing biometric measurements taken using an electronic device according to some embodiments. The user interfaces of FIGS. 12A-12N and 12Q-12AG are used to illustrate processes described below, including the processes of FIGS. 12O-12P and 13A-13B.14A-14I illustrate exemplary user interfaces for providing results of health information captured on an electronic device according to some embodiments. 15A-15B are flow diagrams illustrating methods for providing results of health information captured on an electronic device according to some embodiments. The user interfaces of FIGS. 14A-14I are used to illustrate processes described below, including the processes of FIGS. 15A-15B. 16A-16C illustrate exemplary user interfaces for managing background health measurements on an electronic device according to some embodiments. 17A-17B are flow diagrams illustrating methods for managing background health measurements on an electronic device according to some embodiments. The user interfaces of FIGS. 16A-16C are used to illustrate processes described below, including the processes of FIGS. 17A-17B.

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

[0063] 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. In the description of the various described embodiments and in the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. Also, as used herein, the term "and / or" should be understood to refer to and include any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "includes," "including," "comprises," and / or "comprising," when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

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

[0065] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as PDA and / or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Optionally, other portable electronic devices, such as laptops or tablet computers having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad), are also used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad). In some embodiments, the electronic device is a computer system that communicates (e.g., via wireless communication, via wired communication) with a display generation component. The display generation component is configured to provide a visual output, such as a display via a CRT display, a display via an LED display, or a display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. As used herein, "displaying" content includes displaying content (e.g., video data rendered or decoded by display controller 156) by transmitting data (e.g., image data or video data) via a wired or wireless connection to an integrated or external display generation component to visually generate the content.

[0066] The following discussion describes electronic devices that include a display and a touch-sensitive surface, however, it should be understood that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and / or a joystick.

[0067] The device typically supports a variety of applications such as one or more of a drawing application, a presentation application, a word processing application, a website creation application, a disc authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an email application, an instant messaging application, a training support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music playback application, and / or a digital video playback application.

[0068] Various applications running on the device optionally use at least one common physical user-interface device, such as a touch-sensitive surface. One or more features of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or changed for each application and / or within each application. In this way, the device's common physical architecture (such as the touch-sensitive surface) optionally supports various applications with user interfaces that are intuitive and transparent to the user.

[0069] Attention now turns to embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating portable multifunction device 100 having touch-sensitive display system 112 according to some embodiments. Touch-sensitive display 112 may conveniently be referred to as a "touch screen" and may also be known or referred to as a "touch-sensitive display system." Device 100 includes memory 102 (optionally including one or more computer-readable storage media), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input / output (I / O) subsystem 106, other input control devices 116, and external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 that detect the intensity of a contact on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 that generate tactile output on device 100 (e.g., generate tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0070] As used herein and in the claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or a proxy for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​that includes at least four distinct values ​​and more typically includes hundreds (e.g., at least 256) distinct values. The intensity of a contact is optionally determined (or measured) using various techniques and various sensors or combinations of sensors. For example, one or more force sensors under or adjacent to the touch-sensitive surface are optionally used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted average) to determine an estimated force of the contact. Similarly, a pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and / or change in the contact area detected on the touch-sensitive surface, the capacitance and / or change in the capacitance of the touch-sensitive surface proximate the contact, and / or the resistance and / or change in the capacitance of the touch-sensitive surface proximate the contact are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measurement for the force or pressure of the contact is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is stated in units corresponding to the surrogate measurement). In some implementations, the surrogate measurement for the contact force or pressure is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using contact intensity as an attribute of user input allows a user to access additional device functionality that may not otherwise be accessible by a user on devices of reduced size that have limited area for displaying affordances (e.g., on a touch-sensitive display) and / or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls such as knobs or buttons).

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

[0072] It should be understood that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally has two or more components, optionally a combination of components, or components in a different configuration or arrangement. The various components shown in Figure 1A may be implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing circuits and / or application specific integrated circuits.

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

[0074] Peripheral interface 118 may be used to couple input and output peripherals of the device to CPU 120 and memory 102. One or more processors 120 operate or execute various software programs and / or instruction sets stored in memory 102 to perform various functions and process data for device 100. 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.

[0075] RF (radio frequency) circuitry 108 receives and transmits RF signals, also referred to as electromagnetic signals. RF circuitry 108 converts electrical signals to electromagnetic signals or electromagnetic signals to electrical signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, etc. RF circuitry 108 optionally communicates via wireless communication with networks, such as the Internet, also known as the World Wide Web (WWW), an intranet, and / or wireless networks, such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and with other devices. RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by short-range radios. Wireless communication optionally includes, but is not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), Long Term Evolution (LTE), and other technologies.Wireless technology includes, but is not limited to, technology such as: LTE evolution (LTE), near field communications (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth®, Bluetooth Low Energy (BTLE®), Wireless Fidelity (Wi-Fi®) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and / or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX®, protocols for email (e.g., Internet message access protocol (IMAP) and / or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol), and the like. The present invention may use any of a number of communication standards, protocols, and technologies, including the Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (XMPP), the Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), the Instant Messaging and Presence Service (IMPS), and / or the Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this application.

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

[0077] I / O subsystem 106 couples input / output peripherals on device 100, such as touchscreen 112 and other input control devices 116, to peripheral interface 118. I / O subsystem 106 optionally includes display controller 156, light 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. One or more input controllers 160 receive / send electrical signals from / to other input control devices 116. Other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, etc. In some embodiments, input controller(s) 160 are optionally coupled to any (or none) of a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208 in FIG. 2 ) optionally include up and down buttons for volume control of speaker 111 and / or microphone 113. The one or more buttons optionally include a push button (e.g., 206 in FIG. 2 ). In some embodiments, the electronic device is a computer system in communication (e.g., via wireless communication, via wired communication) with one or more input devices. In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a trackpad 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.

[0078] As described in U.S. Patent Application No. 11 / 322,549, filed December 23, 2005, "Unlocking a Device by Performing Gestures on an Unlock Image," U.S. Patent No. 7,657,849, which is incorporated herein by reference in its entirety, a quick press of the push button optionally disengages a lock on the touchscreen 112 or, optionally, initiates a process to unlock the device using a gesture on the touchscreen. A longer press of a push button (e.g., 206) optionally turns power on or off to the device 100. The functionality of one or more of the buttons is optionally customizable by the user. The touchscreen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

[0079] Touch-sensitive display 112 provides an input and output interface between the device and a user. Display controller 156 receives and / or sends electrical signals to touchscreen 112. Touchscreen 112 displays visual output to the user. This visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output optionally corresponds to user interface objects.

[0080] Touchscreen 112 has a touch-sensitive surface, sensor, or set of sensors that receive 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 sets in memory 102) detects contacts (and any movement or cessation of contact) on touchscreen 112 and translates the detected contacts into interactions with user interface objects (e.g., one or more softkeys, icons, web pages, or images) displayed on touchscreen 112. In an exemplary embodiment, the point of contact between touchscreen 112 and the user corresponds to the user's finger.

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

[0082] The touch-sensitive display in some embodiments of touchscreen 112 is optionally similar to the multi-touch-sensing touchpad described in U.S. Patent Nos. 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman), and / or U.S. Patent Publication No. 2002 / 0015024A1, each of which is incorporated by reference herein in its entirety. However, touchscreen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.

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

[0084] Touchscreen 112 optionally has a video resolution of 100 dpi or greater. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. A user optionally contacts touchscreen 112 using any suitable object or accessory, such as a stylus, finger, or the like. In some embodiments, the user interface is designed to primarily handle finger contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of ​​a finger on the touchscreen. In some embodiments, the device translates the coarse finger input into precise pointer / cursor positions or commands to perform the action desired by the user.

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

[0086] Device 100 also includes a power system 162 for providing power to the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, power failure detection circuitry, power converters or inverters, power status indicators (e.g., light emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power within a portable device.

[0087] Device 100 also optionally includes one or more light sensors 164. FIG. 1A shows a light sensor coupled to light sensor controller 158 in I / O subsystem 106. Light sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Light sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. Light sensor 164 optionally works in conjunction with imaging module 143 (also called a camera module) to capture still images or video. In some embodiments, the light sensor is located on the back of device 100, as opposed to touchscreen display 112, which is on the front of the device, so that the touchscreen display is effectively used as a viewfinder for capturing still and / or video images. In some embodiments, the light sensor is located on the front of the device so that an image of the user is obtained, optionally for video conferencing, and the user sees other video conference participants on the touchscreen display. In some embodiments, the position of the light sensor 164 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), so that a single light sensor 164 is used for both video conferencing and capturing still and / or video images, along with the touchscreen display.

[0088] Device 100 also optionally includes one or more depth camera sensors 175. FIG. 1A shows a depth camera sensor coupled to depth camera controller 169 in I / O subsystem 106. Depth camera sensor 175 receives data from the environment and creates a three-dimensional model of an object (e.g., a face) in a 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 is optionally used to determine a depth map of various portions of an image captured by imaging module 143. In some embodiments, a depth camera sensor is located on the front of device 100 so that images of the user with depth information are optionally obtained for videoconferences and to capture selfie images with depth map data while the user views other videoconference participants on a touchscreen display. In some embodiments, depth camera sensor 175 is located on the back of the device or on both the back and front of device 100. In some embodiments, the position of the depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), so that the depth camera sensor 175 is used for both video conferencing and capturing still and / or video images, along with a touchscreen display.

[0089] Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I / O subsystem 106. Contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor 165 receives contact intensity information (e.g., pressure information, or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is juxtaposed with or proximate to the touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touchscreen display 112, which is located on the front of device 100.

[0090] Device 100 also optionally includes one or more proximity sensors 166. Figure 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternatively, proximity sensor 166 is optionally coupled to input controller 160 within I / O subsystem 106. Proximity sensor 166 optionally functions as described in U.S. patent application Ser. Nos. 11 / 241,839, "Proximity Detector In Handheld Device," 11 / 240,788, "Proximity Detector In Handheld Device," 11 / 620,702, "Using Ambient Light Sensor To Augment Proximity Sensor Output," 11 / 586,862, "Automated Response To And Sensing Of User Activity In Portable Devices," and 11 / 638,251, "Methods And Systems For Automatic Configuration Of Peripherals," which are incorporated herein by reference in their entireties. In some embodiments, the proximity sensor turns off and disables touchscreen 112 when the multifunction device is placed near the user's ear (e.g., when the user is on a phone call).

[0091] Device 100 also optionally includes one or more haptic output generators 167. FIG. 1A shows tactile output generator 167 coupled to haptic feedback controller 161 in I / O subsystem 106. Tactile output generator 167 optionally includes one or more electroacoustic devices, such as speakers or other audio components, and / or electromechanical devices that convert energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile output on the device). Contact intensity sensor 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates a tactile output on device 100 that can be sensed by a user of device 100. In some embodiments, at least one tactile output generator is juxtaposed with or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112) and generates a tactile output, optionally by moving the touch-sensitive surface vertically (e.g., in / out of the surface of device 100) or horizontally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touchscreen display 112, which is located on the front of device 100.

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

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

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

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

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

[0097] In some embodiments, contact / movement module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by a user (e.g., whether a user has “clicked” an icon). In some embodiments, at least a subset of the intensity thresholds are determined according to software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a particular physical actuator, but can be adjusted without changing the physical hardware of device 100). For example, the mouse “click” threshold of a trackpad or touchscreen display can be set to any of a wide range of pre-defined thresholds without changing the trackpad or touchscreen display hardware. Additionally, in some implementations, a device user is provided with software settings to adjust one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or multiple intensity thresholds at once via a system-level click “intensity” parameter).

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

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

[0100] In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. Graphics module 132 receives one or more codes specifying the graphics to be displayed, including coordinate data and other graphic characteristic data, as needed, from an application or the like, and then generates screen image data to output to display controller 156.

[0101] Haptic feedback module 133 includes various software components for generating instructions used by haptic output generator 167 to generate haptic outputs at one or more locations on device 100 in response to a user's interaction with device 100.

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

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

[0104] Application 136 optionally includes the following modules (or sets of instructions), or a subset or superset thereof: • a contacts module 137 (sometimes called an address book or contact list); ●Telephone module 138, ●Videoconferencing module 139, ● an email client module 140; ● Instant messaging (IM) module 141, ●Training support module 142, a camera module 143 for still and / or video images, ● Image management module 144; ●Video player module, ●Music player module, ● Browser module 147, ● Calendar module 148, • A widget module 149 optionally including one or more of a weather widget 149-1, a stocks widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5, and other widgets obtained by the user, and a user-created widget 149-6; a widget creation module 150 for creating user-created widgets 149-6; ● Search module 151, A video and music player module 152 that integrates a video player module and a music player module; ● Memo module 153, Map module 154, and / or ●Online video module 155.

[0105] Optionally, examples of other applications 136 stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice duplication.

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

[0107] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, contact / movement module 130, graphics module 132, and text input module 134, telephone module 138 is optionally used to enter character sequences corresponding to telephone numbers, access one or more telephone numbers in contacts module 137, modify entered telephone numbers, dial respective telephone numbers, conduct conversations, and terminate or hang up when the conversation is completed. As previously mentioned, wireless communication optionally uses any of a number of communication standards, protocols, and technologies.

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

[0109] In cooperation with RF circuitry 108, touch screen 112, display controller 156, contact / movement module 130, graphics module 132, and text input module 134, email client module 140 contains executable instructions for composing, sending, receiving, and managing emails in response to user commands. In cooperation with image management module 144, email client module 140 greatly facilitates the creation and sending of emails with still or video images captured by camera module 143.

[0110] In cooperation with RF circuitry 108, touchscreen 112, display controller 156, contact / movement module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for entering character sequences corresponding to instant messages, modifying previously entered characters, sending respective instant messages (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephony-based instant messaging, or XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, sent and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0111] In conjunction with the RF circuitry 108, touchscreen 112, display controller 156, touch / movement module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, the training support module 142 includes executable instructions for creating workouts (e.g., with time, distance, and / or calorie burn goals), communicating with training sensors (sports devices), receiving training sensor data, calibrating sensors used to monitor workouts, selecting and playing music for workouts, and displaying, storing, and transmitting workout data.

[0112] In conjunction with touch screen 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact / movement module 130, graphics module 132, and image management module 144, camera module 143 contains executable instructions for capturing and storing still images or video (including video streams) in memory 102, modifying characteristics of the still images or video, or deleting the still images or video from memory 102.

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

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

[0115] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / movement module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, calendar module 148 contains executable instructions for creating, displaying, modifying, and storing calendars and data associated with calendars (e.g., calendar items, to-do lists, etc.) in accordance with user instructions.

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

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

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

[0119] In conjunction with touchscreen 112, display controller 156, touch / movement module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 contains executable instructions that enable a user to download and play pre-recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, as well as executable instructions for displaying, presenting, or otherwise playing videos (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.).

[0120] In conjunction with the touch screen 112, display controller 156, contact / movement module 130, graphics module 132, and text input module 134, the notes module 153 contains executable instructions for creating and managing notes, to-do lists, and the like according to user commands.

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

[0122] In cooperation with touchscreen 112, display controller 156, contact / movement module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, online video module 155 contains instructions that enable a user to access, browse for, receive (e.g., by streaming and / or downloading), and play (e.g., on the touchscreen or on an external display connected via external port 124) particular online videos, send emails with links to particular online videos, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141 is used to send links to particular online videos, rather than email client module 140. Additional description of online video applications 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 entireties.

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

[0124] In some embodiments, device 100 is a device in which operation of a predetermined set of functions on the device is performed exclusively via a touchscreen and / or touchpad. Using the touchscreen and / or touchpad as the primary input control device for operation of device 100 optionally reduces the number of physical input control devices (push buttons, dials, etc.) on device 100.

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

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

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

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

[0129] Event monitor 171 receives event information from peripherals interface 118. The event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, accelerometer(s) 168, and / or microphone 113 (via audio circuitry 110). Information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

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

[0131] In some embodiments, event sorter 170 also includes hit view determination module 172 and / or active event recognizer determination module 173 .

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

[0133] Another aspect of a user interface associated with an application is the set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the respective application) in which the touch is detected optionally corresponds to a programmatic level within the application's programmatic or view hierarchy. For example, the lowest-level view in which the touch is detected is optionally referred to as the hit view, and the set of events that are recognized as suitable inputs is optionally determined based at least in part on the hit view of the initial touch that initiates the touch gesture.

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

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

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

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

[0138] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each containing instructions for processing touch events that occur within a respective view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, each application view 191 includes multiple event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit or a higher-level object from which application 136-1 inherits methods and other attributes. In some embodiments, each event handler 190 includes one or more of data updater 176, object updater 177, GUI updater 178, and / or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or invokes data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in each application view 191.

[0139] Each event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes metadata 183 and at least a subset of event delivery instructions 188 (optionally including sub-event delivery instructions).

[0140] Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, e.g., a touch or a movement of a touch. Depending on the sub-event, the event information also includes additional information, such as the position of the sub-event. When the sub-event involves a movement of a touch, the event information also optionally includes the speed and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from portrait to landscape or vice versa), and the event information includes corresponding information about the current orientation of the device (also called the device's attitude).

[0141] The event comparator 184 compares the event information with predefined event or sub-event definitions and determines the event or sub-event, or determines or updates the state of the event or sub-event, based on the comparison. In some embodiments, the event comparator 184 includes an event definition 186. The event definition 186 includes a definition of an event (e.g., a sequence of predefined sub-events), such as Event 1 (187-1) and Event 2 (187-2). In some embodiments, sub-events within an event (187) include, for example, touch start, touch end, touch movement, touch cancellation, and multiple touches. In one example, the definition for Event 1 (187-1) is a double tap on a displayed object. The double tap includes, for example, a first touch on a displayed object relative to a predetermined phase (touch start), a first lift-off (touch end) relative to the predetermined phase, a second touch on a displayed object relative to the predetermined phase (touch start), and a second lift-off (touch end) relative to the predetermined phase. In another example, a definition of event 2 (187-2) is a drag on a displayed object. Drag includes, for example, a touch (or contact) on the displayed object to a predetermined stage, a movement of the touch across the touch-sensitive display 112, and a lift-off of the touch (touch end). In some embodiments, the event also includes information about one or more associated event handlers 190.

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

[0143] In some embodiments, the definition of each event (187) also includes a delay action that delays distribution of the event information until it is determined whether the sequence of sub-events corresponds or does not correspond to the event type of the event recognizer.

[0144] If the respective event recognizer 180 determines that the sequence of sub-events does not match any of the events in the event definition 186, the respective event recognizer 180 enters an event-disabled, event-failed, or event-ended state and thereafter ignores the next sub-event of the touch-based gesture. In this situation, any other event recognizers that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

[0145] In some embodiments, each event recognizer 180 includes a meta list 183 with configurable properties, flags, and / or lists that indicate how the event distribution system performs sub-event distribution to actively participating event recognizers. In some embodiments, meta data 183 includes configurable properties, flags, and / or lists that indicate how event recognizers interact with each other or how event recognizers are enabled to interact with each other. In some embodiments, meta data 183 includes configurable properties, flags, and / or lists that indicate how sub-events are delivered to various levels in the view or programmatic hierarchy.

[0146] In some embodiments, each event recognizer 180 activates an event handler 190 associated with an event when one or more specific sub-events of the event are recognized. In some embodiments, each event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is separate from sending (and postponing) the sub-events to the respective hit view. In some embodiments, the event recognizer 180 pops a flag associated with the recognized event, and the event handler 190 associated with the flag captures the flag and performs a predetermined process.

[0147] In some embodiments, event distribution instructions 188 include sub-event distribution instructions that distribute event information about sub-events without activating an event handler. Instead, the sub-event distribution instructions distribute the event information to an event handler associated with a set of sub-events or to actively participating views. The event handler associated with the set of sub-events or actively participating views receives the event information and performs predetermined processing.

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

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

[0150] It will be appreciated that the above discussion regarding event processing of user touches on a touch-sensitive display also applies to other forms of user input operating multifunction device 100 having input devices, not all of which necessarily originate on a touchscreen. For example, mouse movements and mouse button presses, contact movements such as tapping, dragging, scrolling on a touchpad, optionally coordinated with single or multiple keyboard presses or holds, pen stylus input, device movement, verbal commands, detected eye movement, biometric input, and / or any combination thereof, optionally utilize as inputs corresponding to sub-events that define the recognized event.

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

[0152] Device 100 also optionally includes one or more physical buttons, such as a "home" or menu button 204. As previously mentioned, menu button 204 is optionally used to navigate to any application 136, optionally within a collection of applications running on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key within a GUI displayed on touchscreen 112.

[0153] In some embodiments, device 100 includes touchscreen 112, menu button 204, pushbuttons 206 for powering the device on / off and locking the device, volume control buttons 208, subscriber identity module (SIM) card slot 210, headset jack 212, and external docking / charging port 124. Pushbutton 206 is optionally used to power the device on / off by pressing and holding the button down for a predetermined period of time, to lock the device by pressing and releasing the button before the predetermined time has elapsed, and / or to unlock the device or initiate the unlocking process. In alternative embodiments, device 100 also accepts verbal input via microphone 113 for activating or deactivating some functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on touchscreen 112 and / or one or more tactile output generators 167 for generating a tactile output for a user of device 100.

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

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

[0156] Attention is now directed to user interface embodiments, optionally implemented on portable multifunction device 100, for example.

[0157] 4A shows an exemplary user interface for a menu of applications on portable multifunction device 100 according to some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof: signal strength indicator(s) 402 for wireless communication(s), such as cellular and Wi-Fi® signals; ●Time 404, ●Bluetooth (registered trademark) indicator 405, ● Battery status indicator 406, A tray 408 with icons of frequently used applications, such as: An icon 416 for the phone module 138, labeled "Phone," optionally including an indicator 414 of the number of missed calls or voicemail messages; icon 418 of the email client module 140, labeled "Mail," optionally including an indicator 410 of the number of unread emails; ○ An icon 420 for the browser module 147, labeled "Browser"; and ○ An icon 422 of the video and music player module 152, also called the iPod (trademark of Apple Inc.) module 152, labeled "iPod"; and ● Icons of other applications, such as: ○ Icon 424 of IM module 141, labeled "Messages"; icon 426 of the calendar module 148, labeled "Calendar"; ○ Icon 428 of the image management module 144, labeled "Photos" ○ An icon 430 of the camera module 143, labeled "camera"; ○ Icon 432 of the online video module 155, labeled "Online Video"; Icon 434 of Stocks widget 149-2, labeled "Stocks" ○ Icon 436 of the map module 154, labeled "Map"; Icon 438 of weather widget 149-1, labeled "Weather" ○ Icon 440 of alarm clock widget 149-4, labeled "Clock" ○ Icon 442 of Training Support Module 142, labeled "Training Support"; ○ An icon 444 of the Notes module 153 labeled "Notes," and A settings application or module icon 446 labeled "Settings" that provides access to settings for the device 100 and its various applications 136.

[0158] 4A are merely exemplary. For example, icon 422 for video and music player module 152 may be labeled "Music" or "Music Player." Other labels are optionally used for the various application icons. In some embodiments, the label for each application icon includes the name of the application corresponding to the respective application icon. In some embodiments, the label for a particular application icon is different from the name of the application corresponding to that particular application icon.

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

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

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

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

[0163] Exemplary techniques for detecting and processing touch intensity can be found, for example, in International Patent Application No. PCT / US2013 / 040061, filed May 8, 2013, entitled "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application," published as International Patent Application No. WO / 2013 / 169849, and related applications, including International Patent Application No. PCT / US2013 / 069483, filed November 11, 2013, entitled "Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships," published as International Patent Application No. WO / 2014 / 105276, each of which is incorporated herein by reference in its entirety.

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

[0165] FIG. 5B illustrates an exemplary personal electronic device 500. In some embodiments, device 500 can include some or all of the components described with respect to FIGS. 1A, 1B, and 3. Device 500 has a bus 512 that operably couples an I / O section 514 to one or more computer processors 516 and a memory 518. I / O section 514 can be connected to a display 504, which can have touch-sensing components 522 and, optionally, an intensity sensor 524 (e.g., a contact intensity sensor). Additionally, I / O section 514 can be connected to a communication unit 530 that receives application and operating system data using Wi-Fi, Bluetooth, near-field communication (NFC), cellular, and / or other wireless communication techniques. Device 500 can include input mechanisms 506 and / or 508. Input mechanism 506 is optionally a rotatable input device or a depressible and rotatable input device, for example. In some examples, input mechanism 508 is optionally a button.

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

[0167] 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 process 700 (FIGS. 7A-7C), process 900 (FIGS. 9A-9C), process 1100 (FIGS. 11A-11B), process 1300 (FIGS. 13A-13B), process 1500 (FIGS. 15A-15B), and process 1700 (FIGS. 17A-17B). A computer-readable storage medium may be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some embodiments, the storage medium is a transitory computer-readable storage medium. In some embodiments, the storage medium is a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium may include, but is not limited to, magnetic, optical, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, CDs, DVDs, or optical disks based on Blu-ray® technology, as well as resident solid-state memory such as flash and solid-state drives. The personal electronic device 500 is not limited to the components and configuration of FIG. 5B and may include other or additional components in multiple configurations.

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

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

[0170] As used herein and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of that contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predetermined number of intensity samples, i.e., a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) associated with a predetermined event (e.g., after detecting the contact, before detecting lift-off of the contact, before or after detecting the start of contact movement, before detecting the end of the contact, before or after detecting an increase in the intensity of the contact, and / or before or after detecting a decrease in the intensity of the contact). The characteristic intensity of the contact is optionally based on one or more of the maximum intensity of the contact, the mean intensity of the contact, the average intensity of the contact, the top 10 percentile intensity of the contact, half the maximum intensity of the contact, 90 percent of the maximum intensity of the contact, etc. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action is performed by the user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact having a characteristic intensity that does not exceed the first threshold results in a first action, a contact having a characteristic intensity that exceeds the first intensity threshold but not the second intensity threshold results in a second action, and a contact having a characteristic intensity that exceeds the second threshold results in a third action. In some embodiments, the comparison between the characteristic intensity and the one or more thresholds is not used to determine whether to perform the first action or the second action, but rather to determine whether to perform one or more actions (e.g., whether to perform the respective action or to refrain from performing the respective action).

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

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

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

[0174] Attention is now directed to embodiments of user interfaces (“UIs”) and associated processes implemented on an electronic device such as portable multifunction device 100, device 300, or device 500.

[0175] Figures 6A-6O show example user interfaces for managing health and safety features on an electronic device according to some embodiments. The user interfaces in those figures are used to illustrate processes described below, including the processes in Figures 7A-7C.

[0176] 6A illustrates an electronic device 600A (e.g., a smartphone, a smartwatch) that includes a display generation component 602A (e.g., a display controller, a touch-sensitive display system, a display (e.g., integrated or connected)) and one or more input devices (e.g., a gyroscope, an accelerometer, a microphone, a touch-sensitive surface). In some embodiments, device 600A includes one or more elements or functionality of devices 100, 300, and 500.

[0177] In FIG. 6A , device 600A displays, via display generation component 602A, a user interface 610 for a user account page of a health application. The health application collects and presents data on device 600A related to health-related features associated with the user account. The health-related features correspond to applications (e.g., applications or application functions) running or operable on device 600A, or running or operable on an external electronic device, such as a smartwatch (e.g., device 600B, first described with reference to FIG. 8I), or server paired with device 600A. User interface 610 includes selectable user interface elements 612 that, when selected, cause the display of the user interface described with reference to FIG. 6B .

[0178] In FIG. 6A, while displaying a user interface 610, a device 600A receives input 601 (eg, touch input, tap input) directed to a selectable user interface element 612.

[0179] In Figure 6B, in response to receiving input 601, device 600A displays user interface 614. The left depiction of device 600A in Figure 6B displaying user interface 614 corresponds to the top of user interface 614, and the right depiction of device 600A in Figure 6B displaying user interface 614 corresponds to the bottom of user interface 614.

[0180] User interface 614 includes user interface objects (e.g., 618, 620, 622, 624, 626, 628, 632, 634, 638, and 640), also referred to herein as platters. Each platter corresponds to a particular health-related feature that is currently inactive, active, or unavailable to operate on device 600A or a paired smartwatch. Within user interface 614, device 600A arranges the platters based on whether the respective health-related feature is inactive, active, or unavailable to operate on device 600A or a paired smartwatch. If the respective health-related feature has not been enabled or set up for use on device 600A or a paired smartwatch, the respective health-related feature is inactive on device 600A or a paired smartwatch. Each health-related feature is active on device 600A or a paired smartwatch if it is used continuously and / or intermittently (e.g., automatically) or if it is enabled (e.g., manually) on device 600A or a paired smartwatch. If the respective health-related feature cannot be enabled or set up for use on device 600A or a paired smartwatch, the respective health-related feature is unavailable on device 600A or a paired smartwatch.

[0181] 6B, user interface 614 includes region 616 that includes platters 618, 620, 622, 624, 626, and 628 that correspond to health-related features that are currently inactive on device 600A and / or on a paired smartwatch. In region 616, the platters include information about the corresponding application (e.g., information about the application's functionality), an indication of one or more devices (e.g., device 600A and / or a paired smartwatch) on which the respective application (e.g., or application function) may be activated, and the type of affordance (e.g., a setup affordance, an activation affordance for activating the respective application (e.g., application function)).

[0182] For example, a platter 618 corresponding to an ECG application includes information 618A about taking ECG measurements to monitor cardiac health, an indication 618B that the ECG application can only be used via a paired smartwatch, and a setup affordance 618C that, when activated, initiates a setup process to enable the ECG application for use via a paired smartwatch.

[0183] In another example, platter 622 corresponds to a low heart rate notification application that can measure a user's heart rate, manage the measured heart rate data, and generate a low heart rate notification based on the heart rate data when the measured heart rate falls below a notification threshold. Platter 622 includes information 622A related to heart rate monitoring, an indication 622B that the low heart rate notification application can be used via a paired smartwatch, and an enable affordance 622C. When activated, affordance 622C initiates a simplified (e.g., one-step, rapid) process for activating the low heart rate notification application.

[0184] In another example, a platter 626 corresponding to a fall detection application includes information 626A regarding one or more features of the fall detection application, an indication 626B that the fall detection application can be used via a paired smartwatch, and an enablement affordance 626C that, when activated, initiates a simplified (e.g., one-step, rapid) process for activating the fall detection application (e.g., instead of launching a native setup process for the fall detection application).

[0185] In another example, the platter 628 corresponds to a noise notification application that can detect a noise level in an ambient environment and generate a notification if the detected noise level is determined to be higher than a noise level threshold. The platter 628 includes information 628A regarding one or more features of noise notification, an indication 628A that the noise notification application can be used via both the device 600A and a paired smartwatch, and an enablement affordance 628C that, when activated, initiates a simplified (e.g., one-step, rapid) process for activating the noise notification application on both the device 600A and a paired smartwatch.

[0186] 6B, user interface 614 includes region 630 that includes platters 632 and 636 corresponding to health-related functions currently active on device 600A and / or on an external device paired with device 600A (e.g., device 600B). In the embodiment of FIG. 6B, region 630 includes platter 632 corresponding to a medical ID application and platter 634 corresponding to an emergency SOS application.

[0187] In area 630, the platter includes information about each application (e.g., or application function) and an indication of when each application (e.g., or application function) was last updated (e.g., when one or more settings of each application were last updated / changed, when one or more user interfaces stored in each application were last updated / changed, when the version of each application was last updated to a newer version).

[0188] For example, a platter 632 corresponding to a medical ID application includes information 632A about how the medical ID application is used and an indication 632B of the date when the medical ID application and / or information entered by a user within the medical ID application was last updated.

[0189] 6B, user interface 614 includes region 636 that includes platters 638 and 640 corresponding to health-related features that are not operational on device 600A and / or a paired smartwatch. Region 636 includes platter 638 corresponding to a low cardiac health level notification application and platter 640 corresponding to a cardiac health level tracking application.

[0190] In area 636, the platter includes information about why its respective application (e.g., or application feature) is unavailable, and information about the type of affordance for viewing additional information about the application or changing device settings (e.g., device privileges such as privacy settings) of the respective device to make the application available (e.g., so that the application can be activated).

[0191] For example, a platter 638 corresponding to a low heart health level notification application includes an indication 638A of why the low heart health level notification application is not available (e.g., on a paired smartwatch) and a details affordance 638B for viewing additional information about the low heart health level notification application and / or why the application is not available (e.g., incompatible) on the paired smartwatch.

[0192] In another example, a platter 640 corresponding to a heart health level tracking application includes an indication 640A that the application is unavailable due to device settings (e.g., privacy settings), and an open settings affordance 640B that, when activated, displays a settings user interface where device settings (e.g., including privacy settings) can be changed.

[0193] In FIG. 6B, while displaying user interface 614, device 600A receives input 603 targeted to activation affordance 626C of platter 626 corresponding to a fall detection application.

[0194] In FIG. 6C , in response to receiving input 603, device 600A displays user interface 642 for activating the fall detection application. User interface 642 includes information 642A regarding one or more features of the fall detection application. User interface 642 also includes a suggestion 642B that the fall detection application be operated via a connected smartwatch (e.g., device 600B) paired with device 600A. User interface 642 also includes a selectable toggle button 642C that, when selected, switches the fall detection application from its current inactive “off” state to an active “on” state without requiring further input or steps. In the inactive “off” state, the fall detection application is not activated, and therefore the fall detection functionality of the application is not enabled on device 600B or the paired smartwatch. In the inactive “on” state, the fall detection application is activated, and therefore the fall detection functionality of the application is enabled and used by device 600B or the paired smartwatch. Thus, the user interface 642 allows for a one-step process for activating the fall detection application.

[0195] 6C, while displaying user interface 642, device 600A receives input 605 directed to toggle button 642C to activate (e.g., toggle on) the fall detection application. In response to receiving input 605 directed to activating the fall detection application, device 600A activates the fall detection application on the paired smartwatch.

[0196] 6D shows device 600A displaying user interface 614 after the fall detection application has been activated via input 605. In FIG. 6D, device 600A displays platter 626 corresponding to the fall detection application in region 630 instead of region 616 because the fall detection application has been activated.

[0197] Also in FIG. 6D, while displaying user interface 614, device 600A receives input 607 targeted to activation affordance 628C of platter 628 corresponding to a noise notification application.

[0198] In FIG. 6E , in response to receiving input 607, device 600A displays user interface 644 for activating a noise notification application. User interface 644 includes information 644A regarding one or more features of the noise notification application. User interface 644 also includes an indication 644B that the noise notification application is operated via both device 600A and a paired smartwatch. User interface 644 also includes a selectable toggle button 644C, an affordance that, when activated, switches the noise notification application from its current inactive “off” state to its active “on” state. User interface 644 also includes a selectable user interface object 644D that, when activated, allows the user to change the decibel threshold used to determine whether a noise notification should be triggered from the currently selected threshold of 80 dB to a different threshold. 80 dB is an example of a selectable decibel threshold; the noise notification application may offer multiple decibel thresholds for selection, including or excluding 80 dB.

[0199] 6E, while displaying user interface 644, device 600A receives input 609 directed to toggle button 644C to activate a noise notification application. In response to receiving input 609, device 600A activates the noise notification application on both device 600A and the paired smartwatch.

[0200] 6F shows device 600A displaying user interface 614 after the noise notification application has been enabled via input 609. In FIG. 6F, device 600A displays platter 628 corresponding to the fall detection application in region 630 instead of region 616 because the noise notification application has been activated.

[0201] In FIG. 6F, while displaying user interface 614, device 600A receives input 611 targeted to activation affordance 622C of platter 622 corresponding to a low heart rate notification application.

[0202] 6G, in response to receiving input 611, device 600A displays a user interface 646 for activating a low heart rate notification feature (e.g., of a heart rate measurement / management application). User interface 646 includes information 646A related to one or more features of the low heart rate notification application, including an indication that a BPM threshold must be selected to activate the low heart rate notification application. User interface 646 also includes an indication 646B that the low heart rate notification application is operated via a paired smartwatch, and a threshold selection area 648 for selecting a heart rate threshold for triggering a low heart rate notification when the measured heart rate is lower than the heart rate threshold. The threshold selection area 648 includes multiple BPM thresholds 648A-648F, where threshold 648A corresponds to off (so no notification is activated), threshold 648B corresponding to 55 BPM, threshold 648C corresponding to 50 BPM, threshold 648D corresponding to 45 BPM, threshold 648E corresponding to 40 BPM, and threshold 648F corresponding to 35 BPM.

[0203] 6G, while displaying user interface 646, device 600A receives input 613 directed to selecting threshold 648D (45 BPM). In response to receiving input 613 directed to selecting threshold 648D, device 600A activates a low heart rate notification application on the paired smartwatch based on the selected notification threshold of 45 BPM.

[0204] Figure 6H shows device 600A displaying user interface 614 after the low heart rate notification application has been enabled in Figure 6G. In Figure 6H, device 600A displays platter 622 corresponding to the low heart rate notification application in region 630 instead of region 616 because the low heart rate notification application has been activated.

[0205] 6H, while displaying user interface 614, device 600A receives input 615 targeted to setup affordance 618C of platter 618 corresponding to the ECG application. In response to receiving input 615, device 600A initiates a setup process for the ECG application that corresponds (e.g., in part) to the native multi-step setup process for the ECG application shown in FIGS. 6I-6K.

[0206] In Figure 6I, device 600A displays a first setup user interface 650 of the ECG application setup process. First setup user interface 650 includes information 650A about ECG measurement, a request 650B for user information (e.g., date of birth, age), and an affordance 650C for continuing the ECG application setup process. Also in Figure 6I, while displaying first setup user interface 650, device 600A receives input 617 targeted to affordance 650C.

[0207] 6J , in response to receiving input 617, device 600A displays a second setup user interface 652 of the ECG application setup process. Second setup user interface 652 includes detailed information 652A regarding ECG measurements and their relationship to cardiac health, as well as an affordance 652B for continuing the ECG application setup process. Also in FIG. 6J , while displaying second setup user interface 652, device 600A receives input 619 targeted to affordance 652B.

[0208] 6K, in response to receiving input 619 as shown in FIG. 6J, device 600A displays a third setup user interface 654 of the ECG application setup process. The third setup user interface 654 includes information 654A about completing the setup process by taking an ECG measurement using a paired smartwatch. In some embodiments, device 600A activates the ECG application upon detecting the completion of a successful first ECG measurement obtained via the paired smartwatch.

[0209] Figure 6L shows device 600A displaying user interface 614 after the ECG application has been enabled in Figures 6I-6K. In Figure 6L, device 600A displays platter 616 corresponding to the ECG application in region 630 instead of region 616 because the ECG application has been activated.

[0210] In FIG. 6L, while displaying user interface 614, device 600A receives input 621 targeted to detail affordance 638B of platter 638 corresponding to a low cardiac health level notification application.

[0211] 6M, in response to receiving input 621, device 600A displays a user interface 656 associated with a low cardiac health notification application. User interface 656 includes an indication 656A that the low cardiac health notification application is not operational on device 600A or a paired smartwatch, and an indication 656B of why the application is not available.

[0212] In some embodiments, an application (e.g., or application functionality) is unavailable (to operate on device 600A and / or a paired smartwatch) due to restrictions (e.g., government restrictions) on access to data or the location (e.g., city, state, country) where device 600A or an external device (e.g., device 600B) is being used, as described in more detail below with reference to Figures 8A-8S and 10A-10V. In some embodiments, an application (e.g., or application functionality) is unavailable (to operate on device 600A and / or a paired smartwatch) due to a biological characteristic of the user (e.g., age, pregnancy, pre-existing medical condition), as described in more detail below with reference to Figures 8A-8S.

[0213] 6N shows device 600A displaying a health application overview user interface 660. Overview user interface 660 includes multiple user interface objects 662, 664, and 666 corresponding to different health-related functions corresponding to health-related applications (e.g., or application functions) running on device 600A and / or on a paired smartwatch. Overview user interface 660 includes user interface object 662 corresponding to a noise level notification application and including information associated with a detected noise level. Overview user interface 660 also includes user interface object 664 corresponding to an activity application and including measured / detected activity-related information. Overview user interface 660 also includes user interface object 666 corresponding to a workout application and including past workout information.

[0214] 6O shows device 600A displaying a notification 668 (e.g., a time-based notification) in overview user interface 600 related to user interface 614. Notification 668 includes a suggestion 668A to review and, if necessary, update health-related features listed in user interface 614, as shown in FIG. 6B. In some embodiments, device 600A displays notification 668 as a banner notification (e.g., via the home user interface or a user interface of a different application). In some embodiments, device 600A displays notification 668 in a wake screen of device 600A.

[0215] In some embodiments, device 600A automatically displays notification 668 annually. In some embodiments, device 600A automatically displays notification 668 monthly.

[0216] In some embodiments, in response to receiving input directed to notification 668, device 600A displays user interface 614 so that health-related applications (e.g., or application functionality) can be easily and conveniently managed by the user.

[0217] 7A-7C are flow diagrams illustrating a method for managing health and safety features on an electronic device according to some embodiments. Method 700 is performed in a computer system (e.g., an electronic device (e.g., 100, 300, 500, 600A)) in communication with a display generation component (e.g., 602A) (e.g., a display controller, a touch-sensitive display system, a display (e.g., integrated or connected)) and one or more input devices (e.g., a gyroscope, an accelerometer, a microphone, a touch-sensitive surface). Some operations of method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0218] In some embodiments, the electronic device (e.g., 600A) is a computer system. The computer system is optionally in communication (e.g., wired communication, wireless communication) with a display generation component (e.g., 602A) and one or more input devices. The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. The one or more input devices are configured to receive input, such as a touch-sensitive surface that receives user 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. Thus, the computer system can send data (e.g., image data or video data) via a wired or wireless connection to an integrated or external display generation component to visually generate content (e.g., using a display device), and can receive input from the one or more input devices via a wired or wireless connection.

[0219] As described below, method 700 provides an intuitive way to manage and / or present health data. This method reduces the cognitive burden on the user when managing and / or presenting health data, thereby creating a more efficient human-machine interface. In the case of battery-operated computing devices, allowing users to manage and / or present health data faster and more efficiently conserves power and increases the time between battery charges.

[0220] A computer system (e.g., 600A), via a display generation component (e.g., 602A), displays (702) a user interface (e.g., 614) (e.g., a health function list interface) that includes a plurality of user interface objects (e.g., 618-628, 632-634, 638-640) corresponding to health-related (e.g., physical health (including physical safety), mental health) functions (e.g., applications or application functions running or available to run on the computer system or running or available to run on an external electronic device in communication with the computer system), the plurality of user interface objects including a first user interface object corresponding to a first health-related function (e.g., a heart rate tracking-related function (e.g., 620, 622, 624, 638, 640), a medical identification function (e.g., 632), an emergency contact function (e.g., 634), an ambient noise level tracking function (e.g., 628)).

[0221] A first user interface object (e.g., 632, 634) includes (704) an indication (e.g., 632A) that the first health-related function is active (e.g., a graphical or textual indication) (706) pursuant to a determination that the first health-related function is currently active (e.g., active on the computer system, active on an external electronic device in communication with the computer system, and active to provide data for the first health-related function to the computer system).

[0222] A first user interface object (e.g., 618, 620, 622, 624, 626, 628) includes an indication (e.g., graphical or textual indication) that the first health-related feature is available for activation pursuant to a determination that the first health-related feature is currently inactive and available for activation via a set of one or more inputs (e.g., 602a) received at the computer system, and a selectable user interface object (e.g., 618C, 626C) that, when selected, initiates a process for activating the first health-related feature (708) (704). In some embodiments, the first health-related feature indicates that it is inactive.

[0223] A first user interface object (e.g., 638, 640) includes (704) an indication (e.g., 638A) that the first health-related feature is unavailable for activation (e.g., a graphical or textual indication) (710) pursuant to a determination that the first health-related feature is currently inactive and unavailable for activation (e.g., unavailable for activation via a computer system, currently unavailable for activation (e.g., due to regulatory, hardware, or software constraints or limitations)).

[0224] Displaying the first user interface object with an indication based on whether the first health-related feature is active, inactive and available, or inactive and unavailable for activation provides the user with feedback regarding the status of the first health-related feature. Providing improved visual feedback to the user improves usability of the computer system, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and additionally reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0225] In some embodiments, the indication (e.g., 638A) that the first health-related feature is unavailable for activation includes an indication explaining why the feature is unavailable for activation.

[0226] In some embodiments, a first health-related feature is unavailable for activation due to a first solvable issue (e.g., a software issue solvable through an update, a hardware issue solvable by replacing and / or procuring hardware, a location-based issue solvable by changing location), and an indication that the first health-related feature is unavailable for activation, when selected via input received via one or more input devices, includes initiating a process (e.g., a process in the computer system, a process in an external device in communication with the computer system) to resolve the first solvable issue (724), thereby making the first health-related feature available for activation (726). Providing a selectable portion to initiate a process to resolve a solvable issue that prevents activation of a health-related feature provides users with greater control over their device and allows them to resolve issues without having to manually identify the source of the problem or clutter the UI with multiple options for identifying and resolving the problem. Providing additional control without cluttering the UI with additional displayed controllers enhances usability of the computer system, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and also reduces power usage and improves battery life of the device by allowing the user to use the computer system more quickly and efficiently.

[0227] In some embodiments, the first health-related feature is currently inactive and available for activation, and the first user interface object (e.g., 618, 620, 622, 624, 626, 628) includes a selectable portion (e.g., selectable region, affordance) (714) that, when selected via input received via one or more input devices (e.g., as shown in FIGS. 6C, 6E, 6G, and 6I-6K), initiates a process for activating the first health-related feature (712). In some embodiments, following a determination that the first health-related feature is active, the first user interface object (e.g., 632, 634) does not include a selectable portion that, when selected via input received via one or more input devices, initiates a process for activating the first health-related feature.

[0228] In some embodiments, a process for activating a first health-related feature (e.g., as shown in FIGS. 6C, 6E, 6G, and 6I-6K) includes a first type of activation process (e.g., as shown in FIGS. 6C, 6E, and 6G) ​​(718) (716) that requires a first minimum number of inputs (e.g., a minimum number of inputs that must be received) pursuant to a determination that the first health-related feature is a first type of feature (e.g., a feature having a binary state (active, inactive) (e.g., emergency fall detection, emergency contact)). In some embodiments, the first minimum number of inputs is one.

[0229] In some embodiments, a process for activating a first health-related function (e.g., as shown in FIGS. 6C, 6E, 6G, and 6I-6K) includes a second type of activation process 716 pursuant to a determination that the first health-related function is a second type of function (e.g., a function that requires additional information or approval for activation), where the second type of activation process requires a second minimum number of inputs (e.g., the first number of minimum inputs plus one (e.g., two or more minimum inputs if the first type of activation process requires a minimum of one input)) to activate the first health-related function (e.g., as shown in FIGS. 6I-6K), and the second minimum number of inputs is greater than the first minimum number of inputs 722. Initiating a process for activating the first health-related function using different types of activation processes that require different amounts of minimum inputs based on whether the first health-related function is of the first type or the second type provides the system with the ability to accommodate activation of different types of health-related functions, thereby increasing the control options available to the user via the user interface. Providing additional control options improves the usability of the computer system, makes the user device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and also reduces device power usage and improves battery life by allowing the user to use the computer system more quickly and efficiently.

[0230] In some embodiments, the health-related function is a first type of function and has a binary state (e.g., active or inactive). In some embodiments, the health-related function of the first type has a non-binary state (e.g., inactive, active with a first parameter, active with a second parameter), and the activation process of the first type includes pre-entry of at least one parameter of the function.

[0231] In some embodiments, a second type of activation process (e.g., as shown in Figures 6I-6K) involves providing information or selection of parameters that affect function (e.g., thresholds, degrees of activation values).

[0232] In some embodiments, a first type of activation process (e.g., as shown in FIGS. 6C, 6E, and 6G) ​​includes displaying, via a display generation component (e.g., 602A), a single selectable user interface object that, when selected via input received via one or more input devices, activates a first health-related function (e.g., the first health-related function may be activated by a single input) (720). By providing a single user interface object for activating a function, a user can activate the function without cluttering the user interface with multiple controls. Providing additional controls without cluttering the UI with additional displayed controllers enhances the usability of the computer system and makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), as well as reducing device power usage and improving battery life by allowing the user to use the computer system more quickly and efficiently.

[0233] In some embodiments, a second type of activation process (e.g., as shown in FIGS. 6I-6K) includes displaying, via a display generation component (e.g., 602A), a sequence of multiple user interfaces (e.g., 650, 652, 654) and receiving multiple user inputs received while the multiple user interfaces are displayed. Activating a health-related function using multiple user interfaces via multiple inputs ensures that the information necessary to properly activate the function is received, thereby ensuring proper activation and reducing errors. Reducing the number of required user inputs improves the usability of the computer system and makes the user device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), as well as reducing device power usage and improving battery life by allowing the user to use the computer system more quickly and efficiently.

[0234] In some embodiments, the indication that the first health-related feature is available for activation (e.g., 618A, 626A) includes an indication explaining how to activate the feature.

[0235] In some embodiments, a computer system (e.g., 600A) is associated with a first user account (e.g., an identification account, an access account, an account with information stored on a server), the first user account is associated with a first external electronic device (e.g., 600B of FIG. 8I) (e.g., a smartwatch, a tablet computer), and the first health-related function, when active, includes one or more functions operating on the computer system and one or more functions operating on the first external electronic device. In some embodiments, the computer system (e.g., 600) receives a set of one or more inputs including inputs corresponding to first user interface objects. In some embodiments, in response to receiving the set of one or more inputs including inputs corresponding to the first user interface objects, the computer system, via a display generation component (e.g., 602a), displays a functional user interface corresponding to the first health-related function, including first functional user interface objects corresponding to the one or more functions operating on the computer system and second functional user interface objects corresponding to functions of the one or more functions operating on the first external electronic device. In some embodiments, the first functional user interface object is selectable to modify one or more parameters of the first health-related function on the computer system without affecting the function of the first health-related function on the first external electronic device. In some embodiments, the second functional user interface object is selectable to modify one or more parameters of the first health-related function on the first external electronic device without affecting the function of the first health-related function on the computer system. By providing a functional user interface with separate interface objects corresponding to the operation of the health-related functions on the computer system and the first external electronic device, feedback specific to the computer system or external device is provided to the user regarding the operation of the functions.By providing improved visual feedback to the user, the computer system's usability is improved, the user-device interface is made more efficient (e.g., by assisting the user in providing appropriate input when operating / interacting with the device and reducing user errors), and in addition, the computer system's battery life is improved by allowing the user to use the computer system more quickly and efficiently, thereby reducing power usage.

[0236] In some embodiments, the process for activating a first health-related function includes displaying a settings user interface (e.g., 644) that simultaneously includes a first settings user interface object (e.g., 644D) for modifying (e.g., affecting, changing, setting) parameters of the first health-related function of the computer system and a second settings user interface object (e.g., 644D) for modifying (e.g., affecting, changing, setting) parameters of the first health-related function of a second external electronic device (e.g., a smart watch, a tablet computer, a device the same as or different from the first external electronic device). Simultaneously displaying settings user interface objects for the health-related functions of both the computer system and the external electronic device provides feedback to the user regarding the settings / parameters of the functions of both the computer system and the external device. Providing improved visual feedback to the user improves usability of the computer system and makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), as well as allowing the user to use the computer system more quickly and efficiently, thereby reducing power usage and improving the battery life of the computer system.

[0237] In some embodiments, the configuration user interface for the first health-related function is accessible from an application (e.g., an application corresponding to user interface 660 of FIG. 6N) that collects and presents data for multiple health-related functions, including the first health-related function (e.g., a health data aggregation application).

[0238] In some embodiments, the process for activating the first health-related function includes displaying a settings user interface that also includes one or more pre-entered or pre-selected values ​​for selectable parameters of the function (e.g., as shown in user interface 806 of FIGS. 8C-8D ), and an option to modify the one or more pre-entered or pre-selected values.

[0239] In some embodiments, the process for activating the first health-related function includes displaying a configuration user interface (e.g., 644, 646) that includes one or more selectable user interface objects that control parameters of the function on the computer system (e.g., 600A) and at least one external electronic device (e.g., 600B of FIG. 8I). In some embodiments, the parameters are stored on a remote server and accessible to multiple devices associated with the user of the computer system.

[0240] In some embodiments, the computer system (e.g., 600A) displays a notification (e.g., at a predetermined time, after a predetermined time interval (e.g., a set number of months)) informing the user to check one or more settings of the first health-related feature (e.g., via a settings user interface). In some embodiments, the notification is displayed within an application (e.g., a health data aggregation application) that collects and presents data for multiple health-related features, including the first health-related feature.

[0241] In some embodiments, settings of the first health-related function (e.g., any settings, including the activation state of the function) cannot be modified from a user interface that includes multiple user interface objects corresponding to the health-related function (e.g., modifying the settings of the function requires navigation to one or more different user interfaces). Preventing modification of the settings of the first health-related function from a user interface reduces the risk of inadvertent modification of the settings and / or reduces the risk that a user makes modifications without access to additional information and / or settings about the function. Reducing the risk of inadvertent operation makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), as well as reducing power usage and improving the device's battery life by allowing the user to use the computer system more quickly and efficiently.

[0242] It should be noted that the details of the processes described above with respect to method 700 (e.g., FIGS. 7A-7C ) are also applicable in an analogous manner to the methods described below. For example, method 900 optionally includes one or more of the features of the various methods described above with reference to method 700. For example, the user interface for managing health and safety functions described with reference to method 700 can be used to manage one or more features of the health application described with reference to method 900. In another example, method 1100 optionally includes one or more of the features of the various methods described above with reference to method 700. For example, the user interface for managing health and safety functions described with reference to method 700 can be used to manage one or more features of the background measurement function described with reference to method 1100. In another example, method 1300 optionally includes one or more of the features of the various methods described above with reference to method 700. For example, the user interface for managing health and safety functions described with reference to method 700 can be used to manage one or more features of the application used to measure physiological information described with reference to method 1300. In another example, method 1500 optionally includes one or more of the characteristics of the various methods described above with respect to method 700. For example, a user interface for managing health and safety functions described with reference to method 700 can be used to manage one or more functions of a health application user interface described with reference to method 1500. In another example, method 1700 optionally includes one or more of the characteristics of the various methods described above with respect to method 700. For example, a user interface for managing health and safety functions described with reference to method 700 can be used to manage one or more functions of a background measurement function described with reference to method 1700. For the sake of brevity, these details will not be repeated below.

[0243] 8A-8S show example user interfaces for managing the setup of wellness features on an electronic device according to some embodiments. The user interfaces in those figures are used to illustrate the processes described below, including the processes in FIGS. 9A-9C.

[0244] 8A shows device 600A displaying a health application overview user interface 800 (corresponding to overview interface 660 first described with reference to FIG. 6N). In FIG. 8A, device 600A displays a notification 802 in overview user interface 660 that a low cardiac health notification may be set up (e.g., enabled) on device 600A. Notification 802 includes information 802A about the low cardiac health notification and its relationship to cardiac health. Notification 802 also includes an affordance 802B for initiating setup of the low cardiac health notification.

[0245] Also in FIG. 8A, while displaying overview user interface 800, device 600A receives input 801 targeted to affordance 802B.

[0246] 8B, in response to receiving input 801, device 600A displays a setup user interface 804 corresponding to a portion of a setup (e.g., onboarding) process for activating a low cardiac health notification application. User interface 804 includes an indication 804A that a paired smartwatch can be enabled to generate low cardiac health notifications. User interface 804 also includes an affordance 804B for continuing the setup process for activating the low cardiac health notification application.

[0247] Also in FIG. 8B, while displaying user interface 804, device 600A receives input 803 targeted to affordance 804B.

[0248] In FIG. 8C, in response to receiving input 803, device 600A displays a setup user interface 806 corresponding to a portion of the setup process for activating the low cardiac health notification application.

[0249] 8C , the setup user interface 806 includes a user health details area 808 for receiving information about the user's health (e.g., gender, date of birth, height, weight). In some embodiments, the device 600A requests user input of the user's health information in the user health details area 808. In some embodiments, the device 600A pre-populates the user's health information based on stored user information, for example, from a health application, without manual user input.

[0250] The setup user interface 806 also includes a medication area 810 for receiving information regarding one or more medications the user is currently taking. The medication area 810 includes a plurality of selectable user interface objects corresponding to different medications that may be selected by the user (e.g., a user interface object 812 corresponding to a calcium channel blocker, a user interface object 814 corresponding to a beta blocker, etc.).

[0251] In some embodiments, the setup user interface 806 also includes an area for receiving additional information that may affect cardiac health, such as whether the user is currently pregnant or whether the user currently has a pre-existing medical condition.

[0252] In FIG. 8C, while displaying the setup user interface 806, the device 600A receives input 805 directed to a selection user interface object 814 corresponding to a beta blocker in the medication region 810.

[0253] In FIG. 8D, in response to receiving input 805, device 600A displays an indication 814A (e.g., a check mark, a visual marker) within user interface object 814 corresponding to a beta blocker that a beta blocker has been selected as the medication the user is currently taking.

[0254] Also in FIG. 8D, while displaying user interface 806, device 600A receives input 807 directed to affordance 816 to continue the setup process for activating the low cardiac health notification application.

[0255] 8E, in response to receiving the input 807 shown in FIG. 8D, the device 600A displays a setup user interface 818 corresponding to a portion of the setup process for activating the low cardiac health notification application. The setup user interface 818 includes an indication 818A (e.g., including a chart or list) of quintiles (e.g., very high, high, average, low, very low) into which the user's cardiac health measurement results fall. The quintiles include very high, high, average, low, and very low. The setup interface 818 also includes an affordance 818B for continuing the setup process for activating the low cardiac health notification application.

[0256] Also in FIG. 8E, while displaying onboarding user interface 818, device 600A receives input 809 targeted to affordance 818B.

[0257] 8F, in response to receiving input 809 shown in FIG. 8E, device 600A displays a setup user interface 820 corresponding to a portion of a setup process for activating a low cardiac health notification application. Setup user interface 820 includes indications of multiple factors 822A-822D (e.g., a list) that may affect (e.g., lower) the user's cardiac fitness level, including age, pregnancy, COPD and pulmonary problems, and heart disease. Setup interface 820 also includes an affordance 824 for continuing the setup process for activating the low cardiac health notification application.

[0258] Also in FIG. 8F, while displaying onboarding user interface 820, device 600A receives input 811 targeted to affordance 824.

[0259] 8G, in response to receiving input 811, device 600A displays a setup user interface 826 that includes an affordance 826A for completing the onboarding process of the low heart health notification application and enabling low heart health notifications on the paired smartwatch. The setup user interface 826 also includes an affordance 826B for exiting the onboarding process without enabling low heart health notifications on the paired smartwatch.

[0260] Also in FIG. 8G, while displaying onboarding user interface 826, device 600A receives input 813 targeted to affordance 826A.

[0261] In some embodiments, prior to enabling an application (e.g., or application feature), such as enabling a low heart health notification application, device 600A makes or receives a determination regarding whether the application is operable on device 600A or on a paired smartwatch. In some embodiments, the determination is based on regulations (e.g., government regulations) applicable to the current location of device 600A and / or an external device (e.g., device 600B), the current location being determined based on one or more sensors (e.g., GPS sensor) of device 600A and / or the paired smartwatch. In some embodiments, the determination is based on a characteristic (e.g., age) of the user.

[0262] In response to receiving input 813, device 600A determines whether a low cardiac health notification can be enabled based on the user's current age, which is compared to an age threshold (e.g., 50, 60), thereby enabling a low cardiac health notification on the external device (e.g., device 600B). In FIG. 8G, device 600A determines that the user's current age is below the age threshold.

[0263] In FIG. 8H, in response to receiving input 813 (e.g., pursuant to a determination that the user's current age is below the threshold age), device 600A activates a low cardiac health notification and displays a user interface 828 corresponding to the low cardiac health notification application.

[0264] User interface 828 includes a selectable user interface object 830 for triggering the display of measurement data corresponding to a previous heart health level measured via a paired smartwatch. User interface 828 also includes an indication 832 that low heart health notifications are currently enabled. User interface 828 also includes an information region 834 that includes multiple selectable user interface objects 834A-834D for viewing additional, more detailed information regarding heart health. User interface 828 also includes an information region 836 that includes information (e.g., basic information) regarding low heart health.

[0265] 81 shows a paired smartwatch (referred to herein as device 600B). Device 600B includes one or more biometric sensors (e.g., housed within the device's housing) for measuring cardiac health while the device is worn by a user. In some embodiments, device 600B includes one or more functions or elements of devices 100, 300, 500, and 600A.

[0266] In Figure 8I, low cardiac health notification has been enabled on device 600B via the setup process described above with reference to Figures 8A-8H. In response to determining, based on multiple cardiac health measurements obtained via one or more biometric sensors, that one or more cardiac health measurements (e.g., a specific number of sequences of previous cardiac health measurements, at least a predetermined number of measurements within the specific number of previous measurements) are in a very low quintile, device 600B displays notification 838, as in Figure 8I.

[0267] Notification 838 includes an indication 838A that the previous heart health measurement was measured as very low. Notification 838 also includes an indication 838B of a potential cause of the very low measurement. Notification 838 also includes an indication 838C that additional (e.g., more detailed) information about the very low measurement can be accessed via device 600A. Notification 838 also includes an affordance 838D for causing device 600B to display additional information about the very low heart health measurement. Notification 838 also includes an affordance 838E for causing device 600B to stop displaying the notification. Notification 838 also includes an indication 838F that notifications (e.g., whether to enable or disable notifications on device 600B, including notification 838) can be managed via a Settings application.

[0268] Figure 8J shows device 600B displaying setup user interface 826, as first described with reference to Figure 8G. However, unlike Figure 8G, in Figure 8J the user is above the age threshold permitted for use of low heart health notifications (e.g., over 50, over 60).

[0269] 8J, while displaying onboarding user interface 826, device 600A receives input 815 targeted to affordance 826A for enabling a low heart health notification on device 600B. Similar to FIG. 8G, in response to receiving input 815, device 600A determines whether the low heart health notification can be enabled based on the user's current age, which is compared to an age threshold (e.g., 50, 60), thereby enabling the low heart health notification.

[0270] 8K, in response to receiving input 815, device 600A ceases activating the low cardiac health notification and displays user interface 840. User interface 840 includes an indication 840A that the low cardiac health notification is unavailable (e.g., the low cardiac health notification cannot be activated). User interface 840 also includes an indication 840B of why the low cardiac health notification is unavailable: that the user's age is above the age threshold for enabling the low cardiac health notification.

[0271] 8L shows device 600B displaying notification 842, via display generation component 602B, indicating that there is an update regarding low heart health notifications. In FIG. 8L, device 600A and / or device 600B have determined that the user's age has reached an age threshold (e.g., 50, 60) at which low heart health notifications are not available (e.g., the user is turning 50, the user is turning 60). Upon determining that the user's age has reached the age threshold, device 600A unsubscribes the user from low heart health notifications and deactivates low heart health notifications on device 600B without user input.

[0272] In FIG. 8M, device 600B displays (in response to and / or in response to determining that the low cardiac health notification is no longer available, as described in FIG. 8L) notification 844 via display generation component 602B indicating that the low cardiac health notification is no longer available and therefore no longer active on device 600B.

[0273] Figure 8N shows device 600B displaying summary user interface 800, as initially described with reference to Figure 8A. In Figure 8N, a low cardiac health notification is activated on device 600B. Summary user interface 800 includes a user interface object 846, hereafter referred to as platter 846, that corresponds to the low cardiac health notification. Platter 846 includes an indication 846A that a very low cardiac health level has been detected via device 600B.

[0274] Also in FIG. 8N, while displaying overview user interface 800, device 600A receives input 817 directed to platter 846.

[0275] 8O, in response to receiving input 817, device 600A displays user interface 848 for a cardiac health application. User interface 848 includes graph area 852 containing a graphical indication (e.g., via a chart graph or a point graph) of the user's previous cardiac health measurements that fall within a currently selected time range, where the currently selected time range is the current date indicated via time range indication 850A. Device 600A also indicates (e.g., by visually marking or highlighting) points in the graphical indication in graph area 852 that correspond to cardiac health measurements that fall within a quintile filter of the currently selected cardiac health level.

[0276] User interface 848 also includes a heart health level indication 850B (e.g., including a heart health level quintile indication) of one or more heart health measures during the currently selected time range (or alternatively, an aggregate average of the heart health measures over the currently selected time range). In FIG. 8O, heart health level indication 850B indicates that the user's heart health level during the current date falls in the very low quintile.

[0277] User interface 848 also includes a time range selection area 854 that includes multiple selectable time ranges, including a current date option 854A, a past week option 854B, a past month option 854C, and a past year option 854D. As described above, the currently selected time range is the current date, and time range selection area 854 includes a visual indication (e.g., by visually highlighting or marking current date option 854A) that current date option 854A is the currently selected time range.

[0278] User interface 848 also includes an indication 856 of the currently selected heart health level quintile and a numerical indication 856A of the number of heart health level measurements that fall within the currently selected heart health level quintile level during the currently selected time range. In FIG. 8O, the currently selected heart health level quintile is very low, and numerical indication 856A indicates that three heart health measurements taken during the current date fall within the very low quintile.

[0279] User interface 848 also includes affordance 858 (e.g., describing "Show all filters") that, when activated, applies a display of all available heart health quintiles (e.g., very high, high, average, low, very low) as a filter for the currently displayed heart health data in graphical region 852. In FIG. 8O, while displaying user interface 848, device 600A receives input 819 (e.g., touch input, tap input) targeted to filter affordance 858.

[0280] In FIG. 8P, in response to receiving input 819, device 600A displays on user interface 848 a number of filters 860A-860E corresponding to quintiles (very high, high, average, low, and very low), with very low filter 860E being the currently selected filter.

[0281] The heart health level measurements displayed in graph area 852 include 3 measurements in the very low quintile, 1 measurement in the low quintile, 2 measurements in the average quintile, 0 measurements in the high quintile, and 0 measurements in the very high quintile. The number of measurements corresponding to each quintile is also shown via filters 860A-860E.

[0282] Device 600A also visually indicates (using particular visual characteristics, such as different background or fill colors / patterns) the heart health level measurements that fall within the currently selected quintile filter by indicating the zone or area of ​​the graph that corresponds to the currently selected quintile level in graph region 852. In Figure 8P, the currently selected quintile corresponds to filter 860E (the very low quintile), and graphical region 852 includes a visual indication 852A of the area of ​​the graph that encompasses the very low quintile.

[0283] Also in FIG. 8P, while displaying user interface 848, device 600A receives input 821 (eg, touch input, swipe input) directed to scrolling the user interface.

[0284] 8Q, in response to receiving input 821, device 600A scrolls (e.g., downwards) user interface 848. As shown in FIG. 8Q, user interface 848 further includes previous cardiac fitness level measurement information 862 (e.g., cardiac fitness level measured during the user's last walk). User interface 848 also includes information 864 related to cardiac fitness. User interface 848 also includes information 866 about how cardiac fitness is related to cardiac health.

[0285] 8R shows device 600A displaying user interface 848. In FIG. 8R, low cardiac health notifications are not enabled. Device 600A displays cardiac health notifications 868 in user interface 848 (e.g., displayed as a prompt or platter within the user interface) that include suggestions that cardiac health applications may be enabled (e.g., and the benefits to overall health of monitoring cardiac health).

[0286] In FIG. 8R, while displaying notification 868, device 600A receives input 823 directed to notification 868. In some embodiments, if the low cardiac health notification application was previously set up, device 600A enables the low cardiac health notification in response to receiving input 823 (e.g., without requiring the user to go through an onboarding process such as described above with reference to FIGS. 8A-8H). In some embodiments (e.g., if the low cardiac health notification application was previously set up), device 600A displays a setup user interface in response to receiving input 823 (e.g., via a toggle or input on an affordance that enables the notification) to enable quick (e.g., one-step) enablement of the low cardiac health notification. In some embodiments (e.g., if the low cardiac health notification application was not previously set up), device 600A initiates the onboarding process described above with reference to FIGS. 8A-8H in response to receiving input 823.

[0287] Figure 8S shows device 600A displaying a health application summary user interface 800, as first described with reference to Figure 8A. In Figure 8S, once a predetermined number of previous card health measurements have been determined to fall in the very low quintile, device 600A displays a notification 870 in summary user interface 870 indicating that a predetermined number of previous card health measurements have been determined to fall in the very low quintile.

[0288] 8S, notification 870 includes information 870A about the number of measurements that fall in the very low quintile. Notification 870 also includes a graphical representation 870B (e.g., a line graph or dot graph mapping measurements versus average cardiac fitness level) of previous measurements that fall in the very low quintile.

[0289] In some embodiments, the functionality described with respect to FIGS. 8A-8S with respect to measuring low cardiac health is instead intended to measure or track blood oxygen levels (e.g., SpO2). In some embodiments, the functionality described with respect to FIGS. 8A-8S with respect to measuring low cardiac health is instead intended to measure or track SPO2 blood oxygen levels. In some embodiments, the computer system is in communication with a blood oxygen sensor (e.g., an optical blood oxygen sensor operating in conjunction with a light source (e.g., LED)). In some embodiments, the quintiles are based on blood oxygen percentages.

[0290] 9A-9C are flow diagrams illustrating a method for managing the setup of wellness features on an electronic device according to some embodiments. Method 900 is performed in a computer system (e.g., an electronic device (e.g., 100, 300, 500, 600A, 600B)) in communication with a display generation component (e.g., 602A, 602B) (e.g., a display controller, a touch-sensitive display system, a display (e.g., integrated or connected)) and one or more input devices (e.g., a gyroscope, an accelerometer, a microphone, a touch-sensitive surface). Some operations of method 900 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0291] In some embodiments, the electronic device (e.g., 600A, 600B) is a computer system. The computer system is optionally in communication (e.g., wired communication, wireless communication) with a display generation component (e.g., 602A, 602B) and one or more input devices. The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. The one or more input devices are configured to receive input, such as a touch-sensitive surface that receives user 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. Thus, the computer system can send data (e.g., image data or video data) via a wired or wireless connection to an integrated or external display generation component to visually generate content (e.g., using a display device), and can receive input from the one or more input devices via a wired or wireless connection.

[0292] As described below, method 900 provides an intuitive way to manage and / or present health data. This method reduces the cognitive burden on a user when managing and / or presenting health data, thereby creating a more efficient human-machine interface. In the case of battery-operated computing devices, allowing a user to manage and / or present health data faster and more efficiently conserves power and increases the time between battery charges.

[0293] The computer system (e.g., 600A, 600B) (e.g., in response to an automatic determination that a set of display criteria has been met (e.g., at a predetermined time after a software update)) displays (902), via the display generation component (e.g., 602A, 602B), a set of one or more user interfaces (e.g., as shown in Figures 8A-8H and 10D-10E) corresponding to a first health-related function (e.g., an application or application function operable on the computer system or operable on an external electronic device in communication with the computer system (e.g., a heart rate tracking-related function, a medical identification function, an emergency contact function, an ambient noise level tracking function)), and the first health-related function is currently inactive (e.g., not enabled (e.g., one or more features of the function are inactive or disabled)).

[0294] Displaying a set of one or more user interfaces (e.g., as shown in Figures 8A-8H and 10D-10E) corresponding to the first health-related feature includes displaying (904) a first activation user interface (e.g., 826, 828, 1004, 1008) of the set of one or more activation user interfaces in accordance with a determination that a set of activation permission criteria (e.g., a set of criteria governing whether the first health-related feature is currently available for activation), where the set of activation permission criteria is met when the current location of the computer system (e.g., a state, provincial, or national location) meets a location-based criterion, the first activation user interface (e.g., 826, 828, 1004, 1008) of the set of one or more activation user interfaces including a first selectable user interface object (e.g., an affordance, an "Done" button, an "Activate" switch) that, when selected via input received via one or more input devices, causes the first health-related feature to be activated (906).

[0295] Displaying the set of user interfaces corresponding to the first health-related feature includes, pursuant to determining that the set of activation permission criteria are not met, displaying a notification interface (904) that includes first information corresponding to (e.g., about, pertaining to) the first health-related feature (e.g., details about the feature, information about why the feature is unavailable at the current location) and that does not include a selectable user interface object (e.g., does not include a selectable user interface object for activating the first health-related feature) that, when selected via input received via one or more input devices, activates the first health-related feature (908). Alternatively, displaying the first activation user interface or notification interface provides feedback to the user regarding whether the set of one or more location-based criteria are currently met and whether the first health-related feature may be activated at the current location. Providing improved visual feedback to the user improves usability of the computer system, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and also reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0296] In some embodiments, the set of location-based criteria includes criteria that are met when the current location of the computer system (e.g., 600A, 600B) matches 910 a predetermined set of one or more locations (e.g., locations within a predetermined state, region, or country that permits use of the first health-related feature (e.g., pursuant to relevant regulations)). Alternatively, displaying the first activation user interface or notification interface based on criteria that include matching the current location to a predetermined location provides the user with feedback regarding the current location corresponding to the predetermined location that enables activation of the first health-related feature. Providing improved visual feedback to the user improves usability of the computer system and makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), as well as allowing the user to use the computer system more quickly and efficiently, thereby reducing power usage and improving the battery life of the computer system.

[0297] In some embodiments, the first health-related function is a function for measuring or tracking SPO2 blood oxygen levels.

[0298] In some embodiments, the set of one or more activation user interfaces (e.g., as shown in FIGS. 8C-8D ) includes a second activation user interface (e.g., an interface different from or the same as the first activation user interface) that includes user interface objects (e.g., user interface objects selectable to modify the first biometric detail) for confirming first biometric details of a user of the computer system (e.g., 600A, 600B). Providing the user with interface objects for confirming the biometric details provides feedback to the user as to the current values ​​of the details stored on or accessible to the computer system. Providing improved visual feedback to the user improves operability of the computer system and makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), as well as allowing the user to use the computer system more quickly and efficiently, thereby reducing power usage and improving the battery life of the computer system.

[0299] In some embodiments, the first biometric details are details associated with a health profile of the user that includes multiple biometric details of the user (e.g., as shown in FIGS. 8C-8D). In some embodiments, the health profile was accessible to the computer system (e.g., 600A, 600B) (e.g., via a health application corresponding to user interface 800) prior to displaying the user interface corresponding to the first health-related function.

[0300] In some embodiments, the set of one or more activation user interfaces includes a third activation user interface (e.g., different from or the same as the first or second activation user interface) that includes suggestions of one or more medications that may affect the first health-related function (e.g., affecting heart rate if the function is a cardiac-related function) (e.g., as shown via 810 in FIGS. 8C-8D ). Providing the user with suggestions of one or more medications that may affect heart rate provides feedback to the user as factors that may affect the function of the first health-related system when operating on the computer system. Providing improved visual feedback to the user improves operability of the computer system, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and additionally reduces power usage and improves the battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0301] In some embodiments, the third activation user interface includes a selectable user interface object (e.g., 814) for providing input indicating whether the user is currently taking one or more medications.

[0302] In some embodiments, the set of one or more activation user interfaces includes a fourth activation user interface (e.g., an interface that is different from or the same as the first, second, or third activation user interface) that includes an indication of one or more physiological parameters that may affect the first health-related function (e.g., as shown in Figures 8C-8D).

[0303] In some embodiments, the first health-related function, when activated (e.g., as shown in FIGS. 12A-12G), includes performing one or more biometric measurements (e.g., measuring a heart rate). In some embodiments, the biometric measurements are performed automatically in the background (e.g., without explicit user request). In some embodiments, after completing the biometric measurements of the first health-related function, the computer system (e.g., 600A and / or 600B) issues a sensory indication (e.g., 838) (e.g., a visual, audio, or tactile indication, an alert) corresponding to the biometric measurement. In some embodiments, the indication is a selectable user interface object that, when selected, displays the measurement results. Issuing the sensory indication corresponding to the biometric measurement provides the user with feedback for the completed biometric measurement. Providing the user with improved visual feedback improves usability of the computer system and makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), as well as allowing the user to use the computer system more quickly and efficiently, thereby reducing power usage and improving the battery life of the computer system.

[0304] In some embodiments, the activation permission criteria include criteria that are met when the age of a user of a computer system (e.g., 600A, 600B) (e.g., as indicated by data available to the computer system or entered by the user) does not exceed a threshold age value (e.g., 50, 55, 60) (912). Including an age restriction in the activation permission criteria provides the user with feedback of the age required for activation of the first health-related criterion. Providing improved visual feedback to the user improves usability of the computer system, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and additionally reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0305] In some embodiments, while the first health-related feature is active (e.g., after activation of the feature), the computer system (e.g., 600A, 600B) detects (916) that the user's current age exceeds (e.g., is changed to exceed) a threshold age value (e.g., 50, 55, 60). In some embodiments, in response to detecting that the user's current age exceeds the threshold age value, the computer system deactivates (916) at least one feature of the first health-related feature (e.g., a component, one feature of a set of features, all features of the first health-related feature). Automatically deactivating a feature of the first health-related feature based on the user's age reduces the need for user input to perform the deactivation. Taking action when a set of conditions is met without requiring further user input enhances the usability of the device, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and also reduces the device's power usage and improves battery life by allowing the user to use the device more quickly and efficiently.

[0306] In some embodiments, deactivating at least one feature of the first health-related features includes displaying (918) via a display generation component (e.g., 602A, 602B) an indication (e.g., 844) that the deactivated at least one feature of the first health-related features is unavailable for reactivation. Displaying an indication that the first health-related feature is unavailable for reactivation provides feedback to the user regarding the status of the feature. Providing improved visual feedback to the user improves usability of the computer system, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and additionally reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0307] In some embodiments, the first health-related function, when activated, includes performing one or more biometric measurements (e.g., measuring a heart rate) (920). In some embodiments, the biometric measurements are performed automatically in the background (e.g., without explicit user request). In some embodiments, after completing the first biometric measurement of the first health-related function, the computer system (e.g., 600A, 600B) displays (922) via a display generation component (e.g., 602A, 602B) the results of the first biometric measurement, including a suggestion to categorize the results into five possible quintiles (e.g., the results may be very high, high, average, low, or very low) (e.g., as shown in FIGS. 8O-8P). Displaying the results of the biometric measurement as quintiles provides feedback to the user regarding the measurement results. By providing improved visual feedback to the user, the computer system's usability is improved, the user-device interface is made more efficient (e.g., by assisting the user in providing appropriate input when operating / interacting with the device and reducing user errors), and in addition, the computer system's battery life is improved by allowing the user to use the computer system more quickly and efficiently, thereby reducing power usage.

[0308] In some embodiments, the first biometric measurement was classified into a first quintile (e.g., the lowest of five possible quintiles). In some embodiments, after completing the first biometric measurement, the computer system (e.g., 600A, 600B) performs a second biometric measurement. In some embodiments, after completing the second biometric measurement, the computer system, via a display generation component (e.g., 602A, 602B), displays the results of the second biometric measurement, including an indication that the second biometric measurement falls into the first quintile, in accordance with a determination that the result of the second biometric measurement falls into the first quintile (e.g., the same quintile as the first result), where the indication of classifying the result of the second biometric measurement into the first quintile is different from the indication of classifying the result of the first biometric measurement into the first quintile. In some embodiments, the indication of the second biometric measurement emphasizes that the user's results remain within the first quintile across multiple measurements (e.g., "results remain very low"). By displaying an indication of the result of a second biometric that is in the first quintile that differs from the indication of the result of a first biometric measurement that was also in the first quintile, at least two measurements are in the first quintile, and feedback is provided to the user that distinguishes between the results of the two measurements even though they are in the same quintile. Providing improved visual feedback to the user improves usability of the computer system, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and additionally reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0309] In some embodiments, the result of the first biometric measurement or the result of the second biometric measurement includes an indication of the length of time that the biometric measurement of the first health-related function remains within a particular quintile (e.g., the lowest quintile).

[0310] In some embodiments, before displaying the set of one or more user interfaces corresponding to the first health-related function, the computer system (e.g., 600A, 600B) determines the current location of the computer system (e.g., via GPS, via pinging a cell phone tower, via Wi-Fi access point positioning).

[0311] In some embodiments, displaying the first activation user interface of the set of one or more activation user interfaces occurs in response to input received while displaying a user interface of an application (e.g., a health application corresponding to user interface 800) that collects and presents data regarding multiple health-related functions, including the first health-related function (e.g., a health data aggregation application). Displaying the first activation user interface of the set of one or more activation user interfaces based on input received at the health aggregation application provides the user with the ability to activate the first health-related function from the application related to health information, thereby presenting related functions of the computer system to the user and improving machine-human interaction. Presenting related functions and improving machine-human interaction improves usability of the computer system and makes the machine-user interface more efficient and effective (e.g., more effective in presenting computer operations and functions to the user).

[0312] In some embodiments, the first health-related function, when activated, includes performing one or more biometric measurements (e.g., heart rate). In some embodiments, the biometric measurements are performed automatically in the background (e.g., without explicit user request). In some embodiments, after completing the multiple biometric measurements of the first health-related function, the computer system (e.g., 600A, 600B) displays a data user interface (e.g., 848) including a graphical representation (e.g., 852) (e.g., chart, graph) of results of at least a subset of the multiple biometric measurements. In some embodiments, the graphical representation corresponds to results for an adjustable period (e.g., day, week, month, year). Displaying the data user interface including the graphical representation of results of at least a subset of the multiple biometric measurements provides feedback to the user regarding the measurement data accessible at the computer system. By providing improved visual feedback to the user, the computer system's usability is improved, the user-device interface is made more efficient (e.g., by assisting the user in providing appropriate input when operating / interacting with the device and reducing user errors), and in addition, the computer system's battery life is improved by allowing the user to use the computer system more quickly and efficiently, thereby reducing power usage.

[0313] In some embodiments, the data user interface (e.g., 848) including the graphical representation (e.g., 852) includes additional information (e.g., textual information) regarding the first health-related function and one or more selectable user interface objects for accessing the additional information corresponding to or regarding the first health-related function.

[0314] In some embodiments, the first health-related function, when activated, includes performing one or more biometric measurements (e.g., measuring a heart rate). In some embodiments, the biometric measurements are performed automatically in the background (e.g., without explicit user request). In some embodiments, after completing the third biometric measurement of the first health-related function, the computer system (e.g., 600A, 600B) displays the results of the third biometric measurement via a display generation component (e.g., 602A, 602b), where displaying the results of the third biometric measurement (e.g., very high, high, average, low, or very low) includes displaying reference measurements from a plurality of different age ranges. In some embodiments, the results page (e.g., 848) includes averages and / or statistical ranges of the biometric measurements by age group. Displaying the results of the user's biometric measurements along with the reference measurements from a plurality of different age ranges provides the user with feedback regarding measurements stored and / or accessible from the computer system. By providing improved visual feedback to the user, the computer system's usability is improved, the user-device interface is made more efficient (e.g., by assisting the user in providing appropriate input when operating / interacting with the device and reducing user errors), and in addition, the computer system's battery life is improved by allowing the user to use the computer system more quickly and efficiently, thereby reducing power usage.

[0315] In some embodiments, the baseline measurements from the plurality of different age ranges do not include measurements from age ranges above a predetermined age threshold (eg, 50, 55, 60).

[0316] In some embodiments, baseline measurements from multiple different age ranges can be configured to indicate baseline values ​​for a particular gender (e.g., male, female) or all genders combined.

[0317] It should be noted that the process details described above with respect to method 900 (e.g., FIGS. 9A-9C ) are also applicable in an analogous manner to the methods described below / above. For example, method 700 optionally includes one or more of the characteristics of the various methods described above with reference to method 900. For example, the user interface for managing health and safety functions described with reference to method 700 can be used to manage one or more functions of the health application described with reference to method 900. In another example, method 1100 optionally includes one or more of the characteristics of the various methods described above with reference to method 900. For example, the feature related to the conditional display of the setup user interface described with reference to method 900 can be applied to the setup process described with reference to method 1100. In another example, method 1300 optionally includes one or more of the characteristics of the various methods described above with reference to method 900. For example, the feature related to the conditional display of the setup user interface described with reference to method 900 can be applied during the process for setting up the biometric measurement application described with reference to method 1300. In another example, method 1500 optionally includes one or more of the characteristics of the various methods described above with respect to method 900. For example, the health information presented in the user interface described with reference to method 1500 may be based, at least in part, on whether a particular type of health application or feature may be enabled or set up, as described with reference to method 900. In another example, method 1700 optionally includes one or more of the characteristics of the various methods described above with reference to method 900. For example, the type of health information collected via background measurements described with reference to method 1700 may be based, at least in part, on whether a particular type of health application or feature may be enabled or set up, as described with reference to method 900. For the sake of brevity, these details will not be repeated below.

[0318] 10A-10V illustrate example user interfaces for managing background health measurements on an electronic device according to some embodiments. The user interfaces in those figures are used to illustrate the processes described below, including the processes in FIGS. 11A-11B.

[0319] 10A shows device 600A displaying a user interface 1000 of a companion application for device 600B, which can be used to manage settings, applications, and / or application functionality for device 600B. In FIG. 10A, user interface 1000 includes multiple user interface objects (e.g., affordances) corresponding to applications installed on device 600B, including a user interface object 1002 corresponding to a cardiac fitness level tracking application.

[0320] The cardiac fitness level tracking application causes device 600B to perform automatic / background heart rate measurements using one or more biometric sensors of device 600B without requiring manual user input for the measurements. In some embodiments, the automatic / background heart rate measurements are performed at predetermined time intervals.

[0321] In FIG. 10A, while displaying user interface 1000, device 600A receives input 1001 targeted to user interface object 1002.

[0322] 10B, in response to receiving input 1001, device 600A displays a setup user interface 1004 corresponding to the setup (e.g., onboarding) process of the cardiac fitness level tracking application. In some embodiments, setup user interface 1004 is also accessible from the health application (e.g., setup user interface 1004 is displayed as a pop-up on the user interface of the health application).

[0323] 10B, the setup user interface 1004 includes information 1004A about the functionality of the cardiac health level tracking application. The setup user interface 1004 also includes an indication 1004B that location information is used to determine whether the cardiac health level tracking application is available in the current location. The setup user interface 1004 also includes an affordance 1004C for continuing the cardiac health level tracking application onboarding process.

[0324] 10B, device 600A is in a location (e.g., a city, state, or country) where the cardiac fitness level tracking application is not available (e.g., due to regulations in the respective location). While displaying onboarding user interface 1004, device 600A receives input 1003 targeted to affordance 1004C.

[0325] 10C , in response to receiving input 1003 (e.g., and based on a determination that device 600A is in a location where the cardiac health level tracking application is not available), device 600A displays notification 1006 overlaying setup user interface 1004, including an indication 1006A that the cardiac health level tracking application is not available in the current location. Device 600A also ceases enabling the cardiac health measurement functionality.

[0326] Figure 10D again shows device 600A displaying setup user interface 1004, as first described with reference to Figure 10B. In Figure 10D, device 600A is in a location where a cardiac fitness level tracking application is available (e.g., where regulations do not prohibit its use). While displaying onboarding user interface 1004, device 600A receives input 1005 targeted to affordance 1004C.

[0327] In FIG. 10E, in response to receiving input 1005 (e.g., and based on a determination that device 600A is in a location where the cardiac health level tracking application is available), device 600A displays user interface 1008 (e.g., a settings page for the cardiac health level tracking application).

[0328] The user interface 1008 includes a selectable user interface object 1010 that indicates that the cardiac fitness level tracking feature is activated. The user interface 1008 also includes information 1012 about the cardiac fitness level tracking feature.

[0329] The user interface 1008 also includes a selectable user interface object 1014 that includes an indication of a currently selected threshold (e.g., a default threshold) for triggering a notification indicating that the measured cardiac health level information is below the selected threshold. The user interface 1008 also includes information 1016 regarding when the notification is triggered.

[0330] 10F shows device 600B displaying a user interface 1018 (e.g., a home user interface, an application user interface) that includes an application icon 1020 corresponding to a cardiac fitness level tracking application. In FIG. 10F, the cardiac fitness level tracking application is not activated on device 600B.

[0331] In FIG. 10F, while displaying user interface 1018, device 600B receives input 1007 targeted to application icon 1020.

[0332] In FIG. 10G, in response to receiving input 1007 targeted at application icon 1020, device 600B displays notification 1022 including a suggestion 1022A that the cardiac health level tracking application may be activated (e.g., the setup process for the cardiac health level tracking application may be completed on device 600A).

[0333] 10H, device 600A displays notification 1024 corresponding to a cardiac health level tracking application (e.g., while device 600B displays notification 1022). Notification 1024 includes affordance 1024A for enabling cardiac health level tracking functionality on device 600B. While displaying notification 1024, device 600A receives input 1009 targeted to affordance 1024A.

[0334] In Figure 10I, in response to receiving input 1009, device 600A displays user interface 1008 corresponding to a cardiac fitness level tracking application, as described above with reference to Figure 10E. While displaying user interface 1008, device 600A receives input 1011 directed to selectable user interface object 1010. In Figure 10I, selectable user interface object 1010 indicates that a cardiac fitness level tracking function corresponding to the cardiac fitness level tracking application is active.

[0335] In FIG. 10J, in response to receiving input 1011, device 600A displays user interface 1026 including information 1026A related to a cardiac fitness level tracking application (e.g., device 600B initiates automatic / background heart rate measurements at predetermined time intervals throughout the day).

[0336] 10J, user interface 1026 includes a selectable user interface object 1028 (e.g., a toggle, affordance) for enabling or disabling automatic / background heart rate measurement on device 600B. Selectable user interface object 1028 indicates that background heart rate measurement is currently on.

[0337] While background heart rate measurement is in the on state, user interface 1026 enables management of automatic / background heart rate measurement based on the current device state of device 600B. In some embodiments, the device state includes sleep mode and theater mode (e.g., do not disturb mode).

[0338] With respect to sleep mode, the user interface 1026 includes a selectable user interface object 1030 (e.g., a toggle, affordance) for enabling or disabling automatic / background heart rate measurements when the device 600B is in sleep mode. When the selectable user interface object 1030 is in the on state, the device 600B continues to perform automatic / background heart rate measurements (e.g., at predetermined time intervals) even when the device 600B is in sleep mode. When the selectable user interface object 1030 is in the off state, the device 600B ceases to perform automatic / background heart rate measurements (e.g., at predetermined time intervals) when the device 600B is in sleep mode. In FIG. 10J , the selectable user interface object 1030 is in the off state.

[0339] With respect to theater mode (e.g., do not disturb mode), user interface 1026 includes a selectable user interface object 1032 (e.g., a toggle, affordance) for enabling or disabling automatic / background heart rate measurements when device 600B is in theater mode. When selectable user interface object 1032 is in the on state, device 600B continues to perform automatic / background heart rate measurements (e.g., at predetermined time intervals) even when device 600B is in theater mode. When selectable user interface object 1032 is in the off state, device 600B ceases to perform automatic / background heart rate measurements (e.g., at predetermined time intervals) when device 600B is in theater mode. In FIG. 10J , selectable user interface object 1032 is in the off state.

[0340] In FIG. 10J, while displaying user interface 1026 with selectable user interface object 1030 corresponding to the off sleep mode, device 600A receives input 1013 targeted to selectable user interface object 1030.

[0341] 10K, in response to receiving input 1013, device 600A indicates, via selectable user interface object 1030, that automatic / background heart rate measurement is enabled while in sleep mode, enabling background heart rate measurement of device 600B while device 600B is in sleep mode. In FIG. 10K, automatic / background heart rate measurement remains disabled during theater mode, so that device 600B performs automatic / background heart rate measurement while device 600B is not in sleep mode or theater mode, or while in sleep mode, but does not perform automatic / background heart rate measurement while device 600B is in theater mode.

[0342] Also in FIG. 10K, while displaying user interface 1026 with selectable user interface object 1032 corresponding to theater mode in the off state, device 600A receives input 1015 targeted to selectable user interface object 1032.

[0343] 10L, in response to receiving input 1015, device 600A indicates, via selectable user interface object 1032, that automatic / background heart rate measurement is enabled while in theater mode and enables automatic / background heart rate measurement of device 600B while device 600B is in theater mode. In the embodiment of FIG. 10L, automatic / background heart rate measurement is always enabled, regardless of whether device 600B is in sleep mode and / or theater mode.

[0344] Also in FIG. 10L, while user interface 1026 and automatic / background heart rate measurement are enabled, device 600A receives input 1017 directed to selectable user interface object 1028.

[0345] 10M, in response to receiving input 1017, device 600A indicates via selectable user interface object 1026 that automatic / background heart rate measurements have been disabled. Device 600A ceases to display selectable user interface object 1030 corresponding to sleep mode and selectable user interface object 1032 corresponding to theater mode. Device 600A also disables automatic / background heart rate measurements on device 600B, preventing device 600B from performing any automatic / background heart rate measurements.

[0346] 10N-10P show corresponding processes for enabling or disabling automatic / background heart rate measurement using device 600B (instead of using device 600A). In FIG. 10N, device 600B displays a user interface 1034 for a device settings application, which includes multiple user interface objects (e.g., platters) corresponding to applications installed on device 600B, including a user interface object 1036 corresponding to a cardiac fitness level tracking application.

[0347] Also in FIG. 10N, while displaying user interface 1034, device 600B receives input 1019 directed to user interface object 1036.

[0348] 10O, in response to receiving input 1019, device 600B displays a cardiac fitness level tracking application user interface 1038, which corresponds to user interface 1008 described above with reference to FIG. 10E. Like user interface 1008, user interface 1038 includes a selectable user interface object 1040 (e.g., an affordance) that indicates that cardiac fitness level tracking functionality is activated on device 600B. User interface 1038 also includes a selectable user interface object 1042 that includes an indication of the currently selected threshold (e.g., a default threshold) for triggering a heart rate notification.

[0349] Also in FIG. 10O, while displaying user interface 1038, device 600B receives input 1021 directed to selectable user interface object 1040.

[0350] 10P, in response to receiving input 1021, device 600B displays user interface 1044, which corresponds to user interface 1026 described above with reference to FIG. 10J. Like user interface 1026, user interface 1044 includes information 1044A related to the cardiac fitness level tracking application, specifically, that automatic / background heart rate measurements are initiated by device 600B (e.g., at predetermined time intervals throughout the day).

[0351] Similar to user interface 1026, user interface 1044 includes a selectable user interface object 1046 (e.g., a toggle, affordance) for enabling or disabling automatic / background heart rate measurement on device 600B. In FIG. 10P, selectable user interface object 1046 indicates that automatic / background heart rate measurement is currently on (e.g., the toggle is in the on position).

[0352] Similar to user interface 1026, while automatic / background heart rate measurement is in the on state, user interface 1044 also enables management of automatic / background heart rate measurement based on the current device state of device 600B operating the automatic / background heart rate measurement. In FIG. 10P, the device states include sleep mode and theater mode (e.g., do not disturb mode).

[0353] With respect to sleep mode, the user interface 1044 includes a selectable user interface object 1048 (e.g., a toggle, affordance) for enabling or disabling automatic / background heart rate measurements when the device 600B is in sleep mode. When the selectable user interface object 1048 is in the on state, the device 600B continues to perform automatic / background heart rate measurements (e.g., at predetermined time intervals) even when the device 600B is in sleep mode. When the selectable user interface object 1048 is in the off state, the device 600B ceases to perform automatic / background heart rate measurements (e.g., at predetermined time intervals) when the device 600B is in sleep mode. In FIG. 10P, the selectable user interface object 1048 is in the on state.

[0354] With respect to theater mode (e.g., do not disturb mode), user interface 1044 includes a selectable user interface object 1050 (e.g., a toggle, affordance) for enabling or disabling automatic / background heart rate measurements when device 600B is in theater mode. When selectable user interface object 1050 is in the on state, device 600B continues to perform automatic / background heart rate measurements (e.g., at predetermined time intervals) even when device 600B is in theater mode. When selectable user interface object 1050 is in the off state, device 600B ceases to perform automatic / background heart rate measurements (e.g., at predetermined time intervals) when device 600B is in theater mode. In FIG. 10P, selectable user interface object 1050 is in the off state.

[0355] Figure 10Q shows device 600B displaying user interface 1008, as described above with reference to Figure 10E. In Figure 10Q, while displaying user interface 1008, device 600B receives input 1023 directed to selectable user interface object 1014.

[0356] 10R, in response to receiving input 1023, device 600B displays a user interface 1052 for changing the heart rate BPM threshold for triggering a notification, as illustrated via information 1052A. User interface 1052 also includes information 1052B regarding a typical, average, or normal heart rate.

[0357] User interface 1052 also includes a number of threshold options 1054A-1054E. In FIG. 10R, the threshold options include an off option 1054A (which, when selected, does not enable notifications), a first threshold option 1054B (e.g., 40 BPM), a second threshold option 1054C (e.g., 45 BPM), a third threshold option 1054D (e.g., 50 BPM), and a fourth threshold option 1054E (e.g., 55 BPM). Also in FIG. 10R, marker 1056 indicates that third threshold option 1054D is the currently selected heart rate threshold.

[0358] In FIG. 10S, while displaying a user interface 1052 having a currently selected heart rate threshold that is the third threshold option 1054D (e.g., 50 BPM), the device 600A receives an input 1025 directed to the fourth threshold option 1054E (e.g., 55 BPM).

[0359] In FIG. 10T, in response to receiving input 1025 directed to the fourth threshold option 1054E, device 600B displays notification 1056 indicating that the newly selected threshold (e.g., 55 BPM) will cause more frequent heart rate notifications (e.g., if a high heart rate threshold is set, a larger proportion of the automatic / background heart rate measurements performed by device 600B will fall within the high heart rate threshold, resulting in a greater number of notifications, compared to if a low heart rate threshold is set).

[0360] 10U-10V show corresponding user interfaces for changing the heart rate notification threshold of device 600B. In FIG. 10U, device 600B displays user interface 1038 of a cardiac fitness level tracking application, as described above with reference to FIG. 10O. While displaying user interface 1038, device 600B receives input 1027 relative to selectable user interface object 1042, which includes an indication of the currently selected threshold (e.g., the default threshold) for triggering heart rate notification.

[0361] In Figure 10V, in response to receiving input 1027, device 600B displays a user interface 1058 for changing the heart rate BPM threshold, similar to user interface 1052 described above with reference to Figure 10R. Like user interface 1052, user interface 1052 includes information 1052B regarding a typical, average, or normal heart rate.

[0362] Also, similar to user interface 1052, user interface 1058 includes multiple threshold options 1060A-1060E. In FIG. 10V, as in FIG. 10R, the threshold options include an off option 1060A (which, when selected, does not enable notifications), a first threshold option 1060B (e.g., 40 BPM), a second threshold option 1060C (e.g., 45 BPM), a third threshold option 1060D (e.g., 50 BPM), and a fourth threshold option 1060E (e.g., 55 BPM). Also in FIG. 10V, marker 1062 indicates that fourth threshold option 1060E is the currently selected heart rate threshold. As discussed above with reference to user interface 1052 of FIG. 10S, different heart rate thresholds for triggering heart rate notifications can be selected via user interface 1058.

[0363] In some embodiments, the heart rate level tracking function of Figures 10A-10V is instead a blood oxygen level tracking function. In some embodiments, the computer system is in communication with a blood oxygen sensor (e.g., an optical blood oxygen sensor operating in conjunction with a light source (e.g., an LED)). In some embodiments, the threshold is a percentage of blood oxygen. In some embodiments, the heart rate level tracking function of Figures 10A-10V is instead a function that measures or tracks VO2max (e.g., maximal oxygen consumption, the maximum rate of oxygen consumption measured during incremental exercise).

[0364] 11A-11B are flow diagrams illustrating a method for managing background health measurements on an electronic device according to some embodiments. Method 1100 is performed in a computer system (e.g., an electronic device (e.g., 100, 300, 500, 600A, 600B)) in communication with a display generation component (e.g., 602A, 602B) (e.g., a display controller, a touch-sensitive display system, a display (e.g., integrated or connected)) and one or more input devices (e.g., a gyroscope, an accelerometer, a microphone, a touch-sensitive surface). Some operations of method 1100 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0365] In some embodiments, the electronic device (e.g., 600A, 600B) is a computer system. The computer system is optionally in communication (e.g., wired communication, wireless communication) with a display generation component (e.g., 602A, 602B) and one or more input devices. The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. The one or more input devices are configured to receive input, such as a touch-sensitive surface that receives user 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. Thus, the computer system can send data (e.g., image data or video data) via a wired or wireless connection to an integrated or external display generation component to visually generate content (e.g., using a display device), and can receive input from the one or more input devices via a wired or wireless connection.

[0366] As described below, method 1100 provides an intuitive way to manage and / or present health data. This method reduces the cognitive burden on a user when managing and / or presenting health data, thereby creating a more efficient human-machine interface. In the case of battery-operated computing devices, allowing a user to manage and / or present health data faster and more efficiently conserves power and increases the time between battery charges.

[0367] The computer system (e.g., 600A, 600B), via a display generation component (e.g., 602A, 602B), displays (1102) a collection of one or more configuration user interfaces (e.g., 1004, 1008, 1026, 1038, 1044, 1052, 1058) of a first health-related function (e.g., a tracking (e.g., data tracking, data collection) application or application function (e.g., heart rate tracking-related function, ambient noise level tracking function) operable on the computer system or on an external electronic device in communication with the computer system), the first configuration user interface The device includes one selectable user interface object, and the first health-related tracking feature is currently configured to track (e.g., automatically track, track without requiring explicit user input) a first set of health-related data (e.g., heart rate data, blood pressure data, ambient noise data) while the computer system is in a first mode (e.g., sleep mode, locked mode, low power mode, mode corresponding to a predetermined time of day, do not disturb mode (e.g., theater DND mode)) and a second mode different from the first mode (e.g., default mode, mode operating when the first mode is not operating).

[0368] A computer system (e.g., 600A, 600B) receives (1108) one or more sets of inputs, the one or more sets of inputs including one or more sets of inputs that include inputs corresponding to first selectable user interface objects (e.g., 1028, 1030, 1032) (e.g., toggle switches, check boxes, drop-down menus).

[0369] In response to one or more sets of inputs, the computer system (e.g., 600A, 600B) configures (1110) the first health-related tracking function to not track (not automatically track (e.g., not track without user input), not track in the background) the first set of health-related data while the computer system is in the first mode (e.g., as in FIG. 10J ), while continuing to track the first set of health-related data while the computer system is in the second mode. By configuring the first health-related tracking function to not track in the first mode while continuing to track in the second mode, a user can configure the computer system to automatically and selectively perform the tracking function without manually activating and deactivating the function. Performing optimized operations when the set of conditions is met without requiring further user input improves device usability, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user error), and also reduces power usage and improves device battery life by allowing the user to use the device more quickly and efficiently.

[0370] In some embodiments, the first health-related tracking feature is a heart rate tracking feature.

[0371] In some embodiments, a set of one or more configuration user interfaces (e.g., 1004, 1008, 1026, 1038, 1044, 1052, 1058) for a first health-related tracking feature includes selectable affordances (e.g., 1028, 1046) for changing (e.g., activating or deactivating) an activation state of the first health-related tracking feature and information about the first health-related tracking feature.

[0372] In some embodiments, a collection of one or more configuration user interfaces (e.g., 1004, 1008, 1026, 1038, 1044, 1052, 1058) of health-related tracking features is accessible from an application for configuring one or more features of an external electronic device (e.g., 600B) (e.g., a smartwatch) paired with the computer system (e.g., 600A).

[0373] In some embodiments, a collection of one or more configuration user interfaces (e.g., 1004, 1008, 1026, 1038, 1044, 1052, 1058) for health-related tracking features is accessible from an application (e.g., a health data aggregation application) that collects and presents data for multiple health-related features, including the first health-related feature (e.g., a health application corresponding to user interface 800 of FIG. 8A). In some embodiments, the collection of one or more configuration user interfaces is displayed as a pop-up overlaid on the user interface of the application that collects and presents health data.

[0374] In some embodiments, prior to displaying a first configuration user interface of the set of one or more configuration user interfaces (e.g., 1004, 1008, 1026, 1038, 1044, 1052, 1058) for the first health-related tracking feature, the computer system (e.g., 600A, 600B) receives data from an external electronic device (e.g., a smartwatch paired with the computer system) in communication with the computer system indicating that a process for configuring the first health-related tracking feature (e.g., a process for activation, a process for initially configuring or setting up a feature) has begun at the external electronic device. In some embodiments, in response to receiving the data, the computer system displays a notification (e.g., 1022) indicating that the process for configuring the first health-related tracking feature can be completed at the computer system. In some embodiments, selection of the notification causes display of a second configuration user interface (e.g., the same as or different from the first configuration user interface) of the set of one or more configuration user interfaces for the first health-related tracking feature. Feedback is provided to the user regarding the process that has been initiated and can be completed using the computer system by displaying a notification indicating that the process for configuring the first health-related tracking feature can be completed on the computer system. Providing improved visual feedback to the user improves usability of the computer system, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and additionally reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0375] In some embodiments, after displaying a notification (e.g., 1022) indicating that a process for configuring a first health-related tracking feature can be completed on a computer system (e.g., 600A), the computer system receives one or more sets of inputs that complete the process for configuring the first health-related tracking feature on the computer system (e.g., as shown in FIG. 10H ), where the process for configuring the first health-related tracking feature includes (e.g., automatically) enabling the first health-related tracking feature to perform the first health-related tracking feature without requiring further user input (e.g., automatically performing background measurements). By enabling the first health-related tracking feature to perform tracking operations without requiring further user input, the user can authorize the computer system to perform the operations without requiring further user input. Performing operations without requiring further user input improves device usability, making the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and additionally reduces device power usage and improves battery life by allowing the user to use the device more quickly and efficiently.

[0376] In some embodiments, the set of one or more configuration user interfaces (e.g., 1004, 1008, 1026, 1038, 1044, 1052, 1058) includes a second selectable user interface object (e.g., 1028, 1046) that, when selected, disables the performance of a tracking operation (e.g., measurement) of the first health-related tracking feature without user input (e.g., without user input manually activating the tracking feature). Validating the user interface object to disable the performance of a tracking operation of the first health-related tracking feature without user input provides the user with the option to disable the feature, thereby conserving system resources. Conserving system resources improves the usability of the computer system, provides a more efficient user-device interface (e.g., by limiting unnecessary operations), and further reduces power usage and improves the battery life of the computer system by allowing the user to use the computer system more efficiently.

[0377] In some embodiments, the first health-related tracking feature is configured to perform tracking operations only in response to user input (e.g., the first health-related tracking feature does not perform automatic and / or background tracking operations). Performing the tracking operations of the first health-related tracking feature only in response to user request conserves system resources. Conserving system resources improves the usability of the computer system, provides a more efficient user-device interface (e.g., by limiting unnecessary operations), and further reduces power usage and improves the battery life of the computer system by allowing the user to use the computer system more efficiently.

[0378] In some embodiments, while the first health-related tracking feature is inactive, a computer system (e.g., 600A, 600B) receives a user request to activate the first health-related tracking feature. In some embodiments, in response to the request, the computer system configures the first health-related tracking feature to track in both the first mode (e.g., corresponding to 1030, 1048) and the second mode (e.g., corresponding to 1032, 1050).

[0379] In some embodiments, the computer system (e.g., 600A, 600B) is in a first mode (e.g., a mode in which no tracking occurs) (1106) when the current time corresponds to a predetermined time period (e.g., a particular time of day, a time of day identified as corresponding to a sleep period). Disabling tracking during predetermined times of the day conserves system resources. Conserving system resources improves the usability of the computer system, provides a more efficient user-device interface (e.g., by limiting unnecessary activity), and allows the user to use the computer system more efficiently, thereby reducing power usage and improving the battery life of the computer system.

[0380] In some embodiments, a computer system (e.g., 600A, 600B) receives (1112) a first type of input (e.g., input detected by an accelerometer indicating movement of the computer system consistent with a predetermined movement pattern). In some embodiments, in response to receiving the input of the first type (1114), and following a determination that the computer system is not in the first mode (e.g., following a determination that the device is in another mode), the computer system increases (1116) the brightness of a display generation component (e.g., 602A, 602B) (e.g., including activating the component from an inactive state). In some embodiments, in response to receiving the input of the first type (1114), and following a determination that the computer system is in the first mode, the computer system ceases increasing (1118) the brightness of the display generation component. In some embodiments, the first mode is a “theater mode,” and the brightness of the display screen is more limited than if the mode were not active. Selectively brightening the display generation component conserves system resources and prevents unintended brightness. Conserving system resources can improve the usability of a computer system, provide a more efficient user-device interface (e.g., by limiting unnecessary operations), and allow users to use the computer system more efficiently, thereby reducing power usage and improving battery life of the computer system.

[0381] In some embodiments, a set of one or more configuration user interfaces (e.g., 1004, 1008, 1026, 1038, 1044, 1052, 1058) includes a third selectable user interface object that, when selected, sets a threshold for the first set of health-related data (e.g., as shown at 1052 and 1058), which causes the computer system (e.g., 600A, 600B) to issue a sensory notification (e.g., 838) upon detecting 1104 that the health-related tracking function exceeds the threshold. In some embodiments, the computer system receives 1120 one or more sets of user inputs, including inputs corresponding to the third selectable user interface object. In some embodiments, in response to receiving a set of one or more user inputs including inputs corresponding to the third selectable user interface object (1122), following a determination that the set of one or more inputs causes the threshold to be configured to a predetermined value (e.g., a value (e.g., one of a plurality of predetermined values) that is likely to result in frequent notifications), the computer system displays (1124) an indication that frequent sensory notifications may occur. In some embodiments, in response to receiving a set of one or more user inputs including inputs corresponding to the third selectable user interface object (1122), following a determination that the set of one or more inputs causes the threshold to be set to a value that is not a predetermined value, the computer system ceases displaying (1126) the indication that frequent sensory notifications may occur. Conditionally displaying an indication that frequent sensory notifications may occur based on the setting of the threshold provides feedback to the user regarding the configuration of the first health-related tracking feature. By providing improved visual feedback to the user, the computer system's usability is improved, the user-device interface is made more efficient (e.g., by assisting the user in providing appropriate input when operating / interacting with the device and reducing user errors), and in addition, the computer system's battery life is improved by allowing the user to use the computer system more quickly and efficiently, thereby reducing power usage.

[0382] In some embodiments, the first health-related tracking function is a blood oxygen level tracking function. In some embodiments, the computer system is in communication with a blood oxygen sensor (e.g., an optical blood oxygen sensor operating in conjunction with a light source (e.g., an LED)). In some embodiments, the threshold is a percentage of blood oxygen. In some embodiments, the first health-related function is a function for measuring or tracking VO2max (e.g., maximal oxygen consumption, the maximum rate of oxygen consumption measured during incremental exercise).

[0383] It should be noted that the details of the processes described above with respect to method 1100 (e.g., FIGS. 11A-11B) are also applicable in an analogous manner to the methods described above and below. For example, method 700 optionally includes one or more of the features of the various methods described above with reference to method 1100. For example, the user interface for managing health and safety functions described with reference to method 700 can be used to manage one or more of the background measurement functions described with reference to method 1100. In another example, method 900 optionally includes one or more of the features of the various methods described above with reference to method 1100. For example, the feature related to conditional display of the setup user interface described with reference to method 900 can be applied to the setup process described with reference to method 1100. In another example, method 1300 optionally includes one or more of the features of the various methods described above with reference to method 1100. For example, the setup user interface described with reference to method 1100 can be used to set up a health application used for biometric measurements described with reference to method 1300. In another example, method 1500 optionally includes one or more of the characteristics of the various methods described above with respect to method 1100. For example, the health information presented in the user interface described with reference to method 1500 may be based, at least in part, on health measurements from an application configured via the setup user interface described with reference to method 1100. In another example, method 1700 optionally includes one or more of the characteristics of the various methods described above with respect to method 1100. For example, the background health measurements described with reference to method 1700 may be enabled via a health application configured via the setup user interface described with reference to method 1100. For brevity, these details will not be repeated below.

[0384] 12A-12N and 12Q-12AG show example user interfaces for managing biometric measurements taken using an electronic device according to some embodiments. 12O and 12P are flow diagrams illustrating methods for managing prompts and measurements based on location and movement data, respectively, according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including the process of FIG. 13.

[0385] 12A shows device 600B displaying a home user interface 1200. In some embodiments, device 600B includes a collection of one or more biometric sensors (e.g., a peak oxygen consumption level sensor, a heart rate sensor). In some embodiments, device 600B includes a collection of one or more sensors (e.g., a gyroscope, an accelerometer, a microphone, a location sensor, a GPS sensor).

[0386] 12A, the heart rate tracking application first described above with reference to FIG. 8A has been installed on device 600B. User interface 1200 includes an application icon 1202 corresponding to the heart rate tracking application. While displaying application icon 1202, device 600B receives input 1201 targeted to application icon 1202.

[0387] In FIG. 12B, in response to receiving input 1201, device 600B displays a measurement user interface 1204 for a heart rate tracking application before a heart rate measurement is initiated.

[0388] Prior to initiating a heart rate measurement, device 600B displays measurement instructions 1206 on measurement user interface 1204 that show (e.g., explain, coach) the user how to perform a heart rate measurement with device 600B. In FIG. 12B, measurement instructions 1206 inform the user to "remain as still as possible during the measurement." In the embodiment of FIGS. 12A-12P, heart rate measurements are most accurate when the user minimizes movement of their arm (and device 600B) and maintains an ideal arm orientation with the user's wrist pointing down and the display generation component 602B of device 600B pointing up.

[0389] Prior to initiating the heart rate measurement, the device 600B also displays at least a portion of a measurement animation 1208 on the measurement user interface 1204 that animates the measurement process. As shown in Figures 12C-12E, the measurement animation 1208 includes a plurality of shapes (e.g., ripples, lines) that initially have a first visual characteristic (e.g., a first color) and an increasing portion of the plurality of shapes transition to have a second visual characteristic (e.g., a second color) that is different from the first visual characteristic as the measurement progresses until all of the plurality of shapes have the second visual characteristic when the measurement is complete.

[0390] 12B, measurement user interface 1204 also includes affordance 1210 for initiating a heart rate measurement. While displaying measurement user interface 1204 with affordance 1210, device 600 receives input 1203 targeted to affordance 1210 for initiating a heart rate measurement on device 600B.

[0391] 12C-12E show device 600B displaying measurement user interface 1204 while a heart rate measurement is being performed via device 600B. In some embodiments, the heart rate measurement process includes collecting heart rate data (e.g., multiple discrete sets (e.g., samples) of heart rate data) over a predetermined period of time (e.g., 10 seconds, 15 seconds, 30 seconds). In FIGS. 12C-12E, the predetermined period for completing the heart rate measurement is 15 seconds.

[0392] In response to receiving input 1210 to initiate a heart rate measurement, device 600B displays measurement user interface 1204, as in Figure 12C. In some embodiments, while the heart rate measurement is being performed, device 600B displays a time counter 1212 in measurement user interface 1204 that indicates the time remaining to complete the current heart rate measurement.

[0393] In Figure 12C, there are 15 seconds remaining (because the measurement just started), and in Figure 12C, the measurement animation 1208 includes a first visual characteristic (e.g., a first color) because the measurement just started.

[0394] In Figure 12D, there are 10 seconds remaining (because the measurement is progressing). Also in Figure 12D, some of the shapes in measurement animation 1208 have transitioned from a first visual characteristic to a second visual characteristic while the measurement has progressed, so that measurement animation 1208 partially includes the first visual characteristic (e.g., a first color) and partially includes the second visual characteristic (e.g., a second color).

[0395] 12E, there are 3 seconds remaining (because the measurement is progressing and is nearly complete). Also in FIG. 12E, because the measurement is nearly complete and most of the shapes in measurement animation 1208 have transitioned from the first visual characteristic to the second visual characteristic, a larger portion of measurement animation 1208 includes more of the second visual characteristic (e.g., second color) than the first visual characteristic (e.g., first color), and partially includes the second visual characteristic (e.g., second color).

[0396] FIG. 12F illustrates device 600B displaying results user interface 1214 upon detecting (eg, determining) that the heart rate measurements illustrated in FIGS. 12C-12E have been successfully completed.

[0397] The results user interface 1214 includes a result suggestion 1216. In FIG. 12F, the result suggestion 1216 indicates that the measured heart rate was 87 BPM. The results user interface 1214 also includes an affordance 1220 for causing the device 600B to stop displaying the results user interface 1214. The results user interface 1214 also includes a suggestion 1218 that more detailed information about the measurement can be viewed via a health application of the device 600A (e.g., via the health application's user interface 660 first described above with reference to FIG. 6N).

[0398] 12G shows device 600B displaying a results user interface 1214 for the completed heart rate measurement upon detecting (e.g., determining) that the heart rate measurement shown in FIGS. 12C-12E was completed successfully, and the completed heart rate measurement was taken in an abnormal condition, such as a high altitude environment. In some embodiments, device 600B detects (e.g., determines) the presence of the abnormal condition (e.g., high altitude) via a collection of one or more sensors (e.g., location sensor, GPS sensor).

[0399] 12G, because the heart rate measurement was taken in a high altitude environment, device 600B displays a suggestion 1222 in the results user interface 1214 informing the user that the measurement was taken in a high altitude environment. In FIG. 12G, suggestion 1222 states, "Measurement taken in a high altitude environment."

[0400] 12H-12K show device 600B displaying measurement user interface 1204 while another heart rate measurement is being performed via device 600B.

[0401] 12H, the device 600B displays the measurement user interface 1204 with the measurement just started, and the time counter 1212 therefore indicates that 15 seconds remain to complete the current heart rate measurement.

[0402] In FIG. 12I, as a heart rate measurement is in progress, the time counter 1212 indicates that 12 seconds remain to complete the current heart rate measurement.

[0403] While the heart rate measurement is in progress, the device 600B detects (e.g., determines) one or more sets of sensor data via a set of one or more sensors (e.g., gyroscope, accelerometer). In some embodiments, the one or more sets of sensor data include a first set of sensor data (e.g., accelerometer and / or gyroscope data) that indicates a change in movement and / or orientation of the device 600B. In some embodiments, the one or more sets of sensor data include a second set of sensor data (e.g., accelerometer and / or gyroscope data) that indicates a change in position (e.g., a change in spatial position and / or spatial orientation) of the device 600B or a movement of the device 600B that causes a change in position (e.g., a change or rate of change of position). As described above, heart rate measurements are most accurate when a user minimizes movement of their arm (and device 600B) and maintains an ideal arm position (e.g., arm orientation) with the user's wrist facing down and the display generation component 602B of the device 600B facing up.

[0404] In FIG. 12I , pursuant to determining (e.g., using the detected position of device 600B and / or the detected movement of device 600B) that the sensor data (e.g., data indicating location) meets the prompt criteria, device 600B displays a prompt 1224 (e.g., an instruction prompt, a coaching prompt) on measurement user interface 1204 indicating to the user that user action (e.g., changing the position of device 600B and / or reducing / stopping the movement of device 600B) is required to complete the measurement process. Specifically, in FIG. 12I , device 600B detects that the device is in a non-ideal position (e.g., a predetermined position that causes the prompt criteria to be met) and issues a position-related prompt. In FIG. 12I , prompt 1224 instructs the user to "keep your wrist flat and your watch facing up."

[0405] FIG. 12J illustrates a device 600B that displays a different type of prompt (eg, a different version of the prompt) on the measurement user interface 1204 than the prompt 1224 described above with reference to FIG. 12I.

[0406] In Figure 12J, as the heart rate measurement is in progress, the time counter 1212 indicates that 10 seconds remain to complete the current heart rate measurement. In Figure 12J, pursuant to determining that the sensor data (e.g., data indicative of movement) meets a set of prompt criteria, the device 600B displays a prompt 1226 on the measurement user interface 1204 indicating to the user that user action (e.g., a change in the position of the device 600B and / or a decrease / stop in the movement of the device 600B) is required to complete the measurement process. Specifically, in Figure 12J, the device 600B detects that the device has moved a non-ideal amount (e.g., an amount exceeding a threshold) and issues a movement-related prompt. In Figure 12J, the prompt 1226 indicates to the user to "stay still."

[0407] In some embodiments, after detecting that the second set of sensor data satisfies a set of prompt criteria such as in FIG. 12I or 12J, in response to detecting that the sensor data (e.g., location data and / or movement data) no longer satisfies the set of prompt criteria (e.g., because the user has modified the location of device 600B and / or reduced / stopped the movement of the device) within a predetermined time period (e.g., within 0.5 seconds, within 1 second) the device 600B continues the heart rate measurement process without interruption.

[0408] In some embodiments, as shown in FIG. 12K, device 600B displays a second prompt on measurement user interface 1204 pursuant to again determining that the sensor data meets the set of prompt criteria (based on the detected (e.g., determined) position of device 600B and / or the detected (e.g., determined) movement of device 600B). Specifically, in FIG. 12K, prompt 1228 instructs the user to "keep your wrist flat." In some embodiments, device 600B issues a different prompt if the same non-ideal condition (e.g., non-ideal position or movement) persists for longer than a predetermined time to provide better feedback to the user that the condition persists. In some embodiments, device 600B issues a different prompt only if a different condition occurs, such as a position condition followed by a movement condition.

[0409] In some embodiments, while the heart rate measurement is in progress, device 600B detects (e.g., determines) that a first set of sensor data (e.g., accelerometer and / or gyroscope data indicative of movement and / or changes in position) satisfies a first set of stopping criteria (e.g., criteria that cause device 600B to stop the measurement process).

[0410] In Figure 12L, pursuant to detecting that the first set of sensor data satisfies the first set of stopping criteria, device 600B ceases displaying measurement user interface 1204 without completing the measurement. Specifically, device 600B detects that a non-ideal position and non-ideal degree of movement of the device persist during the heart rate measurement of Figures 12H-12K and aborts the measurement before completion. Device 600B stops the measurement without displaying the results and instead displays user interface 1230 (e.g., a notification, prompt).

[0411] User interface 1230 includes an indication 1232 that the measurement failed and could not be completed. User interface 1230 also includes an indication 1234 of the reason for the failed measurement (e.g., one or more causes that caused triggered device 600B to stop the measurement process without completing the measurement process). User interface 1230 also includes an affordance 1236 for causing device 600B to stop displaying user interface 1230.

[0412] 12L, while displaying user interface 1230, device 600B receives input 1205 directed to affordance 1205. In some embodiments, in response to receiving input 1205, device 600B displays measurement user interface 1204 of FIG.

[0413] As described above, after displaying a prompt (e.g., prompt 1224, prompt 1226, prompt 1228) during a heart rate measurement (e.g., because the second set of sensor data met the prompt criteria during the measurement), as described above, after displaying a prompt (e.g., prompt 1224, prompt 1226, prompt 1228) during a heart rate measurement (e.g., because the second set of sensor data met the prompt criteria during the measurement), device 600B continues the heart rate measurement process in response to detecting (e.g., determining) that the second set of sensor data no longer meets the set of prompt criteria (e.g., within a predetermined time period (e.g., within 0.5 seconds, within 1 second)).

[0414] In FIG. 12L, the set of stopping criteria is determined by a discrete set of data (e.g., N M ) sampling window, M ) exceeds a threshold. In some embodiments, the first set of sensor data is accelerometer data, and the set of stopping criteria is satisfied when at least five distinct windows of accelerometer data from a sampling window of the distinct sets of data exceed a threshold (e.g., five distinct sets from a sampling window of five distinct sets).

[0415] In some embodiments, device 600B analyzes accelerometer data on three axes: x, y, and z. In some embodiments, if the maximum value of any of the three axes from the accelerometer data exceeds a threshold within a given sampling window (e.g., 1 second), device 600B generates a prompt (e.g., prompt 1224 in FIG. 12I , prompt 1226 in FIG. 12J , prompt 1228 in FIG. 12K ). In some embodiments, each sampling window (e.g., 1 second) is spaced apart by an interval shorter than the length of the sampling window (e.g., 0.5 seconds apart) so that the sampling windows overlap.

[0416] In some embodiments, if device 600B detects (e.g., determines) that a predetermined number (e.g., 5) within a predetermined set (e.g., 5) of samples exceeds a threshold (e.g., 5 samples from a predetermined set of 5 samples), device 600B automatically aborts the current heart rate measurement session. In some embodiments, this corresponds to device 600B generating a predetermined number (e.g., 5) of prompts (e.g., prompt 1224 of FIG. 12I, prompt 1226 of FIG. 12J, and / or prompt 1228 of FIG. 12K). Upon aborting the heart rate measurement session, device 600B displays user interface 1230 as shown in FIG. 12L.

[0417] In some embodiments, device 600B aborts the current heart rate measurement session if (e.g., only if) at least a predetermined number of detected samples that exceed the threshold are from consecutive sampling windows. In some embodiments, device 600B does not abort the heart rate measurement session if at least a predetermined number of detected samples that exceed the threshold are detected but are not from consecutive sampling windows.

[0418] In some embodiments, device 600B tracks two channels of sampling data, one covering movement of device 600B and the other covering the location of device 600B. In some embodiments, the two channels of sampling data are evaluated independently of one another. That is, when device 600B detects (e.g., determines) whether a predetermined number (e.g., five) of prompts have been generated that would cause the current heart rate measurement session to be aborted, device 600B does not aggregate the movement-based sampling data and the location-based sampling data of device 600B (e.g., two movement-based samples above a threshold and three location-based samples above a threshold would not be aggregated, and therefore the current session would not be aborted).

[0419] In some embodiments, if the heart rate measurements shown in FIGS. 12H-12L are completed successfully, the device 600B displays the measurement results in a results user interface similar to the results user interface 1214 of FIG. 12G.

[0420] Flowchart 1201A of Figure 12O illustrates a process for determining whether to continue (and ultimately complete) heart rate measurement or to discontinue heart rate measurement, as described above with respect to Figure 12L. Flowchart 1201A illustrates, among other things, whether to continue or discontinue the heart rate measurement process based on location data.

[0421] At step 1203A, device 600B initiates a heart rate measurement (e.g., as described with reference to FIG. 12B). At step 1205A, device 600B detects location data (e.g., via an accelerometer) corresponding to the current location of device 600B.

[0422] In step 1207A, the device 600B determines whether the detected location data meets the location criteria (e.g., the device 600B determines whether it is in an acceptable location for measurement based on location data from an accelerometer). If the device 600B determines that the detected location meets the location criteria, the device 600B determines in step 1209A whether the prompt criteria are met (e.g., based on the number of prompts already generated during the current measurement). If the device 600B determines that the detected location does not meet the location criteria, the device 600B determines in step 1211A whether there is time remaining in the current measurement (e.g., whether there is enough time for another sampling window in the current measurement).

[0423] If device 600B determines in step 1209A that the prompt criteria are met, then device 600B generates a prompt (prompt 1224, 1226, or 1228, described above with respect to Figures 12I-12K, respectively) in step 1212. If device 600B determines in step 1209A that the prompt criteria are (no longer) met, then device 600B ceases generating the prompt.

[0424] If device 600B determines in step 1211A that there is time remaining in the current measurement, device 600B returns to step 1205A to again detect location data while continuing heart rate measurement. If device 600B determines in step 1211A that there is no time remaining, device 600B successfully completes the current measurement in step 1215A.

[0425] After (or in response to) generating the prompt in step 1213A, device 600B determines in step 1217A whether measurement stop criteria have been met (e.g., whether at least a predetermined number of prompts have been generated, whether at least a predetermined number of occurrences of met location criteria have been detected). If device 600B determines in step 1217A that the stop criteria have been met, device 600B proceeds to step 1219A and aborts the current heart rate measurement without completing the measurement. If device 600B determines in step 1217A that the stop criteria have not been met, device 600B returns to step 1205A and again detects location data while continuing heart rate measurements.

[0426] Flowchart 1221A of Figure 12P illustrates a process for determining whether to continue (and ultimately complete) heart rate measurement or to discontinue heart rate measurement, as described above with respect to Figure 12L. Flowchart 1201A illustrates, among other things, whether to continue or discontinue the heart rate measurement process based on ambulatory data.

[0427] At step 1223A, device 600B initiates a heart rate measurement (e.g., as described with reference to FIG. 12B). At step 1225A, device 600B detects (e.g., via an accelerometer) movement data corresponding to detected movement of device 600B (e.g., from one position in 3D space to a different position in 3D space).

[0428] In step 1227A, the device 600B determines whether the detected movement data meets the movement criteria (e.g., the device 600B determines whether the movement exceeds a movement threshold based on the movement data from the accelerometer). If the device 600B determines that the detected movement meets the movement criteria, the device 600B determines in step 1229A whether the prompt criteria are met (e.g., based on the number of prompts already generated during the current measurement). If the device 600B determines that the detected movement does not meet the movement criteria, the device 600B determines in step 1231A whether there is time remaining in the current measurement (e.g., whether there is enough time in another sampling window in the current measurement).

[0429] If device 600B determines in step 1229A that the prompt criteria are met, then device 600B generates a prompt (prompt 1224, 1226, or 1228, described above with respect to Figures 12I-12K, respectively) in step 1233A. If device 600B determines in step 1229A that the prompt criteria are (no longer) met, then device 600B ceases generating the prompt.

[0430] If device 600B determines in step 1231A that there is time remaining in the current measurement, device 600B returns to step 1225A to again detect movement data while continuing heart rate measurement. If device 600B determines in step 1231A that there is no time remaining, device 600B successfully completes the current measurement in step 1235A.

[0431] After generating the prompts in step 1233A (or in response thereto), device 600B determines in step 1237A whether measurement stop criteria have been met (e.g., whether at least a predetermined number of prompts have been generated, whether at least a predetermined numbe...

Claims

1. A computer system in communication with a display generation component and one or more input devices, comprising: means for displaying, via the display generation component, a user interface including a plurality of user interface objects corresponding to health-related functions, the plurality of user interface objects including a first user interface object corresponding to a first health-related function, the first user interface object comprising: an indication that the first health-related function is active in response to a determination that the first health-related function is currently active; an indication that the first health-related feature is available for activation in response to a determination that the first health-related feature is currently inactive and available for activation via a set of one or more inputs received at the computer system; and in response to a determination that the first health-related feature is currently inactive and unavailable for activation, indicating that the first health-related feature is unavailable for activation; and A method comprising:

2. 2. The method of claim 1 , wherein the first health-related feature is unavailable for activation due to a first solvable problem, and the indication that the first health-related feature is unavailable for activation includes a selectable portion that, when selected via input received via the one or more input devices, initiates a process to resolve the first solvable problem, thereby making the first health-related feature available for activation.

3. the first health-related feature is currently inactive and available for activation, and the first user interface object is: and a selectable portion that, when selected via input received via the one or more input devices, initiates a process for activating a first health-related feature, the process for activating the first health-related feature comprising: a first type of activation process that requires a first minimum number of inputs to activate the first health-related function pursuant to a determination that the first health-related function is a first type of function; 2. The method of claim 1, further comprising: a second type activation process in accordance with a determination that the first health-related function is of a second type, the second type activation process requiring a second minimum number of inputs to activate the first health-related function, the second minimum number of inputs being greater than the first minimum number of inputs.

4. 4. The method of claim 3, wherein the first type of activation process includes displaying, via the display generation component, a single selectable user interface object that activates the first health-related feature when selected via input received via the one or more input devices.

5. The second type of activation process comprises: displaying a sequence of a plurality of user interfaces via the display generation component; and receiving a plurality of user inputs received while an interface of the plurality of user interfaces is displayed prior to activating the first health-related function.

6. the computer system is associated with a first user account; the first user account is associated with a first external electronic device; the first health-related function, when active, includes one or more functions operating on the computer system and one or more functions operating on the first external electronic device; The method comprises: receiving a set of one or more inputs including inputs corresponding to the first user interface object; in response to receiving the set of one or more inputs including input corresponding to the first user interface object, via the display generation component; a first functional user interface object corresponding to the one or more functionalities operating on the computer system; and displaying a functional user interface corresponding to the first health-related function including a second functional user interface object corresponding to a function of the one or more functions operating on the first external electronic device.

7. The process for activating the first health-related function comprises: a first configuration user interface object for modifying a parameter of the first health-related function of the computer system; 7. The method of claim 3, further comprising displaying a configuration user interface including simultaneously a second configuration user interface object for modifying a parameter of the first health-related function of a second external electronic device.

8. The method of claim 1 , wherein settings of the first health-related feature cannot be modified from the user interface that includes the plurality of user interface objects corresponding to health-related features.

9. 9. 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 of any one of claims 1 to 8.

10. A display generating component; one or more input devices; one or more processors; A computer system comprising: 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 of any one of claims 1 to 8.

11. 1. A computer system comprising: A display generating component; one or more input devices; and means for executing the method according to any one of claims 1 to 8.

12. 1. 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: and instructions for displaying, via the display generation component, a user interface including a plurality of user interface objects corresponding to health-related functions, the plurality of user interface objects including a first user interface object corresponding to a first health-related function, the first user interface object comprising: an indication that the first health-related function is active in response to a determination that the first health-related function is currently active; an indication that the first health-related feature is available for activation in response to a determination that the first health-related feature is currently inactive and available for activation via a set of one or more inputs received at the computer system; and and an indication that the first health-related feature is unavailable for activation in accordance with a determination that the first health-related feature is currently inactive and unavailable for activation.

13. A display generating component; one or more input devices; one or more processors; A computer system comprising: and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising: and instructions for displaying, via the display generation component, a user interface including a plurality of user interface objects corresponding to health-related functions, the plurality of user interface objects including a first user interface object corresponding to a first health-related function, the first user interface object comprising: an indication that the first health-related function is active in response to a determination that the first health-related function is currently active; an indication that the first health-related feature is available for activation in response to a determination that the first health-related feature is currently inactive and available for activation via a set of one or more inputs received at the computer system; and and indicating that the first health-related feature is unavailable for activation in accordance with a determination that the first health-related feature is currently inactive and unavailable for activation.

14. A display generating component; one or more input devices; A computer system comprising: means for displaying, via the display generation component, a user interface including a plurality of user interface objects corresponding to health-related functions, the plurality of user interface objects including a first user interface object corresponding to a first health-related function, the first user interface object comprising: an indication that the first health-related function is active in response to a determination that the first health-related function is currently active; an indication that the first health-related feature is available for activation in response to a determination that the first health-related feature is currently inactive and available for activation via a set of one or more inputs received at the computer system; and and indicating that the first health-related feature is unavailable for activation in accordance with a determination that the first health-related feature is currently inactive and unavailable for activation.

15. A computer system in communication with a display generation component and one or more input devices, comprising: and displaying, via the display generation component, a collection of one or more user interfaces corresponding to a first health-related feature, the first health-related feature being currently inactive, and displaying the collection of one or more user interfaces corresponding to the first health-related feature comprising: pursuant to determining that a set of activation permission criteria are satisfied, the set of activation permission criteria including location-based criteria that are satisfied when a current location of the computer system satisfies a set of location-based criteria, displaying a first activation user interface of a set of one or more activation user interfaces, the set of one or more activation user interfaces including a first selectable user interface object that, when selected via input received via the one or more input devices, activates the first health-related feature; pursuant to a determination that the set of activation permission criteria is not satisfied, displaying a notification interface that includes first information corresponding to the first health-related feature and does not include a selectable user interface object that, when selected via input received via the one or more input devices, activates the first health-related feature; A method comprising:

16. 16. The method of claim 15, wherein the set of location-based criteria includes criteria that are met when the current location of the computer system matches a predetermined set of one or more locations.

17. 17. A method according to any one of claims 15 to 16, wherein the set of one or more activation user interfaces includes a second activation user interface including a user interface object for verifying first biometric details of a user of the computer system.

18. 18. The method of claim 15, wherein the set of one or more activation user interfaces includes a third activation user interface that includes suggestions of one or more medications that may affect the first health-related function.

19. the first health-related function, when activated, includes performing one or more biometric measurements; 19. The method of claim 15, further comprising, after completing a biometric measurement of the first health-related function, issuing a sensory suggestion corresponding to the biometric measurement.

20. 20. The method of claim 15, wherein the activation permission criteria include a criterion that is met when the age of a user of the computer system does not exceed a threshold age value.

21. Detecting, while the first health-related function is active, that a user's current age exceeds a threshold age value; deactivating at least one function of the first health-related function in response to detecting that the current age of the user exceeds the threshold age value; 21. The method of any one of claims 15 to 20, further comprising:

22. 22. The method of claim 21, wherein deactivating the at least one feature of the first health-related feature includes displaying, via the indication generating component, an indication that the deactivated at least one feature of the first health-related feature is unavailable for reactivation.

23. the first health-related function, when activated, includes performing one or more biometric measurements; 23. The method of any one of claims 15 to 22, further comprising, after completing a first biometric measurement of the first health-related function, displaying via the display generation component a result of the first biometric measurement, the result of the biometric measurement including a suggestion to classify the result into a quintile of five possible quintiles.

24. The first biometric measurement is classified into a first quintile, and the method further comprises: performing a second biometric measurement after completing the first biometric measurement; and and displaying, via the display generation component, a result of the second biometric measurement after completing the second biometric measurement, the result of the second biometric measurement comprising:

24. The method of claim 23, further comprising a suggestion that the second biometric measurement be classified into the first quintile pursuant to a determination that the result of the second biometric measurement is classified into the first quintile, the suggestion classifying the result of the second biometric measurement into the first quintile being different from the suggestion classifying the result of the first biometric measurement into the first quintile.

25. determining the current location of the computer system prior to displaying the set of one or more user interfaces corresponding to the first health-related function; 25. The method of any one of claims 15 to 24, further comprising:

26. 26. The method of any one of claims 15 to 25, wherein displaying the first activation user interface of the set of one or more activation user interfaces is performed in response to input received while displaying a user interface of an application that collects and presents data regarding a plurality of health-related functions, including the first health-related function.

27. the first health-related function, when activated, includes performing one or more biometric measurements; 27. The method of any one of claims 15 to 26, further comprising, after completing a plurality of biometric measurements of the first health-related feature, displaying a data user interface including a graphical representation of results of at least a subset of the plurality of biometric measurements.

28. the first health-related function, when activated, includes performing one or more biometric measurements; 28. The method of claim 15, further comprising, after completing a third biometric measurement of the first health-related function, displaying via the display generation component a result of the third biometric measurement, wherein displaying the result of the third biometric measurement comprises displaying reference measurements from a plurality of different age ranges.

29. 29. 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 of any one of claims 15 to 28.

30. A display generating component; one or more input devices; one or more processors; A computer system comprising: 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 of any one of claims 15 to 28.

31. 1. A computer system comprising: A display generating component; one or more input devices; and means for executing the method according to any one of claims 15 to 28.

32. 1. 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: and displaying, via the display generation component, a collection of one or more user interfaces corresponding to a first health-related feature, the first health-related feature being currently inactive, and displaying the collection of one or more user interfaces corresponding to the first health-related feature comprising: pursuant to determining that a set of activation permission criteria are satisfied, the set of activation permission criteria including location-based criteria that are satisfied when a current location of the computer system satisfies a set of location-based criteria, displaying a first activation user interface of a set of one or more activation user interfaces, the set of one or more activation user interfaces including a first selectable user interface object that, when selected via input received via the one or more input devices, activates the first health-related feature; and displaying a notification interface in accordance with a determination that the set of activation permission criteria is not satisfied, the notification interface including first information corresponding to the first health-related function and not including a selectable user interface object that, when selected via input received via the one or more input devices, activates the first health-related function.

33. A display generating component; one or more input devices; one or more processors; A computer system comprising: and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising: and instructions for displaying, via the display generation component, a set of one or more user interfaces corresponding to a first health-related function, the first health-related function being currently inactive, and displaying the set of one or more user interfaces corresponding to the first health-related function comprising: pursuant to determining that a set of activation permission criteria are satisfied, the set of activation permission criteria including location-based criteria that are satisfied when a current location of the computer system satisfies a set of location-based criteria, displaying a first activation user interface of a set of one or more activation user interfaces, the set of one or more activation user interfaces including a first selectable user interface object that, when selected via input received via the one or more input devices, activates the first health-related feature; and displaying a notification interface in accordance with a determination that the set of activation permission criteria is not met, the notification interface including first information corresponding to the first health-related function and not including a selectable user interface object that, when selected via input received via the one or more input devices, activates the first health-related function.

34. A display generating component; one or more input devices; A computer system comprising: and displaying, via the display generation component, a set of one or more user interfaces corresponding to a first health-related feature, wherein the first health-related feature is currently inactive, and displaying the set of one or more user interfaces corresponding to the first health-related feature comprises: pursuant to determining that a set of activation permission criteria are satisfied, the set of activation permission criteria including location-based criteria that are satisfied when a current location of the computer system satisfies a set of location-based criteria, displaying a first activation user interface of a set of one or more activation user interfaces, the set of one or more activation user interfaces including a first selectable user interface object that, when selected via input received via the one or more input devices, activates the first health-related feature; and displaying a notification interface in accordance with a determination that the set of activation permission criteria is not met, the notification interface including first information corresponding to the first health-related function and not including a selectable user interface object that, when selected via input received via the one or more input devices, activates the first health-related function.

35. A computer system in communication with a display generation component and one or more input devices, comprising: displaying, via the display generation component, a first configuration user interface of a set of one or more configuration user interfaces for a first health-related tracking functionality, the first configuration user interface including a first selectable user interface object, the first health-related tracking functionality currently configured to track a first set of health-related data while the computer system is in a first mode and a second mode different from the first mode; receiving a set of one or more inputs, the set of one or more inputs including an input corresponding to the first selectable user interface object; configuring the first health-related tracking functionality to track the first set of health-related data while the computer system is in the second mode in response to the set of one or more inputs, while not tracking the first set of health-related data while the computer system is in the first mode; A method comprising:

36. 36. The method of claim 35, wherein the first health-related tracking feature is a heart rate tracking feature.

37. receiving data from an external electronic device in communication with the computer system indicating that a process for configuring the first health-related tracking feature has been initiated at the external electronic device prior to displaying the first configuration user interface of the set of one or more configuration user interfaces for the first health-related tracking feature; in response to receiving the data, displaying a notification indicating that the process for configuring the first health-related tracking feature may be completed at the computer system; and 37. The method of any one of claims 35 to 36, further comprising:

38. and after displaying the notification indicating that the process for configuring the first health-related tracking feature may be completed at the computer system, receiving a set of one or more inputs that completes the process for configuring the first health-related tracking feature at the computer system, wherein the process for configuring the first health-related tracking feature includes enabling a first health-related tracking feature to perform the first health-related tracking feature without requiring further user input; 38. The method of claim 37, comprising:

39. 39. The method of any one of claims 35 to 38, wherein the set of one or more configuration user interfaces includes a second selectable user interface object that, when selected, disables execution of a tracking operation of the first health-related tracking function without user input.

40. 40. The method of any one of claims 35 to 39, wherein the first health-related tracking function is configured to perform tracking actions only in response to user input.

41. 41. The method of any one of claims 35 to 40, wherein the computer system is in the first mode when the current time corresponds to a predetermined time period.

42. Receiving a first type of input; in response to receiving the input of the first type; increasing the brightness of the display generation component in response to determining that the computer system is not in the first mode; cease increasing the brightness of the display generation component in response to determining that the computer system is in the first mode; and 42. The method of any one of claims 35 to 41, further comprising:

43. the set of one or more configuration user interfaces includes a third selectable user interface object that, when selected, sets a threshold for the first set of health-related data, which causes the computer system to issue a sensory notification upon detecting that the health-related tracking feature exceeds the threshold; receiving a set of one or more user inputs including inputs corresponding to the third selectable user interface object; in response to receiving the set of one or more user inputs including an input corresponding to the third selectable user interface object; displaying an indication that frequent sensory notifications may result in response to a determination that the set of one or more inputs causes the threshold to be set to a predetermined value; and 43. The method of claim 35, further comprising: ceasing to display an indication that frequent sensory notifications may result pursuant to a determination that the set of one or more inputs causes the threshold to be set to a value other than the predetermined value.

44. 44. The method of any one of claims 37 to 43, wherein the first health-related tracking feature is a blood oxygen level tracking feature.

45. 45. 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 of any one of claims 35 to 44.

46. A display generating component; one or more input devices; one or more processors; A computer system comprising: and a memory storing one or more programs configured to be executed by said one or more processors, said one or more programs including instructions for performing the method of any one of claims 35 to 44.

47. A display generating component; one or more input devices; A computer system comprising: and means for carrying out the method of any one of claims 35 to 44.

48. 1. 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 displaying, via the display generation component, a first configuration user interface of a set of one or more configuration user interfaces for a first health-related tracking functionality, the first configuration user interface including a first selectable user interface object, the first health-related tracking functionality currently configured to track a first set of health-related data while the computer system is in a first mode and a second mode different from the first mode; instructions for receiving a set of one or more inputs, the set of one or more inputs including an input corresponding to the first selectable user-interface object; and instructions to configure the first health-related tracking function to not track the first set of health-related data while the computer system is in the first mode, while tracking the first set of health-related data while the computer system is in the second mode, in response to the set of one or more inputs.

49. A display generating component; one or more input devices; one or more processors; A computer system comprising: a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising: instructions for displaying, via the display generation component, a first configuration user interface of a set of one or more configuration user interfaces for a first health-related tracking functionality, the first configuration user interface including a first selectable user interface object, the first health-related tracking functionality currently configured to track a first set of health-related data while the computer system is in a first mode and a second mode different from the first mode; instructions for receiving a set of one or more inputs, the set of one or more inputs including an input corresponding to the first selectable user-interface object; and instructions to configure the first health-related tracking function in response to the set of one or more inputs to track the first set of health-related data while the computer system is in the second mode, while not tracking the first set of health-related data while the computer system is in the first mode.

50. A display generating component; one or more input devices; A computer system comprising: means for displaying, via the display generation component, a first configuration user interface of a set of one or more configuration user interfaces for a first health-related tracking functionality, the first configuration user interface including a first selectable user interface object, the first health-related tracking functionality currently configured to track a first set of health-related data while the computer system is in a first mode and a second mode different from the first mode; means for receiving a set of one or more inputs, the set of one or more inputs including an input corresponding to the first selectable user-interface object; and means for configuring the first health-related tracking functionality to not track the first set of health-related data while the computer system is in the first mode, while tracking the first set of health-related data while the computer system is in the second mode, in response to the set of one or more inputs.

51. 1. A computer system in communication with a display generation component, a set of one or more biometric sensors, and a set of one or more sensors distinct from the set of one or more biometric sensors, comprising: initiating a biometric analysis process including detecting first biometric data via the one or more biometric sensors; During the biometric analysis process, Detecting a first set of sensor data via the set of one or more sensors; In response to detecting the first set of sensor data, stopping the biometric analysis process in accordance with a determination that the first set of sensor data satisfies a first set of stopping criteria; A method comprising:

52. The set of one or more sensors includes at least a first sensor configured to detect a position or movement of the computer system, and the method further comprises: During the biometric analysis process, detecting, via the set of one or more sensors, a second set of sensor data indicative of a location of the computer system or a movement of the computer system; in response to detecting the second set of sensor data; 52. The method of claim 51, further comprising: displaying, via the display generation component, a first prompt to change a location of the computer system or to limit changing a location of the computer system in accordance with a determination that the second set of sensor data satisfies a first set of prompt criteria.

53. continuing the biometric analysis process after displaying the first prompt; 53. The method of claim 52, further comprising:

54. detecting, during the biometric analysis process and after displaying the first prompt, via the set of one or more sensors, a third set of sensor data indicative of a location of the computer system or a movement of the computer system that satisfies the first set of criteria; responsive to detecting the third set of sensor data, replacing the first prompt with a second prompt different from the first prompt to relocate the computer system or to limit relocation of the computer system; 54. The method of any one of claims 52 to 53, further comprising:

55. 55. The method of any one of claims 52 to 54, wherein the first prompt includes guidance on how to have a proper location for the computer system or how to restrict movement of the computer system.

56. Displaying the first prompt to change the location of the computer system or to limit changing the location of the computer system includes: a prompt to change the location of the computer system in accordance with a determination that the second set of sensor data satisfies a first set of location criteria, the first set of location criteria including criteria that are satisfied when the location of the computer system coincides with a first predefined location of a set of one or more predefined locations; 56. The method of claim 52, further comprising: a prompt to limit movement of the computer system in accordance with a determination that the second set of sensor data satisfies a first set of movement criteria, the first set of movement criteria including criteria that are met when a mobility of the computer system exceeds a threshold.

57. 57. The method of any one of claims 51 to 56, wherein the first biometric data is heart rate data.

58. displaying, after completing the biometric analysis process, a first results user interface including information corresponding to the biometric analysis process, the first results user interface including a first discardable user interface object; receiving a user input corresponding to the first discardable user interface object; in response to receiving the user input corresponding to the first discard selectable user interface object, displaying a first user interface of a set of one or more biometric analysis process initiation user interfaces, the set of one or more biometric analysis process initiation user interfaces including a first initiate selectable user interface object that, when selected, initiates a second biometric analysis process via the set of one or more biometric sensors; 58. The method of any one of claims 51 to 57, further comprising:

59. and displaying, during the biometric analysis process, a graphical indication that collection of biometric data is progressing, wherein displaying the graphical indication that collection of biometric data is progressing comprises displaying a first graphical object having a first visual characteristic transitioning to a second graphical object having a second visual characteristic different from the first visual characteristic.

59. The method of any one of claims 51 to 58, further comprising:

60. and displaying a second result user interface after completion of the biometric analysis process, the second result user interface comprising: the results of said biometric analysis process; and upon determining that the biometric analysis process was performed under one or more conditions of a first type, an indication that the biometric analysis process was performed under one or more conditions of the first type; and 60. The method of any one of claims 51 to 59, further comprising:

61. 61. The method of any one of claims 51 to 60, wherein the first set of stopping criteria is met when a first detected value corresponding to the first set of sensor data exceeds an expected value.

62. 62. The method of any one of claims 51 to 61, wherein the first set of stopping criteria is met when at least a first number of distinct sets of the first set of sensor data from a sampling window of distinct sets of data exceed a threshold.

63. 63. The method of claim 62, wherein the sampling window of distinct sets of data includes a plurality of distinct sets of data, and the at least a first number of distinct sets of data are a plurality of contiguous sets of data.

64. 64. The method of any one of claims 62 to 63, wherein the at least a first number of distinct sets of data are multiple sets of data each collected over the same predetermined period of time.

65. 65. The method of claim 64, wherein at least two of the plurality of sets of data of the at least first number of distinct sets of data overlap in time.

66. The first set of sensor data is detected at a first time during the biometric analysis process, and the method further comprises: At a second time during the biometric analysis process subsequent to the first, detecting a fourth set of sensor data via the set of one or more sensors; in response to detecting the fourth set of sensor data; 66. The method of any one of claims 51 to 65, further comprising: stopping the biometric analysis process in accordance with a determination that the fourth set of sensor data satisfies a second set of stopping criteria that is different from the first set of stopping criteria.

67. 67. The method of any one of claims 51 to 66, wherein the first set of sensor data includes data indicative of a location of the computer system.

68. 68. The method of any one of claims 51 to 67, wherein the first set of sensor data includes data indicative of movement of the computer system.

69. 69. The method of any one of claims 51 to 68, wherein the first set of sensor data includes data indicative of a location of the computer system and data indicative of a movement of the computer system.

70. 70. The method of any one of claims 52-56 and 58-69, wherein the first biometric data is a blood oxygen level measurement.

71. After stopping the biometric analysis process, displaying a first stop user interface in response to a determination that the first set of biometric data and / or the sensor data satisfies a first set of stop-type criteria; displaying a second stop user interface that is different from the first stop user interface in response to a determination that the first set of biometric and / or sensor data satisfies a second set of stop-type criteria that is different from the first set of stop-type criteria; 71. The method of any one of claims 51 to 70, further comprising:

72. the first set of stop-type criteria includes criteria that are met when the first set of sensor data indicates a movement of the computer system that satisfies a first set of movement stop-type criteria; the first stop user interface includes guidance for reducing movement of the computer system; 72. The method of claim 71.

73. the second set of stop-type criteria includes criteria that are met when the first set of sensor data indicates a location of the computer system that satisfies a first set of location stop-type criteria; the second shutdown user interface includes guidance regarding configuration of the computer system; 73. The method of any one of claims 51 to 72.

74. After stopping the biometric analysis process, displaying a user interface for initiating a second biometric analysis process, the second biometric analysis process comprising: a selectable user interface object that, when selected, initiates the second biometric analysis process; responsive to a determination that the first set of stopping criteria is satisfied by the first set of sensor data corresponding to a first type of stopping condition, guidance corresponding to the first type of stopping condition; responsive to a determination that the first set of stopping criteria is satisfied by the first set of sensor data corresponding to a second type of stopping condition, guidance corresponding to the second type of stopping condition; 74. The method of any one of claims 51 to 73, further comprising:

75. During the biometric analysis process, Stopping the biometric analysis process pursuant to a determination that the first biometric data satisfies a second set of stopping criteria different from the first set of stopping criteria.

75. The method of any one of claims 51 to 74, further comprising:

76. displaying a third stop user interface different from the first stop user interface and the second stop user interface after stopping the biometric analysis process in accordance with a determination that the first biometric data satisfies a second set of stop criteria.

76. The method of claim 75, further comprising:

77. the computer system is a wearable electronic device; the third stop user interface includes guidance for adjusting how the wearable electronic device is worn.

77. The method of claim 76.

78. Stopping the biometric analysis process includes:

78. The method of any one of claims 51 to 77, comprising detecting a predetermined amount of biometric data and ceasing to display results indicative of biometric parameters corresponding to the biometric data.

79. 80. 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, a set of one or more biometric sensors, and a set of one or more sensors different from the set of one or more biometric sensors, the one or more programs including instructions for performing the method of any one of claims 51 to 78.

80. A display generating component; a collection of one or more biosensors; a set of one or more sensors distinct from the set of one or more biosensors; one or more processors; and a memory storing one or more programs configured to be executed by said one or more processors, said one or more programs including instructions for performing the method of any one of claims 51 to 78.

81. A display generating component; a collection of one or more biosensors; a set of one or more sensors distinct from the set of one or more biosensors; and means for executing the method of any one of claims 51 to 78.

82. 1. 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, a set of one or more biometric sensors, and a set of one or more sensors distinct from the set of one or more biometric sensors, the one or more programs comprising: instructions for initiating a biometric analysis process including detecting first biometric data via the one or more biometric sensors; During the biometric analysis process, instructions for detecting a first set of sensor data via the set of one or more sensors; In response to detecting the first set of sensor data, and instructions for stopping the biometric analysis process according to a determination that the first set of sensor data satisfies a first set of stopping criteria.

83. A display generating component; a collection of one or more biosensors; a set of one or more sensors distinct from the set of one or more biosensors; one or more processors; A computer system comprising: a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising: instructions for initiating a biometric analysis process including detecting first biometric data via the one or more biometric sensors; During the biometric analysis process, instructions for detecting a first set of sensor data via the set of one or more sensors; In response to detecting the first set of sensor data, and instructions for stopping the biometric analysis process according to a determination that the first set of sensor data satisfies a first set of stopping criteria.

84. A display generating component; a collection of one or more biosensors; a set of one or more sensors distinct from the set of one or more biosensors; A computer system comprising: means for initiating a biometric analysis process including detecting first biometric data via the one or more biometric sensors; During the biometric analysis process, means for detecting a first set of sensor data via said set of one or more sensors; In response to detecting the first set of sensor data, means for stopping the biometric analysis process according to a determination that the first set of sensor data satisfies a first set of stopping criteria.

85. A computer system in communication with a display generation component and one or more input devices, comprising: displaying, via the display generation component, a summary user interface of a first health-related tracking feature; the summary user interface includes a collection of one or more user interface objects corresponding to tracking data collected by the first health-related tracking feature; the set of one or more user interface objects includes a first user interface object corresponding to first data collected via the first health-related tracking feature; Displaying the overview user interface includes: pursuant to determining that the first data was collected under one or more conditions of a first type, displaying the first user interface object with an indication that at least a portion of the tracking data collected by a first health-related tracking feature was collected under the one or more conditions of the first type; A method comprising:

86. Displaying the overview interface includes:

86. The method of claim 85, further comprising: pursuant to a determination that the tracking data collected by the first health-related tracking feature corresponding to the displayed one or more user interface objects was not collected under one or more conditions of the first type, displaying the collection of one or more user interface objects without an indication that at least a portion of the tracking data collected by the first health-related tracking feature was collected under the one or more conditions of the first type.

87. 87. The method of any one of claims 85 to 86, wherein the one or more conditions of the first type include an altitude above a threshold.

88. 88. The method of any one of claims 85 to 87, wherein the tracking data is heart rate tracking data.

89. 89. The method of any one of claims 85 to 88, wherein the collection of one or more user interface objects corresponding to tracking data collected by the first health-related tracking function includes a plurality of user interface objects corresponding to tracking data collected by the first health-related tracking function.

90. Displaying the overview user interface includes:

90. The method of any one of claims 85 to 89, wherein displaying a summary user interface comprises, pursuant to a determination that tracking data collected by a first health-related tracking function indicates that a biometric parameter of a user of a computer system has been below a threshold, for example for at least a predetermined period of time, displaying an indication that the biometric parameter of the user has been below a threshold for at least the predetermined period of time.

91. Displaying the overview user interface includes:

90. The method of any one of claims 85 to 89, wherein displaying a summary user interface comprises, pursuant to a determination that tracking data collected by a first health-related tracking function indicates that a biometric parameter of a user of a computer system has been below a threshold, for example for at least a predetermined period of time, displaying an indication that the biometric parameter of the user has been below a threshold for at least the predetermined period of time.

92. 92. The method of claim 91, wherein the one or more conditions of the first type include a sleep period.

93. 93. The method of any one of claims 85 to 92, wherein the first health-related tracking function is configured to perform tracking operations without requiring further user input.

94. 94. The method of any one of claims 85 to 93, wherein the overview user interface includes a detail selectable user interface object that, when selected, provides additional information regarding one or more conditions under which at least a portion of the tracking data was collected.

95. 95. The method of any one of claims 85 to 94, wherein the indication that at least a portion of the tracking data collected by the first health-related tracking functionality was collected under the one or more conditions of the first type includes an indication of a number of individual measurements taken by the first health-related tracking functionality under the one or more conditions of the first type.

96. 96. The method of any one of claims 85 to 95, wherein the overview user interface includes a collection of one or more filtering user interface objects including a first filtering user interface object that, when selected, filters the collection of one or more user interface objects based on a first filter parameter.

97. 97. The method of any one of claims 85-87 and 89-96, wherein the tracking data is blood oxygen level tracking data.

98. 98. 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 of any one of claims 85 to 97.

99. A display generating component; one or more input devices; one or more processors; A computer system comprising: and a memory storing one or more programs configured to be executed by said one or more processors, said one or more programs including instructions for performing the method of any one of claims 85 to 97.

100. A display generating component; one or more input devices; A computer system comprising: and means for performing the method of any one of claims 85 to 97.

101. 1. 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 displaying, via the display generation component, a summary user interface of a first health-related tracking feature; the summary user interface includes a collection of one or more user interface objects corresponding to tracking data collected by the first health-related tracking feature; the set of one or more user interface objects includes a first user interface object corresponding to first data collected via the first health-related tracking feature; Displaying the overview user interface includes: pursuant to a determination that the first data was collected under one or more conditions of a first type, displaying the first user interface object along with an indication that at least a portion of the tracking data collected by a first health-related tracking feature was collected under the one or more conditions of the first type.

102. A display generating component; one or more input devices; one or more processors; A computer system comprising: a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising: instructions for displaying, via the display generation component, a summary user interface of a first health-related tracking feature; the summary user interface includes a collection of one or more user interface objects corresponding to tracking data collected by the first health-related tracking feature; the set of one or more user interface objects includes a first user interface object corresponding to first data collected via the first health-related tracking feature; Displaying the overview user interface includes: pursuant to a determination that the first data was collected under one or more conditions of a first type, displaying the first user interface object with an indication that at least a portion of the tracking data collected by a first health-related tracking function was collected under the one or more conditions of the first type.

103. A display generating component; one or more input devices; A computer system comprising: means for displaying, via the display generation component, a summary user interface of a first health-related tracking feature; the summary user interface includes a collection of one or more user interface objects corresponding to tracking data collected by the first health-related tracking feature; the set of one or more user interface objects includes a first user interface object corresponding to first data collected via the first health-related tracking feature; Displaying the overview user interface includes: pursuant to a determination that the first data was collected under one or more conditions of a first type, displaying the first user interface object with an indication that at least a portion of the tracking data collected by a first health-related tracking function was collected under the one or more conditions of the first type.

104. 1. A computer system in communication with a collection of one or more biometric sensors, Detecting that a first set of health metrics is satisfied; and in response to detecting that the set of health metrics is satisfied; measuring a value of a biometric parameter via the set of one or more biometric sensors in response to determining that the computer system is in a first mode; ceasing to measure the biometric parameter in response to a determination that the computer system is in a second mode different from the first mode; and A method comprising:

105. 105. The method of claim 104, wherein the computer system includes an outer housing, and wherein measuring the value of the biometric parameter includes activating a sensor that is visible from a vantage point outside the outer housing.

106. The computer system includes an outer housing and a light generating component configured to illuminate a volume outside the outer housing; Measuring the value of the biometric parameter includes activating the light generating component and increasing the luminance of the volume outside the outer housing; 106. The method of any one of claims 104 to 105, comprising:

107. the second mode corresponds to a mode of the system identified via a previously received set of one or more user inputs as a mode in which no measurement of the biometric parameter occurs without a user input initiating the measurement; receiving, while the computer system is in the second mode, a set of one or more inputs corresponding to a request to measure the biometric parameter; 107. The method of any one of claims 104 to 106, further comprising: measuring a value of the biometric parameter via the set of one or more biometric sensors in response to receiving the set of one or more inputs corresponding to a request to measure the biometric parameter.

108. Receiving a first type of input; in response to receiving the input of the first type; increasing the brightness of a display generating component in communication with the computer system in response to determining that the computer system is not in the second mode; cease increasing the brightness of the display generation component in response to determining that the computer system is in the second mode; and 108. The method of any one of claims 104 to 107, further comprising:

109. 109. The method of any one of claims 104 to 108, wherein the computer system is in the second mode when the current time corresponds to a predetermined time period.

110. 110. The method of any one of claims 104 to 109, wherein the biometric parameter is heart rate.

111. 111. The method of any one of claims 104 to 110, wherein the biometric parameter is blood oxygen level.

112. 112. 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 set of one or more biosensors, the one or more programs including instructions for performing the method of any one of claims 104 to 111.

113. a collection of one or more biosensors; one or more processors; A computer system comprising: 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 of any one of claims 104 to 111.

114. a collection of one or more biosensors; Means for carrying out the method of any one of claims 104 to 111; 2. A computer system comprising:

115. 1. 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 collection of one or more biosensors, the one or more programs comprising: instructions for detecting that a first set of health metrics is satisfied; in response to detecting that the set of health metrics is satisfied; instructions for measuring, in response to a determination that the computer system is in a first mode, a value of a biometric parameter via the set of one or more biometric sensors; discontinuing measuring the biometric parameter in response to a determination that the computer system is in a second mode different from the first mode.

116. a collection of one or more biosensors; one or more processors; A computer system comprising: and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising: instructions for detecting that a first set of health metrics is satisfied; in response to detecting that the set of health metrics is satisfied; instructions for measuring, in response to a determination that the computer system is in a first mode, a value of a biometric parameter via the set of one or more biometric sensors; discontinuing measuring the biometric parameter in response to a determination that the computer system is in a second mode different from the first mode.

117. a collection of one or more biosensors; A computer system comprising: means for detecting when a first set of health metrics is satisfied; in response to detecting that the set of health metrics is satisfied; means for measuring, pursuant to a determination that the computer system is in a first mode, a value of a biometric parameter via the set of one or more biometric sensors; means for ceasing to measure the biometric parameter in response to a determination that the computer system is in a second mode different from the first mode.

Images