WO2024054378A1 - Interfaces utilisateur pour suivi de santé - Google Patents

Interfaces utilisateur pour suivi de santé Download PDF

Info

Publication number
WO2024054378A1
WO2024054378A1 PCT/US2023/031421 US2023031421W WO2024054378A1 WO 2024054378 A1 WO2024054378 A1 WO 2024054378A1 US 2023031421 W US2023031421 W US 2023031421W WO 2024054378 A1 WO2024054378 A1 WO 2024054378A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
body temperature
computer system
temperature information
receiving
Prior art date
Application number
PCT/US2023/031421
Other languages
English (en)
Other versions
WO2024054378A4 (fr
Inventor
Lindsey Maratta
Roxanne B. BRITTAIN
Christine L. CURRY
Nicholas D. FELTON
Karen L. JENKINS
Michael Pangburn
Carey Y. ZHANG
Shunan ZHANG
Original Assignee
Apple Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US18/237,339 external-priority patent/US20240079130A1/en
Application filed by Apple Inc. filed Critical Apple Inc.
Publication of WO2024054378A1 publication Critical patent/WO2024054378A1/fr
Publication of WO2024054378A4 publication Critical patent/WO2024054378A4/fr

Links

Classifications

    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B5/00—Measuring for diagnostic purposes; Identification of persons
    • A61B5/01—Measuring temperature of body parts ; Diagnostic temperature sensing, e.g. for malignant or inflamed tissue
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B10/00—Other methods or instruments for diagnosis, e.g. instruments for taking a cell sample, for biopsy, for vaccination diagnosis; Sex determination; Ovulation-period determination; Throat striking implements
    • A61B10/0012—Ovulation-period determination
    • A—HUMAN NECESSITIES
    • A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B10/00—Other methods or instruments for diagnosis, e.g. instruments for taking a cell sample, for biopsy, for vaccination diagnosis; Sex determination; Ovulation-period determination; Throat striking implements
    • A61B10/0012—Ovulation-period determination
    • A61B2010/0019—Ovulation-period determination based on measurement of temperature

Definitions

  • the present disclosure relates generally to computer user interfaces, and more specifically to techniques for tracking health information and generating predictions and notifications.
  • Recurring (e.g., reoccurring) events such as recurring health events can be tracked on electronic devices to log past events and to predict future events.
  • Some techniques for tracking health information using electronic devices are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface, which may include multiple key presses or keystrokes. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices.
  • the present technique provides electronic devices with faster, more efficient methods and interfaces for tracking health information and for generating related predictions and/or notifications. Such methods and interfaces optionally complement or replace other methods for tracking health information and for generating related predictions and/or notifications. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges. [0006] In accordance with some embodiments, a method is described.
  • the method comprises, at a computer system that is 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 notification data of a first type; in response to receiving the notification data of the first type: in accordance with a determination that the computer system is not in the sleep tracking mode, outputting a first notification corresponding to the notification data of the first type; and in accordance with a determination that the computer system is currently in the sleep tracking mode, forgoing outputting the first notification corresponding to the notification data of the first type; and after causing the first set of user body temperature information to be collected, displaying, via display generation component, a body temperature user interface that includes representations of one or more sets of user body temperature information including the first set of user body temperature information.
  • a non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is 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 notification data of a first type; in response to receiving the notification data of the first type: in accordance with a determination that the computer system is not in the sleep tracking mode, outputting a first notification corresponding to the notification data of the first type; and in accordance with a determination that the computer system is currently in the sleep tracking mode, forgoing outputting the first notification corresponding to the notification data of the first type; and after causing the first set
  • a transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is 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 notification data of a first type; in response to receiving the notification data of the first type: in accordance with a determination that the computer system is not in the sleep tracking mode, outputting a first notification corresponding to the notification data of the first type; and in accordance with a determination that the computer system is currently in the sleep tracking mode, forgoing outputting the first notification corresponding to the notification data of the first type; and after causing the first set of user body temperature
  • a computer system configured to communicate with a display generation component, one or more input devices, and a temperature sensor, and comprises: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: receiving, via the one or more input devices, an input corresponding to a request to enter a sleep tracking mode; in response to the input, entering the sleep tracking mode; during the sleep tracking mode, causing a first set of user body temperature information to be collected via the temperature sensor; receiving notification data of a first type; in response to receiving the notification data of the first type: in accordance with a determination that the computer system is not in the sleep tracking mode, outputting a first notification corresponding to the notification data of the first type; and in accordance with a determination that the computer system is currently in the sleep tracking mode, forgoing outputting the first notification corresponding to the notification data of the first type; and after causing the first set of user body temperature information to be
  • a computer system configured to communicate with a display generation component, one or more input devices, and a temperature sensor, and comprises: means 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; means for, during the sleep tracking mode, causing a first set of user body temperature information to be collected via the temperature sensor; receiving notification data of a first type; means for, in response to receiving the notification data of the first type: in accordance with a determination that the computer system is not in the sleep tracking mode, outputting a first notification corresponding to the notification data of the first type; and in accordance with a determination that the computer system is currently in the sleep tracking mode, forgoing outputting the first notification corresponding to the notification data of the first type; and means for, after causing the first set of user body temperature information to be collected, displaying, via display generation component, a body temperature user interface that includes representations of one or more
  • a computer program product comprises one or more programs configured to be executed by one or more processors of a computer system that is 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 notification data of a first type; in response to receiving the notification data of the first type: in accordance with a determination that the computer system is not in the sleep tracking mode, outputting a first notification corresponding to the notification data of the first type; and in accordance with a determination that the computer system is currently in the sleep tracking mode, forgoing outputting the first notification corresponding to the notification data of the first type; and after causing the first set of user body temperature information to be collected, displaying, via display
  • a method comprises, at a computer system that is 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 that indicates to the user that a predicted ovulation date has been determined for the user, wherein the predicted ovulation date was determined based on the body temperature information corresponding to the user.
  • a non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is 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 that indicates to the user that a predicted ovulation date has been determined for the user, wherein the predicted ovulation date was determined based on the body temperature information corresponding to the user.
  • a transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is 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 that indicates to the user that a predicted ovulation date has been determined for the user, wherein the predicted ovulation date was determined based on the body temperature information corresponding to the user.
  • a computer system configured to communicate with a display generation component and one or more input devices, and comprises: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: receiving body temperature information corresponding to a user; 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 that indicates to the user that a predicted ovulation date has been determined for the user, wherein the predicted ovulation date was determined based on the body temperature information corresponding to the user.
  • a computer system configured to communicate with a display generation component and one or more input devices.
  • the computer system comprises: means for receiving body temperature information corresponding to a user; and means 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 that indicates to the user that a predicted ovulation date has been determined for the user, wherein the predicted ovulation date was determined based on the body temperature information corresponding to the user.
  • a computer program product comprises one or more programs configured to be executed by one or more processors of a computer system that is 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 that indicates to the user that a predicted ovulation date has been determined for the user, wherein the predicted ovulation date was determined based on the body temperature information corresponding to the user.
  • a method comprises, at a computer system that is in communication with a display generation component and one or more input devices: displaying, via the display generation component, at a first time, a cycle tracking user interface including displaying a first fertile window prediction for a user; receiving body temperature information corresponding to the user; after receiving the body temperature information corresponding to the user, determining, at a second time subsequent to the first time, based on the body temperature information corresponding to the user, a predicted ovulation date for the user; and displaying, via the display generation component, at a third time subsequent to the second time, an updated cycle tracking user interface, including concurrently displaying: a representation of the predicted ovulation date for the user; and an updated fertile window prediction for the user different from the first fertile window prediction for the user.
  • a non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: displaying, via the display generation component, at a first time, a cycle tracking user interface including displaying a first fertile window prediction for a user; receiving body temperature information corresponding to the user; after receiving the body temperature information corresponding to the user, determining, at a second time subsequent to the first time, based on the body temperature information corresponding to the user, a predicted ovulation date for the user; and displaying, via the display generation component, at a third time subsequent to the second time, an updated cycle tracking user interface, including concurrently displaying: a representation of the predicted ovulation date for the user; and an updated fertile window prediction for the user different from the first fertile window prediction for the user.
  • a transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: displaying, via the display generation component, at a first time, a cycle tracking user interface including displaying a first fertile window prediction for a user; receiving body temperature information corresponding to the user; after receiving the body temperature information corresponding to the user, determining, at a second time subsequent to the first time, based on the body temperature information corresponding to the user, a predicted ovulation date for the user; and displaying, via the display generation component, at a third time subsequent to the second time, an updated cycle tracking user interface, including concurrently displaying: a representation of the predicted ovulation date for the user; and an updated fertile window prediction for the user different from the first fertile window prediction for the user.
  • a computer system configured to communicate with a display generation component and one or more input devices, and comprises: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: displaying, via the display generation component, at a first time, a cycle tracking user interface including displaying a first fertile window prediction for a user; receiving body temperature information corresponding to the user; after receiving the body temperature information corresponding to the user, determining, at a second time subsequent to the first time, based on the body temperature information corresponding to the user, a predicted ovulation date for the user; and displaying, via the display generation component, at a third time subsequent to the second time, an updated cycle tracking user interface, including concurrently displaying: a representation of the predicted ovulation date for the user; and an updated fertile window prediction for the user different from the first fertile window prediction for the user.
  • a computer system configured to communicate with a display generation component and one or more input devices.
  • the computer system comprises: means for displaying, via the display generation component, at a first time, a cycle tracking user interface including displaying a first fertile window prediction for a user; means for receiving body temperature information corresponding to the user; means for, after receiving the body temperature information corresponding to the user, determining, at a second time subsequent to the first time, based on the body temperature information corresponding to the user, a predicted ovulation date for the user; and means for displaying, via the display generation component, at a third time subsequent to the second time, an updated cycle tracking user interface, including concurrently displaying: a representation of the predicted ovulation date for the user; and an updated fertile window prediction for the user different from the first fertile window prediction for the user.
  • a computer program product comprises one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: displaying, via the display generation component, at a first time, a cycle tracking user interface including displaying a first fertile window prediction for a user; receiving body temperature information corresponding to the user; after receiving the body temperature information corresponding to the user, determining, at a second time subsequent to the first time, based on the body temperature information corresponding to the user, a predicted ovulation date for the user; and displaying, via the display generation component, at a third time subsequent to the second time, an updated cycle tracking user interface, including concurrently displaying: a representation of the predicted ovulation date for the user; and an updated fertile window prediction for the user different from the first fertile window prediction for the user.
  • a method comprises, at a computer system that is in communication with a display generation component and one or more input devices: receiving, via the one or more input devices, menstrual cycle information for a user; and in accordance with a determination that the menstrual cycle information satisfies a first set of criteria, displaying, via the display generation component, a push notification that indicates to the user that the computer system has identified a potential health issue for the user.
  • a non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: receiving, via the one or more input devices, menstrual cycle information for a user; and in accordance with a determination that the menstrual cycle information satisfies a first set of criteria, displaying, via the display generation component, a push notification that indicates to the user that the computer system has identified a potential health issue for the user.
  • a transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: receiving, via the one or more input devices, menstrual cycle information for a user; and in accordance with a determination that the menstrual cycle information satisfies a first set of criteria, displaying, via the display generation component, a push notification that indicates to the user that the computer system has identified a potential health issue for the user.
  • a computer system configured to communicate with a display generation component and one or more input devices, and comprises: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: receiving, via the one or more input devices, menstrual cycle information for a user; and in accordance with a determination that the menstrual cycle information satisfies a first set of criteria, displaying, via the display generation component, a push notification that indicates to the user that the computer system has identified a potential health issue for the user.
  • a computer system configured to communicate with a display generation component and one or more input devices.
  • the computer system comprises: means for receiving, via the one or more input devices, menstrual cycle information for a user; and means for, in accordance with a determination that the menstrual cycle information satisfies a first set of criteria, displaying, via the display generation component, a push notification that indicates to the user that the computer system has identified a potential health issue for the user.
  • a computer program product comprises one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: receiving, via the one or more input devices, menstrual cycle information for a user; and in accordance with a determination that the menstrual cycle information satisfies a first set of criteria, displaying, via the display generation component, a push notification that indicates to the user that the computer system has identified a potential health issue for the user.
  • 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.
  • devices are provided with faster, more efficient methods and interfaces for tracking health information and for generating related predictions and/or notifications, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices.
  • Such methods and interfaces may complement or replace other methods for tracking health information and for generating related predictions and/or notifications.
  • FIG. 1 A is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments.
  • FIG. IB is a block diagram illustrating exemplary components for event handling in accordance with some embodiments.
  • FIG. 2 illustrates a portable multifunction device having a touch screen in accordance with some embodiments.
  • FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.
  • FIG. 4A illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.
  • FIG. 4B illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display in accordance with some embodiments.
  • FIG. 5 A illustrates a personal electronic device in accordance with some embodiments.
  • FIG. 5B is a block diagram illustrating a personal electronic device in accordance with some embodiments.
  • FIGS. 6A-6Q illustrate exemplary user interfaces for tracking body temperature information, in accordance with some embodiments.
  • FIG. 7 is a flow diagram illustrating methods for tracking body temperature information, in accordance with some embodiments.
  • FIGS. 8A-8K illustrate exemplary user interfaces for generating and providing ovulation date predictions, in accordance with some embodiments.
  • FIG. 9A is a flow diagram illustrating methods for generating and providing ovulation date predictions, in accordance with some embodiments.
  • FIG. 9B is a flow diagram illustrating methods for generating and providing ovulation date predictions, in accordance with some embodiments.
  • FIGS. 10A-10N illustrate exemplary user interfaces for generating and providing health-related notifications, in accordance with some embodiments.
  • FIG. 11 is a flow diagram illustrating methods for generating and providing health-related notifications, in accordance with some embodiments.
  • FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description of exemplary devices for performing the techniques for tracking health information and for generating related predictions and/or notifications.
  • FIGS. 6A-6Q illustrate exemplary user interfaces for tracking body temperature information.
  • FIG. 7 is a flow diagram illustrating methods of tracking body temperature information in accordance with some embodiments. The user interfaces in FIGS. 6A-6Q are used to illustrate the processes described below, including the processes in FIG. 7.
  • FIGS. 8A-8K illustrate exemplary user interfaces for generating and providing ovulation date predictions.
  • FIG. 9A is a flow diagram illustrating methods of generating and providing ovulation date predictions in accordance with some embodiments.
  • FIGS. 9B is a flow diagram illustrating methods of generating and providing ovulation date predictions in accordance with some embodiments.
  • the user interfaces in FIGS. 8A-8K are used to illustrate the processes described below, including the processes in FIGS. 9 A and 9B.
  • FIGS. 10A-10N illustrate exemplary user interfaces for generating and providing health- related notifications.
  • FIG. 11 is a flow diagram illustrating methods of generating and providing health-related notifications in accordance with some embodiments.
  • the user interfaces in FIGS. 10A-10N are used to illustrate the processes described below, including the processes in FIG. 11.
  • the processes described below enhance the operability of the devices and make the user-device interfaces more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) through various techniques, including by providing improved visual feedback to the user, reducing the number of inputs needed 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 requiring further user input, and/or additional techniques. These techniques also reduce power usage and improve battery life of the device by enabling the user to use the device more quickly and efficiently.
  • system or computer readable medium contains instructions for performing the contingent operations based on the satisfaction of the corresponding one or more conditions and thus is capable of determining whether the contingency has or has not been satisfied without explicitly repeating steps of a method until all of the conditions upon which steps in the method are contingent have been met.
  • a system or computer readable storage medium can repeat the steps of a method as many times as are needed to ensure that all of the contingent steps have been performed.
  • first means “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 could be termed a second touch, and, similarly, a second touch could be termed 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, the first touch and the second touch are both touches, but they are not the same touch.
  • the term “if’ is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context.
  • the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
  • the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions.
  • portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California.
  • Other portable electronic devices such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used.
  • the device is not a portable communications device, but is a desktop computer with a touch- sensitive surface (e.g., a touch screen display and/or a touchpad).
  • the electronic device is a computer system that is in communication (e.g., via wireless communication, via wired communication) with a display generation component.
  • the display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection.
  • the display generation component is integrated with the computer system.
  • the display generation component is separate from the computer system.
  • displaying includes causing to display the content (e.g., video data rendered or decoded by display controller 156) by transmitting, via a wired or wireless connection, data (e.g., image data or video data) to an integrated or external display generation component to visually produce the content.
  • content e.g., video data rendered or decoded by display controller 1566
  • data e.g., image data or video data
  • an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, 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.
  • the device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
  • applications such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
  • the various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface.
  • One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application.
  • a common physical architecture (such as the touch- sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
  • FIG. 1 A is a block diagram illustrating portable multifunction device 100 with touch-sensitive display system 112 in accordance with some embodiments.
  • 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 mediums), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem 106, other input control devices 116, and external port 124.
  • Device 100 optionally includes one or more optical sensors 164.
  • Device 100 optionally includes one or more contact intensity sensors 165 for detecting 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.
  • the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface.
  • the intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors.
  • one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface.
  • force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact.
  • a pressuresensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch- sensitive surface.
  • the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface.
  • the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements).
  • the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure).
  • the intensity threshold is a pressure threshold measured in units of pressure.
  • the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user’s sense of touch.
  • a component e.g., a touch-sensitive surface
  • another component e.g., housing
  • the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device.
  • a touch-sensitive surface e.g., a touch-sensitive display or trackpad
  • the user is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button.
  • a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user’s movements.
  • movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users.
  • a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”)
  • the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.
  • device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components.
  • the various components shown in FIG. 1 A 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.
  • Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices.
  • Memory controller 122 optionally controls access to memory 102 by other components of device 100.
  • Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102.
  • the one or more processors 120 run or execute various software programs (such as computer programs (e.g., including instructions)) and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data.
  • peripherals interface 118, CPU 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.
  • RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals.
  • RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals.
  • RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth.
  • an antenna system an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth.
  • SIM subscriber identity module
  • RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication.
  • the RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio.
  • NFC near field communication
  • the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.
  • GSM Global System for Mobile Communications
  • EDGE Enhanced Data GSM Environment
  • HSDPA high-speed downlink packet access
  • HUPA high-speed uplink packet access
  • Evolution, Data-Only (EV-DO) Evolution, Data-Only
  • HSPA HSPA+
  • DC-HSPDA Dual-Cell HSPA
  • I la IEEE 802.1 lb, IEEE 802.11g, IEEE 802.1 In, and/or IEEE 802.1 lac
  • VoIP voice over Internet Protocol
  • Wi-MAX a protocol for e-mail (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 not yet developed as of the filing date of this document.
  • IMAP Internet message access protocol
  • POP post office protocol
  • 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)
  • SMS Short Message Service
  • Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100.
  • Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111.
  • Speaker 111 converts the electrical signal to human-audible sound waves.
  • Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves.
  • Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118.
  • audio circuitry 110 also includes a headset jack (e.g., 212, FIG. 2).
  • the headset jack provides an interface between audio circuitry 110 and removable audio input/output peripherals, such as output-only headphones or a headset with both output (e.g., a headphone for one or both ears) and input (e.g., a
  • I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118.
  • I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, depth camera controller 169, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices.
  • the one or more input controllers 160 receive/send electrical signals from/to other input control devices 116.
  • the other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth.
  • input controlled s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse.
  • the one or more buttons optionally include an up/down button for volume control of speaker 111 and/or microphone 113.
  • the one or more buttons optionally include a push button (e.g., 206, FIG. 2).
  • the electronic device is a computer system that is in communication (e.g., via wireless communication, via wired communication) with one or more input devices.
  • the one or more input devices include a touch-sensitive surface (e.g., a trackpad, as part of a touch-sensitive display).
  • 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.
  • 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.
  • an air gesture is a gesture that is detected without the user touching an input element that is part of the device (or independently of an input element that is a part of the device) and is based on detected motion of a portion of the user’s body through the air including motion of the user’s body relative to an absolute reference (e.g., an angle of the user’s arm relative to the ground or a distance of the user’s hand relative to the ground), relative to another portion of the user’s body (e.g., movement of a hand of the user relative to a shoulder of the user, movement of one hand of the user relative to another hand of the user, and/or movement of a finger of the user relative to another finger or portion of a hand of the user), and/or absolute motion of a portion of the user’s body (e.g., a tap gesture that includes movement of a hand in a predetermined pose by a predetermined amount and/or speed, or a shake gesture that includes a predetermined speed or amount of rotation of a portion of the user
  • a quick press of the push button optionally disengages a lock of touch screen 112 or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. Patent Application 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed December 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety.
  • a longer press of the push button e.g., 206) optionally turns power to device 100 on or off.
  • the functionality of one or more of the buttons are, optionally, user-customizable.
  • Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
  • Touch-sensitive display 112 provides an input interface and an output interface between the device and a user.
  • Display controller 156 receives and/or sends electrical signals from/to touch screen 112.
  • Touch screen 112 displays visual output to the user.
  • the visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output optionally corresponds to user-interface objects.
  • Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact.
  • Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen 112.
  • user-interface objects e.g., one or more soft keys, icons, web pages, or images
  • a point of contact between touch screen 112 and the user corresponds to a finger of the user.
  • Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments.
  • Touch screen 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112.
  • touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112.
  • projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.
  • a touch-sensitive display in some embodiments of touch screen 112 is, optionally, analogous to the multi-touch sensitive touchpads 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), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety.
  • touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.
  • a touch-sensitive display in some embodiments of touch screen 112 is 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 July 30, 2004; (4) U.S. Patent Application No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed January 31, 2005; (5) U.S. Patent Application No.
  • Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi.
  • the user optionally makes contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth.
  • the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylusbased input due to the larger area of contact of a finger on the touch screen.
  • the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
  • device 100 in addition to the touch screen, device 100 optionally includes a touchpad for activating or deactivating particular functions.
  • the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output.
  • the touchpad is, optionally, a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
  • Device 100 also includes power system 162 for powering the various components.
  • Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
  • Power system 162 optionally also includes one or more optical sensors 164.
  • FIG. 1A shows an optical sensor coupled to optical sensor controller 158 in I/O subsystem 106.
  • Optical sensor 164 optionally includes charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors.
  • Optical sensor 164 receives light from the environment, projected through one or more lenses, and converts the light to data representing an image.
  • imaging module 143 also called a camera module
  • optical sensor 164 optionally captures still images or video.
  • an optical sensor is located on the back of device 100, opposite touch screen display 112 on the front of the device so that the touch screen display is enabled for use as a viewfinder for still and/or video image acquisition.
  • an optical sensor is located on the front of the device so that the user’s image is, optionally, obtained for video conferencing while the user views the other video conference participants on the touch screen display.
  • the position of optical sensor 164 can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a single optical sensor 164 is used along with the touch screen display for both video conferencing and still and/or video image acquisition.
  • Device 100 optionally also includes one or more depth camera sensors 175.
  • FIG. 1A shows a depth camera sensor coupled to depth camera controller 169 in I/O subsystem 106.
  • Depth camera sensor 175 receives data from the environment to create a three dimensional model of an object (e.g., a face) within a scene from a viewpoint (e.g., a depth camera sensor).
  • a viewpoint e.g., a depth camera sensor
  • depth camera sensor 175 in conjunction with imaging module 143 (also called a camera module), depth camera sensor 175 is optionally used to determine a depth map of different portions of an image captured by the imaging module 143.
  • a depth camera sensor is located on the front of device 100 so that the user’s image with depth information is, optionally, obtained for video conferencing while the user views the other video conference participants on the touch screen display and to capture selfies with depth map data.
  • the depth camera sensor 175 is located on the back of device, or on the back and the front of the device 100.
  • the position of depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a depth camera sensor 175 is used along with the touch screen display for both video conferencing and still and/or video image acquisition.
  • Device 100 optionally also includes one or more contact intensity sensors 165. FIG.
  • Contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface).
  • Contact intensity sensor 165 receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment.
  • at least one contact intensity sensor is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system 112).
  • at least one contact intensity sensor is located on the back of device 100, opposite touch screen display 112, which is located on the front of device 100.
  • Device 100 optionally also includes one or more proximity sensors 166.
  • FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.
  • proximity sensor 166 is, optionally, coupled to input controller 160 in VO subsystem 106.
  • Proximity sensor 166 optionally performs as described in U.S. Patent Application Nos.
  • the proximity sensor turns off and disables touch screen 112 when the multifunction device is placed near the user’s ear (e.g., when the user is making a phone call).
  • Device 100 optionally also includes one or more tactile output generators 167.
  • FIG. 1 A shows a tactile output generator coupled to haptic feedback controller 161 in I/O subsystem 106.
  • Tactile output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components and/or electromechanical devices that convert energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts electrical signals into tactile outputs on the device).
  • Contact intensity sensor 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates tactile outputs on device 100 that are capable of being sensed by a user of device 100.
  • At least one tactile output generator is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system 112) and, optionally, generates a tactile output by moving the touch- sensitive surface vertically (e.g., in/out of a surface of device 100) or laterally (e.g., back and forth in the same plane as a surface of device 100).
  • at least one tactile output generator sensor is located on the back of device 100, opposite touch screen display 112, which is located on the front of device 100.
  • Device 100 optionally also includes one or more accelerometers 168.
  • FIG. 1 A shows accelerometer 168 coupled to peripherals interface 118.
  • accelerometer 168 is, optionally, coupled to an input controller 160 in I/O subsystem 106.
  • Accelerometer 168 optionally performs as described in U.S. Patent Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated by reference herein in their entirety.
  • information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers.
  • Device 100 optionally includes, in addition to accelerometer(s) 168, a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device 100.
  • GPS or GLONASS or other global navigation system
  • the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136.
  • memory 102 FIG. 1A
  • 370 FIG. 3
  • Device/global internal state 157 includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch screen display 112; sensor state, including information obtained from the device’s various sensors and input control devices 116; and location information concerning the device’s location and/or attitude.
  • Operating system 126 e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks
  • Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124.
  • External port 124 e.g., Universal Serial Bus (USB), FIREWIRE, etc.
  • USB Universal Serial Bus
  • FIREWIRE FireWire
  • the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.
  • Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch- sensitive devices (e.g., a touchpad or physical click wheel).
  • Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact).
  • Contact/motion module 130 receives contact data from the touch-sensitive surface.
  • Determining movement of the point of contact which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts).
  • contact/motion module 130 and display controller 156 detect contact on a touchpad.
  • contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon).
  • at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware.
  • a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).
  • Contact/motion module 130 optionally detects a gesture input by a user.
  • Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts).
  • a gesture is, optionally, detected by detecting a particular contact pattern.
  • detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon).
  • detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event.
  • Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed.
  • graphics includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like.
  • graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156. [0092]
  • Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
  • Text input module 134 which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts module 137, e-mail client module 140, IM module 141, browser module 147, and any other application that needs text input).
  • applications e.g., contacts module 137, e-mail client module 140, IM module 141, browser module 147, and any other application that needs text input.
  • GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing; to camera module 143 as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
  • applications e.g., to telephone 138 for use in location-based dialing; to camera module 143 as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
  • Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:
  • Contacts module 137 (sometimes called an address book or contact list);
  • Video conference module 139 • Video conference module 139;
  • Camera module 143 for still and/or video images
  • Widget modules 149 which optionally include one or more of: weather widget 149-1, stocks 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 widgets 149-6;
  • Widget creator module 150 for making user-created widgets 149-6;
  • Video and music player module 152 which merges video player module and music player module
  • Map module 154 • Map module 154;
  • Examples of other applications 136 that are, optionally, stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
  • contacts module 137 are, optionally, used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone module 138, video conference module 139, e-mail client module 140, or IM module 141; and so forth.
  • an address book or contact list e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370
  • telephone module 138 are optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed.
  • the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies.
  • video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
  • e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions.
  • e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
  • the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony -based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages.
  • SMS Short Message Service
  • MMS Multimedia Message Service
  • XMPP extensible Markup Language
  • SIMPLE Session Initation Protocol
  • IMPS Internet Messaging Protocol
  • transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS).
  • EMS Enhanced Messaging Service
  • instant messaging refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).
  • workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.
  • create workouts e.g., with time, distance, and/or calorie burning goals
  • communicate with workout sensors sports devices
  • receive workout sensor data calibrate sensors used to monitor a workout
  • select and play music for a workout and display, store, and transmit workout data.
  • camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.
  • image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
  • modify e.g., edit
  • present e.g., in a digital slide show or album
  • browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
  • calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.
  • widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user- created widget 149-6).
  • a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file.
  • a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
  • the widget creator module 150 are, optionally, used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).
  • search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
  • search criteria e.g., one or more user-specified search terms
  • video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124).
  • device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
  • notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.
  • map module 154 are, optionally, used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.
  • online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via 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.
  • instant messaging module 141 rather than e-mail client module 140, is used to send a link to a particular online video.
  • Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein).
  • These modules e.g., sets of instructions
  • modules need not be implemented as separate software programs (such as computer programs (e.g., including instructions)), procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments.
  • video player module is, optionally, combined with music player module into a single module (e.g., video and music player module 152, FIG. 1A).
  • memory 102 optionally stores a subset of the modules and data structures identified above.
  • device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad.
  • a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.
  • the predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces.
  • the touchpad when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100.
  • a “menu button” is implemented using a touchpad.
  • the menu button is a physical push button or other physical input control device instead of a touchpad.
  • FIG. IB is a block diagram illustrating exemplary components for event handling in accordance with some embodiments.
  • memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., in operating system 126) and a respective application 136-1 (e.g., any of the aforementioned applications 137-151, 155, 380-390).
  • event sorter 170 e.g., in operating system 126
  • application 136-1 e.g., any of the aforementioned applications 137-151, 155, 380-390.
  • Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information.
  • Event sorter 170 includes event monitor 171 and event dispatcher module 174.
  • application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing.
  • device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
  • application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
  • Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch- sensitive display 112, as part of a multi-touch gesture).
  • Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110).
  • Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch- sensitive display 112 or a touch-sensitive surface.
  • event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
  • event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
  • Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
  • FIG. 1 Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur.
  • the application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
  • Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub- events that form an event or potential event). Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
  • Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
  • Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.
  • an event recognizer e.g., event recognizer 180.
  • event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173.
  • event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.
  • operating system 126 includes event sorter 170.
  • application 136-1 includes event sorter 170.
  • event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
  • 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 that occur within a respective view of the application’s user interface.
  • Each application view 191 of the application 136-1 includes one or more event recognizers 180.
  • a respective application view 191 includes a plurality of event recognizers 180.
  • one or more of event recognizers 180 are part of a separate module, such as a user interface kit or a higher level object from which application 136-1 inherits methods and other properties.
  • a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170.
  • Event handler 190 optionally utilizes or calls data updater
  • one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater
  • GUI updater 178 is included in a respective application view 191.
  • a respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information.
  • Event recognizer 180 includes event receiver 182 and event comparator 184.
  • event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).
  • Event receiver 182 receives event information from event sorter 170.
  • the event information includes information about a sub-event, for example, a touch or a touch movement.
  • the event information also includes additional information, such as location of the sub-event.
  • the event information optionally also includes speed and direction of the sub-event.
  • events include rotation of the device 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 (also called device attitude) of the device.
  • Event comparator 184 compares the event information to predefined event or subevent definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event.
  • event comparator 184 includes event definitions 186.
  • Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187- 2), and others.
  • sub-events in an event include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching.
  • the definition for event 1 is a double tap on a displayed object.
  • the double tap for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase.
  • the definition for event 2 is a dragging on a displayed object.
  • the dragging for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end).
  • the event also includes information for one or more associated event handlers 190.
  • event definitions 186 include a definition of an event for a respective user-interface object.
  • 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 in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
  • the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer’s event type.
  • a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
  • a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers.
  • metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another.
  • metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
  • a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized.
  • a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
  • event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
  • data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module.
  • object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object.
  • GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch- sensitive display.
  • event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178.
  • data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
  • event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens.
  • mouse movement and mouse button presses optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
  • FIG. 2 illustrates a portable multifunction device 100 having a touch screen 112 in accordance with some embodiments.
  • the touch screen optionally displays one or more graphics within user interface (UI) 200.
  • UI user interface
  • a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure).
  • selection of one or more graphics occurs when the user breaks contact with the one or more graphics.
  • the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and/or downward), and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device 100.
  • inadvertent contact with a graphic does not select the graphic.
  • a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.
  • Device 100 optionally also include one or more physical buttons, such as “home” or menu button 204.
  • menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally, executed on device 100.
  • the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
  • device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124.
  • Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process.
  • device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113.
  • Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.
  • FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.
  • Device 300 need not be portable.
  • device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child’s learning toy), a gaming system, or a control device (e.g., a home or industrial controller).
  • Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communications interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components.
  • CPUs processing units
  • Communication buses 320 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components.
  • Device 300 includes input/output (I/O) interface 330 comprising 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 and touchpad 355, tactile output generator 357 for generating tactile outputs on device 300 (e.g., similar to tactile output generator(s) 167 described above with reference to FIG. 1 A), sensors 359 (e.g., optical, acceleration, proximity, touch-sensitive, and/or contact intensity sensors similar to contact intensity sensor(s) 165 described above with reference to FIG. 1 A).
  • sensors 359 e.g., optical, acceleration, proximity, touch-sensitive, and/or contact intensity sensors similar to contact intensity sensor(s) 165 described above with reference to FIG. 1 A).
  • 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 nonvolatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 370 optionally includes one or more storage devices remotely located from CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1 A), or a subset thereof. Furthermore, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100.
  • memory 370 of device 300 optionally stores drawing module 380, presentation module 382, word processing module 384, website creation module 386, disk authoring module 388, and/or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1 A) optionally does not store these modules.
  • FIG. 3 Each of the above-identified elements in FIG. 3 is, optionally, stored in one or more of the previously mentioned memory devices.
  • Each of the above-identified modules corresponds to a set of instructions for performing a function described above.
  • memory 370 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 370 optionally stores additional modules and data structures not described above.
  • FIG. 4A illustrates an exemplary user interface for a menu of applications on portable multifunction device 100 in accordance with some embodiments. Similar user interfaces are, optionally, implemented on device 300.
  • user interface 400 includes the following elements, or a subset or superset thereof:
  • Tray 408 with icons for frequently used applications such as: o Icon 416 for telephone module 138, labeled “Phone,” which optionally includes an indicator 414 of the number of missed calls or voicemail messages; o Icon 418 for e-mail client module 140, labeled “Mail,” which optionally includes an indicator 410 of the number of unread e-mails; o Icon 420 for browser module 147, labeled “Browser;” and o Icon 422 for video and music player module 152, also referred to as iPod (trademark of Apple Inc.) module 152, labeled “iPod;” and
  • Icons for other applications such as: o Icon 424 for IM module 141, labeled “Messages;” o Icon 426 for calendar module 148, labeled “Calendar;” o Icon 428 for image management module 144, labeled “Photos;” o Icon 430 for camera module 143, labeled “Camera;” o Icon 432 for online video module 155, labeled “Online Video;” o Icon 434 for stocks widget 149-2, labeled “Stocks;” o Icon 436 for map module 154, labeled “Maps;” o Icon 438 for weather widget 149-1, labeled “Weather;” o Icon 440 for alarm clock widget 149-4, labeled “Clock;” o Icon 442 for workout support module 142, labeled “Workout Support;” o Icon 444 for notes module 153, labeled “Notes;” and o Icon 446 for notes module
  • icon labels illustrated in FIG. 4A are merely exemplary.
  • icon 422 for video and music player module 152 is labeled “Music” or “Music Player.”
  • Other labels are, optionally, used for various application icons.
  • a label for a respective application icon includes a name of an application corresponding to the respective application icon.
  • a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon.
  • FIG. 4B illustrates an exemplary user interface on a device (e.g., device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet or touchpad 355, FIG. 3) that is separate from the display 450 (e.g., touch screen display 112).
  • Device 300 also, optionally, includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting intensity of contacts on touch- sensitive surface 451 and/or one or more tactile output generators 357 for generating tactile outputs for a user of device 300.
  • one or more contact intensity sensors e.g., one or more of sensors 359
  • tactile output generators 357 for generating tactile outputs for a user of device 300.
  • the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in FIG. 4B.
  • the touch-sensitive surface e.g., 451 in FIG. 4B
  • the touch-sensitive surface has a primary axis (e.g., 452 in FIG. 4B) that corresponds to a primary axis (e.g., 453 in FIG. 4B) on the display (e.g., 450).
  • the device detects contacts (e.g., 460 and 462 in FIG.
  • finger inputs e.g., finger contacts, finger tap gestures, finger swipe gestures
  • one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input).
  • a swipe gesture is, optionally, replaced with 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 the contact).
  • a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact).
  • a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact).
  • multiple user inputs it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
  • FIG. 5A illustrates exemplary personal electronic device 500.
  • Device 500 includes body 502.
  • device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1 A-4B).
  • device 500 has touch-sensitive display screen 504, hereafter touch screen 504.
  • touch screen 504 optionally includes one or more intensity sensors for detecting intensity of contacts (e.g., touches) being applied.
  • the one or more intensity sensors of touch screen 504 (or the touch-sensitive surface) can provide output data that represents the intensity of touches.
  • the user interface of device 500 can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface operations on device 500.
  • PCT/US2013/040061 titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed November 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety.
  • device 500 has one or more input mechanisms 506 and 508.
  • Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms.
  • device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device 500 to be worn by a user.
  • FIG. 5B depicts exemplary personal electronic device 500.
  • device 500 can include some or all of the components described with respect to FIGS. 1 A, IB, and 3.
  • Device 500 has bus 512 that operatively couples VO section 514 with one or more computer processors 516 and memory 518.
  • I/O section 514 can be connected to display 504, which can have touch-sensitive component 522 and, optionally, intensity sensor 524 (e.g., contact intensity sensor).
  • VO section 514 can be connected with communication unit 530 for receiving application and operating system data, using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and/or other wireless communication techniques.
  • Device 500 can include input mechanisms 506 and/or 508.
  • Input mechanism 506 is, optionally, a rotatable input device or a depressible and rotatable input device, for example.
  • Input mechanism 508 is, optionally, a button, in some examples. [0157]
  • Input mechanism 508 is, optionally, a microphone, in some examples.
  • Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.
  • Memory 518 of personal electronic device 500 can include one or more non- transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described below, including processes 700, 900, 950, and 1100 (FIGS. 7, 9A, 9B, and 11).
  • a computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with the instruction execution system, apparatus, or device.
  • the storage medium is a transitory computer-readable storage medium.
  • the storage medium is a non-transitory computer-readable storage medium.
  • the non- transitory computer-readable storage medium can include, but is not limited to, magnetic, optical, and/or semiconductor storages. Examples of such storage include magnetic disks, optical discs based on CD, DVD, or Blu-ray technologies, as well as persistent solid-state memory such as flash, solid-state drives, and the like.
  • Personal electronic device 500 is not limited to the components and configuration of FIG. 5B, but can include other or additional components in multiple configurations.
  • the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices 100, 300, and/or 500 (FIGS. 1 A, 3, and 5A-5B).
  • an image e.g., icon
  • a button e.g., button
  • text e.g., hyperlink
  • the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting.
  • the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input.
  • a touch-sensitive surface e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B
  • a particular user interface element e.g., a button, window, slider, or other user interface element
  • a detected contact on the touch screen acts as a “focus selector” so that when an input (e.g., a press input by the contact) is detected on the touch screen display at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input.
  • an input e.g., a press input by the contact
  • a particular user interface element e.g., a button, window, slider, or other user interface element
  • focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface.
  • the focus selector is generally the user interface element (or contact on a touch screen display) that is controlled by the user so as to communicate the user’s intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact).
  • a focus selector e.g., a cursor, a contact, or a selection box
  • a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate the respective button (as opposed to other user interface elements shown on a display of the device).
  • the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact).
  • a predefined time period e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds
  • a characteristic intensity of a contact is, optionally, based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like.
  • the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time).
  • the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user.
  • the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold.
  • a contact with a characteristic intensity that does not exceed the first threshold results in a first operation
  • a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation
  • a contact with a characteristic intensity that exceeds the second threshold results in a third operation.
  • a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation), rather than being used to determine whether to perform a first operation or a second operation.
  • 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., become opened) on the device.
  • a downloaded application becomes an installed application by way of an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the operating system of the computer system.
  • open application or “executing application” refer to a software application with retained state information (e.g., as part of device/global internal state 157 and/or application internal state 192).
  • An open or executing application is, optionally, any one of the following types of applications:
  • a background application or background processes
  • a suspended or hibernated application which is not running, but has state information that is stored in memory (volatile and non-volatile, respectively) and that can be used to resume execution of the application.
  • the term “closed application” refers to software applications without retained state information (e.g., state information for closed applications is not stored in a memory of the device). Accordingly, closing an application includes stopping and/or removing application processes for the application and removing state information for the application from the memory of the device.
  • opening a second application while in a first application does not close the first application. When the second application is displayed and the first application ceases to be displayed, the first application becomes a background application.
  • the computer system is in a locked state or an unlocked state.
  • the locked state the computer system is powered on and operational but 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 unintentional or unauthorized use of some functionality of the computer system or activation or deactivation of some functions on the computer system.
  • the unlocked state the computer system is powered on and operational and is not prevented from performing at least a portion of the predefined set of operations that cannot be performed while in the locked state.
  • the computer system 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, the computer system in the locked state optionally responds to a limited set of user inputs, including input that corresponds to an attempt to transition the computer system to the unlocked state or input that corresponds to powering the computer system off.
  • UI user interfaces
  • portable multifunction device 100 such as portable multifunction device 100, device 300, or device 500.
  • FIGS. 6A-6Q illustrate exemplary user interfaces for tracking body temperature information, in accordance with some embodiments.
  • the user interfaces in these figures are used to illustrate the processes described below, including the processes in FIG. 7.
  • FIG. 6A illustrates electronic device 600 with touch-sensitive display 602.
  • electronic device 600 displays health summary user interface 604, which displays various sets of health information pertaining to a user (e.g., a user of electronic device 600 and/or a user that is logged into electronic device 600).
  • Health summary user interface 604 includes selectable options 606a-606g.
  • Option 606a displays heart rate information pertaining to the user (e.g., the user’s heart rate was measured at 82 bpm at 9:41am), and is selectable to display additional heart rate information that is not displayed in health summary user interface 604 (e.g., additional and/or earlier heart rate measurements).
  • Option 606b displays body (e.g., wrist) temperature information pertaining to the user, and is selectable to display additional body temperature information that is not displayed in health summary user interface 604.
  • option 606b indicates that wrist data temperature pertaining to the user has not yet been collected and/or there is no wrist temperature data available for the user.
  • Option 606c displays calorie information pertaining to the user (e.g., 1482 calories burned on April 22), and is selectable to display additional calorie information not shown in health summary user interface 604 (e.g., calorie information for previous days).
  • Option 606d displays active calorie information pertaining to the user (e.g., 249 active calories burned on April 22), and is selectable to display additional active calorie information not shown in health summary user interface 604 (e.g., active calorie information for previous days).
  • Option 606e displays steps information pertaining to the user (e.g., 2,945 steps taken on April 22), and is selectable to display additional steps information not shown in health summary user interface 604 (e.g., steps taken on previous and/or other days).
  • Option 606f is selectable to display a user interface through which a user can access additional health information that is not displayed in health summary user interface 604.
  • Option 606g is selectable to initiate a process for modifying the health information that is displayed in health summary user interface 604 (e.g., remove information that is currently included in health summary user interface 604 and/or add other information that is not currently included in health summary user interface 604).
  • Electronic device 600 also displays selectable options 608a-608c.
  • Option 608a is selectable to display health summary user interface 604.
  • Option 608b is selectable to display a health information sharing user interface, in which a user can view health information that the user is sharing with other users (e.g., other users that the user has selected and/or identified) and/or other user’s health information that the other users have elected to share with the user of electronic device 600.
  • Option 608c is selectable to browse additional health information pertaining to the user.
  • electronic device 600 detects user input 610 (e.g., a touch input and/or a tap input) corresponding to selection of option 606b.
  • user input 610 e.g., a touch input and/or a tap input
  • electronic device 600 displays wrist temperature user interface 612.
  • Wrist temperature user interface 612 displays body temperature information (e.g., wrist temperature information) that has been collected from the user.
  • 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 and/or y degrees below a baseline temperature) rather than absolute body temperature information.
  • Wrist temperature user interface 612 includes options 614a-614c that are selectable to cause body temperature data for different timeframes to be displayed within data chart 614d.
  • option 614a is selectable to view a week of body temperature data within data chart 614d
  • option 614b is selectable to display a month of body temperature data within data chart 614d
  • option 614c is selectable to display six months of body temperature data within data chart 614d.
  • Wrist temperature user interface 612 also includes option 614h that is selectable to return to health summary user interface 604, and option 614g that is selectable to initiate a process for manually adding body temperature data.
  • electronic device 600 displays, within wrist temperature user interface 612, notification 614e.
  • Notification 614e instructs the user to wear his or her watch to bed, and also instructs the user to enable a sleep tracking function (e.g., a sleep focus state, as will be described in greater detail below) in order to log body temperature information.
  • Electronic device 600 also displays option 614f that is selectable to initiate a process for setting up and/or enabling the sleep tracking function.
  • electronic device 600 detects user input 616 (e.g., a touch input and/or a tap input) corresponding to selection of option 614f.
  • 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 are selectable to cause sleep data for different timeframes to be displayed within data chart 620d.
  • option 620a is selectable to view a week of sleep data within data chart 620d
  • option 620b is selectable to view a month of sleep data within data chart 620d
  • option 620c is selectable to view six months of sleep data within data chart 620d.
  • the user has not yet taken the appropriate steps to log sleep data. Accordingly, there is no data shown in data chart 620d.
  • Sleep tracking user interface 618 also includes option 620e that is selectable to display additional sleep data that is not shown in sleep tracking user interface 618, option 620i that is selectable to display health summary user interface 604, and option 620j that is selectable to initiate a process for manually adding and/or logging sleep data.
  • 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 FIG. 6C, the user has specified that the user intends to sleep from 11 :00pm that day until 6:00am the next day.
  • Option 620g is selectable to modify the next sleep cycle (e.g., to specify a start time and/or an end time for the user’s next sleep cycle).
  • Full sleep schedule information 620h identifies the full weekly sleep schedule that the user has specified, and is selectable to modify the user’s weekly sleep schedule (e.g., to specify, for each day of the week, the user’s intended and/or desired sleep start time and sleep end time).
  • the user has defined a sleep schedule that starts at 11 :00pm and ends at 6:00am every day of the week.
  • the user is able to specify different sleep start times and different sleep end times for different days (e.g., for different days of the week).
  • FIG. 6C demonstrated that the user has set up a daily sleep schedule.
  • FIGS. 6D- 6G will now demonstrate an example scenario, according to some embodiments, in which the user enables sleep data logging and also enables body temperature information to be measured and logged while the user is sleeping.
  • electronic device 600 displays settings user interface 622.
  • Settings user interface 622 displays various device settings for electronic device 600, including option 624 that is selectable to modify settings for one or more focus states of electronic device 600, which will be described in greater detail below.
  • the one or more focus states includes a sleep focus state, which is also referred to herein as a sleep tracking state.
  • a sleep focus state which is also referred to herein as a sleep tracking state.
  • electronic device 600 detects user input 626 (e.g., a touch input and/or a tap input) corresponding to selection of option 624.
  • user input 626 e.g., a touch input and/or a tap input
  • electronic device 600 displays focus user interface 628.
  • Focus user interface 628 includes options 630a-630d corresponding to different focus states of electronic device 600.
  • Option 630a corresponds to a do not disturb focus state
  • option 630b corresponds to a sleep focus state
  • option 630c corresponds to a personal focus state
  • option 63 Od corresponds to a work focus state.
  • Each of these options is selectable to modify one or more settings for the corresponding focus state.
  • a focus state can be selectively enabled by a user to indicate that the user does not wish to be disturbed while the focus state is enabled.
  • a focus state of electronic device 600 is enabled (e.g., any of the four focus states in FIG. 6E)
  • one or more notifications that would normally be displayed and/or otherwise output are suppressed and are not output by electronic device 600, as will be described in greater detail below.
  • electronic device 600 when a focus state is not enabled, and electronic device 600 receives a message (e.g., a text message) from another user, electronic device 600 displays a notification corresponding to the message.
  • a focus state when a focus state is enabled, in some embodiments, electronic device 600 does not display notifications corresponding to received messages, as will be described in greater detail below.
  • different focus states result in different settings being applied. For example, in some embodiments, a first focus state will allow notifications from a certain set of users but a second focus state will not allow notifications from those users.
  • the sleep focus state will cause suppression of notifications and collection of body temperature information, whereas a different focus state (e.g., do not disturb and/or work) will cause suppression of notifications without collection of body temperature information.
  • Focus user interface 630e includes toggle 630e.
  • toggle 630e When toggle 630e is toggled to an enabled (or “on”) state, and electronic device 600 enters a particular focus state (e.g., begins operating in the particular focus state) (e.g., automatically and/or based on user input), one or more external devices corresponding to electronic device 600 (e.g., other devices corresponding to the same user) are also caused to enter the particular focus state such that notifications that are suppressed on electronic device 600 during the focus state are also suppressed on other corresponding devices.
  • a particular focus state e.g., begins operating in the particular focus state
  • external devices corresponding to electronic device 600 e.g., other devices corresponding to the same user
  • Focus user interface 628 also includes option 630f that is selectable to return to settings user interface 622.
  • electronic device 600 detects user input 632 (e.g., a touch input and/or a tap input) corresponding to selection of option 630b.
  • Sleep focus user interface 634 includes various options 636a-636h that are selectable to modify one or more settings corresponding to a sleep focus state of electronic device 600.
  • Option 636a is selectable by a user to turn on a sleep focus state (e.g., to cause electronic device 600 to enter and/or operate in the sleep focus state) or to turn off the sleep focus state (e.g., to cause electronic device 600 to exit and/or cease operating in the sleep focus state).
  • option 636a is in the off position, indicating that electronic device 600 is not operating in the sleep focus state (and notifications are not suppressed).
  • Option 636b is selectable to initiate a process for identifying one or more people (e.g., one or more contacts) that are permitted to disturb the user while the sleep focus state is enabled (e.g., on and/or active).
  • the sleep focus state is enabled (e.g., on and/or active).
  • a user selects a first contact as being permitted to disturb the user while the sleep focus state is active
  • electronic device 600 will output a notification (e.g., display a notification, output an audio notification, and/or output haptic notification) as if the sleep focus state was not active.
  • a notification e.g., display a notification, output an audio notification, and/or output haptic notification
  • option 636c is selectable to initiate a process for identifying one or more applications that are permitted to disturb the user while the sleep focus state is active (e.g., while electronic device 600 is operating in the sleep focus state).
  • Option 636d is selectable to open a user interface in which the user can enable or disable a focus status setting.
  • the focus status setting is enabled, other users (e.g., other users attempting to contact the user of electronic device 600) are able to see an indication when the sleep focus state is active for electronic device 600 (e.g., an indication that electronic device 600 is operating in the sleep focus state and/or has suppressed notifications).
  • the focus status setting is disabled, other users are not able to see when electronic device 600 is operating in the sleep focus state.
  • Option 636e is selectable to display a user interface in which the user can enable or disable a home screen notifications setting.
  • notifications that would normally be displayed on a home screen of electronic device 600 are also displayed on the home screen of electronic device 600 when the sleep focus state is active.
  • notifications that would normally be displayed on the home screen of electronic device 600 are suppressed (e.g., not displayed) when the sleep focus state is active.
  • Option 636f is selectable to display a user interface in which the user can enable or disable a lock screen notifications setting.
  • notifications that would normally be displayed on a lock screen of electronic device 600 are also displayed on the lock screen of electronic device 600 when the sleep focus state is active.
  • the lock screen notifications 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 state is active.
  • Option 636g is selectable by a user to toggle option 636g between an on state and an off state.
  • electronic device 600 automatically enters and/or exits the sleep focus state according to a user-specified sleep schedule (e.g., electronic device 600 automatically enters (e.g., activates) the sleep focus state at a user specified bed time, and electronic device 600 automatically exits (e.g., deactivates) the sleep focus state at a user specified wake time).
  • a user-specified sleep schedule e.g., electronic device 600 automatically enters (e.g., activates) the sleep focus state at a user specified bed time, and electronic device 600 automatically exits (e.g., deactivates) the sleep focus state at a user specified wake time).
  • electronic device 600 does not automatically enter and/or exit the sleep focus state according to the user-specified sleep schedule, and the user must manually activate or deactivate the sleep focus state (e.g., using option 636a).
  • Option 636h is selectable by a user to toggle option 636h between an on state and an off state.
  • electronic device 600 collects body temperature information while the user is sleeping (e.g., while electronic device 600 is in the sleep focus state).
  • option 636h is in an off state, electronic device 600 does not collect body temperature information and/or does not log body temperature information while the user is sleeping (e.g., while electronic device 600 is in the sleep focus state).
  • Sleep focus user interface 634 also includes option 636i, which displays next sleep schedule information and is selectable to modify next sleep schedule information (similar to next sleep schedule information 620f and option 620g in FIG.
  • Sleep focus user interface 634 also includes options 636k-636m.
  • Option 636k is selectable to display sleep tracking user interface 618.
  • Option 6361 is selectable to initiate a process for deleting (e.g., removing) the sleep focus state from electronic device 600.
  • Option 636m is selectable to display focus user interface 628.
  • electronic device 600 detects user input 638a (e.g., a touch input and/or a tap input) corresponding to selection of option 636a, user input 638b (e.g., a touch input and/or a tap input) corresponding to selection of option 636g, and user input 638c (e.g., a touch input and/or a tap input) corresponding to selection of option 636h.
  • user input 638a e.g., a touch input and/or a tap input
  • user input 638b e.g., a touch input and/or a tap input
  • user input 638c e.g., a touch input and/or a tap input
  • options 636a, 636g, and 636h have each been toggled into the “on” position.
  • Option 636a being toggled to the on position indicates that the sleep focus state has been activated and electronic device 600 is now operating in the sleep focus state.
  • Option 636g being toggled to the on position indicates that electronic device 600 will automatically enter and exit the sleep focus state according to the user-specified sleep schedule.
  • Option 636h being toggled to the on position indicates that 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 smart watch or other temperature sensor) when electronic device 600 is operating in the sleep focus state.
  • lock screen user interface 640 includes indication 642a, which indicates that electronic device 600 is in a locked state.
  • Lock screen user interface 640 also includes current time information 642b, current date information 642c, object 642g that is selectable to selectively enable or disable a flashlight, and object 642f that is selectable to display a camera user interface.
  • electronic device 600 is operating in the sleep focus state. For example, electronic device 600 enters the sleep focus state in response to user input 638a or, in another example, electronic device 600 automatically enters the sleep focus state based on option 636g in FIG. 6G being toggled to an on state and in response to a user-defined sleep schedule.
  • Electronic device 600 displays indication 642d indicating that electronic device 600 is in the sleep focus state.
  • Electronic device 600 also displays alarm indication 642e indicating that the user has not set a wake alarm. In some embodiments, when the user has set a wake alarm, alarm indication 642e displays the time at which the wake alarm will go off.
  • FIG. 6H also depicts electronic device 800, which is a smart watch with touchscreen display 802, rotatable and depressible input mechanism 804, and button 806.
  • Electronic device 644 displays lock screen user interface 644, indicating that electronic device 800 is in a locked.
  • Lock screen user interface includes current time indication 646a and current date indication 646b.
  • electronic device 800 is also operating in the sleep focus state, as indicated by indication 646d. For example, in some embodiments, as a result of option 63 Oe of FIG. 6D being in the on position, when electronic device 600 enters the sleep focus state, electronic device 800 automatically also enters the sleep focus state.
  • Electronic device 800 also displays alarm indication 646c, similar to alarm indication 642e.
  • FIGS. 6H-6I illustrate an example embodiment in which, when an electronic device (e.g., electronic device 600 and/or electronic device 800) is in the sleep focus state, additional user inputs are required to transition the electronic device from the locked state to an unlocked state and/or to cease displaying the lock screen user interface compared to when the electronic device is not operating in the sleep focus state.
  • an electronic device e.g., electronic device 600 and/or electronic device 800
  • electronic device 800 detects user input 648, which is a depression (e.g., press) of rotatable and depressible input mechanism 648.
  • user input 648 is a depression (e.g., press) of rotatable and depressible input mechanism 648.
  • electronic device 600 receives biometric information corresponding to the user (e.g., a facial scan and/or facial image) via input device 601 (e.g., a camera and/or depth sensor).
  • electronic device 800 in response to user input 648, displays user interface 650, which instructs the user to turn rotatable and depressible input mechanism 804 in order to unlock electronic device 800.
  • user input 648 would be sufficient to unlock electronic device 800.
  • electronic device 600 in response to receiving biometric information from the user, displays indication 642a as an unlocked lock, indicating that the biometric information from the user successfully authenticated the user.
  • an upward swipe would be sufficient to cease display of lock screen user interface 640 and unlock electronic device 600.
  • additional user input is required to cease display of lock screen user interface.
  • a user is first required to press object 642h, and then provide an upward swipe input, and/or the user is required to provide two upward swipe inputs.
  • electronic device 600 displays health summary user interface 604, which was described above with reference to FIG. 6A. However, now that the user has enabled body temperature logging (e.g., by enabling option 636h in FIG. 6G), option 606b now indicates that electronic device 600 is “collecting data.” At FIG. 6J, electronic device 600 detects user input 652 (e.g., a touch input and/or a tap input) corresponding to selection of option 606b.
  • user input 652 e.g., a touch input and/or a tap input
  • electronic device 600 displays wrist temperature user interface 612. Now that the user has enabled body temperature logging, wrist temperature user interface 612 no longer displays notification 614e, as was shown in FIG. 6B. However, in FIG. 6K, electronic device 600 has not collected sufficient body temperature data to accurately determine a baseline temperature for the user. As such, wrist temperature user interface 612 still does not display any actual body temperature data in data chart 614d, and displays notification 654 indicating that more body temperature information is needed.
  • wrist temperature user interface 612 now displays user body temperature data in data chart 614d, and no longer displays notification 654.
  • additional options 656a-656c in wrist temperature user interface 612 are shown.
  • options 656a-656c were part of wrist temperature user interface 612 in the previous figures, but were not shown in those figures.
  • Option 656a is selectable to selectively enable or disable display of body temperature information within health summary user interface 604.
  • Option 656b is selectable to display additional body temperature information that is not shown in wrist temperature user interface 612.
  • Option 656c is selectable to view information pertaining to one or more external devices from which body temperature information for the user was collected (e.g., one or more watches and/or other wearable devices or sensors that were used to collect user body temperature information).
  • one or more external devices from which body temperature information for the user was collected e.g., one or more watches and/or other wearable devices or sensors that were used to collect user body temperature information.
  • electronic device 600 detects user input 658a (e.g., a touch input and/or a tap input) corresponding to selection of option 614b, user input 658b (e.g., a touch input and/or a tap input) corresponding to selection of a data point in data chart 614d, and user input 658c (e.g., a touch input and/or a tap input) corresponding to selection of option 656b.
  • user input 658a e.g., a touch input and/or a tap input
  • user input 658b e.g., a touch input and/or a tap input
  • user input 658c e.g., a touch input and/or a tap input
  • electronic device 600 displays data box 660.
  • User input 658b corresponded to selection of a data point corresponding to the date Friday, June 24, 2022.
  • electronic device 600 displays data box 660, which includes additional information about the data point (e.g., the user’s body temperature on Friday June 24, 2022 was measured to be 0.5 degrees below their baseline temperature).
  • additional information about the data point e.g., the user’s body temperature on Friday June 24, 2022 was measured to be 0.5 degrees below their baseline temperature.
  • a user is able to select any of the data points displayed in data chart 614d to view additional information pertaining to the selected data point.
  • electronic device 600 displays a month of user body temperature data within data chart 614d. Similar to what was shown in FIG. 6M, a user is able to select any data point within data chart 614d to view additional information about the selected data point.
  • User interface 662 includes representations 664a-664g of a plurality of body temperature information collection instances.
  • representation 664a is representative of a first body temperature information collection instance that occurred on June 25, 2022
  • representation 664b is representative of a second body temperature information collection instance that occurred on June 24, 2022, and so forth.
  • user interface 662 includes representations of all instances in which body temperature information was collected from the user, or representations of all body temperature information collection instances that occurred within a predetermined period of time (e.g., in 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 is selectable to return to wrist temperature user interface 612.
  • electronic device 600 detects user input
  • electronic device 600 displays user interface 668.
  • User interface 668 displays additional information pertaining to the selected body temperature information collection instance.
  • user interface 668 includes start time information 670b (e.g., the time at which body temperature information collection begin for this particular collection instance), end time information 670c (e.g., the time at which body temperature information collection ended for this particular collection instance), and data addition information 670e (e.g., the date and time on which the body temperature information was received by electronic device 600 from an external device).
  • User interface 668 also includes source information 670d identifying the external device which collected the body temperature information and/or the external device from which the body temperature information was received.
  • electronic device 600 aggregates body temperature information collected by and/or received from a plurality of external devices.
  • wrist temperature user interface 612 displays body temperature information collected by and/or received from a plurality of external devices.
  • User interface 668 also includes surface temperature information 670f and wrist temperature information 670a. As discussed above, wrist temperature user interface 612 displays baseline temperature information, and does not display actual temperature measurements (e.g., the actual measured temperature). However, user interface 668 displays surface temperature information 670f, which indicates the actual temperature that was measured at the surface of the user’s skin, and wrist temperature information 670a, which indicates the user’s body temperature as derived from surface temperature information 670f.
  • electronic device 600 displays wrist temperature user interface 612.
  • the user has not been consistently wearing his or her wearable device to sleep and, as such, electronic device 600 has not been able to consistently collect body temperature information while the user is sleeping.
  • electronic device 600 has determined that electronic device 600 does not have sufficient 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 of time (e.g., in the last week, in the last month, etc.)).
  • electronic device 600 ceases displaying body temperature information in data chart 614d, and displays indication 672, which informs the user that electronic device 600 does not have sufficient body temperature information, and instructs the user to consistently wear his or her wearable device to sleep.
  • FIG. 7 is a flow diagram illustrating a method for tracking body temperature information using a computer system in accordance with some embodiments.
  • Method 700 is performed at a computer system (e.g., 100, 300, 500) (e.g., a wearable device, a smart watch, a smart phone, a tablet, and/or a computer system controlling an external display) (e.g., 600, 800) that is in communication with a display generation component (e.g., a display controller, a touch-sensitive display system; and/or a display (e.g., integrated and/or connected)) (e.g., 602, 802), one or more input devices (e.g., a touch- sensitive surface (e.g., a touch-sensitive display); an accelerometer; a rotatable input mechanism; a depressible input mechanism; and/or a rotatable and depressible input mechanism) (e.g., 601, 602, 802, 804, 806), and a temperature sensor (e.
  • method 700 provides an intuitive way for tracking body temperature information.
  • the method reduces the cognitive burden on a user for tracking body temperature information, thereby creating a more efficient human-machine interface.
  • the computer system receives (702), via the 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 one or more user inputs defining a sleep schedule (e.g., sleep schedule shown in 636i, 636j)) (e.g., a mode and/or state in which one or more notifications (e.g., notifications of a first type) received by the computer system are suppressed and/or in which information pertaining to the sleep (e.g., sleep quality) of a user is collected).
  • an input e.g., a first set of user inputs and/or one or more user inputs
  • a sleep tracking mode
  • the computer system 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 the sleep tracking). In some embodiments, entering the sleep tracking mode includes initiating a process to collect user body temperature information.
  • the computer system causes a first set of user body temperature information (e.g., user body temperature information displayed in data chart 614d) (e.g., one or more user body temperature measurements) to be collected via the temperature sensor (e.g., a temperature sensor integrated into electronic device 800).
  • the computer system receives (708) notification data of a first type (e.g., notifications of a type that are subject to being suppressed while in a sleep tracking mode) (in some embodiments, all notifications are suppressed in the sleep tracking mode) (in some embodiments, notifications of a second type (e.g., emergency notifications, wake alarm notifications), are not suppressed while in the sleep tracking mode).
  • a first type e.g., notifications of a type that are subject to being suppressed while in a sleep tracking mode
  • all notifications are suppressed in the sleep tracking mode
  • notifications of a second type e.g., emergency notifications, wake alarm notifications
  • the computer system In response to receiving the notification data of the first type (710): in accordance with a determination that the computer system is not in the sleep tracking mode (712), the computer system outputs a first notification (e.g., displays a first notification; causes the display generation component to transition from an inactive state (e.g., off and/or a state in which content is not displayed on the display generation component) to an active state (e.g., on and/or a state in which content is displayed); outputs an audio output; and/or outputs a haptic output) corresponding to the notification data of the first type; and in accordance with a determination that the computer system is currently in the sleep tracking mode (714) (e.g., FIGS.
  • 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 generation component to transition from an inactive state to an active state; forgoes outputting an audio output; and/or forgoes outputting a haptic output).
  • the first notification 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.
  • the computer system displays, via display generation component (e.g., 602), a body temperature user interface (e.g., 612) that includes representations of one or more sets of user body temperature information (e.g., body temperature information displayed in data chart 614d in FIG. 6L) (e.g., user body temperature information associated with a user of the computer system, collected from the user of the computer system and/or collected by the computer system) including the first set of user body temperature information (e.g., a body temperature user interface that depicts representations of a user’s body temperature (e.g., depicts and/or demonstrates changes in the user’s body temperature) over a period of time).
  • display generation component e.g., 602
  • a body temperature user interface e.g., 612
  • representations of one or more sets of user body temperature information e.g., body temperature information displayed in data chart 614d in FIG. 6L
  • user body temperature information associated with a user of the computer system e.g.
  • the computer system receives, via the 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 (e.g., do not disturb, personal focus state, and/or work focus state in FIG.
  • a second input e.g., a second set of user inputs and/or one or more user inputs
  • a first silent mode e.g., do not disturb, personal focus state, and/or work focus state in FIG.
  • the computer system in response to receiving the second input, enters the first silent mode (enabling the first silent mode and/or causing the computer system to operate in the first silent mode) (in some embodiments, without entering the sleep tracking mode) without initiating a process to collect body temperature information.
  • the computer system collects body temperature information while forgoing storing body temperature information and/or collects body temperature information of a second type while forgoing collecting and/or storing body temperature information of a third type.
  • the computer system receives second notification data of the first type.
  • the computer system in response to receiving the second notification data of the first type: in accordance with a determination that the computer system is not in the first silent mode (e.g., the do not disturb state, the personal focus state, and/or the work focus state in FIG. 6E are not active and/or enabled) and that the computer system is not in the sleep tracking mode (e.g., the sleep focus state in FIG.
  • the computer system outputs a second notification (e.g., displays a second notification; causes the display generation component to transition from an inactive state (e.g., off and/or a state in which content is not displayed on the display generation component) to an active state (e.g., on and/or a state in which content is displayed); outputs an audio output; and/or outputs a haptic output) corresponding to the second notification data of the first type; and in accordance with a determination that the computer system is currently in the first silent mode (e.g., at least one of the do not disturb state, the personal focus state, and/or the work focus state in FIG.
  • 6E is active and/or enabled) (e.g., that the computer system is in the first silent mode when the second notification data of the first type is received), the computer system forgoes outputting (e.g., suppresses) a notification corresponding to the second notification data of the first type (e.g., forgoes displaying the second 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 first silent mode allows a user to perform this operation with fewer user inputs, thereby reducing the number of user inputs required to perform an operation.
  • automatically collecting temperature information when the computer system is in the sleep tracking mode, and forgoing collecting temperature information when the computer system is in the first silent mode allows a user to perform these operations with fewer user inputs.
  • the computer system receives, via the one or more input devices, a third input (e.g., a third set of user inputs and/or one or more user inputs) (e.g., one or more touch inputs, one or more non-touch inputs, and/or one or more gestures) corresponding to a request to define a sleep schedule (e.g., sleep schedule shown in FIG. 6C (e.g., 620f, 620h) and/or FIG.
  • a third input e.g., a third set of user inputs and/or one or more user inputs
  • a sleep schedule e.g., sleep schedule shown in FIG. 6C (e.g., 620f, 620h) and/or FIG.
  • the sleep schedule includes, for at least a first day (e.g., a first day of the week (e.g., Sunday, Monday, Tuesday, etc.) and/or a first calendar date), a first sleep start time and a first sleep end time.
  • the sleep schedule includes, for a second day (e.g., a second day of the week and/or a second calendar date) different from the first day, a second sleep start time and a second sleep end time.
  • the computer system in accordance with a determination that a current time corresponds to the first sleep start time (e.g., is the first sleep start time), the computer system enters the sleep tracking mode (e.g., sleep focus state in FIGS. 6H-6I); and in accordance with a determination that the current time does not correspond to the first sleep start time (e.g., is not the first sleep start time), the computer system forgoes entering the sleep tracking mode (e.g., maintains the computer system in a non-sleep tracking mode and/or maintains the computer system in the sleep tracking mode).
  • the sleep schedule defines sleep start times and sleep end times for a plurality of days.
  • the sleep start times and/or the sleep end times are the same for two or more days of the plurality of days. In some embodiments, the sleep start times and/or the sleep end times are different for two or more days of the plurality of days.
  • the computer system subsequent to receiving the third input, and in accordance with a determination that a current time corresponds to the first sleep end time (e.g., 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 engaging a 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 an operation.
  • causing the first set of user body temperature information (e.g., user body temperature information shown in chart 614d) to be collected includes: causing a first external device (e.g., 800) (e.g., a wearable device, a smart watch, a smart phone, a tablet, and/or a computer system controlling an external display) separate from the computer system (e.g., 600) 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).
  • a first external device e.g. 800
  • a wearable device e.g., a smart watch, a smart phone, a tablet, and/or a computer system controlling an external display
  • receiving the first set of user body temperature information from the first external device e.g., via wireless and/or wired transmission
  • the computer system displays, via the display generation component, the body temperature user interface (e.g., 612), including: in accordance with a determination that a threshold amount of body temperature information (e.g., user body temperature information associated with a user of the computer system, collected from the user of the computer system and/or collected by the computer system) has not been collected (e.g., FIG. 6K) (e.g., less than a threshold number of days of body temperature information has been collected and/or less than a threshold number of hours of body temperature information has been collected), displaying an indication that the threshold amount of body temperature information has not been collected (e.g., data chart 614d in FIG.
  • a threshold amount of body temperature information e.g., user body temperature information associated with a user of the computer system, collected from the user of the computer system and/or collected by the computer system
  • FIG. 6K e.g., less than a threshold number of days of body temperature information has been collected and/or less than a threshold number of hours of body temperature information has
  • 6K and/or 654 (and, in some embodiments, forgoing displaying representations of one or more sets of user body temperature information (e.g., collected from the user and/or by the computer system)); and in accordance with a determination that the threshold amount of body temperature information has been collected (e.g., FIG. 6L), displaying representations of one or more sets of user body temperature information (e.g., body temperature information displayed in data chart 614d in FIG. 6L) (e.g., user body temperature information associated with a user of the computer system, collected from the user and/or collected by the computer system) without displaying the indication that the threshold amount of body temperature information has not been collected (e.g., 654).
  • Displaying the indication that the threshold amount of body temperature information has not been collected provides the user with visual feedback about the state of the system (e.g., that the system has not yet collected the threshold amount of body temperature information), thereby providing improved visual feedback to the user.
  • the computer system displays a second instance of the body temperature user interface (e.g., 612), wherein: in accordance with a determination that a second set of criteria are satisfied (e.g., in accordance with a determination that body temperature collection frequency criteria are satisfied (e.g., a threshold amount of body temperature information has been collected in a defined period of time (e.g., the immediately preceding week, month, three months, six months, and/or year))), the second instance of the body temperature user interface includes representations of a second set of user body temperature information (e.g., an updated version of FIG.
  • the second instance of the body temperature user interface does not include the representations of the second set of user body temperature information (e.g., user interface 612 displaying data chart 614d in FIG.
  • the second set of criteria includes a second indication indicating that the second set of criteria are not satisfied (e.g., data chart 614d in FIG. 6Q and/or 672) (e.g., indicating that collection of body temperature information is too sporadic and/or infrequent). Displaying the indication that the second set of criteria are not satisfied provides the user with visual feedback about the state of the system (e.g., that the system has determined that the second set of criteria are not satisfied), thereby providing improved visual feedback to the user.
  • a second indication indicating that the second set of criteria are not satisfied e.g., data chart 614d in FIG. 6Q and/or 672
  • Displaying the indication that the second set of criteria are not satisfied provides the user with visual feedback about the state of the system (e.g., that the system has determined that the second set of criteria are not satisfied), thereby providing improved visual feedback to the user.
  • the computer system while displaying the body temperature user interface (e.g., 612), the computer system receives, via the one or more input devices, a selection input (e.g., 658a) (e.g., one or more touch inputs, one or more non-touch inputs, and/or one or more gestures).
  • a selection input e.g., 658a
  • the computer system receives, via the one or more input devices, a selection input (e.g., 658a) (e.g., one or more touch inputs, one or more non-touch inputs, and/or one or more gestures).
  • the computer system In response to receiving the selection input: in accordance with a determination that the selection input corresponds to selection of a first timeframe option (e.g., 614a, 614b, 614c) corresponding to a first timeframe (e.g., a first duration of time (e.g., a week, a month, six months, and/or a year)), the computer system displays, within the body temperature user interface, representations of one or more sets of user body temperature information corresponding to the first timeframe (e.g., in FIG. 6L user interface 612 displays body temperature information for a weekly timeframe, in FIG.
  • a first timeframe option e.g., 614a, 614b, 614c
  • a first timeframe e.g., a first duration of time (e.g., a week, a month, six months, and/or a year)
  • the computer system displays, within the body temperature user interface, representations of one or more sets of user body temperature information corresponding to the
  • user interface 612 displays body temperature information for a monthly timeframe) (e.g., collected during the first timeframe and/or collected during the first duration of time corresponding to the first timeframe option) (and, optionally, without displaying representations of user body temperature information collected outside of the first timeframe and/or outside of the first duration of time corresponding to the first timeframe option); and in accordance with a determination that the selection input corresponds to selection of a second timeframe option (e.g., 614a, 614b, 614c) different from the first timeframe option, wherein the second timeframe option corresponds to a second timeframe (e.g., a second duration of time (e.g., a week, a month, six months, and/or a year)) different from the first timeframe, the computer system displays, within the body temperature user interface, representations of one or more sets of user body temperature information corresponding to the second timeframe (e.g., in FIG.
  • user interface 612 displays body temperature information for a weekly timeframe, in FIG. 6N, user interface 612 displays body temperature information for a monthly timeframe) (e.g., collected during the second timeframe and/or collected during the second duration of time corresponding to the second timeframe option) (and, optionally, without displaying representations of user body temperature information collected outside of the second timeframe and/or outside of the second duration of time corresponding to the second timeframe option).
  • Providing different selectable options corresponding to different timeframes that allows a user to display body temperature information corresponding to different timeframes allows for a user to view different sets of body temperature information with fewer user inputs, thereby reducing the number of user inputs required to perform an operation.
  • the representations of one or more sets of user body temperature information includes one or more relative temperature measurements (e.g., data chart 614 in FIGS. 6L, 6M, and 6N 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 a baseline temperature) (and, optionally, does not include absolute temperature measurements).
  • relative temperature measurements e.g., data chart 614 in FIGS. 6L, 6M, and 6N 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 a baseline temperature) (and, optionally, does not include absolute temperature measurements).
  • the computer system displays, via the display generation component, a first details user interface (e.g., 668) corresponding to the first set of user body temperature information, wherein the first details 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, make, and/or model of an external device used to collect the first set of user body temperature information)).
  • the first details 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 computer system displays a second details user interface corresponding to a second set of user body temperature information different from the first set of user body temperature information, wherein the second details user interface includes information about the second set of user body temperature information that is not displayed in the body temperature user interface.
  • Displaying a first details user interface provides the user with visual feedback about the state of the system (e.g., that the system has collected additional information about the first set of user body temperature information that is not included in the body temperature user interface), thereby providing improved visual feedback to the user.
  • Providing the first details user interface in which a user can view additional details about the first set of user body temperature information allows the user to perform this operation with fewer user inputs.
  • the first details user interface (e.g., 668) includes: a start time (e.g., 670b) corresponding to the first set of user body temperature information (e.g., a time and/or a date on which collection of the first set of user body temperature information started); and an end time (e.g., 670c) corresponding to the first set of user body temperature information (e.g., a time and/or a date on which collection of the first set of user body temperature information ended).
  • a start time e.g., 670b
  • an end time e.g., 670c
  • Displaying a first details user interface provides the user with visual feedback about the state of the system (e.g., that the system has collected additional information about the first set of user body temperature information that is not included in the body temperature user interface), thereby providing improved visual feedback to the user.
  • Providing the first details user interface in which a user can view additional details about the first set of user body temperature information allows the user to perform this operation with fewer user inputs.
  • 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); and 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., actual measured body temperature and/or measurements indicative of the actual body temperature of the user).
  • Displaying a first details user interface provides the user with visual feedback about the state of the system (e.g., that the system has collected additional information about the first set of user body temperature information that is not included in the body temperature user interface), thereby providing improved visual feedback to the user.
  • Providing the first details user interface in which a user can view additional details about the first set of user body temperature information allows the user to perform this operation with fewer user inputs.
  • 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 pertaining to an external device (e.g., separate from the computer system) that was used to collect the first set of user body temperature information (e.g., name, model, and/or other identifier of external device)).
  • Displaying a first details user interface provides the user with visual feedback about the state of the system (e.g., that the system has collected additional information about the first set of user body temperature information that is not included in the body temperature user interface), thereby providing improved visual feedback to the user.
  • Providing the first details user interface in which a user can view additional details about the first set of user body temperature information allows the user to perform this operation with fewer user inputs.
  • the computer system 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).
  • 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
  • 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.
  • the computer system In response to receiving the first notification data: in accordance with a determination that the computer system is not in the sleep tracking mode (e.g., option 636a is in the inactive and/or off state) (e.g., when the first notification data is received), the computer system outputs a second notification (e.g., displays a second notification; causes the display generation component to transition from an inactive state (e.g., off and/or a state in which content is not displayed on the display generation component) to an active state (e.g., on and/or a state in which content is displayed); outputs an audio output; and/or outputs a haptic output) corresponding to the first notification data; and in accordance with a determination that the computer system is currently in the sleep tracking mode (e.g., option 636a is in the active and/or on state) (e.g., when the first notification data is received), and that the first notification data comprises notification data of a second type (e.g., notification data that is suppressed while the
  • 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 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 pertaining to messages received from other users or applications when the computer system is in the sleep tracking mode allows a user to perform these operations with fewer user inputs.
  • the first notification data in response to receiving the first notification data: in accordance with a determination that the computer system is currently in the sleep tracking mode (e.g., option 636a is in the active and/or on state), and that the first notification data comprises notification data of a third type (e.g., notification data that is not suppressed while the computer system is in the sleep tracking mode, notification data corresponding to one or more messages received from a second subset of external users (e.g., a preapproved and/or preselected subset of external users) (e.g., users identified in object 636b in FIG.
  • a third type e.g., notification data that is not suppressed while the computer system is in the sleep tracking mode
  • notification data corresponding to one or more messages received from a second subset of external users e.g., a preapproved and/or preselected subset of external users
  • the computer system outputs the second notification corresponding to the first notification data.
  • a second subset of applications e.g., a preapproved and/or preselected subset of external users
  • applications identified in object 636c in FIG. 6F different from the first subset
  • the computer system outputs the second notification corresponding to the first notification data.
  • the computer system in accordance with a determination that the computer system is in the sleep tracking mode (e.g., option 636a is in the active and/or on state), the computer system causes a second external device (e.g., 1070) (e.g., a second external device corresponding to a second user different from a user of the computer system) different from the computer system (e.g., separate from 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 in the activated and/or engaged state).
  • a second external device e.g., 1070
  • the computer system e.g., separate from the computer system
  • the computer system while the computer system is not in the sleep tracking mode, and in accordance with a determination that the computer system is not in the sleep tracking mode, the computer system forgoes causing and/or does not cause the second external device to display the indication that the computer system is in the sleep tracking mode.
  • Causing the second external device to display the indication that the computer system has suppressed notifications provides the user of the second external device with visual feedback about the state of the computer system (e.g., that the computer system has suppressed notifications), thereby providing improved visual feedback to the user.
  • the representations of one or more sets of user body temperature information includes: a representation of a third set of user body temperature information (e.g., a third period of time during which body temperature information was collected from the user) collected by a second external device (e.g., a wearable device, a smart watch, a smart phone, a tablet, and/or a computer system controlling an external display) separate from the computer system; and a representation of a fourth set of user body temperature information (e.g., a fourth period of time during which body temperature information was collected from the user (e.g., a third period of time different from the second period of time)) different from the second set of user body temperature information and collected by a third external device (e.g., a wearable device, a smart watch, a smart phone, a tablet, and/or a computer system controlling an external display) different from the second external device and the computer system (e.g., a third external device, a wearable device, a smart watch, a smart phone,
  • the body temperature user interface includes and/or aggregates user body temperature information collected by a plurality of external devices (e.g., a plurality of external devices associated with the computer system and/or associated with a particular user of the computer system). Allowing a user to collect body temperature information using multiple external devices improves the user-device interface and helps the user to provide correct inputs.
  • a plurality of external devices e.g., a plurality of external devices associated with the computer system and/or associated with a particular user of the computer system. Allowing a user to collect body temperature information using multiple external devices improves the user-device interface and helps the user to provide correct inputs.
  • method 900, method 950, and/or method 1100 optionally include one or more of the characteristics of the various methods described above with reference to method 700.
  • the body temperature information that is collected in method 700 can be used to generate health-based notifications and/or predictions in methods 900, 950, and/or 1100. For brevity, these details are not repeated below.
  • FIGS. 8A-8K illustrate exemplary user interfaces for generating and providing ovulation date predictions, in accordance with some embodiments.
  • ovulation date predictions are generated based on user body temperature information.
  • the user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 9 A and 9B.
  • FIG. 8A illustrates electronic device 600 with touch-sensitive display 602.
  • FIGS. 8A-8C illustrate example user interfaces that allow a user to provide information (e.g., health information and/or biometric information) pertaining to and/or relevant to menstrual cycle predictions, including ovulation date predictions and fertile window predictions.
  • electronic device 600 displays health factors user interface 807, which asks the user to specify, via options 808a-808d, whether one or more predetermined health factors are applicable to the user.
  • Option 808a is selectable by a user to indicate that the user is pregnant.
  • Option 808b is selectable by a user to indicate that the user is lactating.
  • Option 808c is selectable by a user to indicate that the user is using contraception.
  • Option 808d is selectable by a user to indicate that none of these health factors currently apply to the user and, in FIG. 8A, has been selected by the user.
  • Health factors user interface 807 includes option 808e that is selectable to move to a next user interface (e.g., a next user interface in a series of onboarding user interfaces and/or a next user interface in a series of settings user interfaces), option 808f that is selectable to skip entering predetermined health factor information, option 808g that is selectable to return to a previous user interface, and option 808h that is selectable to cease display of health factors user interface 807.
  • a next user interface e.g., a next user interface in a series of onboarding user interfaces and/or a next user interface in a series of settings user interfaces
  • option 808f that is selectable to skip entering predetermined health factor information
  • option 808g that is selectable to return to a previous user interface
  • option 808h that is selectable to cease display of health factors user
  • electronic device 600 does not generate one or more menstrual cycle predictions (e.g., menstrual period predictions, ovulation date predictions, and/or fertile window predictions) if the user indicates that one or more predetermined health factors are applicable to the user during the relevant prediction time period.
  • menstrual cycle predictions e.g., menstrual period predictions, ovulation date predictions, and/or fertile window predictions
  • electronic device 600 detects user input 810 (e.g., a tap input and/or a touch input) corresponding to selection of option 808e.
  • user input 810 e.g., a tap input and/or a touch input
  • electronic device 600 displays user interface 812.
  • User interface 812 includes option 814a and option 814b.
  • Option 814a is selectable by a user to selectively enable or disable menstrual period predictions.
  • option 814a When option 814a is enabled (e.g., when menstrual period predictions are enabled), 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).
  • option 814a When option 814a is disabled (e.g., when menstrual period predictions are disabled), electronic device 600 does not generate and/or display menstrual period predictions.
  • Option 814b is selectable by a user to selectively enable or disable menstrual period notifications.
  • electronic device 600 When option 814b is enabled (e.g., when menstrual period notifications are enabled), electronic device 600 generates and/or displays notifications (e.g., push notifications, lock screen notifications, and/or banner notifications) that are indicative of a menstrual period prediction (e.g., a prediction of when the user’s next menstrual period will occur).
  • a menstrual period prediction e.g., a prediction of when the user’s next menstrual period will occur.
  • option 814b When option 814b is disabled (e.g., when menstrual period notifications are disabled), electronic device 600 does not generate and/or display notifications (e.g., push notifications, lock screen notifications, and/or banner notifications) pertaining to menstrual period predictions and/or menstrual period data.
  • User interface 812 also includes option 814c that is selectable to display a next user interface (e.g., a next user interface in a series of onboarding user interfaces and/or a next user interface in a series of settings user interfaces), option 814d that is selectable to display a previous user interface (e.g., user interface 807), and option 814e that is selectable to cease display of user interface 812.
  • electronic device 600 detects user input 816 (e.g., a tap input and/or a touch input) corresponding to selection of option 814c.
  • electronic device 600 displays user interface 818.
  • User interface 818 includes options 820a-820g.
  • Option 820a is selectable by a user to selectively enable or disable fertile window predictions.
  • electronic device 600 When option 820a is enabled (e.g., when fertile window predictions are enabled), electronic device 600 generates and displays fertile window predictions (e.g., based on biometric information (e.g., body temperature information) and/or based on the user’s menstrual cycle history).
  • fertile window predictions include one or more of: a prediction of when the user’s next fertile window will occur, a prediction of when the user’s previous fertile window occurred, and/or a prediction of when the user’s current fertile window began.
  • option 820a is disabled (e.g., when fertile window predictions are disabled)
  • electronic device 600 does not generate and/or display fertile window predictions.
  • Option 820b is selectable by a user to selectively enable or disable fertile window notifications.
  • option 820b is enabled (e.g., when fertile window notifications are enabled)
  • electronic device 600 generates and/or displays notifications (e.g., push notifications, lock screen notifications, and/or banner notifications) that are indicative of a fertile window prediction.
  • option 820b When option 820b is disabled, electronic device 600 does not generate and/or display notifications pertaining to fertile window predictions and/or fertile window data.
  • Option 820c is selectable by a user to selectively enable or disable fertility logging.
  • option 820c When option 820c is enabled (e.g., fertility logging is enabled), the user is provided with options (e.g., electronic device 600 displays options) that allow the user to log ovulation tests and other fertility indicators, and displays indications of fertility indicators logged by a user (e.g., within cycle tracking user interface 828, described below).
  • option 820c When option 820c is disabled (e.g., fertility logging is disabled), electronic device 600 does not display and/or provide the user with the option to log ovulation tests and/or other fertility indicators.
  • Option 820d is selectable by a user to selectively enable or disable sexual activity logging.
  • electronic device 600 displays and/or provides the user with options that allow the user to log sexual activity information (e.g., allows the user to identify dates on which the user had sex).
  • option 820d is disabled (e.g., sexual activity logging is disabled)
  • electronic device 600 does not display and/or provide the user with options that allow the user to log sexual activity information.
  • Option 820e is selectable to return to a previous user interface (e.g., user interface 812), option 820f is selectable to cease display of user interface 818, and option 820g is selectable to display a next user interface (e.g., a next user interface in a series of onboarding user interfaces and/or a next user interface in a series of settings user interfaces).
  • a previous user interface e.g., user interface 812
  • option 820f is selectable to cease display of user interface 818
  • option 820g is selectable to display a next user interface (e.g., a next user interface in a series of onboarding user interfaces and/or a next user interface in a series of settings user interfaces).
  • User interface 818 also includes notification 822, which indicates that the user can improve period predictions, ovulation predictions, and fertile window predictions by setting up sleep tracking, and wearing their wearable device (e.g., watch) to sleep at night (e.g., so that electronic device 600 can log and track body temperature information, which can be used to improve these predictions).
  • notification 822 is displayed in response to a determination that the user has not enabled sleep tracking, has not enabled body temperature logging, and/or has not consistently logged body temperature information.
  • Notification 822 includes option 824b, that is selectable to display sleep tracking user interface 618 (discussed above), and option 824a, that is selectable to cease display of notification 822.
  • electronic device 600 detects user input 826 (e.g., a tap input and/or a touch input) corresponding to selection of option 820g.
  • Cycle tracking user interface 828 includes first region 830, which includes day representations 832a-832g.
  • Each day representation 832a-832g is representative of a single calendar day (e.g., representation 832d is representative of Friday May 6, representation 832c is representative of Thursday May 5, representation 832e is representative of Saturday May 7, and so forth).
  • a user is able to navigate within first region 830 (e.g., by scrolling and/or swiping to the left or right) to view additional day representations representative of dates in the past and/or in the future in order to view and/or log menstrual cycle information about a particular date.
  • Indication 83 la is pointing to representation 832d, indicating that representations 832d is the currently selected day representation, and indication 831b indicates that representation 832d is representative of “Today, May 6.” Accordingly, with representation 832d being currently selected, a user is able to interact with options 834a-834d to log menstrual cycle information for Friday, May 6. If the user swipes to the right to select representation 832c (e.g., to move representation 832c below indication 831a), the user is able to interact with options 834a-834d to log menstrual cycle information for Thursday, May 5.
  • Option 834a is selectable to initiate a process for indicating that the user experienced menstruation on the currently selected date.
  • Option 834b is selectable to initiate a process for logging one or more symptoms for the selected date.
  • Option 834c is selectable to initiate a process for indicating that the user experienced spotting on the currently selected date.
  • Option 834d is selectable to initiate a process for indicating that one or more predetermined health factors (e.g., pregnancy, using contraception, lactation, etc.) were applicable to the user on the selected date.
  • predetermined health factors e.g., pregnancy, using contraception, lactation, etc.
  • Option 834e is selectable to view one or more health-related predictions for the user, including, for example, menstrual period predictions (e.g., when the user will have her next menstrual period), fertile window predictions (e.g., when the user will have her next fertile window and/or when the user’s most recent fertile window occurred), and ovulation date predictions (e.g., a prediction of when the user last ovulated and/or when the user will ovulate next). Such predictions are also shown via daily representations 832a-832g in region 830. In FIG.
  • representations 832a-832e are displayed in a first manner (e.g., in a first color, in a first pattern, etc.) indicating that electronic device 600 has predicted that the user’s fertile window has taken place and/or will take place on those dates (e.g., in FIG. 8D, Tuesday May 3 to Saturday May 7).
  • Cycle tracking user interface 828 also includes option 834g that is selectable to return to a previously-displayed user interface, and option 834f that is selectable to initiate a process for logging a menstrual cycle (e.g., for identifying one or more dates on which the user menstruated).
  • Cycle tracking user interface 828 also includes history section 836, which displays menstrual cycle information for one or more menstrual cycles.
  • History section 836 includes first region 838a, which corresponds to a current menstrual cycle (e.g., which started on April 17 and has continued to the present date, May 6), and second region 838b, which corresponds to a previous menstrual cycle that occurred from March 19 to April 16.
  • First region 838a includes 20 pill-shaped day representations, with each day representation representative of a single day in the current menstrual cycle (e.g., the first pill representative of the first day, the second pill representative of the second day, and so forth). In FIG.
  • the first six day representations 835a in region 838a indicate that the user menstruated for those first six days (e.g., by displaying the small circle at the top of each day representation), and the final six day representations 835b in region 838a indicate that electronic device 600 predicts that the user’s fertile window has occurred during those six days (e.g., based on the user’s past menstrual cycle information).
  • 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 displayed in FIG. 8D, and, in some embodiments, the user is able to swipe in region 838b to reveal the additional day representations).
  • Region 838b indicates that, during the previous menstrual cycle, the user menstruated in the first five days (e.g., based on the small circle shown at the top of those day representations), the user exhibited spotting on the third and fifth days (e.g., based on the small dot at the bottom of the third and fifth day representations), and show a fertile window prediction for days 10-16 of the menstrual cycle (based on the single diagonal hatching shown in those day representations), and shows an ovulation date prediction for the 15 th day of the menstrual cycle (e.g., based on the double diagonal hatching shown on that day representation).
  • cycle tracking user interface 828 does not display fertile window predictions or ovulation date predictions.
  • cycle tracking user interface 828 displays menstrual period predictions. In some embodiments, when fertility predictions are enabled, cycle tracking user interface 828 does not display menstrual period predictions, and only displays fertile window predictions and ovulation date predictions.
  • the fertile window prediction shown in FIG. 8D represents an initial fertile window prediction that is generated with information pertaining to the user (e.g., based on menstrual cycle history information for the user), but is not generated using user body temperature information.
  • the user has enabled sleep tracking and has enabled body temperature collection and logging, as was discussed above with reference to FIGS. 6A-6Q.
  • FIGS. 6A-6Q In FIGS.
  • cycle tracking user interface 828 includes a notification similar to notification 822 in FIG. 8C informing the user that the user can improve menstrual cycle predictions (e.g., menstrual period predictions, ovulation date predictions, and/or fertile window predictions) by setting up sleep tracking, setting up body temperature logging, and/or wearing their wearable device to sleep each night.
  • menstrual cycle predictions e.g., menstrual period predictions, ovulation date predictions, and/or fertile window predictions
  • electronic device 600 displays wrist temperature user interface 612, which was discussed above with reference to FIGS. 6A-6Q.
  • wrist temperature user interface 612 indicates that the user’s relative body temperature spiked around May 3.
  • electronic device 600 Based on the user’s body temperature information, electronic device 600 generates an ovulation date prediction predicting that the user ovulated on May 3.
  • electronic device 600 displays lock screen user interface 840, which includes indication 842a indicating the electronic device 600 is in a locked state.
  • Lock screen user interface also includes current time indication 842b, current date indication 842c, flashlight option 842d, and camera option 842e.
  • electronic device 600 displays push notification 842f while electronic device 600 is in the locked state.
  • push notification 842f causes display 602 to transition from an inactive state (e.g., an off state) to an active state (e.g., an on state).
  • Push notification 842f informs the user that electronic device 600 has determined (e.g., based on the user’s body temperature information), that it is likely that the user ovulated on May 3.
  • FIG. 8F also depicts electronic device 800, which is a smart watch with touch- sensitive display 802, rotatable and depressible input mechanism 804, and button 806.
  • electronic device 800 corresponds to electronic device 600 (e.g., is paired to electronic device 600 and/or corresponds to the same user as electronic device 600).
  • electronic device 800 displays notification 844 informing the user of the ovulation date prediction.
  • electronic device 600 detects user input 846 (e.g., a touch input and/or a tap input) corresponding to selection of notification 842f.
  • cycle tracking user interface 828 in response to user input 846, electronic device 600 displays cycle tracking user interface 828.
  • cycle tracking user interface 828 has been updated based on the ovulation date prediction by electronic device 600.
  • FIG. 8D prior to the ovulation date prediction, cycle tracking user interface 828 displayed an initial fertile window prediction, predicting the user’s fertile window to take place between May 1 and May 7 (e.g., day representations 832a-832e, and day representations 835b).
  • FIG. 8G after electronic device 600 has used the user’s body temperature information to generate a prediction that the user ovulated on May 3, cycle tracking user interface 828 now displays an updated fertile window prediction 835c between April 28 and May 4.
  • the updated fertile window prediction is defined by selecting a predetermined number of days before the ovulation date prediction (e.g., the five days before the ovulation date prediction) and a predetermined number of days after the ovulation date prediction (e.g., the day after the ovulation date prediction). Accordingly, day representations 832j, 832i, 832h, and 832b are displayed in the manner indicative of a fertile window prediction (e.g., single line hatching) while day representations 832c and 832d, which were previously shown with the single line hatching representing fertile window prediction, are no longer filled with this pattern.
  • a fertile window prediction e.g., single line hatching
  • Cycle tracking user interface 828 also displays the ovulation date prediction by displaying day representation 832a with double line hatching, and day representation 835d with double line hatching.
  • electronic device 600 went from displaying an initial fertile window prediction, to generating an ovulation date prediction using user body temperature information, to then displaying the ovulation date prediction and an updated fertile window prediction.
  • cycle history user interface 848 which includes menstrual cycle representations 850a-850d corresponding to a plurality of previous menstrual cycles for a user.
  • menstrual cycle representations 850a, 850c, and 850d do not include fertile window predictions or ovulation date predictions because the user indicated that one or more predetermined health factors (e.g., lactation and/or contraception user) were applicable to the user during those menstrual cycles.
  • menstrual cycle representation 850b does include a fertile window prediction and an ovulation date prediction.
  • electronic device 600 detects user input 852 (e.g., a touch input and/or a tap input) corresponding to selection of menstrual cycle representation 850b.
  • cycle detail user interface 854 displays information pertaining to the menstrual cycle that was selected in cycle history user interface 848.
  • cycle detail user interface 854 displays details pertaining to a menstrual cycle that occurred from December 14, 2021 to January 15, 2022.
  • Cycle history user interface 848 includes cycle length information 856a, a set of day representations 856b representative of each day in the menstrual cycle.
  • Day representations 856b include indications of which days the user menstruated (e.g., days 1-6 in FIG. 81), on which days the user logged spotting (e.g., days 3, 5, and 16 in FIG.
  • Cycle detail user interface 854 also displays body temperature information 856c, which indicates the user’s body temperature (e.g., relative body temperature) for each day in the menstrual cycle.
  • Body temperature information 856c indicates the user’s body temperature (e.g., relative body temperature) for each day in the menstrual cycle.
  • Cycle detail user interface 854 also includes sexual history information 856d.
  • Cycle detail user interface 854 also includes option 856e, which is selectable to initiate a process for exporting the menstrual cycle information in cycle detail user interface 854 (e.g., in a PDF file, in an email, or in another file format), option 856f that is selectable to initiate a process for editing the menstrual cycle information in cycle detail user interface 854, option 856g that is selectable to return to cycle history user interface 848.
  • option 856e is selectable to initiate a process for exporting the menstrual cycle information in cycle detail user interface 854 (e.g., in a PDF file, in an email, or in another file format)
  • option 856f that is selectable to initiate a process for editing the menstrual cycle information in cycle detail user interface 854
  • option 856g that is selectable to return to cycle history user interface 848.
  • FIG. 8J illustrates an alternative embodiment of cycle tracking user interface 828, in which cycle tracking user interface 828 includes option 858 that is selectable to log a positive ovulation prediction kit (OPK) test.
  • FIG. 8J depicts the same scenario that was described above with reference to FIG. 8D.
  • electronic device 600 has generated an initial fertile window prediction, and displays the initial fertile window prediction for May 1 - May 7.
  • Friday May 6 is selected (e.g., as indicated in region 830 and by indications 831a, 831b)
  • electronic device 600 detects user input 860 corresponding to selection of option 858.
  • electronic device 600 logs a positive OPK test for Friday May 6, as indicated by indication 862. Furthermore, in response to user input 860, electronic device 600 marks Saturday May 7 (day representation 832e) as the predicted ovulation date (a positive OPK test is indicative of the day before ovulation), and updates the fertile window based on the new predicted ovulation date by marking May 2 through May 8 as the new predicted fertile window (e.g., within region 830).
  • a positive OPK test overrides any fertile window prediction or ovulation date prediction generated by electronic device 600. In some embodiments, even after electronic device 600 predicts an ovulation date for the user based on user body temperature information, a positive OPK test will override the ovulation date prediction made by electronic device 600.
  • FIG. 9A is a flow diagram illustrating a method for generating and providing ovulation date predictions using a computer system in accordance with some embodiments.
  • Method 900 is performed at a computer system (e.g., 100, 300, 500) (e.g., 600, 800) (e.g., a wearable device, a smart watch, a smart phone, a tablet, and/or a computer system controlling an external display) that is 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 depressible input mechanism; and/or a rotatable and depressible input mechanism).
  • method 900 provides an intuitive way for generating and providing ovulation date predictions.
  • the method reduces the cognitive burden on a user for generating and/or receiving ovulation date predictions, thereby creating a more efficient human-machine interface.
  • the computer system receives (902) (e.g., via the one or more input devices and/or via an external device (e.g., an external (e.g., separate) wearable device, smart watch, smart phone, tablet, and/or computer system controlling an external display) body temperature information corresponding to a user (e.g., body temperature measurements collected from the user over one or more periods of time).
  • an external device e.g., an external (e.g., separate) wearable device, smart watch, smart phone, tablet, and/or computer system controlling an external display
  • body temperature information e.g., body temperature measurements collected from the user over one or more periods of time.
  • the computer system displays (906), via the display generation component (e.g., 602, 802), a push notification (e.g., 842f and/or 844) that causes the display generation component to transition from an inactive state (e.g., FIG. 101) (e.g., off state and/or a state in which the display generation component does not display content) to an active state (e.g., FIG.
  • a push notification e.g., 842f and/or 844
  • the computer system determines, based on the body temperature information corresponding to the user, a predicted ovulation date for the user (e.g., a predicted ovulation date for the user that is determined based on changes in the body temperature of the user over a period of time).
  • a predicted ovulation date for the user e.g., a predicted ovulation date for the user that is determined based on changes in the body temperature of the user over a period of time.
  • the computer system displays the push notification that indicates to the user that the computer system has determined a predicted ovulation date after (in some embodiments, in response to) determining the predicted ovulation date for the user.
  • Automatically displaying a push notification that indicates to the user that a predicted ovulation date has been determined for the user after receiving body temperature information corresponding to the user informs the user of an ovulation date prediction with fewer user inputs, thereby reducing the number of user inputs required to perform an operation.
  • Displaying the push notification that indicates to the user that a predicted ovulation date has been determined for the user provides the user with visual feedback about the state of the system (e.g., that the system has determined a predicted ovulation date for the user), thereby providing improved visual feedback to the user.
  • displaying the push notification comprises displaying the push notification while maintaining the computer system in a locked state (e.g., lock screen user interface 840 and/or indication 842a indicate that computer system 600 is in a locked state in FIG.
  • receiving the body temperature information corresponding to the user comprises receiving the body temperature information corresponding to the user from a first external device (e.g., 800) (e.g., a wearable device, a smart watch, a smart phone, a tablet, and/or a computer system controlling an external display) separate from (e.g., different from) the computer system.
  • a first external device e.g., 800
  • Automatically displaying a push notification that indicates to the user that a predicted ovulation date has been determined for the user after receiving body temperature information corresponding to the user from an external device informs the user of an ovulation date prediction with fewer user inputs, thereby reducing the number of user inputs required to perform an operation.
  • the computer system is in communication with a first sensor (e.g., a first temperature sensor and/or a first body temperature sensor) (e.g., a first sensor built into the computer system (e.g., contained 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 the body temperature information corresponding to the user comprises receiving the body temperature information corresponding to the user from the first sensor.
  • a first sensor e.g., a first temperature sensor and/or a first body temperature sensor
  • a first sensor built into the computer system e.g., contained within a housing corresponding to the computer system
  • receiving the body temperature information corresponding to the user comprises receiving the body temperature information corresponding to the user from the first sensor.
  • the computer system while displaying the push notification (e.g., 842f and/or 844) (908): receives (910), via the one or more input devices, a selection input (e.g., 846) (e.g., one or more touch inputs, one or more tap inputs, one or more mouse inputs, one or more keyboard inputs, and/or one or more gesture inputs) corresponding to selection of the push notification.
  • a selection input e.g., 846
  • a selection inputs 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
  • the computer system In response to receiving the selection input corresponding to selection of the push notification (912), the computer system displays (914), via the display generation component, a cycle tracking user interface (e.g., 828) that includes (e.g., displays and/or shows) the predicted ovulation date (e.g., day representation 832a in FIG. 8G and/or day representation 835d in FIG. 8G). In some embodiments, the push notification does not display the predicted ovulation date.
  • the cycle tracking user interface that includes the predicted ovulation date is displayed in response to receiving the selection input corresponding to selection of the push notification and in accordance with a determination that device security criteria are satisfied (e.g., in accordance with a determination that authentication information (e.g., passcode information and/or biometric authentication information (e.g., face scan authentication, iris scan authentication, and/or fingerprint scan authentication)) satisfies authentication criteria).
  • a determination that authentication information e.g., passcode information and/or biometric authentication information (e.g., face scan authentication, iris scan authentication, and/or fingerprint scan authentication)
  • Displaying a push notification that is selectable to display the predicted ovulation date allows a user to view the predicted ovulation date with fewer user inputs, thereby reducing the number of user inputs required to perform an operation.
  • the push notification (e.g., 842f and/or 844) includes (e.g., displays and/or shows) the predicted ovulation date (e.g., “May 3” in FIG. 8F).
  • Displaying a push notification that displays the predicted ovulation date allows a user to view the predicted ovulation date with fewer user inputs, thereby reducing the number of user inputs required to perform an operation.
  • Displaying a push notification that displays the predicted ovulation date provides the user with visual feedback about the state of the system (e.g., that the system has determined a predicted ovulation date for the user), thereby providing improved visual feedback to the user.
  • displaying the push notification is performed in accordance with a determination that the user has enabled a fertility tracking setting (e.g., 820a, 820b, and/or 820c) (e.g., has enabled a setting that indicates that the user authorizes receipt of fertility information and/or authorizes performance of ovulation date predictions).
  • a fertility tracking setting e.g., 820a, 820b, and/or 820c
  • the computer system after receiving the body temperature information corresponding to the user, and in accordance with a determination that the user has not enabled the fertility tracking setting, the computer system forgoes displaying the push notification.
  • displaying the push notification is performed in accordance with a determination that a threshold amount of body temperature information corresponding to the user has been collected (e.g., in FIGS. 6L-6N, the threshold amount of body temperature information has been collected, whereas in FIGS. 6K and 6Q, the threshold amount of body temperature information has not been collected) (e.g., body temperature information corresponding to the user has been collected for a threshold number of days and/or a body temperature information corresponding to the user has been collected a threshold number of times).
  • a threshold amount of body temperature information corresponding to the user e.g., in FIGS. 6L-6N, the threshold amount of body temperature information has been collected, whereas in FIGS. 6K and 6Q, the threshold amount of body temperature information has not been collected
  • the computer system after receiving the body temperature information corresponding to the user, and in accordance with a determination that the threshold amount of body temperature information corresponding to the user has not been collected, the computer system forgoes displaying the push notification.
  • Automatically displaying a push notification that indicates to the user that a predicted ovulation date has been determined for the user after receiving body temperature information corresponding to the user and in accordance with a determination that a threshold amount of body temperature information corresponding to the user has been collected informs the user that an ovulation date prediction is ready for the user to view with fewer user inputs, thereby reducing the number of user inputs required to perform an operation. Displaying the push notification only if a threshold amount of body temperature information has been collected improves the user-device interface by avoiding presenting the user with information that does not apply to the user and helping the user to provide correct inputs.
  • displaying the push notification is performed in accordance with a determination that one or more predetermined health factors do not apply to the user (e.g., FIG. 8A and/or “factors” option 834d in FIG. 8D) (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).
  • the computer system after receiving the body temperature information corresponding to the user, and in accordance with a determination that at least one of the one or more predetermined health factors apply to the user (e.g., the user is pregnant and/or the user is using contraception), the computer system forgoes displaying the push notification.
  • Automatically displaying a push notification that indicates to the user that a predicted ovulation date has been determined for the user after receiving body temperature information corresponding to the user and in accordance with a determination that the one or more predetermined health factors do not apply to the user informs the user that an ovulation date prediction is ready for the user to view with fewer user inputs, thereby reducing the number of user inputs required to perform an operation.
  • Displaying the push notification only if one or more predetermined health factors do not apply to the user improves the user-device interface by avoiding presenting the user with information that does not apply to the user and helping the user to provide correct inputs.
  • the computer system receives, via the 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 one or more user inputs defining a sleep schedule (e.g., sleep schedule shown in 636i, 636j)) (e.g., a mode and/or state in which one or more notifications (e.g., notifications of a first type) received by the computer system are suppressed and/or in which user sleep information (e.g., sleep quality information) is collected).
  • an input e.g., a first set of user inputs and/or one or more user inputs
  • a sleep tracking mode e.g., 638a and/or 638b and/or one or more user inputs
  • the computer system In response to the input, the computer system enters the sleep tracking mode (e.g., sleep focus state in FIGS. 6H-6I), wherein receiving the body temperature information corresponding to the user is performed while the computer system is in the sleep tracking mode. In some embodiments, receiving the body temperature information corresponding to the user is performed in accordance with a determination that the computer system is in the sleep tracking mode. Automatically collecting body temperature information in response to the computer system entering the sleep tracking mode allows for collection of body temperature information with fewer user inputs, thereby reducing the number of user inputs required to perform an operation.
  • the sleep tracking mode e.g., sleep focus state in FIGS. 6H-6I
  • the computer system receives notification data of a first type (e.g., notifications of a type that are subject to being suppressed while in the sleep tracking mode) (in some embodiments, all notifications are suppressed in the sleep tracking mode) (in some embodiments, notifications of a second type (e.g., emergency notifications, wake alarm notifications), are not suppressed while in the sleep tracking mode).
  • a first type e.g., notifications of a type that are subject to being suppressed while in the sleep tracking mode
  • all notifications are suppressed in the sleep tracking mode
  • notifications of a second type e.g., emergency notifications, wake alarm notifications
  • the computer system In response to receiving the notification data of a first type: in accordance with a determination that the computer system is not in the sleep tracking mode (e.g., option 636a is in the inactive and/or off state) (e.g., when the notification data of the first type is received), the computer system outputs a first notification (e.g., displays a first notification; causes the display generation component to transition from an inactive state (e.g., off and/or a state in which content is not displayed on the display generation component) to an active state (e.g., on and/or a state in which content is displayed); outputs an audio output; and/or outputs a haptic output) corresponding to the notification data of the first type; and in accordance with a determination that the computer system is in the sleep tracking mode (e.g., electronic device 600 in FIGS.
  • a first notification e.g., displays a first notification; causes the display generation component to transition from an inactive state (e.g., off and/or
  • 6H-6I (e.g., option 636a is in the active and/or on state) (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 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 a user to perform this operation with fewer user inputs, thereby reducing the number of user inputs required to perform an operation.
  • the computer system in response to receiving the notification data of the first type: in accordance with a determination that the computer system is not in the sleep tracking mode (e.g., option 636a is in the inactive and/or off 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 smart watch, a smart phone, a tablet, and/or a computer system controlling 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 external device 800 to display and/or output a notification); and in accordance with a determination that the computer system is in the sleep tracking mode (e.g., option 636a is in the active and/or 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
  • electronic device 800 is also in the sleep focus state when electronic device 600 is in the sleep focus state (e.g., based on option 63 Oe being enabled)).
  • Automatically suppressing notifications on the second external device when the computer system is in the sleep tracking mode allows a user to perform this operation with fewer user inputs, thereby reducing the number of user inputs required to perform an operation.
  • receiving the body temperature information corresponding to the user comprises receiving the body temperature information corresponding to the user from a third external device (e.g., 800) (e.g., a wearable device, a smart watch, a smart phone, a tablet, and/or a computer system controlling an external display) separate from (e.g., different from) the computer system.
  • a third external device e.g., 800
  • Automatically displaying a push notification that indicates to the user that a predicted ovulation date has been determined for the user after receiving body temperature information corresponding to the user from an external device informs the user of the predicted ovulation date with fewer user inputs, thereby reducing the number of user inputs required to perform an operation.
  • the computer system receives notification data of a second type (e.g., notifications of a type that are subject to being suppressed while in the sleep tracking mode) (in some embodiments, all notifications are suppressed in the sleep tracking mode) (in some embodiments, notifications of a third type (e.g., emergency notifications, wake alarm notifications), are not suppressed while in the sleep tracking mode).
  • a second type e.g., notifications of a type that are subject to being suppressed while in the sleep tracking mode
  • all notifications are suppressed in the sleep tracking mode
  • notifications of a third type e.g., emergency notifications, wake alarm notifications
  • the computer system In response to receiving the notification data of a second type: in accordance with a determination that the computer system (e.g., 600) is not in the sleep tracking mode (e.g., option 636a is in the inactive and/or off state) (e.g., when the notification data of the second type is received), the computer system (e.g., 600) causes the third external device (e.g., 800) to output a third notification (e.g., causes the third external device to display a third notification; causes a display generation component corresponding to and/or in communication with the third external device to transition from an inactive state (e.g., off and/or a state in which content is not displayed on the display generation component) to an active state (e.g., on and/or a state in which content is displayed); causes the third external device to output an audio output; and/or causes the third external device to output a haptic output) corresponding to the notification data of the third type; and in accordance with a determination that the computer system is
  • the computer system receives (e.g., via the one or more input devices and/or via an external device (e.g., an external (e.g., separate) wearable device, smart watch, smart phone, tablet, and/or 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 periods of time) (e.g., second body temperature information different from the body temperature information).
  • an external device e.g., an external (e.g., separate) wearable device, smart watch, smart phone, tablet, and/or 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 periods of time
  • second body temperature information e.g., second body temperature information different from the body temperature information
  • the computer system displays, via the 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 the inactive state to the active state and that indicates to the user that a second predicted ovulation date has been determined for the user, wherein the second predicted ovulation date was determined based on the second body temperature information corresponding to the user; and in accordance with a determination that the user has logged an ovulation prediction kit test result during the predefined period of time (e.g., user logs positive OPK test in FIGS.
  • a second push notification e.g., 842f and/or 844
  • the computer system forgoes displaying the second push notification (e.g., a push notification indicative of a predicted ovulation date is not generated after the user logs the positive OPK test in FIGS. 8J-8K).
  • the second push notification e.g., a push notification indicative of a predicted ovulation date is not generated after the user logs the positive OPK test in FIGS. 8J-8K.
  • Automatically displaying a second push notification that indicates to the user that a second predicted ovulation date has been determined for the user after receiving second body temperature information corresponding to the user informs the user that an ovulation date prediction is ready for them to view with fewer user inputs, thereby reducing the number of user inputs required to perform an operation.
  • Forgoing displaying the second push notification if the user has logged an ovulation prediction kit test result during the predefined period of time improves the userdevice interface by avoiding presenting the user with information that does not apply to the user and helping the user to provide correct inputs.
  • method 700, method 950, and/or method 1100 optionally include one or more of the characteristics of the various methods described above with reference to method 900.
  • the body temperature information that is collected in method 700 can be used to generate health-based notifications and/or predictions in methods 900, 950, and/or 1100. For brevity, these details are not repeated below.
  • FIG. 9B is a flow diagram illustrating a method for generating and providing ovulation date predictions using a computer system in accordance with some embodiments.
  • Method 950 is performed at a computer system (e.g., 100, 300, 500) (e.g., 600, 800) (e.g., a wearable device, a smart watch, a smart phone, a tablet, and/or a computer system controlling an external display) that is 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 depressible input mechanism; and/or a rotatable and depressible input mechanism).
  • method 950 provides an intuitive way for generating and providing ovulation date predictions.
  • the method reduces the cognitive burden on a user for generating and/or receiving ovulation date predictions, thereby creating a more efficient human-machine interface.
  • the computer system displays (952), via the display generation component (e.g., 602), at a first time, a cycle tracking user interface (e.g., 828) (e.g., a cycle tracking user interface corresponding to a user) including displaying a first fertile window prediction for a user (e.g., 835b and/or day representations 832a-832e in FIG.
  • a cycle tracking user interface e.g., 828
  • a cycle tracking user interface corresponding to a user including displaying a first fertile window prediction for a user (e.g., 835b and/or day representations 832a-832e in FIG.
  • 8D e.g., a prediction of one or more days and/or dates during which the user has an increased likelihood of becoming pregnant (e.g., a prediction of the date on which the user will release an egg from an ovary and a predetermined period of time prior to that date (e.g., five dates prior to that date)) (e.g., a fertile window prediction corresponding to a first period of time).
  • the computer system receives (954) (e.g., via the one or more input devices and/or via an external device (e.g., an external (e.g., separate) wearable device, smart watch, smart phone, tablet, and/or computer system controlling an external display)) body temperature information corresponding to the user (e.g., body temperature information shown in data chart 614d in FIG. 8E) (e.g., body temperature measurements collected from the user over one or more periods of time).
  • an external device e.g., an external (e.g., separate) wearable device, smart watch, smart phone, tablet, and/or computer system controlling an external display
  • body temperature information corresponding to the user e.g., body temperature information shown in data chart 614d in FIG. 8E
  • body temperature information collected from the user over one or more periods of time e.g., body temperature information shown in data chart 614d in FIG. 8E
  • the computer system determines (958), at a second time subsequent to the first time, based on the body temperature information corresponding to the user, a predicted ovulation date for the user (e.g., notification 842f and/or 844) (e.g., a predicted ovulation date for the user that is determined based on changes in the body temperature of the user over a period of time).
  • the computer system displays (960), via the display generation component, at a third time subsequent to the second time, an updated cycle tracking user interface (e.g., 828 in FIG.
  • 8G (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 predicted ovulation date for the user)), including concurrently displaying: a representation of the predicted ovulation date for the user (e.g., 832a, 835d) (e.g., a graphical object indicative of the predicted ovulation date for the user); and an updated fertile window prediction for the user (e.g., day representations 832j , 832i, 832h, 832b, and/or 835c) different from the first fertile window prediction for the user (e.g., an updated, revised, and/or modified fertile window prediction (e.g., updated, revised, and/or modified based on the body temperature information and/or the predicted ovulation date for the user)).
  • a representation of the predicted ovulation date for the user e.g., 832a, 835d
  • the first fertile 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 fertile window prediction is determined based on historical menstrual cycle information corresponding to the user).
  • the predicted ovulation date for the user is determined, based on the body temperature information corresponding to the user, by an external device and transmitted to and received by the computer system. Automatically updating the cycle tracking user interface with an updated fertile window prediction after receiving body temperature information corresponding to the user allows the user to view updated fertile window prediction information with fewer user inputs, thereby reducing the number of user inputs required to perform an operation.
  • Automatically updating the cycle tracking user interface with an updated fertile window prediction after receiving body temperature information corresponding to the user provides the user with visual feedback about the state of the system (e.g., that the system has determined a predicted ovulation date for the user and/or an updated fertile window prediction for the user), thereby providing improved visual feedback to the user.
  • receiving the body temperature information corresponding to the user comprises receiving the body temperature information corresponding to the user from a first external device (e.g., 800) (e.g., a wearable device, a smart watch, a smart phone, a tablet, and/or a computer system controlling an external display) separate from (e.g., different from) the computer system.
  • a first external device e.g., 800
  • Automatically updating the cycle tracking user interface with an updated fertile window prediction after receiving body temperature information corresponding to the user allows the user to view updated fertile window prediction information with fewer user inputs, thereby reducing the number of user inputs required to perform an operation.
  • the computer system is in communication 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 the body temperature information corresponding to the user comprises receiving the body temperature information corresponding to the user from the first sensor.
  • a first sensor e.g., a sensor built into electronic device 600 and/or electronic device 800
  • 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
  • receiving the body temperature information corresponding to the user comprises receiving the body temperature information corresponding to the user from the first sensor.
  • the representation of the predicted ovulation date (e.g., 832a and/or 835d) for the user is displayed with a first visual appearance (e.g., with a first set of visual characteristics (e.g., color, size, shape, font, and/or pattern)); and the updated fertile window prediction for the user (e.g., 832j, 832i, 832h, 832b, 832c, and/or 835c) is displayed with a second visual appearance (e.g., with a second set of visual characteristics (e.g., color, size, shape, font, and/or pattern)) different from the first visual appearance.
  • a first visual appearance e.g., with a first set of visual characteristics (e.g., color, size, shape, font, and/or pattern)
  • the updated fertile window prediction for the user e.g., 832j, 832i, 832h, 832b, 832c, and/or 835c
  • a second visual appearance
  • Displaying the representation of the predicted ovulation date with a first visual appearance and displaying the updated fertile window prediction with a second visual appearance different from the first visual appearance allows a user to visually distinguish between the predicted ovulation date and the fertile window prediction without additional user inputs and also provides improved visual feedback.
  • the representation of the predicted ovulation date for the user includes a first color (e.g., at least a portion of the representation of the predicted ovulation date for the user is displayed in the first color); and the updated fertile 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 fertile window prediction is displayed in the second color) (in some embodiments, the updated fertile window prediction does not include the first color). Displaying the representation of the predicted ovulation date in a first color and displaying the updated fertile window prediction in a second color different from the first color allows a user to visually distinguish between the predicted ovulation date and the fertile window prediction without additional user inputs.
  • the computer system receives second body temperature information corresponding to the user (e.g., body temperature information shown in data chart 614d) (e.g., second body temperature information different from or the same as the first body temperature information).
  • the computer system displays, via the display generation component, the cycle tracking user interface (e.g., 828), including: in accordance with a determination that a fertility tracking setting (e.g., 820a, 820b, and/or 820c) is enabled (e.g., a setting that indicates that the user authorizes receipt of fertility information and/or authorizes performance of ovulation date predictions), displaying (e.g., within the cycle tracking user interface) a representation of a second predicted ovulation date (e.g., 832a, 835d) for the user, wherein the second predicted ovulation date is determined based on the second body temperature information; and in accordance with a determination that the fertility tracking setting is not enabled
  • a fertility tracking setting e.g., 820a, 820
  • the computer system receives third body temperature information corresponding to the user (e.g., body temperature information shown in data chart 614d) (e.g., third body temperature information different from or the same as the first body temperature information and/or the second body temperature information).
  • third body temperature information corresponding to the user e.g., body temperature information shown in data chart 614d
  • the computer system After receiving the third body temperature information corresponding to the user: in accordance with a determination that one or more predetermined health factors (e.g., FIG.
  • the computer system determines, based on the third body temperature information, a third predicted ovulation date (e.g., 842f, 844, 832a, and/or 835d) for the user (and, optionally, displays a representation of and/or an indication of the third predicted ovulation date); and in accordance with a determination that at least one of the one or more predetermined health factors apply 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 subsequent to receiving the third body temperature information corresponding to the user), the
  • Automatically determining a predicted ovulation date for a user in accordance with a determination that one or more predetermined health factors do not apply to the user reduces the number of user inputs required to perform an operation. Furthermore, forgoing performing an ovulation date prediction for a user if one or more predetermined health factors apply to the user improves the user-device interface by avoiding presentation of information that does not apply to the user.
  • the computer system receives fourth body temperature information corresponding to the user (e.g., body temperature information shown in data chart 614d) (e.g., fourth body temperature information different from or the same as the first body temperature information, the second body temperature information, and/or the third body temperature information).
  • fourth body temperature information corresponding to the user (e.g., body temperature information shown in data chart 614d) (e.g., fourth body temperature information different from or the same as the first body temperature information, the second body temperature information, and/or the third body temperature information).
  • the computer system After receiving the fourth body temperature information corresponding to the user: in accordance with a determination that a threshold amount of body temperature information (e.g., user body temperature information associated with a user of the computer system, collected from the user of the computer system and/or collected by the computer system) has been collected (e.g., greater than a threshold number of days of body temperature information has been collected and/or greater than a threshold number of hours of body temperature information has been collected), the computer system determines, based on the fourth body temperature information, a fourth predicted ovulation date for the user (e.g., 842f, 844, 832a, and/or 835d) (and, optionally, displays a representation of and/or an indication of the fourth predicted ovulation date); and in accordance with a determination that the threshold amount of body temperature information has not been collected, the computer system forgoes determining a prediction ovulation date for the user based on the fourth body temperature information.
  • a threshold amount of body temperature information e.g.
  • Automatically determining a predicted ovulation date for a user in accordance with a determination that a threshold amount of body temperature information has been collected reduces the number of user inputs required to perform an operation. Furthermore, forgoing performing an ovulation date prediction for a user if the threshold amount of body temperature information has not been collected improves the userdevice interface by avoiding presentation of information that does not apply to the user and/or that is inaccurate.
  • the computer system receives, via the 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 one or more user inputs defining a sleep schedule (e.g., sleep schedule shown in 636i, 636j)) (e.g., a mode and/or state in which one or more notifications (e.g., notifications of a first type) received by the computer system are suppressed and/or in which user sleep information (e.g., sleep quality information) is collected).
  • an input e.g., a first set of user inputs and/or one or more user inputs
  • a sleep tracking mode e.g., 638a and/or 638b and/or one or more user inputs
  • the computer system In response to the input, the computer system enters the sleep tracking mode (e.g., sleep focus state in FIGS. 6H-6I), wherein: receiving the body temperature information corresponding to the user is performed while the computer system is in the sleep tracking mode (in some embodiments, receiving the body temperature information corresponding to the user is performed in accordance with a determination that the computer system is in the sleep tracking mode).
  • the sleep tracking mode e.g., sleep focus state in FIGS. 6H-6I
  • receiving the body temperature information corresponding to the user is performed while the computer system is in the sleep tracking mode (in some embodiments, receiving the body temperature information corresponding to the user is performed in accordance with a determination that the computer system is in the sleep tracking mode).
  • Automatically collecting body temperature information in response to the computer system entering the sleep tracking mode allows for collection of body temperature information with fewer user inputs, thereby reducing the number of user inputs required to perform an operation.
  • the computer system receives notification data of a first type (e.g., notifications of a type that are subject to being suppressed while in the sleep tracking mode) (in some embodiments, all notifications are suppressed in the sleep tracking mode) (in some embodiments, notifications of a second type (e.g., emergency notifications, wake alarm notifications), are not suppressed while in the sleep tracking mode).
  • a first type e.g., notifications of a type that are subject to being suppressed while in the sleep tracking mode
  • all notifications are suppressed in the sleep tracking mode
  • notifications of a second type e.g., emergency notifications, wake alarm notifications
  • the computer system In response to receiving the notification data of a first type: in accordance with a determination that the computer system is not in the sleep tracking mode (e.g., option 636a is in the inactive and/or off state) (e.g., when the notification data of the first type is received), the computer system outputs a first notification (e.g., displays a first notification; causes the display generation component to transition from an inactive state (e.g., off and/or a state in which content is not displayed on the display generation component) to an active state (e.g., on and/or a state in which content is displayed); outputs an audio output; and/or outputs a haptic output) corresponding to the notification data of the first type; and in accordance with a determination that the computer system is in the sleep tracking mode (e.g., option 636a is in the active and/or on state) (e.g., when the notification data of the first type is received), the computer system forgoes outputting (e.g., suppresse
  • a second external device e.g., 800
  • a sleep tracking mode e.g., a mode and/or state in which one or more notifications (e.g., notifications of a first type) received by the computer system are suppressed and/or in which user sleep information (e.g., sleep quality information) is collected
  • the computer system enters the sleep tracking mode (e.g., a user is able to provide one or more user inputs on electronic device 800 to cause electronic device 600 to enter the sleep focus state)
  • receiving the body temperature information corresponding to the user comprises receiving the body temperature information corresponding to the user from the second external device
  • the second external device collects the body temperature information corresponding to the user in accordance with 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 collection of body temperature information with fewer user inputs, thereby reducing the number of user inputs required to perform an operation.
  • the computer system receives notification data of a second type (e.g., notifications of a type that are subject to being suppressed while in the sleep tracking mode) (in some embodiments, all notifications are suppressed in the sleep tracking mode) (in some embodiments, notifications of a third type (e.g., emergency notifications, wake alarm notifications), are not suppressed while in the sleep tracking mode).
  • a second type e.g., notifications of a type that are subject to being suppressed while in the sleep tracking mode
  • all notifications are suppressed in the sleep tracking mode
  • notifications of a third type e.g., emergency notifications, wake alarm notifications
  • the computer system In response to receiving the notification data of a second type: in accordance with a determination that the computer system is not in the sleep tracking mode (e.g., when the notification data of the second type is received), the computer system (e.g., 600) causes the second external device (e.g., 800) to output a second notification (e.g., causes the second external device to display a second notification; causes a display generation component corresponding to and/or in communication with the second external device to transition from an inactive state (e.g., off and/or a state in which content is not displayed on the display generation component) to an active state (e.g., on and/or a state in which content is displayed); causes the second external device to output an audio output; and/or causes the second external device to output a haptic output) corresponding to the notification data of the second type; and in accordance with a determination that the computer system (e.g., 600) is in the sleep tracking mode (e.g., when the notification data of the second type is received
  • 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 FIG. 8J indicating a positive OPK test on Friday, May 6).
  • OPK e.g., ovulation prediction kit
  • the computer system determines, based on the OPK test result information, an updated predicted ovulation date for the user (e.g., in FIG.
  • a second updated cycle tracking user interface e.g., 828 in FIG. 8K
  • a representation of the updated predicted ovulation date for the user e.g., 832e in FIG.
  • electronic device 600 goes from displaying cycle tracking user interface 828 in FIG. 8G, with a first predicted ovulation date (e.g., 832a in FIG. 8G) to displaying cycle tracking user interface 828 in FIG. 8K that displays a different and/or updated predicted ovulation date (e.g., 832e in FIG. 8K)) (e.g., a graphical object indicative of the updated predicted ovulation date) (optionally, without displaying the representation of the predicted ovulation date for the user).
  • a first predicted ovulation date e.g., 832a in FIG. 8G
  • a different and/or updated predicted ovulation date e.g., 832e in FIG. 8K
  • a graphical object indicative of the updated predicted ovulation date e.g., a graphical object indicative of the updated predicted ovulation date
  • displaying the second updated cycle tracking user interface further includes displaying (e.g., concurrently with the representation of the updated predicted ovulation date for the user) a second updated fertile window prediction for the user, wherein the second updated fertile window prediction is determined based on the updated predicted ovulation date for the user.
  • displaying the second updated cycle tracking user interface further comprises: displaying, concurrently with the representation of the updated predicted ovulation date for the user (e.g., 832e), a second updated fertile window prediction for the user (e.g., 832a, 832b, 832c, 832d, 832f and/or fertile window prediction in region 838a in FIG. 8K) (e.g., a second updated fertile window prediction different from the updated fertile window prediction and/or the same as the updated fertile window prediction), wherein the second updated fertile window prediction is determined based on the OPK test result information.
  • a second updated fertile window prediction e.g., 832a, 832b, 832c, 832d, 832f and/or fertile window prediction in region 838a in FIG. 8K
  • the second updated fertile window prediction is determined based on the updated predicted ovulation date for the user. Automatically updated a fertile window prediction based on an OPK test result allows a user to receive updated fertile window predictions with fewer user inputs, thereby reducing the number of user inputs required to perform an operation.
  • the representation of the predicted ovulation date for the user is displayed with a first set of visual characteristics (e.g., color, size, and/or shape); and the representation of the updated predicted ovulation date for the user (e.g., 832e in FIG. 8K) is displayed with the first set of visual characteristics (e.g., the same color, size, and/or shape).
  • method 700, method 900, and/or method 1100 optionally include one or more of the characteristics of the various methods described above with reference to method 950.
  • the body temperature information that is collected in method 700 can be used to generate health-based notifications and/or predictions in methods 900, 950, and/or 1100. For brevity, these details are not repeated below.
  • FIGS. 10A-10N illustrate exemplary user interfaces for generating and providing health-related notifications, in accordance with some embodiments.
  • the user interfaces in these figures are used to illustrate the processes described below, including the processes in FIG. 11.
  • FIG. 10A illustrates electronic device 600 with touch-sensitive display 602.
  • electronic device 600 displays cycle tracking user interface 828, which was discussed above with reference to FIGS. 8A-8K.
  • the current date is June 6, and in cycle tracking user interface 828, day representation 1001a representing the current date is selected (e.g., as indicated by indications 831a, 831b).
  • FIG. 10A also illustrates electronic device 800, which is a smart watch with touch-sensitive display 802, rotatable and depressible input mechanism 804, and button 806.
  • electronic device 800 corresponds to electronic device 600 (e.g., electronic device 800 is paired to electronic device 600 and/or corresponds to the same user as electronic device 600).
  • FIGS. 10A-10E illustrate electronic device 600 and electronic device 800 displaying substantially identical user interfaces to demonstrate that, in certain embodiments, a user is able to log and/or enter menstruation information using either electronic device 600 or electronic device 800.
  • cycle tracking user interface 1000 which is substantially identical in substance to cycle tracking user interface 828.
  • Cycle tracking user interface 1000 includes region 1002 with a plurality of day representations (similar to region 830 in cycle tracking user interface 828), option 1004a (which corresponds to option 832a), option 1004b (which corresponds to option 834b), and option 1004c (which corresponds to option 834c).
  • day representation 1001b representative of the current day, is selected within cycle tracking user interface 1000.
  • FIG. 10A day representation 1001b, representative of the current day, is selected within cycle tracking user interface 1000.
  • day representation 1001a While day representation 1001a is selected, electronic device 600 detects user input 1005 (e.g., a tap input and/or a touch input) corresponding to selection of option 834a, indicative of a user request to log menstruation information for the selected day. Furthermore, while day representation 1001b is selected, electronic device 800 detects user input 1006 (e.g., a tap input and/or a touch input) corresponding to selection of option 1004a.
  • user input 1005 e.g., a tap input and/or a touch input
  • user input 1006 e.g., a tap input and/or a touch input
  • electronic device 600 displays user interface 1008, and in response to user input 1006, electronic device 800 displays user interface 1012.
  • User interface 1012 corresponds to user interface 1008 (e.g., user interface 1012 is a watch version of user interface 1008 and/or smaller form factor version of user interface 1008).
  • User interface 1008 includes option 1010a that is selectable by a user to indicate that the user is experiencing light flow, option 1010b that is selectable by a user to indicate that the user is experiencing medium flow, option 1010c that is selectable by a user to indicate that the user is experiencing heavy flow, option lOlOd that is selectable by a user to indicate that the user is experiencing unspecified flow, and option lOlOe that is selectable by a user to indicate that the user is experiencing no flow.
  • User interface 1008 also includes option lOlOf that is selectable to cease display of user interface 1008 (and, for example, cancel entry of menstruation information and return to cycle tracking user interface 828), and option 1010g that is selectable to advance to a next user interface.
  • User interface 1012 includes options 1014a-1014g that correspond to options lOlOa-lOlOg, respectively.
  • the user has specified that the user is experiencing light flow.
  • Electronic device 600 detects user input 1016a (e.g., a touch input and/or a tap input) corresponding to selection of option 1010g
  • electronic device 800 detects user input 1016b (e.g., a touch input and/or a tap input) corresponding to selection of option 1014g.
  • electronic device 600 displays user interface 1018
  • 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 smaller form factor version of user interface 1018).
  • User interface 1018 includes various options 1020a-1020e
  • user interface 1022 includes corresponding options 1024a- 1024g, that are selectable by a user to indicate that the user is experience one or more symptoms (e.g., cramps, mood changes, low back pain, aches, bloating, constipation, headache).
  • symptoms e.g., cramps, mood changes, low back pain, aches, bloating, constipation, headache.
  • electronic device 600 detects user input 1026a (e.g., a touch input and/or a tap input) corresponding to selection of option 1020f
  • electronic device 800 detects user input 1026b (e.g., a touch input and/or a tap input) corresponding to selection of option 1024h.
  • user input 1026a e.g., a touch input and/or a tap input
  • user input 1026b e.g., a touch input and/or a tap input
  • electronic device 600 displays user interface 1028
  • 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 smaller form factor version of user interface 1028).
  • User interface 1028 includes option 1030a that is selectable by a user to indicate that the user is experiencing spotting, and user interface 1032 includes corresponding option 1034a.
  • the user is not experiencing spotting, and has not selected option 1030a or option 1034a.
  • electronic device 600 detects user input 1036a (e.g., a touch input and/or a tap input) corresponding to option 1030c
  • electronic device 800 detects user input 1036b (e.g., a touch input and/or a tap input) corresponding to option 1034c.
  • cycle tracking user interface 828 has been updated according to the menstruation information entered by the user in FIGS. 10B-10D.
  • day representation 1001a is now shown with a menstruation indication (e.g., hashed circle at the top of day representation 1001a) indicating that the user has logged menstruation for that day
  • option 834a is shown with “light flow”
  • option 834b is shown indicating that the user has logged 5 symptoms for that day.
  • FIG. 10E depicts an example scenario in which the user has entered menstruation information, and electronic device 600 (and/or electronic device 800) have not detected any potential health issues based on the menstruation information entered by the user.
  • FIG. 10F depicts an alternative scenario in which electronic device 600 detects a potential health issue based on the menstruation information that has just been entered by the user.
  • electronic device 600 displays cycle tracking user interface 828, which is nearly identical to cycle tracking user interface 828 as it was described in FIG. 10E.
  • electronic device 600 has identified, based on the menstrual cycle information entered by the user in FIGS. 10B-10D, a potential health issue for the user.
  • electronic device 600 displays, within cycle tracking user interface 828, notification 1038a indicating that the user may have a potential health issue.
  • notification 1038a does not identify the potential health issue, and the user is not presented with the potential health issue until the user confirms that the underlying menstrual cycle information that led to identification of the potential health issue is accurate.
  • Notification 1038a includes option 1038c that is selectable to dismiss notification 1038a and/or cease display of notification 1038a, and option 1038b that is selectable to review the user’s cycle history to confirm whether or not the user’s cycle history is accurate.
  • electronic device 800 does not display a notification of a potential health issue.
  • electronic device 600 displays notification 1038a indicative of a potential health issue, but a corresponding device (e.g., a corresponding wearable device) such as electronic device 800 does not display a notification of a potential health issue.
  • a corresponding device e.g., a corresponding wearable device
  • electronic device 600 ceases display of notification 1038a within cycle tracking user interface 828.
  • electronic device 600 detects user input 1040 (e.g., a touch input and/or a tap input) corresponding to selection of option 1038b.
  • menstrual cycle information 1044a which includes the underlying menstrual cycle information that resulted in electronic device 600 detecting a potential health issue.
  • menstrual cycle information 1044a shown in user interface 1042 varies based on the potential health issue identified by electronic device 600. For example, if the duration of the user’s periods are determined to be problematic, then menstrual cycle information 1044a shows the period durations that resulted in identification of the potential health issue, whereas if the frequency of the user’s spotting is determined to be problematic, then menstrual cycle information 1044a shows the dates on which the user logged spotting.
  • User interface 1042 instructs the user to review menstrual cycle information 1044a, and either confirm that menstrual cycle information 1044a is accurate (e.g., by selecting option 1044b), or revise and/or modify menstrual cycle information 1044a (e.g., by selecting option 1044c).
  • User interface 1042 also includes option 1044d that is selectable to cease display of user interface 1042 without confirming or modifying menstrual cycle information 1044a (and, for example, return to cycle tracking user interface 828).
  • electronic device 600 detects user input 1046 (e.g., a touch input and/or a tap input) corresponding to selection of option 1044d.
  • electronic device 600 displays health summary user interface 604, which was discussed above with reference to FIGS. 6A-6Q.
  • a notification of the potential health issue is also displayed in health summary user interface 604.
  • electronic device 600 displays notification 1048a in health summary user interface 604.
  • Notification 1048a includes option 1048c that is selectable to cease display of notification 1048a, and option 1048b that is selectable to display user interface 1042.
  • the user does not take any action with respect to notification 1048a (e.g., the user ignores notification 1048a).
  • electronic device 600 when a user ignores and/or does not interact with notification 1048a for a duration of time, and new menstrual cycle information entered by the user (e.g., either revising previously entered menstrual cycle information and/or entering new menstrual cycle information on future days) negates the potential health issue identified by electronic device 600, electronic device 600 ceases display of notification 1048c within health summary user interface 604.
  • electronic device 600 is in an inactive and locked state, and does not display content on display 602.
  • electronic device 600 receives and/or generates information pertaining to a push notification indicating a potential health issue for the user.
  • electronic device 600 displays lock screen user interface 840, which includes push notification 1052 informing the user that electronic device 600 has detected a potential health issue based on menstrual cycle information entered by the user.
  • push notification 1052 causes display 602 to transition from an inactive state (e.g., FIG. 101) to an active state (e.g., FIG. 10J).
  • push notification 1052 is generated in accordance with a determination that the user has not yet confirmed or otherwise negated the potential health issue identified for the user (e.g., in accordance with a determination that there is still an unconfirmed and/or uncleared potential health issue identified for the user).
  • electronic device 600 does not display and/or the user is not presented with another push notification for the same unconfirmed potential health issue for a threshold duration of time (e.g., for one month and/or for sixty days).
  • electronic device 600 detects user input 1054 (e.g., a touch input and/or a tap input) corresponding to selection of push notification 1052.
  • electronic device 600 displays user interface 1042, which was described above with reference to FIG. 10G.
  • electronic device 600 detects user input 1056 (e.g., a touch input and/or a tap input) corresponding to selection of option 1044b, indicating that the user confirms the accuracy of menstrual cycle information 1044a.
  • user input 1056 e.g., a touch input and/or a tap input
  • electronic device 600 displays user interface 1058.
  • User interface 1058 includes indication 1060a, which identifies the potential health issue detected by electronic device 600, as well as the criteria that were used to determine the potential health issue.
  • electronic device 600 has determined that, within the past 180 days, the user has had two periods that lasted longer than 10 days and, accordingly, the user may have prolonged menstrual periods that the user should discuss with a doctor.
  • User interface 1058 includes instruction 1060b, which instructs the user to contact a doctor.
  • User interface 1058 also includes option 1060c, that is selectable to initiate a process for exporting menstrual cycle information for the user (e.g., export a PDF file that contains all menstrual cycle information pertaining to the user over the previous 12 months that is available to electronic device 600).
  • User interface 1058 also includes option 1060d that is selectable to cease display of user interface 1058, and option 1060e that is selectable to return to user interface 1042.
  • FIG. 10L shows the potential health issue of “prolonged periods,” and indication 1060a displays the criteria for this health issue.
  • electronic device 1058 is able to detect other health issues, and indication 1060a would display different information.
  • the potential health issue is an irregular menstrual cycle
  • the criteria for determining the irregular menstrual cycle includes a determination that the difference between the maximum menstrual cycle length and minimum menstrual cycle length for the user for a predetermined period of time is greater than a threshold value (e.g., the difference is greater than or equal to 17 days for the latest two nonoverlapping 90 day windows).
  • the potential health issue is an infrequent menstrual cycle
  • the criteria for determining the infrequent menstrual cycle includes a determination that logged menstrual cycle information includes less than a threshold number of logged menstrual periods during a predetermined period of time (e.g., less than two logged menstrual periods in the latest two non-overlapping 90 day windows).
  • the potential health issue is a frequent spotting
  • the criteria for determining the frequent spotting includes a determination that logged menstrual cycle information includes a threshold number of spotting instances within a predefined period of time (e.g., one or more days of spotting logged non-adjacent to a menstrual period in the latest two non-overlapping 90 day windows).
  • electronic device 600 displays an indication that the potential health issue does not apply to the user (and does not display user interface 1058). However, if the user selects option 1044c, and modifies the underlying menstrual cycle information, and the modified menstrual cycle information still indicates a potential health issue for the user, electronic device 600 displays user interface 1058.
  • a potential health issue when a user confirms a potential health issue (e.g., by confirming the underlying menstrual cycle information, as shown in FIGS. 10K-10L), the potential health issue is displayed in cycle history user interface 848 (of FIG. 8H) and/or cycle detail user interface 854 (of FIG. 81).
  • unconfirmed potential health issues are not displayed in these user interfaces, but confirmed potential health issues are displayed in these user interfaces.
  • cycle history user interface 848 and/or cycle detail user interface 854 displays an option that is selectable to export a 12-month menstrual cycle history (similar to option 1060c).
  • cycle history user interface 848 and/or cycle detail user interface 854 does not display an option that is selectable to export the 12-month menstrual cycle history.
  • notification 1038a and/or notification 1052 are not displayed and/or generated in response to a lack of data entry by a user and/or a lack of interaction by a user in order to avoid false positives and/or inaccurate notifications.
  • notifications of potential health issues are only generated based on menstrual cycle information that is entered by a user.
  • notifications of potential health issues are not generated and/or displayed if the user indicates that one or more predetermined health factors (e.g., use of contraception and/or pregnancy) are applicable to the user and/or have been applicable to the user within a threshold duration of time (e.g., within the last 12 weeks).
  • predetermined health factors e.g., use of contraception and/or pregnancy
  • FIG. 10M depicts electronic device 1070 with touch-sensitive display 1072.
  • electronic device 1070 displays sharing user interface 1074.
  • Electronic device 1070 corresponds to a different user from electronic device 600.
  • electronic device 600 corresponds to a user named Jane Appleseed
  • electronic device 1070 corresponds to a user named Sarah.
  • Jane Appleseed has chosen to share menstrual cycle information with Sarah.
  • sharing user interface 1074 includes object 1076a which indicates that Sarah is able to view menstrual cycle information corresponding to user Jane Appleseed.
  • sharing user interface 1074 includes objects 1076b and 1076c, which indicate that the user Sarah is sharing menstrual cycle information with user “Mom” and is also sharing menstrual cycle information with Jane Appleseed.
  • Object 1076a indicates that there are one or more alerts corresponding to user Jane Appleseed (e.g., based on the determination that one or more potential health issues have been identified for user Jane Appleseed based on menstrual cycle information corresponding to user Jane Appleseed).
  • electronic device 1070 detects user input 1078 (e.g., a touch input and/or a tap input) corresponding to selection of object 1076a.
  • electronic device 1070 displays user interface 1080.
  • User interface 1080 corresponds to user Jane Appleseed, and includes indication 1082e which indicates that electronic device 600 has determined that Jane Appleseed has the potential health issue of prolonged periods.
  • indication 1082e is displayed in user interface 1080 only after the user of electronic device 600 confirms the potential health issue (e.g., by confirming the accuracy of the underlying menstrual cycle information). In some embodiments, unconfirmed potential health issues are not displayed in user interface 1080.
  • User interface 1080 also includes option 1082g that is selectable to cease display of indication 1082e, and option 1082f that is selectable to display additional details about the potential health issue identified for Jane Appleseed.
  • User interface 1080 also includes options 1082a-1082d, 1082h, and 1082i.
  • Option 1082a is selectable to initiate a process for sending a text message to user Jane Appleseed (e.g., display a text message user interface).
  • Option 1082b is selectable to initiate a process for calling user Jane Appleseed (e.g., display a phone call user interface).
  • Option 1082c is selectable to initiate a process for video calling user Jane Appleseed (e.g., display a video call user interface).
  • Option 1082d is selectable to display contact information for user Jane Appleseed.
  • Option 1082h displays ovulation prediction information for user Jane Appleseed.
  • Option 1082i is selectable to return to user interface 1074.
  • FIG. 11 is a flow diagram illustrating a method for generating and providing health-related notifications using a computer system in accordance with some embodiments.
  • Method 1100 is performed at a computer system (e.g., 100, 300, 500) (e.g., 600 and/or 800) (e.g., a wearable device, a smart watch, a smart phone, a tablet, and/or a computer system controlling an external display) that is in communication 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 depressible input mechanism; and/or a rotatable and depress
  • method 1100 provides an intuitive way for generating and providing health-related notifications.
  • the method reduces the cognitive burden on a user for generating and/or receiving health-related notifications, thereby creating a more efficient human-machine interface.
  • the computer system receives (1102), via the one or more input devices (e.g., 601, 602, 802, 804, and/or 806), menstrual cycle information (e.g., information identifying one or more dates during which a user was menstruating; and/or information identifying one or more dates during which a user exhibited spotting) for a user (e.g., inputted by the user via one or more user inputs) (e.g., one or more touch inputs, one or more nontouch inputs, and/or one or more gestures) (e.g., menstrual cycle information received in FIGS. 10A-10D).
  • menstrual cycle information e.g., information identifying one or more dates during which a user was menstruating; and/or information identifying one or more dates during which a user exhibited spotting
  • the computer system displays (1106), via the display generation component, a push notification (e.g., 1052) (e.g., a notification that causes the display generation component to transition from an inactive (e.g., off 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 content) in order to display the push notification and/or a notification that is generated by a second application and is overlaid on and/or displayed concurrently with a user interface corresponding to a first application that is different from the second application) that indicates to the user that the computer system has identified a potential health issue for the user.
  • a push notification e.g., 1052
  • an inactive state e.g., off state and/or a state in which the display generation component does not display content
  • an active state e.g., an on state and/or a state in which the display generation component displays content
  • the computer system in accordance with a determination that the menstrual cycle information does not satisfy the first set of criteria indicative of a potential health issue, the computer system forgoes displaying the push notification. Automatically displaying a push notification that indicates to the user that the computer system has identified a potential health issue for the user in accordance with a determination that the menstrual cycle information satisfies a first set of criteria informs the user of a potential health issue with fewer user inputs, thereby reducing the number of user inputs required to perform an operation.
  • Automatically displaying a push notification that indicates to the user that the computer system has identified a potential health issue for the user in accordance with a determination that the menstrual cycle information satisfies a first set of criteria provides the user with visual feedback about the state of the system (e.g., that the system has identified a potential health issue for the user based on menstrual cycle information corresponding to the user), thereby providing improved visual feedback to the user.
  • the push notification causes the display generation component (e.g., 602) to transition from an inactive state (e.g., in FIG. 101) (e.g., off state and/or a state in which the display generation component does not display content) to an active state (e.g., in FIG. 10J) (e.g., an on state and/or a state in which the display generation component displays content).
  • an inactive state e.g., in FIG. 101
  • an active state e.g., in FIG. 10J
  • displaying the push notification comprises displaying the push notification while maintaining the computer system in a locked state (e.g., user interface 840 and/or indication 842a in FIG. 10J indicate that electronic device 600 is in a locked state) (e.g., a state in which one or more features and/or one or more sets of content of the computer system are inaccessible to a user and/or a state in which authentication information is required to transition the computer system to an unlocked state).
  • a locked state e.g., user interface 840 and/or indication 842a in FIG. 10J indicate that electronic device 600 is in a locked state
  • a locked state e.g., a state in which one or more features and/or one or more sets of content of the computer system are inaccessible to a user and/or a state in which authentication information is required to transition the computer system to an unlocked state.
  • the first set of criteria includes a first criterion that is satisfied when a difference between a maximum menstrual cycle duration during a predetermined period of time (e.g., the duration of a menstrual cycle having the longest duration during the predetermined period of time (e.g., previous sixty days, previous ninety days, or previous 120 days)) and a minimum menstrual cycle duration during the predetermined period of time (e.g., the duration of a menstrual cycle having the shortest
  • the first set of criteria includes a second criterion that is satisfied when the first criterion is satisfied for multiple, consecutive pre-defined time periods (e.g., the first criterion is satisfied for the previous two non-overlapping 90 day windows) and the first set of criteria are satisfied when the first criterion and the second criterion are both satisfied (e.g., difference between maximum menstrual cycle duration and minimum menstrual cycle duration is greater than the threshold value for each of the last two non-overlapping 90 day windows).
  • Displaying the push notification that indicates to the user that the computer system has identified a potential health issue for a user only when it is determined that the menstrual cycle information satisfies a first set of criteria improves the user-device interface by ensuring that a user is only presented with push notifications that are relevant to the user.
  • the first set of criteria includes a second criterion that is satisfied when the menstrual cycle information for the user indicates that the user has experienced (e.g., the user has logged and/or entered) less than a threshold number of menstrual periods within a predetermined period of time (e.g., less than two logged menstrual periods in the latest two non-overlapping 90 day windows). Displaying the push notification that indicates to the user that the computer system has identified a potential health issue for a user only when it is determined that the menstrual cycle information satisfies a first set of criteria improves the user-device interface by ensuring that a user is only presented with push notifications that are relevant to the user.
  • the first set of criteria includes a third criterion that is satisfied when the menstrual cycle information for the user indicates that, within a defined period of time (e.g., in the previous 180 days, in the previous 90 days, in the previous six months, in the previous three months, or in the previous 24 weeks), the user has experienced (e.g., the user has logged and/or entered) greater than a threshold number of menstrual periods that have had a duration that is greater than a threshold duration (e.g., two or more menstrual periods within the defined period of time that lasted 10 or more days, and/or two or more menstrual periods that started within the defined period of time (e.g., that started within the last 180 days) that lasted 10 or more days).
  • a threshold duration e.g., two or more menstrual periods within the defined period of time that lasted 10 or more days, and/or two or more menstrual periods that started within the defined period of time (e.g., that started within the last 180 days) that lasted 10
  • Displaying the push notification that indicates to the user that the computer system has identified a potential health issue for a user only when it is determined that the menstrual cycle information satisfies a first set of criteria improves the user-device interface by ensuring that a user is only presented with push notifications that are relevant to the user.
  • the first set of criteria includes a fourth criterion that is satisfied when the menstrual cycle information for the user indicates that, within a defined period of time (e.g., in the latest two non-overlapping 90 day windows and/or in the latest two non-overlapping three-month windows), the user has experienced (e.g., the user has logged and/or entered) greater than a threshold number of spotting instances that did not occur during a menstrual period and/or directly adjacent to (e.g., directly before and/or after; and/or the day before and/or after) a menstrual period (e.g., one or more days of spotting logged non-adjacent to a menstrual period in the latest two non-overlapping 90 day windows).
  • a defined period of time e.g., in the latest two non-overlapping 90 day windows and/or in the latest two non-overlapping three-month windows
  • Displaying the push notification that indicates to the user that the computer system has identified a potential health issue for a user only when it is determined that the menstrual cycle information satisfies a first set of criteria improves the user-device interface by ensuring that a user is only presented with push notifications that are relevant to the user.
  • the computer system subsequent to displaying the push notification (e.g., 1052) (1108), the computer system receives (1110) second menstrual cycle information (e.g., additional menstrual cycle information, new menstrual cycle information, and/or second menstrual cycle information that includes the menstrual cycle information (and, in some embodiments, additional menstrual cycle information in addition to the menstrual cycle information)) for the user (e.g., user entering menstrual cycle information in FIGS. 10A- 10D).
  • second menstrual cycle information e.g., additional menstrual cycle information, new menstrual cycle information, and/or second menstrual cycle information that includes the menstrual cycle information (and, in some embodiments, additional menstrual cycle information in addition to the menstrual cycle information)
  • the computer system displays, via the display generation component, a second push notification (e.g., another push notification similar to and/or identical to push notification 1052) (e.g., a second push notification that causes the display generation component to transition from an inactive (e.g., off 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 content) in order to display the second push notification and/or a second push notification that is generated by a second application and is overlaid
  • a second push notification e.g., another push notification similar to and/or identical to push notification 1052
  • an active state e.g., an on state and/or a state in which the display generation component displays content
  • the computer system subsequent to receiving the second menstrual cycle information, and in accordance with a determination that the second menstrual cycle information does not satisfy the first set of criteria, the computer system forgoes displaying the second push notification. Automatically forgoing display of the second push notification if less than a threshold duration of time has passed since the previous push notification improves the user-device interface by ensuring that a user is not inundated with too many push notifications pertaining to the same issue.
  • the computer system receives third menstrual cycle information (e.g., user entering menstrual cycle information in FIGS. 10A- 10D) (e.g., additional menstrual cycle information, new menstrual cycle information, and/or third menstrual cycle information that includes the menstrual cycle information (and, in some embodiments, additional menstrual cycle information in addition to the menstrual cycle information)) for the user.
  • third menstrual cycle information e.g., user entering menstrual cycle information in FIGS. 10A- 10D
  • additional menstrual cycle information e.g., additional menstrual cycle information, new menstrual cycle information, and/or third menstrual cycle information that includes the menstrual cycle information (and, in some embodiments, additional menstrual cycle information in addition to the menstrual cycle information)
  • the computer system displays, via the display generation component (e.g., 602), a third push notification (e.g., 1052) (e.g., a notification that causes the display generation component to transition from an inactive (e.g., off 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 content) in order to display the push notification and/or a notification that is generated by a second application and is overlaid on and/or displayed concurrently with a user interface corresponding to a first application that is different from the second application) that indicates to the user that
  • a third push notification e.g., 1052
  • push notifications that indicate that the computer system has identified a potential health issue for the user are generated and/or displayed only based on user-inputted menstrual cycle information and/or user-confirmed menstrual cycle information, and are not generated and/or displayed based on a lack of interaction and/or a lack of data entry by a user (e.g., if the user has not logged and/or entered menstrual cycle information for a period of time, the computer system does not assume that the user has not menstruated and/or had a menstrual period for the period of time and does not generate push notifications based on the lack of data for the period of time).
  • the determination that the third menstrual cycle information was not entered by a user comprises a determination that no user input was received on any computer system to enter, log, and/or confirm the third menstrual cycle information. Displaying the push notification that indicates to the user that the computer system has identified a potential health issue for a user only when it is determined that the menstrual cycle information satisfies a first set of criteria improves the user-device interface by ensuring that a user is only presented with push notifications that are relevant to the user.
  • the first set of criteria includes a sixth criterion that is satisfied when one or more predetermined health factors (e.g., health factors in FIG. 8A and/or “factors” 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).
  • predetermined health factors e.g., health factors in FIG. 8A and/or “factors” option 834d
  • the computer system forgoes displaying the push notification.
  • the first set of criteria includes a seventh criterion that is satisfied when one or more predetermined health factors (e.g., health factors in FIG. 8A and/or “factors” option 834d) have not been applicable to the user for at least a threshold duration of time (e.g., the user has not been pregnant and/or has not used contraception for at least the threshold duration of time (e.g., 12 weeks, 3 months, and/or 90 days)).
  • a threshold duration of time e.g., the user has not been pregnant and/or has not used contraception for at least the threshold duration of time (e.g., 12 weeks, 3 months, and/or 90 days).
  • the computer system when it is determined that at least one of the one or more predetermined health factors have been applicable to the user within the threshold duration of time (e.g., the user was pregnant and/or the user was using contraception within the previous 12 weeks, 3 months, and/or 90 days), the computer system forgoes displaying the push notification. Displaying the push notification only if one or more predetermined health factors have not been applicable to the user for at least the threshold duration of time improves the user-device interface by avoiding presenting the user with information that does not apply to the user.
  • the threshold duration of time e.g., the user was pregnant and/or the user was using contraception within the previous 12 weeks, 3 months, and/or 90 days
  • the computer system while displaying the push notification (e.g., 1052), the computer system (e.g., 600 and/or 800) receives, via the one or more input devices, a selection input (e.g., 1054) (e.g., one or more touch inputs, one or more non-touch inputs, and/or one or more gestures) corresponding to selection of the push notification.
  • a selection input e.g., 1054
  • a selection input e.g., one or more touch inputs, one or more non-touch inputs, and/or one or more gestures
  • the computer system displays, via the display generation component, a cycle history user interface (e.g., 1042), wherein the cycle history user interface includes: a first option (e.g., 1044b) that is selectable to confirm a cycle history of the user (e.g., a log and/or historical data containing historical menstrual cycle information for the user (e.g., for a predefined period of time (e.g., the last 3 months of cycle history and/or the last 6 months of cycle history)) (e.g., selectable to confirm that the cycle history of the user is accurate); and a second option (e.g., 1044c) that is selectable to revise the cycle history of the user (e.g., a second option that is selectable to display a history revision user interface that allows the user to correct and/or change menstrual cycle information for the user) (e.g., a second option that is selectable to indicate that the cycle history of the user is not accurate) (e.g., a first option (
  • the computer system receives, via the one or more input devices, a second selection input (e.g., 1056) (e.g., one or more touch inputs, one or more non-touch inputs, and/or one or more gestures) corresponding to selection of the first option (e.g., 1044b).
  • a second selection input e.g., 1056
  • the computer system receives, via the one or more input devices, a second selection input (e.g., 1056) (e.g., one or more touch inputs, one or more non-touch inputs, and/or one or more gestures) corresponding to selection of the first option (e.g., 1044b).
  • the computer system displays, via the display generation component, first information identifying the potential health issue for the user (e.g., 1060a) (e.g., text and/or graphics identifying and/or naming the potential health issue for the user (e.g., irregular menstrual cycle, infrequent menstrual cycle, prolonged menstrual cycle, and/or frequent spotting)).
  • first information identifying the potential health issue for the user e.g., 1060a
  • the potential health issue for the user e.g., 1060a
  • Displaying the first information identifying the potential health issue for the user only after the user confirms the user’s cycle history improves the user-device interface by ensuring that potentially inaccurate or faulty information is not presented to the user until the user confirms the underlying menstrual cycle information.
  • the computer system in response to receiving the second selection input (e.g., 1056), displays (e.g., concurrently with the first information), via the display generation component, a third option (e.g., 1060c) that is selectable to initiate a process for exporting (e.g., printing, saving, sending, and/or transmitting) a file (e.g., a document file, a PDF file, and/or a graphics file) containing menstrual cycle history information corresponding to the user (e.g., a 12-month menstrual cycle history for the user).
  • a file e.g., a document file, a PDF file, and/or a graphics file
  • menstrual cycle history information e.g., a 12-month menstrual cycle history for the user.
  • the computer system while displaying the cycle history user interface (e.g., 1042), receives, via the one or more input devices, a third selection input (e.g., one or more touch inputs, one or more non-touch inputs, and/or one or more gestures) corresponding to selection of the second option (e.g., 1044c). Subsequent to receiving the third selection input, the computer system receives, via the one or more input devices, corrected menstrual cycle information (e.g., receiving one or more user inputs revising the cycle history of the user, correcting the cycle history of the user, and/or entering corrected menstrual cycle information) corresponding to the user.
  • a third selection input e.g., one or more touch inputs, one or more non-touch inputs, and/or one or more gestures
  • corrected menstrual cycle information e.g., receiving one or more user inputs revising the cycle history of the user, correcting the cycle history of the user, and/or entering corrected menstrual cycle information
  • the computer system In response to receiving the corrected menstrual cycle information: in accordance with a determination that the corrected menstrual cycle information satisfies the first set of criteria, the computer system displays, via the display generation component, second information identifying the potential health issue for the user (e.g., 1060a) (e.g., text and/or graphics identifying and/or naming the potential health issue for the user (e.g., irregular menstrual cycle, infrequent menstrual cycle, prolonged menstrual cycle, and/or frequent spotting)); and in accordance with a determination that the corrected menstrual cycle information does not satisfy the first set of criteria, the computer system displays, via the display generation component, an indication that potential health issues have not been identified for the user (e.g., based on the corrected menstrual cycle information) (and, in some embodiments, forgoes displaying the second information identifying the potential health issue for the user).
  • second information identifying the potential health issue for the user e.g., 1060a
  • the computer system displays,
  • Displaying information identifying the potential health issue for the user only after the user confirms the user’s cycle history improves the user-device interface by ensuring that potentially inaccurate or faulty information is not presented to the user until the user confirms the underlying menstrual cycle information.
  • the computer system in response to receiving the corrected menstrual cycle information: in accordance with a determination that the corrected menstrual cycle information satisfies the first set of criteria, displays (e.g., concurrently with the second information), via the display generation component, an export option (e.g., 1060c) that is selectable to initiate a process for exporting (e.g., printing, saving, sending, and/or transmitting) a file (e.g., a document file, a PDF file, and/or a graphics file) containing menstrual cycle history information corresponding to the user (e.g., a 12-month menstrual cycle history for the user).
  • an export option e.g., 1060c
  • Automatically displaying the export option in response to receiving the corrected menstrual cycle information and in accordance with a determination that the corrected menstrual cycle information satisfied the first set of criteria allows a user to export menstrual cycle history information with fewer inputs, thereby reducing the number of inputs required to perform an operation.
  • the computer system displays, via the display generation component, a cycle tracking user interface (e.g., 828) (e.g., a cycle tracking user interface corresponding to the user) (e.g., a cycle tracking user interface that includes one or more selectable objects that are selectable by a user to enter and/or log menstrual cycle information), wherein: in accordance with a determination that the menstrual cycle information satisfies the first set of criteria, displaying the cycle tracking user interface includes displaying (e.g., within the cycle tracking user interface) a first indicator (e.g., 1038a) (e.g., a visual object and/or visual indication) that indicates to the user that the computer system has identified a potential health issue for the user.
  • a cycle tracking user interface e.g., 828
  • a cycle tracking user interface corresponding to the user e.g., a cycle tracking user interface that includes one or more selectable objects that are selectable by a user to enter and/or log menstrual cycle information
  • the cycle tracking user interface does not include the first indicator. Automatically displaying a first indicator that indicates to the user that the computer system has identified a potential health issue for the user in accordance with a determination that the menstrual cycle information satisfies a first set of criteria informs the user of a potential health issue with fewer user inputs, thereby reducing the number of user inputs required to perform an operation.
  • Automatically displaying a first indicator that indicates to the user that the computer system has identified a potential health issue for the user in accordance with a determination that the menstrual cycle information satisfies a first set of criteria provides the user with visual feedback about the state of the system (e.g., that the system has identified a potential health issue for the user based on menstrual cycle information corresponding to the user), thereby providing improved visual feedback to the user.
  • the computer system subsequent to displaying cycle tracking user interface (e.g., 828), including the first indicator (e.g., 1038a), the computer system receives, via the one or more input devices, second updated menstrual cycle information for the user (e.g., user entering updated menstrual cycle information, similar to FIGS. 10A-10D) (e.g., second updated menstrual cycle information that includes additional menstrual cycle information that is not included in the menstrual cycle information).
  • second updated menstrual cycle information for the user e.g., user entering updated menstrual cycle information, similar to FIGS. 10A-10D
  • second updated menstrual cycle information that includes additional menstrual cycle information that is not included in the menstrual cycle information.
  • the computer system re-displays the cycle tracking user interface (e.g., 828), wherein: in accordance with a determination that the second updated menstrual cycle information does not satisfy the first set of criteria, the cycle tracking user interface does not include the first indicator (e.g., 1038a) (e.g., cycle tracking user interface 828 in FIG. 10E does not include the first indicator 1038a because electronic device 600 has not detected any potential health issues for the user based on entered menstrual cycle information) (in some embodiments, re-displaying the cycle tracking user interface includes forgoing display of the first indicator).
  • the cycle tracking user interface includes forgoing display of the first indicator.
  • re-displaying the cycle tracking user interface includes displaying (within the cycle tracking user interface) the first indicator. Excluding the first indicator and/or forgoing display of the first indicator in accordance with a determination that the second updated menstrual cycle information does not satisfy the first set of criteria improves the user-device interface by ensuring that inaccurate, irrelevant, and/or faulty information is not presented to the user.
  • the computer system receives, via the one or more input devices, one or more confirmation inputs (e.g., 1056) (e.g., one or more touch inputs, one or more non-touch inputs, and/or one or more gestures) confirming the menstrual cycle information for the user (e.g., one or more user inputs indicating that the user confirms the accuracy of the menstrual cycle information for the user and/or indicating that the user confirms the accuracy of menstrual cycle history information for the user).
  • one or more confirmation inputs e.g., 1056
  • the computer system receives, via the one or more input devices, one or more confirmation inputs (e.g., 1056) (e.g., one or more touch inputs, one or more non-touch inputs, and/or one or more gestures) confirming the menstrual cycle information for the user (e.g., one or more user inputs indicating that the user confirms the accuracy of the menstrual cycle information for the user and/or indicating that the user
  • the computer system In response to receiving the one or more confirmation inputs: in accordance with a determination that the user of the computer system has elected to share menstrual cycle information with a second user different from the user of the computer system, the computer system causes an external device (e.g., 1070) (e.g., a wearable device, a smart watch, a smart phone, a tablet, and/or a computer system controlling an external display) (e.g., an external device corresponding to an external user different from the user of the computer system) separate from the computer system and corresponding to the second user to display (e.g., via one or more display generation components in communication with the external device) a first visual indication (e.g., 1076a and/or 1082e) indicating that the computer system (e.g., 600) has identified a potential health issue for the user.
  • an external device e.g., 1070
  • a wearable device e.g., a smart watch, a smart phone, a tablet, and/or
  • the computer system subsequent to displaying the push notification, and prior to receiving the one or more confirmation inputs, the computer system forgoes causing and/or does not cause the external device to display the first visual indication. Automatically causing the external device to display the first visual indication in response to receiving the one or more confirmation inputs allows a user to share health information with fewer user inputs, thereby reducing the number of user inputs required to perform an operation.
  • the computer system displays, via the display generation component (e.g., 602), a cycle history user interface (e.g., 848 and/or 854) (e.g., a user interface that displays historical menstrual cycle information for a user), wherein the cycle history user interface includes one or more health indications indicative of one or more previously identified health issues that were identified by the computer system and confirmed by the user (e.g., in some embodiments, cycle history user interface 848 and/or user interface 854 displays an indication of one or more confirmed potential health issues) (e.g., confirmed by the user based on one or more user inputs confirming the accuracy of underlying menstrual cycle information that was used by the computer system to identify a potential health issue), including: a first health indication indicative of a first previously identified health issue that was identified by the computer system and confirmed by the user.
  • a cycle history user interface e.g., 848 and/or 854
  • the cycle history user interface includes one or more health indications indicative of one or more previously identified health issues that were identified
  • the cycle history user interface does not identify one or more previously identified health issues that were identified by the computer system but were not confirmed by the user (e.g., the user did not confirm the accuracy of underlying menstrual cycle information that was used by the computer system to identify a potential health issue).
  • the cycle history user interface includes a second health indication indicative of a second previously identified health issue that was identified by the computer system and confirm by the user, wherein the second previously identified health issue is different from the first previously identified health issue and the second health indication is different from the first health indication. Displaying a cycle history user interface that displays a history of confirmed health issues provides the user with visual feedback about the state of the system (e.g., that the system has identified one or more potential health issues for the user), thereby providing improved visual feedback to the user.
  • displaying the cycle history user interface further includes displaying a first export option corresponding to the first previously identified health issue and that is selectable to initiate a process for exporting (e.g., printing, saving, sending, and/or transmitting) a file (e.g., a document file, a PDF file, and/or a graphics file) containing menstrual cycle history information corresponding to the user (e.
  • method 700, method 900, and/or method 950 optionally include one or more of the characteristics of the various methods described above with reference to method 1100.
  • the body temperature information that is collected in method 700 can be used to generate health-based notifications and/or predictions in methods 900, 950, and/or 1100. For brevity, these details are not repeated below.
  • this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person.
  • personal information data can include demographic data, locationbased data, telephone numbers, email addresses, social network IDs, home addresses, data or records relating to a user’s health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other identifying or personal information.
  • the present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users.
  • the personal information data can be used to deliver health-related notifications and/or information that is of interest to the user. Accordingly, use of such personal information data enables users to have calculated control of the delivered content.
  • other uses for personal information data that benefit the user are also contemplated by the present disclosure. For instance, health and fitness data may be used to provide insights into a user’s general wellness, or may be used as positive feedback to individuals using technology to pursue wellness goals.
  • the present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices.
  • such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure.
  • Such policies should be easily accessible by users, and should be updated as the collection and/or use of data changes.
  • Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection/sharing should occur after receiving the informed consent of the users.
  • policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations. For instance, in the US, collection of or access to certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Hence different privacy practices should be maintained for different personal data types in each country.
  • HIPAA Health Insurance Portability and Accountability Act
  • the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data.
  • the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services or anytime thereafter.
  • users can select not to receive health-related notifications, predications, and/or information.
  • users can select to limit the length of time health data is maintained or entirely prohibit health-related notifications and/or predictions.
  • the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app.
  • personal information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed.
  • data de-identification can be used to protect a user’s privacy. Deidentification may be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods.
  • the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data.
  • content can be selected and delivered to users by inferring preferences based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the content delivery services and/or health information services, or publicly available information.

Landscapes

  • Health & Medical Sciences (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Medical Informatics (AREA)
  • Molecular Biology (AREA)
  • Pathology (AREA)
  • Engineering & Computer Science (AREA)
  • Biomedical Technology (AREA)
  • Heart & Thoracic Surgery (AREA)
  • Veterinary Medicine (AREA)
  • Public Health (AREA)
  • Surgery (AREA)
  • Animal Behavior & Ethology (AREA)
  • General Health & Medical Sciences (AREA)
  • Biophysics (AREA)
  • Physics & Mathematics (AREA)
  • Measuring And Recording Apparatus For Diagnosis (AREA)

Abstract

La présente invention concerne de manière générale le suivi d'informations de santé et la génération de prédictions et/ou de notifications et/ou des notifications associées.
PCT/US2023/031421 2022-09-06 2023-08-29 Interfaces utilisateur pour suivi de santé WO2024054378A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202263404139P 2022-09-06 2022-09-06
US63/404,139 2022-09-06
US18/237,339 2023-08-23
US18/237,339 US20240079130A1 (en) 2022-09-06 2023-08-23 User interfaces for health tracking

Publications (2)

Publication Number Publication Date
WO2024054378A1 true WO2024054378A1 (fr) 2024-03-14
WO2024054378A4 WO2024054378A4 (fr) 2024-05-10

Family

ID=88188825

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2023/031421 WO2024054378A1 (fr) 2022-09-06 2023-08-29 Interfaces utilisateur pour suivi de santé

Country Status (1)

Country Link
WO (1) WO2024054378A1 (fr)

Citations (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3859005A (en) 1973-08-13 1975-01-07 Albert L Huebner Erosion reduction in wet turbines
US4826405A (en) 1985-10-15 1989-05-02 Aeroquip Corporation Fan blade fabrication system
EP1077046A1 (fr) * 1998-05-06 2001-02-21 Matsushita Electric Industrial Co., Ltd. Thermometre auriculaire a usage feminin
US6323846B1 (en) 1998-01-26 2001-11-27 University Of Delaware Method and apparatus for integrating manual input
US6570557B1 (en) 2001-02-10 2003-05-27 Finger Works, Inc. Multi-touch system and method for emulating modifier keys via fingertip chords
US6677932B1 (en) 2001-01-28 2004-01-13 Finger Works, Inc. System and method for recognizing touch typing under limited tactile feedback conditions
US20040081024A1 (en) * 2002-10-23 2004-04-29 Yuan Sung Weng Wristwatch with functions of basal body temperature charting and ovulation phase informing
US20050190059A1 (en) 2004-03-01 2005-09-01 Apple Computer, Inc. Acceleration-based theft detection system for portable electronic devices
US20060017692A1 (en) 2000-10-02 2006-01-26 Wehrenberg Paul J Methods and apparatuses for operating a portable device based on an accelerometer
US7657849B2 (en) 2005-12-23 2010-02-02 Apple Inc. Unlocking a device by performing gestures on an unlock image
WO2013169849A2 (fr) 2012-05-09 2013-11-14 Industries Llc Yknots Dispositif, procédé et interface utilisateur graphique permettant d'afficher des objets d'interface utilisateur correspondant à une application
WO2014105276A1 (fr) 2012-12-29 2014-07-03 Yknots Industries Llc Dispositif, procédé et interface utilisateur graphique pour effectuer une transition entre des relations d'entrée tactile et de sortie d'affichage
CN104680459A (zh) * 2015-02-13 2015-06-03 北京康源互动健康科技有限公司 一种基于云平台的经期管理系统及方法
WO2015164845A1 (fr) * 2014-04-26 2015-10-29 Lindsey Sanders Capteur de température à cavité créée
US20160296210A1 (en) * 2013-11-28 2016-10-13 Rakuten, Inc. Information processing device, information processing method, and information processing program
WO2017054277A1 (fr) * 2015-09-29 2017-04-06 宇龙计算机通信科技(深圳)有限公司 Procédé de gestion d'un mode anti-dérangement et terminal d'utilisateur
US20210257091A1 (en) * 2020-02-14 2021-08-19 Dexcom, Inc. Decision support and treatment administration systems
WO2021212112A1 (fr) * 2020-04-17 2021-10-21 Empatica Srl Procédés et systèmes de prévision, détection et surveillance d'infections virales
US20210401378A1 (en) * 2020-06-25 2021-12-30 Oura Health Oy Health Monitoring Platform for Illness Detection
WO2022010573A1 (fr) * 2020-07-08 2022-01-13 Google Llc Utilisation de capteurs de lumière ambiante et de capteurs d'audio ambiant pour déterminer la qualité du sommeil
US20220047250A1 (en) * 2020-08-12 2022-02-17 Apple Inc. In-Bed Temperature Array for Menstrual Cycle Tracking

Patent Citations (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3859005A (en) 1973-08-13 1975-01-07 Albert L Huebner Erosion reduction in wet turbines
US4826405A (en) 1985-10-15 1989-05-02 Aeroquip Corporation Fan blade fabrication system
US6323846B1 (en) 1998-01-26 2001-11-27 University Of Delaware Method and apparatus for integrating manual input
US20020015024A1 (en) 1998-01-26 2002-02-07 University Of Delaware Method and apparatus for integrating manual input
EP1077046A1 (fr) * 1998-05-06 2001-02-21 Matsushita Electric Industrial Co., Ltd. Thermometre auriculaire a usage feminin
US20060017692A1 (en) 2000-10-02 2006-01-26 Wehrenberg Paul J Methods and apparatuses for operating a portable device based on an accelerometer
US6677932B1 (en) 2001-01-28 2004-01-13 Finger Works, Inc. System and method for recognizing touch typing under limited tactile feedback conditions
US6570557B1 (en) 2001-02-10 2003-05-27 Finger Works, Inc. Multi-touch system and method for emulating modifier keys via fingertip chords
US20040081024A1 (en) * 2002-10-23 2004-04-29 Yuan Sung Weng Wristwatch with functions of basal body temperature charting and ovulation phase informing
US20050190059A1 (en) 2004-03-01 2005-09-01 Apple Computer, Inc. Acceleration-based theft detection system for portable electronic devices
US7657849B2 (en) 2005-12-23 2010-02-02 Apple Inc. Unlocking a device by performing gestures on an unlock image
WO2013169849A2 (fr) 2012-05-09 2013-11-14 Industries Llc Yknots Dispositif, procédé et interface utilisateur graphique permettant d'afficher des objets d'interface utilisateur correspondant à une application
WO2014105276A1 (fr) 2012-12-29 2014-07-03 Yknots Industries Llc Dispositif, procédé et interface utilisateur graphique pour effectuer une transition entre des relations d'entrée tactile et de sortie d'affichage
US20160296210A1 (en) * 2013-11-28 2016-10-13 Rakuten, Inc. Information processing device, information processing method, and information processing program
WO2015164845A1 (fr) * 2014-04-26 2015-10-29 Lindsey Sanders Capteur de température à cavité créée
CN104680459A (zh) * 2015-02-13 2015-06-03 北京康源互动健康科技有限公司 一种基于云平台的经期管理系统及方法
WO2017054277A1 (fr) * 2015-09-29 2017-04-06 宇龙计算机通信科技(深圳)有限公司 Procédé de gestion d'un mode anti-dérangement et terminal d'utilisateur
US20210257091A1 (en) * 2020-02-14 2021-08-19 Dexcom, Inc. Decision support and treatment administration systems
WO2021212112A1 (fr) * 2020-04-17 2021-10-21 Empatica Srl Procédés et systèmes de prévision, détection et surveillance d'infections virales
US20210401378A1 (en) * 2020-06-25 2021-12-30 Oura Health Oy Health Monitoring Platform for Illness Detection
WO2022010573A1 (fr) * 2020-07-08 2022-01-13 Google Llc Utilisation de capteurs de lumière ambiante et de capteurs d'audio ambiant pour déterminer la qualité du sommeil
US20220047250A1 (en) * 2020-08-12 2022-02-17 Apple Inc. In-Bed Temperature Array for Menstrual Cycle Tracking

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LUO LAN ET AL: "Detection and Prediction of Ovulation From Body Temperature Measured by an In-Ear Wearable Thermometer", IEEE TRANSACTIONS ON BIOMEDICAL ENGINEERING, IEEE, USA, vol. 67, no. 2, 14 May 2019 (2019-05-14), pages 512 - 522, XP011767231, ISSN: 0018-9294, [retrieved on 20200120], DOI: 10.1109/TBME.2019.2916823 *

Also Published As

Publication number Publication date
WO2024054378A4 (fr) 2024-05-10

Similar Documents

Publication Publication Date Title
US11262902B2 (en) System, method and user interface for supporting scheduled mode changes on electronic devices
US11972853B2 (en) Activity trends and workouts
US11209957B2 (en) User interfaces for cycle tracking
US11662796B2 (en) User interfaces for indicating battery information on an electronic device
US11694590B2 (en) Dynamic user interface with time indicator
US11698710B2 (en) User interfaces for logging user activities
US20230016144A1 (en) User interfaces for cycle tracking
US11831799B2 (en) Propagating context information in a privacy preserving manner
US20230161470A1 (en) System, Method and User Interface for Supporting Scheduled Mode Changes on Electronic Devices
EP3735632A2 (fr) Suggestion d'action de verrouillage de capture multimédia pour interface utilisateur graphique
US11973894B2 (en) Utilizing context information with an electronic device
US20230393616A1 (en) Displaying application views
US20240077309A1 (en) Physical activity user interfaces
WO2024054378A1 (fr) Interfaces utilisateur pour suivi de santé
US20240079130A1 (en) User interfaces for health tracking
US20230396575A1 (en) User interfaces for managing messages
US20230389861A1 (en) Systems and methods for sleep tracking
US20240078002A1 (en) User interfaces for device charging
US12001648B2 (en) User interfaces for logging user activities
US20220391076A1 (en) Activity Stream Foundations
WO2023235608A1 (fr) Systèmes et procédés de suivi de sommeil
WO2024054347A1 (fr) Interfaces utilisateur d'activité physique
WO2023235615A1 (fr) Interfaces utilisateur pour messages et documents partagés
EP4330970A1 (fr) Interfaces utilisateur associées à des données cliniques
WO2023219974A2 (fr) État d'affichage à faible puissance

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23776507

Country of ref document: EP

Kind code of ref document: A1