User interface for health tracking

Abstract

The invention relates to a user interface for health tracking. The present disclosure generally relates to tracking health information and generating related predictions and / or notifications.

Description

[0001] This application is a divisional application of a patent application for an invention named "User Interface for Health Tracking" with the application number 202380064379.X, the filing date of August 29, 2023.

[0002] Cross - Reference to Related Applications

[0003] This application claims priority to U.S. Patent Application No. 18 / 237,339, titled "USER INTERFACES FOR HEALTH TRACKING", filed on August 23, 2023, and U.S. Provisional Patent Application No. 63 / 404,139, titled "USER INTERFACES FOR HEALTH TRACKING", filed on September 6, 2022. The entire content of each of these applications is incorporated herein by reference. Technical Field

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

[0005] Recurrent (e.g., recurring) events such as recurrent health events can be tracked on an electronic device to record past events and predict future events. Summary of the Invention

[0006] However, some techniques for using an electronic device to track health information are generally cumbersome and inefficient. For example, some prior arts use complex and time-consuming user interfaces that may include multiple button presses or keystrokes. The prior arts require more time than necessary, which results in wasted user time and device energy. This latter consideration is particularly important in battery-powered devices.

[0007] Accordingly, the present technology provides faster and more efficient methods and interfaces for an electronic device to track health information and to generate related predictions and / or notifications. Such methods and interfaces optionally supplement or replace other methods for tracking health information and for generating related predictions and / or notifications. Such methods and interfaces reduce the cognitive burden imposed on the user and result in a more effective human-machine interface. For battery-powered computing devices, such methods and interfaces save power and increase the time interval between battery charges.

[0008] According to some embodiments, a method is described. The method includes: at a computer system in communication with a display generation 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 a first type of notification data; in response to receiving the first type of the notification data: outputting a first notification corresponding to the first type of the notification data based on a determination that the computer system is not in the sleep tracking mode; and foregoing outputting the first notification corresponding to the first type of the notification data based on a determination that the computer system is currently in the sleep tracking mode; and after causing the first set of user body temperature information to be collected, displaying, via the display generation component, a body temperature user interface including a representation of one or more sets of user body temperature information, the one or more sets of user body temperature information including the first set of user body temperature information.

[0009] 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, one or more input devices, and a temperature sensor, 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 a first type of notification data; in response to receiving the first type of the notification data: outputting a first notification corresponding to the first type of the notification data based on a determination that the computer system is not in the sleep tracking mode; and foregoing outputting the first notification corresponding to the first type of the notification data based on a determination that the computer system is currently in the sleep tracking mode; and after causing the first set of user body temperature information to be collected, displaying, via the display generation component, a body temperature user interface including a representation of one or more sets of user body temperature information, the one or more sets of user body temperature information including the first set of user body temperature information.

[0010] 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, one or more input devices, and a temperature sensor. The one or more programs include 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 first type notification data; in response to receiving the first type of the notification data: outputting a first notification corresponding to the first type of the notification data based on a determination that the computer system is not in the sleep tracking mode; and foregoing outputting the first notification corresponding to the first type of the notification data based on a determination that the computer system is currently in the sleep tracking mode; and after causing the first set of user body temperature information to be collected, displaying, via the display generation component, a body temperature user interface including a representation of one or more sets of user body temperature information, the one or more sets of user body temperature information including the first set of user body 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: one or more processors; and a memory that stores one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for: 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 first type notification data; in response to receiving the first type of the notification data: outputting a first notification corresponding to the first type of the notification data based on a determination that the computer system is not in the sleep tracking mode; and foregoing outputting the first notification corresponding to the first type of the notification data based on a determination that the computer system is currently in the sleep tracking mode; and after causing the first set of user body temperature information to be collected, displaying, via the display generation component, a body temperature user interface including a representation of one or more sets of user body temperature information, the one or more sets of user body temperature information including the first set of user body temperature information.

[0012] 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: components for performing the following operations: 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; components for performing the following operations: during the sleep tracking mode, causing a first set of user body temperature information to be collected via the temperature sensor; receiving first type of notification data; components for performing the following operations: in response to receiving the first type of the notification data: outputting a first notification corresponding to the first type of the notification data based on a determination that the computer system is not in the sleep tracking mode; and foregoing outputting the first notification corresponding to the first type of the notification data based on a determination that the computer system is currently in the sleep tracking mode; and a component for displaying, via the display generation component, a body temperature user interface including a representation of one or more sets of user body temperature information after causing the first set of user body temperature information to be collected, the one or more sets of user body temperature information including the first set of user body temperature information.

[0013] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a computer system that communicates 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, 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 first type of notification data; in response to receiving the first type of the notification data: outputting a first notification corresponding to the first type of the notification data based on a determination that the computer system is not in the sleep tracking mode; and foregoing outputting the first notification corresponding to the first type of the notification data based on a determination that the computer system is currently in the sleep tracking mode; and displaying, via the display generation component, a body temperature user interface including a representation of one or more sets of user body temperature information after causing the first set of user body temperature information to be collected, the one or more sets of user body temperature information including the first set of user body temperature information.

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

[0015] 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: 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.

[0016] According to some embodiments, a transitory computer-readable storage medium is described. The 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: 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.

[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 and includes: one or more processors; and a memory that stores one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: 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.

[0018] 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, 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 date for the user has been determined, wherein the predicted ovulation date is determined based on the body temperature information corresponding to the user.

[0019] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a computer system that communicates with a display generation component and one or more input devices, the one or more programs including instructions for: 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 date for the user has been determined, wherein the predicted ovulation date is determined based on the body temperature information corresponding to the user.

[0020] According to some embodiments, a method is described. The method includes: at a computer system that communicates with a display generation 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 conception window prediction for the 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 date for the user based on the body temperature information corresponding to the user; and at a third time after the second time, displaying, via the display generation component, an updated cycle tracking user interface, including simultaneously displaying: a representation of the predicted ovulation date for the user; and an updated conception window prediction for the user that is different from the first conception window prediction for the user.

[0021] 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: at a first time, displaying a cycle tracking user interface via the display generation component, including displaying a first conception window prediction for the 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 date 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 date for the user; and an updated conception window prediction for the user that is different from the first conception window prediction for the user.

[0022] According to some embodiments, a transitory computer-readable storage medium is described. The 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: at a first time, displaying a cycle tracking user interface via the display generation component, including displaying a first conception window prediction for the 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 date 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 date for the user; and an updated conception window prediction for the user that is different from the first conception 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, and includes: one or more processors; and a memory that stores one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: at a first time, displaying a cycle tracking user interface via the display generation component, including displaying a first conception window prediction for the 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 date 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 date for the user; and an updated conception window prediction for the user that is different from the first conception window prediction for the user.

[0024] 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, at a first time, displaying a cycle tracking user interface via the display generation component, including displaying a first conception window prediction for the user; a component for receiving body temperature information corresponding to the user; a component for, after receiving the body temperature information corresponding to the user, at a second time after the first time, determining a predicted ovulation date for the user based on the body temperature information corresponding to the user; and a component for, 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 date for the user; and an updated conception window prediction for the user that is different from the first conception window prediction for the user.

[0025] 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: at a first time, displaying a cycle tracking user interface via the display generation component, including displaying a first conception window prediction for the 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 date 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 date for the user; and an updated conception window prediction for the user that is different from the first conception window prediction for the user.

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

[0027] 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: 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.

[0028] 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, 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.

[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, and includes: one or more processors; and a memory that stores one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: receiving menstrual cycle information for a user via the one or more input devices; and displaying, via the display generation component, a push notification indicating to the user 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 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: means for receiving menstrual cycle information for a user via the one or more input devices; and means for displaying, via the display generation component, a push notification indicating to the user 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.

[0031] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a computer system that communicates with a display generation component and one or more input devices, the one or more programs including instructions for: receiving menstrual cycle information for a user via the one or more input devices; and displaying, via the display generation component, a push notification indicating to the user 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.

[0032] 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 transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.

[0033] Thus, faster and more effective methods and interfaces for tracking health information and for generating related predictions and / or notifications are provided for the device, thereby improving the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces can supplement or replace other methods for tracking health information and for generating related predictions and / or notifications. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0036] Figure 1B is a block diagram illustrating exemplary components for event handling in accordance with some embodiments.

[0037] Figure 2 illustrates a portable multifunctional device having a touch screen in accordance with some embodiments.

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

[0039] Figure 4A illustrates an exemplary user interface for a menu applied to a portable multifunctional device in accordance with some embodiments.

[0040] Figure 4B illustrates an exemplary user interface for a multifunctional device having a touch-sensitive surface separate from the display in accordance with some embodiments.

[0041] Figure 5A illustrates a personal electronic device in accordance with some embodiments.

[0042] Figure 5B is a block diagram illustrating a personal electronic device in accordance with some embodiments.

[0043] Figures 6A through 6Q illustrates an exemplary user interface for tracking body temperature information in accordance with some embodiments.

[0044] Figure 7 is a flowchart illustrating a method for tracking body temperature information in accordance with some embodiments.

[0045] Figures 8A through 8K illustrates an exemplary user interface for generating and providing ovulation day prediction in accordance with some embodiments.

[0046] Figure 9A is a flowchart illustrating a method for generating and providing ovulation day prediction in accordance with some embodiments.

[0047] Figure 9B is a flowchart illustrating a method for generating and providing ovulation day prediction in accordance with some embodiments.

[0048] Figures 10A through 10NIllustrates an exemplary user interface for generating and providing health-related notifications according to some embodiments.

[0049] Figure 11 Is a flowchart illustrating a method for generating and providing health-related notifications according to some embodiments. Detailed Description

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

[0051] There is a need for an electronic device that provides effective methods and interfaces for tracking health information and for generating related predictions and / or notifications. Such technologies can reduce the cognitive burden on users who track health information, thereby increasing productivity. Additionally, such technologies can reduce processor power and battery power that would otherwise be wasted on redundant user input.

[0052] Below, Figures 1A through 1B 、 Figure 2 、 Figure 3 、 Figures 4A through 4B and Figures 5A through 5B Provide a description of exemplary devices for performing technologies for tracking health information and for generating related predictions and / or notifications. Figures 6A through 6Q Illustrates an exemplary user interface for tracking body temperature information. Figure 7 Is a flowchart illustrating a method for tracking body temperature information according to some embodiments. Figures 6A through 6Q The user interface in is for illustrating the processes described below, including Figure 7 the process in. Figures 8A through 8K Illustrates an exemplary user interface for generating and providing ovulation day predictions. Figure 9A Is a flowchart illustrating a method for generating and providing ovulation day predictions according to some embodiments. Figure 9B Is a flowchart illustrating a method for generating and providing ovulation day predictions according to some embodiments. Figures 8A through 8K The user interface in is for illustrating the processes described below, including Figure 9A and Figure 9B the process in. Figures 10A through 10N Illustrates an exemplary user interface for generating and providing health-related notifications. Figure 11 Is a flowchart illustrating a method for generating and providing health-related notifications according to some embodiments. Figures 10A through 10N The user interface in is for illustrating the processes described below, including Figure 11 the process in.

[0053] The processes described below enhance the operability of a device and make the user-device interface more effective through various techniques (e.g., by helping a user provide appropriate input and reducing user errors when operating / interacting with the device), 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 when a set of conditions has been met without further user input, 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 faster and more effectively.

[0054] In addition, in methods where one or more of the steps described herein depend on one or more conditions being met, it should be understood that the method can be repeated in multiple iterations such that, during the repeated process, all of the conditions that determine the steps in the method are met in different iterations of the method. For example, if a method requires performing a first step (if a condition is met) and a second step (if the condition is not met), a person of ordinary skill in the art will know to repeat the stated steps until both the condition is met and the condition is not met (in no particular order). Thus, a method described as having one or more steps that depend on one or more conditions being met can be rewritten as a method that repeats until each condition described in the method has been met. However, this does not require a system or computer-readable medium to state that the system or computer-readable medium includes instructions for performing conditional operations based on the satisfaction of corresponding one or more conditions and thus be able to determine whether the possible conditions have been met without explicitly repeating the steps of the method until all of the conditions that determine the steps in the method have been met. A person of ordinary skill in the art will also understand that, similar to a method with conditional steps, a system or computer-readable storage medium can repeat the steps of the method as many times as needed to ensure that all conditional steps have been performed.

[0055] Although the following description uses terms such as "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. 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.

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

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

[0058] Embodiments of an electronic device, a user interface for such a device, and associated processes for using such a device are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions such as PDA and / or music player functions. Exemplary embodiments of the portable multifunctional device include, but are not limited to, devices from Apple Inc. (Cupertino, California), devices, iPod devices and Device. Optionally, other portable electronic devices are used, such as a laptop computer or a tablet computer having a touch-sensitive surface (e.g., a touch screen display and / or a touchpad). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer having a touch-sensitive surface (e.g., a touch screen display and / or a touchpad). In some embodiments, the electronic device is a computer system that communicates (e.g., via wireless communication, via wired communication) with a display generation component. The display generation component is configured to provide a visual output, such as a display via a CRT monitor, a display via an LED monitor, or a display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. As used herein, "displaying" content includes displaying content (e.g., video data rendered or decoded by a display controller 156) by 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 the content.

[0059] 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, a mouse, and / or a joystick.

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

[0061] The 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 the corresponding information displayed on the device are optionally adjusted and / or varied for different applications, and / or within the respective applications. Thus, a common physical architecture of the device, such as a touch-sensitive surface, optionally supports various applications with a user interface that is intuitive and clear to the user.

[0062] Attention is now turned to embodiments of a portable device having a touch-sensitive display. Figure 1AFIG. 0 is a block diagram of a portable multifunctional device 100 having a touch-sensitive display system 112 in accordance with some embodiments. The touch-sensitive display 112 is sometimes called a “touch screen” for convenience and is sometimes known as or called a “touch-sensitive display system”. Device 100 includes memory 102 (which optionally includes one or more computer-readable storage media), memory controller 122, one or more processing units (CPUs) 120, peripheral device interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input / output (I / O) subsystem 106, other input control devices 116, and external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 for detecting the intensity of contacts on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile outputs on device 100 (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.

[0063] As used in this specification and the claims, the "intensity" of a contact on a touch-sensitive surface refers to the force or pressure of the contact (e.g., finger contact) on the touch-sensitive surface (force per unit area), or to a surrogate for the force or pressure of the contact on the touch-sensitive surface. The intensity of the contact has a range of values that includes at least four different values and more typically includes hundreds of different values (e.g., at least 256). The intensity of the contact is optionally determined (or measured) using a variety of methods and a variety of sensors or combinations of sensors. For example, one or more force sensors beneath or adjacent to the touch-sensitive surface are optionally used to measure the force at different points on the touch-sensitive surface. In some embodiments, force measurements from multiple force sensors are combined (e.g., weighted average) to determine the estimated contact force. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and / or change in size of the contact area detected on the touch-sensitive surface, the capacitance and / or change in capacitance of the touch-sensitive surface near the contact, and / or the resistance and / or change in resistance of the touch-sensitive surface near the contact are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the surrogate measurement of the contact force or pressure is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measurement). In some embodiments, the surrogate measurement of the contact force or pressure is converted to 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 on a smaller device with limited footprint, the smaller device being used to (e.g., on a touch-sensitive display) display affordances and / or receive user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or physical / mechanical controls such as a knob or button).

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

[0065] It should be understood that device 100 is merely an example of a portable multifunctional device, and device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of these components. 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.

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

[0067] The peripheral device interface 118 can be used to couple the input 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 chip 104. In some other embodiments, they are optionally implemented on separate chips.

[0068] The RF (Radio Frequency) circuit 108 receives and transmits RF signals, which are also referred to as electromagnetic signals. The RF circuit 108 converts electrical signals into electromagnetic signals / converts electromagnetic signals into electrical signals, and communicates with a communication network and other communication devices via electromagnetic signals. The RF circuit 108 optionally includes well-known circuits for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a codec chipset, a subscriber identity module (SIM) card, a memory, and so on. The RF circuit 108 optionally communicates with the network and other devices via wireless communication, and these networks are such as the Internet (also known as the World Wide Web (WWW)), an intranet, and / or a wireless network (such as a cellular phone network, a wireless local area network (LAN), and / or a metropolitan area network (MAN)). The RF circuit 108 optionally includes well-known circuits for detecting a near field communication (NFC) field, for example, via a short-range communication radio component. The wireless communication optionally uses any one 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), Wi-Fi (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), WiMAX, 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 Leveraging 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 date of submission of this document.

[0069] The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between the user and the device 100. The audio circuit 110 receives audio data from the peripheral interface 118, converts the audio data into an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal into sound waves audible to humans. The audio circuit 110 also receives the electrical signal converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signal into audio data and transmits the audio data to the peripheral 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 interface 118. In some embodiments, the audio circuit 110 also includes an earphone jack (e.g., Figure 2 212 in

[0070] The I / O subsystem 106 couples input / output peripheral devices on the device 100, such as the touch screen 112 and other input control devices 116, to the peripheral 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 haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive electrical signals from the other input control devices 116 / send electrical signals to the 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 (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 in Figure 2in 206). 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 detected when the user does not touch an input element that is part of the device (or independent of an input element that is part of the device) and is based on the detected movement of a part of the user's body through the air (including the movement of the user's body relative to an absolute reference (e.g., the angle of the user's arm relative to the ground or the distance of the user's hand relative to the ground), the movement relative to another part of the user's body (e.g., the movement of the user's hand relative to the user's shoulder, the movement of one of the user's hands relative to the other of the user's hands, and / or the movement of the user's finger relative to another finger or part of the hand of the user), and / or the absolute movement of a part of the user's body (e.g., a tap gesture that includes the hand moving a predetermined amount and / or speed in a predetermined pose, or a shake gesture that includes a predetermined speed or amount of rotation of a part of the user's body)).

[0071] Quickly pressing the depress button optionally disengages the lock of the touch screen 112 or optionally starts the process of unlocking the device using gestures on the touch screen, as described in U.S. Patent Application No. 11 / 322,549, filed Dec. 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. Long pressing the depress button (e.g., 206) optionally powers on or powers off the device 100. The functions of the 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.

[0072] 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 and / or sends electrical signals to the touch screen 112. The touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, 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.

[0073] The touch screen 112 has a touch-sensitive surface, sensor, or group of sensors that accepts input from the user based on haptic and / or tactile contact. The touch screen 112 and the display controller 156 (along with any associated modules and / or instruction sets in the memory 102) detect contact (and any movement or interruption of that contact) on the touch screen 112 and convert the detected contact into an 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.

[0074] The touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, but in other embodiments uses other display technologies. The touch screen 112 and the display controller 156 optionally use any of a variety of touch sensing technologies now known or later developed, 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, the variety of touch sensing technologies including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as the technology used in and iPod from Apple Inc. (Cupertino, California).

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

[0076] Touch-sensitive displays in some embodiments of the touchscreen 112 are described in the following applications: (1) U.S. Patent Application No. 11 / 381,313, "Multipoint Touch Surface Controller," filed May 2, 2006; (2) U.S. Patent Application No. 10 / 840,862, "Multipoint Touchscreen," filed May 6, 2004; (3) U.S. Patent Application No. 10 / 903,964, "Gestures For Touch Sensitive Input Devices," filed Jul. 30, 2004; (4) U.S. Patent Application No. 11 / 048,264, "Gestures For Touch Sensitive Input Devices," filed Jan. 31, 2005; (5) U.S. Patent Application No. 11 / 038,590, "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices," filed Jan. 18, 2005; (6) U.S. Patent Application No. 11 / 228,758, "Virtual Input Device Placement On A Touch Screen User Interface," filed Sep. 16, 2005; (7) U.S. Patent Application No. 11 / 228,700, "Operation Of A Computer With A Touch Screen Interface," filed Sep. 16, 2005; (8) U.S. Patent Application No. 11 / 228,737, "Activating Virtual Keys Of A Touch-Screen Virtual Keyboard," filed Sep. 16, 2005; and (9) U.S. Patent Application No. 11 / 367,749, "Multi-Functional Hand-Held Device," filed Mar. 3, 2006. All of these applications are hereby incorporated by reference in their entirety.

[0077] 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 approximately 160 dpi. The user optionally uses any suitable object or attachment such as a stylus, finger, etc. to contact the touch screen 112. In some embodiments, the user interface is designed to work primarily through finger-based contact and gestures, which may not be as precise as stylus-based input due to the larger contact area of the finger on the touch screen. In some embodiments, the device converts the rough finger-based input into precise pointer / cursor positioning or commands for performing the actions desired by the user.

[0078] In some embodiments, in addition to the touch screen, the device 100 optionally further includes a touchpad for activating or deactivating specific functions. In some embodiments, the touchpad is a touch-sensitive area of the device, which, unlike the touch screen, does not display a 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.

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

[0080] The device 100 optionally further 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 referred to as the camera module), the optical sensor 164 optionally captures still images or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite the touch screen display 112 on the front of the device, such that the touch screen display can be used as a viewfinder for still image and / or video image capture. In some embodiments, the optical sensor is located on the front of the device such that an image of the user is optionally captured for video conferencing while the user views other video conferencing participants on the touch screen display. 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) such that a single optical sensor 164 is used with the touch screen display for both video conferencing and still image and / or video image capture.

[0081] The device 100 optionally further 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 a scene from a viewpoint (e.g., the depth camera sensor). In some embodiments, in conjunction with the imaging module 143 (also referred to as the 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 on the front of the device 100 such that an image of the user with depth information is optionally captured for video conferencing while the user views other video conferencing 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 on the rear of the device, or on 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) such that the depth camera sensor 175 is used with the touch screen display for both video conferencing and still image and / or video image capture.

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

[0083] The device 100 optionally further includes one or more proximity sensors 166. Figure 1A Shows a proximity sensor 166 coupled to the peripheral device interface 118. Alternatively, the proximity sensor 166 is optionally coupled to an input controller 160 in the I / O subsystem 106. The proximity sensor 166 optionally operates as described in the following U.S. patent application numbers: 11 / 241,839, titled "Proximity Detector In Handheld Device"; 11 / 240,788, titled "ProximityDetector In Handheld Device"; 11 / 620,702, titled "Using Ambient Light Sensor ToAugment Proximity Sensor Output"; 11 / 586,862, titled "Automated Response To AndSensing Of User Activity In Portable Devices"; and 11 / 638,251, titled "MethodsAnd Systems For Automatic Configuration Of Peripherals", which are hereby incorporated by reference in their entirety.

[0084] The device 100 optionally further includes one or more haptic output generators 167. Figure 1AShows a haptic output generator coupled to the haptic feedback controller 161 in the I / O subsystem 106. The haptic output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components; and / or electromechanical devices for converting energy into linear motion such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other haptic output generating components (e.g., components for converting an electrical signal into a haptic output on the device). The contact intensity sensor 165 receives haptic feedback generation instructions from the haptic feedback module 133 and generates a haptic output on the device 100 that can be felt by a user of the device 100. In some embodiments, at least one haptic output generator is juxtaposed or adjacent to a touch-sensitive surface (e.g., the touch-sensitive display system 112), and optionally generates a haptic output by moving the touch-sensitive surface vertically (e.g., into / out 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 haptic output generator sensor is located on the rear of the device 100, opposite the touch screen display 112 located on the front of the device 100.

[0085] The device 100 optionally further includes one or more accelerometers 168. Figure 1A Shows an accelerometer 168 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 optionally operates 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 hereby incorporated by reference in their entireties. In some embodiments, information is displayed in a portrait view or a landscape view on the touch screen display based on an analysis of data received from one or more accelerometers. The device 100 optionally further 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 location and orientation (e.g., portrait or landscape) of the device 100.

[0086] In some embodiments, the software components stored in the memory 102 include an operating system 126, a communication module (or instruction set) 128, a touch / 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 applications (or instruction sets) 136. Additionally, in some embodiments, the memory 102 ( Figure 1A ) or 370 ( Figure 3 ) stores a device / global internal state 157, as Figure 1A and Figure 3 shown. The device / global internal state 157 includes one or more of the following: an active application state that indicates which applications (if any) are currently active; a display state that indicates what applications, views, or other information occupy various regions of the touch screen display 112; a sensor state that includes information obtained from the various sensors and input control devices 116 of the device; and location information related to the location and / or orientation of the device.

[0087] 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 facilitates communication between the various hardware components and software components.

[0088] 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 ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) are adapted to be directly coupled to other devices or indirectly coupled through a network (e.g., the Internet, a wireless LAN, etc.). In some embodiments, the external port is the same as, similar to, and / or compatible with the 30-pin connector used on (a trademark of Apple Inc.) devices, a multi-pin (e.g., 30-pin) connector.

[0089] The contact / motion module 130 optionally detects contact with the touchscreen 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., a touchpad or a physical click wheel). The contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether contact has occurred (e.g., detecting a finger press event), determining the intensity of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there is 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 ceased (e.g., detecting a finger lift event or contact break). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point optionally includes determining the rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of the contact point being represented by a series of contact data. These operations are optionally applied to single-point contact (e.g., single-finger contact) or multi-point simultaneous contact (e.g., “multi-touch” / multiple finger contact). In some embodiments, the contact / motion module 130 and the display controller 156 detect contact on the touchpad.

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

[0091] The contact / motion module 130 optionally detects gesture inputs made by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and / or intensities of the detected contact). Thus, gestures are optionally detected by detecting a particular contact pattern. 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 subsequently detecting a finger lift (lift-off) event.

[0092] The graphics module 132 includes various known software components for presenting and displaying graphics on the touch screen 112 or other display, including components for altering the visual impact of the displayed graphics (e.g., brightness, transparency, saturation, contrast, or other visual attributes). 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.

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

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

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

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

[0097] Application 136 optionally includes the following modules (or instruction sets) or subsets or supersets thereof:

[0098] ● Contact module 137 (sometimes referred to as an address book or contact list);

[0099] ● Phone module 138;

[0100] ● Video conferencing module 139;

[0101] ● Email client module 140;

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

[0103] ● Fitness support module 142;

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

[0105] ● Image management module 144;

[0106] ● Video player module;

[0107] ● Music player module;

[0108] ● Browser module 147;

[0109] ● Calendar module 148;

[0110] ● Widget module 149, which optionally includes one or more of the following: weather widget 149-1, stock market widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widget 149-6;

[0111] ● Widget creator module 150 for forming user-created widget 149-6;

[0112] ● Search module 151;

[0113] ● Video and music player module 152, which combines the video player module and the music player module;

[0114] ● Notepad module 153;

[0115] ● Map module 154; and / or

[0116] ● Online video module 155.

[0117] Examples of other applications 136 that are optionally stored in the memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice reproduction.

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

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

[0120] In conjunction 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 contacts module 137, and the phone module 138, the video conferencing module 139 includes executable instructions to initiate, conduct, and terminate a video conference between the user and one or more other participants according to user instructions.

[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 email client module 140 includes executable instructions to create, send, receive, and manage emails in response to user instructions. In conjunction with the image management module 144, the email client module 140 makes it very easy to create and send emails with static images or video images taken by the camera module 143.

[0122] In combination with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and 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 a previously entered character, transmitting the corresponding instant message (e.g., using the Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocol for phone-based instant messaging or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving an instant message, and viewing the received instant message. In some embodiments, the transmitted and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments supported in MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant message" refers to both phone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

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

[0124] In combination 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.

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

[0126] In combination 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 browser module 147 includes executable instructions for browsing the Internet according to user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, and linking to attachments and other files of web pages.

[0127] 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 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 calendars (e.g., calendar entries, to-do items, etc.) according to user instructions.

[0128] 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, and the browser module 147, the widget module 149 is a micro application (e.g., weather widget 149-1, stock market widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) optionally downloaded and used by the user or a micro application created by the 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).

[0129] 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, and the browser module 147, the widget creator module 150 is optionally used by the user to create widgets (e.g., transform a user-specified portion of a web page into a widget).

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

[0131] In combination with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, and browser module 147, the 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, as well as executable instructions for displaying, presenting, or otherwise playing back video (e.g., on the touch screen 112 or on an external display connected via the external port 124). In some embodiments, the device 100 optionally includes the functionality of an MP3 player such as an iPod (a trademark of Apple Inc.).

[0132] In combination 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 notepads, to-do lists, etc. according to user instructions.

[0133] In combination with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, 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 related to stores and other points of interest at or near a particular location, and other location-based data) according to user instructions.

[0134] In combination with the 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, e-mail client module 140, and browser module 147, the online video module 155 includes instructions for the following operations: allowing a user to access, browse, receive (e.g., by streaming and / or downloading), play back (e.g., on the touch screen or on an external display connected via the external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, the instant message module 141 is used instead of the e-mail client module 140 to send a link to a particular online video. Additional descriptions of the online video application can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed Jun. 20, 2007, and entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968,067, filed Dec. 31, 2007, and entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of both of which are hereby incorporated by reference in their entirety.

[0135] Each of the above-described modules and applications corresponds to a set of executable instructions 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., sets of instructions) need not be implemented as separate 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, the video player module is optionally combined with the music player module into a single module (e.g., Figure 1A the video and music player module 152 in). In some embodiments, the memory 102 optionally stores a subgroup of the above-described modules and data structures. In addition, the memory 102 optionally stores additional modules and data structures not described above.

[0136] In some embodiments, device 100 is a device in which the operation of a predefined set of functions on the device is performed uniquely via a touchscreen and / or a touchpad. By using the touchscreen and / or the touchpad as the primary input control device for operating device 100, the number of physical input control devices (e.g., push buttons, dials, etc.) on device 100 is optionally reduced.

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

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

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

[0140] In some embodiments, the application internal state 192 includes additional information such as one or more of the following: recovery 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 the 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.

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

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

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

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

[0145] 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 view (of the corresponding application) in which a touch is detected optionally corresponds 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 the hit view, and the set of events that are recognized as correct inputs is optionally determined at least in part based on the hit view of the initial touch that begins the touch-based gesture.

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

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

[0148] The event distributor module 174 distributes event information to an event recognizer (e.g., event recognizer 180). In embodiments that include the active event recognizer determination module 173, the event distributor module 174 delivers the event information to the event recognizer determined by the active event recognizer determination module 173. In some embodiments, the event distributor module 174 stores the event information in an event queue, which is retrieved by the corresponding event receiver 182.

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

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

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

[0152] The event receiver 182 receives event information from the event classifier 170. The event information includes information about sub-events such as a touch or a touch movement. Depending on the sub-event, the event information further includes additional information such as the location of the sub-event. When the sub-event involves the movement of a touch, the event information optionally further includes the rate and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device pose).

[0153] The event comparator 184 compares the 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 status of an event or sub - event. In some embodiments, the event comparator 184 includes an event definition 186. The event definition 186 contains definitions of events (e.g., a predefined sequence of sub - events), such as event 1 (187 - 1), event 2 (187 - 2), and others. In some embodiments, sub - events in an event (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 - tap on a displayed object. For example, a double - tap includes a first touch (touch start) of a predetermined duration on the displayed object, a first lift - off (touch end) of a predetermined duration, a second touch (touch start) of a predetermined duration on the 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, a drag includes a touch (or contact) of a predetermined duration on the displayed object, movement of the touch on the touch - sensitive display 112, and lift - off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

[0154] In some embodiments, the event definition 186 includes definitions of events for corresponding user interface objects. In some embodiments, the event comparator 184 performs a hit test to determine which user interface object is associated with a sub - event. For example, in an application view that displays three user interface objects on the touch - sensitive display 112, when a touch is detected on the touch - sensitive display 112, the 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, the event comparator 184 selects the event handler associated with the sub - event and the object that triggered the hit test.

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

[0156] When the corresponding event recognizer 180 determines that the sub - event sequence does not match any event in the 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 such a case, other event recognizers (if any) that remain active for the hit view continue to track and process the ongoing sub - events of the touch - based gesture.

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

[0158] In some embodiments, when one or more specific sub - events of an event are recognized, the corresponding event recognizer 180 activates the 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 deferring to send) sub - events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a flag associated with the recognized event, and the event handler 190 associated with the flag retrieves the flag and executes a predefined process.

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

[0160] In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone numbers used in contact module 137, or stores video files used in the video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates 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 the touch-sensitive display.

[0161] In some embodiments, event handler 190 includes data updater 176, object updater 177, and GUI updater 178, or has access to the data updater, the object updater, and the GUI updater. 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.

[0162] It should be understood that the above discussion regarding event handling of user touches on the touch-sensitive display also applies to other forms of user input for operating multifunctional device 100 using an input device, and not all user input is initiated on the touchscreen. For example, mouse movement and mouse button presses optionally in cooperation with single or multiple keyboard presses or holds; contact movement on a touchpad, such as tapping, dragging, scrolling, etc.; stylus input; movement of the device; verbal instructions; detected eye movement; biometric input; and / or any combination thereof are optionally used as input corresponding to sub-events defining the events to be discriminated.

[0163] Figure 2Exemplified is a portable multifunctional device 100 having a touch screen 112 according to some embodiments. The touch screen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment and other embodiments described hereinafter, a user can select one or more of these graphics by making gestures on the graphics, for example, by using one or more fingers 202 (not drawn to scale in the figure) or one or more styli 203 (not drawn to scale in the figure). In some embodiments, when a user breaks contact with one or more graphics, selection of the one or more graphics will occur. In some embodiments, the 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 a finger that has made 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, inadvertently contacting a graphic will not select the graphic. For example, when the gesture corresponding to selection is a tap, a swipe gesture that sweeps over an application icon will optionally not select the corresponding application.

[0164] The device 100 optionally further 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 among a set of applications 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.

[0165] In some embodiments, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for powering on / off the device and for locking the device, one or more volume adjustment buttons 208, a subscriber identity module (SIM) card slot 210, a headset jack 212, and a docking / charging external port 124. The push button 206 is optionally used to power on / off the device by pressing the button and holding the button in the pressed state for a predefined time interval; to lock the device by pressing the button and releasing the button before the predefined time interval has elapsed; and / or to 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 intensity sensors 165 for detecting the intensity of contact on the touch screen 112, and / or one or more haptic output generators 167 for generating haptic output for a user of the device 100.

[0166] Figure 3FIG. 0 is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface, in accordance with some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a gaming system, or a control device (e.g., a home or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. Communication bus 320 optionally includes circuitry (sometimes called a chipset) that interconnects system components and controls the communication between them. Device 300 includes an input / output (I / O) interface 330 having a display 340, which is typically a touch screen display. I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350, a touchpad 355, a haptic output generator 357 for generating haptic output on device 300 (e.g., similar to haptic output generator 167 described above with reference to Figure 1A ), sensors 359 (e.g., optical sensors, acceleration sensors, proximity sensors, touch-sensitive sensors, and / or contact intensity sensors (similar to contact intensity sensor 165 described above with reference to Figure 1A ). Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and optionally includes non-volatile memory, such as one or more disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU 310. In some embodiments, memory 370 stores programs, modules, and data structures similar to or a subset of those stored in memory 102 of portable multifunctional device 100 ( Figure 1A ). Additionally, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunctional 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 memory 102 of portable multifunctional device 100 ( Figure 1A ) optionally does not store these modules.

[0167] Figure 3Each of the above - mentioned elements in [element name] is optionally stored in one or more memory devices of the previously mentioned memory device. Each of the above - mentioned modules corresponds to a set of instructions for performing the functions described above. The above - mentioned modules or computer programs (e.g., sets of instructions or including instructions) need not be implemented as separate software programs (such as computer programs (e.g., including instructions)), processes, or modules, and thus various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, the memory 370 optionally stores a subgroup of the above - mentioned modules and data structures. Additionally, the memory 370 optionally stores additional modules and data structures not described above.

[0168] Attention is now turned to embodiments of a user interface optionally implemented on, for example, the portable multifunctional device 100.

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

[0170] ● A signal strength indicator 402 for wireless communications such as cellular signals and Wi - Fi signals;

[0171] ● Time 404;

[0172] ● A Bluetooth indicator 405;

[0173] ● A battery status indicator 406;

[0174] ● A tray 408 with icons for common applications, such as:

[0175] o An icon 416 labeled "Phone" for the phone module 138, which optionally includes an indicator 414 of the number of missed calls or voicemails;

[0176] o An icon 418 labeled "Mail" for the email client module 140, which optionally includes an indicator 410 of the number of unread emails;

[0177] o An icon 420 labeled "Browser" for the browser module 147; and

[0178] o An icon 422 labeled "iPod" for the video and music player module 152 (also known as the iPod (trademark of Apple Inc.) module 152); and

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

[0180] o The icon 424 of the IM module 141 labeled "Message";

[0181] o The icon 426 of the calendar module 148 labeled "Calendar";

[0182] o The icon 428 of the image management module 144 labeled "Photo";

[0183] o The icon 430 of the camera module 143 labeled "Camera";

[0184] o The icon 432 of the online video module 155 labeled "Online Video";

[0185] o The icon 434 of the stock market widget 149-2 labeled "Stock Market";

[0186] o The icon 436 of the map module 154 labeled "Map";

[0187] o The icon 438 of the weather widget 149-1 labeled "Weather";

[0188] o The icon 440 of the alarm clock widget 149-4 labeled "Clock";

[0189] o The icon 442 of the fitness support module 142 labeled "Fitness Support";

[0190] o The icon 444 of the notepad module 153 labeled "Notepad"; and

[0191] o The icon 446 of the settings application or module labeled "Settings", which provides access to the settings of the device 100 and its various applications 136.

[0192] It should be noted that Figure 4A The illustrated icon labels are merely exemplary. For example, the icon 422 of the video and music player module 152 is labeled "Music" or "Music Player". Other labels may optionally be used for the 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.

[0193] Figure 4B An example shows a device having a touch-sensitive surface 451 (e.g., Figure 3 a tablet device or a touchpad 355) separate from the display 450 (e.g., Figure 3Exemplary user interface on device 300). Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting the intensity of contacts on the touch-sensitive surface 451 and / or one or more haptic output generators 357 for generating haptic output for a user of device 300.

[0194] Although some of the following examples will be 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 separate from the display, as Figure 4B shown. In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451 in ) has a major axis (e.g., Figure 4B 453 in ) corresponding to the major axis on the display (e.g., Figure 4B 452 in ). According to these embodiments, the device detects contacts (e.g., Figure 4B 460 and 462 in ) with the touch-sensitive surface 451 at positions corresponding to the respective positions on the display (e.g., in Figure 4B 460 corresponds to 468 and 462 corresponds to 470). Thus, when the touch-sensitive surface (e.g., Figure 4B 451 in ) is separate from the display of the multifunctional device (e.g., Figure 4B 450 in ), user input detected by the device on that touch-sensitive surface (e.g., contacts 460 and 462 and their movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

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

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

[0197] 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, filed May 8, 2013, entitled "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application," published as WIPO Publication No. WO / 2013 / 169849; and International Patent Application Serial Number PCT / US2013 / 069483, filed November 11, 2013, entitled "Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships," published as WIPO Publication No. WO / 2014 / 105276, each of which is hereby incorporated by reference in its entirety.

[0198] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508 (if included) can be in physical form. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms (if included) may allow 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 device 500.

[0199] Figure 5B An exemplary personal electronic device 500 is depicted. In some embodiments, device 500 may include some or all of the components described with respect to Figure 1A , Figure 1B and Figure 3 Device 500 has a bus 512 that operatively couples the I / O section 514 to one or more computer processors 516 and a memory 518. The I / O section 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). Additionally, the I / O section 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 pressable input device and a rotatable input device. In some examples, input mechanism 508 is optionally a button.

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

[0201] The memory 518 of 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 , Figure 9A , Figure 9B and Figure 11)。A computer-readable storage medium can be any medium that tangibly contains or stores computer-executable instructions for use by or in connection with an instruction execution system, apparatus, and device. In some examples, the storage medium is a transient computer-readable storage medium. In some examples, the storage medium is a non-transient computer-readable storage medium. Non-transient computer-readable storage media can include, but are not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical discs based on CD, DVD, or Blu-ray technology, and persistent solid-state memories such as flash memory, solid-state drives, etc. The personal electronic device 500 is not limited to Figure 5B the components and configurations thereof, but may include other components or additional components in a variety of configurations.

[0202] As used herein, the term "presentable representation" refers to a user-interactive graphical user interface object optionally displayed on the display screen of devices 100, 300, and / or 500 ( Figure 1A , Figure 3 and Figures 5A through 5B ). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) each optionally constitute a presentable representation.

[0203] As used herein, the term "focus selector" refers to an input element for indicating the current part of the user interface with which the user is interacting. In some embodiments including a cursor or other position marker, the cursor acts as the "focus selector" such that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., Figure 3 the touchpad 355 in Figure 4B ) or Figure 1A the touch-sensitive display system 112 in Figure 4AIn some specific implementations of the touch screen 112), the detected contact on the touch screen serves as a "focus selector", such that when an input (e.g., a press input made by the contact) is detected at the position of a specific user interface element (e.g., a button, a window, a slider, or other user interface element) on the touch screen display, the specific user interface element is adjusted according to the detected input. In some specific implementations, the focus moves from one area of the user interface to another area of the user interface without a corresponding movement of the cursor or a movement of the contact on the touch screen display (e.g., moving the focus from one button to another button by using the tab key or arrow keys); in these specific implementations, the focus selector moves according to the movement of the focus between different areas of the user interface. Regardless of the specific form taken by the focus selector, the focus selector is typically a user interface element (or a contact on the touch screen display) that is controlled by the user to deliver the interaction with the user interface expected by the user (e.g., by indicating to the device the element of the user interface that the user desires to interact with). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or a touch screen), the position of the focus selector (e.g., a cursor, a contact, or a selection box) above the corresponding button will indicate that the user desires to activate the corresponding button (rather than other user interface elements shown on the device display).

[0204] As used in the specification and claims, the term "feature intensity" of a contact refers to a feature of the contact based on one or more intensities of the contact. In some embodiments, the feature intensity is based on a plurality of intensity samples. The feature intensity is optionally based on a predefined number or set of intensity samples collected during a predefined 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 detection of the contact, before detection of lift-off of the contact, before or after detection of the start of movement of the contact, before detection of the end of the contact, before or after detection of an increase in the intensity of the contact, and / or before or after detection of a decrease in the intensity of the contact). The feature 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 in determining the feature intensity (e.g., when the feature intensity is the average value of the intensity of the contact over time). In some embodiments, the feature intensity is compared to a set of one or more intensity thresholds to determine whether the user has performed an operation. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact whose feature intensity does not exceed the first threshold results in a first operation, a contact whose feature intensity exceeds the first intensity threshold but does not exceed the second intensity threshold results in a second operation, and a contact whose feature intensity exceeds the second threshold results in a third operation. In some embodiments, the comparison between the feature intensity 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 forgo performing the corresponding operation) rather than for determining whether to perform a first operation or a second operation.

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

[0206] As used herein, the terms "open application" or "executing application" refer to a software application that has maintained state information (e.g., as part of the device / global internal state 157 and / or the application internal state 192). An open or executing application is optionally any of the following types of applications:

[0207] ● An active application currently displayed on the display screen of the device on which the application is being used;

[0208] ● A background application (or background process), which is not currently displayed but one or more processes of the application are being processed by one or more processors; and

[0209] ● A paused or hibernated application that is not running but has state information stored in a memory (volatile and non-volatile, respectively)

[0210] and that can be used to resume the execution of the application.

[0211] As used herein, the term "closed application" refers to a software application that does not maintain state information (e.g., the state information of a closed application is not stored in the memory of the device). Thus, 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.

[0212] 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 operable, but it is prevented from performing 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 inadvertent 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 operable, and it is not prevented from performing at least a part of the predefined set of operations that cannot be performed when in the locked state. When the computer system is in the locked state, the computer system is said to be locked. When the computer system is in the unlocked state, the computer is said to be unlocked. In some embodiments, a computer system in the locked state optionally responds to a restricted set of user inputs, the restricted set of user inputs including an input corresponding to an attempt to transition the computer system to the unlocked state or an input corresponding to shutting down the computer system.

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

[0214] Figures 6A through 6Q An exemplary user interface for tracking body temperature information in accordance with some embodiments is illustrated. The user interfaces in these figures are used to illustrate the processes described below, including Figure 7 the processes in.

[0215] Figure 6AAn electronic device 600 having a touch-sensitive display 602 is illustrated. In Figure 6A , the electronic device 600 displays a health summary user interface 604 that shows groups of health information related to a user (e.g., the 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 shows heart rate information related to the user (e.g., the user's heart rate was measured at 82 bpm at 9:41 am) and can be selected to display additional heart rate information (e.g., additional heart rate measurements and / or earlier heart rate measurements) not shown in the health summary user interface 604. Option 606b shows body (e.g., wrist) temperature information related to the user and can be selected to display additional body temperature information not shown in the health summary user interface 604. In Figure 6A , option 606b indicates that wrist data temperature related to the user has not been collected and / or there is no wrist temperature data available for the user. Option 606c shows calorie information related to the user (e.g., 1482 calories were burned on April 22) and can be selected to display additional calorie information (e.g., calorie information for the past few days) not shown in the health summary user interface 604. Option 606d shows active calorie information related to the user (e.g., 249 active calories were burned on April 22) and can be selected to display additional active calorie information (e.g., active calorie information for the past few days) not shown in the health summary user interface 604. Option 606e shows step information related to the user (e.g., 2,945 steps were taken on April 22) and can be selected to display additional step information (e.g., steps taken on past days and / or other days) not shown in the health summary user interface 604. Option 606f can be selected to display a user interface through which the user can access additional health information not shown in the health summary user interface 604. Option 606g can be selected to initiate a process for modifying the health information shown in the health summary user interface 604 (e.g., removing currently included information 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 the health information the user is sharing with other users (e.g., other users the user has selected and / or identified) and / or the 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. InFigure 6A At Figure 6A , the electronic device 600 detects a user input 610 (e.g., a touch input and / or a tap input) corresponding to the selection of option 606b.

[0216] At Figure 6B At Figure 6B , in response to the 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 above the baseline temperature and / or y degrees below the baseline temperature) rather than absolute body temperature information. The wrist temperature user interface 612 includes options 614a - 614c that can be selected to cause body temperature data for different time frames to be displayed within a data graph 614d. For example, option 614a can be selected to view one-week body temperature data within the data graph 614d, option 614b can be selected to display one-month body temperature data within the data graph 614d, and option 614c can be selected to display six-month body temperature data within the data graph 614d. However, in Figure 6B if there is no body temperature data available for the user (e.g., the user has not enabled body temperature recording and / or the user has not taken appropriate steps to record body temperature data), no data is shown in the data graph 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 a process for manually adding body temperature data.

[0217] At Figure 6B if the user of the electronic device 600 has not taken the necessary steps to record any body temperature data. For example, the user has not enabled appropriate settings for the body temperature data to be collected, and / or the user has not taken the appropriate actions required for the body temperature data to be collected. Accordingly, 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 the sleep tracking function (e.g., the sleep focus mode status, as will be described in more detail below) in order to record body temperature information. The electronic device 600 also displays an option 614f that can be selected to initiate a process for setting and / or enabling the sleep tracking function. At Figure 6B At Figure 6B , the electronic device 600 detects a user input 616 (e.g., a touch input and / or a tap input) corresponding to the selection of option 614f.

[0218] At Figure 6CAt 616, in response to user input, 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 graph 620d. For example, option 620a can be selected to view one - week sleep data within data graph 620d, option 620b can be selected to view one - month sleep data within data graph 620d, and option 620c can be selected to view six - month sleep data within data graph 620d. However, in Figure 6C , the user has not taken appropriate steps to record sleep data. Therefore, no data is shown in data graph 620d. Sleep tracking user interface 618 also includes: option 620e that can be selected to display additional sleep data not shown in sleep tracking user interface 618, option 620i that can be selected to display health summary user interface 604, and option 620j that can be selected to initiate a process for manually adding and / or recording sleep data.

[0219] Sleep tracking user interface 618 includes next sleep schedule information 620f, selectable option 620g, and full sleep schedule information 620h. Next sleep schedule information 620f indicates the next sleep cycle that the user has specified. In Figure 6C , the user has specified that the user intends to sleep from 11:00 p.m. to 6:00 a.m. the next day. Option 620g can be selected to modify the next sleep cycle (e.g., specify the 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 expected and / or desired sleep start time and sleep end time for each day of the week). In Figure 6C , the user has defined a sleep schedule that starts at 11:00 p.m. and ends at 6:00 a.m. each day of the week. 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).

[0220] Figure 6C Show that the user has established a daily sleep schedule. Figures 6D through 6G Now an example scenario according to some embodiments will be shown, where the user enables sleep data recording and also enables measurement and recording of body temperature information while the user is sleeping. In Figure 6DAt this point, 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 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. At Figure 6D this point, the electronic device 600 detects a user input 626 (e.g., a touch input and / or a tap input) corresponding to the selection of the option 624.

[0221] At Figure 6E this point, in response to the 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 states can be selectively enabled by the user to indicate that the user does not wish to be disturbed when the focus mode state is enabled. In some embodiments, when a focus mode state of the electronic device 600 is enabled (e.g., Figure 6E any one of the four focus mode states in), one or more notifications that would normally be displayed and / or otherwise output (e.g., via audio and / or haptic output) are suppressed and not output by the electronic device 600, as will be described in more detail below. For example, 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 will be 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.

[0222] The Focus Mode user interface 630e includes a toggle switch 630e. When the toggle switch 630e is toggled to the enabled (or "on") state and the electronic device 600 enters a specific Focus Mode state (e.g., starts operating in a specific Focus Mode state) (e.g., automatically and / or based on user input), it also causes one or more external devices corresponding to the electronic device 600 (e.g., other devices corresponding to the same user) to enter the specific Focus Mode state, such 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 the disabled (or "off") state, when the electronic device 600 enters a specific Focus Mode state and / or operates in that specific Focus Mode state, it does not automatically cause the other corresponding devices to operate in that specific Focus Mode state, such that even if the electronic device 600 suppresses notifications while operating in its selected Focus Mode state, the 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. At Figure 6E which the electronic device 600 detects a user input 632 (e.g., a touch input and / or a tap input) corresponding to the selection of the option 630b.

[0223] At Figure 6F which, in response to the 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., to cause the electronic device 600 to enter the Sleep Focus Mode state and / or operate in the Sleep Focus Mode state) or turn off the Sleep Focus Mode state (e.g., to cause the electronic device 600 to exit the Sleep Focus Mode state and / or stop operating in the Sleep Focus Mode state). In Figure 6F option 636a is in the off position, indicating that the electronic device 600 is not operating in the Sleep Focus Mode state (and notifications are not suppressed).

[0224] Option 636b can be selected to initiate a process for identifying one or more people (e.g., one or more contacts) who are permitted 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 permitted to disturb the user when the sleep focus mode state is active, when a message is received from the first contact while 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 haptic notification) as if the sleep focus mode state were not active. However, notifications related to messages from other users 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 permitted to disturb the user when the sleep focus mode state is active (e.g., when the electronic device 600 is operating in the sleep focus mode state).

[0225] Option 636d can be selected to open a user interface in which the user can enable or disable the Focus mode status setting. When the Focus mode status setting is enabled, other users (e.g., other users of the user attempting to contact electronic device 600) can see an indication of when the Sleep Focus mode status for electronic device 600 is active (e.g., an indication that electronic device 600 is operating in the Sleep Focus mode status and / or has suppressed notifications). When the Focus mode status setting is disabled, other users cannot see when electronic device 600 is operating in the Sleep Focus mode status. Option 636e can be selected to display a user interface in which the user can enable or disable the 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 electronic device 600 (e.g., when the Sleep Focus mode status is inactive) are also displayed on the home screen of electronic device 600 when the Sleep Focus mode status is active. When the Home screen notification setting is disabled, notifications that would normally be displayed on the home screen of electronic device 600 are suppressed (e.g., not displayed) when the Sleep Focus mode status is active. Option 636f can be selected to display a user interface in which the user can enable or disable the 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 electronic device 600 (e.g., when the Sleep Focus mode status is inactive) are also displayed on the lock screen of electronic device 600 when the Sleep Focus mode status is active. When the Lock screen notification setting is disabled, notifications that would normally be displayed on the lock screen of electronic device 600 are suppressed (e.g., not displayed) when the Sleep Focus mode status is active.

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

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

[0228] The sleep focus mode user interface 634 also includes an option 636i that displays next sleep schedule information and can be selected to modify the next sleep schedule information (similar to the next sleep schedule information 620f and option 620g in Figure 6C , as well as an option 636j that displays full sleep schedule information and can be selected to modify the full sleep schedule information (similar to option 620h in 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. At Figure 6F , the electronic device 600 detects a user input 638a (e.g., a touch input and / or a tap input) corresponding to the selection of option 636a, a user input 638b (e.g., a touch input and / or a tap input) corresponding to the selection of option 636g, and a user input 638c (e.g., a touch input and / or a tap input) corresponding to the selection of option 636h.

[0229] At Figure 6G , in response to the user inputs 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 a user - specified sleep schedule. 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 a wearable device, such as a smartwatch or other temperature sensor) while the electronic device 600 is operating in the sleep focus mode state.

[0230] At Figure 6HAt this point, 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.

[0231] In Figure 6H this case, the electronic device 600 operates in a sleep focus mode state. For example, the electronic device 600 enters the sleep focus mode state in response to a user input 638a, or in another example, the electronic device 600 automatically enters the sleep focus mode state based on Figure 6G an option 636g in this case being toggled to an on state and in response to a 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 turn off.

[0232] Figure 6H An electronic device 800 is also depicted, which is a smartwatch having a touchscreen display 802, a rotatable and pressable input mechanism 804, and buttons 806. The electronic device 644 displays a lock screen user interface 644, which indicates that the electronic device 800 is locked. The lock screen user interface includes a current time indication 646a and a current date indication 646b. In Figure 6H this case, the electronic device 800 is also operating in a sleep focus mode state, as indicated by an indication 646d. For example, in some embodiments, as a result of an option 630e in Figure 6D being in an 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.

[0233] Figures 6H through 6I An example embodiment 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 stop displaying the lock screen user interface compared to when the electronic device is not operating in the sleep focus mode state.

[0234] In Figure 6HAt, the electronic device 800 detects a user input 648, which is a press (e.g., a depression) of the rotatable and pressable input mechanism 648. At Figure 6H The electronic device 600 receives biometric information corresponding to the user (e.g., a face scan and / or a face image) via an input device 601 (e.g., a camera and / or a depth sensor).

[0235] At Figure 6I In response to the user input 648, the electronic device 800 displays a user interface 650 that instructs the user to rotate the rotatable and pressable 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, since the electronic device 800 is operating in the sleep focus mode state, an additional user input to rotate the input mechanism 804 is required. Additionally, at Figure 6I In response to receiving the biometric information from the user, the electronic device 600 will display an indication 642a as an unlocked lock, indicating that the biometric information from the user has 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, a swipe 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, since the electronic device 600 is operating in the sleep focus mode state, an additional user input is required to stop the display of the lock screen user interface. In some embodiments, from Figure 6I In the state shown, to stop the display of the lock screen user interface 640, the user is first required to press an object 642h and then provide a swipe up input, and / or the user is required to provide two swipe up inputs.

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

[0237] At Figure 6K In response to the user input 652, the electronic device 600 displays a wrist temperature user interface 612. Since the user has enabled body temperature recording, the wrist temperature user interface 612 no longer displays a notification 614e, as in Figure 6BAs shown. However, 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 graph 614d and displays a notification 654 indicating that more body temperature information is needed.

[0238] In Figure 6L several months have passed since Figure 6K and the electronic device 600 has collected a threshold amount of body temperature information from the user (e.g., has collected body temperature information for at least five nights and / or five consecutive nights). Thus, the wrist temperature user interface 612 now displays the user's body temperature data in the data graph 614d and no longer displays the notification 654. In Figure 6L additional options 656a - 656c in the wrist temperature user interface 612 are shown. In some embodiments, the 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 used to collect the user's body temperature information) from which the body temperature information for the user was collected. In Figure 6L the electronic device 600 detects a user input 658a corresponding to the selection of option 614b (e.g., a touch input and / or a tap input), a user input 658b corresponding to the selection of a data point in the data graph 614d (e.g., a touch input and / or a tap input), and a user input 658c corresponding to the selection of option 656b (e.g., a touch input and / or a tap input).

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

[0240] In Figure 6NAt, in response to user input 658a corresponding to the selection of option 614b, electronic device 600 displays one-month user body temperature data within data graph 614d. Similar to Figure 6M As shown in, the user can select any data point within data graph 614d to view additional information about the selected data point.

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

[0242] At Figure 6PAt , in response to user input 666, electronic device 600 displays user interface 668. User interface 668 displays additional information related to the selected body temperature information collection instance. For example, in the depicted embodiment, user interface 668 includes start time information 670b (e.g., the time when the body temperature information collection for this particular collection instance began), end time information 670c (e.g., the time when the body temperature information collection for this particular collection instance ended), and data addition information 670e (e.g., the date and time when electronic device 600 received body temperature information from an external device). User interface 668 also includes source information 670d that identifies the external device that collected the body temperature information and / or the external device from which the body temperature information was received. In some embodiments, electronic device 600 aggregates body temperature information collected by and / or received from multiple external devices. In some embodiments, the wrist temperature user interface 612 displays body temperature information collected by and / or received from multiple external devices. User interface 668 also includes surface temperature information 670f and wrist temperature information 670a. As described above, the wrist temperature user interface 612 displays baseline temperature information and does not display actual temperature measurement results (e.g., the actually measured temperature). However, user interface 668 displays surface temperature information 670f and wrist temperature information 670a, where the surface temperature information indicates the actual temperature measured at the surface of the user's skin, and the wrist temperature information indicates the user's body temperature derived from the surface temperature information 670f.

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

[0244] Figure 7FIG. 0 is a flow diagram illustrating a method for using a computer system to track body temperature information according to some embodiments. Method 700 is performed at a computer system (e.g., 100, 300, 500) (e.g., a wearable device, smart watch, smart phone, tablet computer, and / or a computer system controlling an external display) (e.g., 600, 800) that communicates with the following: 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.

[0245] As described below, method 700 provides an intuitive way to track body temperature information. The method reduces the cognitive burden on the user to track body temperature information, thus creating a more efficient human-machine interface. For battery-powered computing devices, enabling the user to track body temperature information faster and more efficiently saves power and increases the time interval between battery charges.

[0246] A computer system (e.g., 600, 800) receives (702) via one or more input devices (e.g., 601, 602, 802, 804, 806) an 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 a mode and / or state that defines a sleep schedule (such as 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 information related to the user's sleep (e.g., sleep quality) is collected). In response to the input (704), the computer system enters the sleep tracking mode (e.g., enables the sleep tracking mode and / or causes the computer system to operate in sleep tracking). In some embodiments, entering the sleep tracking mode includes initiating a process for collecting user body 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 body temperature information (e.g., the user body temperature information shown in the data chart 614d) (e.g., one or more user body temperature measurements) to be collected via a temperature sensor (e.g., a temperature sensor integrated into the electronic device 800).

[0247] The computer system receives (708) first type of notification data (e.g., a type of notification that is suppressed when in the sleep tracking mode) (in some embodiments, all notifications are suppressed in the sleep tracking mode) (in some embodiments, a second type of notification (e.g., an emergency notification, a wake-up alarm notification) is not suppressed when in the 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 the 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 the sleep tracking mode (e.g., Figures 6H through 6I )(e.g., when the first type of notification data is received, the computer system is in the sleep tracking mode), the computer system abandons (e.g., suppresses) the output of 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 the inactive state to the active state; abandons outputting the audio output; and / or abandons outputting the tactile output).

[0248] After collecting the first set of user body temperature information (716), the computer system displays, via a display generation component (e.g., 602), a body temperature user interface (e.g., 612) that includes a representation of one or more sets of user body temperature information (e.g., the body temperature information in the data chart 614d shown in Figure 6L (e.g., user body temperature information associated with, collected from, and / or collected by the computer system's user), where the one or more sets of user body temperature information include the first set of user body temperature information (e.g., a body temperature user interface that depicts a representation of the user's body temperature over a period of time (e.g., depicts and / or shows the change in the user's body temperature)).

[0249] Automatically collecting the first set of user body temperature information when the device is in sleep tracking mode allows for the collection of user body temperature information with less user input, thus reducing the amount of user input required to perform an operation. Collecting user body temperature information during sleep tracking mode initiated by user input reduces the risk of erroneously collecting body temperature information during non-sleep states (e.g., due to misidentification of the sleep state); doing so can improve the quality of the data and improve the operations performed by the computer system based on the body temperature data attributed to the sleep state, which enhances the system's operability and makes the user-system interface more efficient (e.g., by helping the user provide appropriate input and reducing errors). Additionally, by enabling the user to use the system faster and more effectively, power usage is reduced and the device's battery life is extended.

[0250] In some embodiments, the computer system receives, via one or more input devices, a second input (e.g., a second 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 first silent mode that is different from the sleep tracking mode (e.g., the sleep focus mode state in Figure 6E (e.g., the do not disturb, personal focus mode state, and / or work focus mode state in Figure 6E (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 in some embodiments, a mode and / or state in which information about the user's sleep (e.g., sleep quality) is not collected). In some embodiments, in response to receiving the second input, the computer system enters the first silent mode (enables the first silent mode and / or causes the computer system to operate in the first silent mode) (in some embodiments, without entering the sleep tracking mode) without initiating the process of collecting body temperature information. In some embodiments, the computer system collects body temperature information while forgoing the storage of the body temperature information, and / or collects a second type of body temperature information while forgoing the collection and / or storage of a third type of body temperature information.

[0251] In some embodiments, the computer system receives second notification data of a first type. In some embodiments, in response to receiving the second notification data of the first type: Based on the determination that the computer system is not in a first silent mode (e.g., the do-not-disturb state, personal focus mode state, and / or work focus mode state in Figure 6E is not active and / or not enabled) and the computer system is not in a sleep tracking mode (e.g., Figure 6E the sleep focus mode state in Figure 6E is not active and / or not enabled (e.g., option 636a is not enabled)), 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., off and / or a state where content is not displayed on the display generation component) to an active state (e.g., on and / or a state where content is displayed); outputs an audio output; and / or outputs a haptic output); and based on the determination that the computer system is currently in the first silent mode (e.g.,

[0252] at least one of the do-not-disturb state, personal focus mode state, and / or work focus mode state in Figure 6C (e.g., 620f, 620h) and / or Figure 6F(e.g., 636i, 636j) the third input of the requested sleep schedule (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), wherein for at least the first day (e.g., the first day of the week (e.g., Sunday, Monday, Tuesday, etc.) and / or the 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., the second day of the week and / or the 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 the 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., Figures 6H through 6I the sleep focus mode state in); and based on the determination that the current time does not correspond to the first sleep start time (e.g., the current time is not the first sleep start time), the computer system abandons entering the sleep tracking mode (e.g., maintains the computer system in a non-sleep tracking mode and / or maintains the computer system in a sleep tracking mode). In some embodiments, the sleep schedule defines sleep start times and sleep end times for multiple days. In some embodiments, the sleep start time and / or the sleep end time are the same for two or more of the multiple days. In some embodiments, the sleep start time and / or the sleep end time are different for two or more of the multiple days. In some embodiments, after receiving the third input, and based on 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., transitions the computer system from the sleep tracking mode to a 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 fewer user inputs, thereby reducing the number of user inputs required to perform the operation.

[0253] In some embodiments, causing the collection of the first set of user body temperature information (e.g., the user body temperature information shown in Chart 614d) includes: causing a first external device (e.g., 800) separate from the computer system (e.g., 600) (e.g., a wearable device, a smartwatch, a smartphone, a tablet computer, and / or a computer system controlling an external display) to collect the first set of user body temperature information; and receiving the first set of user body 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 body temperature information when the computer system is in the sleep tracking mode allows the collection of user body temperature information with fewer user inputs, thereby reducing the number of user inputs required to perform the operation.

[0254] In some embodiments, before receiving an input, the computer system displays a body temperature user interface (e.g., 612) via a display generation component, including: based on the determination that a threshold amount of body temperature information has not been collected (e.g., user body temperature information associated with, collected from, and / or collected by the computer system for the user of the computer system) (e.g., Figure 6K )(e.g., the body temperature information collected is less than the threshold number of days and / or the body temperature information collected is less than the threshold number of hours), displaying an indication that a threshold amount of body temperature information has not been collected (e.g., Figure 6K data chart 614d and / or 654 in Figure 6L ); and in some embodiments, foregoing displaying a representation of one or more sets of user body temperature information (e.g., collected from the user and / or collected by the computer system); and based on the determination that a threshold amount of body temperature information has been collected (e.g., Figure 6L ), displaying a representation of one or more sets of user body temperature information (e.g., the body temperature information in data chart 614d in

[0255] ), without displaying an indication that a threshold amount of body temperature information has not been collected (e.g., 654). Displaying an indication that a threshold amount of body temperature information has not been collected provides visual feedback to the user regarding the state of the system (e.g., the system has not collected a threshold amount of body temperature information), thereby providing improved visual feedback to the user. Figure 6L In some embodiments, after displaying a body temperature user interface (e.g., 612) including a representation of one or more sets of user body temperature information (e.g., Figure 6L 612 in Figure 6Qthe user interface 612 of the data graph 672d therein (and in some embodiments, excluding the 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 the data graphs 614d and / or 614 therein (e.g., indicating that the collection of body temperature information is too sporadic and / or infrequent). Displaying an indication that the second set of criteria is not met provides the user with visual feedback regarding the state of the system (e.g., the system has determined that the second set of criteria is not met), thereby providing the user with improved visual feedback.

[0256] In some embodiments, when displaying the body temperature user interface (e.g., 612), the computer system receives a selection input (e.g., 658a) via one or more input devices (e.g., one or more touch inputs, one or more non-touch inputs, and / or one or more gestures). In response to receiving the selection input: Based on the determination that the selection input corresponds to the 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 a representation of one or more sets of user body temperature information corresponding to the first time frame within the body temperature user interface (e.g., in Figure 6L wherein, the user interface 612 displays body temperature information for a weekly time frame, in Figure 6N wherein, the user interface 612 displays body temperature information for a monthly time frame) (e.g., collected during the first time frame and / or during the first duration corresponding to the first time frame option) (and optionally, does not display the representation of user body temperature information collected outside the first time frame and / or outside the first duration corresponding to the first time frame option); and based on the determination that the selection input corresponds to the selection of 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 (e.g., a second duration (e.g., one week, one month, six months, and / or one year)) different from the first time frame, the computer system displays a representation 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 wherein, the user interface 612 displays body temperature information for a weekly time frame, in Figure 6NIn this case, the user interface 612 displays body temperature information for a monthly time frame (e.g., collected during a second time frame and / or during a second duration corresponding to a second time frame option), and optionally, does not display a 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. Providing different optional 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 sets of body temperature information with less user input, thereby reducing the amount of user input required to perform the operation.

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

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

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

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

[0261] 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 body temperature information (e.g., information regarding an external device (e.g., separate from the computer system) used to collect the first set of user body 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 regarding the status of the system (e.g., the system has collected additional information regarding the first set of user body temperature information not included in the body temperature user interface), thereby providing the user with improved visual feedback. Providing the first details user interface in which the user can view additional details regarding the first set of user body temperature information allows the user to perform this operation with less user input.

[0262] 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: Based on the computer system not being in a sleep tracking mode (e.g., option 636a is inactive and / or off) (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 a display generating component to transition from an inactive state (e.g., off and / or a state in which content is not displayed on the display generating 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 haptic output); and Based on the computer system currently being in a sleep tracking mode (e.g., option 636a is active and / or on) (e.g., when the first notification data is received), and the first notification data includes a second type of notification data (e.g., notification data suppressed when the computer system is in the sleep tracking mode, notification data corresponding to one or more messages received from a first subset of external users (e.g., users not identified in the object 636b in Figure 6F ), and / or notification data corresponding to one or more messages received from a first subset of applications (e.g., applications not identified in the object 636c in Figure 6F ), the computer system forgoes outputting (e.g., suppresses) the second notification corresponding to the first notification data (e.g., forgoes displaying the second notification; forgoes causing the display generating component to transition from the inactive state to the active state; forgoes outputting the audio output; and / or forgoes outputting the haptic output). Automatically suppressing notifications related to messages received from other users or applications when the computer system is in the sleep tracking mode allows the user to perform these operations with less user input.

[0263] In some embodiments, in response to receiving the first notification data: Based on the computer system currently being in a sleep tracking mode (e.g., option 636a is active and / or on) and the first notification data includes a third type of notification data different from the second type (e.g., notification data not suppressed when the computer system is in the sleep tracking mode, notification data 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 Figure 6Ffor one or more messages received by the user identified in object 636b therein and / or corresponding to one or more messages received from a second subset of applications different from the first subset (e.g., a subset of pre-approved and / or pre-selected external users) (e.g., in Figure 6F the determination of notification data for one or more messages received by the application identified in object 636c therein, the computer system outputs a second notification corresponding to the first notification data. When the computer system is in the sleep tracking mode, notifications related to messages received from certain unapproved users or applications are automatically suppressed, while notifications related to messages received from pre-approved users or applications are allowed when the computer system is in the sleep tracking mode, allowing the user to perform these operations with less user input.

[0264] In some embodiments, during the sleep tracking mode (e.g., when the computer system is in the sleep tracking mode): based on the determination that the computer system is in the sleep tracking mode (e.g., option 636a is active and / or turned on), the computer system causes a second external device different from the computer system (e.g., 1070) (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., has suppressed one or more types of notifications) (e.g., based on option 636d being active and / or participating). In some embodiments, when the computer system is not in the sleep tracking mode, and based on the determination that the computer system is not in the sleep tracking mode, the computer system refrains from causing and / or does not cause the second external device to display an indication that the computer system is in the sleep tracking mode. Causing the second external device to display an indication that the computer system has suppressed notifications provides visual feedback to the user of the second external device regarding the state of the computer system (e.g., the computer system has suppressed notifications), thereby providing improved visual feedback to the user.

[0265] In some embodiments, the representation of one or more sets of user body temperature information (e.g., the body temperature information shown in data chart 614d) includes: a representation of a third set of user body temperature information (e.g., a third time period during which body temperature information is collected from the user) collected by a second external device separate from the computer system (e.g., a wearable device, a smartwatch, a smartphone, a tablet computer, and / or a computer system controlling an external display); and a representation of a fourth set of user body temperature information different from the second set of user body 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 smartwatch, a smartphone, a tablet computer, and / or a computer system controlling an external display) (e.g., a fourth time period (e.g., a third time period different from the second time period) during which body temperature information is collected from the user) (e.g., Figure 6Lthe data table 614d in and / or Figure 6N the data table 614d in 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 a 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.

[0266] It should be noted that the processes described above with respect to method 700 (e.g., Figure 7 ) also apply to the methods described below in a similar manner. 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.

[0267] Figures 8A through 8K illustrates an exemplary user interface for generating and providing an ovulation day prediction according to some embodiments. In some embodiments, the ovulation day prediction is generated based on user body temperature information. The user interfaces in these figures are used to illustrate the processes described below including Figure 9A and Figure 9B the processes described below of the processes in.

[0268] Figure 8A illustrates an electronic device 600 having a touch-sensitive display 602. Figures 8A through 8C illustrates an example user interface that allows a user to provide information related to and / or associated with menstrual cycle prediction (e.g., health information and / or biometric information), the menstrual cycle prediction including an ovulation day prediction and a conception window prediction. In Figure 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 apply to the user via options 808a-808d. Option 808a can be selected by the user to indicate that the user is pregnant. Option 808b can be selected by the user to indicate that the user is breastfeeding. Option 808c can be selected by the user to indicate that the user is using contraception. Option 808d can be selected by the user to indicate that none of these health factors currently apply to the user, and in Figure 8Ahas been selected by the user. The health factor user interface 807 includes options 808e that can be selected to move to the next user interface (e.g., the next user interface in a series of guided user interfaces and / or the next user interface in a series of setting user interfaces), options 808f that can be selected to skip entering predetermined health factor information, options 808g that can be selected to return to the previous user interface, and options 808h that can be selected to stop the display of the health factor user interface 807. In some embodiments, if the user indicates that one or more predetermined health factors apply to the user during a relevant prediction time period, the electronic device 600 does not generate one or more menstrual cycle predictions (e.g., menstrual period prediction, ovulation day prediction, and / or conception window prediction). At Figure 8A the electronic device 600 detects a user input 810 (e.g., tap input and / or touch input) corresponding to the selection of option 808e.

[0269] At Figure 8B in response to the user input 810, the electronic device 600 displays a user interface 812. The user interface 812 includes option 814a and option 814b. Option 814a can be selected by the user to selectively enable or disable the menstrual period prediction. When option 814a is enabled (e.g., when the 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 the menstrual period prediction is disabled), the electronic device 600 does not generate and / or does not display the menstrual period prediction. Option 814b can be selected by the user to selectively enable or disable the menstrual period notification. When option 814b is enabled (e.g., when the 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 the menstrual period prediction (e.g., the prediction of when the user's next menstrual period will occur). When option 814b is disabled (e.g., when the menstrual period notification is disabled), the electronic device 600 does not generate and / or does not display a notification related to the menstrual period prediction and / or menstrual period data (e.g., a push notification, a lock screen notification, and / or a banner notification). The user interface 812 also includes option 814c that can be selected to display the next user interface (e.g., the next user interface in a series of guided user interfaces and / or the next user interface in a series of setting user interfaces), option 814d that can be selected to display the previous user interface (e.g., the user interface 807), and option 814e that can be selected to stop the display of the user interface 812. At Figure 8B the electronic device 600 detects a user input 816 (e.g., tap input and / or touch input) corresponding to the selection of option 814c.

[0270] At Figure 8C , 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 a 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 occurred, and / or a prediction of when the user's current conception window begins. 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 does not display a notification related to the conception window prediction and / or conception window data. Option 820c can be selected by the user to selectively enable or disable the fertility record. When option 820c is enabled (e.g., when the fertility record is enabled), options are provided to the user (e.g., the electronic device 600 displays options) that allow the user to record ovulation tests and other fertility metrics, and display an indication of the fertility metrics recorded by the user (e.g., within the cycle tracking user interface 828, as described below). When option 820c is disabled (e.g., when the fertility record is disabled), the electronic device 600 does not display and / or does not provide the user with options to record ovulation tests and / or other fertility metrics. Option 820d can be selected by the user to selectively enable or disable the sexual activity record. When option 820d is enabled (e.g., when the sexual activity record is enabled), the electronic device 600 displays to the user and / or provides options that allow the user to record sexual activity information (e.g., allowing the user to identify the date on which the user had sexual activity). When option 820d is disabled (e.g., when the sexual activity record is disabled), the electronic device 600 does not display and / or does not provide the user with options 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 the display of the 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 guided user interfaces and / or the next user interface in a series of settings user interfaces).

[0271] The user interface 818 also includes a notification 822 that indicates that the user can improve cycle prediction, ovulation prediction, and conception window prediction (e.g., such that the electronic device 600 can record and track body temperature information that can be used to improve these predictions) by setting up sleep tracking and wearing their wearable device (e.g., a watch) while sleeping at night. In some embodiments, the 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. The 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 the display of the notification 822. At Figure 8C which point, the electronic device 600 detects a user input 826 (e.g., a tap input and / or a touch input) corresponding to the selection of the option 820g.

[0272] At ​ which point, in response to the user input 826, the electronic device 600 displays the cycle tracking user interface 828. The cycle tracking user interface 828 includes a first region 830 that includes day representations 832a - 832g. Each day representation 832a - 832g represents a single calendar day (e.g., the representation 832d represents Friday, May 6, the representation 832c represents Thursday, May 5, the representation 832e represents Saturday, May 7, etc.). The user is able to navigate within the first region 830 (e.g., by scrolling left or right and / or swiping) to view additional day representations representing past and / or future dates in order to view and / or record menstrual cycle information about a specific date. An indicator 831a points to the representation 832d, indicating that the representation 832d is the currently selected day representation, and an indicator 831b indicates that the representation 832d represents "Today, May 6". Thus, in the case where the representation 832d is currently selected, the user can interact with the options 834a - 834d to record menstrual cycle information for Friday, May 6. If the user swipes right to select the representation 832c (e.g., moves the representation 832c under the indicator 831a), the user can interact with the options 834a - 834d to record menstrual cycle information for Thursday, May 5. The option 834a can be selected to initiate a process for indicating that the user has menstruated on the currently selected date. The option 834b can be selected to initiate a process for recording one or more symptoms for the selected date. The option 834c can be selected to initiate a process for indicating that the user has experienced spotting on the currently selected date. The option 834d can be selected to initiate a process for indicating that one or more predetermined health factors (e.g., pregnancy, use of contraception, lactation, etc.) apply to the user on the selected date.

[0273] Option 834e can be selected to view one or more health-related predictions for the user, including, for example, menstrual cycle predictions (e.g., when the user will have her next menstrual period), conception window predictions (e.g., when the user will have her next conception window and / or when the user's most recent conception window occurred), and ovulation day predictions (e.g., when the user last ovulated and / or predictions of when the user will next ovulate). Such predictions are also shown via the daily representations 832a - 832g in region 830. In ​ , the representations 832a - 832e are shown 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 conception window has occurred and / or will occur on those dates (e.g., in ​ , from Tuesday, May 3 to Saturday, May 7).

[0274] 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 the menstrual cycle (e.g., for identifying one or more dates on which the user had her period).

[0275] 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 region 838a corresponding to the current menstrual cycle (e.g., starting on April 17 and having continued to the current date, May 6), and a second region 838b corresponding to a previous menstrual cycle that occurred from March 19 to April 16. The first region 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 the first day, the second pill represents the second day, etc.). In ​ , the first six representations 835a in region 838a indicate that the user had her period on those first six days (e.g., by displaying small circles at the top of each day representation), and the last six day representations 835b in region 838a indicate that the electronic device 600 has predicted that the user's conception window has occurred during those six days (e.g., based on the user's past menstrual cycle information). Similarly, in region 838b, there are 28 pill-shaped day representations to represent the 28 days in that menstrual cycle (not all of the day representations are shown in ​In, and in some embodiments, the user can slide in region 838b to display additional day representations). Region 838b indicates that during the previous menstrual cycle, the user had their period on the first five days (e.g., based on the small circles shown at the top of those day representations), the user had spotting on the third and fifth days (e.g., based on the small dots at the bottom of the third and fifth day representations), and shows a predicted conception window for days 10 to 16 of the menstrual cycle (based on the single diagonal hatching shown in those day representations), and shows a predicted ovulation day for day 15 of the menstrual cycle (e.g., based on the double diagonal hatching shown on that day representation). In some embodiments, when fertility prediction is not enabled, the cycle tracking user interface 828 does not display the predicted conception window or the predicted ovulation day. In some embodiments, when fertility prediction is not enabled, the cycle tracking user interface 828 displays the fertility prediction. In some embodiments, when fertility prediction is enabled, the cycle tracking user interface 828 does not display the menstrual period prediction and only displays the predicted conception window and the predicted ovulation day.

[0276] As described above, in ​ , the electronic device 600 has generated a predicted conception window for the user's current menstrual cycle (e.g., the day representations 832a - 832e in region 830, and the day representation 835b in region 838a). In the depicted example scenario, ​ the shown predicted conception window represents an initial predicted conception window generated using information related to the user (e.g., based on the menstrual cycle history information for the user) but without using the user's body temperature information. In ​ the shown example, the user has enabled sleep tracking and has enabled body temperature collection and recording, as discussed above with reference to ​ . In ​ , an example scenario is shown where the electronic device 600 uses the user's body temperature information to generate a predicted ovulation day and updates the initial predicted conception window based on that predicted ovulation day. In some embodiments, when sleep tracking and / or body temperature recording is not enabled, the cycle tracking user interface 828 includes a notification similar to ​ the notification 822 in, which notifies the user that the user can improve menstrual cycle predictions (e.g., menstrual period prediction, predicted ovulation day, and / or predicted conception window) by setting sleep tracking, setting body temperature recording, and / or wearing their wearable device every night while sleeping.

[0277] In ​ , the electronic device 600 displays the wrist temperature user interface 612, which was discussed above with reference to ​ . In ​ , the wrist temperature user interface 612 indicates that the user's relative body temperature peaked around May 3. In​ In [description], 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.

[0278] In ​ In [description], 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 flashlight option 842d, and a camera option 842e. In ​ In [description], 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., off state) to an active state (e.g., on 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.

[0279] ​ An electronic device 800 is also depicted, which is a smartwatch having a touch-sensitive display 802, a rotatable and pressable input mechanism 804, and buttons 806. In some embodiments, the electronic device 800 corresponds to the electronic device 600 (e.g., paired with the electronic device 600 and / or corresponding to the same user as the electronic device 600). In response to the electronic device 600 determining that the user is likely to ovulate on May 3 and / or after such determination, the electronic device 800 displays a notification 844 informing the user of the ovulation day prediction. In ​ At [location], the electronic device 600 detects a user input 846 (e.g., touch input and / or tap input) corresponding to a selection of the notification 842f.

[0280] In ​ At [location], in response to the user input 846, the electronic device 600 displays a cycle tracking user interface 828. In ​ In [description], the cycle tracking user interface 828 has been updated based on the ovulation day prediction made by the electronic device 600. In ​ In [description], before the ovulation day prediction, the cycle tracking user interface 828 displays an initial conception window prediction, predicting that the user's conception window will occur between May 1 and May 7 (e.g., day representations 832a - 832e and day representation 835b). However, in ​In, 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 conception window prediction 835c between April 28 and May 4. In some embodiments, the updated conception 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). Accordingly, the day representations 832j, 832i, 832h, and 832b are displayed in a manner (e.g., single-line hatching) indicating the conception window prediction, while the day representations 832c and 832d, which were previously shown with single-line hatching indicating the conception window prediction, are no longer filled with that pattern. The cycle tracking user interface 828 also displays the ovulation day prediction by showing the day representation 832a with double-line hatching and the day representation 835d with double-line hatching. In this way, from ​ , the electronic device 600 changes from displaying an 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.

[0281] In ​ , 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. In ​ , the menstrual cycle representations 850a, 850c, and 850d do not include a conception window prediction or an ovulation day prediction because the user indicates that one or more predetermined health factors (e.g., lactation and / or contraceptive use) apply to the user during those menstrual cycles. However, the menstrual cycle representation 850b does include a conception window prediction and an ovulation day prediction. At ​ , the electronic device 600 detects a user input 852 (e.g., a touch input and / or a tap input) corresponding to the selection of the menstrual cycle representation 850b.

[0282] In ​ , in response to the user input 852, the electronic device 600 displays a cycle details user interface 854. The cycle details user interface 854 displays information related to the menstrual cycle selected in the cycle history user interface 848. In ​ , 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 and a set of day representations 856b representing each day of the menstrual cycle. The day representations 856b include the days on which the user had a menstrual period (e.g., ​ days 1 to 6 in ​on the 3rd, 5th, and 16th days thereof), ovulation day prediction for the menstrual cycle (e.g., ​ on the 14th day thereof), and indication of the conception window prediction for the menstrual cycle (e.g., ​ from the 9th day to the 15th day thereof). The cycle details user interface 854 also displays body temperature information 856c, which indicates the user's body temperature (e.g., relative body temperature) for each day of 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 the menstrual cycle information in the cycle details user interface 854 (e.g., in a PDF file, by email, or in another file format), an option 856f that can be selected to initiate a process for editing the 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.

[0283] ​ Illustrates an alternative implementation of the cycle tracking user interface 828, wherein the cycle tracking user interface 828 includes an option 858 that can be selected to record a positive ovulation prediction kit (OPK) test. ​ Depicts the same scenario described above with reference to ​ . In ​ , the electronic device 600 has generated an initial conception window prediction and displays the initial conception window prediction for May 1st to May 7th. In ​ , when selecting Friday, May 6th (e.g., as in region 830 and indicated by indications 831a, 831b), the electronic device 600 detects a user input 860 corresponding to the selection of the option 858.

[0284] In ​ , in response to the user input 860, the electronic device 600 records a positive OPK test for Friday, May 6th, as indicated by indication 862. In addition, in response to the user input 860, the electronic device 600 marks Saturday, May 7th (day representation 832e) as the predicted ovulation day (a positive OPK test indicates the day before ovulation), and updates the conception window based on the new predicted ovulation day by marking May 2nd to May 8th as the new predicted conception window (e.g., within region 830). In some embodiments, a positive OPK test overrides any conception window prediction or ovulation day prediction generated by the electronic device 600. In some embodiments, even after the electronic device 600 predicts the ovulation day for the user based on the user's body temperature information, a positive OPK test will override the ovulation day prediction made by the electronic device 600.

[0285] ​is a flowchart illustrating a method for using a computer system to generate and provide ovulation day predictions. Method 900 is executed at a computer system (e.g., 100, 300, 500) (e.g., 600, 800) (e.g., a wearable device, smartwatch, smartphone, tablet computer, and / or a computer system controlling an external display) in communication 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) in a computer system (e.g., 100, 300, 500, and / or 600) (e.g., a wearable device, smartwatch, smartphone, 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 900 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0286] As described below, method 900 provides an intuitive way to generate and provide ovulation day predictions. The method reduces the cognitive burden on the user to generate and / or receive ovulation day predictions, thus creating a more effective human-machine interface. For battery-powered computing devices, enabling the user to generate and / or receive ovulation day predictions more quickly and effectively saves power and increases the time interval between two battery charges.

[0287] 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, smartwatch, smartphone, tablet computer, and / or a computer system controlling an external display)) body temperature information corresponding to the 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 the display generation component (e.g., 602, 802), the push notification causing the display generation component to transition from an inactive state (e.g., ​ )(e.g., a closed state and / or a state where the display generation component does not display content) to an active state (e.g., ​(e.g., an on state and / or a state in which the display generation component displays content) and indicates to the user that a predicted ovulation date for the user has been determined (e.g., has been determined by a computer system and / or an external device), wherein the predicted ovulation date is determined based on temperature information corresponding to the user. In some embodiments, after receiving the temperature information corresponding to the user (in some embodiments, in response to receiving the temperature information corresponding to the user), the computer system determines the predicted ovulation date for the user based on the temperature information corresponding to the user (e.g., the predicted ovulation date for the user determined based on the change in the user's temperature over a period of time). In some embodiments, the computer system displays a push notification that indicates to the user that the computer system has determined the predicted ovulation date after determining the predicted ovulation date for the user (in some embodiments, in response to determining the predicted ovulation date for the user). After receiving the temperature information corresponding to the user, automatically displaying a push notification that indicates to the user that the predicted ovulation date for the user has been determined informs the user of the ovulation date prediction with less user input, thereby reducing the amount of user input required to perform the operation. Displaying a push notification that indicates to the user that the predicted ovulation date for the user has been determined provides the user with visual feedback on the state of the system (e.g., the system has determined the predicted ovulation date for the user), thereby providing the user with improved visual feedback.

[0288] In some embodiments, displaying the push notification includes displaying the push notification while maintaining the computer system in a locked state (e.g., the lock screen user interface 840 and / or an indication 842a indicating that the computer system 600 is in ​ the locked state shown therein) (e.g., a state in which one or more features of the computer system and / or one or more sets of content 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 temperature information corresponding to the user, automatically displaying a push notification that indicates to the user that the predicted ovulation date for the user has been determined informs the user of the ovulation date prediction with less user input, thereby reducing the amount of user input required to perform the operation.

[0289] In some embodiments, receiving the temperature information corresponding to the user (e.g., the user temperature information shown in the data graph 614d) includes receiving the temperature information corresponding to the user from a first external device (e.g., 800) separate from (e.g., different from) the computer system (e.g., a wearable device, a smartwatch, a smartphone, a tablet computer, and / or a computer system controlling an external display). After receiving the temperature information corresponding to the user from the external device, automatically displaying a push notification that indicates to the user that the predicted ovulation date for the user has been determined informs the user of the ovulation date prediction with less user input, thereby reducing the amount of user input required to perform the operation.

[0290] 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., built into the computer system (e.g., a first sensor included within a housing corresponding to the computer system, connected to the computer system, and / or separate from the computer system) (e.g., a first sensor built into electronic device 600 and / or built into electronic device 800)); and receiving body temperature information corresponding to a user includes receiving body temperature information corresponding to the user from the first sensor. After receiving body temperature information corresponding to the user from the first sensor, a push notification indicating that a predicted ovulation day for the user has been determined is automatically displayed to inform the user of the ovulation day prediction with less user input, thereby reducing the amount of user input required to perform the operation.

[0291] In some embodiments, when displaying a push notification (e.g., 842f and / or 844) (908): the computer system receives (910) a selection input (e.g., 846) corresponding to the selection of the push notification via one or more input devices (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). 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 a cycle tracking user interface (e.g., 828) that includes (e.g., displays and / or shows) the predicted ovulation day (e.g., ​ the day representation 832a in ​ and / or the day representation 835d in

[0292] In some embodiments, the push notification (e.g., 842f and / or 844) includes (e.g., displays and / or shows) the predicted ovulation day (e.g., ​("May 3" in ). Displaying a push notification that shows the predicted ovulation date allows the user to view the predicted ovulation date with less user input, thereby reducing the amount of user input required to perform the operation. Displaying a push notification that shows the predicted ovulation date provides the user with visual feedback on the status of the system (e.g., the system has determined the predicted ovulation date for the user), thereby providing the user with improved visual feedback.

[0293] In some embodiments, displaying the push notification (e.g., 842f and / or 844) is performed based on a determination that the user has enabled fertility tracking settings (e.g., 820a, 820b, and / or 820c) (e.g., settings that indicate the user has authorized receiving fertility information and / or authorizing the performance of ovulation date prediction). In some embodiments, after receiving the temperature information corresponding to the user, and based on a determination that the user has not enabled fertility tracking settings, the computer system abandons displaying the push notification. After receiving the temperature information corresponding to the user and based on a determination that the user has enabled fertility tracking, a push notification that indicates to the user that the predicted ovulation date for the user has been determined is automatically displayed, informing the user that the ovulation date prediction is ready for the user to view with less user input, thereby reducing the amount of user input required to perform the operation.

[0294] In some embodiments, displaying the push notification (e.g., 842f and / or 844) is performed based on a determination that a threshold amount of temperature information corresponding to the user has been collected (e.g., in ​ a threshold amount of temperature information has been collected, while in ​ and ​ a threshold amount of temperature information has not been collected) (e.g., the temperature information corresponding to the user has been collected for a threshold number of days and / or the temperature information corresponding to the user has been collected a threshold number of times). In some embodiments, after receiving the temperature information corresponding to the user, and based on a determination that a threshold amount of temperature information corresponding to the user has not been collected, the computer system abandons displaying the push notification. After receiving the temperature information corresponding to the user and based on a determination that a threshold amount of temperature information corresponding to the user has been collected, a push notification that indicates to the user that the predicted ovulation date for the user has been determined is automatically displayed, informing the user that the ovulation date prediction is ready for the user to view with less user input, thereby reducing the amount of user input required to perform the operation. Displaying the push notification only when a threshold amount of temperature information has been collected improves the user-device interface by avoiding presenting information that is not applicable to the user and by helping the user provide correct input.

[0295] In some embodiments, displaying the push notification (e.g., 842f and / or 844) is based on a determination that one or more predetermined health factors do not apply to the user (e.g.,​ and / or ​ using the "factor" option 834d) (e.g., the user is not pregnant, the user is not using contraception, and / or the user is not using a first type of contraception). In some embodiments, after receiving temperature information corresponding to the user and based on a determination that at least one of one or more predetermined health factors applies to the user (e.g., the user is pregnant and / or the user is using contraception), the computer system refrains from displaying a push notification. After receiving temperature information corresponding to the user and based on a determination that one or more predetermined health factors do not apply to the user, a push notification indicating that a predicted ovulation day has been determined for the user 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 amount of user input required to perform the operation. Displaying the push notification only when one or more predetermined health factors do not apply to the user improves the user-device interface by avoiding presenting information that does not apply to the user and assisting the user in providing correct input.

[0296] In some embodiments, the computer system receives, via one or more input devices, an 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 a defined sleep schedule (e.g., the sleep schedule shown in 636i, 636j)), where one or more notifications (e.g., a first type of notification) received by the computer system are suppressed and / or where 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., ​ the sleep focus mode state in), where receiving temperature information corresponding to the user is performed while the computer system is in the sleep tracking mode. In some embodiments, receiving temperature information corresponding to the user is performed based on a determination that the computer system is in the sleep tracking mode. Automatically collecting temperature information in response to the computer system entering the sleep tracking mode allows for collecting temperature information with less user input, thereby reducing the amount of user input required to perform the operation.

[0297] In some embodiments, a computer system receives notification data of a first type (e.g., a type of notification that is suppressed when in a sleep tracking mode) (in some embodiments, all notifications are suppressed in the sleep tracking mode) (in some embodiments, a second type of notification (e.g., an emergency notification, a wake-up alarm notification) is not suppressed when in the sleep tracking mode). In response to receiving the notification data of the first type: Based on the computer system not being in the sleep tracking mode (e.g., option 636a is in an inactive state and / or a closed 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 a display generation component to transition from an inactive state (e.g., off and / or a state where content is not displayed on the display generation component) to an active state (e.g., on and / or a state where content is displayed); outputs an audio output; and / or outputs a haptic output); and Based on a determination that the computer system is in the sleep tracking mode (e.g., ​ the electronic device 600 in) (e.g., option 636a is in an active state and / or an on state) (e.g., when the notification data of the first type is received), the computer system forgoes outputting (e.g., suppressing) the first notification corresponding to the notification data of the first type (e.g., forgoes displaying the first notification; forgoes causing the display generation component to transition from an inactive state to an active state; forgoes outputting an audio output; and / or forgoes outputting a haptic output). Automatically suppressing notifications 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, in response to receiving the notification data of the first type: Based on a determination that the computer system is not in the sleep tracking mode (e.g., option 636a is in an inactive state and / or a closed state) (e.g., when the notification data of the first type is received), the computer system causes a second external device (e.g., 800) (e.g., a wearable device, a smartwatch, a smartphone, a tablet computer, and / or a computer system that controls an external display) separate from (e.g., different from) the computer system to display a second notification corresponding to the notification data of the first type (e.g., causes the external device 800 to display and / or output the notification); and Based on a determination that the computer system is in the sleep tracking mode (e.g., option 636a is in an active state and / or an on state) (e.g., when the notification data of the first type is received), the computer system forgoes causing the second external device to display the second notification corresponding to the notification data of the first type (e.g., at ​In this case, 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.

[0299] In some embodiments, receiving temperature information corresponding to the user (e.g., the temperature information shown in data graph 614d) includes receiving temperature information corresponding to the user from a third external device (e.g., 800) (e.g., a wearable device, a smartwatch, a smartphone, a tablet computer, and / or a computer system controlling an external display) that is separate from (e.g., different from) the computer system. After receiving the temperature information corresponding to the user from the external device, a push notification indicating that a predicted ovulation day for the user has been determined is automatically displayed to inform the user of the predicted ovulation day with less user input, thereby reducing the amount of user input required to perform the operation.

[0300] In some embodiments, the computer system receives notification data of a second type (e.g., the 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., an emergency notification, a wake-up alarm notification) is not suppressed when in sleep tracking mode). In response to receiving the notification data of the second type: Based on the determination that the computer system (e.g., 600) is not in sleep tracking mode (e.g., option 636a is inactive and / or off) (e.g., when the notification data of the second type is received), 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 the third notification; causes a display generation component corresponding to and / or communicating with the third external device to transition from an inactive state (e.g., off and / or a state where the content is not displayed on the display generation component) to an active state (e.g., on and / or a state where the content is displayed); causes the third external device to output an audio output; and / or causes the third external device to output a tactile output corresponding to the notification data of the third type); and Based on the determination that the computer system is in sleep tracking mode (e.g., option 636a is active and / or on) (e.g., when the notification data of the second type is received), the computer system (e.g., 600) forgoes causing the third external device (e.g., 800) to output a third notification corresponding to the notification data of the second type (e.g., when notifications are suppressed on the electronic device 600, notifications are 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 amount of user input required to perform the operation.

[0301] In some embodiments, the 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 smartwatch, a smartphone, a tablet computer, and / or a computer system controlling an external display) second body temperature information corresponding to the user (e.g., body temperature measurements collected from the user over 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): Based on the determination that the user has not recorded (e.g., input and / or provided) an ovulation predictor kit test result during a predefined time period (e.g., ​(e.g., within a threshold amount of time (e.g., in the last two weeks, in the last three weeks, in the last four weeks)) in which no OPK test result is recorded, the computer system displays, via a display generation component (e.g., 602), a second push notification (e.g., 842f and / or 844) 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, where the second predicted ovulation day is determined based on second body temperature information corresponding to the user; and based on the determination that the user has recorded an ovulation predictor kit test result (e.g., the user records a positive OPK test) during a predefined period, the computer system abandons displaying the second push notification (e.g., does not generate a push notification indicating the predicted ovulation day after the user records a positive OPK test). After receiving the second body temperature information corresponding to the user, automatically displaying the second push notification that indicates to the user that a second predicted ovulation day for the user has been determined informs the user that the ovulation day prediction is ready for them to view with less user input, thus reducing the amount of user input required to perform the operation. If the user has recorded an ovulation predictor kit test result during a predefined period, abandoning the display of the second push notification improves the user-device interface by avoiding presenting information that is not applicable to the user and by helping the user provide correct input. ​ a positive OPK test in) the determination, the computer system abandons displaying the second push notification (e.g., does not generate a push notification indicating the predicted ovulation day after the user records ​ a positive OPK test). After receiving the second body temperature information corresponding to the user, automatically displaying the second push notification that indicates to the user that a second predicted ovulation day for the user has been determined informs the user that the ovulation day prediction is ready for them to view with less user input, thus reducing the amount of user input required to perform the operation. If the user has recorded an ovulation predictor kit test result during a predefined period, abandoning the display of the second push notification improves the user-device interface by avoiding presenting information that is not applicable to the user and by helping the user provide correct input.

[0302] It should be noted that the details of the processes described above with respect to method 900 (e.g., ​ ) 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.

[0303] ​is a flowchart illustrating a method for using a computer system to generate and provide ovulation day predictions 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, smartwatch, smartphone, tablet computer, and / or a computer system controlling an external display) in communication 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) in a computer system (e.g., 100, 300, 500, and / or 600) (e.g., a wearable device, smartwatch, smartphone, 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 950 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0304] As described below, method 950 provides an intuitive way to generate and provide ovulation day predictions. The method reduces the cognitive burden on the user to generate and / or receive ovulation day predictions, thus creating a more effective human-machine interface. For battery-powered computing devices, enabling the user to generate and / or receive ovulation day predictions more quickly and effectively saves power and increases the time interval between two battery charges.

[0305] 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 the user) via a display generation component (e.g., 602) at a first time, including displaying a first conception window prediction for the user (e.g., ​ 835b in and / or the day representation 832a - 832e) (e.g., one or more days when the likelihood of the user getting pregnant during her cycle increases and / or a prediction of one or more dates (e.g., the date when the user will release an egg from the ovary and a prediction of a predetermined time period before that date (e.g., five dates before that date)) (e.g., a conception window prediction 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, smartwatch, smartphone, tablet computer, and / or a computer system controlling an external display)) body temperature information corresponding to the user (e.g., ​The body temperature information shown in the data graph 614d therein (e.g., body temperature measurement results 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) (956), the computer system determines (958) the predicted ovulation date for the user (e.g., notifications 842f and / or 844) (e.g., the predicted ovulation date of the user determined based on the change in the user's body temperature over a period of time) at a second time after the first time. The computer system displays (960) an updated cycle tracking user interface (e.g., ​ 828 therein) (e.g., an updated and / or modified version of the cycle tracking user interface (e.g., updated and / or modified based on the body temperature information and / or based on the user's predicted ovulation date)), including simultaneously displaying: a representation of the predicted ovulation date for the user (e.g., 832a, 835d) (e.g., a graphical object indicating the predicted ovulation date for the user); and an updated conception window prediction for the user (e.g., day representations 832j, 832i, 832h, 832b, and / or 835c), which is different from the first conception window prediction for the user (e.g., an updated, revised, and / or modified conception window prediction (e.g., updated, revised, and / or modified based on the user's body temperature information and / or predicted ovulation date)). In some embodiments, the first conception window prediction is determined based on a set of information that does not include the body temperature information corresponding to the user and / or does not include any body temperature information corresponding to the user (e.g., the first conception window prediction is determined based on the historical menstrual cycle information corresponding to the user). In some embodiments, the predicted ovulation date for the user is determined by an external device based on the body temperature information corresponding to the user and transmitted to and received by the computer system. Automatically updating the cycle tracking user interface with the updated conception window prediction after receiving the body temperature information corresponding to the user allows the user to view the updated conception window prediction information with less user input, thereby reducing the amount of user input required to perform the operation. Automatically updating the cycle tracking user interface with the updated conception window prediction after receiving the body temperature information corresponding to the user provides the user with visual feedback on the state of the system (e.g., the system has determined the predicted ovulation date for the user and / or has determined the updated conception window prediction for the user), thereby providing the user with improved visual feedback.

[0306] In some embodiments, receiving body temperature information corresponding to a 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, smartwatch, smartphone, tablet computer, and / or a computer system that controls an external display). Automatically updating the cycle tracking user interface with an updated conception window prediction after receiving the body temperature information corresponding to the user allows the user to view the updated conception window prediction information with less user input, thereby reducing the amount of user input required to perform an operation.

[0307] In some embodiments, the computer system communicates with a first sensor (e.g., a sensor built into electronic device 600 and / or 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., contained within a housing corresponding to the computer system, connected to the computer system, and / or separate 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 conception window prediction after receiving the body temperature information corresponding to the user allows the user to view the updated conception window prediction information with less user input, thereby reducing the amount of user input required to perform an operation.

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

[0309] 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 conception 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 conception window prediction is displayed in the second color) (in some embodiments, the updated conception window prediction does not include the first color). Displaying the representation of the predicted ovulation day in the first color and the updated conception window prediction in a second color different from the first color allows the user to visually distinguish the predicted ovulation day from the conception window prediction without additional user input.

[0310] 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 a third time, including: a determination (e.g., at the fourth time) that fertility tracking settings (e.g., 820a, 820b, and / or 820c) are enabled (e.g., settings indicating that the user authorizes receiving fertility information and / or authorizing ovulation day prediction), and displaying (e.g., within the cycle tracking user interface) a second conception window prediction for the user (e.g., day representations 832a, 832b, 832c, 832d, 832e, 835b, and / or 835c) (e.g., a second conception window prediction different from or the same as the first conception window prediction and / or the updated conception window prediction); and a determination that the fertility tracking settings are not enabled (e.g., at the fourth time), and displaying (e.g., within the cycle tracking user interface) a prediction of the user's menstrual period (e.g., 835a) (e.g., a prediction of one or more days when the user has an increased likelihood of menstruating) without displaying the second conception window prediction for the user (in some embodiments, without displaying any conception window prediction for the user). Displaying the conception window prediction for the user when the fertility tracking settings are enabled and displaying the prediction of the user's menstrual period when the fertility tracking settings are not enabled improves the user-device interface by avoiding presenting information that is irrelevant to and / or not of interest to the user.

[0311] In some embodiments, a computer system receives second body temperature information corresponding to a user (e.g., the body temperature information shown in data graph 614d) (e.g., 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, via a display generation component, a cycle tracking user interface (e.g., 828), including: a determination that fertility tracking settings (e.g., 820a, 820b, and / or 820c) are enabled (e.g., settings indicating that the user authorizes the receipt of fertility information and / or authorizes the execution of ovulation day prediction), a display (e.g., within the cycle tracking user interface) of a representation of a second predicted ovulation day for the user (e.g., 832a, 835d), wherein the second predicted ovulation day is determined based on the second body temperature information; and a determination that the fertility tracking settings are not enabled, and a representation of the second predicted ovulation day for the user is not displayed. Displaying the predicted ovulation day for the user when the fertility tracking settings are enabled and not displaying the predicted ovulation day when the fertility tracking settings are not enabled improves the user-device interface by avoiding presenting information that is not relevant to and / or not of interest to the user.

[0312] In some embodiments, a computer system receives third body temperature information corresponding to a user (e.g., the body temperature information shown in data graph 614d) (e.g., 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: based on a determination that one or more predetermined health factors (e.g., ​ and / or "factor" option 834d) do not apply to the user (e.g., the user is not pregnant, the user is not using contraception, and / or the user is not using a first type of contraception) (e.g., at the time of receiving the third body temperature information and / or within a defined time after receiving the third body temperature information corresponding to the user), the computer system determines a third predicted ovulation day for the user (e.g., 842f, 844, 832a, and / or 835d) (and optionally, displays a representation and / or indication of the third predicted ovulation day) based on the third body temperature information; and based on a determination that at least one of the one or more predetermined health factors applies to the user (e.g., the user is pregnant and / or the user is using contraception) (e.g., at the time of receiving the third body temperature information and / or at a defined time after receiving the third body temperature information corresponding to the user), the computer system does not determine a predicted ovulation day for the user based on the third body temperature information. Automatically determining the predicted ovulation day for the user based on a determination that one or more predetermined health factors do not apply to the user reduces the amount of user input required to perform the operation. Further, if one or more predetermined health factors apply to the user, not performing the ovulation day prediction for the user improves the user-device interface by avoiding presenting information that does not apply to the user.

[0313] In some embodiments, the computer system receives fourth body temperature information corresponding to a user (e.g., the body temperature information shown in data graph 614d) (e.g., fourth body temperature information that is different from or the same as the first, second, and / or 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 has been collected (e.g., user body temperature information associated with, collected from, and / or collected by the computer system for the user of the computer system) (e.g., body temperature information for more than a threshold number of days has been collected and / or body temperature information for more than a threshold number of hours has been collected), the computer system determines a fourth predicted ovulation date 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 date); 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 date for the user based on the fourth body temperature information. Automatically determining a predicted ovulation date for the user based on the determination that a threshold amount of body temperature information has been collected reduces the amount of user input required to perform the operation. Additionally, if a threshold amount of body temperature information has not been collected, abandoning performing an ovulation date prediction for the user improves the user-device interface by avoiding presenting information that is not applicable to the user and / or inaccurate information.

[0314] In some embodiments, the computer system receives, via one or more input devices, an input 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 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) (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., ​ the sleep focus mode state in), in which: While the computer system is in the sleep tracking mode, it performs receiving body temperature information corresponding to the user (in some embodiments, receiving body temperature information corresponding to the user is performed based on the 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 for collecting body temperature information with less user input, thus reducing the amount of user input required to perform the operation.

[0315] In some embodiments, a computer system receives notification data of a first type (e.g., a type of notification that is suppressed when in a sleep tracking mode) (in some embodiments, all notifications are suppressed in the sleep tracking mode) (in some embodiments, a second type of notification (e.g., an emergency notification, a wake-up alarm notification) is not suppressed when in the sleep tracking mode). In response to receiving the notification data of the first type: Based on the computer system not being in the sleep tracking mode (e.g., option 636a is inactive and / or off) (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 a display generating component to transition from an inactive state (e.g., off and / or a state in which content is not displayed on the display generating 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 the sleep tracking mode (e.g., option 636a is active and / or on) (e.g., when the notification data of the first type is received), the computer system forgoes outputting (e.g., suppresses) the first notification corresponding to the notification data of the first type (e.g., forgoes displaying the first notification; forgoes causing the display generating component to transition from the inactive state to the active state; forgoes outputting the audio output; and / or forgoes outputting the tactile output). Automatically suppressing notifications 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.

[0316] 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) corresponding to a request to enter a sleep tracking mode (e.g., where one or more notifications (e.g., a first type of notification) received by the computer system are suppressed and / or where user sleep information (e.g., sleep quality information) is collected) on a second external device (e.g., 800) separate from the computer system (e.g., a wearable device, smartwatch, smartphone, tablet computer, and / or a computer system that controls an external display), the computer system enters the sleep tracking mode (e.g., the user can provide one or more user inputs on the electronic device 800 to cause the electronic device 600 to enter a sleep focused mode state), where: receiving body temperature information corresponding to the user includes receiving body temperature information corresponding to the user from the second external device; and while 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 the sleep tracking mode allows for the collection of body temperature information with fewer user inputs, thereby reducing the number of user inputs required to perform the operation.

[0317] In some embodiments, the computer system receives notification data of a second type (e.g., the 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., an emergency notification, a wake-up alarm notification) is not suppressed when in sleep tracking mode). In response to receiving the notification data of the second type: Based on the determination that the computer system is not in sleep tracking mode (e.g., when the notification data of the second type is received), the computer system (e.g., 600) causes a second external device (e.g., 800) to output a 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., off and / or a state where content is not displayed on the display generation component) to an active state (e.g., on and / or a state where 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 notification data of the second type); and Based on the determination that the computer system (e.g., 600) is in sleep tracking mode (e.g., when the notification data of the second type 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 notification data of the second type. Automatically suppressing notifications on the second 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 amount of user input required to perform the operation.

[0318] In some embodiments, after tracking a user interface (e.g., 828 in ​ during a display update cycle, the computer system receives (e.g., via one or more user inputs, from an application, and / or from an external device) OPK (e.g., ovulation prediction kit) test result information corresponding to the user (e.g., ​ user input 860 in that indicates a positive OPK test on Friday, May 6). 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 date for the user based on the OPK test result information (e.g., in ​ the electronic device 600 has determined that the predicted ovulation date for the user is Saturday, May 7 based on user input 860). After determining the updated predicted ovulation date for the user, the computer system displays a second updated cycle tracking user interface via a display generation component (e.g., ​828) (e.g., an updated, revised, and / or modified version of the cycle tracking user interface; and / or an updated version of the updated cycle tracking user interface (e.g., updated and / or modified based on ovulation predictor kit test result information), including: an updated representation of the predicted ovulation day for the user (e.g., ​ 832e) (in some embodiments, the electronic device 600 displays a first predicted ovulation day (e.g., ​ 832a) in ​ The cycle tracking user interface 828 in ​ 832e) in ​ The cycle tracking user interface 828) (e.g., a graphical object indicating the updated predicted ovulation day) (optionally, without displaying the representation of the predicted ovulation day for the user). In some embodiments, displaying the second updated cycle tracking user interface further includes displaying (e.g., simultaneously with the representation of the updated predicted ovulation day for the user) a second updated conception window prediction for the user, where the second updated conception window prediction is determined based on the updated predicted ovulation day for the user. Automatically determining the 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 amount of user input required to perform the operation.

[0319] In some embodiments, displaying the second updated cycle tracking user interface (e.g., ​ 828) in ​ also includes: displaying a second updated conception window prediction for the user (e.g., 832a, 832b, 832c, 832d, 832f, and / or the conception window prediction in region 838a in

[0320] In some embodiments, the representation of the predicted ovulation day for the user (e.g., ​ 832a) in​ 832e) in [the above] is displayed together with a 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 amount of user input required to perform the operation.

[0321] It should be noted that the details of the processes described above with respect to method 950 (e.g., ​ ) also apply to the methods described above and / or below in a similar manner. 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 1,100. For the sake of brevity, these details are not repeated below.

[0322] ​ Illustrates an exemplary user interface 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 ​ the processes in [the above].

[0323] ​ Illustrates an electronic device 600 having a touch-sensitive display 602. At ​ , the electronic device 600 displays the cycle tracking user interface 828 discussed above with reference to ​ . In ​ , the current date is June 6, and in the cycle tracking user interface 828, the day representing the current date is selected as day 1001a (e.g., as indicated by indicators 831a, 831b).

[0324] ​ Also illustrates an electronic device 800, which is a smartwatch having a touch-sensitive display 802, a rotatable and pressable input mechanism 804, and buttons 806. In the depicted embodiment, the electronic device 800 corresponds to the electronic device 600 (e.g., paired with the electronic device 600 and / or corresponding to the electronic device 800 of the same user as the electronic device 600). ​ Illustrates the electronic device 600 and the electronic device 800 displaying substantially the same user interface to demonstrate that in certain embodiments, a user can use the electronic device 600 or the electronic device 800 to record and / or input menstrual information.

[0325] In ​In [description], the electronic device 800 displays a cycle tracking user interface 1000 that is substantially the same as the cycle tracking user interface 828. The cycle tracking user interface 1000 includes a region 1002 with multiple day representations (similar to region 830 in the cycle tracking user interface 828), option 1004a (corresponding to option 832a), option 1004b (corresponding to option 834b), and option 1004c (corresponding to option 834c). In ​ In [description], the day representation 1001b representing the current day is selected within the cycle tracking user interface 1000. In ​ In [description], 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, and this user input indicates a user request to record menstrual information for the selected day. Additionally, 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.

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

[0327] 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., colic, mood changes, lower back pain, pain, flatulence, constipation, headache). At Figure 10C In, on both electronic device 600 and electronic device 800, the user selects five symptoms (colic, mood changes, pain, flatulence, and headache (the last two symptoms are not visible on electronic device 600, as depicted in Figure 10C ). After the user has selected their symptoms, electronic device 600 detects user input 1026a corresponding to the selection of option 1020f (e.g., a touch input and / or a tap input), and electronic device 800 detects user input 1026b corresponding to the selection of option 1024h (e.g., a touch input and / or a tap input).

[0328] At Figure 10D , 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 petechiae, and user interface 1032 includes corresponding option 1034a. At Figure 10D , the user is not experiencing petechiae and does not select option 1030a or option 1034a. At Figure 10D , electronic device 600 detects user input 1036a corresponding to option 1030c (e.g., a touch input and / or a tap input), and electronic device 800 detects user input 1036b corresponding to option 1034c (e.g., a touch input and / or a tap input).

[0329] At Figure 10E , in response to user input 1036a, electronic device 600 records the menstrual information entered by the user and displays the cycle tracking user interface 828. At Figure 10EIn, the cycle tracking user interface 828 has been updated based on Figures 10B to 10D the menstrual information input by the user in. For example, the day representation 1001a is now shown as having a menstrual indication (e.g., a hash circle at the top of the day representation 1001a) indicating that the user has recorded menstruation for that day, option 834a is shown as having "less menstrual flow", 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 input by the user and displays the cycle tracking user interface 1000, which has also been updated based on the menstrual information input by the user in the same manner as described above with reference to the cycle tracking user interface 828.

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

[0331] In Figure 10F response to user input 1036a, the electronic device 600 displays the cycle tracking user interface 828, which is almost the same as the cycle tracking user interface 828 described in Figure 10E . However, in Figure 10F the electronic device 600 has identified a potential health problem of the user based on the menstrual cycle information input by the user in Figures 10B to 10D . Therefore, in Figure 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 underlying 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.

[0332] In Figure 10FIn [case], the electronic device 800 does not display a notification of a potential health issue. In some embodiments, the electronic device 600 displays a notification 1038a indicating a potential health issue, 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 issue. In some embodiments, when the user ignores the notification 1038a and / or does not interact with the notification for a period of time, and new menstrual cycle information input by the user (e.g., modifying previously input menstrual cycle information and / or inputting new menstrual cycle information in the coming days) eliminates the potential health issue identified by the electronic device 600, the electronic device 600 stops displaying the notification 1038a within the cycle tracking user interface 828. In Figure 10F At [this point], the electronic device 600 detects a user input 1040 corresponding to the selection of the option 1038b (e.g., a touch input and / or a tap input).

[0333] In Figure 10G At [this point], in response to the user input 1040, the electronic device 600 displays a user interface 1042. The user interface 1042 displays menstrual cycle information 1044a, which includes the basic menstrual cycle information that caused the electronic device 600 to detect a potential health issue. In various embodiments, the menstrual cycle information 1044a shown in the user interface 1042 varies based on the potential health issue 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 that led to the identification of the potential health issue, and if the spotting frequency of the user is determined to be problematic, the menstrual cycle information 1044a shows the dates on which the user recorded 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 the option 1044b), or revise and / or modify the menstrual cycle information 1044a (e.g., by selecting the option 1044c). The user interface 1042 also includes an option 1044d that can be selected to stop the display of the user interface 1042 without confirming or modifying the menstrual cycle information 1044a (and, for example, return to the cycle tracking user interface 828). In Figure 10G At [this point], the electronic device 600 detects a user input 1046 corresponding to the selection of the option 1044d (e.g., a touch input and / or a tap input).

[0334] In Figure 10H At [this point], the electronic device 600 displays the health summary user interface 604 discussed above with reference to Figures 6A to 6Q In some embodiments, when a potential health issue for the user is determined based on the user-recorded menstrual cycle information, a notification of the potential health issue is also displayed in the health summary user interface 604. Thus, inFigure 10H In, 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 the display of the notification 1048a, and an option 1048b that can be selected to display the user interface 1042. In Figure 10H In, the user does not take any action with respect to the notification 1048a (e.g., the user ignores the notification 1048a). In some embodiments, when the user ignores the notification 1048a and / or does not interact with the notification for a period of time, and new menstrual cycle information entered by the user (e.g., modifying previously entered menstrual cycle information and / or entering new menstrual cycle information in the coming days) eliminates a potential health problem identified by the electronic device 600, the electronic device 600 stops the display of the notification 1048c within the health summary user interface 604.

[0335] In Figure 10I In, the electronic device 600 is in an inactive and locked state and does not display content on the display 602. In Figure 10J At, the electronic device 600 receives and / or generates information related to a push notification indicating a potential health problem for the user. In Figure 10J At, 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 entered by the user. In some embodiments, the push notification 1052 causes the display 602 to transition from an inactive state (e.g., Figure 10I ) to an active state (e.g., Figure 10J ). In some embodiments, the push notification 1052 is generated based on the determination that the user has not confirmed or otherwise eliminated the identification of a potential health problem for the user (e.g., based on the determination that there remains an unconfirmed and / or uncleared potential health problem identified for the user). In some embodiments, after the electronic device 600 generates and / or displays the push notification 1052, the electronic device 600 does not display and / or present another push notification for the same unconfirmed potential health problem to the user within a threshold duration (e.g., one month and / or sixty days). In Figure 10J At, the electronic device 600 detects a user input 1054 (e.g., a touch input and / or a tap input) corresponding to the selection of the push notification 1052.

[0336] In Figure 10K At, in response to the user input 1054, the electronic device 600 displays the user interface 1042, which is described above with reference to Figure 10G . In Figure 10KIn [description], the electronic device 600 detects a user input 1056 (e.g., a touch input and / or a tap input) corresponding to the selection of option 1044b, thereby instructing the user to confirm the accuracy of the menstrual cycle information 1044a.

[0337] At Figure 10L , in response to the 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 the criteria for determining the potential health problem. At Figure 10L , the electronic device 600 has determined that within the past 180 days, the user has had two cycles that lasted longer than 10 days, and thus the user may have an extended menstrual period that the user should discuss with a doctor. The user interface 1058 includes an instruction 1060b instructing 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 the 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 can be used by the electronic device 600). The user interface 1058 also includes an option 1060d that can be selected to stop the display of the user interface 1058, and an option 1060e that can be selected to return to the user interface 1042.

[0338] Figure 10L The potential health problem of "extended cycle" is shown, and the indication 1060a shows the criteria for this health problem. However, in other scenarios, the electronic device 1058 can detect other health problems, and the indication 1060a will display different information. For example, in one embodiment, the potential health problem is an irregular menstrual cycle, and the criteria for determining an irregular menstrual cycle include determining that the difference between the maximum menstrual cycle length and the minimum menstrual cycle length of the user within a predetermined time period is greater than a threshold (e.g., for the most recent two non-overlapping 90-day windows, the difference is greater than or equal to 17 days). In another example, the potential health problem is an infrequent menstrual cycle, and the criteria for determining this infrequent menstrual cycle include determining that the recorded menstrual cycle information includes a number of recorded menstrual periods less than a threshold during a predetermined time period (e.g., less than two recorded menstrual periods in the most recent two non-overlapping 90-day windows). In another example, the potential 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 spotting instances within a predefined time period (e.g., one or more days of spotting recorded non-adjacent to a menstrual period in the most recent two non-overlapping 90-day windows).

[0339] In some embodiments, if the user selects option 1044c in Figure 10K instead of option 1044b and modifies the basic menstrual cycle information in a manner that eliminates potential health issues, the electronic device 600 displays an indication that the potential health issue does not apply 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 issue for the user, the electronic device 600 displays the user interface 1058.

[0340] In some embodiments, when the user confirms a potential health issue (e.g., by confirming the basic menstrual cycle information as shown in Figures 10K to 10L ), the potential health issue is displayed in the cycle history user interface 848 ( Figure 8H ) and / or the 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. Additionally, 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 (similar to option 1060c) that can be selected to export a 12-month menstrual cycle history. 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.

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

[0342] In some embodiments, if the user indicates that one or more predefined health factors (e.g., using contraception and / or being pregnant) apply to the user and / or have applied to the user within a threshold duration (e.g., within the most recent 12 weeks), notifications of potential health issues (e.g., notification 1038a and / or push notification 1052) are not generated and / or not displayed.

[0343] Figure 10M An electronic device 1070 having a touch-sensitive display 1072 is depicted. In Figure 10MIn this case, the electronic device 1070 displays a shared user interface 1074. The electronic device 1070 corresponds to a user different from the electronic device 600. In the depicted example scenario, the electronic device 600 corresponds to a user named Jane Appleseed, and the electronic device 1070 corresponds to a user named Sarah. Jane Appleseed has selected to share menstrual cycle information with Sarah. Thus, in Figure 10M the shared user interface 1074 includes an object 1076a that indicates that Sarah can view menstrual cycle information corresponding to the user Jane Appleseed. In addition, the shared user interface 1074 includes objects 1076b and 1076c that indicate that the user Sarah is sharing menstrual cycle information with the user "Mom" and is also sharing menstrual cycle information with Jane Appleseed. The object 1076a indicates the existence of one or more reminders corresponding to the user Jane Appleseed (e.g., based on the determination that one or more potential health issues have been identified for the user Jane Appleseed based on the menstrual cycle information corresponding to the user Jane Appleseed). In Figure 10M at this point, the electronic device 1070 detects a user input 1078 (e.g., a touch input and / or a tap input) corresponding to the selection of the object 1076a.

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

[0345] The user interface 1080 also includes an option 1082g that can be selected to stop the display of the indication 1082e, and an option 1082f that can be selected to display additional details regarding the potential health issue identified for Jane Appleseed. The 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 the user Jane Appleseed (e.g., display a text message user interface). Option 1082b can be selected to initiate a process for calling the user Jane Appleseed (e.g., display a phone call user interface). Option 1082c can be selected to initiate a process for video calling the user Jane Appleseed (e.g., display a video call user interface). Option 1082d can be selected to display the contact information of the user Jane Appleseed. Option 1082h displays ovulation prediction information for the user Jane Appleseed. Option 1082i can be selected to return to the user interface 1074.

[0346] Figure 11 is a flowchart illustrating a method for using a computer system to generate and provide health - related notifications according to some embodiments. The method 1100 is executed at a computer system (e.g., 100, 300, 500) (e.g., 600 and / or 800) (e.g., a wearable device, a smartwatch, a smartphone, 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, 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). Some operations in the method 1100 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0347] As described below, method 1100 provides an intuitive way to generate and provide health-related notifications. The method reduces the cognitive burden on the user to generate and / or receive health-related notifications, thereby creating a more effective human-machine interface. For battery-powered computing devices, enabling the user to generate and / or receive health-related notifications more quickly and effectively saves power and increases the time interval between two battery charges.

[0348] A computer system (e.g., 600, 800) receives (1102) menstrual cycle information (e.g., information identifying one or more dates during which the user is menstruating; and / or information identifying one or more dates during which the user exhibits spotting) (e.g., input by the 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., the menstrual cycle information received in Figures 10A to 10D ). Based on a determination (1104) that the menstrual cycle information meets a first set of criteria, the computer system displays (1106) a push notification (e.g., 1052) via a display generation component (e.g., a notification that causes the display generation component to transition from an inactive state (e.g., a closed state and / or a state in which the display generation component does not display content) to an active state (e.g., an on state and / or a state in which the display generation component displays co...

Claims

1. A method, the method comprising: At a computer system in communication with a display generation 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 a first type of notification data; In response to receiving the first type of notification data: Based on determining that the computer system is not in the sleep tracking mode, Outputting a first notification corresponding to the first type of notification data; And Based on determining that the computer system is currently in the sleep tracking mode, foregoing outputting the first notification corresponding to the first type of notification data; After causing the first set of user body temperature information to be collected, displaying, via the display generation component, a body temperature user interface including a representation of one or more sets of user body temperature information, the one or more sets of user body temperature information including the first set of user body temperature information; And Displaying, via the display generation component, a first detailed user interface corresponding to the first set of user body temperature information, wherein the first detailed user interface includes information about the first set of user body temperature information not displayed in the body temperature user interface.

2. The method according to claim 1, the method 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 a second notification data of the first type; And In response to receiving the 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, outputting a second notification corresponding to the second notification data of the first type; And Based on determining that the computer system is currently in the first silent mode, foregoing outputting a notification corresponding to the second notification data of the first type.

3. The method according to any one of claims 1 to 2, the method 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 a first sleep start time and a first sleep end time at least for the first day; After receiving the third input: Based on determining that the current time corresponds to the first sleep start time, entering the sleep tracking mode; and Based on determining that the current time does not correspond to the first sleep start time, foregoing entering the sleep tracking mode.

4. The method according to any one of claims 1 to 2, wherein causing the first set of user body temperature information to be collected includes: Causing a first external device separate from the computer system to collect the first set of user body temperature information; And Receiving the first set of user body temperature information from the first external device.

5. The method according to any one of claims 1 to 2, the method further comprising: Before receiving the input, displaying, via the display generating component, the body temperature user interface, including: According to 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 According to determining that the threshold amount of body temperature information has been collected, displaying a representation of one or more sets of user body temperature information 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 2, the method further comprising: After displaying the body temperature user interface including the representation of one or more sets of user body temperature information, displaying a second instance of the body temperature user interface, wherein: According to determining that a second set of criteria is met, the second instance of the body temperature user interface includes a representation of a second set of user body temperature information; and According to determining that the second set of criteria is not met, the second instance of the body temperature user interface does not include the representation of the second set of user body 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 2, the method further comprising: When displaying the body temperature user interface, receiving a selection input via the one or more input devices; And In response to receiving the selection input: According to determining that the selection input corresponds to selecting a first time frame option corresponding to a first time frame, displaying, within the body temperature user interface, a representation of one or more sets of user body temperature information corresponding to the first time frame; And According to determining that the selection input corresponds to selecting a second time frame option different from the first time frame option, displaying, within the body temperature user interface, a representation of one or more sets of user body temperature information corresponding to a second time frame, wherein the second time frame option corresponds to a second time frame different from the first time frame.

8. The method according to any one of claims 1 to 2, wherein the representation of one or more sets of user body temperature information includes one or more relative temperature measurement results.

9. The method according to any one of claims 1 to 2, wherein the first detailed user interface includes: A start time corresponding to the first set of user body temperature information; And An end time corresponding to the first set of user body temperature information.

10. The method according to any one of claims 1 to 2, wherein: The body temperature user interface includes relative body temperature information corresponding to the first set 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.

11. The method according to any one of claims 1 to 2, wherein the first detailed user interface includes external device information corresponding to the first set of user body temperature information.

12. The method according to any one of claims 1 to 2, the method 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: Output a second notification corresponding to the first notification data based on determining that the computer system is not in the sleep tracking mode; and Abstain from outputting the second notification corresponding to the first notification data based on determining that the computer system is currently in the sleep tracking mode and the first notification data includes a second type of notification data.

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

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

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

16. A 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 including instructions for performing the method according to any one of claims 1 to 15.

17. 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; and A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the method according to any one of claims 1 to 15.

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: Components for performing the method according to any one of claims 1 to 15.

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

Images