Patent Application
20240079130
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, however, 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.
Accordingly, 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.
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.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that 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 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.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system 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 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.
In accordance with some embodiments, a computer system is described. The computer system is configured to communicate with a display generation component, one or more input devices, and a temperature sensor, and 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 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.
In accordance with some embodiments, a computer system is described. The computer system is configured to communicate with a display generation component, one or more input devices, and a temperature sensor, and 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 sets of user body temperature information including the first set of user body temperature information.
In accordance with some embodiments, a computer program product is described. The 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 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.
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 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.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that 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.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system 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.
In accordance with some embodiments, a computer system is described. The computer system is configured to communicate with a display generation component and one or more input devices, and 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.
In accordance with some embodiments, a computer system is described. The computer system is configured to communicate with a display generation component and one or more input devices. The computer system 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.
In accordance with some embodiments, a computer program product is described. The 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.
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 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.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that 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.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system 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.
In accordance with some embodiments, a computer system is described. The computer system is configured to communicate with a display generation component and one or more input devices, and 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.
In accordance with some embodiments, a computer system is described. The computer system is configured to communicate with a display generation component and one or more input devices. The computer system 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.
In accordance with some embodiments, a computer program product is described. The 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.
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 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.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that 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.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system 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.
In accordance with some embodiments, a computer system is described. The computer system is configured to communicate with a display generation component and one or more input devices, and 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.
In accordance with some embodiments, a computer system is described. The computer system is configured to communicate with a display generation component and one or more input devices. The computer system 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.
In accordance with some embodiments, a computer program product is described. The 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.
Thus, 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.
For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments.
There is a need for electronic devices that provide efficient methods and interfaces for tracking health information and for generating related predictions and/or notifications. Such techniques can reduce the cognitive burden on a user who track health information, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs.
Below,
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.
In addition, in methods described herein where one or more steps are contingent upon one or more conditions having been met, it should be understood that the described method can be repeated in multiple repetitions so that over the course of the repetitions all of the conditions upon which steps in the method are contingent have been met in different repetitions of the method. For example, if a method requires performing a first step if a condition is satisfied, and a second step if the condition is not satisfied, then a person of ordinary skill would appreciate that the claimed steps are repeated until the condition has been both satisfied and not satisfied, in no particular order. Thus, a method described with one or more steps that are contingent upon one or more conditions having been met could be rewritten as a method that is repeated until each of the conditions described in the method has been met. This, however, is not required of system or computer readable medium claims where the 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 person having ordinary skill in the art would also understand that, similar to a method with contingent steps, 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.
Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. In some embodiments, these terms are used to distinguish one element from another. 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 terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
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. Similarly, 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.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of 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. It should also be understood that, in some embodiments, 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). In some embodiments, 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. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. As used herein, “displaying” content includes 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.
In the discussion that follows, 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.
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. In this way, 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.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a 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. For example, 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. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, 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. In some implementations, 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). In some implementations, 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). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).
As used in the specification and claims, 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. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, 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. As another example, 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. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, 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.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in
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. In some embodiments, 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. 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. 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.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), 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.
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. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
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. In some embodiments, input controller(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 (e.g., 208,
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 Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 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. In an exemplary embodiment, 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. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.
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. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, 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 Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.
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. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface 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.
Device 100 optionally also includes one or more optical sensors 164.
Device 100 optionally also includes one or more depth camera sensors 175.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 optionally also includes one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 optionally also includes one or more accelerometers 168.
In some embodiments, 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. Furthermore, in some embodiments, memory 102 (
Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
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.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, 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). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
In some embodiments, 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). In some embodiments, 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. Additionally, in some implementations, 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). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, 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). As another example, 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. As used herein, the term “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.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, 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.
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 137, e-mail 140, IM 141, browser 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 module 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:
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.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, 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 138, video conference module 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, 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. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, 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.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, 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.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions 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. In some embodiments, 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). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, 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.
In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, 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.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, 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.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, 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.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, 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.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, 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). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, 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).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, 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.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow 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). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, 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.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, 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. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety.
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) 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. For example, video player module is, optionally, combined with music player module into a single module (e.g., video and music player module 152,
In some embodiments, 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. By using 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. In some embodiments, 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. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
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. In some embodiments, 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. In some embodiments, 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.
In some embodiments, 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.
In some embodiments, 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).
In some embodiments, 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.
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.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events 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. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, 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 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are 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. In some embodiments, 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. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, 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 sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, 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. In some embodiments, sub-events in an event (e.g., 187-1 and/or 187-2) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-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. In another example, the definition for event 2 (187-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). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definitions 186 include a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view 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.
In some embodiments, 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.
When 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.
In some embodiments, 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. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, 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.
In some embodiments, 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. In some embodiments, 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.
In some embodiments, 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.
In some embodiments, 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. In some embodiments, 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.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding 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. For example, 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.
Device 100 optionally also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally, executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
In some embodiments, 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. In an alternative embodiment, 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.
Each of the above-identified elements in
Attention is now directed towards embodiments of user interfaces that are, optionally, implemented on, for example, portable multifunction device 100.
It should be noted that the icon labels illustrated in
Although some of the examples that follow will be given with reference to inputs on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, 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). As another example, 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). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Serial No. 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 Nov. 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety.
In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, 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.
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 (
As used here, 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 (
As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, 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
As used in the specification and claims, 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 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. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact 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, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, 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.
As used herein, an “installed application” refers to a software application that has been downloaded onto an electronic device (e.g., devices 100, 300, and/or 500) and is ready to be launched (e.g., become opened) on the device. In some embodiments, 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.
As used herein, the terms “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:
As used herein, 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. Generally, 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.
In some embodiments, the computer system is in a locked state or an unlocked state. In the locked state, the computer system is powered on and 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. In some embodiments, in 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. 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.
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that are implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.
At
In
At
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
At
Focus user interface 630e includes 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. When toggle 630e is toggled to a disabled (or “off”) state, when electronic device 600 enters a particular focus state and/or operates in the particular focus state, other corresponding devices are not automatically caused to operate in the particular focus state such that even if electronic device 600 suppresses a notification while it is operating in the selected focus state, a different corresponding device is still able to output a notification. Focus user interface 628 also includes option 630f that is selectable to return to settings user interface 622. At
At
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). In other words, for a certain subset of people identified by the user, even when electronic device 600 is operating in the sleep focus state, notifications pertaining to those people (e.g., notifications of messages and/or calls received from those people) are not suppressed, whereas notifications pertaining to other people are suppressed. For example, in some embodiments, if a user selects a first contact as being permitted to disturb the user while the sleep focus state is active, when a message is received from the first contact 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. However, notifications pertaining to messages from other users that were not selected by the user will be suppressed because the sleep focus state is active. Similarly, 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. When 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). When 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. In some embodiments, when the home screen notifications setting is enabled, notifications that would normally be displayed on a home screen of electronic device 600 (e.g., when the sleep focus state is not active) are also displayed on the home screen of electronic device 600 when the sleep focus state is active. When the home screen notifications setting is disabled, notifications that would normally be displayed on the home screen of electronic device 600 are suppressed (e.g., not displayed) when the sleep focus 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. In some embodiments, when the lock screen notifications setting is enabled, notifications that would normally be displayed on a lock screen of electronic device 600 (e.g., when the sleep focus state is not active) are also displayed on the lock screen of electronic device 600 when the sleep focus state is active. When 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. When option 636g is in an on 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). When option 636g is in an off state, 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. When option 636h is in an on 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). When 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
At
At
In
At
At
At
At
At
At
At
At
At
In
As described below, 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. For battery-operated computing devices, enabling a user to track body temperature information faster and more efficiently conserves power and increases the time between battery charges.
The computer system (e.g., 600, 800) 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). 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. During the sleep tracking mode (706) (e.g., while the computer system is in the sleep tracking mode), 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). 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.,
After causing the first set of user body temperature information to be collected (716), 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
Automatically collecting the first set of user body temperature information while the device is in the sleep tracking mode allows for collection of user body temperature information with fewer user inputs, thereby reducing the number of user inputs required to perform an operation. Collecting user body temperature information during a sleep tracking mode that is initiated by a user input reduces the risk that body temperature information is erroneously collected during a non-sleep state (e.g., due to a false positive on a sleep state determination); doing so improves the quality of the data and improves operations performed by the computer system based on body temperature data that is attributed to a sleep state, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing errors) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the system more quickly and efficiently
In some embodiments, 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
In some embodiments, the computer system receives second notification data of the first type. In some embodiments, 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
In some embodiments, 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
In some embodiments, 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). Automatically causing a first external device to collect the first set of user body temperature information while the computer system is in the sleep tracking mode allows for collection of user body temperature information with fewer user inputs, thereby reducing the number of user inputs required to perform an operation.
In some embodiments, prior to receiving the input, 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.,
In some embodiments, subsequent to displaying the body temperature user interface (e.g., 612) that includes the representations of one or more sets of user body temperature information (e.g., 612 in
In some embodiments, 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). 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
In some embodiments, 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
In some embodiments, 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)). In some embodiments, 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.
In some embodiments, the first details user interface (e.g., 668) includes: a start time (e.g., 670b) corresponding to the first set of user 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). 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.
In some embodiments, the body temperature user interface (e.g., 612) includes relative body temperature information corresponding to the first set of user body temperature information (e.g., relative temperature measurements indicating the number of degrees above and/or below a baseline temperature) (and, optionally, does not include absolute temperature measurements); 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.
In some embodiments, the first details user interface (e.g., 668) includes external device information (e.g., 670d) corresponding to the first set of user body temperature information (e.g., information 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.
In some embodiments, the computer system (e.g., 600) receives first notification data corresponding to one or more messages received from a first external user (e.g., a first external user different from a user of the computer system and/or a first external user of a first external device separate from the computer system) and/or one or more messages received from a first application (e.g., a first application running on the computer system and/or a first application running on an external device separate from the computer system). In response to receiving the first notification data: 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 computer system is in the sleep tracking mode, notification data corresponding to one or more messages received from a first subset of external users (e.g., users that are not identified in object 636b in
In some embodiments, 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
In some embodiments, during the sleep tracking mode (e.g., while the computer system is in the sleep tracking mode): 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). In some embodiments, 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.
In some embodiments, the representations of one or more sets of user body temperature information (e.g., body temperature information shown in data chart 614d) 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., data chart 614d in
Note that details of the processes described above with respect to method 700 (e.g.,
At
At
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). In some embodiments, notification 822 is displayed in response to a determination that the user has not enabled sleep tracking, has not enabled body temperature 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. At
At
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
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
As discussed above, in
At
In
At
In
At
At
As described below, 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. For battery-operated computing devices, enabling a user to generate and/or receive ovulation date predictions faster and more efficiently conserves power and increases the time between battery charges.
The computer system (e.g., 600, 800) 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). After (in some embodiments, in response to) receiving the body temperature information corresponding to the user (904), 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.,
In some embodiments, 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
In some embodiments, receiving the body temperature information corresponding to the user (e.g., user body temperature information shown in data chart 614d) 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. 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.
In some embodiments, 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. 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 a first sensor informs the user of an ovulation date prediction with fewer user inputs, thereby reducing the number of user inputs required to perform an operation.
In some embodiments, while displaying the push notification (e.g., 842f and/or 844) (908): the computer system 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. 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
In some embodiments, 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
In some embodiments, displaying the push notification (e.g., 842f and/or 844) 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). In some embodiments, 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. 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 user has enabled fertility tracking 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.
In some embodiments, displaying the push notification (e.g., 842f and/or 844) 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
In some embodiments, displaying the push notification (e.g., 842f and/or 844) is performed in accordance with a determination that one or more predetermined health factors do not apply to the user (e.g.,
In some embodiments, 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). In response to the input, the computer system enters the sleep tracking mode (e.g., sleep focus state in
In some embodiments, 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). 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
In some embodiments, 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 corresponding to the notification data of the first type (e.g., in
In some embodiments, receiving the body temperature information corresponding to the user (e.g., body temperature information shown in data chart 614d) 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. 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.
In some embodiments, 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). 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 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 second type is received), the computer system (e.g., 600) forgoes causing the third external device (e.g., 800) to output the third notification corresponding to the notification data of the second type (e.g., when notifications are suppressed on electronic device 600, notifications are also suppressed on electronic device 800 (e.g., based on setting 630e being enabled)). Automatically suppressing notifications on the third external device when the computer system is in 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.
In some embodiments, the computer system (e.g., 600) 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). After (in some embodiments, in response to) receiving the second body temperature information corresponding to the user: in accordance with a determination that the user has not logged (e.g., entered and/or provided) an ovulation prediction kit test result during a predefined period of time (e.g., no OPK test result is logged in
Note that details of the processes described above with respect to method 900 (e.g.,
As described below, 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. For battery-operated computing devices, enabling a user to generate and/or receive ovulation date predictions faster and more efficiently conserves power and increases the time between battery charges.
The computer system (e.g., 600) 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
In some embodiments, 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. 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.
In some embodiments, 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. 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.
In some embodiments, 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. 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.
In some embodiments, the representation of the predicted ovulation date for the user (e.g., 832a and/or 835d) includes a first color (e.g., at least a portion of the representation of the predicted ovulation 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.
In some embodiments, the computer system (e.g., 600) displays, via the display generation component (e.g., 602), at a fourth time subsequent to the third time, 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) (e.g., at the fourth time), displaying (e.g., within the cycle tracking user interface) a second fertile window prediction (e.g., day representations 832a, 832b, 832c, 832d, 832e, 835b and/or 835c) for the user (e.g., a second fertile window prediction that is different from or the same as the first fertile window prediction and/or the updated fertile window prediction); and in accordance with a determination that the fertility tracking setting is not enabled (e.g., at the fourth time), displaying (e.g., within the cycle tracking user interface) a menstrual period prediction (e.g., 835a) for the user (e.g., a prediction of one or more days during which the user has an increased likelihood of menstruating) without displaying the second fertile window prediction for the user (in some embodiments, without displaying any fertile window prediction for the user). Displaying a fertile window prediction for a user when a fertility tracking setting is enabled, and displaying a menstrual period prediction for the user when the fertility tracking setting is not enabled, improves the user-device interface by avoiding presentation of information that is not relevant and/or of interest to the user.
In some embodiments, 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). After receiving the second body temperature information corresponding to the user, 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, forgoing displaying the representation of the second predicted ovulation date for the user. Displaying a predicted ovulation date for a user when a fertility tracking setting is enabled, and forgoing displaying the predicted ovulation date when the fertility tracking setting is not enabled, improves the user-device interface by avoiding presentation of information that is not relevant and/or of interest to the user.
In some embodiments, 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). 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.,
In some embodiments, 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). 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. 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 user-device interface by avoiding presentation of information that does not apply to the user and/or that is inaccurate.
In some embodiments, 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). In response to the input, the computer system enters the sleep tracking mode (e.g., sleep focus state in
In some embodiments, 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). 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., 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.
In some embodiments, in response to one or more user inputs (e.g., one or more touch inputs, one or more non-touch inputs, and/or one or more gesture inputs) on a second external device (e.g., 800) (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 corresponding to a request to enter 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), wherein: receiving the body temperature information corresponding to the user comprises receiving the body temperature information corresponding to the user from the second external device; and the second external device collects the body temperature information corresponding to the user while the computer system is in the sleep tracking mode. In some embodiments, 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.
In some embodiments, 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). 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 (e.g., 600) forgoes causing the second external device (e.g., 800) to output the second notification corresponding to the notification data of the second type. Automatically suppressing notifications on the second external device when the computer system is in 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.
In some embodiments, after displaying the updated cycle tracking user interface (e.g., 828 in
In some embodiments, displaying the second updated cycle tracking user interface (e.g., 828 in
In some embodiments, the representation of the predicted ovulation date for the user (e.g., 832a in
Note that details of the processes described above with respect to method 950 (e.g.,
In
At
At
At
At
At
In
At
At
At
At
At
In some embodiments, if the user selects option 1044c in
In some embodiments, when a user confirms a potential health issue (e.g., by confirming the underlying menstrual cycle information, as shown in
In some embodiments, 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. In other words, in some embodiments, notifications of potential health issues are only generated based on menstrual cycle information that is entered by a user.
In some embodiments, notifications of potential health issues (e.g., notification 1038a and/or push notification 1052) 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).
At
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.
As described below, 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. For battery-operated computing devices, enabling a user to generate and/or receive health-related notifications faster and more efficiently conserves power and increases the time between battery charges.
The computer system (e.g., 600, 800) 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 non-touch inputs, and/or one or more gestures) (e.g., menstrual cycle information received in
In some embodiments, the push notification (e.g., 1052) causes the display generation component (e.g., 602) to transition from an inactive state (e.g., in
In some embodiments, displaying the push notification (e.g., 1052) comprises displaying the push notification while maintaining the computer system in a locked state (e.g., user interface 840 and/or indication 842a in
In some embodiments, 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 duration during the predetermined period of time) exceeds a threshold value (e.g., the difference is greater than or equal to 14 days, 15 days, 16 days, 17 days, 18 days, or 19 days). In some embodiments, 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.
In some embodiments, 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.
In some embodiments, 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). 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.
In some embodiments, 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). 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.
In some embodiments, 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
In some embodiments, the computer system (e.g., 600 and/or 800) receives third menstrual cycle information (e.g., user entering menstrual cycle information in
In some embodiments, the first set of criteria includes a sixth criterion that is satisfied when one or more predetermined health factors (e.g., health factors in
In some embodiments, the first set of criteria includes a seventh criterion that is satisfied when one or more predetermined health factors (e.g., health factors in
In some embodiments, 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. In response to receiving the selection input, 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 second option that is selectable to initiate a process for revising the cycle history of the user). Automatically displaying the cycle history user interface that includes the first option and the second option in response to a selection input selecting the push notification allows a user to either confirm or revise the user's cycle history with fewer inputs, thereby reducing the number of inputs required to perform an operation.
In some embodiments, while displaying the cycle history user interface (e.g., 1042), 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). In response to receiving the second selection input, 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)). 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.
In some embodiments, in response to receiving the second selection input (e.g., 1056), the computer system 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). Automatically displaying the third option in response to the second selection input allows a user to export menstrual cycle history information with fewer inputs, thereby reducing the number of inputs required to perform an operation.
In some embodiments, while displaying the cycle history user interface (e.g., 1042), the computer system 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. 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). Displaying information identifying the potential health issue for the user only after the user confirms the user's cycle history (e.g., by providing corrected menstrual cycle information) 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.
In some embodiments, 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 (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). 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.
In some embodiments, subsequent to receiving the menstrual cycle information for the user (e.g.,
In some embodiments, 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
In some embodiments, subsequent to displaying the push notification (e.g., 1052), the computer system (e.g., 600) 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). 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. In some embodiments, 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.
In some embodiments, the computer system (e.g., 600) 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. In some embodiments, 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). In some embodiments, 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.
In some embodiments, in accordance with a determination that the first previously identified health issue occurred within a threshold duration of time (e.g., within the last 6 months, within the last 12 months, or within the last 18 months) (e.g., the first previously identified health issue was identified by the computer system within the threshold duration of time, the first previously identified health issue was identified by the computer system based on menstrual cycle information that occurred (e.g., was experienced by the user) within the threshold duration of time, and/or the first previously identified health issue was confirmed by the user within the threshold duration of time), displaying the cycle history user interface (e.g., 848 and/or 854) 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.g., a 12-month menstrual cycle history for the user) (e.g., in some embodiments, cycle history user interface 848 and/or user interface 854 includes a selectable option that is selectable to export menstrual cycle information for one or more confirmed potential health issues that occurred within the threshold period of time); and in accordance with a determination that the first previously identified health issue did not occur within the threshold duration of time, the cycle history user interface does not include the first export option corresponding to the first previously identified health issue. Displaying an export option only if the previously identified health issue occurred within the threshold duration of time improves the user-device interface by helping the user to provide correct inputs, and preventing the user from exporting unimportant, outdated, and/or irrelevant information.
Note that details of the processes described above with respect to method 1100 (e.g.,
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.
Although the disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims.
As described above, one aspect of the present technology is the gathering and use of data available from various sources to improve the delivery to users of health-related notifications and/or information or any other content that may be of interest to them. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based 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. For example, 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. Further, 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. In particular, 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. Additionally, such entities should consider taking any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. In addition, 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.
Despite the foregoing, 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. For example, in the case of health-related information, 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. In another example, users can select not to receive health-related notifications, predications, and/or information. In yet another example, users can select to limit the length of time health data is maintained or entirely prohibit health-related notifications and/or predictions. In addition to providing “opt in” and “opt out” options, 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.
Moreover, it is the intent of the present disclosure that 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. In addition, and when applicable, including in certain health related applications, data de-identification can be used to protect a user's privacy. De-identification 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.
Therefore, although 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. For example, 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.
This application claims priority to U.S. Provisional Patent Application No. 63/404,139, filed Sep. 6, 2022, the contents of which are incorporated by reference in their entirety.
| Number | Date | Country | |
|---|---|---|---|
| 63404139 | Sep 2022 | US |
