User interface for health event logging and coaching

Abstract

To provide a faster and more efficient method and an electronic device having an interface for logging a health-related event and for health-related coaching.SOLUTION: A method for health-related coaching using an electronic device includes: logging an event by associating an action with a specific time and a user sentiment; and transmitting data representing event challenge associated with log entry to an external electronic device.SELECTED DRAWING: Figure 10

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 62 / 875,448, entitled "HEALTH EVENT LOGGING AND COACHING USER INTERFACES," filed July 17, 2019, and U.S. Patent Application No. 16 / 851,451, entitled "HEALTH EVENT LOGGING AND COACHING USER INTERFACES," filed April 17, 2020, the contents of which are incorporated by reference herein in their entirety for all purposes. [Technical field]

[0002] The present disclosure relates generally to computer user interfaces, and more specifically to techniques and user interfaces for logging health-related events and for health-related coaching. [Background technology]

[0003] A user performs or refrains from performing a particular action that may affect health (e.g., one or more physiological parameters associated with health), and the electronic device can collect relevant physiological data and log data that may be relevant to understanding the user's health. Summary of the Invention

[0004] However, some techniques for logging health-related events using electronic devices and for health-related coaching are generally cumbersome and inefficient. For example, some existing techniques use complex and time-consuming user interfaces that may involve multiple key presses or keystrokes. Existing techniques take more time than necessary, wasting the user's time and the device's energy. The latter problem is particularly acute in battery-operated devices.

[0005] Thus, the present technology provides electronic devices with faster, more efficient methods and interfaces for logging health-related events and for health-related coaching. Such methods and interfaces, optionally, complement or replace other methods for logging health-related events and for health-related coaching. Such methods and interfaces reduce the cognitive burden on the user and create a more efficient human-machine interface. In the case of battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges. Such methods and interfaces can also assist users and professionals working with users to improve their health by viewing health-related events, and can assist users by modifying behavior to improve their health.

[0006] According to some embodiments, a method is described that is executed on a first electronic device having a display device and one or more input devices, the method including receiving a first set of one or more inputs via a first input device of the one or more input devices, the first input including a first input identifying a first action performed and a second input identifying a first user emotion associated with the first action, and generating a first log entry in response to the first set of one or more inputs, the first log entry including the first action and the first user emotion, the first log entry being associated with a first time point.

[0007] According to some embodiments, a non-transitory computer-readable storage medium is described that stores one or more programs configured to be executed by one or more processors of a first electronic device having a display device and one or more input devices, the one or more programs including instructions for receiving, via a first input device of the one or more input devices, a first set of one or more inputs including a first input identifying a first action performed and a second input identifying a first user emotion associated with the first action, and generating, in response to the first set of one or more inputs, a first log entry including the first action and the first user emotion, the first log entry being associated with a first time point.

[0008] According to some embodiments, a transitory computer-readable storage medium is described that stores one or more programs configured to be executed by one or more processors of a first electronic device having a display device and one or more input devices, the one or more programs including instructions for receiving, via a first input device of the one or more input devices, a first set of one or more inputs including a first input identifying a first action performed and a second input identifying a first user emotion associated with the first action, and generating, in response to the first set of one or more inputs, a first log entry including the first action and the first user emotion, the first log entry being associated with a first time point.

[0009] According to some embodiments, an electronic device is described. The electronic device includes a display device, one or more input devices, 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 include instructions for receiving, via a first input device of the one or more input devices, a first set of one or more inputs including a first input identifying a first action performed and a second input identifying a first user emotion associated with the first action, and generating a first log entry in response to the first set of one or more inputs, the first log entry including the first action and the first user emotion, the first log entry being associated with a first time point.

[0010] According to some embodiments, an electronic device is described that includes a display device, one or more input devices, means for receiving via a first input device of the one or more input devices a first set of one or more inputs including a first input identifying a first action performed and a second input identifying a first user emotion associated with the first action, and means for generating a first log entry in response to the first set of one or more inputs, the first log entry including the first action and the first user emotion, the first log entry being associated with a first time point.

[0011] According to some embodiments, a method is described that is executed on a first electronic device having a display device and one or more input devices, the method including: displaying, via the display device, a first log entry corresponding to a first event associated with a user of a second electronic device; receiving, while displaying the first log entry corresponding to the first event, via a first input device of the one or more input devices, a first set of one or more inputs corresponding to a request to send a first event challenge to a user associated with the second electronic device, the first set of one or more inputs including a first input corresponding to a set of one or more event conditions; and transmitting, in response to the first set of one or more inputs, data representative of the first event challenge to the second electronic device, the data representative of the first event challenge including a prompt to the user of the second electronic device to log a challenge response event based on the set of one or more event conditions.

[0012] According to some embodiments, a non-transitory computer-readable storage medium is described that stores one or more programs configured to be executed by one or more processors of a first electronic device having a display device and one or more input devices, the one or more programs including instructions for: displaying, via the display device, a first log entry corresponding to a first event associated with a user of a second electronic device; receiving, while displaying the first log entry corresponding to the first event, a first set of one or more inputs via a first input device of the one or more input devices corresponding to a request to send a first event challenge to a user associated with the second electronic device, the first set of one or more inputs including a first input corresponding to a set of one or more event conditions; and transmitting, in response to the first set of one or more inputs, data representative of the first event challenge to the second electronic device, the data representative of the first event challenge including a prompt to the user of the second electronic device to log a challenge response event based on the set of one or more event conditions.

[0013] According to some embodiments, a transitory computer-readable storage medium is described that stores one or more programs configured to be executed by one or more processors of a first electronic device having a display device and one or more input devices, the one or more programs including instructions for displaying, via the display device, a first log entry corresponding to a first event associated with a user of a second electronic device, receiving, while displaying the first log entry corresponding to the first event, a first set of one or more inputs via a first input device of the one or more input devices corresponding to a request to send a first event challenge to a user associated with the second electronic device, the first set of one or more inputs including a first input corresponding to a set of one or more event conditions, and transmitting data representative of the first event challenge to the second electronic device in response to the first set of one or more inputs, the data representative of the first event challenge including a prompt to the user of the second electronic device to log a challenge response event based on the set of one or more event conditions.

[0014] According to some embodiments, a first electronic device is described. The first electronic device comprises a display device, one or more input devices, 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 include instructions for displaying, via the display device, a first log entry corresponding to a first event associated with a user of a second electronic device, and while displaying the first log entry corresponding to the first event, receiving, via a first input device of the one or more input devices, a first set of one or more inputs corresponding to a request to send a first event challenge to a user associated with the second electronic device, the first set of one or more inputs including a first input corresponding to a set of one or more event conditions, and transmitting data representative of the first event challenge to the second electronic device in response to the first set of one or more inputs, the data representative of the first event challenge including a prompt to the user of the second electronic device to log a challenge response event based on the set of one or more event conditions.

[0015] According to some embodiments, a first electronic device is described comprising: a display device, one or more input devices, means for displaying, via the display device, a first log entry corresponding to a first event associated with a user of a second electronic device, means for receiving, while displaying the first log entry corresponding to the first event, a first set of one or more inputs via a first input device of the one or more input devices corresponding to a request to send a first event challenge to a user associated with the second electronic device, the first set of one or more inputs including a first input corresponding to a set of one or more event conditions, and means for transmitting, in response to the first set of one or more inputs, data representative of the first event challenge to the second electronic device, the data representative of the first event challenge including a prompt to the user of the second electronic device to log a challenge response event based on the set of one or more event conditions.

[0016] Executable instructions to perform these functions are optionally contained in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions to perform these functions are optionally contained in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.

[0017] Thus, devices are provided that have faster, more efficient methods and interfaces for logging health-related events and for health-related coaching, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may complement or replace other methods for health-related events and for health-related coaching. [Brief description of the drawings]

[0018] For a better understanding of the various described embodiments, reference should be made to the following Detailed Description in conjunction with the following drawings, in which like reference numerals refer to corresponding parts throughout:

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

[0020] [Figure 1B] FIG. 2 is a block diagram illustrating example components for event processing according to some embodiments.

[0021] [Diagram 2] FIG. 1 illustrates a portable multifunction device having a touch screen in accordance with some embodiments.

[0022] [Diagram 3] 1 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface in accordance with some embodiments.

[0023] [Figure 4A] 1 illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.

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

[0025] [Figure 5A] FIG. 1 illustrates a personal electronic device according to some embodiments.

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

[0027] [Figure 6] 1 is a schematic diagram of a set of interconnected users and electronic devices according to some embodiments.

[0028] [Figure 7A] 1 illustrates a device and user interface for logging health-related events according to some embodiments. [Figure 7B] 1 illustrates a device and user interface for logging health-related events according to some embodiments. [Figure 7C] 1 illustrates a device and user interface for logging health-related events according to some embodiments. [Figure 7D] 1 illustrates a device and user interface for logging health-related events according to some embodiments. [Figure 7E] 1 illustrates a device and user interface for logging health-related events according to some embodiments. [Figure 7F] 1 illustrates a device and user interface for logging health-related events according to some embodiments. [Figure 7G] 1 illustrates a device and user interface for logging health-related events according to some embodiments. [Figure 7H] 1 illustrates a device and user interface for logging health-related events according to some embodiments. [Figure 7I] 1 illustrates a device and user interface for logging health-related events according to some embodiments. [Figure 7J] 1 illustrates a device and user interface for logging health-related events according to some embodiments. [Figure 7K] 1 illustrates a device and user interface for logging health-related events according to some embodiments. [Figure 7L] 1 illustrates a device and user interface for logging health-related events according to some embodiments. [Figure 7M] 1 illustrates a device and user interface for logging health-related events according to some embodiments.

[0029] [Figure 8] FIG. 1 is a flow diagram illustrating a method for logging health-related events according to some embodiments.

[0030] [Figure 9A] 1 illustrates a device and user interface for health-related coaching using an electronic device according to some embodiments. [Figure 9B] 1 illustrates a device and user interface for health-related coaching using an electronic device according to some embodiments. [Figure 9C] 1 illustrates a device and user interface for health-related coaching using an electronic device according to some embodiments. [Figure 9D] 1 illustrates a device and user interface for health-related coaching using an electronic device according to some embodiments. [Figure 9E] 1 illustrates a device and user interface for health-related coaching using an electronic device according to some embodiments. [Figure 9F] 1 illustrates a device and user interface for health-related coaching using an electronic device according to some embodiments. [Figure 9G] 1 illustrates a device and user interface for health-related coaching using an electronic device according to some embodiments. [Figure 9H] 1 illustrates a device and user interface for health-related coaching using an electronic device according to some embodiments. [Figure 9I]1 illustrates a device and user interface for health-related coaching using an electronic device according to some embodiments. [Figure 9J] 1 illustrates a device and user interface for health-related coaching using an electronic device according to some embodiments. [Figure 9K] 1 illustrates a device and user interface for health-related coaching using an electronic device according to some embodiments. [Figure 9L] 1 illustrates a device and user interface for health-related coaching using an electronic device according to some embodiments. [Figure 9M] 1 illustrates a device and user interface for health-related coaching using an electronic device according to some embodiments.

[0031] [Figure 10] FIG. 1 is a flow diagram illustrating a method for health-related coaching using an electronic device according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0032] The following description sets forth example methods, parameters, etc., however, it should be recognized that such description is not intended as a limitation on the scope of the present disclosure, but rather is provided as a description of example embodiments.

[0033] There is a need for electronic devices that provide efficient methods and interfaces for logging health-related events and for health-related coaching. Such techniques can reduce the cognitive burden on users logging health-related events and / or providing health-related coaching, thereby increasing productivity. Furthermore, such techniques can reduce processor and battery power that is otherwise wasted on redundant user input.

[0034] 1A-1B, 2, 3, 4A-4B, and 5A-5B below provide a description of an example device for logging health-related events and performing techniques for health-related coaching. FIGS. 7A-7M show example user interfaces for logging health-related events. FIG. 8 is a flow diagram illustrating a method for managing event notifications, according to some embodiments. The user interfaces of FIGS. 7A-7M are used to illustrate processes described below, including the process of FIG. 8. FIGS. 9A-9M show example user interfaces for providing health-related coaching (e.g., via issuing health-related challenges). FIG. 10 is a flow diagram illustrating a method for health-related coaching using an electronic device, according to some embodiments. The user interfaces of FIGS. 9A-9M are used to illustrate processes described below, including the process of FIG. 10.

[0035] In the following description, terms such as "first" and "second" are used to describe various elements, but these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first touch can be called a second touch, and a second touch can be called a first touch, without departing from the scope of various embodiments described. Although a first touch and a second touch are both touches, they are not the same touch.

[0036] The terminology used in the description of the various embodiments described herein is for the purpose of describing particular embodiments only and is not intended to be limiting. In the description of the various embodiments described and in the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. It should also be understood that as used herein, the term "and / or" refers to and includes any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "includes," "including," "comprises," and / or "comprising," as used herein, 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 groups thereof.

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

[0038] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as PDA and / or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Optionally, other portable electronic devices, such as laptops or tablet computers having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad), are also used. It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad). In some embodiments, the electronic device is a computer system that communicates (e.g., via wireless communication over wired communication) with a display generating component. The display generating component is configured to provide a visual output, such as a display via a CRT display, a display via an LED display, or a display via image projection. In some embodiments, the display generating component is integrated with the computer system. In some embodiments, the display generating component is separate from the computer system. As used herein, "displaying" content includes causing content (e.g., video data rendered or decoded by display controller 156) to be displayed by transmitting data (e.g., image data or video data) over a wired or wireless connection to an integrated or external display generation component to visually generate the content.

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

[0040] The device typically supports a variety of applications, such as one or more of drawing applications, presentation applications, word processing applications, website creation applications, disc authoring applications, spreadsheet applications, gaming applications, telephony applications, video conferencing applications, email applications, instant messaging applications, training support applications, photo management applications, digital camera applications, digital video camera applications, web browsing applications, digital music player applications, and / or digital movie player applications.

[0041] The various applications running on the device optionally use at least one common physical user-interface device, such as a touch-sensitive surface. One or more features of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or changed for each application and / or within each application. In this way, the common physical architecture of the device (such as the touch-sensitive surface) optionally supports a variety of applications with user interfaces that are intuitive and transparent to the user.

[0042] Attention is now directed to embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating a portable multifunction device 100 having a touch-sensitive display system 112, according to some embodiments. Touch-sensitive display 112 may be conveniently referred to as a "touch screen" and may also be known or referred to as a "touch-sensitive display system." Device 100 includes memory 102 (optionally including one or more computer-readable storage media), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input / output (I / O) subsystem 106, other input control devices 116, and external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 that detect the intensity of a contact on device 100 (e.g., a touch-sensitive surface, such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 that generate tactile output on device 100 (e.g., generate tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.

[0043] As used herein and in the 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 a proxy for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​including at least four distinct values, and more typically including hundreds (e.g., at least 256) distinct values. The intensity of a contact is optionally determined (or measured) using various techniques and various sensors or combinations of sensors. For example, one or more force sensors under or adjacent to the touch-sensitive surface are optionally used to measure the force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted averaged) to determine an estimated force of the contact. Similarly, a pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and / or change in the contact area detected on the touch-sensitive surface, the capacitance and / or change in the capacitance of the touch-sensitive surface proximate the contact, and / or the resistance and / or change in the capacitance of the touch-sensitive surface proximate the contact, are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measure of the force or pressure of the contact is used directly to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is described in units that correspond to the surrogate measure). In some implementations, the surrogate measure of the contact force or pressure is converted to an estimate of the force or pressure, and the estimate of the force or pressure is used to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of contact as an attribute of user input may enable a user to access additional device functionality (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) that may not otherwise be accessible on devices of reduced size that have limited real estate for displaying affordances.

[0044] As used herein and in the 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, that will be detected by a user with the user's sense of touch. For example, in a situation where a device or a component of a device is in contact with a touch-sensitive surface of a user (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation that corresponds to a perceived change in a physical characteristic of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "down-click" or "up-click" of a physical actuator button. In some cases, a user feels a tactile sensation such as a "down-click" or "up-click" even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's action. As another example, movement of a touch-sensitive surface is optionally interpreted or sensed by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. Such user interpretation of touch depends on the user's personal sensory perception, but there are many sensory perceptions of touch that are common to a majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an "up click," a "down click," "roughness"), unless otherwise noted, the generated tactile output corresponds to a physical displacement of the device, or a component of the device, that produces the described sensory perception for a typical (or average) user.

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

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

[0047] The peripherals interface 118 may be used to couple input and output peripherals of the device to the CPU 120 and memory 102. The one or more processors 120 operate or execute various software programs and / or instruction sets stored in the memory 102 to perform various functions and process data for the device 100. In some embodiments, the peripherals 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.

[0048] The radio frequency (RF) circuitry 108 transmits and receives RF signals, also referred to as electromagnetic signals. The RF circuitry 108 converts electrical signals to electromagnetic signals or electromagnetic signals to electrical signals and communicates with communication networks and other communication devices via electromagnetic signals. The RF circuitry 108 optionally includes well-known circuits for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, etc. The RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet, and / or wireless networks, such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and with other devices, by wireless communication. RF circuitry 108 optionally includes well known circuitry for detecting near field Communication (NFC) fields, such as by short-range radios. Wireless communication optionally includes, but is 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-HSPA), Long Term Evolution (LDO), and other standard cellular technologies.Wireless technology includes, but is not limited to, wireless technology such as wireless LAN, wireless technology such as wireless technology with a cellular network (WAN), wireless technology such as wireless technology with a cellular network (WAN-CDMA), wireless technology such as wireless technology with a cellular network (WAN-SWAN ... The present invention may use any of a number of communications standards, protocols, and technologies, including Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS), and / or Short Message Service (SMS), or any other suitable communications protocol, including communications protocols not yet developed as of the filing date of this application.

[0049] The audio circuit 110, the speaker 111, and the microphone 113 provide an audio interface between a user and the device 100. The audio circuit 110 receives audio data from the peripherals interface 118, converts the audio data into an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal into human audible sound waves. The audio circuit 110 also receives an electrical signal converted from the sound waves by the microphone 113. The audio circuit 110 converts the electrical signal into audio data, and transmits the audio data to the peripherals interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to the memory 102 and / or the RF circuit 108 by the peripherals interface 118. In some embodiments, the audio circuit 110 also includes a headset jack (e.g., 212 in FIG. 2). The headset jack provides an interface between audio circuitry 110 and a detachable audio input / output peripheral such as an output-only headphone or a headset with both an output (e.g., one-ear or binaural headphones) and an input (e.g., a microphone).

[0050] The I / O subsystem 106 couples input / output peripherals on the device 100, such as the touch screen 112 and other input control devices 116, to a peripheral interface 118. The I / O subsystem 106 optionally includes a display controller 156, a light sensor controller 158, a depth camera controller 169, an intensity sensor controller 159, a haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive / send electrical signals from / to the other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, etc. In some alternative embodiments, the input controller(s) 160 are optionally coupled to any (or none) of a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208 in FIG. 2) optionally include up / down buttons for volume control of speaker 111 and / or microphone 113. The one or more buttons optionally include push buttons (e.g., 206 in FIG. 2). In some embodiments, the electronic device is a computer system in communication (e.g., via wireless communication over wired communication) with one or more input devices. In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a trackpad 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 light sensors 164 and / or one or more depth camera sensors 175), such as for tracking a user's gestures (e.g., hand 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.

[0051] A quick press of a push button optionally unlocks the touch screen 112 or optionally initiates a process of unlocking the device using a gesture on the touch screen, as described in U.S. Patent Application Serial No. 11 / 322,549, filed December 23, 2005, "Unlocking a Device by Performing Gestures on an Unlock Image," U.S. Patent No. 7,657,849, which is incorporated herein by reference in its entirety. A longer press of a push button (e.g., 206) optionally turns power on or off to the device 100. The functionality of one or more of the buttons is optionally customizable by the user. The touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

[0052] Touch-sensitive display 112 provides an input and output interface between the device and a user. Display controller 156 receives and / or transmits electrical signals from touchscreen 112. Touchscreen 112 displays visual output to the user. This visual output optionally includes graphics, text, icons, animation, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output optionally corresponds to user interface objects.

[0053] Touchscreen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from a user based on tactile and / or tactile contact. Touchscreen 112 and display controller 156 (along with any associated modules and / or instruction sets in memory 102) detects contacts (and any movement or breaking of contact) on touchscreen 112 and translates the detected contacts into interactions with user interface objects (e.g., one or more soft keys, icons, web pages, or images) displayed on touchscreen 112. In an exemplary embodiment, the point of contact between touchscreen 112 and the user corresponds to the user's finger.

[0054] Touchscreen 112 optionally uses LCD (Liquid Crystal Display), LPD (Light Emitting Polymer Display), or LED (Light Emitting Diode) technology, although other display technologies are used in other embodiments. Touchscreen 112 and display controller 156 optionally detect contact and any movement or interruption thereof using any of a number of now known or later developed touch sensing technologies, including, but not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements that determine one or more points of contact with touchscreen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

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

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

[0057] The touchscreen 112 optionally has a video resolution of greater than 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. A user optionally contacts the touchscreen 112 using any suitable object or appendage, such as a stylus, finger, etc. In some embodiments, the user interface is designed to operate primarily using finger-based contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of ​​a finger on the touchscreen. In some embodiments, the device translates the rough finger input into precise pointer / cursor positions or commands to perform the action desired by the user.

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

[0059] Device 100 also includes a power system 162 that provides power to 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 failure detection circuitry, 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 within a portable device.

[0060] Device 100 also optionally includes one or more light sensors 164. FIG. 1A shows a light sensor coupled to light sensor controller 158 in I / O subsystem 106. Light sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Light sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. Light sensor 164 cooperates with imaging module 143 (also called a camera module) to optionally capture still or video images. In some embodiments, the light sensor is located on the back of device 100 opposite touchscreen display 112 on the front of the device, so that the touchscreen display can be used as a viewfinder for still and / or video capture. In some embodiments, the light sensor is located on the front of the device such that an image of the user is optionally obtained for a video conference while the user views other video conference participants on the touchscreen display. In some embodiments, the position of the light sensor 164 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), such that a single light sensor 164 is used for both video conferencing and still image and / or video capture, in conjunction with a touchscreen display.

[0061] Device 100 also optionally includes one or more depth camera sensors 175. FIG. 1A shows a depth camera sensor coupled to depth camera controller 169 in I / O subsystem 106. Depth camera sensor 175 receives data from the environment to create a three-dimensional model of an object (e.g., a face) in a scene from a viewpoint (e.g., the depth camera sensor). In some embodiments, in cooperation with imaging module 143 (also called camera module), depth camera sensor 175 is optionally used to determine a depth map of different parts of an image captured by imaging module 143. In some embodiments, a depth camera sensor is disposed on the front of device 100 to obtain an image of a user with depth information for a video conference and to capture a selfie image with depth map data while the user views other video conference participants on a touch screen display. In some embodiments, depth camera sensor 175 is disposed on the back of the device, or on the back and front of device 100. In some embodiments, the position of the depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and sensor within the device housing) such that the depth camera sensor 175 is used for both video conferencing and still and / or video capture in conjunction with a touchscreen display.

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

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

[0064] Device 100 also optionally includes one or more tactile output generators 167. FIG. 1A shows a tactile output generator coupled to tactile feedback controller 161 in I / O subsystem 106. Tactile output generator 167 optionally includes one or more electroacoustic devices, such as speakers or other audio components, and / or electromechanical devices that convert energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile output on the device). Contact intensity sensor 165 receives tactile feedback generation commands from tactile feedback module 133 and generates a tactile output on device 100 that can be sensed by a user of device 100. In some embodiments, at least one tactile output generator is juxtaposed with or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112) and generates a tactile output, optionally by moving the touch-sensitive surface vertically (e.g., in / out of the surface of device 100) or horizontally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, the at least one tactile output generator sensor is located on the back of device 100, opposite touchscreen display 112, which is located on the front of device 100.

[0065] Device 100 also optionally includes one or more accelerometers 168. FIG. 1A shows accelerometer 168 coupled to peripherals interface 118. Alternatively, accelerometer 168 is optionally coupled to input controller 160 in I / O subsystem 106. Accelerometer 168 optionally functions as described in U.S. Patent Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated herein by reference in their entireties. In some embodiments, information is displayed on the touchscreen display in portrait or landscape view based on an analysis of data received from the one or more accelerometers. In addition to accelerometer(s) 168, device 100 optionally includes a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information regarding the position and orientation (e.g., vertical or horizontal) of device 100.

[0066] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a touch / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a Global Positioning System (GPS) module (or instruction set) 135, and applications (or instruction sets) 136. Additionally, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) stores device / global internal state 157, as shown in FIGS. 1A and 3. Device / global internal state 157 includes one or more of an active application state indicating which applications, if any, are currently active, a display state indicating which applications, views, or other information are occupying various regions of touchscreen display 112, a sensor state including information obtained from the device's various sensors and input control devices 116, and location information regarding the location and / or orientation of the device.

[0067] 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 that control and manage general system tasks (e.g., memory management, storage control, power management, etc.) and facilitate communication between various hardware and software components.

[0068] The communications module 128 also includes various software components for facilitating communication with other devices via one or more external ports 124 and for processing data received by the RF circuitry 108 and / or the external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) are adapted to couple to other devices directly or indirectly via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external ports are multi-pin (e.g., 30-pin) connectors that are the same as or similar to and / or compatible with the 30-pin connector used on iPod® (a trademark of Apple Inc.) devices.

[0069] Contact / motion module 130, optionally in conjunction with display controller 156, detects contact with touch screen 112 and other touch-sensing devices (e.g., a touchpad or physical click wheel). Contact / motion module 130 includes various software components for performing various operations related to detecting contact, such as determining whether contact has occurred (e.g., detecting a finger-down event), determining the strength of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more events of dragging a finger), and determining whether the contact has stopped (e.g., detecting a finger-up event or an interruption of the contact). Contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact, as represented by the series of contact data, optionally includes determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact. These actions are, optionally, applied to a single contact (e.g., one finger contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some embodiments, contact / motion module 130 and display controller 156 detect contacts on a touchpad.

[0070] 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” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined according to software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of a particular physical actuator, but can be adjusted without modifying the physical hardware of the device 100). For example, the mouse “click” threshold of a trackpad or touchscreen display can be set to any of a wide range of predefined thresholds without modifying the trackpad or touchscreen display hardware. Additionally, in some implementations, a user of the device is provided with a software setting to adjust one or more of the sets of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds at once via a system-level click “intensity” parameter).

[0071] Contact / motion module 130 optionally detects gesture input by a user. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different movements, timing, and / or strength of detected contacts). Thus, gestures are optionally detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger down event, followed by detecting a finger up (lift off) event at the same location (or substantially the same location) as the finger down 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 down event, followed by one or more finger drag events, followed by detecting a finger up (lift off) event.

[0072] Graphics module 132 includes various known software components that render and display graphics on touchscreen 112 or other display, including components that vary the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual characteristics) 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, video, animations, and the like.

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

[0074] The tactile feedback module 133 includes various software components for generating instructions used by the tactile output generator(s) 167 to generate tactile outputs at one or more locations on the device 100 in response to a user's interaction with the device 100.

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

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

[0077] Application 136 optionally includes the following modules (or sets of instructions), or a subset or superset thereof: ● a contacts module 137 (sometimes called an address book or contact list); ● Telephone module 138, ● Videoconferencing module 139; ● an email client module 140; ● Instant messaging (IM) module 141; ● Training support module 142; ● a camera module 143 for still images and / or video; ● Image management module 144; ● Video player module, ● Music player module, ● Browser module 147, ● Calendar module 148, ● a widget module 149, optionally including one or more of a weather widget 149-1, a stocks widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5, and other widgets obtained by the user, as well as a user-created widget 149-6; ● a widget creator module 150 for creating user-created widgets 149-6; ● Search module 151, A video and music player module 152 that combines a video player module and a music player module; ● Memo module 153, Map module 154, and / or ● Online video module 155.

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

[0079] The contacts module 137, in conjunction with the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134, is optionally used to manage an address book or contact list (e.g., stored in the memory 102 or in the application internal state 192 of the contacts module 137 in the memory 370), including adding a name(s) to the address book, deleting a name(s) from the address book, associating phone number(s), email address(es), physical address(es) or other information with a name(s), categorizing and sorting names, providing phone numbers or email addresses to initiate and / or facilitate communication by telephone 138, videoconferencing module 139, email 140, or IM 141, and the like.

[0080] Telephone module 138, 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, is optionally used to enter character sequences corresponding to telephone numbers, access one or more telephone numbers in contacts module 137, modify entered telephone numbers, dial respective telephone numbers, place calls, and disconnect and hang up when a call is completed. As previously mentioned, wireless communication optionally uses any of a number of communication standards, protocols, and technologies.

[0081] Video conferencing module 139 includes executable instructions to cooperate with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, light sensor 164, light sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138 to initiate, conduct, and end a video conference between a user and one or more other participants according to the user's commands.

[0082] The email client module 140, in conjunction with the RF circuitry 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134, contains executable instructions for composing, sending, receiving, and managing emails in response to user commands. In conjunction with the image management module 144, the email client module 140 greatly facilitates the creation and sending of emails with still or video images captured by the camera module 143.

[0083] Instant messaging module 141 includes executable instructions in cooperation with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134 for entering character sequences corresponding to instant messages, modifying previously entered characters, sending respective instant messages (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephony-based instant messaging, or XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, sent and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments as supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0084] The training support module 142 includes executable instructions to cooperate with the RF circuitry 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 to create workouts (e.g., having time, distance, and / or calorie burn goals), communicate with training sensors (sports devices), receive training sensor data, calibrate sensors used to monitor the workouts, select and play music for the workouts, and display, store, and transmit the workout data.

[0085] Camera module 143, in conjunction with touch screen 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact / motion module 130, graphics module 132, and image management module 144, contains executable instructions for capturing and storing still images or video (including video streams) in memory 102, modifying characteristics of the still images or video, or deleting still images or video from memory 102.

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

[0087] Browser module 147, in conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, contains executable instructions for browsing the Internet according to user commands, including retrieving, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0088] The calendar module 148 includes executable instructions for cooperating with the RF circuitry 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, the email client module 140, and the browser module 147 to create, display, modify, and store a calendar and data associated with the calendar (e.g., calendar entries, to-do lists, etc.) according to a user's instructions.

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

[0090] The widget creator module 150, in conjunction with the RF circuitry 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, and the browser module 147, is optionally used by a user to create a widget (e.g., turn a user-specified portion of a web page into a widget).

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

[0092] Video and music player module 152 includes executable instructions that cooperate with touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147 to enable a user to download and play pre-recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, as well as executable instructions for displaying, presenting, or otherwise playing videos (e.g., on touchscreen 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 (a trademark of Apple Inc.).

[0093] The note module 153 includes executable instructions for cooperating with the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134 to create and manage notes, to-do lists, and the like according to user instructions.

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

[0095] Online video module 155, in conjunction with touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, includes instructions that enable a user to access, browse for, receive (e.g., by streaming and / or downloading), play (e.g., on the touchscreen or on an external display connected via external port 124), send emails with links to the particular online videos, and otherwise manage the online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141 is used to send links to the particular online videos, rather than email client module 140. For additional description of online video applications, see U.S. Provisional Patent Application No. 60 / 936,562, entitled "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," filed June 20, 2007, and U.S. Patent Application No. 11 / 968,067, entitled "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," filed December 31, 2007, the contents of which are incorporated by reference in their entireties.

[0096] Each of the above-identified modules and applications corresponds to a set of executable instructions that perform one or more of the functions previously described and methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus, in various embodiments, various subsets of these modules are optionally combined or otherwise reconfigured. For example, a video player module is optionally combined with a music player module into a single module (e.g., video and music player module 152 of FIG. 1A). In some embodiments, memory 102 optionally stores a subset of the above-identified modules and data structures. Additionally, memory 102 optionally stores additional modules and data structures not described above.

[0097] In some embodiments, device 100 is a device in which operation of a predefined set of functions on the device is performed exclusively via a touchscreen and / or touchpad. Using the touchscreen and / or touchpad as the primary input control device for operation of device 100 optionally reduces the number of physical input control devices (push buttons, dials, etc.) on device 100.

[0098] The set of predefined functions performed only through the touchscreen and / or touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 to a main menu, a home menu, or a root menu from any user interface displayed on 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.

[0099] 1B is a block diagram illustrating example components for event processing, according to some embodiments. In some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., within operating system 126) and a respective application 136-1 (e.g., any of applications 137-151, 155, 380-390 discussed above).

[0100] Event sorter 170 receives the event information and determines which application 136-1 to deliver the event information to and application view 191 of application 136-1. Event sorter 170 includes an event monitor 171 and an event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192 that indicates the current application view(s) that are displayed on touch-sensitive display 112 when the application is active or running. In some embodiments, device / global internal state 157 is used by event sorter 170 to determine which application(s) is currently active, and application internal state 192 is used by event sorter 170 to determine which application view 191 the event information is delivered to.

[0101] In some embodiments, application internal state 192 includes additional information such as one or more of resume information to be used when application 136-1 resumes execution, user interface state information indicating or ready to display information being displayed by application 136-1, state cues that allow a user to return to a previous state or view of application 136-1, and redo / undo cues of previous actions taken by the user.

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

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

[0104] In some embodiments, event sorter 170 also includes a hit view determination module 172 and / or an active event recognizer determination module 173.

[0105] Hit view determination module 172 provides software procedures that determine where a sub-event occurred within one or more views when touch-sensitive display 112 displays more than one view. A view consists of the controls and other elements that a user can see on the display.

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

[0107] Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchical manner, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should process the sub-events. In most situations, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in a sub-event sequence that forms an event or potential event). 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 identified as the hit view.

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

[0109] Event dispatcher module 174 dispatches the event information to event recognizers (e.g., event recognizer 180). In embodiments that include active event recognizer determination module 173, event dispatcher module 174 delivers the event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores event information obtained by each event receiver 182 in an event queue.

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

[0111] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each including instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, each application view 191 includes multiple event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit or a higher-level object from which application 136-1 inherits methods and other properties. In some embodiments, each event handler 190 includes one or more of data updaters 176, object updaters 177, GUI updaters 178, and / or event data 179 received from event sorter 170. Event handlers 190 optionally utilize or call data updaters 176, object updaters 177, or GUI updaters 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in each application view 191.

[0112] Each event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of metadata 183 and event delivery instructions 188 (optionally including sub-event delivery instructions).

[0113] Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, e.g., a touch or a movement of a touch. 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 a movement of a touch, the event information also optionally includes the speed and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from portrait to landscape or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device's attitude).

[0114] The event comparator 184 compares the event information to predefined event or sub-event definitions and determines the event or sub-event or determines or updates the state of the event or sub-event based on the comparison. In some embodiments, the event comparator 184 includes an event definition 186. The event definition 186 includes definitions of events (e.g., a sequence of predefined sub-events), such as event 1 (187-1) and event 2 (187-2). In some embodiments, sub-events within an event (187) include, for example, touch start, touch end, touch move, touch cancel, and multiple touches. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap includes, for example, a first touch on a displayed object for a given phase (touch start), a first lift off (touch end) for a given phase, a second touch on a displayed object for a given phase (touch start), and a second lift off (touch end) for a given phase. In another example, a definition of event 2 (187-2) is a drag on a displayed object. A drag includes, for example, a touch (or contact) on a displayed object to a predetermined stage, a movement of the touch across the touch-sensitive display 112, and a lift-off of the touch (end of the touch). In some embodiments, the event also includes information regarding one or more associated event handlers 190.

[0115] In some embodiments, event definition 187 includes a definition of the event for each user interface object. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, when a touch is detected on touch-sensitive display 112 in an application view in which three user interface objects are displayed on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, event comparator 184 uses the results of the hit test to determine which event handler 190 to activate. For example, event comparator 184 selects the event handler associated with the sub-event and object that triggers the hit test.

[0116] In some embodiments, each event 187 definition also includes a delay action that delays delivery of the event information until it is determined whether the sequence of sub-events corresponds to the event type of the event recognizer.

[0117] If the respective event recognizer 180 determines that the sequence of sub-events does not match any of the events in the event definition 186, the respective event recognizer 180 enters an event disabled, event failed, or event finished state and thereafter ignores the next sub-event of the touch-based gesture. In this situation, any other event recognizers that remain active for the hit view continue to track and process sub-events of the ongoing touch gesture.

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

[0119] In some embodiments, each event recognizer 180 activates an event handler 190 associated with an event when one or more particular sub-events of the event are recognized. In some embodiments, each event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is separate from sending (and postponing sending) the sub-events to the respective hit view. In some embodiments, the event recognizer 180 pops a flag associated with the recognized event, and the event handler 190 associated with the flag catches the flag and performs a predefined process.

[0120] In some embodiments, the event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver the event information to an event handler associated with a set of sub-events or to an actively participating view. The event handler associated with the set of sub-events or the actively participating view receives the event information and performs a predetermined process.

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

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

[0123] It should be understood that the foregoing description of event processing of a user's touch on a touch-sensitive display also applies to other forms of user input for operating multifunction device 100 with input devices, not all of which are initiated on a touch screen. For example, mouse movements and mouse button presses, contact movements such as tapping, dragging, scrolling on a touchpad, optionally coordinated with single or multiple presses or holds of a keyboard, pen stylus input, device movement, verbal commands, detected eye movements, biometric input, and / or any combination thereof, are optionally utilized as inputs corresponding to sub-events that define the event to be recognized.

[0124] FIG. 2 illustrates portable multifunction device 100 having touch screen 112, according to some embodiments. The touch screen optionally displays one or more graphics in user interface (UI) 200. In this embodiment, as well as other embodiments described below, a user may select one or more of the graphics by performing a gesture on the graphics, for example, using one or more fingers 202 (not drawn to scale) or one or more styluses 203 (not drawn to scale). In some embodiments, selection of one or more graphics is performed when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, upwards and / or downwards), and / or rolling (right to left, left to right, upwards and / or downwards) of a finger in contact with device 100. In some implementations or situations, accidental contact with a graphic does not select the graphic, for example, a swipe gesture sweeping over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

[0125] Device 100 optionally also includes one or more physical buttons, such as a “home” button or menu button 204. As previously mentioned, menu button 204 is optionally used to navigate to any application 136 within a set of applications executing on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key within a GUI displayed on touch screen 112.

[0126] In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on / off and locking the device, volume control button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and external port 124 for docking / charging. Push button 206 is optionally used to power the device on / off by pressing and holding the button down for a predefined period of time, to lock the device by pressing and releasing the button before the predefined time has elapsed, and / or to unlock the device or initiate an unlocking process. In an alternative embodiment, device 100 also accepts verbal input via microphone 113 to activate or deactivate some functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on touch screen 112 and / or one or more tactile output generators 167 for generating a tactile output to a user of device 100.

[0127] FIG. 3 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface, according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child's learning toy), a gaming system, or a control device (e.g., a home or commercial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 that interconnect these components. Communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects and controls communication between system components. Device 300 includes input / output (I / O) interface 330, including display 340, which is typically a touchscreen display. I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 (e.g., similar to tactile output generator 167 described above with reference to FIG. 1A) for generating tactile output on device 300, and sensors 359 (e.g., light, acceleration, proximity, touch sensing, and / or contact intensity sensors similar to contact intensity sensor(s) 165 described above with reference to FIG. 1A). Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU(s) 310.In some embodiments, memory 370 stores programs, modules, and data structures similar to, or a subset of, programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A). Additionally, 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 drawing module 380, presentation module 382, ​​word processing module 384, website creation module 386, disk authoring module 388, and / or spreadsheet module 390, whereas memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

[0128] Each of the above-identified elements of FIG. 3 is optionally stored in one or more of the memory devices mentioned above. Each of the above-identified modules corresponds to an instruction set that performs the functions described above. The above-identified modules or programs (e.g., instruction sets) need not be implemented as separate software programs, procedures, or modules, and thus in various embodiments, various subsets of these modules are optionally combined or otherwise reconfigured. In some embodiments, memory 370 optionally stores a subset of the above-identified modules and data structures. Additionally, memory 370 optionally stores additional modules and data structures not described above.

[0129] Attention is now optionally directed to embodiments of user interfaces implemented, for example, on portable multifunction device 100.

[0130] 4A shows an exemplary user interface for a menu of applications on portable multifunction device 100, according to some embodiments. 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: ● signal strength indicator(s) 402 for wireless communication(s), such as cellular and Wi-Fi signals; ● Time 404, ● Bluetooth indicator 405, ● a battery status indicator 406; - A tray 408 with icons of frequently used applications, such as: o An icon 416 for the phone module 138, labeled "Phone", optionally including an indicator 414 of the number of missed calls or voicemail messages; o An icon 418 of the email client module 140, labeled "Mail", optionally including an indicator 410 of the number of unread emails; ○ An icon 420 for the Browser module 147, labeled "Browser"; and o An icon 422 for the video and music player module 152, also referred to as the iPod (trademark of Apple Inc.) module 152, labeled "iPod"; and ● Icons of other applications, such as: ○ Icon 424 of IM module 141, labeled "Messages"; ○ Icon 426 of the calendar module 148, labeled "Calendar", ○ Icon 428 of the image management module 144, labeled "Photos"; ○ An icon 430 of the camera module 143, labeled "camera"; ○ Icon 432 of the online video module 155, labeled "Online Video"; ○ Icon 434 of Stocks widget 149-2, labeled "Stock Prices"; ○ Icon 436 of map module 154, labeled "Map"; ○ Icon 438 of weather widget 149-1, labeled "Weather"; ○ Icon 440 of alarm clock widget 149-4, labeled "Clock"; ○ Icon 442 of Training Support Module 142, labeled "Training Support"; ○ An icon 444 of the Notes module 153, labeled "Notes"; and o A settings application or module icon 446 labeled “Settings,” which provides access to settings for the device 100 and its various applications 136 .

[0131] 4A are merely exemplary. For example, icon 422 of video and music player module 152 is labeled "Music" or "Music Player," although other labels are optionally used for the various application icons. In some embodiments, the label for each application icon includes the name of the application that corresponds to the respective application icon. In some embodiments, the label of a particular application icon is different from the name of the application that corresponds to that particular application icon.

[0132] 4B shows an example user interface on a device (e.g., device 300 of FIG. 3) that has a touch-sensitive surface 451 (e.g., tablet or touchpad 355 of FIG. 3) that is separate from display 450 (e.g., touchscreen display 112). Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) that detect the intensity of a contact on touch-sensitive surface 451 and / or one or more tactile output generators 357 that generate a tactile output to a user of device 300.

[0133] Although some of the following examples are given with reference to input on touch screen display 112 (wherein the touch-sensitive surface and display are combined), in some embodiments the device detects input on a touch-sensitive surface that is separate from the display, as shown in FIG. 4B. In some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) that corresponds to a primary axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). According to these embodiments, the device detects contact with touch-sensitive surface 451 (e.g., 460 and 462 in FIG. 4B) at locations that correspond to respective locations on the display (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In this manner, user input (e.g., contacts 460 and 462 and their movement) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B) is used by the device to operate a user interface on the display (e.g., 450 in FIG. 4B) of the multifunction device when the touch-sensitive surface is separate from the display. It is to be understood that similar methods are optionally used for the other user interfaces described herein.

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

[0135] FIG. 5A illustrates an exemplary personal electronic device 500. Device 500 includes a body 502. In some embodiments, device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1A-4B). In some embodiments, device 500 has a touch-sensitive display screen 504, hereafter touch screen 504. Alternatively, or in addition to touch screen 504, device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, touch screen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors that detect the intensity of a contact (e.g., a touch) being applied. The one or more intensity sensors of touch screen 504 (or touch-sensitive surface) can provide output data representative of the intensity of the touch. A user interface of device 500 can respond to touch(s) based on their intensity, meaning that touches of different intensities can invoke different user interface actions on device 500.

[0136] For exemplary techniques for detecting and processing touch intensity, see, for example, related applications International Patent Application No. PCT / US2013 / 040061, filed May 8, 2013, entitled "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application," published as International Publication No. WO / 2013 / 169849, and International Patent Application No. PCT / US2013 / 069483, filed November 11, 2013, published as International Publication No. WO / 2014 / 105276, entitled "Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships," each of which is incorporated herein by reference in its entirety.

[0137] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can allow device 500 to be attached to, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch bands, chains, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow a user to wear device 500.

[0138] FIG. 5B illustrates an exemplary personal electronic device 500. In some embodiments, the device 500 can include some or all of the components described with respect to FIGS. 1A, 1B, and 3. The device 500 has a bus 512 that operably couples an I / O section 514 to one or more computer processors 516 and a memory 518. The I / O section 514 can be connected to a display 504, which can have a touch-sensing component 522 and, optionally, an intensity sensor 524 (e.g., a contact intensity sensor). In addition, the I / O section 514 can be connected to a communication unit 530 that receives application and operating system data using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and / or other wireless communication technologies. The device 500 can include input mechanisms 506 and / or 508. The input mechanism 506 is optionally, for example, a rotatable input device or a depressible and rotatable input device. In some examples, the input mechanism 508 is optionally a button.

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

[0140] 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, for example, cause the computer processors to perform the techniques described below, including process 800 and process 1000 (FIGS. 8 and 10). A computer-readable storage medium may be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some embodiments, the storage medium is a transient computer-readable storage medium. In some embodiments, 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, optical, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, CDs, DVDs, or optical disks based on Blu-ray technology, as well as resident solid-state memory such as flash, solid-state drives, and the like. The personal electronic device 500 is not limited to the components and configuration of FIG. 5B and may include other or additional components in multiple configurations.

[0141] The term "affordance" as used herein optionally refers to a user-interactive graphical user interface object displayed on a display screen of device 100, 300, and / or 500 (FIGS. 1A, 3, and 5A-5B). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) each, optionally, constitute an affordance.

[0142] The term "focus selector" as used herein refers to an input element that indicates the current portion of the user interface with which the user is interacting. In some implementations involving a cursor or other position marker, the cursor acts as the "focus selector," such that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 of FIG. 3 or touch-sensitive surface 451 of FIG. 4B) while the cursor is positioned over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations involving a touchscreen display (e.g., touch-sensitive display system 112 of FIG. 1A or touchscreen 112 of FIG. 4A) that allows direct interaction with user interface elements on the touchscreen display, a detected contact on the touchscreen acts as the "focus selector," such that when an input (e.g., a press input by 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 touchscreen display, the particular user interface element is adjusted according to the detected input. In some implementations, focus is moved from one region of the user interface to another region of the user interface without a corresponding cursor movement or contact movement on the touchscreen display (e.g., by using a tab key or arrow keys to move focus from one button to another), and in these implementations the focus selector moves to follow the movement of focus between various regions of the user interface. Regardless of the specific form the focus selector takes, the focus selector is generally a user interface element (or contact on a touchscreen display) that is controlled by the user to communicate the user's intended interaction with the user interface (e.g., by indicating to the device which element of the user interface the user intends to interact with).For example, positioning of a focus selector (e.g., a cursor, touch, or selection box) over a corresponding button while a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen) indicates that the user intends to activate that corresponding button (and not another user interface element shown on the device's display).

[0143] As used herein and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of that contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples, i.e., a set of intensity samples collected during a predefined time (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) associated with a predefined event (e.g., after detecting a contact, before detecting a lift-off of the contact, before or after detecting the start of movement of the contact, before detecting an end of the contact, before or after detecting an increase in the intensity of the contact, and / or before or after detecting a decrease in the intensity of the contact). The characteristic intensity of a contact is optionally based on one or more of a maximum intensity of the contact, a mean value of the intensity of the contact, an average value of the intensity of the contact, a top 10 percentile value of the intensity of the contact, a half maximum intensity value of the contact, a 90 percent maximum intensity value of the contact, etc. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action is performed by the user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact having a characteristic intensity not exceeding the first threshold results in a first action, a contact having a characteristic intensity above the first intensity threshold but not exceeding the second intensity threshold results in a second action, and a contact having a characteristic intensity above the second threshold results in a third action. In some embodiments, the comparison between the characteristic intensity and the one or more thresholds is not used to determine whether the first action or the second action should be performed, but rather is used to determine whether one or more actions should be performed (e.g., whether to perform the respective action or to forgo performing the respective action).

[0144] In some embodiments, a portion of the gesture is identified for purposes of determining the characteristic intensity. For example, the touch-sensitive surface optionally receives successive swipe contacts that transition from a start position to an end position where the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end position is optionally based on only a portion of the successive swipe contacts (e.g., only the portion of the swipe contact at the end position) rather than the entire swipe contact. In some embodiments, a smoothing algorithm is optionally applied to the intensity of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of an unweighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the swipe contact intensity for purposes of determining the characteristic intensity.

[0145] The intensity of the contact on the touch-sensitive surface is optionally characterized against one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device performs an action normally associated with clicking a physical mouse button or trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device performs an action different from an action normally associated with clicking a physical mouse button or trackpad. In some embodiments, when a contact is detected having a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is not detected), the device moves the focus selector in accordance with the movement of the contact on the touch-sensitive surface without performing an action associated with the light press intensity threshold or the deep press intensity threshold. In general, unless otherwise specified, these intensity thresholds are consistent among various sets of values ​​for a user interface.

[0146] An increase in the characteristic intensity of a contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold may be referred to as inputting a "light press." An increase in the characteristic intensity of a contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold may be referred to as inputting a "deep press." An increase in the characteristic intensity of a contact from an intensity below the contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold may be referred to as detecting a contact on the touch surface. A decrease in the characteristic intensity of a contact from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold may be referred to as detecting a lift-off of the contact from the touch surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.

[0147] In some embodiments described herein, one or more actions are performed in response to detecting a gesture including a respective press input or in response to detecting a respective press input performed by a respective contact (or contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or contacts) above a press input intensity threshold. In some embodiments, the respective actions are performed in response to detecting an increase in intensity of the respective contact above a press input intensity threshold (e.g., a "downstroke" of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above a press input intensity threshold followed by a decrease in intensity of the respective contact below the press input intensity threshold, where the respective actions are performed in response to detecting a subsequent decrease in intensity of the respective contact below the press input threshold (e.g., an "upstroke" of the respective press input).

[0148] In some embodiments, the device employs intensity hysteresis to avoid accidental inputs, sometimes referred to as "jitter," and the device defines or selects a hysteresis intensity threshold that has a predefined relationship to the press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units below the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the press input intensity threshold). Thus, in some embodiments, the press input includes an increase in the intensity of the respective contact above the press input intensity threshold, followed by a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the press input intensity threshold, and a respective action is performed in response to detecting a subsequent decrease in the intensity of the respective contact below the hysteresis intensity threshold (e.g., an "upstroke" of the respective press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in the intensity of the contact from an intensity below the hysteresis intensity threshold to an intensity above the press input intensity threshold, and optionally a subsequent decrease in the intensity of the contact to an intensity below the hysteresis intensity, and a respective action is performed in response to detecting the press input (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact, as the case may be).

[0149] For ease of explanation, descriptions of operations performed in response to a press input associated with a press input intensity threshold, or a gesture including a press input, are optionally triggered in response to detecting any of an increase in the intensity of a contact above the press input intensity threshold, an increase in the intensity of a contact from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, a decrease in the intensity of a contact below the press input intensity threshold, and / or a decrease in the intensity of a contact below a hysteresis intensity threshold corresponding to the press input intensity threshold. Further, in examples where an operation is described as being performed in response to detecting a decrease in the intensity of a contact below a press input intensity threshold, the operation is optionally performed in response to detecting a decrease in the intensity of a contact below a hysteresis intensity threshold corresponding to and lower than the press input intensity threshold.

[0150] As used herein, an "installed application" refers to a software application that has been downloaded onto an electronic device (e.g., devices 100, 300, and / or 500) and is ready to run (e.g., opened) on the device. In some embodiments, a downloaded application becomes an installed application by an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the computer system's operating system.

[0151] As used herein, the terms "open application" or "running application" refer to a software application that has retained state information (e.g., as part of device / global internal state 157 and / or application internal state 192). An open or running application is, optionally, any one of the following types of applications: ● the active application currently displayed on the display screen of the device on which the application is being used; Background applications (or background processes) that are not currently displayed, but for which one or more processes are being processed by one or more processors; and - A suspended or hibernated application that is not running but has state information stored in memory (volatile and non-volatile, respectively) and that can be used to resume execution of the application.

[0152] As used herein, the term "closed application" refers to a software application that does not have retained state information (e.g., state information for a closed application is not stored in the device's memory). Thus, closing an application includes stopping and / or removing the application process for the application and removing state information for the application from the device's memory. Generally, opening a second application during a first application does not close the first application. When the second application is displayed and the first application is terminated from display, the first application becomes a background application. Attention is now directed to embodiments of user interfaces ("UI") and related processes implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.

[0153] Figure 6 illustrates an exemplary set of interconnected users and devices. Figures 7A-7M illustrate exemplary systems and user interfaces for logging health-related events according to some embodiments. The user interfaces in these figures are used to explain processes described below, including the process of Figure 8.

[0154] 6 is a schematic diagram of a set 600 of interconnected users (e.g., participants and coaches) and electronic devices. Set 600 includes participant 1, participant 2, and participant N, where N represents any number of additional participants. Participants 1-N are connected to a coach 604 via the Internet 602. In some embodiments, each participant is connected to a coach different from coach 604. In some embodiments, one or more participants are connected to additional coaches in addition to coach 604.

[0155] 6, participant 1 is a user of device 606-1 (e.g., a smartphone), device 608-1 (e.g., a smart watch), and device 610-1 (e.g., a continuous glucose monitor). Participant 2 is a user of device 606-2 (e.g., a smartphone), device 608-2 (e.g., a smart watch), and device 610-2 (e.g., a continuous glucose monitor). Participant N is a user of device 606-3 (e.g., a smartphone), device 608-3 (e.g., a smart watch), and device 610-3 (e.g., a continuous glucose monitor).

[0156] Participant 1's device 606-1 is in communication with devices 608-1 and 610-1. In some embodiments, devices 608-1 and 610-1 are also in direct communication. Similarly, participant 2's and participant N's devices are in communication, respectively.

[0157] Coach 604 is a user of a device 612 (e.g., a tablet computer) configured to receive data from and transmit data to one or more devices of participants 1-N via the Internet 602. In some embodiments, the coach can work with one or more participants over a series of sessions (e.g., a set of days (e.g., 10 days)) to monitor health-related events and data, such as diet and blood glucose data, to assist one or more participants in better understanding the participant's physiological responses to health-related events and potentially assist one or more participants in modifying the participant's behavior to improve the participant's health. For example, the coach can work with a pre-diabetic participant in a first session to initially understand the impact of various events that the participant will log on their blood glucose. The coach can then work with the pre-diabetic participant in subsequent sessions to modify the participant's behavior through the use of issued event challenges to positively impact blood glucose levels and / or general health.

[0158] 7A-7M show devices and user interfaces for logging health-related events.

[0159] 7A illustrates a device 700 that is a smartphone. In some embodiments, device 700 is or includes one or more features of devices 100, 300, 500, and / or 606-1. Device 700 includes a touch-sensitive display 702 that functions as both a display and an input device. Device 700 also includes one or more wireless communication antennas for communicating with external electronic devices, such as devices 608-1, 610-1, and 612 of FIG. 6.

[0160] In FIG. 7A, device 700 displays a daily blood glucose interface 704 including a graph 704-1 showing a user's blood glucose data for a current day (e.g., May 10). In some embodiments, blood glucose data is transmitted to device 700 from device 610-1, and a continuous blood glucose monitor sensor is operably connected to the user of device 700. As shown, graph 704-1 has an x-axis of time (e.g., time of day) and a y-axis of blood glucose value (e.g., units of mg / dL or mmol / L). Interface 704 also includes affordances 704-2, 704-3, and 704-4 for navigating to other days. Interface 704 further includes an area 704-5 that displays the user's current (e.g., most recent) blood glucose reading (e.g., most recent data received from device 610-1) and an indication that the displayed day, May 10, is the current date.

[0161] The interface 704 also includes a logged events region 704-6 that displays affordance(s) corresponding to any logged events for the currently displayed date. As shown in FIG. 7A, the region 704-6 includes an affordance 704-6A that corresponds to a logged food event, as indicated by a fork and knife graphic icon. The affordance 704-6A also includes an indication of the action associated with the logged food event ("Consume coffee with almond milk") and the time the event was logged (6:35 AM), indicating when the action occurred. In some embodiments, physiological data other than blood glucose is tracked in addition to or instead of blood glucose. Other physiological data may include, for example, cholesterol, weight, temperature, viral load, and blood pressure.

[0162] Interface 704 further includes a navigation region 704-7 that includes affordances 704-7A, 704-7B, and 704-7C for navigating to various views, as discussed in more detail below. Affordance 704-7A of user interface 704, which corresponds to the daily view, is currently visually highlighted to indicate that the daily view is currently active.

[0163] In Figure 7A, device 700 detects input 706 (e.g., a touch) on add event affordance 704-8. In response to detecting the input, device 700 displays user interface 708 of Figure 7B.

[0164] 7B, device 700 displays event type interface 708 as an overlay on interface 704, with the remainder of the display not visually highlighted (e.g., grayed out) while interface 708 is displayed. Interface 708 includes multiple affordances 708-1 through 708-4 for selecting the type of event to log. For example, affordance 708-1 can be selected to log a food / drink related event. 708-4 can be selected to log a new event based on a previously favorited event.

[0165] In Figure 7B, device 700 detects an input 710 on affordance 708-2 that corresponds to a past activity event. In response to detecting the input, device 700 displays user interface 712 of Figure 7C.

[0166] In FIG. 7C, the device 700 displays a new past activity user interface 712 for logging a new past event after detecting the input 710 and after receiving further input from the user. The interface 712 includes an activity / action input area 712-1 (in which the text "run 5 miles" has already been entered via additional input) and a date / time area 712-2 (in which "May 10, 2019 8:00" has already been entered via additional input). The interface 712 also includes an emotion selection area 712-3 for selecting an emotion associated with the past event. The area 712-3 includes affordances 712-A1-712-A3 for indicating emotions associated with the logged event and action. In some embodiments, the emotions are mutually exclusive and only one may be selected. In some embodiments, multiple emotions may be selected. As shown in FIG. 7C, the emotion "tired" has been selected via previous input. In some embodiments, the emotions are used by the participant and / or coach in subsequent reviews to understand whether subsequent changes in behavior affect the emotions given to subsequent occurrences of the associated event.

[0167] In Figure 7C, device 700 detects input 714 (e.g., a touch) on save affordance 716. In response to detecting the input, device 700 re-displays user interface 704, as seen in Figure 7D.

[0168] 7D, device 700 displays interface 704 with the newly logged event displayed as affordance 704-6B in region 704-6. Affordance 704-6B includes an indication of an action associated with the event ("run 5 miles") and a time associated with the event ("8:00 AM"). In some embodiments, the affordance can also include an indication of an emotion associated with the event (e.g., "tired").

[0169] In Figure 7D, device 700 detects an input 718 (e.g., a touch) on affordance 704-6A that corresponds to a previously logged food / drink event. In response to detecting the input, device 700 displays user interface 720, as seen in Figure 7E.

[0170] In FIG. 7E, the electronic device 700 displays an event details interface 720. The interface 720 includes a graph 720-1 showing the user's blood glucose data throughout the day associated with the logged event. Because the event is associated with the current day, the blood glucose data is the same as that shown in graph 704-1 of interface 704 (FIG. 7A). The graph 720-1 also includes an indication 720-2 indicating the time associated with the event. As can be seen in FIG. 7E, the user's blood glucose level rose immediately after the event (e.g., immediately after consuming coffee with almond milk). The interface 720 also includes an event details area 720-3 that includes further details of the event. For example, the area 720-3 includes an icon 720-3A indicating that the user provided input indicating a feeling (e.g., a prediction) that the event will cause the user's blood glucose to rise slightly, as discussed in more detail below. The area 720-3 also includes an icon 720-3B indicating that the event has been favorited. Region 720-3 also includes an indication 720-3C of whether a photo was associated with the event (eg, a photo of food or drink that was consumed).

[0171] In Figure 7E, device 700 detects an input 722 (e.g., a touch) on an edit affordance 724 that corresponds to a request to edit the event shown in Figure 7E. In response to detecting the input, device 700 displays a user interface 726, as seen in Figure 7F.

[0172] In FIG. 7F, the device 700 displays an event editing interface 726 for editing the event after detecting the input 722 and after receiving further input from the user. As seen in FIG. 7F, the device 700 detects further input to change the action to “coffee with almond milk and sugar” as shown in 726-1, as the user now remembers that the coffee contained additional sugar. The interface 726 also includes an area 726-2 for indicating that the event is a response to an event challenge being issued, as discussed in more detail below. The interface 726 further includes an area 726-3 for indicating an emotion (e.g., an expected physiological response) associated with the event. The area 726-3 includes an affordance 726-3A for indicating that the expected response is “a lot” (e.g., blood glucose will be a lot) in response to the event (e.g., in response to the consumption of a food / drink) and an affordance 726-3B for indicating that the expected response is “a little” (e.g., blood glucose will increase only a little).

[0173] In Figure 7F, device 700 detects an input 728 (e.g., a touch) on affordance 726-3A corresponding to "go up big time." In response to detecting the input, device 700 displays user interface 726, as shown in Figure 7G.

[0174] In FIG. 7G, the device 700 displays an interface 726 with a check mark in affordance 726-3A to indicate that the event is currently associated with a user emotion of a large rise in blood glucose in response to a food / drink event.

[0175] In Figure 7G, device 700 detects input 730 (e.g., a touch) on save affordance 732. In response to detecting the input, device 700 updates its record for the event and redisplays interface 704, as shown in Figure 7H.

[0176] In FIG. 7H, the device 700 displays a user interface 704 based on the edits made in FIG. 7G, now with affordance 704-6A indicating the event as "Coffee with almond milk and sugar."

[0177] In Figure 7H, the device 700 detects an input 734 (e.g., a touch) on the affordance 704-7B to navigate to a challenge view. In response to detecting the input, the device 700 displays the challenge user interface 736 of Figure 7I.

[0178] In FIG. 7I, the electronic device 700 displays a challenge user interface 736. The interface 736 displays active challenges, if any, received by the device 700. Creating a challenge is discussed in more detail below with reference to FIGS. 9A-9M and 10. The interface 736 includes an area 736-1 for displaying an active food challenge, if any, and an area 736-2 for displaying an active habitual challenge, if any. As seen in FIG. 7I, two food challenges are currently active, corresponding to affordances 736-1A and 736-1B. The affordance 746-1A, corresponding to the first food challenge, includes an indication of the action to be taken in response to the challenge ("Replace protein bar with fruits and nuts") and the original food / drink event for which the challenge was created ("Protein bar after run"). In response to the food challenge, the user may log a responsive event (e.g., a food / drink consumption event) in a manner similar to that discussed with respect to Figures 7D-7G, including indicating the particular time of day of the responsive event. For example, a user of device 700 may choose to substitute fruits and nuts for a protein bar that the user may normally consume as part of their routine, and then log a food event responsive to the challenge.

[0179] As seen in Figure 7I, one habitual challenge corresponding to affordance 736-2A is currently active. The device 700 detects an input 738 (e.g., a touch) on the affordance 736-2A that corresponds to the active habitual challenge. In response to detecting the input, the device 700 displays a habitual challenge response interface 740, as seen in Figure 7J.

[0180] In FIG. 7J, device 700 displays an interface 740 for marking one or more days for which the user determines that a habitual challenge has been successfully met. In some embodiments, the habitual challenge may specify one or more actions to be performed throughout the day to meet the challenge (e.g., "eat a protein bar immediately after exercise"). In some embodiments, the habitual challenge may specify one or more actions to be avoided to meet the challenge (e.g., "don't drink sugary sodas"). Interface 740 includes multiple affordances 740-1, including affordance 740-1A corresponding to May 11, 2019.

[0181] In Figure 7J, device 700 detects input 742 (e.g., a touch) on affordance 740-1 A. In response to detecting the input, device 700 modifies interface 740, as shown in Figure 7K.

[0182] 7K, device 700 displays interface 740 with affordance 740-1A checked to indicate that the habitual challenge has been satisfied for that day. In some embodiments, the user can select multiple affordances 740-1 to indicate multiple days that the habitual challenge has been satisfied. In some embodiments, because habitual challenges may only be satisfied on a daily basis, the response to the habitual challenge indicates only a day and not a particular time period.

[0183] 7K, device 700 detects input 744 (e.g., a touch) on save affordance 746. In response to detecting the input, device 700 modifies and saves the user's selection of the date(s) on which the habitual challenge was satisfied.

[0184] 7L shows device 750 that is a smartwatch. In some embodiments, device 60 is or includes one or more features of devices 100, 300, 500, and / or 608-1. Device 750 includes a touch-sensitive display 752 that functions as both a display and an input device. Device 750 also includes one or more wireless communication antennas for communicating with external electronic devices, such as devices 606-1, 610-1, and 612 of FIG. 6.

[0185] In FIG. 7L, device 750 displays a user interface 754 for logging a food / drink event at a particular time. Data of such logged event may then be sent to an external device (e.g., device 700) where additional details may be entered (e.g., via the editing methods shown in FIGS. 7D-7G). In some embodiments, device 750 may be easier or more accessible to a user than device 700, and since it is important to accurately record the time when a food / drink event occurred, device 750 may be used to facilitate more accurate logging of food / drink events. In FIG. 7M, device 750 displays an indication that the event was successfully logged.

[0186] 8 is a flow diagram illustrating a method for logging health-related events using an electronic device, according to some embodiments. Method 800 is performed on a first electronic device (e.g., 100, 300, 500, 606-1, 700) (e.g., personal computer, laptop computer, smartphone, tablet computer) having a display device (e.g., 702) (e.g., an integrated touch-sensitive display) and one or more input devices (e.g., 702) (e.g., a mouse, a touchpad, a touch-sensitive display). Some operations of method 800 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0187] As described below, the method 800 provides an intuitive way to log health-related events. The method reduces the cognitive burden on the user when logging health-related events, thereby creating a more efficient human-machine interface. For battery-operated computing devices, allowing users to log health-related events more quickly and efficiently conserves power and extends the time between battery charges.

[0188] A first electronic device (e.g., 700) receives (802) a first set of one or more inputs via a first input device (e.g., 702) of the one or more input devices. The first set of one or more inputs includes a first input (e.g., an input entering text at 712-1 or 726-1) that identifies a first action (e.g., consuming a food or beverage, performing an exercise) that has been performed (e.g., performed by a user of the first electronic device) and a second input (e.g., an input selecting 712-3B, input 728) that identifies a first user emotion associated with the first action (e.g., the user's current physical well-being (e.g., if the first action is performing an exercise) or a prediction of a future outcome (e.g., a prediction of a future effect of the first action on a physiological parameter (e.g., blood glucose or heart rate) of the first action (e.g., if the first action is consuming a food or beverage)).

[0189] The first electronic device generates (804) a first log entry (e.g., event 704-6A or 704-6B) including a first action and a first user emotion in response to the first set of one or more inputs, the first log entry being associated with a first time point (e.g., the time the first set of one or more inputs was received). Generating a log entry including the entered action and emotion provides the user with an improved input method for creating a log entry with desired information that improves usability of the first electronic device. Improving the usability of the device makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the device), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

[0190] In some embodiments, the first log entry includes an indication (e.g., icon 704-6A) that the first log entry is associated with consumption of a food or beverage, and the first user emotion (e.g., 726-3A or 726-3B) includes a prediction of an impact of the food or beverage consumption on a first physiological parameter (e.g., blood glucose, heart rate, cholesterol) of the user of the first electronic device (e.g., a prediction that the effect, will increase the physiological parameter by a first amount or a second amount). By generating a log entry associated with the consumption of the food or beverage and the user prediction of the impact of the consumption, stored feedback regarding the emotion of the predicted impact of the consumption event is provided to the user for later reference and review. Providing improved feedback improves device usability and makes the user-device interface more efficient (e.g., by helping the user make appropriate inputs and reducing user errors when operating / interacting with the device), which further allows the user to use the device more quickly and efficiently, thereby reducing power usage and improving the battery life of the device.

[0191] In some embodiments, the first set of one or more inputs includes a third input (e.g., 704-8), and the first electronic device displays (806) via the display device a first affordance (e.g., 708-1) corresponding to a first type of log entry (e.g., a log entry corresponding to consuming a food or beverage) and a second affordance (e.g., 708-2) corresponding to a second type of log entry different from the first type (e.g., performing a past activity (e.g., performing an exercise)). In response to a determination that the third input corresponds to a selection of the first affordance, the first log entry includes an indication that the first log entry is of the first type. In response to a determination that the third input corresponds to the first affordance, the first log entry includes an indication that the first log entry is of the second type. By including in the log entry an indication of whether the log entry is a first type or a second type based on user input, the number of inputs required to specify the characteristics of the log entry is reduced. By reducing the number of inputs required to perform this operation, the usability of the first electronic device is increased. Improving the usability of the device makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the device) as well as reducing power usage and improving the battery life of the device by allowing the user to use the device more quickly and efficiently.

[0192] In some embodiments, after generating the first log entry, the first electronic device displays (808) via a display device a first user interface (e.g., 704) including a representation (e.g., 704-1) of a first time period (e.g., 24 hours, January 1) that includes the first time point (e.g., a graph having time as a first axis and a value of the physiological parameter as a second axis), a representation of the first log entry (e.g., 705-6A), and a representation of a second log entry (e.g., 704-6B) associated with a second time point within the first time period that is different from the first time point.

[0193] In some embodiments, the first user interface includes a representation (e.g., a line graph) of a value of a second physiological parameter (e.g., blood glucose, heart rate, cholesterol) of a user of the first electronic device over a first period of time.

[0194] In some embodiments, values ​​of the second physiological parameter over the first period are received from a second electronic device (e.g., 610-1 or 608-1) (e.g., an external electronic device that is a heart rate monitor, a continuous blood glucose monitor).

[0195] In some embodiments, the first user interface includes a representation (e.g., 704-5) of a current value (e.g., current value, real-time value) of a third physiological parameter (e.g., blood glucose, heart rate, cholesterol) of a user of the first electronic device.

[0196] In some embodiments, the first user interface is generated at a third electronic device (e.g., 750) (e.g., a personal computer, a laptop computer, a smartphone, a tablet computer) and includes a representation of a third log entry (e.g., a log entry entered using interface 754) that was sent to the first electronic device. In some embodiments, the third log entry can be edited (e.g., via a set of one or more inputs received at the first electronic device) to add additional details corresponding to the log entry.

[0197] In some embodiments, the first set of one or more inputs is generated at a fourth electronic device (e.g., 612 or 900) (e.g., a personal computer, a laptop computer, a smartphone, a tablet computer) and includes a fourth input (e.g., 738) corresponding to a first event challenge (e.g., 736-2A) (e.g., a set of one or more actions to be taken or not taken (e.g., forgo)) sent to the first electronic device, and the first long entry includes an indication of the first event challenge. Generating a log entry including an indication of the associated event challenge received from the fourth electronic device memorializes a relationship between the action taken by the user and the received event challenge, thereby providing improved feedback. Providing improved feedback improves usability of the device and provides a more efficient user-device interface (e.g., by helping the user make appropriate inputs and reducing user errors when operating / interacting with the device), which further reduces power usage and improves the battery life of the device by allowing the user to use the device more quickly and efficiently.

[0198] In some embodiments, the first electronic device displays (710) via a display device a second user interface (e.g., 736) that includes a representation (e.g., 736-1A) (e.g., an affordance) (e.g., a set of one or more actions to be performed or not performed (e.g., forgo)) of a second event challenge generated at the fourth electronic device and sent to the first electronic device, and a representation (e.g., an affordance) of a third event challenge generated at the fourth electronic device and different from the second event challenge sent to the first electronic device.

[0199] In some embodiments, the second event challenge (e.g., 736-1A) is a first type of event challenge (e.g., a food / beverage consumption challenge) and the third event challenge (e.g., 736-2A) is a second type of event challenge different from the first type (e.g., a habitual challenge). The first electronic device receives a second set of one or more inputs (e.g., a set of inputs including input 738) while displaying the second user interface (e.g., 736). The first electronic device displays a third user interface (e.g., 726) configured to generate an event challenge response associated with a third point in time (a particular point in time within a day / date (e.g., January 1 at 12:00 PM)) in accordance with a determination that the second set of one or more inputs includes a selection of a representation of the second event challenge. The first electronic device displays a fourth user interface (e.g., 740) configured to generate an event challenge response associated with a first date (e.g., January 1 (e.g., but not associated with a specific point in time of the date)) in accordance with a determination that the second set of one or more inputs includes a selection of a representation of the third event challenge. Displaying different challenge response interfaces based on the type of event challenge reduces the number of inputs required for a user to store data associated with a particular challenge event type. Reducing the number of inputs required to perform this operation improves usability of the first electronic device. Improving the usability of the device makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the device), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

[0200] In some embodiments, after the first electronic device generates the first log entry, it transmits the first log entry to a fifth electronic device (e.g., 612 or 900) (e.g., a personal computer, a laptop computer, a smartphone, a tablet computer) (e.g., an electronic device that receives the log entry generated by the first electronic device and transmits one or more event challenges to the first electronic device).

[0201] It should be noted that the process details described above in connection with method 800 (e.g., FIG. 8) are also applicable in an analogous manner to the methods described below. For example, method 1000 optionally includes one or more of the characteristics of the various methods described above with reference to method 800. For example, the log entry displayed at 1002 of method 1000 may be based on the event generated at 804 of method 800. For the sake of brevity, these details will not be repeated below.

[0202] 9A-9M illustrate example systems and user interfaces for health-related coaching using electronic devices.

[0203] 9A shows a device 900 that is a tablet computer. In some embodiments, device 900 is or includes one or more features of devices 100, 300, 500, and / or 612. Device 900 includes a touch-sensitive display 902 that functions as both a display and an input device. Device 900 also includes one or more wireless communication antennas for communicating with external electronic devices, such as devices 606-1, 608-1, and 610-1 of FIG. 6.

[0204] 9A , device 900 displays a participant list interface 904. Interface 904 includes affordances 904-1A, 904-1B, and 904-1C that correspond to various participant devices currently sharing health-related data (e.g., blood glucose data and health-related event data) with device 900. Interface 904 also includes region 904-2 that includes multiple affordances for sorting, searching, and modifying the participants listed in interface 904.

[0205] In Figure 9A, the device 900 detects an input 906 (e.g., a touch) on an affordance 904-1A that corresponds to participant 1 (e.g., participant 1 in Figure 6). In response to the input, the device 900 displays an overview interface 908 for participant 1, as seen in Figure 9B.

[0206] In FIG. 9B, device 900 displays an overview interface 908. Interface 908 includes a navigation area 908-1 that includes affordances such as affordances 908-1A ("Overview") and 908-1B ("Log Data") for navigating between particular interfaces. Affordance 908-1A is now visually distinct to indicate that the current user interface is the overview interface 908. Interface 908 also includes an affordance for navigating to a view for entering comments by a coach using device 900 regarding participant 1's data ("Comments"). Interface 908 also includes an affordance for navigating to a view for reviewing event-related photos submitted by participant 1 ("Photo Check").

[0207] The interface 908 also includes a graph 908-2 illustrating blood glucose data for participant 1. In some embodiments, the blood glucose data is transmitted to the device 900 by one or more of the devices 606-1, 608-1, and 610-1 of FIG. 6 associated with participant 1. As shown, the graph 908-2 has an x-axis illustrating a repeating 24-hour period across multiple days (e.g., the days of session 3 as shown in the graph). The graph 908-2 has a y-axis. As shown, the graph 908-2 includes three lines of blood glucose data, 908-2A, 908-2B, 908-2C, for each of the three days currently logged in session 3 for participant 1. Thus, since blood glucose levels often follow a daily cycle, the graph 908-2 provides the ability to compare blood glucose levels for participant 1 for the same time of day (e.g., 9AM) across multiple days. In some embodiments, device 900 may rescale or modify the graph based on a detected input (e.g., a pinch or swipe gesture) on display 902. Graph 908-2 also includes an indication 908-2D that indicates a period during which participant 1's heart rate exceeded 50% of a maximum heart rate (e.g., maximum heart rate for the depicted period). Graph 908-2 also includes an indication 908-2E that indicates a period during which participant 1's heart rate exceeded a high threshold (64% of maximum). In some embodiments, providing heart rate data in addition to blood glucose data may provide a participant or coach with information indicative of the effect of cardiovascular exercise on blood glucose levels.

[0208] The interface 908 also includes a high response area 908-3 that includes affordances for the subset of glucose data that meets the reporting criteria (also called excursions). In some embodiments, the device 900 identifies and surfaces glucose data that indicates a significant rate of increase in blood glucose or a significant absolute value of blood glucose that exceeds a threshold. In FIG. 9B, the device 900 identifies two salient incidents and displays affordances 908-3A and 908-3B. As shown, each affordance can also include related information. For example, affordance 908-3A includes an indication "coffee with 2 sugars" to indicate that a food / drink event was logged at or near the time associated with the salient data. Affordance 908-3B includes an indication "no meal, no activity" to indicate that no events were logged at or near the time associated with the salient data.

[0209] In Figure 9B, the device 900 detects an input 910 (e.g., a touch) on affordance 908-3A that corresponds to the first high-response data. In response to the input, the device 900 displays participant 1's day interface 912, as seen in Figure 9C.

[0210] In FIG. 9C, the device 900 displays a day interface 912 superimposed on the interface 908. The interface 912 includes a graph 912-1 corresponding to the data illustrated by line 908-2A of the interface 908. As seen in FIG. 9C, that line corresponds to the blood glucose data of participant 1 for day 1 (Monday) of session 3. The graph 912-1 also includes indicators 912-2A and 912-2B corresponding to events logged in the graph by participant 1. The logged events are also shown in an area 912-3 that includes an indication of two respective events, 912-3A (a food / drink event (coffee with two sugars)) and 912-3B (an activity event ("running")). In some embodiments, the area 912-3 is scrollable to show additional events logged for the currently displayed day. Area 912-3 also includes affordances 912-3A1 and 912-3A2, both associated with event 912-3A. Affordance 912-3A1 can be used to initiate the process of generating a food challenge. Affordance 912-3A2 can be used to initiate the process of generating a habit challenge. In some embodiments, each event displayed in area 912-3 includes associated affordances for creating food and event challenges, and scrolling up area 912-3 reveals the affordance for event 912-3B. As shown in graph 912-1, participant 1's blood glucose level rose dramatically after event 912-3A and decreased slightly after event 912-3B. In some embodiments, a coach using device 900 can select to issue a food challenge to guide participant 1 to modify the participant's consumption activity to mitigate the dramatic increase in blood glucose.

[0211] In Figure 9C, device 900 detects an input 914 (e.g., a touch) on affordance 912-3A1. In response to the input, device 900 displays a food challenge interface 916, as seen in Figure 9D.

[0212] In Figure 9D, the device 900 displays an interface 916 for creating a new food challenge for participant 1. The interface 916 includes an area 916-1 for entering a name for the challenge, which also serves as a food / drink related action for participant 1 to perform to fulfill the challenge. In some embodiments, the interface 916 includes separate fields for the name of the challenge and the action(s) required to fulfill the challenge. The interface 916 is displayed along with a keyboard 918 for entering text.

[0213] In FIG. 9E, device 900 detects keyboard input and, in response, displays text 920 ("Coffee with no sugar") as an action for participant 1 to take to fulfill the challenge issued in response to the event "Coffee with 2 sugars." In FIG. 9E, device 900 detects input 922 on an exit affordance 924. In response to the input, device 900 creates a food challenge and transmits data corresponding to the challenge to a device(s) associated with participant 1 (e.g., devices 606-1, 608-1, and 610-1). In some embodiments, the transmitted data causes participant 1's device to prompt participant 1 to log a response event, as described above with respect to FIGS. 7I-7K.

[0214] FIGURE 9F shows device 900 re-displaying interface 908 after generating and submitting a food challenge associated with event 912-3A. In FIGURE 9F, device 900 detects an input 926 on affordance 908-1B. In response to the input, device 900 displays log data interface 928, as seen in FIGURE 9G.

[0215] 9G, device 900 displays logged data interface 928. Interface 928 includes a graph 928-1 showing blood glucose data for participant 1 over the period of the third logged day of session 3. Thus, the x-axis is the full range of logged data for session 3 and the y-axis is blood glucose. A single line 928-1A is a composite of the data shown by lines 908-2A, 908-2B, and 908-2C of interface 908.

[0216] Interface 928 includes region 928-2 with affordance(s) for the logged day of the currently selected session. In FIG. 9G, it includes affordances 928-2A, 928-2B, and 928-2C for each of the three logged days of session 3. Each affordance also includes a summary of the events logged on that day (e.g., "1 meal, 1 activity").

[0217] In Figure 9G, device 900 detects input 930 (e.g., a touch) on affordance 928-2B corresponding to day 2 of session 3. In response to the input, device 900 displays a day interface 932, as seen in Figure 9H.

[0218] In FIG. 9H, the device 900 displays a day interface 932. The interface 932 includes similar elements as the day interface 912, but provides data for day 2 of session 3 instead of day 1. For example, the interface 932 also includes a graph, graph 932-1. A region 932-2 of the interface 932 includes events logged by participant 1 on day 2, including events 932-2A, 932-2B, and 932-2C. As shown in FIG. 9H, each event is associated with its own affordance for creating a corresponding food challenge or a corresponding habitual challenge. For example, the event 932-2C is associated with a food challenge affordance 932-2C1 and a habitual challenge affordance 932-2C2.

[0219] In Figure 9H, device 900 detects input 934 (e.g., a touch) on affordance 932-2C2 corresponding to day 2 of session 3. In response to the input, device 900 displays a habitual challenge interface 936, as seen in Figure 9I.

[0220] 9I shows the device 900 displaying a habitual challenge interface 936 after input 934 and after further input. Specifically, the device 900 detects a keyboard input corresponding to entering the text string "run 6 miles" in field 936-1, which serves as both the name of the challenge and the action to be taken (or forego) to satisfy the habitual challenge. In some embodiments, the interface 936 includes separate fields for the name of the challenge and the action(s) to be taken (or forego) to satisfy the habitual challenge.

[0221] In FIG. 9I , device 900 detects input 938 (e.g., a touch) on exit affordance 940. In response to the input, device 900 creates a habitual challenge and transmits data corresponding to the challenge to a device(s) associated with participant 1 (e.g., devices 606-1, 608-1, and 610-1). In some embodiments, the transmitted data causes participant 1's device to prompt participant 1 to log a response to the habitual challenge, as described above with respect to FIGS. 7I-7K.

[0222] In Figure 9J, the device 900 re-displays the interface 928 after creating and sending a habitual challenge associated with the event 932-2C. In Figure 9J, the device 900 detects an input 942 on a challenge affordance 944. In response to the input, the device 900 displays a challenge interface 946.

[0223] 9K, the device displays a challenge interface 946. Interface 946 includes a current challenge region 946-1 that includes affordances 946-1A, 946-1B, and 946-1C that correspond to currently active challenges (e.g., both food and habitual challenges) that have been sent to participant 1's device(s). As shown, region 946-1 includes affordances for a newly created food challenge (946-1B) and a newly created habitual challenge (946-1C).

[0224] Interface 946 also includes region 946-2, which includes affordance(s) for any challenge for which at least one response has been received. In FIG. 9K, a previously created challenge associated with affordance 946-1A ("Substitute almond milk for coffee") has been responded to / met three times. Thus, region 946-2 includes affordance 946-2A for viewing data corresponding to that challenge response.

[0225] In Figure 9K, device 900 detects input 948 (e.g., a touch) on affordance 946-2A corresponding to day 2 of session 3. In response to the input, device 900 displays a challenge-response interface 950, as seen in Figure 9L.

[0226] In FIG. 9L, the electronic device 900 displays a challenge response interface 950. The interface 950 includes a graph 950-1 of participant 1's blood glucose data for a time period associated with the response event and associated with the original event at which the challenge was issued. The graph 950-1 includes a blood glucose data line 950-1A corresponding to participant 1's blood glucose data around the time the first response event (of three) was logged. The graph 950-1 also includes a blood glucose data line 950-1B corresponding to participant 1's blood glucose data around the time the original event at which the challenge was issued. The graph 950-1 also includes an indication 950-1C marking the time the first response event was recorded. Thus, the graph 950-1 provides a view for easily comparing the impact of challenge actions on participant 1's blood glucose level.

[0227] In Figure 9L, the device 900 detects an input 952 (e.g., a touch) on the next affordance 954. In response to the input, the device 900 updates the challenge response interface 950 to show data associated with the second response event (of three) for the selected challenge, as shown in Figure 9M.

[0228] In Figure 9M, blood glucose data line 950-1A reflects participant 1's blood glucose data before and after the time the second response event was logged. Similarly, indicator 950-1C now marks the time the second response event was logged. Note that blood glucose data line 950-1B remains the same, corresponding to participant 1's blood glucose data before and after the time of the original event where the challenge was issued.

[0229] 10 is a flow diagram illustrating a method for health-related coaching using an electronic device according to some embodiments. Method 1000 is performed on a first electronic device (e.g., 100, 300, 500, 612, 900) (e.g., a personal computer, laptop computer, smartphone, tablet computer) having a display device (e.g., 902) (e.g., an integrated touch-sensitive display) and one or more input devices (e.g., 902) (e.g., a mouse, touchpad, touch-sensitive display). Some operations of method 1000 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0230] As described below, the method 1000 provides an intuitive way to log health-related events. The method reduces the cognitive burden on the user during health-related coaching, thereby creating a more efficient human-machine interface. For battery-operated computing devices, it conserves power and extends the time between battery charges by enabling users to log health-related events more quickly and efficiently.

[0231] The first electronic device displays (1002) via a display device (e.g., 902) a first log entry (e.g., 912-3A) corresponding to a first event (e.g., a food-related event, an activity or exercise-related event) associated with a user of a second electronic device (e.g., 606-1 or 700) (e.g., a personal computer, laptop computer, smartphone, tablet computer that sent data to the first electronic device).

[0232] In some embodiments, displaying the first log entry (e.g., 912-3A) includes displaying a first time point (e.g., 12PM on January 1st) associated with (e.g., in combination with and displayed adjacent to) the first log entry, and first physiological data associated with a user of the second electronic device (e.g., 912-1) (e.g., blood glucose value, heart rate, physiological data specifically associated with the first time point) that is associated with (e.g., in combination with and displayed adjacent to) the first log entry.

[0233] In some embodiments, the first physiological data includes blood glucose data (eg, as seen at 912).

[0234] In some embodiments, displaying the first physiological data includes displaying a plurality of values ​​of the first physiology associated with a range of consecutive time points over a first period of time (e.g., days) (e.g., as seen at 912). Concurrently with displaying the first physiological data, the first electronic device, via the display device, displays second physiological data (e.g., heart rate data 912-2B) associated with a user of a second electronic device that is distinct from the first physiological data (e.g., the first physiological data is blood glucose and the second physiological data is heart rate), the second physiological data being associated with a subset of time points (e.g., time points associated with 912-2B) within the range of consecutive time points (e.g., a subset of days on which the heart rate was above a threshold amount (e.g., above 50% of the maximum heart rate for that day)). By displaying the first and second physiological data simultaneously, feedback is provided to the user regarding the relationship between the first and second physiological data. Providing improved feedback may improve usability of the device and result in a more efficient user-device interface (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device), which may further reduce power usage and improve the battery life of the device by allowing the user to use the device more quickly and efficiently.

[0235] In some embodiments, the first event (eg, 912-3A) is associated with consumption of a food or beverage by a user of the second electronic device.

[0236] The first electronic device, while displaying a first log entry corresponding to a first event (e.g., a food-related event, an activity, or an exercise-related event), receives (1004) a first set of one or more inputs (e.g., including input 914) (e.g., a series or sequence of inputs) corresponding to a request to send a first event challenge (e.g., the challenge created in FIG. 9E) to a user associated with the second electronic device via a first input device (e.g., 902) of the one or more input devices, the first set of one or more inputs including a first input (e.g., an input entering text 920 in 916-1) corresponding to (e.g., the input generates, creates, constructs) a set of one or more event conditions (e.g., a set of one or more actions to be performed or not performed (e.g., forgoed)).

[0237] The first electronic device transmits (1006) data representing a first event challenge to the second electronic device in response to a first set of one or more inputs. The data representing the first event challenge includes a prompt (e.g., the prompt seen at 736) to a user of the second electronic device to log a challenge response event (e.g., an event logged in response to the challenge) based on a set of one or more event conditions (e.g., the transmitted challenge data includes instructions that, when executed on the second electronic device, cause the device to issue a prompt (e.g., the issued prompt includes an indication of the set of one or more event conditions). In some embodiments, the data representing the event challenge includes data that associates (e.g., links and / or identifies) the event challenge with the first event. Transmitting data representing the first event challenge that includes a prompt to the second device to log a challenge response event reduces the number of inputs required to affect coordination between the first electronic device and the second electronic device, thereby improving operability of both devices. Improving the usability of the device makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors) and also reduces power usage and improves the battery life of the device by allowing the user to use the device more quickly and efficiently.

[0238] In some embodiments, subsequent to displaying the first log entry, the first electronic device displays (1008) via the display device a first affordance (e.g., 912-3A1) corresponding to a first type of event challenge (e.g., a challenge associated with a particular point in time (e.g., a challenge associated with consumption of a food or beverage at a particular point or time of a day)) and a second affordance (e.g., 912-3B) corresponding to a second type of event challenge different from the first type (e.g., a challenge associated with a day but not with a particular time of that day), and the first set of one or more inputs includes a second input (e.g., 914) received while displaying the first affordance and the second affordance. In response to a second input in the first set of one or more inputs, the first electronic device includes an indication in the data transmitted to the second electronic device that the first event challenge is of the first type pursuant to a determination that the second input in the first set of one or more inputs corresponds to the first affordance. In response to a second input from the first set of one or more inputs, the first electronic device includes an indication in the data transmitted to the second electronic device that the first event challenge is of a second type in accordance with a determination that the second input from the first set of one or more inputs corresponds to the first affordance. In some embodiments, the transmitted data causes the second electronic device to issue a different prompt depending on whether the challenge is of the first type or the second type. By including an indication of whether the event challenge is of the first type or the second type based on the user input in the transmitted challenge data, the number of inputs required to specify the characteristics of the event challenge is reduced. Reducing the number of inputs required to perform this operation improves usability of the first electronic device.Improving the usability of the device makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors) and also reduces power usage and improves the battery life of the device by allowing the user to use the device more quickly and efficiently.

[0239] In some embodiments, the first event challenge is a first type of challenge, the prompt includes a prompt to the user to log a second event (e.g., at a particular time (e.g., at a particular time of day, at a particular time within a day, at a time more precise than a day)) based on (e.g., based on satisfying) a set of one or more event conditions, and the transmitted data representing the set of one or more event conditions of the first event challenge includes an indication (e.g., as seen at 736) of a first set of one or more actions to be taken (e.g., actions related to consumption of a food or beverage at a particular point or time within a day).

[0240] In some embodiments, the first event challenge is a second type of challenge and the prompt includes a prompt to the user to log a challenge response event (e.g., on a particular date (e.g., a date that does not include a particular time within the date)) based on a set of one or more event conditions. The transmitted data representing the set of one or more event conditions of the first event challenge includes an indication (e.g., as seen at 736) of a second set of one or more actions (e.g., actions related to consuming a food or beverage or actions related to performing a physical activity (e.g., exercising)) and an indication of whether the second set of one or more actions is or is not performed.

[0241] In some embodiments, the first electronic device displays, via the display device, concurrently with the display of the first log entry, a second log entry (e.g., 932-2B) corresponding to a second event associated with the user of the second electronic device (e.g., a second event logged on the same day as the first event), a third affordance associated with the second log entry (e.g., a food challenge affordance associated with 932-2B) that, when selected, initiates a process of sending a second event challenge (e.g., a first or second type challenge) to the user associated with the second electronic device, a third log entry corresponding to a third event associated with the user of the second electronic device, and a fourth affordance associated with the third log entry (e.g., a habit challenge affordance associated with 932-2B) that, when selected, initiates a process of sending a third event challenge to the user associated with the second electronic device. In some embodiments, the first electronic device displays multiple log entries corresponding to the same time period (e.g., the same day). Each of the log entries includes one or more affordances for issuing an event challenge associated with the respective log entry. Displaying the first log entry in association with the second log entry, along with its associated affordance, provides improved feedback regarding which log entry was received by the first electronic device and improved options for performing associated functions with less input. Providing improved feedback improves usability of the device and provides a more efficient user-device interface (e.g., by helping the user make appropriate inputs and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the device's battery life by allowing the user to use the device more quickly and efficiently.

[0242] In some embodiments, the first electronic device, after transmitting data representative of the first event challenge, displays a first user interface (e.g., 946) (e.g., a transmitted challenge user interface) via a display device. The first user interface includes a first area (e.g., 946-1) (e.g., a pending challenge area) and a second area (e.g., 946-2) (e.g., a completed / responded challenge area) that includes a representation (e.g., 946-1A) of the first event challenge (e.g., a representation including an affordance (e.g., a selectable representation), one or more details of the first event challenge (e.g., details regarding a set of one or more event conditions, details regarding the first event). Data representative of the first challenge response event is received from the second electronic device (e.g., the first In accordance with a determination that data representing a first challenge response event has not been received at the second electronic device, the second area includes a representation of the first challenge response event (e.g., 946-2A). In accordance with a determination that data representing a first challenge response event has not been received at the second electronic device, the second area does not include a representation of the first challenge response event (in some embodiments, the second area only includes a representation associated with an issued / transmitted event challenge for which at least one challenge response event has been received).

[0243] In some embodiments, the first challenge response event is responsive to the first event challenge. While displaying a representation of the first challenge response event, the first electronic device receives a second set of one or more inputs (e.g., 948) corresponding to a request to display a response event user interface (e.g., 950) corresponding to the first challenge response event. In response to the second set of one or more inputs, the first electronic device displays the response event user interface via the display device. The response event user interface includes third physiological data (e.g., 950-1B) (e.g., as a line graph) associated with the user of the second electronic device corresponding to the first event (e.g., physiological data associated with the first event (e.g., physiological data when the first event was logged at the second electronic device)) and fourth physiological data (e.g., 950-1A) (e.g., physiological data associated with the first challenge event response (e.g., physiological data when the first challenge event response was logged at the second electronic device)) different from the second physiological data associated with the user of the second electronic device corresponding to the first challenge response event (e.g., physiological data associated with the first challenge event response (e.g., physiological data when the first challenge event response was logged at the second electronic device)). Displaying the third and fourth physiological data simultaneously provides feedback to the user regarding the relationship between the second and third physiological data. Providing improved feedback may improve usability of the device and result in a more efficient user-device interface (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device), which may further reduce power usage and improve the battery life of the device by allowing the user to use the device more quickly and efficiently.

[0244] In some embodiments, the first electronic device displays a second user interface (e.g., 908) (e.g., a summary user interface including multiple days of physiological data for the same range of times of the day) via a display device. The second user interface includes a plurality of representations (e.g., 908-2A, 908-2B, 908-2C) (e.g., a plurality of lines on a graph) of physiological data associated with a user of the second electronic device, including a first representation (e.g., a first line on a graph) of physiological data for a first occurrence (e.g., first day (e.g., January 1)) of a first recurring time period (e.g., morning, 12AM-11:9PM, 24 hour clock), a second representation of physiological data for a second occurrence (e.g., first day (e.g., January 1)) of the first recurring time period, and a fifth affordance (e.g., 908-3A) (e.g., a title affordance including a representation of the subset of physiological data) corresponding to a subset of the physiological data for the first occurrence that satisfies a set of reporting criteria (e.g., criteria based on one or more factors selected from a rate of change (e.g., specifically a rate of increase) of a physiological parameter of the data and an absolute value of the physiological data exceeding a threshold). Displaying a fifth affordance corresponding to a subset of the data that meets a set of reporting criteria provides feedback to the user regarding portions of the data that are potentially important, reducing the number of inputs required to identify and display the potentially important data. Providing improved feedback improves usability of the device and makes the user-device interface more efficient (e.g., by helping the user make appropriate inputs and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the device's battery life by allowing the user to use the device more quickly and efficiently.

[0245] In some embodiments, the first electronic device receives a third set of one or more inputs (e.g., 910) corresponding to a selection of the fifth affordance. In response to receiving the third set of one or more inputs, the first electronic device displays a third user interface (e.g., 912) (e.g., an interface associated with the first occurrence (e.g., day)) via the display device. The third user interface includes a third representation (e.g., 912-1) (a graph line) of the physiological data for the first occurrence of the first recurring period. The third user interface includes a representation (e.g., 912-3A) (e.g., a graph representation of a time at which the fourth event was logged) in accordance with a determination that the first occurrence of the first recurring period is associated with a third log entry corresponding to the fourth event. The third user interface does not include a representation of the third log entry in accordance with a determination that the first occurrence of the first recurring period is not associated with a third log entry corresponding to the fourth event.

[0246] In some embodiments, the first electronic device displays a fourth user interface (e.g., 928) (e.g., a summary user interface including multiple days of physiological data for the same range of times of the day) via the display device. The fourth user interface includes a fourth representation (e.g., 928-1A) of physiological data for a first occurrence (day 1, January 1) of a second recurring period (e.g., 24-hour clock) and a second occurrence (e.g., day 2, January 2) of the second recurring period associated with a user of the second electronic device, as well as a sixth affordance corresponding to the first occurrence of the second recurring period (e.g., not associated with the second occurrence). In some embodiments, selection of the sixth affordance causes physiological data associated with the first occurrence of the recurring period to be displayed without causing physiological data corresponding to the second occurrence of the second recurring period to be displayed.

[0247] In some embodiments, the first electronic device displays, via the display device, a fourth log entry corresponding to a fifth event (e.g., a food-related event, an activity or exercise-related event) associated with a user of a third electronic device (e.g., 606-2) that is different from the first electronic device and the second electronic device (e.g., a personal computer, laptop computer, smartphone, tablet computer that sent data to the first electronic device).

[0248] It should be noted that the processing details described above in connection with method 1000 (e.g., FIG. 10) are applicable in a similar manner to the methods described above. For example, method 800 optionally includes one or more of the characteristics of the various methods described above with reference to method 1000. For example, the first log entry generated at 804 of method 800 may be in response to a first challenge event sent at 1006 of method 1000. For the sake of brevity, these details will not be repeated below.

[0249] The above has been described with reference to specific embodiments for purposes of illustration. However, the above exemplary discussion is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teachings. The embodiments have been chosen and described in order to best explain the principles of the technology and their practical applications. In order to enable others skilled in the art to best utilize the technology and various embodiments with various modifications as suited to the particular applications intended.

[0250] Although the present 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, and such changes and modifications are to be understood as being included within the scope of the present disclosure and examples, as defined by the claims.

[0251] As mentioned above, one aspect of the present technology is to collect and use data available from various sources to improve the delivery to the user of content that the user desires or any other content that may be of interest to the user. The present disclosure contemplates that in some examples, this collected data may include personal information data that uniquely identifies a particular person or that can be used to contact or locate a particular person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, Twitter IDs, home addresses, data or records regarding the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), birth date, or any other identifying or personal information.

[0252] This disclosure recognizes that the use of such personal information data in the present technology may be for the benefit of the user. For example, personal information data may be used to record and deliver personalized health information to the user. Such use of personal information data may thus enable the user to improve logging and viewing of health information. Moreover, other uses of personal information data that benefit the user are also contemplated by this disclosure. For example, health and fitness data may be used to provide insight into the overall wellness of the user, or may be used as proactive feedback to individuals using the technology in pursuit of wellness goals.

[0253] This disclosure contemplates that entities involved in the collection, analysis, disclosure, transmission, storage, or other use of such personal information data will adhere to robust privacy policies and / or practices. Specifically, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for keeping personal information data confidential and secure. Such policies should be easily accessible by users and should be updated as data collection and / or use changes. Personal information from users should be collected for the entity's lawful and legitimate uses and should not be shared or sold except for those lawful uses. Furthermore, such collection / sharing should be conducted after informing and obtaining consent from the user. Furthermore, such entities should consider taking all necessary measures to protect and secure access to such personal information data and ensure that others having access to that personal information data adhere to their privacy policies and procedures. Furthermore, such entities may subject themselves to third-party assessments to attest to their adherence to widely accepted privacy policies and practices. Moreover, policies and practices should be adapted to the specific types of personal data collected and / or accessed, and should conform to applicable laws and standards, including jurisdiction-specific considerations. For example, in the United States, collection of or access to certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA), while health data in other countries may be subject to other regulations and policies and should be addressed accordingly. Therefore, different privacy practices should be maintained with respect to different types of personal data in each country.

[0254] Notwithstanding the foregoing, the present disclosure also contemplates embodiments in which a user selectively blocks use of or access to personal information data. That is, the present disclosure contemplates that hardware and / or software elements may be provided to prevent or block access to such personal information data. For example, in the case of a health monitoring service, the present technology may be configured to allow a user to select to "opt-in" or "opt-out" of participating in the collection of personal information data during registration for the service or at any time thereafter. In another example, a user may choose not to provide health-related data for a targeted content delivery service. In yet another example, a user may choose to limit the period of time that health-related data is maintained or to prohibit the development of a baseline health profile altogether. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notifications regarding access or use of personal information. For example, a user may be notified upon download of an app that will access the user's personal information data, and then again immediately before the personal information data is accessed by the app.

[0255] Moreover, it is the intent of this disclosure that personal information data should be managed and processed in a manner that minimizes the risk of unintended or unauthorized access or use. Risk can be minimized by limiting data collection and deleting it when it is no longer needed. Furthermore, where applicable, de-identification of data can be used to protect user privacy, including in certain health-related applications. De-identification can be facilitated by removing certain identifiers (e.g., date of birth, etc.) where appropriate, controlling the amount or specificity of data stored (e.g., collecting location data at a city level rather than an address level), controlling how data is stored (e.g., aggregating data across users), and / or other methods.

[0256] Thus, while this disclosure broadly encompasses the use of personal information data to implement one or more of the various disclosed embodiments, this disclosure also contemplates that the various embodiments may be implemented without requiring access to such personal information data. That is, the various embodiments of the present technology are not rendered inoperable by the absence of all or a portion of such personal information data. For example, content may be selected and delivered to a user by inferring preferences based only on a minimal amount of non-personal information data or personal information, such as content requested by a device associated with the user, other non-personal information available on a content delivery service, or publicly available information.

Claims

1. A first electronic device having a display device and one or more input devices, displaying via the display device a first log entry corresponding to a first event associated with a user of a second electronic device; generating data representative of a first event challenge; receiving, while displaying the first log entry corresponding to the first event, a first set of one or more inputs via a first input device of the one or more input devices corresponding to a request to send the first event challenge to the user associated with the second electronic device, the first set of inputs including a first input corresponding to a set of one or more event conditions; transmitting data representing the first event challenge to the second electronic device in response to the first set of one or more inputs; transmitting the data representing the first event challenge including a prompt to the user of the second electronic device indicating an action to be taken in response to the first event challenge to log a challenge response event based on the set of one or more event conditions; after transmitting the data representing the first event challenge; a first area including a representation of the first event challenge; A second region, responsive to determining that data representative of a first challenge response event is received from the second electronic device, the representation of the first challenge response event including an affordance for viewing data corresponding to the first challenge response event that, when selected, causes a display of physiological data associated with the first challenge response event; in response to a determination that data representative of the first challenge response event has not been received at the second electronic device, not including the representation of the first challenge response event. A second region; and and displaying via the display device a first user interface comprising:

2. After displaying the first log entry, a first affordance corresponding to a first type of event challenge; and displaying via the display device a first affordance and a second affordance corresponding to a second type of event challenge different from the first type, wherein the first set of one or more inputs includes a second input received while displaying the first affordance and the second affordance; in response to the second input of the first set of one or more inputs; in response to determining that the second input of the first set of one or more inputs corresponds to the first affordance, including in the data transmitted to the second electronic device an indication that the first event challenge is of the first type; in response to determining that the second input of the first set of one or more inputs corresponds to the first affordance, including in the data transmitted to the second electronic device an indication that the first event challenge is of the second type; The method of claim 1 further comprising:

3. the first event challenge is a challenge of the first type; the prompting includes a prompt to the user to log a second event based on the set of one or more event conditions; 3. The method of claim 2, wherein the transmitted data representing the set of one or more event conditions of the first event challenge includes an indication of a first set of one or more actions to be performed.

4. the first event challenge is a challenge of the second type; the prompting includes a prompt to the user to log the challenge response event based on the set of one or more event conditions; The transmitted data representing the set of one or more event conditions of the first event challenge: an indication of a second set of one or more actions; and an indication of whether the second set of one or more actions is performed or not performed; The method of claim 2 , comprising:

5. The method comprises: a second log entry corresponding to a second event associated with the user of the second electronic device; and a third affordance associated with the second log entry that, when selected, initiates a process of sending a second event challenge to the user associated with the second electronic device; and a third log entry corresponding to a third event associated with the user of the second electronic device; and a fourth affordance associated with the third log entry that, when selected, initiates a process of sending a third event challenge to the user associated with the second electronic device; and via the display device, simultaneously with the display of the first log entry; The method of claim 1 , further comprising:

6. Displaying the first log entry includes: a first time point associated with the first log entry; and first physiological data associated with the user of the second electronic device and associated with the first log entry; The method of claim 1 , further comprising:

7. The method of claim 6 , wherein the first physiological data includes blood glucose data.

8. Displaying the first physiological data includes displaying a plurality of values ​​of the first physiological data associated with a continuous range of time points over a first time period, the method comprising:

7. The method of claim 6, further comprising displaying, via the display device, second physiological data associated with the user of the second electronic device that is different from the first physiological data, the second physiological data being associated with a subset of time points within the continuous range of time points.

9. The first challenge response event is responsive to the first event challenge, and the method further comprises: receiving a second set of one or more inputs corresponding to a request to display a response event user interface corresponding to the first challenge response event while displaying the representation of the first challenge response event; In response to the second set of one or more inputs, the response event user interface further comprises: third physiological data associated with the user of the second electronic device corresponding to the first event; and fourth physiological data associated with the user of the second electronic device corresponding to the first challenge-response event, the fourth physiological data being different from the third physiological data; displaying the response event user interface via the display device; The method of claim 1 further comprising:

10. The method comprises: a plurality of representations of physiological data associated with the user of the second electronic device, the representations including a first representation of physiological data for a first occurrence of a first repeating period and a second representation of physiological data for a second occurrence of the first repeating period; and a fifth affordance corresponding to a subset of the physiological data for the first occurrence that satisfies a set of reporting criteria; The method of claim 1 , further comprising displaying via the display device a second user interface comprising:

11. The method comprises: receiving a third set of one or more inputs corresponding to a selection of the fifth affordance; in response to receiving the third set of one or more inputs; a third representation of physiological data for the first occurrence of the first repetition period; responsive to a determination that the first occurrence of the first repeating period is associated with a third log entry corresponding to a fourth event, a representation of the third log entry; and in response to a determination that the first occurrence of the first repeating period is not associated with the third log entry corresponding to the fourth event, not including the representation of the third log entry. displaying a third user interface via the display device; and The method of claim 10 further comprising:

12. The method comprises: a fourth representation of physiological data for a first occurrence of a second repetitive period associated with the user of the second electronic device and a second occurrence of the second repetitive period; and a sixth affordance corresponding to the first occurrence of the second repeating period; and The method of claim 1 , further comprising displaying via the display device a fourth user interface comprising:

13. The method of claim 1 , wherein the first event is associated with the consumption of a food or beverage by the user of the second electronic device.

14. The method comprises:

5. The method of claim 1, further comprising: displaying via the display device a fourth log entry corresponding to a fifth event associated with a user of a third electronic device different from the first electronic device and the second electronic device.

15. A computer program product configured to cause a computer having a display device and one or more input devices to carry out the method according to any one of claims 1 to 14.

16. A display device; one or more input devices; 16. A first electronic device comprising: a memory storing a computer program according to claim 15; and one or more processors capable of executing the computer program stored in said memory.

17. A first electronic device having a display device and one or more input devices, Means for carrying out the method according to any one of claims 1 to 14, A first electronic device comprising:

Images