User interface for health tracking

By realizing health information collection and prediction notification generation in sleep tracking mode in computer systems, the complex and time-consuming user interface in the prior art is solved, and the efficiency of tracking health information and battery life are improved.

CN119855541APending Publication Date: 2025-04-18APPLE INC
View PDF 18 Cites 0 Cited by

Patent Information

Application Number
CN202380064379.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-08-23
Filing Date
2023-08-29
Publication Date
2025-04-18

AI Technical Summary

Technical Problem

The user interface for tracking health information is complex and time-consuming, resulting in a waste of user time and device energy.

Method used

Provides a faster and more efficient method and interface to achieve health information collection and prediction notification generation in sleep tracking mode by communicating with display generation components, input devices and temperature sensors in a computer system.

Benefits of technology

It reduces the cognitive burden of users, improves the efficiency of the human-computer interface, and saves power in battery-powered devices, and extends battery charging intervals.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119855541A_ABST
    Figure CN119855541A_ABST
Patent Text Reader

Abstract

The present disclosure generally relates to tracking health information and generating related predictions and / or notifications.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Patent Application No. 18 / 237,339, entitled “USER INTERFACES FOR HEALTH TRACKING,” filed on August 23, 2023, and U.S. Provisional Patent Application No. 63 / 404,139, entitled “USER INTERFACES FOR HEALTH TRACKING,” filed on September 6, 2022. The contents of each of these applications are incorporated herein by reference in their entirety. Technical Field

[0003] The present disclosure relates generally to computer user interfaces and, more particularly, to techniques for tracking health information and generating predictions and notifications. Background Art

[0004] Recurring (eg, recurring) events such as recurring health events can be tracked on an electronic device to record past events and predict future events. Summary of the invention

[0005] However, some techniques for tracking health information using electronic devices are often cumbersome and inefficient. For example, some prior art techniques use complex and time-consuming user interfaces that may include multiple keystrokes or keystrokes. Prior art techniques require more time than necessary, which results in wasted user time and device energy. This latter consideration is particularly important in battery-powered devices.

[0006] Therefore, the present technology provides electronic devices with faster and more efficient methods and interfaces for tracking health information and for generating relevant predictions and / or notifications. Such methods and interfaces optionally supplement or replace other methods for tracking health information and for generating relevant predictions and / or notifications. Such methods and interfaces reduce the cognitive burden on users and produce more efficient human-computer interfaces. For battery-powered computing devices, such methods and interfaces save power and increase the time interval between battery charges.

[0007] According to some embodiments, a method is described. The method includes: at a computer system that communicates with a display generation component, one or more input devices, and a temperature sensor: receiving input corresponding to a request to enter a sleep tracking mode via the one or more input devices; in response to the input, entering the sleep tracking mode; during the sleep tracking mode, allowing a first set of user temperature information to be collected via the temperature sensor; receiving a first type of notification data; in response to receiving the first type of notification data: outputting a first notification corresponding to the first type of notification data based on a determination that the computer system is not in the sleep tracking mode; and abandoning outputting the first notification corresponding to the first type of notification data based on a determination that the computer system is currently in the sleep tracking mode; and after allowing the first set of user temperature information to be collected, displaying a temperature user interface including a representation of one or more sets of user temperature information via the display generation component, the one or more sets of user temperature information including the first set of user temperature information.

[0008] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system communicating with a display generation component, one or more input devices, and a temperature sensor, the one or more programs including instructions for the following operations: receiving input corresponding to a request to enter a sleep tracking mode via the one or more input devices; in response to the input, entering the sleep tracking mode; during the sleep tracking mode, causing a first set of user temperature information to be collected via the temperature sensor; receiving a first type of notification data; in response to receiving the first type of notification data: outputting a first notification corresponding to the notification data of the first type according to a determination that the computer system is not in the sleep tracking mode; and abandoning outputting the first notification corresponding to the notification data of the first type according to a determination that the computer system is currently in the sleep tracking mode; and after causing the first set of user temperature information to be collected, displaying a temperature user interface including a representation of one or more sets of user temperature information via the display generation component, the one or more sets of user temperature information including the first set of user temperature information.

[0009] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system communicating with a display generation component, one or more input devices, and a temperature sensor, the one or more programs including instructions for the following operations: receiving input corresponding to a request to enter a sleep tracking mode via the one or more input devices; in response to the input, entering the sleep tracking mode; during the sleep tracking mode, causing a first set of user temperature information to be collected via the temperature sensor; receiving a first type of notification data; in response to receiving the first type of notification data: outputting a first notification corresponding to the notification data of the first type according to a determination that the computer system is not in the sleep tracking mode; and abandoning outputting the first notification corresponding to the notification data of the first type according to a determination that the computer system is currently in the sleep tracking mode; and after causing the first set of user temperature information to be collected, displaying a temperature user interface including a representation of one or more sets of user temperature information via the display generation component, the one or more sets of user temperature information including the first set of user temperature information.

[0010] According to some embodiments, a computer system is described. The computer system is configured to communicate with a display generation component, one or more input devices, and a temperature sensor, and includes: one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for the following operations: receiving input corresponding to a request to enter a sleep tracking mode via the one or more input devices; in response to the input, entering the sleep tracking mode; during the sleep tracking mode, causing a first set of user temperature information to be collected via the temperature sensor; receiving a first type of notification data; in response to receiving the first type of notification data: outputting a first notification corresponding to the notification data of the first type according to a determination that the computer system is not in the sleep tracking mode; and abandoning outputting the first notification corresponding to the notification data of the first type according to a determination that the computer system is currently in the sleep tracking mode; and after causing the first set of user temperature information to be collected, displaying a temperature user interface including a representation of one or more sets of user temperature information via the display generation component, the one or more sets of user temperature information including the first set of user temperature information.

[0011] According to some embodiments, a computer system is described. The computer system is configured to communicate with a display generation component, one or more input devices, and a temperature sensor, and includes: a component for performing the following operations: receiving an input corresponding to a request to enter a sleep tracking mode via the one or more input devices; entering the sleep tracking mode in response to the input; a component for performing the following operations: during the sleep tracking mode, causing a first set of user temperature information to be collected via the temperature sensor; receiving a first type of notification data; a component for performing the following operations: in response to receiving the first type of notification data: outputting a first notification corresponding to the first type of notification data based on a determination that the computer system is not in the sleep tracking mode; and abandoning outputting the first notification corresponding to the first type of notification data based on a determination that the computer system is currently in the sleep tracking mode; and a component for displaying a temperature user interface including a representation of one or more sets of user temperature information via the display generation component after causing the first set of user temperature information to be collected, the one or more sets of user temperature information including the first set of user temperature information.

[0012] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a computer system communicating with a display generation component, one or more input devices, and a temperature sensor, the one or more programs including instructions for the following operations: receiving input corresponding to a request to enter a sleep tracking mode via the one or more input devices; in response to the input, entering the sleep tracking mode; during the sleep tracking mode, causing a first set of user temperature information to be collected via the temperature sensor; receiving a first type of notification data; in response to receiving the first type of notification data: outputting a first notification corresponding to the notification data of the first type according to a determination that the computer system is not in the sleep tracking mode; and abandoning outputting the first notification corresponding to the notification data of the first type according to a determination that the computer system is currently in the sleep tracking mode; and after causing the first set of user temperature information to be collected, displaying a temperature user interface including a representation of one or more sets of user temperature information via the display generation component, the one or more sets of user temperature information including the first set of user temperature information.

[0013] According to some embodiments, a method is described. The method includes: at a computer system in communication with a display generation component and one or more input devices: receiving body temperature information corresponding to a user; and after receiving the body temperature information corresponding to the user, displaying via the display generation component a push notification that causes the display generation component to transition from an inactive state to an active state and indicates to the user that a predicted ovulation day for the user has been determined, wherein the predicted ovulation day is determined based on the body temperature information corresponding to the user.

[0014] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system communicating with a display generation component and one or more input devices, and the one or more programs include instructions for the following operations: receiving body temperature information corresponding to a user; and after receiving the body temperature information corresponding to the user, displaying via the display generation component so that the display generation component transitions from an inactive state to an active state and indicating to the user that a push notification of a predicted ovulation day for the user has been determined, wherein the predicted ovulation day is determined based on the body temperature information corresponding to the user.

[0015] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that communicates with a display generation component and one or more input devices, and the one or more programs include instructions for the following operations: receiving body temperature information corresponding to a user; and after receiving the body temperature information corresponding to the user, displaying via the display generation component so that the display generation component transitions from an inactive state to an active state and indicates to the user that a push notification of a predicted ovulation day for the user has been determined, wherein the predicted ovulation day is determined based on the body temperature information corresponding to the user.

[0016] According to some embodiments, a computer system is described. The computer system is configured to communicate with a display generation component and one or more input devices, and includes: one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for the following operations: receiving body temperature information corresponding to a user; and after receiving the body temperature information corresponding to the user, displaying via the display generation component so that the display generation component transitions from an inactive state to an active state and indicates to the user that a push notification of a predicted ovulation day for the user has been determined, wherein the predicted ovulation day is determined based on the body temperature information corresponding to the user.

[0017] According to some embodiments, a computer system is described. The computer system is configured to communicate with a display generation component and one or more input devices. The computer system includes: a component for receiving body temperature information corresponding to a user; and a component for displaying, via the display generation component, a push notification that causes the display generation component to transition from an inactive state to an active state and indicates to the user that a predicted ovulation day for the user has been determined, after receiving the body temperature information corresponding to the user, wherein the predicted ovulation day is determined based on the body temperature information corresponding to the user.

[0018] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for the following operations: receiving body temperature information corresponding to a user; and after receiving the body temperature information corresponding to the user, displaying via the display generation component so that the display generation component transitions from an inactive state to an active state and indicating to the user that a push notification of a predicted ovulation day for the user has been determined, wherein the predicted ovulation day is determined based on the body temperature information corresponding to the user.

[0019] According to some embodiments, a method is described. The method includes: at a computer system in communication with a display generation component and one or more input devices: at a first time, displaying a cycle tracking user interface via the display generation component, including displaying a first fertility window prediction for a user; receiving body temperature information corresponding to the user; after receiving the body temperature information corresponding to the user, at a second time after the first time, determining a predicted ovulation day for the user based on the body temperature information corresponding to the user; and at a third time after the second time, displaying an updated cycle tracking user interface via the display generation component, including simultaneously displaying: a representation of the predicted ovulation day for the user; and an updated fertility window prediction for the user that is different from the first fertility window prediction for the user.

[0020] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that communicates with a display generation component and one or more input devices, and the one or more programs include instructions for the following operations: at a first time, displaying a cycle tracking user interface via the display generation component, including displaying a first pregnancy window prediction for a user; receiving body temperature information corresponding to the user; after receiving the body temperature information corresponding to the user, at a second time after the first time, determining a predicted ovulation day for the user based on the body temperature information corresponding to the user; and at a third time after the second time, displaying an updated cycle tracking user interface via the display generation component, including simultaneously displaying: a representation of the predicted ovulation day for the user; and an updated pregnancy window prediction for the user that is different from the first pregnancy window prediction for the user.

[0021] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that communicates with a display generation component and one or more input devices, the one or more programs including instructions for the following operations: at a first time, displaying a cycle tracking user interface via the display generation component, including displaying a first pregnancy window prediction for a user; receiving body temperature information corresponding to the user; after receiving the body temperature information corresponding to the user, at a second time after the first time, determining a predicted ovulation day for the user based on the body temperature information corresponding to the user; and at a third time after the second time, displaying an updated cycle tracking user interface via the display generation component, including simultaneously displaying: a representation of the predicted ovulation day for the user; and an updated pregnancy window prediction for the user that is different from the first pregnancy window prediction for the user.

[0022] According to some embodiments, a computer system is described. The computer system is configured to communicate with a display generation component and one or more input devices, and includes: one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for the following operations: at a first time, displaying a cycle tracking user interface via the display generation component, including displaying a first fertility window prediction for a user; receiving body temperature information corresponding to the user; after receiving the body temperature information corresponding to the user, at a second time after the first time, determining a predicted ovulation day for the user based on the body temperature information corresponding to the user; and at a third time after the second time, displaying an updated cycle tracking user interface via the display generation component, including simultaneously displaying: a representation of the predicted ovulation day for the user; and an updated fertility window prediction for the user that is different from the first fertility window prediction for the user.

[0023] According to some embodiments, a computer system is described. The computer system is configured to communicate with a display generation component and one or more input devices. The computer system includes: a component for displaying a cycle tracking user interface via the display generation component at a first time, including a component for displaying a first pregnancy window prediction for a user; a component for receiving body temperature information corresponding to the user; a component for determining a predicted ovulation day for the user based on the body temperature information corresponding to the user at a second time after the first time after receiving the body temperature information corresponding to the user; and a component for displaying an updated cycle tracking user interface via the display generation component at a third time after the second time, including simultaneously displaying: a representation of the predicted ovulation day for the user; and an updated pregnancy window prediction for the user that is different from the first pregnancy window prediction for the user.

[0024] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for the following operations: at a first time, displaying a cycle tracking user interface via the display generation component, including displaying a first fertility window prediction for a user; receiving body temperature information corresponding to the user; after receiving the body temperature information corresponding to the user, at a second time after the first time, determining a predicted ovulation day for the user based on the body temperature information corresponding to the user; and at a third time after the second time, displaying an updated cycle tracking user interface via the display generation component, including simultaneously displaying: a representation of the predicted ovulation day for the user; and an updated fertility window prediction for the user that is different from the first fertility window prediction for the user.

[0025] According to some embodiments, a method is described. The method includes: at a computer system in communication with a display generation component and one or more input devices: receiving menstrual cycle information for a user via the one or more input devices; and based on a determination that the menstrual cycle information meets a first set of criteria, displaying, via the display generation component, a push notification to the user indicating that the computer system has identified a potential health issue for the user.

[0026] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for the following operations: receiving menstrual cycle information for a user via the one or more input devices; and based on a determination that the menstrual cycle information meets a first set of criteria, displaying a push notification to the user via the display generation component indicating that the computer system has identified a potential health issue for the user.

[0027] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for: receiving menstrual cycle information for a user via the one or more input devices; and based on a determination that the menstrual cycle information meets a first set of criteria, displaying a push notification to the user via the display generation component indicating that the computer system has identified a potential health issue for the user.

[0028] According to some embodiments, a computer system is described. The computer system is configured to communicate with a display generation component and one or more input devices, and includes: one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for the following operations: receiving menstrual cycle information for a user via the one or more input devices; and based on a determination that the menstrual cycle information meets a first set of criteria, displaying a push notification to the user via the display generation component indicating that the computer system has identified a potential health issue for the user.

[0029] According to some embodiments, a computer system is described. The computer system is configured to communicate with a display generation component and one or more input devices. The computer system includes: a component for receiving menstrual cycle information for a user via the one or more input devices; and a component for displaying, via the display generation component, a push notification to the user indicating that the computer system has identified a potential health issue for the user based on a determination that the menstrual cycle information meets a first set of criteria.

[0030] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for: receiving menstrual cycle information for a user via the one or more input devices; and based on a determination that the menstrual cycle information meets a first set of criteria, displaying a push notification to the user via the display generation component indicating that the computer system has identified a potential health issue for the user.

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

[0032] Thus, a faster, more efficient method and interface for tracking health information and for generating relevant predictions and / or notifications is provided for devices, thereby improving the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may supplement or replace other methods for tracking health information and for generating relevant predictions and / or notifications. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] For a better understanding of the various described embodiments, reference should be made to the following detailed description taken in conjunction with the following drawings, wherein like reference numerals designate corresponding parts throughout the several views.

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

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

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

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

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

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

[0040] Figure 5A Personal electronic devices according to some embodiments are illustrated.

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

[0042] FIG. 6A to FIG. 6Q An exemplary user interface for tracking body temperature information according to some embodiments is illustrated.

[0043] Figure 7 is a flow chart illustrating a method for tracking body temperature information according to some embodiments.

[0044] FIG. 8A to FIG. 8K An exemplary user interface for generating and providing an ovulation day prediction is illustrated according to some embodiments.

[0045] Fig. 9A is a flow chart illustrating a method for generating and providing an ovulation day prediction according to some embodiments.

[0046] Fig. 9B is a flow chart illustrating a method for generating and providing an ovulation day prediction according to some embodiments.

[0047] FIG. 10A to FIG. 10NAn exemplary user interface for generating and providing health-related notifications according to some embodiments is illustrated.

[0048] Fig.11 is a flow chart illustrating a method for generating and providing health-related notifications according to some embodiments. DETAILED DESCRIPTION

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

[0050] There is a need for electronic devices that provide efficient methods and interfaces for tracking health information and for generating related predictions and / or notifications. Such techniques can reduce the cognitive burden on users who track health information, thereby increasing productivity. In addition, such techniques can reduce processor power and battery power that would otherwise be wasted on redundant user input.

[0051] Below, Figure 1A to Figure 1B , Figure 2 , Figure 3 , FIG. 4A to FIG. 4B and FIG. 5A to FIG. 5B A description of an example device for performing techniques for tracking health information and for generating related predictions and / or notifications is provided. FIG. 6A to FIG. 6Q An exemplary user interface for tracking body temperature information is illustrated. Figure 7 is a flow chart illustrating a method of tracking body temperature information according to some embodiments. FIG. 6A to FIG. 6Q The user interface in is used to illustrate the process described below, including Figure 7 process. FIG. 8A to FIG. 8K An exemplary user interface for generating and providing an ovulation day prediction is illustrated. Fig. 9A is a flow chart illustrating a method of generating and providing an ovulation day prediction according to some embodiments. Fig. 9B is a flow chart illustrating a method of generating and providing an ovulation day prediction according to some embodiments. FIG. 8A to FIG. 8K The user interface in is used to illustrate the process described below, including Fig. 9A and Fig. 9B process. FIG. 10A to FIG. 10N An exemplary user interface for generating and providing health-related notifications is illustrated. Fig.11 is a flow chart illustrating a method of generating and providing health-related notifications according to some embodiments. FIG. 10A to FIG. 10N The user interface in is used to illustrate the process described below, including Fig.11 process.

[0052] The processes described below enhance the operability of the device and make the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device) through various techniques, including by providing improved visual feedback to the user, reducing the number of inputs required to perform an operation, providing additional control options without cluttering the user interface with additional displayed controls, performing an operation without further user input when a set of conditions have been met, and / or additional techniques. These techniques also reduce power usage and extend the battery life of the device by enabling the user to use the device more quickly and efficiently.

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

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

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

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

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

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

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

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

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

[0062] As used in this specification and claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a surrogate (surrogate) of the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​that includes at least four different values ​​and more typically includes hundreds of different values ​​(e.g., at least 256). The intensity of a contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure the force at different points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted average) to determine an estimated contact force. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and / or its change, the capacitance of the touch-sensitive surface near the contact and / or its change, and / or the resistance of the touch-sensitive surface near the contact and / or its change are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some embodiments, the substitute measurement of the contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of the contact as an attribute of the user input allows the user to access additional device functions that would otherwise be inaccessible to the user on a smaller device with limited real estate, which is used to display an enable indication (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls, such as knobs or buttons).

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

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

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

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

[0067] RF (radio frequency) circuit 108 receives and sends RF signals, also referred to as electromagnetic signals. RF circuit 108 converts electrical signals into / converts electromagnetic signals into electrical signals, and communicates with communication networks and other communication devices via electromagnetic signals. RF circuit 108 optionally includes well-known circuits for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codec chipsets, user identity modules (SIM) cards, memories, and the like. RF circuit 108 optionally communicates with networks and other devices via wireless communications, such as the Internet (also referred to as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs)). RF circuit 108 optionally includes well-known circuits for detecting near field communications (NFC) fields, such as through short-range communication radio components. Wireless communication optionally uses any of a variety of communication standards, protocols and technologies, including, but not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual Cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11d), IEEE 802.11e, IEEE 802.11f, IEEE 802.11g, IEEE 802.11g). 11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Utilizing Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)) and / or Short Message Service (SMS), or any other suitable communication protocol including communication protocols that have not been developed as of the filing date of this document.

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

[0069] The I / O subsystem 106 couples input / output peripherals on the device 100, such as a touch screen 112 and other input control devices 116, to a peripheral device interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, a depth camera controller 169, an intensity sensor controller 159, a tactile feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive / send electrical signals from other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, etc. In some embodiments, the input controller 160 is optionally coupled to any of the following (or none of the following): a keyboard, an infrared port, a USB port, and a pointing device such as a mouse. One or more buttons (e.g., Figure 2 208) optionally includes an increase / decrease button for volume control of the speaker 111 and / or the microphone 113. The one or more buttons optionally include a push button (e.g., Figure 2206 in). In some embodiments, the electronic device is a computer system that communicates with one or more input devices (e.g., via wireless communication, via wired communication). In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a touchpad as part of a touch-sensitive display). In some embodiments, the one or more input devices include one or more camera sensors (e.g., one or more optical sensors 164 and / or one or more depth camera sensors 175), such as for tracking a user's gestures (e.g., hand gestures and / or air 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. In some embodiments, an air gesture is a gesture that is detected without the user touching an input element that is part of the device (or is independent of an input element that is part of the device) and is based on detected movement of a part of the user's body through the air, including movement of the user's body relative to an absolute reference (for example, the angle of the user's arm relative to the ground or the distance of the user's hand relative to the ground), movement relative to another part of the user's body (for example, movement of the user's hand relative to the user's shoulder, movement of one of the user's hands relative to the user's other hand, and / or movement of the user's fingers relative to another finger or part of the user's hand), and / or absolute movement of a part of the user's body (for example, a tap gesture involving a hand moving a predetermined amount and / or speed in a predetermined position, or a shake gesture involving a predetermined speed or amount of rotation of a part of the user's body).

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

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

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

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

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

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

[0076] The touch screen 112 optionally has a video resolution of more than 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user optionally uses any suitable object or attachment such as a stylus, a finger, etc. to contact the touch screen 112. In some embodiments, the user interface is designed to work primarily through finger-based contacts and gestures, which may not be as accurate as stylus-based input due to the larger contact area of ​​the finger on the touch screen. In some embodiments, the device converts rough finger-based input into precise pointer / cursor positioning or commands for performing the actions desired by the user.

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

[0078] The device 100 also includes a power system 162 for powering the various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, a power fault detection circuit, a power converter or inverter, a power status indicator (e.g., a light emitting diode (LED)), and any other components associated with the generation, management, and distribution of power in a portable device.

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

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

[0081] Device 100 optionally also includes one or more contact intensity sensors 165 . Figure 1AA contact force sensor is shown coupled to a force sensor controller 159 in the I / O subsystem 106. Contact force sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other force sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). Contact force sensor 165 receives contact force information (e.g., pressure information or a surrogate for pressure information) from the environment. In some embodiments, at least one contact force sensor is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact force sensor is located on the back of device 100, opposite to touch screen display 112 located on the front of device 100.

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

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

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

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

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

[0087] The communication module 128 facilitates communication with other devices through one or more external ports 124, and also includes various software components for processing data received by the RF circuit 108 and / or the external port 124. The external port 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) is suitable for coupling directly to other devices, or indirectly through a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is connected to (trademark of Apple Inc.) devices.

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

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

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

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

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

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

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

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

[0096] Application 136 optionally includes the following modules (or instruction sets) or a subset or superset thereof:

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

[0098] ● Telephone module 138;

[0099] ● Video conferencing module 139;

[0100] ● Email client module 140;

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

[0102] ●Fitness support module 142;

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

[0104] ●Image management module 144;

[0105] ●Video player module;

[0106] ●Music player module;

[0107] ●Browser module 147;

[0108] ● Calendar module 148;

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

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

[0111] ●Search module 151;

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

[0113] ●Notepad module 153;

[0114] ● Map module 154; and / or

[0115] ●Online video module 155.

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

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

[0118] In conjunction with RF circuit 108, audio circuit 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, phone module 138 is optionally used to enter a character sequence corresponding to a phone number, access one or more phone numbers in contact module 137, modify an entered phone number, dial a corresponding phone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

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

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

[0121] In conjunction with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134, the instant messaging module 141 includes executable instructions for the following operations: entering a character sequence corresponding to an instant message, modifying previously entered characters, transmitting a corresponding instant message (e.g., using a short message service (SMS) or multimedia message service (MMS) protocol for telephone-based instant messaging or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, the transmitted and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments supported in MMS and / or enhanced messaging services (EMS). As used herein, "instant messaging" refers to both telephone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0149] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events occurring within a corresponding view of the user interface of the application. Each application view 191 of application 136-1 includes one or more event identifiers 180. Typically, the corresponding application view 191 includes multiple event identifiers 180. In other embodiments, one or more event identifiers in event identifiers 180 are part of an independent module, which is a higher-level object such as a user interface toolkit or application 136-1 from which methods and other properties are inherited. In some embodiments, the corresponding event handler 190 includes one or more of the following: data updater 176, object updater 177, GUI updater 178 and / or event data 179 received from event classifier 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177 or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more corresponding event handlers 190. In addition, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in the corresponding application view 191.

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

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

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

[0153] In some embodiments, event definition 186 includes a definition of an event for a corresponding user interface object. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view displaying three user interface objects on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a corresponding event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with a sub-event and the object that triggered the hit test.

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

[0155] When a corresponding event recognizer 180 determines that a sequence of sub-events does not match any event in event definition 186, the corresponding event recognizer 180 enters an event impossible, event failed, or event ended state, after which subsequent sub-events of the touch-based gesture are ignored. In this case, other event recognizers (if any) that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

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

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

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

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

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

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

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

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

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

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

[0166] Figure 3Each element in the above-mentioned elements in is optionally stored in one or more memory devices of the previously mentioned memory device. Each module in the above-mentioned modules corresponds to the instruction set for performing the function described above. The above-mentioned modules or computer programs (for example, instruction sets or including instructions) do not have to be realized with independent software programs (such as computer programs (for example, including instructions)), processes or modules, and therefore the various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores the subset of the above-mentioned modules and data structures. In addition, memory 370 optionally stores additional modules and data structures not described above.

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

[0168] Figure 4A An exemplary user interface of an application menu on portable multifunction device 100 according to some embodiments is illustrated. 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:

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

[0170] ●Time 404;

[0171] ●Bluetooth indicator 405;

[0172] ●Battery status indicator 406;

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

[0174] o an icon 416 of the phone module 138 labeled “Phone”, which optionally includes an indicator 414 of the number of missed calls or voicemails;

[0175] o an icon 418 of the email client module 140 labeled “Mail”, which optionally includes an indicator 410 of the number of unread emails;

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

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

[0178] ● Icons for other apps, such as:

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

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

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

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

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

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

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

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

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

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

[0189] o Icon 444 labeled "Notepad" of the Notepad module 153; and

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

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

[0192] Figure 4B The example embodiment has a touch-sensitive surface 451 (eg, touch screen display 112) that is separate from a display 450 (eg, touch screen display 112). Figure 3 a tablet device or a touch pad 355) (e.g., Figure 3Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting intensity of contacts on touch-sensitive surface 451 and / or one or more tactile output generators 357 for generating tactile output for a user of device 300.

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

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

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

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

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

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

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

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

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

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

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

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

[0205] As used herein, the term "open application" or "executing application" refers 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 executing application is optionally any of the following types of applications:

[0206] ● The active app currently displayed on the display of the device on which the app is being used;

[0207] ● 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

[0208] ●Not running but has data stored in memory (volatile and non-volatile respectively)

[0209] A suspended or dormant application that contains status information that can be used to resume execution of the application.

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

[0211] In some embodiments, the computer system is in a locked state or an unlocked state. In the locked state, the computer system is powered on and is operable, but it is prevented from executing a predefined set of operations in response to user input. The predefined set of operations optionally includes navigation between user interfaces, activation or deactivation of a predefined set of functions, and activation or deactivation of certain applications. The locked state can be used to prevent the unintentional or unauthorized use of a certain function of the computer system, or to activate or deactivate some functions on the computer system. In some embodiments, in the unlocked state, the computer system is powered on and is operable, and does not prevent it from executing at least a part of the predefined set of operations that cannot be executed when in the locked state. When the computer system is in the locked state, it is said that the computer system is locked. When the computer system is in the unlocked state, it is said that the computer is unlocked. In some embodiments, the computer system in the locked state optionally responds to a limited set of user inputs, and the limited set of user inputs includes an input corresponding to an attempt to convert the computer system to the unlocked state or an input corresponding to closing the computer system.

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

[0213] FIG. 6A to FIG. 6Q Illustrated are exemplary user interfaces for tracking body temperature information according to some embodiments. The user interfaces in these figures are used to illustrate the process described below, including Figure 7 process.

[0214] Fig. 6AAn electronic device 600 is illustrated having a touch-sensitive display 602. Fig. 6A , the electronic device 600 displays a health summary user interface 604 that displays various groups of health information related to a user (e.g., a user of the electronic device 600 and / or a user logged into the electronic device 600). The health summary user interface 604 includes selectable options 606a-606g. Option 606a displays heart rate information related to the user (e.g., the user's heart rate was measured to be 82bpm at 9:41am), and can be selected to display additional heart rate information not displayed in the health summary user interface 604 (e.g., additional heart rate measurements and / or earlier heart rate measurements). Option 606b displays body (e.g., wrist) temperature information related to the user, and can be selected to display additional body temperature information not displayed in the health summary user interface 604. In Fig. 6A , option 606b indicates that the wrist data temperature associated with the user has not been collected and / or no wrist temperature data is available for the user. Option 606c displays calorie information associated with the user (e.g., 1482 calories consumed on April 22), and can be selected to display additional calorie information not shown in the health summary user interface 604 (e.g., calorie information for the past few days). Option 606d displays effective calorie information associated with the user (e.g., 249 effective calories consumed on April 22), and can be selected to display additional effective calorie information not shown in the health summary user interface 604 (e.g., effective calorie information for the past few days). Option 606e displays step information associated with the user (e.g., 2,945 steps walked on April 22), and can be selected to display additional step information not shown in the health summary user interface 604 (e.g., the number of steps walked in the past few days and / or other days). Option 606f can be selected to display a user interface through which the user can access additional health information not displayed in the health summary user interface 604. Option 606g can be selected to initiate a process for modifying the health information displayed in the health summary user interface 604 (e.g., removing information currently included in the health summary user interface 604 and / or adding other information not currently included in the health summary user interface 604). The electronic device 600 also displays selectable options 608a-608c. Option 608a can be selected to display the health summary user interface 604. Option 608b can be selected to display a health information sharing user interface in which the user can view health information that the user is sharing with other users (e.g., other users that the user has selected and / or identified) and / or health information of other users that other users have selected to share with the user of the electronic device 600. Option 608c can be selected to browse additional health information related to the user. In Fig. 6A At , the electronic device 600 detects a user input 610 (eg, a touch input and / or a tap input) corresponding to a selection of the option 606b.

[0215] exist Figure 6B At , in response to user input 610, the electronic device 600 displays a wrist temperature user interface 612. The wrist temperature user interface 612 displays body temperature information (e.g., wrist temperature information) that has been collected from the user. In some embodiments, the wrist temperature user interface 612 displays relative body temperature information (e.g., body temperature information relative to a baseline temperature (e.g., x degrees higher than the baseline temperature and / or y degrees lower than the baseline temperature) rather than absolute body temperature information. The wrist temperature user interface 612 includes options 614a-614c that can be selected to display body temperature data for different time frames within the data chart 614d. For example, option 614a can be selected to view a week of body temperature data within the data chart 614d, option 614b can be selected to display a month of body temperature data within the data chart 614d, and option 614c can be selected to display six months of body temperature data within the data chart 614d. However, in Figure 6B In the data chart 614d, there is no temperature data available for the user (e.g., the user has not enabled temperature recording and / or the user has not taken appropriate steps to record temperature data), so no data is shown in the data chart 614d. The wrist temperature user interface 612 also includes an option 614h that can be selected to return to the health summary user interface 604, and an option 614g that can be selected to initiate the process for manually adding temperature data.

[0216] exist Figure 6B , the user of the electronic device 600 has not taken the necessary steps to record any temperature data. For example, the user has not enabled the appropriate settings for the temperature data to be collected, and / or the user has not taken the appropriate actions required for the temperature data to be collected. Therefore, the electronic device 600 displays a notification 614e within the wrist temperature user interface 612. The notification 614e instructs the user to wear his or her watch to bed, and also instructs the user to enable a sleep tracking function (e.g., a sleep focus mode state, as described in more detail below) in order to record temperature information. The electronic device 600 also displays an option 614f that can be selected to initiate a process for setting up and / or enabling the sleep tracking function. Figure 6B At , the electronic device 600 detects a user input 616 (eg, a touch input and / or a tap input) corresponding to a selection of the option 614f.

[0217] exist Figure 6CAt 616, in response to user input 616, electronic device 600 displays sleep tracking user interface 618. Sleep tracking user interface 618 displays sleep information that has been collected from the user. Sleep tracking user interface 618 includes options 620a-620c that can be selected to cause sleep data for different time frames to be displayed within data chart 620d. For example, option 620a can be selected to view one week of sleep data within data chart 620d, option 620b can be selected to view one month of sleep data within data chart 620d, and option 620c can be selected to view six months of sleep data within data chart 620d. However, in Figure 6C , the user has not taken the appropriate steps to record sleep data. Therefore, no data is shown in the data chart 620d. The sleep tracking user interface 618 also includes an option 620e that can be selected to display additional sleep data not shown in the sleep tracking user interface 618, an option 620i that can be selected to display the health summary user interface 604, and an option 620j that can be selected to initiate a process for manually adding and / or recording sleep data.

[0218] The sleep tracking user interface 618 includes next sleep schedule information 620f, selectable options 620g, and full sleep schedule information 620h. The next sleep schedule information 620f indicates the next sleep cycle that the user has specified. Figure 6C , the user has specified that the user intends to sleep from 11:00 p.m. that night to 6:00 a.m. the next day. Option 620g can be selected to modify the next sleep cycle (e.g., specify a start time and / or end time for the user's next sleep cycle). Full sleep schedule information 620h identifies the complete weekly sleep schedule that the user has specified, and can be selected to modify the user's weekly sleep schedule (e.g., specify the user's intended and / or desired sleep start time and sleep end time for each day of the week). Figure 6C In , the user has defined a sleep schedule that starts at 11:00 p.m. every day of the week and ends at 6:00 a.m. In some embodiments, the user can specify different sleep start times and different sleep end times for different days (e.g., for different days of the week).

[0219] Figure 6C Shows that the user has established a daily sleep schedule. FIG. 6D to FIG. 6G An example scenario will now be presented in accordance with some embodiments, in which a user enables sleep data recording and also enables body temperature information to be measured and recorded while the user is sleeping. Fig.6DAt 615 , the electronic device 600 displays a settings user interface 622. The settings user interface 622 displays various device settings for the electronic device 600, including an option 624 that can be selected to modify settings for one or more focus mode states for the electronic device 600, which will be described in more detail below. The one or more focus mode states include a sleep focus mode state, which is also referred to herein as a sleep tracking state. Fig.6D At , the electronic device 600 detects a user input 626 (eg, a touch input and / or a tap input) corresponding to a selection of the option 624 .

[0220] exist Fig. 6E At, in response to user input 626, the electronic device 600 displays a focus mode user interface 628. The focus mode user interface 628 includes options 630a-630d corresponding to different focus mode states of the electronic device 600. Option 630a corresponds to a do not disturb focus mode state, option 630b corresponds to a sleep focus mode state, option 630c corresponds to a personal focus mode state, and option 630d corresponds to a work focus mode state. Each of these options can be selected to modify one or more settings for the corresponding focus mode state. In some embodiments, the focus mode state can be selectively enabled by the user to indicate that the user does not want to be disturbed when the focus mode state is enabled. In some embodiments, when the focus mode state of the electronic device 600 is enabled (for example, Fig. 6E In some embodiments, when the focus mode state is not enabled and the electronic device 600 receives a message (e.g., a text message) from another user, the electronic device 600 displays a notification corresponding to the message. However, when the focus mode state is enabled, in some embodiments, the electronic device 600 does not display a notification corresponding to the received message, as described in more detail below. In some embodiments, different focus mode states result in different settings being applied. For example, in some embodiments, a first focus mode state will allow notifications from a certain group of users, but a second focus mode state will not allow notifications from those users. In some embodiments, the sleep focus mode state will result in the suppression of notifications and the collection of body temperature information, while different focus mode states (e.g., do not disturb and / or work) will result in the suppression of notifications without resulting in the collection of body temperature information.

[0221] The focus mode user interface 630e includes a toggle switch 630e. When the toggle switch 630e is toggled to an enabled (or "on") state and the electronic device 600 enters a specific focus mode state (e.g., begins operating in a specific focus mode state) (e.g., automatically and / or based on user input), one or more external devices corresponding to the electronic device 600 (e.g., other devices corresponding to the same user) are also caused to enter the specific focus mode state, so that notifications suppressed on the electronic device 600 during the focus mode state are also suppressed on the other corresponding devices. When the toggle switch 630e is toggled to a disabled (or "off") state, when the electronic device 600 enters a specific focus mode state and / or operates in the specific focus mode state, the other corresponding devices are not automatically caused to operate in the specific focus mode state, so that even if the electronic device 600 suppresses notifications when it operates in the selected focus mode state, different corresponding devices can still output notifications. The focus mode user interface 628 also includes an option 630f that can be selected to return to the settings user interface 622. Fig. 6E At , the electronic device 600 detects a user input 632 (eg, a touch input and / or a tap input) corresponding to a selection of the option 630b.

[0222] exist Fig. 6F At , in response to user input 632, the electronic device 600 displays a sleep focus mode user interface 634. The sleep focus mode user interface 634 includes various options 636a-636h that can be selected to modify one or more settings corresponding to the sleep focus mode state of the electronic device 600. Option 636a can be selected by the user to turn on the sleep focus mode state (e.g., so that the electronic device 600 enters the sleep focus mode state and / or operates in the sleep focus mode state) or turn off the sleep focus mode state (e.g., so that the electronic device 600 exits the sleep focus mode state and / or stops operating in the sleep focus mode state). Fig. 6F , option 636a is in the off position, thereby indicating that the electronic device 600 is not operating in the sleep focus mode state (and notifications are not suppressed).

[0223] Option 636b can be selected to initiate a process for identifying one or more people (e.g., one or more contacts) who are allowed to disturb the user when the sleep focus mode state is enabled (e.g., turned on and / or active). In other words, for a certain subset of people identified by the user, even when the electronic device 600 is operating in the sleep focus mode state, notifications related to those people (e.g., notifications of messages and / or calls received from those people) are not suppressed, while notifications related to other people are suppressed. For example, in some embodiments, if the user selects a first contact who is allowed to disturb the user when the sleep focus mode state is active, when a message is received from the first contact when the sleep focus mode state is active, the electronic device 600 will output a notification (e.g., display a notification, output an audio notification, and / or output a tactile notification), as if the sleep focus mode state is inactive. However, notifications related to messages from other users who are not selected by the user will be suppressed because the sleep focus mode state is active. Similarly, option 636c can be selected to initiate a process for identifying one or more applications that are allowed to interrupt the user while active in the sleep focus mode state (eg, while the electronic device 600 is operating in the sleep focus mode state).

[0224] Option 636d can be selected to open a user interface in which a user can enable or disable a focus mode state setting. When the focus mode state setting is enabled, other users (e.g., other users trying to contact the user of the electronic device 600) can see an indication of when the sleep focus mode state for the electronic device 600 is active (e.g., an indication that the electronic device 600 is operating in the sleep focus mode state and / or that notifications have been suppressed). When the focus mode state setting is disabled, other users cannot see when the electronic device 600 is operating in the sleep focus mode state. Option 636e can be selected to display a user interface in which a user can enable or disable a home screen notification setting. In some embodiments, when the home screen notification setting is enabled, notifications that would normally be displayed on the home screen of the electronic device 600 (e.g., when the sleep focus mode state is inactive) are also displayed on the home screen of the electronic device 600 when the sleep focus mode state is active. When the home screen notification setting is disabled, notifications that would normally be displayed on the home screen of the electronic device 600 are suppressed (e.g., not displayed) when the sleep focus mode state is active. Option 636f can be selected to display a user interface in which a user can enable or disable a lock screen notification setting. In some embodiments, when the lock screen notification setting is enabled, notifications that would normally be displayed on the lock screen of the electronic device 600 (e.g., when the sleep focus mode state is not active) are also displayed on the lock screen of the electronic device 600 when the sleep focus mode state is active. When the lock screen notification setting is disabled, notifications that would normally be displayed on the lock screen of the electronic device 600 are suppressed (e.g., not displayed) when the sleep focus mode state is active.

[0225] Option 636g can be selected by the user to toggle option 636g between an on state and an off state. When option 636g is in the on state, the electronic device 600 automatically enters and / or exits the sleep focus mode state according to the sleep schedule specified by the user (e.g., the electronic device 600 automatically enters (e.g., activates) the sleep focus mode state at the bedtime specified by the user, and the electronic device 600 automatically exits (e.g., deactivates) the sleep focus mode state at the wake-up time specified by the user). When option 636g is in the off state, the electronic device 600 does not automatically enter and / or exit the sleep focus mode state according to the sleep schedule specified by the user, and the user must manually activate or deactivate the sleep focus mode state (e.g., using option 636a).

[0226] Option 636h can be selected by the user to toggle option 636h between an on state and an off state. When option 636h is on, the electronic device 600 collects body temperature information when the user is sleeping (e.g., when the electronic device 600 is in a sleep focus mode state). When option 636h is off, the electronic device 600 does not collect body temperature information and / or does not record body temperature information when the user is sleeping (e.g., when the electronic device 600 is in a sleep focus mode state).

[0227] The sleep focus mode user interface 634 also includes a menu that displays the next sleep schedule information and can be selected to modify the next sleep schedule information (similar to Figure 6C Next sleep schedule information 620f and option 620g in the display, and option 636i that displays the full sleep schedule information and can be selected to modify the full sleep schedule information (similar to Figure 6C The sleep focus mode user interface 634 also includes options 636k-636m. Option 636k can be selected to display the sleep tracking user interface 618. Option 636l can be selected to initiate a process for deleting (e.g., removing) the sleep focus mode state from the electronic device 600. Option 636m can be selected to display the focus mode user interface 628. Fig. 6F At this point, the electronic device 600 detects user input 638a (e.g., touch input and / or tap input) corresponding to the selection of option 636a, user input 638b (e.g., touch input and / or tap input) corresponding to the selection of option 636g, and user input 638c (e.g., touch input and / or tap input) corresponding to the selection of option 636h.

[0228] exist Figure 6G At, in response to user input 638a-638c, options 636a, 636g, and 636h have each been toggled to the "on" position. Option 636a toggled to the on position indicates that the sleep focus mode state has been activated and the electronic device 600 is now operating in the sleep focus mode state. Option 636g toggled to the on position indicates that the electronic device 600 will automatically enter and exit the sleep focus mode state according to the sleep schedule specified by the user. Option 636h toggled to the on position indicates that the electronic device 600 will automatically collect body temperature information from the user (e.g., via an external device and / or wearable device, such as a smart watch or other temperature sensor) when the electronic device 600 is operating in the sleep focus mode state.

[0229] exist Figure 6HAt 600, the electronic device 600 displays a lock screen user interface 640. The lock screen user interface 640 includes an indication 642a indicating that the electronic device 600 is in a locked state. The lock screen user interface 640 also includes current time information 642b, current date information 642c, an object 642g that can be selected to selectively enable or disable a flash, and an object 642f that can be selected to display a camera user interface.

[0230] exist Figure 6H In the example, the electronic device 600 operates in the sleep focus mode state. For example, the electronic device 600 enters the sleep focus mode state in response to the user input 638a, or in another example, the electronic device 600 enters the sleep focus mode state based on Figure 6G Option 636g in is toggled to the on state and automatically enters the sleep focus mode state in response to the user-defined sleep schedule. The electronic device 600 displays an indication 642d indicating that the electronic device 600 is in the sleep focus mode state. The electronic device 600 also displays an alarm indication 642e indicating that the user has not set a wake-up alarm. In some embodiments, when the user has set a wake-up alarm, the alarm indication 642e displays the time when the wake-up alarm will go off.

[0231] Figure 6H Also depicted is an electronic device 800 that is a smartwatch having a touch screen display 802, a rotatable and depressible input mechanism 804, and buttons 806. The electronic device 644 displays a lock screen user interface 644 indicating that the electronic device 800 is locked. The lock screen user interface includes a current time indication 646a and a current date indication 646b. Figure 6H In the embodiment, the electronic device 800 is also operating in the sleep focus mode state, as indicated by indication 646d. For example, in some embodiments, as Fig.6D As a result of the option 630e being in the on position, when the electronic device 600 enters the sleep focus mode state, the electronic device 800 also automatically enters the sleep focus mode state. The electronic device 800 also displays an alarm indication 646c, similar to the alarm indication 642e.

[0232] FIG. 6H to FIG. 6I An example implementation is illustrated in which, when an electronic device (e.g., electronic device 600 and / or electronic device 800) is in a sleep focus mode state, additional user input is required to transition the electronic device from a locked state to an unlocked state and / or to stop displaying a lock screen user interface, compared to when the electronic device is not operating in the sleep focus mode state.

[0233] exist Figure 6HAt , the electronic device 800 detects a user input 648, which is a press (e.g., a push) of the rotatable and depressible input mechanism 648. Figure 6H , the electronic device 600 receives biometric information (e.g., a facial scan and / or a facial image) corresponding to a user via an input device 601 (e.g., a camera and / or a depth sensor).

[0234] exist Fig.6I In response to the user input 648, the electronic device 800 displays a user interface 650 instructing the user to rotate the rotatable and depressible input mechanism 804 to unlock the electronic device 800. In some embodiments, when the electronic device 800 is not operating in the sleep focus mode state, the user input 648 will be sufficient to unlock the electronic device 800. However, because the electronic device 800 is operating in the sleep focus mode state, additional user input is required to rotate the input mechanism 804. In addition, in Fig.6I In response to receiving the biometric information from the user, the electronic device 600 displays an indication 642a as an unlocked lock, indicating that the biometric information from the user successfully authenticated the user. In some embodiments, when the electronic device 600 is in this state, and when the electronic device 600 is not operating in the sleep focus mode state, swiping up will be sufficient to stop the display of the lock screen user interface 640 and unlock the electronic device 600. However, in the depicted embodiment, because the electronic device 600 is operating in the sleep focus mode state, additional user input is required to stop the display of the lock screen user interface. In some embodiments, from Fig.6I In the state shown, in order to stop display of the lock screen user interface 640, the user is first required to press the object 642h and then provide an upward slide input, and / or the user is required to provide two upward slide inputs.

[0235] exist Figure 6J At, the electronic device 600 displays the above reference Fig. 6A The health summary user interface 604 is depicted. However, now that the user has enabled temperature recording (e.g., by enabling Figure 6G Option 636h in FIG. 10 ), option 606b now indicates that the electronic device 600 is "collecting data". Figure 6J At , the electronic device 600 detects a user input 652 (eg, a touch input and / or a tap input) corresponding to a selection of the option 606b.

[0236] exist Figure 6K In response to user input 652, the electronic device 600 displays the wrist temperature user interface 612. Now that the user has enabled temperature recording, the wrist temperature user interface 612 no longer displays the notification 614e, such as Figure 6BHowever, in Figure 6K , the electronic device 600 has not yet collected enough body temperature data to accurately determine the baseline temperature for the user. Thus, the wrist temperature user interface 612 still does not display any actual body temperature data in the data chart 614d, and displays a notification 654 indicating that more body temperature information is needed.

[0237] exist Figure 6L From Figure 6K Several months have passed, and the electronic device 600 has collected a threshold amount of temperature information from the user (e.g., has collected temperature information for at least five nights and / or five consecutive nights). As a result, the wrist temperature user interface 612 now displays the user's temperature data in the data chart 614d, and no longer displays the notification 654. Figure 6L , additional options 656a-656c in the wrist temperature user interface 612 are shown. In some embodiments, options 656a-656c are part of the wrist temperature user interface 612 in the previous figures, but are not shown in those figures. Option 656a can be selected to selectively enable or disable the display of body temperature information within the health summary user interface 604. Option 656b can be selected to display additional body temperature information not shown in the wrist temperature user interface 612. Option 656c can be selected to view information related to one or more external devices (e.g., one or more watches and / or other wearable devices or sensors for collecting body temperature information for the user) from which body temperature information for the user is collected. In Figure 6L At the point, the electronic device 600 detects user input 658a (e.g., touch input and / or tap input) corresponding to selection of option 614b, user input 658b (e.g., touch input and / or tap input) corresponding to selection of a data point in a data chart 614d, and user input 658c (e.g., touch input and / or tap input) corresponding to selection of option 656b.

[0238] exist Figure 6M At 614d, in response to user input 658b corresponding to the selection of a data point in the data chart 614d, the electronic device 600 displays a data box 660. The user input 658b corresponds to the selection of a data point corresponding to the date Friday, June 24, 2022. In response to the user input 658b, the electronic device 600 displays a data box 660, which includes additional information about the data point (e.g., the user's body temperature on Friday, June 24, 2022 was measured to be 0.5 degrees below its baseline temperature). In some embodiments, the user can select any of the data points displayed in the data chart 614d to view additional information related to the selected data point.

[0239] exist Figure 6NIn response to user input 658a corresponding to the selection of option 614b, electronic device 600 displays one month of user temperature data in data chart 614d. Figure 6M As shown in , a user can select any data point within data chart 614d to view additional information about the selected data point.

[0240] exist Fig.6O At , in response to user input 658c corresponding to selection of option 656b, the electronic device 600 displays a user interface 662. The user interface 662 includes representations 664a-664g of multiple body temperature information collection instances. For example, representation 664a represents a first body temperature information collection instance that occurred on June 25, 2022, and representation 664b represents a second body temperature information collection instance that occurred on June 24, 2022, and so on. In some embodiments, the user interface 662 includes representations of all instances of collecting body temperature information from the user, or representations of all body temperature information collection instances that occurred within a predetermined time period (e.g., in the current calendar year, in the last month, in the last three months, in the last six months, in the last year, in the last three years, etc.). The user interface 662 also includes an option 664h that can be selected to return to the wrist temperature user interface 612. At Fig.6O At , the electronic device 600 detects a user input 666 (eg, a tap input and / or a touch input) corresponding to a selection of the representation 664a.

[0241] exist Figure 6PAt, in response to user input 666, the electronic device 600 displays a user interface 668. The user interface 668 displays additional information related to the selected body temperature information collection instance. For example, in the depicted embodiment, the user interface 668 includes start time information 670b (e.g., the time when the body temperature information collection for this particular collection instance starts), end time information 670c (e.g., the time when the body temperature information collection for this particular collection instance ends) and data addition information 670e (e.g., the date and time when the electronic device 600 receives the body temperature information from the external device). The user interface 668 also includes source information 670d for identifying the external device that collects the body temperature information and / or the external device from which the body temperature information is received. In some embodiments, the electronic device 600 aggregates body temperature information collected by multiple external devices and / or received from multiple external devices. In some embodiments, the wrist temperature user interface 612 displays body temperature information collected by multiple external devices and / or received from multiple external devices. The user interface 668 also includes surface temperature information 670f and wrist temperature information 670a. As described above, wrist temperature user interface 612 displays baseline temperature information and does not display actual temperature measurements (e.g., actual measured temperatures). However, user interface 668 displays surface temperature information 670f, which indicates the actual temperature measured at the surface of the user's skin, and wrist temperature information 670a, which indicates the user's body temperature derived from surface temperature information 670f.

[0242] exist Figure 6Q In FIG. 6 , the electronic device 600 displays the wrist temperature user interface 612. However, in Figure 6Q , the user has not yet consistently worn his or her wearable device to sleep, and therefore the electronic device 600 has not been able to consistently collect body temperature information while the user is sleeping. Therefore, the electronic device 600 has determined that the electronic device 600 does not have enough data to continue to accurately display body temperature information (e.g., the electronic device 600 has collected less than a threshold amount of body temperature information during a predetermined time period (e.g., in the last week, last month, etc.)). In response to this determination, the electronic device 600 stops displaying body temperature information in the data chart 614d and displays an indication 672, which informs the user that the electronic device 600 does not have enough body temperature information and instructs the user to consistently wear his or her wearable device to sleep.

[0243] Figure 7is a flow chart illustrating a method for tracking body temperature information using a computer system according to some embodiments. Method 700 is performed at a computer system (e.g., 100, 300, 500) (e.g., a wearable device, a smart watch, a smart phone, a tablet computer, and / or a computer system that controls an external display) (e.g., 600, 800) that communicates with: a display generation component (e.g., a display controller, a touch-sensitive display system; and / or a display (e.g., integrated and / or connected)) (e.g., 602, 802), one or more input devices (e.g., a touch-sensitive surface (e.g., a touch-sensitive display); an accelerometer; a rotatable input mechanism; a pressable input mechanism; and / or a rotatable and pressable input mechanism (e.g., 601, 602, 802, 804, 806), and a temperature sensor (e.g., an integrated sensor; a sensor integrated into an external device that communicates with the computer system (e.g., a temperature sensor integrated into device 800). Some operations in method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0244] As described below, method 700 provides an intuitive way to track body temperature information. The method reduces the cognitive burden of tracking body temperature information for users, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to track body temperature information faster and more efficiently saves power and increases the time interval between battery charges.

[0245] The computer system (e.g., 600, 800) receives (702) via one or more input devices (e.g., 601, 602, 802, 804, 806) input (e.g., a first set of user inputs and / or one or more user inputs) (e.g., one or more touch inputs, one or more non-touch inputs, and / or one or more gestures) corresponding to a request to enter a sleep tracking mode (e.g., 638a and / or 638b and / or define a sleep schedule (e.g., the sleep schedule shown in 636i, 636j) (e.g., wherein one or more notifications (e.g., a first type of notification) received by the computer system are suppressed and / or wherein sleep related to the user (e.g., sleep schedule) is defined. In some embodiments, entering the sleep tracking mode includes initiating a process for collecting user temperature information. During the sleep tracking mode (706) (e.g., when the computer system is in the sleep tracking mode), the computer system causes a first set of user temperature information (e.g., user temperature information displayed in the data chart 614d) to be collected via a temperature sensor (e.g., a temperature sensor integrated into the electronic device 800) (e.g., one or more user temperature measurements).

[0246] The computer system receives (708) a first type of notification data (e.g., notifications of a type that are subject to suppression when in sleep tracking mode) (in some embodiments, all notifications are suppressed in sleep tracking mode) (in some embodiments, a second type of notification (e.g., emergency notifications, wake-up alarm notifications) are not suppressed when in sleep tracking mode). In response to receiving the first type of notification data (710): based on a determination (712) that the computer system is not in sleep tracking mode, the computer system outputs a first notification corresponding to the first type of notification data (e.g., displays the first notification; causes a display generation component to transition from an inactive state (e.g., off and / or a state in which content is not displayed on the display generation component) to an active state (e.g., on and / or a state in which content is displayed); outputs an audio output; and / or outputs a tactile output); and based on a determination (714) that the computer system is currently in sleep tracking mode (e.g., FIG. 6H to FIG. 6I ) (for example, when receiving the first type of notification data, the computer system is in a sleep tracking mode), the computer system abandons outputting (for example, suppresses) a first notification corresponding to the first type of notification data (for example, abandons displaying the first notification; abandons causing the display generating component to transition from an inactive state to an active state; abandons outputting an audio output; and / or abandons outputting a tactile output).

[0247] After collecting the first set of user temperature information (716), the computer system displays a display including one or more sets of user temperature information (e.g., displayed on a display generating component (e.g., 602) Figure 6L A temperature user interface (e.g., 612) is provided for representing body temperature information in a data chart 614d in the computer system (e.g., user body temperature information associated with, collected from, and / or collected by a user of the computer system), wherein the one or more sets of user body temperature information include a first set of user body temperature information (e.g., a temperature user interface depicting a representation of a user's body temperature over a period of time (e.g., depicting and / or showing changes in the user's body temperature)).

[0248] Automatically collecting a first set of user temperature information when the device is in sleep tracking mode allows user temperature information to be collected with less user input, thereby reducing the number of user inputs required to perform operations. Collecting user temperature information during sleep tracking mode initiated by user input reduces the risk of erroneously collecting temperature information during a non-sleep state (e.g., due to false positives in sleep state determinations); doing so can improve the quality of the data and improve operations performed by the computer system based on temperature data attributed to the sleep state, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user provide appropriate input and reducing errors), and in addition, reduces power usage and extends the battery life of the device by enabling the user to use the system more quickly and efficiently.

[0249] In some embodiments, the computer system receives, via one or more input devices, a command corresponding to entering a mode other than sleep tracking mode (e.g., Fig. 6E The first silent mode (e.g., Fig. 6E In some embodiments, in response to receiving the second input, the computer system enters a first silent mode (enabling the first silent mode and / or causing the computer system to operate in the first silent mode) (in some embodiments, without entering a sleep tracking mode) without initiating a process of collecting body temperature information. In some embodiments, the computer system collects body temperature information while abandoning storage of the body temperature information, and / or collects the second type of body temperature information while abandoning collection and / or storage of the third type of body temperature information.

[0250] In some embodiments, the computer system receives the second notification data of the first type. In some embodiments, in response to receiving the second notification data of the first type: according to the computer system is not in the first silent mode (for example, Fig. 6E The Do Not Disturb state, the Personal Focus Mode state, and / or the Work Focus Mode state in the computer system are not active and / or enabled) and the computer system is not in a sleep tracking mode (e.g., Fig. 6E The computer system outputs a second notification corresponding to the second notification data of the first type (e.g., displays the second notification); causes the display generation component to transition from an inactive state (e.g., a state that is off and / or in which content is not displayed on the display generation component) to an active state (e.g., a state that is on and / or in which content is displayed); outputs an audio output; and / or outputs a tactile output); and according to the computer system currently being in the first silent mode (e.g., Fig. 6E At least one of the Do Not Disturb state, personal focus mode state and / or work focus mode state in the first silent mode is active and / or enabled) (for example, when the computer system is in the first silent mode when the first type of second notification data is received), the computer system abandons outputting (for example, suppressing) a notification corresponding to the first type of second notification data (for example, abandoning displaying the second notification; abandoning causing the display generation component to transition from an inactive state to an active state; abandoning outputting audio output; and / or abandoning outputting tactile output). Automatically suppressing notifications when the computer system is in the first silent mode allows the user to perform the operation with less user input, thereby reducing the number of user inputs required to perform the operation. In addition, automatically collecting temperature information when the computer system is in sleep tracking mode, and abandoning collecting temperature information when the computer system is in the first silent mode, allows the user to perform these operations with less user input.

[0251] In some embodiments, the computer system receives, via one or more input devices, input corresponding to a defined sleep schedule (e.g., Figure 6C (e.g., 620f, 620h) and / or Fig. 6FIn some embodiments, the computer system receives a third input (e.g., a third set of user inputs and / or one or more user inputs) (e.g., one or more touch inputs, one or more non-touch inputs, and / or one or more gestures) requesting a sleep schedule (e.g., a sleep schedule shown in 636i, 636j), wherein for at least a first day (e.g., a first day of the week (e.g., Sunday, Monday, Tuesday, etc.) and / or a first calendar date), the sleep schedule includes a first sleep start time and a first sleep end time. In some embodiments, for a second day different from the first day (e.g., a second day of the week and / or a second calendar date), the sleep schedule includes a second sleep start time and a second sleep end time. After receiving the third input: based on a determination that the current time corresponds to the first sleep start time (e.g., the current time is the first sleep start time), the computer system enters a sleep tracking mode (e.g., FIG. 6H to FIG. 6I In some embodiments, the sleep schedule defines the sleep start time and sleep end time of multiple days. In some embodiments, the sleep start time and / or sleep end time are the same for two or more of the multiple days. In some embodiments, the sleep start time and / or sleep end time are different for two or more of the multiple days. In some embodiments, after receiving the third input, and according to the determination that the current time corresponds to the first sleep end time (e.g., the current time is the sleep end time), the computer system exits the sleep tracking mode (e.g., the computer system is converted from the sleep tracking mode to the non-sleep tracking mode). Automatically entering the sleep tracking mode based on a user-defined schedule allows the user to enable the sleep tracking mode with less user input, thereby reducing the number of user inputs required to perform the operation.

[0252] In some embodiments, causing a first set of user temperature information (e.g., the user temperature information shown in chart 614d) to be collected includes: causing a first external device (e.g., 800) (e.g., a wearable device, a smart watch, a smart phone, a tablet computer, and / or a computer system controlling an external display) separate from the computer system (e.g., 600) to collect the first set of user temperature information; and receiving the first set of user temperature information from the first external device (e.g., via wireless and / or wired transmission) (e.g., directly or indirectly). Automatically causing the first external device to collect the first set of user temperature information when the computer system is in sleep tracking mode allows the user temperature information to be collected with less user input, thereby reducing the number of user inputs required to perform the operation.

[0253] In some embodiments, before receiving the input, the computer system displays a temperature user interface (e.g., 612) via a display generation component, including: based on the fact that a threshold amount of temperature information (e.g., user temperature information associated with, collected from, and / or collected by a user of the computer system) has not yet been collected (e.g., Figure 6K ) (e.g., a determination that less than a threshold number of days of temperature information has been collected and / or less than a threshold number of hours of temperature information has been collected), an indication that a threshold amount of temperature information has not been collected (e.g., Figure 6K 614d and / or 654) (and in some embodiments, foregoing displaying a representation of one or more sets of user temperature information (e.g., collected from the user and / or collected by the computer system)); and determining that a threshold amount of temperature information has been collected (e.g., Figure 6L ), display one or more sets of user temperature information (for example, display Figure 6L In one embodiment, the present invention provides a representation of the temperature information in the data chart 614d in the computer system (e.g., user temperature information associated with, collected from, and / or collected by a user of the computer system) without displaying an indication that a threshold amount of temperature information has not been collected (e.g., 654). Displaying an indication that a threshold amount of temperature information has not been collected provides visual feedback to the user regarding the status of the system (e.g., the system has not collected a threshold amount of temperature information), thereby providing improved visual feedback to the user.

[0254] In some embodiments, when displaying one or more sets of user temperature information (e.g., Figure 6L After displaying a temperature user interface (e.g., 612) represented by 612 in the computer system, the computer system displays a second instance of the temperature user interface (e.g., 612), wherein: based on a determination that a second set of criteria is met (e.g., based on a determination that a temperature collection frequency criterion is met (e.g., a threshold amount of temperature information has been collected within a defined time period (e.g., the immediately preceding week, month, three months, six months, and / or year)), the second instance of the temperature user interface includes a second set of user temperature information (e.g., Figure 6L and a second instance of the temperature user interface that does not include a representation of the second set of user temperature information (e.g., a set of user temperature information collected after the first set of user temperature information); and a determination that a second set of criteria is not met (e.g., a determination that a temperature collection frequency criterion is not met (e.g., a threshold amount of temperature information has not been collected within a defined time period (e.g., the immediately preceding week, month, three months, six months, and / or year)), the second instance of the temperature user interface does not include a representation of the second set of user temperature information (e.g., a display of Figure 6Q672d in the data graph 672d) (and in some embodiments, does not include a representation of the user's body temperature information) and includes a second indication indicating that the second set of criteria is not met (e.g., Figure 6Q Displaying an indication that the second set of criteria are not met provides visual feedback to the user about the state of the system (e.g., the system has determined that the second set of criteria are not met), thereby providing improved visual feedback to the user.

[0255] In some embodiments, while displaying the temperature user interface (e.g., 612), the computer system receives a selection input (e.g., 658a) (e.g., one or more touch inputs, one or more non-touch inputs, and / or one or more gestures) via one or more input devices. In response to receiving the selection input: based on a determination that the selection input corresponds to a selection of a first time frame option (e.g., 614a, 614b, 614c) corresponding to a first time frame (e.g., a first duration (e.g., one week, one month, six months, and / or one year)), the computer system displays within the temperature user interface a representation of one or more sets of user temperature information corresponding to the first time frame (e.g., in Figure 6L In FIG. 6 , the user interface 612 displays body temperature information for a weekly time frame. Figure 6N In the embodiment, the user interface 612 displays body temperature information for a monthly time frame) (e.g., collected during a first time frame and / or collected during a first duration corresponding to a first time frame option) (and optionally, representations of user body temperature information collected outside the first time frame and / or outside the first duration corresponding to the first time frame option are not displayed); and based on a determination of a selection input corresponding to a second time frame option (e.g., 614a, 614b, 614c) different from the first time frame option, wherein the second time frame option corresponds to a second time frame different from the first time frame (e.g., a second duration (e.g., one week, one month, six months, and / or one year)), the computer system displays representations of one or more sets of user body temperature information corresponding to the second time frame within the body temperature user interface (e.g., in Figure 6L In FIG. 6 , the user interface 612 displays body temperature information for a weekly time frame. Figure 6NIn the embodiment, the user interface 612 displays body temperature information for a monthly time frame) (e.g., collected during the second time frame and / or collected during the second duration corresponding to the second time frame option) (and optionally, representation of the user's body temperature information collected outside the second time frame and / or outside the second duration corresponding to the second time frame option is not displayed). Providing different selectable options corresponding to different time frames that allow the user to display body temperature information corresponding to different time frames allows the user to view different groups of body temperature information with less user input, thereby reducing the number of user inputs required to perform operations.

[0256] In some embodiments, one or more sets of representations of user temperature information include one or more relative temperature measurements (e.g., Figure 6L , Figure 6M and Figure 6N The data graph 614 in the sleep tracking mode displays relative temperature measurements (e.g., +2, +1, 0, -1, -2)) (e.g., relative temperature measurements indicating degrees above and / or below a baseline temperature) (and optionally, does not include absolute temperature measurements). Automatically collecting a first set of user temperature information when the device is in sleep tracking mode allows for collecting user temperature information with less user input, thereby reducing the number of user inputs required to perform an operation.

[0257] In some embodiments, the computer system displays a first detail user interface (e.g., 668) corresponding to the first set of user temperature information via a display generation component, wherein the first detail user interface includes information about the first set of user temperature information (e.g., 670a-670f) not displayed in the temperature user interface (e.g., collection start time, collection end time, actual temperature measurement information (while in some embodiments, the temperature user interface displays relative temperature measurement information) and / or external device information (e.g., information identifying the name, construction and / or model of the external device used to collect the first set of user temperature information)). In some embodiments, the computer system displays a second detail user interface corresponding to a second set of user temperature information different from the first set of user temperature information, wherein the second detail user interface includes information about the second set of user temperature information not displayed in the temperature user interface. Displaying the first detail user interface provides visual feedback to the user about the status of the system (e.g., the system has collected additional information about the first set of user temperature information not included in the temperature user interface), thereby providing improved visual feedback to the user. Providing a first detail user interface in which the user can view additional details about the first set of user temperature information allows the user to perform the operation with less user input.

[0258] In some embodiments, the first details user interface (e.g., 668) includes: a start time (e.g., 670b) corresponding to the first set of user temperature information (e.g., the time and / or date when the collection of the first set of user temperature information is started); and an end time (e.g., 670c) corresponding to the first set of user temperature information (e.g., the time and / or date when the collection of the first set of user temperature information is ended). Displaying the first details user interface provides the user with visual feedback about the status of the system (e.g., the system has collected additional information about the first set of user temperature information that is not included in the temperature user interface), thereby providing improved visual feedback to the user. Providing a first details user interface in which the user can view additional details about the first set of user temperature information allows the user to perform the operation with less user input.

[0259] In some embodiments, the temperature user interface (e.g., 612) includes relative temperature information corresponding to the first set of user temperature information (e.g., relative temperature measurements indicating degrees above the baseline temperature and / or below the baseline temperature) (and optionally, does not include absolute temperature measurements); the first details user interface (e.g., 668) includes one or more absolute temperature measurements (e.g., 670a, 670f) corresponding to the first set of user temperature information (e.g., actual measured temperatures and / or measurements indicating the user's actual temperature). Displaying the first details user interface provides visual feedback to the user about the state of the system (e.g., the system has collected additional information about the first set of user temperature information that is not included in the temperature user interface), thereby providing improved visual feedback to the user. Providing a first details user interface in which the user can view additional details about the first set of user temperature information allows the user to perform the operation with less user input.

[0260] In some embodiments, the first details user interface (e.g., 668) includes external device information (e.g., 670d) corresponding to the first set of user temperature information (e.g., information about an external device (e.g., separate from the computer system) used to collect the first set of user temperature information (e.g., the name, model, and / or other identifier of the external device). Displaying the first details user interface provides the user with visual feedback about the status of the system (e.g., the system has collected additional information about the first set of user temperature information that is not included in the temperature user interface), thereby providing improved visual feedback to the user. Providing a first details user interface in which the user can view additional details about the first set of user temperature information allows the user to perform the operation with less user input.

[0261] In some embodiments, a computer system (e.g., 600) receives first notification data corresponding to one or more messages received from a first external user (e.g., a first external user different from a user of the computer system and / or a first external user of a first external device separate from the computer system) and / or one or more messages received from a first application (e.g., a first application running on the computer system and / or a first application running on an external device separate from the computer system). In response to receiving the first notification data: according to the computer system not being in the sleep tracking mode (e.g., option 636a is in an inactive state and / or an off state) (e.g., when the first notification data is received), the computer system outputs a second notification corresponding to the first notification data (e.g., displays the second notification; causes the display generation component to transition from an inactive state (e.g., off and / or a state in which content is not displayed on the display generation component) to an active state (e.g., on and / or a state in which content is displayed); outputs an audio output; and / or outputs a tactile output); and according to the computer system currently being in the sleep tracking mode (e.g., option 636a is in an active state and / or an on state) (e.g., when the first notification data is received), and the first notification data includes notification data of the second type (e.g., notification data suppressed when the computer system is in the sleep tracking mode, notification data corresponding to a first subset of external users (e.g., in Fig. 6F 636b in the object 636b) and / or corresponding to notification data of one or more messages received from a first subset of applications (e.g., in Fig. 6F Automatically suppressing notifications related to messages received from other users or applications when the computer system is in sleep tracking mode allows the user to perform these operations with less user input.

[0262] In some embodiments, in response to receiving first notification data: based on the computer system currently being in sleep tracking mode (e.g., option 636a is active and / or turned on) and the first notification data including a third type of notification data different from the second type (e.g., notification data that is not suppressed when the computer system is in sleep tracking mode, corresponding to a second subset of external users different from the first subset (e.g., a subset of pre-approved and / or pre-selected external users) (e.g., in Fig. 6F636b in the example) and / or corresponding to one or more messages received from a second subset of applications (e.g., a subset of pre-approved and / or pre-selected external users) that is different from the first subset (e.g., in the example). Fig. 6F The computer system outputs a second notification corresponding to the first notification data. Notifications related to messages received from certain unapproved users or applications are automatically suppressed when the computer system is in sleep tracking mode, while notifications related to messages received from pre-approved users or applications are allowed when the computer system is in sleep tracking mode, allowing the user to perform these operations with less user input.

[0263] In some embodiments, during sleep tracking mode (e.g., when the computer system is in sleep tracking mode): based on a determination that the computer system is in sleep tracking mode (e.g., option 636a is active and / or turned on), the computer system causes a second external device (e.g., 1070) different from the computer system (e.g., separate from the computer system) (e.g., a second external device corresponding to a second user different from the user of the computer system) to display an indication that the computer system has suppressed notifications (e.g., one or more types of notifications have been suppressed) (e.g., based on option 636d being in an activated state and / or engaged state). In some embodiments, when the computer system is not in sleep tracking mode, and based on a determination that the computer system is not in sleep tracking mode, the computer system forgoes causing and / or does not cause the second external device to display an indication that the computer system is in sleep tracking mode. Causing the second external device to display an indication that the computer system has suppressed notifications provides visual feedback to a user of the second external device about the state of the computer system (e.g., that the computer system has suppressed notifications), thereby providing improved visual feedback to the user.

[0264] In some embodiments, representations of one or more sets of user temperature information (e.g., the temperature information shown in data chart 614d) include: representations of a third set of user temperature information (e.g., a third time period during which temperature information is collected from the user) collected by a second external device separate from the computer system (e.g., a wearable device, a smart watch, a smart phone, a tablet computer, and / or a computer system that controls an external display); and representations of a fourth set of user temperature information (e.g., a fourth time period during which temperature information is collected from the user (e.g., a third time period different from the second time period)) that is different from the second set of user temperature information and collected by a third external device different from the second external device and the computer system (e.g., a wearable device, a smart watch, a smart phone, a tablet computer, and / or a computer system that controls an external display) (e.g., Figure 6LData Sheet 614d and / or Figure 6N Data table 614d in the display shows data aggregated from multiple external devices (e.g., multiple wearable devices, such as device 800). In some embodiments, the body temperature user interface includes and / or aggregates user body temperature information collected by multiple external devices (e.g., multiple external devices associated with the computer system and / or associated with a particular user of the computer system). Allowing the user to collect body temperature information using multiple external devices improves the user-device interface and helps the user provide correct input.

[0265] It should be noted that the process described above with respect to method 700 (eg Figure 7 ) also apply in a similar manner to the methods described below. For example, method 900, method 950, and / or method 1100 optionally include one or more features of the various methods described above with reference to method 700. For example, the body temperature information collected in method 700 can be used to generate health-based notifications and / or predictions in methods 900, 950, and / or 1100. For the sake of brevity, these details are not repeated below.

[0266] FIG. 8A to FIG. 8K An exemplary user interface for generating and providing an ovulation day prediction according to some embodiments is illustrated. In some embodiments, an ovulation day prediction is generated based on user temperature information. The user interface in these figures is used to illustrate the user interface including Fig. 9A and Fig. 9B The process is described below in the process.

[0267] Fig. 8A An electronic device 600 with a touch-sensitive display 602 is illustrated. FIG. 8A to FIG. 8C An example user interface that allows a user to provide information (e.g., health information and / or biometric information) related to and / or associated with menstrual cycle predictions, including ovulation day predictions and fertility window predictions, is illustrated. Fig. 8A , the electronic device 600 displays a health factor user interface 807 that requires the user to specify whether one or more predetermined health factors are applicable to the user via options 808a-808d. Option 808a may be selected by the user to indicate that the user is pregnant. Option 808b may be selected by the user to indicate that the user is breastfeeding. Option 808c may be selected by the user to indicate that the user is using contraception. Option 808d may be selected by the user to indicate that none of the health factors are currently applicable to the user, and in Fig. 8Ahas been selected by the user. The health factor user interface 807 includes an option 808e that can be selected to move to the next user interface (e.g., the next user interface in a series of navigation user interfaces and / or the next user interface in a series of setup user interfaces), an option 808f that can be selected to skip entering predetermined health factor information, an option 808g that can be selected to return to the previous user interface, and an option 808h that can be selected to stop display of the health factor user interface 807. In some embodiments, if the user indicates that one or more predetermined health factors are applicable to the user during the relevant prediction time period, the electronic device 600 does not generate one or more menstrual cycle predictions (e.g., menstrual period predictions, ovulation day predictions, and / or conception window predictions). Fig. 8A At , the electronic device 600 detects a user input 810 (eg, a tap input and / or a touch input) corresponding to a selection of the option 808e.

[0268] exist Figure 8B At, in response to user input 810, the electronic device 600 displays a user interface 812. The user interface 812 includes options 814a and options 814b. Option 814a can be selected by the user to selectively enable or disable menstrual period prediction. When option 814a is enabled (e.g., when menstrual period prediction is enabled), the electronic device 600 predicts when the user's next menstrual period will occur (e.g., based on biometric information (e.g., body temperature information) and / or based on the user's previous menstrual cycle history). When option 814a is disabled (e.g., when menstrual period prediction is disabled), the electronic device 600 does not generate and / or does not display menstrual period prediction. Option 814b can be selected by the user to selectively enable or disable menstrual period notification. When option 814b is enabled (e.g., when menstrual period notification is enabled), the electronic device 600 generates and / or displays a notification (e.g., a push notification, a lock screen notification, and / or a banner notification) indicating a menstrual period prediction (e.g., a prediction of when the user's next menstrual period will occur). When option 814b is disabled (e.g., when menstrual period notifications are disabled), the electronic device 600 does not generate and / or display notifications related to menstrual period predictions and / or menstrual period data (e.g., push notifications, lock screen notifications, and / or banner notifications). The user interface 812 also includes an option 814c that can be selected to display a next user interface (e.g., a next user interface in a series of guide user interfaces and / or a next user interface in a series of settings user interfaces), an option 814d that can be selected to display a previous user interface (e.g., user interface 807), and an option 814e that can be selected to stop displaying the user interface 812. Figure 8B At , the electronic device 600 detects a user input 816 (eg, a tap input and / or a touch input) corresponding to a selection of the option 814c.

[0269] exist Figure 8C At, in response to user input 816, the electronic device 600 displays a user interface 818. The user interface 818 includes options 820a-820g. Option 820a can be selected by the user to selectively enable or disable the conception window prediction. When option 820a is enabled (e.g., when the conception window prediction is enabled), the electronic device 600 generates and displays the conception window prediction (e.g., based on biometric information (e.g., body temperature information) and / or based on the user's menstrual cycle history). In various embodiments, the conception window prediction includes one or more of the following: a prediction of when the user's next conception window will occur, a prediction of when the user's previous conception window will occur, and / or a prediction of when the user's current conception window will begin. When option 820a is disabled (e.g., when the conception window prediction is disabled), the electronic device 600 does not generate and / or does not display the conception window prediction. Option 820b can be selected by the user to selectively enable or disable the conception window notification. When option 820b is enabled (e.g., when the conception window notification is enabled), the electronic device 600 generates and / or displays a notification indicating the conception window prediction (e.g., a push notification, a lock screen notification, and / or a banner notification). When option 820b is disabled, the electronic device 600 does not generate and / or display notifications related to the conception window prediction and / or conception window data. Option 820c can be selected by the user to selectively enable or disable fertility recording. When option 820c is enabled (e.g., fertility recording is enabled), options are provided to the user (e.g., the electronic device 600 displays options), which allow the user to record ovulation tests and other fertility indicators, and display indications of fertility indicators recorded by the user (e.g., within the cycle tracking user interface 828, as described below). When option 820c is disabled (e.g., fertility recording is disabled), the electronic device 600 does not display and / or does not provide the user with the option of recording ovulation tests and / or other fertility indicators. Option 820d can be selected by the user to selectively enable or disable sexual activity recording. When option 820d is enabled (e.g., sexual activity recording is enabled), the electronic device 600 displays and / or provides the user with an option to allow the user to record sexual activity information (e.g., allow the user to identify the date on which the user has sexual activity). When option 820d is disabled (e.g., sexual activity recording is disabled), the electronic device 600 does not display and / or does not provide the user with an option to allow the user to record sexual activity information. Option 820e can be selected to return to the previous user interface (e.g., user interface 812), option 820f can be selected to stop display of user interface 818, and option 820g can be selected to display the next user interface (e.g., the next user interface in a series of navigation user interfaces and / or the next user interface in a series of settings user interfaces).

[0270] The user interface 818 also includes a notification 822 that indicates that the user can improve cycle predictions, ovulation predictions, and fertility window predictions by setting up sleep tracking and wearing their wearable device (e.g., a watch) while sleeping at night (e.g., so that the electronic device 600 can record and track body temperature information, which can be used to improve these predictions). In some embodiments, notification 822 is displayed in response to a determination that the user has not enabled sleep tracking, has not enabled body temperature recording, and / or has not consistently recorded body temperature information. Notification 822 includes an option 824b that can be selected to display the sleep tracking user interface 618 (as described above) and an option 824a that can be selected to stop display of notification 822. In Figure 8C At , the electronic device 600 detects a user input 826 (eg, a tap input and / or a touch input) corresponding to a selection of option 820g.

[0271] exist Fig.8D At, in response to user input 826, electronic device 600 displays cycle tracking user interface 828. Cycle tracking user interface 828 includes a first area 830, which includes day representations 832a-832g. Each day representation 832a-832g represents a single calendar day (e.g., representation 832d represents Friday, May 6, representation 832c represents Thursday, May 5, representation 832e represents Saturday, May 7, etc.). The user can navigate within first area 830 (e.g., by scrolling and / or sliding left or right) to view additional day representations representing past and / or future dates in order to view and / or record menstrual cycle information about a particular date. Indicator 831a points to representation 832d, indicating that representation 832d is the currently selected day representation, and indicator 831b indicates that representation 832d represents "Today, May 6". Thus, with representation 832d currently selected, the user can interact with options 834a-834d to record menstrual cycle information for Friday, May 6. If the user swipes right to select representation 832c (e.g., moves representation 832c below representation 831a), the user can interact with options 834a-834d to record menstrual cycle information for Thursday, May 5. Option 834a can be selected to initiate a process for indicating that the user is experiencing menstruation on the currently selected date. Option 834b can be selected to initiate a process for recording one or more symptoms for the selected date. Option 834c can be selected to initiate a process for indicating that the user is experiencing spotting on the currently selected date. Option 834d can be selected to initiate a process for indicating that one or more predetermined health factors (e.g., pregnancy, use of contraceptive measures, lactation, etc.) are applicable to the user on the selected date.

[0272] Option 834e can be selected to view one or more health-related predictions for the user, including, for example, a menstrual period prediction (e.g., when the user will have her next menstrual period), a fertility window prediction (e.g., when the user will have her next fertility window and / or when the user's most recent fertility window occurred), and an ovulation day prediction (e.g., a prediction of when the user last ovulated and / or when the user will next ovulate). Such predictions are also shown via daily representations 832a-832g in region 830. Fig.8D , representations 832a-832e are displayed in a first manner (e.g., in a first color, in a first pattern, etc.), indicating that the electronic device 600 has predicted that the user's fertility window has occurred and / or will occur on those dates (e.g., on Fig.8D The event will take place from Tuesday, May 3 to Saturday, May 7.

[0273] The cycle tracking user interface 828 also includes an option 834g that can be selected to return to a previously displayed user interface, and an option 834f that can be selected to initiate a process for recording a menstrual cycle (e.g., for identifying one or more dates when the user has her period).

[0274] The cycle tracking user interface 828 also includes a history section 836 that displays menstrual cycle information for one or more menstrual cycles. The history section 836 includes a first area 838a corresponding to the current menstrual cycle (e.g., started on April 17 and has continued until the current date of May 6), and a second area 838b corresponding to previous menstrual cycles that occurred from March 19 to April 16. The first area 838a includes 20 pill-shaped day representations, where each day representation represents a single day in the current menstrual cycle (e.g., the first pill represents day one, the second pill represents day two, and so on). Fig.8D 8, the first six day representations 835a in area 838a indicate that the user had her period in those first six days (e.g., by displaying a small circle at the top of each day representation), and the last six day representations 835b in area 838a indicate that the electronic device 600 predicts that the user's fertility window has occurred during those six days (e.g., based on the user's past menstrual cycle information). Similarly, in area 838b, there are 28 pill-shaped day representations to represent the 28 days in the menstrual cycle (not all day representations are displayed in the figure). Fig.8D838b). In some embodiments, the user can slide in area 838b to display additional day representations. Area 838b indicates that during the previous menstrual cycle, the user had menstruation in the first five days (e.g., based on the small circles shown at the top of those day representations), the user showed spotting on the third and fifth days (e.g., based on the small dots at the bottom of the third day representation and the fifth day representation), and the pregnancy window prediction for days 10 to 16 of the menstrual cycle is displayed (based on the single diagonal hatching shown in those day representations), and the ovulation day prediction for day 15 of the menstrual cycle is displayed (e.g., based on the double diagonal hatching shown on the day representation). In some embodiments, when fertility prediction is not enabled, the cycle tracking user interface 828 does not display a pregnancy window prediction or an ovulation day prediction. In some embodiments, when fertility prediction is not enabled, the cycle tracking user interface 828 displays a fertility prediction. In some embodiments, when fertility prediction is enabled, the cycle tracking user interface 828 does not display a menstrual period prediction, and only displays a fertile window prediction and an ovulation day prediction.

[0275] As mentioned above, in Fig.8D , the electronic device 600 has generated a fertility window prediction for the user's current menstrual cycle (e.g., day representations 832a-832e in area 830, and day representation 835b in area 838a). In the depicted example scenario, Fig.8D The fertility window prediction shown represents an initial fertility window prediction generated using information about the user (e.g., based on historical menstrual cycle information for the user) but without using the user's body temperature information. Fig.8D In the example shown, the user has enabled sleep tracking and has enabled temperature collection and recording, as described in the reference above. FIG. 6A to FIG. 6Q discussed. FIG. 8E to FIG. 8G , an example scenario is shown in which the electronic device 600 uses the user's body temperature information to generate an ovulation day prediction and updates the initial pregnancy window prediction based on the ovulation day prediction. In some embodiments, when sleep tracking and / or body temperature recording are not enabled, the cycle tracking user interface 828 includes a similar Figure 8C , which notifies the user that the user can improve menstrual cycle predictions (e.g., menstrual period predictions, ovulation day predictions, and / or fertility window predictions) by setting up sleep tracking, setting up temperature logging, and / or wearing their wearable device while sleeping every night.

[0276] exist Fig. 8E At , the electronic device 600 displays the wrist temperature user interface 612, which is referred to above FIG. 6A to FIG. 6Q was discussed. Fig. 8E , wrist temperature user interface 612 indicates that the user's relative body temperature peaked around May 3. Fig. 8E In the example, based on the user's body temperature information, the electronic device 600 generates an ovulation day prediction predicting that the user will ovulate on May 3.

[0277] exist Fig.8F In FIG. 8 , the electronic device 600 displays a lock screen user interface 840, which includes an indication 842a indicating that the electronic device 600 is in a locked state. The lock screen user interface also includes a current time indication 842b, a current date indication 842c, a flash option 842d, and a camera option 842e. Fig.8F , after the electronic device 600 generates an ovulation day prediction for May 3, the electronic device 600 displays a push notification 842f when the electronic device 600 is in a locked state. In some embodiments, the push notification 842f causes the display 602 to transition from an inactive state (e.g., a closed state) to an active state (e.g., an open state). The push notification 842f informs the user that the electronic device 600 has determined (e.g., based on the user's body temperature information) that the user is likely to ovulate on May 3.

[0278] Fig.8F Also depicted is an electronic device 800 that is a smartwatch having a touch-sensitive display 802, a rotatable and depressible input mechanism 804, and a button 806. In some embodiments, electronic device 800 corresponds to electronic device 600 (e.g., is paired with electronic device 600 and / or corresponds to the same user as electronic device 600). In response to electronic device 600 determining that the user is likely to ovulate on May 3 and / or after the determination, electronic device 800 displays notification 844 informing the user of the ovulation day prediction. Fig.8F At , the electronic device 600 detects user input 846 (eg, touch input and / or tap input) corresponding to selection of the notification 842f.

[0279] exist Figure 8G At 846, in response to user input 846, electronic device 600 displays cycle tracking user interface 828. Figure 8G In FIG. 8 , the cycle tracking user interface 828 has been updated based on the ovulation day prediction made by the electronic device 600. Fig.8D , prior to the ovulation day prediction, the cycle tracking user interface 828 displays an initial fertility window prediction, thereby predicting that the user's fertility window occurs between May 1 and May 7 (e.g., day representations 832a-832e and day representation 835b). Figure 8G, after the electronic device 600 has used the user's body temperature information to generate a prediction that the user will ovulate on May 3, the cycle tracking user interface 828 now displays an updated ovulation window prediction 835c between April 28 and May 4. In some embodiments, the updated ovulation window prediction is defined by selecting a predetermined number of days before the ovulation day prediction (e.g., five days before the ovulation day prediction) and a predetermined number of days after the ovulation day prediction (e.g., the day after the ovulation day prediction). Therefore, the day representations 832j, 832i, 832h, and 832b are displayed in a manner indicating the ovulation window prediction (e.g., single-line hatching), while the day representations 832c and 832d previously shown with single-line hatching indicating the ovulation window prediction are no longer filled with that pattern. The cycle tracking user interface 828 also displays the ovulation day prediction by displaying a day representation 832a with double-line hatching and a day representation 835d with double-line hatching. In this way, the ovulation day prediction is displayed from the day representation 832j, 832i, 832h, and 832b. Figure 8D to Figure 8G , the electronic device 600 changes from displaying the initial conception window prediction to using the user's body temperature information to generate an ovulation day prediction, and then displays the ovulation day prediction and the updated conception window prediction.

[0280] exist Figure 8H In FIG. 8 , the electronic device 600 displays a cycle history user interface 848 that includes menstrual cycle representations 850a-850d corresponding to a plurality of previous menstrual cycles for the user. Figure 8H , menstrual cycle representations 850a, 850c, and 850d do not include a fertile window prediction or an ovulation day prediction because the user indicated that one or more predetermined health factors (e.g., lactation and / or contraceptive user) apply to the user during those menstrual cycles. However, menstrual cycle representation 850b does include a fertile window prediction and an ovulation day prediction. Figure 8H At , the electronic device 600 detects a user input 852 (eg, a touch input and / or a tap input) corresponding to a selection of the menstrual cycle representation 850b.

[0281] exist Figure 8I At 850, in response to user input 852, electronic device 600 displays cycle details user interface 854. Cycle details user interface 854 displays information related to the menstrual cycle selected in cycle history user interface 848. Figure 8I , the cycle details user interface 854 displays details related to the menstrual cycle that occurred from December 14, 2021 to January 15, 2022. The cycle history user interface 848 includes cycle length information 856a, a set of day representations 856b representing each day in the menstrual cycle. The day representations 856b include which days the user had her period (e.g., Figure 8I 1 to 6 in ), on which days the user records spotting (e.g. Figure 8I3, 5, and 16 in the menstrual cycle), ovulation day prediction for the menstrual cycle (e.g. Figure 8I 14 in the menstrual cycle) and fertility window predictions for the menstrual cycle (e.g. Figure 8I The cycle details user interface 854 also displays temperature information 856c indicating the user's body temperature (e.g., relative body temperature) for each day in the menstrual cycle. The cycle details user interface 854 also includes sexual history information 856d. The cycle details user interface 854 also includes an option 856e that can be selected to initiate a process for exporting menstrual cycle information in the cycle details user interface 854 (e.g., as a PDF file, as an email, or in another file format), an option 856f that can be selected to initiate a process for editing menstrual cycle information in the cycle details user interface 854, and an option 856g that can be selected to return to the cycle history user interface 848.

[0282] Figure 8J An alternative embodiment of the cycle tracking user interface 828 is illustrated, wherein the cycle tracking user interface 828 includes an option 858 that can be selected to record a positive ovulation predictor kit (OPK) test. Figure 8J Depicted above reference Fig.8D The same scene described. Figure 8J In FIG. 6 , the electronic device 600 has generated an initial fertility window prediction and displays the initial fertility window prediction for May 1 to May 7. Figure 8J , when Friday, May 6 is selected (eg, as indicated in area 830 and by indications 831a , 831b ), the electronic device 600 detects user input 860 corresponding to selection of option 858 .

[0283] exist Figure 8K At, in response to user input 860, the electronic device 600 records a positive OPK test for Friday, May 6, as indicated by indication 862. In addition, in response to user input 860, the electronic device 600 marks Saturday, May 7 (day indication 832e) as a predicted ovulation day (the day before the positive OPK test indicates ovulation), and updates the conception window based on the new predicted ovulation day by marking May 2 to May 8 as a new predicted conception window (e.g., within area 830). In some embodiments, a positive OPK test covers any conception window prediction or ovulation day prediction generated by the electronic device 600. In some embodiments, even after the electronic device 600 predicts an ovulation day for the user based on the user's body temperature information, a positive OPK test will also cover the ovulation day prediction made by the electronic device 600.

[0284] Fig. 9Ais a flow chart illustrating a method for generating and providing an ovulation day prediction using a computer system according to some embodiments. Method 900 is performed at a computer system (e.g., 100, 300, 500) (e.g., 600, 800) (e.g., a wearable device, a smart watch, a smart phone, a tablet computer, and / or a computer system that controls an external display) that communicates with: a display generation component (e.g., 602, 802) (e.g., a display controller, a touch-sensitive display system; and / or a display (e.g., integrated and / or connected)) and one or more input devices (e.g., 601, 602, 802, 804, 806) (e.g., a touch-sensitive surface (e.g., a touch-sensitive display); an accelerometer; a rotatable input mechanism; a pressable input mechanism; and / or a rotatable and pressable input mechanism) (e.g., a wearable device, a smart watch, a smart phone, a tablet computer, a head-mounted device (e.g., a head-mounted augmented reality and / or extended reality device), and / or a computer system that controls an external display). Some operations in method 900 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0285] As described below, method 900 provides an intuitive way to generate and provide ovulation day prediction. The method reduces the cognitive burden of the user generating and / or receiving ovulation day prediction, thereby creating a more effective human-computer interface. For battery-powered computing devices, it enables users to generate and / or receive ovulation day prediction more quickly and more efficiently, saving power and increasing the time interval between two battery charges.

[0286] A computer system (e.g., 600, 800) receives (902) (e.g., via one or more input devices and / or via an external device (e.g., an external (e.g., separate) wearable device, smart watch, smart phone, tablet computer, and / or a computer system controlling an external display) body temperature information corresponding to a user (e.g., body temperature measurements collected from the user over one or more time periods). After receiving the body temperature information corresponding to the user (in some embodiments, in response to receiving the body temperature information corresponding to the user) (904), the computer system displays (906) a push notification (e.g., 842f and / or 844) via a display generation component (e.g., 602, 802), which causes the display generation component to be activated from an inactive state (e.g., Fig.10I ) (e.g., a closed state and / or a state in which the display generating component does not display content) to an active state (e.g., Fig.8F) (e.g., the state of being turned on and / or the state of displaying the content of the display generating component) and indicating to the user that a predicted ovulation day for the user has been determined (e.g., determined by the computer system and / or an external device), wherein the predicted ovulation day is determined based on the body temperature information corresponding to the user. In some embodiments, after receiving the body temperature information corresponding to the user (in some embodiments, in response to receiving the body temperature information corresponding to the user), the computer system determines the predicted ovulation day for the user based on the body temperature information corresponding to the user (e.g., the predicted ovulation day for the user determined based on the change in the user's body temperature over a period of time). In some embodiments, the computer system displays a push notification indicating to the user that the computer system has determined the predicted ovulation day after determining the predicted ovulation day for the user (in some embodiments, in response to determining the predicted ovulation day for the user). After receiving the body temperature information corresponding to the user, a push notification indicating to the user that the predicted ovulation day for the user has been determined is automatically displayed to inform the user of the ovulation day prediction performed with less user input, thereby reducing the number of user inputs required to perform the operation. Displaying a push notification indicating to the user that a predicted ovulation day has been determined for the user provides visual feedback to the user regarding the status of the system (eg, the system has determined a predicted ovulation day for the user), thereby providing improved visual feedback to the user.

[0287] In some embodiments, displaying the push notification includes displaying the push notification while maintaining the computer system in a locked state (e.g., lock screen user interface 840 and / or indicating that the computer system 600 is in a locked state). Fig.8F An indication of a locked state in the computer system 842a) (e.g., a state in which one or more features and / or one or more groups of content of the computer system are inaccessible to the user and / or a state in which authentication information is required to transition the computer system to an unlocked state). After receiving the body temperature information corresponding to the user, a push notification indicating to the user that a predicted ovulation day for the user has been determined is automatically displayed to inform the user of the ovulation day prediction made with less user input, thereby reducing the number of user inputs required to perform the operation.

[0288] In some embodiments, receiving body temperature information corresponding to the user (e.g., the user body temperature information shown in data chart 614d) includes receiving body temperature information corresponding to the user from a first external device (e.g., 800) that is separate from (e.g., different from) the computer system (e.g., a wearable device, a smart watch, a smart phone, a tablet computer, and / or a computer system that controls an external display). After receiving the body temperature information corresponding to the user from the external device, automatically displaying a push notification indicating to the user that a predicted ovulation day has been determined for the user informs the user of the ovulation day prediction made with less user input, thereby reducing the number of user inputs required to perform the operation.

[0289] In some embodiments, the computer system communicates with a first sensor (e.g., a first temperature sensor and / or a first body temperature sensor) (e.g., a first sensor built into the computer system (e.g., contained in a housing corresponding to the computer system, connected to the computer system, and / or separated from the computer system) (e.g., a first sensor built into the electronic device 600 and / or built into the electronic device 800); and receiving body temperature information corresponding to the user includes receiving body temperature information corresponding to the user from the first sensor. After receiving the body temperature information corresponding to the user from the first sensor, a push notification indicating to the user that a predicted ovulation day for the user has been determined is automatically displayed to inform the user of the ovulation day prediction made with less user input, thereby reducing the number of user inputs required to perform the operation.

[0290] In some embodiments, while displaying a push notification (e.g., 842f and / or 844) (908): the computer system receives (910) a selection input (e.g., 846) (e.g., one or more touch inputs, one or more tap inputs, one or more mouse inputs, one or more keyboard inputs, and / or one or more gesture inputs) corresponding to a selection of the push notification via one or more input devices. In response to receiving the selection input corresponding to the selection of the push notification (912), the computer system displays (914) via a display generation component including (e.g., displays and / or shows) a predicted ovulation day (e.g., Figure 8G The day in 832a and / or Figure 8G In some embodiments, the push notification does not display the predicted ovulation day. In some embodiments, in response to receiving a selection input corresponding to the selection of the push notification and a determination that the device security standards are met (e.g., a determination that the authentication standards are met according to authentication information (e.g., password information and / or biometric authentication information (e.g., facial scan authentication, iris scan authentication, and / or fingerprint scan authentication)), a cycle tracking user interface including the predicted ovulation day is displayed. Displaying a push notification that can be selected to display the predicted ovulation day allows the user to view the predicted ovulation day with less user input, thereby reducing the number of user inputs required to perform the operation.

[0291] In some embodiments, the push notification (e.g., 842f and / or 844) includes (e.g., displays and / or shows) a predicted ovulation day (e.g., Fig.8FDisplaying a push notification showing the predicted ovulation day allows the user to view the predicted ovulation day with less user input, thereby reducing the number of user inputs required to perform an operation. Displaying a push notification showing the predicted ovulation day provides the user with visual feedback about the state of the system (e.g., the system has determined a predicted ovulation day for the user), thereby providing improved visual feedback to the user.

[0292] In some embodiments, displaying the push notification (e.g., 842f and / or 844) is performed based on a determination that the user has enabled a fertility tracking setting (e.g., 820a, 820b, and / or 820c) (e.g., a setting indicating that the user has authorized receiving fertility information and / or authorized performing an ovulation day prediction has been enabled). In some embodiments, after receiving temperature information corresponding to the user, and based on a determination that the user has not enabled the fertility tracking setting, the computer system forgoes displaying the push notification. After receiving temperature information corresponding to the user and based on a determination that the user has enabled fertility tracking, automatically displaying a push notification indicating to the user that a predicted ovulation day for the user has been determined informs the user that the ovulation day prediction is ready for the user to view with less user input, thereby reducing the amount of user input required to perform the operation.

[0293] In some embodiments, displaying a push notification (e.g., 842f and / or 844) is performed based on a determination that a threshold amount of body temperature information corresponding to the user has been collected (e.g., in Figures 6L to 6N In the case of Figure 6K and Figure 6Q In some embodiments, after receiving the body temperature information corresponding to the user, and according to the determination that the threshold amount of body temperature information corresponding to the user has not been collected, the computer system abandons displaying the push notification. After receiving the body temperature information corresponding to the user and according to the determination that the threshold amount of body temperature information corresponding to the user has been collected, a push notification indicating that the predicted ovulation day for the user has been determined is automatically displayed to the user to inform the user that the ovulation day prediction is ready for the user to view with less user input, thereby reducing the number of user inputs required to perform the operation. Displaying a push notification only when the threshold amount of body temperature information has been collected improves the user-device interface by avoiding presenting information that is not applicable to the user to the user and helping the user provide correct input.

[0294] In some embodiments, displaying a push notification (e.g., 842f and / or 844) is based on a determination that one or more predetermined health factors are not applicable to the user (e.g., Fig. 8A and / or Fig.8D In some embodiments, after receiving the temperature information corresponding to the user, and based on a determination that at least one of the one or more predetermined health factors is applicable to the user (e.g., the user is pregnant and / or the user is using contraception), the computer system abandons displaying the push notification. After receiving the temperature information corresponding to the user, and based on a determination that one or more predetermined health factors are not applicable to the user, a push notification indicating to the user that a predicted ovulation day for the user has been determined is automatically displayed to inform the user that the ovulation day prediction is ready for the user to view with less user input, thereby reducing the number of user inputs required to perform the operation. Displaying a push notification only when one or more predetermined health factors are not applicable to the user improves the user-device interface by avoiding presenting information that is not applicable to the user to the user and helping the user provide correct input.

[0295] In some embodiments, the computer system receives input (e.g., a first set of user inputs and / or one or more user inputs) (e.g., one or more touch inputs, one or more non-touch inputs, and / or one or more gestures) via one or more input devices corresponding to a request to enter a sleep tracking mode (e.g., 638a and / or 638b and / or define a sleep schedule (e.g., the sleep schedule shown in 636i, 636j) (e.g., a mode and / or state in which one or more notifications (e.g., a first type of notification) received by the computer system are suppressed and / or in which user sleep information (e.g., sleep quality information) is collected). In response to the input, the computer system enters a sleep tracking mode (e.g., FIG. 6H to FIG. 6I In some embodiments, receiving the body temperature information corresponding to the user is performed in response to a determination that the computer system is in the sleep tracking mode. Automatically collecting the body temperature information in response to the computer system entering the sleep tracking mode allows the body temperature information to be collected with less user input, thereby reducing the amount of user input required to perform the operation.

[0296] In some embodiments, a computer system receives notification data of a first type (e.g., notifications of a type that are suppressed when in sleep tracking mode) (in some embodiments, all notifications are suppressed in sleep tracking mode) (in some embodiments, notifications of a second type (e.g., emergency notifications, wake-up alarm notifications) are not suppressed when in sleep tracking mode). In response to receiving the notification data of the first type: based on the computer system not being in sleep tracking mode (e.g., option 636a is in an inactive state and / or off state) (e.g., when the notification data of the first type is received), the computer system outputs a first notification corresponding to the notification data of the first type (e.g., displays the first notification; causes the display generation component to transition from an inactive state (e.g., off and / or a state in which content is not displayed on the display generation component) to an active state (e.g., on and / or a state in which content is displayed); outputs an audio output; and / or outputs a tactile output); and based on a determination that the computer system is in sleep tracking mode (e.g., FIG. 6H to FIG. 6I When the computer system is in sleep tracking mode, the computer system abandons outputting (e.g., suppressing) a first notification corresponding to the first type of notification data (e.g., abandons displaying the first notification; abandons causing the display generating component to transition from an inactive state to an active state; abandons outputting an audio output; and / or abandons outputting a tactile output). Automatically suppressing notifications when the computer system is in sleep tracking mode allows the user to perform the operation with less user input, thereby reducing the amount of user input required to perform the operation.

[0297] In some embodiments, in response to receiving a first type of notification data: based on a determination that the computer system is not in sleep tracking mode (e.g., option 636a is in an inactive state and / or turned off) (e.g., when the first type of notification data is received), the computer system causes a second external device (e.g., 800) (e.g., a wearable device, a smart watch, a smart phone, a tablet computer, and / or a computer system that controls an external display) that is separate from the computer system (e.g., different from the computer system) to display a second notification corresponding to the first type of notification data (e.g., causes external device 800 to display and / or output a notification); and based on a determination that the computer system is in sleep tracking mode (e.g., option 636a is in an active state and / or turned on) (e.g., when the first type of notification data is received), the computer system abandons causing the second external device to display a second notification corresponding to the first type of notification data (e.g., in Figure 6HIn the embodiment of the present invention, when the electronic device 800 is in the sleep focus mode state, the electronic device 600 is also in the sleep focus mode state (e.g., based on option 630e being enabled). Automatically suppressing notifications on the second external device when the computer system is in the sleep tracking mode allows the user to perform the operation with less user input, thereby reducing the amount of user input required to perform the operation.

[0298] In some embodiments, receiving body temperature information corresponding to the user (e.g., body temperature information shown in data chart 614d) includes receiving body temperature information corresponding to the user from a third external device (e.g., 800) that is separate from (e.g., different from) the computer system (e.g., a wearable device, a smart watch, a smart phone, a tablet computer, and / or a computer system that controls an external display). After receiving the body temperature information corresponding to the user from the external device, automatically displaying a push notification indicating to the user that a predicted ovulation day has been determined for the user informs the user of the predicted ovulation day with less user input, thereby reducing the number of user inputs required to perform the operation.

[0299] In some embodiments, the computer system receives a second type of notification data (e.g., a type of notification that is suppressed when in sleep tracking mode) (in some embodiments, all notifications are suppressed in sleep tracking mode) (in some embodiments, a third type of notification (e.g., emergency notification, wake-up alarm notification) is not suppressed when in sleep tracking mode). In response to receiving the second type of notification data: based on a determination that the computer system (e.g., 600) is not in sleep tracking mode (e.g., option 636a is in an inactive state and / or off state) (e.g., when receiving the second type of notification data), the computer system (e.g., 600) causes a third external device (e.g., 800) to output a third notification (e.g., causes the third external device to display a third notification; causes a display generation component corresponding to the third external device and / or communicating with the third external device to transition from an inactive state (e.g., off and / or a state in which content is not displayed on the display generation component) to an active state (e.g., on and / or a state in which content is displayed); causes the third external device to output an audio output; and / or causes The third external device outputs a tactile output corresponding to the third type of notification data; and based on the determination that the computer system is in sleep tracking mode (e.g., option 636a is active and / or turned on) (e.g., when the second type of notification data is received), the computer system (e.g., 600) abandons causing the third external device (e.g., 800) to output a third notification corresponding to the second type of notification data (e.g., when the notification is suppressed on the electronic device 600, the notification is also suppressed on the electronic device 800 (e.g., based on setting 630e being enabled)). Automatically suppressing notifications on the third external device when the computer system is in sleep tracking mode allows the user to perform the operation with less user input, thereby reducing the number of user inputs required to perform the operation.

[0300] In some embodiments, a computer system (e.g., 600) receives (e.g., via one or more input devices and / or via an external device (e.g., an external (e.g., separate) wearable device, a smart watch, a smart phone, a tablet computer, and / or a computer system controlling an external display) second body temperature information corresponding to a user (e.g., body temperature measurements collected from the user during one or more time periods) (e.g., second body temperature information different from the body temperature information). After receiving the second body temperature information corresponding to the user (in some embodiments, in response to receiving the second body temperature information corresponding to the user): according to the fact that the user has not recorded (e.g., input and / or provided) an ovulation prediction kit test result during a predefined time period (e.g., during Fig.8DThe computer system displays a second push notification (e.g., 842f and / or 844) via a display generation component (e.g., 602) that causes the display generation component to transition from an inactive state to an active state and indicates to the user that a second predicted ovulation day for the user has been determined, wherein the second predicted ovulation day is determined based on second body temperature information corresponding to the user; and based on the user having recorded an ovulation prediction kit test result during a predefined time period (e.g., the user recorded Figure 8J to Figure 8K OPK test in the user record), the computer system forgoes displaying the second push notification (e.g., Figure 8J to Figure 8K After receiving the second body temperature information corresponding to the user, automatically displaying a second push notification indicating that the second predicted ovulation day for the user has been determined to inform the user that the ovulation day prediction is ready for them to view with less user input, thereby reducing the number of user inputs required to perform the operation. If the user has already recorded the ovulation prediction kit test results during the predefined time period, then giving up displaying the second push notification improves the user-device interface by avoiding presenting information that is not applicable to the user and helping the user provide correct input.

[0301] It should be noted that the above description with respect to method 900 (eg, Fig. 9A ) also apply in a similar manner to the methods described above and / or below. For example, method 700, method 950, and / or method 1100 optionally include one or more features of the various methods described above with reference to method 900. For example, the body temperature information collected in method 700 can be used to generate health-based notifications and / or predictions in methods 900, 950, and / or 1100. For the sake of brevity, these details are not repeated below.

[0302] Fig. 9Bis a flow chart illustrating a method for generating and providing an ovulation day prediction using a computer system according to some embodiments. Method 950 is performed at a computer system (e.g., 100, 300, 500) (e.g., 600, 800) (e.g., a wearable device, a smart watch, a smart phone, a tablet computer, and / or a computer system that controls an external display) that communicates with: a display generation component (e.g., 602, 802) (e.g., a display controller, a touch-sensitive display system; and / or a display (e.g., integrated and / or connected)) and one or more input devices (e.g., 601, 602, 802, 804, 806) (e.g., a touch-sensitive surface (e.g., a touch-sensitive display); an accelerometer; a rotatable input mechanism; a pressable input mechanism; and / or a rotatable and pressable input mechanism) (e.g., a wearable device, a smart watch, a smart phone, a tablet computer, a head-mounted device (e.g., a head-mounted augmented reality and / or extended reality device), and / or a computer system that controls an external display). Some operations in method 950 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0303] As described below, method 950 provides an intuitive way to generate and provide ovulation day prediction. The method reduces the cognitive burden of the user generating and / or receiving ovulation day prediction, thereby creating a more effective human-computer interface. For battery-powered computing devices, enabling users to generate and / or receive ovulation day predictions more quickly and more efficiently saves power and increases the time interval between battery charges.

[0304] The computer system (e.g., 600) displays (952) a cycle tracking user interface (e.g., 828) (e.g., a cycle tracking user interface corresponding to a user) via the display generation component (e.g., 602) at a first time, including displaying a first fertility window prediction for the user (e.g., Fig.8D 835b and / or day representations 832a-832e in FIG. 835b and / or day representations 832a-832e in FIG. 835b) (e.g., a prediction of one or more days and / or one or more dates during which the user has an increased likelihood of becoming pregnant (e.g., a prediction of a date on which the user will release an egg from an ovary and a predetermined time period prior to that date (e.g., five dates prior to that date)) (e.g., a prediction of a fertility window corresponding to a first time period). The computer system receives (954) (e.g., via one or more input devices and / or via an external device (e.g., an external (e.g., separate) wearable device, smart watch, smart phone, tablet computer, and / or a computer system controlling an external display) body temperature information corresponding to the user (e.g., Fig. 8EAfter receiving the body temperature information corresponding to the user (in some embodiments, in response to receiving the body temperature information corresponding to the user) (956), the computer system determines (958) a predicted ovulation day for the user based on the body temperature information corresponding to the user at a second time after the first time (e.g., notifications 842f and / or 844) (e.g., the predicted ovulation day of the user determined based on changes in the user's body temperature over a period of time). The computer system displays (960) an updated cycle tracking user interface (e.g., a display generation component) at a third time after the second time. Figure 8G 828 of the cycle tracking user interface) (e.g., an updated and / or modified version of the cycle tracking user interface (e.g., updated and / or modified based on body temperature information and / or based on the user's predicted ovulation day)), including simultaneously displaying: a representation of the predicted ovulation day for the user (e.g., 832a, 835d) (e.g., a graphical object indicating the predicted ovulation day for the user); and an updated fertility window prediction for the user (e.g., day representations 832j, 832i, 832h, 832b, and / or 835c), the updated fertility window prediction being different from the first fertility window prediction for the user (e.g., an updated, revised, and / or modified fertility window prediction (e.g., updated, revised, and / or modified based on the user's body temperature information and / or predicted ovulation day)). In some embodiments, the first fertility window prediction is determined based on a set of information that does not include body temperature information corresponding to the user and / or does not include any body temperature information corresponding to the user (e.g., the first fertility window prediction is determined based on historical menstrual cycle information corresponding to the user). In some embodiments, based on the body temperature information corresponding to the user, a predicted ovulation day for the user is determined by an external device, transmitted to and received by the computer system. Automatically updating the cycle tracking user interface with an updated pregnancy window prediction after receiving the body temperature information corresponding to the user allows the user to view the updated pregnancy window prediction information with less user input, thereby reducing the number of user inputs required to perform operations. Automatically updating the cycle tracking user interface with an updated pregnancy window prediction after receiving the body temperature information corresponding to the user provides the user with visual feedback about the status of the system (e.g., the system has determined a predicted ovulation day for the user and / or has determined an updated pregnancy window prediction for the user), thereby providing improved visual feedback to the user.

[0305] In some embodiments, receiving body temperature information corresponding to the user includes receiving body temperature information corresponding to the user from a first external device (e.g., 800) that is separate from (e.g., different from) the computer system (e.g., a wearable device, a smart watch, a smart phone, a tablet computer, and / or a computer system that controls an external display). Automatically updating the cycle tracking user interface with an updated fertility window prediction after receiving the body temperature information corresponding to the user allows the user to view updated fertility window prediction information with less user input, thereby reducing the amount of user input required to perform operations.

[0306] In some embodiments, the computer system communicates with a first sensor (e.g., a sensor built into the electronic device 600 and / or the electronic device 800) (e.g., a first temperature sensor and / or a first body temperature sensor) (e.g., a first sensor built into the computer system (e.g., a first sensor contained in a housing corresponding to the computer system, connected to the computer system, and / or separated from the computer system); and receiving body temperature information corresponding to the user includes receiving body temperature information corresponding to the user from the first sensor. Automatically updating the cycle tracking user interface with an updated fertility window prediction after receiving the body temperature information corresponding to the user allows the user to view updated fertility window prediction information with less user input, thereby reducing the number of user inputs required to perform operations.

[0307] In some embodiments, a representation of a predicted ovulation day for a user (e.g., 832a and / or 835d) is displayed in a first visual appearance (e.g., in a first set of visual characteristics (e.g., color, size, shape, font, and / or pattern)); and an updated fertility window prediction for the user (e.g., 832j, 832i, 832h, 832b, 832c, and / or 835c) is displayed in a second visual appearance different from the first visual appearance (e.g., in a second set of visual characteristics (e.g., color, size, shape, font, and / or pattern)). Displaying the representation of the predicted ovulation day in a first visual appearance and displaying the updated fertility window prediction in a second visual appearance different from the first visual appearance allows the user to visually distinguish between the predicted ovulation day and the fertility window prediction without additional user input, and also provides improved visual feedback.

[0308] In some embodiments, the representation of the predicted ovulation day for the user (e.g., 832a and / or 835d) includes a first color (e.g., at least a portion of the representation of the predicted ovulation day for the user is displayed in the first color); and the updated fertility window prediction for the user (e.g., 832j, 832i, 832h, 832b, 832c, and / or 835c) includes a second color different from the first color (e.g., at least a portion of the updated fertility window prediction is displayed in the second color) (in some embodiments, the updated fertility window prediction does not include the first color). Displaying the representation of the predicted ovulation day in the first color and displaying the updated fertility window prediction in the second color different from the first color allows the user to visually distinguish the predicted ovulation day and the fertility window prediction without additional user input.

[0309] In some embodiments, the computer system (e.g., 600) displays a cycle tracking user interface (e.g., 828) via a display generation component (e.g., 602) at a fourth time after the third time, including: based on a determination (e.g., at the fourth time) that a fertility tracking setting (e.g., 820a, 820b, and / or 820c) is enabled (e.g., a setting indicating that the user authorizes receiving fertility information and / or authorizing performing ovulation day prediction), displaying (e.g., within the cycle tracking user interface) a second fertility window prediction (e.g., day representations 832a, 832b, 832c) for the user; 2c, 832d, 832e, 835b, and / or 835c) (e.g., a second fertility window prediction that is different from or the same as the first fertility window prediction and / or the updated fertility window prediction); and based on a determination that the fertility tracking setting is not enabled (e.g., at a fourth time), displaying (e.g., within a period tracking user interface) a menstrual period prediction (e.g., 835a) for the user (e.g., a prediction of one or more days during which the user has an increased likelihood of having a period) without displaying the second fertility window prediction for the user (in some embodiments, without displaying any fertility window prediction for the user). Displaying the fertility window prediction for the user when the fertility tracking setting is enabled and displaying the menstrual period prediction for the user when the fertility tracking setting is not enabled improves the user-device interface by avoiding presenting information that is not relevant to and / or of no interest to the user.

[0310] In some embodiments, the computer system receives second body temperature information corresponding to the user (e.g., the body temperature information shown in data chart 614d) (e.g., the second body temperature information that is different from or the same as the first body temperature information). After receiving the second body temperature information corresponding to the user, the computer system displays a cycle tracking user interface (e.g., 828) via a display generation component, including: according to a determination that a fertility tracking setting (e.g., 820a, 820b, and / or 820c) is enabled (e.g., a setting indicating that the user authorizes the reception of fertility information and / or the execution of ovulation day prediction), displaying (e.g., within the cycle tracking user interface) a representation of a second predicted ovulation day (e.g., 832a, 835d) for the user, wherein the second predicted ovulation day is determined based on the second body temperature information; and according to a determination that the fertility tracking setting is not enabled, abandoning the display of the representation of the second predicted ovulation day for the user. Displaying a predicted ovulation day for a user when a fertility tracking setting is enabled, and forgoing display of the predicted ovulation day when the fertility tracking setting is not enabled, improves the user-device interface by avoiding presentation of information that is irrelevant and / or not of interest to the user.

[0311] In some embodiments, the computer system receives third body temperature information corresponding to the user (e.g., the body temperature information shown in the data chart 614d) (e.g., the third body temperature information that is different from or the same as the first body temperature information and / or the second body temperature information). After receiving the third body temperature information corresponding to the user: according to one or more predetermined health factors (e.g., Fig. 8A and / or the “factor” option 834d) is not applicable to the user (e.g., the user is not pregnant, the user is not using contraceptive measures, and / or the user is not using the first type of contraceptive measures) (e.g., when the third body temperature information is received and / or at a limited time after the third body temperature information corresponding to the user is received), the computer system determines a third predicted ovulation day for the user based on the third body temperature information (e.g., 842f, 844, 832a and / or 835d) (and optionally, displays a representation and / or indication of the third predicted ovulation day); and according to the determination that at least one of the one or more predetermined health factors is applicable to the user (e.g., the user is pregnant and / or the user is using contraceptive measures) (e.g., when the third body temperature information is received and / or at a limited time after the third body temperature information corresponding to the user is received), the computer system abandons determining the predicted ovulation day for the user based on the third body temperature information. Automatically determining the predicted ovulation day for the user based on the determination that one or more predetermined health factors are not applicable to the user reduces the number of user inputs required to perform the operation. Additionally, if one or more predetermined health factors are applicable to the user, forgoing performing an ovulation day prediction for the user improves the user-device interface by avoiding presentation of information that is not applicable to the user.

[0312] In some embodiments, the computer system receives fourth body temperature information corresponding to the user (e.g., the body temperature information shown in data chart 614d) (e.g., the fourth body temperature information that is different from or the same as the first body temperature information, the second body temperature information, and / or the third body temperature information). After receiving the fourth body temperature information corresponding to the user: based on the determination that a threshold amount of body temperature information (e.g., user body temperature information associated with the user of the computer system, collected from the user of the computer system, and / or collected by the computer system) has been collected (e.g., body temperature information greater than a threshold number of days has been collected and / or body temperature information greater than a threshold number of hours has been collected), the computer system determines a fourth predicted ovulation day for the user based on the fourth body temperature information (e.g., 842f, 844, 832a, and / or 835d) (and optionally, displays a representation and / or indication of the fourth predicted ovulation day); and based on the determination that a threshold amount of body temperature information has not been collected, the computer system abandons determining a predicted ovulation day for the user based on the fourth body temperature information. Automatically determining a predicted ovulation day for the user based on determining that a threshold amount of body temperature information has been collected reduces the number of user inputs required to perform an operation. Additionally, if a threshold amount of body temperature information has not been collected, abandoning the performance of an ovulation day prediction for the user improves the user-device interface by avoiding presentation of information that is not applicable to the user and / or inaccurate information.

[0313] In some embodiments, the computer system receives input (e.g., a first set of user inputs and / or one or more user inputs) (e.g., one or more touch inputs, one or more non-touch inputs, and / or one or more gestures) via one or more input devices corresponding to a request to enter a sleep tracking mode (e.g., 638a and / or 638b and / or define a sleep schedule (e.g., the sleep schedule shown in 636i, 636j) (e.g., a mode and / or state in which one or more notifications (e.g., a first type of notification) received by the computer system are suppressed and / or in which user sleep information (e.g., sleep quality information) is collected). In response to the input, the computer system enters a sleep tracking mode (e.g., FIG. 6H to FIG. 6I In some embodiments, the computer system is in a sleep tracking mode, wherein: receiving body temperature information corresponding to the user is performed when the computer system is in the sleep tracking mode (in some embodiments, receiving body temperature information corresponding to the user is performed based on a determination that the computer system is in the sleep tracking mode). Automatically collecting body temperature information in response to the computer system entering the sleep tracking mode allows the body temperature information to be collected with less user input, thereby reducing the amount of user input required to perform the operation.

[0314] In some embodiments, a computer system receives notification data of a first type (e.g., notifications of a type that are suppressed while in sleep tracking mode) (in some embodiments, all notifications are suppressed in sleep tracking mode) (in some embodiments, notifications of a second type (e.g., emergency notifications, wake-up alarm notifications) are not suppressed while in sleep tracking mode). In response to receiving the first type of notification data: based on the computer system not being in sleep tracking mode (e.g., option 636a is in an inactive state and / or an off state) (e.g., when the first type of notification data is received), the computer system outputs a first notification corresponding to the first type of notification data (e.g., displays the first notification; causes the display generation component to transition from an inactive state (e.g., off and / or a state in which content is not displayed on the display generation component) to an active state (e.g., on and / or a state in which content is displayed); outputs an audio output; and / or outputs a tactile output); and based on a determination that the computer system is in sleep tracking mode (e.g., option 636a is in an active state and / or an on state) (e.g., when the first type of notification data is received), the computer system abandons outputting (e.g., suppresses) the first notification corresponding to the first type of notification data (e.g., abandons displaying the first notification; abandons causing the display generation component to transition from an inactive state to an active state; abandons outputting an audio output; and / or abandons outputting a tactile output). Automatically suppressing notifications when the computer system is in sleep tracking mode allows the user to perform the operation with less user input, thereby reducing the amount of user input required to perform the operation.

[0315] In some embodiments, in response to one or more user inputs (e.g., one or more touch inputs, one or more non-touch inputs, and / or one or more gesture inputs) on a second external device (e.g., 800) separate from the computer system (e.g., a wearable device, a smart watch, a smart phone, a tablet computer, and / or a computer system that controls an external display) corresponding to a request to enter a sleep tracking mode (e.g., where one or more notifications (e.g., notifications of the first type) received by the computer system are suppressed and / or where user sleep information (e.g., sleep quality information) is collected), the computer system enters a sleep tracking mode (e.g., a user is able to provide one or more user inputs on the electronic device 800 to cause the electronic device 600 to enter a sleep focus mode state), wherein: receiving body temperature information corresponding to the user includes receiving body temperature information corresponding to the user from the second external device; and when the computer system is in the sleep tracking mode, the second external device collects body temperature information corresponding to the user. In some embodiments, the second external device collects body temperature information corresponding to the user based on a determination that the computer system is in the sleep tracking mode. Automatically collecting body temperature information from an external device in response to the computer system entering a sleep tracking mode allows the body temperature information to be collected with less user input, thereby reducing the amount of user input required to perform an operation.

[0316] In some embodiments, the computer system receives notification data of a second type (e.g., notifications of a type that are suppressed while in sleep tracking mode) (in some embodiments, all notifications are suppressed in sleep tracking mode) (in some embodiments, a third type of notification (e.g., emergency notifications, wake-up alarm notifications) are not suppressed while in sleep tracking mode). In response to receiving the second type of notification data: based on a determination that the computer system is not in the sleep tracking mode (e.g., when the second type of notification data is received), the computer system (e.g., 600) causes the second external device (e.g., 800) to output the second notification (e.g., causes the second external device to display the second notification; causes a display generation component corresponding to the second external device and / or communicating with a third external device to transition from an inactive state (e.g., closed and / or a state in which content is not displayed on the display generation component) to an active state (e.g., opened and / or a state in which content is displayed); causes the second external device to output an audio output; and / or causes the second external device to output a tactile output corresponding to the second type of notification data; and based on a determination that the computer system (e.g., 600) is in the sleep tracking mode (e.g., when the second type of notification data is received), the computer system (e.g., 600) abandons causing the second external device (e.g., 800) to output the second notification corresponding to the second type of notification data. Automatically suppressing notifications on the second external device when the computer system is in the sleep tracking mode allows the user to perform the operation with less user input, thereby reducing the number of user inputs required to perform the operation.

[0317] In some embodiments, before displaying an updated period tracking user interface (e.g., Figure 8G After 828 in the example, the computer system receives (e.g., via one or more user inputs, from an application, and / or from an external device) test result information (e.g., an OPK (e.g., an ovulation prediction kit) corresponding to the user) from the computer system. Figure 8J After receiving the OPK test result information corresponding to the user (in some embodiments, in response to receiving the OPK test result information corresponding to the user), the computer system determines an updated predicted ovulation day for the user based on the OPK test result information (e.g., Figure 8K , the electronic device 600 has determined based on the user input 860 that the predicted ovulation day for the user is Saturday, May 7). After determining the updated predicted ovulation day for the user, the computer system displays a second updated cycle tracking user interface (e.g., Figure 8K828) (e.g., an updated, revised and / or modified version of the cycle tracking user interface; and / or an updated, revised and / or modified version of the updated cycle tracking user interface (e.g., updated and / or modified based on ovulation prediction kit test result information), including: a representation of an updated predicted ovulation day for the user (e.g., Figure 8K 832e in (in some embodiments, the electronic device 600 uses the first predicted ovulation day (e.g., Figure 8G 832a) in the display Figure 8G The cycle tracking user interface 828 in the embodiment switches to a different and / or updated predicted ovulation day (e.g., Figure 8K 832e) in the display Figure 8K In some embodiments, displaying the second updated cycle tracking user interface also includes displaying (e.g., simultaneously with the representation of the updated predicted ovulation day for the user) a second updated pregnancy window prediction for the user, wherein the second updated pregnancy window prediction is determined based on the updated predicted ovulation day for the user. Automatically determining an updated predicted ovulation day for the user based on the OPK test results allows the user to receive an updated ovulation day prediction with less user input, thereby reducing the number of user inputs required to perform an operation.

[0318] In some embodiments, a second updated period tracking user interface (e.g., Figure 8K 828 in the example) further includes: simultaneously displaying a second updated fertility window prediction for the user (e.g., 832e) with the representation of the updated predicted ovulation day for the user (e.g., 832e) Figure 8K 832a, 832b, 832c, 832d, 832f, and / or a pregnancy window prediction in area 838a in (e.g., a second updated pregnancy window prediction that is different from the updated pregnancy window prediction and / or the same as the updated pregnancy window prediction), wherein the second updated pregnancy window prediction is determined based on the OPK test result information. In some embodiments, the second updated pregnancy window prediction is determined based on an updated predicted ovulation day for the user. Automatically updating the pregnancy window prediction based on the OPK test results allows the user to receive an updated pregnancy window prediction with less user input, thereby reducing the amount of user input required to perform an operation.

[0319] In some embodiments, a representation of a predicted ovulation day for a user (e.g., Figure 8G 832a) is displayed together with a first set of visual characteristics (e.g., color, size and / or shape); and a representation of an updated predicted ovulation day for the user (e.g., Figure 8K 832e) is displayed together with the first set of visual characteristics (e.g., the same color, size, and / or shape). Automatically determining an updated predicted ovulation day for a user based on the OPK test results allows the user to receive an updated ovulation day prediction with less user input, thereby reducing the number of user inputs required to perform the operation.

[0320] It should be noted that the above description with respect to method 950 (eg, Fig. 9B ) also apply in a similar manner to the methods described above and / or below. For example, method 700, method 900, and / or method 1100 optionally include one or more features of the various methods described above with reference to method 950. For example, the body temperature information collected in method 700 can be used to generate health-based notifications and / or predictions in methods 900, 950, and / or 1100. For the sake of brevity, these details are not repeated below.

[0321] FIG. 10A to FIG. 10N Illustrated are exemplary user interfaces for generating and providing health-related notifications according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including Fig.11 process.

[0322] Fig. 10A An electronic device 600 is illustrated having a touch-sensitive display 602. Fig. 10A At, the electronic device 600 displays the above reference FIG. 8A to FIG. 8K The cycle tracking user interface 828 is discussed. Fig. 10A , the current date is June 6, and in the cycle tracking user interface 828, the day indication 1001a representing the current date is selected (eg, as indicated by indications 831a, 831b).

[0323] Fig. 10A Also illustrated is electronic device 800, which is a smartwatch having a touch-sensitive display 802, a rotatable and depressible input mechanism 804, and buttons 806. In the depicted embodiment, electronic device 800 corresponds to electronic device 600 (e.g., electronic device 800 that is paired with electronic device 600 and / or corresponds to the same user as electronic device 600). FIG. 10A to FIG. 10E Electronic device 600 and electronic device 800 are illustrated as displaying substantially identical user interfaces to demonstrate that in certain embodiments, a user can use electronic device 600 or electronic device 800 to record and / or input menstrual information.

[0324] exist Fig. 10A, electronic device 800 displays cycle tracking user interface 1000, which is substantially the same as cycle tracking user interface 828. Cycle tracking user interface 1000 includes area 1002 with multiple day representations (similar to area 830 in cycle tracking user interface 828), option 1004a (corresponding to option 832a), option 1004b (corresponding to option 834b), and option 1004c (corresponding to option 834c). Fig. 10A In the cycle tracking user interface 1000, the day display 1001b representing the current day is selected. Fig. 10A , when the day representation 1001a is selected, the electronic device 600 detects a user input 1005 (e.g., a tap input and / or a touch input) corresponding to the selection of option 834a, which indicates a user request to record menstrual information for the selected day. In addition, when the day representation 1001b is selected, the electronic device 800 detects a user input 1006 (e.g., a tap input and / or a touch input) corresponding to the selection of option 1004a.

[0325] exist Fig. 10B , in response to user input 1005, electronic device 600 displays user interface 1008, and in response to user input 1006, electronic device 800 displays user interface 1012. User interface 1012 corresponds to user interface 1008 (e.g., user interface 1012 is a watch version of user interface 1008 and / or a smaller form factor version of user interface 1008). User interface 1008 includes option 1010a that can be selected by the user to indicate that the user is experiencing light menstrual bleeding, option 1010b that can be selected by the user to indicate that the user is experiencing moderate menstrual bleeding, option 1010c that can be selected by the user to indicate that the user is experiencing heavy menstrual bleeding, option 1010d that can be selected by the user to indicate that the user is experiencing unspecified menstrual bleeding, and option 1010e that can be selected by the user to indicate that the user is not experiencing menstrual bleeding. User interface 1008 also includes option 1010f that can be selected to stop display of user interface 828 (and, for example, cancel entry of menstrual information and return to cycle tracking user interface 1008), and option 1010g that can be selected to advance to the next user interface. User interface 1012 includes options 1014a-1014g corresponding to options 1010a-1010g, respectively. Fig. 10B , the user has specified that the user is experiencing less menstrual bleeding on both electronic device 600 and electronic device 800. Electronic device 600 detects user input 1016a (e.g., touch input and / or tap input) corresponding to selection of option 1014g, and electronic device 800 detects user input 1016b (e.g., touch input and / or tap input) corresponding to selection of option 1010g.

[0326] exist Fig. 10C At , in response to user input 1016a, electronic device 600 displays user interface 1018, and in response to user input 1016b, electronic device 800 displays user interface 1022. User interface 1022 corresponds to user interface 1018 (e.g., user interface 1022 is a watch version of user interface 1018 and / or a smaller form factor version of user interface 1018). User interface 1018 includes various options 1020a-1020e, and user interface 1022 includes corresponding options 1024a-1024g, which can be selected by the user to indicate that the user is experiencing one or more symptoms (e.g., cramps, mood changes, lower back pain, pain, bloating, constipation, headache). At Fig. 10C In the example, on both electronic device 600 and electronic device 800, the user selects five symptoms (cramps, mood changes, pain, bloating, and headache (the last two symptoms are not visible on electronic device 600, as shown in FIG. Fig. 10C After the user has selected their symptom, the electronic device 600 detects user input 1026a (e.g., touch input and / or tap input) corresponding to the selection of option 1020f, and the electronic device 800 detects user input 1026b (e.g., touch input and / or tap input) corresponding to the selection of option 1024h.

[0327] exist Fig. 10D At 1026a, in response to user input 1026a, electronic device 600 displays user interface 1028, and in response to user input 1026b, electronic device 800 displays user interface 1032. User interface 1032 corresponds to user interface 1028 (e.g., user interface 1032 is a watch version of user interface 1028 and / or a smaller form factor version of user interface 1028). User interface 1028 includes option 1030a that can be selected by the user to indicate that the user is experiencing spotting, and user interface 1032 includes corresponding option 1034a. Fig. 10D In , the user is not experiencing spotting and does not select option 1030a or option 1034a. Fig. 10D At , electronic device 600 detects user input 1036a (e.g., touch input and / or tap input) corresponding to option 1030c, and electronic device 800 detects user input 1036b (e.g., touch input and / or tap input) corresponding to option 1034c.

[0328] exist Fig.10E At 1036a, in response to user input 1036a, the electronic device 600 records the menstrual information input by the user and displays the cycle tracking user interface 828. Fig.10EIn the cycle tracking user interface 828, the cycle tracking user interface 828 has been FIG. 10B to FIG. 10D 1001a is now shown with a menstrual indication indicating that the user has recorded menstruation for that day (e.g., a hashed circle at the top of the day representation 1001a), option 834a is shown with "less menstrual blood", and option 834b is shown as indicating that the user has recorded 5 symptoms for that day. Similarly, in response to user input 1036b, the electronic device 800 records the menstrual information entered by the user and displays the cycle tracking user interface 1000, which has also been updated according to the menstrual information entered by the user in the same manner as described above with reference to the cycle tracking user interface 828.

[0329] Fig.10E An example scenario is depicted in which a user has input menstrual information and the electronic device 600 (and / or the electronic device 800) has not detected any potential health issues based on the menstrual information input by the user. However, Fig.10F An alternative scenario is depicted in which the electronic device 600 detects potential health issues based on menstrual information just input by the user.

[0330] exist Fig.10F In response to user input 1036a, the electronic device 600 displays a cycle tracking user interface 828, which is similar to the cycle tracking user interface shown in FIG. Fig.10E The cycle tracking user interface 828 is almost identical to that described in . Fig.10F In the embodiment, the electronic device 600 is based on FIG. 10B to FIG. 10D The user's menstrual cycle information input by the user is used to identify the user's potential health problems. Fig.10F , the electronic device 600 displays a notification 1038a within the cycle tracking user interface 828 indicating that the user may have a potential health problem. In some embodiments, the notification 1038a does not identify the potential health problem and does not present the potential health problem to the user until the user confirms that the basic menstrual cycle information that led to the identification of the potential health problem is accurate. The notification 1038a includes an option 1038c that can be selected to reject the notification 1038a and / or stop the display of the notification 1038a, and an option 1038b that can be selected to view the user's cycle history to confirm whether the user's cycle history is accurate.

[0331] exist Fig.10F, the electronic device 800 does not display a notification of a potential health problem. In some embodiments, the electronic device 600 displays a notification 1038a indicating a potential health problem, but a corresponding device such as the electronic device 800 (e.g., a corresponding wearable device) does not display a notification of a potential health problem. In some embodiments, when the user ignores the notification 1038a and / or does not interact with the notification for a period of time, and the new menstrual cycle information entered by the user (e.g., modifying the previously entered menstrual cycle information and / or entering new menstrual cycle information in the next few days) eliminates the potential health problem identified by the electronic device 600, the electronic device 600 stops displaying the notification 1038a within the cycle tracking user interface 828. Fig.10F At , the electronic device 600 detects a user input 1040 (eg, a touch input and / or a tap input) corresponding to a selection of option 1038b.

[0332] exist Figure 10G At, in response to user input 1040, the electronic device 600 displays a user interface 1042. The user interface 1042 displays menstrual cycle information 1044a, which includes basic menstrual cycle information that causes the electronic device 600 to detect a potential health problem. In various embodiments, the menstrual cycle information 1044a shown in the user interface 1042 changes based on the potential health problem identified by the electronic device 600. For example, if the duration of the user's cycle is determined to be problematic, the menstrual cycle information 1044a shows the cycle duration of the identification that causes the potential health problem, and if the user's spotting frequency is determined to be problematic, the menstrual cycle information 1044a shows the date when the user records spotting. The user interface 1042 instructs the user to view the menstrual cycle information 1044a, and confirm that the menstrual cycle information 1044a is accurate (e.g., by selecting option 1044b), or revise and / or modify the menstrual cycle information 1044a (e.g., by selecting option 1044c). The user interface 1042 also includes an option 1044d that can be selected to stop display of the user interface 1042 without confirming or modifying the menstrual cycle information 1044a (and, for example, returning to the cycle tracking user interface 828). Figure 10G At , the electronic device 600 detects a user input 1046 (eg, a touch input and / or a tap input) corresponding to a selection of option 1044d.

[0333] exist Fig. 10H At, the electronic device 600 displays the above reference FIG. 6A to FIG. 6Q Health summary user interface 604 discussed. In some embodiments, when a potential health problem is determined for the user based on the menstrual cycle information recorded by the user, a notification of the potential health problem is also displayed in the health summary user interface 604. Fig. 10H In FIG. 6 , the electronic device 600 displays a notification 1048a in the health summary user interface 604. The notification 1048a includes an option 1048c that can be selected to stop display of the notification 1048a, and an option 1048b that can be selected to display the user interface 1042. Fig. 10H In some embodiments, when the user ignores notification 1048a and / or does not interact with the notification for a period of time, and the new menstrual cycle information entered by the user (e.g., modifying the previously entered menstrual cycle information and / or entering new menstrual cycle information in the next few days) eliminates the potential health problem identified by the electronic device 600, the electronic device 600 stops displaying notification 1048c in the health summary user interface 604.

[0334] exist Fig.10I In , the electronic device 600 is in an inactive state and a locked state, and no content is displayed on the display 602. Fig.10J At , the electronic device 600 receives and / or generates information related to a push notification indicating a potential health issue for the user. Fig.10J In response to receiving and / or generating the information, the electronic device 600 displays a lock screen user interface 840 that includes a push notification 1052 informing the user that the electronic device 600 has detected a potential health problem based on the menstrual cycle information input by the user. In some embodiments, the push notification 1052 causes the display 602 to change from an inactive state (e.g., Fig.10I ) to the active state (e.g., Fig.10J ). In some embodiments, push notification 1052 is generated based on a determination that the user has not yet confirmed or otherwise eliminated a potential health issue identified for the user (e.g., based on a determination that there are still unconfirmed and / or uncleared potential health issues identified for the user). In some embodiments, after electronic device 600 generates and / or displays push notification 1052, electronic device 600 does not display and / or present to the user another push notification for the same unconfirmed potential health issue within a threshold duration (e.g., one month and / or sixty days). Fig.10J At , the electronic device 600 detects user input 1054 (eg, touch input and / or tap input) corresponding to selection of the push notification 1052 .

[0335] exist Figure 10K In response to user input 1054, the electronic device 600 displays a user interface 1042, which is referred to above. Figure 10G Described in Figure 10K, the electronic device 600 detects a user input 1056 (eg, a touch input and / or a tap input) corresponding to a selection of option 1044b, thereby indicating that the user confirms the accuracy of the menstrual cycle information 1044a.

[0336] exist Fig.10L At 1054, in response to user input 1056 and based on the determination that the user has confirmed the menstrual cycle information 1044a, the electronic device 600 displays a user interface 1058. The user interface 1058 includes an indication 1060a identifying a potential health problem detected by the electronic device 600 and criteria for determining the potential health problem. Fig.10L , the electronic device 600 has determined that in the past 180 days, the user has had two cycles that lasted longer than 10 days, and therefore the user may have an extended menstrual period that the user should discuss with a doctor. The user interface 1058 includes an instruction 1060b that instructs the user to contact a doctor. The user interface 1058 also includes an option 1060c that can be selected to initiate a process for exporting menstrual cycle information for the user (e.g., exporting a PDF file containing all menstrual cycle information related to the user in the past 12 months, which PDF file can be used for the electronic device 600). The user interface 1058 also includes an option 1060d that can be selected to stop display of the user interface 1058, and an option 1060e that can be selected to return to the user interface 1042.

[0337] Fig.10L A potential health problem of "extended cycle" is shown, and indication 1060a displays criteria for the health problem. However, in other scenarios, the electronic device 1058 is capable of detecting other health problems, and indication 1060a will display different information. For example, in one embodiment, the potential health problem is irregular menstrual cycles, and the criteria for determining irregular menstrual cycles include determining that the difference between the user's maximum menstrual cycle length and the minimum menstrual cycle length within a predetermined time period is greater than a threshold value (e.g., for the last two non-overlapping 90-day windows, the difference is greater than or equal to 17 days). In another example, the potential health problem is infrequent menstrual cycles, and the criteria for determining the infrequent menstrual cycles include determining that the recorded menstrual cycle information includes less than a threshold number of recorded menstrual periods during the predetermined time period (e.g., less than two recorded menstrual periods in the last two non-overlapping 90-day windows). In another example, the underlying health problem is frequent spotting, and the criteria for determining frequent spotting include determining that the recorded menstrual cycle information includes a threshold number of instances of spotting within a predefined time period (e.g., one or more days of spotting recorded that are not adjacent to menstrual periods in the last two non-overlapping 90-day windows).

[0338] In some embodiments, if the user selects Figure 10K 1044b) and modifies the basic menstrual cycle information in a manner that eliminates the determination of the potential health problem, the electronic device 600 displays an indication that the potential health problem is not applicable to the user (and does not display the user interface 1058). However, if the user selects option 1044c and modifies the basic menstrual cycle information, and the modified menstrual cycle information still indicates a potential health problem for the user, the electronic device 600 displays the user interface 1058.

[0339] In some embodiments, when a user identifies a potential health issue (e.g., by identifying basic menstrual cycle information, such as Figures 10K to 10L ), potential health issues are displayed in the cycle history user interface 848 ( Figure 8H ) and / or cycle details user interface 854 ( Figure 8I ). In some embodiments, unconfirmed potential health issues are not displayed in these user interfaces, but confirmed potential health issues are displayed in these user interfaces. In addition, in some embodiments, for confirmed potential health issues that occurred within a threshold time period (e.g., within the past 6 months or within the past 12 months), the cycle history user interface 848 and / or the cycle details user interface 854 display an option that can be selected to export a 12-month menstrual cycle history (similar to option 1060c). However, for confirmed potential health issues that did not occur within the threshold time period (e.g., occurred more than 6 months ago or more than 12 months ago), the cycle history user interface 848 and / or the cycle details user interface 854 do not display an option that can be selected to export a 12-month menstrual cycle history.

[0340] In some embodiments, in response to lack of user data input and / or lack of user interaction, notification 1038a and / or notification 1052 are not displayed and / or generated to avoid false positives and / or inaccurate notifications. In other words, in some embodiments, notifications of potential health issues are generated based solely on the menstrual cycle information input by the user.

[0341] In some embodiments, if the user indicates that one or more predetermined health factors (e.g., use of birth control and / or pregnancy) apply to the user and / or have applied to the user for a threshold duration (e.g., within the last 12 weeks), a notification of the potential health issue (e.g., notification 1038a and / or push notification 1052) is not generated and / or displayed.

[0342] Figure 10M An electronic device 1070 is depicted having a touch-sensitive display 1072. Figure 10M, electronic device 1070 displays sharing user interface 1074. Electronic device 1070 corresponds to a different user than electronic device 600. In the depicted example scenario, electronic device 600 corresponds to a user named Jane Appleseed, and electronic device 1070 corresponds to a user named Sarah. Jane Appleseed has chosen to share menstrual cycle information with Sarah. Figure 10M , sharing user interface 1074 includes object 1076a, which indicates that Sarah is able to view menstrual cycle information corresponding to user Jane Appleseed. Additionally, sharing user interface 1074 includes objects 1076b and 1076c, which indicate that user Sarah is sharing menstrual cycle information with user "Mom" and is also sharing menstrual cycle information with Jane Appleseed. Object 1076a indicates that there are one or more reminders corresponding to user Jane Appleseed (e.g., based on a determination that one or more potential health issues have been identified for user Jane Appleseed based on the menstrual cycle information corresponding to user Jane Appleseed). Figure 10M At , the electronic device 1070 detects a user input 1078 (eg, a touch input and / or a tap input) corresponding to a selection of the object 1076a.

[0343] exist Fig.10N At 1078, in response to user input 1078, electronic device 1070 displays user interface 1080. User interface 1080 corresponds to user Jane Appleseed and includes an indication 1082e indicating that electronic device 600 has determined that Jane Appleseed has a potential health problem of extended menstrual cycle. In some embodiments, indication 1082e is displayed in user interface 1080 only after the user of electronic device 600 confirms the potential health problem (e.g., by confirming the accuracy of basic menstrual cycle information). In some embodiments, unconfirmed potential health problems are not displayed in user interface 1080.

[0344] User interface 1080 also includes option 1082g that can be selected to stop the display of indication 1082e, and option 1082f that can be selected to display additional details about the potential health problems identified for Jane Appleseed. User interface 1080 also includes options 1082a-1082d, 1082h and 1082i. Option 1082a can be selected to initiate a process for sending a text message to user Jane Appleseed (e.g., displaying a text message user interface). Option 1082b can be selected to initiate a process for calling user Jane Appleseed (e.g., displaying a phone call user interface). Option 1082c can be selected to initiate a process for video calling user Jane Appleseed (e.g., displaying a video call user interface). Option 1082d can be selected to display the contact information of user Jane Appleseed. Option 1082h displays ovulation prediction information for user Jane Appleseed. Option 1082i can be selected to return to user interface 1074.

[0345] Fig.11 1 is a flowchart illustrating a method for generating and providing health-related notifications using a computer system according to some embodiments. Method 1100 is performed at a computer system (e.g., 100, 300, 500) (e.g., 600 and / or 800) (e.g., a wearable device, a smart watch, a smart phone, a tablet computer, and / or a computer system controlling an external display) that communicates with: a display generation component (e.g., 602 and / or 802) (e.g., a display controller, a touch-sensitive display system; and / or a display (e.g., integrated and / or connected)) and one or more input devices (e.g., 601, 602, 603, 604, 605, 606, 607, 608, 609, 610, 611, 612, 613, 614, 615, 616, 617, 618, 619, 620, 621, 623, 624, 625, 626, 627, 628, 629, 630, 631, 632, 633, 634, 635, 636, 637, 638, 639, 640, 641, 642, 643, 644, 645, 646, 647, 648, 649, 650, 651, 652, 653, 654, 655, 656, 657, 658, 659, 660, 661, 662, 663, 664, 665 2, 802, 804 and / or 806) (e.g., a touch-sensitive surface (e.g., a touch-sensitive display); an accelerometer; a rotatable input mechanism; a pressable input mechanism; and / or a rotatable and pressable input mechanism) is performed at a computer system (e.g., 100, 300, 500 and / or 600) (e.g., a wearable device, a smart watch, a smart phone, a tablet computer, a head-mounted device (e.g., a head-mounted augmented reality and / or extended reality device), and / or a computer system controlling an external display). Some operations in method 1100 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0346] As described below, method 1100 provides an intuitive way to generate and provide health-related notifications. The method reduces the cognitive burden of users generating and / or receiving health-related notifications, thereby creating a more effective human-computer interface. For battery-powered computing devices, users are enabled to generate and / or receive health-related notifications more quickly and more efficiently, saving power and increasing the time interval between battery charges.

[0347] The computer system (e.g., 600, 800) receives (1102) menstrual cycle information (e.g., information identifying one or more dates during which a user is menstruating; and / or information identifying one or more dates during which a user exhibits spotting) via one or more input devices (e.g., 601, 602, 802, 804, and / or 806) (e.g., input by a user via one or more user inputs) (e.g., one or more touch inputs, one or more non-touch inputs, and / or one or more gestures) (e.g., in FIG. 10A to FIG. 10D In some embodiments, based on a determination that the menstrual cycle information does not meet the first set of criteria for indicating a potential health problem, the computer system forgoes displaying the push notification. Based on a determination that the menstrual cycle information meets the first set of criteria, the computer system displays (1106) a push notification (e.g., 1052) via a display generation component (e.g., causing the display generation component to transition from an inactive state (e.g., a closed state and / or a state in which the display generation c...

Claims

1. A method, comprising: At a computer system in communication with a display generating component, one or more input devices, and a temperature sensor: receiving, via the one or more input devices, an input corresponding to a request to enter a sleep tracking mode; In response to the input, entering the sleep tracking mode; During the sleep tracking mode, causing a first set of user body temperature information to be collected via the temperature sensor; receiving notification data of a first type; In response to receiving the notification data of the first type: Based on determining that the computer system is not in the sleep tracking mode, outputting a first notification corresponding to notification data of the first type; as well as based on determining that the computer system is currently in the sleep tracking mode, forgoing outputting the first notification corresponding to the first type of notification data; as well as After causing the first set of user temperature information to be collected, a temperature user interface including representations of one or more sets of user temperature information including the first set of user temperature information is displayed via a display generation component.

2. The method according to claim 1, further comprising: receiving, via the one or more input devices, a second input corresponding to a request to enter a first silent mode different from the sleep tracking mode; In response to receiving the second input, entering the first silent mode without initiating a process of collecting body temperature information; receiving second notification data of the first type; as well as In response to receiving second notification data of the first type: outputting a second notification corresponding to second notification data of the first type based on determining that the computer system is not in the first silent mode and the computer system is not in the sleep tracking mode; as well as Based on determining that the computer system is currently in the first silent mode, outputting a notification corresponding to the second notification data of the first type is abandoned.

3. The method according to any one of claims 1 to 2, further comprising: receiving, via the one or more input devices, a third input corresponding to a request to define a sleep schedule, wherein the sleep schedule includes, for at least a first day, a first sleep start time and a first sleep end time; After receiving the third input: Entering the sleep tracking mode in response to determining that the current time corresponds to the first sleep start time; and Based on determining that the current time does not correspond to the first sleep start time, entering the sleep tracking mode is abandoned.

4. The method according to any one of claims 1 to 3, wherein causing the first set of user temperature information to be collected comprises: enabling a first external device separate from the computer system to collect the first group of user temperature information; as well as The first set of user body temperature information is received from the first external device.

5. The method according to any one of claims 1 to 4, further comprising: Before receiving the input, displaying the body temperature user interface via the display generation component includes: Based on determining that a threshold amount of body temperature information has not been collected, displaying an indication that the threshold amount of body temperature information has not been collected; and Based on determining that the threshold amount of body temperature information has been collected, a representation of one or more sets of user body temperature information is displayed without displaying the indication that the threshold amount of body temperature information has not been collected.

6. The method according to any one of claims 1 to 5, further comprising: After displaying the temperature user interface including the representation of one or more sets of user temperature information, displaying a second instance of the temperature user interface, wherein: Based on determining that a second set of criteria is satisfied, the second instance of the temperature user interface includes a representation of a second set of user temperature information; and Based on determining that the second set of criteria is not met, the second instance of the temperature user interface does not include the representation of the second set of user temperature information and includes a second indication indicating that the second set of criteria is not met.

7. The method according to any one of claims 1 to 6, further comprising: When the temperature user interface is displayed, receiving a selection input via the one or more input devices; as well as In response to receiving the selection input: Based on determining that the selection input corresponds to a selection of a first time frame option corresponding to a first time frame, displaying within the temperature user interface a representation of one or more sets of user temperature information corresponding to the first time frame; as well as Based on determining that the selection input corresponds to a selection of a second time frame option different from the first time frame option, representations of one or more sets of user body temperature information corresponding to the second time frame are displayed in the body temperature user interface, wherein the second time frame option corresponds to a second time frame different from the first time frame.

8. A method according to any one of claims 1 to 7, wherein the representation of one or more sets of user temperature information comprises one or more relative temperature measurements.

9. The method according to any one of claims 1 to 8, further comprising: A first detailed user interface corresponding to the first group of user temperature information is displayed via the display generation component, wherein the first detailed user interface includes information about the first group of user temperature information that is not displayed in the temperature user interface.

10. The method according to claim 9, wherein the first details user interface comprises: The start time corresponding to the first group of user temperature information; as well as Corresponding to the end time of the first group of user temperature information.

11. The method according to any one of claims 9 to 10, wherein: The body temperature user interface includes relative body temperature information corresponding to the first group of user body temperature information; and The first detailed user interface includes one or more absolute body temperature measurement results corresponding to the first set of user body temperature information. 12 . The method according to claim 9 , wherein the first detailed user interface comprises external device information corresponding to the first set of user body temperature information.

13. The method according to any one of claims 1 to 12, further comprising: receiving first notification data corresponding to one or more messages received from a first external user and / or one or more messages received from a first application; In response to receiving the first notification data: outputting a second notification corresponding to the first notification data based on determining that the computer system is not in the sleep tracking mode; as well as Based on determining that the computer system is currently in the sleep tracking mode and the first notification data includes notification data of a second type, outputting the second notification corresponding to the first notification data is foregone.

14. The method according to claim 13, further comprising: In response to receiving the first notification data: Based on determining that the computer system is currently in the sleep tracking mode and the first notification data includes notification data of a third type different from the second type, the second notification corresponding to the first notification data is output.

15. The method according to any one of claims 1 to 14, further comprising: During the sleep tracking mode: Based on determining that the computer system is in the sleep tracking mode, causing a second external device different from the computer system to display an indication that the computer system has suppressed notifications.

16. The method according to any one of claims 1 to 15, wherein: The representation of one or more sets of user temperature information includes: a representation of a third set of user temperature information collected by a second external device separate from the computer system; and A representation of a fourth set of user temperature information, the fourth set of user temperature information being different from the second set of user temperature information and being collected by a third external device different from the second external device and the computer system.

17. 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 that communicates with a display generation component, one or more input devices, and a temperature sensor, the one or more programs comprising instructions for executing the method according to any one of claims 1 to 16.

18. A computer system configured to communicate with a display generation component, one or more input devices, and a temperature sensor, the computer system comprising: one or more processors; as well as 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 executing the method according to any one of claims 1 to 16.

19. A computer system configured to communicate with a display generation component, one or more input devices, and a temperature sensor, the computer system comprising: Components for carrying out the method according to any one of claims 1 to 16.

20. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component, one or more input devices and a temperature sensor, the one or more programs comprising instructions for performing the method according to any one of claims 1 to 16.

21. 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, one or more input devices, and a temperature sensor, the one or more programs comprising instructions for: receiving, via the one or more input devices, an input corresponding to a request to enter a sleep tracking mode; In response to the input, entering the sleep tracking mode; During the sleep tracking mode, causing a first set of user body temperature information to be collected via the temperature sensor; receiving notification data of a first type; In response to receiving the notification data of the first type: outputting a first notification corresponding to notification data of the first type in response to determining that the computer system is not in the sleep tracking mode; as well as based on determining that the computer system is currently in the sleep tracking mode, forgoing outputting the first notification corresponding to the first type of notification data; as well as After causing the first set of user temperature information to be collected, a temperature user interface including representations of one or more sets of user temperature information including the first set of user temperature information is displayed via a display generation component.

22. A computer system configured to communicate with a display generation component, one or more input devices, and a temperature sensor, the computer system comprising: one or more processors; as well as 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: receiving, via the one or more input devices, an input corresponding to a request to enter a sleep tracking mode; In response to the input, entering the sleep tracking mode; During the sleep tracking mode, causing a first set of user body temperature information to be collected via the temperature sensor; receiving notification data of a first type; In response to receiving the notification data of the first type: Based on determining that the computer system is not in the sleep tracking mode, outputting a first notification corresponding to notification data of the first type; as well as based on determining that the computer system is currently in the sleep tracking mode, forgoing outputting the first notification corresponding to the first type of notification data; as well as After causing the first set of user temperature information to be collected, a temperature user interface including representations of one or more sets of user temperature information including the first set of user temperature information is displayed via a display generation component.

23. A computer system configured to communicate with a display generation component, one or more input devices, and a temperature sensor, the computer system comprising: means for receiving, via the one or more input devices, an input corresponding to a request to enter a sleep tracking mode; means for entering said sleep tracking mode in response to said input; a component for causing a first set of user body temperature information to be collected via the temperature sensor during the sleep tracking mode; means for receiving notification data of a first type; means for, in response to receiving notification data of said first type, performing the following operations: outputting a first notification corresponding to notification data of the first type in response to determining that the computer system is not in the sleep tracking mode; as well as based on determining that the computer system is currently in the sleep tracking mode, forgoing outputting the first notification corresponding to the first type of notification data; as well as A component for displaying a temperature user interface including representations of one or more sets of user temperature information via a display generation component after causing the first set of user temperature information to be collected, the one or more sets of user temperature information including the first set of user temperature information.

24. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component, one or more input devices, and a temperature sensor, the one or more programs comprising instructions for: receiving, via the one or more input devices, an input corresponding to a request to enter a sleep tracking mode; In response to the input, entering the sleep tracking mode; During the sleep tracking mode, causing a first set of user body temperature information to be collected via the temperature sensor; receiving notification data of a first type; In response to receiving the notification data of the first type: outputting a first notification corresponding to notification data of the first type in response to determining that the computer system is not in the sleep tracking mode; as well as based on determining that the computer system is currently in the sleep tracking mode, forgoing outputting the first notification corresponding to the first type of notification data; as well as After causing the first set of user temperature information to be collected, a temperature user interface including representations of one or more sets of user temperature information including the first set of user temperature information is displayed via a display generation component.

25. A method comprising: At a computer system in communication with a display generating component and one or more input devices: Receiving body temperature information corresponding to a user; as well as After receiving the body temperature information corresponding to the user, a push notification is displayed via the display generating component so that the display generating component changes from an inactive state to an active state and indicates to the user that a predicted ovulation day for the user has been determined, wherein the predicted ovulation day is determined based on the body temperature information corresponding to the user.

26. The method of claim 25, wherein displaying the push notification comprises displaying the push notification while maintaining the computer system in a locked state. 27 . The method according to claim 25 , wherein receiving the body temperature information corresponding to the user comprises receiving the body temperature information corresponding to the user from a first external device separate from the computer system.

28. A method according to any one of claims 25 to 27, wherein: The computer system is in communication with a first sensor; and Receiving the body temperature information corresponding to the user includes receiving the body temperature information corresponding to the user from the first sensor.

29. The method according to any one of claims 25 to 28, further comprising: When the push notification is displayed: receiving, via the one or more input devices, a selection input corresponding to selecting the push notification; as well as In response to receiving the selection input corresponding to selecting the push notification, displaying a cycle tracking user interface including the predicted ovulation day via the display generation component.

30. The method of any one of claims 25 to 29, wherein the push notification includes the predicted ovulation day.

31. A method according to any one of claims 25 to 30, wherein displaying the push notification is performed in response to determining that the user has enabled a fertility tracking setting.

32. The method of any one of claims 25 to 31, wherein displaying the push notification is performed based on determining that a threshold amount of body temperature information corresponding to the user has been collected.

33. The method of any one of claims 25 to 32, wherein displaying the push notification is performed based on determining that one or more predetermined health factors are not applicable to the user.

34. The method according to any one of claims 25 to 33, further comprising: receiving, via the one or more input devices, an input corresponding to a request to enter a sleep tracking mode; as well as In response to the input, entering the sleep tracking mode, wherein: Receiving the body temperature information corresponding to the user is performed when the computer system is in the sleep tracking mode.

35. The method of claim 34, further comprising: receiving notification data of a first type; as well as In response to receiving notification data of the first type: outputting a first notification corresponding to notification data of the first type in response to determining that the computer system is not in the sleep tracking mode; as well as Based on determining that the computer system is in the sleep tracking mode, outputting the first notification corresponding to the first type of notification data is foregone.

36. The method of claim 35, further comprising: In response to receiving the notification data of the first type: causing a second external device separate from the computer system to display a second notification corresponding to the first type of notification data based on determining that the computer system is not in the sleep tracking mode; as well as Based on determining that the computer system is in the sleep tracking mode, causing the second external device to display the second notification corresponding to the first type of notification data is abandoned.

37. The method according to any one of claims 34 to 36, wherein receiving the body temperature information corresponding to the user comprises receiving the body temperature information corresponding to the user from a third external device separate from the computer system.

38. The method of claim 37, further comprising: receiving notification data of a second type; as well as In response to receiving notification data of the second type: causing the third external device to output a third notification corresponding to the third type of notification data based on determining that the computer system is not in the sleep tracking mode; as well as Based on determining that the computer system is in the sleep tracking mode, causing the third external device to output the third notification corresponding to the second type of notification data is abandoned.

39. The method according to any one of claims 25 to 38, further comprising: receiving second body temperature information corresponding to the user; as well as After receiving the second body temperature information corresponding to the user: Based on determining that the user has not logged an ovulation prediction kit test result during a predefined time period, displaying, via the display generation component, a second push notification that causes the display generation component to transition from the inactive state to the active state and indicates to the user that a second predicted ovulation day for the user has been determined, wherein the second predicted ovulation day is determined based on the second body temperature information corresponding to the user; as well as Based on determining that the user has logged ovulation prediction kit test results during the predefined time period, forgoing displaying the second push notification.

40. 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 that communicates with a display generating component and one or more input devices, the one or more programs comprising instructions for executing the method according to any one of claims 25 to 39.

41. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: one or more processors; as well as 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 executing the method according to any one of claims 25 to 39.

42. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: Means for carrying out the method according to any one of claims 25 to 39.

43. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices, the one or more programs comprising instructions for performing a method according to any one of claims 25 to 39.

44. 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: receiving body temperature information corresponding to a user; and After receiving the body temperature information corresponding to the user, a push notification is displayed via the display generating component so that the display generating component changes from an inactive state to an active state and indicates to the user that a predicted ovulation day for the user has been determined, wherein the predicted ovulation day is determined based on the body temperature information corresponding to the user.

45. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: one or more processors; as well as 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: Receiving body temperature information corresponding to a user; as well as After receiving the body temperature information corresponding to the user, a push notification is displayed via the display generating component so that the display generating component changes from an inactive state to an active state and indicates to the user that a predicted ovulation day for the user has been determined, wherein the predicted ovulation day is determined based on the body temperature information corresponding to the user.

46. ​​A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: A component for receiving body temperature information corresponding to a user; as well as A component for, after receiving the body temperature information corresponding to the user, displaying via the display generating component a push notification that causes the display generating component to transition from an inactive state to an active state and indicating to the user that a predicted ovulation day for the user has been determined, wherein the predicted ovulation day is determined based on the body temperature information corresponding to the user.

47. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for: receiving body temperature information corresponding to a user; and After receiving the body temperature information corresponding to the user, a push notification is displayed via the display generating component so that the display generating component changes from an inactive state to an active state and indicates to the user that a predicted ovulation day for the user has been determined, wherein the predicted ovulation day is determined based on the body temperature information corresponding to the user.

48. A method comprising: At a computer system in communication with a display generating component and one or more input devices: At a first time, displaying, via the display generation component, a cycle tracking user interface, including displaying a first fertility window prediction for a user; receiving body temperature information corresponding to the user; After receiving the body temperature information corresponding to the user, at a second time after the first time, determining a predicted ovulation day for the user based on the body temperature information corresponding to the user; as well as At a third time after the second time, displaying, via the display generation component, an updated cycle tracking user interface, includes simultaneously displaying: a representation of the predicted ovulation day for the user; as well as An updated fertility window prediction for the user that is different than the first fertility window prediction for the user.

49. The method of claim 48, wherein receiving the body temperature information corresponding to the user comprises receiving the body temperature information corresponding to the user from a first external device separate from the computer system.

50. The method of claim 48, wherein: The computer system is in communication with a first sensor; and Receiving the body temperature information corresponding to the user includes receiving the body temperature information corresponding to the user from the first sensor.

51. A method according to any one of claims 48 to 50, wherein: said representation of said predicted ovulation day for said user is displayed in a first visual appearance; as well as The updated fertility window prediction for the user is displayed in a second visual appearance different from the first visual appearance.

52. The method of claim 51, wherein: The representation of the predicted ovulation day for the user comprises a first color; and The updated fertility window prediction for the user includes a second color different from the first color.

53. The method according to any one of claims 48 to 52, further comprising: At a fourth time after the third time, displaying the cycle tracking user interface via the display generation component includes: Based on determining that the fertility tracking setting is enabled, displaying a second fertility window prediction for the user; and Based on determining that the fertility tracking setting is not enabled, displaying a menstrual period prediction for the user without displaying the second fertility window prediction for the user.

54. The method according to any one of claims 48 to 53, further comprising: receiving second body temperature information corresponding to the user; After receiving the second body temperature information corresponding to the user, displaying the cycle tracking user interface via the display generation component includes: based on determining that a fertility tracking setting is enabled, displaying a representation of a second predicted ovulation day for the user, wherein the second predicted ovulation day is determined based on the second body temperature information; as well as Based on determining that the fertility tracking setting is not enabled, forgoing displaying the representation of the second predicted ovulation day for the user.

55. The method according to any one of claims 48 to 54, further comprising: receiving third body temperature information corresponding to the user; After receiving the third body temperature information corresponding to the user: determining a third predicted ovulation day for the user based on the third body temperature information in accordance with determining that one or more predetermined health factors are not applicable to the user; as well as According to determining that at least one of the one or more predetermined health factors is applicable to the user, determining a predicted ovulation day for the user based on the third body temperature information is abandoned.

56. The method according to any one of claims 48 to 55, further comprising: receiving fourth body temperature information corresponding to the user; as well as After receiving the fourth body temperature information corresponding to the user: upon determining that a threshold amount of body temperature information has been collected, determining a fourth predicted ovulation day for the user based on the fourth body temperature information; as well as Based on determining that the threshold amount of body temperature information has not been collected, determining the predicted ovulation day for the user based on the fourth body temperature information is abandoned.

57. The method according to any one of claims 48 to 56, further comprising: receiving, via the one or more input devices, an input corresponding to a request to enter a sleep tracking mode; as well as In response to the input, entering the sleep tracking mode, wherein: Receiving the body temperature information corresponding to the user is performed when the computer system is in the sleep tracking mode.

58. The method of claim 57, further comprising: receiving notification data of a first type; as well as In response to receiving notification data of the first type: outputting a first notification corresponding to notification data of the first type in response to determining that the computer system is not in the sleep tracking mode; as well as Based on determining that the computer system is in the sleep tracking mode, outputting the first notification corresponding to the first type of notification data is foregone.

59. The method according to any one of claims 48 to 58, further comprising: In response to one or more user inputs on a second external device separate from the computer system corresponding to a request to enter a sleep tracking mode, entering the sleep tracking mode, wherein: Receiving the body temperature information corresponding to the user includes receiving the body temperature information corresponding to the user from the second external device; and When the computer system is in the sleep tracking mode, the second external device collects the body temperature information corresponding to the user.

60. The method of claim 59, further comprising: receiving notification data of a second type; as well as In response to receiving notification data of the second type: causing the second external device to output a second notification corresponding to the second type of notification data based on determining that the computer system is not in the sleep tracking mode; as well as Based on determining that the computer system is in the sleep tracking mode, causing the second external device to output the second notification corresponding to the second type of notification data is abandoned.

61. The method of any one of claims 48 to 60, further comprising: After displaying the updated cycle tracking user interface, receiving OPK test result information corresponding to the user; after receiving the OPK test result information corresponding to the user, determining an updated predicted ovulation day for the user based on the OPK test result information; as well as After determining an updated predicted ovulation day for the user, displaying, via the display generating component, a second updated cycle tracking user interface, the second updated cycle tracking user interface comprising: A representation of an updated predicted ovulation day for the user.

62. The method of claim 61, wherein displaying the second updated cycle tracking user interface further comprises: A second updated fertility window prediction for the user is displayed concurrently with the representation of the updated predicted ovulation day for the user, wherein the second updated fertility window prediction is determined based on the OPK test result information.

63. The method according to any one of claims 61 to 62, wherein: The representation of the predicted ovulation day for the user is displayed with a first set of visual characteristics; as well as The representation of the updated predicted ovulation day for the user is displayed with the first set of visual characteristics.

64. 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 that communicates with a display generating component and one or more input devices, the one or more programs comprising instructions for executing a method according to any one of claims 48 to 63.

65. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: one or more processors; as well as 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 executing the method according to any one of claims 48 to 63.

66. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: Means for carrying out the method according to any one of claims 48 to 63.

67. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices, the one or more programs comprising instructions for performing a method according to any one of claims 48 to 63.

68. 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: At a first time, displaying, via the display generation component, a cycle tracking user interface, including displaying a first fertility window prediction for a user; receiving body temperature information corresponding to the user; After receiving the body temperature information corresponding to the user, at a second time after the first time, determining a predicted ovulation day for the user based on the body temperature information corresponding to the user; as well as At a third time after the second time, displaying, via the display generation component, an updated cycle tracking user interface, includes simultaneously displaying: a representation of the predicted ovulation day for the user; as well as An updated fertility window prediction for the user that is different than the first fertility window prediction for the user.

69. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: one or more processors; as well as 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: At a first time, displaying, via the display generation component, a cycle tracking user interface, including displaying a first fertility window prediction for a user; receiving body temperature information corresponding to the user; After receiving the body temperature information corresponding to the user, at a second time after the first time, determining a predicted ovulation day for the user based on the body temperature information corresponding to the user; as well as At a third time after the second time, displaying, via the display generation component, an updated cycle tracking user interface, includes simultaneously displaying: a representation of the predicted ovulation day for the user; as well as An updated fertility window prediction for the user that is different than the first fertility window prediction for the user.

70. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: for displaying, via the display generating component, a cycle tracking user interface at a first time, including components for displaying a first fertility window prediction for a user; A component for receiving body temperature information corresponding to the user; means for determining a predicted ovulation day for the user based on the body temperature information corresponding to the user at a second time after the first time after receiving the body temperature information corresponding to the user; as well as Means for displaying, via the display generating means, an updated period tracking user interface at a third time after the second time, comprises simultaneously displaying: a representation of the predicted ovulation day for the user; as well as An updated fertility window prediction for the user that is different than the first fertility window prediction for the user.

71. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for: At a first time, displaying, via the display generation component, a cycle tracking user interface, including displaying a first fertility window prediction for a user; receiving body temperature information corresponding to the user; After receiving the body temperature information corresponding to the user, at a second time after the first time, determining a predicted ovulation day for the user based on the body temperature information corresponding to the user; as well as At a third time after the second time, displaying, via the display generation component, an updated cycle tracking user interface, includes simultaneously displaying: a representation of the predicted ovulation day for the user; as well as An updated fertility window prediction for the user that is different than the first fertility window prediction for the user.

72. A method comprising: At a computer system in communication with a display generating component and one or more input devices: receiving menstrual cycle information for a user via the one or more input devices; as well as Based on determining that the menstrual cycle information satisfies a first set of criteria, a push notification is displayed, via the display generation component, to the user indicating that the computer system has identified a potential health issue for the user.

73. The method of claim 72, wherein the push notification causes the display generating component to transition from an inactive state to an active state.

74. The method of any one of claims 72 to 73, wherein displaying the push notification comprises displaying the push notification while maintaining the computer system in a locked state.

75. The method of any one of claims 72 to 74, wherein: The first set of criteria includes a first criterion that is met when a difference between a maximum menstrual cycle duration during a predetermined time period and a minimum menstrual cycle duration during the predetermined time period exceeds a threshold value.

76. A method according to any one of claims 72 to 75, wherein: The first set of criteria includes a second criterion that is met when the menstrual cycle information for the user indicates that the user has experienced less than a threshold number of menstrual periods within a predetermined time period.

77. The method of any one of claims 72 to 76, wherein: The first set of criteria includes a third criterion that is met when the menstrual cycle information for the user indicates that the user has experienced greater than a threshold number of menstrual periods having a duration greater than a threshold duration within a defined time period.

78. The method of any one of claims 72 to 77, wherein: The first set of criteria includes a fourth criterion, which is met when the menstrual cycle information for the user indicates that the user has experienced greater than a threshold number of instances of spotting that did not occur during and / or directly adjacent to a menstrual period within a defined time period.

79. The method of any one of claims 72 to 78, further comprising: After displaying the push notification, receiving second menstrual cycle information for the user; as well as After receiving the second menstrual cycle information: displaying, via the display generating component, a second push notification indicating to the user that the computer system has identified a potential health issue for the user based on determining that the second menstrual cycle information satisfies the first set of criteria and a threshold duration has elapsed since displaying the push notification; as well as Based on determining that the second menstrual cycle information satisfies the first set of criteria and less than the threshold duration has elapsed since the push notification was displayed, displaying the second push notification is foregone.

80. The method of any one of claims 72 to 79, further comprising: receiving third menstrual cycle information for the user; After receiving the third menstrual cycle information for the user: Based on determining that the third menstrual cycle information is input by the user and that the third menstrual cycle information satisfies the first set of criteria, displaying, via the display generation component, a third push notification to the user indicating that the computer system has identified a potential health issue for the user; as well as Based on determining that the third menstrual cycle information is not input by the user, displaying the third push notification is abandoned.

81. The method of any one of claims 72 to 80, wherein the first set of criteria includes a sixth criterion that is met when one or more predetermined health factors are not applicable to the user.

82. A method according to any one of claims 72 to 81, wherein the first set of criteria includes a seventh criterion, which is met when one or more predetermined health factors are not applicable to the user for at least a threshold duration.

83. The method of any one of claims 72 to 82, further comprising: while displaying the push notification, receiving, via the one or more input devices, a selection input corresponding to selecting the push notification; as well as In response to receiving the selection input, displaying a cycle history user interface via the display generation component, wherein the cycle history user interface includes: a first option selectable to confirm a cycle history for the user; as well as A second option selectable to revise the period history for the user.

84. The method of claim 83, further comprising: receiving, via the one or more input devices, a second selection input corresponding to a selection of the first option while displaying the cycle history user interface; as well as In response to receiving the second selection input, first information identifying the potential health issue for the user is displayed via the display generation component.

85. The method of claim 84, further comprising: In response to receiving the second selection input, a third option is displayed via the display generation component, the third option being selectable to initiate a process for exporting a file containing menstrual cycle history information corresponding to the user.

86. The method of claim 83, further comprising: receiving, via the one or more input devices, a third selection input corresponding to a selection of the second option while the period history user interface is displayed; receiving, via the one or more input devices, corrected menstrual cycle information corresponding to the user after receiving the third selection input; as well as In response to receiving the corrected menstrual cycle information: Based on determining that the corrected menstrual cycle information satisfies the first set of criteria, displaying, via the display generating component, second information identifying the potential health issue for the user; as well as Based on determining that the corrected menstrual cycle information does not satisfy the first set of criteria, an indication is displayed via the display generation component that a potential health issue has not been identified for the user.

87. The method of claim 86, further comprising: In response to receiving the corrected menstrual cycle information: Based on determining that the corrected menstrual cycle information satisfies the first set of criteria, An export option is displayed via the display generating component, the export option being selectable to initiate a process for exporting a file containing menstrual cycle history information corresponding to the user.

88. The method of any one of claims 72 to 87, further comprising: After receiving the menstrual cycle information for the user, displaying a cycle tracking user interface via the display generation component, wherein: Based on determining that the menstrual cycle information satisfies the first set of criteria, displaying the cycle tracking user interface includes displaying a first indicator to indicate to the user that the computer system has identified a potential health issue for the user.

89. The method of claim 88, further comprising: receiving, via the one or more input devices, second updated menstrual cycle information for the user after displaying the cycle tracking user interface including the first indicator; as well as After receiving the second updated menstrual cycle information, the cycle tracking user interface is redisplayed, wherein: Based on determining that the second updated menstrual cycle information does not meet the first set of criteria, the cycle tracking user interface does not include the first indicator.

90. The method of any one of claims 72 to 89, further comprising: After displaying the push notification, receiving, via the one or more input devices, one or more confirmation inputs confirming the menstrual cycle information for the user; as well as In response to receiving the one or more confirmation inputs: Based on determining that the user of the computer system has chosen to share menstrual cycle information with a second user who is different from the user of the computer system, an external device separate from the computer system and corresponding to the second user displays a first visual indication indicating that the computer system has identified a potential health issue for the user.

91. The method of any one of claims 72 to 90, further comprising: displaying, via the display generating component, a cycle history user interface, wherein the cycle history user interface includes one or more health indicators indicative of one or more previously identified health issues identified by the computer system and confirmed by the user, the one or more health indicators including: A first health indication is indicative of a first previously identified health problem identified by the computer system and confirmed by the user.

92. The method of claim 91, wherein: Based on determining that the first previously identified health issue occurred within a threshold duration, displaying the cycle history user interface further comprises displaying a first export option corresponding to the first previously identified health issue and selectable to initiate a process for exporting a file containing menstrual cycle history information corresponding to the user; as well as Based on determining that the first previously identified health issue has not occurred within the threshold duration, the period history user interface does not include the first export option corresponding to the first previously identified health issue.

93. 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 that communicates with a display generating component and one or more input devices, the one or more programs comprising instructions for executing a method according to any one of claims 72 to 92.

94. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: one or more processors; as well as 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 executing the method according to any one of claims 72 to 92.

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

96. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices, the one or more programs comprising instructions for performing a method according to any one of claims 72 to 92.

97. 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: receiving menstrual cycle information for a user via the one or more input devices; and Based on determining that the menstrual cycle information satisfies a first set of criteria, a push notification is displayed, via the display generation component, to the user indicating that the computer system has identified a potential health issue for the user.

98. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: one or more processors; as well as 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: receiving menstrual cycle information for a user via the one or more input devices; as well as Based on determining that the menstrual cycle information satisfies a first set of criteria, a push notification is displayed, via the display generation component, to the user indicating that the computer system has identified a potential health issue for the user.

99. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: means for receiving menstrual cycle information for a user via the one or more input devices; as well as Means for displaying, via the display generating means, a push notification to the user indicating that the computer system has identified a potential health issue for the user based on determining that the menstrual cycle information satisfies a first set of criteria.

100. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for: receiving menstrual cycle information for a user via the one or more input devices; and Based on determining that the menstrual cycle information satisfies a first set of criteria, a push notification is displayed, via the display generation component, to the user indicating that the computer system has identified a potential health issue for the user.

Citation Information

Patent Citations

  • Method and apparatus for integrating manual input

    US20020015024A1

  • Gestures for touch sensitive input devices

    US20060026521A1

  • Gestures for touch sensitive input devices

    US20060026536A1

  • Virtual input device placement on a touch screen user interface

    US20060033724A1

  • Multipoint touchscreen

    US20060097991A1