User interface related to physiological measurements

Abstract

It is detected that a physiological parameter of a user is at a first level during a first activity and at a second level during a second activity, and a predictive change in the physiological parameter if the second activity is a third activity different from the second activity is displayed based on the first level and the second level.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 348,938, filed on June 3, 2022, entitled “USER INTERFACES RELATED TO PHYSIOLOGICAL MEASUREMENTS” and U.S. Patent Application No. 17 / 982,968, filed on November 8, 2022, entitled “USER INTERFACES RELATED TO PHYSIOLOGICAL MEASUREMENTS”. The contents of each of these patent applications are incorporated herein by reference in their entirety. Technical Field

[0003] The present disclosure relates generally to computer user interfaces, and more particularly to techniques for displaying a user interface that includes information related to physiological measurements. Background Art

[0004] Personal electronic devices allow users to view information related to physiological measurements. Some personal electronic devices include the ability to collect physiological measurements of users. Some personal electronic devices include the ability to display a user interface related to physiological measurements. Summary of the invention

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

[0006] Thus, the present technology provides a faster, more efficient method and interface for displaying a user interface including information related to physiological measurements for an electronic device. Such methods and interfaces optionally supplement or replace other methods for displaying a user interface including information related to physiological measurements. Such methods and interfaces reduce the cognitive burden on the user and produce a more efficient human-computer interface. For battery-powered computing devices, such methods and interfaces save power and increase the time interval between battery charges.

[0007] According to some embodiments, a method is described that is performed at a computer system that communicates with a display generation component and one or more sensors. The method includes: when a user of the computer system performs a first activity, detecting via one or more sensors that a physiological parameter of the user of the computer system is at a first level; after detecting that the physiological parameter is at the first level and when the user of the computer system performs a second activity different from the first activity, detecting via one or more sensors that the physiological parameter of the user of the computer system is at a second level different from the first level; and displaying via the display generation component and based on the first level and the second level, a predicted change in the physiological parameter if the second activity is a third activity different from the second activity.

[0008] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more sensors, and the one or more programs include instructions for performing the following operations: when a user of the computer system performs a first activity, detecting via one or more sensors that a physiological parameter of the user of the computer system is at a first level; after detecting that the physiological parameter is at the first level and when the user of the computer system performs a second activity different from the first activity, detecting via one or more sensors that the physiological parameter of the user of the computer system is at a second level different from the first level; and displaying via the display generation component and based on the first level and the second level, a predictive change in the physiological parameter if the second activity is a third activity different from the second activity.

[0009] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more sensors, and the one or more programs include instructions for performing the following operations: when a user of the computer system performs a first activity, detecting via one or more sensors that a physiological parameter of the user of the computer system is at a first level; after detecting that the physiological parameter is at the first level and when the user of the computer system performs a second activity different from the first activity, detecting via one or more sensors that the physiological parameter of the user of the computer system is at a second level different from the first level; and displaying via the display generation component and based on the first level and the second level, a predicted change in the physiological parameter if the second activity is a third activity different from the second activity.

[0010] According to some embodiments, a computer system configured to communicate with a display generation component and one or more sensors is described. The computer system includes: one or more processors; and a memory storing one or more programs, the one or more programs being configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: when the user of the computer system performs a first activity, detecting via one or more sensors that a physiological parameter of the user of the computer system is at a first level; after detecting that the physiological parameter is at the first level and when the user of the computer system performs a second activity different from the first activity, detecting via one or more sensors that the physiological parameter of the user of the computer system is at a second level different from the first level; and displaying via the display generation component and based on the first level and the second level, a predictive change in the physiological parameter if the second activity is a third activity different from the second activity.

[0011] According to some embodiments, a computer system configured to communicate with a display generation component and one or more sensors is described. The computer system includes: when the user of the computer system performs a first activity, a device for detecting via one or more sensors that a physiological parameter of the user of the computer system is at a first level; after detecting that the physiological parameter is at the first level and when the user of the computer system performs a second activity different from the first activity, a device for detecting via one or more sensors that the physiological parameter of the user of the computer system is at a second level different from the first level; and a device for performing the following operations: displaying, via the display generation component and based on the first level and the second level, a predicted change in the physiological parameter if the second activity is a third activity different from the second activity.

[0012] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a computer system communicating with a display generation component and one or more sensors. The one or more programs include instructions for performing the following operations: when a user of the computer system performs a first activity, detecting via one or more sensors that a physiological parameter of the user of the computer system is at a first level; after detecting that the physiological parameter is at the first level and when the user of the computer system performs a second activity different from the first activity, detecting via one or more sensors that the physiological parameter of the user of the computer system is at a second level different from the first level; and displaying via the display generation component and based on the first level and the second level the predictive change of the physiological parameter in the case of a third activity different from the second activity.

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

[0014] Thus, a faster, more efficient method and interface for displaying a user interface including information related to physiological measurements is provided for devices, thereby improving the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may supplement or replace other methods for displaying a user interface including information related to physiological measurements. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

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

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

[0024] FIG. 6A to FIG. 6M Exemplary devices and user interfaces for displaying a user interface including information related to physiological measurements according to some embodiments are illustrated.

[0025] Figure 7 is a flow chart illustrating a method for displaying a user interface including information related to physiological measurements according to some embodiments. DETAILED DESCRIPTION

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

[0027] There is a need for electronic devices to provide efficient methods and interfaces for displaying user interfaces that include information related to physiological measurements. For example, there is a need to display to a user physiological parameters of the user and predictive changes in such parameters. Such techniques can reduce the cognitive burden imposed on a user accessing a user interface that includes information related to physiological measurements, thereby increasing productivity. In addition, such techniques can reduce processor power and battery power that would otherwise be wasted on redundant user input.

[0028] under Figure 1A to Figure 1B , Figure 2 , Figure 3 , FIG. 4A to FIG. 4B and FIG. 5A to FIG. 5B A description of an exemplary device for performing techniques for management event notifications is provided. FIG. 6A to FIG. 6M An exemplary user interface including information related to physiological measurements is illustrated. Figure 7 is a flow chart illustrating a method of displaying a user interface including information related to physiological measurements according to some embodiments. FIG. 6A to FIG. 6M The user interface in is used to illustrate the processes described below, which include Figure 7 process.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0055] Device 100 also includes a power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, power fault detection circuits, power converters or inverters, power status indicators (e.g., light emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power in a portable device.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0075] Telephone module 138;

[0076] Video conferencing module 139;

[0077] Email client module 140;

[0078] Instant messaging (IM) module 141;

[0079] Fitness support module 142;

[0080] A camera module 143 for still images and / or video images;

[0081] Image management module 144;

[0082] Video player module;

[0083] Music player module;

[0084] Browser module 147;

[0085] Calendar module 148;

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

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

[0088] Search module 151;

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

[0090] Note module 153;

[0091] Map module 154; and / or

[0092] Online video module 155.

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

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

[0095] 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, phone module 138 is optionally used to enter a character sequence corresponding to a phone number, access one or more phone numbers in contact module 137, modify an entered phone number, dial a corresponding phone number, conduct a conversation, and disconnect or hang up when the conversation is complete. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0147] Time 404;

[0148] Bluetooth indicator 405;

[0149] Battery status indicator 406;

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

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

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

[0153] o An icon 420 labeled "Browser" of the browser module 147; and

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

[0155] Icons for other apps, such as:

[0156] o Icon 424 labeled "Message" of IM module 141;

[0157] o An icon 426 labeled “Calendar” of the calendar module 148;

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

[0159] o An icon 430 labeled “Camera” of the camera module 143;

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

[0161] ○ Icon 434 labeled “Stock Market” of the Stock Market Widget 149 - 2 ;

[0162] o An icon 436 labeled “Map” of the map module 154;

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

[0164] ○ Icon 440 labeled as “Clock” of the alarm clock widget 149 - 4 ;

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

[0166] o An icon 444 labeled "Notes" of the notes module 153; and

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0182] FIG. 6A to FIG. 6M An exemplary user interface including information related to physiological measurements according to some embodiments is illustrated. The user interfaces in these figures are used to illustrate the processes described below, which include Figure 7 process.

[0183] Fig. 6ADevice 600 is illustrated, which includes a display 602 (e.g., a touch screen display or a non-touch screen display) in a low power state (e.g., a display off state and / or a state using reduced power compared to a non-low power state). Device 600 is a smart phone with one or more features of device 100, 300, and / or 500, and can be used to track the health data of the user. In some embodiments, device 600 includes a sensor for tracking health-related user data (e.g., an accelerometer, a gyroscope, a GPS sensor, a heart rate sensor, and / or a blood oxygen sensor). In some embodiments, device 600 communicates with one or more smart devices (e.g., a smart watch and / or a heart rate monitor) via one or more wireless communication protocols (e.g., Bluetooth, WiFi, and / or ultra-wideband connections), and the one or more smart devices are associated with a user of device 600. In some embodiments, device 600 and one or more smart devices are all associated with the same user account of the same service (e.g., logged in and / or used). In this example, device 600 communicates with an external device 604 that includes a display 606 (e.g., a touch screen display or a non-touch screen display). External device 604 is a smartwatch that has one or more features of device 400 and can be used to collect health data of a user. In some embodiments, external device 604 includes sensors (e.g., accelerometers, gyroscopes, GPS, optical heart sensors, electrical heart sensors, and / or blood oxygen sensors) for measuring and tracking physiological user data.

[0184] like Fig. 6A As shown in , the external device 604 is currently operating a fitness application (e.g., "Fitness") (e.g., the fitness application is an active application on the external device 604). The external device 604 includes a display 606 that displays a running fitness user interface 608 for the active application. The external device 604 starts recording various metrics (e.g., distance and / or time) and health data (e.g., heart rate and / or non-heart rate data) of the user at the beginning of fitness (e.g., outdoor running fitness). In some embodiments, the external device 604 also records (e.g., automatically and / or based on user request) the health information of the user during other types of activities (e.g., hiking, walking, cycling, swimming, playing sports, dancing and / or practicing yoga). In some embodiments, the external device 604 records the health data of the user when the fitness application is not active (e.g., the fitness application is a closed application on the external device 604) and / or without displaying the user interface of the fitness application.

[0185] exist Fig. 6A, the running fitness user interface 608 includes an elapsed time 608a at "00:00.01" and a heart rate 610, a pace 608b, and a distance 608c at "0FT". The external device 604 displays the heart rate 610 and the pace 608b in a pending state (e.g., "--BPM") until sufficient user data is collected via one or more sensors to present the values ​​of the heart rate 610 and the pace 608b, as shown in FIG. Figure 6B shown.

[0186] exist Figure 6B , the external device 604 continues to record the outdoor running fitness in the fitness application, as shown in the running fitness user interface 608 on the display 606. The elapsed time 608a now reads "30:00.00", indicating that 30 minutes have passed since the start of recording the outdoor running fitness. The external device 604 has collected enough user data via one or more sensors, so the pace 608b now reads "8'34" average miles" to indicate that the external device 604 has recorded the user running at an average pace of 8 minutes and 34 seconds per mile. The distance 608c now reads "3.50MI" to indicate that the external device 604 has recorded the user running 3.5 miles via one or more sensors. In some embodiments, the distance is recorded via one or more sensors of the device 600 and sent via one or more wireless communication protocols for display on the display 606 of the external device 604.

[0187] exist Figure 6B In the running fitness user interface 608, the running fitness user interface 608 also includes Fig. 6A The external device 604 has collected enough user data via one or more sensors of the external device 604, so the running heart rate 610a now reads "150 BPM". In some embodiments, the running heart rate 610a is the user's current heart rate detected by the external device 604. In some embodiments, the running heart rate 610a is the user's average heart rate during outdoor running, as detected and calculated by the external device 604 over a 30-minute period. In some embodiments, the running heart rate 610a is collected by external sensors and sent to the external device 604 via one or more wireless communication protocols for display on the display 606. Figure 6B At , the external device 604 detects an input 612 (eg, a swipe input) on the display 606, and in response to detecting the input 612, the external device 604 displays a fitness options user interface 614 on the display 606, such as Figure 6C shown.

[0188] exist Figure 6C, external device 604 displays a fitness options user interface 614 on display 606. Fitness options user interface 614 includes the following: a new fitness enable indication 614a for starting to record a new fitness; a pause enable indication 614b for pausing the recording of the current outdoor running fitness; an end enable indication 614c for ending the recording of the current outdoor running fitness; and a water lock enable indication 614d for disabling detection of inputs on touch screen display 606 of external device 604 (e.g., touch inputs and / or water drops that may be misinterpreted as intentional user input).

[0189] like Figure 6C As shown in , external device 604 detects input 616 (e.g., a tap input or a press and hold input) at a new fitness enable representation 614a. In some embodiments, in response to detecting input 616, external device 604 displays an additional user interface having various enable representations (e.g., an outdoor walking enable representation and an indoor walking enable representation) corresponding to various fitness types that can be selected (e.g., via touch input) to initiate recording of a new fitness. In some embodiments, external device 604 detects input selecting the outdoor walking enable representation, and in response to detecting selection of the outdoor walking enable representation, begins recording various metrics (e.g., distance; time) and health data (e.g., heart rate) of the user at the start of an outdoor walking fitness, such as Fig.6D shown.

[0190] exist Fig.6D , when the external device 604 records an outdoor walking workout in the fitness application, the external device 604 displays a walking workout user interface 618 on the display 606. The walking workout user interface 618 and the various metrics contained therein (e.g., elapsed time 618a, pace 618b, distance 618c, and walking heart rate 610b) are similar in behavior to the outdoor running workout user interface 608 and the various metrics contained therein (e.g., elapsed time 608a, pace 608b, distance 608c, and running heart rate 610a).

[0191] exist Fig.6D, the walking fitness user interface 618 includes an elapsed time 618a showing "01:00.00" to indicate that the external device 604 has recorded 1 minute of outdoor walking fitness. The walking fitness user interface 618 also includes a walking heart rate 610b reading "135 BPM". In some embodiments, the walking heart rate 610b is the current heart rate of the user detected by the external device 604. In some embodiments, the walking heart rate 610b is the average heart rate of the user during outdoor walking, as detected and calculated by the external device 604 over a 1-minute period. In some embodiments, the walking heart rate 610b is collected by an external sensor and sent to the external device 604 via one or more wireless communication protocols for display on the display 606.

[0192] from FIG. 6D to FIG. 6E , 30 seconds have passed, as indicated by the elapsed time 618a showing "01:30.00" on the walking fitness user interface 618, indicating that the external device 604 has recorded the outdoor walking fitness for 1 minute and 30 seconds. Fig.6D and Fig. 6E Distance 618c now reads "370 FT" to indicate that external device 604 has recorded, via one or more sensors, that the user has walked 370 feet. FIG. 6D to FIG. 6E , the walking heart rate 610b of "135 BPM" has been reduced to the walking heart rate 610c of "130 BPM". In some embodiments, the walking heart rate 610c is the current heart rate of the user detected by the external device 604. In some embodiments, the walking heart rate 610c is the average heart rate of the user during outdoor walking, as detected and calculated by the external device 604 within a period of 1 minute and 30 seconds. In some embodiments, the walking heart rate 610c is collected by an external sensor and sent to the external device 604 via one or more wireless communication protocols for display on the display 606.

[0193] In some embodiments, the external device 604 detects a device for navigating to a location similar to Figure 6C The fitness options user interface input 614 (e.g., swipe input and / or similar Figure 6B In some embodiments, external device 604 detects an input (e.g., a tap input and / or a press input) on an end fitness affordance representation similar to end affordance representation 614c to end the recording of the current outdoor walking fitness. After ending the recording of the current fitness, external device 604 displays a fitness summary user interface 620 on display 606, such as Fig. 6FAs shown. In some embodiments, the device 600 and / or the external device 604 automatically detects the start and / or end of fitness based on the movement of the corresponding device, without the need for the user to specify the start and / or end of fitness. In some embodiments, the device 600 and / or the external device 604 automatically determines the fitness type (e.g., outdoor running, indoor running, hiking, outdoor walking, indoor walking and / or yoga) without the need for the user to input the fitness type. In some embodiments, the device 600 and / or the external device 604 automatically records heart rate and / or physical exertion information during the automatically detected fitness.

[0194] exist Fig. 6F , external device 604 displays a fitness summary user interface 620 on display 606. Fitness summary user interface 620 includes selectable outdoor running fitness affordance 620a, selectable outdoor walking fitness affordance 620b, total time 620c (e.g., "35:00.00;", as shown on display 602 of device 600 as the sum of 624a and 626a), active calories 620d (e.g., "400 calories;", as shown on display 602 of device 600 as the sum of 624c and 626c), total calories 620e (e.g., "480 calories;", as shown on display 602 of device 600 as the sum of 624d and 626d), and selectable completion affordance 620f. In some embodiments, external device 604 detects an input (e.g., a tap input or a tap and hold input) at selectable outdoor running workout affordance 620a and, in response, displays a display including metrics recorded during the outdoor running portion of the user's workout (e.g., Figure 6B In some embodiments, external device 604 detects input (e.g., a tap input or a tap and hold input) at selectable outdoor walking workout affordance 620b and, in response, displays metrics recorded during the outdoor walking portion of the user's workout (e.g., Fig.6D 618a-618c and 610b; Fig. 6E 618a-618c and 610c) of the outdoor walking summary user interface.

[0195] In some embodiments, external device 604 detects an input (e.g., a tap input or a tap and hold input) at selectable completion affordance 620f, and in response, stops display of fitness summary user interface 620. In some embodiments, external device 604 detects a set of one or more inputs (e.g., one or more tap inputs; one or more swipe inputs; a combination of a tap input and a swipe input), and in response to detecting the set of one or more inputs, stops display of fitness summary user interface 620 on display 606 and displays heart rate summary user interface 628, such as Figure 6G In some embodiments, external device 604 transmits the recorded fitness data to device 600 for display on display 602 .

[0196] Now go to Fig. 6F 6, the display 602 of the device 600 is no longer in the low power mode (e.g., but is in the high power mode or the standard power mode). The device 600 displays a workout summary user interface 622 on the display 602. The workout summary user interface 622 includes an outdoor running portion 624 corresponding to the outdoor running portion of the user's workout and an outdoor walking portion 626 corresponding to the outdoor walking portion of the user's workout. The outdoor running portion 624 includes a total time 624a (e.g., "30:00.00;", Figure 6B 608a), distance 624b (e.g., "3.50MI;", Figure 6B 608c), active calories 624c (e.g., "380 calories"), total calories 624d (e.g., "445 calories"), average heart rate 624e (e.g., "150 BPM"), average pace 624f (e.g., "8'34" / MI;", Figure 6B 608b) and heart rate graph 624g. Heart rate graph 624g shows heart rate values ​​recorded by one or more sensors on external device 604 during outdoor running fitness. In some embodiments, average heart rate 624e is related to Figure 6B In some embodiments, Figure 6B The heart rate 610a is the current heart rate when the heart rate is detected by one or more sensors on the external device 604, and therefore, Fig. 6F The average heart rate shown in 624e is Figure 6B The heart rate 610a is different.

[0197] In addition, Fig. 6F, the outdoor walking portion 626 includes the total time 626a (e.g., "05:00.00"), the distance 626b (e.g., "0.25Mi"), the active calories 626c (e.g., "20 calories"), the total calories 626d (e.g., "35 calories"), the average heart rate 626e (e.g., "130BPM"), the average pace 626f (e.g., "20'05" / MI;", Figure 6B 618b). In some embodiments, outdoor walking portion 626 includes a heart rate graph corresponding to the outdoor walking portion of the user's workout, similar to heart rate graph 624g of outdoor running portion 624. In some embodiments, device 600 detects an input (e.g., an upward swipe input or a tap input) and, in response, scrolls workout summary user interface 622 upward to display the heart rate graph corresponding to the outdoor walking portion of the workout.

[0198] In some embodiments, the device 600 detects a set of one or more inputs (e.g., one or more tap inputs; one or more swipe inputs; a combination of tap inputs and swipe inputs), and in response to detecting the set of one or more inputs, stops displaying the fitness summary user interface 622 on the display 602 and displays the health summary user interface 630, such as Figure 6G shown.

[0199] exist Figure 6G In some embodiments, the external device 604 displays a heart rate summary user interface 628 on the display 606. The heart rate summary user interface 628 includes various selectable user interface objects (e.g., 628a-628g) for heart rate values. In some embodiments, the external device 604 detects an input (e.g., a tap input) corresponding to a selection of one of the selectable user interface objects (e.g., 628a-628g) and, in response, displays a heart rate summary user interface 628 on the display 606 having a heart rate summary user interface 628. Fig. 6F The heart rate graph 624g is a detailed heart rate user interface.

[0200] In particular, Figure 6G , the heart rate summary user interface 628 includes an outdoor running heart rate indicator 628e (e.g., "150 BPM;", Fig. 6F 624e), which corresponds to Fig. 6A and Figure 6B The average heart rate recorded by one or more sensors of the external device 604 during the outdoor running portion of the workout in question. The heart rate summary user interface 628 also includes an outdoor walking heart rate indicator 628f (e.g., "130 BPM;", Fig. 6F 626e), which corresponds to Fig.6D and Fig. 6EThe average heart rate recorded by one or more sensors of the external device 604 during the outdoor walking portion of the workout in question. The heart rate summary user interface 628 also includes a post-workout heart rate indicator 628g (e.g., "120-80 BPM"), which is based on a decrease in heart rate in the three minutes after the workout is completed (e.g., after the outdoor walk). The heart rate summary user interface 628 also includes a recovery heart rate indicator 628c (e.g., "25 BPM"), which will be related to the recovery heart rate indicator. Figure 6H Discuss in more detail.

[0201] Now go to Figure 6G Device 600 in the embodiment of the present invention displays a health summary user interface 630 on display 602, which is part of a health application (e.g., a "health application") for storing and viewing health-related user data. The health summary user interface 630 includes various selectable user interface objects (e.g., 630a-630f). The activity summary indicator 630a includes metrics such as calories, exercise minutes, and standing hours. In some embodiments, calories and minutes of exercise are included in the information about the activity summary. 6A to 6F The calories consumed during the discussed fitness and the time recorded by the external device 604. The heart rate enable representation 630b is similar to the heart rate enable representation 628a shown on the external device 604. The resting heart rate enable representation 630c is similar to the resting heart rate enable representation 628b shown on the external device 604. The walking heart rate average enable representation 630d is similar to the walking heart rate average enable representation 628c shown on the external device 604. The heart rate recovery enable representation 630e is similar to the recovery heart rate enable representation 628c shown on the external device 604. The health summary user interface 630 also includes a display all enable representation 630f. In some embodiments, the device 600 detects an input corresponding to a selection of the display all enable representation 630f (e.g., a tap input or a tap and hold input), and in response, displays a list user interface with various selectable enable representations corresponding to various health data types on the display 602.

[0202] Figure 6G The health summary user interface 630 in FIG. 1 also includes an optional workout heart rate highlight 632 and an optional post-workout heart rate highlight 634. The workout heart rate highlight 632 provides information corresponding to the heart rate range recorded during the outdoor running portion of the workout, as previously described with respect to FIG. FIG. 6A to FIG. 6BIn some embodiments, device 600 receives an input corresponding to a selection of workout heart rate highlight 632 (e.g., a tap input or a tap and hold input), and in response, displays a heart rate user interface with additional details related to the heart rate measurement. Post-workout heart rate highlight 634 provides information related to completing a recently recorded workout (e.g., about 6A to 6F In some embodiments, device 600 receives input (e.g., a tap input) corresponding to selection of post-workout heart rate highlight 634, and in response, displays a heart rate user interface with additional details related to the heart rate measurement.

[0203] exist Figure 6G , device 600 detects input 636 (e.g., a tap input or a tap and hold input) corresponding to selection of heart rate recovery affordance indication 630e, and in response, displays heart rate recovery user interface 638 on display 602, as shown in FIG. Figure 6H 6. Heart rate recovery user interface 638 includes a graph area 638a. Graph area 638a includes a heart rate recovery graph 640, heart rate recovery data points 640a-640g, a selectable time period indicator 640h arranged as a one-week view (as indicated by the rectangle surrounding the "W"), and a selectable trend indicator 640i. Heart rate recovery graph 640 shows seven heart rate recovery data points 640a-640g for the week of May 2-8, which correspond to the current day (e.g., Sunday, May 8) and the previous six days, respectively. Heart rate recovery data point 640a for the current day (e.g., Sunday) has a reading of 25, corresponding to 6. Figure 6G The heart rate recovery indicator in 630e can represent the "25 BPM" shown on 630e. In some embodiments, the heart rate recovery value (e.g.,

[0204] "25 BPM; ", the value associated with heart rate recovery data points 640a-640g) is a prediction of a decrease in heart rate one minute after cessation of physical activity following maximum physical exertion. In some embodiments, the values ​​associated with heart rate recovery data points 640a-640g are not measured heart rate recovery values ​​(e.g., they are not the difference between the heart rate during physical activity (e.g., at maximum physical exertion) and one minute after cessation of physical activity). As shown by heart rate recovery data points 640a-640g in heart rate recovery graph 640, the heart rate recovery value may change from day to day (e.g., heart rate recovery data points 640a, 640c, 640d, and 640g are 25 BPM, while heart rate recovery data point 640b is 28 BPM, and heart rate recovery data point 640f is 24 BPM). In some embodiments, the heart rate recovery value is predicted based on a set of one or more recorded heart rate values ​​recorded during one or more types of physical activity (e.g., running, walking, hiking, swimming, stretching, resting). In some embodiments, the heart rate recovery value is predicted (and / or displayed) by the device 600. In some embodiments, the heart rate recovery value is predicted (and / or displayed) by the external device 604. In some embodiments, the heart rate recovery value is higher than the actual change in heart rate between the first exercise (e.g., running or first physical activity) and the second exercise (e.g., walking or second physical activity). In some embodiments, the heart rate recovery value is not based on the heart rate detected during the maximum physical exertion (e.g., the heart rate recovery uses the heart rate detected during the non-maximum physical exertion to predict the heart rate recovery). In some embodiments, the heart rate recovery value is lower than the actual change in heart rate between the first exercise (e.g., running) and the second exercise (e.g., walking). Therefore, the displayed heart rate recovery value is based on the predicted value of the first exercise (e.g., running) and the second exercise (e.g., walking and / or exercise that is not resting), rather than the actual measurement of heart rate recovery one minute after the end of physical activity (e.g., the end of maximum physical exertion or the end of non-maximum physical exertion). In some embodiments, the heart rate recovery value is different from the difference between the heart rate measured at the end of the first workout and the heart rate measured one minute after the end of the first workout (e.g., one minute into the second workout). In some embodiments, the heart rate recovery value is not based on the heart rate measured when the user is not exercising. In some embodiments, the user is not required to stop exercising or stop physical activity in order to determine and then display the heart rate recovery value (which predicts the user's actual heart rate recovery if the user stops exercising and / or stops physical activity). Therefore, the user can continue to exercise according to their preferences and be able to view their heart rate recovery value without having to perform a first workout (e.g., at maximum or non-maximal physical exertion) and then stop exercising (e.g., for one minute or three minutes).

[0205] In some embodiments, in response to selection of a different time period within the time period indicator 640h (e.g., "D"; "M"), the device 600 changes the heart rate recovery graph 640 from Figure 6H The one-week view of the heart rate recovery data points shown is updated to a different view of the heart rate recovery data points (e.g., one day's data points if "D" is selected; one month's data points if "M" is selected; six months' data points if "6M" is selected; and one year's data points if "Y" is selected). In some embodiments, selecting a longer time period (e.g., "M;" "6M;" "Y") in the time period indicator 640h causes an average heart rate recovery value to be displayed within the heart rate recovery graph 640. Figure 6H , the selectable trend indicator 640i reads "Not Available". In some embodiments, the device 600 requires more than a minimum number of data points to calculate a trend for the data (e.g., more than one week). In some embodiments, selecting a longer time period (e.g., "M;" "6M;" "Y") in the time period indicator 640h causes the selectable trend indicator 640i to be Figure 6H ” in the heart rate recovery graph 640 is updated to a trend value (e.g., a consistent average heart rate recovery value, an increase or decrease in heart rate recovery value), which trend value can be selected to cause a trend line to be displayed on the heart rate recovery graph 640.

[0206] exist Figure 6H , heart rate recovery user interface 638 also includes a selectable about enable indication 638b, a selectable favorites enable indication 638c, a selectable show all data enable indication 638d, a selectable data source enable indication 638e, and a unit enable indication 638f to indicate the unit of measurement of heart rate (e.g., "BPM"). In some embodiments, device 600 detects input corresponding to selection of about enable indication 638b (e.g., a tap input or a tap and hold input), and in response, displays a user interface with descriptive details related to heart rate recovery on display 602. In some embodiments, device 600 detects input corresponding to selection of favorites enable indication 638c (e.g., a tap input or a tap and hold input), and in response, provides a visual indication of receiving the selection (e.g., by updating the asterisk from filled to unfilled) and displays a user interface with descriptive details related to heart rate recovery on display 602. Figure 6GIn some embodiments, device 600 detects an input (e.g., a tap input or a tap and hold input) corresponding to a selection of data source enable indication 638e, and in response, displays a user interface detailing permission settings for one or more devices (e.g., device 600; external device 604) for recording heart rate data and other applications for accessing the recorded heart rate data. Figure 6H , device 600 detects input 642 (e.g., a tap input or a tap and hold input) corresponding to a selection to display all data affordance 638d, and in response, displays all data user interface 644, as shown. Fig.6I shown.

[0207] exist Fig.6I At , the device 600 displays a recorded data user interface 644 on the display 602. The recorded data user interface 644 includes selectable heart rate recovery items 644a-644j. In some embodiments, the device 600 detects a swipe input on the display 602 and, in response, scrolls the recorded data user interface 644 to show additional selectable heart rate recovery items. The device 600 detects a first input 646a corresponding to a selection of the heart rate recovery item 644a and, in response, displays a details user interface 648a on the display 602, such as Figure 6J Device 600 detects a second input 646b corresponding to selection of heart rate recovery entry 644c and, in response, displays a detailed user interface 648b on display 602, as shown. Figure 6K Device 600 detects a third input 646c corresponding to selection of heart rate recovery entry 644d, and in response, displays a detailed user interface 648c on display 602, as shown. Figure 6L The device 600 detects a fourth input 646d corresponding to the selection of the heart rate recovery entry 644f, and in response, displays a detailed user interface 648d on the display 602, as shown. Figure 6M shown.

[0208] exist Figure 6J , the device 600 responds to Fig.6I The first input 646a in displays a details user interface 648a on the display 602. The details user interface 648a includes a heart rate recovery value 650a, a date 652a, a source 654a, a date added to health 656a, an activity type 658a, a recovery behavior 660a, a medication factor 662a, and a device details section 664a. Figure 6J, the heart rate recovery value 650a is "25BPM". The heart rate recovery value 650a was generated at "10:45 am on May 8, 2022", as indicated in the date 652a. The heart rate data used to determine the heart recovery value 650a was collected using "JANE APPLESEED's watch" (e.g., external device 604), as indicated by source 654a. More details about source 654a are included in the device details section 664a. The heart rate recovery value 650a was added to the health application (e.g., "Health App") at "10:45 am on May 8, 2022", as indicated in the date 656a added to health. In this example, the date 656a added to health is the same as the date 652a. In some embodiments, the date 656a added to health is different from the date 652a, such as when the source device (e.g., external device 604) is not communicating with the device 600 and later regains communication. The physical activity during which heart rate data was collected for determining the heart recovery value 650a is indicated by the activity type 658a (e.g., "outdoor running") and the recovery behavior 660a (e.g., "outdoor walking"). The medication factor 662a indicates that no medications that affect heart rate were used during the collection of the heart rate data used to determine the heart rate recovery value 650a. In some embodiments, additional factors that affect heart rate (e.g., caffeine intake) are included in detail in the user interface 648a.

[0209] exist Figure 6K , the device 600 responds to Fig.6I The second input 646b in the display 602 displays a detailed user interface 648b on the display 602. The detailed user interface 648b includes a heart rate recovery value 650b, a date 652b, a source 654b, a date added to health 656b, an activity type 658b, a recovery behavior 660b, a medication factor 662b, and device details 664b, which are similar to those described above. Figure 6J Detailed description of the user interface 648a of 650a-664a. In particular, the heart rate recovery value 650b is "25 BPM", which is consistent with Figure 6J The physical activity for which heart rate data is collected to determine the heart recovery value 650b is indicated by an activity type 658b (e.g., “outdoor running”) and a recovery behavior 660b (e.g., “outdoor walking”). The activity type 658b and the recovery behavior 660b are respectively Figure 6J The heart rate recovery value 650b is generated at "3:21 PM on May 6, 2022", as shown in the date 652b (which is the same as the Figure 6J Although generated on different days, Figure 6KHeart rate recovery value 650b and Figure 6J The heart rate recovery value 650a is the same, reading "25 BPM". In some embodiments, the same activity type (e.g., 658a; 658b) and the same recovery type (e.g., 660a; 660b) recorded on different days (e.g., 652a; 652b) result in different heart rate recovery values ​​(e.g., 25 BPM and 26 BPM).

[0210] exist Figure 6L In response to Fig.6I In response to the third input 646c in the device 600, the device 600 displays a details user interface 648c on the display 602. The details user interface 648c includes a heart rate recovery value 650c, a date 652c, a source 654c, a date added to health 656c, an activity type 658c, a recovery behavior 660c, a medication factor 662c, and device details 664c, which are similar to those described above with respect to Figure 6J Detailed description of the user interface 648a of 650a-664a. In particular, the heart rate recovery value 650c is "25 BPM", which is consistent with Figure 6J The physical activity for which heart rate data is collected to determine the heart recovery value 650c is indicated by an activity type 658c (e.g., "hiking") and a recovery behavior 660c (e.g., "yoga"). The activity type 658c and the recovery behavior 660c are different from Figure 6J activity type 658a (e.g., "outdoor running") and recovery behavior 660a (e.g., "outdoor walking"). Although different activity types (e.g., 658a; 658c) and recovery behaviors (e.g., 660a; 660c) are used to generate Figure 6L Heart rate recovery value 650c and Figure 6JThe heart rate recovery value 650a is the same as that of 25 BPM. In some embodiments, different activity types (e.g., 658a; 658c) and different recovery types (e.g., 660a; 660c) result in different heart rate recovery values ​​(e.g., 25 BPM and 26 BPM). In some embodiments, the same activity type (e.g., hiking) and different recovery types (e.g., outdoor walking; yoga) result in the same heart rate recovery value (e.g., 25 BPM and 26 BPM). In some embodiments, the same activity type (e.g., hiking) and different recovery types (e.g., outdoor walking; yoga) result in different heart rate recovery values ​​(e.g., 25 BPM and 26 BPM). In some embodiments, different activity types (e.g., outdoor running; hiking) and the same recovery type (e.g., outdoor walking) result in the same heart rate recovery value (e.g., 25 BPM). In some embodiments, different activity types (e.g., outdoor running; hiking) and the same recovery type (e.g., outdoor walking) result in different heart rate recovery values ​​(e.g., 25 BPM and 26 BPM).

[0211] exist Figure 6M , the device 600 responds to Fig.6I The fourth input 646d in the embodiment of the present invention is used to display the detailed user interface 648d on the display 602. The detailed user interface 648d includes the heart rate recovery value 650d, the date 652d, the source 654d, the date added to the health 656d, the activity type 658d, the recovery behavior 660d, the medication factor 662d and the device details 664d, which are similar to those described above. Figure 6J Detailed description of the user interface 648a of 650a-664a. In particular, the heart rate recovery value 650d is "25 BPM", which is consistent with Figure 6J The physical activity for which heart rate data is collected to determine the heart recovery value 650d is indicated by an activity type 658d (e.g., “outdoor running”) and a recovery behavior 660d (e.g., “outdoor walking”). The activity type 658d and the recovery behavior 660d are respectively Figure 6J The heart rate recovery value 650d is generated after taking a medication that affects heart rate, as indicated by the "Salbuterol Inhaler" in the medication factor 662d, which is different from Figure 6J Although different drug factors are used to generate Figure 6M Heart rate recovery value 650d and Figure 6JThe heart rate recovery value 650a is the same, reading "25BPM". In some embodiments, the same activity type (e.g., 658a; 658b) and the same recovery type (e.g., 660a; 660b) recorded with different medication factors (e.g., 662a; 662d) result in different heart rate recovery values ​​(e.g., 25BPM and 26BPM). In some embodiments, different activity types (e.g., outdoor running; hiking) and / or recovery types (e.g., outdoor walking; yoga) with different medication factors (e.g., 662a; 662d) result in the same heart rate recovery value (e.g., 25BPM). In some embodiments, different activity types (e.g., outdoor running; hiking) and / or recovery types (e.g., outdoor walking; yoga) with different medication factors (e.g., 662a; 662d) result in different heart rate recovery values ​​(e.g., 25BPM and 26BPM).

[0212] Figure 7 700 is a flowchart illustrating a method for using a computer system to display a user interface including information related to physiological measurements according to some embodiments. Method 700 is performed at a computer system (e.g., 100, 300, 500, 600, 604) (e.g., a smart phone, a desktop computer, a laptop computer, a tablet computer, or a head-mounted device (e.g., a head-mounted augmented reality and / or extended reality device)), which communicates with a display generation component (e.g., a display controller, a touch-sensitive display system, and / or a head-mounted display system) and one or more sensors (e.g., a heart rate sensor, an optical heart sensor, an electrical heart sensor, a blood flow sensor, an accelerometer, and / or a gyroscope; an integrated sensor; a sensor that communicates with a computer system (e.g., a sensor integrated into a connected external device)). Some operations in method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0213] As described below, method 700 provides an intuitive way to display a user interface including information related to physiological measurements. The method reduces the cognitive burden of a user viewing a user interface including information related to physiological measurements, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling a user to view a user interface including information related to physiological measurements more quickly and efficiently saves power and increases the time between battery charges.

[0214] When a user of a computer system (e.g., 600 and / or 604) (e.g., a user wearing the computer system (such as worn on a wrist or arm) and / or a user holding the computer system) performs a first activity (e.g., FIG. 6A to FIG. 6BIn some embodiments, the computer system (e.g., 600 and / or 604) detects (702) via one or more sensors that a physiological parameter (e.g., as indicated by 610 and / or 610a) (e.g., heart rate or blood pressure) of a user of the computer system is at a first level (e.g., as indicated by 610a) (e.g., heart rate of 165 bpm, 170 bpm, or 175 bpm; or systolic blood pressure of 190, 200, or 210). In some embodiments, the computer system identifies the first activity based on a fitness tracking function (e.g., an activity identification function) and / or based on one or more user inputs identifying an activity (e.g., via selection of a particular fitness type (e.g., jogging, swimming, cycling)).

[0215] After the physiological parameter is detected to be at the first level (e.g., after a predetermined amount of time, such as 1 minute, 2 minutes, or 3 minutes) and when a user of the computer system performs an activity related to the first activity (e.g., FIG. 6A to FIG. 6B "Outdoor running")) a different second activity (e.g. FIG. 6E to FIG. 6F When the user of the computer system is exercising (e.g., “outdoor walking”) (e.g., walking, climbing stairs and / or exercising without stopping), the computer system (e.g., 600 and / or 604) detects (704) via one or more sensors (e.g., 534, 536, 532, a heart rate sensor and / or a blood oxygen sensor) that a physiological parameter (e.g., heart rate or blood pressure) of the user of the computer system is at a second level (e.g., as indicated by 610b and / or 610c) (e.g., a heart rate of 130bpm, 135bpm, or 140bpm; or a systolic blood pressure of 160, 170, or 180), which is different from the first level (e.g., 610a) (e.g., the second level is lower than the first level).

[0216] The computer system (e.g., 600 and / or 604) displays (706) via a display generation component (e.g., 602 and / or 606) and based on the first level (e.g., 610a) and the second level (e.g., 610b and / or 610c), if the second activity (e.g., FIG. 6E to FIG. 6FIn some embodiments, the predicted change in the physiological parameter is based on the duration of time that elapsed between detecting the physiological parameter at the first level and detecting the physiological parameter at the second level. In some embodiments, the predicted change in the physiological parameter predicts the change (e.g., a decrease or increase) between the first measurement (resulting in the first level) and the second measurement (resulting in the second level) if the user performs the third activity instead of the second activity (e.g., stopping the exercise and / or resting). In some embodiments, the computer system determines the predicted change in the physiological parameter before displaying the predicted change in the physiological parameter. Displaying the predicted change in the physiological parameter if the second activity was the third activity provides feedback to the user regarding information about the user (e.g., the level of the physiological parameter) that the computer system has detected, and provides feedback to the user regarding the level of change in the physiological parameter if the user performs the third activity without requiring the user to perform the third activity, thereby providing improved visual feedback to the user.

[0217] In some embodiments, the physiological parameter is heart rate (e.g., as indicated by 610, 610a, 610b, 610c, 624e, 626e, 628a-628e, and / or 630b-630e). In some embodiments, the computer system uses a heart rate sensor to measure the user's heart rate during the first activity and the second activity. In some embodiments, the heart rate sensor is wirelessly connected to the computer system (e.g., the heart rate sensor is worn on the user's wrist, the heart rate sensor is worn on the user's chest). Displaying the predicted change in heart rate if the second activity is the third activity provides feedback to the user about the computer system is sensing the user's heart rate, thereby providing improved visual feedback to the user.

[0218] In some embodiments, the predictive change of the physiological parameter is a predicted heart rate recovery (e.g., 628d, 630e, 640a-640g, 644a-644j, and / or 650a-650d). In some embodiments, heart rate recovery is a decrease in heart rate 1 minute after stopping exercise. In some embodiments, heart rate recovery is a measure of how fast your heart rate drops after strenuous exercise. In some embodiments, heart rate recovery is a reduction in the number of heart beats per minute one minute after stopping fitness. In some embodiments, the predicted heart rate recovery is a definite prediction of the user's heart rate recovery. Displaying the predicted heart rate recovery provides feedback to the user about the user's heart rate that the computer system is sensing, and gives the user an indication of their health without requiring the user to perform a specific activity (e.g., no activity after strenuous activity), thereby providing improved visual feedback to the user.

[0219] In some embodiments, after detecting that the first activity has stopped (e.g., 634) (e.g., has ended or is no longer detected), after a predetermined amount of time (e.g., 30 seconds, 1 minute, or 2 minutes), a physiological parameter (e.g., heart rate or blood pressure) of the user is detected at a second level (e.g., 628f). In some embodiments, the predetermined time period is the same as the time of the predicted change in the physiological parameter (e.g., the second level is measured one minute after the computer system detects the end of the first activity, and the predicted change in the physiological parameter is the predicted change within 1 minute). In some embodiments, detecting that the first activity has stopped includes and or is based on detecting an input for stopping a fitness tracking function associated with the first activity (e.g., stopping the fitness function). After the user ends the first activity, after a predetermined time period, displaying the predicted change in the physiological parameter provides feedback to the user about what the computer system is sensing about the user, thereby providing improved visual feedback to the user.

[0220] In some embodiments, the first activity includes a first exercise (e.g., 658a and / or 658c) (e.g., running and / or non-stop activity or exercise), and the second activity includes a second exercise (e.g., 660a and / or 660c) that is different from the first exercise (e.g., cool down walking and / or non-stop activity or exercise). Even when both the first activity and the second activity include exercise, displaying the predictive change of the physiological parameter provides the user with a standardized measure of the user's health without requiring the user to perform a specific activity (e.g., no activity followed by intense activity), thereby providing improved visual feedback to the user.

[0221] In some embodiments, the third activity does not include exercise (e.g., the user has stopped exercising and / or is sitting or standing). Even if the third activity does not include exercise, displaying the predictive change in the physiological parameter provides the user with a standardized measure of the user's health without requiring the user to perform a specific activity (e.g., intense activity followed by no activity), thereby providing improved visual feedback to the user.

[0222] In some embodiments, after detecting (e.g., the next day or the next week) that a physiological parameter of a user of the computer system is at a first level and a second level (and optionally, after a predictive change in the physiological parameter is displayed): when the user of the computer system performs (e.g., on the following day or week) a first activity (e.g., FIG. 6A to FIG. 6B During an outdoor run (e.g., running, walking, and / or hiking), a computer system (e.g., 600 and / or 604) detects via one or more sensors that a physiological parameter (e.g., heart rate or blood pressure) of a user of the computer system is at a third level (e.g., a heart rate of 165 bpm, 170 bpm, or 175 bpm; or a systolic blood pressure of 190, 200, or 210), which is different from the first level.

[0223] In some embodiments, after detecting that the physiological parameter of the user of the computer system is at the first level and the second level (and optionally, after displaying a predictive change in the physiological parameter) (e.g., the next day or the next week) and after detecting that the physiological parameter is at a third level (e.g., after a predetermined amount of time, such as 1 minute, 2 minutes, or 3 minutes) and when the user of the computer system performs a second activity different from the first activity (e.g., FIG. 6E to FIG. 6F When the user of the computer system is engaged in “outdoor walking” (e.g., walking, climbing stairs and / or exercising without stopping), the computer system (e.g., 600 and / or 604) detects via one or more sensors that a physiological parameter (e.g., heart rate or blood pressure) of the user of the computer system is at a fourth level (e.g., a heart rate of 130 bpm, 135 bpm, or 140 bpm; or a systolic blood pressure of 160, 170, or 180), which is different from the third level (e.g., the fourth level is lower than the second level).

[0224] In some embodiments, after detecting that a physiological parameter of a user of the computer system is at a first level and a second level (e.g., the next day or the next week) (and optionally, after displaying a predicted change in the physiological parameter): the computer system (e.g., 600, 604) displays, via a display generation component (e.g., 602 and / or 606) and based on the third level and the fourth level, a second predicted change in the physiological parameter if the second activity (e.g., walking, climbing stairs, and / or other exercise) is a third activity different from the second activity (e.g., stopping exercise and / or resting) (e.g., different from the actual change in the physiological parameter between detecting the first level and detecting the second level (e.g., the predicted change from the first level)), wherein the second predicted change in the physiological parameter is the same as the predicted change in the physiological parameter (e.g., 650a-650d). In some embodiments, when the user performs the same activity on multiple days, the computer system determines and displays the same predictive change in the physiological parameter even when the difference between the first level and the second level is different from the difference between the third level and the fourth level. Displaying the same predictive change in the physiological parameter after performing the same fitness at different times provides the user with visual feedback on a standardized measure of the user's health without requiring the user to perform a specific activity (e.g., intense activity followed by no activity), thereby providing improved visual feedback to the user.

[0225] In some embodiments, after detecting that a physiological parameter of a user of the computer system is at a first level and a second level (e.g., the next day or the next week) (and optionally, after displaying a predictive change in the physiological parameter): when the user of the computer system performs a fourth activity (e.g., 658c) that is different from the first activity (e.g., running, walking, and / or hiking) (e.g., performed on the following day or week), the computer system (e.g., 600, 604) detects via one or more sensors that a physiological parameter (e.g., heart rate or blood pressure) of the user of the computer system is at a fifth level (e.g., a heart rate of 165 bpm, 170 bpm, or 175 bpm; or a systolic blood pressure of 190, 200, or 210), which is different from the first level.

[0226] In some embodiments, after detecting that the physiological parameter of the user of the computer system is at the first level and the second level (and optionally, after a predictive change in the physiological parameter is displayed) (e.g., the next day or the next week) and after detecting that the physiological parameter is at a fifth level (e.g., after a predetermined amount of time, such as 1 minute, 2 minutes, or 3 minutes) and when the user of the computer system performs a fifth activity (e.g., 660c) that is different from the fourth activity and the second activity (e.g., walking, climbing stairs, and / or exercising without stopping), the computer system (e.g., 600 and / or 604) detects via one or more sensors that the physiological parameter of the user of the computer system (e.g., heart rate or blood pressure) is at a sixth level (e.g., a heart rate of 130 bpm, 135 bpm, or 140 bpm; or a systolic blood pressure of 160, 170, or 180), which is different from the fifth level (e.g., the sixth level is lower than the fifth level).

[0227] In some embodiments, after detecting that a physiological parameter of a user of the computer system is at a first level and a second level (e.g., the next day or the next week) (and optionally, after displaying a predictive change in the physiological parameter): the computer system (e.g., 600 and / or 604) displays, via a display generation component (e.g., 602 and / or 606) and based on the fifth and sixth levels, a third predictive change (e.g., 650c) of the physiological parameter if the fifth activity (e.g., walking, climbing stairs, and / or other exercise) is a third activity different from the fifth activity (e.g., stopping exercise and / or resting) (e.g., different from the actual change in the physiological parameter between detecting the first level and detecting the second level (e.g., the predictive change from the first level)), wherein the third predictive change in the physiological parameter is the same as the predictive change in the physiological parameter. In some embodiments, when the user performs the same activity on multiple days, the computer system determines and displays the same predictive change in the physiological parameter even when the difference between the first and second levels is different from the difference between the third and fourth levels. Displaying the same predictive changes in a physiological parameter after different fitness sessions by the user provides the user with visual feedback regarding a standardized measure of the user's health without requiring the user to perform specific activities (e.g., intense activity followed by no activity), thereby providing improved visual feedback to the user.

[0228] In some embodiments, where the computer system communicates with one or more input devices (e.g., a touch-sensitive surface, a keyboard, and / or a mouse), when a predicted change in a physiological parameter (e.g., 630e) is displayed (e.g., on display 602 and / or 606), the computer system (e.g., 600, 604) receives a set of one or more inputs (e.g., 636) including a selection of the predicted change in the physiological parameter (e.g., 630e) via the one or more input devices (e.g., 602).

[0229] In some embodiments, where the computer system communicates with one or more input devices (e.g., a touch-sensitive surface, a keyboard, and / or a mouse), in response to receiving a selection (e.g., 636) of a predicted change in a physiological parameter (e.g., 630e), the computer system (e.g., 600 and / or 604) displays a graph (e.g., 640) via a display generation component, the graph including indications of a plurality (e.g., 3, 5, or 7) of corresponding predicted changes in the physiological parameter (e.g., 640a-640g). In some embodiments, in the case where the user performs a third activity (e.g., no exercise and / or rest) as a subsequent activity over multiple days, the computer system predicts changes in the physiological parameter and displays a graph including the predicted changes in the physiological parameter for those days. Displaying a graph including indications of a plurality of corresponding predicted changes in the physiological parameter provides visual feedback to the user regarding a standardized measure of the user's health over time, thereby providing improved visual feedback to the user.

[0230] In some embodiments, the predictive change of the physiological parameter if the second activity is the third activity is based on one or more medications that the user is taking (e.g., 662d). In some embodiments, the computer system receives user input indicating the medication the user is taking (e.g., type, amount, frequency, and / or duration), and uses the characteristics of the medication to determine the predictive change (e.g., determining the user's heart rate recovery when the user is not taking the medication). In some embodiments, the computer system considers one or more medications that the user is taking when determining the predictive change of the physiological parameter (e.g., as typed by the user into the computer system or a remote database). In some embodiments, an algorithm is used to determine the predictive change of the physiological parameter, and the algorithm includes information related to one or more medications that the user is taking as input. Providing the user with a predictive change of the physiological parameter based on one or more medications that the user is taking provides the user with visual feedback on a standardized measure of the user's health that takes into account the effects of the medication, thereby providing improved visual feedback to the user.

[0231] In some embodiments, the computer system (e.g., 600 and / or 604) displays an indication (e.g., text and / or graphical indication) of a first activity (e.g., 658a-658d) and a second activity (e.g., 660a-660d) via a display generation component (e.g., 602 and / or 606) and concurrently with the predicted change in the physiological parameter (e.g., 650a-650d). Concurrently displaying the predicted change in the physiological parameter and the indication of the first activity and the second activity provides the user with visual feedback about the activity on which the predicted change in the physiological parameter is based, thereby providing improved visual feedback to the user.

[0232] In some embodiments, the computer system (e.g., 600, 604) displays the predicted change of the physiological parameter without displaying the actual change of the physiological parameter between the first level and the second level (e.g., the difference between the first level and the second level is not displayed concurrently with the predicted change of the physiological parameter). Displaying the predicted change of the physiological parameter without displaying the actual change of the physiological parameter between the first level and the second level reduces visual clutter in the user interface and enables the user to more quickly and easily access the predicted change of the physiological parameter, thereby providing improved visual feedback to the user.

[0233] In some embodiments, the predicted change in the physiological parameter is based on one or more medications (e.g., 662a-662d) that the user is taking. In some embodiments, the computer system (e.g., 600 and / or 604) displays one or more indications of the one or more medications (e.g., 662d) that the user is taking via a display generation component (e.g., 602 and / or 606) and concurrently with the predicted change in the physiological parameter (e.g., 650d). Displaying one or more indications of the one or more medications that the user is taking that have affected the predicted change in the physiological parameter provides visual feedback to the user about what information the computer system is using to determine the predicted change in the physiological parameter, thereby providing improved visual feedback to the user.

[0234] In some embodiments, the predicted change in the physiological parameter (e.g., 630e) is higher than the actual change between the first level and the second level (e.g., based on Fig. 6F Displaying the predicted change in the physiological parameter above the actual change between the first level and the second level enables the computer system to provide visual feedback to the user regarding a standardized measure of the user's health without requiring the user to perform a specific activity (e.g., intense activity followed by no activity), thereby providing improved visual feedback to the user.

[0235] In some embodiments, the computer system (e.g., 600, 604) displays an indication (e.g., a binary indication and / or a quantitative indication) of whether the trend (e.g., 640i) in the plurality of predicted changes in the physiological parameter is positive or negative via a display generation component (e.g., 602 and / or 606) (e.g., and optionally, concurrently with the predicted changes in the physiological parameter). Displaying an indication of whether the trend in the plurality of predicted changes in the physiological parameter is positive or negative provides feedback to the user as to whether their health is increasing or decreasing, thereby providing improved visual feedback to the user.

[0236] For the purpose of explanation, the preceding description is described by reference to specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or limit the invention to the disclosed precise form. According to the above teachings, many modifications and variations are possible. These embodiments are selected and described in order to best explain the principles of these technologies and their practical applications. Others skilled in the art can thus best utilize these technologies and various embodiments with various modifications suitable for the intended specific use.

[0237] Although the disclosure and examples have been fully described with reference to the accompanying drawings, it should be noted that various changes and modifications will become apparent to those skilled in the art. It should be understood that such changes and modifications are considered to be included within the scope of the disclosure and examples defined by the claims.

[0238] As described above, one aspect of the present technology is to collect and use data available from various sources to allow users to view and manage relevant clinical, health-related and / or physiological data. The present disclosure contemplates that, in some instances, these collected data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, social network IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identification or personal information.

[0239] The present disclosure recognizes that the use of such personal information data in the present technology can be used to benefit users. For example, personal information data can be used to display user-specific clinical, health-related, or physiological measurement data. Therefore, the use of such personal information data enables users to view and manage their corresponding data. In addition, the present disclosure also anticipates other uses of personal information data that benefit users. For example, health and fitness data can be used to provide insights into the user's overall health status, or can be used as positive feedback to individuals who use technology to pursue health goals.

[0240] The disclosure anticipates that entities responsible for the collection, analysis, disclosure, transmission, storage or other purposes of such personal information data will comply with sound privacy policies and / or privacy measures. Specifically, such entities should implement and adhere to the use of privacy policies and practices that are recognized as meeting or exceeding the industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be easy for users to access and should be updated as changes in the collection and / or use of data occur. Personal information from users should be collected for legal and reasonable entity purposes and should not be shared or sold outside these legal purposes. In addition, such collection / sharing should be carried out after receiving the informed consent of the user. In addition, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data, and ensure that other entities with access to personal information data comply with their privacy policies and procedures. In addition, such entities can subject themselves to third-party assessments to prove that they comply with widely accepted privacy policies and practices. In addition, policies and practices should be adapted to specific types of personal information data collected and / or accessed, and to applicable laws and standards including considerations of special jurisdictions. For example, in the United States, the collection or acquisition of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); while health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy measures should be advocated for different types of personal data in each country.

[0241] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates hardware elements and / or software elements to prevent or block access to such personal information data. For example, with respect to clinical, health-related or physiological measurement data, the technology of the present invention may be configured to allow users to choose to "opt in" or "opt out" to participate in the collection of personal information data during service registration or at any time thereafter. As another example, a user may choose not to provide clinical, health-related or physiological measurement data for a target content delivery service. In another example, a user may choose to limit the length of time that clinical, health-related or physiological measurement data is retained, or completely prohibit the development of basic emotional conditions. In addition to providing "opt-in" and "opt-out" options, the present disclosure also contemplates providing notifications related to access or use of personal information. For example, a user may be notified that their personal information data will be accessed when downloading an application, and then the user may be reminded again just before the personal information data is accessed by the application.

[0242] In addition, the intention of the present disclosure is that personal information data should be managed and processed in a manner that minimizes the risk of unintentional or unauthorized access or use. Once the data is no longer needed, the risk can be minimized by limiting data collection and data deletion. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. De-identification can be promoted when appropriate by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than at the address level), controlling how the data is stored (e.g., aggregating data between users), and / or other methods.

[0243] Thus, while the present disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may also be implemented without access to such personal information data. That is, various embodiments of the present technology will not fail to function properly due to the lack of all or a portion of such personal information data. For example, clinical, health-related, or physiological measurement data may be displayed to a user by inferring preferences based on non-personal information data or an absolute minimum measure of personal information (such as content requested by a device associated with the user, other non-personal information available to a computer system, or publicly available information).

Claims

1. A method, comprising: At a computer system in communication with a display generating component and one or more sensors: When a user of the computer system performs a first activity, detecting, via the one or more sensors, a physiological parameter of the user of the computer system at a first level; detecting, via the one or more sensors, that the physiological parameter of the user of the computer system is at a second level different from the first level after detecting that the physiological parameter is at the first level and when the user of the computer system performs a second activity different from the first activity; as well as A predicted change in the physiological parameter if the second activity is a third activity different from the second activity is displayed via the display generation component and based on the first level and the second level. The method according to claim 1 , wherein the physiological parameter is heart rate.

3. The method according to any one of claims 1 to 2, wherein the predicted change in the physiological parameter is a predicted heart rate recovery.

4. The method of any one of claims 1 to 3, wherein the physiological parameter of the user is detected at the second level after a predetermined amount of time after detecting that the first activity has ceased.

5. The method of any one of claims 1 to 4, wherein the first activity comprises a first exercise and the second activity comprises a second exercise different from the first exercise. The method according to claim 1 , wherein the third activity does not include exercising.

7. The method according to any one of claims 1 to 6, further comprising: After detecting that the physiological parameter of the user of the computer system is at the first level and the second level: when the user of the computer system performs the first activity, detecting, via the one or more sensors, that the physiological parameter of the user of the computer system is at a third level different from the first level; after detecting that the physiological parameter is at the third level and when the user of the computer system performs the second activity different from the first activity, detecting, via the one or more sensors, that the physiological parameter of the user of the computer system is at a fourth level different from the third level; as well as A second predicted change of the physiological parameter if the second activity is the third activity different from the second activity is displayed, via the display generation component and based on the third level and the fourth level, wherein the second predicted change of the physiological parameter is the same as the predicted change of the physiological parameter.

8. The method according to any one of claims 1 to 7, further comprising: After detecting that the physiological parameter of the user of the computer system is at the first level and the second level: when the user of the computer system performs a fourth activity different from the first activity, detecting, via the one or more sensors, that the physiological parameter of the user of the computer system is at a fifth level different from the first level; after detecting that the physiological parameter is at the fifth level and when the user of the computer system performs a fifth activity different from the fourth activity and the second activity, detecting, via the one or more sensors, that the physiological parameter of the user of the computer system is at a sixth level different from the fifth level; as well as A third predicted change of the physiological parameter if the fifth activity is the third activity different from the fifth activity is displayed via the display generation component and based on the fifth level and the sixth level, wherein the third predicted change of the physiological parameter is the same as the predicted change of the physiological parameter.

9. The method of any one of claims 1 to 8, wherein the computer system is in communication with one or more input devices, the method further comprising: receiving, via the one or more input devices, a set of one or more inputs comprising a selection of the predicted change in the physiological parameter while displaying the predicted change in the physiological parameter; and In response to receiving a selection of the predicted change in the physiological parameter, a graphic including an indication of a plurality of corresponding predicted changes in the physiological parameter is displayed via the display generation component.

10. The method of any one of claims 1 to 9, wherein the predicted change in the physiological parameter if the second activity is the third activity is based on one or more medications being taken by the user.

11. The method according to any one of claims 1 to 10, further comprising: An indication of the first activity and the second activity is displayed via the display generation component and concurrently with the predicted change in the physiological parameter.

12. The method of any one of claims 1 to 11, wherein the computer system displays the predicted change in the physiological parameter without displaying an actual change in the physiological parameter between the first level and the second level.

13. The method of any one of claims 1 to 12, wherein the predicted change in the physiological parameter is based on one or more medications being taken by the user, the method further comprising: One or more indications of the one or more medications being taken by the user are displayed via the display generation component and concurrently with the predicted change in the physiological parameter.

14. The method according to any one of claims 1 to 13, wherein the predicted change in the physiological parameter is higher than the actual change between the first level and the second level.

15. The method according to any one of claims 1 to 14, further comprising: An indication of whether trends in the plurality of predicted changes in the physiological parameter are positive or negative is displayed via the display generation component.

16. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more sensors, the one or more programs comprising instructions for executing the method according to any one of claims 1 to 15.

17. A computer system configured to communicate with a display generation component and one or more sensors, the computer system comprising: one or more processors; and A memory storing one or more programs, wherein the one or more programs are configured to be executed by the one or more processors, and the one or more programs include instructions for executing the method according to any one of claims 1 to 15.

18. A computer system configured to communicate with a display generation component and one or more sensors, the computer system comprising: Device for carrying out the method according to any one of claims 1 to 15.

19. A computer program product, comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more sensors, the one or more programs comprising instructions for executing the method according to any one of claims 1 to 15.

20. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more sensors, the one or more programs comprising instructions for: When a user of the computer system performs a first activity, detecting, via the one or more sensors, a physiological parameter of the user of the computer system at a first level; detecting, via the one or more sensors, that the physiological parameter of the user of the computer system is at a second level different from the first level after detecting that the physiological parameter is at the first level and when the user of the computer system performs a second activity different from the first activity; as well as A predicted change in the physiological parameter if the second activity is a third activity different from the second activity is displayed via the display generation component and based on the first level and the second level.

21. A computer system configured to communicate with a display generation component and one or more sensors, the computer system comprising: one or more processors; and A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising instructions for performing the following operations: When a user of the computer system performs a first activity, detecting, via the one or more sensors, a physiological parameter of the user of the computer system at a first level; detecting, via the one or more sensors, that the physiological parameter of the user of the computer system is at a second level different from the first level after detecting that the physiological parameter is at the first level and when the user of the computer system performs a second activity different from the first activity; as well as A predicted change in the physiological parameter if the second activity is a third activity different from the second activity is displayed via the display generation component and based on the first level and the second level.

22. A computer system configured to communicate with a display generation component and one or more sensors, the computer system comprising: means for detecting, via the one or more sensors, that a physiological parameter of the user of the computer system is at a first level when the user of the computer system performs a first activity; means for detecting, via the one or more sensors, that the physiological parameter of the user of the computer system is at a second level different from the first level after detecting that the physiological parameter is at the first level and when the user of the computer system performs a second activity different from the first activity; and Means for displaying, via the display generation component and based on the first level and the second level, a predicted change in the physiological parameter if the second activity is a third activity different from the second activity.

23. A computer program product, the computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more sensors, the one or more programs comprising instructions for: When a user of the computer system performs a first activity, detecting, via the one or more sensors, a physiological parameter of the user of the computer system at a first level; detecting, via the one or more sensors, that the physiological parameter of the user of the computer system is at a second level different from the first level after detecting that the physiological parameter is at the first level and when the user of the computer system performs a second activity different from the first activity; as well as A predicted change in the physiological parameter if the second activity is a third activity different from the second activity is displayed via the display generation component and based on the first level and the second level.

Images